This commit was manufactured by cvs2svn to create branch 'accessibility_work_R3_6'. Sprout from master 2009-10-20 10:49:54 UTC Tomasz Zarna <tzarna> 'The map file has been updated for the following Bug changes:' Delete: bundles/org.eclipse.jdt.doc.isv/.cvsignore bundles/org.eclipse.jdt.doc.isv/.project bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt bundles/org.eclipse.jdt.doc.isv/about.html bundles/org.eclipse.jdt.doc.isv/about.ini bundles/org.eclipse.jdt.doc.isv/about.mappings bundles/org.eclipse.jdt.doc.isv/about.properties bundles/org.eclipse.jdt.doc.isv/book.css bundles/org.eclipse.jdt.doc.isv/build.properties bundles/org.eclipse.jdt.doc.isv/build.xml bundles/org.eclipse.jdt.doc.isv/buildDoc.xml bundles/org.eclipse.jdt.doc.isv/cpy.png bundles/org.eclipse.jdt.doc.isv/eclipse32.png bundles/org.eclipse.jdt.doc.isv/guide/CopyrightTabPage.html bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeformatter.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_contributing_a_cleanup.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt bundles/org.eclipse.jdt.doc.isv/notices.html bundles/org.eclipse.jdt.doc.isv/plugin.properties bundles/org.eclipse.jdt.doc.isv/plugin.xml bundles/org.eclipse.jdt.doc.isv/porting/3.2/faq.html bundles/org.eclipse.jdt.doc.isv/porting/3.2/incompatibilities.html bundles/org.eclipse.jdt.doc.isv/porting/3.2/recommended.html bundles/org.eclipse.jdt.doc.isv/porting/3.3/faq.html bundles/org.eclipse.jdt.doc.isv/porting/3.3/incompatibilities.html bundles/org.eclipse.jdt.doc.isv/porting/3.3/recommended.html bundles/org.eclipse.jdt.doc.isv/porting/3.4/faq.html bundles/org.eclipse.jdt.doc.isv/porting/3.4/incompatibilities.html bundles/org.eclipse.jdt.doc.isv/porting/3.4/recommended.html bundles/org.eclipse.jdt.doc.isv/porting/3.5/faq.html bundles/org.eclipse.jdt.doc.isv/porting/3.5/incompatibilities.html bundles/org.eclipse.jdt.doc.isv/porting/3.5/recommended.html bundles/org.eclipse.jdt.doc.isv/porting/3.6/faq.html bundles/org.eclipse.jdt.doc.isv/porting/3.6/incompatibilities.html bundles/org.eclipse.jdt.doc.isv/porting/3.6/recommended.html bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_2_porting_guide.html bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_3_porting_guide.html bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_4_porting_guide.html bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_5_porting_guide.html bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_6_porting_guide.html bundles/org.eclipse.jdt.doc.isv/questions/index.html bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html bundles/org.eclipse.jdt.doc.isv/schema.css bundles/org.eclipse.jdt.doc.isv/toc.xml bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml bundles/org.eclipse.jdt.doc.user/.project bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF bundles/org.eclipse.jdt.doc.user/about.html bundles/org.eclipse.jdt.doc.user/about.ini bundles/org.eclipse.jdt.doc.user/about.mappings bundles/org.eclipse.jdt.doc.user/about.properties bundles/org.eclipse.jdt.doc.user/book.css bundles/org.eclipse.jdt.doc.user/build.properties bundles/org.eclipse.jdt.doc.user/build.xml bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm bundles/org.eclipse.jdt.doc.user/concepts/cdebugger.htm bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-access-rules.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-build-classpath.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-classpath-variables.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-editor-templates.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-inclusion-exclusion-patterns.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-editor.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-perspective.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-project.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-search.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-decorators.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-filtering.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-presentation.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-sorting.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-jdt.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-quickfix-assist.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-refactoring.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-string-externalization.htm bundles/org.eclipse.jdt.doc.user/concepts/concept-template-variables.htm bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm bundles/org.eclipse.jdt.doc.user/concepts/cscrapbook.htm bundles/org.eclipse.jdt.doc.user/concepts/images/qs-37a.png bundles/org.eclipse.jdt.doc.user/contexts_APT.xml bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml bundles/org.eclipse.jdt.doc.user/cpy.png bundles/org.eclipse.jdt.doc.user/eclipse32.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/active_break_point.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_as_source_folder.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_linked_source_to_buildpath.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/debug_button.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/edit_undo_refactoring_menu.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_display.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_sysytem_get.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_field.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_getters.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_import.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_moved.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_outline_override.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname_quickfix.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_hover.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_unsaved.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_search_references.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_extract_method.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_outline_collectinheritedmethod.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist_t.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_debug.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_e.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_expected.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_inspect.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_organized_imports.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_outline_main.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_problem_hover.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_quickoutline.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_testSizeIsThree.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_exp.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_integer.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_preview_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/generate_getter_setter_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull_workspace_modifed.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox-coloring.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/compiler-property-page.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/editor_override_annotation_hover.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/enum.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-inserted.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-proposal.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/infer-generic.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/inferred-generic.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/quick-fix.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-applied.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-proposed.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/unused-warning.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_incompatible.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_inexact.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_unfiltered.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/wiz_new_java_project_myproject.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/move_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_open_typehieracrchy.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opendeclaration.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opentype.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/open_run_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/override_implement_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/packagefolder_obj.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_buildpath.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_compiler.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_editor.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_jre.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_launch_operation.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_workspace.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/previous_searches_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout1.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout2.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout3.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout4.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources1.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources2.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources3.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources4.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources5.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources6.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout10.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout11.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout12.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout13.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout14.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout15.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout20.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout21.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout22.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout23.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout24.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout25.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout26.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout27.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout28.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout29.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout30.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout31.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout32.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout33.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout34.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout35.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout36.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout40.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout41.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout42.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout43.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout44.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout45.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout46.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout47.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout48.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout49.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout50.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout51.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout52.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout53.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout54.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout55.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout56.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout57.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout58.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout59.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5a.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5b.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout60.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout61.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout62.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout63.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout64.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout65.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout66.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout67.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout68.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout69.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6a.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6b.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6c.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_menu.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_submethods.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialog_setup.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialogs.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_preview_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/replace_local_element.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/restore_local_history.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_arguments.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_junit.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dropdown.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_file_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_next.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_prev.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_runTest_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_how.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_java_app_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/superclass_selection_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_noarg.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_success.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug_removelaunched.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display_done.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_inspect.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_junit_red.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_delete_import.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_search_references.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_main.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_run.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest_filtered.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit_exp.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_open_type_hierarchy.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_vectortest_error.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_problems_goto.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_editor_runTest.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_previous.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_research_menu.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_runTest.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_focused.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_menu.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_runtest_locked.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_small.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_subtype.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype_locked.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_1.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_logical_structures.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_import_arch.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog_superchecked.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_project.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_scrap.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_suite.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_testcase.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_debug_vectortest.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_java_browsing.png bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_testcase_errors.png bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Quickviews.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm bundles/org.eclipse.jdt.doc.user/images/ngrelc.png bundles/org.eclipse.jdt.doc.user/images/ngrelr.png bundles/org.eclipse.jdt.doc.user/images/ngrelt.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/export_brkpts.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/import_brkpts.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/next_thread_nav.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prev_thread_nav.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prop_ps.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeerr_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeout_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_grp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_references.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/autoform_menu.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/threadgroup_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/flatLayout.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/hierarchicalLayout.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/history_list.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testignored.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/category_menu.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/copy_qualified.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/cpyqual_menu.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/javaassist_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/jtypeassist_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/templateprop_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/wordassist_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/toggle_breadcrumb.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_src_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_linked_rename.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/settings_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_swt_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/testfile_obj.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/annotation_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_abs_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/enum_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/interface_tsk.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/library_ovr.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/date_mode.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/filter_ps.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/prj_mode.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/change.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/composite_change.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/date_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/error_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/fatalerror_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/file_change.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/info_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactoring_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactorings_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/text_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/time_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/warning_obj.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/clear_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/console_view.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/cut_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/lock_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/new_con.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/paste_edit.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/pin.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/rem_co.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/next_nav.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/prev_nav.png bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/show_whitespace_chars.gif bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.workbench.texteditor/etool16/block_selection_mode.gif bundles/org.eclipse.jdt.doc.user/notices.html bundles/org.eclipse.jdt.doc.user/plugin.properties bundles/org.eclipse.jdt.doc.user/plugin.xml bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_caught.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_condition.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_enabled.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_entry.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_exit.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_hitcount.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendpolicy.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendsubclass.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_uncaught.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_access_option.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_mod.PNG bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-access_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-caught_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-condition_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-enabled_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-entry_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-exit_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-hitcount_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-modification_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendpolicy_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendsubclass_option.htm bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-uncaught_option.htm bundles/org.eclipse.jdt.doc.user/reference/images/c-quickfix.png bundles/org.eclipse.jdt.doc.user/reference/images/contentassist.png bundles/org.eclipse.jdt.doc.user/reference/images/ref-breadcrumb.png bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/add_class_load_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_as.PNG bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_history.PNG bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_as.PNG bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_history.PNG bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-add_class_load_breakpoint.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-addwatch.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_as.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_history.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-dll_debug.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-menu-run.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_debug_dialog.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_run_dialog.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-rll_run.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_as.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_history.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_to_line.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-step_into_selection.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_breakpoint.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_line_breakpoint.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_method_breakpoint.htm bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_watchpoint.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-member-sort-order.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-type-filters.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-user-libraries.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-cleanup.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-code-templates.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-formatter.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-organize-imports.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-building.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-javadoc.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-task-tags.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-debug.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-detail_formatters.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-execution_environments.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-heap_walking.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-installed_jres.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-logical_structures.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-primitive_display_options.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-step_filtering.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-advanced.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-favorites.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-edit-template-dialog.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-folding.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-hovers.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-mark-occurrences.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-save-actions.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-syntax-coloring.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-templates.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-typing.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-appearance.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-build-path.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-code-style.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-compiler.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-editor.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-installed-jres.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-junit.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-properties-files-editor.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/ref-preferences-java.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-default_launchers.PNG bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-ext_string_subbed.PNG bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-lcd_string_subbed.PNG bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_sub.PNG bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-console.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-default_launchers.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launch_configurations.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launching.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-perspectives.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-run_debug.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-string_substitution.htm bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-view_management.htm bundles/org.eclipse.jdt.doc.user/reference/propertypages/images/rundebug-proppage.PNG bundles/org.eclipse.jdt.doc.user/reference/propertypages/ref-properties-rundebug.htm bundles/org.eclipse.jdt.doc.user/reference/ref-actions-toolbar.htm bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-configure-working-sets.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-search.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-open-type.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-tostring.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-type-selection.htm bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-working-set-assignments.htm bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm bundles/org.eclipse.jdt.doc.user/reference/ref-icons.htm bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-breadcrumb.htm bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-code-assist.htm bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickassist.htm bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-actions.htm bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-faq.htm bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-glossary.htm bundles/org.eclipse.jdt.doc.user/reference/ref-keybindings.htm bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm bundles/org.eclipse.jdt.doc.user/reference/ref-properties-build-path.htm bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm bundles/org.eclipse.jdt.doc.user/reference/ref-properties-source-attachment.htm bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm bundles/org.eclipse.jdt.doc.user/reference/ref-refactoring-extract-method.htm bundles/org.eclipse.jdt.doc.user/reference/ref-toolbar-run.htm bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-listcontent.htm bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-styles.htm bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-templates.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-annotation.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-class.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-enum.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-interface.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-java-project.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-package.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-refactorings.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-scrapbook.htm bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-source-folder.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views-breakpoint_set_hitcount_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_accesscontext.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_addexceptiondialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_caughtcontext.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_defaultworkingset_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_entrycontext.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_exitcontext.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbyadvanced_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbymenu.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_modcontext.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_select_default_workingset_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_skipall_example.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_uncaughtcontext.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingset_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingsets.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoints_view.PNG bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-access_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-addexception_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-breakpoints_view.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-caught_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-disable_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-enable_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-entry_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-exit_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-expandall_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-export_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-gotofile_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-groupby_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-hitcount_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-import_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-linkwith_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-modification_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-properties_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-remove_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-removeall_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-selectdefaultws_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-showsupported_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-skipall_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-suspendpolicy_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-uncaught_contextaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-workingsets_viewaction.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-console_view.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-cvs_console.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-format_context.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-open_console_menu.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-openlink_context.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-prefs_context.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-removeterminated_context.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-stacktrace_console.PNG bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-autoformat_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-clear_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-cvs_console.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-display_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-format_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-open_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-openlink_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-pin_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-prefs_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-process_console.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removeallterminated_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removelaunch_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-scrolllock_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_err_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_out_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-stacktrace_console.htm bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-terminate_action.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb.png bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb_drop_down.png bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-configdialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-debug_view.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editlaunchconfig.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editstepfilters.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filterpackage.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filtertype.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-find_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-lookupsource.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_supported.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_unsupported.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclared.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclaredhier.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog2.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-sourcelookupdialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmanagement.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmng_menu.PNG bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-breadcrumb.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-debug_view.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-disconnect.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-droptoframe.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editlaunchconfig.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editsourcelookup.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editstepfilters.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-executioncontrolcommands.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filterpackage.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filtertype.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_automatic.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb_auto_expand.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_tree.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-lookupsource.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclared.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclaredhier.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-properties.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-relaunch.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-removeallterminated.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-resume.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showmonitors.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showsystemthreads.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showthreadgroups.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepinto.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepover.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepreturn.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-suspend.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminate.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateall.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateandremove.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminaterelaunch.htm bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-usestepfilters.htm bundles/org.eclipse.jdt.doc.user/reference/views/display/images/ref-display_view.PNG bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-clear.htm bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-display_view.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-addwatchexpression_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-convert.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-disable.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-enable.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-expressions_view.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-java.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-reevaluate.PNG bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-addwatch.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-convert.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-disable.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-edit.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-enable.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-expressions_view.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-inspect.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-reevaluate.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-remove.htm bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-removeall.htm bundles/org.eclipse.jdt.doc.user/reference/views/ref-call-hierarchy.htm bundles/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm bundles/org.eclipse.jdt.doc.user/reference/views/ref-type-hierarchy.htm bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-package-explorer.htm bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-scrapbook.htm bundles/org.eclipse.jdt.doc.user/reference/views/ref-viewsandeditors.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-action.png bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-code.png bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeobjectvalue.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeprimitivevalue.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changestringvalue.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-contentassist.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-displayresult.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-find_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-findreplace_dialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-inspectresult.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-javapreferences.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectcolumnsdialog.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectedstatement.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-showreferences.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewdisplaycommands.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewlayoutmenu.PNG bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allinstances.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allreferences.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-assignvalue.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-changevarvalue.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-collapseall.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-contentassist.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-copy.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-cut.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-detailpane.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-display.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-execute.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-find.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-findreplace.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-forcereturn.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-horizview.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspect.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspectvariable.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-maxlength.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-paste.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-preferences.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectall.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectcolumns.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showcolumns.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showconstants.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showlogical.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-shownull.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showqualified.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showreferences.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showstatic.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showtypenames.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-togglewp.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-vertview.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewdisplaycommands.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewlayoutcommands.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewonly.htm bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-wrap.htm bundles/org.eclipse.jdt.doc.user/reference/views/variables/images/ref-variables_view.PNG bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-createwatch.htm bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-variables_view.htm bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_breakpoints.htm bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_launch_configs.htm bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_breakpoints.htm bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_launch_configs.htm bundles/org.eclipse.jdt.doc.user/tasks/images/task-add-exception-breakpoint.PNG bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_ee_file.PNG bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_std_vm.PNG bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-add-monitor.gif bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-det-pane.gif bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-link-panes.gif bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-new.gif bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-pin.gif bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-remove-monitor.gif bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-199a.png bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-46.png bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-exception-filtering-add.PNG bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-excetpion-filtering-page.PNG bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_200a.png bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_201a.png bundles/org.eclipse.jdt.doc.user/tasks/task-add_line_breakpoints.htm bundles/org.eclipse.jdt.doc.user/tasks/task-add_new_jre.htm bundles/org.eclipse.jdt.doc.user/tasks/task-apply_hit_count.htm bundles/org.eclipse.jdt.doc.user/tasks/task-assign_default_jre.htm bundles/org.eclipse.jdt.doc.user/tasks/task-catching_exceptions.htm bundles/org.eclipse.jdt.doc.user/tasks/task-choose_config_jre.htm bundles/org.eclipse.jdt.doc.user/tasks/task-create_scrapbook_page.htm bundles/org.eclipse.jdt.doc.user/tasks/task-disconnect_remote_debug.htm bundles/org.eclipse.jdt.doc.user/tasks/task-display_evaluation_result.htm bundles/org.eclipse.jdt.doc.user/tasks/task-enable_disable_breakpoints.htm bundles/org.eclipse.jdt.doc.user/tasks/task-evaluating_expressions.htm bundles/org.eclipse.jdt.doc.user/tasks/task-executing_an_expression.htm bundles/org.eclipse.jdt.doc.user/tasks/task-inspect_evaluation_result.htm bundles/org.eclipse.jdt.doc.user/tasks/task-inspecting.htm bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_applet.htm bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_program.htm bundles/org.eclipse.jdt.doc.user/tasks/task-manage_conditional_breakpoint.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-add.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-change.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-inspect.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-monitors.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-add.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-views.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-preference.htm bundles/org.eclipse.jdt.doc.user/tasks/task-memory-remove.htm bundles/org.eclipse.jdt.doc.user/tasks/task-preparing_to_debug.htm bundles/org.eclipse.jdt.doc.user/tasks/task-relaunch_program.htm bundles/org.eclipse.jdt.doc.user/tasks/task-remotejava_launch_config.htm bundles/org.eclipse.jdt.doc.user/tasks/task-remove_line_breakpoints.htm bundles/org.eclipse.jdt.doc.user/tasks/task-resuming_threads.htm bundles/org.eclipse.jdt.doc.user/tasks/task-running_and_debugging.htm bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_content_assist.htm bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_error_reporting.htm bundles/org.eclipse.jdt.doc.user/tasks/task-set_method_breakpoints.htm bundles/org.eclipse.jdt.doc.user/tasks/task-stepping.htm bundles/org.eclipse.jdt.doc.user/tasks/task-suspending_threads.htm bundles/org.eclipse.jdt.doc.user/tasks/task-view_compilation_errors.htm bundles/org.eclipse.jdt.doc.user/tasks/task-view_runtime_exceptions.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-create-exception-filter-expression.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png bundles/org.eclipse.jdt.doc.user/tips/images/breadcrumb.png bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-1.png bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-2.png bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-3.png bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-5.png bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-6.png bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-7.png bundles/org.eclipse.jdt.doc.user/tips/images/cleanupprofiles.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym1.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym2.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import-result.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import.png bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png bundles/org.eclipse.jdt.doc.user/tips/images/colored-labels.png bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png bundles/org.eclipse.jdt.doc.user/tips/images/completiononcamelcase.png bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png bundles/org.eclipse.jdt.doc.user/tips/images/content-assist-proposals.png bundles/org.eclipse.jdt.doc.user/tips/images/content_assist_participant.png bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png bundles/org.eclipse.jdt.doc.user/tips/images/create-hashcode-equals.png bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png bundles/org.eclipse.jdt.doc.user/tips/images/gettersetter-quickassist.png bundles/org.eclipse.jdt.doc.user/tips/images/group-problems.png bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-always-false.png bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-compl-proposals.png bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-hover.png bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-view.png bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png bundles/org.eclipse.jdt.doc.user/tips/images/link-with-editor-in-occs.png bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png bundles/org.eclipse.jdt.doc.user/tips/images/new-project-with-ee.png bundles/org.eclipse.jdt.doc.user/tips/images/nls-problem-search.png bundles/org.eclipse.jdt.doc.user/tips/images/null-reference.png bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/activate-debug-view.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/dbg-bread-crumb.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/hyperlink_step.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/perspective-prompt.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/view-mngmt.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png bundles/org.eclipse.jdt.doc.user/tips/images/organize-imports-on-save.png bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png bundles/org.eclipse.jdt.doc.user/tips/images/potential-null-ref.png bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png bundles/org.eclipse.jdt.doc.user/tips/images/redundant-null-check.png bundles/org.eclipse.jdt.doc.user/tips/images/rich-problem-hover.png bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png bundles/org.eclipse.jdt.doc.user/tips/images/swt-templates.png bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png bundles/org.eclipse.jdt.doc.user/tips/images/type-indicator.png bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png bundles/org.eclipse.jdt.doc.user/tips/images/working-set-selection.png bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html bundles/org.eclipse.jdt.doc.user/toc.xml bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml bundles/org.eclipse.jdt.doc.user/topics_Reference.xml bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-dot-dot-path.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-duplicate-entries.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-invalid-dups.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/class-path-header.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/comparing-identical-values-example.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-deadcode-diagnosis.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-hashcode-diagnosis.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/compliance-follows-ee.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/constructor-completion.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/delete-working-set.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/dynamic-structure-compare.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/expand-with-constructors.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-after.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-before.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/generate-tostring-dialog.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/hashcode-and-equals-wizard.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/jar-export.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-assist.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hover.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hyperlinking.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-outline.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-header-links.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-hover.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/junit-view-import.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/missing-synchronized.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-implementation.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-junit-view.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-properties-file.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-in-workspace.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/runnable-jar-in-jar-export.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/sort-working-sets.png bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch-case-fall-through.png bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html bundles/org.eclipse.pde.doc.user/.classpath bundles/org.eclipse.pde.doc.user/.cvsignore bundles/org.eclipse.pde.doc.user/.project bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt bundles/org.eclipse.pde.doc.user/about.html bundles/org.eclipse.pde.doc.user/about.mappings bundles/org.eclipse.pde.doc.user/about.properties bundles/org.eclipse.pde.doc.user/apache_style.css bundles/org.eclipse.pde.doc.user/api_contexts.xml bundles/org.eclipse.pde.doc.user/book.css bundles/org.eclipse.pde.doc.user/build.properties bundles/org.eclipse.pde.doc.user/buildDoc.xml bundles/org.eclipse.pde.doc.user/concepts/extension.htm bundles/org.eclipse.pde.doc.user/concepts/feature.htm bundles/org.eclipse.pde.doc.user/concepts/fragment.htm bundles/org.eclipse.pde.doc.user/concepts/plugin.htm bundles/org.eclipse.pde.doc.user/concepts/product.htm bundles/org.eclipse.pde.doc.user/concepts/target.htm bundles/org.eclipse.pde.doc.user/concepts/update_site.htm bundles/org.eclipse.pde.doc.user/contexts_PDE.xml bundles/org.eclipse.pde.doc.user/customBuildCallbacks.xml bundles/org.eclipse.pde.doc.user/guide/book.css bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/compiler.png bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/content_assist.png bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/convert.PNG bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/discouraged.png bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/forbidden.png bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/friend.png bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/hidden.png bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/properties.png bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/visible.png bundles/org.eclipse.pde.doc.user/guide/images/category_editor/manage_categories.png bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/dialog_cheat-sheet-selection.png bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_content.png bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_enclosing-text.png bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_group.png bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_task.png bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_title.png bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_command.png bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_filled.png bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_second_topic.png bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_topic_details.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/cross_platform.PNG bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/destination.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/export_wizard_select.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/feature_available.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/jar_signing.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_features.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_plugins.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/plugin_available.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/product.png bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/webstart_features.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_properties.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_required.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_details.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_included.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_copyright.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_description.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_license.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_sites.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_environments.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_general.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins.png bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins_details.png bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/feature_import.png bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_categories.png bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_from_all.PNG bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import.png bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import_for_existing.PNG bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_arguments.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_common.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_configuration.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_environment.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_main.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_plugins.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_tracing.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_arguments.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_plugins.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_settings.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_configuration.PNG bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_headless.PNG bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_main.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_plugins.png bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_test.png bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer1.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer2.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/category_definition.png bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature1.png bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature2.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_explorer.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_patch.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment1.png bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment2.png bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment_explorer.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_toc_wizard.png bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_wizards_projects.png bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/other_category.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_content.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_customize.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_explorer.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_structure.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_templates.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/product.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/schema.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site_explorer.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/target.PNG bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/wizard_new_cheat-sheet.png bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/actions_select.png bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/convert_project.png bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_selection.png bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_substitution.png bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/organize_manifest.png bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/update_classpath.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/binary_source.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/classpath.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_analysis.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_automated.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_imported.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_required.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extension_points.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_body.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_details.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/filter_pages.PNG bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_execution.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_general.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_classpath.png bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_exported.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_features.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_plugin.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_schemas.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_manifest.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_xml.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/osgi_frameworks.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/outline.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/plugin_development.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_locations_group.png bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_preferences.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_about.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_welcome.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_window.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_features.PNG bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_file.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_plugins.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_arguments.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_jre.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_program.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_definition.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_exporting.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_testing.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_custom.png bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_location.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/editor_header.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_1.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_2.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_3.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_4.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_compositor-details.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_description.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_documentation.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_1.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_2.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-reference-details.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_1.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_2.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_general-information.png bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_schema-inclusions.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_1.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_2.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_3.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_master.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/page_cheat-sheet_header.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_command_details.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_id.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_link.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_none.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_details.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_master.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_view.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_1.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_2.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_1.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_2.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_1.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_2.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_details.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_master.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_view.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_details.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_master.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_view.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_category.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_cheat-sheet.png bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_selection.png bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_description.png bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_mirrors.png bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_environment.png bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_managing.png bundles/org.eclipse.pde.doc.user/guide/images/target_editor/content_page.png bundles/org.eclipse.pde.doc.user/guide/images/target_editor/definition_page.png bundles/org.eclipse.pde.doc.user/guide/images/target_editor/environment_page.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_arguments_tab.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_content_tab.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_environment_tab.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_implicit_tab.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_locations_tab.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_wizard.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/import_arguments_dialog.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_application.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_directory.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_features.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_site.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_preview.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_selection.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_site_include.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/move_target_wizard.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard_template.png bundles/org.eclipse.pde.doc.user/guide/images/target_shared/select_implicit.png bundles/org.eclipse.pde.doc.user/guide/images/tasks/api_filter_properties.png bundles/org.eclipse.pde.doc.user/guide/images/tasks/baseline_dialog.png bundles/org.eclipse.pde.doc.user/guide/images/tasks/feature-jar.png bundles/org.eclipse.pde.doc.user/guide/images/tasks/plugin_creation_wizard.png bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/anchor_details.png bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/book_details.png bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/link_details.png bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/toc_section.png bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/topic_details.png bundles/org.eclipse.pde.doc.user/guide/images/views/all_views.PNG bundles/org.eclipse.pde.doc.user/guide/images/views/error_log.png bundles/org.eclipse.pde.doc.user/guide/images/views/error_log_details.png bundles/org.eclipse.pde.doc.user/guide/images/views/perspective.PNG bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_1.png bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_flat_callees.png bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_hierarchical_callers.png bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_state_status.png bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_registry.png bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm bundles/org.eclipse.pde.doc.user/guide/schema.css bundles/org.eclipse.pde.doc.user/guide/tools/editors/category_editor/definition_page.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/page_cheat-sheet.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/ctx_help_editor/ctx_help_editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/dependencies.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/feature_editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/included_features.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/information.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/installation.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/overview.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/plugins.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/automated_management.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/build.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/dependencies.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extension_points.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extensions.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/runtime.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/testing.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/branding.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/configuration.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/dependencies.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/launching.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/licensing.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/splash.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_definition.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_overview.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/dialog_command-composer.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/page_cheat-sheet.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command-details.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_commands.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_content.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_help.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_introduction.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_step.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_sub-step.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_title.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/archives.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_map.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/content_page.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/definition_page.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/target_editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/editor.htm bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/page_toc.htm bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_features.htm bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_plugins.htm bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_wizards.htm bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_category.htm bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_cheat_sheet.htm bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_file_wizards.htm bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_product_config.htm bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_schema.htm bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_target_definition.htm bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_toc.htm bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_features.htm bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_plugins.htm bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_wizards.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/common.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/configuration.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_application_launcher.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_args.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_main.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_plugins.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/environment.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_args.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_launcher.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_plugins.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_settings.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_configuration.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_launcher.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_main.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_plugins.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_test.htm bundles/org.eclipse.pde.doc.user/guide/tools/launchers/tracing.htm bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/convert_projects.htm bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/externalize_strings.htm bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/organize_manifests.htm bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/task_wizards.htm bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/update_classpaths.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/compilers.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/feature_compiler.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/osgi_frameworks.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plug_in_development.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plugin_compiler.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/preferences.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/schema_compiler.htm bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_content.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_structure.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_patch.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_project.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_fragment_project.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_plugin_project.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_project_wizards.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_update_site_project.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_content.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_from_archives.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_structure.htm bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_templates.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_arguments_tab.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_content_tab.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_environment_tab.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_implicit_tab.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_locations_tab.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/implicit_plugin_selection_dialog.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/import_arguments_dialog.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_features_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_directory_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_feature_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_installation_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_site_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_preview.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/move_target_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/new_target_wizard.htm bundles/org.eclipse.pde.doc.user/guide/tools/views/error_log.htm bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_dependencies.htm bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_registry.htm bundles/org.eclipse.pde.doc.user/guide/tools/views/plugins.htm bundles/org.eclipse.pde.doc.user/guide/tools/views/target_platform_state.htm bundles/org.eclipse.pde.doc.user/guide/tools/views/views.htm bundles/org.eclipse.pde.doc.user/guide/tweak.css bundles/org.eclipse.pde.doc.user/images/ngrelc.png bundles/org.eclipse.pde.doc.user/images/ngrelr.png bundles/org.eclipse.pde.doc.user/images/ngrelt.png bundles/org.eclipse.pde.doc.user/notices.html bundles/org.eclipse.pde.doc.user/pdeOptions.txt bundles/org.eclipse.pde.doc.user/plugin.properties bundles/org.eclipse.pde.doc.user/plugin.xml bundles/org.eclipse.pde.doc.user/reference/actions/ref-pdetools.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-apitooling-setup-action.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-compare-action.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-ant-task.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-reportconversion-ant-task.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-ant-task.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-reportconversion-ant-task.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-ant-task.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-reportconversion-ant-task.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/filegeneration-ant-task.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_javadoc_tags.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_since_tags.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-compare-wizard.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-problem-filter-prop.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard-preview.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_analysis.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_compatibility.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_usage.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_version.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_tooling.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-pref-page.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf-dialog.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/error_ovr.gif bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/errorwarning-prop-page.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-dialog-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/ok.gif bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-dialog-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-editor-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-dialog-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-editor-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/success_ovr.gif bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-dialog-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-editor-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-qf.png bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-baselines.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-errorswarnings.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-errorswarnings-prop.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-filters-prop.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-missing-baseline-qf.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-remove-api-filter-qf.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-sincetag-qf.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-version-qf.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/views/ref-api-tooling-view.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-baseline-wizard.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-compare-wizard.htm bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-setup-wizard.htm bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html bundles/org.eclipse.pde.doc.user/reference/images/pde-tools-flyout.PNG bundles/org.eclipse.pde.doc.user/reference/misc/index.html bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html bundles/org.eclipse.pde.doc.user/reference/pde_builder_config.htm bundles/org.eclipse.pde.doc.user/reference/pde_feature_generating_build.htm bundles/org.eclipse.pde.doc.user/schema.css bundles/org.eclipse.pde.doc.user/tasks/api_tooling_baseline.htm bundles/org.eclipse.pde.doc.user/tasks/api_tooling_compare_to_baseline.htm bundles/org.eclipse.pde.doc.user/tasks/api_tooling_create_filters.htm bundles/org.eclipse.pde.doc.user/tasks/api_tooling_options.htm bundles/org.eclipse.pde.doc.user/tasks/api_tooling_remove_filters.htm bundles/org.eclipse.pde.doc.user/tasks/api_tooling_setup.htm bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_env.htm bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_order.htm bundles/org.eclipse.pde.doc.user/tasks/pde_controlling_output.htm bundles/org.eclipse.pde.doc.user/tasks/pde_custom_callbacks.htm bundles/org.eclipse.pde.doc.user/tasks/pde_customization.htm bundles/org.eclipse.pde.doc.user/tasks/pde_feature_build.htm bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_ant.htm bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm bundles/org.eclipse.pde.doc.user/tasks/pde_fetch_phase.htm bundles/org.eclipse.pde.doc.user/tasks/pde_individual_source.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_builds.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_buildtasks.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featurebuilds.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featuremetadata.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_integration.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_productbuilds.htm bundles/org.eclipse.pde.doc.user/tasks/pde_p2_reusingmetadata.htm bundles/org.eclipse.pde.doc.user/tasks/pde_packager.htm bundles/org.eclipse.pde.doc.user/tasks/pde_plugins_build.htm bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm bundles/org.eclipse.pde.doc.user/tasks/pde_rootfiles.htm bundles/org.eclipse.pde.doc.user/tasks/pde_source_generation.htm bundles/org.eclipse.pde.doc.user/tasks/pde_version_qualifiers.htm bundles/org.eclipse.pde.doc.user/tasks/ui_export_install_into_host.htm bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm bundles/org.eclipse.pde.doc.user/toc.xml bundles/org.eclipse.pde.doc.user/topics_Reference.xml bundles/org.eclipse.pde.doc.user/topics_Tasks.xml bundles/org.eclipse.pde.doc.user/whatsNew/default_style.css bundles/org.eclipse.pde.doc.user/whatsNew/images/apichanges.png bundles/org.eclipse.pde.doc.user/whatsNew/images/categorydef.png bundles/org.eclipse.pde.doc.user/whatsNew/images/categoryexport.png bundles/org.eclipse.pde.doc.user/whatsNew/images/click-install.png bundles/org.eclipse.pde.doc.user/whatsNew/images/dstemplate.png bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation-pref.png bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation.png bundles/org.eclipse.pde.doc.user/whatsNew/images/err-warn.png bundles/org.eclipse.pde.doc.user/whatsNew/images/export-options.png bundles/org.eclipse.pde.doc.user/whatsNew/images/filter-quick-fix.png bundles/org.eclipse.pde.doc.user/whatsNew/images/installcategory.png bundles/org.eclipse.pde.doc.user/whatsNew/images/installed.png bundles/org.eclipse.pde.doc.user/whatsNew/images/keypass.png bundles/org.eclipse.pde.doc.user/whatsNew/images/menuspy.png bundles/org.eclipse.pde.doc.user/whatsNew/images/nl-fragments.png bundles/org.eclipse.pde.doc.user/whatsNew/images/non-ui-thread.png bundles/org.eclipse.pde.doc.user/whatsNew/images/options-editor.png bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-binarycycles.png bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-ds.png bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-jumpconsole.png bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-registryview.png bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-versioning.png bundles/org.eclipse.pde.doc.user/whatsNew/images/registryfragments.png bundles/org.eclipse.pde.doc.user/whatsNew/images/start-levels.png bundles/org.eclipse.pde.doc.user/whatsNew/images/target-editor.png bundles/org.eclipse.pde.doc.user/whatsNew/images/target-platform.png bundles/org.eclipse.pde.doc.user/whatsNew/images/targetstateview.png bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm bundles/org.eclipse.platform.doc.isv/.cvsignore bundles/org.eclipse.platform.doc.isv/.project bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt bundles/org.eclipse.platform.doc.isv/about.html bundles/org.eclipse.platform.doc.isv/book.css bundles/org.eclipse.platform.doc.isv/build.properties bundles/org.eclipse.platform.doc.isv/buildDoc.xml bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml bundles/org.eclipse.platform.doc.isv/guide/ant.htm bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm bundles/org.eclipse.platform.doc.isv/guide/arch.htm bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm bundles/org.eclipse.platform.doc.isv/guide/bundle_security.html bundles/org.eclipse.platform.doc.isv/guide/cnf.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_config.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_operation.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_rcp.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_steps.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_content.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_general.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_rn_migration.htm bundles/org.eclipse.platform.doc.isv/guide/cnf_troubleshooting.htm bundles/org.eclipse.platform.doc.isv/guide/compare.htm bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm bundles/org.eclipse.platform.doc.isv/guide/debug.htm bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example_advanced.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm bundles/org.eclipse.platform.doc.isv/guide/editors.htm bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm bundles/org.eclipse.platform.doc.isv/guide/forms.htm bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm bundles/org.eclipse.platform.doc.isv/guide/images/about.png bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png bundles/org.eclipse.platform.doc.isv/guide/images/contributions_global.png bundles/org.eclipse.platform.doc.isv/guide/images/contributions_popup.png bundles/org.eclipse.platform.doc.isv/guide/images/contributions_view_dropdown.png bundles/org.eclipse.platform.doc.isv/guide/images/contributions_window.png bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png bundles/org.eclipse.platform.doc.isv/guide/images/efs-newProject.png bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_data.png bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_prov.png bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExample.png bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance1.png bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance2.png bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance3.png bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png bundles/org.eclipse.platform.doc.isv/guide/images/no_category.png bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_filters.png bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_groupByType.png bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_markerTypeCat.png bundles/org.eclipse.platform.doc.isv/guide/images/problemsview_groups.png bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png bundles/org.eclipse.platform.doc.isv/guide/images/quickfix.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png bundles/org.eclipse.platform.doc.isv/guide/images/readmetrim.png bundles/org.eclipse.platform.doc.isv/guide/images/readmetrimxml.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewcommand.png bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png bundles/org.eclipse.platform.doc.isv/guide/images/sample.gif bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg bundles/org.eclipse.platform.doc.isv/guide/images/showview.png bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png bundles/org.eclipse.platform.doc.isv/guide/int.htm bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm bundles/org.eclipse.platform.doc.isv/guide/int_who.htm bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm bundles/org.eclipse.platform.doc.isv/guide/jface.htm bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm bundles/org.eclipse.platform.doc.isv/guide/login_extensions.html bundles/org.eclipse.platform.doc.isv/guide/network.htm bundles/org.eclipse.platform.doc.isv/guide/p2_category_generation.htm bundles/org.eclipse.platform.doc.isv/guide/p2_composite_repositories.htm bundles/org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html bundles/org.eclipse.platform.doc.isv/guide/p2_director.html bundles/org.eclipse.platform.doc.isv/guide/p2_metadata.html bundles/org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html bundles/org.eclipse.platform.doc.isv/guide/p2_mirror.html bundles/org.eclipse.platform.doc.isv/guide/p2_overview.htm bundles/org.eclipse.platform.doc.isv/guide/p2_publisher.html bundles/org.eclipse.platform.doc.isv/guide/p2_publishingtasks.htm bundles/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm bundles/org.eclipse.platform.doc.isv/guide/product.htm bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm bundles/org.eclipse.platform.doc.isv/guide/product_def.htm bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm bundles/org.eclipse.platform.doc.isv/guide/product_update.htm bundles/org.eclipse.platform.doc.isv/guide/rcp.htm bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_api.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_intro.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_providers.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_resources.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm bundles/org.eclipse.platform.doc.isv/guide/resInt.htm bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm bundles/org.eclipse.platform.doc.isv/guide/runtime.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_app_model.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_components.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm bundles/org.eclipse.platform.doc.isv/guide/search.htm bundles/org.eclipse.platform.doc.isv/guide/search_page.htm bundles/org.eclipse.platform.doc.isv/guide/search_result.htm bundles/org.eclipse.platform.doc.isv/guide/secure_storage.htm bundles/org.eclipse.platform.doc.isv/guide/secure_storage_architecture.htm bundles/org.eclipse.platform.doc.isv/guide/secure_storage_dev.htm bundles/org.eclipse.platform.doc.isv/guide/secure_storage_providers.htm bundles/org.eclipse.platform.doc.isv/guide/swt.htm bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm bundles/org.eclipse.platform.doc.isv/guide/team.htm bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm bundles/org.eclipse.platform.doc.isv/guide/team_model.htm bundles/org.eclipse.platform.doc.isv/guide/team_model_model.htm bundles/org.eclipse.platform.doc.isv/guide/team_model_repo.htm bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm bundles/org.eclipse.platform.doc.isv/guide/team_ui_history.htm bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm bundles/org.eclipse.platform.doc.isv/guide/ua.htm bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_child_links.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_process.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_remote.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_menu.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_help_data.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm bundles/org.eclipse.platform.doc.isv/guide/workbench.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_expressions.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_services.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo_ide.htm bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm bundles/org.eclipse.platform.doc.isv/notices.html bundles/org.eclipse.platform.doc.isv/platformOptions.txt bundles/org.eclipse.platform.doc.isv/plugin.properties bundles/org.eclipse.platform.doc.isv/plugin.xml bundles/org.eclipse.platform.doc.isv/porting/3.3/faq.html bundles/org.eclipse.platform.doc.isv/porting/3.3/incompatibilities.html bundles/org.eclipse.platform.doc.isv/porting/3.3/recommended.html bundles/org.eclipse.platform.doc.isv/porting/3.4/faq.html bundles/org.eclipse.platform.doc.isv/porting/3.4/incompatibilities.html bundles/org.eclipse.platform.doc.isv/porting/3.4/recommended.html bundles/org.eclipse.platform.doc.isv/porting/3.5/faq.html bundles/org.eclipse.platform.doc.isv/porting/3.5/incompatibilities.html bundles/org.eclipse.platform.doc.isv/porting/3.5/recommended.html bundles/org.eclipse.platform.doc.isv/porting/3.6/faq.html bundles/org.eclipse.platform.doc.isv/porting/3.6/incompatibilities.html bundles/org.eclipse.platform.doc.isv/porting/3.6/recommended.html bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_3_porting_guide.html bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_4_porting_guide.html bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_5_porting_guide.html bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_6_porting_guide.html bundles/org.eclipse.platform.doc.isv/questions/index.html bundles/org.eclipse.platform.doc.isv/reference/.cvsignore bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html bundles/org.eclipse.platform.doc.isv/reference/misc/gcj.html bundles/org.eclipse.platform.doc.isv/reference/misc/index.html bundles/org.eclipse.platform.doc.isv/reference/misc/launcher.html bundles/org.eclipse.platform.doc.isv/reference/misc/launcher_ini.html bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html bundles/org.eclipse.platform.doc.isv/reference/misc/p2_dropins_format.html bundles/org.eclipse.platform.doc.isv/reference/misc/platform-scheme-uri.html bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd_30.html bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest_30.html bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html bundles/org.eclipse.platform.doc.isv/samples/samples.html bundles/org.eclipse.platform.doc.isv/schema.css bundles/org.eclipse.platform.doc.isv/toc.xml bundles/org.eclipse.platform.doc.isv/topics_Guide.xml bundles/org.eclipse.platform.doc.isv/topics_Porting.xml bundles/org.eclipse.platform.doc.isv/topics_Questions.xml bundles/org.eclipse.platform.doc.isv/topics_Reference.xml bundles/org.eclipse.platform.doc.isv/topics_Samples.xml bundles/org.eclipse.platform.doc.isv/whatsNew/images/blockselection.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/button-order.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/cairoaix.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/datetime-dropdown.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/dnd.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/editor.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/filtered-tree.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/injection_graph_func.js bundles/org.eclipse.platform.doc.isv/whatsNew/images/jnigen.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/link.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/margins.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/modified.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/multi-font-labels.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/nautiluscopy.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/printdialog.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/search.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet-prompt.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/showwelcome.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-intro.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-overview.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/solarisx86-browser.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout1.png bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout2.png bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html bundles/org.eclipse.platform.doc.isv/workbench.png bundles/org.eclipse.platform.doc.user/.project bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF bundles/org.eclipse.platform.doc.user/about.html bundles/org.eclipse.platform.doc.user/book.css bundles/org.eclipse.platform.doc.user/build.properties bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm bundles/org.eclipse.platform.doc.user/concepts/accessibility/text_editor.htm bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm bundles/org.eclipse.platform.doc.user/concepts/cnav.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-21a.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-antexttools.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm bundles/org.eclipse.platform.doc.user/concepts/coutline.htm bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm bundles/org.eclipse.platform.doc.user/concepts/help.htm bundles/org.eclipse.platform.doc.user/concepts/help_view.htm bundles/org.eclipse.platform.doc.user/concepts/welcome.htm bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml bundles/org.eclipse.platform.doc.user/contexts_CommonNavigator.xml bundles/org.eclipse.platform.doc.user/contexts_Compare.xml bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml bundles/org.eclipse.platform.doc.user/contexts_JSch.xml bundles/org.eclipse.platform.doc.user/contexts_Net.xml bundles/org.eclipse.platform.doc.user/contexts_P2.xml bundles/org.eclipse.platform.doc.user/contexts_Search.xml bundles/org.eclipse.platform.doc.user/contexts_SecureStorage.xml bundles/org.eclipse.platform.doc.user/contexts_Team.xml bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml bundles/org.eclipse.platform.doc.user/contexts_Update.xml bundles/org.eclipse.platform.doc.user/contexts_UserAssistance.xml bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_workingWithHistory.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm bundles/org.eclipse.platform.doc.user/gettingStarted/team-cvs.css bundles/org.eclipse.platform.doc.user/images/EAMaxed.png bundles/org.eclipse.platform.doc.user/images/EANormal.png bundles/org.eclipse.platform.doc.user/images/EATrim.png bundles/org.eclipse.platform.doc.user/images/Image1.png bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv2.png bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png bundles/org.eclipse.platform.doc.user/images/Image275_project_explorer.png bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png bundles/org.eclipse.platform.doc.user/images/Image276_available_content.png bundles/org.eclipse.platform.doc.user/images/Image276_available_filters.png bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png bundles/org.eclipse.platform.doc.user/images/Image37drop.png bundles/org.eclipse.platform.doc.user/images/Image38_import.png bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png bundles/org.eclipse.platform.doc.user/images/Image3_single.png bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png bundles/org.eclipse.platform.doc.user/images/Image42_export.png bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png bundles/org.eclipse.platform.doc.user/images/Image45_setup.png bundles/org.eclipse.platform.doc.user/images/Image48_move.png bundles/org.eclipse.platform.doc.user/images/Image48_rename.png bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png bundles/org.eclipse.platform.doc.user/images/Image4_showview.png bundles/org.eclipse.platform.doc.user/images/Image50_search.png bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png bundles/org.eclipse.platform.doc.user/images/Image51_search_pinview.png bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png bundles/org.eclipse.platform.doc.user/images/Image55_reset.png bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png bundles/org.eclipse.platform.doc.user/images/Image610_et_targets_tab.png bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png bundles/org.eclipse.platform.doc.user/images/Image619_ole.png bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png bundles/org.eclipse.platform.doc.user/images/Image71_arrow.png bundles/org.eclipse.platform.doc.user/images/Image71_dialog_menu.png bundles/org.eclipse.platform.doc.user/images/Image71_dialog_toolbar.png bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_after.png bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_before.png bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_after.png bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_before.png bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png bundles/org.eclipse.platform.doc.user/images/Image80_compare.png bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png bundles/org.eclipse.platform.doc.user/images/Image82_nav.png bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png bundles/org.eclipse.platform.doc.user/images/Image84_decorator_pref.png bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png bundles/org.eclipse.platform.doc.user/images/Image84_replace3.png bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png bundles/org.eclipse.platform.doc.user/images/Image8_view.png bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png bundles/org.eclipse.platform.doc.user/images/TrimStack.png bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png bundles/org.eclipse.platform.doc.user/images/addtask.png bundles/org.eclipse.platform.doc.user/images/alpha_mode.png bundles/org.eclipse.platform.doc.user/images/ancestorpane_co.gif bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png bundles/org.eclipse.platform.doc.user/images/ant_formatter.png bundles/org.eclipse.platform.doc.user/images/ant_prefs.png bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png bundles/org.eclipse.platform.doc.user/images/ant_templates.png bundles/org.eclipse.platform.doc.user/images/ant_view.png bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg bundles/org.eclipse.platform.doc.user/images/backward_nav.png bundles/org.eclipse.platform.doc.user/images/block_selection_mode.gif bundles/org.eclipse.platform.doc.user/images/build_exec.png bundles/org.eclipse.platform.doc.user/images/cap-conf.png bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png bundles/org.eclipse.platform.doc.user/images/cap-pref.png bundles/org.eclipse.platform.doc.user/images/change-obj.gif bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png bundles/org.eclipse.platform.doc.user/images/close_view.png bundles/org.eclipse.platform.doc.user/images/compare-editor-diff-change.png bundles/org.eclipse.platform.doc.user/images/compare-editor.png bundles/org.eclipse.platform.doc.user/images/confadd_ov.png bundles/org.eclipse.platform.doc.user/images/confchg_ov.png bundles/org.eclipse.platform.doc.user/images/confdel_ov.png bundles/org.eclipse.platform.doc.user/images/content_type.png bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png bundles/org.eclipse.platform.doc.user/images/copy_edit.png bundles/org.eclipse.platform.doc.user/images/copy_l_co.gif bundles/org.eclipse.platform.doc.user/images/copy_r_co.gif bundles/org.eclipse.platform.doc.user/images/copycont_l_co.gif bundles/org.eclipse.platform.doc.user/images/copycont_r_co.gif bundles/org.eclipse.platform.doc.user/images/cut_edit.png bundles/org.eclipse.platform.doc.user/images/cvs-annotate.png bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates.png bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates2.png bundles/org.eclipse.platform.doc.user/images/cvs-connection.png bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png bundles/org.eclipse.platform.doc.user/images/cvs-console.png bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png bundles/org.eclipse.platform.doc.user/images/cvs-ext.png bundles/org.eclipse.platform.doc.user/images/cvs-files.png bundles/org.eclipse.platform.doc.user/images/cvs-general.png bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png bundles/org.eclipse.platform.doc.user/images/cvs-password.png bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png bundles/org.eclipse.platform.doc.user/images/cvs-share1.png bundles/org.eclipse.platform.doc.user/images/cvs-share2.png bundles/org.eclipse.platform.doc.user/images/cvs-share3.png bundles/org.eclipse.platform.doc.user/images/cvs-share4.png bundles/org.eclipse.platform.doc.user/images/cvs-specify-repository.png bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png bundles/org.eclipse.platform.doc.user/images/cvs-updatemerge.png bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png bundles/org.eclipse.platform.doc.user/images/cvs_change_ascii_binary_prop.png bundles/org.eclipse.platform.doc.user/images/cvs_configure_branches_and_versions.png bundles/org.eclipse.platform.doc.user/images/cvs_filter_res_history.png bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png bundles/org.eclipse.platform.doc.user/images/cvs_new_branch.png bundles/org.eclipse.platform.doc.user/images/cvs_refresh_branches.png bundles/org.eclipse.platform.doc.user/images/debug_exec.png bundles/org.eclipse.platform.doc.user/images/defaults_ps.png bundles/org.eclipse.platform.doc.user/images/delete_edit.png bundles/org.eclipse.platform.doc.user/images/detachview2.png bundles/org.eclipse.platform.doc.user/images/dirty_ov.png bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png bundles/org.eclipse.platform.doc.user/images/drop_left_source.png bundles/org.eclipse.platform.doc.user/images/drop_offscreen_source.png bundles/org.eclipse.platform.doc.user/images/drop_right_source.png bundles/org.eclipse.platform.doc.user/images/drop_stack.png bundles/org.eclipse.platform.doc.user/images/drop_top_source.png bundles/org.eclipse.platform.doc.user/images/edited_ov.png bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_pswd.png bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_start.png bundles/org.eclipse.platform.doc.user/images/et_dialog.png bundles/org.eclipse.platform.doc.user/images/et_dropdown.png bundles/org.eclipse.platform.doc.user/images/export_wiz.png bundles/org.eclipse.platform.doc.user/images/external_tools.png bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png bundles/org.eclipse.platform.doc.user/images/fast_view_menu.png bundles/org.eclipse.platform.doc.user/images/filter_ps.png bundles/org.eclipse.platform.doc.user/images/first_anteditor.png bundles/org.eclipse.platform.doc.user/images/forward_nav.png bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png bundles/org.eclipse.platform.doc.user/images/help_icon.png bundles/org.eclipse.platform.doc.user/images/help_icon_back.png bundles/org.eclipse.platform.doc.user/images/help_icon_book_closed.png bundles/org.eclipse.platform.doc.user/images/help_icon_book_open.png bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark.png bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark_add.png bundles/org.eclipse.platform.doc.user/images/help_icon_capabilities.png bundles/org.eclipse.platform.doc.user/images/help_icon_external.png bundles/org.eclipse.platform.doc.user/images/help_icon_forward.png bundles/org.eclipse.platform.doc.user/images/help_icon_highlight.png bundles/org.eclipse.platform.doc.user/images/help_icon_home.png bundles/org.eclipse.platform.doc.user/images/help_icon_maximize.png bundles/org.eclipse.platform.doc.user/images/help_icon_print.png bundles/org.eclipse.platform.doc.user/images/help_icon_restore.png bundles/org.eclipse.platform.doc.user/images/help_icon_search_infocenter.png bundles/org.eclipse.platform.doc.user/images/help_icon_search_local.png bundles/org.eclipse.platform.doc.user/images/help_icon_search_web.png bundles/org.eclipse.platform.doc.user/images/help_icon_sync.png bundles/org.eclipse.platform.doc.user/images/help_icon_toc.png bundles/org.eclipse.platform.doc.user/images/help_icon_topic.png bundles/org.eclipse.platform.doc.user/images/help_icon_topic_container.png bundles/org.eclipse.platform.doc.user/images/help_infopop.png bundles/org.eclipse.platform.doc.user/images/help_preference.png bundles/org.eclipse.platform.doc.user/images/help_preference_content.png bundles/org.eclipse.platform.doc.user/images/help_preference_infocenter.png bundles/org.eclipse.platform.doc.user/images/help_preference_server.png bundles/org.eclipse.platform.doc.user/images/help_view_bookmarks.png bundles/org.eclipse.platform.doc.user/images/help_view_context.png bundles/org.eclipse.platform.doc.user/images/help_view_index.png bundles/org.eclipse.platform.doc.user/images/help_view_search.png bundles/org.eclipse.platform.doc.user/images/help_view_toc.png bundles/org.eclipse.platform.doc.user/images/help_window.png bundles/org.eclipse.platform.doc.user/images/help_window_external.png bundles/org.eclipse.platform.doc.user/images/image92-begin.png bundles/org.eclipse.platform.doc.user/images/image92-check.png bundles/org.eclipse.platform.doc.user/images/image92-close.png bundles/org.eclipse.platform.doc.user/images/image92-collapse.png bundles/org.eclipse.platform.doc.user/images/image92-complete.png bundles/org.eclipse.platform.doc.user/images/image92-expand.png bundles/org.eclipse.platform.doc.user/images/image92-help.png bundles/org.eclipse.platform.doc.user/images/image92-hide.png bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png bundles/org.eclipse.platform.doc.user/images/image92-perform.png bundles/org.eclipse.platform.doc.user/images/image92-redo.png bundles/org.eclipse.platform.doc.user/images/image92-restart.png bundles/org.eclipse.platform.doc.user/images/image92-save.png bundles/org.eclipse.platform.doc.user/images/image92-select.png bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png bundles/org.eclipse.platform.doc.user/images/image92-skip.png bundles/org.eclipse.platform.doc.user/images/import_wiz.png bundles/org.eclipse.platform.doc.user/images/keys1.png bundles/org.eclipse.platform.doc.user/images/keys2.png bundles/org.eclipse.platform.doc.user/images/keys3.png bundles/org.eclipse.platform.doc.user/images/keys4.png bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png bundles/org.eclipse.platform.doc.user/images/localHistoryCompare.png bundles/org.eclipse.platform.doc.user/images/localHistoryView.png bundles/org.eclipse.platform.doc.user/images/local_history_mode.png bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png bundles/org.eclipse.platform.doc.user/images/max.png bundles/org.eclipse.platform.doc.user/images/merged_ov.png bundles/org.eclipse.platform.doc.user/images/minmaxOptions.png bundles/org.eclipse.platform.doc.user/images/net-general.png bundles/org.eclipse.platform.doc.user/images/new_persp.png bundles/org.eclipse.platform.doc.user/images/new_wiz.png bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png bundles/org.eclipse.platform.doc.user/images/next_change_nav.gif bundles/org.eclipse.platform.doc.user/images/next_diff_nav.gif bundles/org.eclipse.platform.doc.user/images/next_nav.png bundles/org.eclipse.platform.doc.user/images/ngrelc.png bundles/org.eclipse.platform.doc.user/images/ngrelr.png bundles/org.eclipse.platform.doc.user/images/ngrelt.png bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png bundles/org.eclipse.platform.doc.user/images/open_persp.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/filter_internal_targets.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png bundles/org.eclipse.platform.doc.user/images/outline_hello.png bundles/org.eclipse.platform.doc.user/images/paste_edit.png bundles/org.eclipse.platform.doc.user/images/pin_editor.png bundles/org.eclipse.platform.doc.user/images/prb_quickfix.png bundles/org.eclipse.platform.doc.user/images/prbfil.png bundles/org.eclipse.platform.doc.user/images/prev_change_nav.gif bundles/org.eclipse.platform.doc.user/images/prev_diff_nav.gif bundles/org.eclipse.platform.doc.user/images/prev_nav.png bundles/org.eclipse.platform.doc.user/images/print_edit.png bundles/org.eclipse.platform.doc.user/images/prob.png bundles/org.eclipse.platform.doc.user/images/question_ov.png bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png bundles/org.eclipse.platform.doc.user/images/redo_edit.png bundles/org.eclipse.platform.doc.user/images/ref-1.png bundles/org.eclipse.platform.doc.user/images/ref-10.png bundles/org.eclipse.platform.doc.user/images/ref-11.png bundles/org.eclipse.platform.doc.user/images/ref-12.png bundles/org.eclipse.platform.doc.user/images/ref-15.png bundles/org.eclipse.platform.doc.user/images/ref-16.png bundles/org.eclipse.platform.doc.user/images/ref-17.png bundles/org.eclipse.platform.doc.user/images/ref-18.png bundles/org.eclipse.platform.doc.user/images/ref-2.png bundles/org.eclipse.platform.doc.user/images/ref-20.png bundles/org.eclipse.platform.doc.user/images/ref-21.png bundles/org.eclipse.platform.doc.user/images/ref-22.png bundles/org.eclipse.platform.doc.user/images/ref-23.png bundles/org.eclipse.platform.doc.user/images/ref-24.png bundles/org.eclipse.platform.doc.user/images/ref-25.png bundles/org.eclipse.platform.doc.user/images/ref-3.png bundles/org.eclipse.platform.doc.user/images/ref-4.png bundles/org.eclipse.platform.doc.user/images/ref-5.png bundles/org.eclipse.platform.doc.user/images/ref-52.png bundles/org.eclipse.platform.doc.user/images/ref-7.png bundles/org.eclipse.platform.doc.user/images/ref-79.png bundles/org.eclipse.platform.doc.user/images/ref-8.png bundles/org.eclipse.platform.doc.user/images/ref-9.png bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png bundles/org.eclipse.platform.doc.user/images/ref-p2-autoupdate.png bundles/org.eclipse.platform.doc.user/images/ref-p2-installupdate.png bundles/org.eclipse.platform.doc.user/images/ref-p2-siteprefs.png bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png bundles/org.eclipse.platform.doc.user/images/ref-templates-view.png bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png bundles/org.eclipse.platform.doc.user/images/refresh_nav.png bundles/org.eclipse.platform.doc.user/images/remote_history_mode.png bundles/org.eclipse.platform.doc.user/images/res.png bundles/org.eclipse.platform.doc.user/images/res_blocked.png bundles/org.eclipse.platform.doc.user/images/res_build.png bundles/org.eclipse.platform.doc.user/images/res_details.png bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png bundles/org.eclipse.platform.doc.user/images/res_pref.png bundles/org.eclipse.platform.doc.user/images/run_exec.png bundles/org.eclipse.platform.doc.user/images/save_edit.png bundles/org.eclipse.platform.doc.user/images/saveall_edit.png bundles/org.eclipse.platform.doc.user/images/saveas_edit.png bundles/org.eclipse.platform.doc.user/images/search_src.png bundles/org.eclipse.platform.doc.user/images/searchm_obj.png bundles/org.eclipse.platform.doc.user/images/segment_edit.png bundles/org.eclipse.platform.doc.user/images/show_whitespace_chars.gif bundles/org.eclipse.platform.doc.user/images/showcat_co.png bundles/org.eclipse.platform.doc.user/images/showdesc_co.png bundles/org.eclipse.platform.doc.user/images/ssh2-general.png bundles/org.eclipse.platform.doc.user/images/ssh2-hosts.png bundles/org.eclipse.platform.doc.user/images/ssh2-keys.png bundles/org.eclipse.platform.doc.user/images/stop_nav.png bundles/org.eclipse.platform.doc.user/images/switch_workspace.png bundles/org.eclipse.platform.doc.user/images/synced.png bundles/org.eclipse.platform.doc.user/images/synch_participants.png bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png bundles/org.eclipse.platform.doc.user/images/team-file-content.png bundles/org.eclipse.platform.doc.user/images/team-models.png bundles/org.eclipse.platform.doc.user/images/tree_mode.png bundles/org.eclipse.platform.doc.user/images/twowaycompare_co.gif bundles/org.eclipse.platform.doc.user/images/undo_edit.png bundles/org.eclipse.platform.doc.user/images/up_nav.png bundles/org.eclipse.platform.doc.user/images/version_controlled.png bundles/org.eclipse.platform.doc.user/images/view_menu.png bundles/org.eclipse.platform.doc.user/images/welcome.png bundles/org.eclipse.platform.doc.user/images/welcome_preference.png bundles/org.eclipse.platform.doc.user/images/win_only.png bundles/org.eclipse.platform.doc.user/notices.html bundles/org.eclipse.platform.doc.user/plugin.properties bundles/org.eclipse.platform.doc.user/plugin.xml bundles/org.eclipse.platform.doc.user/reference/help_preferences.htm bundles/org.eclipse.platform.doc.user/reference/help_preferences_content.htm bundles/org.eclipse.platform.doc.user/reference/ref-10.htm bundles/org.eclipse.platform.doc.user/reference/ref-11.htm bundles/org.eclipse.platform.doc.user/reference/ref-12.htm bundles/org.eclipse.platform.doc.user/reference/ref-13.htm bundles/org.eclipse.platform.doc.user/reference/ref-14.htm bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm bundles/org.eclipse.platform.doc.user/reference/ref-15.htm bundles/org.eclipse.platform.doc.user/reference/ref-16.htm bundles/org.eclipse.platform.doc.user/reference/ref-17.htm bundles/org.eclipse.platform.doc.user/reference/ref-19.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-annotate.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-commenttemplates.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-updatemerge.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm bundles/org.eclipse.platform.doc.user/reference/ref-2.htm bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm bundles/org.eclipse.platform.doc.user/reference/ref-20.htm bundles/org.eclipse.platform.doc.user/reference/ref-20team-models.htm bundles/org.eclipse.platform.doc.user/reference/ref-21.htm bundles/org.eclipse.platform.doc.user/reference/ref-22.htm bundles/org.eclipse.platform.doc.user/reference/ref-23.htm bundles/org.eclipse.platform.doc.user/reference/ref-24.htm bundles/org.eclipse.platform.doc.user/reference/ref-25.htm bundles/org.eclipse.platform.doc.user/reference/ref-26.htm bundles/org.eclipse.platform.doc.user/reference/ref-27.htm bundles/org.eclipse.platform.doc.user/reference/ref-28.htm bundles/org.eclipse.platform.doc.user/reference/ref-29.htm bundles/org.eclipse.platform.doc.user/reference/ref-3.htm bundles/org.eclipse.platform.doc.user/reference/ref-30.htm bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm bundles/org.eclipse.platform.doc.user/reference/ref-31.htm bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm bundles/org.eclipse.platform.doc.user/reference/ref-32.htm bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm bundles/org.eclipse.platform.doc.user/reference/ref-33.htm bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm bundles/org.eclipse.platform.doc.user/reference/ref-35.htm bundles/org.eclipse.platform.doc.user/reference/ref-36.htm bundles/org.eclipse.platform.doc.user/reference/ref-37.htm bundles/org.eclipse.platform.doc.user/reference/ref-38.htm bundles/org.eclipse.platform.doc.user/reference/ref-39.htm bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm bundles/org.eclipse.platform.doc.user/reference/ref-4.htm bundles/org.eclipse.platform.doc.user/reference/ref-40.htm bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm bundles/org.eclipse.platform.doc.user/reference/ref-42.htm bundles/org.eclipse.platform.doc.user/reference/ref-43.htm bundles/org.eclipse.platform.doc.user/reference/ref-45.htm bundles/org.eclipse.platform.doc.user/reference/ref-47.htm bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm bundles/org.eclipse.platform.doc.user/reference/ref-5.htm bundles/org.eclipse.platform.doc.user/reference/ref-56.htm bundles/org.eclipse.platform.doc.user/reference/ref-57.htm bundles/org.eclipse.platform.doc.user/reference/ref-58.htm bundles/org.eclipse.platform.doc.user/reference/ref-59.htm bundles/org.eclipse.platform.doc.user/reference/ref-6.htm bundles/org.eclipse.platform.doc.user/reference/ref-60.htm bundles/org.eclipse.platform.doc.user/reference/ref-61.htm bundles/org.eclipse.platform.doc.user/reference/ref-65.htm bundles/org.eclipse.platform.doc.user/reference/ref-66.htm bundles/org.eclipse.platform.doc.user/reference/ref-67.htm bundles/org.eclipse.platform.doc.user/reference/ref-68.htm bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm bundles/org.eclipse.platform.doc.user/reference/ref-7.htm bundles/org.eclipse.platform.doc.user/reference/ref-70.htm bundles/org.eclipse.platform.doc.user/reference/ref-71.htm bundles/org.eclipse.platform.doc.user/reference/ref-72.htm bundles/org.eclipse.platform.doc.user/reference/ref-73.htm bundles/org.eclipse.platform.doc.user/reference/ref-8.htm bundles/org.eclipse.platform.doc.user/reference/ref-9.htm bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm bundles/org.eclipse.platform.doc.user/reference/ref-capabilitiespref.htm bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm bundles/org.eclipse.platform.doc.user/reference/ref-net-preferences.htm bundles/org.eclipse.platform.doc.user/reference/ref-p2-autoupdate.htm bundles/org.eclipse.platform.doc.user/reference/ref-p2-installupdate.htm bundles/org.eclipse.platform.doc.user/reference/ref-p2-siteprefs.htm bundles/org.eclipse.platform.doc.user/reference/ref-regex-find-replace.htm bundles/org.eclipse.platform.doc.user/reference/ref-search.htm bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-options.htm bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-passwd.htm bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-prefs.htm bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-recovery.htm bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-start.htm bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-works.htm bundles/org.eclipse.platform.doc.user/reference/ref-ssh2-preferences.htm bundles/org.eclipse.platform.doc.user/reference/ref-startup-workspaces.htm bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm bundles/org.eclipse.platform.doc.user/reference/ref-templates-view.htm bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm bundles/org.eclipse.platform.doc.user/reference/ref-workspaceswitch.htm bundles/org.eclipse.platform.doc.user/reference/welcome_preferences.htm bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm bundles/org.eclipse.platform.doc.user/tasks/help.xhtml bundles/org.eclipse.platform.doc.user/tasks/help_accessibility.htm bundles/org.eclipse.platform.doc.user/tasks/help_context.htm bundles/org.eclipse.platform.doc.user/tasks/help_navigate.htm bundles/org.eclipse.platform.doc.user/tasks/help_search.htm bundles/org.eclipse.platform.doc.user/tasks/help_settings.htm bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-120.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-122.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-123.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-124.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-125.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-126.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-127.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-128.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-129.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-130.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-131.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-132.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-133.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-134.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-32.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9l.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9m.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-9n.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm bundles/org.eclipse.platform.doc.user/tasks/welcome.htm bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png bundles/org.eclipse.platform.doc.user/tips/images/cap-pref.png bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png bundles/org.eclipse.platform.doc.user/tips/images/detachview1.png bundles/org.eclipse.platform.doc.user/tips/images/detachview2.png bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_1.png bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_2.png bundles/org.eclipse.platform.doc.user/tips/images/help_external_window.png bundles/org.eclipse.platform.doc.user/tips/images/help_show_topic.png bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png bundles/org.eclipse.platform.doc.user/tips/images/keycompletions.png bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png bundles/org.eclipse.platform.doc.user/tips/images/line-delimiter.png bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png bundles/org.eclipse.platform.doc.user/tips/images/props-view.png bundles/org.eclipse.platform.doc.user/tips/images/quickaccess.png bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png bundles/org.eclipse.platform.doc.user/tips/images/show-in.png bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png bundles/org.eclipse.platform.doc.user/tips/platform_tips.html bundles/org.eclipse.platform.doc.user/toc.xml bundles/org.eclipse.platform.doc.user/topics_Concepts.xml bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml bundles/org.eclipse.platform.doc.user/topics_Reference.xml bundles/org.eclipse.platform.doc.user/topics_Tasks.xml bundles/org.eclipse.platform.doc.user/whatsNew/images/alternate.png bundles/org.eclipse.platform.doc.user/whatsNew/images/apply-patch-syncview.png bundles/org.eclipse.platform.doc.user/whatsNew/images/block-selection-mode.png bundles/org.eclipse.platform.doc.user/whatsNew/images/cnf-gointo.png bundles/org.eclipse.platform.doc.user/whatsNew/images/cocoa.png bundles/org.eclipse.platform.doc.user/whatsNew/images/collapse-projection.png bundles/org.eclipse.platform.doc.user/whatsNew/images/contentMergeViewerSwitching.png bundles/org.eclipse.platform.doc.user/whatsNew/images/customicon.png bundles/org.eclipse.platform.doc.user/whatsNew/images/customize-perspective.png bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-1.png bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-2.png bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-3.png bundles/org.eclipse.platform.doc.user/whatsNew/images/gotoLine.png bundles/org.eclipse.platform.doc.user/whatsNew/images/injection_graph_func.js bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-instance-properties.png bundles/org.eclipse.platform.doc.user/whatsNew/images/open-resource-dialog.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install-details-wizard.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2installwizard.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2menu.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2repoprefs2.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2revert.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard1.png bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard2.png bundles/org.eclipse.platform.doc.user/whatsNew/images/proxy-settings-ui.png bundles/org.eclipse.platform.doc.user/whatsNew/images/quicksearch.png bundles/org.eclipse.platform.doc.user/whatsNew/images/solarisx86.png bundles/org.eclipse.platform.doc.user/whatsNew/images/switch-editors.png bundles/org.eclipse.platform.doc.user/whatsNew/images/sync-schedule.png bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-history.png bundles/org.eclipse.platform.doc.user/whatsNew/images/textSelection.png bundles/org.eclipse.platform.doc.user/whatsNew/images/welcomescale.png bundles/org.eclipse.platform.doc.user/whatsNew/images/wordinplace.png bundles/org.eclipse.platform.doc.user/whatsNew/images/workspaces-preference-page.png bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html

diff --git a/bundles/org.eclipse.jdt.doc.isv/.cvsignore b/bundles/org.eclipse.jdt.doc.isv/.cvsignore
deleted file mode 100644
index f29a4cb..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/.cvsignore
+++ /dev/null

@@ -1,2 +0,0 @@
-jdtOptions.tmp.txt
-jdtaptOptions.tmp.txt

diff --git a/bundles/org.eclipse.jdt.doc.isv/.project b/bundles/org.eclipse.jdt.doc.isv/.project
deleted file mode 100644
index 8b90291..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/.project
+++ /dev/null

@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.jdt.doc.isv</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.SchemaBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.PluginNature</nature>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF b/bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF
deleted file mode 100644
index f4ff64b..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,7 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.jdt.doc.isv; singleton:=true
-Bundle-Version: 3.6.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin

diff --git a/bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt b/bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt
deleted file mode 100644
index cef029f..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/aaa-how-to-add-things.txt
+++ /dev/null

@@ -1,11 +0,0 @@
-The information that was here has been moved to:
-
-http://wiki.eclipse.org/index.php/How_to_add_things_to_the_Eclipse_doc
-
-
-Differences for jdt.doc.isv:
-
-- platformOptions.txt    -> jdtOptions.txt
-                            AND jdtaptOptions.txt
-                            
-- overview-platform.html -> /reference/misc/overview-jdt.html

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.html b/bundles/org.eclipse.jdt.doc.isv/about.html
deleted file mode 100644
index 4602330..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.html
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>June 2, 2006</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise 
-indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available 
-at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is 
-being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was 
-provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.ini b/bundles/org.eclipse.jdt.doc.isv/about.ini
deleted file mode 100644
index 4164f9a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.ini
+++ /dev/null

@@ -1,24 +0,0 @@
-# about.ini
-# contains information about a feature
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# "%key" are externalized strings defined in about.properties
-# This file does not need to be translated.
-
-# Property "aboutText" contains blurb for "About" dialog (translated)
-aboutText=%blurb
-
-# Property "windowImage" contains path to window icon (16x16)
-# needed for primary features only
-
-# Property "featureImage" contains path to feature image (32x32)
-featureImage=eclipse32.png
-
-# Property "aboutImage" contains path to product image (500x330 or 115x164)
-# needed for primary features only
-
-# Property "appName" contains name of the application (not translated)
-# needed for primary features only
-
-# Property "welcomePage" contains path to welcome page (special XML-based format)
-# optional
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.mappings b/bundles/org.eclipse.jdt.doc.isv/about.mappings
deleted file mode 100644
index bddaab4..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.mappings
+++ /dev/null

@@ -1,6 +0,0 @@
-# about.mappings
-# contains fill-ins for about.properties
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# This file does not need to be translated.
-
-0=@build@
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/about.properties b/bundles/org.eclipse.jdt.doc.isv/about.properties
deleted file mode 100644
index c22e18e..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/about.properties
+++ /dev/null

@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2008 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# about.properties
-# contains externalized strings for about.ini
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# fill-ins are supplied by about.mappings
-# This file should be translated.
-
-blurb=Eclipse Java development tooling plug-in developers guide\n\
-\n\
-Version: {featureVersion}\n\
-Build id: {0}\n\
-\n\
-(c) Copyright IBM Corp. and others 2000, 2004.  All rights reserved.\n\
-Visit http://www.eclipse.org/jdt
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/book.css b/bundles/org.eclipse.jdt.doc.isv/book.css
deleted file mode 100644
index 84d8880..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/book.css
+++ /dev/null

@@ -1 +0,0 @@
-@import "../PRODUCT_PLUGIN/book.css";

diff --git a/bundles/org.eclipse.jdt.doc.isv/build.properties b/bundles/org.eclipse.jdt.doc.isv/build.properties
deleted file mode 100644
index 88dc9e4..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/build.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# use provided build.xml
-custom=true

diff --git a/bundles/org.eclipse.jdt.doc.isv/build.xml b/bundles/org.eclipse.jdt.doc.isv/build.xml
deleted file mode 100644
index 3585e09..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/build.xml
+++ /dev/null

@@ -1,90 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="org.eclipse.jdt.doc.isv" default="build.jars" basedir=".">
-
-	<path id="path_bootclasspath">
-		<fileset dir="${java.home}/lib">
-			<include name="*.jar" />
-		</fileset>
-	</path>
-	<property name="bootclasspath" refid="path_bootclasspath" />
-
-	<target name="init">
-		<property name="plugin" value="org.eclipse.jdt.doc.isv" />
-		<property name="version.suffix" value="3.3.0" />
-		<property name="full.name" value="${plugin}_${version.suffix}" />
-		<property name="temp.folder" value="${basedir}/temp.folder" />
-		<property name="plugin.destination" value="${basedir}" />
-		<property name="build.result.folder" value="${basedir}" />
-		<condition property="p2.publish.parts" value="true">
-			<istrue value="${p2.gathering}" />
-		</condition>
-	</target>
-
-	<target name="build.update.jar" depends="init">
-		<delete dir="${temp.folder}" />
-		<mkdir dir="${temp.folder}" />
-		<antcall target="build.jars" />
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/" />
-		</antcall>
-		<zip zipfile="${plugin.destination}/${full.name}.jar" basedir="${temp.folder}/${full.name}" filesonly="false" />
-		<delete dir="${temp.folder}" />
-	</target>
-
-	<target name="publish.bin.parts" depends="init" if="p2.publish.parts">
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${build.result.folder}" />
-		</antcall>
-		<eclipse.gatherBundle metadataRepository="${p2.build.repo}" artifactRepository="${p2.build.repo}" buildResultFolder="${build.result.folder}" targetFolder="${build.result.folder}/${full.name}" />
-	</target>
-
-	<target name="gather.bin.parts" depends="init" if="destination.temp.folder">
-		<ant antfile="buildDoc.xml" />
-		<mkdir dir="${destination.temp.folder}/${full.name}" />
-		<copy todir="${destination.temp.folder}/${full.name}">
-			<fileset dir="${basedir}" includes="concepts/, gettingStarted/, images/, reference/, tasks/,samples/,guide/,porting/,questions/,*.properties,*.xml,*.zip,*.html,*.htm,*.png,*.css,META-INF/,index/" excludes="build.properties,build.xml,buildDoc.xml" />
-		</copy>
-		<eclipse.versionReplacer path="${destination.temp.folder}/${full.name}" version="${version.suffix}" />
-	</target>
-
-	<target name="build.jars" depends="init">
-	</target>
-
-	<target name="gather.sources" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="build.sources" depends="init">
-	</target>
-
-	<target name="gather.logs" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="clean" depends="init">
-		<delete file="${plugin.destination}/${full.name}.jar" />
-		<delete file="${plugin.destination}/${full.name}.zip" />
-		<delete dir="${temp.folder}" />
-	</target>
-
-	<target name="refresh" depends="init" if="eclipse.running">
-		<eclipse.refreshLocal resource="${plugin}" depth="infinite" />
-	</target>
-
-	<target name="zip.plugin" depends="init">
-		<delete dir="${temp.folder}" />
-		<mkdir dir="${temp.folder}" />
-		<antcall target="build.jars" />
-		<antcall target="build.sources" />
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/" />
-		</antcall>
-		<antcall target="gather.sources">
-			<param name="destination.temp.folder" value="${temp.folder}/" />
-		</antcall>
-		<delete>
-			<fileset dir="${temp.folder}" includes="**/*.bin.log" />
-		</delete>
-		<zip zipfile="${plugin.destination}/${full.name}.zip" basedir="${temp.folder}" filesonly="true" />
-		<delete dir="${temp.folder}" />
-	</target>
-
-</project>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/buildDoc.xml b/bundles/org.eclipse.jdt.doc.isv/buildDoc.xml
deleted file mode 100644
index f80c435..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/buildDoc.xml
+++ /dev/null

@@ -1,110 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="Jdt Doc Isv Build" default="all"  basedir="." >
-
-	<target name="init">
-		<available file="${basedir}/index" property="index.present"/>
-	</target>
-
-	<target name="all" depends="init" unless="index.present">
-		<antcall target="convertSchemaToHtml" />
-		<antcall target="generateJavadoc" />
-		<antcall target="build.index" />
-		<!--antcall target="createDocZip" /-->
-	</target>
-
-
-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.jdt.doc.isv" if="eclipse.running">
-		<help.buildHelpIndex manifest="${basedir}/plugin.xml" destination="${basedir}"/>
-	</target>
-
-	<target name="convertSchemaToHtml" if="eclipse.running">
-		<property name="dest" value="reference/extension-points" />
-		<record name="${basedir}/jdtconvert.txt" action="start"/>
-
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.apt.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.core.manipulation/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.debug/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.debug.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.junit/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.junit.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.launching/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.jdt.ui/plugin.xml" destination="${dest}" />
-
-		<record name="${basedir}/jdtconvert.txt" action="stop"/>
-	</target>
-
-	<target name="getJavadocPath">
-		<available file="${java.home}/../bin/javadoc.exe" property="javadoc" value="${java.home}/../bin/javadoc.exe"/>
-		<available file="${java.home}/../bin/javadoc" property="javadoc" value="${java.home}/../bin/javadoc" />
-	</target>
-
-
-	<target name="generateJavadoc" depends="getJavadocPath" if="javadoc">
-
-		<!--HACK to ensure the platform doc is built before JDT - call to this script should be moved to build.jars target-->
-		<available file="../org.eclipse.platform.doc.isv/index" property="platform.index.present"/>
-		<antcall target="buildPlatformDoc" />
-
-		<property name="optionsFile" value="jdtOptions.tmp.txt" />
-		<copy file="jdtOptions.txt" tofile="${optionsFile}" overwrite="true" />
-		
-		<condition property="argsListDelimiter" value=":">
-			<os family="unix" />
-		</condition>
-		<condition property="argsListDelimiter" value=";">
-			<os family="windows" />
-		</condition>
-
-		<replaceregexp file="${basedir}/${optionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" />
-		<replace file="${basedir}/${optionsFile}" token="@rt@" value="${bootclasspath}" />
-		<replace file="${basedir}/${optionsFile}" token="@baseLocation@" value="${baseLocation}" />
-
-
-		<!--scrub isv plugin directories of any preexisting api doc content-->
-		<delete dir="reference/api"/>
-		<mkdir dir="reference/api"/>
-
-		<exec dir="." executable="${javadoc}" output="doc.bin.log">
-			<arg line="@${basedir}/${optionsFile} -J-Xmx500M" />
-		</exec>
-		<antcall target="generateJdtAptJavadoc" />
-	</target>
-	
-	<target name="generateJdtAptJavadoc">
-		<property name="javadoc15" value="${javadoc}" />
-		
-		<property name="jdtaptoptionsFile" value="jdtaptOptions.tmp.txt" />
-		<copy file="jdtaptOptions.txt" tofile="${jdtaptoptionsFile}" overwrite="true" />
-		
-		<condition property="argsListDelimiter" value=":">
-			<os family="unix" />
-		</condition>
-		<condition property="argsListDelimiter" value=";">
-			<os family="windows" />
-		</condition>
-
-		<replaceregexp file="${basedir}/${jdtaptoptionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" />
-		<replace file="${basedir}/${jdtaptoptionsFile}" token="@rt@" value="${bootclasspath}" />
-
-		<!--scrub isv plugin directories of any preexisting api doc content-->
-		<delete dir="reference/apt" />
-		<mkdir dir="reference/apt" />
-
-		<exec dir="." executable="${javadoc15}" output="jdtapt.doc.bin.log">
-			<arg line="@${basedir}/${jdtaptoptionsFile} -J-Xmx500M" />
-		</exec>
-	</target>
-
-	<target name="buildPlatformDoc" unless="platform.index.present">
-		<ant antfile="buildDoc.xml" dir="../org.eclipse.platform.doc.isv" />
-	</target>
-
-	<target name="createDocZip">
-		<zip zipfile="${basedir}/doc.zip"
-		basedir="${basedir}"
-		includes="book.css, cpy.png, notices.html, about.html, no_help_exists.htm, concepts/**, gettingStarted/**, images/**, reference/**, tasks/**,samples/**,guide/**,questions/**"
-	/>
-	</target>
-
-</project>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/cpy.png b/bundles/org.eclipse.jdt.doc.isv/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/eclipse32.png b/bundles/org.eclipse.jdt.doc.isv/eclipse32.png
deleted file mode 100644
index 4983d64..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/eclipse32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/CopyrightTabPage.html b/bundles/org.eclipse.jdt.doc.isv/guide/CopyrightTabPage.html
deleted file mode 100644
index 9e59c29..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/CopyrightTabPage.html
+++ /dev/null

@@ -1,240 +0,0 @@
-<pre><font color="#4444cc">/*******************************************************************************
- * Copyright (c) 2009 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- ********************************************************************************/
-package org.eclipse.jdt.ui.internal.copyrightupdater;
-
-import org.eclipse.swt.SWT;
-import org.eclipse.swt.custom.SashForm;
-import org.eclipse.swt.custom.ScrolledComposite;
-import org.eclipse.swt.events.ControlEvent;
-import org.eclipse.swt.events.ControlListener;
-import org.eclipse.swt.events.SelectionAdapter;
-import org.eclipse.swt.events.SelectionEvent;
-import org.eclipse.swt.graphics.Point;
-import org.eclipse.swt.graphics.Rectangle;
-import org.eclipse.swt.layout.GridData;
-import org.eclipse.swt.layout.GridLayout;
-import org.eclipse.swt.widgets.Button;
-import org.eclipse.swt.widgets.Composite;
-import org.eclipse.swt.widgets.Control;
-import org.eclipse.swt.widgets.Group;
-import org.eclipse.swt.widgets.Label;
-import org.eclipse.swt.widgets.Layout;
-
-import org.eclipse.jface.dialogs.IDialogConstants;
-import org.eclipse.jface.layout.PixelConverter;
-
-import org.eclipse.jdt.ui.cleanup.CleanUpOptions;
-import org.eclipse.jdt.ui.cleanup.ICleanUpConfigurationUI;
-
-public class CopyrightTabPage implements ICleanUpConfigurationUI {
-
-	private PixelConverter fPixelConverter;
-	private CleanUpOptions fOptions;
-
-	public CopyrightTabPage() {
-		super();
-	}
-
-	/* (non-Javadoc)
-	 * @see org.eclipse.jdt.ui.cleanup.ICleanUpConfigurationUI#createContents(org.eclipse.swt.widgets.Composite)
-	 */
-	public Composite createContents(Composite parent) {
-		final int numColumns= 4;
-
-		if (fPixelConverter == null) {
-			fPixelConverter= new PixelConverter(parent);
-		}
-
-		final SashForm sashForm = new SashForm(parent, SWT.HORIZONTAL);
-		sashForm.setFont(parent.getFont());
-
-		Composite scrollContainer = new Composite(sashForm, SWT.NONE);
-
-		GridData gridData = new GridData(SWT.FILL, SWT.FILL, true, true);
-		scrollContainer.setLayoutData(gridData);
-
-		GridLayout layout= new GridLayout(2, false);
-		layout.marginHeight= 0;
-		layout.marginWidth= 0;
-		layout.horizontalSpacing= 0;
-		layout.verticalSpacing= 0;
-		scrollContainer.setLayout(layout);
-
-		ScrolledComposite scroll= new ScrolledComposite(scrollContainer, SWT.V_SCROLL | SWT.H_SCROLL);
-		scroll.setLayoutData(new GridData(SWT.FILL, SWT.FILL, true, true));
-		scroll.setExpandHorizontal(true);
-		scroll.setExpandVertical(true);
-
-		final Composite settingsContainer= new Composite(scroll, SWT.NONE);
-		settingsContainer.setFont(sashForm.getFont());
-
-		scroll.setContent(settingsContainer);
-
-		settingsContainer.setLayout(new PageLayout(scroll, 400, 400));
-		settingsContainer.setLayoutData(new GridData(SWT.FILL, SWT.FILL, true, true));
-
-		Composite settingsPane= new Composite(settingsContainer, SWT.NONE);
-		settingsPane.setLayoutData(new GridData(SWT.FILL, SWT.FILL, true, true));
-
-		layout= new GridLayout(numColumns, false);
-		layout.verticalSpacing= (int)(1.5 * fPixelConverter.convertVerticalDLUsToPixels(IDialogConstants.VERTICAL_SPACING));
-		layout.horizontalSpacing= fPixelConverter.convertHorizontalDLUsToPixels(IDialogConstants.HORIZONTAL_SPACING);
-		layout.marginHeight= fPixelConverter.convertVerticalDLUsToPixels(IDialogConstants.VERTICAL_MARGIN);
-		layout.marginWidth= fPixelConverter.convertHorizontalDLUsToPixels(IDialogConstants.HORIZONTAL_MARGIN);
-		settingsPane.setLayout(layout);
-		doCreatePreferences(settingsPane);
-
-		settingsContainer.setSize(settingsContainer.computeSize(SWT.DEFAULT, SWT.DEFAULT));
-
-		scroll.addControlListener(new ControlListener() {
-
-			public void controlMoved(ControlEvent e) {
-			}
-
-			public void controlResized(ControlEvent e) {
-				settingsContainer.setSize(settingsContainer.computeSize(SWT.DEFAULT, SWT.DEFAULT));
-			}
-		});
-
-		Label sashHandle = new Label(scrollContainer, SWT.SEPARATOR | SWT.VERTICAL);
-		gridData= new GridData(SWT.RIGHT, SWT.FILL, false, true);
-		sashHandle.setLayoutData(gridData);	
-
-		return sashForm;		
-	}
-	
-	
-	
-	/**
-	 * Creates the preferences for the tab page. 
-	 * 
-	 * @param composite Composite to create in  
-	 */
-	protected void doCreatePreferences(Composite composite) {
-		Group group= new Group(composite, SWT.NONE);
-		group.setLayoutData(new GridData(SWT.FILL, SWT.FILL, true, false));
-		group.setLayout(new GridLayout(1, false));
-		group.setText("Copyright Update"); //$NON-NLS-1$
-
-		final Button updateCheckbox= new Button(group, SWT.CHECK);
-		updateCheckbox.setLayoutData(new GridData(SWT.BEGINNING, SWT.CENTER, false, false));
-		updateCheckbox.setText("Update the Copyrights"); //$NON-NLS-1$
-		updateCheckbox.setSelection(fOptions.isEnabled("cleanup.update_copyrights")); //$NON-NLS-1$
-		updateCheckbox.addSelectionListener(new SelectionAdapter() {
-			/* 
-			 * @see org.eclipse.swt.events.SelectionAdapter#widgetSelected(org.eclipse.swt.events.SelectionEvent)
-			 */
-			public void widgetSelected(SelectionEvent e) {
-				fOptions.setOption("cleanup.update_copyrights", updateCheckbox.getSelection() ? CleanUpOptions.TRUE : CleanUpOptions.FALSE); //$NON-NLS-1$
-			}
-		});		
-	}
-
-	/* (non-Javadoc)
-	 * @see org.eclipse.jdt.ui.cleanup.ICleanUpConfigurationUI#getCleanUpCount()
-	 */
-	public int getCleanUpCount() {		
-		return 1;
-	}
-
-	/* (non-Javadoc)
-	 * @see org.eclipse.jdt.ui.cleanup.ICleanUpConfigurationUI#getPreview()
-	 */
-	public String getPreview() {		
-		StringBuffer buf= new StringBuffer();
-
-		if (fOptions.isEnabled("cleanup.update_copyrights")) {//$NON-NLS-1$
-			buf.append("/* Copyright (c) 2007, 2009 IBM Corporation and others.*/"); //$NON-NLS-1$
-		} else {
-			buf.append("/* Copyright (c) 2007, 2008 IBM Corporation and others.*/"); //$NON-NLS-1$
-		}
-
-		return buf.toString();
-
-	}
-
-	/* (non-Javadoc)
-	 * @see org.eclipse.jdt.ui.cleanup.ICleanUpConfigurationUI#getSelectedCleanUpCount()
-	 */
-	public int getSelectedCleanUpCount() {		
-		return fOptions.isEnabled("cleanup.update_copyrights") ? 1 : 0; //$NON-NLS-1$
-	}
-
-	/* (non-Javadoc)
-	 * @see org.eclipse.jdt.ui.cleanup.ICleanUpConfigurationUI#setOptions(org.eclipse.jdt.ui.cleanup.CleanUpOptions)
-	 */
-	public void setOptions(CleanUpOptions options) {
-		fOptions= options;
-
-	}
-	
-	/**
-	 * Layout used for the settings part. Makes sure to show scrollbars
-	 * if necessary. The settings part needs to be layouted on resize.
-	 */
-	private static class PageLayout extends Layout {
-
-		private final ScrolledComposite fContainer;
-		private final int fMinimalWidth;
-		private final int fMinimalHight;
-
-		private PageLayout(ScrolledComposite container, int minimalWidth, int minimalHight) {
-			fContainer= container;
-			fMinimalWidth= minimalWidth;
-			fMinimalHight= minimalHight;
-		}
-
-		public Point computeSize(Composite composite, int wHint, int hHint, boolean force) {
-			if (wHint != SWT.DEFAULT &amp;&amp; hHint != SWT.DEFAULT) {
-				return new Point(wHint, hHint);
-			}
-
-			int x = fMinimalWidth;
-			int y = fMinimalHight;
-			Control[] children = composite.getChildren();
-			for (int i = 0; i &lt; children.length; i++) {
-				Point size = children[i].computeSize(SWT.DEFAULT, SWT.DEFAULT, force);
-				x = Math.max(x, size.x);
-				y = Math.max(y, size.y);
-			}
-
-			Rectangle area= fContainer.getClientArea();
-			if (area.width > x) {
-				fContainer.setExpandHorizontal(true);
-			} else {
-				fContainer.setExpandHorizontal(false);
-			}
-
-			if (area.height > y) {
-				fContainer.setExpandVertical(true);
-			} else {
-				fContainer.setExpandVertical(false);
-			}
-
-			if (wHint != SWT.DEFAULT) {
-				x = wHint;
-			}
-			if (hHint != SWT.DEFAULT) {
-				y = hHint;
-			}
-
-			return new Point(x, y);
-		}
-
-		/* (non-Javadoc)
-		 * @see org.eclipse.swt.widgets.Layout#layout(org.eclipse.swt.widgets.Composite, boolean)
-		 */
-		public void layout(Composite composite, boolean force) {
-			Rectangle rect = composite.getClientArea();
-			Control[] children = composite.getChildren();
-			for (int i = 0; i &lt; children.length; i++) {
-				children[i].setSize(rect.width, rect.height);
-			}
-		}
-	}
-}</font></pre>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png
deleted file mode 100644
index 99197d3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/annotation_processing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png
deleted file mode 100644
index cc95af0..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/compiler_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png
deleted file mode 100644
index 3a4c514..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/factory_path.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png
deleted file mode 100644
index 8f7d48b..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/javanavigator.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png
deleted file mode 100644
index 55648c9..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/openables.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png b/bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png
deleted file mode 100644
index 35ac2fb..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/images/sourceelements.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm
deleted file mode 100644
index 8e52041..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT structure and API</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>JDT structure and API</h1>
-<p>Given that the JDT supplies a full featured Java IDE, why would you need to 
-  use the JDT API?</p>
-<p>If you are building a plug-in that interacts with Java programs or resources 
-  as part of its function, you may need to do one or more of the following things:</p>
-<ul>
-  <li> Programmatically manipulate Java resources, such as creating projects, 
-    generating Java source code, performing builds, or detecting problems in code.</li>
-  <li> Programmatically launch a Java program from the platform</li>
-  <li> Provide a new type of VM launcher to support a new family of Java runtimes</li>
-  <li> Add new functions and extensions to the Java IDE itself</li>
-</ul>
-<p>If you want to use JDT API in your plug-in, you must include the JDT plug-ins 
-  as prerequisites in your plug-in.xml.</p>
-<ul>
-  <li><b>org.eclipse.jdt.core</b> is the plug-in that defines the core Java elements 
-    and API. You should always list this plug-in as a prerequisite.</li>
-  <li><b>org.eclipse.jdt.ui</b> is the plug-in that defines the Java UI API. You 
-    should list this plug-in as a prerequisite if you are using the JDT UI classes.</li>
-  <li><b>org.eclipse.jdt.junit</b> is the plug-in that defines the JUnit integration API. You 
-    should list this plug-in as a prerequisite if you are using the JUnit integration classes.</li>
-  <li><b>org.eclipse.jdt.launching</b> is the plug-in that defines the Java launching 
-    and runtime support. You should list this plug-in as a prerequisite if you 
-    need to launch Java virtual machines programmatically.</li>
-  <li><b>org.eclipse.jdt.debug</b> is the plug-in that defines the Java debug 
-    model. You should list this plug-in as a prerequisite if you need to programmatically 
-    access objects in a program being debugged.</li>
-  <li><b>org.eclipse.jdt.debug.ui</b> is the plug-in that defines the Java debug 
-    UI extensions. You should list this plug-in as a prerequisite if you need 
-    to programmatically access the prompting source locator or Java launch configuration 
-    tabs.</li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm
deleted file mode 100644
index 15fc495..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_classpath.htm
+++ /dev/null

@@ -1,293 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting the Java build path</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY>
-<h2>
-Setting the Java build path</h2>
-<P>
-
-This section describes how to set the Java build path.&nbsp; The build path is
-the classpath that is used for building a Java project (<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html">IJavaProject</a></b>).
-</p>
-<P>
-A classpath is simply an array of classpath entries (<b><a href="../reference/api/org/eclipse/jdt/core/IClasspathEntry.html">IClasspathEntry</a></b>)
-that describe the types that are available.&nbsp; The types can appear in source
-or binary form and the ordering of the entries on the path defines the lookup
-order for resolving types during a build.
-</p>
-
-<P>
-The Java build path is reflected in the structure of a Java project
-element.&nbsp; You can query a project for its package fragment roots (<b><a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html">IPackageFragmentRoot</a></b>).&nbsp;
-Each classpath entry maps to one or more package fragment roots, each of which
-further contains a set of package fragments.</p>
-<P>This discussion of the
-build path does not involve the Java runtime path, which can be defined
-separately from the build path.&nbsp; (See <b><a href="../guide/jdt_api_run.htm">Running
-Java code</a></b> for a discussion of the runtime classpath.)</p>
-
-<h3>
-Changing the build path</h3>
-<P>
-You can programmatically change a project's build path using <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setRawClasspath(org.eclipse.jdt.core.IClasspathEntry[], org.eclipse.core.runtime.IProgressMonitor)">
-setRawClasspath</a></b> on the corresponding project's Java element.&nbsp; The
-following code sets the classpath for a project resource:</p>
-
-	<pre><font color='#4444CC'>
-	IProject project = ... // get some project resource
-	IJavaProject javaProject = JavaCore.create(project);
-	IClasspathEntry[] newClasspath = ...;
-	javaProject.setRawClasspath(newClasspath, someProgressMonitor);
-	</font></pre>
-
-<P>(Note:&nbsp; The use of the term &quot;raw&quot; classpath is used to
-emphasize the fact that any variables used to describe entry locations have not
-been resolved.)
-</p>
-<P>
-The Java build path is persisted into a file named '.classpath' in the project's
-file structure.&nbsp; The purpose of this file is to provide a way to share Java build path settings with others through 
-some source code repository. In particular, this file should not be manually edited, since it may get corrupted.
-</p> 
-<H3>
-Classpath entries</H3>
-<P>
-Classpath entries can be defined using factory methods defined on <b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html">JavaCore</a></b>.&nbsp;
-Classpath entries can reference any of the following:</p>
-
-<ul>
-<li><b>a source folder</b> - 
-a folder containing source compilation units organized under their corresponding package directory structure. Source folders are used to better structure 
-source files in large projects, and may only be referenced within the containing project.
-  The corresponding factory method is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newSourceEntry(org.eclipse.core.runtime.IPath)">newSourceEntry</a></b>.
-Inside a given source folder, each compilation unit is expected to be nested in the appropriate folder structure according to its package
-  statement.&nbsp; For example, compilation unit 'X.java' in package 'p1' 
-must be located inside sub-folder 'p1' of a source folder.
-It is possible to use multiple source folders, as long as they don't overlap. A
-  source folder may be assigned its own output location which determines where
-  generated class files should be placed.&nbsp; If none is specified, then class
-  files will be placed in the containing project's output location
-  (see <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setOutputLocation(org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IProgressMonitor)">IJavaProject.setOutputLocation</a></b>).<P>The
-  following is an example classpath entry that denotes the source folder 'src' of project
-  'MyProject':</p>
-	<pre><font color='#4444CC'>   IClasspathEntry srcEntry = JavaCore.newSourceEntry(new Path(&quot;/MyProject/src&quot;));</font></pre>
-</li>
-<li><b>a binary library</b> - either a class file folder (contained inside or outside the workspace) or a class file archive file (contained inside or outside the workspace).
-Archive libraries can have attached source archives, which are extracted when asking a class file element  for
-  its source (<b><a href="../reference/api/org/eclipse/jdt/core/ISourceReference.html#getSource()">getSource</a></b>).
-The factory method for libraries is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newLibraryEntry(org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath, boolean)">newLibraryEntry</a></b>.
-<P>
-The following is an example classpath entry that denotes the class file folder 'lib' of  'MyProject':</p>
-	<pre><font color='#4444CC'>
-  IClasspathEntry libEntry = JavaCore.newLibraryEntry(
-    new Path(&quot;/MyProject/lib&quot;), 
-    null, // no source
-    null, // no source
-    false); // not exported
-	</font></pre>
-  <p>The following classpath entry has a source attachment:</p>
-	<pre><font color='#4444CC'>
-  IClasspathEntry libEntry = JavaCore.newLibraryEntry(
-    new Path(&quot;d:/lib/foo.jar&quot;), // library location
-    new Path(&quot;d:/lib/foo_src.zip&quot;), // source archive location
-    new Path(&quot;src&quot;), // source archive root path
-    true); // exported
-	</font></pre><p>The source archive root path describes the location of the
-  root within the source archive.&nbsp; If set to null, the root of the archive
-  will be inferred dynamically.</p>
-  <br></li>
-<li><b>a prerequisite project</b> - another Java project.&nbsp; A prerequisite project always contributes its source folders to dependent projects.
-It can also optionally contribute any of its classpath entries which are tagged as exported (see factory methods supporting
-  the extra boolean argument 'isExported').
-This means that in addition to contributing its source to its dependents, a project will also export all classpath entries tagged as
-  such.&nbsp; This allows prerequisite projects to better hide their own
-  structure changes.&nbsp; For example, a given project may choose to switch from using a source folder to exporting a library.&nbsp;
-  This can be done without requiring its dependent projects to change their classpath.
-The factory method for a project prerequisite is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newProjectEntry(org.eclipse.core.runtime.IPath, boolean)">newProjectEntry</a></b>.
-<P>
-The following classpath entry denotes a prerequisite project 'MyFramework'.</p>
-	<pre><font color='#4444CC'>
-  IClasspathEntry prjEntry = JavaCore.newProjectEntry(new Path(&quot;/MyFramework&quot;), true); // exported
-	</font></pre>
-</li>
-<li><b>an indirect reference to a project or library, using some classpath variable</b> -
-  The location of projects or libraries can be dynamically resolved relative to a
-classpath variable, which is specified as the first segment of the entry path. The remainder of the entry path is then appended to the resolved variable path.
-The factory method for a classpath variable is 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newVariableEntry(org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IPath)">newVariableEntry</a></b>.
-Classpath variables are global to the workspace, and can be manipulated through JavaCore methods 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getClasspathVariable(java.lang.String)">getClasspathVariable</a></b> and
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setClasspathVariable(java.lang.String, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IProgressMonitor)">setClasspathVariable</a></b>.&nbsp;
-  <p>
-It is possible to register an automatic <b><a href="../reference/api/org/eclipse/jdt/core/ClasspathVariableInitializer.html">classpath variable initializer</a></b>
-which is invoked through the extension point <b><a href="../reference/extension-points/org_eclipse_jdt_core_classpathVariableInitializer.html">org.eclipse.jdt.core.classpathVariableInitializer</a></b> 
-when the workspace is started.</p>
-<P>
-The following classpath entry denotes a library whose location is kept in the
-variable 'HOME'.&nbsp; The source attachment is defined using the
-variables&nbsp; 'SRC_HOME' and 'SRC_ROOT' :</p>
-	<pre><font color='#4444CC'>
-  IClasspathEntry varEntry = JavaCore.newVariableEntry(
-    new Path(&quot;HOME/foo.jar&quot;), // library location
-    new Path(&quot;SRC_HOME/foo_src.zip&quot;), // source archive location
-    new Path(&quot;SRC_ROOT&quot;), // source archive root path
-    true); // exported	
-  JavaCore.setClasspathVariable(&quot;HOME&quot;, new Path(&quot;d:/myInstall&quot;), null); // no progress monitor
-	</font></pre>
-</li>
-<li><b>entry denoting a classpath container</b> - an indirect reference to a structured set of project or libraries.
-  Classpath containers are used to refer to a set of classpath entries that
-  describe a complex library structure.&nbsp; Like classpath variables,
-  classpath containers <b><a href="../reference/api/org/eclipse/jdt/core/IClasspathContainer.html">(IClasspathContainer)</a></b>
-are dynamically resolved.&nbsp; Classpath containers may be used by different
-  projects, causing their path entries to resolve to distinct values per
-  project.&nbsp; They also provide meta information about the library that they
-  represent (name, kind, description of library.)&nbsp; 
-  The factory method for a classpath variable is 
-  <b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#newContainerEntry(org.eclipse.core.runtime.IPath, boolean)">newContainerEntry</a></b>.
-  Classpath containers can be manipulated through JavaCore methods 
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getClasspathContainer(org.eclipse.core.runtime.IPath, org.eclipse.jdt.core.IJavaProject)">getClasspathContainer</a></b> and
-<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setClasspathContainer(org.eclipse.core.runtime.IPath, org.eclipse.jdt.core.IJavaProject[], org.eclipse.jdt.core.IClasspathContainer[], org.eclipse.core.runtime.IProgressMonitor)">setClasspathContainer</a></b>.&nbsp;
-  <p>
-It is possible to register an automatic <b><a href="../reference/api/org/eclipse/jdt/core/ClasspathContainerInitializer.html">classpath container initializer</a></b>
-which is lazily invoked through the extension point <b><a href="../reference/extension-points/org_eclipse_jdt_core_classpathContainerInitializer.html">org.eclipse.jdt.core.classpathContainerInitializer</a></b>
-when the container needs to be bound.</p>
-  <P>The following classpath entry denotes a system class library container:</p>
-	<pre><font color='#4444CC'>
-  IClasspathEntry varEntry = JavaCore.newContainerEntry(
-    new Path(&quot;JDKLIB/default&quot;), // container 'JDKLIB' + hint 'default'
-    false); // not exported	
-
-  JavaCore.setClasspathContainer(
-    new Path(&quot;JDKLIB/default&quot;), 
-    new IJavaProject[]{ myProject }, // value for 'myProject'
-    new IClasspathContainer[] {
-      new IClasspathContainer() {
-        public IClasspathEntry[] getClasspathEntries() {
-          return new IClasspathEntry[]{ 
-            JavaCore.newLibraryEntry(new Path(&quot;d:/rt.jar&quot;), null, null, false);
-          }; 
-        }
-        public String getDescription() { return &quot;Basic JDK library container&quot;; }
-        public int getKind() { return IClasspathContainer.K_SYSTEM; }
-        public IPath getPath() { return new Path(&quot;JDKLIB/basic&quot;); }
-      }
-    }, 
-    null);
-</font></pre>
-</li>
-</ul>
-
-<h3>
-Exclusion patterns</h3>
-
-<p>A classpath source entry may be assigned an exclusion pattern, which prevents
-certain resources in a source folder from being visible on the classpath.&nbsp;
-Using a pattern allows
-specified portions of the resource tree to be filtered out.&nbsp; Each exclusion
-pattern path is relative to the classpath entry and uses a pattern mechanism
-similar to Ant.&nbsp; Exclusion patterns can be used to specify nested source
-folders as long as the outer pattern excludes the inner pattern.</p>
-
-<p> See <b><a href="../reference/api/org/eclipse/jdt/core/IClasspathEntry.html#getExclusionPatterns()">getExclusionPatterns</a></b> for
-more detail on exclusion patterns.</p>
-
-<p>
-The Java project API <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#isOnClasspath(org.eclipse.core.resources.IResource)">isOnClasspath</a>
-</b> checks both inclusion and exclusion patterns before determining
-whether a particular resource is on the classpath.</p>
-
-<P>
-Remarks:</p>
-<ul>
-<li>
-Exclusion patterns have higher precedence than inclusion patterns; in other
-words, exclusion patterns can remove files from the ones that are to be included, not the
-other way around.
-</li>
-<li>
-A nested source folder excluded from build path can be set as an output location.
- The following is an example classpath entry that denotes the source folder 'src' of project
- 'MyProject' with an excluded nested source folder used as an output location:
-	<pre><font color='#4444CC'>
-  IPath sourceFolder = new Path(&quot;/MyProject/src&quot;);
-  IPath outputLocation = sourceFolder.append(&quot;bin&quot;);
-  IClasspathEntry srcEntry = JavaCore.newSourceEntry(
-    sourceFolder, // source folder location
-    new Path[] { outputLocation }, // excluded nested folder
-    outputLocation); // output location
-    </font></pre>
-</li>
-</ul>
-<h3>
-Inclusion patterns</h3>
-
-<p>A classpath source entry may also be assigned an inclusion pattern, which explicitly
- defines resources to be visible on the classpath.&nbsp;
-When no inclusion patterns are specified, the source entry includes all relevant files
- in the resource tree rooted at this source entry's path.
-Specifying one or more inclusion patterns means that only the specified portions of
- the resource tree are to be included. Each path specified must be a relative path,
- and will be interpreted relative to this source entry's path. File patterns are
- case-sensitive. A file matched by one or more of these patterns is included in
- the corresponding package fragment root unless it is excluded by one or more of
- this entry's exclusion patterns.</p>
-
-<p>See <b><a href="../reference/api/org/eclipse/jdt/core/IClasspathEntry.html#getExclusionPatterns()">getExclusionPatterns</a></b>
- for a discussion of the syntax and semantics of path patterns. The absence of any inclusion patterns
- is semantically equivalent to the explicit inclusion pattern <code>**</code>.</p>
-
-<p>
-The Java project API <b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#isOnClasspath(org.eclipse.core.resources.IResource)">isOnClasspath</a>
-</b> checks both inclusion and exclusion patterns before determining
-whether a particular resource is on the classpath.</p>
-
-<p>Examples:</p>
-<ul>
-<li>
-The inclusion pattern <code>src/**</code> by itself includes all files under a root
- folder named <code>src</code>.
-</li>
-<li>
-The inclusion patterns <code>src/**</code> and <code>tests/**</code>
- includes all files under the root folders named <code>src</code> and <code>tests</code>.
-</li>
-<li>
-The inclusion pattern <code>src/**</code> together with the exclusion pattern
- <code>src/**/Foo.java</code> includes all files under a root folder named
- <code>src</code> except for ones named <code>Foo.java</code>.
-</li>
-</ul>
-<H2>
-Classpath resolution</H2>
-
-Since classpath variables and containers allow you to define dynamically bound
-classpath entries, the classpath API distinguishes between a raw and a resolved
-classpath.&nbsp;&nbsp; The raw classpath is the one originally
-set on the Java project using 
-<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setRawClasspath(org.eclipse.jdt.core.IClasspathEntry[], org.eclipse.core.runtime.IProgressMonitor)">setRawClasspath</a></b>,
-and can be further queried by asking the project for
-<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#getRawClasspath()">getRawClasspath</a></b>.&nbsp;
-The resolved classpath can be queried using 
-<b><a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#getResolvedClasspath(boolean)">getResolvedClasspath</a></b>. 
-This operation triggers initialization of any variables and containers necessary
-to resolve the classpath.&nbsp; Many Java Model operations
-implicitly cause the Java build path to be resolved.&nbsp; For example,
-computing a project's package fragment roots requires the build path to be
-resolved.
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm
deleted file mode 100644
index fb6cb30..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeassist.htm
+++ /dev/null

@@ -1,178 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Performing code assist on Java code</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY>
-<h2>Performing code assist on Java code</h2>
-<P>
-The JDT API allows other plug-ins to perform code assist or code select on some Java elements. 
-Elements that allow this manipulation should implement <b><a href="../reference/api/org/eclipse/jdt/core/ICodeAssist.html"> ICodeAssist</a></b>.</p>
-<P>There are two kinds of manipulation:</P>
-<ul>
-<li>Code completion - compute the completion of a Java token.</li>
-<li>Code selection - answer the Java element indicated by the selected text of a
-  given offset and length.</li>
-</ul>
-<p>
-In the Java model there are two elements that implement this interface: <b><a href="../reference/api/org/eclipse/jdt/core/IClassFile.html"> IClassFile</a></b> and <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"> ICompilationUnit</a></b>.&nbsp;
-Code completion and code selection only answer results for a class file if it has attached source.</p>
-<H3>
-Code completion</h3>
-
-<H4>
-Performing a code completion
-</h4>
-<P>
-One way to programmatically perform code completion is to invoke <b><a href="../reference/api/org/eclipse/jdt/core/ICodeAssist.html#codeComplete(int, org.eclipse.jdt.core.CompletionRequestor)">ICodeAssist.codeComplete</a></b>.
-You specify the offset in the compilation unit after which the code completion
-is desired.&nbsp; You must also supply an instance of <b><a href="../reference/api/org/eclipse/jdt/core/CompletionRequestor.html"> CompletionRequestor</a></b> to accept the possible completions.</P>
-
-
-
-<P>The method in <b><a href="../reference/api/org/eclipse/jdt/core/CompletionRequestor.html#accept(org.eclipse.jdt.core.CompletionProposal)">CompletionRequestor.accept(CompletionProposal)</a>
-</b>accepts all kinds of proposals for code completion.&nbsp;
-The methods of <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html">CompletionProposal</a>
-</b> give information that describes the proposed element (its
-name, declaring type, etc.), its proposed position for insertion in the
-compilation unit, and its relevance.&nbsp;&nbsp;</P>
-
-<P>A completion requestor can accept many different kinds of completions.
-This kind is given by <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#getKind()">CompletionProposal.getKind</a></b>.
-</P><P>Some of the possible completion kinds are (The complete list of possible completion kinds can be seen on <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html">
-CompletionProposal</a></b>):</P>
-
-<ul>
-  <li>annotation attribute - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#ANNOTATION_ATTRIBUTE_REF">ANNOTATION_ATTRIBUTE_REF</a></b></li>
-  <li>anonymous type - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#ANONYMOUS_CLASS_DECLARATION">ANONYMOUS_CLASS_DECLARATION</a></b></li>
-  <li>type reference - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#TYPE_REF">TYPE_REF</a></b></li>
-  <li>field reference- <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#FIELD_REF">FIELD_REF</a></b></li>
-  <li>keyword - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#KEYWORD">KEYWORD</a></b></li>
-  <li>label reference - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#LABEL_REF">LABEL_REF</a></b></li>
-  <li>local variable reference - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#LOCAL_VARIABLE_REF">LOCAL_VARIABLE_REF</a></b></li>
-  <li>method reference - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#METHOD_REF">METHOD_REF</a></b></li>
-  <li>method declaration - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#METHOD_DECLARATION">METHOD_DECLARATION</a></b></li>
-  <li>package import or reference - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#PACKAGE_REF">PACKAGE_REF</a></b></li>
-  <li>variable name - <b><a href="../reference/api/org/eclipse/jdt/core/CompletionProposal.html#VARIABLE_DECLARATION">VARIABLE_DECLARATION</a></b></li>
-</ul>
-
-<p>The completion requestor must also be able to accept compilation
-errors.&nbsp;&nbsp;</p>
-<h4>Completion relevance
-</h4>
-
-<p>Because there may be many different possible completions, the notion of
-relevance is used to compare the relevance of a suggested completion to other
-proposals.&nbsp; Relevance is represented by a positive integer.&nbsp; The value
-has no implicit meaning except to be used relative to the value for other
-proposals.&nbsp; The relevance of a code completion candidate can be affected by
-the expected type of the expression, as it relates to the types in the
-surrounding code, such as variable types, cast types, return types, etc.&nbsp;
-The presence of an expected prefix or suffix in a completion also affects its
-relevance.
-</p>
-
-<h4>Completion context
-</h4>
-
-<p>An instance of <b><a href="../reference/api/org/eclipse/jdt/core/CompletionRequestor.html">CompletionRequestor</a></b> can also
-accept a completion context. This context is given by the method
-<b><a href="../reference/api/org/eclipse/jdt/core/CompletionRequestor.html#acceptContext(org.eclipse.jdt.core.CompletionContext)">
-CompletionRequestor.acceptContext(CompletionContext)</a></b> and does not depend on a specific completion proposal. The methods of 
-<b><a href="../reference/api/org/eclipse/jdt/core/CompletionContext.html">CompletionContext</a></b> give information that describe 
-the general context like the offset of completion, the completed token, the completed token kind (name or string literal) and its position.<br>
-</p>
-<p>A <b><a href="../reference/api/org/eclipse/jdt/core/CompletionContext.html">CompletionContext</a></b> can also give some
-information about elements (<b><a href="../reference/api/org/eclipse/jdt/core/IJavaElement.html">IJavaElement</a></b>) which are
-related to the completion location. These elements are based on the content of the completed compilation unit's buffer and are not
-the result of the last reconcile operation.<br>
-</p>
-
-<p>Some of these methods are:</p>
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/CompletionContext.html#getEnclosingElement()">getEnclosingElement()</a>
-</b> - This method returns the innermost enclosing element
-which contains the completion location</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/CompletionContext.html#getVisibleElements(java.lang.String)">getVisibleElements(String)</a>
-</b> - This method returns the elements which are visible from the completion location and which can be assigned to the given type</li>
-</ul>
-
-<H4>
-Code completion options
-</h4>
-
-<P>
-The JDT Core plug-in defines options that control the behavior of code
-completion.&nbsp; These options can be changed by other plug-ins.&nbsp;&nbsp;</P>
-<ul>
-<li>Activate Visibility Sensitive Completion<br>
-  When this option is active, code completion will not answer elements that are
-  not visible in the current context.&nbsp; (For example, it will not answer
-  private methods of a super class.)</li>
-<li>Automatic Qualification of Implicit Members<br>
-  When this option is active, completion automatically qualifies completion on implicit field references and message expressions.</li>
-</ul>
-
-<p>Additional options allow you to specify prefixes and suffixes for the
-proposed completion names for fields, static fields, local variables, and method
-arguments.&nbsp;&nbsp;</p>
-
-<p> See&nbsp;<a href="jdt_api_options.htm#codeassist"> JDT Core Code Assist
-Options</a>
-for more information about the code assist options and their defaults.</p>
-
-<H3>
-Code selection</h3>
-
-<H4>
-Performing a code selection
-</h4>
-<P>Code selection is used to find the Java element represented by a range of
-text (typically the selected text) in a compilation unit.&nbsp; To programmatically perform code selection,
-you must invoke <b><a href="../reference/api/org/eclipse/jdt/core/ICodeAssist.html#codeSelect(int, int)">ICodeAssist.codeSelect</a></b>.
-You must supply the starting index location of the selection and its
-length. The result is an array of Java elements. Most of the time there is only one element in the array, but if the selection is ambiguous then all the possible elements are returned.</p><P>In
-the following example, code select is invoked for a compilation unit.</p>
-
-<pre><font color='#4444CC'>   // Get the compilation unit
-   ICompilationUnit unit = ...;
-   
-   // Get the offset and length
-   int offset = ...;
-   int length = ...;
-   
-   // perform selection
-   IJavaElement[] elements = unit.codeSelect(offset, length);
-   System.out.println(&quot;the selected element is &quot; + element[0].getElementName());
-</font></pre>
-
-<H4>
-Selection at cursor location
-</h4>
-<P>
-When the selection length is specified as 0, a selection will be computed by
-finding the complete token that encloses the specified offset.&nbsp; Consider
-the following example method:</P>
-
-<P>
-<code>&nbsp;&nbsp; public void fooMethod(Object) {<br>
-&nbsp;&nbsp; }<br>
-</code>
-</P>
-
-If you specify an offset after the first character of <i>fooMethod</i>, and you
-specify a length of 0,&nbsp; then the selection will be computed to include the
-entire token <i>fooMethod</i>. If instead, you specify a length of 5, the
-selection will considered as <i>ooMet</i>.
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeformatter.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeformatter.htm
deleted file mode 100644
index a9741f0..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_codeformatter.htm
+++ /dev/null

@@ -1,248 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<meta HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the code formatter</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</head>
-<body>
-<h2>Using the code formatter</h2>
-<P>The JDT API allows other plug-ins to use the default <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html">code formatter</a></b> to format source code.</p>
-The two methods to consider are:
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/ToolFactory.html#createCodeFormatter(java.util.Map)">ToolFactory.createCodeFormatter(Map)</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/ToolFactory.html#createCodeFormatter(java.util.Map, int)">ToolFactory.createCodeFormatter(Map, int)</a></b></li>
-</ul>
-Note: The <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html">CodeFormatter</a></b> class is not intended to be subclassed by clients.
-
-<h3>Getting a code formatter instance</h3>
-<p>
-The factory methods on <b><a href="../reference/api/org/eclipse/jdt/core/ToolFactory.html">ToolFactory</a></b> can be invoked to create a new instance of the default code formatter. 
-Before invoking one of those, you need to define a map that contains the code formatter options. In order to create such a map, you can use the methods defined in the class
-<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html">DefaultCodeFormatterConstants</a></b> like 
-<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#getEclipseDefaultSettings()">DefaultCodeFormatterConstants.getEclipseDefaultSettings()</a></b></p>
-<p>NOTE: These predefined maps contain only the code formatter specific options. In order to invoke the code formatter, you also need to specify what kind of source 
-the code formatter will format. In order to do so, specify the three options:</p>
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_CODEGEN_TARGET_PLATFORM">JavaCore.COMPILER_CODEGEN_TARGET_PLATFORM</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_SOURCE">JavaCore.COMPILER_SOURCE</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_COMPLIANCE">JavaCore.COMPILER_COMPLIANCE</a></b></li>
-</ul>
-<p>The possible values of these options are given by the constants:</p>
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_1">JavaCore.VERSION_1_1</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_2">JavaCore.VERSION_1_2</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_3">JavaCore.VERSION_1_3</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_4">JavaCore.VERSION_1_4</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_5">JavaCore.VERSION_1_5</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_6">JavaCore.VERSION_1_6</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_7">JavaCore.VERSION_1_7</a></b></li>
-</ul>
-<p>If you want to modify the default maps, it is recommended that you use the methods defined on <b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html">DefaultCodeFormatterConstants</a></b>
-to create the values of the corresponding options. This is especially true for the options relative to code wrapping.
-</p>
-
-<h3>Invoking the code formatter</h3>
-<p>Use the newly created code formatter to format code snippets.
-The default code formatter allows you to format different kind of code snippets.<br>
-These kinds are specified in the documentation of the <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#format(int, java.lang.String, int, int, int, java.lang.String)">format</a></b> method.
-The returned value of this method is a text edit. This text edit then needs to be applied to an <b><a href="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/jface/text/IDocument.html">IDocument</a></b> instance
-in order to get the formatted result.</p>
-
-<h4>Example</h4>
-<pre><font color="#4444CC">
-		// take default Eclipse formatting options
-		Map options = DefaultCodeFormatterConstants.getEclipseDefaultSettings();
-		
-		// initialize the compiler settings to be able to format 1.5 code
-		options.put(JavaCore.COMPILER_COMPLIANCE, JavaCore.VERSION_1_5);
-		options.put(JavaCore.COMPILER_CODEGEN_TARGET_PLATFORM, JavaCore.VERSION_1_5);
-		options.put(JavaCore.COMPILER_SOURCE, JavaCore.VERSION_1_5);
-		
-		// change the option to wrap each enum constant on a new line
-		options.put(
-			DefaultCodeFormatterConstants.FORMATTER_ALIGNMENT_FOR_ENUM_CONSTANTS,
-			DefaultCodeFormatterConstants.createAlignmentValue(
-				true,
-				DefaultCodeFormatterConstants.WRAP_ONE_PER_LINE,
-				DefaultCodeFormatterConstants.INDENT_ON_COLUMN));
-		
-		// instanciate the default code formatter with the given options
-		final CodeFormatter codeFormatter = ToolFactory.createCodeFormatter(options);
-		
-		// retrieve the source to format
-		String source = null;
-		try {
-			source = ...; // retrieve the source 
-		} catch (IOException e) {
-			System.err.println("Could not retrieve the source"); //$NON-NLS-1$
-			e.printStackTrace();
-			return;
-		}
-		final TextEdit edit = codeFormatter.format(
-			CodeFormatter.K_COMPILATION_UNIT, // format a compilation unit
-			source, // source to format
-			0, // starting position
-			source.length(), // length
-			0, // initial indentation
-			System.getProperty("line.separator") // line separator
-		);
-		
-		IDocument document = new Document(source);
-		try {
-			edit.apply(document);
-		} catch (MalformedTreeException e) {
-			e.printStackTrace();
-		} catch (BadLocationException e) {
-			e.printStackTrace();
-		}
-		
-		// display the formatted string on the System out
-		System.out.println(document.get());
-</font></pre>
-<p>On this example,</p>
-<pre><font color="#4444CC">
-public enum X { A,B,C,D,E,F}
-</font></pre>
-the result would be:
-<pre><font color="#4444CC">
-public enum X {
-	A,
-	B,
-	C,
-	D,
-	E,
-	F
-}
-</font></pre>
-<h3>Formatting a set of regions</h3>
-The default <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html">code formatter</a></b> allows to format a set of regions of a given source file.<br>
-This can be achieved by calling the <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#format(int, java.lang.String, org.eclipse.jface.text.IRegion[], int, java.lang.String)">format(int, String, IRegion[], int, String)</a></b> method of the code formatter,
-with a given <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_UNKNOWN">source kind</a></b>
-and an array of <b><a href="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/jface/text/IRegion.html">regions</a></b>.
-<ul>
-<li>Each of the region to format must be within source range and should not overlap with another region.</li>
-<li>The array of regions to format must contain at least one region. Regions should be sorted by their offsets, smaller offset first.</li>
-</ul>
-<h3>Comment Formatter API</h3>
-The default <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html">code formatter</a></b>
-API offers the possibility to format comments during the processing of the code snippet.<br>
-This can be achieved by combining the appropriate flag <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#F_INCLUDE_COMMENTS">F_INCLUDE_COMMENTS</a></b> with <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_COMPILATION_UNIT">K_COMPILATION_UNIT</a></b> and <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_UNKNOWN">K_UNKNOWN</a></b> flags.<br>
-<br>
-This flag is effective only if the corresponding formatting option was enabled when calling <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#format(int, java.lang.String, int, int, int, java.lang.String)">format(int, String, int, int, int, String)</a></b> or <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#format(int, java.lang.String, org.eclipse.jface.text.IRegion[], int, java.lang.String)">format(int, String, IRegion[], int, String)</a></b> methods:
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_JAVADOC_COMMENT">FORMATTER_COMMENT_FORMAT_JAVADOC_COMMENT</a></b> which controls the formatting of javadoc comments</li> 
-<li><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_BLOCK_COMMENT">FORMATTER_COMMENT_FORMAT_BLOCK_COMMENT</a></b> which controls the formatting of multiple lines comments</li> 
-<li><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_LINE_COMMENT">FORMATTER_COMMENT_FORMAT_LINE_COMMENT</a></b> which controls the formatting of single line comments</li> 
-</ul> 
-
-<h3>Comment formatter options</h3>
-Various formatting options are available in order to format comments:
-<ul>
-<li>General options to enable or disable the formatting of specific comments (javadoc, multi or single line comments), set maximum line width for comments.</li>
-<li>javadoc comments options to enable the formatting of code snippets or HTML sections inside javadoc comments, indent tag descriptions, etc.</li>
-<li>block comments option to keep or remove blanks lines within such comment</li>
-</ul>
-For detailed information about these settings, refer to the <b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html">DefaultCodeFormatterConstants</a></b>
-
-
-<h3>Formatting comments with the stand-alone formatter</h3>
-The default <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html">code formatter</a></b> can be used to format comments (javadoc, multi or single line).
-In this case, the source passed to the <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#format(int, java.lang.String, int, int, int, java.lang.String)">format method</a></b> should only contain a specific kind of comments,
-and corresponding kind <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_JAVA_DOC">K_JAVA_DOC</a></b>, <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_MULTI_LINE_COMMENT">K_MULTI_LINE_COMMENT</a></b> or <b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_SINGLE_LINE_COMMENT">K_SINGLE_LINE_COMMENT</a></b> should be used.<br>
-<ul>
-<li><h4>Formatting javadoc comments</h4>
-The following unformatted javadoc:
-<pre><font color="#4444CC">
- 	/**
- * This is just a simple example to show how javadoc comments can 			 be formatted .
- * @param str The input string
- 	 * @return 		 		The resulting 		string
- 	 */
-</font></pre>
-should be formatted as follows:
-<pre><font color="#4444CC">
-/**
- * This is just a simple example to show how javadoc comments can be formatted .
- * 
- * @param str
- *            The input string
- * @return The resulting string
- */
-</font></pre>
-using command:
-<pre><font color="#4444CC">
-(...)
- final TextEdit edit = codeFormatter.format(
-	<b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_JAVA_DOC">CodeFormatter.K_JAVA_DOC</a></b>, // specify the kind: javadoc
-	source, // source to format (as per the above example)
-	0, // starting position
-	source.length(), // length
-	0, // initial indentation
-	System.getProperty("line.separator") // line separator
-);
-(...)
-</font></pre></li>
-<li><h4>Formatting multi-line comments</h4>
-The following unformatted multi-line comment:
-<pre><font color="#4444CC">
-/*
-	 * This is just an example of multi- line comment intended to demonstrate the default code formatter ability to format multi-line comments .
-	 * 
-	 * 		These possibilities include:	Formatting of javadoc 				comments, 
-	 * 				formatting of multi-line comments
- */
-</font></pre>
-should be formatted as follows:
-<pre><font color="#4444CC">
-/*
- * This is just an example of multi- line comment intended to demonstrate
- * the default code formatter ability to format multi-line comments .
- * 
- * These possibilities include: Formatting of javadoc comments, formatting
- * of multi-line comments
- */
-</font></pre>
- using command:
-<pre><font color="#4444CC">
-(...)
- final TextEdit edit = codeFormatter.format(
-	<b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_MULTI_LINE_COMMENT">CodeFormatter.K_MULTI_LINE_COMMENT</a></b>, // specify the kind: multi-line comments
-	source, // source to format (as per the above example)
-	0, // starting position
-	source.length(), // length
-	0, // initial indentation
-	System.getProperty("line.separator") // line separator
-);
-(...)
-</font></pre></li>
-<li><h4>Formatting single line comments</h4>
-The following unformatted single line comments:
-<pre><font color="#4444CC">
-// This is a long comment that should be split in multiple line comments in case the line comment formatting is enabled
-</font></pre>
-should be formatted as follows:
-<pre><font color="#4444CC">
-// This is a long comment that should be split in multiple line comments in
-// case the line comment formatting is enabled
-</font> </pre>
- using command:
-<pre><font color="#4444CC">
-(...)
- final TextEdit edit = codeFormatter.format(
-	<b><a href="../reference/api/org/eclipse/jdt/core/formatter/CodeFormatter.html#K_SINGLE_LINE_COMMENT">CodeFormatter.K_SINGLE_LINE_COMMENT</a></b>,  // specify the kind: single-line comments
-	source, // source to format (as per the above example)
-	0, // starting position
-	source.length(), // length
-	0, // initial indentation
-	System.getProperty("line.separator") // line separator
-);
-(...)
-</font></pre></li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm
deleted file mode 100644
index 49c5dca..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm
+++ /dev/null

@@ -1,958 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-     
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Compiling Java code</title>
-          
-  <link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2> Compiling Java code</h2>
-<p> The JDT plug-ins include an incremental and batch Java compiler for building 
-Java .class files from source code. There is no direct API provided by the 
-compiler. It is installed as a builder on Java projects. Compilation is triggered 
-using standard platform build mechanisms.</p>
-<p> The platform build mechanism is described in detail in <a href="../../org.eclipse.platform.doc.isv/guide/resAdv_builders.htm" class="XRef">
- Incremental project builders</a>.</p>
-<h3> Compiling code</h3>
-<p> You can programmatically compile the Java source files in a project using 
-the build API.</p>
-<pre><font color="#4444cc">
-   IProject myProject;
-   IProgressMonitor myProgressMonitor;
-   myProject.build(IncrementalProjectBuilder.INCREMENTAL_BUILD, myProgressMonitor);
-</font></pre>
-<p>For a Java project, this invokes the Java incremental project builder
- (along with any other incremental project builders that have been added
-to the project's build spec). The generated .class files are written to
-the designated output folder. Additional resource files are also copied to the output folder.&nbsp;</p>
-<p>In the case of a full batch build, all the
-.class files in the output folder may be 'scrubbed' to ensure that no stale
-files are found. This is controlled using a JDT Core Builder Option (<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER">CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER</a>).&nbsp;
-The default for this option is to clean output folders.&nbsp; Unless this option
-is reset, you must ensure that you place all .class files for which
-you do not have corresponding source files in a separate class file folder
-on the classpath  instead of the output folder.</p>
-<p>The
-incremental and batch builders can be configured with other options that
-control which resources are copied to the output folder.&nbsp; The following sample shows how to set up a resource filter so that files ending with '.ignore' and folders named 'META-INF',
-are not copied to the output folder:</p>
-<pre><font color="#4444cc">
-   Hashtable options = JavaCore.getOptions();
-   options.put(JavaCore.CORE_JAVA_BUILD_RESOURCE_COPY_FILTER, &quot;*.ignore,META-INF/&quot;);
-   JavaCore.setOptions(options);
-</font></pre>
-<p> Filenames are filtered out if they match one of the supplied patterns. Entire 
-folders are filtered out if their name matches one of the supplied folder names 
-which end in a path separator.</p>
-<p> The incremental and batch builders can also be configured to only generate
- a single error when the .classpath file has errors. This option is set by
- default and eliminates numerous errors.&nbsp; See <a href="jdt_api_options.htm#builder">JDT
-Core Builder Options</a> for a complete list of builder-related options and
-their defaults. </p>
-<p>The compiler can also be configured using <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a>
-options.&nbsp; For example, you can define the severity that should be used for
-different kinds of problems that are found during compilation.&nbsp; See <a href="jdt_api_options.htm#compiler">JDT
-Core Compiler Options </a>for a complete list of compiler-related options and their defaults. </p>
-<p>When programmatically configuring options for the builder or compiler, you
-should specify the scope of the option.&nbsp; For example, setting up a
-resource filter may apply to a particular project only:</p>
-<pre><font color="#4444cc">
-   Hashtable options = myProject.getOptions(false);  // get only the options set up in this project
-   options.put(JavaCore.CORE_JAVA_BUILD_RESOURCE_COPY_FILTER, &quot;*.ignore,META-INF/&quot;);
-   myProject.setOptions(options);
-</font>
-</pre>
-<h3>Using the batch compiler</h3>
-
-<h4>Finding the batch compiler</h4>
-
-<p>The batch compiler class is located in the JDT Core plug-in.
-The name of the class is <i>org.eclipse.jdt.compiler.batch.BatchCompiler</i>.
-It is packaged into <code>plugins/org.eclipse.jdt.core_3.4.0.&lt;qualifier&gt;.jar</code>. Since 3.2, it is also available as a separate download.
-The name of the file is <code>ecj.jar</code>. Its corresponding source is also available. To get them, go to the <a href="http://download.eclipse.org/eclipse/downloads/">download page</a> and 
-search for the section <b>JDT Core Batch Compiler</b>. This jar contains the batch compiler and the javac ant adapter.</p>
-<p>Since 3.3, this jar also contains the support for jsr199 (Compiler API) and the support for jsr269 (Annotation processing). <b>In order to use the annotations
-processing support, a 1.6 VM is required.</b></p>
-<p>So it can be used as a standalone application and inside an Ant build outside of Eclipse.</p>
-<h4>Running the batch compiler</h4>
-<ul>
-<li>From the command line.
-<p><code><font color="#3366FF">java -jar org.eclipse.jdt.core_3.4.0&lt;qualifier&gt;.jar -classpath rt.jar A.java</font></code></p>
-<p>or:</p>
-<p><code><font color="#3366FF">java -jar ecj.jar -classpath rt.jar A.java</font></code></p>
-</li>
-<li>Using the static <code>compile(String commandLine, PrintWriter outWriter, PrintWriter errWriter, CompilationProgress progress)</code> method of the class BatchCompiler.
-<pre><font color="#3366FF">
-org.eclipse.jdt.compiler.CompilationProgress progress = null; // instantiate your subclass
-org.eclipse.jdt.internal.compiler.batch.BatchCompiler.compile(
-   "-classpath rt.jar A.java",
-   new PrintWriter(System.out),
-   new PrintWriter(System.err),
-   progress);
-</font></pre><p>
-You can control how progress is reported, or how the batch compiler is canceled, by subclassing the class <i>org.eclipse.jdt.compiler.CompilationProgress</i>.
-</p></li>
-</ul>
-
-<h4>Which options are available?</h4>
-<p>
-The recommended options have an orange background.
-</p>
-<p>When some options are being set multiple times, the batch compiler consumes them from left to right. When the warning option (-warn:....) is used without 
-'+' or '-', this overrides the set of warnings previously specified. So the user should make sure that such an option is given before
-any other usage of the -warn option.
-</p>
-<p>Same applies for the -err: option.</p>
-<table BORDER CELLSPACING="2" CELLPADDING="2">
-<tr>
-<th>Name</th>
-<th colspan="3">Usage</th>
-</tr>
-<tr>
-<th colspan="4">Classpath options</th>
-</tr>
-<tr>
-<td valign=top bgcolor="#FFCCAA" width="250">-bootclasspath &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top bgcolor="#FFCCAA" colspan="3">This is a list of directories or jar files used to bootstrap the class files used by the compiler. By default the libraries of the running
-VM are used. Entries are separated by the platform path separator.
-<br>Each directory or file can specify access rules for types between '[' and ']'.
-<p>If no bootclasspath is specified, the compiler will infer it using the following system properties <code>sun.boot.class.path</code>,
-<code>vm.boot.class.path</code> or <code>org.apache.harmony.boot.class.path</code> in this order respectively.</p>
-</td>
-</tr>
-<tr>
-<td valign="top" bgcolor="#FFCCAA" width="250">-cp<br>-classpath &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top bgcolor="#FFCCAA" colspan="3">This is a list of directories or jar files used to compile the source files. The default value is the value of the property "java.class.path".
- Entries are separated by the platform path separator.
-<br>Each directory or file can specify access rules for types between '[' and ']' (e.g. [-X] to forbid access to type X, [~X] to 
-discourage access to type X, [+p/X:-p/*] to forbid access to all types in package p but allow access to p/X).
-<br>The compiler follows the <code>Class-Path</code> clauses of jar files' 
-manifests recursively and appends each referenced jar file to the end of the 
-classpath, provided it is not on the classpath yet.
-</td>
-</tr>
-<tr>
-<td valign=top width="250">-extdirs &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top colspan="3">This is a list of directories used to specify the location of extension zip/jar files. Entries are separated by the platform path separator.</td>
-</tr>
-<tr>
-<td valign=top width="250">-endorseddirs &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top colspan="3">This is a list of directories used to specify the location of endorsed zip/jar files. Entries are separated by the platform path separator.</td>
-</tr>
-<tr>
-<td valign=top width="250">-sourcepath &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top colspan="3">This is a list of directories used to specify the source files. Entries are separated by the platform path separator.
-<br>Each directory can specify access rules for types between '[' and ']'.</td>
-</tr>
-<tr>
-<td valign=top bgcolor="#FFCCAA" width="250">-d &lt;dir 1&gt;|none</td>
-<td bgcolor="#FFCCAA" colspan="3">This is used to specify in which directory the generated .class files should be dumped. If it is omitted, no package directory structure is created.<br>
-If you want to generate no .class file at all, use <font color="#3366FF">-d none</font>.</td>
-</tr>
-<tr>
-<td valign=top width="250">-encoding &lt;encoding name&gt;</td>
-<td colspan="3">Specify default source encoding format (custom encoding can also be specified on a per file basis by suffixing each input source file/folder name with <font color="#3366FF">[&lt;encoding name&gt;]</font>, 
-    for example <font color="#3366FF">X.java[utf8]</font>).</td>
-</tr>
-<tr>
-<th colspan="4">Compliance options</th>
-</tr>
-<tr>
-<td valign=top width="250">-target 1.1 to 1.7 or (5, 5.0, etc)</td>
-<td colspan="3">This specifies the .class file target setting.
-The possible value are:
-<ul>
-<li><font color="#3366FF">1.1</font> (major version: 45 minor: 3)</li>
-<li><font color="#3366FF">1.2</font> (major version: 46 minor: 0)</li>
-<li><font color="#3366FF">1.3</font> (major version: 47 minor: 0)</li>
-<li><font color="#3366FF">1.4</font> (major version: 48 minor: 0)</li>
-<li><font color="#3366FF">1.5</font>, <font color="#3366FF">5</font> or <font color="#3366FF">5.0</font> (major version: 49 minor: 0)</li>
-<li><font color="#3366FF">1.6</font>, <font color="#3366FF">6</font> or <font color="#3366FF">6.0</font> (major version: 50 minor: 0)</li>
-<li><font color="#3366FF">1.7</font>, <font color="#3366FF">7</font> or <font color="#3366FF">7.0</font> (major version: 51 minor: 0)</li>
-</ul>
-Defaults are:
-<ul>
-<li><font color="#3366FF">1.1</font> in <font color="#3366FF">-1.3</font> mode</li>
-<li><font color="#3366FF">1.2</font> in <font color="#3366FF">-1.4</font> mode</li>
-<li><font color="#3366FF">1.5</font> in <font color="#3366FF">-1.5</font> mode</li>
-<li><font color="#3366FF">1.6</font> in <font color="#3366FF">-1.6</font> mode</li>
-<li><font color="#3366FF">1.7</font> in <font color="#3366FF">-1.7</font> mode</li>
-</ul>
-<p>clcd1.1 can be used to generate the StackMap attribute.</p>
-</td>
-</tr>
-<tr>
-<td valign=top>-1.3</td>
-<td colspan="3">Set compliance level to <font color="#3366FF">1.3</font>. Implicit -source 1.3 -target 1.1.</td>
-</tr>
-<tr>
-<td valign=top>-1.4</td>
-<td colspan="3">Set compliance level to <font color="#3366FF">1.4</font> (default). Implicit -source 1.3 -target 1.2.</td>
-</tr>
-<tr>
-<td valign=top>-1.5</td>
-<td colspan="3">Set compliance level to <font color="#3366FF">1.5</font>. Implicit -source 1.5 -target 1.5.</td>
-</tr>
-<tr>
-<td valign=top>-1.6</td>
-<td colspan="3">Set compliance level to <font color="#3366FF">1.6</font>. Implicit -source 1.6 -target 1.6.</td>
-</tr>
-<tr>
-<td valign=top>-1.7</td>
-<td colspan="3">Set compliance level to <font color="#3366FF">1.7</font>. Implicit -source 1.7 -target 1.7.</td>
-</tr>
-<tr>
-<td valign=top width="250">-source 1.1 to 1.7 or (5, 5.0, etc)</td>
-<td colspan="3">This is used to specify the source level expected by the compiler.<br>
-The possible value are:
-<ul>
-<li><font color="#3366FF">1.3</font></li>
-<li><font color="#3366FF">1.4</font></li>
-<li><font color="#3366FF">1.5</font>, <font color="#3366FF">5</font> or <font color="#3366FF">5.0</font></li>
-<li><font color="#3366FF">1.6</font>, <font color="#3366FF">6</font> or <font color="#3366FF">6.0</font></li>
-<li><font color="#3366FF">1.7</font>, <font color="#3366FF">7</font> or <font color="#3366FF">7.0</font></li>
-</ul>
-Defaults are:
-<ul>
-<li><font color="#3366FF">1.3</font> in <font color="#3366FF">-1.3</font> mode</li>
-<li><font color="#3366FF">1.3</font> in <font color="#3366FF">-1.4</font> mode</li>
-<li><font color="#3366FF">1.5</font> in <font color="#3366FF">-1.5</font> mode</li>
-<li><font color="#3366FF">1.6</font> in <font color="#3366FF">-1.6</font> mode</li>
-<li><font color="#3366FF">1.7</font> in <font color="#3366FF">-1.7</font> mode</li>
-</ul>
-In <font color="#3366FF">1.4</font>, <font color="#3366FF"><I>assert</I></font> is treated as a keyword. In <font color="#3366FF">1.5</font>
-and <font color="#3366FF">1.6</font>, <font color="#3366FF"><I>enum</I></font> and <font color="#3366FF"><i>assert</i></font> are treated as a keywords.</td>
-</tr>
-<tr>
-<th colspan="4">Warning options</th>
-</tr>
-<tr>
-<td valign=top>-?:warn -help:warn</td>
-<td colspan="3">Display advanced warning options</td>
-</tr>
-<tr>
-<td valign=top width="250" rowspan="66">-warn:...
-</td>
-<td valign=top colspan="3">Specify the set of enabled warnings.<br>e.g. <font color="#3366FF">-warn:unusedLocal,deprecation</font><br>
-<table>
-<tr>
-<td>-warn:none</td><td>disable all warnings</td>
-</tr>
-<tr>
-<td>-warn:&lt;warning tokens separated by ,&gt;</td><td>enable exactly the listed warnings</td>
-</tr>
-<tr>
-<td>-warn:+&lt;warning tokens separated by ,&gt;</td><td>enable additional warnings</td>
-</tr>
-<tr>
-<td>-warn:-&lt;warning tokens separated by ,&gt;</td><td>disable specific warnings</td>
-</tr>
-</table>
-</td>
-<tr>
-<th align=center width="50">Default</th>
-<th align=left width="150">Token name</th>
-<th align=left>Description</th>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>allDeadCode</td>
-<td valign=top>dead code including trivial if(DEBUG) check</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>allDeprecation</td>
-<td valign=top>deprecation even inside deprecated code</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>allJavadoc</td>
-<td valign=top>invalid or missing javadoc</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>allOver-ann</td>
-<td valign=top>all missing @Override annotations (superclass and superinterfaces)</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>assertIdentifier</td>
-<td valign=top>occurrence of <i>assert</i> used as identifier</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>boxing</td>
-<td valign=top>autoboxing conversion</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>charConcat</td>
-<td valign=top>when a char array is used in a string concatenation without being converted explicitly to a string</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>compareIdentical</td>
-<td valign=top>comparing identical expressions</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>conditionAssign</td>
-<td valign=top>possible accidental boolean assignment</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>constructorName</td>
-<td valign=top>method with constructor name</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>deadCode</td>
-<td valign=top>dead code excluding trivial if (DEBUG) check</td>
-</tr><tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>dep-ann</td>
-<td valign=top>missing @Deprecated annotation</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>deprecation</td>
-<td valign=top>usage of deprecated type or member outside deprecated code</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>discouraged</td>
-<td valign=top>use of types matching a discouraged access rule</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>emptyBlock</td>
-<td valign=top>undocumented empty block</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>enumIdentifier</td>
-<td valign=top>occurrence of <i>enum</i> used as identifier</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>enumSwitch</td>
-<td valign=top>incomplete enum switch</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>fallthrough</td>
-<td valign=top>possible fall-through case</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>fieldHiding</td>
-<td valign=top>field hiding another variable</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>finalBound</td>
-<td valign=top>type parameter with final bound</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>finally</td>
-<td valign=top>finally block not completing normally</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>forbidden</td>
-<td valign=top>use of types matching a forbidden access rule</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>hashCode</td>
-<td valign=top>missing hashCode() method when overriding equals()</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>hiding</td>
-<td valign=top>macro for fieldHiding, localHiding, typeHiding and maskedCatchBlock</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>indirectStatic</td>
-<td valign=top>indirect reference to static member</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>intfAnnotation</td>
-<td valign=top>annotation type used as super interface</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>intfNonInherited</td>
-<td valign=top>interface non-inherited method compatibility</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>intfRedundant</td>
-<td valign=top>find redundant superinterfaces</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>javadoc</td>
-<td valign=top>invalid javadoc</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>localHiding</td>
-<td valign=top>local variable hiding another variable</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>maskedCatchBlock</td>
-<td valign=top>hidden catch block</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>nls</td>
-<td valign=top>non-nls string literals (lacking of tags //$NON-NLS-&lt;n&gt;)</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>noEffectAssign</td>
-<td valign=top>assignment with no effect</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>null</td>
-<td valign=top>potential missing or redundant null check</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>nullDereference</td>
-<td valign=top>missing null check</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>over-ann</td>
-<td valign=top>missing @Override annotation (superclass only)</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>paramAssign</td>
-<td valign=top>assignment to a parameter</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>pkgDefaultMethod</td>
-<td valign=top>attempt to override package-default method</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>raw</td>
-<td valign=top>usage a of raw type (instead of a parametrized type)</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>semicolon</td>
-<td valign=top>unnecessary semicolon or empty statement</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>serial</td>
-<td valign=top>missing serialVersionUID</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>specialParamHiding</td>
-<td valign=top>constructor or setter parameter hiding another field</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>static-access</td>
-<td valign=top>macro for indirectStatic and staticReceiver</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>staticReceiver</td>
-<td valign=top>if a non static receiver is used to get a static field or call a static method</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>super</td>
-<td valign=top>overriding a method without making a super invocation</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>suppress</td>
-<td valign=top>enable @SuppressWarnings</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>syncOverride</td>
-<td valign=top>missing synchronized in synchronized method override</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>syntheticAccess</td>
-<td valign=top>when performing synthetic access for innerclass</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>tasks</td>
-<td valign=top>enable support for tasks tags in source code</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>typeHiding</td>
-<td valign=top>type parameter hiding another type</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>unchecked</td>
-<td valign=top>unchecked type operation</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>unnecessaryElse</td>
-<td valign=top>unnecessary else clause</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>unqualifiedField</td>
-<td valign=top>unqualified reference to field</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>unused</td>
-<td valign=top>macro for unusedArgument, unusedImport, unusedLabel, unusedLocal, unusedPrivate and unusedThrown</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>unusedArgument</td>
-<td valign=top>unused method argument</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>unusedImport</td>
-<td valign=top>unused import reference</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>unusedLabel</td>
-<td valign=top>unused label</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>unusedLocal</td>
-<td valign=top>unused local variable</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>unusedPrivate</td>
-<td valign=top>unused private member declaration</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>unusedThrown</td>
-<td valign=top>unused declared thrown exception</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>unusedTypeArgs</td>
-<td valign=top>unused type arguments for method</td>
-</tr>
-<tr>
-<td align=center valign=top>-</td>
-<td align=left valign=top>uselessTypeCheck</td>
-<td valign=top>unnecessary cast/instanceof operation</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>varargsCast</td>
-<td valign=top>varargs argument need explicit cast</td>
-</tr>
-<tr>
-<td align=center valign=top>+</td>
-<td align=left valign=top>warningToken</td>
-<td valign=top>unhandled warning token in @SuppressWarnings</td>
-</tr>
-<tr>
-<td valign=top>-nowarn</td>
-<td colspan="3">No warning (equivalent to <font color="#3366FF">-warn:none</font>)</td>
-</tr>
-<tr>
-<td valign=top width="250">-err:...
-</td>
-<td valign=top colspan="3">Specify the set of enabled warnings that are converted to errors.
-<br>e.g. <font color="#3366FF">-err:unusedLocal,deprecation</font><br>
-unusedLocal and deprecation warnings will be converted to errors. All other warnings are still reported as warnings.
-<table>
-<tr>
-<td>-err:&lt;warning tokens separated by ,&gt;</td><td>convert exactly the listed warnings to errors</td>
-</tr>
-<tr>
-<td>-err:+&lt;warning tokens separated by ,&gt;</td><td>convert additional warnings to errors</td>
-</tr>
-<tr>
-<td>-err:-&lt;warning tokens separated by ,&gt;</td><td>remove specific warnings from being converted to errors</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td valign=top>-deprecation</td>
-<td colspan="3">Equivalent to <font color="#3366FF">-warn:+deprecation</font>.</td>
-</tr>
-<tr>
-<th colspan="4">Debug options</th>
-</tr>
-<tr>
-<td valign=top>-g[:none|:lines,vars,source]
-</td>
-<td colspan="3">Set the debug attributes level<br>
-<table>
-<tr>
-<th align=left>-g</th>
-<td colspan="3">All debug info (equivalent to <font color="#3366FF">-g:lines,vars,source</font>)
-</td>
-</tr>
-<tr>
-<th align=left>-g:none</th>
-<td colspan="3">No debug info</td>
-</tr>
-<tr>
-<th align=left>-g:[lines,vars,source]</th>
-<td colspan="3">Selective debug info</td>
-</tr>
-</table>
-</td>
-</tr>
-<tr>
-<td valign=top>-preserveAllLocals</td>
-<td colspan="3">Explicitly request the compiler to preserve all local variables (for debug purpose). If omitted, the compiler will remove unused locals.</td>
-</tr>
-<tr>
-<th colspan="4">Annotation processing options (require a 1.6 VM or above and are used only if the compliance is 1.6)</th>
-</tr>
-<tr>
-<td>-Akey[=value]</td>
-<td valign=top colspan="3">Annotation processors options that are passed to annotation processors. <code>key</code> is made of identifiers separated by dots</td>
-</tr>
-<tr>
-<td>-proc:[only|none]</td>
-<td valign=top colspan="3">If <code>-proc:only</code> is specified, the annotation processors will run but
-no compilation will be performed. If <code>-proc:none</code> is specified, annotation processors
-will not be discovered or run; compilation will proceed as if no annotation processors
-were found. By default the compiler must search the classpath for annotation
-processors, so specifying <code>-proc:none</code> may speed compilation if annotation processing is
-not required.</td>
-</tr>
-<tr>
-<td>-processor &lt;class1[,class2,...]&gt;</td>
-<td valign=top colspan="3">Qualified class names of annotation processors to run. If specified, the normal
-<a href="http://java.sun.com/javase/6/docs/api/javax/annotation/processing/Processor.html">
-processor discovery process</a> will be skipped.</td>
-</tr>
-<tr>
-<td>-processorpath &lt;dir&nbsp;1&gt;;&lt;dir&nbsp;2&gt;;...;&lt;dir&nbsp;P&gt;</td>
-<td valign=top colspan="3">A list of directories or jar files which will be searched for annotation processors. 
-Entries are separated by the platform path separator. If not specified, the classpath will be searched instead.</td>
-</tr>
-<tr>
-<td>-s &lt;dir&gt;</td>
-<td valign=top colspan="3">The directory where generated source files will be created.</td>
-</tr>
-<tr>
-<td>-XprintProcessorInfo</td>
-<td valign=top colspan="3">Print information about which annotations and which elements a processor is asked to process</td>
-</tr>
-<tr>
-<td>-XprintRounds</td>
-<td valign=top colspan="3">Print information about annotation processing rounds</td>
-</tr>
-<tr>
-<td>-classNames &lt;class1[,class2,...]&gt;</td>
-<td valign=top colspan="3">Qualified names of binary types that need to be processed</td>
-</tr>
-<tr>
-<th colspan="4">Ignored options (for compatibility with javac options)</th>
-</tr>
-<tr>
-<td>-J&lt;option&gt;</td>
-<td valign=top colspan="3">Pass option to the virtual machine</td>
-</tr>
-<tr>
-<td>-X&lt;option&gt;</td>
-<td valign=top colspan="3">Specify non-standard option. -Xemacs is not ignored.</td>
-</tr>
-<tr>
-<td>-X</td>
-<td valign=top colspan="3">Print non-standard options and exit</td>
-</tr>
-<tr>
-<td>-O</td>
-<td valign=top colspan="3">Optimize for execution time</td>
-</tr>
-<tr>
-<th colspan="4">Advanced options</th>
-</tr>
-<tr>
-<td>@&lt;file&gt;</td>
-<td valign=top colspan="3">Read command-line arguments from file</td>
-</tr>
-<tr>
-<td>-maxProblems&nbsp;&lt;n&gt;</td>
-<td valign=top colspan="3">Max number of problems per compilation unit (100 by default)</td>
-</tr>
-<tr>
-<td valign=top>-log &lt;filename&gt;</td>
-<td colspan="3">Specify a log file in which all output from the compiler will be dumped. This is really useful if you want to debug the batch
-compiler or get a file which contains all errors and warnings from a batch build. If the extension is <b>.xml</b>, the generated log
-will be an xml file.
-</td>
-</tr>
-<tr>
-<td valign=top>-Xemacs</td>
-<td colspan="3">Use emacs style to present errors and warnings locations into the console
-    and regular text logs. XML logs are unaffected by this option. With this option
-    active, the message:
-    <br><code><font color="#3366FF">
-2. WARNING in /workspace/X.java<br>
- (at line 8)...</font></code><br>is presented as:
-    <br><code><font color="#3366FF">
-/workspace/X.java:8: warning: The method...</font></code></td>
-</tr>
-<tr>
-<td valign=top>-proceedOnError</td>
-<td colspan="3">Keep compiling in spite of errors, dumping class files with problem methods or problem types. This is recommended only if you want
-to be able to run your application even if you have remaining errors.</td>
-</tr>
-<tr>
-<td valign=top>-verbose</td>
-<td colspan="3">Print accessed/processed compilation units in the console or the log file if specified.</td>
-</tr>
-<tr>
-<td valign=top>-referenceInfo</td>
-<td colspan="3">Compute reference info. This is useful only if connected to the builder. The reference infos are useless otherwise.</td>
-</tr>
-<tr>
-<td valign=top>-progress</td>
-<td colspan="3">Show progress (only in -log mode).</td>
-</tr>
-<tr>
-<td valign=top>-time
-</td>
-<td colspan="3">Display speed information.</td>
-</tr>
-<tr>
-<td valign=top>-noExit</td>
-<td colspan="3">Do not call <font color="#3366FF">System.exit(n)</font> at end of compilation (<font color="#3366FF">n=0</font> if no error).</td>
-</tr>
-<tr>
-<td valign=top>-repeat &lt;n&gt;
-</td>
-<td colspan="3">Repeat compilation process <font color="#3366FF">&lt;n&gt;</font> times (perf analysis).</td>
-</tr>
-<tr>
-<td valign=top>-inlineJSR</td>
-<td colspan="3">Inline JSR bytecode (implicit if target &gt;= 1.5).</td>
-</tr>
-<tr>
-<td valign=top>-enableJavadoc</td>
-<td colspan="3">Consider references inside javadoc.</td>
-</tr>
-<tr>
-<th colspan="4">Helping options</th>
-</tr>
-<tr>
-<td>-? -help</td>
-<td valign=top colspan="3">Display the help message.</td>
-</tr>
-<tr>
-<td valign=top>-v -version</td>
-<td colspan="3">Display the build number of the compiler. This is very useful to report a bug.</td>
-</tr>
-<tr>
-<td valign=top>-showversion</td>
-<td colspan="3">Display the build number of the compiler and continue. This is very useful to report a bug.</td>
-</tr>
-</table>
-<h4>Examples</h4>
-<table>
-<tr>
-<td valign=top><code><font color="#3366FF">d:\temp -classpath rt.jar -time -g -d d:/tmp</font></code>
-</td>
-<td valign=top>It compiles all source files in d:\temp and its subfolders. The classpath is simply rt.jar. It generates all debug
-attributes and all generated .class files are dumped in d:\tmp. The speed of the compiler will be displayed once the batch process
-is completed.</td>
-</tr>
-<tr>
-<td valign=top><code><font color="#3366FF">d:\temp\Test.java -classpath d:\temp;rt.jar -g:none</font></code>
-</td>
-<td valign=top>It compiles only Test.java and its dependant files if any, retrieving dependant files from d:\temp. The classpath is d:\temp followed by rt.jar, which means that all necessary classes
-are searched first in d:\temp and then in rt.jar. It generates no debug attributes and all generated .class files are dumped in d:\temp.</td>
-</tr>
-</table>
-<h3>Using the ant javac adapter</h3>
-<p>The Eclipse compiler can be used inside an Ant buildfile using the javac adapter. 
-In order to use the Eclipse compiler, you simply need to define the <b>build.compiler</b>
- property in your buildfile.</p>
-<p>In order to get the batch compiler working in an ant buildfile, the ant runtime classpath needs to contain the 
-Eclipse batch compiler. When you run your ant buildfile:</p>
-<ol>
-<li>outside of Eclipse: the easiest way to set up the ant runtime classpath is to add the <code>ecj.jar</code> file using the <code>-lib</code>
-argument or dumping it inside the <code>ANT_HOME</code> location.</li>
-<li>inside Eclipse using the same JRE than Eclipse: the Eclipse batch compiler is implicitely added to the ant runtime
-classpath.</li>
-<li>inside Eclipse using the different JRE: the Eclipse batch compiler must be explicitely added to the ant runtime classpath.
-This can be done using the <code>ecj.jar</code> file or using the org.eclipse.jdt.core jar file and the <code>jdtCompilerAdapter.jar</code> file located inside the
-org.eclipse.jdt.core jar file (this jar file needs to be extracted first).</li>
-</ol>
-<p>Here is a small example:</p>
-<pre><font color="#4444cc">
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;project name=&quot;compile&quot; default=&quot;main&quot; basedir=&quot;../.&quot;&gt;
-
-	<b>&lt;property name=&quot;build.compiler&quot; value=&quot;org.eclipse.jdt.core.JDTCompilerAdapter&quot;/&gt;</b>
-
-	&lt;property name=&quot;root&quot; value=&quot;${basedir}/src&quot;/&gt;
-
-	&lt;property name=&quot;destdir&quot; value=&quot;d:/temp/bin&quot; /&gt;
-
-	&lt;target name=&quot;main&quot;&gt;
-		&lt;javac srcdir=&quot;${root}&quot; destdir=&quot;${destdir}&quot; debug=&quot;on&quot; nowarn=&quot;on&quot; extdirs=&quot;d:/extdirs&quot; source=&quot;1.4&quot;&gt;
-		    &lt;classpath&gt;
-		      &lt;pathelement location=&quot;${basedir}/../org.eclipse.jdt.core/bin&quot;/&gt;
-		    &lt;/classpath&gt;
-		&lt;/javac&gt;
-	&lt;/target&gt;
-&lt;/project&gt;
-</font>
-</pre><p>The syntax used for the javac Ant task can be found in the <a href="http://ant.apache.org/manual/CoreTasks/javac.html">
- Ant javac task documentation</a>. The current adapter supports the Javac Ant task 1.4.1 up to 1.6.5 versions.</p>
-<p>If you are using a version above 1.5.0, you can use the nested compiler argument element (<code>&lt;compilerarg&gt;</code>) to specify compiler
-specific options.
-</p>
-<pre><font color="#4444cc">
-...
-&lt;javac srcdir=&quot;${root}&quot; destdir=&quot;${destdir}&quot; debug=&quot;on&quot; nowarn=&quot;on&quot; extdirs=&quot;d:/extdirs&quot; source=&quot;1.4&quot;&gt;
-    &lt;classpath&gt;
-      &lt;pathelement location=&quot;${basedir}/../org.eclipse.jdt.core/bin&quot;/&gt;
-    &lt;/classpath&gt;
-    &lt;compilerarg</font> <font color="red">compiler=&quot;org.eclipse.jdt.core.JDTCompilerAdapter&quot;</font> <font color="#4444cc">line=&quot;-1.5 -warn:+boxing&quot;/&gt;
-&lt;/javac&gt;
-...
-</font>
-</pre>
-<b>Note:</b>
-<ol>
-<li>To prevent compiler dependant buildfiles, we <u>strongly</u> advise you to use a <code>&lt;compilerarg&gt;</code> whose "compiler" attribute value is <code>org.eclipse.jdt.core.JDTCompilerAdapter</code>.
-If this is not set, the buildfile can only be used with the Eclipse compiler. If set, the nested compiler argument is ignored if the name is different from the 
-compiler name specified by the <code>build.compiler</code> property.</li>
-<li><code>&lt;compilerarg&gt;</code> should not be used to set values like target value, source value, debug options, or any options that could be set using the
-defined attributes of the <code>javac</code> ant task. Its usage must be reserved to pass
-compiler specific options like warning options. When a command-line argument is specified more than once, the Eclipse batch compiler can report errors like:
-<pre>duplicate target compliance setting specification: 1.5</pre>
-</li>
-</ol>
-<h3> Problem determination</h3>
-<p> JDT Core defines a specialized marker (marker type "<b>org.eclipse.jdt.core.problem</b>
-  ") to denote compilation problems. To programmatically discover problems
- detected by the compiler, the standard platform marker protocol should be
- used. See <a href="../../org.eclipse.platform.doc.isv/guide/resAdv_markers.htm" class="XRef">
- Resource Markers</a>
-  for an overview of using markers.</p>
-<p> The following snippet finds all Java problem markers in a compilation 
-unit.</p>
-<pre><font color="#4444cc">
-   public IMarker[] findJavaProblemMarkers(ICompilationUnit cu) 
-      throws CoreException {
-      IResource javaSourceFile = cu.getUnderlyingResource();
-      IMarker[] markers = 
-         javaSourceFile.findMarkers(IJavaModelMarker.JAVA_MODEL_PROBLEM_MARKER,
-            true, IResource.DEPTH_INFINITE);
-   }
-</font>
-</pre><p> Java problem markers are maintained by the Java project builder and are 
-removed automatically as problems are resolved and the Java source is recompiled.</p>
-<p>The problem id value is set to one of the constants defined in <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IProblem.html">
- IProblem</a>
-</b>. The problem's id is reliable, but the message is localized and therefore 
-can be changed according to the default locale. The constants defined in <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IProblem.html">
- IProblem</a>
-</b> are self-descriptive. </p>
-<p>An implementation of <b><a href="../reference/api/org/eclipse/jdt/core/IProblemRequestor.html">
- IProblemRequestor</a>
-</b> should be defined to collect the problems discovered during a Java operation. 
-  Working copies can be reconciled with problem detection if a <b><a href="../reference/api/org/eclipse/jdt/core/IProblemRequestor.html">
- IProblemRequestor</a>
-</b> has been supplied for the working copy creation. To achieve this, you 
-can use the <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">
- reconcile</a></b> method. Here is an example:</p>
-<pre><font color="#4444cc">
-  ICompilationUnit unit = ..; // get some compilation unit
-			
-  // create requestor for accumulating discovered problems
-  IProblemRequestor problemRequestor = new IProblemRequestor() {
-    public void acceptProblem(IProblem problem) {
-      System.out.println(problem.getID() + &quot;: &quot; + problem.getMessage());
-    }
-    public void beginReporting() {}
-    public void endReporting() {}
-    public boolean isActive() {	return true; } // will detect problems if active
-  };
-    
-  // use working copy to hold source with error
-  ICompilationUnit workingCopy = unit.getWorkingCopy(new WorkingCopyOwner() {}, problemRequestor, null);
-  ((IOpenable)workingCopy).getBuffer().setContents(&quot;public class X extends Zork {}&quot;);
-
-  // trigger reconciliation			
-  workingCopy.reconcile(NO_AST, true, null, null);
-</font></pre>
-<p>You can add an action on the reported problems in the acceptProblem(IProblem) 
-method. In this example, the reported problem will be that <b>Zork cannot 
-be resolved or is not a valid superclass</b> and its id is <b>IProblem.SuperclassNotFound</b>.
-</p>
-<h3>Excluding warnings using <code>SuppressWarnings</code></h3>
-<p>Java 5.0 offers the option to the user to disable compilation warnings relative to a subset of a compilation unit using
-the annotation <code>java.lang.SuppressWarning</code>.</p>
-<pre>
-	@SuppressWarning("unused") public void foo() {
-		String s;
-	}
-</pre>
-<p>Without the annotation, the compiler would complain that the local variable <code>s</code> is never used.
-With the annotation, the compiler silently ignores this warning locally to the <code>foo</code> method. This enables to
-keep the warnings in other locations of the same compilation unit or the same project.</p>
-<p>The list of tokens that can be used inside an <code>SuppressWarning</code> annotation is:</p>
-<!-- cross-checked with the code for 3.2 RC4 by maxime 20060517 -->
-<ul>
-<li><font color="green">all</font> to suppress all warnings</li>
-<li><font color="green">boxing</font> to suppress warnings relative to boxing/unboxing operations</li>
-<li><font color="green">cast</font> to suppress warnings relative to cast operations</li>
-<li><font color="green">dep-ann</font> to suppress warnings relative to deprecated annotation</li>
-<li><font color="green">deprecation</font> to suppress warnings relative to deprecation</li>
-<li><font color="green">fallthrough</font> to suppress warnings relative to missing breaks in switch statements</li>
-<li><font color="green">finally</font> to suppress warnings relative to finally block that don't return</li>
-<li><font color="green">hiding</font> to suppress warnings relative to locals that hide variable</li>
-<li><font color="green">incomplete-switch</font> to suppress warnings relative to missing entries in a switch statement (enum case)</li>
-<li><font color="green">nls</font> to suppress warnings relative to non-nls string literals</li>
-<li><font color="green">null</font> to suppress warnings relative to null analysis</li>
-<li><font color="green">raw</font> to suppress warnings relative to usage of raw types</li>
-<li><font color="green">restriction</font> to suppress warnings relative to usage of discouraged or forbidden references</li>
-<li><font color="green">serial</font> to suppress warnings relative to missing serialVersionUID field for a serializable class</li>
-<li><font color="green">static-access</font> to suppress warnings relative to incorrect static access</li>
-<li><font color="green">super</font> to suppress warnings relative to overriding a method without super invocations</li>
-<li><font color="green">synthetic-access</font> to suppress warnings relative to unoptimized access from inner classes</li>
-<li><font color="green">unchecked</font> to suppress warnings relative to unchecked operations</li>
-<li><font color="green">unqualified-field-access</font> to suppress warnings relative to field access unqualified</li>
-<li><font color="green">unused</font> to suppress warnings relative to unused code and dead code</li>
-</ul>
-</body>
-</html>
-
-

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_contributing_a_cleanup.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_contributing_a_cleanup.htm
deleted file mode 100644
index 3c3f9a8..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_contributing_a_cleanup.htm
+++ /dev/null

@@ -1,133 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Contributing a simple clean up and a simple save action using the org.eclipse.jdt.ui.cleanUps extension point</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2> Contributing a clean up and a save action using the <b>clean up</b> extension point</h2>
-<p>The <a href="../reference/extension-points/org_eclipse_jdt_ui_cleanUps.html"><b>org.eclipse.jdt.ui.cleanUps</b></a> extension point enables you to contribute your own Java code clean ups and Java editor save actions.
-Clean ups help in resolving problems in a compilation unit or establishing a code style. A save action is a special clean up that perform the requested modifications on save automatically.
-</p>
-<h3> Using the extension point</h3>
-<p>To create a new extension for the <a href="../reference/extension-points/org_eclipse_jdt_ui_cleanUps.html"><b>org.eclipse.jdt.ui.cleanUps</b></a> extension point
-you need to first provide the required extensions in the plugin.xml. There are 3 extensions that need to be declared as shown below with the example of a clean up
-which updates the copyrights for a file on save: </p>
-
-<pre>
-   &lt;extension
-         point=&quot;org.eclipse.jdt.ui.cleanUps&quot;&gt;
-      &lt;cleanUp
-            id=&quot;org.eclipse.jdt.copyrightsaveaction.copyright_clean_up&quot;
-            class=&quot;org.eclipse.jdt.ui.internal.copyrightupdater.CopyrightUpdaterCleanUp&quot;&gt;
-      &lt;/cleanUp&gt;
-      
-      &lt;cleanUpOptionsInitializer
-            class=&quot;org.eclipse.jdt.ui.internal.copyrightupdater.CopyrightOnSaveOptionsInitializer&quot;
-            cleanUpKind=&quot;saveAction&quot;&gt;
-      &lt;/cleanUpOptionsInitializer&gt;
-      
-      &lt;cleanUpConfigurationUI
-            class=&quot;org.eclipse.jdt.ui.internal.copyrightupdater.CopyrightTabPage&quot;
-            name=&quot;%cleanUpConfigurationUI.name&quot;
-            cleanUpKind=&quot;saveAction&quot;&gt;
-      &lt;/cleanUpConfigurationUI&gt;
-   &lt;/extension&gt;
-</pre>
-
-<p>
-For a description of the individual attributes, please refer to the extension point documentation.
-</p>
-
-<h3>Contributing a clean up</h3>
-<p>To contribute a clean up, you need to first create the class that implements the <a href="../reference/api/org/eclipse/jdt/ui/cleanup/ICleanUp.html"><b>ICleanUp</b></a> Interface. 
-Lets create the <code>CopyrightUpdaterCleanUp</code> class for our example clean up and implement the inherited methods:</p>
-<pre><font color="#4444cc">	public class CopyrightUpdaterCleanUp implements ICleanUp {
-	
-		private CleanUpOptions fOptions;
-		private RefactoringStatus fStatus;
-
-		public CopyrightUpdaterCleanUp() {
-		
-		}</font></pre>
-
-The <code>CleanUpRequirements</code> contain various requirements for the clean up such as an AST or a fresh AST containing changes from other clean ups, compiler options and changed 
-regions, which are used by the <code>CleanUpContext</code> to create the fix. It has to be returned from the method getRequirements(): 
-<pre><font color="#4444cc">		public CleanUpRequirements getRequirements() {
-			boolean changedRegionsRequired= false;
-			Map compilerOptions= null;
-			boolean isUpdateCopyrights= fOptions.isEnabled("cleanup.update_copyrights");//$NON-NLS-1$
-			return new CleanUpRequirements(isUpdateCopyrights, isUpdateCopyrights, changedRegionsRequired, compilerOptions);	    
-		}</font></pre>
-
-A human readable description should be returned for each step of the clean up that is enabled in the current options:
-<pre><font color="#4444cc">		public String[] getStepDescriptions() {
-			if (fOptions.isEnabled("cleanup.update_copyrights"))//$NON-NLS-1$
-				return new String[] {"Update Copyrights"};//$NON-NLS-1$
-
-			return null;
-		}</font></pre>
-
-The CleanUpOptions for the supported options keys will be set using setOptions(...):
-<pre><font color="#4444cc">		public void setOptions(CleanUpOptions options) {
-			Assert.isLegal(options != null);
-			Assert.isTrue(fOptions == null);
-			fOptions= options;		
-		}</font></pre>
-
-The clean up pre-conditions and post-conditions are being checked in checkPreConditions(...) and checkPostConditions(...):
-<pre><font color="#4444cc">		public RefactoringStatus checkPreConditions(IJavaProject project, ICompilationUnit[] compilationUnits, IProgressMonitor monitor) throws CoreException {
-			if (fOptions.isEnabled("cleanup.update_copyrights")) { //$NON-NLS-1$
-				fStatus= new RefactoringStatus();
-			}
-			return new RefactoringStatus();
-		}</font></pre>
-
-<pre><font color="#4444cc">		public RefactoringStatus checkPostConditions(IProgressMonitor monitor) throws CoreException {
-			try {
-				if (fStatus == null || fStatus.isOK()) {
-					return new RefactoringStatus();
-				} else {
-					return fStatus;
-				}
-			} finally {
-				fStatus= null;
-			}
-		}</font></pre>
-
-Finally, a <a href="../reference/api/org/eclipse/jdt/ui/cleanup/ICleanUpFix.html"><b>ICleanUpFix</b></a> is to be created which fixes all the problems for the given context using createFix(...)
-<pre><font color="#4444cc">		public ICleanUpFix createFix(CleanUpContext context) throws CoreException {
-			CompilationUnit compilationUnit= context.getAST();
-			if (compilationUnit == null)
-				return null;
-
-			return CopyrightsFix.createCleanUp(compilationUnit, fOptions.isEnabled("cleanup.update_copyrights"));//$NON-NLS-1$
-		}</font></pre> 
-
-<h3>Contributing a clean up options provider</h3>
-<p>To create the UI for the clean up, an options provider tab page has to be created by implementing the <a href="../reference/api/org/eclipse/jdt/ui/cleanup/ICleanUpConfigurationUI.html"><b>ICleanUpConfigurationUI</b></a> interface.
-The page can be created by implementing the createContents(...) method in the <code>CopyrightTabPage</code> class. The preferences page along with the desired groups and options can be 
-created using the method doCreatePreferences().
-Optionally, a code snippet of the new clean up with the given options can be shown in the clean up preview tab using the method getPreview(). If the CleanUpOptions get modified in the UI,
- they need to be set again using the method setOptions(...).
-
-<h3> Contributing a clean up options initializer</h3>
-<p>A clean up options initializer, which returns the default options for each clean up kind can be created by implementing the <a href="../reference/api/org/eclipse/jdt/ui/cleanup/ICleanUpOptionsInitializer.html"><b>ICleanUpOptionsInitializer</b></a>.
-The options initializer can either be contributed for a normal code clean up or for a save action.
-<pre><font color="#4444cc">	public class CopyrightOnSaveOptionsInitializer implements ICleanUpOptionsInitializer {
-
-		public CopyrightOnSaveOptionsInitializer() {		
-		}</font></pre>
-
-The default options for this initializer can be set in setDefaultOptions(...)
-<pre><font color="#4444cc">		public void setDefaultOptions(CleanUpOptions options) {
-			options.setOption("cleanup.update_copyrights", CleanUpOptions.TRUE);
-		}
-	}</font></pre>
-<p> The UI code to configure the options for this example can be found here: <a href="CopyrightTabPage.html"><b>CleanUpTabPage.java</b></a>.
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm
deleted file mode 100644
index ff8cb5a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_editors.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Customizing Java editors</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2> Customizing Java editors</h2>
-<p>The JDT tools implement a fully-functioning Java editor.&nbsp; They also
-define API so you can assign Java text editing features to your own editors or
-enhance the Java editor with your plug-in specific features.</p>
-<h3> Java text editing</h3>
-<p><a href="../reference/api/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.html"><b>JavaSourceViewerConfiguration</b></a>
-describes the configuration for a viewer that displays Java code.&nbsp; Given a
-source code viewer, this class provides access to the instances of the utility
-classes that add Java specific behavior to the viewer, such as coloring,
-scanning of tokens, content assist, etc.</p>
-<h3> Java text hovers</h3>
-<p>When you implement a plug-in that provides additional capabilities associated
-with Java code, you may want to implement new hover behavior in the editor, so
-that information about your model elements will be shown as the user hovers over
-Java code.&nbsp; For example, the debugger uses a customized hover to show
-variable values when the user hovers over variable names in the editor.</p>
-<p>The extension point <a href="../reference/extension-points/org_eclipse_jdt_ui_javaEditorTextHovers.html"> 
-    <b> 
-    org.eclipse.jdt.ui.javaEditorTextHovers</b></a>  allows you to register your
-own hover implementation.&nbsp; You are responsible for implementing the <a href="../reference/api/org/eclipse/jdt/ui/text/java/hover/IJavaEditorTextHover.html"><b>IJavaEditorTextHover</b></a> 
-and registering your implementation class in the extension definition.&nbsp; You
-also provide a label for your hover type so that the user can enable and disable
-the different types of hovers from the editor preferences page.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm
deleted file mode 100644
index b8fb704..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_junit.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<!-- Benjamin Muskalla <b.muskalla@gmx.net> - Typo in JUnit ISV doc - https://bugs.eclipse.org/bugs/show_bug.cgi?id=248935 -->
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Observing JUnit test runs</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Observing JUnit test runs</h2>
-<p>The JDT JUnit plug-in lets you listen to test runs. To observe test runs, register your listener with
-<a href="../reference/api/org/eclipse/jdt/junit/JUnitCore.html#addTestRunListener(org.eclipse.jdt.junit.TestRunListener)">JUnitCore.addTestRunListener(TestRunListener)</a>.
-</p>
-<p>The listener will report all sessions and test cases started.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm
deleted file mode 100644
index 518396d..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_manip.htm
+++ /dev/null

@@ -1,539 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Manipulating Java code</title>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY>
-<h2>Manipulating Java code</h2>
-<P>
-Your plug-in can use the JDT API to create classes or interfaces, add methods to existing types, or alter the methods for types. </P>
-<P>
-The simplest way to alter Java objects is to use the Java element API. More general techniques can be used to work with the raw source code for a Java element.</P>
-
-<H3>
-Code modification using Java elements</h3>
-
-<H4>
-Generating a compilation unit
-</h4>
-<P>
-The easiest way to programmatically generate a compilation unit is to use 
-<b><a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html#createCompilationUnit(java.lang.String, java.lang.String, boolean, org.eclipse.core.runtime.IProgressMonitor)">IPackageFragment.createCompilationUnit</a></b>. 
-You specify the name and contents of the compilation unit. The compilation unit is created inside the package and the new
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"> ICompilationUnit</a></b> is returned. </P>
-<P>
-A compilation unit can be created generically by creating a file resource whose extension is &quot;<b>.java&quot;</b> in the appropriate folder that corresponds to the package directory. Using the generic resource API is a back door to the Java tooling, so the Java model is not updated until the generic resource change listeners are
-notified and the JDT listeners update the Java model with the new compilation unit.</P>
-
-
-<H4>
-Modifying a compilation unit
-</h4>
-<P>
-Most simple modifications of Java source can be done using the Java element API.</P>
-<P>
-For example, you can query a type from a compilation unit. Once you have the <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b>IType</b></a>, you can use protocols such as
-<a href="../reference/api/org/eclipse/jdt/core/IType.html#createField(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>createField</b></a>, 
-<a href="../reference/api/org/eclipse/jdt/core/IType.html#createInitializer(java.lang.String, org.eclipse.jdt.core.IJavaElement, org.eclipse.core.runtime.IProgressMonitor)"><b>createInitializer</b></a>,
-<a href="../reference/api/org/eclipse/jdt/core/IType.html#createMethod(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>createMethod</b></a>, 
-or <a href="../reference/api/org/eclipse/jdt/core/IType.html#createType(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>createType</b></a> 
-to add source code members to the type. The source code and information about the location of the member is supplied in these methods.</P>
-<P>
-The <b><a href="../reference/api/org/eclipse/jdt/core/ISourceManipulation.html"> ISourceManipulation</a></b> interface defines common source manipulations for Java elements. This includes methods for renaming, moving, copying, or deleting a type's member. </P>
-
-
-<H4>
-Working copies
-</h4>
-<P>
-Code can be modified by manipulating the compilation unit (and thus the underlying 
-<a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a> is modified) or
-one can modify an in-memory copy of the compilation unit called a working copy. </P>
-<P>
-A working copy is obtained from a compilation unit using the 
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#getWorkingCopy(org.eclipse.core.runtime.IProgressMonitor)">getWorkingCopy</a></b>
-method. (Note that the compilation unit does not need to exist in the Java model
-in order for a working copy to be created.)&nbsp; Whoever creates such a working copy is responsible for discarding it when not needed any longer using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#discardWorkingCopy()">discardWorkingCopy</a></b>
-method. </P>
-<P>
-Working copies modify an in-memory buffer. The <b>getWorkingCopy()</b> method creates a default buffer, but
-clients can provide their own buffer implementation using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ITypeRoot.html#getWorkingCopy(org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">getWorkingCopy(WorkingCopyOwner, IProgressMonitor)</a></b>
-method. Clients can manipulate the text of this buffer directly. If they do so, they must synchronize the working copy with
-the buffer from time to time using either the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">reconcile(int, boolean, WorkingCopyOwner, IProgressMonitor)</a></b>
-method.  </P>
-<P>
-Finally a working copy can be saved to disk (replacing the original compilation unit) using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#commitWorkingCopy(boolean, org.eclipse.core.runtime.IProgressMonitor)">commitWorkingCopy</a></b>
-method.&nbsp;&nbsp; </P>
-<P>
-For example the following code snippet creates a working copy on a compilation unit using a custom working copy owner. The snippet
-modifies the buffer, reconciles the changes, commits the changes to disk and finally discards the working copy. </P>
-<pre>
-<font color='#4444CC'>
-    // Get original compilation unit
-    ICompilationUnit originalUnit = ...;
-    
-    // Get working copy owner
-    WorkingCopyOwner owner = ...;
-    
-    // Create working copy
-    ICompilationUnit workingCopy = originalUnit.getWorkingCopy(owner, null);
-    
-    // Modify buffer and reconcile
-    IBuffer buffer = ((IOpenable)workingCopy).getBuffer();
-    buffer.append(&quot;class X {}&quot;);
-    workingCopy.reconcile(ICompilationUnit.NO_AST, false, null, null);
-    
-    // Commit changes
-    workingCopy.commitWorkingCopy(false, null);
-    
-    // Destroy working copy
-    workingCopy.discardWorkingCopy();
-</font>
-</pre>
-<P>
-The compilation unit's buffer can also be modified using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#applyTextEdit(org.eclipse.text.edits.TextEdit, org.eclipse.core.runtime.IProgressMonitor)">ICompilationUnit.applyTextEdit</a></b>
-method.</P>
-<pre>
-<font color='#4444CC'>
-    // Get original compilation unit
-    ICompilationUnit originalUnit = ...;
-    
-    // Get working copy owner
-    WorkingCopyOwner owner = ...;
-    
-    // Create working copy
-    ICompilationUnit workingCopy = originalUnit.getWorkingCopy(owner, null);
-    
-    // Get text edits
-    TextEdit edit = ...;
-    
-    // Modify buffer and reconcile
-    workingCopy.applyTextEdit(edit, null);
-    workingCopy.reconcile(ICompilationUnit.NO_AST, false, null, null);
-    
-    // Commit changes
-    workingCopy.commitWorkingCopy(false, null);
-    
-    // Destroy working copy
-    workingCopy.discardWorkingCopy();
-</font>
-</pre>
-<P>
-Working copies can also be shared by several clients using a working copy owner. A working copy can be later retrieved using the
-<b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#findWorkingCopy(org.eclipse.jdt.core.WorkingCopyOwner)">findWorkingCopy</a></b>
-method. A shared working copy is thus keyed on the original compilation unit and on a working copy owner.</P>
-<P>
-The following shows how client 1 creates a shared working copy, client 2 retrieves this working copy, client 1 discards the
-working copy, and client 2 trying to retrieve the shared working copy notices it does not exist any longer: </P>
-<pre>
-<font color='#4444CC'>
-    // Client 1 &amp; 2: Get original compilation unit
-    ICompilationUnit originalUnit = ...;
-    
-    // Client 1 &amp; 2: Get working copy owner
-    WorkingCopyOwner owner = ...;
-    
-    // Client 1: Create shared working copy
-    ICompilationUnit workingCopyForClient1 = originalUnit.getWorkingCopy(owner, null);
-    
-    // Client 2: Retrieve shared working copy
-    ICompilationUnit workingCopyForClient2 = originalUnit.findWorkingCopy(owner);
-     
-    // This is the same working copy
-    assert workingCopyForClient1 == workingCopyForClient2;
-    
-    // Client 1: Discard shared working copy
-    workingCopyForClient1.discardWorkingCopy();
-    
-    // Client 2: Attempt to retrieve shared working copy and find out it's null
-    workingCopyForClient2 = originalUnit.findWorkingCopy(owner);
-    assert workingCopyForClient2 == null;
-</font>
-</pre>
-<H3>Code modification using the DOM/AST API</h3>
-
-
-There are three ways to create a <b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html">CompilationUnit</a></b>.
-The first one is to use <b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html">ASTParser</a></b>.
-The second is to use <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">ICompilationUnit#reconcile(...)</a></b>.
-The third is to start from scratch using the factory methods on <b><a href="../reference/api/org/eclipse/jdt/core/dom/AST.html">AST</a></b> (Abstract Syntax Tree).
-
-<h4>
-Creating an AST from existing source code
-</h4>
-
-An instance of <b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html">ASTParser</a></b> must be created with <b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#newParser(int)">ASTParser.newParser(int)</a></b>.<br>
-<br>
-The source code is given to the <b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html">ASTParser</a></b> with one of the following methods:
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setSource(char[])">setSource(char[])</a></b>: to create the AST from source code</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setSource(org.eclipse.jdt.core.IClassFile)">setSource(IClassFile)</a></b>: to create the AST from a classfile</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setSource(org.eclipse.jdt.core.ICompilationUnit)">setSource(ICompilationUnit)</a></b>: to create the AST from a compilation unit</li>
-</ul>
-
-Then the AST is created by calling
-<b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#createAST(org.eclipse.core.runtime.IProgressMonitor)">createAST(IProgressMonitor)</a></b>.<br>
-<br>
-The result is an AST with correct source positions for each node.
-The resolution of bindings has to be requested before the creation of the tree with
-<b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setResolveBindings(boolean)">setResolveBindings(boolean)</a></b>.
-Resolving the bindings is a costly operation and should be done only when necessary.
-As soon as the tree has been modified, all positions and bindings are lost.<br>
-Note that some bindings recovery can also be done during this resolution with
-<b><a href="../reference/api/org/eclipse/jdt/core/dom/ASTParser.html#setBindingsRecovery(boolean)">setBindingsRecovery(boolean)</a></b>.
-Using this recovery, some bindings - <i>typically missing types</i> - will no longer
-be <code>null</code>, hence improving the resilience of any clients using the AST tree.
-
-<h4>
-Creating an AST by reconciling a working copy
-</h4>
-If a working copy is not consistent (has been modified) then an AST can be created by calling the method <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">reconcile(int, boolean, WorkingCopyOwner, IProgressMonitor)</a></b>.
-To request AST creation, call the <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">reconcile(...)</a></b>
- method with <b><a href="../reference/api/org/eclipse/jdt/core/dom/AST.html#JLS3">AST.JLS3</a></b> as first parameter.<br>
-<br>
-Its bindings are computed only if the problem requestor is active, or if the problem detection is forced.
-Resolving the bindings is a costly operation and should be done only when necessary. As soon as the tree has been modified, all positions and
-bindings are lost.<br>
-Note that some bindings recovery can also be done during this resolution with
-by using the method <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, int, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)">reconcile(int, int, WorkingCopyOwner, IProgressMonitor)</a></b>
-with the flag <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#ENABLE_BINDINGS_RECOVERY">ENABLE_BINDINGS_RECOVERY</a></b>
-set on the second parameter. Using this recovery, some bindings - <i>typically missing types</i> - will no longer
-be <code>null</code>, hence improving the resilience of any clients using the AST tree.
-
-<h4>
-From scratch
-</h4>
-<P>It is possible to create a <b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html">CompilationUnit</a></b> from scratch using the factory methods on <b><a href="../reference/api/org/eclipse/jdt/core/dom/AST.html">AST</a></b>.
-These method names start with <b>new...</b>. The following is an example that creates a <b>HelloWorld</b> class.
-</P>
-<P>The first snippet is the generated output:</p>
-<pre>
-<font color='#4444CC'>
-	package example;
-	import java.util.*;
-	public class HelloWorld {
-		public static void main(String[] args) {
-			System.out.println(&quot;Hello&quot; + &quot; world&quot;);
-		}
-	}
-</font>
-</pre>
-<P>The following snippet is the corresponding code that generates the output.</p>
-<pre><font color='#4444CC'>
-		AST ast = AST.newAST(AST.JLS3);
-		CompilationUnit unit = ast.newCompilationUnit();
-		PackageDeclaration packageDeclaration = ast.newPackageDeclaration();
-		packageDeclaration.setName(ast.newSimpleName(&quot;example&quot;));
-		unit.setPackage(packageDeclaration);
-		ImportDeclaration importDeclaration = ast.newImportDeclaration();
-		QualifiedName name = 
-			ast.newQualifiedName(
-				ast.newSimpleName(&quot;java&quot;),
-				ast.newSimpleName(&quot;util&quot;));
-		importDeclaration.setName(name);
-		importDeclaration.setOnDemand(true);
-		unit.imports().add(importDeclaration);
-		TypeDeclaration type = ast.newTypeDeclaration();
-		type.setInterface(false);
-		type.modifiers().add(ast.newModifier(Modifier.ModifierKeyword.PUBLIC_KEYWORD));
-		type.setName(ast.newSimpleName(&quot;HelloWorld&quot;));
-		MethodDeclaration methodDeclaration = ast.newMethodDeclaration();
-		methodDeclaration.setConstructor(false);
-		List modifiers = methodDeclaration.modifiers();
-		modifiers.add(ast.newModifier(Modifier.ModifierKeyword.PUBLIC_KEYWORD));
-		modifiers.add(ast.newModifier(Modifier.ModifierKeyword.STATIC_KEYWORD));
-		methodDeclaration.setName(ast.newSimpleName(&quot;main&quot;));
-		methodDeclaration.setReturnType2(ast.newPrimitiveType(PrimitiveType.VOID));
-		SingleVariableDeclaration variableDeclaration = ast.newSingleVariableDeclaration();
-		variableDeclaration.setType(ast.newArrayType(ast.newSimpleType(ast.newSimpleName(&quot;String&quot;))));
-		variableDeclaration.setName(ast.newSimpleName(&quot;args&quot;));
-		methodDeclaration.parameters().add(variableDeclaration);
-		org.eclipse.jdt.core.dom.Block block = ast.newBlock();
-		MethodInvocation methodInvocation = ast.newMethodInvocation();
-		name = 
-			ast.newQualifiedName(
-				ast.newSimpleName(&quot;System&quot;),
-				ast.newSimpleName(&quot;out&quot;));
-		methodInvocation.setExpression(name);
-		methodInvocation.setName(ast.newSimpleName(&quot;println&quot;)); 
-		InfixExpression infixExpression = ast.newInfixExpression();
-		infixExpression.setOperator(InfixExpression.Operator.PLUS);
-		StringLiteral literal = ast.newStringLiteral();
-		literal.setLiteralValue(&quot;Hello&quot;);
-		infixExpression.setLeftOperand(literal);
-		literal = ast.newStringLiteral();
-		literal.setLiteralValue(&quot; world&quot;);
-		infixExpression.setRightOperand(literal);
-		methodInvocation.arguments().add(infixExpression);
-		ExpressionStatement expressionStatement = ast.newExpressionStatement(methodInvocation);
-		block.statements().add(expressionStatement);
-		methodDeclaration.setBody(block);
-		type.bodyDeclarations().add(methodDeclaration);
-		unit.types().add(type);
-</font></pre>
-<h4>Retrieving extra positions</h4>
-<p>The DOM/AST node contains only a pair of positions (the starting position and the length of the node). This is not always
-sufficient. In order to retrieve intermediate positions, the <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IScanner.html">IScanner</a></b> API should be used. For example,
-we have an <b><a href="../reference/api/org/eclipse/jdt/core/dom/InstanceofExpression.html">InstanceofExpression</a></b> for which we want to know the 
-positions of the <i>instanceof</i> operator.
-We could write the following method to achieve this:</p>
-<pre><font color='#4444CC'>
-	private int[] getOperatorPosition(Expression expression, char[] source) {
-		if (expression instanceof InstanceofExpression) {
-			IScanner scanner = ToolFactory.createScanner(false, false, false, false);
-			scanner.setSource(source);
-			int start = expression.getStartPosition();
-			int end = start + expression.getLength();
-			scanner.resetTo(start, end);
-			int token;
-			try {
-				while ((token = scanner.getNextToken()) != ITerminalSymbols.TokenNameEOF) {
-					switch(token) {
-						case ITerminalSymbols.TokenNameinstanceof:
-							return new int[] {scanner.getCurrentTokenStartPosition(), scanner.getCurrentTokenEndPosition()};
-					}
-				}
-			} catch (InvalidInputException e) {
-			}
-		}
-		return null;
-	}
-</font></pre>
-<p>The <b><a href="../reference/api/org/eclipse/jdt/core/compiler/IScanner.html">IScanner</a></b> is used to divide the input source into tokens.
-Each token has a specific value that is defined in the <b><a href="../reference/api/org/eclipse/jdt/core/compiler/ITerminalSymbols.html">ITerminalSymbols</a></b> interface. It is 
-fairly simple to iterate and retrieve the right token. We also recommend that you use the scanner if you want to find the 
-position of the <i>super</i> keyword in a 
-<b><a href="../reference/api/org/eclipse/jdt/core/dom/SuperMethodInvocation.html">SuperMethodInvocation</a></b>.</p>
-
-<h4>Source code modifcations</h4>
-
-<P>
-Some source code modifications are not provided via the Java element API.
-A more general way to edit source code (such as changing the source code for existing elements) is accomplished using the compilation unit's raw source code and the rewrite API of the DOM/AST.</P>
-<P>
-To perform DOM/AST rewriting, there are two sets of API: the descriptive rewriting and the modifying rewriting.
-</p>
-<p>
-The descriptive API does not modify the AST but use <b><a href="../reference/api/org/eclipse/jdt/core/dom/rewrite/ASTRewrite.html">ASTRewrite</a></b> API to generate the descriptions of modifications.
-The AST rewriter collects descriptions of modifications to nodes and translates these descriptions into text edits that can then be applied to the original source.</p>
-<pre>
-<font color='#4444CC'>
-   // creation of a Document
-   ICompilationUnit cu = ... ; // content is "public class X {\n}"
-   String source = cu.getSource();
-   Document document= new Document(source);
-
-   // creation of DOM/AST from a ICompilationUnit
-   ASTParser parser = ASTParser.newParser(AST.JLS3);
-   parser.setSource(cu);
-   CompilationUnit astRoot = (CompilationUnit) parser.createAST(null);
-
-   // creation of ASTRewrite
-   ASTRewrite rewrite = ASTRewrite.create(astRoot.getAST());
-
-   // description of the change
-   SimpleName oldName = ((TypeDeclaration)astRoot.types().get(0)).getName();
-   SimpleName newName = astRoot.getAST().newSimpleName("Y");
-   rewrite.replace(oldName, newName, null);
-
-   // computation of the text edits
-   TextEdit edits = rewrite.rewriteAST(document, cu.getJavaProject().getOptions(true));
-
-   // computation of the new source code
-   edits.apply(document);
-   String newSource = document.get();
-
-   // update of the compilation unit
-   cu.getBuffer().setContents(newSource);
-</font></pre>
-
-<p>
-The modifying API allows to modify directly the AST:</P>
-<ul>
-<li>Request the recording of modifications (<b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html#recordModifications()">CompilationUnit.recordModifications()</a></b>).</li>
-<li>Perform the modifications on the AST Nodes.</li>
-<li>And when the modifications are finished, generate text edits that can then be applied to the original source (<b><a href="../reference/api/org/eclipse/jdt/core/dom/CompilationUnit.html#rewrite(org.eclipse.jface.text.IDocument, java.util.Map)">CompilationUnit.rewrite(...)</a></b>).</li>
-</ul>
-<pre>
-<font color='#4444CC'>
-   // creation of a Document
-   ICompilationUnit cu = ... ; // content is "public class X {\n}"
-   String source = cu.getSource();
-   Document document= new Document(source);
-
-   // creation of DOM/AST from a ICompilationUnit
-   ASTParser parser = ASTParser.newParser(AST.JLS3);
-   parser.setSource(cu);
-   CompilationUnit astRoot = (CompilationUnit) parser.createAST(null);
-
-   // start record of the modifications
-   astRoot.recordModifications();
-
-   // modify the AST
-   TypeDeclaration typeDeclaration = (TypeDeclaration)astRoot.types().get(0);
-   SimpleName newName = astRoot.getAST().newSimpleName("Y");
-   typeDeclaration.setName(newName);
-
-   // computation of the text edits
-   TextEdit edits = astRoot.rewrite(document, cu.getJavaProject().getOptions(true));
-
-   // computation of the new source code
-   edits.apply(document);
-   String newSource = document.get();
-
-   // update of the compilation unit
-   cu.getBuffer().setContents(newSource);
-</font>
-</pre>
-
-<H3>
-<a name="javadeltas">
-Responding to changes in Java elements</a></h3>
-<P>
-If your plug-in needs to know about changes to Java elements after the fact, you can register a Java
-<a href="../reference/api/org/eclipse/jdt/core/IElementChangedListener.html"><b> IElementChangedListener</b></a> with
-<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a>.</P>
-<pre><font color='#4444CC'>
-   JavaCore.addElementChangedListener(new MyJavaElementChangeReporter());
-</font></pre>
-<P>
-You can be more specific and specify the type of events you're interested in using 
-<a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#addElementChangedListener(org.eclipse.jdt.core.IElementChangedListener, int)"><b> addElementChangedListener(IElementChangedListener, int)</b></a>. </P>
-<P>
-For example, if you're only interested in listening for events during a reconcile operation: </P>
-<pre><font color='#4444CC'>
-   JavaCore.addElementChangedListener(new MyJavaElementChangeReporter(), ElementChangedEvent.POST_RECONCILE);
-</font></pre>
-<P>
-There are two kinds of events that are supported by <b>JavaCore</b>:</P>
-<ul>
-<li><a href="../reference/api/org/eclipse/jdt/core/ElementChangedEvent.html#POST_CHANGE"><b>POST_CHANGE</b></a>: 
-      Listeners of this event kind will get notified during the corresponding 
-      <a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IResourceChangeEvent.html#POST_CHANGE"><b>POST_CHANGE</b></a> 
-      resource change notification.</li>
-<li><a href="../reference/api/org/eclipse/jdt/core/ElementChangedEvent.html#POST_RECONCILE"><b>POST_RECONCILE</b></a>: 
-      Listeners of this event kind will get notified at the end of a reconcile operation on a working copy
-      (see <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)"><b>ICompilationUnit.reconcile(int, boolean, WorkingCopyOwner, IProgressMonitor)</b></a>).</li>
-</ul>
-<P>
-Java element change listeners are similar conceptually to resource change listeners
-(described in
-<a HREF="../../org.eclipse.platform.doc.isv/guide/resAdv_events.htm" CLASS="XRef">tracking resource changes</a>). The following snippet implements a Java element change reporter that prints the element deltas to the system console.</P>
-<pre><font color='#4444CC'>
-   public class MyJavaElementChangeReporter implements IElementChangedListener {
-      public void elementChanged(ElementChangedEvent event) {
-         IJavaElementDelta delta= event.getDelta();
-         if (delta != null) {
-            System.out.println(&quot;delta received: &quot;);
-            System.out.print(delta);
-         }
-      }
-   }
-</font></pre>
-<P>
-The <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html"><b> IJavaElementDelta</b></a> includes the 
-<a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getElement()">element</a> that was
-changed and <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getFlags()">flags</a> describing 
-the kind of change that occurred. Most of the time the delta tree is rooted at the Java Model level. Clients must then navigate
-this delta using <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getAffectedChildren()"><b>getAffectedChildren</b></a> 
-to find out what projects have changed. </P>
-<P>
-The following example method traverses a delta and prints the elements that have been added, removed and changed:</P>
-<pre><font color='#4444CC'>
-    void traverseAndPrint(IJavaElementDelta delta) {
-        switch (delta.getKind()) {
-            case IJavaElementDelta.ADDED:
-                System.out.println(delta.getElement() + &quot; was added&quot;);
-                break;
-            case IJavaElementDelta.REMOVED:
-                System.out.println(delta.getElement() + &quot; was removed&quot;);
-                break;
-            case IJavaElementDelta.CHANGED:
-                System.out.println(delta.getElement() + &quot; was changed&quot;);
-                if ((delta.getFlags() &amp; IJavaElementDelta.F_CHILDREN) != 0) {
-                    System.out.println(&quot;The change was in its children&quot;);
-                }
-                if ((delta.getFlags() &amp; IJavaElementDelta.F_CONTENT) != 0) {
-                    System.out.println(&quot;The change was in its content&quot;);
-                }
-                /* Others flags can also be checked */
-                break;
-        }
-        IJavaElementDelta[] children = delta.getAffectedChildren();
-        for (int i = 0; i &lt; children.length; i++) {
-            traverseAndPrint(children[i]);
-        }
-    }
-</font></pre>
-<P>
-Since <a href="../reference/api/org/eclipse/jdt/core/IAnnotation.html"><b> IAnnotation</b></a>s are not children of any
-Java element, annotation deltas are obtained using 
-<a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getAnnotationDeltas()"><b>getAnnotationDeltas()</b></a>.
-</P><P>
-Several kinds of operations can trigger a Java element change notification. Here are some examples:</P>
-<ul>
-<li>Creating a resource, e.g. <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html#createCompilationUnit(java.lang.String, java.lang.String, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>IPackageFragment.createCompilationUnit</b></a> 
-      (the delta indicates the <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#ADDED">addition</a> of the compilation unit)</li>
-<li>Modifying a resource, e.g. <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#createType(java.lang.String, org.eclipse.jdt.core.IJavaElement, boolean, org.eclipse.core.runtime.IProgressMonitor)"><b>ICompilationUnit.createType</b></a> 
-     (the delta indicates that the compilation unit has <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#CHANGED">changed</a> and that a type was 
-     <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#getAddedChildren()"> added as a child</a> of this compilation unit)</li>
-<li>Modifying a project's classpath, e.g. <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html#setRawClasspath(org.eclipse.jdt.core.IClasspathEntry[], org.eclipse.core.runtime.IProgressMonitor)"><b>IJavaProject.setRawClasspath</b></a>
-     (the delta indicates that package fragment roots have been <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_ADDED_TO_CLASSPATH">added to the classpath</a>, 
-     <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_REMOVED_FROM_CLASSPATH">removed from the classpath</a>, or
-     <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_CLASSPATH_REORDER">reordered on the classpath</a>)</li>
-<li>Modifying a classpath variable value, e.g. <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setClasspathVariable(java.lang.String, org.eclipse.core.runtime.IPath, org.eclipse.core.runtime.IProgressMonitor)"><b>JavaCore.setClasspathVariable</b></a>
-     (the delta also indicates that package fragment roots have been affected)</li>
-<li>Reconciling a working copy with its buffer, e.g. <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html#reconcile(int, boolean, org.eclipse.jdt.core.WorkingCopyOwner, org.eclipse.core.runtime.IProgressMonitor)"><b>ICompilationUnit.reconcile</b></a></li>
-<li>Modifying an <a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a> that ends with ".java" and that is on the
-      project's classpath, e.g. using <b>IFile.setContents</b> (the delta indicates that a compilation unit was changed, but 
-      <a href="../reference/api/org/eclipse/jdt/core/IJavaElementDelta.html#F_FINE_GRAINED">no finer-grained information</a>
-      is provided as this was not done through a Java Model operation)</li>
-</ul>
-<P>Similar to <a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IResourceDelta.html"><b>IResourceDelta</b></a> 
-the Java element deltas can be batched using an 
-<a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html"><b>IWorkspaceRunnable</b></a>. 
-The deltas resulting from several Java Model operations that are run inside a <b>IWorkspaceRunnable</b> are merged and reported at once.&nbsp;&nbsp; </P>
-<P><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a><b>
-</b>provides a <b>run</b> method for batching Java element changes. </P>
-<P>
-For example, the following code fragment will trigger 2 Java element change events: </P>
-<pre><font color='#4444CC'>
-    // Get package
-    IPackageFragment pkg = ...;
-    
-    // Create 2 compilation units
-    ICompilationUnit unitA = pkg.createCompilationUnit(&quot;A.java&quot;, &quot;public class A {}&quot;, false, null);
-    ICompilationUnit unitB = pkg.createCompilationUnit(&quot;B.java&quot;, &quot;public class B {}&quot;, false, null);
-</font></pre>
-<P>
-Whereas the following code fragment will trigger 1 Java element change event: </P>
-<pre><font color='#4444CC'>
-    // Get package
-    final IPackageFragment pkg = ...;
-    
-    // Create 2 compilation units
-    JavaCore.run(
-        new IWorkspaceRunnable() {
- 	        public void run(IProgressMonitor monitor) throws CoreException {
- 	            ICompilationUnit unitA = pkg.createCompilationUnit(&quot;A.java&quot;, &quot;public class A {}&quot;, false, null);
- 	            ICompilationUnit unitB = pkg.createCompilationUnit(&quot;B.java&quot;, &quot;public class B {}&quot;, false, null);
- 	        }
-        },
-        null);
-</font></pre>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm
deleted file mode 100644
index 9f52a45..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_open_editor.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Opening a Java editor</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h3>Opening a Java editor</h3>
-<p>The following snippet shows how <b><a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html"> 
-  JavaUI</a></b> can be used to open a Java editor and display a specific member of a 
-  Java compilation unit.</p>
-<pre><font color="#4444cc">    void showMethod(IMember member) throws PartInitException, JavaModelException {
-        ICompilationUnit cu = member.getCompilationUnit();
-        IEditorPart javaEditor = JavaUI.openInEditor(cu);
-        JavaUI.revealInEditor(javaEditor, (IJavaElement)member);
-    }
-</font></pre>
-<p> The methods <code>openInEditor</code> and <code>revealInEditor</code> also 
-  work for class files and for members contained in class files. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm
deleted file mode 100644
index 4ea4517..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_options.htm
+++ /dev/null

@@ -1,4618 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<HEAD>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>JDT Core options</title>
-
-</HEAD>
-<BODY>
-<h2>JDT Core options</h2>
-<P>
-JDT Core options control the behavior of core features such as the Java
-compiler, code formatter, code assist, and other core behaviors.&nbsp; The APIs
-for accessing the options are defined in <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a>.&nbsp;
-Options can be accessed as a group as follows:</P>
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getDefaultOptions()">JavaCore.getDefaultOptions()</a></b> - Answers the default value of the options.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getOptions()">JavaCore.getOptions()</a></b> - Answers the current values of the options.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#setOptions(java.util.Hashtable)">JavaCore.setOptions(Hashtable newOptions)</a></b> - Replaces the options values by new values.</li>
-</ul>
-
-<p>Options can also be accessed individually by a string name.</P>
-
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getOption(java.lang.String)">JavaCore.getOption(String optionName)</a></b> - Answers the value of a specific option.</li>
-</ul>
-
-<p>Options that can configure the severity of a compiler problem can also be found.</p>
-
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#getOptionForConfigurableSeverity(int)">JavaCore.getOptionForConfigurableSeverity(int problemID)</a></b> - Answers the
-option to use to configure the severity of the compiler problem identified by <code>problemID</code>.</li>
-</ul>
-
-<p>Options are stored as a hash table of all known configurable options with their values.
-Helper constants have been defined on <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a> for each option ID and its possible constant values.</P>
-
-<P>
-The following code fragment restores the value of all core options to their
-defaults except for one (<code>COMPILER_PB_DEPRECATION</code>), which is set specifically.</p>
-<pre><font color='#4444CC'>
-   // Get the default options
-   Hashtable options = JavaCore.getDefaultOptions();
-   
-   // Change the value of an option
-   options.put(JavaCore.COMPILER_PB_DEPRECATION, JavaCore.ERROR);
-   
-   // Set the new options
-   JavaCore.setOptions(options);
-</font></pre>
-
-<p>The following code fragment keeps the value of the current options and modifies
-only one (<code>COMPILER_PB_DEPRECATION</code>):</p>
-
-<pre><font color='#4444CC'>
-   // Get the current options
-   Hashtable options = JavaCore.getOptions();
-   
-   // Change the value of an option
-   options.put(JavaCore.COMPILER_PB_DEPRECATION, JavaCore.ERROR);
-   
-   // Set the new options
-   JavaCore.setOptions(options);
-</font></pre>
-
-<H3>Project specific options</h3>
-
-<p>The values of options can be overridden per project using protocol in <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b>IJavaProject</b></a>.</p>
-
-<p>The following code fragment retrieves the value of an option (<code>COMPILER_PB_DEPRECATION</code>)
-for a specific project in two different ways.&nbsp; The boolean parameter
-controls whether only the project-specific options should be returned in a query
-or whether the project's option values should be merged with the values in
-JavaCore.</p>
-
-<pre><font color="#4444CC">
-   // Get the project
-   IJavaProject project = ...;
-
-   // See if the value of an option has been set in this project
-   String value = project.getOption(JavaCore.COMPILER_PB_DEPRECATION, <b>false</b>);
-   if (value == null) {
-     // no specific option was set on the project
-     ...
-   }
-   
-   // Get the value of an option from this project.  Use the value from 
-   // JavaCore value if none is specified for the project
-   String value = project.getOption(JavaCore.COMPILER_PB_DEPRECATION, <b>true</b>);</font>
-</pre>
-<H3>JDT Core options descriptions</h3>
-
-<P>
-The following tables describe the available JDT Core options.&nbsp; The option
-id is shown in parentheses and the default value is shown in bold italics. </P>
-
-<H4>Options categories</h4>
-<ul>
-<li><b><a href="#compiler">Compiler options</a></b></li>
-<li><b><a href="#builder">Builder options</a></b></li>
-<li><b><a href="#javacore">JavaCore options</a></b></li>
-<li><b><a href="#formatter">Formatter options</a></b></li>
-<li><b><a href="#codeassist">CodeAssist options</a></b></li>
-</ul>
-
-<H4><a name="compiler">Compiler options</a></h4>
-
-<table BORDER="1" CELLSPACING="2" CELLPADDING="2" WIDTH="100%" >
-<tr>
-<th>Description</th>
-<th width=140>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Inline JSR Bytecode Instruction</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_CODEGEN_INLINE_JSR_BYTECODE">COMPILER_CODEGEN_INLINE_JSR_BYTECODE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled in conjunction with a Java target platform lesser than or 
-equal to "1.4", the compiler will no longer generate JSR instructions, but rather inline corresponding
-subroutine code sequences (mostly corresponding to try finally blocks). The generated code will thus
-get bigger, but will load faster on virtual machines since the verification process is then much simpler. 
-This mode is adding support for the Java Specification Request 202 to pre-"1.5" Java 
-target platforms.<br>
-For a Java target platform greater than or equal to "1.5", the inlining of the JSR 
-bytecode instruction is mandatory and this option is ignored.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Setting Target Java Platform</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_CODEGEN_TARGET_PLATFORM">COMPILER_CODEGEN_TARGET_PLATFORM</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=8>For binary compatibility reason, .class files are tagged with VM versions
-that are defined for each level of the reference specification. The target Java platform
-specifies the minimum runtime level required to execute the generated class files.<br>
-The compliance, source and target levels must satisfy a set of constraints summarized 
-in a <a HREF="#compatibility"><b>compatibility table</b></a> below.
-</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_1">VERSION_1_1</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_2">VERSION_1_2</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_3">VERSION_1_3</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_4">VERSION_1_4</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_5">VERSION_1_5</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_6">VERSION_1_6</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_7">VERSION_1_7</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_CLDC_1_1">VERSION_CLDC_1_1</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Preserving Unused Local Variables</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_CODEGEN_UNUSED_LOCAL">COMPILER_CODEGEN_UNUSED_LOCAL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Unless requested to preserve unused local variables (i.e. never read), the compiler will optimize them out, potentially altering debugging.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRESERVE">PRESERVE</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#OPTIMIZE_OUT">OPTIMIZE_OUT</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Setting Compliance Level</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_COMPLIANCE">COMPILER_COMPLIANCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=5>Select the compliance level for the compiler, which will then behave 
-according to the said level of the reference specification.<br>
-The compliance, source and target levels must satisfy a set of constraints summarized 
-in a <a HREF="#compatibility"><b>compatibility table</b></a> below.
-</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_3">VERSION_1_3</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_4">VERSION_1_4</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_5">VERSION_1_5</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_6">VERSION_1_6</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_7">VERSION_1_7</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Javadoc Comment Support</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_DOC_COMMENT_SUPPORT">COMPILER_DOC_COMMENT_SUPPORT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When this support is disabled, the compiler will ignore all javadoc problems options settings
-and will not report any javadoc problem. It will also not find any reference in javadoc comment and
-DOM AST Javadoc node will be only a flat text instead of having structured tag elements.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Generating Line Number Debug Attribute</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_LINE_NUMBER_ATTR">COMPILER_LINE_NUMBER_ATTR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When generated, this attribute will enable source code highlighting in the debugger (.class file is then bigger).</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#GENERATE">GENERATE</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_GENERATE">DO_NOT_GENERATE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Generating Local Variable Debug Attribute</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_LOCAL_VARIABLE_ATTR">COMPILER_LOCAL_VARIABLE_ATTR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When generated, this attribute will enable local variable names to be displayed in the debugger, only in places where variables are definitely assigned (.class file is then bigger).</td>
-<td><i><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#GENERATE">GENERATE</a></b></i></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_GENERATE">DO_NOT_GENERATE</a></b></td>
-</tr>								  
-
-<tr>
-<td colspan=2><b>Reporting Use of Annotation Type as Super Interface</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_ANNOTATION_SUPER_INTERFACE">COMPILER_PB_ANNOTATION_SUPER_INTERFACE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever an annotation type is used as a super-interface. Though legal, this is discouraged.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Usage of 'assert' Identifier</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_ASSERT_IDENTIFIER">COMPILER_PB_ASSERT_IDENTIFIER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever 'assert' is used as an identifier (reserved keyword in 1.4)</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Boxing/Unboxing Conversion</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_AUTOBOXING">COMPILER_PB_AUTOBOXING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a boxing or an unboxing conversion is performed.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Usage of char[] Expressions in String Concatenations
-  </b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_CHAR_ARRAY_IN_STRING_CONCATENATION">COMPILER_PB_CHAR_ARRAY_IN_STRING_CONCATENATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever a char[] expression is used in String concatenations (e.g.
-  &quot;hello&quot; + new char[]{'w','o','r','l','d'}).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Deprecation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DEPRECATION">COMPILER_PB_DEPRECATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will signal use of deprecated API either as an error or a warning.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Deprecation Inside Deprecated Code</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DEPRECATION_IN_DEPRECATED_CODE">COMPILER_PB_DEPRECATION_IN_DEPRECATED_CODE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal use of deprecated API 
-              inside deprecated code either as an error or a warning.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Deprecation When Overriding Deprecated Method</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DEPRECATION_WHEN_OVERRIDING_DEPRECATED_METHOD">COMPILER_PB_DEPRECATION_WHEN_OVERRIDING_DEPRECATED_METHOD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal the declaration of a method overriding a deprecated one.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Discouraged Reference to Type with Restricted Access</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_DISCOURAGED_REFERENCE">COMPILER_PB_DISCOURAGED_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when referring to a type with discouraged access, as defined according to the access rule specifications.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Empty Statements and Unnecessary Semicolons</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_EMPTY_STATEMENT">COMPILER_PB_EMPTY_STATEMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if an empty statement or a
-  unnecessary semicolon is encountered.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Usage of 'enum' Identifier</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_ENUM_IDENTIFIER">COMPILER_PB_ENUM_IDENTIFIER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever 'enum' is used as an identifier (reserved keyword in 1.5).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Switch Fall-Through Case</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FALLTHROUGH_CASE">COMPILER_PB_FALLTHROUGH_CASE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when 
-  a case may be entered by falling through a preceeding, non empty case.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Treating Optional Errors as Fatal</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FATAL_OPTIONAL_ERROR">COMPILER_PB_FATAL_OPTIONAL_ERROR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, optional errors (i.e. optional problems which 
-  severity has been set to "error") will be treated as standard compiler 
-  errors, that is as fatal errors. When detecting a fatal error in source code,
-  the compiler generates problem methods/types into the corresponding class 
-  files, in effect preventing the offending code from running until all issues 
-  get resolved.<br>
-  When disabled, optional errors are only considered as warnings for code 
-  generation purposes, but they still carry an error indicator to make them more
-  severe than regular warnings.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Field Declaration Hiding another Variable</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FIELD_HIDING">COMPILER_PB_FIELD_HIDING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a field
-  declaration is hiding some field or local variable (either locally, inherited or defined in enclosing type).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Final Bound for Type Parameter</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FINAL_PARAMETER_BOUND">COMPILER_PB_FINAL_PARAMETER_BOUND</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a generic type parameter is associated with a 
-bound corresponding to a final type; since final types cannot be further extended, the parameter is pretty useless.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Finally Blocks Not Completing Normally</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FINALLY_BLOCK_NOT_COMPLETING">COMPILER_PB_FINALLY_BLOCK_NOT_COMPLETING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a finally block does not complete normally.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Forbidden Reference to Type with Restricted Access</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_FORBIDDEN_REFERENCE">COMPILER_PB_FORBIDDEN_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when referring to a type that is non accessible, as defined according to the access rule specifications.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR"><i>ERROR</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing HashCode Method</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_HASHCODE_METHOD">COMPILER_PB_MISSING_HASHCODE_METHOD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if a type overrides Object.equals(Object) but does not override hashCode().</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR"><i>ERROR</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Hidden Catch Block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_HIDDEN_CATCH_BLOCK">COMPILER_PB_HIDDEN_CATCH_BLOCK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Local to a try statement, some catch blocks may hide others , e.g.
-<pre>
-   try {
-      throw new java.io.CharConversionException();
-   } catch (java.io.CharConversionException e) {
-   } catch (java.io.IOException e) {}.
-</pre>
-When enabling this option, the compiler will issue an error or a warning for hidden catch blocks corresponding to checked exceptions.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Interface Method not Compatible with non-Inherited Methods</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INCOMPATIBLE_NON_INHERITED_INTERFACE_METHOD">COMPILER_PB_INCOMPATIBLE_NON_INHERITED_INTERFACE_METHOD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever an interface defines a method incompatible with a non-inherited
-  Object one.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Incomplete Enum Switch</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INCOMPLETE_ENUM_SWITCH">COMPILER_PB_INCOMPLETE_ENUM_SWITCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning 
-  whenever an enum constant has no corresponding case label in an enum switch
-  statement.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Indirect Reference to a Static Member</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INDIRECT_STATIC_ACCESS">COMPILER_PB_INDIRECT_STATIC_ACCESS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a static field
-  or method is accessed in an indirect way. A reference to a static member should
-  preferably be qualified with its declaring type name.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Invalid Javadoc Comment</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC">COMPILER_PB_INVALID_JAVADOC</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>This is the generic control for the severity of Javadoc problems.
-  When enabled, the compiler will issue an error or a warning for a problem in Javadoc.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Invalid Javadoc Tags</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS">COMPILER_PB_INVALID_JAVADOC_TAGS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal unbound or unexpected reference tags in Javadoc.
-  A 'throws' tag referencing an undeclared exception would be considered as unexpected.
-  <br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc;<br>
-  see also <a href="#INVALID_JAVADOC_TAGS_VISIBILITY">COMPILER_PB_INVALID_JAVADOC_TAGS_VISIBILITY</a>.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><i>DISABLED</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Javadoc Tags with Deprecated References</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS__DEPRECATED_REF">COMPILER_PB_INVALID_JAVADOC_TAGS__DEPRECATED_REF</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will report deprecated references used in Javadoc tags.
-<br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc;<br>
-  see also <a href="#INVALID_JAVADOC_TAGS_VISIBILITY">COMPILER_PB_INVALID_JAVADOC_TAGS_VISIBILITY</a>.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><i>DISABLED</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Javadoc Tags with Not Visible References</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS__NOT_VISIBLE_REF">COMPILER_PB_INVALID_JAVADOC_TAGS__NOT_VISIBLE_REF</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will report non-visible references used in Javadoc tags.
-<br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc;<br>
-  see also <a href="#INVALID_JAVADOC_TAGS_VISIBILITY">COMPILER_PB_INVALID_JAVADOC_TAGS_VISIBILITY</a>.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><i>DISABLED</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><a name="INVALID_JAVADOC_TAGS_VISIBILITY"></a><b>Visibility Level For Invalid Javadoc Tags</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS_VISIBILITY">COMPILER_PB_INVALID_JAVADOC_TAGS_VISIBILITY</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Set the minimum visibility level for Javadoc tag problems. Below this level problems will be ignored.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PUBLIC"><i>PUBLIC</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PROTECTED">PROTECTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DEFAULT">DEFAULT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRIVATE">PRIVATE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Local Variable Declaration Hiding another Variable</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_LOCAL_VARIABLE_HIDING">COMPILER_PB_LOCAL_VARIABLE_HIDING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a local variable
-  declaration is hiding some field or local variable (either locally, inherited or defined in enclosing type).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Maximum number of problems reported per compilation unit</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MAX_PER_UNIT">COMPILER_PB_MAX_PER_UNIT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>Specify the maximum number of problems reported on each compilation unit (if the maximum is zero then all problems are reported).</td>
-<td>A positive or null integer. <br><b><i>Default value is 100.</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Method With Constructor Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_METHOD_WITH_CONSTRUCTOR_NAME">COMPILER_PB_METHOD_WITH_CONSTRUCTOR_NAME</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Naming a method with a constructor name is generally considered poor style programming. When enabling this option, the compiler will signal such scenarios either as an error or a warning.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing @Deprecated Annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_DEPRECATED_ANNOTATION">COMPILER_PB_MISSING_DEPRECATED_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever encountering a declaration carrying a @deprecated doc tag but having no corresponding @Deprecated annotation.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Comments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_COMMENTS">COMPILER_PB_MISSING_JAVADOC_COMMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>This is the generic control for the severity of missing Javadoc comment problems.
-  When enabled, the compiler will issue an error or a warning when Javadoc comments are missing.
-  <br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the expected Javadoc.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Comments on Overriding Methods</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_COMMENTS_OVERRIDING">COMPILER_PB_MISSING_JAVADOC_COMMENTS_OVERRIDING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will verify overriding methods in order to report missing Javadoc comment problems.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><i>DISABLED</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Visibility Level For Missing Javadoc Comments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_COMMENTS_VISIBILITY">COMPILER_PB_MISSING_JAVADOC_COMMENTS_VISIBILITY</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Set the minimum visibility level for missing Javadoc problems. Below this level problems will be ignored.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PUBLIC"><i>PUBLIC</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PROTECTED">PROTECTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DEFAULT">DEFAULT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRIVATE">PRIVATE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting missing tag description</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION">COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will report a warning or an error for 
-  any Javadoc tag missing a required description.<br>
-  The severity of the problem is controlled with option 
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC">COMPILER_PB_INVALID_JAVADOC</a>.
-  It does <em>not</em> depend on option 
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_INVALID_JAVADOC_TAGS">COMPILER_PB_INVALID_JAVADOC_TAGS</a>.<br>
-  When this option is valued to 
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_ALL_STANDARD_TAGS">COMPILER_PB_MISSING_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_ALL_STANDARD_TAGS">JAVADOC_TAG_DESCRIPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_ALL_STANDARD_TAGS">ALL_STANDARD_TAGS</a>,
-  a subset of the standard
-  <a href="http://java.sun.com/javase/6/docs/technotes/tools/windows/javadoc.html#javadoctags">Javadoc 
-  tags</a> that have a description, text or label are checked. While this set 
-  may grow in the future, note that user-defined tags are not and will not be 
-  checked.
-</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_RETURN_TAG">COMPILER_PB_MISSING_</a><br><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_RETURN_TAG">JAVADOC_TAG_DESCRIPTION_RETURN_TAG</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_ALL_STANDARD_TAGS">COMPILER_PB_MISSING_</a><br><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_ALL_STANDARD_TAGS">JAVADOC_TAG_DESCRIPTION_ALL_STANDARD_TAGS</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_NO_TAG">COMPILER_PB_MISSING_</a><br><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAG_DESCRIPTION_NO_TAG">JAVADOC_TAG_DESCRIPTION_NO_TAG</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Tags</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAGS">COMPILER_PB_MISSING_JAVADOC_TAGS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>This is the generic control for the severity of Javadoc missing tag problems.
-  When enabled, the compiler will issue an error or a warning when tags are missing in Javadoc comments.
-  <br>Note that this diagnosis can be enabled based on the visibility of the construct associated with the Javadoc.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Missing Javadoc Tags on Overriding Methods</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAGS_OVERRIDING">COMPILER_PB_MISSING_JAVADOC_TAGS_OVERRIDING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Specify whether the compiler will verify overriding methods in order to report Javadoc missing tag problems.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><i>DISABLED</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Visibility Level For Missing Javadoc Tags</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_JAVADOC_TAGS_VISIBILITY">COMPILER_PB_MISSING_JAVADOC_TAGS_VISIBILITY</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Set the minimum visibility level for Javadoc missing tag problems. Below this level problems will be ignored.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PUBLIC"><i>PUBLIC</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PROTECTED">PROTECTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DEFAULT">DEFAULT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#PRIVATE">PRIVATE</a></b></td>
-</tr> 
-
-<tr>
-<td colspan=2><b>Reporting Missing @Override Annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_OVERRIDE_ANNOTATION">COMPILER_PB_MISSING_OVERRIDE_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever encountering a method declaration which overrides a superclass method but has no @Override annotation.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>							  
-
-<tr>
-<td colspan=2><b>Reporting Missing Declaration of serialVersionUID Field on Serializable Class</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_MISSING_SERIAL_VERSION">COMPILER_PB_MISSING_SERIAL_VERSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a serializable class is missing a local declaration of a serialVersionUID field. This field must be declared as static final and be of type long.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Assignment with No Effect</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_NO_EFFECT_ASSIGNMENT">COMPILER_PB_NO_EFFECT_ASSIGNMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever an assignment has no effect (e.g. 'x = x').</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Non-Externalized String Literal</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_NON_NLS_STRING_LITERAL">COMPILER_PB_NON_NLS_STRING_LITERAL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for non externalized String literal (i.e. non tagged with //$NON-NLS-&lt;n&gt;$).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Null Dereference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_NULL_REFERENCE">COMPILER_PB_NULL_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning 
-  whenever a variable that is statically known to hold a null value is used to
-  access a field or method.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Overriding Methods that do not call their super method invocation.</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_OVERRIDING_METHOD_WITHOUT_SUPER_INVOCATION">COMPILER_PB_OVERRIDING_METHOD_WITHOUT_SUPER_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if a 
-  method is overriding another method without calling the super invocation.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Potential Null Dereference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_POTENTIAL_NULL_REFERENCE">COMPILER_PB_POTENTIAL_NULL_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning 
-  whenever a variable that has formerly been tested against null but is not (no 
-  more) statically known to hold a non-null value is used to access a field or 
-  method.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Redundant Null Check</b> (<b><a href=
-  "../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_REDUNDANT_NULL_CHECK">COMPILER_PB_REDUNDANT_NULL_CHECK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning 
-  whenever a variable that is statically known to hold a null or a non-null 
-  value is tested against null.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Attempt to Override Package Visible Method</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_OVERRIDING_PACKAGE_DEFAULT_METHOD">COMPILER_PB_OVERRIDING_PACKAGE_DEFAULT_METHOD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>A package visible method, which is any method that is not explicitly 
-  declared as public, protected or private, is not visible from other 
-  packages, and thus cannot be overridden from another package. 
-  Attempting to override a package visible method from another package 
-  introduces a new method that is unrelated to the original one. When 
-  enabling this option, the compiler will signal such situations as an 
-  error or a warning.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Parameter Assignment</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_PARAMETER_ASSIGNMENT">COMPILER_PB_PARAMETER_ASSIGNMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if a 
-  parameter is assigned to.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Possible Accidental Boolean Assignment</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_POSSIBLE_ACCIDENTAL_BOOLEAN_ASSIGNMENT">COMPILER_PB_POSSIBLE_ACCIDENTAL_BOOLEAN_ASSIGNMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if a boolean assignment is acting as the condition
-  of a control statement  (where it probably was meant to be a boolean comparison).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Raw Type Reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_RAW_TYPE_REFERENCE">COMPILER_PB_RAW_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when 
-  detecting references to raw types. Raw types are discouraged, and are 
-  intended to help interfacing with legacy code. In the future, the language 
-  specification may reject raw references to generic types.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Redundant Superinterface</b> (<b><a href=
-  "../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_REDUNDANT_SUPERINTERFACE">COMPILER_PB_REDUNDANT_SUPERINTERFACE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning if a 
-  type explicitly implements an interface that is already implemented by any 
-  of its supertypes.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Special Parameter Hiding another Field</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_SPECIAL_PARAMETER_HIDING_FIELD">COMPILER_PB_SPECIAL_PARAMETER_HIDING_FIELD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal cases where a constructor or setter method parameter declaration 
-  is hiding some field (either locally, inherited or defined in enclosing type).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><i>DISABLED</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Non-Static Reference to a Static Member</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_STATIC_ACCESS_RECEIVER">COMPILER_PB_STATIC_ACCESS_RECEIVER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever a static field or method is accessed with an expression receiver.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Determining Effect of @SuppressWarnings</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_SUPPRESS_WARNINGS">COMPILER_PB_SUPPRESS_WARNINGS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the @SuppressWarnings annotation can be used to suppress some compiler warnings. 
-<br>When disabled, all @SupressWarnings annotations are ignored; i.e., warnings are reported
-  even when they occur in the scope of an entity that carries an 
-  @SuppressWarnings annotation.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><i>ENABLED</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Synthetic Access Emulation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_SYNTHETIC_ACCESS_EMULATION">COMPILER_PB_SYNTHETIC_ACCESS_EMULATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever it emulates access to a non-accessible member of an enclosing type. Such access can have performance implications.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Type Parameter Declaration Hiding another Type</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_TYPE_PARAMETER_HIDING">COMPILER_PB_TYPE_PARAMETER_HIDING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a type parameter declaration is hiding some type.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unchecked Type Operation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNCHECKED_TYPE_OPERATION">COMPILER_PB_UNCHECKED_TYPE_OPERATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever an operation involves generic types, and potentially
-invalidates type safety since involving raw types (e.g. invoking #foo(X&lt;String&gt;) with arguments (X)).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Undocumented Empty Block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNDOCUMENTED_EMPTY_BLOCK">COMPILER_PB_UNDOCUMENTED_EMPTY_BLOCK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when an empty block is detected and it is not
-  documented with any comment.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unhandled Warning Token for @SuppressWarnings</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNHANDLED_WARNING_TOKEN">COMPILER_PB_UNHANDLED_WARNING_TOKEN</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when encountering a token it cannot handle inside a @SuppressWarnings annotation.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unnecessary Else</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNNECESSARY_ELSE">COMPILER_PB_UNNECESSARY_ELSE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a statement is unnecessarily
-  nested within an else clause (in situation where then clause is not completing normally).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unnecessary Type Check</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNNECESSARY_TYPE_CHECK">COMPILER_PB_UNNECESSARY_TYPE_CHECK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a cast or an instanceof operation 
-  is unnecessary.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unqualified Access to Field</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNQUALIFIED_FIELD_ACCESS">COMPILER_PB_UNQUALIFIED_FIELD_ACCESS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a field is access without any qualification.
-  In order to improve code readability, it should be qualified, e.g. 'x' should rather be written 'this.x'.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Declared Thrown Exception</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when a 
-  method or a constructor is declaring a checked exception as thrown,
-  but its body actually raises neither that exception, nor any other 
-  exception extending it.<br>
-  This diagnostic is further tuned by options
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  EXEMPT_EXCEPTION_AND_THROWABLE</a></u>,
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  INCLUDE_DOC_COMMENT_REFERENCE</a></u>,
-  and 
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  WHEN_OVERRIDING</a></u>.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Declared Thrown Exception Exempts Exception And Throwable</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will issue an error or a warning when a 
-  method or a constructor is declaring a checked exception else than
-  <code>java.lang.Throwable</code> or <code>java.lang.Exception</code> as thrown,
-  but its body actually raises neither that exception, nor any other 
-  exception extending it. When disabled, the compiler will issue an 
-  error or a warning when a method or a constructor is declaring a 
-  checked exception (including <code>java.lang.Throwable</code> and 
-  <code>java.lang.Exception</code>) as thrown, but its body actually raises 
-  neither that exception, nor any other exception extending it.<br> 
-  The severity of the unused declared thrown exception problem is 
-  controlled with option 
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  UNUSED_DECLARED_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  THROWN_EXCEPTION</a></u>.<br>
-  This diagnostic is further tuned by options
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  INCLUDE_DOC_COMMENT_REFERENCE</a></u>
-  and 
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  WHEN_OVERRIDING</a></u>.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><i>ENABLED</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Consider Reference in Doc Comment for Unused Declared Thrown Exception Check</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will consider doc comment references to 
-  exceptions (i.e. <code>@throws</code> clauses) for the unused declared thrown 
-  exception check. Thus, documented exceptions will be considered as mandated as 
-  per doc contract.<br>
-  The severity of the unused declared thrown exception problem is controlled 
-  with option
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  UNUSED_DECLARED_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  THROWN_EXCEPTION</a></u>.<br>
-  Note: this option has no effect until the doc comment support is enabled 
-  according to the option <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_DOC_COMMENT_SUPPORT">COMPILER_DOC_COMMENT_SUPPORT</a>.<br>
-  This diagnostic is further tuned by options
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  EXEMPT_EXCEPTION_AND_THROWABLE</a></u>
-  and 
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">
-  WHEN_OVERRIDING</a></u>.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><i>ENABLED</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Declared Thrown Exception in Overriding Method</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING">COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_WHEN_OVERRIDING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When disabled, the compiler will report unused declared thrown
-  exceptions neither on overriding methods nor on implementing methods.<br>
-  The severity of the unused declared thrown exception problem is controlled 
-  with option
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  UNUSED_DECLARED_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION">
-  THROWN_EXCEPTION</a></u>.<br>
-  This diagnostic is further tuned by options
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_EXEMPT_EXCEPTION_AND_THROWABLE">
-  EXEMPT_EXCEPTION_AND_THROWABLE</a></u> and
-  <u><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  COMPILER_PB_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  UNUSED_DECLARED_THROWN_EXCEPTION_</a>
-  <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_DECLARED_THROWN_EXCEPTION_INCLUDE_DOC_COMMENT_REFERENCE">
-  INCLUDE_DOC_COMMENT_REFERENCE</a></u>.</td>  
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED"><i>DISABLED</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unreferenced Label</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_LABEL">COMPILER_PB_UNUSED_LABEL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when 
-  encountering a labeled statement which label is never explicitly referenced. 
-  A label is considered to be referenced if its name explicitly appears within 
-  a break or continue statement; for instance the following label would be 
-  considered unreferenced:<br>
-  <code>LABEL: { break; }</code></td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Import</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_IMPORT">COMPILER_PB_UNUSED_IMPORT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for unused import reference.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Local</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_LOCAL">COMPILER_PB_UNUSED_LOCAL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for unused local variables (i.e. variables never read from).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Parameter</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PARAMETER">COMPILER_PB_UNUSED_PARAMETER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning for unused method parameters (i.e. parameters never read from).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Parameter if Implementing Abstract Method</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PARAMETER_WHEN_IMPLEMENTING_ABSTRACT">COMPILER_PB_UNUSED_PARAMETER_WHEN_IMPLEMENTING_ABSTRACT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal unused parameters in
-  abstract method implementations.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Parameter if Overriding Concrete Method</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PARAMETER_WHEN_OVERRIDING_CONCRETE">COMPILER_PB_UNUSED_PARAMETER_WHEN_OVERRIDING_CONCRETE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will signal unused parameters in
-  methods overriding concrete ones.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Consider Reference in Doc Comment for Unused Parameter Check</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PARAMETER_INCLUDE_DOC_COMMENT_REFERENCE">COMPILER_PB_UNUSED_PARAMETER_INCLUDE_DOC_COMMENT_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, the compiler will consider doc comment references to parameters (i.e. @param clauses) for the unused
-	      parameter check. Thus, documented parameters will be considered as mandated as per doc contract.<br>
-	      The severity of the unused parameter problem is controlled with option "org.eclipse.jdt.core.compiler.problem.unusedParameter"<br>.
- 	      Note: this option has no effect until the doc comment support is enabled according to the option "org.eclipse.jdt.core.compiler.doc.comment.support".</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Unused Private Members </b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_PRIVATE_MEMBER">COMPILER_PB_UNUSED_PRIVATE_MEMBER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning
-  whenever a private method or field is declared but never used within the same
-  unit. </td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Presence of Type Arguments for a Non-Generic Method Invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_TYPE_ARGUMENTS_FOR_METHOD_INVOCATION">COMPILER_PB_UNUSED_TYPE_ARGUMENTS_FOR_METHOD_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning 
-  whenever type arguments are encountered for a non-generic method invocation.<br> 
-  Note that prior to compliance level <code>"1.7"</code>, this situation would 
-  automatically result into an error. From Java 7 on, unused type arguments are 
-  tolerated, and optionally warned against.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-
-<tr>
-<td colspan=2><b>Reporting Unnecessary <code>@SuppressWarnings</code></b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_UNUSED_WARNING_TOKEN">COMPILER_PB_UNUSED_WARNING_TOKEN</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning when 
-  encountering a <code>@SuppressWarnings</code> annotation for which no 
-  corresponding warning got detected in the code. This diagnostic is provided 
-  to help developers to get rid of transient <code>@SuppressWarnings</code> that
-  are no longer needed.<br>
-  Note that <code>@SuppressWarnings("all")</code> is still silencing the warning 
-  for unnecessary <code>@SuppressWarnings</code>, as it is the master switch to 
-  silence <em>all</em> warnings.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-<tr>
-
-<td colspan=2><b>Reporting Varargs Argument Needing a Cast in Method/Constructor Inv</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_PB_VARARGS_ARGUMENT_NEED_CAST">COMPILER_PB_VARARGS_ARGUMENT_NEED_CAST</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>When enabled, the compiler will issue an error or a warning whenever a varargs arguments should be cast
-when passed to a method/constructor invocation. (e.g. Class.getMethod(String name, Class ... args )  
-invoked with arguments ("foo", null)).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING"><i>WARNING</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Setting Source Compatibility Mode</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_SOURCE">COMPILER_SOURCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=5>
-Specify the compatibility level of the Java source code.<br>
-Source level "1.4" enables assertions. From "1.4" on, 'assert' is a reserved keyword.<br>
-Source level "1.5" enables generics, autoboxing, covariance, annotations, enumerations
-enhanced for loops, static imports and varargs. From "1.5" on, 'enum' is a reserved 
-keyword.<br>
-The compliance, source and target levels must satisfy a set of constraints summarized 
-in a <a HREF="#compatibility"><b>compatibility table</b></a> below.
-</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_3">VERSION_1_3</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_4">VERSION_1_4</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_5">VERSION_1_5</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_6">VERSION_1_6</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#VERSION_1_7">VERSION_1_7</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Generating Source Debug Attribute</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_SOURCE_FILE_ATTR">COMPILER_SOURCE_FILE_ATTR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When generated, this attribute will enable the debugger to present the corresponding source code.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#GENERATE">GENERATE</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_GENERATE">DO_NOT_GENERATE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Determine whether task tags are case-sensitive</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_CASE_SENSITIVE">COMPILER_TASK_CASE_SENSITIVE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, task tags are considered in a case-sensitive way.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><i>ENABLED</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Automatic Task Priorities</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITIES">COMPILER_TASK_PRIORITIES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1><p>In parallel with the Automatic Task Tags, this list defines the
-  priorities (high, normal or low) of the task markers issued by the
-  compiler.<br>
-  Possible priorities are 
-  "<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITY_HIGH">HIGH</a></b>", 
-  "<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITY_NORMAL">NORMAL</a></b>" or
-  "<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_PRIORITY_LOW">LOW</a></b>".</p></td>
-<td>{&lt;priority&gt;[,&lt;priority&gt;]*}.<br><b><i>Default value is "NORMAL,HIGH,<br>NORMAL"</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Automatic Task Tags</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPILER_TASK_TAGS">COMPILER_TASK_TAGS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the tag list is not empty, the compiler will issue a task 
-  marker whenever it encounters one of the corresponding tags inside any 
-  comment in Java source code. Generated task messages will start with the tag,
-  and range until the next line separator, comment ending, or tag.<br>
-  When a given line of code bears multiple tags, each tag will be reported 
-  separately. Moreover, a tag immediately followed by another tag will be 
-  reported using the contents of the next non-empty tag of the line, if any.<br>
-  Note that tasks messages are trimmed. If a tag is starting with a letter or 
-  digit, then it cannot be leaded by another letter or digit to be recognized 
-  ("fooToDo" will not be recognized as a task for tag "ToDo", but "foo#ToDo"
-  will be detected for either tag "ToDo" or "#ToDo"). Respectively, a tag 
-  ending with a letter or digit cannot be followed by a letter or digit to be 
-  recognized ("ToDofoo" will not be recognized as a task for tag "ToDo", but 
-  "ToDo:foo" will be detected either for tag "ToDo" or "ToDo:").
-</td>
-<td>{&lt;tag&gt;[,&lt;tag&gt;]*}.<br><b><i>Default value is "TODO,FIXME,<br>XXX"</i></b></td>
-</tr>
-</table>
-<a name="compatibility"></a>
-<p>The following table summarizes the compatible combinations of Java compliance, 
-   target and source levels (bold values are the defaults for each compliance level).</p>
-
-<table border="1">
-<tr>                         <th>Compliance</th>               
-                                         <th>Target</th>
-                                                     <th>Source</th></tr>
-<tr>
-   <td valign="top" rowspan="5"><b>1.7</b></td>
-                <td valign="top"><b>1.7</b></td><td><b>1.7</b>, 1.6, 1.5, 1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.6</td><td>1.6, 1.5, 1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.5</td><td>1.5, 1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.4</td><td>1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.3, 1.2, 1.1</td><td>1.3</td></tr>
-<tr>
-   <td valign="top" rowspan="4"><b>1.6</b></td>
-                <td valign="top"><b>1.6</b></td><td><b>1.6</b>, 1.5, 1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.5</td><td>1.5, 1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.4</td><td>1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.3, 1.2, 1.1</td><td>1.3</td></tr>
-<tr>
-   <td valign="top" rowspan="3"><b>1.5</b></td>
-                <td valign="top"><b>1.5</b></td><td><b>1.5</b>, 1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.4</td><td>1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.3, 1.2, 1.1</td><td>1.3</td></tr>
-<tr>
-   <td valign="top" rowspan="2"><b>1.4</b></td>
-                <td valign="top">1.4</td><td>1.4, 1.3</td></tr>
-<tr>            <td valign="top">1.3, <b>1.2</b>, 1.1, cldc1.1</td><td><b>1.3</b></td></tr>
-<tr>
-   <td valign="top"><b>1.3</b></td>
-                <td valign="top">1.3, 1.2, <b>1.1</b>, cldc1.1</td><td><b>1.3</b></td></tr>
-</table>
-
-<H4><a name="builder">Builder options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 WIDTH="100%" >
-
-<tr>
-<th>Description</th>
-<th width=150>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Cleaning Output Folder(s)</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER">CORE_JAVA_BUILD_CLEAN_OUTPUT_FOLDER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate whether the JavaBuilder is allowed to clean the output
-  folders when performing full build operations.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CLEAN"><i>CLEAN</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Duplicate Resources</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_DUPLICATE_RESOURCE">CORE_JAVA_BUILD_DUPLICATE_RESOURCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate the severity of the problem reported when more than one 
-  occurrence of a given resource is to be copied to the output location.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Abort if Invalid Classpath</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_INVALID_CLASSPATH">CORE_JAVA_BUILD_INVALID_CLASSPATH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Instruct the builder to abort if the classpath is invalid.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ABORT"><i>ABORT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Computing Project Build Order</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_ORDER">CORE_JAVA_BUILD_ORDER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate whether JavaCore should enforce the project build order to be based on the classpath prerequisite chain. When requesting to compute, this takes over the platform default order (based on project references).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#COMPUTE">COMPUTE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE">IGNORE</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Recreate Modified class files in Output Folder</b> (<b><a href=
-  "../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_RECREATE_MODIFIED_CLASS_FILES_IN_OUTPUT_FOLDER">CORE_JAVA_BUILD_RECREATE_MODIFIED_CLASS_FILES_IN_OUTPUT_FOLDER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate whether the JavaBuilder should check for any changes to 
-  .class files in the output folders while performing incremental build 
-  operations. If changes are detected to managed .class files, then a full 
-  build is performed, otherwise the changes are left as is. Tools further 
-  altering generated .class files, like optimizers, should ensure this option 
-  remains set to its default state of ignore.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ABORT">ENABLE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Specifying Filters for Resource Copying Control</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_JAVA_BUILD_RESOURCE_COPY_FILTER">CORE_JAVA_BUILD_RESOURCE_COPY_FILTER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>Specify filters to control the resource copy process. (&lt;name&gt; is a file name pattern (only * wild-cards allowed) or the name of a folder which ends with '/';
-  any resource which name matches one or more of these patterns is <em>not</em>
-  copied to the ouput folder.)</td>
-<td>{&lt;name&gt;[,&lt;name&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-</table>
-
-<H4><a name="javacore">JavaCore options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 WIDTH="100%" >
-
-<tr>
-<th>Description</th>
-<th width=120>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Classpath Cycle</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_CIRCULAR_CLASSPATH">CORE_CIRCULAR_CLASSPATH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate the severity of the problem reported when a project is
-  involved in a cycle.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR"><i>ERROR</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Enabling Usage of Classpath Exclusion Patterns</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_ENABLE_CLASSPATH_EXCLUSION_PATTERNS">CORE_ENABLE_CLASSPATH_EXCLUSION_PATTERNS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When set to &quot;disabled&quot;, no entry on a project classpath
-  can be associated with an exclusion or inclusion pattern.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><i>ENABLED</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Enabling Usage of Classpath Multiple Output Locations</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_ENABLE_CLASSPATH_MULTIPLE_OUTPUT_LOCATIONS">CORE_ENABLE_CLASSPATH_MULTIPLE_OUTPUT_LOCATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When set to &quot;disabled&quot;, no entry on a project classpath
-  can be associated with a specific output location. In particular, this 
-  prevents the use of multiple output locations for a single project.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><i>ENABLED</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Default Source Encoding Format</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_ENCODING">CORE_ENCODING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>Get the default encoding format of source files. This value is
-  immutable and preset to the result of 
-  <b><a href="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/ResourcesPlugin.html#getEncoding()">ResourcesPlugin.getEncoding()</a></b>.<br>
-  It is offered as a convenience shortcut only.</td>
-<td><b><i>Immutable, preset to the platform default.</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Reporting Incompatible JDK Level for Required Binaries</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_INCOMPATIBLE_JDK_LEVEL">CORE_INCOMPATIBLE_JDK_LEVEL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Indicate the severity of the problem reported when a project prerequisites another project 
-  or library with an incompatible target JDK level (e.g. project targeting 1.1 vm, but compiled against 1.4 libraries).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR">ERROR</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#IGNORE"><i>IGNORE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Reporting Incomplete Classpath</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CORE_INCOMPLETE_CLASSPATH">CORE_INCOMPLETE_CLASSPATH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Indicate the severity of the problem reported when an entry on the
-  classpath doesn't exist, is not legitimate, or is not visible (e.g. a
-  referenced project is closed).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ERROR"><i>ERROR</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#WARNING">WARNING</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Set the timeout value for retrieving a method's parameter names from javadoc</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#TIMEOUT_FOR_PARAMETER_NAME_FROM_ATTACHED_JAVADOC">TIMEOUT_FOR_PARAMETER_NAME_FROM_ATTACHED_JAVADOC</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Timeout in milliseconds to retrieve a method's parameter names from javadoc.<br>If the value is 0, the parameter names are not fetched and the raw names are returned.</td>
-<td rowspan=2>A positive or null integer.<br>Default is <b><i>"50"</i></b>.</td>
-</tr>
-</table>
-
-<H4><a name="formatter">Formatter options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 WIDTH="100%" >
-<tr>
-<th>Description</th>
-<th width=80>Values</th>
-</tr>
-<tr>
-<td colspan=2><b>Option to align type members of a type declaration on column</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGN_TYPE_MEMBERS_ON_COLUMNS">FORMATTER_ALIGN_TYPE_MEMBERS_ON_COLUMNS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ALLOCATION_EXPRESSION">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ENUM_CONSTANT">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in explicit constructor call</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_EXPLICIT_CONSTRUCTOR_CALL">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_EXPLICIT_CONSTRUCTOR_CALL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_METHOD_INVOCATION">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_METHOD_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of arguments in qualified allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_QUALIFIED_ALLOCATION_EXPRESSION">FORMATTER_ALIGNMENT_FOR_ARGUMENTS_IN_QUALIFIED_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of assignment</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ASSIGNMENT">FORMATTER_ALIGNMENT_FOR_ASSIGNMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, 0, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of binary expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_BINARY_EXPRESSION">FORMATTER_ALIGNMENT_FOR_BINARY_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of compact if</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_COMPACT_IF">FORMATTER_ALIGNMENT_FOR_COMPACT_IF</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_ONE_PER_LINE, INDENT_BY_ONE)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of conditional expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_CONDITIONAL_EXPRESSION">FORMATTER_ALIGNMENT_FOR_CONDITIONAL_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_ONE_PER_LINE, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of enum constants</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_ENUM_CONSTANTS">FORMATTER_ALIGNMENT_FOR_ENUM_CONSTANTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_NO_SPLIT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of expressions in array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_EXPRESSIONS_IN_ARRAY_INITIALIZER">FORMATTER_ALIGNMENT_FOR_EXPRESSIONS_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of multiple fields</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_MULTIPLE_FIELDS">FORMATTER_ALIGNMENT_FOR_MULTIPLE_FIELDS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of parameters in constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_CONSTRUCTOR_DECLARATION">FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of parameters in method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_METHOD_DECLARATION">FORMATTER_ALIGNMENT_FOR_PARAMETERS_IN_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of selector in method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SELECTOR_IN_METHOD_INVOCATION">FORMATTER_ALIGNMENT_FOR_SELECTOR_IN_METHOD_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of superclass in type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SUPERCLASS_IN_TYPE_DECLARATION">FORMATTER_ALIGNMENT_FOR_SUPERCLASS_IN_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_NEXT_SHIFTED, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of superinterfaces in enum declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_ENUM_DECLARATION">FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_ENUM_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of superinterfaces in type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_TYPE_DECLARATION">FORMATTER_ALIGNMENT_FOR_SUPERINTERFACES_IN_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of throws clause in constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_CONSTRUCTOR_DECLARATION">FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option for alignment of throws clause in method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_METHOD_DECLARATION">FORMATTER_ALIGNMENT_FOR_THROWS_CLAUSE_IN_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>values returned by <code>createAlignmentValue(boolean, int, int)</code> call</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>createAlignmentValue(false, WRAP_COMPACT, INDENT_DEFAULT)</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines after the imports declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_AFTER_IMPORTS">FORMATTER_BLANK_LINES_AFTER_IMPORTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines after the package declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_AFTER_PACKAGE">FORMATTER_BLANK_LINES_AFTER_PACKAGE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines at the beginning of the method body</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_AT_BEGINNING_OF_METHOD_BODY">FORMATTER_BLANK_LINES_AT_BEGINNING_OF_METHOD_BODY</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a field declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_FIELD">FORMATTER_BLANK_LINES_BEFORE_FIELD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before the first class body declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_FIRST_CLASS_BODY_DECLARATION">FORMATTER_BLANK_LINES_BEFORE_FIRST_CLASS_BODY_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before the imports declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_IMPORTS">FORMATTER_BLANK_LINES_BEFORE_IMPORTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a member type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_MEMBER_TYPE">FORMATTER_BLANK_LINES_BEFORE_MEMBER_TYPE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_METHOD">FORMATTER_BLANK_LINES_BEFORE_METHOD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before a new chunk</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_NEW_CHUNK">FORMATTER_BLANK_LINES_BEFORE_NEW_CHUNK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines before the package declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BEFORE_PACKAGE">FORMATTER_BLANK_LINES_BEFORE_PACKAGE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines between import groups</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BETWEEN_IMPORT_GROUPS">FORMATTER_BLANK_LINES_BETWEEN_IMPORT_GROUPS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"1"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to add blank lines between type declarations</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BLANK_LINES_BETWEEN_TYPE_DECLARATIONS">FORMATTER_BLANK_LINES_BETWEEN_TYPE_DECLARATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an annotation type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ANNOTATION_TYPE_DECLARATION">FORMATTER_BRACE_POSITION_FOR_ANNOTATION_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an anonymous type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ANONYMOUS_TYPE_DECLARATION">FORMATTER_BRACE_POSITION_FOR_ANONYMOUS_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ARRAY_INITIALIZER">FORMATTER_BRACE_POSITION_FOR_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_BLOCK">FORMATTER_BRACE_POSITION_FOR_BLOCK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a block in a case statement when the block is the first statement following</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_BLOCK_IN_CASE">FORMATTER_BRACE_POSITION_FOR_BLOCK_IN_CASE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_CONSTRUCTOR_DECLARATION">FORMATTER_BRACE_POSITION_FOR_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ENUM_CONSTANT">FORMATTER_BRACE_POSITION_FOR_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of an enum declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_ENUM_DECLARATION">FORMATTER_BRACE_POSITION_FOR_ENUM_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_METHOD_DECLARATION">FORMATTER_BRACE_POSITION_FOR_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a switch statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_SWITCH">FORMATTER_BRACE_POSITION_FOR_SWITCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to position the braces of a type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_BRACE_POSITION_FOR_TYPE_DECLARATION">FORMATTER_BRACE_POSITION_FOR_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=4>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#END_OF_LINE"><i>END_OF_LINE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE">NEXT_LINE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_SHIFTED">NEXT_LINE_SHIFTED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#NEXT_LINE_ON_WRAP">NEXT_LINE_ON_WRAP</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether blank lines are cleared inside block comments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_CLEAR_BLANK_LINES_IN_BLOCK_COMMENT">FORMATTER_COMMENT_CLEAR_BLANK_LINES_IN_BLOCK_COMMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether blank lines are cleared inside javadoc comments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_CLEAR_BLANK_LINES_IN_JAVADOC_COMMENT">FORMATTER_COMMENT_CLEAR_BLANK_LINES_IN_JAVADOC_COMMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether multiple line comments are formatted</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_BLOCK_COMMENT">FORMATTER_COMMENT_FORMAT_BLOCK_COMMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether javadoc comments are formatted</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_JAVADOC_COMMENT">FORMATTER_COMMENT_FORMAT_JAVADOC_COMMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether single line comments are formatted</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_LINE_COMMENT">FORMATTER_COMMENT_FORMAT_LINE_COMMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether the header comment of a Java source file is formatted</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_HEADER">FORMATTER_COMMENT_FORMAT_HEADER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether HTML tags are formatted.</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_HTML">FORMATTER_COMMENT_FORMAT_HTML</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether code snippets are formatted in comments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_FORMAT_SOURCE">FORMATTER_COMMENT_FORMAT_SOURCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether description of Javadoc parameters are indented</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INDENT_PARAMETER_DESCRIPTION">FORMATTER_COMMENT_INDENT_PARAMETER_DESCRIPTION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to control whether Javadoc root tags are indented.</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INDENT_ROOT_TAGS">FORMATTER_COMMENT_INDENT_ROOT_TAGS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert an empty line before the Javadoc root tag block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INSERT_EMPTY_LINE_BEFORE_ROOT_TAGS">FORMATTER_COMMENT_INSERT_EMPTY_LINE_BEFORE_ROOT_TAGS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after Javadoc root tag parameters</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_INSERT_NEW_LINE_FOR_PARAMETER">FORMATTER_COMMENT_INSERT_NEW_LINE_FOR_PARAMETER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the line length for comments.</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMMENT_LINE_LENGTH">FORMATTER_COMMENT_LINE_LENGTH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"80"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to compact else/if</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_COMPACT_ELSE_IF">FORMATTER_COMPACT_ELSE_IF</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to set the continuation indentation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_CONTINUATION_INDENTATION">FORMATTER_CONTINUATION_INDENTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"2"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to set the continuation indentation inside array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_CONTINUATION_INDENTATION_FOR_ARRAY_INITIALIZER">FORMATTER_CONTINUATION_INDENTATION_FOR_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"2"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing annotation declaration header</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ANNOTATION_DECLARATION_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ANNOTATION_DECLARATION_HEADER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing enum constant header</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_CONSTANT_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_CONSTANT_HEADER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing enum declaration header</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_DECLARATION_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_ENUM_DECLARATION_HEADER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent body declarations compare to its enclosing type header</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_TYPE_HEADER">FORMATTER_INDENT_BODY_DECLARATIONS_COMPARE_TO_TYPE_HEADER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent breaks compare to cases</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_BREAKS_COMPARE_TO_CASES">FORMATTER_INDENT_BREAKS_COMPARE_TO_CASES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent empty lines</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_EMPTY_LINES">FORMATTER_INDENT_EMPTY_LINES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent statements inside a block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BLOCK">FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BLOCK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent statements inside the body of a method or a constructor</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BODY">FORMATTER_INDENT_STATEMENTS_COMPARE_TO_BODY</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent switch statements compare to cases</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_CASES">FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_CASES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent switch statements compare to switch</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_SWITCH">FORMATTER_INDENT_SWITCHSTATEMENTS_COMPARE_TO_SWITCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the equivalent number of spaces that represents one indentation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INDENTATION_SIZE">FORMATTER_INDENTATION_SIZE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"4"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after an annotation on a member (package, class, method, field declaration)</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_MEMBER">FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_MEMBER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after an annotation on a parameter</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_PARAMETER">FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_PARAMETER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after an annotation on a local variable</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_LOCAL_VARIABLE">FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_LOCAL_VARIABLE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line after the opening brace in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_NEW_LINE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line at the end of the current file if missing</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_AT_END_OF_FILE_IF_MISSING">FORMATTER_INSERT_NEW_LINE_AT_END_OF_FILE_IF_MISSING</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the catch keyword in try statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_CATCH_IN_TRY_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_CATCH_IN_TRY_STATEMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the closing brace in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_NEW_LINE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the else keyword in if statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_ELSE_IN_IF_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_ELSE_IN_IF_STATEMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before the finally keyword in try statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_FINALLY_IN_TRY_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_FINALLY_IN_TRY_STATEMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line before while in do statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_BEFORE_WHILE_IN_DO_STATEMENT">FORMATTER_INSERT_NEW_LINE_BEFORE_WHILE_IN_DO_STATEMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty annotation declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANNOTATION_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANNOTATION_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty anonymous type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANONYMOUS_TYPE_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ANONYMOUS_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_BLOCK">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_BLOCK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_CONSTANT">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty enum declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_ENUM_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty method body</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_METHOD_BODY">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_METHOD_BODY</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a new line in an empty type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_NEW_LINE_IN_EMPTY_TYPE_DECLARATION">FORMATTER_INSERT_NEW_LINE_IN_EMPTY_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after and in wilcard</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_AND_IN_TYPE_PARAMETER">FORMATTER_INSERT_SPACE_AFTER_AND_IN_TYPE_PARAMETER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after an assignment operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_ASSIGNMENT_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_ASSIGNMENT_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after at in annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION">FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after at in annotation type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_AFTER_AT_IN_ANNOTATION_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after a binary operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_BINARY_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_BINARY_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing angle bracket in type arguments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing angle bracket in type parameters</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing brace of a block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_BRACE_IN_BLOCK">FORMATTER_INSERT_SPACE_AFTER_CLOSING_BRACE_IN_BLOCK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the closing parenthesis of a cast expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_CLOSING_PAREN_IN_CAST">FORMATTER_INSERT_SPACE_AFTER_CLOSING_PAREN_IN_CAST</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the colon in an assert statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_ASSERT">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_ASSERT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after colon in a case statement when a opening brace follows the colon</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CASE">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CASE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the colon in a conditional expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_CONDITIONAL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after colon in a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_FOR">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_FOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the colon in a labeled statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COLON_IN_LABELED_STATEMENT">FORMATTER_INSERT_SPACE_AFTER_COLON_IN_LABELED_STATEMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in an allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ANNOTATION">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the parameters of a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the exception names in a throws clause of a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the arguments of an enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_CONSTANT_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_CONSTANT_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in enum declarations</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_DECLARATIONS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_ENUM_DECLARATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the arguments of an explicit constructor call</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the increments of a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INCREMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INCREMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the initializations of a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INITS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_FOR_INITS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the parameters of a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the exception names in a throws clause of a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_DECLARATION_THROWS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in the arguments of a method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_INVOCATION_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_METHOD_INVOCATION_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in multiple field declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in multiple local declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in parameterized type reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in superinterfaces names of a type header</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_SUPERINTERFACES">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_SUPERINTERFACES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in type arguments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the comma in type parameters</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_COMMA_IN_TYPE_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after ellipsis</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_ELLIPSIS">FORMATTER_INSERT_SPACE_AFTER_ELLIPSIS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening angle bracket in parameterized type reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening angle bracket in type arguments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening angle bracket in type parameters</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_AFTER_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening brace in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACE_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening bracket inside an array allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening bracket inside an array reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_REFERENCE">FORMATTER_INSERT_SPACE_AFTER_OPENING_BRACKET_IN_ARRAY_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ANNOTATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a cast expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CAST">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CAST</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a catch</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CATCH">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CATCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_FOR">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_FOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in an if statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_IF">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_IF</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_METHOD_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a parenthesized expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a switch statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SWITCH">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SWITCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a synchronized statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SYNCHRONIZED">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_SYNCHRONIZED</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after the opening parenthesis in a while statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_WHILE">FORMATTER_INSERT_SPACE_AFTER_OPENING_PAREN_IN_WHILE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after a postfix operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_POSTFIX_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_POSTFIX_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after a prefix operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_PREFIX_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_PREFIX_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after question mark in a conditional expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_CONDITIONAL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after question mark in a wildcard</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_WILDCARD">FORMATTER_INSERT_SPACE_AFTER_QUESTION_IN_WILDCARD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after semicolon in a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_SEMICOLON_IN_FOR">FORMATTER_INSERT_SPACE_AFTER_SEMICOLON_IN_FOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space after an unary operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_AFTER_UNARY_OPERATOR">FORMATTER_INSERT_SPACE_AFTER_UNARY_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before and in wildcard</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_AND_IN_TYPE_PARAMETER">FORMATTER_INSERT_SPACE_BEFORE_AND_IN_TYPE_PARAMETER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before an assignment operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_ASSIGNMENT_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_ASSIGNMENT_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before at in annotation type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_AT_IN_ANNOTATION_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_AT_IN_ANNOTATION_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before an binary operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_BINARY_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_BINARY_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing angle bracket in parameterized type reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing angle bracket in type arguments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing angle bracket in type parameters</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing brace in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACE_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing bracket in an array allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing bracket in an array reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_BRACKET_IN_ARRAY_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ANNOTATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a cast expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CAST">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CAST</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a catch</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CATCH">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CATCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_FOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in an if statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_IF">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_IF</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_METHOD_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a parenthesized expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_PARENTHESIZED_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_PARENTHESIZED_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a switch statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SWITCH">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SWITCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a synchronized statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SYNCHRONIZED">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_SYNCHRONIZED</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the closing parenthesis in a while statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_WHILE">FORMATTER_INSERT_SPACE_BEFORE_CLOSING_PAREN_IN_WHILE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in an assert statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_ASSERT">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_ASSERT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a case statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CASE">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CASE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a conditional expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_CONDITIONAL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a default statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_DEFAULT">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_DEFAULT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_FOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before colon in a labeled statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_LABELED_STATEMENT">FORMATTER_INSERT_SPACE_BEFORE_COLON_IN_LABELED_STATEMENT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in an allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ANNOTATION">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the parameters of a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the exception names of the throws clause of a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_CONSTRUCTOR_DECLARATION_THROWS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the arguments of enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_CONSTANT_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_CONSTANT_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in enum declarations</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_DECLARATIONS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_ENUM_DECLARATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the arguments of an explicit constructor call</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_EXPLICIT_CONSTRUCTOR_CALL_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the increments of a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INCREMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INCREMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the initializations of a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INITS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_FOR_INITS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the parameters of a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the exception names of the throws clause of a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_THROWS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_DECLARATION_THROWS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the arguments of a method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_INVOCATION_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_METHOD_INVOCATION_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in a multiple field declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_FIELD_DECLARATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in a multiple local declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_MULTIPLE_LOCAL_DECLARATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in parameterized type reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_PARAMETERIZED_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in the superinterfaces names in a type header</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_SUPERINTERFACES">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_SUPERINTERFACES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in type arguments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before comma in type parameters</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_COMMA_IN_TYPE_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before ellipsis</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_ELLIPSIS">FORMATTER_INSERT_SPACE_BEFORE_ELLIPSIS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening angle bracket in parameterized type reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_PARAMETERIZED_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening angle bracket in type arguments</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS">FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_ARGUMENTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening angle bracket in type parameters</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS">FORMATTER_INSERT_SPACE_BEFORE_OPENING_ANGLE_BRACKET_IN_TYPE_PARAMETERS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an annotation type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANNOTATION_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANNOTATION_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an anonymous type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANONYMOUS_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ANONYMOUS_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a block</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_BLOCK">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_BLOCK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in an enum declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_ENUM_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a switch statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_SWITCH">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_SWITCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening brace in a type declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_TYPE_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACE_IN_TYPE_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening bracket in an array allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening bracket in an array reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening bracket in an array type reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_BRACKET_IN_ARRAY_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in annotation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in annotation type member declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION_TYPE_MEMBER_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ANNOTATION_TYPE_MEMBER_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a catch</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CATCH">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CATCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_FOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in an if statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_IF">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_IF</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_METHOD_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a parenthesized expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_PARENTHESIZED_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a switch statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SWITCH">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SWITCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a synchronized statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SYNCHRONIZED">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_SYNCHRONIZED</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before the opening parenthesis in a while statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_WHILE">FORMATTER_INSERT_SPACE_BEFORE_OPENING_PAREN_IN_WHILE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before parenthesized expression in return statement
-  </b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_PARENTHESIZED_EXPRESSION_IN_RETURN">FORMATTER_INSERT_SPACE_BEFORE_PARENTHESIZED_EXPRESSION_IN_RETURN</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before parenthesized expression in throw statement
-  </b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_PARENTHESIZED_EXPRESSION_IN_THROW">FORMATTER_INSERT_SPACE_BEFORE_PARENTHESIZED_EXPRESSION_IN_THROW</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before a postfix operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_POSTFIX_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_POSTFIX_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before a prefix operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_PREFIX_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_PREFIX_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before question mark in a conditional expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_CONDITIONAL">FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_CONDITIONAL</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT"><i>INSERT</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT">DO_NOT_INSERT</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before question mark in a wildcard</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_WILDCARD">FORMATTER_INSERT_SPACE_BEFORE_QUESTION_IN_WILDCARD</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before semicolon</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON">FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before semicolon in for statement</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON_IN_FOR">FORMATTER_INSERT_SPACE_BEFORE_SEMICOLON_IN_FOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space before unary operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BEFORE_UNARY_OPERATOR">FORMATTER_INSERT_SPACE_BEFORE_UNARY_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between brackets in an array type reference</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_BRACKETS_IN_ARRAY_TYPE_REFERENCE">FORMATTER_INSERT_SPACE_BETWEEN_BRACKETS_IN_ARRAY_TYPE_REFERENCE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty braces in an array initializer</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACES_IN_ARRAY_INITIALIZER">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACES_IN_ARRAY_INITIALIZER</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty brackets in an array allocation expression</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACKETS_IN_ARRAY_ALLOCATION_EXPRESSION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_BRACKETS_IN_ARRAY_ALLOCATION_EXPRESSION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in an annotation type member declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ANNOTATION_TYPE_MEMBER_DECLARATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ANNOTATION_TYPE_MEMBER_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in a constructor declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_CONSTRUCTOR_DECLARATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_CONSTRUCTOR_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in enum constant</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ENUM_CONSTANT">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_ENUM_CONSTANT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in a method declaration</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_DECLARATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_DECLARATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to insert a space between empty parenthesis in a method invocation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_INVOCATION">FORMATTER_INSERT_SPACE_BETWEEN_EMPTY_PARENS_IN_METHOD_INVOCATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#INSERT">INSERT</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DO_NOT_INSERT"><i>DO_NOT_INSERT</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep else statement on the same line</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_ELSE_STATEMENT_ON_SAME_LINE">FORMATTER_KEEP_ELSE_STATEMENT_ON_SAME_LINE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep empty array initializer one one line</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_EMPTY_ARRAY_INITIALIZER_ON_ONE_LINE">FORMATTER_KEEP_EMPTY_ARRAY_INITIALIZER_ON_ONE_LINE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep guardian clause on one line</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_GUARDIAN_CLAUSE_ON_ONE_LINE">FORMATTER_KEEP_GUARDIAN_CLAUSE_ON_ONE_LINE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep simple if statement on the one line</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_SIMPLE_IF_ON_ONE_LINE">FORMATTER_KEEP_SIMPLE_IF_ON_ONE_LINE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to keep then statement on the same line</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_KEEP_THEN_STATEMENT_ON_SAME_LINE">FORMATTER_KEEP_THEN_STATEMENT_ON_SAME_LINE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the length of the page. Beyond this length, the formatter will try to split the code</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_LINE_SPLIT">FORMATTER_LINE_SPLIT</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"80"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent block comments that start on the first column</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_NEVER_INDENT_BLOCK_COMMENTS_ON_FIRST_COLUMN">FORMATTER_NEVER_INDENT_BLOCK_COMMENTS_ON_FIRST_COLUMN</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to indent line comments that start on the first column</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_NEVER_INDENT_LINE_COMMENTS_ON_FIRST_COLUMN">FORMATTER_NEVER_INDENT_LINE_COMMENTS_ON_FIRST_COLUMN</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the number of empty lines to preserve</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_NUMBER_OF_EMPTY_LINES_TO_PRESERVE">FORMATTER_NUMBER_OF_EMPTY_LINES_TO_PRESERVE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"0"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify whether or not empty statement should be on a new line</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_PUT_EMPTY_STATEMENT_ON_NEW_LINE">FORMATTER_PUT_EMPTY_STATEMENT_ON_NEW_LINE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the tabulation size</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_TAB_CHAR">FORMATTER_TAB_CHAR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=3>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#TAB"><i>TAB</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#SPACE">SPACE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#MIXED">MIXED</a></b></td>
-</tr>
-<tr>
-<td colspan=2><b>Option to specify the equivalent number of spaces that represents one tabulation</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_TAB_SIZE">FORMATTER_TAB_SIZE</a></b>)</td>
-</tr>
-<tr valign="top">
-<td>Possible value</td>
-<td>"&lt;n&gt;", where n is zero or a positive integer</td>
-</tr>
-<tr valign="top">
-<td>Default value</td>
-<td>"4"</td>
-</tr>
-<tr>
-<td colspan=2><b>Option to use tabulations only for leading indentations</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_USE_TABS_ONLY_FOR_LEADING_INDENTATIONS">FORMATTER_USE_TABS_ONLY_FOR_LEADING_INDENTATIONS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE">TRUE</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE"><i>FALSE</i></a></b></td>
-</tr>
-<tr><td colspan=2><b>Option to wrap before the binary operator</b> (<b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FORMATTER_WRAP_BEFORE_BINARY_OPERATOR">FORMATTER_WRAP_BEFORE_BINARY_OPERATOR</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>Possible values</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#TRUE"><i>TRUE</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/formatter/DefaultCodeFormatterConstants.html#FALSE">FALSE</a></b></td>
-</tr>
-</table>
-
-<H4><a name="codeassist">CodeAssist options</a></h4>
-
-<table BORDER CELLSPACING=2 CELLPADDING=2 WIDTH="100%" >
-<tr>
-<th>Description</th>
-<th width=80>Values</th>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Argument Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_ARGUMENT_PREFIXES">CODEASSIST_ARGUMENT_PREFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for argument name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Argument Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_ARGUMENT_SUFFIXES">CODEASSIST_ARGUMENT_SUFFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for argument name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Camel Case Sensitive Completion</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_CAMEL_CASE_MATCH">CODEASSIST_CAMEL_CASE_MATCH</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, completion shows proposals whose name match the 
-  CamelCase pattern.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED"><i>ENABLED</i></a></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Deprecation Sensitive Completion</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_DEPRECATION_CHECK">CODEASSIST_DEPRECATION_CHECK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, completion doesn't propose deprecated members and types.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Discouraged Reference Sensitive Completion</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_DISCOURAGED_REFERENCE_CHECK">CODEASSIST_DISCOURAGED_REFERENCE_CHECK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, completion doesn't propose elements which match a
-  discouraged reference rule.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Field Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_FIELD_PREFIXES">CODEASSIST_FIELD_PREFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for field name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Field Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_FIELD_SUFFIXES">CODEASSIST_FIELD_SUFFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for field name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Forbidden Reference Sensitive Completion</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_FORBIDDEN_REFERENCE_CHECK">CODEASSIST_FORBIDDEN_REFERENCE_CHECK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, completion doesn't propose elements which match a
-  forbidden reference rule.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Automatic Qualification of Implicit Members</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_IMPLICIT_QUALIFICATION">CODEASSIST_IMPLICIT_QUALIFICATION</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, completion automatically qualifies completion on implicit field references and message expressions.</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Local Variable Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_LOCAL_PREFIXES">CODEASSIST_LOCAL_PREFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for local variable name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Local Variable Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_LOCAL_SUFFIXES">CODEASSIST_LOCAL_SUFFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for local variable name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Prefixes for Static Field Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_STATIC_FIELD_PREFIXES">CODEASSIST_STATIC_FIELD_PREFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the prefixes is non empty, completion for static field name will
-  begin with one of the proposed prefixes.</td>
-<td>{&lt;prefix&gt;[,&lt;prefix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Define the Suffixes for Static Field Name</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_STATIC_FIELD_SUFFIXES">CODEASSIST_STATIC_FIELD_SUFFIXES</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=1>When the suffixes is non empty, completion for static field name will end
-  with one of the proposed suffixes.</td>
-<td>{&lt;suffix&gt;[,&lt;suffix&gt;]*}.<br><b><i>Default value is ""</i></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Suggestion of Static Import</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_SUGGEST_STATIC_IMPORTS">CODEASSIST_SUGGEST_STATIC_IMPORTS</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, completion proposals can contain static import pattern.</td>
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></i></b></td>
-</tr>
-<tr valign="top">
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></b></td>
-</tr>
-
-<tr>
-<td colspan=2><b>Activate Visibility Sensitive Completion</b> (<b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#CODEASSIST_VISIBILITY_CHECK">CODEASSIST_VISIBILITY_CHECK</a></b>)</td>
-</tr>
-<tr valign="top">
-<td rowspan=2>When enabled, completion doesn't propose elements that are not
-  visible at the insertion point according to Java visibility rules (e.g. the 
-  private methods of a super class are not proposed).</td>
-<td><b><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#ENABLED">ENABLED</a></b></td>
-</tr>
-<tr valign="top">
-<td><b><i><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html#DISABLED">DISABLED</a></i></b></td>
-</tr>
-
-</table>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm
deleted file mode 100644
index 96083a8..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_prompter.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Creating Java specific prompter dialogs</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h3>Creating Java specific prompter dialogs</h3>
-<p> The following snippet uses the <b><a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html">JavaUI</a> </b>class to open the Open Type dialog:</p>
-<pre><font color="#4444cc">    public IType selectType() throws JavaModelException {
-        Shell parent = ...;
-        SelectionDialog dialog= JavaUI.createTypeDialog(
-            parent, new ProgressMonitorDialog(parent),
-            SearchEngine.createWorkspaceScope(),
-            IJavaElementSearchConstants.CONSIDER_ALL_TYPES, false);
-        dialog.setTitle(&quot;My Dialog Title&quot;);
-        dialog.setMessage(&quot;My Dialog Message&quot;);
-        if (dialog.open() == IDialogConstants.CANCEL_ID)
-            return null;
-
-        Object[] types= dialog.getResult();
-        if (types == null || types.length == 0)
-            return null;
-        return (IType)types[0];
-    }</font></pre>
-<p> <a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html"><b>JavaUI</b></a> 
-  provides additional methods for creating Open Package and Open Main Type dialogs. 
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm
deleted file mode 100644
index 4e7169f..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_render.htm
+++ /dev/null

@@ -1,114 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Presenting Java elements in a JFace viewer</title>
-</head>
-<body>
-<h2>Presenting Java elements in a JFace viewer</h2>
-<p> The JDT UI API provides classes that allow you to present the Java model or parts 
-  of it in a standard JFace viewer. This functionality is provided primarily by: 
-</p>
-<ul>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/StandardJavaElementContentProvider.html"> 
-    <b> 
-    StandardJavaElementContentProvider</b></a>  - translates the Java element hierarchy 
-    into a data structure accessible by a tree, table or list viewer</li>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/JavaElementLabelProvider.html"> 
-    <b> 
-    JavaElementLabelProvider</b></a>  - provides corresponding images and labels 
-    for a standard JFace viewer</li>
-	<li><a
-		href="../reference/api/org/eclipse/jdt/ui/JavaElementLabels.html"><b>JavaElementLabels</b></a> - provides corresponding text labels for Java elements</li>
-</ul>
-<p>Content and label providers for JFace viewers are described in detail in <a href="../../org.eclipse.platform.doc.isv/guide/jface_viewers.htm" class="XRef">JFace
-viewers</a>.</p>
-If you understand the basic platform mechanism, then putting the Java content
-and label providers together is quite simple:
-<pre><font color="#4444cc">    ...
-    TreeViewer viewer= new TreeViewer(parent);
-    // Provide members of a compilation unit or class file
-    ITreeContentProvider contentProvider= new StandardJavaElementContentProvider(true);
-    viewer.setContentProvider(contentProvider);
-    // There are more flags defined in class JavaElementLabelProvider
-    ILabelProvider labelProvider= new JavaElementLabelProvider(
-        JavaElementLabelProvider.SHOW_DEFAULT |
-        JavaElementLabelProvider.SHOW_QUALIFIED |
-        JavaElementLabelProvider.SHOW_ROOT);
-    viewer.setLabelProvider(labelProvider);
-    // Using the Java model as the viewers input present Java projects on the first level.
-    viewer.setInput(JavaCore.create(ResourcesPlugin.getWorkspace().getRoot()));
-    ...</font></pre>
-<p>The example above uses a Java model (<a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b>IJavaModel</b></a>)
-as the input element for the viewer.&nbsp; The <a href="../reference/api/org/eclipse/jdt/ui/StandardJavaElementContentProvider.html"><b>StandardJavaElementContentProvider</b></a>
-also supports <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-      IJavaProject</b></a>, <a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html"><b> 
-      IPackageFragmentRoot</b></a>, <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a>, and <b>IFolder</b> as input elements: 
-</p>
-<h3>Overlaying images with Java information</h3>
-        <p><a href="../reference/api/org/eclipse/jdt/ui/JavaElementImageDescriptor.html"><b> 
-    JavaElementImageDescriptor</b></a> can be used to create an image based on an 
-    arbitrary base image descriptor and a set of flags specifying which Java specific 
-    adornments (e.g. static, final, synchronized, ....) are to be superimposed 
-    on the image.</p>
-<h3>Adding problem and override decorators</h3>
-When a viewer is supposed to include problem annotations, the JFace <b>DecoratingLabelProvider</b> 
-together with the <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html"> 
-<b> 
-ProblemsLabelDecorator</b></a> is used. The snippet below illustrates the use of
-a problem label decorator.
-<pre><font color="#4444cc">    ...
-    DecoratingLabelProvider decorator= new DecoratingLabelProvider(labelProvider, new ProblemsLabelDecorator());
-    viewer.setLabelProvider(decorator);
-    ...</font></pre>
-<p> In the same way the <a href="../reference/api/org/eclipse/jdt/ui/OverrideIndicatorLabelDecorator.html"> 
-  <b> 
-  OverrideIndicatorLabelDecorator</b></a> can be used to decorate a normal label provider 
-  to show the implement and override indicators for methods. </p>
-<h3>Updating the presentation on model changes</h3>
-<p> Neither the <a href="../reference/api/org/eclipse/jdt/ui/OverrideIndicatorLabelDecorator.html"><b> 
-  OverrideIndicatorLabelDecorator</b></a><b> </b>nor the <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html"><b> 
-ProblemsLabelDecorator</b></a><b> </b>listen to model changes. Hence, the viewer doesn't update its presentation if 
-  the Java or resource marker model changes. The reason for pushing the update 
-  onto the client for these classes is that there isn't yet a generic implementation 
-  that fulfills all performance concerns. Handling Java model delta inspection 
-  and viewer refreshing in each label decorator or provider would lead to multiple 
-  delta inspections and unnecessary viewer updates.</p>
-<p> So what does the client need to do in order to update their viewers ?</p>
-<ul>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/OverrideIndicatorLabelDecorator.html"><b> 
-  OverrideIndicatorLabelDecorator</b></a>: the client must listen to 
-    Java model changes (see <a href="jdt_api_manip.htm#javadeltas">Responding to
-    changes in Java elements</a>) 
-    and decide if the change(s) described by the delta invalidates the override 
-    indicator of elements presented in the viewer. If so, the class inspecting 
-    the delta should trigger a repaint of the corresponding Java elements using 
-    the standard JFace viewer API (see update methods on StructuredViewer).</li>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html"><b> 
-ProblemsLabelDecorator</b></a>: the client should listen to changes 
-    notified by the decorator via a <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.ProblemsLabelChangedEvent.html"> 
-    <b> 
-    ProblemsLabelChangedEvent</b></a> (see also <a href="../reference/api/org/eclipse/jdt/ui/ProblemsLabelDecorator.html#addListener(org.eclipse.jface.viewers.ILabelProviderListener)"> 
-    <b> 
-    ProblemsLabelDecorator.addListener</b></a> ). Since the marker model is resource 
-    based, the listener has to map the resource notifications to its underlying 
-    data model. For an example showing how to do this for viewers presenting Java 
-    elements see the internal classes <code>ProblemTreeViewer.handleLabelProviderChanged.</code></li>
-</ul>
-<p> For the same reasons enumerated for label decorators the <a href="../reference/api/org/eclipse/jdt/ui/StandardJavaElementContentProvider.html"><b>StandardJavaElementContentProvider</b></a>
-  doesn't listen to model changes. If the viewer needs to update its presentation 
-  according to Java model changes, then the client should add a corresponding 
-  listener to JavaCore. If the change described by the delta invalidates the structure 
-  of the elements presented in the viewer then the client should update the viewer 
-  using the standard JFace API (see refresh methods on StructuredViewer, and the 
-  add and remove methods on TableViewer and AbstractTreeViewer). </p>
-<h3>Sorting the viewer</h3>
-<p> <a href="../reference/api/org/eclipse/jdt/ui/JavaElementSorter.html"><b> 
-    JavaElementSorter</b></a> can be plugged into a JFace viewer to sort Java elements 
-    according to the Java UI sorting style. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm
deleted file mode 100644
index 1c502b0..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_run.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-     
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Running a Java program</title>
-          
-  <link rel="stylesheet" type="text/css" href="../book.css">
-</head>
- <body>
-<h2>Running a Java program</h2>
-<p> The JDT Debug component includes facilities for launching a Java program using the 
-VM install that is currently configured by the user for a Java project.&nbsp;&nbsp;</p>
-<h3> Launching a compiled Java program</h3>
-<p> Java programs that have been compiled in a Java project can be run by 
-getting the appropriate <a href="../reference/api/org/eclipse/jdt/launching/IVMRunner.html"><b>
- IVMRunner</b></a>
-  for the Java project and running the class by name. The following code
-snippet shows how the class <b>MyClass</b> inside <b>myJavaProject</b> can
-be launched.</p>
-<pre>
-<font color="#4444cc">
-   IVMInstall vmInstall = JavaRuntime.getVMInstall(myJavaProject);
-   if (vmInstall == null)
-      vmInstall = JavaRuntime.getDefaultVMInstall();
-   if (vmInstall != null) {
-      IVMRunner vmRunner = vmInstall.getVMRunner(ILaunchManager.RUN_MODE);
-      if (vmRunner != null) {
-         String[] classPath = null;
-         try {
-            classPath = JavaRuntime.computeDefaultRuntimeClassPath(myJavaProject);
-         } catch (CoreException e) { }
-         if (classPath != null) {
-            VMRunnerConfiguration vmConfig = 
-               new VMRunnerConfiguration(&quot;MyClass&quot;, classPath);
-            ILaunch launch = new Launch(null, ILaunchManager.RUN_MODE, null);
-            vmRunner.run(vmConfig, launch, null);
-         }
-      }
-   }
-</font>
-</pre>
-<p> Another way to launch a Java program is to create a <b>Java application</b>
-  launch configuration, and launch it. The following snippet shows how the 
-class <b>MyClass</b> inside <b> myJavaProject</b> can be launched using a 
-simple launch configuration. By default, the resulting running application
- uses the JRE and classpath associated with <b>myJavaProject</b>. </p>
-<pre><font color="#4444cc">
-   ILaunchManager manager = DebugPlugin.getDefault().getLaunchManager();
-   ILaunchConfigurationType type = manager.getLaunchConfigurationType(IJavaLaunchConfigurationConstants.ID_JAVA_APPLICATION);
-   ILaunchConfigurationWorkingCopy wc = type.newInstance(null, &quot;SampleConfig&quot;);
-   wc.setAttribute(IJavaLaunchConfigurationConstants.ATTR_PROJECT_NAME, &quot;myJavaProject&quot;);
-   wc.setAttribute(IJavaLaunchConfigurationConstants.ATTR_MAIN_TYPE_NAME, &quot;myClass&quot;);
-   ILaunchConfiguration config = wc.doSave();	
-   config.launch(ILaunchManager.RUN_MODE, null);
-</font>
-</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm
deleted file mode 100644
index e230ba0..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_search.htm
+++ /dev/null

@@ -1,287 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><html lang="en"><head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Using the Java search engine</title>
-
-
-<link rel="stylesheet" type="text/css" href="../book.css"></head>
-<body>
-<h2>Using the Java search engine</h2>
-<p> Your plug-in can use the JDT API to search Java projects in the workspace
-for Java elements, such as method references, field declarations, implementors
-of an interface, etc. </p>
-<p>
-The entry point for Java search is the <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html">SearchEngine</a></b> class. You can search for particular
-patterns inside a Java element and scope the search to specific elements.&nbsp;
-Search patterns can be created using <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createPattern(org.eclipse.jdt.core.IJavaElement, int)">createPattern</a></b>.&nbsp;
-A pattern is scoped using <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#createJavaSearchScope(org.eclipse.jdt.core.IJavaElement[])">createJavaSearchScope</a></b>.&nbsp;
-Once a pattern and scope are defined, the <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#search(org.eclipse.jdt.core.search.SearchPattern, org.eclipse.jdt.core.search.SearchParticipant[], org.eclipse.jdt.core.search.IJavaSearchScope, org.eclipse.jdt.core.search.SearchRequestor, org.eclipse.core.runtime.IProgressMonitor)">search</a></b>
- method is used to collect the results. </p>
-
-<p>
-Search results are reported to a  <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html">SearchRequestor</a></b> which you must
-extend in order to access the results. </p>
-
-<h3>
-Preparing for search</h3>
-<p> A search operation will use both a pattern for describing the nature
-of the search, and a scope for restraining the range of investigation. </p>
-
-<h4>
-Creating a Java search pattern
-</h4>
-<p>
-A search pattern defines how search results are found. You can either create a search pattern from a Java element (see
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createPattern(org.eclipse.jdt.core.IJavaElement, int)">createPatternPattern(IJavaElement element, int limitTo)</a></b>) 
-or from a string (see <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createPattern(java.lang.String, int, int, int)">createPattern(String, int, int, int)</a></b>.)
-The last method supports wildcards (i.e. '*') and can be used to widen the search results.</p>
-<p>
-For example, creating a search pattern for searching for references to a given method is done as follows:</p>
-<pre><font color="#4444cc">
-    // Get the method
-    IMethod method = ...;
-    
-    // Create search pattern
-    SearchPattern pattern = SearchPattern.createPattern(method, IJavaSearchConstants.REFERENCES);
-</font></pre>
-<p>
-Or creating a search pattern for searching for declarations of all types starting with "Obj":</p>
-<pre><font color="#4444cc">
-    // Create search pattern
-    SearchPattern pattern = SearchPattern.createPattern(&quot;Obj*&quot;, IJavaSearchConstants.TYPE, IJavaSearchConstants.DECLARATIONS, SearchPattern.R_PATTERN_MATCH | SearchPattern.R_CASE_SENSITIVE);
-</font></pre>
-<p>
-The following search patterns are supported:
-</p><ul>
-<li>Package declarations</li>
-<li>Type declarations</li>
-<li>Field declarations</li>
-<li>Method (and constructor) declarations</li>
-<li>Package references</li>
-<li>Type references</li>
-<li>Interface implementors</li>
-<li>Field references</li>
-<li>Field write accesses</li>
-<li>Field read accesses</li>
-<li>Method (and constructor) references</li>
-<li>Combinations of the above patterns using the OR pattern (see
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#createOrPattern(org.eclipse.jdt.core.search.SearchPattern, org.eclipse.jdt.core.search.SearchPattern)">createOrPattern</a></b>)</li>
-</ul>
-<p>
-Note that these patterns are created using the following possible rules:
-</p>
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_EXACT_MATCH">R_EXACT_MATCH</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_PREFIX_MATCH">R_PREFIX_MATCH</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_PATTERN_MATCH">R_PATTERN_MATCH</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_REGEXP_MATCH">R_REGEXP_MATCH</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_CAMELCASE_MATCH">R_CAMELCASE_MATCH</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_CAMELCASE_SAME_PART_COUNT_MATCH">R_CAMELCASE_SAME_PART_COUNT_MATCH</a></b></li>
-</ul>
-which may be also combined with one of the following flags:
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_CASE_SENSITIVE">R_CASE_SENSITIVE</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_ERASURE_MATCH">R_ERASURE_MATCH</a></b></li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/SearchPattern.html#R_EQUIVALENT_MATCH">R_EQUIVALENT_MATCH</a></b></li>
-</ul>
-<p>For example,</p>
-<pre><font color="#4444cc">
-    // a case insensitive prefix match is requested
-    SearchPattern pattern1 = SearchPattern.createPattern(&quot;Hash&quot;, IJavaSearchConstants.TYPE, IJavaSearchConstants.DECLARATIONS, SearchPattern.R_PREFIX_MATCH);
-
-    // a camel case match is requested
-    SearchPattern pattern2 = SearchPattern.createPattern(&quot;HM&quot;, IJavaSearchConstants.TYPE, IJavaSearchConstants.DECLARATIONS, SearchPattern.R_CAMEL_CASE_MATCH);
-
-    // a camel case with a strict expected number of parts match is requested
-    SearchPattern pattern3 = SearchPattern.createPattern(&quot;HM&quot;, IJavaSearchConstants.TYPE, IJavaSearchConstants.DECLARATIONS, SearchPattern.R_CAMELCASE_SAME_PART_COUNT_MATCH);
-</font></pre>
-<p>Note that using the patterns created above reduce the number of possible results among others:</p>
-<ul>
-<li>pattern1: <code>Hashtable</code>, <code>HashMap</code>, <code>HashMapEntry</code>, etc.</li>
-<li>pattern2: <code>HashMap</code>, <code>HashMapEntry</code>, etc.</li>
-<li>pattern3: <code>HashMapEntry</code>, etc.</li>
-</ul>
-
-<h4>
-Using <i>fine grain</i> flags in a Java search pattern
-</h4>
-<p>
-Some references patterns can be refined by adding one or several <i>fine grain</i>
-flags to the <code>limitTo</code> parameter.
-</p><p>
-For example, only the type references used in a cast expression will match the
-pattern created as follows:</p>
-<pre><font color="#4444cc">
-    // Get the type
-    IType type = ...;
-    
-    // Create search pattern
-    SearchPattern pattern = SearchPattern.createPattern(type, IJavaSearchConstants.REFERENCES | IJavaSearchConstants.CAST_TYPE_REFERENCE);
-</font></pre>
-<p>
-Note that the fine grain flags can be combined together but only for the same kind of search
-(e.g. only a combination of flags for <u>type</u> references will be meaningful
-if the <code>searchFor</code> parameter is set to
-<a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#TYPE">TYPE</a>).
-</p><p>
-<u>Flags for type references</u></p>
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#FIELD_DECLARATION_TYPE_REFERENCE">FIELD_DECLARATION_TYPE_REFERENCE</a></b>:
-type references used as the type of a field declaration.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#LOCAL_VARIABLE_DECLARATION_TYPE_REFERENCE">LOCAL_VARIABLE_DECLARATION_TYPE_REFERENCE</a></b>:
-type references used as the type of a local variable declaration.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#PARAMETER_DECLARATION_TYPE_REFERENCE">PARAMETER_DECLARATION_TYPE_REFERENCE</a></b>:
-type references used as the type of a method parameter.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#SUPERTYPE_TYPE_REFERENCE">SUPERTYPE_TYPE_REFERENCE</a></b>:
-type references used as a super type or as a super interface.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#THROWS_CLAUSE_TYPE_REFERENCE">THROWS_CLAUSE_TYPE_REFERENCE</a></b>:
-type references used in a throws clause.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#CAST_TYPE_REFERENCE">CAST_TYPE_REFERENCE</a></b>:
-type references used in a cast expression.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#CATCH_TYPE_REFERENCE">CATCH_TYPE_REFERENCE</a></b>:
-type references used in a catch header.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#CLASS_INSTANCE_CREATION_TYPE_REFERENCE">CLASS_INSTANCE_CREATION_TYPE_REFERENCE</a></b>:
-type references used in class instance creation.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#RETURN_TYPE_REFERENCE">RETURN_TYPE_REFERENCE</a></b>:
-type references used as a method return type.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#IMPORT_DECLARATION_TYPE_REFERENCE">IMPORT_DECLARATION_TYPE_REFERENCE</a></b>:
-type references used in an import declaration.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#ANNOTATION_TYPE_REFERENCE">ANNOTATION_TYPE_REFERENCE</a></b>:
-type references used as an annotation.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#TYPE_ARGUMENT_TYPE_REFERENCE">TYPE_ARGUMENT_TYPE_REFERENCE</a></b>:
-type references used as a type argument in a parameterized type or a parameterized method.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#TYPE_VARIABLE_BOUND_TYPE_REFERENCE">TYPE_VARIABLE_BOUND_TYPE_REFERENCE</a></b>:
-type references used as a type variable bound.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#WILDCARD_BOUND_TYPE_REFERENCE">WILDCARD_BOUND_TYPE_REFERENCE</a></b>:
-type references used as a wildcard bound.</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#INSTANCEOF_TYPE_REFERENCE">INSTANCEOF_TYPE_REFERENCE</a></b>:
-type references used in an <code>instance of</code> condition.</li>
-</ul>
-<p>
-<u>Flags for field or method references</u>
-</p>
-<ul>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#SUPER_REFERENCE">SUPER_REFERENCE</a></b>:
-super field accesses or super method invocations (e.g. using the <code>super</code> qualifier).
-</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#QUALIFIED_REFERENCE">QUALIFIED_REFERENCE</a></b>:
-qualified field accesses or qualified method invocations.
-</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#THIS_REFERENCE">THIS_REFERENCE</a></b>:
-primary field accesses or primary method invocations (e.g. using the <code>this</code> qualifier).
-</li>
-<li><b><a href="../reference/api/org/eclipse/jdt/core/search/IJavaSearchConstants.html#IMPLICIT_THIS_REFERENCE">IMPLICIT_THIS_REFERENCE</a></b>:
-field accesses or method invocations without any qualification.
-</li>
-</ul>
-
-<h4>
-Creating a Java search scope
-</h4>
-<p>
-If you are interested in search results in a given project or even in a given package, or if you know that search results
-can only be found in the hierarchy of a given type, you can create the appropriate search scope using 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#createJavaSearchScope(org.eclipse.jdt.core.IJavaElement[])">createJavaSearchScope(IJavaElement[])</a></b>
-or <b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#createHierarchyScope(org.eclipse.jdt.core.IType)">createHierarchyScope(IType)</a></b>.</p>
-<p>
-For example, creating a search scope on a given package is done as follows:</p>
-<pre><font color="#4444cc">
-    // Get the package
-    IPackageFragment pkg = ...;
-
-    // Create search scope
-    IJavaSearchScope scope = SearchEngine.createJavaSearchScope(new IJavaElement[] {pkg});
-</font></pre>
-<p>
-Or creating a search scope on the hierarchy of a given type is:</p>
-<pre><font color="#4444cc">
-    // Get the type
-    IType type = ...;
-
-    // Create search scope
-    IJavaSearchScope scope = SearchEngine.createHierarchyScope(type);
-</font></pre>
-<p>
-Finally, you can create a search scope comprising the entire workspace using
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchEngine.html#createWorkspaceScope()">createWorkspaceScope</a></b>:</p>
-<pre><font color="#4444cc">
-    // Create search scope
-    IJavaSearchScope scope = SearchEngine.createWorkspaceScope();
-</font></pre>
-
-<h3>
-Searching</h3>
-<p>
-Once you have created a search pattern and a search scope, and you have extended 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html">SearchRequestor</a></b>,
-you can start a search query as follows: </p>
-<pre><font color="#4444cc">
-    // Get the search pattern
-    SearchPattern pattern = ...;
-
-    // Get the search scope
-    IJavaSearchScope scope = ...;
-
-    // Get the search requestor
-    SearchRequestor requestor = ...;
-
-    // Search
-    SearchEngine searchEngine = new SearchEngine();
-    searchEngine.search(pattern, new SearchParticipant[] {SearchEngine.getDefaultSearchParticipant()}, scope, requestor, null);
-</font></pre>
-<p>
-A notification that the search starts is sent to your search requestor using the
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#beginReporting()">beginReporting</a></b>
-method. &nbsp;Then, each search result is reported using the 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#acceptSearchMatch(org.eclipse.jdt.core.search.SearchMatch)">acceptSearchMatch</a></b>
-method. Finally 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#endReporting()">endReporting</a></b>
-indicates that the search has ended.</p>
-
-<h3>
-Collecting search results</h3>
-<p>
-Search results are reported using the 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchRequestor.html#acceptSearchMatch(org.eclipse.jdt.core.search.SearchMatch)">acceptSearchMatch(SearchMatch)</a></b>
-method. Paragraphs below highlight some features of 
-<b><a href="../reference/api/org/eclipse/jdt/core/search/SearchMatch.html">SearchMatch</a></b>. </p>
-
-<h4>
-Resources and Java elements</h4>
-<p>
-A search result can correspond to a Java element (e.g. a type declaration) or it can be contained in a Java element
-(e.g. a reference to a type inside a method). The search engine always tries to find the innermost Java element that
-corresponds to or that contains the search result. For example, searching for references to a method could find
-such a reference in an initializer. The initializer that contains this method reference is the element of the search match. </p>
-<p>
-The search engine also tries to find the resource that contains the Java element. If the Java
-element is contained in a compilation unit or a class file, the resource is the corresponding 
-<a HREF="../../org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>. 
-If the Java element is contained in a .jar file, the returned resource is that .jar
-file if it is in the workspace, <b>null</b> otherwise. </p>
-
-<h4>
-Source positions</h4>
-<p>Source positions <b><a HREF="../reference/api/org/eclipse/jdt/core/search/SearchMatch.html#getOffset()">
-getOffset</a></b> and <b><a HREF="../reference/api/org/eclipse/jdt/core/search/SearchMatch.html#getLength()">getLength</a></b> are given relative to the compilation unit that contains
-the search result. If the search result is contained in  a .jar file, the
-source positions are relative to the attached source. They are (-1, -1) if
-there is no source attached to  the .jar file. </p>
-
-<h4>
-Accurate versus inaccurate search results</h4>
-<p>
-In most cases search results are accurate, meaning that the search engine was able to determine that the given
-match is what was asked for. However in some cases the search engine is unable to do so, in such cases the match is
-inaccurate. Some possible reasons why a match could be inaccurate are:
-</p><ul>
-<li>The classpath on the project that contains the result is not properly set. For example, it refers to a project that is
-      not accessible, a jar on the classpath requires another jar that is not on the classpath, etc.</li>
-<li>The user code would not compile. For example, it refers to a class that is not yet defined.</li>
-</ul> 
-
-
-
-</body></html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm
deleted file mode 100644
index e95dd0a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_utility.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JavaUI utilities</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JavaUI utilities</h2>
-<p><a href="../reference/api/org/eclipse/jdt/ui/JavaUI.html"><b>JavaUI</b></a> 
-    is the main access point to the Java user interface components. It allows 
-    you to programmatically open editors on Java elements, open a Java or Java 
-    Browsing perspective,&nbsp; and open package and type prompter dialogs. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm
deleted file mode 100644
index 8cd4a1f..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_wizards.htm
+++ /dev/null

@@ -1,164 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Java wizard pages</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Java wizard pages</h2>
-<p> The <a href="../reference/api/org/eclipse/jdt/ui/wizards/package-summary.html"><b>org.eclipse.jdt.ui.wizards</b></a> 
-  package provides wizard pages for creating and configuring Java
-elements.&nbsp; Several
-prefabricated pages are provided for your use.</p>
-<h3><b>Creating new Java elements</b></h3>
-<p>A hierarchy of wizard pages support the creation of new Java
-elements.&nbsp;&nbsp;</p>
-<p><a href="../reference/api/org/eclipse/jdt/ui/wizards/NewElementWizardPage.html"><b>NewElementWizardPage</b></a>
-is the abstract class that defines the basic operation of the wizard.&nbsp;
-Additional abstract classes are provided in the hierarchy for making
-customizations to the functionality provided by the concrete wizards.</p>
-<p>The concrete creation wizards can be used directly and generally are not
-intended to be subclassed.&nbsp;</p>
-<ul>
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewClassWizardPage.html"><b>NewClassWizardPage</b></a>
-    allows users to define a new Java class. Clients can instantiate and configure the wizard page. To implement your own type wizard
-    subclass <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.
-    To simply open the original 'New Java Class wizard' use the <a href="../reference/api/org/eclipse/jdt/ui/actions/OpenNewClassWizardAction.html"><b>OpenNewClassWizardAction</b></a>.
-  </li>    
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewInterfaceWizardPage.html"><b>NewInterfaceWizardPage</b></a>
-    allows users to define a new Java interface. Clients can instantiate and configure the wizard page. To implement your own type wizard
-    subclass <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.
-    To simply open the original 'New Java Interface wizard' use the <a href="../reference/api/org/eclipse/jdt/ui/actions/OpenNewInterfaceWizardAction.html"><b>OpenNewInterfaceWizardAction</b></a>.
-  </li>    
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewEnumWizardPage.html"><b>NewEnumWizardPage</b></a>
-    allows users to define a new Java enumeration. Clients can instantiate and configure the wizard page. To implement your own type wizard
-    subclass <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.
-    To simply open the original 'New Java Enum wizard' use the <a href="../reference/api/org/eclipse/jdt/ui/actions/OpenNewEnumWizardAction.html"><b>OpenNewEnumWizardAction</b></a>.
-  </li>    
-  <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewAnnotationWizardPage.html"><b>NewAnnotationWizardPage</b></a>
-    allows users to define a new Java annotations.Clients can instantiate and configure the wizard page. To implement your own type wizard
-    subclass <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.html"><b>NewTypeWizardPage</b></a>.
-    To simply open the original 'New Java Annotation wizard' use the <a href="../reference/api/org/eclipse/jdt/ui/actions/OpenNewAnnotationWizardAction.html"><b>OpenNewAnnotationWizardAction</b></a>.
-    </li>    
-   <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewPackageWizardPage.html"><b>NewPackageWizardPage</b></a>
-    allows users to create a new Java package. Clients can instantiate and configure the wizard page. 
-    To simply open the original 'New Java Package wizard' use the <a href="../reference/api/org/eclipse/jdt/ui/actions/OpenNewPackageWizardAction.html"><b>OpenNewPackageWizardAction</b></a>.
-    </li>  
-   <li> 
-    <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPageOne.html"><b>NewJavaProjectWizardPageOne</b></a>
-    and <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPageTwo.html"><b>NewJavaProjectWizardPageTwo</b></a>
-    allow users to create a new Java project wizard. Clients can use and configure these pages in their own project wizard. To simply open the
-    original 'New Java Project wizard' use the <a href="../reference/api/org/eclipse/jdt/ui/actions/OpenNewJavaProjectWizardAction.html"><b>OpenNewJavaProjectWizardAction</b></a>
-   </li>
-</ul>
-<h3>Contributing a classpath container wizard page</h3>
-<p>The interface <a href="../reference/api/org/eclipse/jdt/ui/wizards/IClasspathContainerPage.html"><b>IClasspathContainerPage</b></a>
-defines a structure for contributing a wizard page that allows a user to define
-a new classpath container entry or edit an existing one.&nbsp; If your plug-in
-has defined its own type of classpath container using the JDT Core <b><a href="../reference/extension-points/org_eclipse_jdt_core_classpathContainerInitializer.html">org.eclipse.jdt.core.classpathContainerInitializer</a></b>
- extension point, then you will probably want to define a corresponding wizard
-page for editing and creating classpath containers of this type.</p>
-<p>Your plug-in's markup should provide an extension <b><a href="../reference/extension-points/org_eclipse_jdt_ui_classpathContainerPage.html">org.eclipse.jdt.ui.classpathContainerPage</a>.&nbsp;
-</b>In the extension markup, you provide the name of your class that implements <a href="../reference/api/org/eclipse/jdt/ui/wizards/IClasspathContainerPage.html"><b>IClasspathContainerPage</b></a>.&nbsp;
-If you need additional information in your wizard page about the
-classpath's context when it is selected, you can implement <a href="../reference/api/org/eclipse/jdt/ui/wizards/IClasspathContainerPageExtension.html"><b>IClasspathContainerPageExtension</b></a>. If your configuration page
-wants to returns more than one entry when being added, implement 
- <a href="../reference/api/org/eclipse/jdt/ui/wizards/IClasspathContainerPageExtension.html"><b>IClasspathContainerPageExtension2</b></a>.
-</p>
-<h3> Customizing a wizard page</h3>
-<p> Besides using 
-  prefabricated pages, you can subclass the wizard pages to 
-  add your own input fields or to influence the code generation.&nbsp; You
-should use the abstract classes in the <a href="../reference/api/org/eclipse/jdt/ui/wizards/NewElementWizardPage.html"><b>NewElementWizardPage</b></a>
-hierarchy to customize a wizard rather than subclassing the concrete
-classes.</p>
-<p> Below is a sample 
-  of a new type wizard page that is customized to create JUnit test case classes. 
-  The page initializes the super class field with &quot;junit.framework.TestCase&quot; 
-  and adds a checkbox that controls whether method stubs for the <code>setUp()</code> and <code>tearDown()</code>
-  method are to be created.</p>
-<pre><font color="#4444CC">public class TestCaseWizardPage extends NewTypeWizardPage {
-    private Button fCreateStubs;
-
-    public TestCaseWizardPage() {
-        super(true, &quot;TestCaseWizardPage&quot;);
-    }
-
-    /**
-     * The wizard managing this wizard page must call this method
-     * during initialization with a corresponding selection.
-     */   
-    public void init(IStructuredSelection selection) {
-        IJavaElement jelem= getInitialJavaElement(selection);
-        initContainerPage(jelem);
-        initTypePage(jelem);
-        doStatusUpdate();
-    }
-
-    private void doStatusUpdate() {
-        // define the components for which a status is desired
-        IStatus[] status= new IStatus[] {
-            fContainerStatus,
-            isEnclosingTypeSelected() ? fEnclosingTypeStatus : fPackageStatus,
-            fTypeNameStatus,
-        };
-        updateStatus(status);
-    }
-
-
-    protected void handleFieldChanged(String fieldName) {
-        super.handleFieldChanged(fieldName);
-
-        doStatusUpdate();
-    }
-	
-    public void createControl(Composite parent) {
-        initializeDialogUnits(parent);
-        Composite composite= new Composite(parent, SWT.NONE);
-        int nColumns= 4;
-        GridLayout layout= new GridLayout();
-        layout.numColumns= nColumns;
-        composite.setLayout(layout);
-
-        // Create the standard input fields
-        createContainerControls(composite, nColumns);
-        createPackageControls(composite, nColumns);
-        createSeparator(composite, nColumns);
-        createTypeNameControls(composite, nColumns);
-        createSuperClassControls(composite, nColumns);
-
-        // Create the checkbox controlling whether we want stubs
-        fCreateStubs= new Button(composite, SWT.CHECK);
-        fCreateStubs.setText(&quot;Add 'setUp()' and 'tearDown()' to new class&quot;);
-        GridData gd= new GridData();
-        gd.horizontalSpan= nColumns;
-        fCreateStubs.setLayoutData(gd);
-
-        setControl(composite);
-
-        // Initialize the super type field and mark it as read-only
-        setSuperClass(&quot;junit.framework.TestCase&quot;, false);
-    }
-
-    protected void createTypeMembers(IType newType, ImportsManager imports, IProgressMonitor monitor) throws CoreException {
-        if (fCreateStubs.getSelection()) {
-            String setUpMathod= &quot;public void setUp() {}&quot;;
-            newType.createMethod(setUpMathod, null, false, null);
-
-            String tearDownMathod= &quot;public void tearDown() {}&quot;;
-            newType.createMethod(tearDownMathod, null, false, null); 
-        }
-   }
-}</font></pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm
deleted file mode 100644
index 0109a1d..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_api_write_jar_file.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Programmatically Writing a Jar file</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Programmatically Writing a Jar file</h2>
-<p> The <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/package-summary.html"> 
-  <b> 
-  org.eclipse.ui.jarpackager</b></a> package provides utility classes to programmatically 
-  export files to a Jar file. Below is a code snippet that outlines the use of 
-  the <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a> 
-  class:</p>
-<pre><font color="#4444cc">    void createJar(IType mainType, IFile[] filestoExport) {
-        Shell parentShell= ...;
-        JarPackageData description= new JarPackageData();
-        IPath location= new Path(&quot;C:/tmp/myjar.jar&quot;);
-        description.setJarLocation(location);
-        description.setSaveManifest(true);
-        description.setManifestMainClass(mainType);
-        description.setElements(filestoExport);
-        IJarExportRunnable runnable= description.createJarExportRunnable(parentShell);
-        try {
-            new ProgressMonitorDialog(parentShell).run(true,true, runnable);
-        } catch (InvocationTargetException e) {
-            // An error has occurred while executing the operation
-        } catch (InterruptedException e) {
-            // operation has been canceled.
-        }
-    }</font></pre>
-<p> Additional API is provided to create a plug-in specific subclass of <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a>. 
-  This allows other plug-ins to implement their own Jar export/import wizards 
-  and to save the content of the <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a>
-object to a corresponding Jar 
-  description file.</p>
-<p> Once the JAR is described by a <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarPackageData.html"><b>JarPackageData</b></a>,
-it can be programmatically written using a <a href="../reference/api/org/eclipse/jdt/ui/jarpackager/JarWriter3.html"><b>JarWriter3</b></a>.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm
deleted file mode 100644
index 173a31d..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_building_with_apt.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-   <title>Headless Building with APT in Eclipse</title>
-</head>
-
-<body>
-<h1>Headless Building with APT in Eclipse</h1>
-<h2>Instructions for building workspaces from the command-line directly or with ant</h2>
-
-<p>
-The APT plugin can be used in conjunction with Eclipse to build your preconfigured 
-workspace, either directly from the command-line or via ant with its built-in ant task.
-</p>
-
-<h3>Building from the command-line</h3>
-Given an installation of Eclipse with the APT plugin installed, you can invoke the command-line builder
-with the following command:
-
-<pre>
-eclipsec -nosplash -application org.eclipse.jdt.apt.core.aptBuild -data %WORKSPACE%
-</pre>
-
-This invokes Eclipse as a console application in headless mode and builds the workspace as provided on the command-line.
-Any configuration for the provided workspace will be observed in the build. 
-
-<h3>Building with Ant</h3>
-Again, you will need an installation of Eclipse with the APT plugin installed. Given this, the "apt"
-task can be invoked with the following xml in your build.xml file:
-
-<pre>
-&lt;project name="test_eclipse" default="build" basedir="."&gt;
-
-    &lt;taskdef name="apt" classname="org.eclipse.jdt.apt.core.build.JdtApt"/&gt;
-    
-    &lt;target name="build"&gt;
-        &lt;apt workspace="%WORKSPACE%" eclipseHome="%ECLIPSE_HOME%"/&gt;
-    &lt;/target&gt;
-    
-&lt;/project&gt;
-</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm
deleted file mode 100644
index 4a73302..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_apt_getting_started.htm
+++ /dev/null

@@ -1,122 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-   <title>Getting started with APT in Eclipse</title>
-</head>
-
-<body>
-<h1>Getting Started</h1>
-<h2>APT in Eclipse</h2>
-
-<p>
-A Java annotation processor is a compiler plug-in that can gather information about source code as 
-it is being compiled, generate additional Java types or other resource files, and post warnings 
-and errors. Eclipse 3.2 provided support for annotation processors using the 
-<a href="http://java.sun.com/j2se/1.5.0/docs/guide/apt/mirror/overview-summary.html">Java 5 Mirror APIs</a>,
-and Eclipse 3.3 added support for processors using the 
-<a href="http://java.sun.com/javase/6/docs/api/javax/annotation/processing/package-summary.html">
-Java 6 annotation processing APIs</a>.</p>
-<p>
-Both Java 5 and Java 6 annotation processors can be called during a build. Errors and warnings 
-produced by the processors will be reported in the Problems view, and build artifacts will
-be created just as if you were running Sun's apt tool (for Java 5) or javac compiler (for Java 6)
-from the command line.</p>
-<p>
-Java 5 processors can also be executed as you are typing in the editor. This permits processors
-to report errors during editing, which may be helpful. This feature can
-be enabled or disabled via the annotation processor properties dialog. 
-In addition to reporting errors, Java 5 processors can also generate files as you are typing in the editor.
-This feature is only enabled if the processor includes &quot;enableTypeGenerationInEditor&quot; in
-the set of strings it returns from its implementation of 
-<a href="http://java.sun.com/j2se/1.5.0/docs/guide/apt/mirror/com/sun/mirror/apt/AnnotationProcessorFactory.html#supportedOptions()">
-<code>AnnotationProcessorFactory.supportedOptions()</code></a>. This string is defined in
-the class <code>org.eclipse.jdt.apt.core.AptPreferenceConstants</code>.</p>
-<p>
-Eclipse does not support executing Java 6 processors while typing in the editor; you must save and build
-in order for Java 6 processors to report errors or generate files.</p>
-
-<p>
-For more detailed information about how the APT plugins work and how to write annotation
-processors of your own, you can view the 
-<a href="http://www.eclipse.org/jdt/apt/index.html">JDT-APT project web site</a>.
-</p>
-
-<h3>Batch Compilation</h3>
-The Eclipse Java compiler is available outside of the Eclipse IDE by using the
-<a href="jdt_api_compile.htm">batch mode compiler</a>, via ecj.jar or the Java 6
-<a href="http://java.sun.com/javase/6/docs/api/javax/tools/JavaCompiler.html">
-<code>javax.tools.JavaCompiler</code></a> interface. Java 5 annotation processors 
-are not available in this way, but Java 6 annotation processors are fully supported.
-
-<h3>Turning on Annotation Processing</h3>
-You must have your project's compiler configured to use Java 5.0 or higher compliance
-in the preferences, under Java-&gt;Compiler:
-<p>
-<img src="images/compiler_dialog.png" alt="Screenshot of Compiler preference page"></p>
-<p>
-Java 6 processors will only be run if the project's Java 
-compiler compliance level is set to Java 6 or higher, and Eclipse is running on
-a Java 1.6 or higher JVM.</p>  
-<p>Next you need to enable annotation processing under 
-Java-&gt;Compiler-&gt;Annotation Processing:</p>
-<p>
-<img src="images/annotation_processing.png" alt="Screenshot of Annotation Processing properties page"></p>
-<p>
-In this dialog you can also specify the generated source directory if desired,
-and provide any processor options that are necessary.</p>
-<p>
-<b>Note: "-Aclasspath" and "-Asourcepath" options are automatically passed
-to all your Java 5 processors by Eclipse, so it is unnecessary to provide those.</b>
-</p>
-<h3>Adding Annotation Processors</h3>
-You can add annotation processors to your project under Java-&gt;Compiler-&gt;Annotation Processing-&gt;Factory Path:
-
-<p>
-<img src="images/factory_path.png" alt="Screenshot of Factory Path properties page"></p>
-<p>
-Processors can be contained in jar files or in Eclipse plug-ins. The Factory Path list includes 
-both Java 5 and Java 6 processors.</p>
-
-<h3>Working On Annotation Processors</h3>
-<p>The annotation processors used in a project must exist in binary form (as jar files or plug-ins)
-before the project is built. Therefore it is not possible to include both processor code and
-code to be processed within the same project. Developers of annotation processors are advised
-to keep annotation processor projects separate from the projects containing the target code that
-is to be processed. Indeed it may be preferable to keep them in separate workspaces, to facilitate 
-debugging.</p>
-
-<h3>Factory Path and Source Control</h3>
-
-<P>The factory path is stored in a file named &quot;.factorypath&quot; at the project root,
-similar to the classpath, and should be treated the same way as the classpath with regard to
-version control. In order to avoid hard-coding paths to factory jars, you can either use project-relative jars
-via the "Add Jars..." button, or use a classpath variable via the "Add Variable..." button.</p>
-
-<h3>Processor Options and Source Control</h3>
-
-<p>
-Processor options are stored in the .settings folder within each project, which is also
-where other compiler options are stored. All files within the .settings folder are typically
-managed with source control.</p>
-<p>
-You may need to use paths as some of the options passed to your annotation processors.
-Again, by avoiding hard-coding of absolute paths you'll be able to share your configuration
-in source control. To permit this, Eclipse supports using classpath variables inside of processor options.
-Variables are delimited on both sides by %, and must be the first segment of a path.</p>
-<p>
-For example, if FOO is a classpath variable that points to d:/foo, then %FOO%/bar.txt 
-will resolve to d:/foo/bar.txt when the processor is called.  If the classpath
-variable does not exist, then the raw string (&quot;%FOO%&quot; in this example) will be added to 
-the environment options.  However, the remainder of the string (&quot;bar.txt&quot; in this example) 
-does not need to exist.</p>
-<p>
-The reserved variable ROOT is given special meaning: it is the workspace root, 
-and introduces a project resource.  For instance, if quux is the name of a 
-project, then %ROOT%/quux will resolve to the absolute path of quux and 
-%ROOT%/quux/.classpath will resolve to the absolute path of the file .classpath
-within project quux.  When using ROOT, the first segment of the path must 
-actually exist: in the example, the project quux must exist, but .classpath need not.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm
deleted file mode 100644
index 94f14de..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Programmer's Guide</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h1>JDT Programmer's Guide</h1>
-<p>The Eclipse platform is delivered with a full featured Java integrated development 
-  environment (IDE). Java development tooling (JDT) allows users to write, compile, 
-  test, debug, and edit programs written in the Java programming language.</p>
-<p>The JDT makes use of many of the platform extension points and frameworks described 
-  in the Platform Plug-in Developer Guide.&nbsp; It's easiest to think of 
-  the JDT as a set of plug-ins that add Java specific behavior to the generic 
-  platform resource model and contribute Java specific views, editors, and actions 
-  to the workbench.</p>
-<p> This guide discusses the extension points and API provided by the JDT. 
-  We assume that you already understand the concepts of plug-ins, extension points, 
-  workspace resources, and the workbench UI.&nbsp; </p>
-<p>Given that the JDT supplies a full featured Java IDE, why would you need to 
-  use the JDT API?&nbsp; If you are building a plug-in that interacts with Java programs or resources 
-  as part of its function, you may need to do one or more of the following things:</p>
-<ul>
-  <li> Programmatically manipulate Java resources, such as creating projects, 
-    generating Java source code, performing builds, or detecting problems in code.</li>
-  <li> Programmatically launch a Java program from the platform</li>
-  <li> Provide a new type of VM launcher to support a new family of Java runtimes</li>
-  <li> Add new functions and extensions to the Java IDE itself</li>
-</ul>
-<p> The JDT is structured into three major components:</p>
-<ul>
-  <li><a href="jdt_int_core.htm">JDT Core</a> - the headless infrastructure for compiling and manipulating Java
-    code.</li>
-  <li><a href="jdt_int_ui.htm">JDT UI</a> - the user interface extensions that provide the IDE.</li>
-  <li><a href="jdt_int_debug.htm">JDT Debug</a> - program launching and debug support specific to the Java programming language.</li>
-</ul>
-<p>We'll examine each component's structure and the API it provides.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm
deleted file mode 100644
index 7e78ca5..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_apt.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) BEA Systems 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Core</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT Annotation Processing</h2>
-<p> JDT Annotation Processing (APT) (<b>org.eclipse.jdt.apt.core</b>) is the plug-in that supports compile-time 
-    processing of Java annotations.  You should only need to list this plug-in as a dependency if your plugin is an
-    annotation processor.</p>
-<p> For an introduction to working with APT, see 
-	<a href="jdt_apt_getting_started.htm">Getting Started with APT</a>.  For information on how to access APT
-	during command-line builds, see <a href="jdt_apt_building_with_apt.htm">Headless Building With APT</a>.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm
deleted file mode 100644
index 79d04f9..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_core.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Core</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT Core</h2>
-<p> JDT Core (<b>org.eclipse.jdt.core</b>) is the plug-in that defines the core Java elements 
-    and API. You should always list this plug-in as a prerequisite when you are
-developing Java specific features.</p>
-<p> JDT Core packages give you access to the Java model objects and headless
-Java IDE infrastructure.&nbsp; The JDT Core packages include:</p>
-<ul>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/package-summary.html">org.eclipse.jdt.core</a></b>
-    - defines the classes that describe the Java model.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/compiler/package-summary.html">org.eclipse.jdt.core.compiler</a>
-    </b> - defines an API for the compiler infrastructure.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/dom/package-summary.html">org.eclipse.jdt.core.dom</a> </b>
-    - supports Abstract Syntax Trees (AST) that 
-    can be used for examining the structure of a compilation unit down to the 
-    statement level.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/dom/rewrite/package-summary.html">org.eclipse.jdt.core.dom.rewrite</a> </b>
-    - supports rewriting of Abstract Syntax Trees (AST) that 
-    can be used for manipulating the structure of a compilation unit down to the 
-    statement level.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/eval/package-summary.html">org.eclipse.jdt.core.eval</a></b>
-    - supports
-    the evaluation of code snippets in a scrapbook or inside the debugger.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/formatter/package-summary.html">org.eclipse.jdt.core.formatter</a></b>
-    - supports
-    the formatting of compilation units, types, statements, expressions, etc.
-  </li>
-  <li><a href="../reference/api/org/eclipse/jdt/core/jdom/package-summary.html"><b> 
-    org.eclipse.jdt.core.jdom</b></a> - supports a Java Document Object Model (DOM) 
-    that can be used for walking the structure of a Java compilation unit.
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/search/package-summary.html"> 
-    org.eclipse.jdt.core.search</a></b> - supports searching the workspace's Java
-    model for Java elements that match a particular description.&nbsp;&nbsp;
-  </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/core/util/package-summary.html">org.eclipse.jdt.core.util</a>
-    </b>- provides
-    utility classes for manipulating .class files and Java model elements.
-  </li>
-</ul>
-<p><code>org.eclipse.jdt.core.jdom</code> is deprecated since version 3.0.
-The manipulation of the structure of a compilation unit should be done using 
-<code>org.eclipse.jdt.core.dom</code> instead.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm
deleted file mode 100644
index 8d8b16e..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_debug.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Debug</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT Debug</h2>
-<p> JDT Debug is comprised of several plug-ins that support the running and
-debugging of Java code.</p>
-<ul>
-  <li><b>org.eclipse.jdt.launching</b> is the plug-in that defines the Java launching 
-    and runtime support. You will require this plug-in if you 
-    need to launch Java virtual machines programmatically.&nbsp; The JDT
-    launching is closely tied to the platform launching facility, which is
-    described in <a href="../../org.eclipse.platform.doc.isv/guide/debug_launch.htm">Launching
-    a program</a>.
-    <p>The package <a href="../reference/api/org/eclipse/jdt/launching/package-summary.html"><b>org.eclipse.jdt.launching </b></a> provides classes for launching Java runtimes 
-    from the platform.&nbsp; <b><a href="../reference/api/org/eclipse/jdt/launching/JavaRuntime.html">JavaRuntime</a> </b> implements static methods to access registered VMs and 
-    compute runtime classpaths and source lookup paths.&nbsp; A family of VM's 
-    (such as the JDK) is represented by the <a href="../reference/api/org/eclipse/jdt/launching/IVMInstallType.html"><b> 
-    IVMInstallType</b></a> class. <a href="../reference/api/org/eclipse/jdt/launching/IVMInstall.html"><b> 
-    IVMInstall</b></a> represents particular installations within a family.&nbsp; 
-    The <a href="../reference/api/org/eclipse/jdt/launching/IVMRunner.html"><b> 
-    IVMRunner</b></a> is used to start a particular Java VM and register its processes 
-    with the debug plug-in.</p>
-    <p>The package <a href="../reference/api/org/eclipse/jdt/launching/sourcelookup/containers/package-summary.html"><b>org.eclipse.jdt.launching.sourcelookup.containers 
-      </b></a>defines classes for locating source code elements in the file system.<br></p>
-  </li>
-  <li><b>org.eclipse.jdt.debug</b> is the plug-in that defines the Java debug 
-    model. You will require this plug-in if you need to programmatically 
-    access objects in a program being debugged.&nbsp; The JDT debug model is
-    closely tied to the platform debug model, which is described in <a href="../../org.eclipse.platform.doc.isv/guide/debug_model.htm">Platform
-    debug model</a>.
-    <p>The package <a href="../reference/api/org/eclipse/jdt/debug/core/package-summary.html"><b>org.eclipse.jdt.debug.core</b></a> supports a Java debug model based on
-    JDI/JDWP 
-    that can be used for controlling a Java program under debug.</p>
-    <p>The package <a href="../reference/api/org/eclipse/jdt/debug/eval/package-summary.html"><b>org.eclipse.jdt.debug.eval</b></a> provides infrastructure for evaluating
-    Java expressions and reporting results.</p>
-  </li>
-  <li><b>org.eclipse.jdt.debug.ui</b> is the plug-in that defines the Java debug 
-    UI extensions. Most of the debugger API is provided by the platform debugger
-    infrastructure described in <a href="../../org.eclipse.platform.doc.isv/guide/debug_presentation.htm">Debug
-    model presentation</a> and <a href="../../org.eclipse.platform.doc.isv/guide/debug_ui.htm">Debug
-    UI utility classes</a>.&nbsp; The Java debug UI API focuses on accessing the prompting source locator
-    and Java launch configuration 
-    tabs.&nbsp;&nbsp;
-    <p>The package <a href="../reference/api/org/eclipse/jdt/debug/ui/launchConfigurations/package-summary.html"><b> 
-    org.eclipse.jdt.debug.ui.launchConfigurations</b></a> defines the launch
-    configuration tabs for local and remote Java applications.</p></li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm
deleted file mode 100644
index 1d1ed8e..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_junit.htm
+++ /dev/null

@@ -1,18 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT JUnit integration</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT JUnit integration</h2>
-<p><a href="http://www.junit.org">JUnit</a> is a simple test framework used to
-write repeatable tests.&nbsp; </p>
-<p>The JDT tools include a plug-in that integrates JUnit into the Java
-IDE.&nbsp; The JUnit plug-in allows you to define regression tests for your code
-and run them from the Java IDE. </p></body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm
deleted file mode 100644
index 86666f3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_model.htm
+++ /dev/null

@@ -1,235 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Java model</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>Java model</h2>
-<p> The Java model is the set of classes that model the objects associated with 
-  creating, editing, and building a Java program. The Java model classes are defined 
-  in <b><a href="../reference/api/org/eclipse/jdt/core/package-summary.html"> 
-  org.eclipse.jdt.core</a></b>.&nbsp; These classes implement Java specific 
-  behavior for resources and further decompose Java resources into model elements.</p>
-<h3> Java elements</h3>
-<p> The package <a href="../reference/api/org/eclipse/jdt/core/package-summary.html"><b> 
-  org.eclipse.jdt.core</b></a> defines the classes that model the elements that 
-  compose a Java program. The JDT uses an in-memory object model to represent 
-  the structure of a Java program. This structure is derived from the project's class path.
-  The model is hierarchical. Elements of a program can be decomposed into child elements.</p>
-<p> Manipulating Java elements is similar to manipulating resource objects.&nbsp; When you work with a Java 
-  element, you are actually working with a <b>handle</b> to some underlying model 
-  object.&nbsp; You must use the <b>exists()</b> protocol to determine whether 
-  the element is actually present in the workspace.&nbsp;</p>
-<p> The following table summarizes the different kinds of Java elements.</p>
-<table border="1">
-  <tbody> 
-  <tr> 
-    <th rowspan="1" colspan="1"> Element </th>
-    <th rowspan="1" colspan="1"> Description </th>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b> IJavaModel</b></a> 
-    </td>
-    <td> Represents the root Java element, corresponding to the workspace. The 
-      parent of all projects with the Java nature. It also gives you access to the projects without the java nature.</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-      IJavaProject</b></a> </td>
-    <td> Represents a Java project in the workspace. (Child of <a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b> 
-      IJavaModel</b></a>) </td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html"><b> 
-      IPackageFragmentRoot</b></a> </td>
-    <td> Represents a set of package fragments, and maps the fragments to an underlying 
-      resource which is either a folder, JAR, or ZIP file. (Child of <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-      IJavaProject</b></a>) </td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a> </td>
-    <td> Represents the portion of the workspace that corresponds to an entire 
-      package, or a portion of the package. (Child of <a href="../reference/api/org/eclipse/jdt/core/IPackageFragmentRoot.html"><b> 
-      IPackageFragmentRoot</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"><b> 
-      ICompilationUnit</b></a> </td>
-    <td> Represents a Java source (<b>.java</b>) file. (Child of <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IPackageDeclaration.html"><b> 
-      IPackageDeclaration</b></a> </td>
-    <td> Represents a package declaration in a compilation unit. (Child of <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"><b> 
-      ICompilationUnit</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IImportContainer.html"><b> 
-      IImportContainer</b></a> </td>
-    <td> Represents the collection of package import declarations in a compilation 
-      unit. (Child of <a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html"><b> 
-      ICompilationUnit</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IImportDeclaration.html"><b> 
-      IImportDeclaration</b></a> </td>
-    <td> Represents a single package import declaration. (Child of <a href="../reference/api/org/eclipse/jdt/core/IImportContainer.html"><b> 
-      IImportContainer</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> IType</b></a> 
-    </td>
-    <td> Represents either a source type inside a compilation unit, or a binary 
-      type inside a class file. </td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IField.html"><b> IField</b></a> 
-    </td>
-    <td> Represents a field inside a type. (Child of <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> 
-      IType</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IMethod.html"><b> IMethod</b></a> 
-    </td>
-    <td> Represents a method or constructor inside a type. (Child of <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> 
-      IType</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IInitializer.html"><b> 
-      IInitializer</b></a> </td>
-    <td> Represents a static or instance initializer inside a type. (Child of 
-      <a href="../reference/api/org/eclipse/jdt/core/IType.html"><b> IType</b></a> 
-      )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IClassFile.html"><b> IClassFile</b></a> 
-    </td>
-    <td> Represents a compiled (binary) type.&nbsp; (Child of <a href="../reference/api/org/eclipse/jdt/core/IPackageFragment.html"><b> 
-      IPackageFragment</b></a> )</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/ITypeParameter.html"><b> ITypeParameter</b></a> 
-    </td>
-    <td> Represents a type parameter.&nbsp; (Not a child of any Java element, it is obtained using
-           <a href="../reference/api/org/eclipse/jdt/core/IType.html#getTypeParameter(java.lang.String)"><b> 
-           IType.getTypeParameter(String)</b></a> or
-           <a href="../reference/api/org/eclipse/jdt/core/IMethod.html#getTypeParameter(java.lang.String)"><b> 
-           IMethod.getTypeParameter(String)</b></a>)</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/ILocalVariable.html"><b> ILocalVariable</b></a> 
-    </td>
-    <td> Represents a local variable in a method or an initializer.&nbsp; (Not a child of any Java element, it is obtained using
-           <a href="../reference/api/org/eclipse/jdt/core/ICodeAssist.html#codeSelect(int, int)"><b> 
-           ICodeAssist.codeSelect(int, int)</b></a>)</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IAnnotation.html"><b> IAnnotation</b></a> 
-    </td>
-    <td> Represents a Java 5 annotation. (Not a child of any Java element, it is obtained using
-           <a href="../reference/api/org/eclipse/jdt/core/IAnnotatable.html#getAnnotation(java.lang.String)"><b> 
-           IAnnotatable.getAnnotation(String)</b></a> or
-           <a href="../reference/api/org/eclipse/jdt/core/IAnnotatable.html#getAnnotations()"><b> 
-           IAnnotatable.getAnnotations()</b></a>)</td>
-  </tr>
-  <tr> 
-    <td> <a href="../reference/api/org/eclipse/jdt/core/IAnnotatable.html"><b> IAnnotatable</b></a> 
-    </td>
-    <td> Represents a type, a field, a method, a local variable, or a package declaration that can be 
-      annotated with one or several <a href="../reference/api/org/eclipse/jdt/core/IAnnotation.html"><b> IAnnotation</b></a>s.</td>
-  </tr>
-  </tbody> 
-</table>
-<p> All Java elements support the <a href="../reference/api/org/eclipse/jdt/core/IJavaElement.html"><b> 
-  IJavaElement</b></a> interface. </p>
-<p> Some of the elements are shown in the Packages view.&nbsp; These elements 
-  implement the <b><a href="../reference/api/org/eclipse/jdt/core/IOpenable.html"> 
-  IOpenable</a> </b> interface, since they must be opened before they can be navigated. 
-  The figure below shows how these elements are represented in the Packages view.</p>
-<p><img src="images/openables.png"  border="0" alt="Packages View showing elements implementing the IOpenable interface"> 
-</p>
-<p>The Java elements that implement <b><a href="../reference/api/org/eclipse/jdt/core/IOpenable.html"> 
-  IOpenable</a> </b> are created primarily from information found in the underlying 
-  resource files.&nbsp; The same elements are represented generically in the resource 
-  navigator view.</p>
-<p><img src="images/javanavigator.png"  border="0" alt="Resource Navigator showing elements implementing the IOpenable interface"> 
-</p>
-<p>Since 3.3, <b><a href="../reference/api/org/eclipse/jdt/core/IOpenable.html">IOpenable</a></b>s that are the root of 
-  <b><a href="../reference/api/org/eclipse/jdt/core/IType.html">IType</a></b>s implement 
-  <b><a href="../reference/api/org/eclipse/jdt/core/ITypeRoot.html">ITypeRoot</a> </b>. These are 
-  <b><a href="../reference/api/org/eclipse/jdt/core/ICompilationUnit.html">ICompilationUnit</a></b> and
-  <b><a href="../reference/api/org/eclipse/jdt/core/IClassFile.html">IClassFile</a></b>.
-</p>
-<p> Other elements correspond to the items that make up a Java compilation unit. 
-  The figure below shows a Java compilation unit and a content outliner that displays 
-  the source elements in the compilation unit.</p>
-<img src="images/sourceelements.png"  border="0" alt="An editor and a content outliner illustrating the relation between corresponding source elements"> 
-<p> These elements implement the <a href="../reference/api/org/eclipse/jdt/core/ISourceReference.html"><b> 
-  ISourceReference</b></a> interface, since they can provide corresponding source 
-  code. (As these elements are selected in the content outliner, their corresponding 
-  source code is shown in the Java editor).</p>
-<h3> Java elements and their resources</h3>
-<p> Many of the Java elements correspond to generic resources in the workspace.&nbsp; 
-  When you want to create Java elements from a generic resource the class <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b> 
-  JavaCore</b></a> is the best starting point. The following code snippet shows 
-  how to get Java elements from their corresponding resources.</p>
-<pre>
-<font color="#4444cc">    
-    private void createJavaElementsFrom(IProject myProject, IFolder myFolder, IFile myFile) {
-        IJavaProject myJavaProject= JavaCore.create(myProject);
-        if (myJavaProject == null)
-            // the project is not configured for Java (has no Java nature)
-            return;
-            
-        // get a package fragment or package fragment root
-        IJavaElement myPackageFragment= JavaCore.create(myFolder);
-        
-        // get a .java (compilation unit), .class (class file), or
-        // .jar (package fragment root)
-        IJavaElement myJavaFile = JavaCore.create(myFile);
-    }</font></pre> 
-<p>Once you have a Java element, you can use the JDT API to traverse and query
-the model.&nbsp; You may also query the non-Java resources contained in a Java
-element.&nbsp;</p>
-<pre>
-<font color="#4444cc">
-    private void createJavaElementsFrom(IProject myProject, IFolder myFolder, IFile myFile) throws JavaModelException {
-        ...
-        // get the non Java resources contained in my project.
-        Object[] nonJavaChildren = myJavaProject.getNonJavaResources();
-        ...
-    }</font></pre>
-<h3> Java projects</h3>
-<p>When you create a Java project from a simple project, <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b> 
-  JavaCore</b></a> will check to see if the project is configured with the Java 
-  nature.&nbsp; The JDT plug-in uses a project nature to designate a project as 
-  having Java behavior.&nbsp; This nature (<b>org.eclipse.jdt.core.JavaCore#NATURE_ID</b> 
-  ) is assigned to a project when the "New Java project" wizard creates a project.&nbsp; 
-  If the Java nature is not configured on a project, <a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b> 
-  JavaCore</b></a> will return null when asked to create the project.</p>
-<p><a href="../reference/api/org/eclipse/jdt/core/JavaCore.html"><b>JavaCore</b></a> 
-  is also used to maintain the Java class path, including locations for finding 
-  source code and libraries, and locations for generating output binary (<b>.class</b>) 
-  files.</p>
-<p> What are the unique characteristics of Java projects? They record their classpath 
-  in a "<b>.classpath</b>" file and add the Java incremental project builder to 
-  the project's build spec.&nbsp; Otherwise, they are just regular projects and 
-  can be configured with other natures (and other incremental builders) by plug-ins. 
-  Plug-ins that want to configure projects with Java behavior in addition to their 
-  own behavior typically use the <b><a href="../reference/api/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPage.html"> 
-  NewJavaProjectWizardPage</a> </b> to assign the Java nature to the project in 
-  addition to their own custom natures or behavior.</p>
-<p><a href="../reference/api/org/eclipse/jdt/core/IJavaModel.html"><b> IJavaModel</b></a> 
-  can be considered the parent of all projects in the workspace that have the 
-  Java project nature (and therefore can be treated as an <a href="../reference/api/org/eclipse/jdt/core/IJavaProject.html"><b> 
-  IJavaProject</b></a>).</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm b/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm
deleted file mode 100644
index 1946607..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/guide/jdt_int_ui.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT UI</title>
-<link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-<body>
-<h2>JDT UI</h2>
-<p>JDT UI (<b>org.eclipse.jdt.ui</b>) is the plug-in implementing the Java specific user interface 
-  classes that manipulate Java elements. The packages in the JDT UI implement
-the Java-specific extensions to the workbench.&nbsp;&nbsp;&nbsp; The JDT UI
-packages include:</p>
-<ul>
-  <li> <b><a href="../reference/api/org/eclipse/jdt/ui/package-summary.html"> 
-    org.eclipse.jdt.ui</a> </b> - provides support classes for presenting Java 
-    elements in the user interface.&nbsp; This package exposes constants for retrieving 
-    Java user interface parts from the workbench registry and for retrieving preference 
-    settings from the Java preferences.&nbsp; Programming interfaces <a href="../reference/api/org/eclipse/jdt/ui/ITypeHierarchyViewPart.html"><b>ITypeHierarchyViewPart</b></a> 
-    and <a href="../reference/api/org/eclipse/jdt/ui/IPackagesViewPart.html"> 
-    <b> IPackagesViewPart</b></a> are provided for interacting with Java views. 
-  </li>
-  <li> <b><a href="../reference/api/org/eclipse/jdt/ui/actions/package-summary.html">org.eclipse.jdt.ui.actions</a> 
-    </b>- provides actions and action groups to populate tool bars, global menu 
-    bars and context menus with JDT specific functionality. You should use action 
-    groups to populate menus and tool bars instead of adding actions directly. 
-    This shields you from missing newly added actions or from using outdated menu 
-    structures. </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/cleanup/package-summary.html"> 
-    org.eclipse.jdt.ui.cleanup</a> </b> - provides the interfaces and classes that are needed to contribute a code clean up via <code>org.eclipse.jdt.ui.cleanUps</code> extension point.</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/dialogs/package-summary.html"> 
-    org.eclipse.jdt.ui.dialogs</a> </b> - provides classes and interfaces 
-    to access and extend JDT dialogs, in particular the 'open type' dialog.</li>    
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/jarpackager/package-summary.html"> 
-    org.eclipse.jdt.ui.jarpackager</a> </b> - provides classes and interfaces 
-    to generate a JAR file. </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/refactoring/package-summary.html">org.eclipse.jdt.ui.refactoring</a></b> 
-    - provides support for running rename refactorings</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/search/package-summary.html">org.eclipse.jdt.ui.search</a></b> 
-    - provides classes and interfaces to contribute participants to a Java search</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/package-summary.html"> 
-    org.eclipse.jdt.ui.text</a> </b> - provides support classes for presenting 
-    Java text.&nbsp; </li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/folding/package-summary.html">org.eclipse.jdt.ui.text.folding</a></b> - provides interfaces to implement code folding strategies for the Java editor.</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/java/package-summary.html">org.eclipse.jdt.ui.text.java</a></b> - provides interfaces to implement code completion processors.</li>
-  <li><b><a href="../reference/api/org/eclipse/jdt/ui/text/java/hover/package-summary.html"> 
-    org.eclipse.jdt.ui.text.java.hover</a> </b> - provides implementations for 
-    presenting text hovers in Java editors.&nbsp; </li>
-  <li><a href="../reference/api/org/eclipse/jdt/ui/wizards/package-summary.html"> 
-    <b> org.eclipse.jdt.ui.wizards</b></a> - provides wizard pages for creating 
-    and configuring Java elements. </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt b/bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt
deleted file mode 100644
index 1f254ca..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/jdtOptions.txt
+++ /dev/null

@@ -1,147 +0,0 @@
--quiet
--encoding "iso-8859-1"
--charset "iso-8859-1"
--sourcepath "../org.eclipse.jdt.core/antadapter
-;../org.eclipse.jdt.core/batch
-;../org.eclipse.jdt.core/codeassist
-;../org.eclipse.jdt.core/compiler
-;../org.eclipse.jdt.core/dom
-;../org.eclipse.jdt.core/eval
-;../org.eclipse.jdt.core/formatter
-;../org.eclipse.jdt.core/model
-;../org.eclipse.jdt.core/search
-;../org.eclipse.jdt.debug/model
-;../org.eclipse.jdt.debug/jdi
-;../org.eclipse.jdt.debug/eval
-;../org.eclipse.jdt.debug.ui/ui
-;../org.eclipse.jdt.junit/src
-;../org.eclipse.jdt.junit.core/src
-;../org.eclipse.jdt.junit.runtime/src
-;../org.eclipse.jdt.launching/launching
-;../org.eclipse.jdt.ui/ui
-;../org.eclipse.jdt.ui/core refactoring
-;../org.eclipse.jdt.ui/ui refactoring
-;../org.eclipse.jdt.ui/core extension
-;../org.eclipse.jdt.core.manipulation/refactoring
-;../org.eclipse.jdt.core.manipulation/common
-;../org.eclipse.ant.launching/src
-;../org.eclipse.ant.ui/Ant Tools Support
-;../org.eclipse.ant.ui/Ant Editor
-;../org.eclipse.jdt.apt.core/src"
--d reference/api
--classpath @rt@
-;../com.ibm.icu_4.0.1.v20090822.jar
-;../org.eclipse.jdt.apt.core/mirrorapi.jar
-;../org.apache.ant_1.7.1.v20090120-1145/lib/ant.jar
-;../org.eclipse.ant.core/@dot
-;../org.eclipse.compare/@dot
-;../org.eclipse.compare.core/@dot
-;../org.eclipse.core.commands/@dot
-;../org.eclipse.core.contenttype/@dot
-;../org.eclipse.core.expressions/@dot
-;../org.eclipse.core.externaltools/@dot
-;../org.eclipse.core.filebuffers/@dot
-;../org.eclipse.core.filesystem/@dot
-;../org.eclipse.core.jobs/@dot
-;../org.eclipse.core.resources/@dot
-;../org.eclipse.core.runtime/@dot
-;../org.eclipse.core.runtime.content/@dot
-;../org.eclipse.core.runtime.jobs/@dot
-;../org.eclipse.core.runtime.preferences/@dot
-;../org.eclipse.core.variables/@dot
-;../org.eclipse.debug.core/@dot
-;../org.eclipse.debug.ui/@dot
-;../org.eclipse.equinox.app/@dot
-;../org.eclipse.equinox.common/@dot
-;../org.eclipse.equinox.preferences/@dot
-;../org.eclipse.equinox.registry/@dot
-;../org.eclipse.equinox.supplement/@dot
-;../org.eclipse.help/@dot
-;../org.eclipse.help.ui/@dot
-;../org.eclipse.jdt.core.manipulation/@dot
-;../org.eclipse.jdt.debug/jdi.jar
-;../org.eclipse.jdt.junit/@dot
-;../org.eclipse.jdt.junit.core/@dot
-;../org.eclipse.jface/@dot
-;../org.eclipse.jface.text/@dot
-;../org.eclipse.ltk.core.refactoring/@dot
-;../org.eclipse.ltk.ui.refactoring/@dot
-;../org.eclipse.osgi.services/@dot
-;../org.eclipse.osgi.util/@dot
-;../org.eclipse.osgi/@dot
-;../org.eclipse.search/@dot
-;../org.eclipse.swt.win32.win32.x86/@dot
-;../org.eclipse.team.core/@dot
-;../org.eclipse.team.ui/@dot
-;../org.eclipse.text/@dot
-;../org.eclipse.ui/@dot
-;../org.eclipse.ui.console/@dot
-;../org.eclipse.ui.editors/@dot
-;../org.eclipse.ui.externaltools/@dot
-;../org.eclipse.ui.forms/@dot
-;../org.eclipse.ui.ide/@dot
-;../org.eclipse.ui.navigator/@dot
-;../org.eclipse.ui.views/@dot
-;../org.eclipse.ui.workbench.texteditor/@dot
-;../org.eclipse.ui.workbench/@dot
-;../org.junit/junit.jar
--breakiterator
--use
--splitIndex
--windowtitle "Eclipse JDT API Specification"
--doctitle "Eclipse JDT API Specification"
--header "<b>Eclipse JDT</b><br>Release 3.6"
--bottom "Copyright (c) IBM Corp. and others 2000, 2009.  All Rights Reserved."
--group "Java development tools core plug-in packages" "org.eclipse.jdt.core
-;org.eclipse.jdt.core.*"
--group "Java development tools UI plug-in packages" "org.eclipse.jdt.ui
-;org.eclipse.jdt.ui.*"
--link http://java.sun.com/javase/6/docs/api
--linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api ../org.eclipse.platform.doc.isv/reference/api
--link http://bundles.osgi.org/javadoc/r4
--tag 'noimplement:a:Restriction:'
--tag 'noextend:a:Restriction:'
--tag 'noreference:a:Restriction:'
--tag 'noinstantiate:a:Restriction:'
--tag 'nooverride:a:Restriction:'
--tag 'category:a:Category:'
-
-org.eclipse.ant.launching
-org.eclipse.ant.ui.launching
-org.eclipse.jdt.core
-org.eclipse.jdt.core.compiler
-org.eclipse.jdt.core.dom
-org.eclipse.jdt.core.dom.rewrite
-org.eclipse.jdt.core.eval
-org.eclipse.jdt.core.formatter
-org.eclipse.jdt.core.jdom
-org.eclipse.jdt.core.manipulation
-org.eclipse.jdt.core.refactoring
-org.eclipse.jdt.core.refactoring.descriptors
-org.eclipse.jdt.core.refactoring.participants
-org.eclipse.jdt.core.search
-org.eclipse.jdt.core.util
-org.eclipse.jdt.debug.core
-org.eclipse.jdt.debug.eval
-org.eclipse.jdt.debug.ui
-org.eclipse.jdt.debug.ui.launchConfigurations
-org.eclipse.jdt.launching
-org.eclipse.jdt.launching.environments
-org.eclipse.jdt.launching.sourcelookup
-org.eclipse.jdt.launching.sourcelookup.containers
-org.eclipse.jdt.ui
-org.eclipse.jdt.ui.actions
-org.eclipse.jdt.ui.cleanup
-org.eclipse.jdt.ui.dialogs
-org.eclipse.jdt.ui.jarpackager
-org.eclipse.jdt.ui.refactoring
-org.eclipse.jdt.ui.search
-org.eclipse.jdt.ui.text
-org.eclipse.jdt.ui.text.folding
-org.eclipse.jdt.ui.text.java
-org.eclipse.jdt.ui.text.java.hover
-org.eclipse.jdt.ui.wizards
-org.eclipse.jdt.junit
-org.eclipse.jdt.junit.launcher
-org.eclipse.jdt.junit.model
-org.eclipse.jdt.junit.wizards

diff --git a/bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt b/bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt
deleted file mode 100644
index 844d1ca..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/jdtaptOptions.txt
+++ /dev/null

@@ -1,111 +0,0 @@
--quiet
--encoding "iso-8859-1"
--charset "iso-8859-1"
--sourcepath "../org.eclipse.jdt.core/antadapter
-;../org.eclipse.jdt.core/batch
-;../org.eclipse.jdt.core/codeassist
-;../org.eclipse.jdt.core/compiler
-;../org.eclipse.jdt.core/dom
-;../org.eclipse.jdt.core/eval
-;../org.eclipse.jdt.core/formatter
-;../org.eclipse.jdt.core/model
-;../org.eclipse.jdt.core/search
-;../org.eclipse.jdt.debug/model
-;../org.eclipse.jdt.debug/jdi
-;../org.eclipse.jdt.debug/eval
-;../org.eclipse.jdt.debug.ui/ui
-;../org.eclipse.jdt.junit/src
-;../org.eclipse.jdt.junit.core/src
-;../org.eclipse.jdt.junit.runtime/src
-;../org.eclipse.jdt.launching/launching
-;../org.eclipse.jdt.ui/ui
-;../org.eclipse.jdt.ui/core refactoring
-;../org.eclipse.jdt.ui/ui refactoring
-;../org.eclipse.jdt.ui/core extension
-;../org.eclipse.jdt.core.manipulation/refactoring
-;../org.eclipse.jdt.core.manipulation/common
-;../org.eclipse.jdt.apt.core/src"
--d reference/apt
--classpath ${bootclasspath}
-;../com.ibm.icu_4.0.1.v20090822.jar
-;../org.eclipse.jdt.apt.core/mirrorapi.jar
-;../org.apache.ant_1.7.1.v20090120-1145/lib/ant.jar
-;../org.eclipse.ant.core/@dot
-;../org.eclipse.compare/@dot
-;../org.eclipse.compare.core/@dot
-;../org.eclipse.core.commands/@dot
-;../org.eclipse.core.contenttype/@dot
-;../org.eclipse.core.expressions/@dot
-;../org.eclipse.core.externaltools/@dot
-;../org.eclipse.core.filebuffers/@dot
-;../org.eclipse.core.filesystem/@dot
-;../org.eclipse.core.jobs/@dot
-;../org.eclipse.core.resources/@dot
-;../org.eclipse.core.runtime/@dot
-;../org.eclipse.core.runtime.content/@dot
-;../org.eclipse.core.runtime.jobs/@dot
-;../org.eclipse.core.runtime.preferences/@dot
-;../org.eclipse.core.variables/@dot
-;../org.eclipse.debug.core/@dot
-;../org.eclipse.debug.ui/@dot
-;../org.eclipse.equinox.app/@dot
-;../org.eclipse.equinox.common/@dot
-;../org.eclipse.equinox.preferences/@dot
-;../org.eclipse.equinox.registry/@dot
-;../org.eclipse.equinox.supplement/@dot
-;../org.eclipse.help/@dot
-;../org.eclipse.help.ui/@dot
-;../org.eclipse.jdt.core/@dot
-;../org.eclipse.jdt.core.manipulation/@dot
-;../org.eclipse.jdt.debug/jdi.jar
-;../org.eclipse.jdt.junit/@dot
-;../org.eclipse.jdt.junit.core/@dot
-;../org.eclipse.jface/@dot
-;../org.eclipse.jface.text/@dot
-;../org.eclipse.ltk.core.refactoring/@dot
-;../org.eclipse.ltk.ui.refactoring/@dot
-;../org.eclipse.osgi.services/@dot
-;../org.eclipse.osgi.util/@dot
-;../org.eclipse.osgi/@dot
-;../org.eclipse.search/@dot
-;../org.eclipse.swt.win32.win32.x86/@dot
-;../org.eclipse.team.core/@dot
-;../org.eclipse.team.ui/@dot
-;../org.eclipse.text/@dot
-;../org.eclipse.ui/@dot
-;../org.eclipse.ui.console/@dot
-;../org.eclipse.ui.editors/@dot
-;../org.eclipse.ui.externaltools/@dot
-;../org.eclipse.ui.forms/@dot
-;../org.eclipse.ui.ide/@dot
-;../org.eclipse.ui.navigator/@dot
-;../org.eclipse.ui.views/@dot
-;../org.eclipse.ui.workbench.texteditor/@dot
-;../org.eclipse.ui.workbench/@dot
-;../org.junit/junit.jar
--breakiterator
--use
--splitIndex
--windowtitle "Eclipse JDT API Specification"
--doctitle "Eclipse JDT API Specification"
--header "<b>Eclipse JDT</b><br>Release 3.6"
--bottom "Copyright (c) IBM Corp. and others 2000, 2009.  All Rights Reserved."
--group "Java development tools APT plug-in packages" "org.eclipse.jdt.apt.core
-;org.eclipse.jdt.apt.core.*"
--link http://java.sun.com/javase/6/docs/api
--linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api ../org.eclipse.platform.doc.isv/reference/api
--linkoffline ./../../../org.eclipse.jdt.doc.isv/reference/api ./reference/api
--link http://bundles.osgi.org/javadoc/r4
--tag 'noimplement:a:Restriction:'
--tag 'noextend:a:Restriction:'
--tag 'noreference:a:Restriction:'
--tag 'noinstantiate:a:Restriction:'
--tag 'nooverride:a:Restriction:'
-
-org.eclipse.jdt.apt.core.build
-org.eclipse.jdt.apt.core.env
-org.eclipse.jdt.apt.core.util
-com.sun.mirror.apt
-com.sun.mirror.declaration
-com.sun.mirror.type
-com.sun.mirror.util

diff --git a/bundles/org.eclipse.jdt.doc.isv/notices.html b/bundles/org.eclipse.jdt.doc.isv/notices.html
deleted file mode 100644
index b2201a7..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2009.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/plugin.properties b/bundles/org.eclipse.jdt.doc.isv/plugin.properties
deleted file mode 100644
index ae49064..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName=Eclipse JDT Plug-in Developer Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.jdt.doc.isv/plugin.xml b/bundles/org.eclipse.jdt.doc.isv/plugin.xml
deleted file mode 100644
index 3c90aa5..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/plugin.xml
+++ /dev/null

@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-
-<!-- ===================================================== -->
-<!-- Declare the documentation for the JDT ISV Guide       -->
-<!-- We will declare only one infoset (book)               -->
-<!-- ===================================================== -->
-
-<plugin>
-
-
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc"> 
-       <toc file="toc.xml" primary="true" />
-       <index path="index"/>
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc">
-       <toc file="topics_Guide.xml" />
-       <toc file="topics_Reference.xml" />
-       <toc file="topics_Porting.xml"/>
-       <toc file="topics_Questions.xml" />
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- Define Javadoc locations                                                      -->
-<!-- ============================================================================= -->
-   <extension point="org.eclipse.pde.core.javadoc">
-       <javadoc path="reference/api">
-           <plugin id="org.eclipse.ant.launching"/>
-           <plugin id="org.eclipse.ant.ui"/>
-           <plugin id="org.eclipse.jdt.core"/>
-           <plugin id="org.eclipse.jdt.core.manipulation"/>
-           <plugin id="org.eclipse.jdt.debug"/>
-           <plugin id="org.eclipse.jdt.debug.ui"/>
-           <plugin id="org.eclipse.jdt.launching"/>
-           <plugin id="org.eclipse.jdt.ui"/>
-           <plugin id="org.eclipse.jdt.apt.ui"/>
-           <plugin id="org.eclipse.jdt.apt.core"/>
-           <plugin id="org.eclipse.jdt.junit"/>
-           <plugin id="org.eclipse.jdt.junit.core"/>
-       </javadoc>
-   </extension>
-   
-</plugin>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.2/faq.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.2/faq.html
deleted file mode 100644
index fdafd38..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.2/faq.html
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse JDT 3.2 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse JDT 3.2 Plug-in Migration FAQ</h1>
-<ol>
-	<li>None</li>
-</ol>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.2/incompatibilities.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.2/incompatibilities.html
deleted file mode 100644
index 1d8879d..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.2/incompatibilities.html
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse JDT 3.1 and 3.2</title>
-</head>
-
-<body>
-
-<h1>Incompatibilities between Eclipse JDT 3.1 and 3.2</h1>
-
-<p> Eclipse changed in incompatible ways between 3.1 and 3.2 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.1 plug-ins to 3.2. Note that you only need to look 
-  here if you are experiencing problems running your 3.1 plug-in on 3.2.</p>
-<ol>
-  <li><a href="#NullClassLoaderObject">API contract changes to IJavaReferenceType</a></li>
-</ol>
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="NullClassLoaderObject"></a>API contract changes to IJavaReferenceType</h2>
-<p><strong>What is affected:</strong> Clients that call <code>IJavaReferenceType.getClassLoaderObject()</code>.</p>
-<p><strong>Description:</strong> In Eclipse 3.1, the method <code>org.eclipse.jdt.debug.core.IJavaReferenceType.getClassLoaderObject()</code> 
-  was added to <code>IJavaReferenceType</code>. The method was not specified to 
-  return <code>null</code>, but could. In Eclipse 3.2, the specification has been 
-  updated to indicate that <code>null</code> is a valid return value. The behavior 
-  of the method has not changed, but callers should be aware that <code>null</code> 
-  can be returned and should add appropriate checks.</p>
-<p><strong>Action required:</strong> Clients calling <code>IJavaReferenceType.getClassLoaderObject()</code> 
-  should be modified to handle <code>null</code> as a return value.</p>
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.2/recommended.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.2/recommended.html
deleted file mode 100644
index c6e9ca5..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.2/recommended.html
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Changes required when adopting 3.2 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Changes required when adopting 3.2 mechanisms and APIs</h1>
-<p>This section describes changes that are required if you are trying to change 
-  your 3.1 plug-in to adopt the 3.2 mechanisms and APIs.</p>
-  
-<ol>
-	<li><a href="#compilationParticipant">Compilation participant extension point</a></li>
-</ol>
-
-<h2><a name="compilationParticipant">Compilation participant extension point</a></h2>
-	<p>A new extension point (<code>org.eclipse.jdt.core.compilationParticipant</code>) allows plugins that are dependent on
-	<code>org.eclipse.jdt.core</code> to participate in the Java build process, as well as in the reconciling of Java editors.</p>
-	<p>By implementing <code>org.eclipse.jdt.core.compiler.CompilationParticipant</code> and extending this extension
-	point, one can be notified when a build is starting, when a clean is starting, or when a working copy (in a Java editor) is being
-	reconciled. During these notifcations, types can be added, changed or removed, build markers can be created, or errors
-	can be reported to the Java editor.</p>
-  
-  </body>
-
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.3/faq.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.3/faq.html
deleted file mode 100644
index 5729119..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.3/faq.html
+++ /dev/null

@@ -1,131 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse JDT 3.3 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse JDT 3.3 Plug-in Migration FAQ</h1>
-<ol>
-	<li><a href="#deprecatedWorkingCopyMethods">How can I remove deprecation warning I get on <code>*WorkingCopy(...IProblemRequestor...)</code> methods and keep same behavior?</a></li>
-</ol>
-<h2><a name="deprecatedWorkingCopyMethods">How can I remove deprecation warning I get on <code>*WorkingCopy(...IProblemRequestor...)</code> methods and keep same behavior?</a></h2>
-<p>
-While implementing bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=175243">175243</a>, following methods
-have been deprecated:</p>
-<ol>
-<li><code>ICompilationUnit#becomeWorkingCopy(IProblemRequestor, IProgressMonitor)</code></li>
-<li><code>ICompilationUnit#getWorkingCopy(WorkingCopyOwner, IProblemRequestor, IProgressMonitor)</code></li>
-<li><code>IClassFile#becomeWorkingCopy(IProblemRequestor, WorkingCopyOwner, IProgressMonitor)</code></li>
-<li><code>WorkingCopyOwner#newWorkingCopy(String, IClasspathEntry[], IProblemRequestor, IProgressMonitor)</code></li>
-</ol>
-This answer gives some advice to use new API corresponding methods without changing
-the behavior of the existing code.
-How to re-write the code depends on the fact that given problem requestor was null or not
-(i.e. if the client code was interested in reporting problems of the working copy):
-<ol>
-	<li><strong>Problem requestor was null</strong>
-	<p>
-	There's no specific migration issue when the given requestor was null.
-	</p><p>
-	So, following snippet warned for calls to deprecated methods...:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	WorkingCopyOwner owner = new WorkingCopyOwner() {};
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(new WorkingCopyOwner() {}, null, null);
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(null, null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, null, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(null, owner, null);</b>
-	</pre><p>
-	... can now be easily rewritten as follow due to the fact that default owner's problem requestor is null:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	WorkingCopyOwner owner = new WorkingCopyOwner() {};
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	// just remove the IProblemRequestor parameter
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(new WorkingCopyOwner() {}, null); 
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(null, owner, null);</b>
-	</pre>
-	</li>
-	<li><strong>Problem requestor was not null</strong>
-	<p>
-	In this case, client must ensure that the working copy owner requestor is the same than
-	the one given as parameter to the deprecated method. The simplest way to to this is to make
-	the working copy owner returning this requestor.
-	</p><p>
-	So, following snippet warned for calls to deprecated methods...:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	WorkingCopyOwner owner = new WorkingCopyOwner() {};
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	IProblemRequestor requestor = new IProblemRequestor {
-		public void acceptProblem(IProblem problem) {}
-		public void beginReporting() {}
-		public void endReporting() {}
-		public boolean isActive() {
-			return true;
-		}
-	};
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(new WorkingCopyOwner() {}, requestor, null);
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(requestor, null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, requestor, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(requestor, owner, null);</b>
-	</pre><p>
-	... needs to be rewritten as follow to keep the same behavior:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	// Make the requestor final...
-	final IProblemRequestor requestor = new IProblemRequestor {
-		public void acceptProblem(IProblem problem) {}
-		public void beginReporting() {}
-		public void endReporting() {}
-		public boolean isActive() {
-			return true;
-		}
-	};
-	// ...and let the created working copy owner returning it
-	WorkingCopyOwner owner = new WorkingCopyOwner() {
-		public IProblemRequestor getProblemRequestor(ICompilationUnit unit) {
-			return requestor;
-		}
-	};
-	// Calls can now be done to the new API methods using this working copy owner
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(owner, null); 
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(owner, null);
-	</b>
-	</pre>
-	</li>
-</ol>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.3/incompatibilities.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.3/incompatibilities.html
deleted file mode 100644
index 74a2e36..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.3/incompatibilities.html
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse JDT 3.2 and 3.3</title>
-</head>
-
-<body>
-
-<h1>Incompatibilities between Eclipse JDT 3.2 and 3.3</h1>
-
-<p> Eclipse changed in incompatible ways between 3.2 and 3.3 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.2 plug-ins to 3.3. Note that you only need to look 
-  here if you are experiencing problems running your 3.2 plug-in on 3.3.</p>
-<ol>
-  <li><a href="#IClassFile">API contract changes to IClassFile</a></li>
-</ol>
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="IClassFile"></a>API contract changes to IClassFile</h2>
-<p><strong>What is affected:</strong> Clients that call <code>IClassFile.getType()</code>.</p>
-<p><strong>Description:</strong> In Eclipse 3.2, the method <code>org.eclipse.jdt.core.IClassFile.getType()</code> 
-  threw a <code>org.eclipse.jdt.core.JavaModelException</code>. This is no longer the case in Eclipse 3.3!
-  <i>Note that this change has no impact on binary compatibility</i>.</p>
-<p><strong>Action required:</strong> Clients calling <code>IClassFile.getType()</code> 
-  will have to fix possible <strong>'Unreachable catch block for JavaModelException'</strong> compiler errors
-  (only if this call is the only one throwing a <code>JavaModelException</code> in the try block).
-  They also should verify for methods calling this API and throwing a <code>JavaModelException</code>
-  that they still need to throw this exception.</p>
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.3/recommended.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.3/recommended.html
deleted file mode 100644
index 501430d..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.3/recommended.html
+++ /dev/null

@@ -1,136 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Adopting 3.3 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Adopting 3.3 mechanisms and APIs</h1>
-<p>This section describes changes that are required if you are trying to change 
-  your 3.2 plug-in to adopt the 3.3 mechanisms and APIs.</p>
-  
-<ol>
-	<li><a href="#deprecatedWorkingCopyMethods">How can I remove deprecation warning I get on <code>*WorkingCopy(...IProblemRequestor...)</code> methods and keep same behavior?</a></li>
-</ol>
-<h2><a name="deprecatedWorkingCopyMethods">1. How can I remove deprecation warning I get on <code>*WorkingCopy(...IProblemRequestor...)</code> methods and keep same behavior?</a></h2>
-<p>
-While implementing bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=175243">175243</a>, following methods
-have been deprecated:</p>
-<ol>
-<li><code>ICompilationUnit#becomeWorkingCopy(IProblemRequestor, IProgressMonitor)</code></li>
-<li><code>ICompilationUnit#getWorkingCopy(WorkingCopyOwner, IProblemRequestor, IProgressMonitor)</code></li>
-<li><code>IClassFile#becomeWorkingCopy(IProblemRequestor, WorkingCopyOwner, IProgressMonitor)</code></li>
-<li><code>WorkingCopyOwner#newWorkingCopy(String, IClasspathEntry[], IProblemRequestor, IProgressMonitor)</code></li>
-</ol>
-<p>This answer gives some advice to use new API corresponding methods without changing
-the behavior of the existing code.
-</p>
-How to re-write the code depends on the fact that given problem requestor was null or not
-(i.e. if the client code was interested in reporting problems of the working copy):
-<ol>
-	<li><strong>Problem requestor was null</strong>
-	<p>
-	There's no specific migration issue when the given requestor was null.
-	</p><p>
-	So, following snippet warned for calls to deprecated methods...:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	WorkingCopyOwner owner = new WorkingCopyOwner() {};
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(new WorkingCopyOwner() {}, null, null);
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(null, null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, null, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(null, owner, null);</b>
-	</pre><p>
-	... can now be easily rewritten as follow due to the fact that default owner's problem requestor is null:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	WorkingCopyOwner owner = new WorkingCopyOwner() {};
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	// just remove the IProblemRequestor parameter
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(new WorkingCopyOwner() {}, null); 
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(null, owner, null);</b>
-	</pre>
-	</li>
-	<li><strong>Problem requestor was not null</strong>
-	<p>
-	In this case, client must ensure that the working copy owner requestor is the same than
-	the one given as parameter to the deprecated method. The simplest way to to this is to make
-	the working copy owner returning this requestor.
-	</p><p>
-	So, following snippet warned for calls to deprecated methods...:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	WorkingCopyOwner owner = new WorkingCopyOwner() {};
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	IProblemRequestor requestor = new IProblemRequestor {
-		public void acceptProblem(IProblem problem) {}
-		public void beginReporting() {}
-		public void endReporting() {}
-		public boolean isActive() {
-			return true;
-		}
-	};
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(new WorkingCopyOwner() {}, requestor, null);
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(requestor, null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, requestor, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(requestor, owner, null);</b>
-	</pre><p>
-	... needs to be rewritten as follow to keep the same behavior:</p>
-	<pre>
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/pack/X.java"));
-	ICompilationUnit compilationUnit = (ICompilationUnit)JavaCore.create(file);
-	IFile file = getWorkspaceRoot().getFile(new Path("FAQ/bin/pack/Y.class"));
-	IClassFile classFile = JavaCore.createClassFileFrom(file);
-	IClasspathEntry[] entries = classFile.getJavaProject().getResolvedClasspath(true);
-	<b>
-	// Make the requestor final...
-	final IProblemRequestor requestor = new IProblemRequestor {
-		public void acceptProblem(IProblem problem) {}
-		public void beginReporting() {}
-		public void endReporting() {}
-		public boolean isActive() {
-			return true;
-		}
-	};
-	// ...and let the created working copy owner returning it
-	WorkingCopyOwner owner = new WorkingCopyOwner() {
-		public IProblemRequestor getProblemRequestor(ICompilationUnit unit) {
-			return requestor;
-		}
-	};
-	// Calls can now be done to the new API methods using this working copy owner
-	ICompilationUnit workingCopy = compilationUnit.getWorkingCopy(owner, null); 
-	ICompilationUnit newWorkingCopy = compilationUnit.becomeWorkingCopy(null);
-	ICompilationUnit newWorkingCopy2 = owner.newWorkingCopy(new Path("FAQ/test/Z.java"), entries, null);
-	ICompilationUnit classWorkingCopy = classFile.becomeWorkingCopy(owner, null);
-	</b>
-	</pre>
-	</li>
-</ol>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.4/faq.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.4/faq.html
deleted file mode 100644
index 734946c..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.4/faq.html
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.4 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.4 Plug-in Migration FAQ</h1>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2><a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.4/incompatibilities.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.4/incompatibilities.html
deleted file mode 100644
index 01c35f6..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.4/incompatibilities.html
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.3 and 3.4</title>
-</head>
-<body>
-<h1>Incompatibilities between Eclipse 3.3 and 3.4</h1>
-
-<p>
-  Eclipse changed in incompatible ways between 3.3 and 3.4 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.3 plug-ins to 3.4. Note that you only need to look 
-  here if you are experiencing problems running your 3.3 plug-in on 3.4.
-</p>
-
-<ol>
-  <li><a href="#ExternalFolders">Library entries on the build path can now target external folders</a></li>
-  <li><a href="#ZipArchives">Assumption that a ZIP archive extension was always .zip or .jar has been removed</a></li>
-  <li><a href="#BinaryQualifiedName">Asking the qualified name of a binary type with a dot ('.') separator will now honor this separator</a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="ExternalFolders">Library entries on the build path can now target external folders</a></h2>
-<p><strong>What is affected:</strong> Clients that call <code>IJavaProject.getResolvedClasspath(boolean)</code>,
-  <code>IJavaProject.getRawClasspath()</code>, or <code>IPackageFragmentRoot.getPath()</code>.</p>
-<p><strong>Description:</strong> In Eclipse 3.3, the class folders on a classpath could only be inside the workspace.
-  In Eclipse 3.4, these class folders can also be outside the workspace.
-  <i>Note that this change has no impact on binary compatibility</i>.</p>
-<p><strong>Action required:</strong> Clients retrieving the <code>IPath</code> from a class folder on the
-  classpath should no longer assume that this path is internal to the workspace.
-</p>
-
-<!-- ############################################## -->
-
-<!-- ############################################## -->
-<h2>2. <a name="ZipArchives">Assumption that a ZIP archive extension was always ".zip" or ".jar" has been removed</a></h2>
-<p><strong>What is affected:</strong> Clients that call <code>IJavaProject.getResolvedClasspath(boolean)</code>,
-  <code>IJavaProject.getRawClasspath()</code>, <code>IPackageFragmentRoot.getPath()</code>, or
-  <code>JavaConventions.validateClasspath(IJavaProject, IClasspathEntry[], IPath)</code>.</p>
-<p><strong>Description:</strong> In Eclipse 3.3, the ZIP archives on a classpath could only have a ".zip" or a ".jar" extension.
-  In Eclipse 3.4, these ZIP archives can have any extension. Thus the classpath validation will no longer report an error
-  if a ZIP archive with an extension other than ".zip" or ".jar" is put on the classpath.
-  <i>Note that this change has no impact on binary compatibility</i>.</p>
-<p><strong>Action required:</strong> Clients should no longer assume that the only valid extensions for ZIP archives on
-  the classpath are ".zip" or ".jar".
-</p>
-
-<!-- ############################################## -->
-
-<!-- ############################################## -->
-<h2>3. <a name="BinaryQualifiedName">Asking the qualified name of a binary type with a dot ('.') separator will now honor this separator</a></h2>
-<p><strong>What is affected:</strong> Clients that call <code>IType.getTypeQualifiedName(char)</code>, or
-  <code>IType.getFullyQualifiedName(char)</code> on a binary member type with a dot ('.') separator.</p>
-<p><strong>Description:</strong> In Eclipse 3.3, calling <code>IType.getTypeQualifiedName(char)</code>, or
-  <code>IType.getFullyQualifiedName(char)</code> on a binary member type with a dot ('.') separator would return
-  a qualified name where the member type name was separated from the enclosing type name with a dollar ('$').
-  In Eclipse 3.4, calling <code>IType.getTypeQualifiedName(char)</code>, or
-  <code>IType.getFullyQualifiedName(char)</code> on a binary member type with a dot ('.') separator now correctly
-  honor this separator.
-  <i>Note that this change has no impact on binary compatibility</i>.</p>
-<p><strong>Action required:</strong> Clients should no longer assume that the member type separator in the qualified name
-  of a binary type is always dollar ('$').
-</p>
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.4/recommended.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.4/recommended.html
deleted file mode 100644
index ceb4e9a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.4/recommended.html
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adopting 3.4 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Adopting 3.4 mechanisms and APIs</h1>
-<p>
-  This section describes changes that are required if you are trying to change 
-  your 3.3 plug-in to adopt the 3.4 mechanisms and APIs.
-</p>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2>1. <a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.5/faq.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.5/faq.html
deleted file mode 100644
index 0cbc131..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.5/faq.html
+++ /dev/null

@@ -1,118 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.5 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.5 Plug-in Migration FAQ</h1>
-
-<ol>
-	<li><a href="#wildcarddeprecation">How can I remove the deprecation warning I get on 
-	<code>createWilcardTypeBindingKey(String, char)</code> method ?</a></li>
-	<li><a href="#deprecatedSuggestVariableNames">How can I remove the deprecation warning I get on
-	<code>NamingConventions.suggest*Names(...)</code> methods and keep same behavior?</a></li>
-	<li><a href="#deprecatedRemovePrefixAndSuffix">How can I remove the deprecation warning I get on
-	<code>NamingConventions.removePrefixAndSuffixFor*Name(...)</code> methods and keep same behavior?</a></li>
-</ol>
-<h2><a name="wildcarddeprecation">How can I remove the deprecation warning I get on 
-<code>createWilcardTypeBindingKey(String, char)</code> method ?</a></h2>
-<p>
-While implementing the fix for bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=234609">234609</a>,
-the method <code>org.eclipse.jdt.core.BindingKey.createWilcardTypeBindingKey(String, char)</code>
-has been deprecated. 
-
-In order to create a wildcard binding the following pieces of information are needed:</p>
-<ol>
-<li> a generic type (a wildcard is always the wildcard of a generic type)</li>
-<li>a kind</li>
-<li>a bound type (optional)</li>
-<li>a rank (the relative position of the wildcard in the type argument list, e.g. in 
-<code>HashMap&lt;? extends Integer,? super String&gt;</code>, the wildcard type 
-<code>? extends Integer</code> has a rank of 0 while the following wildcard has a rank of 1)</li>
-</ol>
-<p>
-All this information should be encoded in the binding key.</p>
-
-<p>
-However, <code>BindingKey.createWilcardTypeBindingKey(String, char)</code> allows to pass in only partial information.
-Thus this API is not enough to create a proper binding key from which a wildcard type could be recreated. 
-Hence this method has been deprecated and it is recommended that uses of this method be replaced with the
-new API <code>org.eclipse.jdt.core.BindingKey.createWildcardTypeBindingKey(String genericTypeKey, char boundKind, String boundTypeKey, int rank)</code> introduced as of version 3.5.
-</p>
-
-<!-- ############################################## -->
-<h2><a name="deprecatedSuggestVariableNames">How can I remove deprecation warning I get on <code>NamingConventions.suggest*Names(...)</code> methods and keep same behavior?</a></h2>
-<p>
-While implementing bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=38111">38111</a>, following methods
-have been deprecated:</p>
-<ol>
-<li><code>NamingConventions#suggestArgumentNames(IJavaProject, char[], char[], int, char[][])</code></li>
-<li><code>NamingConventions#suggestArgumentNames(IJavaProject, String, String, int, String[])</code></li>
-<li><code>NamingConventions#suggestFieldNames(IJavaProject, char[], char[], int, int, char[][])</code></li>
-<li><code>NamingConventions#suggestFieldNames(IJavaProject, String, String, int, int, String[])</code></li>
-<li><code>NamingConventions#suggestLocalVariableNames(IJavaProject, char[], char[], int, char[][])</code></li>
-<li><code>NamingConventions#suggestLocalVariableNames(IJavaProject, String, String, int, String[])</code></li>
-</ol>
-
-<p>This answer gives some advice to use new API corresponding methods without changing the behavior of the existing code.<br>
-A call to one of these methods can be replaced by a call to <code>NamingConventions#suggestVariableNames(int, int, String, IJavaProject, int, String[], boolean)</code></p>
-
-<ul>
-<li>A call to <code>suggestArgumentNames(...)</code> can be replaced by a call to <code>suggestVariableNames(...)</code>  with <code>NamingConventions#VK_PARAMETER</code> as variable kind</li>
-<li>A call to <code>suggestFieldNames(...)</code> can be replaced by a call to <code>suggestVariableNames(...)</code>  with <code>NamingConventions#VK_INSTANCE_FIELD</code> or <code>NamingConventions#VK_STATIC_FIELD</code> as variable kind</li>
-<li>A call to <code>suggestLocalVariableNames(...)</code> can be replaced by a call to <code>suggestVariableNames(...)</code>  with <code>NamingConventions#VK_LOCAL</code> as variable kind</li>
-</ul>
-
-<p>The following code</p>
-<pre>
-	IJavaProject javaProject = ... ;
-	String[] argumentNames = NamingConventions.suggestArgumentNames(javaProject, "java.util", "ArrayList", 0, null);
-</pre>
-<p>can be replaced by:</p>
-<pre>
-	IJavaProject javaProject = ... ;
-	String[] argumentNames = NamingConventions.suggestVariableNames(NamingConventions.VK_PARAMETER, NamingConventions.BK_TYPE_NAME, "ArrayList", javaProject, 0, null, true);
-</pre>
-
-<!-- ############################################## -->
-<h2><a name="deprecatedRemovePrefixAndSuffix">How can I remove deprecation warning I get on <code>NamingConventions.removePrefixAndSuffixFor*Name(...)</code> methods and keep same behavior?</a></h2>
-<p>
-While implementing bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=38111">38111</a>, following methods
-have been deprecated:</p>
-<ol>
-<li><code>NamingConventions#removePrefixAndSuffixForArgumentName(IJavaProject, char[])</code></li>
-<li><code>NamingConventions#removePrefixAndSuffixForArgumentName(IJavaProject, String)</code></li>
-<li><code>NamingConventions#removePrefixAndSuffixForFieldName(IJavaProject, char[], int)</code></li>
-<li><code>NamingConventions#removePrefixAndSuffixForFieldName(IJavaProject, String, int)</code></li>
-<li><code>NamingConventions#removePrefixAndSuffixForLocalVariableName(IJavaProject, char[])</code></li>
-<li><code>NamingConventions#removePrefixAndSuffixForLocalVariableName(IJavaProject, String)</code></li>
-</ol>
-
-<p>This answer gives some advice to use new API corresponding methods without changing the behavior of the existing code.<br>
-A call to one of these methods can be replaced by a call to <code>NamingConventions#getBaseName(int, String, IJavaProject)</code></p>
-
-<ul>
-<li>A call to <code>removePrefixAndSuffixForArgumentName(...)</code> can be replaced by a call to <code>getBaseName(...)</code>  with <code>NamingConventions#VK_PARAMETER</code> as variable kind</li>
-<li>A call to <code>removePrefixAndSuffixForFieldName(...)</code> can be replaced by a call to <code>getBaseName(...)</code>  with <code>NamingConventions#VK_INSTANCE_FIELD</code> or <code>NamingConventions#VK_STATIC_FIELD</code> as variable kind</li>
-<li>A call to <code>removePrefixAndSuffixForLocalVariableName(...)</code> can be replaced by a call to <code>getBaseName(...)</code>  with <code>NamingConventions#VK_LOCAL</code> as variable kind</li>
-</ul>
-
-<p>The following code</p>
-<pre>
-	IJavaProject javaProject = ... ;
-	String name = NamingConventions.removePrefixAndSuffixForArgumentName(javaProject, "preNamesuf");
-</pre>
-<p>can be replaced by</p>
-<pre>
-	IJavaProject javaProject = ... ;
-	String name = NamingConventions.getBaseName(NamingConventions.VK_PARAMETER, "preNamesuf", javaProject);
-</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.5/incompatibilities.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.5/incompatibilities.html
deleted file mode 100644
index ca71977..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.5/incompatibilities.html
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.4 and 3.5</title>
-</head>
-<body>
-<h1>Incompatibilities between Eclipse 3.4 and 3.5</h1>
-
-<p>
-  Eclipse changed in incompatible ways between 3.4 and 3.5 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.4 plug-ins to 3.5. Note that you only need to look 
-  here if you are experiencing problems running your 3.4 plug-in on 3.5.
-</p>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2><a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.5/recommended.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.5/recommended.html
deleted file mode 100644
index 94831e5..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.5/recommended.html
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adopting 3.5 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Adopting 3.5 mechanisms and APIs</h1>
-<p>
-  This section describes changes that are required if you are trying to change 
-  your 3.4 plug-in to adopt the 3.5 mechanisms and APIs.
-</p>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2>1. <a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.6/faq.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.6/faq.html
deleted file mode 100644
index 6194a2a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.6/faq.html
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.6 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.6 Plug-in Migration FAQ</h1>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2><a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.6/incompatibilities.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.6/incompatibilities.html
deleted file mode 100644
index 3ed809c..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.6/incompatibilities.html
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.5 and 3.6</title>
-</head>
-<body>
-<h1>Incompatibilities between Eclipse 3.5 and 3.6</h1>
-
-<p>
-  Eclipse changed in incompatible ways between 3.5 and 3.6 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.5 plug-ins to 3.6. Note that you only need to look 
-  here if you are experiencing problems running your 3.5 plug-in on 3.6.
-</p>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2><a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/3.6/recommended.html b/bundles/org.eclipse.jdt.doc.isv/porting/3.6/recommended.html
deleted file mode 100644
index 2976096..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/3.6/recommended.html
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adopting 3.6 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Adopting 3.6 mechanisms and APIs</h1>
-<p>
-  This section describes changes that are required if you are trying to change 
-  your 3.5 plug-in to adopt the 3.6 mechanisms and APIs.
-</p>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2>1. <a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_2_porting_guide.html b/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_2_porting_guide.html
deleted file mode 100644
index b1b15a3..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_2_porting_guide.html
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse JDT 3.2 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse JDT 3.2 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse JDT 3.1 (or earlier) plug-ins to Eclipse JDT 3.2.</p>
-<p>One of the goals of Eclipse 3.2 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.1 APIs should continue to work in 3.2 in spite of the 
-  API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.1 APIs remains valid for 
-  3.2, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.2 libraries.</p>
-<p>While every effort way made to avoid breakage, there are a few areas of incompatibility. 
-  This document describes the areas where Eclipse changed in incompatible ways 
-  between 3.1 and 3.2, and provides instructions for migrating 3.1 plug-ins to 
-  3.2.</p>
-<ul>
-  <li><a href="3.2/faq.html">Eclipse JDT 3.2 Plug-in Migration FAQ</a></li>
-  <li><a href="3.2/incompatibilities.html">Incompatibilities between Eclipse JDT 3.1 
-    and 3.2</a></li>
-  <li><a href="3.2/recommended.html">Adopting 3.2 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_3_porting_guide.html b/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_3_porting_guide.html
deleted file mode 100644
index 20e51cc..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_3_porting_guide.html
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse JDT 3.3 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse JDT 3.3 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse JDT 3.2 (or earlier) plug-ins to Eclipse JDT 3.3.</p>
-<p>One of the goals of Eclipse 3.3 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.2 APIs should continue to work in 3.3 in spite of the 
-  API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.2 APIs remains valid for 
-  3.3, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.3 libraries.</p>
-<p>While every effort way made to avoid breakage, there are a few areas of incompatibility. 
-  This document describes the areas where Eclipse changed in incompatible ways 
-  between 3.2 and 3.3, and provides instructions for migrating 3.2 plug-ins to 
-  3.3.</p>
-<ul>
-  <li><a href="3.3/faq.html">Eclipse JDT 3.3 Plug-in Migration FAQ</a></li>
-  <li><a href="3.3/incompatibilities.html">Incompatibilities between Eclipse JDT 3.2 
-    and 3.3</a></li>
-  <li><a href="3.3/recommended.html">Adopting 3.3 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_4_porting_guide.html b/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_4_porting_guide.html
deleted file mode 100644
index 882a5bf..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_4_porting_guide.html
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse JDT 3.4 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse JDT 3.4 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse JDT 3.3 plug-ins to Eclipse JDT 3.4.</p>
-<p>One of the goals of Eclipse 3.4 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.3 APIs should continue to work in 3.4 in spite of the 
-  API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.3 APIs remains valid for 
-  3.4, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.4 libraries.</p>
-<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
-  APIs that should be adopted by clients. 
-  This document describes those areas and provides instructions for migrating 3.3 plug-ins to 
-  3.4.</p>
-<ul>
-  <li><a href="3.4/faq.html">Eclipse JDT 3.4 Plug-in Migration FAQ</a></li>
-  <li><a href="3.4/incompatibilities.html">Incompatibilities between Eclipse JDT 3.3 and 3.4</a></li>
-  <li><a href="3.4/recommended.html">Adopting 3.4 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_5_porting_guide.html b/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_5_porting_guide.html
deleted file mode 100644
index 468980a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_5_porting_guide.html
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse JDT 3.5 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse JDT 3.5 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse JDT 3.4 plug-ins to Eclipse JDT 3.5.</p>
-<p>One of the goals of Eclipse 3.5 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.4 APIs should continue to work in 3.5 in spite of the 
-  API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.4 APIs remains valid for 
-  3.5, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.5 libraries.</p>
-<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
-  APIs that should be adopted by clients. 
-  This document describes those areas and provides instructions for migrating 3.4 plug-ins to 
-  3.5.</p>
-<ul>
-  <li><a href="3.5/faq.html">Eclipse JDT 3.5 Plug-in Migration FAQ</a></li>
-  <li><a href="3.5/incompatibilities.html">Incompatibilities between Eclipse JDT 3.4 and 3.5</a></li>
-  <li><a href="3.5/recommended.html">Adopting 3.5 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_6_porting_guide.html b/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_6_porting_guide.html
deleted file mode 100644
index 432896b..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_3_6_porting_guide.html
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse JDT 3.6 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse JDT 3.6 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse JDT 3.5 plug-ins to Eclipse JDT 3.6.</p>
-<p>One of the goals of Eclipse 3.6 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.5 APIs should continue to work in 3.6 in spite of the 
-  API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.5 APIs remains valid for 
-  3.6, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.6 libraries.</p>
-<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
-  APIs that should be adopted by clients. 
-  This document describes those areas and provides instructions for migrating 3.5 plug-ins to 
-  3.6.</p>
-<ul>
-  <li><a href="3.6/faq.html">Eclipse JDT 3.6 Plug-in Migration FAQ</a></li>
-  <li><a href="3.6/incompatibilities.html">Incompatibilities between Eclipse JDT 3.5 and 3.6</a></li>
-  <li><a href="3.6/recommended.html">Adopting 3.6 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/questions/index.html b/bundles/org.eclipse.jdt.doc.isv/questions/index.html
deleted file mode 100644
index ecf813f..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/questions/index.html
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="OTI">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>JDT Questions Index</title>
-</head>
-<body>
-<h1>JDT Questions Index</h1>
-<h2> JDT Core</h2>
-<ul>
-  <li><a href="../guide/jdt_int_core.htm">What is available in the JDT Core 
-    API Packages?</a> </li>
-  <li><a href="../guide/jdt_api_run.htm">How do I launch a Java program from the 
-    platform?</a> </li>
-  <li><a href="../guide/jdt_api_compile.htm">How do I programmatically compile 
-    a Java program?</a> </li>
-  <li><a href="../guide/jdt_api_classpath.htm">How do I setup a project's classpath?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_manip.htm">How do I manipulate Java code?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_search.htm">How do I use the Java search engine?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_options.htm">What are the JDT Core options? </a> 
-  </li>
-  <li><a href="../guide/jdt_api_codeassist.htm">How do I programmatically use 
-    CodeAssist and CodeSelect?</a> </li>
-  <li><a href="../guide/jdt_int_model.htm">How are Java projects, folders, 
-    and files different from regular resources?</a> </li>
-</ul>
-<h2> JDT UI</h2>
-<ul>
-  <li><a href="../guide/jdt_int_ui.htm">What is available in the JDT UI packages?</a> 
-  </li>
-  <li><a href="../guide/jdt_api_open_editor.htm">How do I programmatically open 
-    a Java editor and display a specific Java element in the editor?</a> </li>
-  <li><a href="../guide/jdt_api_prompter.htm">How do I programmatically open 
-    the Open Type dialog?</a> <br>
-  </li>
-  <li><a href="../guide/jdt_api_render.htm">How do I present Java elements in 
-    a standard JFace viewer?</a></li>
-  <li><a href="../guide/jdt_api_write_jar_file.htm">How do I write a Jar file?</a></li>
-  <li><a href="../guide/jdt_api_wizards.htm">How do I create a customized 
-    new Java element wizard page?</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore b/bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore
deleted file mode 100644
index a5939d2..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/.cvsignore
+++ /dev/null

@@ -1,2 +0,0 @@
-apt
-api

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html b/bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html
deleted file mode 100644
index 16b5a27..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/extension-points/index.html
+++ /dev/null

@@ -1,52 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>JDT Extension Points</title>
-<link rel="stylesheet" type="text/css" HREF="../../book.css">
-</head>
-<body>
-<h1>JDT Extension Points</h1>
-<p>The following extension points can be used to extend the capabilities of the 
-  JDT infrastructure: </p>
-<ul>
-  <li><a href="org_eclipse_jdt_apt_core_annotationProcessorFactory.html">org.eclipse.jdt.apt.core.annotationProcessorFactory</a></li>
-  <li><a href="org_eclipse_jdt_core_annotationProcessorManager.html">org.eclipse.jdt.core.annotationProcessorManager</a></li>
-  <li><a href="org_eclipse_jdt_core_classpathContainerInitializer.html">org.eclipse.jdt.core.classpathContainerInitializer</a></li>
-  <li><a href="org_eclipse_jdt_core_classpathVariableInitializer.html">org.eclipse.jdt.core.classpathVariableInitializer</a></li>
-  <li><a href="org_eclipse_jdt_core_compilationParticipant.html">org.eclipse.jdt.core.compilationParticipant</a></li>
-  <li><a href="org_eclipse_jdt_core_codeFormatter.html">org.eclipse.jdt.core.codeFormatter</a></li>
-  <li><a href="org_eclipse_jdt_core_manipulation_changeMethodSignatureParticipants.html">org.eclipse.jdt.core.manipulation.changeMethodSignatureParticipants</a></li>
-  <li><a href="org_eclipse_jdt_debug_breakpointListeners.html">org.eclipse.jdt.debug.breakpointListeners</a> </li>
-  <li><a href="org_eclipse_jdt_debug_javaLogicalStructures.html">org.eclipse.jdt.debug.javaLogicalStructures</a> </li>
-  <li><a href="org_eclipse_jdt_debug_ui_vmInstallPages.html">org.eclipse.jdt.debug.ui.vmInstallPages</a> </li>  
-  <li><a href="org_eclipse_jdt_debug_ui_vmInstallTypePage.html">org.eclipse.jdt.debug.ui.vmInstallTypePage</a> </li>
-  <li><a href="org_eclipse_jdt_junit_junitLaunchConfigs.html">org.eclipse.jdt.junit.junitLaunchConfigs</a> </li>
-  <li><a href="org_eclipse_jdt_junit_testRunListeners.html">org.eclipse.jdt.junit.testRunListeners</a> </li>
-  <li><a href="org_eclipse_jdt_launching_classpathProviders.html">org.eclipse.jdt.launching.classpathProviders</a></li>
-  <li><a href="org_eclipse_jdt_launching_executionEnvironments.html">org.eclipse.jdt.launching.executionEnvironments</a></li>  
-  <li><a href="org_eclipse_jdt_launching_runtimeClasspathEntries.html">org.eclipse.jdt.launching.runtimeClasspathEntries</a> </li>
-  <li><a href="org_eclipse_jdt_launching_runtimeClasspathEntryResolvers.html">org.eclipse.jdt.launching.runtimeClasspathEntryResolvers</a> </li>
-  <li><a href="org_eclipse_jdt_launching_vmConnectors.html">org.eclipse.jdt.launching.vmConnectors</a></li>
-  <li><a href="org_eclipse_jdt_launching_vmInstalls.html">org.eclipse.jdt.launching.vmInstalls</a></li>
-  <li><a href="org_eclipse_jdt_launching_vmInstallTypes.html">org.eclipse.jdt.launching.vmInstallTypes</a></li>
-  <li><a href="org_eclipse_jdt_ui_classpathAttributeConfiguration.html">org.eclipse.jdt.ui.classpathAttributeConfiguration</a></li>
-  <li><a href="org_eclipse_jdt_ui_classpathContainerPage.html">org.eclipse.jdt.ui.classpathContainerPage</a></li>
-  <li><a href="org_eclipse_jdt_ui_classpathFixProcessors.html">org.eclipse.jdt.ui.classpathFixProcessors</a></li>
-  <li><a href="org_eclipse_jdt_ui_cleanUps.html">org.eclipse.jdt.ui.cleanUps</a></li>
-  <li><a href="org_eclipse_jdt_ui_foldingStructureProviders.html">org.eclipse.jdt.ui.foldingStructureProviders</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaCompletionProposalComputer.html">org.eclipse.jdt.ui.javaCompletionProposalComputer</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaCompletionProposalSorters.html">org.eclipse.jdt.ui.javaCompletionProposalSorters</a></li>
-  <li><a href="org_eclipse_jdt_ui_javadocCompletionProcessor.html">org.eclipse.jdt.ui.javadocCompletionProcessor</a></li>
-  <li><a href="org_eclipse_jdt_ui_javadocExportWizardPage.html">org.eclipse.jdt.ui.javadocExportWizardPage</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaEditorTextHovers.html">org.eclipse.jdt.ui.javaEditorTextHovers</a></li>
-  <li><a href="org_eclipse_jdt_ui_javaElementFilters.html">org.eclipse.jdt.ui.javaElementFilters</a></li>
-  <li><a href="org_eclipse_jdt_ui_queryParticipants.html">org.eclipse.jdt.ui.queryParticipants</a></li>
-  <li><a href="org_eclipse_jdt_ui_quickAssistProcessors.html">org.eclipse.jdt.ui.quickAssistProcessors</a></li>
-  <li><a href="org_eclipse_jdt_ui_quickFixProcessors.html">org.eclipse.jdt.ui.quickFixProcessors</a></li>
-  
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html b/bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html
deleted file mode 100644
index c1ee77c..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/misc/index.html
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="OTI">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Other Reference Information</title>
-</head>
-<body>
-<h1>Other Reference Information</h1>
-<p>The following specifications, white papers, and design notes describe various 
-  aspects of the Java development tooling. </p>
-<ul>
-  <li><a href="overview-jdt.html">Map of Eclipse Java development tooling plug-ins</a> 
-  </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html b/bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html
deleted file mode 100644
index 2da5767..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/reference/misc/overview-jdt.html
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="OTI">
-<title>JDT Overview - Map of JDT Plug-ins</title>
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>JDT Overview - Map of JDT Plug-ins</h1>
-<p>The Eclipse Java development tooling provides a comprehensive Java development 
-  environment. </p>
-<p>The Java development tooling itself is divided up into a number of separate 
-  plug-ins. The following table shows which API packages are found in which plug-ins as of
-Eclipse 3.5. This table is useful 
-  for determining which plug-ins a given plug-in should include as prerequisites. 
-</p>
-<table border="1" width="80%" align="center">
-  <tbody> 
-  <tr> 
-    <td><b>API Package</b></td>
-    <td><b>Required plug-in id</b></td>
-  </tr>
-  <tr> 
-    <td><tt>com.sun.jdi[.*]<br>
-      org.eclipse.jdi[.*]<br>
-      org.eclipse.jdt.debug[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.debug</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.debug.ui[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.debug.ui</tt><br>
-    </td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.core[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.core</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>com.sun.mirror.*<br>
-      org.eclipse.jdt.apt.core.*</tt></td>
-    <td><tt>org.eclipse.jdt.apt.core</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.launching[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.launching</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.core.manipulation[.*]<br>
-    		org.eclipse.jdt.core.refactoring[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.core.manipulation</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.jdt.ui[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.ui</tt></td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.jdt.junit[.*]</tt></td>
-    <td><tt>org.eclipse.jdt.junit<br>
-            org.eclipse.jdt.junit.core</tt></td>
-  </tr>
-  <tr>
-    <td><tt>junit.*</tt></td>
-    <td><tt>org.junit</tt></td>
-  </tr>
-  <tr>
-    <td><tt>junit.*<br>
-    	    org.junit[.*]</tt></td>
-    <td><tt>org.junit4</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.ant.launching</tt></td>
-    <td><tt>org.eclipse.ant.launching</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.ant.ui.launching</tt></td>
-    <td><tt>org.eclipse.ant.ui</tt></td>
-  </tr>  
-  </tbody> 
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.isv/schema.css b/bundles/org.eclipse.jdt.doc.isv/schema.css
deleted file mode 100644
index 3a25ba2..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/schema.css
+++ /dev/null

@@ -1,71 +0,0 @@
-/*******************************************************************************

- * Copyright (c) 2003, 2009 IBM Corporation and others.

- * All rights reserved. This program and the accompanying materials 

- * are made available under the terms of the Eclipse Public License v1.0

- * which accompanies this distribution, and is available at

- * http://www.eclipse.org/legal/epl-v10.html

- * 

- * Contributors:

- *     IBM Corporation - initial API and implementation

- *******************************************************************************/

-

-H6.SchemaHeader {

-	font-size:16px; 

-	display:inline

-}

-

-P.SchemaCopyright {

-	font-size: smaller; 

-	font-style: normal;

-	color: #336699; 

-	display:inline;

-	margin-top: 3.000000pt;

-	margin-bottom: 11.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.SchemaDtd {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-P.SchemaDtdAttlist {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 20.000000pt;

-}

-

-span.SchemaTag {

-	color: #000080;

-}

-

-span.SchemaCstring {

-	color: #008000;

-}

-

-pre.Example {

-	margin-top: 0.000000pt;

-}

-

-.ConfigMarkupElementDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-.ConfigMarkupAttlistDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 32.000000pt;

-}

-


diff --git a/bundles/org.eclipse.jdt.doc.isv/toc.xml b/bundles/org.eclipse.jdt.doc.isv/toc.xml
deleted file mode 100644
index 88207e7..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/toc.xml
+++ /dev/null

@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="JDT Plug-in Developer Guide">
-	<topic label="Programmer&apos;s Guide" href="guide/jdt_int.htm">
-		<link toc="topics_Guide.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<topic label="3.6 Plug-in Migration Guide">
-		<link toc="topics_Porting.xml"/>
-	</topic>
-	<topic label="Questions Index" href="questions/index.html">
-		<link toc="topics_Questions.xml" />
-	</topic>
-	<topic label="Legal" href="notices.html"/>
-	<enablement>
-		<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.jdt.ui"/>
-	</enablement>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml
deleted file mode 100644
index af84d12..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Guide.xml
+++ /dev/null

@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the main guide                                              -->
-<!-- ============================================================================= -->
-<toc label="Guide">
-	<topic label="JDT Core" href="guide/jdt_int_core.htm">
-		<topic label="Java model" href="guide/jdt_int_model.htm" />
-		<topic label="Manipulating Java code" href="guide/jdt_api_manip.htm" />
-		<topic label="Setting the Java build path" href="guide/jdt_api_classpath.htm" />
-		<topic label="Compiling Java code" href="guide/jdt_api_compile.htm" />
-		<topic label="Using the Java search engine" href="guide/jdt_api_search.htm" />
-		<topic label="Performing code assist on Java code" href="guide/jdt_api_codeassist.htm" />
-		<topic label="JDT Core options" href="guide/jdt_api_options.htm" />
-		<topic label="Formatting Java code" href="guide/jdt_api_codeformatter.htm" />
-	</topic>
-	<topic label="JDT UI" href="guide/jdt_int_ui.htm">
-		<topic label="JavaUI utilities" href="guide/jdt_api_utility.htm">
-			<topic label="Opening a Java editor" href="guide/jdt_api_open_editor.htm" />
-			<topic label="Creating Java specific prompter dialogs" href="guide/jdt_api_prompter.htm" />
-		</topic>
-		<topic label="Presenting Java elements in a JFace viewer" href="guide/jdt_api_render.htm" />
-		<topic label="Java wizard pages" href="guide/jdt_api_wizards.htm" />
-		<topic label="Customizing Java editors" href="guide/jdt_api_editors.htm" />
-		<topic label="Writing Jar files" href="guide/jdt_api_write_jar_file.htm" />
-		<topic label="Contributing a clean up and a save action" href="guide/jdt_api_contributing_a_cleanup.htm" />
-	</topic>
-	<topic label="JDT Debug" href="guide/jdt_int_debug.htm">
-		<topic label="Running Java code" href="guide/jdt_api_run.htm" />
-	</topic>
-	<topic label="JDT JUnit integration" href="guide/jdt_int_junit.htm">
-		<topic label="Observing JUnit test runs" href="guide/jdt_api_junit.htm" />
-	</topic>
-	<topic label="JDT Annotation Processing" href="guide/jdt_int_apt.htm">
-		<topic label="Getting Started" href="guide/jdt_apt_getting_started.htm"/>
-		<topic label="Headless Build" href="guide/jdt_apt_building_with_apt.htm"/>
-	</topic>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml
deleted file mode 100644
index e3d6b5c..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml
+++ /dev/null

@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the porting guide index                                     -->
-<!-- ============================================================================= -->
-<toc label="Migration">
-	<topic label="Migrating to Eclipse JDT 3.6 from 3.5">
-		<topic label="Introduction" href="porting/eclipse_3_6_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.6/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.6/incompatibilities.html" />
-		<topic label="Adopting 3.6 Mechanisms and API" href="porting/3.6/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse JDT 3.5 from 3.4">
-		<topic label="Introduction" href="porting/eclipse_3_5_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.5/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.5/incompatibilities.html" />
-		<topic label="Adopting 3.5 Mechanisms and API" href="porting/3.5/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse JDT 3.4 from 3.3">
-		<topic label="Introduction" href="porting/eclipse_3_4_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.4/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.4/incompatibilities.html" />
-		<topic label="Adopting 3.4 Mechanisms and API" href="porting/3.4/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse JDT 3.3 from 3.2">
-		<topic label="Introduction" href="porting/eclipse_3_3_porting_guide.html"/>
-		<topic label="Incompatibilities" href="porting/3.3/incompatibilities.html" />
-		<topic label="Adopting 3.3 mechanisms and API" href="porting/3.3/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse JDT 3.2 from 3.1">
-		<topic label="Introduction" href="porting/eclipse_3_2_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.2/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.2/incompatibilities.html" />
-		<topic label="Adopting 3.2 Mechanisms and API" href="porting/3.2/recommended.html" />
-	</topic>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml
deleted file mode 100644
index ad5a504..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Questions.xml
+++ /dev/null

@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the questions index                                         -->
-<!-- ============================================================================= -->
-<toc label="Questions">
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml
deleted file mode 100644
index 9ca962a..0000000
--- a/bundles/org.eclipse.jdt.doc.isv/topics_Reference.xml
+++ /dev/null

@@ -1,98 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the references                                              -->
-<!-- ============================================================================= -->
-<toc label="Reference">
-	<topic label="API Reference" href="reference/api/overview-summary.html">
-	   <topic label="org.eclipse.ant.launching" href="reference/api/org/eclipse/ant/launching/package-summary.html"/>
-	   <topic label="org.eclipse.ant.ui.launching" href="reference/api/org/eclipse/ant/ui/launching/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core" href="reference/api/org/eclipse/jdt/core/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.compiler" href="reference/api/org/eclipse/jdt/core/compiler/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.dom" href="reference/api/org/eclipse/jdt/core/dom/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.dom.rewrite" href="reference/api/org/eclipse/jdt/core/dom/rewrite/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.eval" href="reference/api/org/eclipse/jdt/core/eval/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.formatter" href="reference/api/org/eclipse/jdt/core/formatter/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.jdom" href="reference/api/org/eclipse/jdt/core/jdom/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.manipulation" href="reference/api/org/eclipse/jdt/core/manipulation/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.refactoring" href="reference/api/org/eclipse/jdt/core/refactoring/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.refactoring.descriptors" href="reference/api/org/eclipse/jdt/core/refactoring/descriptors/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.refactoring.participants" href="reference/api/org/eclipse/jdt/core/refactoring/participants/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.search" href="reference/api/org/eclipse/jdt/core/search/package-summary.html"/>
-       <topic label="org.eclipse.jdt.core.util" href="reference/api/org/eclipse/jdt/core/util/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.core" href="reference/api/org/eclipse/jdt/debug/core/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.eval" href="reference/api/org/eclipse/jdt/debug/eval/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.ui" href="reference/api/org/eclipse/jdt/debug/ui/package-summary.html"/>
-       <topic label="org.eclipse.jdt.debug.ui.launchConfigurations" href="reference/api/org/eclipse/jdt/debug/ui/launchConfigurations/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching" href="reference/api/org/eclipse/jdt/launching/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching.environments" href="reference/api/org/eclipse/jdt/launching/environments/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching.sourcelookup" href="reference/api/org/eclipse/jdt/launching/sourcelookup/package-summary.html"/>
-       <topic label="org.eclipse.jdt.launching.sourcelookup.containers" href="reference/api/org/eclipse/jdt/launching/sourcelookup/containers/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui" href="reference/api/org/eclipse/jdt/ui/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.actions" href="reference/api/org/eclipse/jdt/ui/actions/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.cleanup" href="reference/api/org/eclipse/jdt/ui/cleanup/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.dialogs" href="reference/api/org/eclipse/jdt/ui/dialogs/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.jarpackager" href="reference/api/org/eclipse/jdt/ui/jarpackager/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.refactoring" href="reference/api/org/eclipse/jdt/ui/refactoring/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.search" href="reference/api/org/eclipse/jdt/ui/search/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text" href="reference/api/org/eclipse/jdt/ui/text/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text.folding" href="reference/api/org/eclipse/jdt/ui/text/folding/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text.java" href="reference/api/org/eclipse/jdt/ui/text/java/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.text.java.hover" href="reference/api/org/eclipse/jdt/ui/text/java/hover/package-summary.html"/>
-       <topic label="org.eclipse.jdt.ui.wizards" href="reference/api/org/eclipse/jdt/ui/wizards/package-summary.html"/>
-       <topic label="org.eclipse.jdt.junit" href="reference/api/org/eclipse/jdt/junit/package-summary.html"/>
-       <topic label="org.eclipse.jdt.junit.launcher" href="reference/api/org/eclipse/jdt/junit/launcher/package-summary.html"/>
-       <topic label="org.eclipse.jdt.junit.model" href="reference/api/org/eclipse/jdt/junit/model/package-summary.html"/>
-       <topic label="org.eclipse.jdt.junit.wizards" href="reference/api/org/eclipse/jdt/junit/wizards/package-summary.html"/>
-	</topic>
-
-	<topic label="APT API Reference" href="reference/apt/overview-summary.html">
-       <topic label="com.sun.mirror.apt" href="reference/apt/com/sun/mirror/apt/package-summary.html"/>
-       <topic label="com.sun.mirror.declaration" href="reference/apt/com/sun/mirror/declaration/package-summary.html"/>
-       <topic label="com.sun.mirror.type" href="reference/apt/com/sun/mirror/type/package-summary.html"/>
-       <topic label="com.sun.mirror.util" href="reference/apt/com/sun/mirror/util/package-summary.html"/>
-       <topic label="org.eclipse.jdt.apt.core.build" href="reference/apt/org/eclipse/jdt/apt/core/build/package-summary.html"/>
-       <topic label="org.eclipse.jdt.apt.core.env" href="reference/apt/org/eclipse/jdt/apt/core/env/package-summary.html"/>
-       <topic label="org.eclipse.jdt.apt.core.util" href="reference/apt/org/eclipse/jdt/apt/core/util/package-summary.html"/>
-	</topic>
-
-	<topic label="Extension Points Reference" href="reference/extension-points/index.html">
-	     <topic label="org.eclipse.jdt.apt.core.annotationProcessorFactory" href="reference/extension-points/org_eclipse_jdt_apt_core_annotationProcessorFactory.html"/>
-         <topic label="org.eclipse.jdt.core.annotationProcessorManager" href="reference/extension-points/org_eclipse_jdt_core_annotationProcessorManager.html"/>
-         <topic label="org.eclipse.jdt.core.classpathContainerInitializer" href="reference/extension-points/org_eclipse_jdt_core_classpathContainerInitializer.html"/>
-         <topic label="org.eclipse.jdt.core.classpathVariableInitializer" href="reference/extension-points/org_eclipse_jdt_core_classpathVariableInitializer.html"/>
-         <topic label="org.eclipse.jdt.core.codeFormatter" href="reference/extension-points/org_eclipse_jdt_core_codeFormatter.html"/>
-         <topic label="org.eclipse.jdt.core.manipulation.changeMethodSignatureParticipants" href="reference/extension-points/org_eclipse_jdt_core_manipulation_changeMethodSignatureParticipants.html"/>
-         <topic href="reference/extension-points/org_eclipse_jdt_debug_breakpointListeners.html" label="org.eclipse.jdt.debug.breakpointListeners"/>
-         <topic label="org.eclipse.jdt.debug.javaLogicalStructures" href="reference/extension-points/org_eclipse_jdt_debug_javaLogicalStructures.html"/>
-         <topic label="org.eclipse.jdt.debug.ui.vmInstallPages" href="reference/extension-points/org_eclipse_jdt_debug_ui_vmInstallPages.html"/>
-         <topic label="org.eclipse.jdt.debug.ui.vmInstallTypePage" href="reference/extension-points/org_eclipse_jdt_debug_ui_vmInstallTypePage.html"/>
-         <topic label="org.eclipse.jdt.junit.junitLaunchConfigs" href="reference/extension-points/org_eclipse_jdt_junit_junitLaunchConfigs.html"/>
-         <topic label="org.eclipse.jdt.junit.testRunListeners" href="reference/extension-points/org_eclipse_jdt_junit_testRunListeners.html"/>
-         <topic label="org.eclipse.jdt.launching.classpathProviders" href="reference/extension-points/org_eclipse_jdt_launching_classpathProviders.html"/>
-         <topic label="org.eclipse.jdt.launching.executionEnvironments" href="reference/extension-points/org_eclipse_jdt_launching_executionEnvironments.html"/>
-         <topic label="org.eclipse.jdt.launching.runtimeClasspathEntries" href="reference/extension-points/org_eclipse_jdt_launching_runtimeClasspathEntries.html"/>
-         <topic label="org.eclipse.jdt.launching.runtimeClasspathEntryResolvers" href="reference/extension-points/org_eclipse_jdt_launching_runtimeClasspathEntryResolvers.html"/>
-         <topic label="org.eclipse.jdt.launching.vmConnectors" href="reference/extension-points/org_eclipse_jdt_launching_vmConnectors.html"/>
-         <topic label="org.eclipse.jdt.launching.vmInstalls" href="reference/extension-points/org_eclipse_jdt_launching_vmInstalls.html"/>
-         <topic label="org.eclipse.jdt.launching.vmInstallTypes" href="reference/extension-points/org_eclipse_jdt_launching_vmInstallTypes.html"/>
-         <topic label="org.eclipse.jdt.ui.classpathAttributeConfiguration" href="reference/extension-points/org_eclipse_jdt_ui_classpathAttributeConfiguration.html"/>
-         <topic label="org.eclipse.jdt.ui.classpathContainerPage" href="reference/extension-points/org_eclipse_jdt_ui_classpathContainerPage.html"/>
-         <topic label="org.eclipse.jdt.ui.classpathFixProcessors" href="reference/extension-points/org_eclipse_jdt_ui_classpathFixProcessors.html"/>
-         <topic label="org.eclipse.jdt.ui.cleanUps" href="reference/extension-points/org_eclipse_jdt_ui_cleanUps.html"/>
-         <topic label="org.eclipse.jdt.ui.foldingStructureProviders" href="reference/extension-points/org_eclipse_jdt_ui_foldingStructureProviders.html"/>
-         <topic label="org.eclipse.jdt.ui.javaCompletionProposalComputer" href="reference/extension-points/org_eclipse_jdt_ui_javaCompletionProposalComputer.html"/>
-         <topic label="org.eclipse.jdt.ui.javaCompletionProposalSorters" href="reference/extension-points/org_eclipse_jdt_ui_javaCompletionProposalSorters.html"/>
-         <topic label="org.eclipse.jdt.ui.javadocCompletionProcessor" href="reference/extension-points/org_eclipse_jdt_ui_javadocCompletionProcessor.html"/>
-         <topic label="org.eclipse.jdt.ui.javadocExportWizardPage" href="reference/extension-points/org_eclipse_jdt_ui_javadocExportWizardPage.html"/>
-         <topic label="org.eclipse.jdt.ui.javaEditorTextHovers" href="reference/extension-points/org_eclipse_jdt_ui_javaEditorTextHovers.html"/>
-         <topic label="org.eclipse.jdt.ui.javaElementFilters" href="reference/extension-points/org_eclipse_jdt_ui_javaElementFilters.html"/>
-         <topic label="org.eclipse.jdt.ui.queryParticipants" href="reference/extension-points/org_eclipse_jdt_ui_queryParticipants.html"/>
-         <topic label="org.eclipse.jdt.ui.quickAssistProcessors" href="reference/extension-points/org_eclipse_jdt_ui_quickAssistProcessors.html"/>
-         <topic label="org.eclipse.jdt.ui.quickFixProcessors" href="reference/extension-points/org_eclipse_jdt_ui_quickFixProcessors.html"/>
-         <topic label="org.eclipse.jdt.ui.classpathFixProcessors" href="reference/extension-points/org_eclipse_jdt_ui_classpathFixProcessors.html"/>
-	</topic>
-	<topic label="Other Reference Information" href="reference/misc/index.html">
-      	<topic label="JDT Plug-ins Map" href="reference/misc/overview-jdt.html"/>
-	</topic>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/.project b/bundles/org.eclipse.jdt.doc.user/.project
deleted file mode 100644
index 84e6438..0000000
--- a/bundles/org.eclipse.jdt.doc.user/.project
+++ /dev/null

@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.jdt.doc.user</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.SchemaBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.PluginNature</nature>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF b/bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index 1e3c735..0000000
--- a/bundles/org.eclipse.jdt.doc.user/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,7 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.jdt.doc.user; singleton:=true
-Bundle-Version: 3.6.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin

diff --git a/bundles/org.eclipse.jdt.doc.user/about.html b/bundles/org.eclipse.jdt.doc.user/about.html
deleted file mode 100644
index 4602330..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.html
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>June 2, 2006</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise 
-indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available 
-at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is 
-being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was 
-provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/about.ini b/bundles/org.eclipse.jdt.doc.user/about.ini
deleted file mode 100644
index df1510b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.ini
+++ /dev/null

@@ -1,24 +0,0 @@
-# about.ini
-# contains information about a feature
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# "%key" are externalized strings defined in about.properties
-# This file does not need to be translated.
-
-# Property "aboutText" contains blurb for "About" dialog (translated)
-aboutText=%blurb
-
-# Property "windowImage" contains path to window icon (16x16)
-# needed for primary features only
-
-# Property "featureImage" contains path to feature image (32x32)
-featureImage=eclipse32.png
-
-# Property "aboutImage" contains path to product image (500x330 or 115x164)
-# needed for primary features only
-
-# Property "appName" contains name of the application (translated)
-# needed for primary features only
-
-# Property "welcomePage" contains path to welcome page (special XML-based format)
-# optional
-

diff --git a/bundles/org.eclipse.jdt.doc.user/about.mappings b/bundles/org.eclipse.jdt.doc.user/about.mappings
deleted file mode 100644
index bddaab4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.mappings
+++ /dev/null

@@ -1,6 +0,0 @@
-# about.mappings
-# contains fill-ins for about.properties
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# This file does not need to be translated.
-
-0=@build@
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/about.properties b/bundles/org.eclipse.jdt.doc.user/about.properties
deleted file mode 100644
index 536ead4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/about.properties
+++ /dev/null

@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2008 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# about.properties
-# contains externalized strings for about.ini
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# fill-ins are supplied by about.mappings
-# This file should be translated.
-
-blurb=Eclipse Java development tooling user guide\n\
-\n\
-Version: {featureVersion}\n\
-Build id: {0}\n\
-\n\
-(c) Copyright IBM Corp. and others 2000, 2004.  All rights reserved.\n\
-Visit http://www.eclipse.org/jdt
-

diff --git a/bundles/org.eclipse.jdt.doc.user/book.css b/bundles/org.eclipse.jdt.doc.user/book.css
deleted file mode 100644
index d7e2b57..0000000
--- a/bundles/org.eclipse.jdt.doc.user/book.css
+++ /dev/null

@@ -1,22 +0,0 @@
-@import "../PRODUCT_PLUGIN/book.css";
-
-span.control {
-  font-weight: bold;
-}
-
-span.name {
-  font-style: italic;
-}
-
-span.code {
-  font-family: monospace;
-}
-
-p.nav_footer {
-	font-weight: bold;
-}
-
-p.nav_footer a {
-	font-weight: bold;
-	font-style: italic;
-}

diff --git a/bundles/org.eclipse.jdt.doc.user/build.properties b/bundles/org.eclipse.jdt.doc.user/build.properties
deleted file mode 100644
index 527729e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/build.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# use provided build.xml
-custom=true
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/build.xml b/bundles/org.eclipse.jdt.doc.user/build.xml
deleted file mode 100644
index 502c0a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/build.xml
+++ /dev/null

@@ -1,106 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="org.eclipse.jdt.doc.user" default="build.jars" basedir=".">
-
-	<property name="version.suffix" value="3.3.0" />
-	<property name="full.name" value="org.eclipse.jdt.doc.user_${version.suffix}" />
-	<property name="bootclasspath" value="" />
-	<property name="basews" value="${ws}" />
-	<property name="baseos" value="${os}" />
-	<property name="basearch" value="${arch}" />
-	<property name="basenl" value="${nl}" />
-	<property name="javacFailOnError" value="false" />
-	<property name="javacDebugInfo" value="on" />
-	<property name="javacVerbose" value="true" />
-	<property name="javacSource" value="1.3" />
-	<property name="javacTarget" value="1.1" />
-
-	<target name="init" depends="properties">
-		<property name="temp.folder" value="${basedir}/temp.folder" />
-		<property name="plugin.destination" value="${basedir}" />
-		<property name="build.result.folder" value="${basedir}" />
-		<available file="${basedir}/doc.zip" property="doc.zip.present" />
-		<condition property="p2.publish.parts" value="true">
-			<istrue value="${p2.gathering}" />
-		</condition>
-	</target>
-
-	<target name="properties" if="eclipse.running">
-		<property name="build.compiler" value="org.eclipse.jdt.core.JDTCompilerAdapter" />
-	</target>
-
-	<target name="build.update.jar" depends="init" description="Build the plug-in: org.eclipse.jdt.doc.user for an update site.">
-		<delete dir="${temp.folder}" />
-		<mkdir dir="${temp.folder}" />
-		<antcall target="build.jars" />
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/" />
-		</antcall>
-		<zip zipfile="${plugin.destination}/${full.name}.jar" basedir="${temp.folder}/${full.name}" filesonly="false" whenempty="skip" />
-		<delete dir="${temp.folder}" />
-	</target>
-
-	<target name="publish.bin.parts" depends="init" if="p2.publish.parts">
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${build.result.folder}" />
-		</antcall>
-		<eclipse.gatherBundle metadataRepository="${p2.build.repo}" artifactRepository="${p2.build.repo}" buildResultFolder="${build.result.folder}" targetFolder="${build.result.folder}/${full.name}" />
-	</target>
-
-	<target name="gather.bin.parts" depends="init" if="destination.temp.folder">
-		<antcall target="build.index" />
-		<mkdir dir="${destination.temp.folder}/${full.name}" />
-		<copy todir="${destination.temp.folder}/${full.name}">
-			<fileset dir="${basedir}" includes="*.properties,*.xml,*.zip,*.html,*.htm,*.png,*.css,META-INF/**,index/**,concepts/**, gettingStarted/**, images/**, reference/**, tasks/**, tips/**, whatsNew/**" excludes="build.properties,build.xml" />
-		</copy>
-		<eclipse.versionReplacer path="${destination.temp.folder}/${full.name}" version="${version.suffix}" />
-	</target>
-
-	<target name="build.jars" depends="init" description="Build all the jars for the plug-in: org.eclipse.jdt.doc.user.">
-	</target>
-
-	<target name="build.index" depends="init" description="Builds search index for the plug-in: org.eclipse.jdt.doc.user." if="eclipse.running">
-		<help.buildHelpIndex manifest="plugin.xml" destination="." />
-	</target>
-
-	<target name="build.sources" depends="init">
-	</target>
-
-	<target name="build.zips" depends="init">
-	</target>
-
-	<target name="gather.sources" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="gather.logs" depends="init" if="destination.temp.folder">
-	</target>
-
-	<target name="clean" depends="init" description="Clean the plug-in: org.eclipse.jdt.doc.user of all the zips, jars and logs created.">
-		<delete file="${plugin.destination}/${full.name}.jar" />
-		<delete file="${plugin.destination}/${full.name}.zip" />
-		<delete dir="${temp.folder}" />
-	</target>
-
-	<target name="refresh" depends="init" if="eclipse.running" description="Refresh this folder.">
-		<eclipse.convertPath fileSystemPath="D:/30workspace/org.eclipse.jdt.doc.user/" property="resourcePath" />
-		<eclipse.refreshLocal resource="${resourcePath}" depth="infinite" />
-	</target>
-
-	<target name="zip.plugin" depends="init" description="Create a zip containing all the elements for the plug-in: org.eclipse.jdt.doc.user." if="eclipse.running">
-		<delete dir="${temp.folder}" />
-		<mkdir dir="${temp.folder}" />
-		<antcall target="build.jars" />
-		<antcall target="build.sources" />
-		<antcall target="gather.bin.parts">
-			<param name="destination.temp.folder" value="${temp.folder}/" />
-		</antcall>
-		<antcall target="gather.sources">
-			<param name="destination.temp.folder" value="${temp.folder}/" />
-		</antcall>
-		<delete>
-			<fileset dir="${temp.folder}" includes="**/*.bin.log" />
-		</delete>
-		<zip zipfile="${plugin.destination}/${full.name}.zip" basedir="${temp.folder}" filesonly="true" whenempty="skip" />
-		<delete dir="${temp.folder}" />
-	</target>
-
-</project>

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm
deleted file mode 100644
index 1aaad7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cbrkpnts.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Breakpoints</title>
-  </head>
-
-  <body>
-    <h1>Breakpoints</h1>
-    <p>A breakpoint suspends the execution of a program at the location where the breakpoint is set.</p>
-
-    <p>Breakpoints can be enabled and disabled via the context menu in the <strong><a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></strong>, or via the context menu in the <strong><a href="../concepts/concept-java-editor.htm">Java Editor</a></strong> ruler.</p>
-
-    <ul>
-      <li>An enabled breakpoint causes a thread to suspend whenever
-        the breakpoint is encountered. Enabled breakpoints are drawn with a blue circle [ <img src="../images/org.eclipse.debug.ui/obj16/brkp_obj.png" alt="Breakpoint"> ] and
-        have a checkmark overlay once successfully installed. A breakpoint can only
-        be installed when the class the breakpoint is located in has been loaded by the VM.</li>
-
-      <li>A disabled breakpoint will not cause threads to suspend. Disabled breakpoints are drawn with a white circle [ <img src="../images/org.eclipse.debug.ui/obj16/brkpd_obj.png" alt="Disabled Breakpoint"> ].</li>
-    </ul>
-
-    <p>Breakpoints are displayed in the vertical editor ruler and in the Breakpoints view.</p>
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-     <a href="../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-     <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-     <a href="../tasks/task-suspending_threads.htm">Suspending threads</a></p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-     <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a>
-     <a href="../reference/menus/run/ref-menu-run.htm"><br>Run menu actions</a><br>
-     <a href="../reference/ref-toolbar-run.htm">Run and debug toolbar actions</a><br>
-     <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cdebugger.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cdebugger.htm
deleted file mode 100644
index 53d244f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cdebugger.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Debugger</title>
-  </head>
-
-  <body>
-    <h1>Debugger</h1>
-    <p>The Java development toolkit (JDT) includes a debugger that enables you to detect and diagnose errors in your programs running either locally or remotely.</p>
-
-    <p>The debugger allows you to control the execution of your program by setting breakpoints, suspending
-    launched programs, stepping through your code, and examining the contents of
-    variables.</p>
-
-    <p>The debugger has a client/server design so you can debug programs running remotely on other systems in the network as well as programs running locally on your workstation.
-    The debug client runs inside the workbench on your workstation.&nbsp; The debugger server runs on the same system as the program you want to
-    debug.&nbsp; This could be a program launched on your workstation (local debugging) or a
-    program started on a computer that is accessible through a
-    network (remote debugging).</p>
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a><br>
-     <a href="../concepts/cbrkpnts.htm">Breakpoints</a><br>
-     <a href="cremdbug.htm">Remote debugging</a><br>
-     <a href="clocdbug.htm">Local debugging</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-     <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-     <a href="../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-     <a href="../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-     <a href="../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-     <a href="../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-     <a href="../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-     <a href="../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-     <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-     <a href="../tasks/task-suspending_threads.htm">Suspending threads</a><br>
-    </p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-     <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-    <a href="../reference/menus/run/ref-menu-run.htm">Run menu actions</a><br>
-    <a href="../reference/ref-toolbar-run.htm">Run and Debug toolbar actions</a></p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm b/bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm
deleted file mode 100644
index fad41d7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/clocdbug.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Local Debugging</title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>Local Debugging</h1>
-    <p>The Java debugger has a client/server design so that it can be used to
-    debug programs that run locally (on the same workstation as the debugger) or
-    remotely (on another computer on the network).</p>
-
-    <p>Local debugging is the simplest and most common kind of debugging.&nbsp;
-    After you have finished editing and building your Java program, you can
-    launch the program on your workstation using the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenDebugConfigurations")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the launch configuration dialog">
-    <strong>Run &gt; Debug Configurations...</strong></a> menu item
-    on the workbench.&nbsp; Launching the program in this way will establish a
-    connection between the debugger client and the Java program that you are
-    launching.&nbsp; You may then use breakpoints, stepping, or expression
-    evaluation to debug your program.</p>
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-    <a href="cbrkpnts.htm">Breakpoints</a></p>
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-    <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-    <a href="../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-    <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-    <a href="../tasks/task-suspending_threads.htm">Suspending threads</a></p>
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-    <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-    <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-    <a href="../reference/menus/run/ref-menu-run.htm">Run menu actions</a><br>
-    <a href="../reference/ref-toolbar-run.htm">Run and Debug toolbar actions</a>
-    </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-access-rules.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-access-rules.htm
deleted file mode 100644
index b435838..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-access-rules.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Access Rules</title>
-  </head>
-
-  <body>
-    <h1>Access Rules</h1>
-
-    Access rules can be added to build classpath entries to specify which types in the given entry
-    can be accessed and which not. If the compiler detects a type access to a type that should not be
-    accessed, it will create a problem marker.
-    <ul>
-    <li>Non-accessible rules define types that must not be referenced. The compiler typically creates an error marker for accesses to these types.</li>
-    <li>Discouraged rules define types that should not be referenced. The compiler typically creates a warning marker for accesses to these types.</li>
-    <li>Accessible rules define types that can be referenced.</li>
-    </ul>
-    Each rule consist of a pattern (same format as ANT patterns) and one of the rule types listed above.<br>
-    Each classpath entry can have any number of rules defined. The compiler will process the list in the order
-    defined and take the first matching rule. <br><br>  
-    The severity of the problem marker generated for accesses to 'Non-accessible' and 'Discouraged' type can be configured
-    on the Java compiler's <a href="../reference/preferences/java/compiler/ref-preferences-errors-warnings.htm">Error/Warnings</a> preference page.     
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concept-java-builder.htm">Java builder</a><br>
-     <a href="concept-classpath-variables.htm">Classpath variable</a><br>
-     <a href="concept-inclusion-exclusion-patterns.htm">Inclusion and exclusion patterns</a><br>
-     <a href="concept-access-rules.htm">Access rules</a>    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-properties-build-path.htm">Java build path properties</a><br>
-     <a href="../reference/preferences/java/compiler/ref-preferences-errors-warnings.htm">Error/Warnings preference page</a>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-build-classpath.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-build-classpath.htm
deleted file mode 100644
index 7e33837..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-build-classpath.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Build Classpath</title>
-  </head>
-
-  <body>
-    <h1>Build Classpath</h1>
-
-    <p>The build classpath specifies which Java source files and resource files in a project are considered by the Java builder
-    and specifies how to find types outside of the project. The Java builder compiles the Java source files
-    into the output folder and also copies the resources into it.  The build classpath is
-    specified for each project. In the project properties, it is referred
-    to as the <strong>Java Build Path</strong></p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concept-java-builder.htm">Java builder</a><br>
-     <a href="concept-classpath-variables.htm">Classpath variables</a><br>
-     <a href="concept-inclusion-exclusion-patterns.htm">Inclusion and exclusion patterns</a><br>
-     <a href="concept-access-rules.htm">Access rules</a>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm">Classpath variables preferences</a><br>
-     <a href="../reference/ref-properties-build-path.htm">Java build path properties</a><br>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-classpath-variables.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-classpath-variables.htm
deleted file mode 100644
index 831eb87..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-classpath-variables.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Classpath Variables</title>
-  </head>
-
-  <body>
-    <h1>Classpath Variables</h1>
-
-    <p>The build path for a Java project can include source code files, other
-    Java projects, folders containing class files and JAR files. JAR files can be specified using file
-    system paths, or by using variables that refer to locations on the
-    network.&nbsp;</p>
-
-    <p>Classpath variables allow you to avoid references to the location of a JAR
-    file or folders on your local file system. By using a classpath variable, you can
-    specify a JAR file or folder using only a variable name, such as JRE_LIB,
-    rather than specifying the location on your workstation. In
-    this way, you can share build paths across teams and define the variables to
-    refer to the correct location for your particular computer.</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concept-java-builder.htm">Java builder</a><br>
-     <a href="concept-classpath-variables.htm">Classpath variable</a><br>
-     <a href="concept-inclusion-exclusion-patterns.htm">Inclusion and exclusion patterns</a><br>
-     <a href="concept-access-rules.htm">Access rules</a>
-	</p>
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm">Classpath variables preferences</a><br>
-     <a href="../reference/ref-properties-build-path.htm">Java build path properties</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-editor-templates.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-editor-templates.htm
deleted file mode 100644
index c84990e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-editor-templates.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Editor Templates</title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>Editor Templates</h1>
-
-    <p>Templates are a structured description of coding patterns that reoccur in
-    source code. The Java editor supports the use of templates to fill in
-    commonly used source patterns. Templates are inserted using content
-    assist (<strong>Ctrl+Space</strong>).</p>
-
-    <p>For example, a common coding pattern is to iterate over the elements of
-    an array using a for loop that indexes into the array. By using a
-    template for this pattern, you can avoid typing in the complete code for the
-    loop. Invoking content assist after typing the word <code>for</code> will present
-    you with a list of possible templates for a for loop.  You can choose the appropriate
-    template by name (<code>iterate over array</code>). Selecting this template will
-    insert the code into the editor and position your cursor so that you can
-    edit the details.</p>
-
-    <p>Templates can contain <a href="../concepts/concept-template-variables.htm">template variables</a>. Variables mark the editable locations. They can be resolves to a concrete value when the template is evaluated in its context. They can also provide
-    a list of alternative proposals valid at the given location.
-    </p> 
-
-
-    <p>Many common templates are already defined. These can be viewed with the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaTemplatePreferencePage)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java editor preferences page">
-    <strong>Java &gt; Editor &gt; Templates</strong></a> preference page.
-    You can also create your own templates or edit the existing ones.</p>
-    
-    
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/preferences/java/editor/ref-preferences-templates.htm">Templates preferences</a><br>
-     <a href="../concepts/concept-template-variables.htm">Template variables</a><br>
-     <a href="../reference/preferences/java/editor/ref-preferences-edit-template-dialog.htm">Template editing</a><br>
-     <a href="../reference/ref-menu-edit.htm">Edit menu</a><br>
-     <a href="../reference/ref-java-editor-code-assist.htm">Java content assist</a><br>
-    </p>
-
-    <p><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-inclusion-exclusion-patterns.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-inclusion-exclusion-patterns.htm
deleted file mode 100644
index 2270ffa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-inclusion-exclusion-patterns.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Inclusion and Exclusion Patterns</title>
-  </head>
-
-  <body>
-    <h1>Inclusion and Exclusion Patterns</h1>
-
-    <p>Inclusion and Exclusion patterns can be configured for source folders. They define 
-    which files are considered by the Java builder and 
-    other Java tooling. This set of files consists of all files and folders where the path
-    relative to the source folder matches an inclusion pattern but not an exclusion pattern.</p>
-    <p>By default, all files and folders contained in a source folder are included. By defining an inclusion pattern,
-    the set of included resources will be limited to the resources matching the inclusion pattern.
-    Using exclusion patterns, some of these resources can be excluded again.</p>
-    <p>Exclusion patterns are required when nesting source folders. The nested folder must be
-    excluded from the outer source folder.</p>
-
-    <p>The patterns have the same format as <a href="http://ant.apache.org/manual/dirtasks.html#patterns">ANT patterns</a>:</p>
-    <ul>
-    <li>'*' matches zero or more characters, '?' matches one character.</li>
-    <li>'/' is used to separate folders: This means the first segment in the pattern is matched against the most outer folder name in the path to match, the second segment with the second, and so on.</li>
-    <li>'**' matches any number of folders</li>
-    </ul>
- 
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concept-java-builder.htm">Java builder</a><br>
-     <a href="concept-classpath-variables.htm">Classpath variables</a><br>
-     <a href="concept-access-rules.htm">Access rules</a>
-    </p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-properties-build-path.htm">Java Build Path properties</a><br>
-     
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm
deleted file mode 100644
index 92105dc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java Builder</title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>Java Builder</h1>
-
-    <p>The Java builder builds Java programs using its own compiler (the Eclipse Compiler for Java) that implements the Java Language Specification.&nbsp;
-    The Java builder can build programs incrementally as individual Java files are saved. Note that the Eclipse Compiler for Java can also be invoked
-    using Ant as described in the <b>Using the ant javac adapter</b> section of  <a href="../../org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm">Compiling Java code</a><br></p>
-
-    <p>Problems detected by the compiler are classified as either warnings or errors. The existence of a warning does not affect the execution of the program; the code executes as
-    if it were written correctly. Compile-time errors (as specified by the Java Language Specification) are always reported as errors by the Java compiler. For some other types of
-    problems you can, however, specify if you want the Java compiler to report them as warnings, errors or to ignore them. To change the default settings, use the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java compiler preference page">
-    <span class="control">Java &gt; Compiler &gt; Errors/Warnings</span></a>
-    preference page.</p>
-
-    <p>The Java compiler can create CLASS files even in presence of compilation errors. However, in the case of serious errors (for example, references to inconsistent binaries,
-    most likely related to an invalid build path), the Java builder does not produce any CLASS
-    files.</p>
-
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="concept-build-classpath.htm">Build classpath</a><br></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-properties-build-path.htm">Java build path properties</a><br>
-     <a href="../reference/preferences/java/ref-preferences-compiler.htm">Java compiler preferences</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-editor.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-editor.htm
deleted file mode 100644
index 7e04379..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-editor.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java Editor</title>
-  </head>
-
-  <body>
-    <h1>Java Editor</h1>
-
-    <p>The Java editor provides specialized features for editing Java code.</p>
-
-    <p>Associated with the editor is a Java-specific Outline view, which shows the structure of the active Java compilation unit.
-    It is updated as the user edits the compilation unit.</p>
-    
-    
-    <p>The editor can also show a breadcrumb navigation bar. The breadcrumb shows the parent chain of the element at the current
-    cursor position. It is also updated when the user edits the compilation unit or changes the selection.</p>
-    
-
-    <p>The Java editor can be opened on binary CLASS files.
-    If a JAR file containing the CLASS files has a source attachment,
-    then the editor shows the corresponding source.</p>
-
-    <p>The editor includes the following features:</p>
-
-    <ul>
-      <li>Syntax highlighting</li>
-
-      <li>Content/code assist</li>
-
-      <li>Code formatting</li>
-
-      <li>Import assistance</li>
-      
-      <li>Quick fix</li>
-
-      <li>Integrated debugging features</li>
-    </ul>
-
-    <p>The Java editor can be configured to either show an entire compilation unit or a single Java element only.
-    To change the setting, use the toolbar button <span class="control">Show Source of Selected Element Only</span>.
-    </p>
-
-    <p>The most common way to invoke the Java editor is to open a Java file from the
-    Package explorer using pop-up menus or by clicking the file
-    (single or double-click depending on the user preferences). You can
-    also open the editor by opening Java elements, such as types, methods, or
-    fields, from other views.</p>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="concept-quickfix-assist.htm">Quick fix and assist</a><br>
-     <a href="concept-editor-templates.htm">Templates</a><br>
-     </p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-     <a href="../tasks/task-view_runtime_exceptions.htm">Viewing runtime exceptions</a><br>
-     <a href="../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-    </p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/ref-java-editor-quickassist.htm">Quick assists</a><br>   
-     <a href="../reference/ref-java-editor-quickfix.htm">Quick fixes</a><br> 
-     <a href="../reference/views/ref-java-editor.htm">Java editor actions</a><br>
-     <a href="../reference/preferences/java/ref-preferences-editor.htm">Java editor preferences</a><br>
-     <a href="../reference/views/ref-view-outline.htm">Java outline</a><br>
-     <a href="../reference/ref-java-editor-breadcrumb.htm">Java Editor Breadcrumb</a><br>
-     <a href="../reference/views/ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-perspective.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-perspective.htm
deleted file mode 100644
index 3555b75..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-perspective.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java Perspectives</title>
-  </head>
-
-  <body>
-    <h1>Java Perspectives</h1>
-
-    The Java development tools contribute the following perspectives to the workbench:
-
-    <h2>Java</h2>
-
-    <p>A perspective designed for working with Java projects. It consists of an editor area and the following views:</p>
-
-    <ul>
-      <li><span>Package Explorer</span></li>
-
-      <li><span>Hierarchy</span></li>
-
-      <li><span>Outline</span></li>
-
-      <li><span>Problems</span></li>
-
-      <li><span>Javadoc</span></li>
-
-      <li><span>Declaration</span></li>
-    </ul>
-
-    <h2>Java Browsing</h2>
-
-    <p>A perspective designed for browsing the structure of Java projects. It consists of an editor area and the following views:</p>
-
-    <ul>
-      <li><span>Projects</span></li>
-
-      <li><span>Packages</span></li>
-
-      <li><span>Types</span></li>
-
-      <li><span>Members</span></li>
-    </ul>
-
-    <h2>Java Type Hierarchy</h2>
-
-    <p>A perspective designed for exploring a type hierarchy. It can be opened on types, compilation units, packages, projects or source folders and consists of the Hierarchy
-    view and an editor.</p>
-
-    <h2>Debug</h2>
-
-    <p>A perspective designed for debugging your Java program. It includes an editor area and the following views.</p>
-
-    <ul>
-      <li><span>Debug</span></li>
-
-      <li><span>Breakpoints</span></li>
-      
-      <li><span>Variables</span></li>
-
-      <li><span>Expressions</span></li>
-
-      <li><span>Outline</span></li>
-
-      <li><span>Console</span></li>
-      
-      <li><span>Tasks</span></li>
-      
-    </ul>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concept-java-views.htm">Java views</a></p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a><br>
-     <a href="../reference/views/console/ref-console_view.htm">Console view</a><br>
-     <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-     <a href="../reference/views/display/ref-display_view.htm">Display view</a><br>
-     <a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a><br>
-     <a href="../reference/views/ref-view-outline.htm">Java outline</a><br>
-     <a href="../reference/views/ref-view-package-explorer.htm">Package explorer view</a><br>
-     <a href="../reference/views/ref-type-hierarchy.htm">Type hierarchy view</a><br>
-     <a href="../reference/views/variables/ref-variables_view.htm">Variables view</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-project.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-project.htm
deleted file mode 100644
index 6565981..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-project.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java Projects</title>
-  </head>
-
-  <body>
-    <h1>Java Projects</h1>
-
-    <p>A Java project contains source code and related files for building a Java
-    program. It has an associated Java builder that can incrementally compile Java source files as they are changed.</p>
-
-    <p>A Java project also maintains a model of its contents. This model
-    includes information about the type hierarchy, references and declarations of Java elements.
-    This information is constantly updated as the user changes
-    the Java source code. The updating of the internal Java project model is independent of the
-    Java builder; in particular, when performing code modifications, if auto-build is turned
-    off, the model will still reflect the present project contents.</p>
-
-    <p>You can organize Java projects in two different ways:</p>
-
-    <ul>
-      <li><span>Using the project as the source container. This is the recommended organization for simple projects.</span></li>
-
-      <li><span>Using source folders inside the project as the source container. This is the recommended organization for more complex projects. It allows you to subdivide packages into
-      groups.</span></li>
-    </ul>
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concept-java-builder.htm">Java builder</a><br></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-wizard-java-project.htm">New Java project wizard</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-search.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-search.htm
deleted file mode 100644
index 6b6ec23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-search.htm
+++ /dev/null

@@ -1,130 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java Search</title>
-  </head>
-
-  <body>
-    <h1>Java Search</h1>
-
-    <p><span>The Java searching support allows you to find declarations, references and occurrences of Java elements
-    (packages, types, methods, fields). Searching is supported by an index that
-    is kept up to date in the background as the resources corresponding to Java elements are changed.
-    The Java search operates on workspaces independent of their build state. For
-    example, searches can be conducted when auto-build is turned off.</span></p>
-
-    <p>The following searches can be initiated from the pop-up menus of Java elements or from the Java search dialog:</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="Java search actions">
-      <thead>
-        <tr>
-          <td>
-            <p><span class="control">Command</span></p>
-          </td>
-
-          <td>
-            <p><span class="control">Description</span></p>
-          </td>
-        </tr>
-      </thead>
-
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>References</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all references to the selected Java element</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Declarations</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all declarations of the selected Java element</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Implementors</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all implementors of the selected Java interface</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Read access</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all read accesses to the selected Java field</p>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            <p>Write access</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all write accesses to the selected Java field</p>
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">
-            <p>Match locations for type references</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all type references at specified locations (in casts, as field type, ...)</p>
-          </td>
-        </tr>        
-
-        <tr>
-          <td valign="top">
-            <p>Occurrences in File</p>
-          </td>
-
-          <td valign="top">
-            <p>Finds all occurrences of the selected Java element in its file</p>
-          </td>
-        </tr>
-
-      </tbody>
-    </table>
-        
-
-    <p>The scope of the search is defined as:</p>
-
-    <p><span class="control">Workspace</span> - all projects and files in the workspace are included in this search</p>
-
-    <p><span class="control">Enclosing Projects</span> - the projects enclosing the currently selected elements</p>
-
-    <p><span class="control">Hierarchy</span> - only the type hierarchy of the selected element is included in this search</p>
-
-    <p><span class="control">Working Set</span> - only resources that belong to the chosen working set are included in this search</p>
-
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-menu-search.htm">Search actions</a><br>
-     <a href="../reference/ref-dialog-java-search.htm">Java search tab</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-decorators.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-decorators.htm
deleted file mode 100644
index 765395d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-decorators.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-    <title>Java Element Decorations</title>
-  </head>
-
-   <body>
-    <h1>Java Element Decorations</h1>
-
-    <h2>Override Indicators</h2>
-    <p>Java views can show special decoration icons to indicate methods that override or implement methods from supertypes.</p>
-
-    <p>To show or hide the override indicators, select or clear the <span class="control">Java Method Override Indicator</span> checkbox in the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-        <span class="control">General &gt; Appearance &gt; Label Decorations</span></a> preference page.
-	</p>
-	
-    <h2>Java Type Indicator</h2>
-    <p>The package explorer can indicate the kind of Java type (Enum, Interface, Annotation) contained in a Java file.</p>
-    
-    <p><em>Note:</em></p>
-    <ul>
-     <li>If a Java file contains more than one top-level type, it is decorated according to its primary type.</li>
-     <li>No decoration is shown for classes, except for abstract classes.</li>
-    </ul>
-
-    <p>To show or hide the Java type indicators, select or clear the <span class="control">Java Type Indicator</span> checkbox in the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Label Decoarations preference page">
-        <span class="control">General &gt; Appearance &gt; Label Decorations</span></a> preference page.
-	</p>
-	
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/preferences/java/ref-preferences-appearance.htm">Appearance preference page</a><br>
-     <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-filtering.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-filtering.htm
deleted file mode 100644
index 3d56ccd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-filtering.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-    <title>Filtering in Java Views</title>
-  </head>
-  
-  <body>
-    <h1>Filtering in Java Views</h1>
-    
-    <h2>Applying View Filters</h2>
-    
-    <p>All Java views allow to filter the displayed Java elements. The set of available filters depends on the view.</p>
-    
-    <p>To filter elements:</p>
-    <ol>
-      <li>On the view toolbar, click the <strong>Menu</strong> button and choose <strong>Filters...</strong>.</li>
-      <li>Select or clear the filters that you want to apply to the view (read <strong>Filter description</strong> to learn about the selected filter's functionality).</li>
-      <li>Optionally, you can select patterns for filtering the view:
-        <ul>
-          <li>Select the <strong>Name filter patterns</strong> checkbox at the top of the dialog.</li>
-          <li>In the text field below, specify the desired patterns (names matching one of the patterns will be hidden).</li>
-        </ul>
-      </li>
-    </ol>
-    
-    <h2>Filtering Members</h2>
-
-    <p>Several Java views (e.g. <strong>Outline</strong>, <strong>Type Hierarchy</strong>, <strong>Members</strong>) offer filtering of members (fields, types and methods).
-    The filters are available as toolbar buttons or as view menu items, depending on the view. There are
-    3 member filters:</p>
-
-    <ul>
-      <li><span class="control">Hide Fields</span>: when activated, this filter causes all fields to be removed from the view.</li>
-      <li><span class="control">Hide Static Fields and Methods</span>: when activated, this filter causes all static members to be removed from the view.</li>
-      <li><span class="control">Hide Non-Public Members</span>: when activated, this filter causes all non-public members to be removed from the view.</li>
-    </ul>
-    
-    Additionally, the <strong>Package Explorer</strong> view can display or hide all elements inside compilation units. 
-
-    <p>To show or hide members in the <strong>Package Explorer</strong> view, select or clear the <span class="control">Show members in Package Explorer</span> checkbox in the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-        <span class="control">Java &gt; Appearance</span></a> preference page.
-    </p>
-    
-    <h2>Filtering Working Sets</h2>
-    <p>Several Java views (e.g. <strong>Package Explorer</strong>, <strong>Type Hierarchy</strong>) offer to filter by one or more working sets.
-    The filters are available in the view menu. Only the elements that are contained in the selected working sets are shown in the view.</p>
-    
-        
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-	<p>
-	<a href="../concepts/concept-java-project.htm">Java projects</a><br>
-    <a href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm">Working sets</a>
-    </p>
-	
-	
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-presentation.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-presentation.htm
deleted file mode 100644
index 08e2bd1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-presentation.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-    <title>Presentation options for Java views</title>
-  </head>
-
-  <body>
-    <h1>Presentation Options for Java Views</h1>
-
-    <h2>Showing and Hiding Method Return Types</h2>
-
-    <p>Several Java views (e.g. <strong>Outline</strong>, <strong>Members</strong>) present methods and can also show their return types and type parameters.</p>
-
-    <p>To show method return types in Java views select or clear the <span class="control">Show method return types</span> or <span class="control">Show method type parameters</span> checkbox in the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-        <span class="control">Java &gt; Appearance</span></a> preference page.
-	</p>
-    
-    <h2>Showing Full or Compressed Package Names</h2>
-
-    <p>The <strong>Package Explorer</strong> and <strong>Packages</strong> views can show full or compressed package names.</p>
-
-    <p>To show full package names:</p>
-
-    <ul>
-      <li>Clear the <span class="control"> Compress all package name segments, except the final segment</span> checkbox
-        on the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-        <span class="control">Java &gt; Appearance</span></a> preference page.</li>
-    </ul>
-    To show compressed package names: 
-
-    <ul>
-      <li>
-        <p>Select the <span class="control">Compress all package name segments, except the final segment</span> 
-        checkbox on the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-        <span class="control">Java &gt; Appearance</span></a> preference page.</p>
-
-        <p>Compression patterns control how many characters of each package name
-        segment are displayed. The last segment of a package name is
-        always displayed.</p>
-        <p>A compression pattern of &quot;.&quot; indicates that only the
-        separating periods are shown to represent a segment. A digit (n)
-        in a compression pattern represents the first n characters of a package name segment.
-        Examples are the best way to understand compression patterns. The
-        package <span class="control">org.eclipse.jdt </span>would be displayed
-        as follows using the example compression patterns:</p>
-        <p> <span class="control">.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>..jdt</p>
-        <p><span class="control">0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>jdt</p>
-        <p><span class="control">2~&nbsp;&nbsp;&nbsp;&nbsp; </span>or~.ec~.jdt</p>
-        <p> <span class="control">3~&nbsp;&nbsp;&nbsp;&nbsp; </span>org.ecl~.jdt</p>
-      </li>
-    </ul>
-	<br>
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/preferences/java/ref-preferences-appearance.htm">Java appearance preference page</a><br>
-     <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a><br>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-sorting.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-sorting.htm
deleted file mode 100644
index de7bb2a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views-sorting.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-    <title>Sorting in Java Views</title>
-  </head>
-
-  <body>
-    <h1>Sorting in Java Views</h1>
-
-    <p>The <strong>Members</strong> and <strong>Outline</strong> views can present members sorted
-    or in the order of declaration in the compilation unit.</p>
-
-    <p>To sort members:</p>
-
-    <ul>
-      <li>Toggle on the <span class="control">Sort</span> toolbar button in the view toolbar.</li>
-      <li>The sorting order can be configured on the on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.MembersOrderPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Members Sort Order preference page">
-      <span class="control">Java &gt; Appearance &gt; Members Sort Order</span></a>
-      preference page.</li>
-      <li>After the above sorting is performed, members in each group are sorted alphabetically.</li>
-    </ul>
-    
-    To present members in the order of declaration in the compilation unit. 
-
-    <ul>
-      <li>Toggle off the <span class="control">Sort</span> toolbar button in the view toolbar.</li>
-    </ul>
-    <img src="../images/ngrelr.png" alt="Related reference" border="0" > <br>
-     <a href="../reference/ref-actions-toolbar.htm">Java toolbar actions</a><a href="../reference/ref-actions-toolbar.htm"></a> 
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views.htm
deleted file mode 100644
index 6e29ca9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-java-views.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-    <title>Java Views</title>
-  </head>
-
-  <body>
-    <h1>Java Views</h1>
-
-    <p>The Java development tools contribute the following views to the workbench:</p>
-
-    <h2>Package Explorer View</h2>
-
-    <p>The Package Explorer view shows a Java-specific view of resources inside Java projects in your workbench.
-    The Java element hierarchy is defined by the project's build class paths and consists of elements like</p>
-    <ul>
-	    <li>source folders and libraries</li>
-	    <li>packages</li>
-	    <li>source and class files</li>
-	    <li>types, methods, fields and initialzers</li>
-    </ul>
-
-    <h2>Hierarchy View</h2>
-
-    <p>The Hierarchy view allows you to look at the complete hierarchy for a
-    type, only its subtypes, or only its supertypes. You can also open the hierarchy on a project, source folder or package.</p>
-
-    <h2>Projects View</h2>
-
-    <p>The Projects view shows Java projects, source folders, external and internal libraries.
-    <br>
-    Note: source folders and libraries (both internal and external) presented in this view are not expandable.
-    When they are selected, their contents are shown in the Packages view.</p>
-
-    <h2>Packages View</h2>
-
-    <p>The Packages view shows a list of Java packages from the currently selected Java projects, source folders or libraries.
-    Typically, the Projects view is used to make this selection.
-    </p>
-
-    <h2>Types View</h2>
-
-    <p>The Types view shows a list of Java types from the currently selected packages.
-    Typically, the Packages view is used to make this selection.
-    </p>
-
-    <h2>Members View</h2>
-
-    <p>The Members shows the content of a type, compilation unit or CLASS file.
-    Typically, the Types view is used to make this selection.
-    </p>
-    
-    <h1>View Customization</h1>
-    <p>Both the appearance and behavior of the Java views can be customized.</p>
-    <ul>
-        <li><a href="concept-java-views-filtering.htm">Filtering</a></li>
-        <li><a href="concept-java-views-sorting.htm">Sorting</a></li>
-        <li><a href="concept-java-views-decorators.htm">Java element decorations</a></li>
-        <li><a href="concept-java-views-presentation.htm">Presentation options</a></li>
-    </ul>    
-
-    <p><img  src="../images/ngrelc.png" alt="Related concepts"></p>
-    <p><a href="../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-
-    <p><img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-    <p>
-     <a href="../tasks/tasks-consoleAppearance.htm">Changing the appearance of the Console view</a>
-    </p>
-
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a><br>
-     <a href="../reference/views/console/ref-console_view.htm">Console view</a><br>
-     <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-     <a href="../reference/views/display/ref-display_view.htm">Display view</a><br>
-     <a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a><br>
-     <a href="../reference/views/ref-view-outline.htm">Java outline</a><br>
-     <a href="../reference/views/ref-view-package-explorer.htm">Package explorer view</a><br>
-     <a href="../reference/views/ref-type-hierarchy.htm">Type hierarchy view</a><br>
-     <a href="../reference/views/ref-call-hierarchy.htm">Call hierarchy view</a><br>
-     <a href="../reference/views/variables/ref-variables_view.htm">Variables view</a><br>
-     <a href="../reference/views/ref-viewsandeditors.htm">Views and editors</a><br>
-    <br>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-jdt.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-jdt.htm
deleted file mode 100644
index 1868b08..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-jdt.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java development tools (JDT)</title>
-  </head>
-
-  <body>
-    <h1>Java development tools (JDT)</h1>
-
-    <p>The Java development tools (JDT) are a set of extensions to the workbench that
-    allow you to edit, compile, and run Java programs.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="concept-build-classpath.htm">Build classpath</a><br>
-     <a href="../concepts/concept-classpath-variables.htm">Classpath variables</a><br>
-     <a href="../concepts/cdebugger.htm">Debugger</a><br>
-     <a href="../concepts/concept-java-builder.htm">Java builder</a><br>
-     <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-     <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-     <a href="../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-     <a href="../concepts/concept-java-views.htm">Java views</a><br>
-     <a href="../concepts/concept-java-search.htm">Java search</a><br>
-     <a href="../concepts/concept-refactoring.htm">Refactoring support</a><br>
-     <a href="../concepts/cscrapbook.htm">Scrapbook</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../tasks/tasks-64.htm">Restoring a deleted workbench element</a><br>
-     <a href="../tasks/tasks-JREs.htm">Working with JREs</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-jdt-actions.htm">JDT actions</a><br>
-     <a href="../reference/ref-jdt-faq.htm">Frequently asked questions on JDT</a><br>
-     <a href="../reference/ref-jdt-glossary.htm">JDT glossary</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-quickfix-assist.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-quickfix-assist.htm
deleted file mode 100644
index 2ef82e3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-quickfix-assist.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Quick Fix and Quick Assist
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-     Quick Fix and Quick Assist
-    </h1>
-    <p>
-      For most problems underlined with a problem highlight line, the Java editor can offer corrections. This is shown by the light bulb shown in the editor marker bar.
-    </p>
-	<p>
-    <img src="images/qs-37a.png"  alt="A Java editor indicating a quick-fixable problem with a light bulb in the editor marker bar"> <br>
-	</p>
-     To see the correction proposals use the Quick Fix action 
-    <ul>
-      <li>
-        Set the cursor inside or near the highlight range, and select&nbsp;<strong>Quick Fix</strong> from the <a href="../reference/ref-menu-edit.htm">Edit menu</a> or the context menu.
-      </li>
-      <li>
-        Set the cursor inside or near the highlight range, and press Ctrl + 1
-      </li>
-      <li>
-        Click on the light bulb
-      </li>
-    </ul>
-<p>Quick fix is also available on a problem entry in the Problem view. The Quick Fix action will open a dialog to select the correction.
-<br>
-    <br>
-Note that the light bulb is only a hint. It is possible that even with the light bulb shown, it turns out that no corrections can be offered.<br>
-A overview of quick fixes available in the Java editor can be found <a
-	href="../reference/ref-java-editor-quickfix.htm">here</a>.<br>
-	
-	
-	<br>Quick Assists are proposals available even if there is no problem or warning. They use the same short cut and action like Quick Fix. Quick assists
-	are used for local code manipulations. See the <a
-	href="../reference/ref-java-editor-quickassist.htm">Quick assist</a> reference for more information.</p>
-	<p>	  
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-<a href="../concepts/concept-java-editor.htm">Java editor</a>
-</p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-java-editor-quickassist.htm">Quick assists</a><br>
-      <a href="../reference/ref-java-editor-quickfix.htm">Quick fix</a><br>
-      <a href="../reference/preferences/java/ref-preferences-editor.htm">Java editor preferences</a><br>
-      <a href="../reference/ref-menu-edit.htm">Edit menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-refactoring.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-refactoring.htm
deleted file mode 100644
index 72c7a51..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-refactoring.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Refactoring Support</title>
-  </head>
-
-  <body>
-    <h1>Refactoring Support</h1>
-
-    <p>The goal of Java program refactoring is to make system-wide code changes without affecting the behavior of the
-    program. The Java tools provide assistance in easily refactoring code. </p>
-
-    <p>The refactoring tools support a number of transformations described in Martin Fowler's
-    book <span class="name">Refactoring: Improving the Design of Existing Code</span>, Addison Wesley
-    1999, such as <span class="name">Extract Method</span>, <span class="name">Inline Local
-    Variable, etc.</span>.</p>
-    <p>To get an overview of all offered refactorings look at the <a href="../reference/ref-menu-refactor.htm"><b>Refactor menu</b></a>.
-    Refactoring commands are also available from the context menus in many views or appear as <a href="../reference/ref-java-editor-quickassist.htm"><b>quick assists</b></a>.
-    </p>
-
-    <p>When performing a refactoring operation, you can optionally preview all
-    of the changes resulting from a refactoring action before you choose to carry them out.
-    When previewing a refactoring operation, you will be notified of potential
-    problems and will be presented with a list of the changes the
-    refactoring action will perform. If you do not preview a refactoring
-    operation, the change will be made in its entirety and any resultant
-    problems will be shown. If a problem is detected that does not allow
-    the refactoring to continue, the operation will be halted and a list of
-    problems will be displayed.</p>
-
-    <p>Refactoring commands are available from the context menus of several Java views (e.g. Package Explorer, Outline) and editors.
-    Many &quot;apparently simple&quot; commands, such as <strong>Move</strong> and <strong>Rename</strong>, are
-    actually refactoring operations, since moving and renaming Java elements
-    often require changes in dependent files.
-    </p>
-
-	<p>Refactorings can not only be performed interactively, but also from refactoring scripts. Most refactorings available in the <strong>Refactor</strong>
-	menu are stored in the workspace refactoring history in order to be used in refactoring scripts afterwards. The refactoring tools support the creation of refactoring
-	scripts based on refactorings in the workspace refactoring history. Refactoring scripts can then be applied to an arbitrary workspace. Applying a refactoring
-	script launches a refactoring wizard which is able to replay the refactorings as if they had been initiated by the user which originally had created them.
-	</p>
-	
-	<p>Related to refactoring scripts, the refactoring tools offer a refactoring to migrate a JAR File to a newer version, using refactoring information
-	to avoid breaking changes in your workspace after the migration.
-	</p>
-	
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-     <a href="../reference/ref-wizard-refactorings.htm">Refactoring wizard</a><br>
-     <a href="../reference/preferences/ref-preferences-java.htm">Java preferences</a>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-string-externalization.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-string-externalization.htm
deleted file mode 100644
index 342645b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-string-externalization.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>String Externalization</title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>String Externalization</h1>
-
-    <p>The Java tools help you to develop applications that can be run on
-    international platforms. An important facet of designing a program for
-    use in different countries is the localization, or externalization, of text
-    that is displayed by the program. By externalizing strings, the text
-    can be translated for different countries and languages without rebuilding
-    the Java program.</p>
-
-    
-<p>The JDT provides the following support for internationalization and string 
-  externalization:</p>
-
-    
-<ul>
-  <li> A compiler option lets you mark non-externalized strings as compile-time 
-    warnings or errors. 
-    <ul>
-      <li>See the <b>Non-externalized strings</b> option in the <b>Code style</b> section of the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java compiler preference page">
-      <span class="control">Java &gt; Compiler &gt; Errors/Warnings</span></a> preference page.</li>
-    </ul>
-  </li>
-  <li>Tools that allow you to find strings that have not been externalized.</li>
-  <li>A wizard that will guide you through externalizing the strings.</li>
-  <li>Tools that help you to find unused and incorrectly used keys for strings 
-    located in property files.</li>
-</ul>
-
-    <p>Comments can be used to denote strings that should not be externalized
-    and should not result in compile-time warnings or errors. These comments are of form <code>//$NON-NLS-n$</code>
-    where n is the 1-based index of the string in a line of code.</p>
-    <p>Additional information about internationalized applications can be found
-    in the following documents:</p>
-
-    <ul>
-      <li><a href=
-      "http://eclipse.org/articles/Article-Internationalization/how2I18n.html">http://eclipse.org/articles/Article-Internationalization/how2I18n.html</a></li>
-
-      <li><a href="http://java.sun.com/docs/books/tutorial/i18n/intro/index.html" target="_blank">http://java.sun.com/docs/books/tutorial/i18n/intro/index.html</a></li>
-    </ul>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/tasks-188.htm">Finding strings to externalize</a><br>
-     <a href="../tasks/tasks-202.htm">Finding unused and incorrectly used keys in property files</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/ref-menu-source.htm">Source menu</a><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize strings wizard</a><br>
-     <a href="../reference/preferences/java/ref-preferences-compiler.htm">Java compiler preferences</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/concept-template-variables.htm b/bundles/org.eclipse.jdt.doc.user/concepts/concept-template-variables.htm
deleted file mode 100644
index de5b673..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/concept-template-variables.htm
+++ /dev/null

@@ -1,294 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>Java Editor Template Variables</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"></script>
-  </head>
-  
-  <body>
-    <h1>Java Editor Template Variables</h1>
-    <ul>
-      <li><a href="#general_vars">General Template Variables</a></li>
-      <li><a href="#java_vars">Java Specific Template Variables</a></li>
-    </ul>
-
-    <p>
-      Template variables may be used in the template pattern. Variables are resolved
-      to their concrete value when the template is evaluated in its context. Variables may be specified
-      using <i>simple</i> or <i>full</i> syntax:</p> 
-      <ul>
-        <li><strong>Simple</strong> variables take the following form:
-          <p><strong><code>${array}</code></strong></p>
-          <p>This defines a variable with name 'array' that will resolve to an array. It can be referenced multiple times as is.</p>
-        </li>
-        <li><strong>Full</strong> variables take the following form:
-          <p><strong><code>${it:var(java.util.Iterator)}</code></strong></p>
-          <p>This defines a variable with name 'it' that will resolve to a local variable of type <code>java.util.Iterator</code>. It can be referenced multiple times by simply giving its name without the type: <code>${it}</code>.</p>
-        </li>
-      </ul>
-    <p>If there are several possible matches for a variable, they may be presented as proposals to the user.</p>
-    
-    <h3><a name="general_vars">General Template Variables</a></h3>
-    <p>Both Java and Javadoc context define the following variables:</p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="General Template Variables">
-      <thead>
-        <tr>
-          <th>Variable</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody valign="baseline">
-        <tr>
-          <td><strong>${cursor}</strong></td>
-          <td>Specifies the cursor position when the template edit mode is left. This is useful when the cursor should jump to another place than to the end of the template on
-              leaving template edit mode.</td>
-        </tr>
-        <tr>
-          <td><strong>${date}</strong></td>
-          <td>Evaluates to the current date.</td>
-        </tr>
-        <tr>
-          <td><strong>${dollar}</strong></td>
-          <td>Evaluates to the dollar symbol '$'. Alternatively, two dollars can be used: '$$'.</td>
-        </tr>
-        <tr>
-          <td><strong>${enclosing_method}</strong></td>
-          <td>Evaluates to the name of the enclosing name.</td>
-        </tr>
-        <tr>
-          <td><strong>${enclosing_method_arguments}</strong></td>
-          <td>Evaluates to a comma separated list of argument names of the enclosing method. This variable can be useful when generating log statements for many methods.</td>
-        </tr>
-        <tr>
-          <td><strong>${enclosing_package}</strong></td>
-          <td>Evaluates to the name of the enclosing package.</td>
-        </tr>
-        <tr>
-          <td><strong>${enclosing_project}</strong></td>
-          <td>Evaluates to the name of the enclosing project.</td>
-        </tr>
-        <tr>
-          <td><strong>${enclosing_type}</strong></td>
-          <td>Evaluates to the name of the enclosing type.</td>
-        </tr>
-        <tr>
-          <td><strong>${file}</strong></td>
-          <td>Evaluates to the name of the file.</td>
-        </tr>
-        <tr>
-          <td><strong>${line_selection}</strong></td>
-          <td>Evaluates to content of all currently selected lines.</td>
-        </tr>
-        <tr>
-          <td><strong>${primary_type_name}</strong></td>
-          <td>Evaluates to the name primary type of the current compilation unit.</td>
-        </tr>
-        <tr>
-          <td><strong>${return_type}</strong></td>
-          <td>Evaluates to the return type of the enclosing method.</td>
-        </tr>
-        <tr>
-          <td><strong>${time}</strong></td>
-          <td>Evaluates to the current time.</td>
-        </tr>
-        <tr>
-          <td><strong>${user}</strong></td>
-          <td>Evaluates to the user name.</td>
-        </tr>
-        <tr>
-          <td><strong>${word_selection}</strong></td>
-          <td>Evaluates to the content of the current text selection.</td>
-        </tr>
-        <tr>
-          <td><strong>${year}</strong></td>
-          <td>Evaluates to the current year.</td>
-        </tr>
-      </tbody>
-    </table>
-    
-    <h3><a name="java_vars">Java Specific Template Variables</a></h3>
-    <p>The Java context additionally defines the following variables.
-    	<b>Note:</b> In the table below, <i>id</i> is a user-chosen name of a new variable.</p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Specific Template Variables">
-      <thead>
-        <tr>
-          <th>Variable</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody valign="baseline">
-        <tr>
-          <td><strong>${<i>id</i>:field(<i>type[,type]*</i>)}</strong></td>
-          <td>Evaluates to a field in the current scope that is a subtype of any of the given types. If no type is specified, any non-primitive field matches.
-              <p>Example:<br>
-              <code>${count:field(int)}</code>
-            </p>
-          
-          </td>
-        </tr>
-        <tr>
-          <td><strong>${<i>id</i>:var(<i>type[,type]*</i>)}</strong></td>
-          <td>Evaluates to a field, local variable or parameter visible in the current scope that is a subtype of any of the given types. If no type is specified, any non-primitive variable matches.
-              <p>Example:<br>
-              <code>${array:var(java.lang.Object[])}</code>
-            </p>
-          
-          </td>
-        </tr>
-        <tr>
-          <td><strong>${<i>id</i>:localVar(<i>type[,type]*</i>)}</strong></td>
-          <td>Evaluates to a local variable or parameter visible in the current scope that is a subtype of any of the given type. If no type is specified, any non-primitive local variable matches.
-              <p>
-	              <strong>${array}</strong> is a shortcut for <strong>${array:localVar(java.lang.Object[])}</strong>, but also matches arrays of primitive types.<br>
-    	          <strong>${collection}</strong> is a shortcut for <strong>${collection:localVar(java.util.Collection)}</strong>.<br>
-        	      <strong>${iterable}</strong> is a shortcut for <strong>${iterable:localVar(java.lang.Iterable)}</strong>, but also matches arrays.
-              </p>
-          </td>
-        </tr>
-        <tr>
-          <td><strong>${<i>id</i>:argType(<i>variable,&nbsp;n</i>)}</strong></td>
-          <td>
-            Evaluates to the <i>nth</i> type argument of the referenced template variable. The reference should be the name of another
-            template variable. Resolves to <code>java.lang.Object</code> if the referenced variable cannot be found or is not
-            a parameterized type.
-            <p>Example:<br>
-              <code>${type:argType(vector, 0)}&nbsp;${first:name(type)}&nbsp;=&nbsp;${vector:var(java.util.Vector)}.get(0)</code>
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td><strong>${<i>id</i>:elemType(<i>variable</i>)}</strong></td>
-          <td>Evaluates to the element type of the referenced template variable. 
-              The reference should be the name of another
-              template variable that resolves to an array or an instance of <code>java.lang.Iterable</code>.
-              The <strong>elemType</strong> variable type is similar to <strong><code>${<i>id</i>:argType(<i>reference</i>,0)}</code></strong>, the difference
-              being that it also resolves the element type of an array.
-              <p>
-	              <strong>${array_type}</strong> is a shortcut for <strong>${array_type:elemType(array)}</strong>.<br>
-	              <strong>${iterable_type}</strong> is a shortcut for <strong>${iterable_type:elemType(iterable)}</strong>.
-              </p>
-          </td>
-        </tr>
-        <tr>
-          <td><strong>${<i>id</i>:newName(<i>reference</i>)}</strong></td>
-          <td>Evaluates to an non-conflicting name for a new local variable of the type specified
-              by the reference. The reference may either be a Java type name or the name of another
-              template variable. The generated name respects the code style settings.
-              <p>
-	              <strong>${index}</strong> is a shortcut for <strong>${index:newName(int)}</strong>.<br>
-	              <strong>${iterator}</strong> is a shortcut for <strong>${iterator:newName(java.util.Iterator)}</strong>.<br>
-	              <strong>${array_element}</strong> is a shortcut for <strong>${array_element:newName(array)}</strong>.<br>
-	              <strong>${iterable_element}</strong> is a shortcut for <strong>${iterable_element:newName(iterable)}</strong>.
-              </p>
-          </td>
-        </tr>
-        <tr>
-          <td><strong>${<i>id</i>:newType(<i>qualifiedTypeName</i>)}</strong></td>
-          <td>Evaluates to a type name given the fully qualified Java type name.
-          	Evaluates to a simple type name and an import if no conflicting type
-          	exists. Evaluates to a fully qualified type name otherwise.
-          	  <p>Example:<br>
-                   <code>${type:newType(java.util.Iterator)}</code>
-        	  </p>
-          </td>
-        </tr>
-        <tr>
-        	<td><strong>${:import(<i>type[,type]*</i>)}</strong></td>
-        	<td>
-        		Adds an import statement for each type. Does nothing if the import already exists. Does nothing if a conflicting import exists.
-        		Evaluates to nothing.
-        		<p>Example:<br>
-        			<code>${:import(java.util.List, java.util.Collection)}</code>
-        		</p>
-        	</td>
-        </tr>
-        <tr>
-        	<td><strong>${:importStatic(<i>[qualifiedName[,qualifiedName]*]</i>)}</strong></td>
-        	<td>
-        		Adds a static import statement for each qualified name that is not already imported. 
-        		The <code>qualifiedName</code> is the fully qualified name of a static field or method 
-        		or it is the qualified name of a type plus a '.*' suffix. 
-        		Does nothing if a conflicting import exists. 
-        		Evaluates to nothing.
-        		<p>Example:<br>
-        			<code>${is:importStatic(java.util.Collections.EMPTY_SET, 'java.lang.System.*')}</code>
-        		</p>
-        	</td>
-        </tr>
-        <tr>
-        	<td><strong>${<i>id</i>:link(<i>proposal[,proposal]*</i>)}</strong></td>
-        	<td>
-        		Evaluates to <i>id</i> if the list of proposals is empty, evaluates to the first proposal otherwise. 
-        		The evaluated value is put into linked mode. 
-        		A proposal window shows all the given proposals.
-        		<p>Example:<br>
-        			<code>java.util.Collections.${kind:link(EMPTY_SET, EMPTY_LIST, EMPTY_MAP)}</code>
-        		</p>
-        	</td>
-        </tr>
-        <tr>
-          <td><strong>${array}</strong></td>
-          <td>Evaluates to a proposal for an array visible in the current scope.</td>
-        </tr>
-        <tr>
-          <td><strong>${array_element}</strong></td>
-          <td>Evaluates to a name for a new local variable for an element of the <strong>${array}</strong> variable match.</td>
-        </tr>
-        <tr>
-          <td><strong>${array_type}</strong></td>
-          <td>Evaluates to the element type of the <strong>${array}</strong> variable match.</td>
-        </tr>
-        <tr>
-          <td><strong>${collection}</strong></td>
-          <td>Evaluates to a proposal for a collection visible in the current scope.</td>
-        </tr>
-        <tr>
-          <td><strong>${exception_variable_name}</strong></td>
-          <td>Exception variable name in catch blocks.</td>
-        </tr>
-        <tr>
-          <td><strong>${index}</strong></td>
-          <td>Evaluates to a proposal for an undeclared array index.</td>
-        </tr>
-        <tr>
-          <td><strong>${iterator}</strong></td>
-          <td>Evaluates to an unused name for a new local variable of type <code>java.util.Iterator</code>.</td>
-        </tr>
-        <tr>
-          <td><strong>${iterable}</strong></td>
-          <td>Evaluates to a proposal for an iterable or array visible in the current scope.</td>
-        </tr>
-        <tr>
-          <td><strong>${iterable_element}</strong></td>
-          <td>Evaluates to a name for a new local variable for an element of the <strong>${iterable}</strong> variable match.</td>
-        </tr>
-        <tr>
-          <td><strong>${iterable_type}</strong></td>
-          <td>Evaluates to the element type of the <strong>${iterable}</strong> variable match.</td>
-        </tr>
-        <tr>
-          <td><strong>${todo}</strong></td>
-          <td>Evaluates to a proposal for the currently specified default task tag.</td>
-        </tr>
-      </tbody>
-    </table>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p><a href="concept-editor-templates.htm">Templates</a><br></p>
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-      <a href="../reference/preferences/java/editor/ref-preferences-edit-template-dialog.htm">Editing templates</a><br>
-      <a href="../reference/preferences/java/editor/ref-preferences-templates.htm">Templates preference page</a><br>
-      <a href="../reference/ref-java-editor-code-assist.htm">Java content assist</a><br>
-      <a href="../reference/preferences/java/compiler/ref-preferences-task-tags.htm">Task tag preferences</a><br>
-      <a href="../reference/preferences/java/codestyle/ref-preferences-code-templates.htm">Code templates preferences</a><br>
-      <a href="../reference/preferences/java/ref-preferences-code-style.htm">Code style preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm
deleted file mode 100644
index e65ef7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cremdbug.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Remote Debugging</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Remote Debugging</h1>
-<p>The client/server design of the Java debugger allows you to launch a Java
-  program from computer on your network and debug it from the workstation running
-  the platform.&nbsp; This is particularly useful when you are developing a program
-  for a device that cannot host the development platform.&nbsp; It is also useful
-  when debugging programs on dedicated machines such as web servers.&nbsp; </p>
-<p>Note:&nbsp; To use remote debugging, you must be using a Java VM that supports
-  this feature.</p>
-<p>To debug a program remotely, you must be able to launch the program in debug
-  mode on the remote machine so that it will wait for a connection from your
-  debugger.&nbsp; The specific technique for launching the program and connecting
-  the debugger are VM-specific.&nbsp; The basic steps are as follows:</p>
-<ol>
-  <li>Ensure that you are building your Java program with available debug information.&nbsp; (You
-    can control these attributes from the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CompliancePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java compiler preference page"> <strong>Java &gt; Compiler</strong></a> preference
-    page).&nbsp; </li>
-  <li>After you build your Java program, install it to the target computer.&nbsp; This
-    involves copying the .CLASS files or .JAR files to the appropriate location
-    on the remote computer.</li>
-  <li>Invoke the Java program on the remote computer using the appropriate VM
-    arguments to specify debug mode and a communication port for the debugger.</li>
-  <li>Start the debugger using a remote launch configuration and specify the
-    address and port of the remote computer.</li>
-</ol>
-<p>When setting up the remote launch configuration there are a few items to take
-  note of:</p>
-<ul>
-  <li>You must ensure you enter the correct hostname i.e. the name of the remote
-    computer where you are currently running your code. The hostname can also
-    be the IP address of the remote machine, for example using <em><strong>127.0.0.1</strong></em> instead
-    of <em><strong>localhost</strong></em>.</li>
-  <li>The port number must be the number of the port on the <em><strong>remote
-        machine</strong></em>.</li>
-</ul>
-<p>Certain Java VMs support another way of starting a remote debug session. In
-  this alternative connection type, the debugger is launched first. The debugger
-  then waits and listens for the VM to connect to it. To debug this way, you
-  must properly configure and launch a remote debug session, then launch the
-  VM, specifying the location of your waiting debugger. For more information,
-  see <a href="../tasks/task-remotejava_launch_config.htm">Using the remote Java
-  application launch configuration</a>.</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../tasks/task-remotejava_launch_config.htm">Using the remote Java
-    application launch configuration</a><br>
-  <a href="../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/cscrapbook.htm b/bundles/org.eclipse.jdt.doc.user/concepts/cscrapbook.htm
deleted file mode 100644
index bf465fe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/cscrapbook.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Scrapbook</title>
-  </head>
-
-  <body>
-    <h1>Scrapbook</h1>
-    <p>The Java development toolkit (JDT) contributes a scrapbook facility that can be used to experiment and evaluate Java
-    code snippets before building a complete Java program. Snippets are edited and evaluated in the Scrapbook page
-    editor, with resultant problems reported in the editor.</p>
-
-    <p>From a Java scrapbook editor, you can select a code snippet, evaluate it, and display the result as a string.
-    You can also show the object that results from evaluating a code snippet in the debuggers' <a href="../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a>.</p>
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-    <p>
-     <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a><br>
-     <a href="cdebugger.htm">Debugger</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p>
-     <a href="../tasks/task-create_scrapbook_page.htm">Creating a Java scrapbook page</a><br>
-     <a href="../tasks/task-display_evaluation_result.htm">Displaying the result of evaluating an expression</a><br>
-     <a href="../tasks/task-inspect_evaluation_result.htm">Inspecting the result of evaluating an expression</a>
-	</p>
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ></p>
-    <p>
-     <a href="../reference/ref-wizard-scrapbook.htm">New Java Scrapbook Page wizard</a><br>
-     <a href="../reference/views/ref-view-scrapbook.htm">Java Scrapbook page</a><br>
-     <a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a></p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/concepts/images/qs-37a.png b/bundles/org.eclipse.jdt.doc.user/concepts/images/qs-37a.png
deleted file mode 100644
index 0dafde5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/concepts/images/qs-37a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_APT.xml b/bundles/org.eclipse.jdt.doc.user/contexts_APT.xml
deleted file mode 100644
index ff3ddec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_APT.xml
+++ /dev/null

@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-    <!-- Dialogs -->
-
-    <context id="advanced_factory_path_options_dialog_context">
-    	<description>A dialog for configuring factory path options that do not normally need to be changed.</description>
-    	<topic label="Advanced factory path options dialog" href="reference/ref-apt-factoryPathOptions.htm"/>
-    </context>
-    <context id="processor_option_input_dialog_context">
-    	<description>A dialog for adding or editing an annotation processor option.</description>
-    	<topic label="Processor option input dialog" href="reference/ref-apt-processorOptionsInput.htm"/>
-    </context>
-    
-    <!-- Preference pages -->
-
-    <context id="apt_configuration_preference_page_context">
-        <description>Configure general Java annotation processing settings.</description>
-        <topic label="Java annotation processing preferences" href="reference/ref-apt-config.htm"/>
-    </context>
-    <context id="factory_path_preference_page_context">
-        <description>Configure the factory path for Java annotation processing.</description>
-        <topic label="Java annotation processing factory path preferences" href="reference/ref-apt-factoryPath.htm"/>
-    </context>
-    
-</contexts>
-    

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml b/bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml
deleted file mode 100644
index 6fcb56c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_Debugger.xml
+++ /dev/null

@@ -1,1487 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-<!--
-	Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.
-	
-	All Platform Debug contexts, those for org.eclipse.debug.ui, are located in this file
-	All contexts are grouped by their relation, with all relations grouped alphabetically.
--->
-<!--
-	Breakpoints View
--->
-	<context  id="breakpoint_view_context" >
-		<description>The Breakpoints view lists all the breakpoints you have set.</description>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Add Java Exception Breakpoint" href="reference/views/breakpoints/ref-addexception_viewaction.htm" />
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Collapse All" href="reference/views/shared/ref-collapseall.htm"/>
-		<topic label="Expand All" href="reference/views/breakpoints/ref-expandall_viewaction.htm"/>
-		<topic label="Go to File for Breakpoint" href="reference/views/breakpoints/ref-gotofile_viewaction.htm" />
-		<topic label="Link with Debug View" href="reference/views/breakpoints/ref-linkwith_viewaction.htm"/>
-		<topic label="Remove Selected Breakpoints" href="reference/views/breakpoints/ref-remove_viewaction.htm" />
-		<topic label="Remove All Breakpoints" href="reference/views/breakpoints/ref-removeall_viewaction.htm" />
-		<topic label="Show Supported Breakpoints" href="reference/views/breakpoints/ref-showsupported_viewaction.htm" /> 
-		<topic label="Skip All Breakpoints" href="reference/views/breakpoints/ref-skipall_viewaction.htm"/>
-	</context>
-	<context  id="enable_breakpoint_action_context" >
-		<description>This command enables the selected breakpoints.</description>
-		<topic label="Enable Context Action" href="reference/views/breakpoints/ref-enable_contextaction.htm" />
-		<topic label="Breakpoint Enabled Option" href="reference/breakpoints/ref-enabled_option.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context  id="disable_breakpoint_action_context" >
-		<description>This command disables the selected breakpoints.</description>
-		<topic label="Disable Context Action" href="reference/views/breakpoints/ref-disable_contextaction.htm" />
-		<topic label="Breakpoint Enabled Option" href="reference/breakpoints/ref-enabled_option.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context  id="open_breakpoint_action_context" >
-		<description>This command opens an editor for the file containing the selected breakpoint.</description>
-		<topic label="Go to File for Breakpoint" href="reference/views/breakpoints/ref-gotofile_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-	<context  id="select_all_breakpoints_action_context" >
-      	<description>This command selects all breakpoint in the view.</description>
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="remove_breakpoint_action_context" >
-      	<description>This command deletes the selected breakpoints.</description>
-		<topic label="Remove Selected Breakpoints" href="reference/views/breakpoints/ref-remove_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="remove_all_breakpoints_action_context" >
-    	<description>This command deletes all breakpoints in the view.</description>
-		<topic label="Remove All Breakpoints" href="reference/views/breakpoints/ref-removeall_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="copy_breakpoints_action_context" >
-    	<description>This command copies the selected breakpoints to the system clipboard.</description>
-		<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-		<topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="paste_breakpoints_action_context" >
-    	<description>This command adds breakpoints from the system clipboard to the selected breakpoint group.  Breakpoints will only be added if they are valid for the selected group.</description>
-		<topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-		<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="import_breakpoints_action_context" >
-    	<description>This command opens a wizard allowing you to import breakpoints from a file.</description>
-		<topic label="Import Breakpoints" href="reference/views/breakpoints/ref-import_contextaction.htm" />
-		<topic label="Export Breakpoints" href="reference/views/breakpoints/ref-export_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-	<context id="skip_all_breakpoints_context" >
-		<description>When selected, breakpoints will not suspend execution while debugging.</description>
-		<topic label="Skip All Breakpoints" href="reference/views/breakpoints/ref-skipall_viewaction.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-	</context>		
-   	<context  id="export_breakpoints_action_context" >
-    	<description>This command opens a wizard allowing you to export your breakpoints to a file.</description>
-		<topic label="Export Breakpoints" href="reference/views/breakpoints/ref-export_contextaction.htm" />
-		<topic label="Import Breakpoints" href="reference/views/breakpoints/ref-import_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="set_default_breakpoint_group_action_context" >
-    	<description>This command opens a dialog allowing you to choose a working set to be the default working set.  New breakpoints will be added to the default working set.</description>
-		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm" />
-		<topic label="Breakpoint View Working Sets" href="reference/views/breakpoints/ref-workingsets_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="breakpoint_working_sets_action_context" >
-    	<description>This command opens a dialog allowing you to create, configure and remove working sets.</description>
-		<topic label="Breakpoint View Working Sets" href="reference/views/breakpoints/ref-workingsets_viewaction.htm" />
-		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="clear_default_breakpoint_group_action_context" >
-    	<description>This command turns off the default working set setting for the breakpoints view.</description>
-		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm" />
-		<topic label="Breakpoint View Working Sets" href="reference/views/breakpoints/ref-workingsets_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>
-   	<context  id="edit_breakpoint_working_set_action_context" >
-    	<description>This command opens a dialog allowing you to edit the working set properties, including its name and what breakpoints it contains.</description>
-		<topic label="Breakpoint View Working Sets" href="reference/views/breakpoints/ref-workingsets_viewaction.htm" />
-		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context> 
-   	<context  id="set_as_default_breakpoint_working_set_action_context" >
-    	<description>This command allows you to change whether the selected breakpoint group is the default working set.</description>
-		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm" />
-		<topic label="Breakpoint View Working Sets" href="reference/views/breakpoints/ref-workingsets_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-   	</context>  
-	<context  id="access_toggle_action_context" >
-		<description>When checked, this command configures a watchpoint to suspend execution when a field is accessed (read).</description>
-		<topic label="Access Command" href="reference/views/breakpoints/ref-access_contextaction.htm" />
-		<topic label="Watchpoint Access Option" href="reference/breakpoints/ref-access_option.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>				
-	<context  id="modification_toggle_action_context" >
-		<description>When checked, this command configures a watchpoint to suspend execution when a field is modified (written).</description>
-		<topic label="Modification Command" href="reference/views/breakpoints/ref-modification_contextaction.htm" />
-		<topic label="Watchpoint Modification Option" href="reference/breakpoints/ref-modification_option.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>	
-
-<!--
-	Console View
--->
-	<context  id="console_view_context" >
-		<description>This view shows a collection of available consoles.</description>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Clear the Console" href="reference/views/console/ref-clear_action.htm"/>
-		<topic label="Display Selected Console" href="reference/views/console/ref-display_action.htm"/>
-		<topic label="Open Console" href="reference/views/console/ref-open_action.htm"/>
-		<topic label="Pin the Console" href="reference/views/console/ref-pin_action.htm"/>
-		<topic label="Scroll Lock" href="reference/views/console/ref-scrolllock_action.htm"/>
-	</context>
-	<context  id="clear_console_action_context" >
-		<description>This command clears the console.</description>
-		<topic label="Clear Console" href="reference/views/console/ref-clear_action.htm"/>
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-	<context id="console_open_console_action_context">
-		<description>This command allows you to open a different type of console from the action drop down</description>
-		<topic label="Open Console" href="reference/views/console/ref-open_action.htm"/>
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-	<context id="console_pin_console_action">
-		<description>This command allows you to pin the current console to always remain on top of other consoles</description>
-		<topic label="Pin the Console" href="reference/views/console/ref-pin_action.htm"/>
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-	<context id="console_display_console_action">
-		<description>This command allow you to display a console of your choosing the resutling drop-down menu</description>
-		<topic label="Display Selected Console" href="reference/views/console/ref-display_action.htm"/>
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-	<context  id="process_console_context">
-		<description>This console shows the output of the execution of your program and allows you to enter any necessary user input.</description>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-		<topic label="Console Preferences" href="reference/views/console/ref-prefs_action.htm"/>
-		<topic label="Remove All Terminated Launches" href="reference/views/console/ref-removeallterminated_action.htm"/>
-		<topic label="Remove Launch" href="reference/views/console/ref-removelaunch_action.htm"/>
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		<topic label="Show Console When Standard Out Changes"  href="reference/views/console/ref-show_out_action.htm"/>
-		<topic label="Show Console When Standard Error Changes"  href="reference/views/console/ref-show_err_action.htm"/>
-		<topic label="Terminate" href="reference/views/console/ref-terminate_action.htm"/>
-	</context>
-	<context  id="copy_to_clipboard_action_context" >
-		<description>This command copies the selection to the system clipboard.</description>
-		<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-		<topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-		<topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-	<context  id="console_terminate_action_context">
-		<description>Terminates the process associated with the console.</description>
-		<topic label="Terminate" href="reference/views/console/ref-terminate_action.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context> 
-   	<context  id="console_remove_all_terminated_context">
-		<description>Removes all terminated launches.</description>
-		<topic label="Remove All Terminated Launches" href="reference/views/console/ref-removeallterminated_action.htm"/>
-		<topic label="Remove Launch" href="reference/views/console/ref-removelaunch_action.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context> 	
-	<context  id="console_remove_launch_context">
-		<description>Removes the selected launch.</description>
-		<topic label="Remove Launch" href="reference/views/console/ref-removelaunch_action.htm"/>
-		<topic label="Remove All Terminated Launches" href="reference/views/console/ref-removeallterminated_action.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-	<context  id="console_scroll_lock_action_context">
-		<description>This command enables and disables scroll lock.</description>
-		<topic label="Scroll Lock" href="reference/views/console/ref-scrolllock_action.htm"/>
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id="console_select_all_action_context">
-    	<description>This command allows you to select all of the text in the current console.</description>
-    	<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-    	<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-	    <topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-    	<topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-    	<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id="console_cut_action_context">
-	    <description>This command allows you to copy the selected text to the system clipboard and remove it from the current console.</description>
-	    <topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-	    <topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-	    <topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-	    <topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-	    <topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id="console_paste_action_context">
-	    <description>This command allows you to copy text from the system clipboard into the current console.</description>
-	    <topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-	    <topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-	    <topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-	    <topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-	    <topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id="console_find_replace_action_context">
-    	<description>This command allows you to search for a specified pattern within the current console.</description>
-	    <topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-	    <topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id ="console_show_preferences_action_context">
-    	<description>This command opens the preferences page for the console.</description>
-	    <topic label="Console Preferences" href="reference/views/console/ref-prefs_action.htm"/>
-	    <topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id="console_open_link_action_context">
-    	<description>This command allows you to search for a specified pattern within the current console.</description>
-	    <topic label="Open Link" href="reference/views/console/ref-openlink_action.htm"/>
-	  	<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id="show_stdout_action_context">
-    	<description>This command toggles the preference to automatically show the console view when output is written to the standard output stream.</description>
-		<topic label="Show Console When Standard Out Changes" href="reference/views/console/ref-show_out_action.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-    </context>
-    <context id="show_stderr_action_context">
-    	<description>This command toggles the preference to automatically show the console view when output is written to the standard error stream.</description>
-		<topic label="Show Console When Standard Error Changes" href="reference/views/console/ref-show_err_action.htm"/>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>		
-    </context>
-	  
-<!-- 
-	Debug View
--->
-	<context  id="debug_view_context" >
-		<description>This view displays system processes and the threads and stack frames for each target you are debugging.</description>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Changing Debugger Launch Options" href="tasks/tasks-9.htm"/>
-	</context>
-	<context  id="disconnect_action_context" >
-		<description>This command disconnects the debugger from the selected debug target.</description>
-		<topic label="Disconnect" href="reference/views/debug/ref-disconnect.htm" />
-		<topic label="Disconnecting from a VM" href="tasks/task-disconnect_remote_debug.htm"></topic>
-		<topic label="Debugging Remotely" href="concepts/cremdbug.htm"/>
-		<topic label="Connecting to a remote VM with the Remote Java application launch configuration" href="tasks/task-remotejava_launch_config.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-    </context>
-	<context  id="edit_launch_configuration_action_context" >
-	  	<description>This command opens the launch configuration dialog on the launch configuration associated with the selection.</description>
-		<topic label="Edit Launch Configuration" href="reference/views/debug/ref-editlaunchconfig.htm"/>
-		<topic label="Changing Debugger Launch Options" href="tasks/tasks-9.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="edit_source_lookup_path_context">
-		<description>This command allows you to edit the source lookup path.</description>
-		<topic label="Edit Source Lookup" href="reference/views/debug/ref-editsourcelookup.htm"/>
-		<topic label="Lookup Source" href="reference/views/debug/ref-lookupsource.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context> 
-	<context  id="lookup_source_context">
-		<description>Forces source lookup.</description>
-		<topic label="Lookup Source" href="reference/views/debug/ref-lookupsource.htm"/>
-		<topic label="Edit Source Lookup" href="reference/views/debug/ref-editsourcelookup.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context id="open_declared_type_debug_view">
-		<description>This command opens the declared type of the selected stack frame in an editor</description>
-		<topic label="Open Declared Type" href="reference/views/debug/ref-opendeclared.htm"/>
-		<topic label="Open Declared Type Hierarchy" href="reference/views/debug/ref-opendeclaredhier.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm"/>
-	</context>
-	<context id="open_declared_type_hierarchy_debug_view">
-		<description>This command opens the declared type of the selected stack frame in an editor</description>
-		<topic label="Open Declared Type Hierarchy" href="reference/views/debug/ref-opendeclaredhier.htm"/>
-		<topic label="Open Declared Type" href="reference/views/debug/ref-opendeclared.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm"/>
-	</context>
-	<context  id="relaunch_action_context" >
-		<description>This command relaunches the selected debug target or process.</description>
-		<topic label="Relaunch" href="reference/views/debug/ref-relaunch.htm" />
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="resume_action_context" >
-		<description>This command resumes the selected thread or the thread containing the selected stack frame.</description>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Resuming Threads" href="tasks/task-resuming_threads.htm" />
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Suspending Threads" href="tasks/task-suspending_threads.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="step_with_filters_action_context" >
-		<description>This command toggles step filters on/off, which are applied to the step into, over, and return commands.</description>
-		<topic label="Use Step Filters" href="reference/views/debug/ref-usestepfilters.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-		<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-		<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="step_into_action_context" >
-		<description>This command steps into the highlighted statement.</description>
-		<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-		<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-		<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="step_over_action_context" >
-		<description>This command steps over the highlighted statement. Execution will continue at the next line either in the same method or (if you are at the end of a method) it will continue in the method from which the current method was called.</description>
-		<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-		<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-		<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="step_return_action_context" >
-		<description>This command steps out of the current method. The execution stops after exiting the current method.</description>
-		<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-		<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-		<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="suspend_action_context" >
-		<description>This command suspends the selected debug target so that you can browse or modify code, inspect data, step, and so on.</description>
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Suspending Threads" href="tasks/task-suspending_threads.htm"/>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Resuming Threads" href="tasks/task-resuming_threads.htm" />
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="terminate_action_context" >
-		<description>This command terminates the selected debug target.</description>
-		<topic label="Terminate" href="reference/views/debug/ref-terminate.htm"/>
-		<topic label="Terminate/Disconnect All" href="reference/views/debug/ref-terminateall.htm"/>
-		<topic label="Terminate and Relaunch" href="reference/views/debug/ref-terminaterelaunch.htm"/>
-		<topic label="Terminate and Remove" href="reference/views/debug/ref-terminateandremove.htm"/>
-		<topic label="Connecting to a remote VM with the Remote Java application launch configuration" href="tasks/task-remotejava_launch_config.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="terminate_all_action_context" >
-		<description>This command terminates all active debug targets.  If a target cannot be terminated, it will be disconnected.</description>
-		<topic label="Terminate/Disconnect All" href="reference/views/debug/ref-terminateall.htm"/>
-		<topic label="Terminate" href="reference/views/debug/ref-terminate.htm"/>
-		<topic label="Terminate and Relaunch" href="reference/views/debug/ref-terminaterelaunch.htm"/>
-		<topic label="Terminate and Remove" href="reference/views/debug/ref-terminateandremove.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="terminate_and_remove_action_context" >
-		<description>This command terminates the selected process or debug target and removes it from the view.</description>
-		<topic label="Terminate and Remove" href="reference/views/debug/ref-terminateandremove.htm"/>
-		<topic label="Terminate" href="reference/views/debug/ref-terminate.htm"/>
-		<topic label="Terminate/Disconnect All" href="reference/views/debug/ref-terminateall.htm"/>
-		<topic label="Terminate and Relaunch" href="reference/views/debug/ref-terminaterelaunch.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context id="terminate_and_relaunch_action_context">
-		<description>This command terminates and removes the selected launch from the debug view</description>
-		<topic label="Terminate and Relaunch" href="reference/views/debug/ref-terminaterelaunch.htm"/>
-		<topic label="Terminate" href="reference/views/debug/ref-terminate.htm"/>
-		<topic label="Terminate/Disconnect All" href="reference/views/debug/ref-terminateall.htm"/>
-		<topic label="Terminate and Remove" href="reference/views/debug/ref-terminateandremove.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context id="view_management_action_context">
-		<description>This command opens the view management preference page that is used to control which views are opened and closed while debugging.</description>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="drop_to_frame_action_context" >
-		<description>This command resets the instruction pointer to the first line of the method associated with the selected stack frame. All frames above the selected stack frame are removed from the stack.</description>
-		<topic label="Drop to Frame" href="reference/views/debug/ref-droptoframe.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="remove_all_terminated_action_context" >
-		<description>This command removes all terminated launches from the view.</description>
-		<topic label="Remove All Terminated Launches" href="reference/views/debug/ref-removeallterminated.htm" /> 
-		<topic label="Terminate and Remove" href="reference/views/debug/ref-terminateandremove.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-    <context id="debug_view_mode_auto_action_context">
-        <description>Configures the debug view to switch layout between a tree and a breadcrumb viewer automatically when the view is resized.</description>
-        <topic href="reference/views/debug/ref-layout_automatic.htm" label="Automatic Layout"/>
-        <topic href="reference/views/debug/ref-debug_view.htm" label="Debug View"/>
-        <topic href="reference/views/debug/ref-breadcrumb.htm" label="Debug Breadcrumb"/>
-        <topic href="reference/views/debug/ref-layout_breadcrumb.htm" label="Breadcrumb Layout"/>
-        <topic href="reference/views/debug/ref-layout_tree.htm" label="Tree Layout"/>
-    </context>
-    <context id="debug_view_mode_compact_action_context">
-        <description>Configures the debug view layout to use a breadcrumb viewer.</description>
-        <topic href="reference/views/debug/ref-layout_breadcrumb.htm" label="Breadcrumb Layout"/>
-        <topic href="reference/views/debug/ref-debug_view.htm" label="Debug View"/>
-        <topic href="reference/views/debug/ref-breadcrumb.htm" label="Debug Breadcrumb"/>
-        <topic href="reference/views/debug/ref-layout_automatic.htm" label="Automatic Layout"/>
-        <topic href="reference/views/debug/ref-layout_tree.htm" label="Tree Layout"/>
-    </context>
-    <context id="debug_view_mode_full_action_context">
-        <description>Configures the debug view layout to use a tree viewer.</description>
-        <topic href="reference/views/debug/ref-layout_tree.htm" label="Tree Layout"/>
-        <topic href="reference/views/debug/ref-debug_view.htm" label="Debug View"/>
-        <topic href="reference/views/debug/ref-breadcrumb.htm" label="Debug Breadcrumb"/>
-        <topic href="reference/views/debug/ref-layout_automatic.htm" label="Automatic Layout"/>
-        <topic href="reference/views/debug/ref-layout_breadcrumb.htm" label="Breadcrumb Layout"/>
-    </context>
-    <context id="debug_view_drop_down_autoexpand_action_context">
-        <description>Configures the Debug Breadcrumb Drop-down to automatically expand elements when opened.</description>
-        <topic href="reference/views/debug/ref-layout_breadcrumb_auto_expand.htm" label="Breadcrumb Layout"/>
-        <topic href="reference/views/debug/ref-debug_view.htm" label="Debug View"/>
-        <topic href="reference/views/debug/ref-breadcrumb.htm" label="Debug Breadcrumb"/>
-    </context>
-	
-<!--
-	Detail Pane
--->
-	<context id="detail_pane_context">
-	    <description>Provides detailed information about the selected variable(s).  By default, the detail pane uses a source viewer to display text with source markup.  When debugging a Java application, the detail pane displays the toString() value of the selected variable.</description>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>
-    <context id="detail_pane_assign_value_action_context">
-	    <description>This command allows you to assign a new value to the selected variable by evaluating text in the detail pane.</description>
-	    <topic label="Assign Value" href="reference/views/shared/ref-assignvalue.htm" />
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>	
-    <context id="detail_pane_content_assist_action_context">
-	    <description>This command opens a popup dialog with context sensitive code help.</description>
-	    <topic label="Content Assist" href="reference/views/shared/ref-contentassist.htm" />
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>
-    <context id="detail_pane_cut_action_context">
-	    <description>This command allows you to copy the selected text to the system clipboard and remove it from the detail pane.</description>
-	    <topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-	    <topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-	    <topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-	    <topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>
-    <context id="detail_pane_copy_action_context" >
-		<description>This command copies the selection to the system clipboard.</description>
-		<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-		<topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-		<topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-	</context>
-    <context id="detail_pane_paste_action_context">
-	    <description>This command allows you to copy text from the system clipboard into the detail pane.</description>
-	    <topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-	    <topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-	    <topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-	    <topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-    </context>
-    	<context id="detail_pane_select_all_action_context">
-    	<description>This command allows you to select all of the text in the detail pane.</description>
-    	<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-    	<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-	    <topic label="Cut" href="reference/views/shared/ref-cut.htm" />
-    	<topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-    	<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-    </context>
-    <context id="detail_pane_find_replace_action_context">
-    	<description>This command allows you to search for a specified pattern within the detail pane.</description>
-	    <topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-    </context>
-	<context id="detail_pane_word_wrap_action_context" >
-		<description>This command toggles word wrap on and off in the detail pane.</description>
-		<topic label="Wrap Text in the Detail Pane" href="reference/views/shared/ref-wrap.htm"/>
-		<topic label="Max Length in the Detail Pane" href="reference/views/shared/ref-maxlength.htm"/>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-	</context>
-	<context id="detail_pane_max_length_action_context">
-   		<description>This dialog allows you to change the maximum number of characters allowed in the detail pane.</description>
-   		<topic label="Max Length in the Detail Pane" href="reference/views/shared/ref-maxlength.htm"/>
-		<topic label="Wrap Text in the Detail Pane" href="reference/views/shared/ref-wrap.htm"/>
-   		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-   	</context>
-
-<!-- 
-	Dialogs 
--->
-	<context id="variable_selection_dialog_context">
-		<description>This dialog allows you to select variables to be used as launch configuration parameters. Variables are evaluated each time you launch your configuration, which can give your configuration dynamic behavior. Variables specifying 'Selected Resource...' are evaluated to the resource currently selected in the navigator or packages view, etc. at the time the configuration is launched.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="launch_configuration_dialog" >
-		<description>This dialog allows you to manage aspects of launching programs from within Eclipse.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context> 
-	<context id="launch_configuration_properties_dialog" >
-		<description>This dialog allows you to edit aspects of the launch configuration for the selected launch.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="launch_configuration_view_context" >
-		<description>Select a type in this tree view to create a new launch configuration. You can also select a specific launch configuration to duplicate, edit or delete it.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="edit_source_lookup_path_dialog" >
-		<description>This dialog allows you to edit the current source lookup path.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Edit Source Lookup Command" href="reference/views/debug/ref-editsourcelookup.htm"/>
-		<topic label="Lookup Source Command" href="reference/views/debug/ref-lookupsource.htm"/>
-	</context>
-	<context id="add_source_container_dialog">
-		<description>This dialog allows you to add one of a variety of source containers to your source lookup path.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Edit Source Lookup Command" href="reference/views/debug/ref-editsourcelookup.htm"/>
-		<topic label="Lookup Source Command" href="reference/views/debug/ref-lookupsource.htm"/>		
-	</context>
-	<context id="single_launch_configuration_dialog" >
-		<description>This dialog allows you to edit a launch configuration.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="import_launch_configurations_context" >
-		<description>This wizard page allows you to import a launch configuration from the local file system into your workspace.</description>
-  <topic href="reference/wizards/ref-import_launch_configs.htm" label="Import Launch Configurations Wizard"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="export_launch_configurations_context" >
-		<description>This wizard page allows you to export launch configurations from your workspace to the local file system.</description>
-  <topic href="reference/wizards/ref-export_launch_configs.htm" label="Export Launch Configurations Wizard"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="export_breakpoints_wizard_page_context" >
-		<description>This wizard page allows you to select breakpoints to export to the local filesystem.</description>
-		<topic label="Export Breakpoints" href="reference/wizards/ref-export_breakpoints.htm"/>
-		<topic label="Import Breakpoints" href="reference/wizards/ref-import_breakpoints.htm"/>
-		<topic label="Adding Line Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Removing Line Breakpoints" href="tasks/task-remove_line_breakpoints.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-	</context>
-	<context id="import_breakpoints_wizard_page_context" >
-		<description>This wizard page allows you to import breakpoints into your workspace from a previously exported file.</description>
-		<topic label="Import Breakpoints" href="reference/wizards/ref-import_breakpoints.htm"/>
-		<topic label="Export Breakpoints" href="reference/wizards/ref-export_breakpoints.htm"/>
-		<topic label="Adding Line Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Removing Line Breakpoints" href="tasks/task-remove_line_breakpoints.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-	</context> 
-	<context id="add_watch_expression_dialog_context" >
-		<description>This dialog allows you to create a new watch expression.</description>
-		<topic label="Add Watch Expression" href="reference/views/expressions/ref-addwatch.htm"/>
-		<topic label="Edit Watch Expression" href="reference/views/expressions/ref-edit.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context>
-	<context id="edit_watch_expression_dialog_context" >
-		<description>This dialog allows you to edit an existing watch expression.</description>
-		<topic label="Edit Watch Expression" href="reference/views/expressions/ref-edit.htm"/>
-		<topic label="Add Watch Expression" href="reference/views/expressions/ref-addwatch.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context>
-	<context id="find_element_dialog_context">
-		<description>This dialog allows you to search for an element by name.</description>
-	</context>
-	<context id="configure_columns_dialog_context">
-		<description>This dialog allows you to select the columns to display in a view.</description>
-		<topic label="Toggle Columns" href="reference/views/shared/ref-showcolumns.htm" />
-		<topic label="Select Columns" href="reference/views/shared/ref-selectcolumns.htm" />
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-	</context> 
-	<context  id="AddMemoryRenderingDialog_context" >
-		<description>This dialog allows you to add a memory rendering.</description>
-	</context>
-	<context id="group_breakpoints_dialog_context">
-   		<description>This dialog allows you to create your own custom grouping for your breakpoints in the breakpoints view.</description>
-   		<topic label="Group By" href="reference/views/breakpoints/ref-groupby_viewaction.htm"/>
-   		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm"/>
-   		<topic label="Working Sets..." href="reference/views/breakpoints/ref-workingsets_viewaction.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-   	</context>
-   	<context id="organize_favorites_dialog_context">
-   		<description>This dialog allows you to add/remove and arrange your favorite launches.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-   	</context>
-   	<context id="select_breakpoint_workingset_dialog">
-   		<description>This dialog allows users to quickly select a new default breakpoint workingset</description>
-   		<topic label="Group By" href="reference/views/breakpoints/ref-groupby_viewaction.htm"/>
-   		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm"/>
-   		<topic label="Working Sets..." href="reference/views/breakpoints/ref-workingsets_viewaction.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-   	</context>
-   	<context id="delete_associated_launch_configs_dialog">
-   		<description>This dialog prompts users to clean up launch configurations that are associated with, or used to launch code from, the project that is being deleted </description>
-   		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-   	</context>
-   	<context id="select_launch_modes_dialog">
-   		<description>This dialog prompts users to select an available set of modes to set on the current launch configuration in the event the current set is not valid.</description>
-   		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-   	</context>
-   	<context id="select_launchers_dialog">
-   		<description>This dialog allows you to select a preferred launcher to continue launching if more than one launcher is available to launch a particular launch configuration in a given mode.</description>
-   		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-   	</context>
-	<context id="select_resources_to_save_dialog">
-		<description>This dialog is used to select the resources that you wish to save prior to continuing launching. Canceling this dialog will cancel the launch.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="select_launch_method_dialog">
-		<description>This dialog allows you to select a way to launch the currently selected resource.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-	</context>
-	<context id="select_launch_configuration_dialog">
-		<description>This dialog allows you to select a launch configuration.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-	</context>
-	<context id="select_directory_source_container_dialog">
-		<description>This dialog allows you to select a directory from the file system to search for program source.</description>
-		<topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-		<topic label="Source Attachments" href="reference/ref-properties-source-attachment.htm"/>
-	</context>
-	<context id="select_configuration_type_dialog">
-		<description>This dialog allows you to select a type of configuration to create.</description>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context id="select_favorites_dialog">
-		<description>This dialog allows you to select one or more launch configurations to add to your favorites listing.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-	</context>
-	<context id="select_native_environment_dialog">
-		<description>This dialog allows you to select one or more native environment variables from a list to add to your launch configuration.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-	</context>
-	<context id="select_launch_configuration_migration_dialog">
-		<description>This dialog allows you to select one or more launch configurations to migrate.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-
-<!--
-	Editors
--->
-	<context  id="enable_disable_breakpoint_action_context" >
-		<description>This command toggles the breakpoint in the editor ruler.</description>
-		<topic label="Debugger" href="concepts/cdebugger.htm" />
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Adding Line Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Removing Line Breakpoints" href="tasks/task-remove_line_breakpoints.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-	</context>
-
-<!--
-	Expressions View
--->
-	<context  id="expression_view_context" >
-		<description>This view shows the results of inspecting an expression or variable.</description>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Change Variable Values" href="reference/views/shared/ref-changevarvalue.htm" />
-		<topic label="Remove Selected Expressions" href="reference/views/expressions/ref-remove.htm" />
-		<topic label="Remove All Expressions" href="reference/views/expressions/ref-removeall.htm" />
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-	<context  id="select_all_expressions_action_context" >
-		<description>This command selects all expressions in the view.</description>
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context>         
-	<context  id="remove_expression_action_context" >
-		<description>This command deletes the selected expressions.</description>
-		<topic label="Remove Selected Expressions" href="reference/views/expressions/ref-remove.htm" />
-		<topic label="Remove All Expressions" href="reference/views/expressions/ref-removeall.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context>      
-	<context  id="remove_all_expressions_action_context" >
-		<description>This command deletes all expressions in the view.</description>
-		<topic label="Remove All Expressions" href="reference/views/expressions/ref-removeall.htm" />
-		<topic label="Remove Selected Expressions" href="reference/views/expressions/ref-remove.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context>
-	<context  id="add_watch_expression_context">
-		<description>This command adds a watch expression to the Expressions View.</description>
-		<topic label="Add Watch Expression" href="reference/views/expressions/ref-addwatch.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context> 
-	<context  id="reevaluate_watch_expression_context">
-		<description>This command reevaluates a watch expression.</description>
-		<topic label="Reevaluate Watch Expression" href="reference/views/expressions/ref-reevaluate.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context> 
-	<context  id="disable_watch_expression_context">
-		<description>This command disables a watch expression.</description>
-		<topic label="Disable Selected Watch Expression" href="reference/views/expressions/ref-disable.htm"/>
-		<topic label="Enable Selected Watch Expression" href="reference/views/expressions/ref-enable.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context> 
-	<context  id="enable_watch_expression_context">
-		<description>This command enables a watch expression.</description>
-		<topic label="Enable Selected Watch Expression" href="reference/views/expressions/ref-enable.htm"/>
-		<topic label="Disable Selected Watch Expression" href="reference/views/expressions/ref-disable.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context> 			
-	<context  id="edit_watch_expression_context">
-		<description>This command allows for editing of watch expressions.</description>
-		<topic label="Edit Watch Expression" href="reference/views/expressions/ref-edit.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context> 
-	<context  id="convert_to_watch_expression_context" >
-		<description>This command replaces the selected object with an equivalent watch expression.</description>
-		<topic label="Convert to Watch Expression" href="reference/views/expressions/ref-convert.htm"/>
-		<topic label="Inspect" href="reference/views/expressions/ref-inspect.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-	</context>
-
-<!-- 
-	Launch Configuration Tabs
--->
-	<context id="launch_configuration_dialog_refresh_tab" >
-		<description>This tab allows you to choose which resources are refreshed when a launch configuration is executed.</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-	</context>
-	<context id="launch_configuration_dialog_common_tab" >
-		<description>This tab allows you to set the type of the launch configuration, which favorites menu it will be displayed within and whether to launch the configuration in the background.</description>
-		<topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-	</context>
-	<context id="launch_configuration_dialog_environment_tab" >
-		<description>This tab allows you to create and configure the environment variables that will be passed into the launch configuration when it is executed</description>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_source_tab" >
-		<description>This tab allows you to define the location of source files used to display source when debugging a Java application.</description>
-		<topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-		<topic label="Source Attachments" href="reference/ref-properties-source-attachment.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_launchers_tab" >
-		<description>This tab allows you to specify the launcher to use with the selected launch configuration when more than one is available.</description>
-		<topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"/>
-	</context>
-
-<!--
-	Memory View
--->
-	<context  id="MemoryView_context" >
-		<description>The Memory view lets you see blocks of memory rendered into a variety of formats.
-
-The Memory view is divided into two panes. The <b>Monitors</b> pane lists expressions and addresses that have been added to the Memory view. The <b>Renderings</b> pane contains renderings that you add for the memory that is being monitored.
-
-To see memory for a variable or expression in the Memory view, you can use the <b>Add Memory Monitor</b> action and dialog box.
-
-In the view, you can change the contents of memory. You can also change the address range that you want to see in the view.</description>
-	</context>
-	<context  id="ResetBaseAddressContextAction_context" >
-		<description>If you have moved away from the address that you originally set to monitor, choose this action to position the cursor back to the base address of the memory monitor.</description>
-	</context>
-	<context  id="TableRenderingPrefAction_context" >
-		<description>Select this to open the <b>Table Renderings Preferences</b> dialog box.</description>
-	</context>
-	<context  id="PrintViewTabContextAction_context" >
-		<description>The behavior of this action depends on table renderings preference settings. If you have set table renderings to automatic memory loading mode, selecting the <b>Print</b> action will print the rendering that is currently visible. If you have set table renderings to manual memory loading mode, selecting the <b>Print</b> action will print the entire buffer.</description>
-	</context>
-	<context  id="GoToAddressAction_context" >
-		<description>Select this to open the address bar at the bottom of the rendering. The address bar allows you go to an address that you specify, go to an offset, or jump memory units.</description>
-	</context>
-	<context  id="CopyViewTabToClipboardContextAction_context" >
-		<description>The behavior of this action depends on table renderings preference settings. If you have set table renderings to automatic memory loading mode, selecting the <b>Copy To Clipboard</b> action will copy the rendering that is currently visible. If you have set table renderings to manual memory loading mode, selecting the <b>Copy To Clipboard</b> action will copy the entire buffer.</description>
-	</context>
-	<context  id="RemoveMemoryBlockAction_context" >
-		<description>Choose this menu item to remove the selected memory monitor.</description>
-	</context>   
-	<context  id="RemoveAllMemoryBlocksAction_context" >
-		<description>Remove all memory monitors from the workbench.</description>
-	</context>   
-	<context id="RemoveRenderingContextAction_context">
-		<description>Choose this menu item to remove the selecting rendering.</description>
-	</context>
-	<context id="AddRenderingContextAction_context">
-		<description>This action opens a dialog box which allows you to add a memory rendering for any variable or expression that is currently being monitored.</description>
-	</context>   
-	<context id="LittleEndianAction_context">
-		<description>Select this to display the rendering as Little Endian.</description>
-	</context>   
-	<context id="BigEndianAction_context">
-		<description>Select this to display the rendering as Big Endian.</description>
-	</context>   
-	<context id="RestoreDefEndianessAction_context">
-		<description>Select this to display the rendering in its default endianess.</description>
-	</context>   
-	<context id="ReformatAction_context">
-		<description>Select this to resize all columns so that all text within them can be viewed.</description>
-	</context>   
-	<context id="ShowAddressColumnAction_context">
-		<description>This action toggles the visibility of the Address column.</description>
-	</context>   
-	<context id="SelectCodePagesAction_context">
-		<description>This command opens the dialog for setting up codepage preferences in the Memory View.</description>
-	</context>
-	<context id="CodePagesPrefDialog_context">
-		<description>Use this page to indicate the codepages to use for rendering memory to ASCII and EBCDIC strings.
-
-If you have changed one or both of the values in this page and would like the values to return to default values, click <b>Restore Defaults</b>.</description>
-	</context>
-	<context id="SelectCodepageDialog_context">
-		<description>This page sets the codepage for the selected preference.</description>
-	</context>
-	<context id="SetPaddedStrAction_context">
-		<description>This commands opens the dialog for setting up the padded string used in memory renderings.</description>
-	</context>
-	<context id="SetPaddedStrDialog_context">
-		<description>In this page, specify the string that you want to display when memory contents cannot be determined.
-
-If you have changed the padded string value in this page and would like it to return to the default value, click <b>Restore Defaults</b>.</description>
-	</context>
-	<context id="NextPageAction_context">
-		<description>Select this to load the next page of memory.</description>
-	</context>
-	<context id="PrevPageAction_context">
-		<description>Select this to load the previous page of memory.</description>
-	</context>
-	<context  id="switchMemoryBlockAction_context" >
-		<description>This command displays the renderings associated with the next memory monitor.</description>
-	</context>
-	<context  id="resetMemoryMonitor_context" >
-		<description>If you have moved away from the address that you originally set to monitor, choose this action to position the cursor back to the base address of the memory monitor. By default, the visible renderings will also be reset to the base address. To reset all renderings in the current Memory view to the base address, modify the Memory view preferences.</description>
-	</context>
-	<context  id="FormatTableRenderingAction_context" >
-		<description>Select this to open the Format dialog box, which allows you to set the number of units per row and the number of units per column in the memory rendering.</description>
-	</context>
-	<context  id="MemoryViewPreferences_context" >
-		<description>Select this to open the Memory view Preferences dialog box.</description>
-	</context>  
-	<context  id="memory_view_pane_orientation_action_context" >
-		<description>The Memory view is divided into two panes. The <b>Monitors</b> pane lists expressions and addresses that have been added to the Memory view. The <b>Renderings</b> pane contains renderings that you add for the memory that is being monitored. You can set these two panes to display in a horizontal orientation (side-by-side) or in a vertical orientation (top-to-bottom) by selecting the appropriate menu item.</description>
-	</context>
-	<context  id="GoToAddressDialog_context" >
-		<description>This dialog box lets you jump to an address in the memory block.</description>
-	</context>       
-	<context  id="GoToAddressComposite_context" >
-		<description>The address bar allows you to go to a location in memory which you specify. These options are available by pull-down menu in the address bar:
-
-- <b>Go to Address:</b> Select this and then enter an address that you want to jump to. The rendering will be positioned so that the address entered is visible and selected.
-
-- <b>Go to Offset:</b> Select this and then enter the offset. The rendering will be positioned so that the address of the expression (base address), plus the offset entered, is visible and selected. A negative value will position the rendering back from the base address.
-
-- <b>Jump Memory Units:</b> This function takes the currently-selected address and adds the number of memory units that you specify to it. The resulting address is selected. A negative value will position the rendering back from the current address.
-
-For all of these entries, you can input them as HEX by selecting the <b>Input as Hex</b> check box (if this check box is not selected, input will be decimal). Once you have made the entry in the field, hit Enter or click <b>OK</b> to go to the location in the rendering. To close this section, click <b>Cancel</b>.</description>
-	</context>       
-	<context  id="MemoryViewPreferencePage_context" >
-		<description>Preference page for setting the default column size when a new memory monitor is added.</description>
-	</context>
-	<context  id="MonitorMemoryBlockDialog_context" >
-		<description>Use this dialog box to specify an address or expression that you would like to add to the Memory view.</description>
-	</context>
-	<context  id="FormatTableRenderingDialog_context" >
-		<description>Use this dialog box to set the number of units per row and the number of units per column. As you make these settings, the <b>Preview</b> window in the dialog box displays the monitor layout that you are setting. To save these settings as the default layout, click <b>Save as Defaults</b>.</description>
-	</context>
-	<context  id=" AbstractAsyncTableRendering_context" >
-		<description>This memory rendering displays content of a memory monitor in table format.</description>
-	</context>
-	<context  id="addMemoryMonitorAction_context" >
-		<description>Select this to open the Monitor Memory dialog box, which allows you to specify an address or expression that you would like to add to the Memory view.</description>
-	</context> 
-	<context id="tableRenderingPropertiesAction_context">
-		<description>Select this to open a page that displays properties for the selected memory.</description>
-	</context>
-	
-<!--
-	Modules View
--->	
-	<context id="modules_view_context">
-		<description>This view displays the modules in your program.</description>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-	</context>
-
-<!-- 
-	Preference Pages 
--->
-	<context  id="debug_preference_page_context">
-		<description>On this page, you can set preferences for debugging your programs.</description>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Console Preferences" href="reference/preferences/run-debug/ref-console.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Perspectives Preferences" href="reference/preferences/run-debug/ref-perspectives.htm"/>
-		<topic label="String Substitution Preferences" href="reference/preferences/run-debug/ref-string_substitution.htm"/>
-		<topic label="View Management Preferences" href="reference/preferences/run-debug/ref-view_management.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context id="console_preference_page_context" >
-		<description>On this page, you can set the preferences for the debug console.</description>
-		<topic label="Console Preferences" href="reference/preferences/run-debug/ref-console.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Perspectives Preferences" href="reference/preferences/run-debug/ref-perspectives.htm"/>
-		<topic label="String Substitution Preferences" href="reference/preferences/run-debug/ref-string_substitution.htm"/>
-		<topic label="View Management Preferences" href="reference/preferences/run-debug/ref-view_management.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context  id="launching_preference_page_context">
-		<description>On this page, you can configure launch options.</description>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Default Launchers Preferences" href="reference/preferences/run-debug/ref-default_launchers.htm"/>	
-		<topic label="Console Preferences" href="reference/preferences/run-debug/ref-console.htm"/>
-		<topic label="Launch Configurations Preferences" href="reference/preferences/run-debug/ref-launch_configurations.htm"/>
-		<topic label="Perspectives Preferences" href="reference/preferences/run-debug/ref-perspectives.htm"/>
-		<topic label="String Substitution Preferences" href="reference/preferences/run-debug/ref-string_substitution.htm"/>
-		<topic label="View Management Preferences" href="reference/preferences/run-debug/ref-view_management.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context  id="launch_configuration_preference_page_context">
-		<description>On this page, you can configure the filters used in the launch dialog and migrate launch configurations.</description>
-		<topic label="Launch Configurations Preferences" href="reference/preferences/run-debug/ref-launch_configurations.htm"/>
-		<topic label="Default Launchers Preferences" href="reference/preferences/run-debug/ref-default_launchers.htm"/>	
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context id="launch_delegate_preference_page_context">
-		<description>On this page, you can select preferred launch tooling if there are duplicates for any given launch configuration type and set of modes.</description>
-		<topic label="Default Launchers Preferences" href="reference/preferences/run-debug/ref-default_launchers.htm"/>	
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Launch Configurations Preferences" href="reference/preferences/run-debug/ref-launch_configurations.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context  id="perspective_preference_page_context">
-		<description>On this page, you can configure the perspectives used when running and debugging.</description>
-		<topic label="Perspectives Preferences" href="reference/preferences/run-debug/ref-perspectives.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Console Preferences" href="reference/preferences/run-debug/ref-console.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="String Substitution Preferences" href="reference/preferences/run-debug/ref-string_substitution.htm"/>
-		<topic label="View Management Preferences" href="reference/preferences/run-debug/ref-view_management.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context id="simple_variable_preference_page_context">
-		<description>One this page, you can create and configure simple launch variables which you can reference in launch configurations that support variables.</description>
-		<topic label="String Substitution Preferences" href="reference/preferences/run-debug/ref-string_substitution.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Console Preferences" href="reference/preferences/run-debug/ref-console.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Perspectives Preferences" href="reference/preferences/run-debug/ref-perspectives.htm"/>
-		<topic label="View Management Preferences" href="reference/preferences/run-debug/ref-view_management.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context  id="view_management_preference_page_context">
-		<description>On this page, you can select the perspectives that debug related views will be opened in automatically.</description>
-		<topic label="View Management Preferences" href="reference/preferences/run-debug/ref-view_management.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Console Preferences" href="reference/preferences/run-debug/ref-console.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Perspectives Preferences" href="reference/preferences/run-debug/ref-perspectives.htm"/>
-		<topic label="String Substitution Preferences" href="reference/preferences/run-debug/ref-string_substitution.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context  id="table_renderings_preference_page_context">
-		<description>Use this page to configure the memory loading mode in table renderings:
-
-- <b>Automatic:</b> Select this option to have the debugger automatically load a buffer of memory before and after the visible region in the Memory view. When this option is selected, you can easily scroll away from the visible region.
-
-- <b>Manual:</b> Select this option if you want to specify the exact number of lines of memory block to display in the Memory view. When you specify an exact memory block to display, you can only move away from that block by using pop-up menu actions.</description>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	<context  id="resetMemoryMonitor_preference_page_context" >
-		<description>You can reset a memory monitor to the base address if you have moved away from it. When you reset a monitor to the base address, you can set it to reset only the visible renderings - or you can set it to reset all renderings. If you choose to reset all renderings, performance of the reset operation can be negatively impacted.</description>
-		<topic label="Debug Preferences" href="reference/preferences/run-debug/ref-run_debug.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-	</context>
-	
-<!-- 
-	Property Pages 
--->
-	<context id="process_property_page_context" >
-		<description>This page displays the run-at time, name and command line used to launch the selected process.</description>
-	</context>
-	<context id="process_page_run_at_time_widget">
-		<description>The time when the selected process was initially run.</description>
-	</context>
-	<context id="TableRenderingPropertiesPage_context" >
-		<description>This page displays properties for the selected memory.</description>
-	</context>
-	<context id="run_debug_resource_property_page">
-		<description>This page displays all of the launch configurations that fall within the scope of the selected resource.</description>
-  <topic href="reference/propertypages/ref-properties-rundebug.htm" label="Run / Debug Property Page"/>
-  <topic href="tasks/tasks-java-local-configuration.htm" label="Creating a Java application launch configuration"/>
-  <topic href="tasks/task-running_and_debugging.htm" label="Running and Debugging"/>
-  <topic href="reference/preferences/run-debug/ref-launching.htm" label="Launching Preferences"/>
-	</context>
-
-<!--
-	Registers View
--->
-	<context id="registers_view_context">
-		<description>This view displays the registers in your program.</description>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Inspecting Values" href="tasks/task-inspecting.htm"/>
-		<topic label="Show Type Names" href="reference/views/shared/ref-showtypenames.htm" />
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-
-<!--
-	Run Menu
--->
-	<context  id="debug_last_action_context" >
-      	<description>This command re-launches the most recently launched application in debug mode, or debugs the selected resource or active editor, based on your launching preferences</description>
-		<topic label="Debug / Debug Last" href="reference/menus/run/ref-dll_debug.htm"/>
-		<topic label="Debug Toolbar Action" href="reference/ref-toolbar-run.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-    </context>
-	<context  id="run_action_context" >
-      	<description>This command allows you to run the selected executable.</description>
-		<topic label="Run Toolbar Action" href="reference/ref-toolbar-run.htm"/>
-		<topic label="Run / Run Last" href="reference/menus/run/ref-rll_run.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-    </context>
-	<context  id="run_last_action_context" >
-		<description>This command re-launches the most recently launched application in run mode, or launches the selected resource or active editor, based on your launching preferences</description>
-		<topic label="Run / Relaunch" href="reference/menus/run/ref-rll_run.htm"/>
-		<topic label="Run Toolbar Action" href="reference/ref-toolbar-run.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-    </context>
-	<context  id="profile_action_context" >
-     	<description>This command allows you to profile the selected executable.</description>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>        
-	<context  id="profile_last_action_context" >
-    	<description>This command re-launches the most recently launched application in profile mode.</description>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Launching Preferences" href="reference/preferences/run-debug/ref-launching.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>
-	<context  id="inspect_action_context" >
-      	<description>This command allows you to inspect the result of evaluating the selected expression.</description>
-		<topic label="Inspecting in the Display View" href="reference/views/shared/ref-inspect.htm" /> 
-		<topic label="Display View" href="reference/views/display/ref-display_view.htm" />
-		<topic label="Inspecting in the Expressions View" href="reference/views/expressions/ref-inspect.htm" /> 
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Inspecting in the Variables View" href="reference/views/shared/ref-inspect.htm" /> 
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>
-	<context  id="run_to_line_action_context" >
-    	<description>This command resumes execution to the selected line.</description> 
-		<topic label="Run To Line" href="reference/menus/run/ref-run_to_line.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" /> 
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-  	</context>
-	<context  id="open_debug_configurations_action_context" >
-		<description>This command opens the launch configuration dialog in debug mode.</description>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>    
-	<context  id="open_run_configurations_action_context" >
-		<description>This command opens the launch configuration dialog in run mode.</description>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>    
-	<context  id="open_profile_configurations_action_context" >
-		<description>This command opens the launch configuration dialog in profile mode.</description>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>     
-	<context  id="relaunch_history_action_context" >
-		<description>This command allows you to select a previous launch from the launch history.</description>
-		<topic label="Relaunching a Previously-launched Program" href="tasks/task-relaunch_program.htm" />
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>
-	<context  id="open_launch_configuration_action_context" >
-		<description>This command opens the launch configuration dialog in the context of the specified launch group.</description>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>
-	<context  id="debug_action_context" >
-      <description>This command allows you to run the selected executable under debugger control.</description> 
-	  <topic label="Debug Toolbar Action" href="reference/ref-toolbar-run.htm"/>
-	  <topic label="Debug / Debug Last" href="reference/menus/run/ref-dll_debug.htm"/>
-      <topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-      <topic label="Debugging Locally" href="concepts/clocdbug.htm"/>
-	  <topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>
-    <context id="toggle_breakpoint_action_context">
-	    <description>This command creates or removes a breakpoint based on the cursor location in the active editor.</description>
-		<topic label="Toggle Breakpoint" href="reference/menus/run/ref-toggle_breakpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>
-    <context id="toggle_line_breakpoint_action_context">
-	    <description>This command creates or removes a line breakpoint based on the cursor location in the active editor.</description>
-		<topic label="Toggle Line Breakpoint" href="reference/menus/run/ref-toggle_line_breakpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>
-    <context id="toggle_method_breakpoint_action_context">
-	    <description>This command creates or removes a method breakpoint based on the cursor location in the active editor or selected method.</description>
-		<topic label="Toggle Method Breakpoint" href="reference/menus/run/ref-toggle_method_breakpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>
-   <context id="toggle_watchpoint_action_context">
-	    <description>This command creates or removes a watchpoint based on the cursor location in the active editor or selected field.</description>
-		<topic label="Toggle Watchpoint" href="reference/menus/run/ref-toggle_watchpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-    </context>
-	<context id="skip_all_breakpoints_action_context" >
-		<description>When checked, breakpoints will not suspend execution while debugging.</description>
-		<topic label="Skip All Breakpoints" href="reference/views/breakpoints/ref-skipall_viewaction.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>
-    
-<!--
-	Shared Contexts
--->
-	<context id="find_element_context">
-		<description>This command finds an element by name.</description>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
- 	<context  id="change_value_action_context" >
-		<description>This command allows you to change the value of the selected variable.</description>
-		<topic label="Change Variable Value" href="reference/views/shared/ref-changevarvalue.htm" /> 
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-    </context>
-	<context  id="select_all_variables_action_context" >
-		<description>This command selects all elements in the view.</description>
-		<topic label="Change Variable Value" href="reference/views/shared/ref-selectall.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm"/>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Display View" href="reference/views/display/ref-display_view.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="copy_variables_to_clipboard_action_context" >
-		<description>This command copies a textual representation of the selected variables to the clipboard.</description>
-		<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="show_types_action_context" >
-		<description>This option can be toggled to show or hide type names of variables in the view.</description>
-		<topic label="Show Type Names" href="reference/views/shared/ref-showtypenames.htm" /> 
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="variables_content_providers_action_context" >
-		<description>This command toggles the display of logical variable structure.</description>
-		<topic label="Show Logical Structures Names" href="reference/views/shared/ref-showlogical.htm" /> 
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context> 
-	<context id="variables_select_detail_pane_action_context">
-	    <description>Use this menu to choose between several different types of detail panes, each capable of displaying information about selected variables in different ways.</description>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>
-    <context id="horizontal_detail_pane_layout_action_context">
-	    <description>This command reveals the detail pane and sets it in a horizontal alignment within the view.</description>
-	    <topic label="Horizontal View Orientation" href="reference/views/shared/ref-horizview.htm"/>
-	    <topic label="Vertical View Orientation" href="reference/views/shared/ref-vertview.htm"/>
-	    <topic label="View Only Layout" href="reference/views/shared/ref-viewonly.htm"/>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>
-    <context id="vertical_detail_pane_layout_action_context">
-	    <description>This command reveals the detail pane and sets it in a vertical alignment within the view.</description>
-	    <topic label="Vertical View Orientation" href="reference/views/shared/ref-vertview.htm"/>
-	    <topic label="Horizontal View Orientation" href="reference/views/shared/ref-horizview.htm"/>
-	    <topic label="View Only Layout" href="reference/views/shared/ref-viewonly.htm"/>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>
-    <context id="detail_pane_hidden_layout_action_context">
-	    <description>This command hides the detail pane within the view.</description>
-	    <topic label="View Only Layout" href="reference/views/shared/ref-viewonly.htm"/>
-	    <topic label="Horizontal View Orientation" href="reference/views/shared/ref-horizview.htm"/>
-	    <topic label="Vertical View Orientation" href="reference/views/shared/ref-vertview.htm"/>
-	    <topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-    </context>
-    <context id="show_columns_context">
-	    <description>This command toggles whether to display columns in the view.</description>
-		<topic label="Show Columns" href="reference/views/shared/ref-showcolumns.htm" />
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-    </context>
-    <context id="configure_columns_context">
-		<description>This command sets the visible columns in the associated view.</description>
-		<topic label="Select Columns" href="reference/views/shared/ref-selectcolumns.htm" />
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-	</context>
-    
-<!--
-	Variables View
---> 
-	<context  id="variable_view_context" >
-		<description>This view displays the variables in your program.</description>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Inspecting Values" href="tasks/task-inspecting.htm"/>
-		<topic label="Show Qualified Names in Variables View" href="reference/views/shared/ref-showqualified.htm" />
-		<topic label="Show Type Names in Variables View" href="reference/views/shared/ref-showtypenames.htm" />
-		<topic label="Add/Remove Watchpoint" href="reference/views/shared/ref-togglewp.htm" />
-		<topic label="Show Static Fields in Variables View" href="reference/views/shared/ref-showstatic.htm" />
-		<topic label="Show Constants in Variables View" href="reference/views/shared/ref-showconstants.htm" />
-		<topic label="Change Variable Values in the Variables View" href="reference/views/shared/ref-changevarvalue.htm" /> 
-		<topic label="Inspect in the Variables View" href="reference/views/shared/ref-inspect.htm" /> 
-	</context>
-		<context  id="variable_watch_action_context">
-		<description>This command creates a watch expression from the selected variable.</description>
-		<topic label="Create Watch Expression" href="reference/views/variables/ref-createwatch.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-
-</contexts>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml b/bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml
deleted file mode 100644
index 98c73d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_JDT.xml
+++ /dev/null

@@ -1,1848 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-    <!-- Actions -->
-
-    <context id="add_unimplemented_constructors_action_context">
-        <description>This command copies the constructors of the super class to the selected class.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="getter_setter_action_context">
-        <description>This command generates getter and setter methods for the selected field.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_methodbreakpoint_action_context">
-        <description>This command adds a method entry breakpoint for the selected method.</description>
-        <topic label="Adding Line Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-        <topic label="Removing Line Breakpoints" href="tasks/task-remove_line_breakpoints.htm"/>
-        <topic label="Enabling and disabling breakpoints" href="tasks/task-enable_disable_breakpoints.htm"/>
-        <topic label="Setting Method Breakpoints" href="tasks/task-set_method_breakpoints.htm"/>
-        <topic label="Applying Hit Counts" href="tasks/task-apply_hit_count.htm"/>
-        <topic label="Managing Conditional Breakpoints" href="tasks/task-manage_conditional_breakpoint.htm"/>
-        <topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-        <topic label="Breakpoints view" href="reference/ref-35.htm"/>
-        <topic label="Debugger" href="concepts/cdebugger.htm"/>
-        <topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-    </context>
-
-    <context id="add_methodstub_action_context">
-        <description>This command creates a method stub for the selected method.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="add_unimplemented_methods_action_context">
-        <description>Allows you to override methods from a superclass or to implement a method from an interface.</description>
-        <topic label="Override Methods dialog" href="reference/ref-dialog-override-method.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="show_in_packageview_action_context">
-        <description>Displays the selected element in the Package Explorer.</description>
-        <topic label="Showing a Type&apos;s Compilation Unit in the Package Explorer" href="tasks/tasks-74.htm"/>
-        <topic label="Package Explorer view" href="reference/views/ref-view-package-explorer.htm"/>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="show_in_hierarchyview_action_context">
-        <description>This command opens the Hierarchy view on the selected element.</description>
-        <topic label="Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="add_imports_on_selection_action_context">
-        <description>This command adds an import statement for the selected type to the compilation unit.</description>
-    </context>
-
-    <context id="organize_imports_action_context">
-        <description>This command generates the import statements for this type. It adds all required import statements and removes those that are not required.</description>
-    </context>
-
-    <context id="run_to_line_action_context">
-        <description>While debugging, this command allows you to run the program to the location of the cursor.</description>
-        <topic label="Run to Line" href="reference/menus/run/ref-run_to_line.htm"/>
-        <topic label="Stepping" href="tasks/task-stepping.htm"/>
-       <topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-        <topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-        <topic label="Debugger" href="concepts/cdebugger.htm"/>
-        <topic label="Remote debugging" href="concepts/cremdbug.htm"/>
-    </context>
-
-    <context id="toggle_presentation_action_context">
-        <description>Allows you to toggle the editor between displaying the whole compilation unit and the code for just the selected element.</description>
-        <topic label="Java editor concepts" href="reference/views/ref-java-editor.htm"/>
-    </context>
-
-    <context id="toggle_texthover_action_context">
-        <description>Allows you to switch the hover hints on and off for Javadoc and Debug.</description>
-        <topic label="Java editor reference" href="reference/views/ref-java-editor.htm"/>
-        <topic label="Java editor concepts" href="concepts/concept-java-editor.htm"/>
-    </context>
-
-    <context id="toggle_mark_occurrences_action_context">
-        <description>Allows you to switch mark occurrences on and off.</description>
-    </context>
-
-    <context id="display_action_context">
-        <description>This command evaluates the selected expression and shows the result in the Display view.</description>
-        <topic label="Displaying the result of evaluating an expression" href="tasks/task-display_evaluation_result.htm"/>
-        <topic label="Evaluating expressions" href="tasks/task-evaluating_expressions.htm"/>
-        <topic label="Display view" href="reference/views/display/ref-display_view.htm"/>
-    </context>
-
-    <context id="focus_on_selection_action">
-        <description>This command allows you to select a type visible in the Hierarchy view to become the new focus of the Hierarchy view.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="focus_on_type_action">
-        <description>This command allows you to choose any type and opens it in the Hierarchy view.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="typehierarchy_history_action">
-        <description>Allows you to switch back to previously shown type hierarchies.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="filter_public_action">
-        <description>This filter removes all non-public members from the presentation.</description>
-        <topic label="Showing and hiding members in Java views" href="concepts/concept-java-views-filtering.htm"/>
-    </context>
-
-    <context id="filter_fields_action">
-        <description>This filter removes all fields from the presentation.</description>
-        <topic label="Showing and hiding members in Java views" href="concepts/concept-java-views-filtering.htm"/>
-    </context>
-
-    <context id="filter_static_action">
-        <description>This filter removes all static members from the presentation.</description>
-        <topic label="Showing and hiding members in Java views" href="concepts/concept-java-views-filtering.htm"/>
-    </context>
-
-    <context id="show_inherited_action">
-        <description>This option will display all members inherited from the super types.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="show_supertypes_action">
-        <description>This option will display all super types. </description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="show_subtypes_action">
-        <description>This option will display all subtypes.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="show_hierarchy_action">
-        <description>This option displays the class hierachy.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="enable_methodfilter_action">
-        <description>This option displays all types in the current hierarchy that define or implement the selected method.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="open_class_wizard_action">
-        <description>This action opens a wizard for creating a new class.</description>
-        <topic label="New Class wizard reference" href="reference/ref-wizard-class.htm"/>
-    </context>
-
-    <context id="open_enum_wizard_action">
-        <description>This action opens a wizard for creating a new enum.</description>
-        <topic label="New Enum wizard reference" href="reference/ref-wizard-enum.htm"/>
-    </context>
-
-    <context id="open_interface_wizard_action">
-        <description>This action opens a wizard for creating a new interface.</description>
-        <topic label="New Interface wizard reference" href="reference/ref-wizard-interface.htm"/>
-    </context>
-
-    <context id="open_annotation_wizard_action">
-        <description>This action opens a wizard for creating a new annotation.</description>
-        <topic label="New Annotation wizard reference" href="reference/ref-wizard-annotation.htm"/>
-    </context>
-
-    <context id="open_package_wizard_action">
-        <description>This action opens a wizard for creating a new package.</description>
-        <topic label="New Package wizard reference" href="reference/ref-wizard-package.htm"/>
-    </context>
-
-    <context id="open_project_wizard_action">
-        <description>This action opens a wizard for creating a new Java project.</description>
-        <topic label="New Java Project wizard reference" href="reference/ref-wizard-java-project.htm"/>
-        <topic label="Java projects" href="concepts/concept-java-project.htm"/>
-    </context>
-
-    <context id="open_snippet_wizard_action">
-        <description>This action opens a wizard for creating a new Java scrapbook page.</description>
-        <topic label="Creating a Java Scrapbook Page" href="tasks/task-create_scrapbook_page.htm"/>
-        <topic label="New Scrapbook wizard reference" href="reference/ref-wizard-scrapbook.htm"/>
-        <topic label="Scrapbook" href="concepts/cscrapbook.htm"/>
-    </context>
-
-    <context id="clear_working_set_action">
-        <description>This action removes the currently installed working set filter.</description>
-        <topic label="Package Explorer view" href="reference/views/ref-view-package-explorer.htm"/>
-    </context>
-
-    <context id="goto_marker_action">
-        <description>This action shows the search result in a Java editor.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Java search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="java_search_action_context">
-        <description>This command opens the Java search page in the search dialog.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Java search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="goto_package_action">
-        <description>This action allows you to choose any package and selects it in the Package Explorer.</description>
-        <topic label="Showing an element in the Package Explorer" href="tasks/tasks-74.htm"/>
-        <topic label="Package Explorer view" href="reference/views/ref-view-package-explorer.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="history_list_action">
-        <description>Choose and switch back to a previously shown type hierarchy.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="lexical_sorting_outline_action">
-        <description>Displays the elements in alphabetical order.</description>
-        <topic label="Sorting elements in Java views" href="concepts/concept-java-views-sorting.htm"/>
-    </context>
-
-    <context id="lexical_sorting_browsing_action">
-        <description>Displays the elements in aphabetical order.</description>
-        <topic label="Sorting elements in Java views" href="concepts/concept-java-views-sorting.htm"/>
-    </context>
-
-    <context id="open_java_perspective_action">
-        <description>This action opens the Java Perspective.</description>
-        <topic label="Java perspectives" href="concepts/concept-java-perspective.htm"/>
-    </context>
-
-    <context id="open_java_browsing_perspective_action">
-        <description>This action opens the Java Browsing Perspective.</description>
-        <topic label="Java perspectives" href="concepts/concept-java-perspective.htm"/>
-    </context>
-
-    <context id="open_project_action">
-        <description>This action opens a previously closed project.</description>
-        <topic label="Java projects" href="concepts/concept-java-project.htm"/>
-        <topic label="Project actions" href="reference/ref-menu-project.htm"/>
-    </context>
-
-    <context id="open_type_action">
-        <description>Choose a type and open it in a Java editor.</description>
-        <topic label="Opening an editor on a type" href="tasks/tasks-76.htm"/>
-        <topic label="Opening an editor for a selected element" href="tasks/tasks-73.htm"/>
-        <topic label="Open type dialog" href="reference/ref-dialog-open-type.htm"/>
-    </context>
-
-    <context id="open_type_in_hierarchy_action">
-        <description>Choose a type and open it in the Hierarchy view and in a Java editor.</description>
-        <topic label="Open type dialog" href="reference/ref-dialog-open-type.htm"/>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="add_javadoc_stub_action">
-        <description>This action generates a Javadoc skeleton for the selected member. The skeleton contains all the information that can be derived from the member&apos;s signature.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_task_action">
-        <description>Adds a new task.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="externalize_strings_action">
-        <description>Finds and supports externalizing of all strings that are not externalized.</description>
-        <topic label="Finding strings to externalize" href="tasks/tasks-188.htm"/>
-        <topic label="String externalization" href="concepts/concept-string-externalization.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="extract_method_action">
-        <description>Support for extracting a method from a code selection.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="extract_temp_action">
-        <description>Support for extracting a temporary variable from a code selection.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="find_declarations_in_workspace_action">
-        <description>Searches for all declarations of a selected element.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_declarations_in_project_action">
-        <description>Searches for all declarations of a selected element in the project enclosing the element.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_declarations_in_hierarchy_action">
-        <description>Searches for all declarations of a selected element in the element&apos;s type hierarchy.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_declarations_in_working_set_action">
-        <description>Searches for all declarations of a selected element in a specified working set.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_workspace_action">
-        <description>Searches for all references to a selected element.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_project_action">
-        <description>Searches for all references to a selected element in the project enclosing the element..</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_hierarchy_action">
-        <description>Searches for all references to a selected element in the element&apos;s type hierarchy.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_references_in_working_set_action">
-        <description>Searches for all references to a selected element in a specified working set.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_implementors_in_workspace_action">
-        <description>Searches for all implementors of a selected element.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-     <context id="find_implementors_in_project_action">
-        <description>Searches for all implementors of a selected element in the project enclosing the element.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
- 
-    <context id="find_implementors_in_working_set_action">
-        <description>Searches for all implementors of a selected element in a specified working set.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_action">
-        <description>Searches for all locations where the selected field is read.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_workspace_action">
-        <description>Searches for all locations where the selected field is read.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_project_action">
-        <description>Searches in the project enclosing the selected field for all locations where the selected field is read.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_hierarchy_action">
-        <description>Searches in the type hierarchy for all locations where the selected field is read.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_hierarchy_action">
-        <description>Searches in the type hierarchy for all locations where the selected field is modified.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_read_references_in_working_set_action">
-        <description>Searches in a working set for all locations where the selected field is read.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_working_set_action">
-        <description>Searches in a working set for all locations where the selected field is modified.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_workspace_action">
-        <description>Searches for all locations where the selected field is modified.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_in_project_action">
-        <description>Searches in the project enclosing the selected field for all locations where the selected field is modified.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_write_references_action">
-        <description>Searches for all locations where the selected field is modified.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_occurrences_in_file_action">
-        <description>Searches for all locations of the selected element in its file.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="working_set_find_action">
-        <description>Searches for a selected Java element in a working set.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="find_strings_to_externalize_action">
-        <description>Searches for all strings that are not externalized.</description>
-        <topic label="String externalization" href="concepts/concept-string-externalization.htm"/>
-        <topic label="Finding strings to externalize" href="tasks/tasks-188.htm"/>
-        <topic label="Externalize Strings wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-    </context>
-
-    <context id="inline_temp_action">
-        <description>This action removes a local variable and replaces all occurrences with its computing expression.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="modify_parameters_action">
-        <description>Supports changing the signature of a method.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="open_action">
-        <description>Opens the selected element in a Java editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="open_external_javadoc_action">
-        <description>Opens the selected element&apos;s Javadoc in the default external HTML browser.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-        <topic label="Javadoc location" href="reference/ref-dialog-javadoc-location.htm"/>
-    </context>
-
-    <context id="open_super_implementation_action">
-        <description>This action opens the method in the super class that is overridden by the selected method.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="pull_up_action">
-        <description>Supports moving members up in the type hierarchy.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="refresh_action">
-        <description>Refreshes the contents from the local file system.</description>
-        <topic label="File actions" href="reference/ref-menu-file.htm"/>
-    </context>
-
-    <context id="rename_action">
-        <description>Renames a Java element.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="self_encapsulate_action">
-        <description>Modifies code by replacing a field&apos;s read and write accesses with corresponding calls to getter and setter methods.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="show_in_navigator_action">
-        <description>Shows the selected element in the Navigator view.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="surround_with_try_catch_action">
-        <description>Wraps the code selection into a try/catch block. Handles all exceptions that would cause a compilation error.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="open_resource_action">
-        <description>Opens the selected element in a Java editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="select_working_set_action">
-        <description>This filter removes all elements from the view that are not part of the working set.</description>
-        <topic label="Package Explorer view" href="reference/views/ref-view-package-explorer.htm"/>
-    </context>
-
-    <context id="structured_selection_history_action">
-        <description>Restores the last structured selection.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="structured_select_enclosing_action">
-        <description>Extends the selection according to the Java grammar, to the enclosing syntactic container.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="structured_select_next_action">
-        <description>Extends the selection according to the Java grammar, to include the next neighboring syntactic element.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="structured_select_previous_action">
-        <description>Extends the selection according to the Java grammar, to include the previous neighboring syntactic element.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="toggle_orientations_action">
-        <description>Changes the orientation of the panes of the Hierarchy view.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="cut_action">
-        <description>Deletes the selected elements and copies them onto the clipboard.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="copy_action">
-        <description>Copies the selected element into the clipboard.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="paste_action">
-        <description>Pastes the elements currently on the clipboard at the insertion point.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="delete_action">
-        <description>Deletes the selected elements.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="open_type_hierarchy_action">
-        <description>Opens the Hierarchy view for the selected element.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-    
-    <context id="collapse_all_action">
-        <description>Collapses all elements.</description>
-    </context>
-    
-    <context id="find_break_continue_target_occurrences">
-        <description>Finds the target of a break or continue statement.</description>
-    </context>
-    
-    <context id="find_return_target_occurrences">
-        <description>Finds all method exits for the given method.</description>
-    </context>
-    
-    <!-- Dialogs -->
-    <context id="maintype_selection_dialog_context">
-        <description>Choose a type from all types defining a main method.</description>
-        <topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-        <topic label="Defining the JAR file&apos;s manifest" href="tasks/tasks-35.htm"/>
-    </context>
-
-    <context id="type_selection_dialog2_context">
-        <description>This dialog allows you to choose a type.</description>
-        <topic label="Type Selection Dialog" href="reference/ref-dialog-type-selection.htm"/>
-    </context>
-    
-    <context id="open_type_dialog_context">
-        <description>This dialog allows you to choose a type from the workspace.</description>
-        <topic label="Open Type Dialog" href="reference/ref-dialog-open-type.htm"/>
-        <topic label="Opening on a Type" href="tasks/tasks-76.htm"/>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-        <topic label="Java Actions" href="reference/ref-actions-toolbar.htm"/>
-    </context>
-
-    <context id="access_rules_dialog_context">
-        <description>This dialog allows you to confugre access rules.</description>
-        <topic label="Access Rules" href="concepts/concept-access-rules.htm"/>
-    </context>
-    
-    <context id="edit_jre_dialog_context">
-        <description>Edit an existing JRE definition.</description>
-        <topic label="Choosing a JRE for Launching a Project" href="tasks/task-choose_config_jre.htm"/>
-        <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-        <topic label="Building" href="concepts/concept-java-builder.htm"/>
-        <topic label="JRE Installations Preferences" href="reference/preferences/java/debug/ref-installed_jres.htm"/>
-    </context>
-
-    <context id="source_attachment_dialog_context">
-        <description>Attach source code to the selected JAR file.</description>
-        <topic label="JRE Installations Preferences" href="reference/preferences/java/debug/ref-installed_jres.htm"/>
-    </context>
-
-    <context id="variable_selection_dialog_context">
-        <description>Select a classpath variable to be added to the build class path.</description>
-        <topic label="Classpath Variables Preferences" href="reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm"/>
-        <topic label="Classpath Variables Concepts" href="concepts/concept-classpath-variables.htm"/>
-    </context>
-
-    <context id="variable_creation_dialog_context">
-        <description>Define a new classpath variable.</description>
-        <topic label="Classpath Variables Preferences" href="reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm"/>
-        <topic label="Classpath Variables Concepts" href="concepts/concept-classpath-variables.htm"/>
-    </context>
-
-    <context id="advanced_dialog_context">
-        <description>A dialog for adding the listed entries to the class path.</description>
-        <topic label="Build classpath" href="concepts/concept-build-classpath.htm"/>
-    </context>
-
-    <context id="confirm_save_modified_resources_dialog_context">
-        <description>Confirm that you want to save the modified resource.</description>
-    </context>
-
-    <context id="new_variable_dialog_context">
-        <description>A dialog for adding class path variables to the class path.</description>
-        <topic label="Classpath Variables Preferences" href="reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm"/>
-        <topic label="Classpath Variables Concepts" href="concepts/concept-classpath-variables.htm"/>
-    </context>
-
-    <context id="nonnls_dialog_context">
-        <description>Lists all locations of strings that are not externalized.</description>
-        <topic label="String externalization" href="concepts/concept-string-externalization.htm"/>
-        <topic label="Finding strings to externalize" href="tasks/tasks-188.htm"/>
-        <topic label="Externalize Strings Wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-        <topic label="Externalize Strings Concepts" href="concepts/concept-string-externalization.htm"/>
-    </context>
-
-    <context id="multi_main_type_selection_dialog_context">
-        <description>Lists all classes with a main method.</description>
-        <topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"/>
-        <topic label="Defining the JAR file&apos;s manifest" href="tasks/tasks-35.htm"/>
-    </context>
-
-    <context id="multi_type_selection_dialog_context">
-        <description>A dialog for selecting one or more types from a list of types.</description>
-        <topic label="Opening a type in the Package Explorer view" href="tasks/tasks-75.htm"/>
-        <topic label="Opening an editor on a type" href="tasks/tasks-76.htm"/>
-    </context>
-
-    <context id="super_interface_selection_dialog_context">
-        <description>A dialog for selecting a super interface from a displayed list.</description>
-        <topic label="Type Selection Dialog" href="reference/ref-dialog-type-selection.htm"/>
-        <topic label="New Java Class Wizard" href="reference/ref-wizard-class.htm"/>
-        <topic label="New Java Interface Wizard" href="reference/ref-wizard-interface.htm"/>
-    </context>
-
-    <context id="override_tree_selection_dialog_context">
-        <description>A dialog where you can mark all methods that should be overridden.</description>
-        <topic label="Override Methods" href="reference/ref-dialog-override-method.htm"/>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_getter_setter_selection_dialog_context">
-        <description>A dialog where you can choose the getters and setters that should be generated for existing fields.</description>
-        <topic label="Create Getters and Setters" href="reference/ref-dialog-gettersetter.htm"/>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_delegate_methods_selection_dialog_context">
-        <description>A dialog where you can choose the delegates that should be generated for existing fields.</description>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="hash_code_equals_tree_selection_dialog_context">
-        <description>A dialog where you can choose the fields to include in the generated hashCode() and equals() methods.</description>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-    
-    <context id="to_string_tree_selection_dialog_context">
-		<description>A dialog where you can choose the fields to include in the generated toString() method.</description>
-		<topic label="Generate toString() dialog description" href="reference/ref-dialog-tostring.htm"/>
-		<topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-		<topic label="toString() Generator: Format Templates" href="reference/ref-tostring-templates.htm"/>
- 		<topic label="toString() Generator: Code Styles" href="reference/ref-tostring-styles.htm"/>
-		<topic label="toString() Generator: Content Listing" href="reference/ref-tostring-listcontent.htm"/>
-    </context>
-    <context id="to_string_manage_templates_dialog_context">
-		<description>This dialog allows you to manage your toString() templates.</description>
-		<topic label="toString() Generator: Format Templates" href="reference/ref-tostring-templates.htm"/>
-		<topic label="Generate toString() dialog description" href="reference/ref-dialog-tostring.htm"/>
- 		<topic label="toString() Generator: Code Styles" href="reference/ref-tostring-styles.htm"/>
-		<topic label="toString() Generator: Content Listing" href="reference/ref-tostring-listcontent.htm"/>
-    </context>
-    <context id="to_string_configure_custom_builder_dialog_context">
-		<description>This dialog lets you configure a custom toString() builder.</description>
- 		<topic label="toString() Generator: Code Styles" href="reference/ref-tostring-styles.htm"/>
-		<topic label="toString() Generator: Content Listing" href="reference/ref-tostring-listcontent.htm"/>
-		<topic label="toString() Generator: Format Templates" href="reference/ref-tostring-templates.htm"/>
-		<topic label="Generate toString() dialog description" href="reference/ref-dialog-tostring.htm"/>
-    </context>
-
-    <context id="generate_constructor_using_fields_selection_dialog_context">
-        <description>A dialog where you can choose the fields to initialize in the generated constructor.</description>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_unimplemented_constructors_dialog_context">
-        <description>A dialog where you can choose the superclass constructors that should be implemented.</description>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="move_destination_dialog_context">
-        <description>A dialog for selecting the move destination of an element.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-    </context>
-
-    <context id="choose_variable_dialog_context">
-        <description>A dialog for selecting template variables from a displayed list.</description>
-        <topic label="Templates" href="concepts/concept-editor-templates.htm"/>
-        <topic label="Templates Preferences" href="reference/preferences/java/editor/ref-preferences-templates.htm"/>
-        <topic label="Templates Concepts" href="concepts/concept-editor-templates.htm"/>
-    </context>
-
-    <context id="edit_template_dialog_context">
-        <description>A dialog for editing a template.</description>
-        <topic label="Template Variables" href="concepts/concept-template-variables.htm"/>
-        <topic label="Edit Template Dialog" href="reference/preferences/java/editor/ref-preferences-edit-template-dialog.htm"/>
-    </context>
-
-    <context id="history_list_dialog_context">
-        <description>A dialog for re-opening previously opened type hierarchies.</description>
-        <topic label="Type Hierarchy View" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="import_organize_input_dialog_context">
-        <description>A dialog for adding a new package to the Organize Imports preferences page.</description>
-        <topic label="Organize Imports Preferences" href="reference/preferences/java/codestyle/ref-preferences-organize-imports.htm"/>
-        <topic label="Source Actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="javadoc_property_dialog_context">
-        <description>A dialog where you can specify the Javadoc location for a selected jar file.</description>
-        <topic label="Javadoc Location Properties" href="reference/ref-dialog-javadoc-location.htm"/>
-        <topic label="Javadoc Generation" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-    <context id="new_container_dialog_context">
-        <description>A dialog where you can specify a new source folder.</description>
-        <topic label="Build classpath" href="concepts/concept-build-classpath.htm"/>
-    </context>
-
-    <context id="nls_search_page_context">
-        <description>A dialog where you can select options for searching the specifics of string externalizations.</description>
-        <topic label="String externalization" href="concepts/concept-string-externalization.htm"/>
-        <topic label="Finding unused and incorrectly used keys in property files" href="tasks/tasks-202.htm"/>
-    </context>
-
-    <context id="java_editor_context">
-        <description>The Java editor provides you with Java specific text editing support.</description>
-        <topic label="Java editor concepts" href="concepts/concept-java-editor.htm"/>
-        <topic label="Java editor reference" href="reference/views/ref-java-editor.htm"/>
-        <topic label="Opening a Java editor" href="gettingStarted/qs-OpenJavaEditor.htm"/>
-        <topic label="Using content assist" href="gettingStarted/qs-ContentAssist.htm"/>
-        <topic label="Identifying problems in your code" href="gettingStarted/qs-7.htm"/>
-        <topic label="Using code templates" href="gettingStarted/qs-EditorTemplates.htm"/>
-        <topic label="Organizing import statements" href="gettingStarted/qs-OrganizeImports.htm"/>
-        <topic label="Java editor preferences" href="reference/preferences/java/ref-preferences-editor.htm"/>
-        <topic label="Quick Fixes" href="reference/ref-java-editor-quickfix.htm"/>
-        <topic label="Quick Assists" href="reference/ref-java-editor-quickassist.htm"/>
-        <topic label="Configuring accessibility options for textual editors" href="PLUGINS_ROOT/org.eclipse.platform.doc.user/concepts/accessibility/text_editor.htm"/>
-    </context>
-    
-    <context id="java_editor_breadcrumb_context">
-        <description>The Java editor breadcrumb shows the element at the current cursor position and all its parent elements.</description>
-        <topic label="Java breadcrumb" href="reference/ref-java-editor-breadcrumb.htm"/>
-        <topic label="Java editor concepts" href="concepts/concept-java-editor.htm"/>
-        <topic label="Java editor reference" href="reference/views/ref-java-editor.htm"/>
-        <topic label="Opening a Java editor" href="gettingStarted/qs-OpenJavaEditor.htm"/>
-    </context>
-
-    <context id="compare_dialog_context">
-        <description>A dialog displaying the results of comparing Java elements.</description>
-    </context>
-
-    <context id="add_element_from_history_dialog_context">
-        <description>A dialog that lets you restore deleted Java elements from the local history.</description>
-        <topic label="Restoring a deleted workbench element" href="tasks/tasks-64.htm"/>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="compare_element_with_history_dialog_context">
-        <description>A dialog that lets you compare a Java element with entries from the local history.</description>
-        <topic label="Comparing a Java element with a local history edition" href="tasks/tasks-63a.htm"/>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="replace_element_with_history_dialog_context">
-        <description>A dialog that lets you replace Java elements with entries from the local history.</description>
-        <topic label="Replacing a Java element with a local history edition" href="tasks/tasks-63.htm"/>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="sort_members_dialog_context">
-        <description>A dialog that lets you sort members.</description>
-        <topic label="Sorting elements in Java views" href="concepts/concept-java-views-sorting.htm"/>
-    </context>
-
-    <!-- View parts -->
-
-    <context id="package_view_context" title="About Package Explorer">
-        <description>This view displays the workspace&apos;s Java projects and lets you explore their contents.</description>
-        <topic label="Browsing Java elements" href="gettingStarted/qs-4.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-        <topic label="Package explorer view" href="reference/views/ref-view-package-explorer.htm"/>
-        <topic label="Java element filters dialog" href="reference/ref-dialog-java-element-filters.htm"/>
-    </context>
-    
-    <context id="type_hierarchy_view_context" title="About Hierarchy view">
-        <description>This view displays a type&apos;s hierarchy.</description>
-        <topic label="Viewing the Type Hierarchy" href="gettingStarted/qs-6.htm"/>
-        <topic label="Java Views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="projects_view_context" title="About Projects view">
-        <description>Displays all Java projects according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="packages_browsing_view_context" title="About Packages view">
-        <description>Displays all packages of the selected Java project according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="types_view_context" title="About Types view">
-        <description>Displays all types of the selected package according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="members_view_context" title="About Members view">
-        <description>Displays all members of the selected type according to the current filter settings.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-    
-    <context id="call_hierarchy_view_context" title="About Call Hierarchy view">
-        <description>The Call Hierarchy shows all callers or callees of the given method.</description>
-        <topic label="Call Hierarchy view" href="reference/views/ref-call-hierarchy.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-    
-    <context id="javadoc_view_context" title="About Javadoc view">
-        <description>Displays the Javadoc for the selected Java element.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-    
-    <context id="source_view_context" title="About Declarations view">
-        <description>Displays the source for the selected Java element.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-
-
-    <!-- Preference pages -->
-
-    <context id="java_base_preference_page_context">
-        <description>On this page you can indicate your preferences for the general Java tooling settings.</description>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="appearance_preference_page_context">
-        <description>On this page you can indicate your preferences for the appearence of Java views.</description>
-        <topic label="Appearance preferences" href="reference/preferences/java/ref-preferences-appearance.htm"/>
-    </context>
-    
-    <context id="sort_order_preference_page_context">
-        <description>On this page you can indicate your preferences for sorting elements in views.  The same settings are also used by the Sort Members command.</description>
-        <topic label="Members Sort Order preference page" href="reference/preferences/java/appearance/ref-preferences-member-sort-order.htm"/>
-        <topic label="Sorting elements in Java views" href="concepts/concept-java-views-sorting.htm"/>
-    </context>
-
-    <context id="type_filter_preference_page_context">
-        <description>On this page you can indicate your preferences for filtering types from various lists.</description>
-        <topic label="Type Filters preference page" href="reference/preferences/java/appearance/ref-preferences-type-filters.htm"/>
-    </context>
-    
-    <context id="tasktags_preference_page_context">
-        <description>On this page you can create new tags (e.g. TODO, FIXME) for which task markers will be created.</description>
-        <topic label="Task Tags preferences" href="reference/preferences/java/compiler/ref-preferences-task-tags.htm"/>
-        <topic label="Java Compiler Preferences" href="reference/preferences/java/ref-preferences-compiler.htm"/>
-    </context>
-
-    <context id="organizeimports_preference_page_context">
-        <description>On this page you can define the sort order of import statements.</description>
-        <topic label="Organize imports preferences" href="reference/preferences/java/codestyle/ref-preferences-organize-imports.htm"/>
-    </context>
-
-    <context id="refactoring_preference_page_context">
-        <description>On this page you can indicate your preferences when performing a refactoring.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="java_editor_preference_page_context">
-        <description>On this page you can indicate your preferences for using the Java editor.</description>
-        <topic label="Java editor preferences" href="reference/preferences/java/ref-preferences-editor.htm"/>
-        <topic label="Java editor concepts" href="concepts/concept-java-editor.htm"/>
-        <topic label="Java editor reference" href="reference/views/ref-java-editor.htm"/>
-    </context>
-    
-    <context id="spelling_configuration_block_context">
-        <description>On this page you can indicate your spelling preferences.
-
-<b>Hint</b>: If your preferred language is not available as <b>Platform dictionary</b> choose <b>none</b> and then search the internet for a word list with the words of your preferred language and set it as <b>User defined dictionary</b>. 
-</description>
-        <topic label="Preferences - Text Editor" href="PLUGINS_ROOT/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm"/>
-        <topic label="Editors" href="PLUGINS_ROOT/org.eclipse.platform.doc.user/concepts/concepts-6.htm"/>
-    </context>
-    
-    <context id="properties_file_editor_preference_page_context">
-        <description>On this page you can indicate your preferences for using the properties files editor.</description>
-        <topic label="Properties File editor preference page" href="reference/preferences/java/ref-preferences-properties-files-editor.htm"/>
-    </context>
-
-    <context id="build_path_property_page_context">
-        <description>This page is where you can define the project&apos;s build path.</description>
-        <topic label="Building" href="concepts/concept-java-builder.htm"/>
-        <topic label="Java Settings Page" href="reference/ref-properties-build-path.htm"/>
-    </context>
-
-    <context id="cp_variables_preference_page_context">
-        <description>This page is where you can create and manage classpath variables for the workbench.</description>
-        <topic label="Classpath Variables Preferences" href="reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm"/>
-        <topic label="Classpath Variables" href="concepts/concept-classpath-variables.htm"/>
-        <topic label="Installed JREs" href="reference/preferences/java/ref-preferences-installed-jres.htm"/>
-    </context>
-
-    <context id="codeformatter_preference_page_context">
-        <description>This page is where you can set preferences for formatting Java code.</description>
-        <topic label="Code Formatter Preferences" href="reference/preferences/java/codestyle/ref-preferences-formatter.htm"/>
-    </context>
-    
-    <context id="clean_up_preference_page_context">
-        <description>This page is where you can set preferences to clean up Java code.</description>
-        <topic label="Clean Up preference page" href="reference/preferences/java/codestyle/ref-preferences-cleanup.htm"/>
-    </context>
-
-    <context id="source_attachment_property_page_context">
-        <description>This page is where you can attach source code to a JAR file.</description>
-        <topic label="Source Attachment Properties" href="reference/ref-properties-source-attachment.htm"/>
-    </context>
-
-    <context id="jre_preference_page_context">
-        <description>This page is where you can add, remove, and edit JREs install definitions.</description>
-        <topic label="JRE Installations Preferences" href="reference/preferences/java/debug/ref-installed_jres.htm"/>
-        <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-        <topic label="Choosing a JRE for Launching a Project" href="tasks/task-choose_config_jre.htm"/>
-        <topic label="Preparing the Workbench" href="gettingStarted/qs-2.htm"/>
-    </context>
-
-    <context id="source_lookup_property_page_context">
-        <description>When debugging the projects specified on this page are used to look up a type&apos;s source.</description>
-    </context>
-
-    <context id="launch_jre_property_page_context">
-        <description>Select the JRE to be used when launching from this project. This option should only be used when this project&apos;s JRE is different from the default JRE selected in the preferences.</description>
-        <topic label="Choosing a JRE for Launching a Project" href="tasks/task-choose_config_jre.htm"/>
-        <topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-        <topic label="JRE Installations Preferences" href="reference/preferences/java/debug/ref-installed_jres.htm"/>
-    </context>
-
-    <context id="code_manipulation_preference_context">
-        <description>Specify the code styles used for code generation, content assist, and refactorings.</description>
-        <topic label="Code Style Preferences" href="reference/preferences/java/ref-preferences-code-style.htm"/>
-        <topic label="Code Template Preferences" href="reference/preferences/java/codestyle/ref-preferences-code-templates.htm"/>
-    </context>
-    
-    <context id="code_templates_preference_context">
-        <description>Specify the code templates used for code generation.</description>
-        <topic label="Code Template Preferences" href="reference/preferences/java/codestyle/ref-preferences-code-templates.htm"/>
-    </context>
-
-    <context id="compiler_preference_page_context">
-        <description>Specify the behavior of the JDT Java compiler.</description>
-        <topic label="Java Compiler Preferences" href="reference/preferences/java/ref-preferences-compiler.htm"/>
-        <topic label="Building Preferences" href="reference/preferences/java/compiler/ref-preferences-building.htm"/>        
-        <topic label="Errors/Warnings Preferences" href="reference/preferences/java/compiler/ref-preferences-errors-warnings.htm"/>
-        <topic label="Javadoc Preferences" href="reference/preferences/java/compiler/ref-preferences-javadoc.htm" />
-        <topic label="Task Tags Preferences" href="reference/preferences/java/compiler/ref-preferences-task-tags.htm" />
-        <topic label="Java Builder" href="concepts/concept-java-builder.htm"/>
-    </context>
-
-    <context id="template_preference_page_context">
-        <description>Define and manage your code templates.</description>
-        <topic label="Java Templates Preferences" href="reference/preferences/java/editor/ref-preferences-templates.htm"/>
-        <topic label="Templates Concepts" href="concepts/concept-editor-templates.htm"/>
-    </context>
-
-    <context id="new_java_project_preference_page_context">
-        <description>Specify the settings to use when generating new Java projects.</description>
-        <topic label="Java Projects" href="concepts/concept-java-project.htm"/>
-        <topic label="Build Path preference page" href="reference/preferences/java/ref-preferences-build-path.htm"/>
-    </context>
-    
-    <context id="javadoc_configuration_property_page_context">
-        <description>Specify the path for the application for generating Javadoc.</description>
-        <topic label="Export Javadoc Wizard" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-    <context id="java_element_info_page_context">
-        <description>Displays file system information about the selected Java element.</description>
-        
-    </context>
-
-    <context id="java_build_preference_page_context">
-        <description>Specify the behavior of the JDT Java builder on this preference site.</description>
-        <topic label="Building Preferences" href="reference/preferences/java/compiler/ref-preferences-building.htm"/> 
-    </context>
-    
-    <context id="problem_severities_preference_page_context">
-        <description>Specify the severities of the problems detected by the JDT Java compiler on this preference site.</description>
-        <topic label="Errors/Warnings Preferences" href="reference/preferences/java/compiler/ref-preferences-errors-warnings.htm"/> 
-    </context>
-    
-    <context id="javadoc_problems_preference_page_context">
-        <description>Specify the severities of the problems detected by the JDT Java compiler within Javadoc comments on this preference site.</description>
-        <topic label="Javadoc Preferences" href="reference/preferences/java/compiler/ref-preferences-javadoc.htm"/> 
-    </context>
-    
-    <context id="java_build_property_page_context">
-        <description>Specify the behavior of the JDT Java builder on this preference site.</description>
-        <topic label="Building Preferences" href="reference/preferences/java/compiler/ref-preferences-building.htm"/> 
-    </context>
-    
-    <context id="problem_severities_property_page_context">
-        <description>Specify the severities of the problems detected by the JDT Java compiler on this preference site.</description>
-        <topic label="Errors/Warnings Preferences" href="reference/preferences/java/compiler/ref-preferences-errors-warnings.htm"/> 
-    </context>
-    
-    <context id="javadoc_problems_property_page_context">
-        <description>Specify the severities of the problems detected by the JDT Java compiler within Javadoc comments on this preference site.</description>
-        <topic label="Javadoc Preferences" href="reference/preferences/java/compiler/ref-preferences-javadoc.htm"/> 
-    </context>
-    
-    
-    <!-- Wizard pages -->
-
-    <context id="new_javaproject_wizard_page_context">
-        <description>This wizard helps you create a new Java project.</description>
-        <topic label="Java projects" href="concepts/concept-java-project.htm"/>
-        <topic label="Creating your first Java project" href="gettingStarted/qs-3.htm"/>
-        <topic label="New Java Project Wizard" href="reference/ref-wizard-java-project.htm"/>
-    </context>
-    <context id="new_snippet_wizard_page_context">
-        <description>This wizard helps you create a new Java scrapbook page.</description>
-        <topic label="Creating a Scrapbook Page" href="tasks/task-create_scrapbook_page.htm"/>
-        <topic label="New Java Scrapbook Page Wizard" href="reference/ref-wizard-scrapbook.htm"/>
-    </context>
-    <context id="new_package_wizard_page_context">
-        <description>This wizard helps you create a new Java package.</description>
-        <topic label="New Java Package Wizard" href="reference/ref-wizard-package.htm"/>
-    </context>
-    <context id="new_class_wizard_page_context">
-        <description>This wizard helps you create a new Java class.</description>
-        <topic label="New Java Class Wizard" href="reference/ref-wizard-class.htm"/>
-    </context>
-    <context id="new_enum_wizard_page_context">
-        <description>This wizard helps you create a new Java enum.</description>
-        <topic label="New Java Enum Wizard" href="reference/ref-wizard-enum.htm"/>
-    </context>
-    <context id="new_interface_wizard_page_context">
-        <description>This wizard helps you create a new Java interface.</description>
-        <topic label="New Java Interface Wizard" href="reference/ref-wizard-interface.htm"/>
-    </context>
-    <context id="new_annotation_wizard_page_context">
-        <description>This wizard helps you create a new Java annotation.</description>
-        <topic label="New Java Annotation Wizard" href="reference/ref-wizard-annotation.htm"/>
-    </context>
-
-    <context id="new_packageroot_wizard_page_context">
-        <description>This wizard helps you create a new Java source folder.</description>
-        <topic label="New Source Folder Wizard" href="reference/ref-wizard-source-folder.htm"/>
-    </context>
-    
-    <context id="edit_inclusion_exlusion_filter_wizard_page_context">
-        <description>This wizard helps you to add or remove Inclusion and Exclusion filters to a source folder.</description>
-        <topic label="Inclusion and Exclusion patterns" href="concepts/concept-inclusion-exclusion-patterns.htm"/>
-    </context>
-
-    <context id="java_application_page_context">
-        <description>This wizard displays a list of launchable elements where you can select an element to be launched.</description>
-        <topic label="Running a Java program" href="tasks/task-launching_java_program.htm"/>
-        <topic label="Run and Debug Actions" href="reference/menus/run/ref-menu_run.htm"/>
-    </context>
-
-    <context id="jdi_attach_launcher_page_context">
-        <description>This wizard helps you configure the settings for launching a remote Java application.</description>
-        <topic label="Connecting to a remote VM with the Remote Java application launch configuration" href="tasks/task-remotejava_launch_config.htm"/>
-        <topic label="Run and Debug Actions" href="reference/menus/run/ref-menu_run.htm"/>
-    </context>
-
-    <context id="jar_packager_wizard_page_context">
-        <description>This wizard helps you set packaging options for exporting resources to a JAR file.</description>
-        <topic label="Creating a new JAR file" href="tasks/tasks-33.htm"/>
-        <topic label="Creating JAR files" href="tasks/tasks-32.htm"/>
-        <topic label="Export JAR Wizard" href="reference/ref-export-jar.htm"/>
-    </context>
-
-    <context id="jar_manifest_wizard_page_context">
-        <description>This wizard helps you create or locate the manifest file for the created JAR file.</description>
-        <topic label="Defining the JAR File&apos;s Manifest" href="tasks/tasks-35.htm"/>
-        <topic label="Creating JAR files" href="tasks/tasks-32.htm"/>
-        <topic label="Export JAR Wizard" href="reference/ref-export-jar.htm"/>
-    </context>
-    
-    <context id="jar_import_wizard_page_context">
-        <description>This wizard helps you migrate a JAR to a new version and apply refactorings stored in the JAR.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="jar_packager_refactoring_dialog_context">
-        <description>This dialog helps you choose the refactorings to export.</description>
-    </context>
-
-    <context id="jar_options_wizard_page_context">
-        <description>This wizard helps you configure the settings for managing export problems. It includes the option to save a description of the JAR file in the workbench.</description>
-        <topic label="Setting advanced options" href="tasks/tasks-34.htm"/>
-        <topic label="Creating JAR files" href="tasks/tasks-32.htm"/>
-        <topic label="Export JAR Wizard" href="reference/ref-export-jar.htm"/>
-    </context>
-
-   <context  id="java_working_set_page_context" >
-      <description>Create a new working set by selecting the Java elements that will belong to it.</description>
-   </context>
-
-    <context id="classpath_container_default_page_context">
-        <description>Allows you to edit a container entry of the class path. A container entry has the format &quot;container name/container specific arguments&quot;.</description>
-        <topic label="Build classpath" href="concepts/concept-build-classpath.htm"/>
-        <topic label="Java Build Path Properties" href="reference/ref-properties-build-path.htm"/>
-        <topic label="Classpath Variables Preferences" href="reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm"/>
-    </context>
-    
-    <context id="select_clean_ups_wizard_page_context">
-        <description>This wizard helps you to clean up your code.</description>
-        <topic label="Clean Up preference page" href="reference/preferences/java/codestyle/ref-preferences-cleanup.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-    </context>
-
-    <context id="javadoc_standard_page_context">
-        <description>Allows you to select the options for generating Javadoc using the standard doclet.</description>
-        <topic label="Export Javadoc Wizard" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-    <context id="javadoc_specifics_page_context">
-        <description>Allows you to textually specify further arguments passed to the Javadoc generator.</description>
-        <topic label="Export Javadoc Wizard" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-    <context id="javadoc_tree_page_context">
-        <description>Select the elements for which Javadoc will be created.</description>
-        <topic label="Export Javadoc Wizard" href="reference/ref-export-javadoc.htm"/>
-    </context>
-
-
-    <!-- Refactoring Preview Pages-->
-
-    <context id="refactoring_preview_wizard_page_context">
-        <description>This dialog presents a preview of the impending refactoring changes.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-	<!-- Refactoring Error Wizard Pages -->
-	
-    <context id="refactoring_error_wizard_page_context">
-        <description>Displays errors that occurred while executing the refactoring.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="rename_params_wizard_page">
-        <description>This dialog helps you rename a method parameter. References to the parameter inside the method are updated to refer to the new name.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="extract_method_wizard_page_context">
-        <description>This dialog helps you extract the selected statements into a new method.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="rename_package_wizard_page_context">
-        <description>This dialog helps you rename a Java package. References to the old package name are updated to refer to the new name.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="rename_cu_wizard_page_context">
-        <description>This dialog helps you rename a compilation unit. References to the compilation unit&apos;s public type are updated to refer to the new name.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="rename_method_wizard_page_context">
-        <description>This dialog helps you rename a method.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="rename_type_wizard_page_context">
-        <description>This dialog helps you rename a type.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="rename_field_wizard_page_context">
-        <description>This dialog helps you rename a field.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="externalize_wizard_keyvalue_page_context">
-        <description>Supports you in defining the keys for looking up externalized strings.</description>
-        <topic label="String externalization" href="concepts/concept-string-externalization.htm"/>
-        <topic label="Externalize strings wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="externalize_wizard_properties_file_page_context">
-        <description>Supports you in specifying the properties file used to externalize strings.</description>
-        <topic label="String externalization" href="concepts/concept-string-externalization.htm"/>
-        <topic label="Externalize strings wizard" href="reference/ref-wizard-externalize-strings.htm"/>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="extract_method_temp_page_context">
-        <description>This dialog helps you extract a local variable.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="modify_parameters_wizard_page_context">
-        <description>This dialog helps you modify the signature of a method.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="move_members_wizard_page_context">
-        <description>This dialog helps you move static members from one type to another.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="pull_up_wizard_page_context">
-        <description>This dialog helps you move members up the type hierarchy.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="rename_local_variable_wizard_page_context">
-        <description>This dialog helps you rename a local variable.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="self_encapsulate_field_wizard_page_context">
-        <description>This dialog helps you insert calls to setter and getter methods at all locations where the selected field is set or read.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-    
-    <context id="infer_type_arguments_wizard_page_context">
-        <description>This dialog helps inferring generic type arguments for references to generic types.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="change_type_wizard_page_context">
-        <description>This dialog allows to choose a supertype of the reference's current type. If the reference can be safely changed to the new type, it is.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="extract_supertype_wizard_page_context">
-        <description>This dialog helps extracting a common superclass from a set of sibling types.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="introduce_factory_wizard_page_context">
-        <description>This dialog helps introducing a factory method for a constructor.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="introduce_indirection_wizard_page_context">
-        <description>This dialog helps introducing a static indirection method delegating to the selected method.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="introduce_parameter_page_context">
-        <description>This dialog helps creating a new method parameter from a selected expression.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-    
-    <context id="inline_temp_wizard_page_context">
-        <description>This dialog helps inlining a local variable.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <!-- ltk.ui.refactoring -->
-    
-    <context id="refactoring_accept_page">
-        <description>This dialog helps you accept a refactoring.</description>
-    </context>
-    
-    <context id="refactoring_apply_script_page">
-        <description>This wizard helps you apply a refactoring script to projects in your workspace.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-    
-    <context id="refactoring_create_script_page">
-        <description>This dialog helps you create a script of the refactorings that have been applied in the workspace.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-    
-    <context id="refactoring_history_wizard_page_context">
-        <description>This wizard shows the refactoring history.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-    
-    <context id="refactoring_show_history_page">
-        <description>This dialog allows to browse the workspace refactoring history and and offers the option to delete refactorings from the refactoring history.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-    
-    <context id="refactoring_property_page">
-        <description>This page allows to browse the project's refactoring history and and offers the option to delete refactorings from the refactoring history.</description>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-    
-    <!-- Reused UI Blocks -->
-
-    <context id="build_paths_context">
-        <description>A page for defining the build classpath for the project.</description>
-        <topic label="Build class path" href="concepts/concept-java-builder.htm"/>
-        <topic label="Preparing the workbench" href="gettingStarted/qs-2.htm"/>
-        <topic label="Java build path properties" href="reference/ref-properties-build-path.htm"/>
-        <topic label="Classpath variables preferences" href="reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm"/>
-    </context>
-    <context id="source_attachment_context">
-        <description>Allows you to attach a source code archive to a JAR file.</description>
-        <topic label="Build class path" href="concepts/concept-java-builder.htm"/>
-    </context>
-
-
-    <!-- Search -->
-
-    <context id="java_search_page_context">
-        <description>On this page you can search for references to and declarations of Java elements.</description>
-        <topic label="Java Searching" href="concepts/concept-java-search.htm"/>
-        <topic label="Searching the workbench" href="gettingStarted/qs-11.htm"/>
-        <topic label="Java search tab" href="reference/ref-dialog-java-search.htm"/>
-        <topic label="Search menu" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="java_search_result">
-		<description>This view displays the results of a Java search.</description>
-        <topic label="Java Searching" href="concepts/concept-java-search.htm"/>
-    </context>
-
-    <context id="java_search_result">
-		<description>This view displays the results of a Java search.</description>
-        <topic label="Java Searching" href="concepts/concept-java-search.htm"/>
-    </context>
-
-    <context id="occurrences_search_result">
-		<description>This view displays the results of a 'Find Occurrences' search.</description>
-        <topic label="Java search" href="concepts/concept-java-search.htm"/>
-        <topic label="Search actions" href="reference/ref-menu-search.htm"/>
-    </context>
-
-    <context id="nls_search_result">
-		<description>This view displays the results of a 'Find Broken Externalized Strings' search.</description>
-        <topic label="String externalization" href="concepts/concept-string-externalization.htm"/>
-    </context>
-
-
-    <!-- Custom Filters -->
-
-    <context id="open_custom_filters_dialog_context">
-        <description>On this page you can activate and deactivate filters.</description>
-        <topic label="Filtering elements" href="concepts/concept-java-views.htm"/>
-    </context>
-
-
-    <!-- NEW CONTEXT IDs -->
-
-    <context id="sort_members_action">
-        <description>This command sorts the members in this compilation unit.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="quick_fix_action">
-        <description>This command helps you to correct Java problems.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="format_action">
-        <description>This command formats the selected text.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="add_delegate_methods_action">
-        <description>This command lets you create delegate methods for a set of fields.(Delegate methods are methods that delegate to a method provided by a field.)</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="history_action">
-        <description>This action is used to switch between previously displayed type hierarchies.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="go_into_top_level_type_action">
-        <description>This command modifies the Java outline view to show only the members of the compilation unit's main type.</description>
-    </context>
-
-    <context id="tasktags_property_page_context">
-        <description>This page is where you can define the project-specific task tags.</description>
-    </context>
-
-    <context id="compiler_property_page_context">
-        <description>This page is where you can define the project-specific compiler settings.</description>
-    </context>
-
-    <context id="replace_with_previous_from_history_action">
-        <description>This command lets you replace the selected element with a version from the local history.</description>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="compare_with_history_action">
-        <description>This command lets you compare the selected element with a version from the local history.</description>        
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="add_from_history_action">
-        <description>This command adds elements from the local history.</description>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="replace_with_history_action">
-        <description>This command replaces the selected element with a version from the local history.</description>
-        <topic label="Using the local history" href="tasks/tasks-62.htm"/>
-    </context>
-
-    <context id="comment_action">
-        <description>This command lets you comment out a sequence of lines in Java code.</description>        
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="uncomment_action">
-        <description>This command uncomments a sequence of lines that are commented out.</description>
-        <topic label="Source actions" href="reference/ref-menu-source.htm"/>
-    </context>
-
-    <context id="extract_temp_page_context">
-        <description>This dialog helps you to extract a local variable from a selected expression.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="previous_problem_action">
-        <description>This command navigates to the previous problem in the active editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="addjtoclasspath_action_context">
-        <description>This command adds the selected JAR to the project's classpath.</description>
-        <topic label="Build classpath" href="concepts/concept-build-classpath.htm"/>
-    </context>
-
-    <context id="removefromclasspath_action_context">
-        <description>This command removes an entry from the project's classpath.</description>        
-        <topic label="Build classpath" href="concepts/concept-build-classpath.htm"/>
-    </context>
-
-    <context id="push_down_action">
-        <description>This command opens a dialog that will help you to push down members of a class to the class's subclasses.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="inline_method_wizard_page_context">
-        <description>This dialog helps you to inline a method.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="move_action">
-        <description>This command moves elements.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="next_change_action">
-        <description>This command navigates to the next change.</description>
-    </context>
-
-    <context id="previous_change_action">
-        <description>This command navigates to the previous change.</description>
-    </context>
-
-    <context id="goto_next_member_action">
-        <description>This command moves the caret to the next member.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="goto_previous_member_action">
-        <description>This command moves the caret to the previous member.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="show_qualified_names_action">
-        <description>This command shows the qualified names for types.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="open_structure_action">
-        <description>This command opens the outline of the selected element.</description>
-    </context>
-
-    <context id="inline_action">
-        <description>This command opens a dialog that will help you to inline a method, local variable or constant.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="extract_interface_action">
-        <description>This command opens a dialog that will help you to extract an interface from the selected type.  You can optionally change references to the selected type into references to the new interface.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="promote_temp_to_field_page_context">
-        <description>This dialog helps you convert a local variable to a field.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="move_inner_to_top_level_action">
-        <description>This command opens a dialog that will help you to convert a nested type to a top level type.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="use_supertype_wizard_page_context">
-        <description>This dialog helps you to replace references to a type with references to one of the type's supertypes.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="parameter_hints_action">
-        <description>This command shows hints for method call parameters.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="convert_anonymous_to_nested_action">
-        <description>This command opens a dialog that will help you to convert an anonymous inner class to a nested class.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="goto_resource_dialog">
-        <description>This dialog helps you to find and navigate to a workspace resource.</description>
-    </context>
-
-    <context id="extract_constant_page_context">
-        <description>This dialog helps you to extract a selected expression to a constant.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="extract_constant_action">
-        <description>This command opens a dialog that will help you to extract a constant from the selected expression.  You can optionally replace all matching expressions with references to the new constant.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="link_editor_action">
-        <description>This command links the view with an editor.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="use_supertype_action">
-        <description>This command opens a dialog that will help you to replace references to a type with references to one of the type's supertypes.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="inline_constant_wizard_page_context">
-        <description>This dialog helps you to inline a constant.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="goto_matching_bracket_action">
-        <description>This command moves the caret to the matching bracket.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="goto_type_action">
-        <description>This command finds a selected type in the workspace and opens its code in the editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="java_select_marker_ruler_action">
-        <description>This command activates Quick Fix.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-
-    <context id="show_outline_action">
-        <description>This command shows an in-place outline of the currently edited file.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="goto_resource_action">
-        <description>This command finds and navigates to a selected resource in the workspace.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="convert_anonymous_to_nested_page_context">
-        <description>This dialog helps you to convert an anonymous inner class to a nested class.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="next_problem_action">
-        <description>This command navigates to the next problem in the Java editor.</description>
-        <topic label="Navigate actions" href="reference/ref-menu-navigate.htm"/>
-    </context>
-
-    <context id="layout_flat_action">
-        <description>This command changes the view to a flat layout.</description>
-        <topic label="Package Explorer view" href="reference/views/ref-view-package-explorer.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="layout_hierarchical_action">
-        <description>This command changes the view to a hierarchical layout.</description>
-        <topic label="Package Explorer view" href="reference/views/ref-view-package-explorer.htm"/>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-
-    <context id="output_location_dialog_context">
-        <description>This dialog helps you to edit the output folder of a project or a source folder.</description>
-        <topic label="Build classpath" href="concepts/concept-build-classpath.htm"/>
-        <topic label="Java Settings Page" href="reference/ref-properties-build-path.htm"/>
-    </context>
-
-    <context id="sort_by_defining_type_action">
-        <description>This command sorts the members by their declaring type.</description>
-        <topic label="Type Hierarchy view" href="reference/views/ref-type-hierarchy.htm"/>
-    </context>
-
-    <context id="edit_working_set_action">
-        <description>This command lets you edit a working set.</description>
-    </context>
-
-    <context id="move_inner_to_top_wizard_page_context">
-        <description>This dialog helps you to convert a nested type to a top level type.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="push_down_wizard_page_context">
-        <description>This dialog helps you to push down class members to their subclasses.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="promote_temp_to_field_action">
-        <description>This command opens a dialog that will help you to convert a local variable to a field.</description>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-    </context>
-
-    <context id="exclusion_pattern_dialog_context">
-        <description>This dialog excludes selected source files within a source folder from being compiled.</description>
-        <topic label="Build classpath" href="concepts/concept-build-classpath.htm"/>
-        <topic label="Java Settings Page" href="reference/ref-properties-build-path.htm"/>
-    </context>
-
-    <context id="extract_interface_temp_page_context">
-        <description>This dialog helps you to extract an interface from a type.  You can optionally change references to the type into references to the new interface.</description>
-        <topic label="Refactoring dialogs" href="reference/ref-wizard-refactorings.htm"/>
-        <topic label="Refactoring support" href="concepts/concept-refactoring.htm"/>
-        <topic label="Refactor actions" href="reference/ref-menu-refactor.htm"/>
-        <topic label="Java preferences" href="reference/preferences/ref-preferences-java.htm"/>
-    </context>
-
-    <context id="select_all_action">
-        <description>This command selects all elements in the active view.</description>
-        <topic label="Java views" href="concepts/concept-java-views.htm"/>
-    </context>
-    
-    <context id="generate_javadoc_action">
-        <description>This command generates Javadoc for a project.</description>
-        <topic label="Javadoc Location Properties" href="reference/ref-dialog-javadoc-location.htm"/>
-        <topic label="Creating Javadoc documentation" href="reference/ref-export-javadoc.htm"/>
-    </context>
-    
-    <context id="cp_userlibraries_preference_page_context">
-        <description>User libraries can be added to a Java Build path and bundle a number of external archives. System libraries will be added to the boot class path when launched.</description>
-        <topic label="User Libraries preference page" href="reference/preferences/java/buildpath/ref-preferences-user-libraries.htm"/>
-    </context>
-    
-    <context id="cp_edit_user_library">
-        <description>Select a name for the user library.</description>
-    </context>
-    
-    <context id="cp_export_user_library">
-        <description>Select the libraries to export and a location to export the libraries to.</description>
-    </context>
-    
-    <context id="cp_import_user_library">
-        <description>Select the libraries to import by clicking on 'Browse...'</description>
-    </context>
-    
-    <context id="code_style_edit_prefix_suffix">
-        <description>Specify a prefix and/or a suffix. The prefix and suffix will be used by code assists and refactorings.</description>
-    </context>
-    
-    <context id="todo_task_input_dialog_context">
-        <description>Specify a tag and its corresponding priority.</description>
-    </context>
-    
-    <context id="bp_choose_existing_folder_to_make_source_folder">
-        <description>Choose an existing folder to turn it into a source folder. Source folders can contain java source code.</description>
-    </context>
-    
-    <context id="bp_select_default_output_folder_dialog">
-        <description>This dialog allows to select an existing folder as default output folder or to create new folder when selecting 'Create New Folder...'</description>
-    </context>
-    
-    <context id="bp_select_classpath_container">
-        <description>Select the type of library to add to the build path and select 'Next' to configure the library.</description>
-    </context>
-    <context id="configure_working_set_dialog_context">
-       <description>This dialog helps you to configure the contents and the order of the working sets as seen in the Package Explorer.</description>
-       <topic href="reference/ref-dialog-configure-working-sets.htm" label="Configure Working Sets dialog description"/>
-    </context>
-    <context id="configure_working_sets_action_context">
-       <description>This action helps you to configure the contents and the order of the working sets as seen in the Package Explorer using the Configure Working Sets dialog.</description>
-       <topic href="reference/ref-dialog-configure-working-sets.htm" label="Configure Working Sets dialog description"/>
-    </context>
-    <context id="working_set_assignments_dialog_context">
-       <description>This dialog helps you assign one or more working sets to each of the selected resources.</description>
-       <topic href="reference/ref-dialog-working-set-assignments.htm" label="Working Set Assignments dialog description"/>
-    </context>
-    <context id="assign_working_sets_action_context">
-       <description>This action helps you assign one or more working sets to each of the selected resources using the Working Set Assignments dialog.</description>
-       <topic href="reference/ref-dialog-working-set-assignments.htm" label="Working Set Assignments dialog description"/>
-    </context>
-    <context id="call_hierarchy_filters_dialog_context" title="About Call Hierarchy Filter">
-       <description>This filter helps you specify the patterns,  whose matching type or method names  need to be hidden from the call hierarchy.</description>
-       <topic href="reference/views/ref-call-hierarchy.htm" label="Call Hierarchy View"/>
-    </context>
-    <context id="call_hierarchy_expand_with_constructors_dialog_context">
-       <description>This dialog helps you to specify a list of qualified names of the types that would be expanded with constructors by default.</description>
-       <topic href="reference/views/ref-call-hierarchy.htm" label="Call Hierarchy View"/>
-    </context>
-    <context id="call_hierarchy_expand_with_constructors_action_context">
-       <description>This action can be called on instance methods to show the constructors of its declaring type along with a node that contains the direct callers of the method.</description>
-       <topic href="reference/views/ref-call-hierarchy.htm" label="Call Hierarchy View"/>
-    </context>
-    
-</contexts>

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml b/bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml
deleted file mode 100644
index 9c68ac3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_Debugger.xml
+++ /dev/null

@@ -1,723 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-<!--
-	Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.
-
-	All JDT Debug contexts, those for org.eclipse.jdt.debug.ui, are located in this file
-	All contexts are grouped by their relation, with all relations grouped alphabetically.
--->
-
-<!--
-	Breakpoints View
--->
-	<context  id="breakpoint_suspend_policy_toggle_action_context" >
-		<description>This command toggles a breakpoint's suspend policy between suspending all threads in a VM or only the thread in which the breakpoint was encountered.</description>
-		<topic label="Exception Breakpoint Suspend Policy" href="reference/breakpoints/ref-suspendpolicy_option.htm"/>
-		<topic label="Exception Breakpoint Suspend on Subclass Option" href="reference/breakpoints/ref-suspendsubclass_option.htm"/>
-		<topic label="Suspend Policy Context Action" href="reference/views/breakpoints/ref-suspendpolicy_contextaction.htm" />
-		<topic label="Exception Breakpoint Uncaught Option" href="reference/breakpoints/ref-uncaught_option.htm" />
-		<topic label="Add Java Exception Breakpoint" href="reference/views/breakpoints/ref-addexception_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>				
-	<context  id="hit_count_action_context" >
-		<description>This command opens a dialog to configure a breakpoint's hit count.</description>
-		<topic label="Hit Count Option" href="reference/breakpoints/ref-hitcount_option.htm" />
-		<topic label="Hit Count Context Action" href="reference/views/breakpoints/ref-hitcount_contextaction.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>	
-	<context  id="breakpoint_properties_action_context" >
-		<description>This command opens a dialog to configure a breakpoint's properties.</description>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context  id="exception_caught_toggle_action_context" >
-		<description>When checked, this command configures an exception breakpoint to suspend execution in caught locations.</description>
-		<topic label="Exception Breakpoint Caught Option" href="reference/breakpoints/ref-caught_option.htm" />
-		<topic label="Exception Breakpoint Uncaught Option" href="reference/breakpoints/ref-uncaught_option.htm" />
-		<topic label="Caught Context Action" href="reference/views/breakpoints/ref-caught_contextaction.htm" />
-		<topic label="Uncaught Context Action" href="reference/views/breakpoints/ref-uncaught_contextaction.htm" />
-		<topic label="Exception Breakpoint Suspend on Subclass Option" href="reference/breakpoints/ref-suspendsubclass_option.htm"/>
-		<topic label="Add Java Exception Breakpoint" href="reference/views/breakpoints/ref-addexception_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context  id="exception_uncaught_toggle_action_context" >
-		<description>When checked, this command configures an exception breakpoint to suspend execution in uncaught locations.</description>
-		<topic label="Uncaught" href="reference/views/breakpoints/ref-uncaught_contextaction.htm" />
-		<topic label="Exception Breakpoint Uncaught Option" href="reference/breakpoints/ref-uncaught_option.htm" />
-		<topic label="Exception Breakpoint Caught Option" href="reference/breakpoints/ref-caught_option.htm" />
-		<topic label="Caught Context Action" href="reference/views/breakpoints/ref-caught_contextaction.htm" />
-		<topic label="Exception Breakpoint Suspend on Subclass Option" href="reference/breakpoints/ref-suspendsubclass_option.htm"/>
-		<topic label="Add Java Exception Breakpoint" href="reference/views/breakpoints/ref-addexception_viewaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>	
-	<context  id="entry_toggle_action_context" >
-		<description>When checked, this command configures a method breakpoint to suspend execution when a method is entered.</description>
-		<topic label="Entry" href="reference/views/breakpoints/ref-entry_contextaction.htm" />
-		<topic label="Method Breakpoint Entry Option" href="reference/breakpoints/ref-entry_option.htm" />
-		<topic label="Exit" href="reference/views/breakpoints/ref-exit_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>				
-	<context  id="exit_toggle_action_context" >
-		<description>When checked, this command configures a method breakpoint to suspend execution when a method is exited.</description>
-		<topic label="Exit" href="reference/views/breakpoints/ref-exit_contextaction.htm" />
-		<topic label="Method Breakpoint Exit Option" href="reference/breakpoints/ref-exit_option.htm" />
-		<topic label="Entry" href="reference/views/breakpoints/ref-entry_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>				
-
-<!--
-	Console
--->
-	<context  id="stack_trace_console_context">
-		<description>You can paste, format, and navigate Java stack traces in this console.</description>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-		<topic label="Autoformat Console" href="reference/views/console/ref-autoformat_action.htm"/>
-		<topic label="Copy" href="reference/views/shared/ref-copy.htm"/>
-		<topic label="Cut" href="reference/views/shared/ref-cut.htm"/>
-		<topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-		<topic label="Format" href="reference/views/console/ref-format_action.htm"/>
-		<topic label="Open Link" href="reference/views/console/ref-openlink_action.htm"/>
-		<topic label="Paste" href="reference/views/shared/ref-paste.htm"/>
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-	</context>
-	<context id="console_autoformat_stacktraces_action">
-		<description>This command allows you to quickly toggle the stacktrace auto-format option. When on, all Java stacktraces pasted into the console will automatically be formatted for you.</description>
-		<topic label="Autoformat Console" href="reference/views/console/ref-autoformat_action.htm"/>
-		<topic label="Format" href="reference/views/console/ref-format_action.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-	<context id="format_java_stack_trace_console_action_context">
-		<description>Select this command to format the text in the console as a Java stack trace.  Formatting will fix whitespace problems and add links where possible.</description>
-		<topic label="Format" href="reference/views/console/ref-format_action.htm"/>
-		<topic label="Autoformat Console" href="reference/views/console/ref-autoformat_action.htm"/>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm"/>
-		<topic label="Console View" href="reference/views/console/ref-console_view.htm"/>
-	</context>
-
-<!-- 
-	Context Launch Shortcuts
--->
-	<context  id="shortcut_local_java_application" >
-		<description>This command launches the selected main type as a Java application.</description>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context> 
-	<context  id="shortcut_java_applet" >
-		<description>This command launches the selected applet in an applet viewer.</description>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
-
-<!--
-	Debug View
--->
-	<context  id="show_system_threads_action_context" >
-		<description>This command toggles the display of non-suspended system threads.</description>
-		<topic label="Show System Threads" href="reference/views/debug/ref-showsystemthreads.htm"/>
-		<topic label="Show Monitors" href="reference/views/debug/ref-showmonitors.htm"/>
-		<topic label="Show Qualified Names" href="reference/views/shared/ref-showqualified.htm"/>
-		<topic label="Show Thread Groups" href="reference/views/debug/ref-showthreadgroups.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context id="show_monitors_action_context">
-		<description>This command toggles the display of owned monitors and monitors being waiting on by each suspended thread in the debug view.</description>
-		<topic label="Show Monitors" href="reference/views/debug/ref-showmonitors.htm"/>
-		<topic label="Show Qualified Names" href="reference/views/shared/ref-showqualified.htm"/>
-		<topic label="Show System Threads" href="reference/views/debug/ref-showsystemthreads.htm"/>
-		<topic label="Show Thread Groups" href="reference/views/debug/ref-showthreadgroups.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="show_thread_groups_action_context" >
-		<description>This command toggles the display of thread groups in the debug view.</description>
-		<topic label="Show Thread Groups" href="reference/views/debug/ref-showthreadgroups.htm"/>
-		<topic label="Show Monitors" href="reference/views/debug/ref-showmonitors.htm"/>
-		<topic label="Show Qualified Names" href="reference/views/shared/ref-showqualified.htm"/>
-		<topic label="Show System Threads" href="reference/views/debug/ref-showsystemthreads.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-	<context  id="add_package_step_filter_action_context" >
-		<description>This command creates a step filter for the package associated with the receiver of the selected stack frame.</description>
-		<topic label="Filter Package" href="reference/views/debug/ref-filterpackage.htm"/>
-		<topic label="Edit Step Filters" href="reference/views/debug/ref-editstepfilters.htm"/>
-		<topic label="Filter Type" href="reference/views/debug/ref-filtertype.htm"/>
-		<topic label="Use Step Filters" href="reference/views/debug/ref-usestepfilters.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-		<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-		<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>	
-	<context  id="add_type_step_filter_action_context" >
-		<description>This command creates a step filter for the type associated with the receiver of the selected stack frame.</description>
-		<topic label="Filter Type" href="reference/views/debug/ref-filtertype.htm"/>
-		<topic label="Edit Step Filters" href="reference/views/debug/ref-editstepfilters.htm"/>
-		<topic label="Filter Package" href="reference/views/debug/ref-filterpackage.htm"/>
-		<topic label="Use Step Filters" href="reference/views/debug/ref-usestepfilters.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-		<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-		<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>	
-	<context  id="edit_step_filters_action_context" >
-		<description>This command opens the Java step filters preference page.</description>
-		<topic label="Edit Step Filters" href="reference/views/debug/ref-editstepfilters.htm"/>
-		<topic label="Use Step Filters" href="reference/views/debug/ref-usestepfilters.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-		<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-		<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-		<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-		<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-	</context>
-
-<!-- 
-	Dialogs
--->     
-	<context id="add_exception_dialog_context">
-		<description>This dialog allows you to add an exception breakpoint.</description>
-		<topic label="Add Java Exception Breakpoint" href="reference/views/breakpoints/ref-addexception_viewaction.htm" />
-		<topic label="Exception Breakpoint Suspend Policy" href="reference/breakpoints/ref-suspendpolicy_option.htm"/>
-		<topic label="Exception Breakpoint Suspend on Subclass Option" href="reference/breakpoints/ref-suspendsubclass_option.htm"/>
-		<topic label="Exception Breakpoint Uncaught Option" href="reference/breakpoints/ref-uncaught_option.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-	</context>
-	<context  id="add_new_jre_wizard_page_context" >
-		<description>This wizard allows you to create a new JRE install.  Select the type of JRE you are trying to add and hit next to continue.</description>
-  <topic href="tasks/task-add_new_jre.htm" label="Add New JRE"/>
-  <topic href="tasks/tasks-JREs.htm" label="Working with JREs"/>
-		<topic label="Installed JREs Preference Page" href="reference/preferences/java/debug/ref-installed_jres.htm" />
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-	</context>
- <context id="edit_std_vm_jre_wizard_page_context">
-    <description>This dialog allows you to configure the location, name, and libraries associated with a JRE. Source and javadoc can be configured for each library.</description>
-    <topic href="tasks/task-add_new_jre.htm#StdVM" label="Add New JRE for Standard VM"/>
-    <topic href="tasks/tasks-JREs.htm" label="Working with JREs"/>
-    <topic href="reference/preferences/java/debug/ref-installed_jres.htm" label="Installed JREs Preference Page"/>
-    <topic href="tasks/task-running_and_debugging.htm" label="Running and Debugging"/>
- </context>
- <context id="edit_ee_file_jre_wizard_page_context">
-    <description>This dialog allows you to configure the location, name, and libraries associated with a JRE. Source and javadoc can be configured for each library.</description>
-    <topic href="tasks/task-add_new_jre.htm#EEFile" label="Add New JRE from Execution Environment Description File"/>
-    <topic href="tasks/tasks-JREs.htm" label="Working with JREs"/>
-    <topic href="reference/preferences/java/debug/ref-installed_jres.htm" label="Installed JREs Preference Page"/>
-    <topic href="tasks/task-running_and_debugging.htm" label="Running and Debugging"/>
- </context>
-	<context  id="jre_details_dialog_context" >
-		<description>This dialog allows you to view the read-only properties of a JRE contributed by a plug-in.</description>
-  <topic href="tasks/tasks-JREs.htm" label="Working with JREs"/>
-		<topic label="Installed JREs Preference Page" href="reference/preferences/java/debug/ref-installed_jres.htm" />
-  <topic href="tasks/task-running_and_debugging.htm" label="Running and Debugging"/>
-	</context>
-	<context  id="edit_detail_formatter_dialog_context" >
-		<description>This dialog allows you to configure the detail formatter code snippet associated with a Java class.</description>
-		<topic label="Detail Formatters Preference Page" href="reference/preferences/java/debug/ref-detail_formatters.htm" />
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-	</context>
-	<context  id="edit_logical_structure_dialog_context" >
-		<description>This dialog allows you to configure the logical structure code snippet associated with a Java class.</description>
-		<topic label="Logical Structures Preference Page" href="reference/preferences/java/debug/ref-logical_structures.htm" />
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm" />
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm" />
-	</context>
-	<context  id="snippet_imports_dialog_context" >
-		<description>This dialog allows you to configure the imports associated with a snippet editor.</description>
-	</context>
-	<context id="select_main_method_dialog">
-		<description>This dialog allows you to select a class with the main method you wish to launch.</description>
-		<topic label="Debugger Concepts" href="concepts/cdebugger.htm"/>
-		<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm"/>
-		<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"/>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm"/>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-		<context id="expression_input_dialog">
-		<description>This dialog allows you to change the value of a Java object by creating an expression that will be evaluated to generate the value.</description>
-		<topic label="Change Variable Value Command" href="reference/views/shared/ref-changevarvalue.htm"/>
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context id="string_value_input_dialog">
-		<description>This dialog allows you to change the value of a Java String by entering literal text or by creating an expression that will be eveluated to generate the value.</description>
-		<topic label="Change Variable Value Command" href="reference/views/shared/ref-changevarvalue.htm"/>
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context id="default_input_dialog">
-		<description>This dialog allows you to input a new value for a variable.</description>
-		<topic label="Change Variable Value Command" href="reference/views/shared/ref-changevarvalue.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context id="instance_breakpoint_selection_dialog_context">
-		<description>This dialog allows you to restrict breakpoints to only suspend execution when they are in specific Java object instances.</description>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-	</context>
-	<context id="select_project_dialog">
-		<description>This dialog allows you to select projects to add to the classpath or source lookup path.  In addition, you can choose whether you want exported entries and required projects to also be added.</description>
-	</context>
-
-<!--
-	Display View
--->
-    <context  id="display_view_context" >
-		<description>This view displays the result of expression evaluations. It allows you to select an expression and evaluate it.</description>
-		<topic label="Display View" href="reference/views/display/ref-display_view.htm"/>
-		<topic label="Clear" href="reference/views/display/ref-clear.htm"/>	
-		<topic label="Display Result" href="reference/views/shared/ref-display.htm"/>
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-		<topic label="Execute Selected Statement" href="reference/views/shared/ref-execute.htm"/>
-		<topic label="Inspect" href="reference/views/shared/ref-inspect.htm"/>
-   	</context>
-	<context  id="clear_display_view_action_context" >
-		<description>This command clears the contents of the Display view.</description>
-		<topic label="Clear" href="reference/views/display/ref-clear.htm"/>
-		<topic label="Display View" href="reference/views/display/ref-display_view.htm"/>
-	</context>
-
-<!-- 
-	Launch Configuration Tabs
--->
-	<context  id="launch_configuration_dialog_arguments_tab" >
-		<description>This tab allows you to specify the program and virtual machine arguments for the launch associated with this launch configuration as well as the working directory</description>
-		<topic label="Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Setting execution arguments" href="tasks/tasks-executionArgs.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_classpath_tab" >
-		<description>This tab allows you to specify the classpath for the launch associated with this launch configuration</description>
-		<topic label="Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_connect_tab" >
-		<description>This tab allows you to set specific information for remote debugging</description>
-  <topic href="tasks/tasks-java-local-configuration.htm" label="Java application launch configuration"/>
-		<topic label="Remote debugging" href="concepts/cremdbug.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_jre_tab" >
-		<description>This tab allows you to define the JRE used to run or debug the application</description>
-		<topic label="Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_main_tab" >
-		<description>This tab allows you specify parameters associated with the main type for the launch.</description>
-		<topic label="Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context id="new_snippet_wizard_page_context">
-		<description>This wizard helps you create a new Java scrapbook page.</description>
-		<topic label="Creating a Scrapbook Page" href="tasks/task-create_scrapbook_page.htm"/>
-		<topic label="New Java Scrapbook Page Wizard" href="reference/ref-wizard-scrapbook.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context id="working_directory_context">
-		<description>This component allows you to change the default working directory.</description>
-		<topic label="Java application launch configuration" href=" tasks\tasks-java-local-configuration.htm"/>
-		<topic label="Setting execution arguments" href="tasks/tasks-executionArgs.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_applet_parameters_tab" >
-    	<description>This tab allows you to specify the applet viewer parameters for the launch associated with this launch configuration</description>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_applet_main_tab">
-	    <description>This tab allows you specify parameters associated with the applet for the launch.</description>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-	</context>
-	<context  id="launch_configuration_dialog_applet_arguments_tab">
-	    <description>This tab allows you to specify the program and virtual machine arguments for the launch associated with this launch configuration as well as the working directory</description>
-     	<topic label="Setting execution arguments" href="tasks/tasks-executionArgs.htm"/>
-		<topic label="Launching a Java Program" href="tasks/task-launching_java_program.htm"/>
-    </context>
-	
-<!--
-	Navigate Menu
--->
-	<context  id="open_variable_concrete_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the type of the selected object.</description>
-	</context>	
-	<context  id="open_variable_concrete_type_action_context" >
-		<description>This command opens a Java editor on the type of the selected object.</description>
-	</context>				
-	<context  id="open_variable_declared_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the declared type of the selected variable.</description>
-	</context>
-	<context  id="open_on_variable_type_action_context" >
-		<description>This command opens a Java editor on the declared type of the selected variable.</description>
-	</context>
-	<context  id="open_on_receiving_type_action_context" >
-		<description>This command opens a Java editor on the type of the receiver of the selected stack frame.</description>
-	</context>		
-	<context  id="open_receiving_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the type of the receiver of the selected stack frame.</description>
-	</context>	
-	<context  id="open_on_declaring_type_action_context" >
-		<description>This command opens a Java editor on the type in which the method of the selected stack frame is defined.</description>
-	</context>		
-	<context  id="open_declaring_type_hierarchy_action_context" >
-		<description>This command opens a Type Hierarchy view on the type in which the method of the selected stack frame is defined.</description>
-	</context>
-
-<!-- 
-	Preference/Property Pages 
--->
-	<context  id="java_debug_preference_page_context" >
-		<description>On this page, you can configure Java debugging preferences for suspending execution, hot code replace, and communication timeouts.</description>
-		<topic label="Debug Preferences" href="reference/preferences/java/debug/ref-debug.htm"/>
-		<topic label="Detail Formatters Preferences" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Heap Walking Preferences" href="reference/preferences/java/debug/ref-heap_walking.htm"/>
-		<topic label="Logical Structures Preferences" href="reference/preferences/java/debug/ref-logical_structures.htm"/>
-		<topic label="Primitive Display Options Preferences" href="reference/preferences/java/debug/ref-primitive_display_options.htm"/>
-		<topic label="Step Filtering Preferences" href="reference/preferences/java/debug/ref-step_filtering.htm"/>
-	</context>
-	<context  id="java_detail_formatter_preference_page_context" >
-		<description>On this page, you can define code snippets used to display the details for variables and expressions in the Variables and Expressions view details area.</description>
-		<topic label="Detail Formatters Preferences" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/java/debug/ref-debug.htm"/>
-		<topic label="Heap Walking Preferences" href="reference/preferences/java/debug/ref-heap_walking.htm"/>
-		<topic label="Logical Structures Preferences" href="reference/preferences/java/debug/ref-logical_structures.htm"/>
-		<topic label="Primitive Display Options Preferences" href="reference/preferences/java/debug/ref-primitive_display_options.htm"/>
-		<topic label="Step Filtering Preferences" href="reference/preferences/java/debug/ref-step_filtering.htm"/>
-	</context>
-	<context id="java_heapwalking_preference_page">
-		<description>This page allows you to configure heap walking settings for Java 1.6 SE vms</description>
-		<topic label="Heap Walking Preferences" href="reference/preferences/java/debug/ref-heap_walking.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/java/debug/ref-debug.htm"/>
-		<topic label="Detail Formatters Preferences" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Logical Structures Preferences" href="reference/preferences/java/debug/ref-logical_structures.htm"/>
-		<topic label="Primitive Display Options Preferences" href="reference/preferences/java/debug/ref-primitive_display_options.htm"/>
-		<topic label="Step Filtering Preferences" href="reference/preferences/java/debug/ref-step_filtering.htm"/>
-	</context>
-	<context id="java_logical_structures_page">
-		<description>On this page, you can configure logical structure displays for variables in the Java debugger.</description>
-		<topic label="Logical Structures Preferences" href="reference/preferences/java/debug/ref-logical_structures.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/java/debug/ref-debug.htm"/>
-		<topic label="Detail Formatters Preferences" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Heap Walking Preferences" href="reference/preferences/java/debug/ref-heap_walking.htm"/>
-		<topic label="Primitive Display Options Preferences" href="reference/preferences/java/debug/ref-primitive_display_options.htm"/>
-		<topic label="Step Filtering Preferences" href="reference/preferences/java/debug/ref-step_filtering.htm"/>
-	</context> 
-	<context  id="java_primitives_preference_page_context" >
-		<description>On this page, you can configure display options for primitive variables in the Java debugger.</description>
-		<topic label="Primitive Display Options Preferences" href="reference/preferences/java/debug/ref-primitive_display_options.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/java/debug/ref-debug.htm"/>
-		<topic label="Detail Formatters Preferences" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Heap Walking Preferences" href="reference/preferences/java/debug/ref-heap_walking.htm"/>
-		<topic label="Logical Structures Preferences" href="reference/preferences/java/debug/ref-logical_structures.htm"/>
-		<topic label="Step Filtering Preferences" href="reference/preferences/java/debug/ref-step_filtering.htm"/>
-	</context>
-	<context  id="java_step_filter_preference_page_context" >
-		<description>On this page, you can configure the step filters for the Java debugger.</description>
-		<topic label="Step Filtering Preferences" href="reference/preferences/java/debug/ref-step_filtering.htm"/>
-		<topic label="Debug Preferences" href="reference/preferences/java/debug/ref-debug.htm"/>
-		<topic label="Detail Formatters Preferences" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Heap Walking Preferences" href="reference/preferences/java/debug/ref-heap_walking.htm"/>
-		<topic label="Logical Structures Preferences" href="reference/preferences/java/debug/ref-logical_structures.htm"/>
-		<topic label="Primitive Display Options Preferences" href="reference/preferences/java/debug/ref-primitive_display_options.htm"/>
-	</context>
-	<context  id="jre_preference_page_context" >
-		<description>On this page, you can add, remove, and edit JRE configurations.</description>
-		<topic label="Installed JREs Preferences" href="reference/preferences/java/debug/ref-installed_jres.htm"/>
-		<topic label="Execution Environments Preferences" href="reference/preferences/java/debug/ref-execution_environments.htm"/>
-		<topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-	</context>
-	<context  id="jre_profiles_page_context" >
-		<description>On this page, you can specify a default JRE to use for each JRE profile.</description>
-		<topic label="Execution Environments Preferences" href="reference/preferences/java/debug/ref-execution_environments.htm"/>
-		<topic label="Installed JREs Preferences" href="reference/preferences/java/debug/ref-installed_jres.htm"/>
-		<topic label="Working with JREs" href="tasks/tasks-JREs.htm"/>
-	</context>
-	<context  id="java_breakpoint_preference_page_context" >
-		<description>On this page, you can modify the properties of a Java breakpoint.</description>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>     
-	<context id="vm_capabilities_property_page">
-		<description>This page displays optional debug capabilities of the selected VM.</description>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context id="java_breakpoint_property_page">
-		<description>This page allows you to configure the selected breakpoint.  Enablement restricts when this breakpoint will suspend execution.  Hit count sets the number of times this breakpoint must be reached before suspending execution.</description>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context id="java_breakpoint_advanced_property_page">
-		<description>This page allows you to restrict the breakpoint to only suspend execution in specific threads.</description>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context id="java_exception_breakpoint_property_page">
-		<description>This page allows you to configure an exception breakpoint.  Caught and uncaught options allow you to change the circumstances in which the breakpoint will suspend execution.  You can also change the suspend policy determining what actions to take when an exception occurs.</description>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context id="java_exception_breakpoint_filtering_property_page">
-		<description>This page allows you to select or define breakpoint filters for Java exception breakpoints. A filter can be selected, or you can define an expression using the Add button.</description>
-		<topic label="Add Exception Breakpoint Filters" href="tasks/tasks-create-exception-filter-expression.htm"></topic>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-	<context id="java_line_breakpoint_property_page">
-		<description>This page allows you to configure the selected breakpoint.  Line breakpoints can have enablement conditions, which are snippets of code that must return a boolean value determining when this breakpoint should suspend execution.  Watchpoints can choose to suspend on field access or modification.</description>
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm" />
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-	</context>
-
-<!--
-	Run Menu
--->
-	<context  id="add_exception_action_context" >
-		<description>This command opens a dialog to create a Java exception breakpoint.</description>
-		<topic label="Add Exception Breakpoint" href="reference/view/breakpoints/ref-addexception_viewaction.htm"/>
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context> 	 		
-	<context  id="step_into_selection_action_context" >
-		<description>This command steps into the selected method on the current line of execution. Method selection is determined by the selected text or cursor location in the Java editor.</description>
-		<topic label="Step Into Selection" href="reference/menus/run/ref-step_into_selection.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context> 	
-	<context  id="run_to_line_action_context" >
-		<description>This command resumes execution to the line on which the cursor is located in the Java editor.</description>
-		<topic label="Run To Line" href="reference/menus/run/ref-run_to_line.htm"/>
-		<topic label="Stepping" href="tasks/task-stepping.htm" /> 
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>
-	<context  id="force_return_action_context" >
-		<description>This command forces the selected frame to return the value of the selected code snippet without executing any more instructions in the method.</description>
-		<topic label="Force Return" href="reference/views/shared/ref-forcereturn.htm"/>
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>	
-	<context  id="execute_action_context" >
-		<description>This command executes the selected code snippet.</description>
-		<topic label="Execute" href="reference/views/shared/ref-execute.htm"/>
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>	
-	<context  id="display_action_context" >
-		<description>This command executes the selected code snippet and displays a textual result.</description>
-		<topic label="Display" href="reference/views/shared/ref-display.htm"/>
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>		
-	<context  id="inspect_action_context" >
-		<description>This command executes the selected code snippet and shows the resulting object or primitive in the Expressions view.</description>
-		<topic label="Inspect" href="reference/views/shared/ref-inspect.htm"/>
-		<topic label="Evaluating Expressions" href="tasks/task-evaluating_expressions.htm"/>
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>	
-	<context  id="watch_action_context" >
-		<description>This command creates a watch item for the selected text or variable, and places it in the Expressions view.</description>
-		<topic label="Watch" href="reference/menus/run/ref-addwatch.htm" />
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>
-	<context  id="add_class_prepare_action_context" >
-		<description>This command allows you to add a class load breakpoint to a selected type.</description>
-		<topic label="Add Class Load Breakpoint" href="reference/menus/run/ref-add_class_load_breakpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-	</context>	
-
-<!--
-	Outline View contributions
--->
-
-	<context  id="manage_watchpoint_action_context" >
-		<description>This command adds or removes a watchpoint on the selected field.</description>
-		<topic label="Toggle Watchpoint" href="reference/menus/run/ref-toggle_watchpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-	</context>  
-	<context  id="manage_method_breakpoint_action_context" >
-		<description>This command adds or removes a method breakpoint on the selected method.</description>
-		<topic label="Toggle Method Breakpoint" href="reference/menus/run/ref-toggle_method_breakpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-	</context>	
-	<context  id="manage_breakpoint_action_context" >
-		<description>This command adds or removes a breakpoint on the current line.</description>
-		<topic label="Toggle Line Breakpoint" href="reference/menus/run/ref-toggle_line_breakpoint.htm" />
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm"/>
-		<topic label="Adding Breakpoints" href="tasks/task-add_line_breakpoints.htm"/>
-	</context>	
-
-<!--
-	Scrapbook
--->
-	<context  id="scrapbook_imports_action_context" >
-		<description>This command opens a dialog to configure the imports associated with this snippet editor.</description>
-	</context>
-	<context  id="terminate_scrapbook_vm_action_context" >
-		<description>This command terminates the VM performing evaluations for this snippet editor.</description>
-	</context>	
-
-<!--
-	Shared Action Contexts
--->
-	<context id="show_qualified_action_context" >
-		<description>This option can be toggled to show or hide qualified names in the view.</description>
-		<topic label="Show Qualified Names" href="reference/views/shared/ref-showqualified.htm" /> 
-		<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm"/>
-		<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm" />
-		<topic label="View Display Commands" href="reference/views/shared/ref-viewdisplaycommands.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="show_constants_action_context" >
-		<description>This option can be toggled to show or hide constants (static final variables) in the view.</description>
-		<topic label="Show Constants" href="reference/views/shared/ref-showconstants.htm" /> 
-		<topic label="View Display Commands" href="reference/views/shared/ref-viewdisplaycommands.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>   
-	<context  id="show_static_action_context" >
-		<description>This option can be toggled to show or hide static variables in the view.</description>
-		<topic label="Show Static Fields" href="reference/views/shared/ref-showstatic.htm" /> 
-		<topic label="View Display Commands" href="reference/views/shared/ref-viewdisplaycommands.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="variable_inspect_action_context" >
-		<description>This command adds the selected object or primitive value to the Expressions view.</description>
-		<topic label="Inspect Variable" href="reference/views/shared/ref-inspectvariable.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="variable_watch_action_context" >
-		<description>This command creates a Java watch expression based on the name of the selected variable.</description>
-		<topic label="Create Watch Expression" href="references/views/variables/ref-createwatch.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="new_detail_formatter_action_context" >
-		<description>This command opens a dialog to define a detail formatter for the class of the selected variable.</description>
-		<topic label="Detail Formatters Preference Page" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="edit_detail_formatter_action_context" >
-		<description>This command opens a dialog to edit an existing detail formatter for the class of the selected variable.</description>
-		<topic label="Detail Formatters Preference Page" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="remove_detail_formatter_action_context" >
-		<description>This command removes the existing detail formatter for the class of the selected variable.</description>
-		<topic label="Detail Formatters Preference Page" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context  id="edit_variable_preferences" >
-		<topic label="Java Preferences" href="reference/views/shared/ref-preferences.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-		<description>Opens preference pages to configure settings related to variables in the Java debugger.</description>
-	</context> 
-	<context  id="all_instances_action_context">
-		<description>Displays all of the instances of the currently selected object in the variables view</description>
-		<topic label="All Instances" href="reference/views/shared/ref-allinstances.htm"/>
-		<topic label="All References" href="reference/views/shared/ref-allreferences.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-		<topic label="Run Menu" href="reference/menus/run/ref-menu-run.htm"/>
-	</context> 	
-	<context  id="all_references_action_context" >
-		<description>Opens a popup displaying all objects referencing the selected object.</description>
-		<topic label="All References" href="reference/views/shared/ref-allreferences.htm"/>
-		<topic label="All Instances" href="reference/views/shared/ref-allinstances.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context> 
-	<context  id="show_references_action_context">
-		<description>Toggles the display of references in the view. When turned on, each Java object that supports references will have a new child item with the name "'[variable name]' referenced from:". This new variable contains a list of all Java objects that refer to the parent object.</description>
-		<topic label="Show References" href="reference/views/shared/ref-showreferences.htm" /> 
-		<topic label="View Display Commands" href="reference/views/shared/ref-viewdisplaycommands.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context> 
-	<context id="show_null_entries_action_context" >
-		<description>This option can be toggled to show or hide null array entries in the view.</description>
-		<topic label="Show Null Array Entries" href="reference/views/shared/ref-shownull.htm" /> 
-		<topic label="View Display Commands" href="reference/views/shared/ref-viewdisplaycommands.htm"/>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	<context id="instance_filters_action_context" >
-		<description>This command opens a dialog that allows you to filter breakpoints to specific Java object instances.</description>
-		<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm"/>
-		<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm"/>
-	</context>
-	
-<!--
-	Variables View
---> 
-	
-</contexts>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml b/bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml
deleted file mode 100644
index db28a5c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/contexts_JDT_JUnit.xml
+++ /dev/null

@@ -1,75 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-    <!-- Actions -->
-    <context id="goto_referenced_test_action_context">
-        <description>This command navigates to the tests that reference this Java element.</description>
-    </context>
-    <context id="enable_filter_action_context">
-        <description>Toggles the filtering of the stack trace entries as defined in the JUnit preference page.</description>
-        <topic label="JUnit Preferences" href="reference/preferences/java/ref-preferences-junit.htm"/>
-    </context>
-    <context id="junit_tab_group">
-        <description>This launch configuration runs JUnit tests.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="launch_shortcut">
-        <description>This command launches JUnit tests. When a class is selected its tests are run. When a project, package or source folder is selected then all contained tests are run. When a single test method is selected then the selected test is run.
-		</description>
-         <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="copy_trace_action_context">
-        <description>This command copies the stack trace to the clipboard.</description>
-    </context>
-    <context id="open_test_action_context">
-        <description>This command opens the corresponding test case.</description>
-    </context>
-    <context id="open_editor_atline_action_context">
-        <description>This commands opens the corresponding test method.</description>
-    </context>
-    <context id="rerun_test_action_context">
-        <description>Reruns the selected test.</description>
-    </context>
-    <context id="scroll_lock">
-        <description>Locks the test result view so that the currently executed tests isn't automatically revealed.</description>
-    </context>
-    
-    <!-- View parts -->
-    <context id="results_view_context">
-        <description>This view displays the test results.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    
-    <!-- Wizard pages -->
-    <context id="new_testcase_wizard_page_context">
-        <description>This wizard helps you to create a new test case and to generate test stubs for existing methods.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="new_testcase_wizard_page2_context">
-        <description>This wizard helps you to create a new test case and to generate test stubs for existing methods.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context id="new_testsuite_wizard_page2_context">
-        <description>This wizard helps you to create a new test suite.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-    <context  id="launch_configuration_dialog_junit_main_tab" >
-        <description>This tab allows you to specify JUnit tests to be executed.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-    </context>
-   
-    <!-- Dialogs -->
-    <context id="test_selection_context">
-        <description>Dialog for selecting a test.</description>
-   </context>
-    <context id="result_compare_context">
-        <description>This dialog compares the expected with the actual test result in a text compare view.</description>
-    </context>
-    
-    <!-- Preference pages -->
-    <context id="junit_preference_page_context">
-        <description>This page is where you can set JUnit preferences.</description>
-        <topic label="Using JUnit" href="gettingStarted/qs-junit.htm"/>
-        <topic label="JUnit Preferences" href="reference/preferences/java/ref-preferences-junit.htm"/>
-    </context>
-</contexts>

diff --git a/bundles/org.eclipse.jdt.doc.user/cpy.png b/bundles/org.eclipse.jdt.doc.user/cpy.png
deleted file mode 100644
index a0f8775..0000000
--- a/bundles/org.eclipse.jdt.doc.user/cpy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/eclipse32.png b/bundles/org.eclipse.jdt.doc.user/eclipse32.png
deleted file mode 100644
index 4983d64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/eclipse32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/active_break_point.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/active_break_point.png
deleted file mode 100644
index 4e89d1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/active_break_point.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_as_source_folder.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_as_source_folder.png
deleted file mode 100644
index f50271a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_as_source_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_linked_source_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_linked_source_to_buildpath.png
deleted file mode 100644
index 5ef9813..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/add_linked_source_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/debug_button.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/debug_button.png
deleted file mode 100644
index 9942fdb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/debug_button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/edit_undo_refactoring_menu.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/edit_undo_refactoring_menu.png
deleted file mode 100644
index 9adb992..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/edit_undo_refactoring_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_display.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_display.png
deleted file mode 100644
index 7617c22..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_display.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_sysytem_get.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_sysytem_get.png
deleted file mode 100644
index 010eb64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_myscrap_sysytem_get.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_field.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_field.png
deleted file mode 100644
index cb9730f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_field.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_getters.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_getters.png
deleted file mode 100644
index 985d61c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_getters.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_import.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_import.png
deleted file mode 100644
index 48a7f6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_moved.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_moved.png
deleted file mode 100644
index c1875d7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_moved.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_outline_override.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_outline_override.png
deleted file mode 100644
index f23f1b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_mytestcase_outline_override.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase.png
deleted file mode 100644
index 4dfa899..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname.png
deleted file mode 100644
index 266cd44..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname_quickfix.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname_quickfix.png
deleted file mode 100644
index a63ee6e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_getname_quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_hover.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_hover.png
deleted file mode 100644
index 438906d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_unsaved.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_unsaved.png
deleted file mode 100644
index 6e2ffa0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_error_unsaved.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_search_references.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_search_references.png
deleted file mode 100644
index 8c731cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testcase_search_references.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_extract_method.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_extract_method.png
deleted file mode 100644
index f4c3168..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_extract_method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_outline_collectinheritedmethod.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_outline_collectinheritedmethod.png
deleted file mode 100644
index 551d80e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_testsuite_outline_collectinheritedmethod.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest.png
deleted file mode 100644
index 47cbd41..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist.png
deleted file mode 100644
index 12dee3c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist_t.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist_t.png
deleted file mode 100644
index a689db8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_content_assist_t.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_debug.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_debug.png
deleted file mode 100644
index e5cbd17..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_debug.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template.png
deleted file mode 100644
index 559a78d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp.png
deleted file mode 100644
index ca200dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_e.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_e.png
deleted file mode 100644
index 5c12687..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_e.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_expected.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_expected.png
deleted file mode 100644
index c5e3c58..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_for_template_exp_expected.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_inspect.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_inspect.png
deleted file mode 100644
index 530dab9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_inspect.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_organized_imports.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_organized_imports.png
deleted file mode 100644
index 63f1c7c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_organized_imports.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_outline_main.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_outline_main.png
deleted file mode 100644
index ce85193..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_outline_main.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_problem_hover.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_problem_hover.png
deleted file mode 100644
index 7a48b79..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_problem_hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_quickoutline.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_quickoutline.png
deleted file mode 100644
index c4fc73f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_quickoutline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_testSizeIsThree.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_testSizeIsThree.png
deleted file mode 100644
index 711002a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_testSizeIsThree.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template.png
deleted file mode 100644
index f35ac86..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_exp.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_exp.png
deleted file mode 100644
index 55410b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_integer.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_integer.png
deleted file mode 100644
index 1ce6172..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/editor_vectortest_toarray_template_integer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_dialog.png
deleted file mode 100644
index 1ce79b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_preview_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_preview_dialog.png
deleted file mode 100644
index d1c1982..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/extract_method_preview_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/generate_getter_setter_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/generate_getter_setter_dialog.png
deleted file mode 100644
index 7451efa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/generate_getter_setter_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull.png
deleted file mode 100644
index 3311495..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull_workspace_modifed.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull_workspace_modifed.png
deleted file mode 100644
index 74ce13b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/icon_junit_successfull_workspace_modifed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox-coloring.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox-coloring.png
deleted file mode 100644
index ab6f4db..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox-coloring.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox.png
deleted file mode 100644
index f68e438..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/autobox.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/compiler-property-page.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/compiler-property-page.png
deleted file mode 100644
index 644b64e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/compiler-property-page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/editor_override_annotation_hover.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/editor_override_annotation_hover.png
deleted file mode 100644
index 6c712f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/editor_override_annotation_hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/enum.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/enum.png
deleted file mode 100644
index 075cb5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/enum.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-inserted.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-inserted.png
deleted file mode 100644
index 342e905..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-inserted.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-proposal.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-proposal.png
deleted file mode 100644
index f9e2a17..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/foreach-proposal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/infer-generic.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/infer-generic.png
deleted file mode 100644
index e7d1582..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/infer-generic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/inferred-generic.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/inferred-generic.png
deleted file mode 100644
index bea5b35..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/inferred-generic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/quick-fix.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/quick-fix.png
deleted file mode 100644
index 98bbc11..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/quick-fix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-applied.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-applied.png
deleted file mode 100644
index 82092cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-applied.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-proposed.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-proposed.png
deleted file mode 100644
index 1bd8536..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/suppress-proposed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/unused-warning.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/unused-warning.png
deleted file mode 100644
index 6972414..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/unused-warning.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger.png
deleted file mode 100644
index a65b363..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_incompatible.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_incompatible.png
deleted file mode 100644
index 14b7aec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_incompatible.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_inexact.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_inexact.png
deleted file mode 100644
index 292380c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_inexact.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_unfiltered.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_unfiltered.png
deleted file mode 100644
index 4de1a2f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/view_search_listInteger_unfiltered.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/wiz_new_java_project_myproject.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/wiz_new_java_project_myproject.png
deleted file mode 100644
index b34ba7f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/j2se50/wiz_new_java_project_myproject.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/move_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/move_dialog.png
deleted file mode 100644
index bb0a4b5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/move_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_open_typehieracrchy.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_open_typehieracrchy.png
deleted file mode 100644
index 84bd10d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_open_typehieracrchy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opendeclaration.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opendeclaration.png
deleted file mode 100644
index d9856b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opendeclaration.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opentype.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opentype.png
deleted file mode 100644
index 6d47c03..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/navigate_opentype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/open_run_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/open_run_dialog.png
deleted file mode 100644
index 7924390..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/open_run_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/override_implement_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/override_implement_dialog.png
deleted file mode 100644
index d8c9c70..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/override_implement_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/packagefolder_obj.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/packagefolder_obj.png
deleted file mode 100644
index 93053b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/packagefolder_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_buildpath.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_buildpath.png
deleted file mode 100644
index d5439a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_compiler.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_compiler.png
deleted file mode 100644
index a8d4b3d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_compiler.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_editor.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_editor.png
deleted file mode 100644
index 626c708..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_jre.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_jre.png
deleted file mode 100644
index 3f8ff53..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_jre.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_launch_operation.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_launch_operation.png
deleted file mode 100644
index 608a322..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_launch_operation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_workspace.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_workspace.png
deleted file mode 100644
index 3b6536c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/pref_workspace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/previous_searches_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/previous_searches_dialog.png
deleted file mode 100644
index a8177b6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/previous_searches_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout1.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout1.png
deleted file mode 100644
index 5a2803a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout2.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout2.png
deleted file mode 100644
index 712efbe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout3.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout3.png
deleted file mode 100644
index 1112ca3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout4.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout4.png
deleted file mode 100644
index ca3a89c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-DetectingExistingLayout4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources1.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources1.png
deleted file mode 100644
index cea221e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources2.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources2.png
deleted file mode 100644
index 6c45dc3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources3.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources3.png
deleted file mode 100644
index 3f594e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources4.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources4.png
deleted file mode 100644
index ae9333b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources5.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources5.png
deleted file mode 100644
index c3f176d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources6.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources6.png
deleted file mode 100644
index 9b316b2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-OrganizeSources6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout10.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout10.png
deleted file mode 100644
index 527aa10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout10.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout11.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout11.png
deleted file mode 100644
index 0d06300..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout11.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout12.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout12.png
deleted file mode 100644
index c236ccb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout12.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout13.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout13.png
deleted file mode 100644
index 9f6bb54..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout13.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout14.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout14.png
deleted file mode 100644
index fd5fec1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout14.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout15.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout15.png
deleted file mode 100644
index 94832d6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout15.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout20.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout20.png
deleted file mode 100644
index 72ab280..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout20.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout21.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout21.png
deleted file mode 100644
index 0d06300..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout21.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout22.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout22.png
deleted file mode 100644
index c236ccb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout22.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout23.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout23.png
deleted file mode 100644
index 53f104c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout23.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout24.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout24.png
deleted file mode 100644
index 5c950ee..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout24.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout25.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout25.png
deleted file mode 100644
index 34fc678..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout25.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout26.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout26.png
deleted file mode 100644
index 3b29188..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout26.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout27.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout27.png
deleted file mode 100644
index ae75ac3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout27.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout28.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout28.png
deleted file mode 100644
index 3e8bd27..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout28.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout29.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout29.png
deleted file mode 100644
index 46439a2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout29.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout30.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout30.png
deleted file mode 100644
index 3c21195..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout30.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout31.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout31.png
deleted file mode 100644
index 0d06300..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout32.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout32.png
deleted file mode 100644
index c236ccb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout32.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout33.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout33.png
deleted file mode 100644
index 1d86890..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout33.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout34.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout34.png
deleted file mode 100644
index 818a8b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout34.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout35.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout35.png
deleted file mode 100644
index 3a4dd19..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout35.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout36.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout36.png
deleted file mode 100644
index 830bdd8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout36.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout40.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout40.png
deleted file mode 100644
index 29f6df4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout40.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout41.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout41.png
deleted file mode 100644
index 0d06300..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout41.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout42.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout42.png
deleted file mode 100644
index c236ccb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout42.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout43.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout43.png
deleted file mode 100644
index 1d86890..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout43.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout44.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout44.png
deleted file mode 100644
index f1c4370..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout44.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout45.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout45.png
deleted file mode 100644
index fb0efec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout45.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout46.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout46.png
deleted file mode 100644
index 0627404..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout46.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout47.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout47.png
deleted file mode 100644
index 20fa3ed..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout47.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout48.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout48.png
deleted file mode 100644
index adf939e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout48.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout49.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout49.png
deleted file mode 100644
index a6e8874..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout49.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout50.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout50.png
deleted file mode 100644
index fdf23f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout50.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout51.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout51.png
deleted file mode 100644
index 6bb6387..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout51.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout52.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout52.png
deleted file mode 100644
index ac9a1bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout52.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout53.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout53.png
deleted file mode 100644
index d6e7359..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout53.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout54.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout54.png
deleted file mode 100644
index 99027c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout54.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout55.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout55.png
deleted file mode 100644
index 9f0683e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout55.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout56.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout56.png
deleted file mode 100644
index aac337b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout56.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout57.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout57.png
deleted file mode 100644
index ce8c120..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout57.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout58.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout58.png
deleted file mode 100644
index b161d8a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout58.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout59.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout59.png
deleted file mode 100644
index db80007..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout59.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5a.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5a.png
deleted file mode 100644
index adcbf69..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5b.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5b.png
deleted file mode 100644
index 7042d60..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout5b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout60.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout60.png
deleted file mode 100644
index 1572d47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout60.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout61.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout61.png
deleted file mode 100644
index d53efea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout61.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout62.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout62.png
deleted file mode 100644
index 6f92ccd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout62.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout63.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout63.png
deleted file mode 100644
index 63b46fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout63.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout64.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout64.png
deleted file mode 100644
index b4c8074..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout64.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout65.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout65.png
deleted file mode 100644
index abc3a96..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout65.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout66.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout66.png
deleted file mode 100644
index 15d6e9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout66.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout67.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout67.png
deleted file mode 100644
index 49d8492..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout67.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout68.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout68.png
deleted file mode 100644
index 45d9d05..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout68.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout69.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout69.png
deleted file mode 100644
index 9f34460..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout69.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6a.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6a.png
deleted file mode 100644
index 4fb0246..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6b.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6b.png
deleted file mode 100644
index 8fa14a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6b.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6c.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6c.png
deleted file mode 100644
index 0af4338..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/qs-WorkingWithExistingLayout6c.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_menu.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_menu.png
deleted file mode 100644
index 2786edf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_submethods.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_submethods.png
deleted file mode 100644
index 4fbbd53..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quickoutline_submethods.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialog_setup.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialog_setup.png
deleted file mode 100644
index deb6cb2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialog_setup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialogs.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialogs.png
deleted file mode 100644
index d3e6701..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/quicktype_dialogs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_dialog.png
deleted file mode 100644
index 827194e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_preview_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_preview_dialog.png
deleted file mode 100644
index 5381c79..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/rename_cu_preview_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/replace_local_element.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/replace_local_element.png
deleted file mode 100644
index 154dd6f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/replace_local_element.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/restore_local_history.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/restore_local_history.png
deleted file mode 100644
index a209c12..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/restore_local_history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog.png
deleted file mode 100644
index fb7d83d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_arguments.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_arguments.png
deleted file mode 100644
index b3c48cb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_arguments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_junit.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_junit.png
deleted file mode 100644
index 09e1890..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dialog_junit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dropdown.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dropdown.png
deleted file mode 100644
index 9ccbb2e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/run_dropdown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search.png
deleted file mode 100644
index 95e60a5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_file_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_file_dialog.png
deleted file mode 100644
index ee5624f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_file_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_next.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_next.png
deleted file mode 100644
index 6a7fed1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_prev.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_prev.png
deleted file mode 100644
index 6b70440..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_prev.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_runTest_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_runTest_dialog.png
deleted file mode 100644
index 8004aae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/search_runTest_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_how.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_how.png
deleted file mode 100644
index 7bf8828..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_how.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_java_app_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_java_app_dialog.png
deleted file mode 100644
index 937a6d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/select_java_app_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/superclass_selection_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/superclass_selection_dialog.png
deleted file mode 100644
index 3dc6d15..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/superclass_selection_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_noarg.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_noarg.png
deleted file mode 100644
index a087e2a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_noarg.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_success.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_success.png
deleted file mode 100644
index a9abd4b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_console_success.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug.png
deleted file mode 100644
index 5596530..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug_removelaunched.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug_removelaunched.png
deleted file mode 100644
index 72f475a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_debug_removelaunched.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display.png
deleted file mode 100644
index 06380e4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display_done.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display_done.png
deleted file mode 100644
index abfac84..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_display_done.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_inspect.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_inspect.png
deleted file mode 100644
index a1f1bab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_display_inspect.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_junit_red.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_junit_red.png
deleted file mode 100644
index 0155cc7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_junit_red.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_delete_import.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_delete_import.png
deleted file mode 100644
index 99f1278..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_delete_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_search_references.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_search_references.png
deleted file mode 100644
index 33f0d83..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_search_references.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_main.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_main.png
deleted file mode 100644
index 3d60c5d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_main.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_run.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_run.png
deleted file mode 100644
index 701224c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_testrunner_run.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest.png
deleted file mode 100644
index bde46ed..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest_filtered.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest_filtered.png
deleted file mode 100644
index 930a9c3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_outline_vectortest_filtered.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit.png
deleted file mode 100644
index 5e8a137..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit_exp.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit_exp.png
deleted file mode 100644
index 0d9a176..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_junit_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_open_type_hierarchy.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_open_type_hierarchy.png
deleted file mode 100644
index ffcc2e3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_open_type_hierarchy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_vectortest_error.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_vectortest_error.png
deleted file mode 100644
index b0ef9a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_package_explorer_vectortest_error.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_problems_goto.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_problems_goto.png
deleted file mode 100644
index fee906b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_problems_goto.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_editor_runTest.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_editor_runTest.png
deleted file mode 100644
index 26c084f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_editor_runTest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_previous.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_previous.png
deleted file mode 100644
index 0f10e28..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_previous.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_research_menu.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_research_menu.png
deleted file mode 100644
index c1aa6e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_research_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_runTest.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_runTest.png
deleted file mode 100644
index 5740b76..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_search_runTest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase.png
deleted file mode 100644
index 8790a32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_focused.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_focused.png
deleted file mode 100644
index 748e646..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_focused.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_menu.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_menu.png
deleted file mode 100644
index dd1103e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_runtest_locked.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_runtest_locked.png
deleted file mode 100644
index baeb61c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_runtest_locked.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_small.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_small.png
deleted file mode 100644
index 1d5d1cd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_small.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_subtype.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_subtype.png
deleted file mode 100644
index 444bd092..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_subtype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype.png
deleted file mode 100644
index 811d436..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype_locked.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype_locked.png
deleted file mode 100644
index f905ecd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_typehierarchy_testcase_supertype_locked.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_1.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_1.png
deleted file mode 100644
index c93fb0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_logical_structures.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_logical_structures.png
deleted file mode 100644
index 8861294..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/view_variables_logical_structures.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_import_arch.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_import_arch.png
deleted file mode 100644
index 9091889..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_import_arch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog.png
deleted file mode 100644
index fbdaa6f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog_superchecked.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog_superchecked.png
deleted file mode 100644
index 577a6dc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_class_dialog_superchecked.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_project.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_project.png
deleted file mode 100644
index f85b9e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_scrap.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_scrap.png
deleted file mode 100644
index b568e9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_scrap.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_suite.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_suite.png
deleted file mode 100644
index 01d4c87..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_suite.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_testcase.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_testcase.png
deleted file mode 100644
index 1a0f9d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/wiz_new_testcase.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_debug_vectortest.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_debug_vectortest.png
deleted file mode 100644
index b9c5edb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_debug_vectortest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_java_browsing.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_java_browsing.png
deleted file mode 100644
index edb920d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_java_browsing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_testcase_errors.png b/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_testcase_errors.png
deleted file mode 100644
index 5d5fc2e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/images/workbench_testcase_errors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm
deleted file mode 100644
index 86ecf5f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/intro/overview.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Java development overview</title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-   </head>
-   
-  <body>
-    <h1>
-      Java development overview</h1>
-    <p>
-		The JDT project provides the tool plug-ins that implement a Java IDE supporting the development of any Java application, including Eclipse plug-ins. It adds a Java project nature and Java perspective to the Eclipse Workbench as well as a number of views, editors, wizards, builders, and code merging and refactoring tools. The JDT project allows Eclipse to be a development environment for itself.</p>
-	<p>
-		Try the <a href="../../gettingStarted/qs-BasicTutorial.htm">
-		Basic tutorial</a> to get a first impression. Discover more in the <a href="../../tips/jdt_tips.html">
-		Tips and Tricks</a> section and learn about the latest features in <a href="../../whatsNew/jdt_whatsnew.html">
-		What's new in 3.4</a>
-	</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm
deleted file mode 100644
index c613f30..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-10.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title>Moving and copying Java elements</title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>Moving and copying Java elements</h1>
-<p> In this section, you will use refactoring to move a resource between Java packages.&nbsp;
-Refactoring actions change the structure of your code without changing its
-semantic behavior. </p>
-<ol>
-  <li> In the Package Explorer view, select the <em>MyTestCase.java</em> 
-    file from the <em>test</em> package and drag it into the <em>junit.samples</em> package. 
-    Dragging and dropping the file is similar to selecting the file and
-    choosing <strong>Refactor &gt; Move </strong>from the context menu.
-  </li>
-  <li> You will be prompted to select whether or not to update references to the
-    file you are moving. Typically, you will want to do this to avoid compile errors. You can
-    press the <strong>Preview </strong>button to see the list of changes that
-    will be made as a result of the move.
-  </li>
-  <li>
-<p>Press <strong>OK</strong>. The file 
-    is moved, and its package declaration changes to reflect the new location.</p>
-    <p> <img src="images/editor_mytestcase_moved.png"  alt="File moved to junit.samples package"> 
-    </p>
-    </li>
-    <li><p>Use <strong>Edit &gt; Undo Move</strong> to undo the move.</p></li>
-  </ol>
-  <p>The context menu is an alternative to using drag and drop.&nbsp; When
-  using the menu, you must specify a target package in the Move dialog, in
-  addition to selecting the update references options you've already seen.</p>
-  <ol>
-  <li> 
-    Select the <em>MyTestCase.java</em> file and from its context menu, select <strong>Refactor 
-    &gt; Move</strong>.</li>
-    <li> In the Move dialog, expand the hierarchy to browse the 
-    possible new locations for the resource. Select the <em>junit.samples</em> 
-    package, then click <strong>OK</strong>. The class is moved, and its 
-    package declaration is updated to the new location. 
-    <p> <img src="images/move_dialog.png"  alt="Move destination dialog"> 
-    </p>
- </li>
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-Navigate.htm">Navigate to a Java element's declaration</A>
-</P>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../concepts/concept-refactoring.htm">Refactoring support</a> </p>
-
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-  <a href="../reference/ref-wizard-refactorings.htm">Refactoring wizard</a><br>
-  <a href="../reference/preferences/ref-preferences-java.htm">Java preferences</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm
deleted file mode 100644
index 8fcfea7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-11.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<title> Searching the workbench </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1> Searching the workbench </h1>
-<p> In this section, you will search the workbench for Java elements. </p>
-<p> In the Search dialog, you can perform file, text or Java searches. Java searches 
-  operate on the structure of the code. File searches operate on the files 
-  by name and/or text content. Java searches are faster, since there is an
-underlying indexing structure for the code structure.  Text searches allow
-you to find matches inside comments and strings. 
-</p>
-<h2> Performing a Java search from the workbench </h2>
-<ol>
-  <li> In the Java perspective, click the <strong>Search</strong> 
-    (<img src="images/search.png" alt="Search">) button 
-    in the workbench toolbar or use <strong>Search &gt; Java...</strong> from 
-    the menu bar. </li>
-  <li> If it is not already selected, select the <strong>Java Search</strong> 
-    tab. </li>
-  <li> In the <strong>Search string</strong> field, type <em>runTest</em>. 
-    In the <em>Search For</em> area, select <strong>Method</strong>, and in the <em>Limit 
-    To</em> area, select <strong>References</strong>.<br>
-    Verify that the Scope is set to <strong>Workspace</strong>. 
-    <p> <img src="images/search_runTest_dialog.png"  alt="Java Search dialog"> 
-    </p>
-    Then click <strong>Search</strong>. While searching you may click <strong>Cancel</strong> 
-    at any time to stop the search. Partial results will be shown. </li>
-  <li> In the Java perspective, the Search view shows the search results. 
-    <p> <img src="images/view_search_runTest.png"  alt="Search results view"> 
-    </p>
-    Use the <strong>Show Next Match</strong> 
-    (<img src="images/search_next.png" alt="Show Next Match">) and <strong>Show Previous 
-    Match</strong> (<img src="images/search_prev.png" alt="Show Previous Match">) buttons to navigate to each match. If the file in which the 
-    match was found is not currently open, it is opened in an editor. </li>
-  <li> When you navigate to a search match using the Search view buttons, 
-    the file opens in the editor at the position of the match. Search matches 
-    are tagged with a search marker in the rulers. 
-    <p> <img src="images/view_search_editor_runTest.png"  alt="Editor with Search marker"> 
-    </p>
-  </li>
-</ol>
-<h2> Searching from a Java view </h2>
-<p> Java searches can also be performed from specific views, including the Outline, 
-  Hierarchy view and the Package Explorer view. </p>
-<ol>
-  <li> In the Package Explorer view, double-click <em>junit.framework.Assert.java</em> 
-    to open it in an editor. </li>
-  <li> In the Outline view, select the fail(String) method, and from its context 
-    menu, select&nbsp;<strong>References &gt; Workspace</strong>. 
-    <p> <img src="images/view_outline_search_references.png"  alt="Search context menu in Outline view"> 
-    </p>
-  </li>
-</ol>
-<h2> Searching from an editor </h2>
-<p> From the Package Explorer view, open <em>junit.framework.TestCase.java</em>. 
-  In the editor, select the class name <em>TestCase</em> and from the context 
-  menu, select <strong>  References &gt; Workspace</strong>. 
-  </p>
-    <img src="images/editor_testcase_search_references.png"  alt="Search context menu in editor"> 
-<h2> Continuing a search from the search view </h2>
-<p> The Search Results view shows the results for the TestCase search. Select 
-  a search result and open the context menu. You can continue searching the selected 
-  element's references and declarations. </p>
-<img src="images/view_search_research_menu.png"  alt="Search context menu in Search results view">
-<p> If you want to follow multiple levels of method calls, you can also use
-<strong>Navigate &gt; Open Call Hierarchy</strong>.
-</p>
- 
-<h2> Performing a file search </h2>
-<ol>
-  <li> In the Java perspective, click the&nbsp;<strong>Search</strong> button 
-    in the workbench toolbar or select <strong>Search &gt; File</strong> from the menu bar. </li>
-  <li> If it is not already selected, select the <strong>File Search</strong> 
-    tab.</li>
-  <li> In the <strong>Containing text</strong> field, type <em>TestCase</em>.
-    Make sure that the <strong>File name patterns</strong>  field is set 
-    to <em>*.java</em>. The Scope should be set to <em>Workspace</em>.
-    Then click <strong>Search</strong>.
-    <p> <img src="images/search_file_dialog.png"  alt="File search tab"> 
-    </p>
-  </li>
-  <li> To find all files of a given file name pattern, leave the Containing 
-    Text field empty. </li>
-</ol>
-<h2> Viewing previous search results </h2>
-<p> In the Search Results view, click the arrow next to the<strong> Previous 
-  Search Results</strong> toolbar button to see a menu containing the list of the most 
-  recent searches. You can choose items from this menu to view previous
-searches.&nbsp; The list can be cleared by choosing <strong>Clear History</strong>. 
-</p>
-<img src="images/view_search_previous.png"  alt="Previous search results menu"> 
-<p> 
-The <strong>Previous Search Results</strong> button will display a dialog 
-  with the list of all previous searches from the current session. 
-  </p>
-<img src="images/previous_searches_dialog.png"  alt="Previous search results dialog"> 
-<p> 
-Selecting a previous search from this dialog will let you view that search. 
-</p>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-12.htm">Running your programs</A>
-</P>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> 
-
-<a href="../concepts/concept-java-search.htm">Java search</a> </p>
-
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-  <a href="../reference/ref-wizard-refactorings.htm">Refactoring wizard</a><br>
-  <a href="../reference/preferences/ref-preferences-java.htm">Java preferences</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm
deleted file mode 100644
index bdca042..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-12.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Running your programs </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Running your programs </h1>
-<p> In this section, you will learn more about running Java programs in the workbench. 
-</p>
-<ol>
-  <li> In the Package Explorer view, find <em>junit.textui/TestRunner.java</em> 
-    and double-click it to open it in an editor. </li>
-  <li> In the Outline view, notice that the TestRunner class has an icon which 
-    indicates that the class defines a <code>main</code> method. 
-    <p> <img src="images/view_outline_testrunner_main.png"  alt="Outline view with selected TestRunner class"> 
-    </p>
-  </li>
-  <li> Right click on TestRunner.java in the Package Explorer and select
-    <strong>Run As</strong> &gt; <strong>Java Application</strong>. This will launch the
-    selected class as a local Java application. The <strong>Run As</strong>
-    context menu item is also available in other places, such as the Outline view.
-    <p> <img src="images/view_outline_testrunner_run.png"  alt="Run context menu"> </p>
-  </li>
-  <li> Notice that the program has finished running and the following message appears in the 
-    Console view telling you that the program needs an execution argument.&nbsp;
-    Running class from the Package Explorer as a Java Application uses the default settings for
-    launching the selected class and does not allow you to specify any
-    arguments. 
-    <p> <img src="images/view_console_noarg.png"  alt="Console with error message: Usage: TestRunner [-wait] testCaseName, where name is the name of the TestCase class"> 
-    </p>
-  </li>
-  <li> To specify arguments, use the drop-down <strong>Run</strong> menu in the
-    toolbar and select <strong>Run Configurations...</strong>. 
-    <p> <img src="images/open_run_dialog.png"  alt="Run menu of the toolbar"> </p>
-    You can also Ctrl+Click a configuration in the drop-down menu to start editing that configuration.
-  </li>
-  <li> This time, the Launch Configurations dialog opens with the TestRunner launch configuration selected.
-    A launch configuration allows you to configure how a program is launched,
-    including its arguments, classpath, and other options.&nbsp; (A default
-    launch configuration was created for you when you chose <strong>Run &gt;
-    Java Application</strong>). 
-    <p> <img src="images/run_dialog.png"  alt="Launch configuration dialog showing the Main tab"> 
-    </p>
-  </li>
-  <li> Select the Arguments tab and type <em>junit.samples.VectorTest</em> in 
-    the Program arguments area. 
-    <p> <img src="images/run_dialog_arguments.png"  alt="Arguments tab of the launch configuration dialog"> 
-    </p>
-  </li>
-  <li> Click <strong>Run</strong>. This time the program runs correctly, indicating 
-    the number of tests that were run. 
-    <p> <img src="images/view_console_success.png"  alt="Console showing program output"> </p>
-  </li>
-  <li> <p>Switch to the Debug perspective. In the Debug view, notice that a process
-    for the last program launch was registered when the program was run.</p>
-    <p>By default, the Debug view automatically removes any terminated launches when
-    a new launch is created. This preference can be configured on the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Launching preference page">
-      <strong>Run/Debug &gt; Launching</strong></a>
-    preference page</p>
-    <p> <img src="images/view_debug.png"  alt="Debug view showing two terminated run launches"> 
-    </p>
-    <em>Note: You can relaunch a terminated process by selecting <strong>Relaunch</strong> 
-    from its context menu.</em> </li>
-  <li> Select the drop-down menu from the <strong>Run</strong> button in the workbench 
-    toolbar. This list contains the previously launched programs. These programs
-    can be relaunched by selecting them in the history list. 
-    <p> <img src="images/run_dropdown.png"  alt="Run drop down menu from the workbench toolbar"> 
-    </p>
-  </li>
-  <li> By default the currently selected resource or active editor is launched when the run button is hit. If none of these is 
-  launchable the current project will be launched. You can configure this behaviour under
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Launching preference page">
-      <strong>Run/Debug &gt; Launching</strong></a>.
-  <p> <img src="images/pref_launch_operation.png"  alt="Debug view showing two terminated run launches"> 
-    </p> 
-  </li>
-  <li> From the context menu in the Debug view (or the equivalent toolbar button), 
-    select <strong>Remove All Terminated</strong> to clear the view of terminated
-    launch processes. 
-    <p> <img src="images/view_debug_removelaunched.png"  alt="Debug view showing context menu"> 
-    </p>
-  </li>
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-13.htm">Debugging your programs</A>
-</P>
-    <p><img src="../images/ngrelt.png"  border="0" alt="Related tasks"><br>
-     <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-     <a href="../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-     <a href="../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-     <a href="../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-     <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-    </p>
-
-    <p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-     <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-     <a href="../reference/menus/run/ref-menu-run.htm">Run menu actions</a><br>
-     <a href="../reference/ref-toolbar-run.htm">Run and debug toolbar actions</a><br>
-    </p>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm
deleted file mode 100644
index e41b33d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-13.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Debugging your programs </title>
-</head>
-<body>
-<h1> Debugging your programs </h1>
-<p> In this section, you will debug a Java program. </p>
-<ol>
-  <li> In the Package Explorer view in the Java perspective, double-click <em>junit.samples/VectorTest.java</em> 
-    to open it in an editor. </li>
-  <li> Place your cursor on the vertical ruler along the left edge of the editor
-    area on the following line in the setUp() method: 
-    <p> <code>fFull.addElement (new Integer(1));</code> </p>
-    <p> and double-click on the ruler to set a breakpoint. </p>
-    <p> <img src="images/editor_vectortest_debug.png"  alt="VectorTest.java editor showing added breakpoint"> 
-    </p>
-    The breakpoint icon indicates the status of the breakpoint.&nbsp; The plain
-    blue breakpoint icon indicates that the breakpoint has been set, but not yet
-    installed.&nbsp;&nbsp;
-    <p>
-    <em>Note: Once the class is loaded by the Java VM, the breakpoint will be
-    installed and a checkmark overlay will be displayed on the breakpoint icon.</em> </p></li>
-  <li> In the Package Explorer view, select the <em>junit.samples</em> package 
-    and select <strong>Debug As</strong>, and then <strong>Java 
-    Application</strong>.&nbsp; When you run a program from a package, you will be
-    prompted to choose a type from all classes in the package that define a <code>main
-    </code>method.&nbsp; </li>
-  <li> Select the <em>VectorTest</em> item in the dialog, 
-    then click <strong>OK</strong>. 
-    <p> <img src="images/select_java_app_dialog.png"  alt="Type selection dialog"> </p>
-    <p><em>Note: You can also simply hit the debug button <img src="images/debug_button.png" alt="Debug button"> 
-      which will launch the currently selected resource or active editor. Select 
-      <strong>Java Application </strong>when you are prompted to select a way 
-      to debug VectorTest.</em></p>
-	  <p><img src="images/select_how.png" alt="Select way to debug VectorTest"></p>
-  </li>
-  <li> The program will run until the breakpoint is reached.&nbsp; When the breakpoint is hit, execution 
-    is suspended, and you are asked whether to open the Debug perspective.  Click <strong>Yes</strong>.
-    Notice that the process is still active (not terminated) in 
-    the Debug view. Other threads might still be running.
-    <p> <img src="images/workbench_debug_vectortest.png"  alt="Debug perspective"> </p>
-    <em>Note: The breakpoint now has a checkmark overlay <img src="images/active_break_point.png" alt="Breakpoint with overlay"> since the class
-    VectorTest was loaded in the Java VM.</em> </li>
-  <li> In the editor in the Debug perspective, select <code>new Vector()</code> from the line above
-    where the breakpoint is set, and from its context menu, select <strong>Inspect</strong>. 
-    <p> <img src="images/editor_vectortest_inspect.png"  alt="VectorTest.java editor with selected breakpoint line showing context menu"> 
-    </p>
-  </li>
-  <li> The expression is evaluated in the context of the current stack frame, 
-    and a pop-up appears which displays the results. You can send a result to
-    the Expressions view by pressing the key binding displayed in the pop-up.
-  </li>
-  <li> Expressions that you evaluate while debugging a program will be listed in
-    this view. To delete an expression after working with it, select the
-    expression and choose <strong>Remove</strong> from its context menu. 
-  </li>
-  <li> The Variables view (available on a tab along with the Expressions view) displays the values of the variables in the selected 
-    stack frame. Expand the this.fFull tree in the Variables view until you can see 
-    elementCount. 
-  </li>
-  <li> The variables (e.g., elementCount) in the Variables view will change when
-    you step 
-    through VectorTest in the Debug view.&nbsp; To step through the code, click the 
-    <strong>Step Over</strong> (<img src="../images/org.eclipse.debug.ui/elcl16/stepover_co.png" alt="Step Over" >) button.&nbsp;
-    Execution will continue at the next line in the same method 
-      (or, if you are at the end of a method, it will continue in the method from 
-      which the current method was called).
-    <p> <img src="images/view_variables_1.png"  alt="Variables view"> </p>
-  </li>
-  <li>In the variables view you can choose to see certain types as logical structures. This hides the implementation details of a 
-  type and simply shows it as arrays or fields. You can define logical structures by yourself in the preference page <strong>Java &gt; Debug &gt; Logical Structures</strong>.
-  <p> <img src="images/view_variables_logical_structures.png" alt="fFull shown as logical structure"> </p>
-  </li>
-  <li> Try some other step buttons 
-    (<strong>Step Into <img src="../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" alt="Step Into" >, 
-    Step Return <img src="../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" alt="Step Return" >) </strong>to
-    step through the code.&nbsp; Note the differences in stepping techniques.
-  </li>
-  <li> You can end a debugging session by allowing the program to run to
-    completion or by terminating it.
-    <ul>
-      <li>You can continue to step over the code with the <strong>Step </strong>buttons
-        until the program completes.</li>
-      <li>You can click the&nbsp; <strong>Resume </strong>  
-      (<img src="../images/org.eclipse.debug.ui/elcl16/resume_co.png" alt="Resume" >) button to allow the
-        program to run until the next breakpoint is encountered or until the
-        program is completed.</li>
-      <li>You can select 
-    <strong>Terminate</strong> from the context menu of the program's
-        process in the Debug view to terminate the program.</li>
-    </ul>
-  </li>
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-14.htm">Evaluating expressions</A>
-</P>
-    <p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-     <a href="../concepts/cbrkpnts.htm">Breakpoints</a><br>
-     <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-     <a href="../concepts/clocdbug.htm">Local debugging</a></p>
-
-    <p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-     <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-     <a href="../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-     <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-     <a href="../tasks/task-suspending_threads.htm">Suspending threads</a></p>
-
-    <p><img src="../images/ngrelr.png"  border="0" alt="Related reference"><br>
-     <a href="../reference/preferences/java/debug/ref-debug.htm">Debug preferences</a><br>
-     <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-     <a href="../reference/menus/run/ref-menu-run.htm">Run menu actions</a><br>
-     <a href="../reference/ref-toolbar-run.htm">Run and debug toolbar actions</a><br>
-     <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a><br>
-     <a href="../reference/views/console/ref-console_view.htm">Console view</a><br>
-     <a href="../reference/views/display/ref-display_view.htm">Display view</a><br>
-     <a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a><br>
-<a href="../reference/views/variables/ref-variables_view.htm">Variables view</a></p>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm
deleted file mode 100644
index 399af7f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-14.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Evaluating expressions </title>
-</head>
-<body>
-<h1> Evaluating expressions </h1>
-<p> In this section, you will evaluate expressions in the context of your
-running Java program. </p>
-<ol>
-  <li> Debug <em>junit.samples.VectorTest.java</em> to the breakpoint in the
-    <code>setUp()</code> method and select <b>Step Over</b> twice to populate <code>fFull</code>.&nbsp; (See the <a href="qs-13.htm">Debugging your Programs</a> section for full
-    details.)<br>
-  </li>
-  <li>Open the Display view by selecting <b>Window &gt; Show View &gt; Display</b> 
-    and type the following line in the view:
-    <p> <code>fFull.size()</code></p>
-  </li>
-  <li> Select the text you just typed, and from its context menu, select <strong>Display</strong>.&nbsp;
-    (You can also choose <strong>Display Result of Evaluating Selected Text </strong> (<img src="../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" alt="Display" >) from
-    the Display view toolbar.) 
-    <p> <img src="images/view_display_display.png"  alt="Display view with fFull.size selected and showing context menu"> 
-    </p>
-  </li>
-  <li> The expression is evaluated and the result is displayed in the Display
-    view. 
-    <p> <img src="images/view_display_display_done.png"  alt="Display view showing evaluation result: (int) 2"> 
-    </p>
-  </li>
-  <li> On a new line in the Display view, type the following line: 
-    <p> <code>fFull.toArray()</code> </p>
-  </li>
-  <li> Select this line, and select <strong>Inspect</strong> from the context
-    menu.&nbsp; (You can also choose <strong>Inspect Result of Evaluating
-    Selected Text </strong> (<img src="../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" alt="Inspect" >) from the Display view toolbar.) </li>
-  <li>A lightweight window opens with the value of the evaluated expression. 
-    <p> <img src="images/view_display_inspect.png"  alt="Pop-up containing fFull.toArray() expression"> 
-    </p>
-  </li> 
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-15.htm">Evaluating snippets</A>
-</P>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/cdebugger.htm">Debugger</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-     <a href="../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-<a href="../tasks/task-display_evaluation_result.htm">Displaying the result of evaluating an
-expression</a><br>
-<a href="../tasks/task-inspect_evaluation_result.htm">Inspecting the result of evaluating an
-expression</a></p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a></p>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm
deleted file mode 100644
index 3cf1ebb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-15.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2001, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Evaluating snippets </title>
-</head>
-<body>
-<h1> Evaluating snippets </h1>
-<p> In this section, you will evaluate Java expressions using the Java scrapbook.
-Java scrapbook pages allow you to experiment with Java code fragments before
-putting them in your program. </p>
-<ol>
-  <li> In the File menu select <STRONG>New &gt; Other &gt; Java &gt;
-	Java Run/Debug &gt; Scrapbook Page</STRONG>. You will be prompted for a folder
-    destination for the page. <p> <img src="images/wiz_new_scrap.png"  alt="Create Java Scrapbook Page wizard"> 
-    </p></li>
-  <li> In the <strong>Enter or select the folder</strong> field, type or browse below 
-    to select the <em>JUnit</em> project root directory. </li>
-  <li> In the <strong>File name</strong> field, type <em>MyScrap</em>.&nbsp; </li>
-  <li>  
-    
-    Click <strong>Finish</strong> when you are done.&nbsp; A scrapbook page
-    resource is created for you with the <em>jpage</em> file extension.&nbsp; (The <em>jpage
-    </em>file extension will be added automatically if you do not enter it yourself.)&nbsp;
-    The scrapbook page opens automatically in an editor. 
- </li>
-  <li> In the editor, type <code>System.get</code> and then use content assist (<kbd>Ctrl+Space</kbd>) 
-    to complete the snippet as <code>System.getProperties()</code>. 
-    <p> <img src="images/editor_myscrap_sysytem_get.png"  alt="Content proposals popup"> </p>
-  </li>
-  <li> Select the entire line you just typed and select <strong>Display</strong> 
-    from the context menu.&nbsp; You can also select <strong>Display Result of
-    Evaluating Selected Text</strong> from the toolbar. 
-    <p> <img src="images/editor_myscrap_display.png"  alt="Snippet editor with System.getProperties() selected showing context menu"> 
-    </p>
-  </li>
-  <li> When the evaluation completes, the result of the evaluation is displayed
-    and highlighted 
-    in the scrapbook page. </li>
-  <li> You can inspect the result of an evaluation by selecting text and
-    choosing <strong>Inspect</strong> from the context menu (or selecting <strong>Inspect
-    Result of Evaluating Selected Text</strong> from the toolbar.) </li>
-  <li> When you are finished evaluating code snippets in the scrapbook page, you
-    can close the editor.&nbsp; Save the changes in the page if you want to keep
-    the snippets for future use. </li>
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-Browsing.htm">Using the Java browsing perspective</A>
-</P>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/cdebugger.htm">Debugger</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/task-create_scrapbook_page.htm">Creating a Java scrapbook page</a><br>
-<a href="../tasks/task-display_evaluation_result.htm">Displaying the result of evaluating an
-expression</a><br>
-<a href="../tasks/task-inspect_evaluation_result.htm">Inspecting the result of evaluating an
-expression</a></p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-wizard-scrapbook.htm">New Java Scrapbook Page wizard</a><br>
-<a href="../reference/views/ref-view-scrapbook.htm">Java scrapbook page</a><br>
-<a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a></p>
-<p><a href="../notices.html"><img src="../cpy.png" border="0" alt="Legal notices" ></a>
-</p>
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm
deleted file mode 100644
index d8cc197..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-2.htm
+++ /dev/null

@@ -1,138 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Preparing Eclipse
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Preparing Eclipse
-    </h1>
-    <p>
-      In this section, you will verify that Eclipse is properly set up for Java development.
-    </p>
-    <p>
-      The following is assumed:
-    </p>
-    <ul>
-      <li>
-        You are starting with a new Eclipse installation with default settings.
-      </li>
-      <li>
-        You are familiar with the basic Eclipse workbench mechanisms, such as views and perspectives.
-      </li>
-    </ul>
-    <p>
-      If you're not familiar with the basic workbench mechanisms, please see the
-      <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm">Getting Started</a> chapter of the Workbench User Guide.
-    </p>
-    <h2>
-      Verifying JRE installation and classpath variables
-    </h2>
-    <ol>
-      <li>
-        If you still see the Eclipse Welcome page, click the arrow icon to begin using Eclipse.
-      </li>
-      <li>
-        Select the menu item
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto workbench preferences">
-        <b>Window &gt; Preferences...</b></a>
-        to open the workbench preferences.&nbsp;
-      </li>
-      <li>
-        Select the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.preferences.VMPreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the installed JREs preference page">
-        <b>Java &gt; Installed JREs</b></a>
-        preference page to display the installed Java Runtime Environments. Confirm
-        that a JRE has been detected. By default, the JRE used to run the workbench will be used to build and run 
-        Java programs. It should appear with a checkmark in the list of installed JREs. We recommend that you
-        use a Java SDK instead of a JRE. An SDK is designed for development and contains the source code for the
-        Java library, easing debugging. Additional SDKs can be added by searching the hard drive for installed
-        SDKs. To do so, simply click the <strong>Search...</strong> button and specify a root folder for the search.
-        <br>If you work with code that does not yet use generics (as we do in this tutorial), we recommend
-        that you install a Java SDK 1.4 as well, but leave the most recent version checked as default.
-		<p>
-		<img src="images/pref_jre.png"  alt="Installed JREs preference page">
-		</p>
-      </li>
-      <li>
-        Select the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the workspace preference page">
-        <strong>General &gt; Workspace</strong></a>
-        preference page. Confirm that the <strong>Build automatically</strong> option is checked.
-		<p>
-		<img src="images/pref_workspace.png"  alt="Workbench preference page">
-		</p>
-      </li>
-      <li>
-        Select the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.BuildPathPreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java build path preference page">
-        <b>Java &gt; Build Path</b></a>
-        preference page. Confirm that <strong>Source and output folder </strong> is set to <strong>Folders</strong>.
-		<p>
-		<img src="images/pref_buildpath.png"  alt="New project build patch preference page">
-		</p>
-      </li>
-      <li>
-        Select the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorPreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java editor preference page">
-        <strong>Java &gt; Editor</strong></a>
-        preference page. 
-        Confirm that  option <STRONG>Report problems as you type</STRONG>   is checked.
-		<p>
-		<img src="images/pref_editor.png"  alt="Java editor preference page">
-		</p>
-      </li>
-      <li>
-        Select the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CompliancePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java compiler preference page">
-        <strong>Java &gt; Compiler</strong></a>
-        preference page. 
-        Confirm that option <STRONG>Compiler compliance level</STRONG> matches your default JRE version (usually <strong>1.6</strong>).
-		<p>
-		<img src="images/pref_compiler.png"  alt="Java compiler settings preference page">
-		</p>
-      </li>
-      <li>
-        Click on <strong>OK</strong> to save the preferences.
-      </li>
-    </ol>
- <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-3.htm">Creating your first Java project</A>
-</P>
-<p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-       <a href="../concepts/concept-classpath-variables.htm">Classpath variables</a><br>
-       <a href="../concepts/concept-build-classpath.htm">Build classpath</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png"  alt="Related tasks">
-    </p>
-    <p>
-       <a href="../tasks/tasks-JREs.htm">Working with JREs</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a><br>
-       <a href="../reference/preferences/java/ref-preferences-editor.htm">Java Editor Preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm
deleted file mode 100644
index 9bcbf18..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-3.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Creating your first Java project
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Creating your first Java project
-    </h1>
-    <p>
-      In this section, you will create a new Java project. You will be using
-      JUnit as your example project. JUnit is an open source unit testing framework for Java.
-    </p>
-<H2>Getting the Sample Code (JUnit)</H2>
-
-
-<P>First you need to download the JUnit source code.</P>
-<OL>
-	<LI>Click <A href="http://www.eclipse.org/jdt/ui/smoke-test/junit3.8.1src.zip">here</A> to download the JUnit source code.</LI>
-	<LI>Save the archive (do not extract) to a directory from now on referenced as <em>&lt;Downloads&gt;</em>.</LI>
-	</OL>
-<H2>Creating the project</H2>
-
-<OL>
-
-	<LI>Inside Eclipse select the menu item <STRONG>File &gt; New &gt;
-	Project...</STRONG>. to open the <STRONG>New Project</STRONG> wizard
-	</LI>
-	<LI>Select <STRONG>Java Project</STRONG> then click <STRONG>Next</STRONG> 
-	to start the
-	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new Java project wizard">
-	<STRONG>New Java Project</STRONG></a> wizard:
-	<P><img src="images/wiz_new_project.png"  alt="New Java Project wizard"></P>
-	On this page,
-	<UL>
-	  <LI>type &quot;JUnit&quot; in the <STRONG>Project name</STRONG> field, and</LI>
-	  <LI>select &quot;J2SE-1.4&quot; in the <STRONG>Use an execution environment JRE</STRONG> field.</LI>
-	</UL>
-	Then click <STRONG>Finish</STRONG>. 
-	</LI>
-	<LI>In the Package Explorer, expand the <EM>JUnit</EM> project and
-	select the source folder <EM>src</EM>.</LI>
-	<LI>Select the menu item <STRONG>File &gt; Import...</STRONG>.</LI>
-	<LI>Expand <STRONG>General</STRONG>, select <STRONG>Archive file</STRONG>, and click <STRONG>Next</STRONG>.
-	</LI>
-	<LI>Click the <STRONG>Browse</STRONG> button next to the <STRONG>Archive
-	file</STRONG> field and browse to select
-	<p><em>&lt;Downloads&gt;/junit381src.jar</em></p>
-	<STRONG>Note:</STRONG> This step assumes that you followed steps 1 and 2 in the <STRONG>Getting
-	the Sample Code</STRONG> section above.<BR>
-	</LI>
-	<LI>In the Import wizard, expand the root node, press <STRONG>Deselect All</STRONG> and select only the <STRONG>junit</STRONG> node.
-	You can expand and select elements within the <EM>junit</EM>
-	directory on the left pane to view the individual resources that you
-	are importing on the right pane. <EM>Note: Do not deselect any of the
-	resources in the junit directory at this time. You will need all
-	of these resources in the tutorial.</EM>
-	<P><img src="images/wiz_import_arch.png"  alt="Import archive wizard">
-</P>
-	</LI>
-	<LI>Make sure that the JUnit project's source folder appears in the destination <STRONG>Into folder</STRONG>
-	field. Then click <STRONG>Finish</STRONG>. In the import progress
-	indicator, notice that the imported resources are compiled as they are
-	imported into the workbench. This is because the <STRONG>Build
-	automatically</STRONG> option is checked on the Workbench preferences
-	page.</LI>
-	<LI>In the Package Explorer view, expand the JUnit project and the src folder to view the
-	JUnit packages.
-	<P><img src="images/view_package_explorer_junit.png"  alt="Package explorer"></P>
-	</LI>
-</OL>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-4.htm">Browsing Java elements using the package explorer</A>
-</P>
-<p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm
deleted file mode 100644
index 9a51128..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-4.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Browsing Java elements using the package explorer
-    </title>
-  </head>
-  <body>
-    <h1>
-      Browsing Java elements using the package explorer
-    </h1>
-    <p>
-      In this section, you will browse Java elements within the JUnit project.
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer view, make sure the JUnit project and the source folder are expanded so you can see the packages.
-      </li>
-      <li>
-        Expand the package <code>junit.framework</code> to see the Java files contained in the package.
-      </li>
-      <li>
-        Expand the Java file <code>TestCase.java. </code>Note that the Package
-        Explorer shows Java-specific sub-elements of the source code file.&nbsp;
-        The public type and its members (fields and
-        methods) appear in the tree.
-        <p>
-            <img src="images/view_package_explorer_junit_exp.png"  alt="Package explorer"> 
-        </p>
-      </li>
-    </ol>
-    
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-OpenJavaEditor.htm">Opening a Java editor</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm
deleted file mode 100644
index b29472b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-6.htm
+++ /dev/null

@@ -1,137 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title> Viewing the type hierarchy</title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Viewing the type hierarchy</h1>
-<p> In this section, you will learn about using the Hierarchy view by viewing
-classes and members in a variety of different ways. </p>
-<ol>
-  <li> In the Package Explorer view, find <em>junit.framework/TestCase.java</em>. 
-    From its context menu, select
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.jdt.ui.commands.showElementInTypeHierarchyView(elementRef=JUnit/junit.framework.TestCase)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open type hierarchy">
-    <strong>Open Type Hierarchy</strong></a>.
-    You can also open type hierarchy view: 
-    <ul>
-      <li> from the menu bar by selecting <strong>Navigate &gt; Open Type 
-        Hierarchy</strong>.</li>
-      <li> from the keyboard by pressing <kbd>F4</kbd> after selecting <em>TestCase.java</em>. 
-      </li>
-    </ul>
-	<p>
-    <img src="images/view_package_explorer_open_type_hierarchy.png"  alt="Context menu">
-	</p>
-  </li>
-  <li> The buttons in the view tool bar control which part of the hierarchy is
-    shown.&nbsp; Click the&nbsp;<strong>Show the Type Hierarchy&nbsp;</strong>button 
-    to see the class hierarchy, including the base classes and subclasses. The 
-    small arrow on the left side of the type icon of TestCase indicates that the 
-    hierarchy was opened on this type.
-	<p>
-    <img src="images/view_typehierarchy_testcase_small.png"  alt="Type hierarchy"> 
-	</p>
-  </li>
-  <li> Click the <strong>Show the Supertype Hierarchy</strong> button to 
-    see a hierarchy showing the type's parent elements including implemented
-    interfaces. This view shows the results of going up the type hierarchy.
-	<p>
-    <img src="images/view_typehierarchy_testcase_supertype.png"  alt="Supertype hierarchy"> 
-	</p>
-    In this &quot;reversed hierarchy&quot; view, you can see that TestCase implements 
-    the Test interface. </li>
-  <li> Click the&nbsp;<strong>Show the Subtype Hierarchy</strong> button in the 
-    view toolbar.
-	<p>
-    <img src="images/view_typehierarchy_testcase_subtype.png"  alt="Subtype hierarchy"> 
-	</p>
-  </li>
-  <li> Click the <strong>Lock View and Show Members in Hierarchy</strong> 
-    button in the toolbar of the member pane, then select the runTest() method 
-    in the member pane. The view will now show all the types implementing runTest(). 
-	<p>
-    <img src="images/view_typehierarchy_testcase_runtest_locked.png"  alt="Subtype hierarchy showing method implementors"> 
-	</p>
-  </li>
-  <li> In the Hierarchy view, click the <strong>Show the Supertype Hierarchy</strong> 
-    button. Then on the member pane, select <code>countTestCases()</code> to display 
-    the places where this method is declared.
-	<p>
-    <img src="images/view_typehierarchy_testcase_supertype_locked.png"  alt="Supertype hierarchy showing method implementors"> 
-	</p>
-  </li>
-  <li> In the Hierarchy view select the <em>Test</em> element and select <strong>Focus 
-    On 'Test'</strong> from its context menu. <em>Test</em> is presented in the Hierarchy view. </li>
-  <li> Activate the Package Explorer view and select the package junit.framework. 
-    Use <strong>Open Type Hierarchy</strong> from its context menu. A hierarchy 
-    is opened containing all classes of the package. For completion of the tree, 
-    the hierarchy also shows some classes from other packages. These types are 
-    shown by a type icon with a white fill.
-	<p>
-    <img src="images/view_typehierarchy_testcase_focused.png"  alt="Hierarchy on a package"> 
-	</p>
-  </li>
-  <li> Use <strong>Previous Type Hierarchies</strong> to go back to a previously 
-    opened element. Click on the arrow next to the button to see a list of elements or click 
-    on the button to edit the history list.
-	<p>
-    <img src="images/view_typehierarchy_testcase_menu.png"  alt="History menu"> 
-	</p>
-  </li>
-
-
-
-
-</ol>
-<p><a name="quick_type_hierarchy"></a>
-If you are working in the editor and only want to do a quick lookup for a hierarchy you can use the
-<strong>Quick Type Hierarchy</strong>:</p>
-<ol>
-<li>Open 
-<em>junit.framework.TestCase.java</em> file in the Java editor 
-if you do not already have it open.</li>
-<li>Select the type name in the Java editor</li>
-<li>Press <kbd>Ctrl+T</kbd> or invoke <strong>Navigate &gt; Quick Type Hierarchy</strong> and the
-in-place type hierarchy view is shown.</li>
-
-<li>Pressing <kbd>Ctrl+T</kbd> while the type hierarchy view is shown will toggle between 
-supertype hierarchy and subtype hierarchy.</li>
-</ol>
-<img src="images/quicktype_dialogs.png" alt="Quicktype dialogs showing subtype and supertype hierarchy">
-<p>
-To see where a virtual method call can resolve to:
-</p>
-<ol>
-<li>In the body of <em>runBare()</em> select the invocation of
-<em>setUp()</em></li>
-<li>Press <kbd>Ctrl+T</kbd> or invoke <strong>Navigate &gt; Quick Type Hierarchy</strong> and the
-in-place type hierarchy view is shown.</li>
-<li>You can see that <em>setIup()</em> is implemented in 3 more classes. <em>Object</em> and <em>Assert</em> are
-only shown with a white filled images as are only required to complete the hierarchy but do not implement <em>setUp()</em></li>
-<li>Select a type to navigate to its implementation of <em>setUp()</em></li>
-</ol>
-<img src="images/quicktype_dialog_setup.png" alt="Quicktype dialog showing types that implement setUp()">
-
-
-
-
-
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-11.htm">Searching the workbench</A>
-</P>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concept-java-editor.htm">Java views</a> </p>
-
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/views/ref-type-hierarchy.htm">Type Hierarchy view</a><br>
-  <a href="../reference/preferences/ref-preferences-java.htm">Java Base preference page</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm
deleted file mode 100644
index 1e5766e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-7.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title> Identifying problems in your code </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Identifying problems in your code </h1>
-<p> In this section, you will review the different indicators for identifying 
-  problems in your code. </p>
-<p>Build problems are displayed in the  Problems view and annotated in the vertical
-ruler of your source code. </p>
-<ol>
-  <li> Open <em>junit.framework/TestCase.java</em> in the editor from the 
-    Package Explorer view. </li>
-  <li> Add a syntax error by deleting the semicolon at the end of the package
-    declaration in the source code. 
-    <p> <img src="images/editor_testcase_error_unsaved.png"  alt="Editor with missing semicolon"> 
-    </p>
-  </li>
-  <li> Click the <strong>Save</strong> button. The project is rebuilt
-    and the problem is indicated in several ways: 
-    <ul>
-      <li> In the  Problems view, the problems are listed, </li>
-      <li> In the Package Explorer view, the Type Hierarchy or the Outline view, 
-        problem ticks appear on the affected Java elements and their parent elements, 
-      </li>
-      <li> In the editor's vertical ruler, a problem marker is displayed near the affected line, 
-      </li>
-      <li> Squiggly lines appear under the word which might have caused the error, and</li>
-      <li> The editor tab is annotated with a problem marker. </li>
-    </ul>
-    <p><img src="images/workbench_testcase_errors.png"  alt="Problem marker in Package Explorer, editor and Tasks view"> 
-    </p>
-  </li>
-  <li> You can hover over the marked word in the editor to view a description 
-    of the problem. You can also hover over the problem markers in the vertical or overview rulers. 
-    <p> <img src="images/editor_testcase_error_hover.png"  alt="Problem marker hover"> 
-    </p>
-  </li>
-  <li> Click the <strong>Close</strong> (&quot;X&quot;) button on the editor's tab to 
-    close the editor. </li>
-  <li> In the  Problems view, select a problem in the list. Open its context menu 
-    and select <strong>Go To</strong>. The file is opened in the editor at the location of the 
-    problem. 
-    <p> <img src="images/view_problems_goto.png"  alt="Problems view"> 
-    </p>
-  </li>
-  <li> Correct the problem in the editor by adding the semicolon. Click 
-    the <strong>Save</strong> button. The project is rebuilt and the problem indicators disappear. </li>
-  <li> In the Outline view, select the method <em>getName()</em>. The editor will 
-    scroll to this method. </li>
-  <li> On the first line of the method change the returned variable <code>fName</code> 
-    to <code>fTestName</code>. While you type, a problem highlight underline appears 
-    on fTestName, to indicate a problem. Hovering over the highlighted problem 
-    will display a description of the problem and applicable quick fixes.</li>
-  <li> On the marker bar a light bulb marker appears. The light bulb signals that 
-    correction proposals are available for this problem. 
-    <p> <img src="images/editor_testcase_error_getname.png"  alt="Light bulb and problem highlight line"> 
-    </p>
-  </li>
-  <li> Click to place the cursor onto the highlighted error, and choose <strong>Quick Fix</strong> 
-    from the Edit menu bar. You can also press <kbd>Ctrl+1</kbd> or left click the light 
-    bulb. A selection dialog appears with possible corrections. 
-    <p> <img src="images/editor_testcase_error_getname_quickfix.png"  alt="Correction proposals"> 
-    </p>
-  </li>
-  <li> Select 'Change to fName' to fix the problem. The problem highlight 
-    line will disappear as the correction is applied. </li>
-  <li> Close the file without saving. </li>
-  <li> You can configure how problems are indicated on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Annotations)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the annotations preference page">
-  <strong>General &gt; Editors &gt; Text Editors &gt; Annotations</strong></a>
-  preference page.</li>
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-EditorTemplates.htm">Using code templates</A>
-</P>
-
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-  <a href="../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../concepts/concept-java-builder.htm">Java builder</a> </p>
-
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/preferences/java/ref-preferences-editor.htm">Editor preference page</a><br>
-  <a href="../reference/ref-java-editor-quickfix.htm">Quick fix</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm
deleted file mode 100644
index ef0a4cb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-8.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title> Renaming Java elements </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1> Renaming Java elements </h1>
-<p> In this section, you will rename a Java element using refactoring.&nbsp;
-Refactoring actions change the structure of your code without changing its
-semantics (behavior). </p>
-<ol>
-  <li> In the Package Explorer view, select&nbsp;<em>junit.framework/TestCase.java</em>. 
-  </li>
-  <li> From its context menu, select&nbsp;<strong>Refactor &gt; Rename</strong>. </li>
-  <li> In the&nbsp;<strong>New Name</strong> field on the Rename Compilation 
-    Unit page, type &quot;<em>TestCase2</em>&quot;. 
-    <p> <img src="images/rename_cu_dialog.png"  alt="Rename refactoring wizard"> 
-    </p>
-  </li>
-  <li> To preview the changes that will be made as a result of renaming the
-    class, press <strong>Next</strong>.
-  </li>
-  <li> The workbench analyzes the proposed change and presents you with a preview 
-    of the changes that would take place if you rename this 
-    resource.&nbsp;<p>Since renaming a compilation unit will affect the import
-    statements in other compilation units, there are other compilation units
-    affected by the change.&nbsp; These are shown in a list of changes in the
-    preview pane. </p>
-    <p> <img src="images/rename_cu_preview_dialog.png"  alt="Refactoring wizard preview page"> 
-    </p>
-  </li>
-  <li> On the Refactoring preview page, you can scroll through the proposed 
-    changes and select or deselect changes, if necessary.&nbsp; You will
-    typically accept all of the proposed changes. </li>
-  <li> Click&nbsp;<strong>Finish</strong>  to accept all proposed changes. </li>
-</ol>
-<p>You have seen that a refactoring action can cause many changes in different
-compilation units.&nbsp; These changes can be undone as a group.</p>
-<ol>
-  <li> In the menu bar, select&nbsp;<strong>Edit &gt; Undo Rename Compilation Unit</strong>. 
-    <p> <img src="images/edit_undo_refactoring_menu.png"  alt="Refactor menu"> 
-    </p>
-  </li>
-  <li> The refactoring changes are undone, and the workbench returns to its previous 
-    state. You can undo refactoring actions right up until you change and save 
-    a compilation unit, at which time the refactoring undo buffer is cleared. 
-  </li>
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-10.htm">Moving and copying Java elements</A>
-</P>
-<img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-<p> <a href="../concepts/concept-refactoring.htm">Refactoring support</a> </p>
-
-<p> <img src="../images/ngrelr.png" alt="Related reference" border="0" > 
-</p>
-<p> <a href="../reference/ref-menu-refactor.htm">Refactoring actions</a><br>
-  <a href="../reference/ref-wizard-refactorings.htm">Refactoring wizard</a><br>
-  <a href="../reference/preferences/ref-preferences-java.htm">Java preferences</a> </p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm
deleted file mode 100644
index 9ab8d55..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-9.htm
+++ /dev/null

@@ -1,119 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title> Creating a Java class </title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<h1> Creating a Java class </h1>
-<p> In this section, you will create a new Java class and add methods using 
-  code generation actions. </p>
-<ol>
-  <li> In the Package Explorer view, select the JUnit project. 
-  Click the&nbsp;<strong>New Java Package</strong> button in the toolbar, or select&nbsp;<strong>New &gt; Package</strong> from the project's 
-    context menu . </li>
-  <li> In the&nbsp;<strong>Name</strong> field, type&nbsp;<em>test</em> as the 
-    name for the new package. Then click&nbsp;<strong>Finish</strong>. </li>
-  <li> In the Package Explorer view, select the new&nbsp;<em>test</em> package 
-    and click the&nbsp;<strong>New Java Class</strong> button in the toolbar. 
-  </li>
-  <li> Make sure that&nbsp;<em>JUnit</em> appears in the&nbsp;<strong>Source Folder</strong> 
-    field and that&nbsp;<em>test</em> appears in the&nbsp;<strong>Package</strong> 
-    field. In the&nbsp;<strong>Name</strong> field, type&nbsp;<em>MyTestCase</em>. 
-    <p> <img src="images/wiz_new_class_dialog.png"  alt="Java Class wizard"> 
-    </p>
-  </li>
-  <li> Click the&nbsp;<strong>Browse</strong> button next to the&nbsp;<strong>Superclass</strong> 
-    field. </li>
-  <li> In the&nbsp;<strong>Choose a type</strong> field in the Superclass Selection 
-    dialog, type&nbsp;<em>Test</em> to narrow the list of available superclasses. 
-    <p> <img src="images/superclass_selection_dialog.png"  alt="Superclass Selection dialog"> 
-    </p>
-  </li>
-  <li> Select the&nbsp;<em>TestCase</em> class and click&nbsp;<strong>OK</strong>. 
-  </li>
-  <li> Select the checkbox for&nbsp;<strong>Constructors from superclass</strong>. 
-  </li>
-  <li> Click&nbsp;<strong>Finish</strong> to create the new class. 
-    <p> <img src="images/wiz_new_class_dialog_superchecked.png"  alt="Java Class wizard"> 
-    </p>
-  </li>
-  <li> The new file is opened in the editor. It contains the new class,
-    the constructor and comments.&nbsp; You can select options for the creation and
-    configuration of generated comments in the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeTemplatePreferencePage)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the code templates preference page">
-    <strong>Java &gt; Code Style &gt; Code Templates</strong></a>
-    preference page.</li>
-  <li> In the Outline view select the new class&nbsp;<em>MyTestCase</em>. Open 
-    the context menu and select&nbsp;<strong>Source &gt; Override/Implement Methods...</strong>. 
-    <p> <img src="images/editor_mytestcase_outline_override.png"  alt="Context menu of a type"> 
-    </p>
-  </li>
-  <li> In the Override Methods dialog, check <em>setUp()</em> and <em>tearDown()</em>
-    and click&nbsp;<strong>OK</strong>. Two methods are added to the class. 
-    <p> <img src="images/override_implement_dialog.png"  alt="Override Methods dialog"> 
-    </p>
-  </li>
-  <li> Change the body of <em>setUp()</em> to <code>container= new Vector();</code> </li>
-  <li> <em>container</em> and <em>Vector</em> are underlined with a problem 
-    highlight line as they cannot be resolved. A light bulb appears on the marker 
-    bar. Move the mouse over the underlined word <em>Vector</em>. A hover appears that
-    shows the error message and contains quick fixes. Move the mouse into the hover and
-    click <em>Import 'Vector' (java.util)</em>. This adds the missing import declaration. 
-    <p> <img src="images/editor_mytestcase_import.png"  alt="Correction proposals hover for Vector"><br>
-    </p>
-    The blinking cursor should still be on the line that contains the error (if not, set it to the end of the line).
-    Press <kbd>Ctrl+1</kbd>. This lets the cursor jump to the nearest error location and opens the quick fix proposals.
-    Choose <em>Create field 'container'</em> to add the new field. 
-    <p> <img src="images/editor_mytestcase_field.png"  alt="Correction proposals for container"> 
-    </p>
-  </li>
-  <li> In the Outline view, select the class <em>MyTestCase</em>. Open the 
-    context menu and select <strong>Source &gt; Generate Getters and Setters...</strong>. 
-    <p> <img src="images/editor_mytestcase_getters.png"  alt="Generate Getter and Setter in context menu"> 
-    </p>
-  </li>
-  <li> The Generate Getter and Setter dialog suggests that you create the methods getContainer 
-    and setContainer. Select both and click <strong>OK</strong>. A getter 
-    and setter method for the field container are added. 
-    <p> <img src="images/generate_getter_setter_dialog.png"  alt="Generate Getter and Setter dialog"> 
-    </p>
-  </li>
-  <li> Save the file. </li>
-  <li> The formatting of generated code can be configured in the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeFormatterPreferencePage)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the code style formatter perference page">
-    <strong>Java &gt; Code Style &gt; Formatter</strong></a> preference page.
-    If you use a prefix or suffix for field names (e.g. fContainer), you can specify this in the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeStylePreferencePage)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the code style preference page">
-    <strong>Java &gt; Code Style</strong></a> preference page so that generated
-    getters and setters will suggest method names without the prefix or suffix. 
-  </li>
-</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-8.htm">Renaming Java elements</A>
-</P>
-<img src="../images/ngrelc.png"  alt="Related concepts" border="0"> 
-<p> <a href="../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../concepts/concept-java-editor.htm">Java editor</a> </p>
-<p> <img src="../images/ngrelr.png"  alt="Related reference" border="0"> 
-</p>
-<p> <a href="../reference/ref-wizard-class.htm">New Java Class wizard</a><br>
-  <a href="../reference/ref-menu-source.htm">Source actions</a><br>
-  <a href="../reference/ref-java-editor-quickfix.htm">Quick fix</a><br>
-  <a href="../reference/ref-dialog-override-method.htm">Override methods dialog</a><br>
-  <a href="../reference/ref-dialog-gettersetter.htm">Generate Getter and Setter dialog</a><br>
-  <a href="../reference/preferences/java/codestyle/ref-preferences-formatter.htm">Code formatter preference page</a><br>
-  <a href="../reference/preferences/java/ref-preferences-code-style.htm">Code style preference page</a><br>
-  <a href="../reference/preferences/java/codestyle/ref-preferences-code-templates.htm">Code templates preference page</a><br>
-</p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm
deleted file mode 100644
index 123cd4a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-AddMethod.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Adding new methods
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Adding new methods
-    </h1>
-    <ol>
-      <li>
-        Start adding a method by typing the following at the end of the <em>VectorTest.java</em> file (but before the closing 
-        brace of the type) in the Java editor:<br>
-        <code>public void testSizeIsThree()</code><br>
-		As soon as you type the method name in the editor area, the new method appears at the bottom of the Outline view. 
-		<p>
-		<img src="images/editor_vectortest_testSizeIsThree.png"  alt="New method in outline view">
-		</p>
-		In addition,
-		<ul>
-		  <li>error annotations (red boxes) appear in the overview ruler positioned on the right hand side of the editor,</li>
-		  <li>error icons appear in the vertical ruler positioned on the left of the editor,</li>
-		  <li>an error indicator appears in the top right corner of the editor,</li>
-		  <li>errors are marked in the text.</li>
-		</ul>
-		These error annotations indicate that the compilation unit is currently not correct. If you hover
-		over the error in the text, a tool tip appears: <em>Syntax error on token &quot;)&quot;, 
-		{ expected after this token</em>. This is correct since the method doesn't have a body yet. Note that error 
-		annotations in the editor are updated as you type. This behavior can be controlled via  the
-		<STRONG>Report problems as you type</STRONG> option located on the
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorPreferencePage)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the Java editor preference page">
-		<strong>Java &gt; Editor</strong></a> preference page.
-		<p>
-		<img src="images/editor_vectortest_problem_hover.png"  alt="Error annotations in vertical and overview ruler">
-		</p>
-		
-      </li>
-      <li>
-        Click the <strong>Save</strong> button. The compilation unit is compiled automatically and errors appear in the 
-        Package Explorer view, in the Problems view and on the vertical ruler (left hand side of the editor). In the Package 
-        Explorer view, the errors are propagated up to the project of the compilation unit containing the error.
-		<p>
-		<img src="images/view_package_explorer_vectortest_error.png"  alt="Error propagation in package explorer">
-		</p>
-      </li>
-      <li>
-        Complete the new method by typing the following:<br>
-        <p><code>
-          {<br>
-          &nbsp; //TODO: Check size<br>
-        </code></p>
-        Note that the closing curly brace has been inserted automatically.
-      </li>
-      <li>
-        Save the file. Notice that the error indicators disappear since the
-        missing brace has been added.
-      </li>
-    </ol>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-ContentAssist.htm">Using content assist</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/preferences/java/ref-preferences-editor.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm
deleted file mode 100644
index abdbb78..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Basic tutorial
-    </title>
-  </head>
-  <body>
-    <h1>
-      Basic tutorial
-    </h1>
-    <p>
-      This tutorial provides a step by step walk-through of the Java development tools.
-    </p>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-2.htm">Preparing the workbench</A>
-</P>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm
deleted file mode 100644
index 866eb02..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Browsing.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using the Java browsing perspective
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Using the Java browsing perspective
-    </h1>
-    <p>
-      In this section you will use the Java browsing perspective to browse and
-      manipulate your code. <a href="qs-4.htm">Browsing Java elements with the 
-      Package Explorer</a> gives an overview of using the Package Explorer to browse
-      elements. In contrast to the Package Explorer, which organizes all Java elements
-      in a tree, consisting of projects, packages, compilation units, types, etc., the
-      browsing perspective uses distinct views to present the same information. Selecting 
-      an element in one view, will show its content in another view.
-    </p> 
-    <p>To open a browsing perspective activate
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaBrowsingPerspective)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Java browsing perspective">
-      <strong>Window &gt; Open Perspective &gt; Java Browsing</strong></a> from 
-      within the Java perspective or use the context menu of the <strong>Open a Perspective
-      </strong> toolbar button.
-    </p>
-    <p>
-	  <img src="images/workbench_java_browsing.png"  alt="Java browsing perspective">
-    </p>
-    <p>
-      The views of the perspective are connected to each other in the following ways:</p>
-      <ul>
-        <li>
-          Selecting an element in the <strong>Projects</strong> views shows its packages
-          in the <strong>Packages</strong> view.
-        </li>
-        <li>
-          The <strong>Types</strong> view shows the types contained in the package selected
-          in the <strong>Packages</strong> view.
-        </li>
-        <li>
-          The <strong>Members</strong> view shows the members of a selected type. Functionally,
-          the <strong>Members</strong> view is comparable to the <strong>Outline</strong> view used in the normal Java
-          perspective.
-        </li>
-        <li>
-          Selecting an element in the <strong>Members</strong> view reveals the element in the editor. If there
-          isn't an editor open for the element, double-clicking on the element will open a corresponding editor.
-        </li>
-      </ul>
-    <p>
-      All four views are by default linked to the active editor. This means that the views will adjust 
-      their content and their selection according to the file presented in the active editor. The 
-      following steps illustrate this behavior:</p>
-      <ol>
-        <li>
-          Select <em>junit.extensions</em> in the <strong>Packages</strong> view.
-        </li>
-        <li>
-          Open type <em>TestSetup</em> in the editor by double-clicking it in the <strong>Types view</strong>.
-        </li>
-        <li>
-          Now give back focus to the editor opened on file <em>TestCase.java</em> by clicking on the
-          editor tab. The <strong>Packages</strong>, <strong>Types</strong> and <strong>
-          Members</strong> view adjust their content and selections to reflect the active editor. The
-          <strong>Packages</strong> view's selection is set to <em>junit.framework</em> and the <strong>
-          Types</strong> view shows the content of the <em>junit.framework</em> packages. In addition,
-          the type <em>TestCase</em> is selected.
-        </li>
-      </ol>
-    <p>
-      Functionally, the Java browsing perspective is fully comparable to the Java perspective.
-      The context menus for projects, packages, types, etc. and the global menu and tool bar are the same.
-      Therefore activating these functions is analogous to activating them in the Java perspective.
-    </p>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-junit.htm">Writing and running JUnit tests</A>
-</P>
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm
deleted file mode 100644
index 8fac13d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ContentAssist.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using content assist
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using content assist
-    </h1>
-    <p>
-      In this section you will use <em>content assist</em> to finish writing a new
-      method. Open the file <em>junit.samples/VectorTest.java</em> in the Java
-      editor if you do not already have it open and select the <code>testSizeIsThree()</code> method
-      in the Outline view. If the file doesn't contain such a method see <a href="qs-AddMethod.htm">Adding new methods</a>
-      for instructions on how to add this method.
-    </p>
-    <ol>
-      <li>
-        Replace the <tt>TODO</tt> comment with the following lines.
-        <p>
-          <code>
-            assertTrue(fFull.size() == 3);<br>
-            Vector v = new Vector();<br>
-            for (int i=0; i&lt;3; i++)<br>
-            &nbsp;&nbsp;v.addElement(new Object());<br>
-            assert<br>
-          </code>
-        </p>  
-      </li>
-      <li>
-        With your cursor at the end of the word <code>assert</code>, press <kbd>Ctrl+Space</kbd> to activate content assist. The content assist window with a list of
-        proposals will appear. Scroll the list to see the available choices.
-		<p>
-		<img src="images/editor_vectortest_content_assist.png"  alt="Content assist">
-		</p>
-      </li>
-      <li>
-        With the content assist window still active, type the letter 't'
-        in the source code after <code>assert</code> (with no space in between). The list is narrowed and only shows entries
-        starting with 'assert'. Single-click various items in the list to view any available Javadoc help for each item.
-		<p>
-		<img src="images/editor_vectortest_content_assist_t.png"  alt="Content assist filtered">
-		</p>
-      </li>
-      <li>
-        Select <code>assertTrue(boolean)</code> from the list and press <kbd>Enter</kbd>. The code for the <code>assertTrue(boolean)</code> method is inserted.
-      </li>
-      <li>
-        Complete the line so that it reads as follows:<br>
-        <p><code>
-        assertTrue(v.size() == fFull.size());
-        </code></p>
-      </li>
-      <li>
-        Save the file.
-      </li>
-    </ol>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-7.htm">Identifying problems in your code</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/ref-java-editor-code-assist.htm">Java Content Assist</a><br>
-       <a href="../reference/preferences/java/ref-preferences-editor.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm
deleted file mode 100644
index 73bafa6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-DetectingExistingLayout.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Detecting existing layout
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Detecting existing layout
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The source files for a product are laid out in one directory "src".</li>
-	<li>The class files are in another directory "bin".
-	<p><img src="images/qs-DetectingExistingLayout1.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-    <ol>
-    <li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open new Java project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;Product&quot; in the <strong>Project name</strong> field.</p>
-    </li>
-    <li>
-    	<p>In <strong>Project layout</strong> group, change selection to <strong>Create separate source and output folders</strong>.</p>
-    	<p>In <strong>Contents</strong> group, change selection to <strong>Create project from existing source</strong>.</p>
-    	<p>Click <strong>Browse...</strong> and choose the <i><code>Product</code></i> directory on drive <i><code>D:</code></i>.</p>
-		<p><img src="images/qs-DetectingExistingLayout2.png"  alt="New Java Project wizard"></p>
-    </li>
-    <li>
-     	<p>Click <strong>Next</strong>.</p>
-     	<p>Ensure that the source and output folders are detected.</p>
-		<p><img src="images/qs-DetectingExistingLayout3.png"  alt="Java Project Source setup"></p>
-		<p>
-			<em>Warning: </em>If the <strong>Scrub output folders when cleaning projects</strong> preference in the
-			<strong>Output folder</strong> section of the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaBuildPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the building preference page">
-			<strong>Java &gt; Compiler &gt; Building</strong></a> preference page
-			is checked, clicking <strong>Finish</strong> will scrub the &quot;bin&quot; directory in the file system before
-			generating the class files.		</p>
-    </li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-    <li>
-    	You now have a Java project with a &quot;src&quot; folder which contains the sources of the &quot;Product&quot; directory.
-		<p><img src="images/qs-DetectingExistingLayout4.png"  alt="Created Java project in Workspace"></p>
-    </li>
-	</ol>
-	<p>
-		<em>Note: </em>This solution creates a &quot;.project&quot; file and a &quot;.classpath&quot; file in the 
-		&quot;Product&quot; directory. If you do not wish to have these files in the &quot;Product&quot; directory,
-		you should use linked folders as shown in the 
-		<a href="qs-WorkingWithExistingLayout1.htm">Sibling products in a common source tree</a> section.
-	</p>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-OrganizingSources.htm">Organizing sources</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm
deleted file mode 100644
index aa5f38f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-EditorTemplates.htm
+++ /dev/null

@@ -1,129 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using code templates
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using code templates
-    </h1>
-    <p>
-      In this section you will use content assist to fill in a template for a common loop structure. 
-      Open <em>junit.samples/VectorTest.java</em> file in the Java editor if you do not already 
-      have it open.
-    </p>
-    <ol>
-      <li>
-        Start adding a new method by typing the following:<br>
-        <p><code>
-        public void testValues() {<br>
-        &nbsp;&nbsp;&nbsp; Integer[] expected= new Integer[3];<br>
-        &nbsp;&nbsp;&nbsp; for<br>
-        </code></p>
-      </li>
-      <li>
-        With the cursor at the end of <code>for</code>, press <kbd>Ctrl+Space</kbd> to enable content assist.&nbsp;
-        You will see a list of common templates for &quot;for&quot; loops.&nbsp;
-        When you single-click a template, or select it with the <kbd>Up</kbd> or <kbd>Down</kbd>
-        arrow keys, you'll see the code for the template in
-        its help message.&nbsp; Note that the local array name is guessed automatically.
-		<p>
-		<img src="images/editor_vectortest_for_template.png"  alt="Content assist for for">
-		</p>
-      </li>
-      <li>
-        Choose the <code>for - iterate over array</code>  entry and press <kbd>Enter</kbd> to confirm the template.&nbsp;
-        The template will be inserted in your source code.
-		<p>
-		<img src="images/editor_vectortest_for_template_exp.png"  alt="Inserted for template">
-		</p>
-      </li>
-      <li>
-        Next we change the name of the index variable from <em>i</em> to <em>e</em>. To do so simply press <kbd>e</kbd>, as
-        the index variable is automatically selected. 
-        Observe that the name of the index variable changes at all places. When inserting a template all references to the same variable
-        are connected to each other. So changing one changes all the other values 
-        as well.
-		<p>
-		<img src="images/editor_vectortest_for_template_exp_e.png"  alt="Altered for template">
-		</p>
-      </li>
-      <li>
-        Pressing the <kbd>tab</kbd> key moves the cursor to the next variable of the code template. This is the array
-        <em>expected</em>.
-		<p>
-		<img src="images/editor_vectortest_for_template_exp_expected.png"  alt="Altered for template">
-		</p>
-        Since we don't want to change the name (it was guessed right by the template) we press
-        tab again, which leaves the template since there aren't any variables left to edit.
-      </li>
-      <li>
-        Complete the <code>for</code> loop as follows:<br>
-        <p><code>
-        for (int e= 0; e &lt; expected.length; e++) {<br>
-        &nbsp;&nbsp;&nbsp; expected[e]= new Integer(e + 1);<br>
-        }<br>
-        Integer[] actual= to<br>
-        </code></p>
-      </li>
-      <li>
-        With the cursor at the end of <code>to</code>, press <kbd>Ctrl+Space</kbd> to enable content assist. Pick <code>toarray - convert collection to array</code>
-        and press <kbd>Enter</kbd> to confirm the selection (or double-click the
-        selection).
-		<p>
-        <img src="images/editor_vectortest_toarray_template.png"  alt="toarray template">
-		</p>
-		The template is inserted in the editor and <code>type</code> is highlighted and selected.
-		<p>
-		<img src="images/editor_vectortest_toarray_template_exp.png"  alt="Inserted toarray template">
-		</p>
-      </li>
-      <li>
-        Overwrite the selection by typing <code>Integer</code>. The type of array constructor changes
-        when you change the selection.
-      </li>
-      <li>
-        Press <kbd>Tab</kbd> to move the selection to <code>collection</code> and
-        overwrite it by typing <code>fFull</code>.
-		<p>
-		<img src="images/editor_vectortest_toarray_template_integer.png"  alt="Inserted toarray template">
-		</p>
-      </li>
-      <li>
-        Add a semicolon and the following lines of code to complete the method:<br>
-        <p><code>
-        assertEquals(expected.length, actual.length);<br>
-        for (int i= 0; i &lt; actual.length; i++)<br>
-        &nbsp;&nbsp;&nbsp; assertEquals(expected[i], actual[i]);<br>
-        </code></p>
-      </li>
-      <li>
-        Save the file.
-      </li>
-    </ol>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-OrganizeImports.htm">Organizing import statements</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-       <a href="../concepts/concept-editor-templates.htm">Templates</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/preferences/java/editor/ref-preferences-templates.htm">Templates Preferences</a><br>
-       <a href="../reference/preferences/java/ref-preferences-editor.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm
deleted file mode 100644
index 717d21f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ExtractMethod.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Extracting a new method
-    </title>
-  </head>
-  <body>
-    <h1>
-      Extracting a new method
-    </h1>
-    <p>
-      In this section, you will improve the code of the constructor of <em>junit.framework.TestSuite</em>. 
-      To make the intent of the code clearer, you will extract the code that collects test cases 
-      from base classes into a new method called <em>collectTestMethods</em>.
-    </p>
-    <ol>
-      <li>
-        In the <em>junit.framework/TestSuite.java</em> file, select the following range of
-        code inside the <em>TestSuite(Class)</em> constructor:<br>
-        <p><code>
-        Class superClass= theClass;<br>
-        Vector names= new Vector();<br>
-        while(Test.class.isAssignableFrom(superClass)) {<br>
-        &nbsp;&nbsp;&nbsp; Method[] methods= superClass.getDeclaredMethods();<br>
-        &nbsp;&nbsp;&nbsp; for (int i= 0; i &lt; methods.length; i++) {<br>
-        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; addTestMethod(methods[i],names, constructor);<br>
-        &nbsp;&nbsp;&nbsp; }<br>
-        &nbsp;&nbsp;&nbsp; superClass= superClass.getSuperclass();<br>
-        }</code></p>
-      </li>
-      <li>
-        From the selection's context menu in the editor, select <strong>Refactor &gt; Extract Method...</strong>.
-		<p>
-		<img src="images/editor_testsuite_extract_method.png"  alt="Context menu extract method">
-		</p>
-      </li>
-      <li>
-        In the <strong>Method Name</strong> field, type <em>collectInheritedTests</em>.
-		<p>
-		<img src="images/extract_method_dialog.png"  alt="Extract method wizard data input page">
-		</p>
-      </li>
-      <li>
-        To preview the changes, press <strong>Preview&gt;</strong>.The preview page displays the 
-        changes that will be made. Press <strong>OK</strong> to extract the method.
-		<p>
-		<img src="images/extract_method_preview_dialog.png"  alt="Extract method preview page">
-		</p>
-      </li>
-      <li>
-        Go to the extracted method by selecting it in the Outline view.
-		<p>
-		<img src="images/editor_testsuite_outline_collectinheritedmethod.png"  alt="Extracted method">
-		</p>
-      </li>
-    </ol>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-9.htm">Creating a Java class</A>
-</P>
-    <p>
-      <img src="../images/ngrelc.png"  border="0" alt="Related concepts">
-    </p>
-    <p>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-       <a href="../concepts/concept-refactoring.htm">Refactoring support</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/preferences/ref-preferences-java.htm">Java Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm
deleted file mode 100644
index b58d291..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-LocalHistory.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using the local history
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the local history
-    </h1>
-    <p>
-      In this section, you will use the local history feature to switch to a previously saved version of an individual 
-      Java element.
-    </p>
-    <ol>
-      <li>
-        Open <em>junit.samples/VectorTest.java</em> file in the Java editor and select the method
-        <em>testCapacity()</em> in the Outline view.
-      </li>
-      <li>
-      	Change the content of the method so that the 'for' statements reads as:<br>
-      	<p><code>
-      	for (int i= 0; i &lt; 99; i++)
-      	</code></p>
-	    Save the file by pressing <kbd>Ctrl+S</kbd>.
-      </li>
-      <li>
-        In the Outline view, select the method <code>testCapacity()</code>, and from its context menu, select <strong>Replace
-        With &gt; Element from Local History</strong>.
-      </li>
-      <li>
-        In the <strong>Replace Java Element from Local History</strong> dialog, the Local History list 
-        shows the various saved states of the method. The Java Source Compare pane shows details of the 
-        differences between the selected history resource and the existing workbench resource.
-		<p>
-		<img src="images/replace_local_element.png"  alt="Replace from local history">
-		</p>
-      </li>
-      <li>
-       In the top pane, select the previous version, and click the <strong> Replace 
-       button</strong>. In the Java editor, the method is replaced with the selected history version.
-      </li>
-      <li>
-        Save the file.
-      </li>
-      <li>
-        Beside replacing a method's version with a previous one you can also restore Java elements that were 
-        deleted. Again, select the method <em>testCapacity()</em> in the Outline view, and from its context
-        menu, select <strong>Delete</strong>. Confirm the resulting dialog with <strong>Yes</strong> and
-        save the file. 
-      </li>
-      <li>
-        Now select the type <em>VectorTest</em> in the Outline view, and from its context menu, select
-        <strong>Restore from Local History...</strong>. Select and check the method <em>testCapacity()</em>
-        in the Available Java Elements pane. As before, the Local History pane shows the versions saved 
-        in the local history.
-		<p>
-		<img src="images/restore_local_history.png"  alt="Restore from local history">
-		</p>
-      </li>
-      <li>
-        In the Local History pane, select the earlier working version and then click <strong>Restore</strong>.
-      </li>
-    </ol>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-ExtractMethod.htm">Extracting a new method</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-62.htm">Using the local history</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm
deleted file mode 100644
index f5fa283..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Navigate.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Navigate to a Java element's declaration
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Navigate to a Java element's declaration
-    </h1>
-	<p> In this section, you will learn how to open a type in the Java Editor and
-	how to navigate to related types and members. </p>
-	<ol>
-	  <li> Open the <strong>Open Type</strong> dialog by pressing <kbd>Ctrl+Shift+T</kbd>, choosing
-	    <strong>Navigate &gt; Open Type...</strong>, or clicking the toolbar icon
-	    (<img src="../images/org.eclipse.jdt.ui/etool16/opentype.png" alt="Open Type toolbar button">).
-	    Type <kbd>Money</kbd>, press the <kbd>Arrow Down</kbd> key a few times to select
-	    <em>MoneyTest</em>, and then press <kbd>Enter</kbd> to open the type in the Java editor. 
-	    <p>
-	      <img src="images/navigate_opentype.png"  alt="Open Type dialog">
-	    </p>
-	  </li>
-	  <li> On the first line of the <em>MoneyTest</em> class declaration, select the
-	    superclass <em>TestCase</em> and either 
-	    <ul>
-	      <li> from the menu bar select <strong>Navigate &gt; Open Declaration</strong> or </li>
-	      <li> press <kbd>F3</kbd>. </li>
-	    </ul>	    
-		<p>
-	    <img src="images/navigate_opendeclaration.png"  alt="Menu open declaration">
-		</p>
-	    The TestCase class opens in the editor area and is also represented in 
-	    the Outline view. <br><em>Note: This command also works on methods and fields.</em>
-		<p>
-	    <img src="images/editor_testcase.png"  alt="Opened declaration">
-		</p>
-	  </li>
-	  <li> With the <em>TestCase.java</em> editor open and the class declaration
-	    selected: 
-	    <ul>
-	      <li> from the menu bar select <strong>Navigate &gt; Open Type Hierarchy</strong> or </li>
-	      <li> press <kbd>F4</kbd>. </li>
-	    </ul>
-		<p>
-	    <img src="images/navigate_open_typehieracrchy.png"  alt="Menu open type hierarchy">
-		</p>
-	  </li>
-	  <li> 
-	    The Hierarchy view opens with the TestCase class displayed.
-		<p>
-	    <img src="images/view_typehierarchy_testcase.png"  alt="Type hierarchy view">
-		</p>
-	    <em>Note: You can also open editors on types and methods in the Hierarchy view.</em> 
-	  </li>
-	</ol>
-	<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-6.htm">Viewing the type hierarchy</A>
-</P>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/views/ref-type-hierarchy.htm">Type Hierarchy View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm
deleted file mode 100644
index 8473541..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OpenJavaEditor.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Opening a Java editor
-    </title>
-  </head>
-  <body>
-    <h1>
-      Opening a Java editor
-    </h1>
-    <p>
-      In this section, you will learn how to open an editor for Java files.  You will also learn about some of the basic Java editor features.
-    </p>
-		<ol>
-		  <li> Expand the package <em>junit.samples</em> and select the file <em>VectorTest.java</em>.
-		    You can open <em>VectorTest.java</em> in the Java editor by double clicking on
-		    it. In general you can open a Java editor for Java files, types, methods and fields by simply double 
-		    clicking on them. For example, to open the editor directly on the method <em>testClone</em>
-		    defined in <em>VectorTest.java</em>, expand the file in the Package Explorer and double click on the method.</li>
-		  <li> Notice the syntax highlighting. Different kinds of elements in the
-		    Java source are rendered in unique colors.&nbsp; Examples of Java source
-		    elements that are rendered differently are: 
-		    <ul>
-		      <li> Regular comments </li>
-		      <li> Javadoc comments </li>
-		      <li> Keywords </li>
-		      <li> Strings </li>
-		    </ul>
-			<p>
-		    <img src="images/editor_vectortest.png"  alt="Syntax highlighting">
-			</p>
-		  </li>
-		  <li> Look at the Outline view. It displays an outline of the Java file including 
-		    the package declaration, import declarations, fields, types and methods. The 
-		    Outline view uses icons to annotate Java elements.&nbsp; For example, icons indicate whether a Java element is 
-		    static (<img src="../images/org.eclipse.jdt.ui/ovr16/static_co.png" alt="S" >), 
-		    abstract (<img src="../images/org.eclipse.jdt.ui/ovr16/abstract_co.png" alt="A" >),
-		    or final (<img src="../images/org.eclipse.jdt.ui/ovr16/final_co.png" alt="F" >).&nbsp; Different icons show you whether a method overrides a method from a 
-		    base class (<img src="../images/org.eclipse.jdt.ui/ovr16/over_co.png"  alt="overridden">
-) or 
-		    when it implements a method from an interface (<img src="../images/org.eclipse.jdt.ui/ovr16/implm_co.png"  alt="implements">
-).
-			<p>	
-		    <img src="images/view_outline_vectortest.png"  alt="Outline view">
-			</p>
-		  </li>
-		  <li> Toggle the <strong>Hide Fields</strong>, <strong>Hide Static Members</strong>, 
-		    and <strong>Hide Non-Public Members</strong> buttons in the Outline view toolbar 
-		    to filter the view's display.
-			Before going to the next step make sure that the <STRONG>Hide Non-Public
-	Members</STRONG> and <STRONG>Hide Static Fields and Methods</STRONG>
-	buttons are not pressed.<p>
-			<img src="images/view_outline_vectortest_filtered.png"  alt="Outline view tool bar"> 
-			</p>
-		  </li>
-		  <li>In the Outline view, select different 
-		    elements and note that they are again displayed in a whole file view 
-		    in the editor. The Outline view selection now contains a range indicator 
-		    on the vertical ruler on the left border of the Java editor that indicates
-		    the range of the selected element.
-			<p>
-			<img src="images/editor_vectortest_outline_main.png"  alt="Range indicator"> 
-			</p>
-		  </li>
-		</ol>
-	<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-Quickviews.htm">Using quick views</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-      <a href="../concepts/concept-java-views-sorting.htm">Sorting elements in Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/views/ref-view-outline.htm">Java Outline View</a><br>
-       <a href="../reference/preferences/java/ref-preferences-editor.htm">Java Editor Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm
deleted file mode 100644
index 8a04ef7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizeImports.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Organizing import statements
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Organizing import statements
-    </h1>
-    <p>
-      In this section you will organize the import declarations in your
-      source code.&nbsp; Open <em>junit.samples/VectorTest.java</em> file in the Java
-      editor if you do not already have it open.
-    </p>
-    <ol>
-      <li>
-        Delete the import declarations by selecting them in the Outline view and selecting 
-        <strong>Delete</strong> from the context menu. Confirm the resulting dialog with
-        <strong>Yes</strong>.
-        You will see numerous compiler warnings in the vertical ruler since the
-        types used in the method are no longer imported.
-		<p>
-		<img src="images/view_outline_delete_import.png"  alt="Outline view context menu">
-		</p>
-      </li>
-      <li>
-        From the context menu in the editor, select <strong>Source &gt; Organize Imports</strong>. The required import statements are added to the beginning of your code below the package
-        declaration.
-		<p>
-		<img src="images/editor_vectortest_organized_imports.png"  alt="Organize imports">
-		</p>
-        You can also choose <strong>Organize Imports</strong> from the context menu of the
-        import declarations in the Outline view.<br>
-        Note: You can specify the order of the import declarations using the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ImportOrganizePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Goto the organize imports preference page">
-        <strong>Java &gt; Code Style &gt; Organize Imports</strong></a>
-        preference page.
-      </li>
-      <li>
-        Save the file.
-      </li>
-    </ol>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-LocalHistory.htm">Using the local history</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-       <a href="../reference/preferences/java/codestyle/ref-preferences-organize-imports.htm">Organize Imports Preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm
deleted file mode 100644
index 64e6321..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-OrganizingSources.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Organizing sources
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Organizing sources
-    </h1>
-
-    <h3>Layout on file system</h3>
-    <ul>
-    <li>
-		In this section, you will create a new Java project and organize your sources in separate folders. This will 
-		prepare you for handling more complex layouts.
-    </li>
-	<li>Let's assume you want to put your sources in one folder and your tests in another folder:
-	<p><img src="images/qs-OrganizeSources1.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-    <ol>
-    <li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;MyProject&quot; in the <strong>Project name</strong> field.</p>
-    </li>
-    <li>
-    	<p>In <strong>Project layout</strong> group, change selection to <strong>Create separate source and output folders</strong>
-    	and edit <strong>Configure default...</strong> to modify <strong>Source folder name</strong> from "src" to "sources".</p>
-		<p><img src="images/qs-OrganizeSources2.png"  alt="Build Path Preferences page"></p>
-    </li>
-    <li>
-    	Click <strong>OK</strong> to return on New Java Project wizard and then click <strong>Next</strong>.
-		<p><img src="images/qs-OrganizeSources3.png"  alt="Java Project Source setup"></p>
-	</li>
-    <li>
-		<p>To add another source folder to your project, click <strong>Create new source folder</strong> link in <strong>Details</strong> pane
-		or button <img src="images/packagefolder_obj.png" alt="Create a new Source Folder for the Project"> in view bar.</p>
-	</li>
-	<li>
-		<p>In <strong>New Source Folder</strong> dialog, type &quot;tests&quot; in the <strong>Folder name</strong> field.</p>
-    	<p><img src="images/qs-OrganizeSources4.png"  alt="New Source Folder dialog"></p>
-    </li>
-	<li>
-		Click <strong>Finish</strong> to validate and close the dialog.
-	</li>
-    <li>
-    	<p>Your project setup now looks as follows:</p>
-	    <p><img src="images/qs-OrganizeSources5.png"  alt="Java Project Sources final setup"></p>
-    </li>
-    <li>
-    	Click <strong>Finish</strong>
-    </li>
-    <li>
-    	You now have a Java project with two source folders: <i><code>sources</code></i> and <i><code>tests</code></i>. You can start adding classes
-    	to these folders or you can copy them using drag and drop.
-	    <p><img src="images/qs-OrganizeSources6.png"  alt="Created Java project in Workspace"></p>
-    </li>
-	</ol>    
-	<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-WorkingWithExistingLayout1.htm">Sibling products in a common source tree</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm
deleted file mode 100644
index 9e3b778..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-ProjectConfiguration.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Project configuration tutorial
-    </title>
-  </head>
-  <body>
-    <h1>
-    	Project configuration tutorial
-    </h1>
-    <p>
-    	In this section, you will create and configure a new Java project to use source folders and 
-    	to match some existing layout on the file system. Some typical layouts have been identified. 
-    	Choose the sub-section that matches your layout. 
-    </p>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-DetectingExistingLayout.htm">Detecting existing layout</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Quickviews.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Quickviews.htm
deleted file mode 100644
index 58dc3e4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-Quickviews.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Using quick views </title>
-</head>
-<body>
-<h1> Using quick views </h1>
-<p> 
-In this section, you will be introduced to the quick outline view. Quick views are in-place views which 
-are shown on top of the editor area and can easily be controlled using the keyboard. A second quick view will
-be introduced in the <a href="qs-6.htm#quick_type_hierarchy">Type Hierarchy section</a>.
-</p>
-<h2>Quick Outline <a name="quick_outline"></a></h2>
-<p>To use the quick outline view in the Java editor:</p>
-<ol>
-<li>Open 
-<em>junit.samples.VectorTest.java</em> file in the Java editor 
-if you do not already have it open.</li>
-<li> Press <kbd>Ctrl+O</kbd> or select <strong>Navigate &gt; Quick Outline</strong> and 
-you will see an in-place outline of the current source file. <br>
-<img src="images/editor_vectortest_quickoutline.png" alt="Quick outline of VectorTest"> </li>
-
-<li>Press <kbd>Ctrl+O</kbd> a second time and all inherited fields, 
-types and methods are shown as well. Inherited members are shown in grey. </li>
-
-<li>Start typing while the quick outline view is shown to filter the list of displayed elements.
-Further, use the arrow keys to navigate in the outline view
-and press <kbd>Enter</kbd> to reveal the selected element in the Java editor. <br>
-<img src="images/quickoutline_submethods.png" alt="Filtered quick outline view">
-</li>
-
-<li>Click the triangle in the upper right corner to see the quick view menu: <br>
-
-<img src="images/quickoutline_menu.png" alt="Quick view menu">
-<br>
-The menu items can be divided into 3 categories:
-<ul>
-<li><em>Position</em> - Allows you to resize and move the quick view and to remember these settings</li>
-<li><em>Filter</em> - Define filters so that not all members are shown in the quick outline.</li>
-<li><em>Sort</em> - Sort the members by their defining type or alphabetically.</li>
-</ul>
-</li>
-</ol>
-<p><em>Note:</em> <kbd>Ctrl+O</kbd> always opens the outline for the current Java editor.
-Press <kbd>Ctrl+F3</kbd> to open the quick outline for the currently selected type.
-</p>
-
-
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-AddMethod.htm">Adding new methods</A>
-</P>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm
deleted file mode 100644
index 6c8faf5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout1.htm
+++ /dev/null

@@ -1,93 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Sibling products in a common source tree
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Sibling products in a common source tree
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The source files for products are laid out in one big directory that is version and configuration managed outside Eclipse.</li>
-	<li>The source directory contains two siblings directories <i><code>Product1</code></i> and <i><code>Product2</code></i>.
-	<p><img src="images/qs-WorkingWithExistingLayout10.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining corresponding projects</h3>
-    <ol>
-	<li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout11.png"  alt="New Java Project wizard"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link additional source</strong> link in <strong>Details</strong> pane
-		or button <img src="images/add_linked_source_to_buildpath.png" alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout12.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Source</strong> dialog click <strong>Browse....</strong> and choose the <i><code>D:\AllProducts\Product1\JavaSourceFiles</code></i> directory.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout13.png"  alt="Link Source dialog"></p>
-	</li>
-	<li>
-		Click <strong>Finish</strong> to validate and close the dialog.
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout14.png"  alt="Java Project Source final setup"></p>
-	</li>
-    <li>
-    	<p>Click <strong>Finish</strong>.</p>
-    </li>
-    <li>
-    	<p>Repeat steps 2 to 8 for  &quot;Product2&quot;.</p>
-    </li>
-    <li>
-    	<p>You now have two Java projects which respectively contain the sources of &quot;Product1&quot; and &quot;Product2&quot;.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout15.png"  alt="Created Java projects in Workspace"></p>
-    </li>
-	</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-WorkingWithExistingLayout2.htm">Overlapping products in a common source tree</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm
deleted file mode 100644
index e045c6d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout2.htm
+++ /dev/null

@@ -1,114 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Overlapping products in a common source tree
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Overlapping products in a common source tree
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for products are all held in a single main directory.</li>
-	<li>Products are separated into four siblings packages <i><code>Product1</code></i>, <i><code>Product2</code></i>, <i><code>Product3</code></i> and <i><code>Product4</code></i>.
-	<p><img src="images/qs-WorkingWithExistingLayout20.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining corresponding &quot;Product1&quot; and &quot;Product2&quot; projects</h3>
-    <ol>
-	<li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout21.png"  alt="New Java Project wizard"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link additional source</strong> link in <strong>Details</strong> pane or button <img src="images/add_linked_source_to_buildpath.png" alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout22.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\AllJavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src&quot; in <strong>Folder name</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout23.png"  alt="Link Source dialog"></p>
-	</li>
-	<li>
-		<p>Click <strong>Finish</strong> to validate and close the dialog.</p>
-	</li>
-	<li>
-		<p>Expand the &quot;src&quot; source folder. Select the three last packages and exclude them from build path
-		using either <strong>Exclude from build path</strong> link or <strong>Exclude</strong> popup-menu item.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout24.png"  alt="Exclude packages from build path"></p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout25.png"  alt="Java Project Source final setup"></p>
-	</li>
-	<li>
-    	<p>Click <strong>Finish</strong>.</p>
-	</li>
-    <li>
-    	<p>Copy &quot;Product1&quot; project and paste it as &quot;Product2&quot;.</p>
-    	<p>Edit &quot;Product2&quot; project properties and go on <strong>Java Build Path</strong> page.</p>
-    	<p>In <strong>Source</strong> tab, expand &quot;Product2/src&quot; source folder, select <strong>Excluded</strong> and click <strong>Edit...</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout26.png"  alt="Java Build Path Properties Source tab"></p>
-    </li>
-    <li>
-    	<p>In <strong>Inclusion and Exclusion Patterns</strong>, select &quot;com/xyz/product2&quot; and click <strong>Edit...</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout27.png"  alt="Inclusion and Exclusion Patterns dialog"></p>
-    </li>
-    <li>
-    	<p>Change &quot;com/xyz/product2&quot; to &quot;com/xyz/product1&quot;.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout28.png"  alt="Edit Exclusion Pattern dialog"></p>
-    </li>
-    <li>
-		<p>Click <strong>OK</strong> to enter the change.</p>
-		<p>Click <strong>Finish</strong> to validate and close <strong>Inclusion and Exclusion Patterns</strong> dialog.</p>
-		<p>Click <strong>OK</strong> again to validate &quot;Product2&quot; project properties changes.</p>
-    </li>
-    <li>
-    	<p>You now have two Java projects which respectively contain the sources of &quot;product1&quot;, &quot;product2&quot;.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout29.png"  alt="Created Java projects in Workspace"></p>
-    </li>
-	</ol>
-		<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-WorkingWithExistingLayout3.htm">Product with nested tests</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm
deleted file mode 100644
index 5545c02..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout3.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Product with nested tests
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Product with nested tests
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for a product are laid out in a package directory.</li>
-	<li>Source files of tests are laid out in a nested package directory.
-	<p><img src="images/qs-WorkingWithExistingLayout30.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-    <ol>
-	<li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout31.png"  alt="New Java Project wizard"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link additional source</strong> link in <strong>Details</strong> pane or button <img src="images/add_linked_source_to_buildpath.png" alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout32.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product1\JavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src&quot; in the <strong>Folder name</strong> field.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout33.png"  alt="Link Source dialog"></p>
-	</li>
-	<li>
-		<p>Click <strong>Finish</strong> to validate and close the dialog.</p>
-	</li>
-	<li>
-		<p>Expand the &quot;src&quot; source folder. Select the empty package &quot;tests&quot;
-		and set it as source folder using either <strong>Use as Source Folder</strong> popup-menu item
-		or button <img src="images/add_as_source_folder.png" alt="Use as Source Folder"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout34.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout35.png"  alt="Java Project Source final setup"></p>
-	</li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-    <li>
-    	You now have a Java project with two source folders: &quot;src&quot; and &quot;src/tests&quot; which contain respectively 
-    	the <i><code>D:\Product1\JavaSourceFiles</code></i> directory and the <i><code>D:\Product1\JavaSourceFiles\tests</code></i> directory.
-		<p><img src="images/qs-WorkingWithExistingLayout36.png"  alt="Created Java project in Workspace"></p>
-    </li>
-	</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-WorkingWithExistingLayout4.htm">Products sharing a common source framework</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm
deleted file mode 100644
index 03c1206..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout4.htm
+++ /dev/null

@@ -1,127 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Products sharing a common source framework
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Products sharing a common source framework
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for two products require a common framework.</li>
-	<li>Projects and common framework are in separate directories which have their own source and output folders.
-	<p><img src="images/qs-WorkingWithExistingLayout40.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining corresponding projects</h3>
-	<ol>
-	<li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;Product1&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout41.png"  alt="New Java Project wizard"></p>
-	</li>
-	<li>
-		<p>On the next page, Select &quot;Product1&quot; source folder.</p>
-		<p>Click <strong>Link additional source</strong> link in <strong>Details</strong> pane or button <img src="images/add_linked_source_to_buildpath.png" alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout42.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product1\JavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src&quot; in the <strong>Folder name</strong> field.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout43.png"  alt="Link Source dialog"></p>
-	</li>
-	<li>
-		<p>Click <strong>Finish</strong> to validate and close the dialog.</p>
-	</li>
-	<li>
-		<p>Again, Select &quot;Product1&quot; and click <strong>Link additional source</strong> link in <strong>Details</strong> pane or button <img src="images/add_linked_source_to_buildpath.png" alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout44.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Framework\JavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src-common&quot; in the <strong>Folder name</strong> field.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout45.png"  alt="Link Source dialog"></p>
-	</li>
-	<li>
-		<p>Click <strong>Finish</strong> to validate and close the dialog.</p>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout46.png"  alt="Java Project Source final setup"></p>
-	</li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-    <li>
-    	<p>Create project &quot;Product2&quot; repeating steps 2 to 5 choosing <i><code>D:\Product2\JavaSourceFiles</code></i>
-    	directory for source folder instead.</p>
-    </li>
-    <li>
-    	<p>Click on <strong>Finish</strong> to create the project immediately.</p>
-    </li>
-    <li>
-    	<p>Now, we'll see how to add a linked source folder when project is already created in workspace...</p>
-    	<p>Edit project &quot;Product2&quot; properties and select <strong>Java Builder Path</strong> page.</p>
-		<p>On <strong>Source</strong> tab, click <strong>Link Source...</strong>.</p>
-    	<p><img src="images/qs-WorkingWithExistingLayout47.png"  alt="Java Build Path Properties Source tab"></p>
-    </li>
-	<li>
-		<p>In <strong>Link Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Framework\JavaSourceFiles</code></i> directory.</p>
-		<p>Type &quot;src-common&quot; in the <strong>Folder name</strong> field.</p>
-    	<p><img src="images/qs-WorkingWithExistingLayout48.png"  alt="Link Source dialog"></p>
-    </li>
-	<li>
-		<p>Click <strong>Finish</strong> to validate and close the dialog.</p>
-    	<p>Click <strong>OK</strong> to apply project &quot;Product2&quot; properties changes.</p>
-	</li>
-    <li>
-    	You now have two Java projects which respectively contain the sources of &quot;Product1&quot; and &quot;Product2&quot;
-    	and which are using the sources of &quot;Framework&quot;.
-		<p><img src="images/qs-WorkingWithExistingLayout49.png"  alt="Created Java projects in Workspace"></p>
-    </li>
-	</ol>
-	<em>Note: </em>Files in &quot;src-common&quot; are shared. So editing &quot;Common.java&quot; in &quot;Product1&quot;
-	will modify &quot;Common.java&quot; in &quot;Product2&quot;. However they are compiled in the context of their
-	respective projects. Two &quot;Common.class&quot; files will be generated; one for each project. If the two projects have 
-	different compiler options, then different errors could be reported on each &quot;Common.java&quot; file.
-	<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-WorkingWithExistingLayout5.htm">Product nesting resources in output directory</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm
deleted file mode 100644
index 1a1d019..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout5.htm
+++ /dev/null

@@ -1,116 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Nesting resources in output directory
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Nesting resources in output directory
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for a product are laid out both in <i><code>sources</code></i> and <i><code>deliverables</code></i> directories.</li>
-	<li>All Java class files are laid out in <i><code>deliverables</code></i> directory.</li>
-	<li>Project needs to use some libraries located in <i><code>deliverables/libraries</code></i> directory:
-	<p><img src="images/qs-WorkingWithExistingLayout50.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining a corresponding project</h3>
-	<ol>
-	<li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;Product&quot; in the <strong>Project name</strong> field. Click <strong>Next</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout51.png"  alt="New Java Project wizard"></p>
-	</li>
-	<li>
-		<p>On the next page, Type &quot;Product/deliverables&quot; in <strong>Default output folder</strong> field.</p>
-		<p>Select &quot;Product&quot; source folder.</p>
-		<p>Click <strong>Link additional source</strong> link in <strong>Details</strong> pane or button <img src="images/add_linked_source_to_buildpath.png" alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout52.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product\sources</code></i> directory.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout53.png"  alt="Link Source dialog"></p>
-	</li>
-	<li>
-		<p>Click <strong>Finish</strong> to validate and close the dialog.</p>
-	</li>
-	<li>
-		<p>Again, Select &quot;Product&quot; and click <strong>Link additional source</strong> link in <strong>Details</strong> pane or button <img src="images/add_linked_source_to_buildpath.png" alt="Link Additional Source to Project"> in view bar.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout54.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Link Source</strong> click <strong>Browse....</strong> and choose the <i><code>D:\Product\deliverables</code></i> directory.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout55.png"  alt="Link Source dialog"></p>
-	</li>
-	<li>
-		<p>Expand the &quot;Product/deliverables&quot; source folder. Select the &quot;libraries&quot; package
-		and exclude it from build path using either <strong>Exclude 'libraries' from build path</strong> link
-		or <strong>Exclude</strong> popup-menu item.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout56.png"  alt="Exclude 'libraries' from build path"></p>
-	</li>
-	<li>
-		<p>Your project source setup now looks as follows:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout57.png"  alt="Java Project Source final setup"></p>
-	</li>
-    <li>
-    	<p>Select <strong>Libraries</strong> tab.</p>
-    	<p>Click on <strong>Add JARs...</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout58.png"  alt="Java Project Libraries setup"></p>
-    </li>
-    <li>
-    	<p>Expand &quot;Product&quot; hierarchy to select jar files in &quot;libraries&quot; directory</p>
-    	<p>Click <strong>OK</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout59.png"  alt="JAR Selection dialog"></p>
-    </li>
-	<li>
-		<p>Click <strong>Finish</strong> to finalize project creation.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout5a.png"  alt="Java Project Libraries final setup"></p>
-	</li>
-    <li>
-    	<p>You now have a Java project with a &quot;sources&quot; folder and an output folder which contains nested library resources.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout5b.png"  alt="Created Java projects in Workspace"></p>
-    </li>
-	</ol>
-<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-WorkingWithExistingLayout6.htm">Project using a source framework with restricted access</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm
deleted file mode 100644
index e7afadd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-WorkingWithExistingLayout6.htm
+++ /dev/null

@@ -1,151 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Project using a source framework with restricted access
-    </title>
-    <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-  </head>
-  <body>
-    <h1>
-      Project using a source framework with restricted access
-    </h1>
-    <h3>Layout on file system</h3>
-    <ul>
-	<li>The Java source files for a product requires a source framework.</li>
-	<li>&quot;Product&quot; and &quot;Framework&quot; are in separate directories which have their own source and output folders.
-	<p><img src="images/qs-WorkingWithExistingLayout60.png"  alt="Layout on file system"></p></li>
-	</ul>
-    <h3>Steps for defining corresponding projects</h3>
-	<ol>
-	<li>
-    	<p>Click 
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java perspective">
-    	<strong>Window &gt; Open Perspective &gt; Other... &gt; Java</strong></a>
-    	to change to the Java perspective.
-    	</p>
-    </li>
-	<li>
-		<p>
-		Click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-		<strong>File &gt; New &gt; Other... &gt; Java Project</strong></a>
-		to open the <strong>New Java Project</strong> wizard.
-		</p>
-	</li>
-    <li>
-    	<p>Type &quot;Framework&quot; in the <strong>Project name</strong> field.</p>
-    </li>
-    <li>
-    	<p>In <strong>Contents</strong> group, change selection to <strong>Create project from existing source</strong>.</p>
-    	<p>Click <strong>Browse...</strong> and choose the <i><code>D:\Framework</code></i> directory.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout61.png"  alt="New Java Project wizard"></p>
-    	<p>Click <strong>Next</strong>.</p>
-	</li>
-	<li>
-		<p>On the next page, verify that directory <i><code>JavaSourceFiles</code></i> has been automatically added as source folder.</p>
-		<p>Expand it to preview your project source folder contents:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout62.png"  alt="Java Project Source setup"></p>
-	</li>
-    <li>
-    	Click <strong>Finish</strong>.
-    </li>
-	<li>
-		<p>In Java perspective, type <strong>Ctrl+N</strong> to open <strong>New</strong> wizards dialog.</p>
-        <p>Select <strong>Java project</strong> in the list of wizards and click <strong>Next</strong>.</p>
-    </li>
-    <li>
-    	<p>On the next page, type &quot;Product&quot; in the <strong>Project name</strong> field.</p>
-	</li>
-    <li>
-    	<p>In <strong>Contents</strong> group, change selection to <strong>Create project from existing source</strong>.</p>
-    	<p>Click <strong>Browse...</strong> and choose the <i><code>D:\Product</code></i> directory.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout63.png"  alt="New Java Project wizard"></p>
-	</li>
-    <li>
-    	<p>Click <strong>Next</strong>.</p>
-	</li>
-	<li>
-		<p>On the next page, verify that directory <i><code>JavaSourceFiles</code></i> has been automatically added as source folder.</p>
-		<p>Expand it to preview your project source folder contents:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout64.png"  alt="Java Project Source setup"></p>
-	</li>
-	<li>
-		<p>Select <strong>Projects</strong> tab.</p>
-    	<p>Click <strong>Add...</strong>to add a dependency to source framework project...</p>
-		<p><img src="images/qs-WorkingWithExistingLayout65.png"  alt="Java Project Required Projects setup"></p>
-	</li>
-	<li>
-		<p>In <strong>Required Project Selection</strong>, check &quot;Framework&quot;.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout66.png"  alt="Required Project Selection dialog"></p>
-	</li>
-	<li>
-    	<p>Click <strong>OK</strong> to validate and close dialog.</p>
-	</li>
-	<li>
-		<p>Now, let's put access rules on source framework content to authorize, discourage or forbid access to &quot;Framework&quot; source folders, package and classes...</p>
-		<p>In <strong>Projects</strong> tab, select &quot;Access rules&quot; of &quot;Framework&quot; depending project.</p>
-    	<p>Click <strong>Edit...</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout67.png"  alt="Edit Required Project Access Rules"></p>
-	</li>
-	<li>
-		<p>In <strong>Type Access Rules</strong>, click <strong>Add...</strong>.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout68.png"  alt="Type Access Rules dialog"></p>
-	</li>
-	<li>
-		<p>In <strong>Add Access Rule</strong>, select &quot;Forbidden&quot; for <strong>Resolution</strong>.</p>
-		<p>Type &quot;**/forbidden/**&quot; in <strong>Rule Pattern</strong> field.</p>
-		<p><img src="images/qs-WorkingWithExistingLayout69.png"  alt="Add Access Rule dialog"></p>
-	</li>
-	<li>
-    	<p>Click <strong>OK</strong> to validate access rule and close dialog.</p>
-	</li>
-	<li>
-		<p>Add another access rule:</p>
-		<p><strong>Resolution</strong>: &quot;Discouraged&quot; and <strong>Rule Pattern</strong>: &quot;**/internal/**&quot;.</p>
-	</li>
-	<li>
-		<p>Your access rules now look as follows:</p>
-		<p><img src="images/qs-WorkingWithExistingLayout6a.png"  alt="Type Access Rules final result"></p>
-	</li>
-	<li>
-    	<p>Click <strong>OK</strong> to validate these new rules and close dialog.</p>
-	</li>
-    <li>
-    	<p>Dependent project has now 2 access rules set.</p>
-    	<p><img src="images/qs-WorkingWithExistingLayout6b.png"  alt="Java Project Required Projects final setup"></p>
-	</li>
-    <li>
-    	<p>Click <strong>Finish</strong>.</p>
-    </li>
-    <li>
-    	<p>You now have a Java project which contains the source of &quot;Product&quot; and which is using the source of &quot;Framework&quot;.</p>
-    	<p>Some packages of the project &quot;Framework&quot; are restricted and if you try to import them, compiler displays either warnings or errors depending on your restriction level:</p> 
-		<p><img src="images/qs-WorkingWithExistingLayout6c.png"  alt="Created Java projects in Workspace"></p>
-    </li>
-	</ol>
-	<P class="nav_footer" id="nav_footer">Next Section: <A href="qs-with-j2se50.htm">Eclipse and J2SE 5.0</A>
-</P>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-wizard-java-project.htm">New Java Project Wizard</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer View</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm
deleted file mode 100644
index dc1d653..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-junit.htm
+++ /dev/null

@@ -1,177 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Writing and running JUnit tests
-    </title>
-  </head>
-  <body>
-    <h1>
-      Writing and running JUnit tests
-    </h1>
-    <p>
-      In this section, you will be using the <a href="http://www.junit.org" target="_blank"> JUnit</a> 
-    testing framework to write and run tests. To get started with JUnit you can
-    refer to the <a href="http://junit.sourceforge.net/doc/cookbook/cookbook.htm" target="_blank">JUnit
-    Cookbook</a>.
-    </p>
-    <h2>
-      Writing Tests
-    </h2>
-
-    <p>
-      Create a project &quot;JUnitTest&quot;.  Now you can write your
-      first test. You implement the test in a subclass of <strong>TestCase</strong>. You can
-      do so either using the standard Class wizard or the specialized <strong>Test Case 
-      </strong> wizard:
-    </p>
-    <ol>
-      <li>Open the New wizard (<strong>File  &gt; New  &gt; JUnit Test Case</strong>).</li>
-      <li>Select <strong>New JUnit 3 test</strong> and enter 
-		  &quot;<i>TestFailure&quot;</i> as the name of your test class:
-       <p>
-        <img src="images/wiz_new_testcase.png"  alt="TestCase creation wizard page 1"><br>
-       </p>
-	   <p>
-	   <em>Note: </em>If you want to use JUnit 4 tests you have to make
-			sure that your compiler compliance is set to 1.5. 
-		   </p>
-      </li>
-	  <li>You will see a warning message asking you to add the junit library
-		  to the build path. Use the <strong>Click here</strong> link to 
-		  add the junit library automatically.</li>
-      
-      <li>Click <strong>Finish</strong> to create the test class.
-      </li>
-    </ol>
-    <p>
-      Add a test method that fails to the class <i>TestFailure</i>. A quick
-      way to enter a test method is with the <i>test</i> template. To do so, place the cursor inside the class declaration. 
-      Type &quot;test&quot; followed by <kbd>Ctrl+Space</kbd> to activate code
-      assist and select the &quot;test&quot; template. Change the name of the
-      created method to <i>testFailure</i> and invoke the <i>fail() </i>method.
-    </p>
-    <p><code>
-      public void testFailure() throws Exception {<br>
-      &nbsp;&nbsp;&nbsp; fail();<br>
-      }
-    </code></p>
-     
-    <p>Now you are ready to run your first test.</p>
-
-    <h2>
-      Running Tests
-    </h2>
-    
-    <p>To run TestFailure hit the run button in the toolbar. It will automatically run as JUnit Test.
-    You can inspect the test results in the <i>JUnit</i> view. This view shows
-    you the test run progress and status:</p>
-
-    <p><img src="images/view_junit_red.png"  alt="Failed test"></p>
-
-    <p> The view is shown in the current
-    perspective whenever you start a test run. A convenient arrangement for the
-    JUnit view is to dock it as a fast view. The JUnit view has two tabs: one shows
-    you a list of failures and the other shows you the full test suite as
-    a tree. You can navigate from a failure to the corresponding source by
-    double clicking the corresponding line in the failure trace.</p>
-
-    <p>Dock the JUnit view as a fast view, remove the <i>
-    fail()</i> statement in the method <i> testFailure()</i> so that the test passes and rerun
-    the test again. You can rerun a test either by clicking the <b>Rerun</b> button in
-    the view's tool bar or you can re-run the program that was last launched by activating
-    the <b>Run</b> drop down. This time the test should succeed. Because the test was successful,
-     the JUnit view doesn't pop up, but the success indicator shows on 
-    the JUnit view icon and the status line shows the test result. As a reminder
-    to rerun your tests the view icon is decorated by a &quot;*&quot;
-    whenever you change the workspace contents after the run.</p>
-
-    <blockquote>
-      <p><img src="images/icon_junit_successfull.png"  border="0" alt="Successful test">
-      - A successful test run<br>
-      <img src="images/icon_junit_successfull_workspace_modifed.png"  border="0" alt="Successful test but workspace has changed"> - 
-      A successful test run, but the workspace contents have changed since the
-      last test run.</p>
-
-    </blockquote>
-    <p>In addition to running a test case as described above you can also:</p>
-    <ul>
-      <li>Run all tests inside a project, source folder, or package - &nbsp;<br>
-        Select a project, package or source folder and run all the included tests with <strong>Run as &gt; JUnit Test</strong>.
-        This command finds all tests inside a project, source folder or package
-        and executes them.</li>
-      <li>Run a single test method - <br>
-        Select a test method in the Outline or Package Explorer and with <strong>Run as &gt; JUnit Test</strong>
-        the selected test method will be run.</li>
-      <li>Rerun a single test - <br>
-        Select a test in the JUnit view and execute <b>Run </b>from the context
-        menu.</li>
-    </ul>
-
-    <h2>
-      Customizing a Test Configuration
-    </h2>
-    
-    <p>When you want to pass parameters or customize the
-    settings for a test run you open the Launch Configuration Dialog. Select <strong>Open Run Dialog...</strong>.in the <strong>Run</strong>
-    drop-down menu in the toolbar:</p>
-    <p><img src="images/run_dialog_junit.png"  alt="JUnit Launch Configuration"></p>
-    <p>In this dialog you can specify the test to be run, its arguments, its run-time
-    class path, and the Java run-time environment.</p>
-
-    <h2>
-      Debugging a Test Failure
-    </h2>
-    
-    <p>In the case of a test failure you can follow these steps to debug it:</p>
-    <ol>
-      <li>Double click the failure entry from the Failures tab in the JUnit view to open the
-        corresponding file in the editor.</li>
-      <li>Set a breakpoint at the beginning of the test method.</li>
-      <li>Select the test case and execute&nbsp; <b>Debug As&gt;JUnit Test</b> from
-        the <b>Debug </b>drop down.</li>
-    </ol>
-    <p>A JUnit launch configuration has a &quot;keep alive&quot; option. If your
-    Java virtual machine supports &quot;hot code replacement&quot; you can fix the code and rerun the test
-    without restarting the full test run. To enable this option select the <strong>Keep
-    JUnit running after a test run when debugging</strong> checkbox in the JUnit
-    launch configuration.</p>
-
-    <h2>
-      Creating a Test Suite
-    </h2>
-    
-    <p>
-      The JUnit <b>TestSuite </b>wizard helps you with the creation of a test
-      suite. You can select the set of classes that should belong to a suite. 
-    </p>
-    
-    <ol>
-      <li>Open the New wizard</li>
-      <li>Select <strong>Java &gt; JUnit &gt; JUnit Test Suite</strong> and click <strong>Next</strong>.</li>
-      <li>Enter a name for your test suite class (the convention is to use
-        &quot;AllTests&quot; which appears by default).<br>
-        <p><img src="images/wiz_new_suite.png"  alt="Test Suite wizard"></p>
-      </li>
-      <li>Select the classes that should be included in the suite. We currently
-        have a single test class only, but you can add to the suite later.</li>
-    </ol>
-    
-    <p>You can add or remove test classes from the test suite in two ways:</p>
-    <ul>
-      <li>Manually by editing the test suite file</li>
-	  <li>By re-running the wizard and selecting the new set of test classes.</li>
-    </ul>
-    <p>Note: the wizard puts 2 markers, <code>//$JUnit-BEGIN$</code> and
-    <code>//$JUnit-END$</code>, into the created Test suite class, which allows
-    the wizard to update existing test suite classes. Editing code between the markers is 
-    not recommended.</p>
-    <P class="nav_footer" id="nav_footer">Next Section: <A href="qs-ProjectConfiguration.htm">Project configuration tutorial</A>
-</P>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm b/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm
deleted file mode 100644
index 4fe590c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/gettingStarted/qs-with-j2se50.htm
+++ /dev/null

@@ -1,257 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-<title>Eclipse and J2SE 5.0</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Eclipse and J2SE 5.0</h1>
-<p>
-Since release 3.1, Eclipse includes full support for the new Java language features of J2SE 5.0.
-One of the most important consequences of this support is that you 
-may not notice it at all--everything you expect to work for J2SE 1.4, 
-including editing, compiling, debugging, quick fixes, refactorings, source
-actions, searching, etc., will
-work seamlessly with J2SE 5.0's new types and syntax.  In this document,
-we will introduce some of the more interesting capabilities Eclipse users
-will find when working with J2SE 5.0.
-</p>
-
-<p>Note that both version numbers '1.5' and '5.0' are used to identify the release of the Java 2 Platform Standard Edition. Version '5.0' is the product version, while '1.5' is the developer version and also used for the compliance level.
-</p>
-
-
-
-<h2>Prerequisites</h2>
-
-<p>
-In order to develop code compliant with J2SE 5.0, you will need a J2SE 5.0 or J2SE 6.0 Java Runtime Environment (JRE).
-If you start Eclipse for the first time using a J2SE 5.0 JRE, then it will use it by default.
-Otherwise, you will need to use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.preferences.VMPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Installed JRE preference page">
-<strong>Java &gt; Installed JREs</strong></a>
-preference page to register it with Eclipse.
-</p>
-
-<p>
-This document introduces some of the 
-new language features in J2SE 5.0 very briefly, but it is not a proper tutorial for these features. See <a href="http://java.sun.com/developer/technicalArticles/releases/j2se15/" target="_blank">here</a> for more information.
-</p>
-
-<h3>Compiler Compliance Level</h3>
-
-<p>
-To use the new J2SE 5.0 features, you must be working on a project that has a 1.5 compliance level enabled and has a 5.0 JRE.
-New projects will automatically get 1.5-compliance when choosing a 5.0 JRE on the first page of the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the new Java project wizard">
-<strong>New Java Project wizard</strong></a>:
-</p>
-<p><img src="images/j2se50/wiz_new_java_project_myproject.png" alt="New Project Wizard"></p>
-To convert an existing J2SE 1.4 project to J2SE 5.0, you can simply:
-<ol>
-<li>Make sure you have a J2SE 5.0 JRE installed.</li>
-<li>Start using the 5.0 features in your code.</li>
-<li>When a compiler error is flagged, use Quick Fix to update the project's compliance level:
-<p><img src="images/j2se50/quick-fix.png" alt="Quick fix to enable J2SE 5.0">
-</p>
-</li>
-<li>For more fine-tuned control, 
-the compiler compliance level can be set globally for a workspace
-(with the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CompliancePreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java compiler preference page">
-<strong>Java &gt; Compiler</strong></a> preference page)
-or individually for each project (from the project's context menu, choose <strong>Properties &gt; Java Compiler</strong>).
-<img src="images/j2se50/compiler-property-page.png" alt="Compiler property page">
-</li>
-</ol> 
-
-<p>
-Projects with different compliance levels can co-exist in the workspace, and depend on each other.
-You can also fine-tune the kinds of compiler warnings and errors produced for each project 
-using <strong>Properties &gt; Java Compiler &gt; Errors/Warnings</strong>. The <strong>Generic Types</strong> and the <strong>Annotations</strong> section contain options added for J2SE 5.0.
-</p>
-
-
-<h2>Generic Types</h2>
-
-<p>
-Generic types allow objects of the same class to safely operate on objects of different types.
-For example, they allow compile-time assurances that a 
-<code>List&lt;String&gt;</code> always contains <code>String</code>s, and a <code>List&lt;Integer&gt;</code> always contains <code>Integer</code>s.
-</p>
-
-
-Anywhere that Eclipse handles a non-generic type, it can handle a generic type:
-<ul>
-<li> Generic types can be safely renamed.</li>
-<li> Type variables can be safely renamed.</li>
-<li> Generic methods can be safely extracted from / inlined into generic code.</li>
-<li> Code assist can automatically insert appropriate type parameters in parameterized types.</li>
-</ul>
-
-
-In addition, a new refactoring has been added: <strong>Infer Generic Type Arguments</strong> can infer
-type parameters for every type reference in a class, a package, or an entire project.
-
-<p><img src="images/j2se50/infer-generic.png" alt="Invoking Infer Generic Type Arguments"></p>
-
-Invoking the refactoring produces:
-
-<p><img src="images/j2se50/inferred-generic.png" alt="Invoked Infer Generic Type Arguments">
-</p>
-
-
-<p>
-Eclipse provides new options when searching for references to generic types. Consider this example:
-</p>
-<p><img src="images/j2se50/view_search_listInteger.png" alt="Example with four different parameterized instantiations of List"></p>
-
-Selecting the reference to <code>List&lt;Integer&gt;</code> and using 
-<strong>Search &gt; References &gt; Project</strong> from the context menu
-will highlight the List types on all four lines:
-
-<p><img src="images/j2se50/view_search_listInteger_unfiltered.png" alt="Search with no filters"></p>
-
-Using the Search View menu, the results can be filtered:
-
-<p>
-Filter <strong>Incompatible Type Arguments</strong> leaves only references to types that are assignment-compatible with
-the selected type:</p>
-<p><img src="images/j2se50/view_search_listInteger_incompatible.png" alt="Filter incompatible">
-</p>
-
-
-<p>Filter <strong>Inexact Type Arguments</strong> leaves only type references with the exact same signature:</p>
-<p><img src="images/j2se50/view_search_listInteger_inexact.png" alt="Filter inexact"></p>
-
-<h2>Annotations</h2>
-
-<p>
-Annotations attach metadata about how Java types and methods are used 
-and documented to the Java source and can then affect compilation or 
-be queried at run-time.  For example, <code>@Override</code> will trigger
-a compiler warning if the annotated method does not override a method in
-a superclass:
-</p>
-
-<p><img src="images/j2se50/editor_override_annotation_hover.png" alt="Override annotation"></p>
-
-Everything you can do with a Java type, you can do with an annotation:
-<ul>
-<li> Create new annotations using <strong>New &gt; Annotation</strong></li>
-<li> Refactor: rename, move, change signatures of members, etc.</li>
-<li> Search for occurrences</li>
-<li> Use code assist to fill in names and values</li>
-</ul>
-
-
-<p>
-A very useful annotation with full support in Eclipse is <code>@SuppressWarnings</code>.
-For example, consider a private method that is currently unused, but you'd rather not delete:</p>
-<p><img src="images/j2se50/unused-warning.png" alt="Warning: unused private method"></p>
-
-Invoking quick fix on the warning proposes adding a <code>@SuppressWarnings</code> annotation:
-<p><img src="images/j2se50/suppress-proposed.png" alt="SuppressWarnings proposed"></p>
-
-Selecting the quick fix adds the annotation.  The Eclipse compiler honors the annotation by
-removing the warning on <code>foo</code>:
-<p><img src="images/j2se50/suppress-applied.png" alt="SuppressWarnings inserted"></p>
-
-<h2>Enumerations</h2>
-
-<p>
-Enumerations are types that are instantiated at runtime by a known, finite set of objects:</p>
-<p><img src="images/j2se50/enum.png" alt="enum type"></p>
-
-
-Again, anything you can do to a Java class can be done to an enumeration:
-
-<ul>
-<li> Create new enumerations using <strong>New &gt; Enum</strong></li>
-<li> Refactor: rename, move, rename constants, etc.</li>
-<li> Search for occurrences</li>
-<li> Use code assist to fill in constants</li>
-</ul>
-
-<h2>Autoboxing</h2>
-
-<p>
-Autoboxing and auto unboxing allow for elegant syntax when primitive types are assigned
-to or retrieved from Object references:
-</p>
-<p><img src="images/j2se50/autobox.png" alt="autoboxing highlighted"></p>
-
-<p>
-Eclipse's source manipulation features handle autoboxing seamlessly, 
-giving the correct types to new local variables and correct code assists.
-For code understanding, it is also possible to flag instances of 
-autoboxing or autounboxing conversions:</p>
-
-<ul>
-<li>
-mark them as compiler warnings or errors (<strong>Boxing and unboxing conversions</strong> in the <strong>Potential Programming Problems</strong> section of the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-<strong>Java &gt; Compiler &gt; Errors/Warnings</strong></a> preference page)
-</li>
-<li>
-highlight them using syntax coloring
-(via the
-<strong>Java &gt; Auto(un)boxed expressions</strong> section of the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorColoringPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Syntax coloring preference page">
-<strong>Java &gt; Editor &gt; Syntax Coloring</strong></a> preference page):
-<p><img src="images/j2se50/autobox-coloring.png" alt="Enabling highlighting for autoboxing"></p>
-</li>
-</ul>
-
-<h2>Enhanced for loop</h2>
-
-<p>
-For the common case of operating on each element of an array or collection in turn, 
-J2SE 5.0 allows a new, cleaner syntax.  
-Eclipse provides a "foreach" code template that can automatically guess 
-the collection to be iterated:
-</p>
-<p><img src="images/j2se50/foreach-proposal.png" alt="foreach template proposed"></p>
-
-Choosing the template produces:
-
-<p><img src="images/j2se50/foreach-inserted.png" alt="foreach template inserted"></p>
-
-<p>
-Eclipse also provides a "Convert to enhanced for loop" quick-assist to
-upgrade 1.4-style <code>for</code> loops where possible.
-</p>
-
-<h2>Static Imports</h2>
-
-<p>Static imports allow you to use static fields and methods from other classes without qualification.</p>
-<p>Content assist in the Java editor can suggest such static members and adds a static import when required. To get
-such proposals, configure the static import favorites on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferenceFavorites)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Content Assist Favorites preference page">
-<strong>Java &gt; Editor &gt; Content Assist &gt; Favorites</strong></a> preference page.
-</p>
-
-
-<h2>Converting J2SE 1.4 code to 5.0</h2>
-
-Eclipse offers the following tools to help you bring J2SE 1.4 code to 5.0:
-
-<ul>
-<li><strong>Clean Up</strong> action
-<ul>
-  <li>Add missing <code>@Override</code> and <code>@Deprecated</code> annotations</li>
-  <li>Convert <code>for</code> loops to enhanced</li>
-</ul>
-</li>
-<li><strong>Infer Generic Type Arguments</strong> refactoring</li>
-</ul>
-
-Happy coding!
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/images/ngrelc.png b/bundles/org.eclipse.jdt.doc.user/images/ngrelc.png
deleted file mode 100644
index 161e3aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/ngrelc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/ngrelr.png b/bundles/org.eclipse.jdt.doc.user/images/ngrelr.png
deleted file mode 100644
index 4726f8c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/ngrelr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/ngrelt.png b/bundles/org.eclipse.jdt.doc.user/images/ngrelt.png
deleted file mode 100644
index 74bee2b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/ngrelt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png
deleted file mode 100644
index 5944714..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/changevariablevalue_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png
deleted file mode 100644
index e6a51f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png
deleted file mode 100644
index 6710357..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copy_edit_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png
deleted file mode 100644
index ae69f07..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/copyviewtoclipboard_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png
deleted file mode 100644
index 99cf37c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/debuglast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png
deleted file mode 100644
index b35b56d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_hide.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png
deleted file mode 100644
index 10af6c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_right.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png
deleted file mode 100644
index 16200d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/det_pane_under.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png
deleted file mode 100644
index a772650..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png
deleted file mode 100644
index 9db8853..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/disconnect_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png
deleted file mode 100644
index 2eae230..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/edtsrclkup_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png
deleted file mode 100644
index ca175c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/enabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png
deleted file mode 100644
index e613f9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/lock_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png
deleted file mode 100644
index 5e807fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/memoryreset_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png
deleted file mode 100644
index 5b829ff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/metharg_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png
deleted file mode 100644
index 66fd225..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/monitorexpression_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png
deleted file mode 100644
index 0550c10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/printview_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png
deleted file mode 100644
index 7d5a844..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png
deleted file mode 100644
index 1d3ee9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png
deleted file mode 100644
index 1d3ee9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/removememory_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png
deleted file mode 100644
index 7f78504..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png
deleted file mode 100644
index 7620144..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runlast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png
deleted file mode 100644
index e4ef891..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/runtoline_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png
deleted file mode 100644
index ac88344..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/skip_brkp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png
deleted file mode 100644
index 4d308c1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepbystep_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png
deleted file mode 100644
index 7ba98b1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepinto_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png
deleted file mode 100644
index f1b8323..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepover_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png
deleted file mode 100644
index c7a6f4a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/stepreturn_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png
deleted file mode 100644
index 349f8ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png
deleted file mode 100644
index d28c6b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png
deleted file mode 100644
index e9a444b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png
deleted file mode 100644
index d3a0590..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png
deleted file mode 100644
index 191bf21..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/terminate_rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png
deleted file mode 100644
index 2c6b2f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/tnames_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png
deleted file mode 100644
index 24eba96..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/toggledetailpane_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png
deleted file mode 100644
index d997a25..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dlcl16/var_cntnt_prvdr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png
deleted file mode 100644
index 2e29e64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png
deleted file mode 100644
index d4dfe0c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/environment_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png
deleted file mode 100644
index 1bf8948..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/profile_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png
deleted file mode 100644
index 9a55714..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png
deleted file mode 100644
index 1b106fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/term_restart.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png
deleted file mode 100644
index 706bc23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/dtool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png
deleted file mode 100644
index 6d6a3f0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png
deleted file mode 100644
index 2349877..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png
deleted file mode 100644
index bb5451c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copy_edit_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png
deleted file mode 100644
index 39f1090..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/copyviewtoclipboard_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png
deleted file mode 100644
index 69221be..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/debuglast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png
deleted file mode 100644
index c6ff25e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_hide.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png
deleted file mode 100644
index 8d23eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_right.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png
deleted file mode 100644
index b22ac64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/det_pane_under.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png
deleted file mode 100644
index 6fa89b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png
deleted file mode 100644
index 070671e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/disconnect_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png
deleted file mode 100644
index 21a7c0d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/dissolve_group.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png
deleted file mode 100644
index 96cf8c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/drop_to_frame.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png
deleted file mode 100644
index 3e92946..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png
deleted file mode 100644
index e3e9baa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/enabled_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png
deleted file mode 100644
index 12e979a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/expandall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/export_brkpts.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/export_brkpts.png
deleted file mode 100644
index 2399c85..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/export_brkpts.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png
deleted file mode 100644
index a9355ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/import_brkpts.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/import_brkpts.png
deleted file mode 100644
index 9a7a9d5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/import_brkpts.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png
deleted file mode 100644
index 6a00020..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/lock_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png
deleted file mode 100644
index a7b8b42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/memoryreset_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png
deleted file mode 100644
index a037e58..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/metharg_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png
deleted file mode 100644
index 6d48492..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/monitorexpression_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png
deleted file mode 100644
index 469ec49..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/new_con.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/next_thread_nav.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/next_thread_nav.png
deleted file mode 100644
index eef7e39..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/next_thread_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png
deleted file mode 100644
index fc0cf1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/pin.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prev_thread_nav.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prev_thread_nav.png
deleted file mode 100644
index 0522d72..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prev_thread_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png
deleted file mode 100644
index 495b869..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/printview_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prop_ps.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prop_ps.png
deleted file mode 100644
index 8ef0300..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/prop_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png
deleted file mode 100644
index 73053c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png
deleted file mode 100644
index 91e4e01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png
deleted file mode 100644
index 91e4e01..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/removememory_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png
deleted file mode 100644
index 114193f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png
deleted file mode 100644
index 668fd32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runlast_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png
deleted file mode 100644
index 560e289..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/runtoline_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png
deleted file mode 100644
index 30c82c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/skip_brkp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png
deleted file mode 100644
index a24953f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepbystep_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png
deleted file mode 100644
index b237fe8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepinto_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png
deleted file mode 100644
index 407268c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepover_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png
deleted file mode 100644
index 7fc74f9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/stepreturn_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png
deleted file mode 100644
index 5254176..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png
deleted file mode 100644
index 7d54854..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png
deleted file mode 100644
index d9aa1ee..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_all_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png
deleted file mode 100644
index cddc772..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png
deleted file mode 100644
index 833ebf3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png
deleted file mode 100644
index a1a64c1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/tnames_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png
deleted file mode 100644
index e5f9f9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/toggledetailpane_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png
deleted file mode 100644
index 918861d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeerr_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeerr_co.png
deleted file mode 100644
index f70616d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeerr_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeout_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeout_co.png
deleted file mode 100644
index 87eeb98..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/elcl16/writeout_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png
deleted file mode 100644
index 95d69dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png
deleted file mode 100644
index 1e5240e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/environment_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png
deleted file mode 100644
index 983ba0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/profile_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png
deleted file mode 100644
index 967cf0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png
deleted file mode 100644
index 6e3a83d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/term_restart.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png
deleted file mode 100644
index 236d9ad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/etool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png
deleted file mode 100644
index 379357a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/breakpoint_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png
deleted file mode 100644
index 71b6ebd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png
deleted file mode 100644
index 71b6ebd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/debug_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png
deleted file mode 100644
index 095263c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/details_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png
deleted file mode 100644
index 8264f7d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/memory_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png
deleted file mode 100644
index b164d3a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/register_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png
deleted file mode 100644
index 9a44e10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/variable_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png
deleted file mode 100644
index 41ae47f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/eview16/watchlist_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_grp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_grp.png
deleted file mode 100644
index a65d4d2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_grp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png
deleted file mode 100644
index 5672584..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkp_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png
deleted file mode 100644
index 5c7b2fe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/brkpd_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png
deleted file mode 100644
index 471c091..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png
deleted file mode 100644
index 6801070..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugts_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png
deleted file mode 100644
index 0ad64e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/debugtt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png
deleted file mode 100644
index aeb9294..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/expression_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png
deleted file mode 100644
index 02b6e29..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/genericvariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png
deleted file mode 100644
index 2fa71f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png
deleted file mode 100644
index ba437e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/inst_ptr_top.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png
deleted file mode 100644
index 6e4d0d8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/ldebug_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png
deleted file mode 100644
index 5bd0e13..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/lrun_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png
deleted file mode 100644
index 38ac821..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png
deleted file mode 100644
index a3c460e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/osprct_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png
deleted file mode 100644
index 1eb5eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/readwrite_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png
deleted file mode 100644
index 6871a8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png
deleted file mode 100644
index 45089c1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png
deleted file mode 100644
index 7299114..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png
deleted file mode 100644
index 212a6c2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/thread_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png
deleted file mode 100644
index 9e69cf1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/obj16/threads_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png
deleted file mode 100644
index d8f0680..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/error.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png
deleted file mode 100644
index dabc465..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/ovr16/stcksync_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png
deleted file mode 100644
index d0b18e7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/addsrcloc_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png
deleted file mode 100644
index 0fdecfb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/debug_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png
deleted file mode 100644
index 8b1108f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/edtsrclkup_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png
deleted file mode 100644
index f922f24..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/profile_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png
deleted file mode 100644
index 1a9b33f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.debug.ui/wizban/run_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png
deleted file mode 100644
index cfbdd66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/constant_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png
deleted file mode 100644
index f7f2995..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/deadlock_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png
deleted file mode 100644
index ed6fe17..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png
deleted file mode 100644
index bb8312d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/final_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png
deleted file mode 100644
index 17446cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/monitor_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png
deleted file mode 100644
index 7f78504..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png
deleted file mode 100644
index dedb799..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/sethitcount_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png
deleted file mode 100644
index a7489e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png
deleted file mode 100644
index 349f8ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png
deleted file mode 100644
index 3c33fd6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dlcl16/thread_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png
deleted file mode 100644
index 2e29e64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png
deleted file mode 100644
index 0157f6e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/disp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png
deleted file mode 100644
index fa1fe6b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/insp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png
deleted file mode 100644
index c3b0a18..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png
deleted file mode 100644
index d329a42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_applet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png
deleted file mode 100644
index 002a532..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/java_attach.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png
deleted file mode 100644
index fb3388a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png
deleted file mode 100644
index 9a55714..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png
deleted file mode 100644
index 2279f74..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/run_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png
deleted file mode 100644
index d3a0590..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/term_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png
deleted file mode 100644
index 706bc23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/dtool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png
deleted file mode 100644
index 0c64ad1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_references.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_references.png
deleted file mode 100644
index fad6f83..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/all_references.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/autoform_menu.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/autoform_menu.png
deleted file mode 100644
index a93e894..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/autoform_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png
deleted file mode 100644
index 8c72bed..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png
deleted file mode 100644
index 90973ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/deadlock_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png
deleted file mode 100644
index 95070cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png
deleted file mode 100644
index bf224ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/final_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png
deleted file mode 100644
index c11b767..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/monitor_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png
deleted file mode 100644
index 114193f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/resume_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png
deleted file mode 100644
index 2c8726a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png
deleted file mode 100644
index 8adf87a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png
deleted file mode 100644
index 5254176..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/suspend_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png
deleted file mode 100644
index 4dcff67..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/elcl16/thread_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png
deleted file mode 100644
index 95d69dd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png
deleted file mode 100644
index 694fe36..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png
deleted file mode 100644
index e936fba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png
deleted file mode 100644
index e491d06..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png
deleted file mode 100644
index dad7e1e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_applet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png
deleted file mode 100644
index b3cb48b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/java_attach.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png
deleted file mode 100644
index eefe413..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png
deleted file mode 100644
index 967cf0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png
deleted file mode 100644
index 9d7dbbe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png
deleted file mode 100644
index cfbf9d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png
deleted file mode 100644
index 236d9ad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png
deleted file mode 100644
index 59c5e0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/thread_and_monitor_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png
deleted file mode 100644
index 9a44e10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/eview16/variable_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png
deleted file mode 100644
index edb0b3f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/brkpi_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png
deleted file mode 100644
index b763245..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/class_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png
deleted file mode 100644
index 9557b04..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/classpath_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png
deleted file mode 100644
index 1f5638b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/contended_monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png
deleted file mode 100644
index 9044217..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/envvar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png
deleted file mode 100644
index 1a9271c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png
deleted file mode 100644
index af4d58f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png
deleted file mode 100644
index 2d07a1e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexcept_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png
deleted file mode 100644
index 7056a38..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png
deleted file mode 100644
index a2ab6e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png
deleted file mode 100644
index fe55c43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jline_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png
deleted file mode 100644
index 8c6a3e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jload_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png
deleted file mode 100644
index 5f1afe6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jmeth_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png
deleted file mode 100644
index 6d90522..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png
deleted file mode 100644
index b89a649..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png
deleted file mode 100644
index de97cd7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png
deleted file mode 100644
index 6644b96..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jspbrkpt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png
deleted file mode 100644
index 8307428..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/jwatch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png
deleted file mode 100644
index e21e089..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/library_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png
deleted file mode 100644
index 493ffc9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png
deleted file mode 100644
index c11b767..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png
deleted file mode 100644
index cfb8a11..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/owned_monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png
deleted file mode 100644
index 922c435..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png
deleted file mode 100644
index c4b05fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/prj_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png
deleted file mode 100644
index 9869709..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/read_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png
deleted file mode 100644
index 52cbf7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png
deleted file mode 100644
index ed03ca0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png
deleted file mode 100644
index 14ebb9e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/threadgroup_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/threadgroup_obj.png
deleted file mode 100644
index c7db78e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/threadgroup_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png
deleted file mode 100644
index 5a17ef5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/obj16/write_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png
deleted file mode 100644
index 97faa0b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png
deleted file mode 100644
index 27f7dd9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png
deleted file mode 100644
index fbb326a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png
deleted file mode 100644
index d9a1f0d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png
deleted file mode 100644
index a9fb776..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png
deleted file mode 100644
index c5b975e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png
deleted file mode 100644
index 3ad81a1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/deadlock_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png
deleted file mode 100644
index d57e6f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png
deleted file mode 100644
index 2f22f66..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png
deleted file mode 100644
index afb5bbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/error_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png
deleted file mode 100644
index d7f0d5a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png
deleted file mode 100644
index 08bb335..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png
deleted file mode 100644
index 1764c9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png
deleted file mode 100644
index 1cdb362..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png
deleted file mode 100644
index d15e6e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png
deleted file mode 100644
index a3bc4c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png
deleted file mode 100644
index 13de7f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png
deleted file mode 100644
index fb5815c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png
deleted file mode 100644
index 9809abb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/sync_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png
deleted file mode 100644
index cc7ad8d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png
deleted file mode 100644
index fbc3432..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr_disabled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png
deleted file mode 100644
index 20fe5b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png
deleted file mode 100644
index eada818..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_app_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png
deleted file mode 100644
index aaa4aec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/java_attach_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png
deleted file mode 100644
index 2afd872..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/library_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png
deleted file mode 100644
index 50e4f8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.debug.ui/wizban/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png
deleted file mode 100644
index 6079b2a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/cfilter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png
deleted file mode 100644
index 6985e4c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/flatLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/flatLayout.png
deleted file mode 100644
index 555a831..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/flatLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/hierarchicalLayout.png
deleted file mode 100644
index c75c196..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/history_list.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/history_list.png
deleted file mode 100644
index fe58676..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/history_list.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png
deleted file mode 100644
index e705035..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/lock.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png
deleted file mode 100644
index 1cefb5e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png
deleted file mode 100644
index 9d30443..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/relaunchf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png
deleted file mode 100644
index 3f3e0d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png
deleted file mode 100644
index 4a40bdf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/select_prev.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png
deleted file mode 100644
index 6df3da7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/stop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png
deleted file mode 100644
index c401e95..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_automatic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png
deleted file mode 100644
index abd2645..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_horizontal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png
deleted file mode 100644
index f84a647..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/elcl16/th_vertical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png
deleted file mode 100644
index a2837b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/debugjunit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png
deleted file mode 100644
index 2680437..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testcase.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png
deleted file mode 100644
index 3a9ab34..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/new_testsuite.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png
deleted file mode 100644
index 0fb70e9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/etool16/runjunit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png
deleted file mode 100644
index 0336f5a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png
deleted file mode 100644
index 4c6a758..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png
deleted file mode 100644
index 26601c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/juniterrq.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png
deleted file mode 100644
index 4f09774..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsucc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png
deleted file mode 100644
index e5e6e20..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/junitsuccq.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png
deleted file mode 100644
index 6871a8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/eview16/stackframe.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png
deleted file mode 100644
index 33c2b73..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png
deleted file mode 100644
index 4667c65..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/faillist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png
deleted file mode 100644
index 96955df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/failures.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png
deleted file mode 100644
index 8c427b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/julaunch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png
deleted file mode 100644
index 6871a8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png
deleted file mode 100644
index b74a9fc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/test.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png
deleted file mode 100644
index e46c875..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testerr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png
deleted file mode 100644
index 057698b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testfail.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png
deleted file mode 100644
index 969818d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testhier.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testignored.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testignored.png
deleted file mode 100644
index b3c69ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testignored.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png
deleted file mode 100644
index 5977335..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testok.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png
deleted file mode 100644
index 8d8d6f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/testrun.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png
deleted file mode 100644
index b7efb0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuite.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png
deleted file mode 100644
index 14cb1af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteerror.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png
deleted file mode 100644
index 0dd6ee3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuitefail.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png
deleted file mode 100644
index f7a6020..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiteok.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png
deleted file mode 100644
index e8ddc30..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/obj16/tsuiterun.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png
deleted file mode 100644
index 6ee04ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/error_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png
deleted file mode 100644
index 26e5b2d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/failed_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png
deleted file mode 100644
index 629da64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/ovr16/success_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png
deleted file mode 100644
index e138e44..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png
deleted file mode 100644
index c7e54f3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png
deleted file mode 100644
index 58d236b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png
deleted file mode 100644
index 1be032d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png
deleted file mode 100644
index 5fcee43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png
deleted file mode 100644
index e67a1ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png
deleted file mode 100644
index 20c5839..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png
deleted file mode 100644
index bdaf8e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png
deleted file mode 100644
index cc49dbc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ff9.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png
deleted file mode 100644
index 63f6cd5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png
deleted file mode 100644
index 736fdbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png
deleted file mode 100644
index 71623bf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png
deleted file mode 100644
index 078da49..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png
deleted file mode 100644
index 83e2f3b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png
deleted file mode 100644
index c38090b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png
deleted file mode 100644
index 54297f7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png
deleted file mode 100644
index 4c7ac05..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png
deleted file mode 100644
index 4ade100..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.junit/prgss/ss9.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png
deleted file mode 100644
index f50271a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_as_source_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png
deleted file mode 100644
index b291fb4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.gif
deleted file mode 100644
index 83b778d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png
deleted file mode 100644
index b9c8562..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png
deleted file mode 100644
index de3af12..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/add_to_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png
deleted file mode 100644
index 585fd8a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/alphab_sort_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/category_menu.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/category_menu.png
deleted file mode 100644
index 04b4333..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/category_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png
deleted file mode 100644
index 03cdd7e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callees.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png
deleted file mode 100644
index bc59c6b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_callers.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png
deleted file mode 100644
index 6df3da7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/ch_cancel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png
deleted file mode 100644
index 86738bd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/class_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png
deleted file mode 100644
index 76207ac..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/clear_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png
deleted file mode 100644
index fa0367d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/collapseall.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png
deleted file mode 100644
index 329f7d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_build_path.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png
deleted file mode 100644
index a6f42c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png
deleted file mode 100644
index 86751af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/configure_output_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/copy_qualified.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/copy_qualified.png
deleted file mode 100644
index a3d7188..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/copy_qualified.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/cpyqual_menu.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/cpyqual_menu.png
deleted file mode 100644
index fab5842..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/cpyqual_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png
deleted file mode 100644
index 719781d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/default_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png
deleted file mode 100644
index 7359919..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/definingtype_sort_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png
deleted file mode 100644
index 0629d90..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exc_catch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png
deleted file mode 100644
index 994c487..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclude_from_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png
deleted file mode 100644
index 88594c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png
deleted file mode 100644
index a03311f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/fields_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png
deleted file mode 100644
index ad43b29..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/file_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png
deleted file mode 100644
index 3f6d29e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/filter_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png
deleted file mode 100644
index 555a831..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/flatLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png
deleted file mode 100644
index 1535279..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/gointo_toplevel_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png
deleted file mode 100644
index 7d05466..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/goto_input.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png
deleted file mode 100644
index 6ce18f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/help.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png
deleted file mode 100644
index 63c7740..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_externalized.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png
deleted file mode 100644
index d1ee9e8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_ignored.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png
deleted file mode 100644
index 5e55ce1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hide_internalized.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png
deleted file mode 100644
index c75c196..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchicalLayout.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png
deleted file mode 100644
index c3a523f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/hierarchy_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png
deleted file mode 100644
index fe58676..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/history_list.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png
deleted file mode 100644
index 264fff8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/impl_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png
deleted file mode 100644
index e686418..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/include_on_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png
deleted file mode 100644
index 0e434f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png
deleted file mode 100644
index 8891756..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/inher_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/javaassist_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/javaassist_co.png
deleted file mode 100644
index e909cb6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/javaassist_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/jtypeassist_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/jtypeassist_co.png
deleted file mode 100644
index f7ce5dc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/jtypeassist_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png
deleted file mode 100644
index 02e0c37..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/localtypes_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png
deleted file mode 100644
index 6e83969..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/metharg_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png
deleted file mode 100644
index a2d4310..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/pack_empty_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png
deleted file mode 100644
index 207652b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/package_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png
deleted file mode 100644
index 45c6364..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/private_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png
deleted file mode 100644
index 52b9bc1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/prj_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png
deleted file mode 100644
index 4876547..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/protected_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png
deleted file mode 100644
index c59da7c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/public_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png
deleted file mode 100644
index a3884fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/refresh_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.gif
deleted file mode 100644
index 57995c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png
deleted file mode 100644
index 9e3dd2a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png
deleted file mode 100644
index b9e8142..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.gif
deleted file mode 100644
index 57995c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png
deleted file mode 100644
index ce00ac0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/remove_from_buildpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png
deleted file mode 100644
index ea14834..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/removea_exc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png
deleted file mode 100644
index eecc577..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/search_sortmatch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png
deleted file mode 100644
index 3d4377f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/smartmode_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png
deleted file mode 100644
index 978a411..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png
deleted file mode 100644
index cdf29c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/sub_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png
deleted file mode 100644
index b297252..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/super_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png
deleted file mode 100644
index d9a996f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/templateprop_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/templateprop_co.png
deleted file mode 100644
index 4a7596a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/templateprop_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png
deleted file mode 100644
index c401e95..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_automatic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png
deleted file mode 100644
index abd2645..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_horizontal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png
deleted file mode 100644
index 61eabf5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_showqualified.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png
deleted file mode 100644
index edebc25..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_single.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png
deleted file mode 100644
index f84a647..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/th_vertical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png
deleted file mode 100644
index f9dec29..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/type_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png
deleted file mode 100644
index 7ed8e16..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/view_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/wordassist_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/wordassist_co.png
deleted file mode 100644
index 2ded795..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/elcl16/wordassist_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png
deleted file mode 100644
index 7ed907c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/comment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png
deleted file mode 100644
index c26339f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportapp_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png
deleted file mode 100644
index 78500d7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/exportjar_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png
deleted file mode 100644
index 6a71ca7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/importjar_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png
deleted file mode 100644
index 6ff0cdd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png
deleted file mode 100644
index 7a682fd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/java_attach.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png
deleted file mode 100644
index cebbdd3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png
deleted file mode 100644
index 1c1b6ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/jdoc_hover_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png
deleted file mode 100644
index 6cef6c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/mark_occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png
deleted file mode 100644
index 4b29310..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png
deleted file mode 100644
index 5a1c796..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newclass_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png
deleted file mode 100644
index ddebbce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newenum_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png
deleted file mode 100644
index 884a854..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newint_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png
deleted file mode 100644
index 76e6c86..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png
deleted file mode 100644
index 6ff0cdd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newjworkingSet_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png
deleted file mode 100644
index 1f5b66d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpack_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.gif
deleted file mode 100644
index f2c0079..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png
deleted file mode 100644
index 58e8b21..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png
deleted file mode 100644
index dc24cb9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/newsbook_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png
deleted file mode 100644
index f0ba8f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/opentype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png
deleted file mode 100644
index e8d1286..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/segment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png
deleted file mode 100644
index 27d7876..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_l_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png
deleted file mode 100644
index d95601d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/shift_r_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/toggle_breadcrumb.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/toggle_breadcrumb.gif
deleted file mode 100644
index 1354e47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/etool16/toggle_breadcrumb.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png
deleted file mode 100644
index 574ad1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/browse_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png
deleted file mode 100644
index 12bd8f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/call_hierarchy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png
deleted file mode 100644
index 4f3f063..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/class_hi.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png
deleted file mode 100644
index 67af917..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/classfilegeneration_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png
deleted file mode 100644
index c30e61a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/errorwarning_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png
deleted file mode 100644
index 5e16fe2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/hierch_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png
deleted file mode 100644
index 37f44bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png
deleted file mode 100644
index 7c43489..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jdkcompliance_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png
deleted file mode 100644
index a0b5ad3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/jperspective.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png
deleted file mode 100644
index e909cb6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/members.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png
deleted file mode 100644
index 0fbcb71..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/package.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png
deleted file mode 100644
index a51e1bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/packages.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png
deleted file mode 100644
index 6990f95..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/projects.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png
deleted file mode 100644
index 8d7e6aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png
deleted file mode 100644
index 5d1524e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/eview16/types.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png
deleted file mode 100644
index b846f2a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png
deleted file mode 100644
index 04e5487..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/add_correction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png
deleted file mode 100644
index 18d0232..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_alt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png
deleted file mode 100644
index 38ba1f4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png
deleted file mode 100644
index e1b272b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png
deleted file mode 100644
index 9ff2268..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png
deleted file mode 100644
index ec14c1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/annotation_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png
deleted file mode 100644
index 5145843..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/brkpi_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_obj.png
deleted file mode 100644
index 1a02ea3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_src_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_src_obj.png
deleted file mode 100644
index 9cbd53a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cf_src_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png
deleted file mode 100644
index bde11f1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png
deleted file mode 100644
index af7e9df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png
deleted file mode 100644
index c57c2d0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/class_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png
deleted file mode 100644
index d358d0e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_generate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png
deleted file mode 100644
index 6393f81..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classf_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png
deleted file mode 100644
index 4dd221a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/classfo_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png
deleted file mode 100644
index f7fe67d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_field.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png
deleted file mode 100644
index c845021..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/compare_method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png
deleted file mode 100644
index 30161b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_cast.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png
deleted file mode 100644
index a388417..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png
deleted file mode 100644
index 9d125c3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_delete_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_linked_rename.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_linked_rename.png
deleted file mode 100644
index 61925d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_linked_rename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png
deleted file mode 100644
index 2467a94..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_move.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png
deleted file mode 100644
index a388417..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/correction_rename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png
deleted file mode 100644
index 44442f4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cp_order_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png
deleted file mode 100644
index ea4eaf0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/cu_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png
deleted file mode 100644
index acfb223..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png
deleted file mode 100644
index cccab62..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png
deleted file mode 100644
index a2d4310..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png
deleted file mode 100644
index 15e8b5d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_alt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png
deleted file mode 100644
index c512b12..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png
deleted file mode 100644
index 5e96f5e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png
deleted file mode 100644
index bc34417..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png
deleted file mode 100644
index e310ae1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/enum_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png
deleted file mode 100644
index 57c7557..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/envvar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png
deleted file mode 100644
index 4261edb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_gray_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png
deleted file mode 100644
index e66c98e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/error_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png
deleted file mode 100644
index cd877d4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png
deleted file mode 100644
index 6f04aa4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/externalize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png
deleted file mode 100644
index 9ff8c1e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/fatalerror_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png
deleted file mode 100644
index becfe6b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png
deleted file mode 100644
index d3fa87d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png
deleted file mode 100644
index dc80489..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png
deleted file mode 100644
index 40a5ef1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/field_public_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png
deleted file mode 100644
index 4e9dc38..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/file_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png
deleted file mode 100644
index a24c718..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/history_working_set_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png
deleted file mode 100644
index 8d425a9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/html_tag_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png
deleted file mode 100644
index a0d5bb5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/ignore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png
deleted file mode 100644
index e53f89a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/imp_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png
deleted file mode 100644
index 7689df7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/impc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png
deleted file mode 100644
index 92641b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/implm_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png
deleted file mode 100644
index f23b3e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png
deleted file mode 100644
index 6cb6b84..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/info_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png
deleted file mode 100644
index af7e9df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png
deleted file mode 100644
index 3fbcbe9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png
deleted file mode 100644
index 9a668e4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png
deleted file mode 100644
index c57c2d0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerclass_public_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png
deleted file mode 100644
index dc353aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png
deleted file mode 100644
index 893fdaf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_private_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png
deleted file mode 100644
index b7dd227..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_protected_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png
deleted file mode 100644
index 31caf5a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/innerinterface_public_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png
deleted file mode 100644
index dc353aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_default_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png
deleted file mode 100644
index 31caf5a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/int_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png
deleted file mode 100644
index 0fcb647..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/internalize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png
deleted file mode 100644
index 6c22ad7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/intf_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png
deleted file mode 100644
index be4a980..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png
deleted file mode 100644
index 6124fd2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_l_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png
deleted file mode 100644
index 68b56f7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png
deleted file mode 100644
index 7863464..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png
deleted file mode 100644
index 9237bb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jar_src_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png
deleted file mode 100644
index 3918c21..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/java_model_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png
deleted file mode 100644
index 63d014b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png
deleted file mode 100644
index dceae72..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png
deleted file mode 100644
index e211d7d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png
deleted file mode 100644
index 37f44bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png
deleted file mode 100644
index 33c2b73..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png
deleted file mode 100644
index 6523160..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jexceptiond_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png
deleted file mode 100644
index 831e17c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jrtexception_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png
deleted file mode 100644
index 0f4be2b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsbook_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png
deleted file mode 100644
index c34b058..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jsearch_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png
deleted file mode 100644
index 22cbdbe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png
deleted file mode 100644
index ed1a4d6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/library_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png
deleted file mode 100644
index 75bdd6f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/localvariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png
deleted file mode 100644
index 2f41788..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/logical_package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png
deleted file mode 100644
index a4131b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methdef_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png
deleted file mode 100644
index 57dbb76..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpri_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png
deleted file mode 100644
index 3e4c0d7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpro_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png
deleted file mode 100644
index 3004195..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/methpub_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png
deleted file mode 100644
index be8651e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png
deleted file mode 100644
index 360d306..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/never_translate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png
deleted file mode 100644
index 26c7d02..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/nls_search_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png
deleted file mode 100644
index 770e4fd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/no_breakpoint.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png
deleted file mode 100644
index 4997ed4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_match.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png
deleted file mode 100644
index db4de5c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_read.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png
deleted file mode 100644
index a3c180e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/occ_write.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png
deleted file mode 100644
index 802438a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png
deleted file mode 100644
index 7390299..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/over_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png
deleted file mode 100644
index 0afea5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/package_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png
deleted file mode 100644
index 93053b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png
deleted file mode 100644
index 61eabf5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/packd_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png
deleted file mode 100644
index 7a6c926..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickassist_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png
deleted file mode 100644
index dac3c3f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png
deleted file mode 100644
index 8876c5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png
deleted file mode 100644
index 83811f9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/remove_correction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png
deleted file mode 100644
index 25d9f4a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_decl_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png
deleted file mode 100644
index ca64574..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/search_ref_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png
deleted file mode 100644
index 731afd1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/searchm_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/settings_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/settings_obj.png
deleted file mode 100644
index 4f09886..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/settings_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png
deleted file mode 100644
index c8fc7f3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/skip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png
deleted file mode 100644
index 9037623..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png
deleted file mode 100644
index 4a7596a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_swt_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_swt_obj.png
deleted file mode 100644
index 7ac6c73..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/template_swt_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/testfile_obj.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/testfile_obj.gif
deleted file mode 100644
index 9ddabac..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/testfile_obj.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png
deleted file mode 100644
index 493b281..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/translate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png
deleted file mode 100644
index 3d0824d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/type_separator.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png
deleted file mode 100644
index 5d29a40..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/typevariable_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png
deleted file mode 100644
index 37c7e9c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/unknown_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png
deleted file mode 100644
index 9cc943c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_gray_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png
deleted file mode 100644
index 67f30b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/obj16/warning_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png
deleted file mode 100644
index 658b8fd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/abstract_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/annotation_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/annotation_tsk.png
deleted file mode 100644
index d7208f3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/annotation_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png
deleted file mode 100644
index 02ed83e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/callee_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png
deleted file mode 100644
index 4adf45e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/caller_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_abs_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_abs_tsk.png
deleted file mode 100644
index bb0df79..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_abs_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_tsk.png
deleted file mode 100644
index 546a4e3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/class_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png
deleted file mode 100644
index 65964a9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/constr_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png
deleted file mode 100644
index ee5d9da..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/deprecated.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/enum_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/enum_tsk.png
deleted file mode 100644
index a1913c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/enum_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png
deleted file mode 100644
index d8f0680..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/error_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png
deleted file mode 100644
index ec1b034..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/final_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png
deleted file mode 100644
index abba822..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/focus_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png
deleted file mode 100644
index d3495df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/implm_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/interface_tsk.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/interface_tsk.png
deleted file mode 100644
index 961406a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/interface_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png
deleted file mode 100644
index 11cf64a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/java_ovr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/library_ovr.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/library_ovr.gif
deleted file mode 100644
index 3013a8d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/library_ovr.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png
deleted file mode 100644
index c4d5851..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png
deleted file mode 100644
index bb410c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/native_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png
deleted file mode 100644
index 573da35..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/over_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png
deleted file mode 100644
index 06b42b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/read.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png
deleted file mode 100644
index e9ea7eb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/recursive_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png
deleted file mode 100644
index d253a17..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/run_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png
deleted file mode 100644
index 655c9c0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/static_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png
deleted file mode 100644
index 1f936bd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_impl.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png
deleted file mode 100644
index 9c85c44..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/sync_over.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png
deleted file mode 100644
index 2e950e9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/synch_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png
deleted file mode 100644
index cd99249..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/volatile_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png
deleted file mode 100644
index 5e0b018..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/warning_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png
deleted file mode 100644
index 5e0b018..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.jdt.ui/ovr16/write.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/date_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/date_mode.png
deleted file mode 100644
index 77a20ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/date_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/filter_ps.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/filter_ps.png
deleted file mode 100644
index 3f6d29e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/filter_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/prj_mode.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/prj_mode.png
deleted file mode 100644
index 52b9bc1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/elcl16/prj_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/change.png
deleted file mode 100644
index bde11f1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/composite_change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/composite_change.png
deleted file mode 100644
index 4691b33..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/composite_change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/date_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/date_obj.png
deleted file mode 100644
index a24c718..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/date_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/error_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/error_obj.png
deleted file mode 100644
index e66c98e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/error_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/fatalerror_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/fatalerror_obj.png
deleted file mode 100644
index 9ff8c1e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/fatalerror_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/file_change.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/file_change.png
deleted file mode 100644
index 2d5eef0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/file_change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/info_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/info_obj.png
deleted file mode 100644
index 6cb6b84..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/info_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactoring_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactoring_obj.png
deleted file mode 100644
index 5770dbb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactoring_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactorings_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactorings_obj.png
deleted file mode 100644
index 0959e1c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/refactorings_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/text_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/text_edit.png
deleted file mode 100644
index cef1319..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/text_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/time_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/time_obj.png
deleted file mode 100644
index 8711d4c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/time_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/warning_obj.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/warning_obj.png
deleted file mode 100644
index 67f30b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ltk.ui.refactoring/obj16/warning_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/clear_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/clear_co.png
deleted file mode 100644
index 3a5e8a9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/clear_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/console_view.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/console_view.png
deleted file mode 100644
index 50720c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/console_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/cut_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/cut_edit.png
deleted file mode 100644
index 2413278..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/cut_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/lock_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/lock_co.png
deleted file mode 100644
index ffd1bc3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/lock_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/new_con.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/new_con.png
deleted file mode 100644
index d136786..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/new_con.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/paste_edit.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/paste_edit.png
deleted file mode 100644
index 3bf2701..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/paste_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/pin.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/pin.png
deleted file mode 100644
index f6b1404..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/pin.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/rem_co.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/rem_co.png
deleted file mode 100644
index ccfc9b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.console/elcl16/rem_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/next_nav.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/next_nav.png
deleted file mode 100644
index 0328357..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/next_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/prev_nav.png b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/prev_nav.png
deleted file mode 100644
index 830c2c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/prev_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/show_whitespace_chars.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/show_whitespace_chars.gif
deleted file mode 100644
index a2587b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.editors/etool16/show_whitespace_chars.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.workbench.texteditor/etool16/block_selection_mode.gif b/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.workbench.texteditor/etool16/block_selection_mode.gif
deleted file mode 100644
index dc486d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/images/org.eclipse.ui.workbench.texteditor/etool16/block_selection_mode.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/notices.html b/bundles/org.eclipse.jdt.doc.user/notices.html
deleted file mode 100644
index b2201a7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2009.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/plugin.properties b/bundles/org.eclipse.jdt.doc.user/plugin.properties
deleted file mode 100644
index 129d417..0000000
--- a/bundles/org.eclipse.jdt.doc.user/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2008 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName=Eclipse Java development user guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.jdt.doc.user/plugin.xml b/bundles/org.eclipse.jdt.doc.user/plugin.xml
deleted file mode 100644
index 0b582ce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/plugin.xml
+++ /dev/null

@@ -1,59 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-
-<!-- ===================================================== -->
-<!-- Declare the documentation for the JDT User Guide  -->
-<!-- We will declare only one infoset (book)               -->
-<!-- ===================================================== -->
-
-<plugin>
-
-
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc"> 
-       <toc file="toc.xml" primary="true" />
-       <index path="index"/>
-   </extension>
-
-
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc">
-       <toc file="topics_GettingStarted.xml" />
-       <toc file="topics_Concepts.xml" />
-       <toc file="topics_Tasks.xml" />
-       <toc file="topics_Reference.xml" />
-   </extension>
-
-
-<!-- ============================================================================= -->
-<!-- F1 context files                                                              -->
-<!-- ============================================================================= -->
-
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_JDT.xml" plugin="org.eclipse.jdt.ui"/> 
-	</extension>
-
-	<extension point="org.eclipse.help.contexts">
-		<contexts file="contexts_Debugger.xml" plugin="org.eclipse.debug.ui"/> 
-		<contexts file="contexts_Debugger.xml" plugin="org.eclipse.ui.console"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts">
-		<contexts file="contexts_JDT_Debugger.xml" plugin="org.eclipse.jdt.debug.ui"/> 
-	</extension>
-
-	<extension point="org.eclipse.help.contexts">
-		<contexts file="contexts_JDT_JUnit.xml" plugin="org.eclipse.jdt.junit"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts">
-   		<contexts file="contexts_APT.xml" plugin="org.eclipse.jdt.apt.ui"/>
-	</extension>
-
-</plugin>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_caught.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_caught.PNG
deleted file mode 100644
index 1065674..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_caught.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_condition.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_condition.PNG
deleted file mode 100644
index e81b353..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_condition.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_enabled.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_enabled.PNG
deleted file mode 100644
index a45108b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_enabled.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_entry.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_entry.PNG
deleted file mode 100644
index b6c9ec4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_entry.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_exit.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_exit.PNG
deleted file mode 100644
index da620b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_exit.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_hitcount.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_hitcount.PNG
deleted file mode 100644
index 3c742ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_hitcount.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendpolicy.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendpolicy.PNG
deleted file mode 100644
index 17482ed..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendpolicy.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendsubclass.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendsubclass.PNG
deleted file mode 100644
index 85e8369..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_suspendsubclass.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_uncaught.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_uncaught.PNG
deleted file mode 100644
index 4c704c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-breakpoint_uncaught.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_access_option.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_access_option.PNG
deleted file mode 100644
index 18ee045..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_access_option.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_mod.PNG b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_mod.PNG
deleted file mode 100644
index 3f4b207..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/images/ref-watchpoint_mod.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-access_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-access_option.htm
deleted file mode 100644
index dd6abaa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-access_option.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Watchpoint Field Access</title>
-</head>
-<body>
-<h1> Watchpoint Field Access </h1>
-<p> Select the <strong>Field Access </strong>option to suspend execution when the associated field is accessed (read). </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>,  or by <a href="../../reference/views/breakpoints/ref-access_contextaction.htm">right-clicking</a> a watchpoint. </p>
-<p><img src="images/ref-watchpoint_access_option.PNG" alt="The 'access' option for a watchpoint"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a> <br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../reference/views/breakpoints/ref-properties_contextaction.htm">Opening the Breakpoint Properties Dialog</a><br>
-  <a href="../../reference/views/breakpoints/ref-access_contextaction.htm">Watchpoint Access Context Action </a><br>
-  <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-caught_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-caught_option.htm
deleted file mode 100644
index 59667f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-caught_option.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Exception Breakpoint Caught Exception</title>
-</head>
-<body>
-<h1>Exception Breakpoint Caught Exception </h1>
-<p> Select the <strong>Caught Exception</strong> option to suspend execution when an exception of the same type as the breakpoint is thrown in a caught location. </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-caught_contextaction.htm">right-clicking</a> an exception breakpoint.</p>
-<p><img src="images/ref-breakpoint_caught.PNG" alt="Exception breakpoint caught option"></p>
-<p>&nbsp;</p>
-<p> <img src="../../images/ngrelc.png" alt="Related concepts" ></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img src="../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../tasks/task-catching_exceptions.htm">Catching exceptions</a><br>
-  <a href="../../tasks/tasks-create-exception-filter-expression.htm">Creating Exception Breakpoint Filters</a> <br>
-  <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a> <br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../views/breakpoints/ref-addexception_viewaction.htm">Add Java exception breakpoint</a><br>
-  <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-condition_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-condition_option.htm
deleted file mode 100644
index c5bd12f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-condition_option.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Enable Condition</title>
-</head>
-<body>
-<h1>Breakpoint Enable Condition</h1>
-<p>Select the <strong>Enable Condition</strong> option to enable the ability to provide a custom condition for the breakpoint. </p>
-<p>Each breakpoint can have a unique condition that determines when the breakpoint will be hit.</p>
-<p>A condition for a breakpoint can be any logical expression that evaluates to either true or false.
-  The expression is evaluated in the scope of the breakpoint location, meaning you cannot make reference to a class, etc., outside the scope of the breakpoint
-  location when composing your expression. </p>
-<p>Consider the following example:</p>
-<pre>public class Person {
-
-	String name = "";
-	int age = 0;
-
-	public Person(String name, int age) {
-		this.name = name;
-		this.age = age;		//breakpoint here
-  }
-};</pre>
-<p>If we take the above example, place a breakpoint where indicated and go to the breakpoint properties we can add our condition. In this case we are limited only to the members of the class the breakpoint is contained in and those provided by Object.</p>
-<p>For example a valid condition could be:</p>
-<pre>	age == 56 </pre>
-<p>meaning the breakpoint would only suspend when age was equal to 56.</p>
-<p>Conditions can be added to breakpoints with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoints Properties...</strong></a> shown below. </p>
-<p><img src="images/ref-breakpoint_condition.PNG" alt="Breakpoint condition option"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts"></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks"> </p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a><br>
-  <a href="../../reference/breakpoints/ref-entry_option.htm">Method Entry</a><br>
-  <a href="../../reference/breakpoints/ref-exit_option.htm">Method Exit</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-enabled_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-enabled_option.htm
deleted file mode 100644
index 85b6d20..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-enabled_option.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Enabled</title>
-</head>
-<body>
-<h1>Breakpoint Enabled</h1>
-<p>Select the <strong>Enabled</strong> option to enable or disable a breakpoint. </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>,  by <a href="../../reference/views/breakpoints/ref-enable_contextaction.htm">right-clicking</a> a breakpoint, or by selecting the breakpoint or its grouping in the <strong><a href="../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></strong>. </p>
-<p><img src="images/ref-breakpoint_enabled.PNG" alt="Breakpoint enabled option"></p>
-<p>&nbsp;</p>
-<p> <img  src="../../images/ngrelc.png" alt="Related concepts"></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img  src="../../images/ngrelt.png" alt="Related tasks"> </p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a><br>
-</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-entry_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-entry_option.htm
deleted file mode 100644
index 867211d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-entry_option.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Method Entry</title>
-</head>
-<body>
-<h1> Breakpoint Method Entry</h1>
-<p> Select the <strong>Method Entry</strong> option to suspend execution when the method associated with the breakboint is entered. </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-entry_contextaction.htm">right-clicking</a> a method breakpoint.</p>
-<p><img src="images/ref-breakpoint_entry.PNG" alt="Method breakpoint entry option"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts"></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a><br>
-  <a href="../../reference/breakpoints/ref-exit_option.htm">Method Exit</a><br>
-  <a href="../../reference/breakpoints/ref-condition_option.htm">Breakpoint Conditions</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-exit_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-exit_option.htm
deleted file mode 100644
index 83802d3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-exit_option.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Method Exit</title>
-</head>
-<body>
-<h1> Breakpoint Method Exit</h1>
-<p> Select the <strong>Method Exit</strong> option to suspend execution when the method associated with the breakpoint is exited. </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-exit_contextaction.htm">right-clicking</a> a method breakpoint.</p>
-<p><img src="images/ref-breakpoint_exit.PNG" alt="Method breakpoint exit option"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts"></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a><br>
-  <a href="../../reference/breakpoints/ref-exit_option.htm">Method Exit</a><br>
-  <a href="../../reference/breakpoints/ref-condition_option.htm">Breakpoint Conditions</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-hitcount_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-hitcount_option.htm
deleted file mode 100644
index 9a444da..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-hitcount_option.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Hit Count</title>
-</head>
-<body>
-<h1> Breakpoint Hit Count</h1>
-<p> Select the <strong>Hit Count </strong>option to define a hit count for the selected breakpoint. </p>
-<p>The <strong>Hit Count</strong> option is used to determine when your program should suspend on that breakpoint. </p>
-<p>If a breakpoint has a hit count of <em>N</em>, execution will suspend when the breakpoint is encountered for the <em>N</em>th time. After being hit, the breakpoint is disabled until either it is re-enabled or its hit count is changed.<br>
-  <br>
-  This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-hitcount_contextaction.htm">right-clicking</a> a breakpoint.</p>
-<p><img src="images/ref-breakpoint_hitcount.PNG" alt="Breakpoint hit count option"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts" ></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a> <br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a><br>
-</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-modification_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-modification_option.htm
deleted file mode 100644
index ccc8a92..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-modification_option.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Watchpoint Field Modification</title>
-</head>
-<body>
-<h1> Watchpoint Field Modification</h1>
-<p> Select this option to suspend execution when the associated field is modified (written). </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-modification_contextaction.htm">right-clicking</a> a watchpoint. </p>
-<p><img src="images/ref-watchpoint_mod.PNG" alt="Watchpoint field modification option"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm">Opening the Breakpoint Properties Dialog</a><br>
-  <a href="../../reference/views/breakpoints/ref-modification_contextaction.htm">Watchpoint Modification Context Action </a><br>
-  <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a><br>
-</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendpolicy_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendpolicy_option.htm
deleted file mode 100644
index 9e37cfe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendpolicy_option.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-<title>Breakpoint Suspend Policy</title>
-</head>
-<body>
-<h1>Breakpoint Suspend Policy</h1>
-<p>The <strong>Suspend Policy</strong>  option is used to indicate what should be suspended when a  breakpoint is hit. </p>
-<p>There are two options for Java breakpoints:</p>
-<ul>
-  <li>Suspend Thread - suspends only the thread that encountered the breakpoint</li>
-  <li>Suspend VM - suspends the entire VM when the breakpoint is encountered<br>
-  </li>
-</ul>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-suspendpolicy_contextaction.htm">right-clicking</a> a breakpoint.</p>
-<p><img src="images/ref-breakpoint_suspendpolicy.PNG" alt="Breakpoint suspend policy option"></p>
-<p>You can also change the default setting for the suspend policy for all newly created breakpoints. </p>
-<p>To do this go to the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaDebugPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java Debug preference page"> <strong>Java &gt;Debug</strong></a> preference page and change it there. </p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts"></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks"> </p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendsubclass_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendsubclass_option.htm
deleted file mode 100644
index d579885..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-suspendsubclass_option.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Exception Breakpoint Suspend on Subclass of this Exception</title>
-</head>
-<body>
-<h1> Exception Breakpoint Suspend on Subclass of this Exception </h1>
-<p> Select the <strong>Suspend on Subclass of this Exception</strong> option to suspend execution when subclasses of the exception type are encountered.</p>
-<p>For example, if an exception breakpoint for <code>RuntimeException</code> is configured to suspend on subclasses, it will also be triggered by a <code>NullPointerException</code>. </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-suspendpolicy_contextaction.htm">right-clicking</a> a breakpoint.</p>
-<p><img src="images/ref-breakpoint_suspendsubclass.PNG" alt="Exception breakpoint suspend on subclass option"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts"></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks"> </p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../views/breakpoints/ref-addexception_viewaction.htm">Add Java exception breakpoint</a><br>
-  <a href="../../reference/breakpoints/ref-enabled_option.htm">Enabled Option </a><br>
-  <a href="../../reference/breakpoints/ref-hitcount_option.htm">Hit Count</a><br>
-  <a href="../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy</a><br>
-  <a href="../../reference/breakpoints/ref-caught_option.htm">Caught Option</a><br>
-  <a href="../../reference/breakpoints/ref-uncaught_option.htm">Uncaught Option</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-uncaught_option.htm b/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-uncaught_option.htm
deleted file mode 100644
index 89fa30c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/breakpoints/ref-uncaught_option.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Exception Breakpoint Uncaught Exception</title>
-</head>
-<body>
-<h1> Exception Breakpoint Uncaught Exception </h1>
-<p> Select the <strong>Uncaught Exception</strong> option to suspend execution when an exception of the same type as the breakpoint is thrown in an uncaught location. </p>
-<p>This option can be changed with the <a href="../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a>, or by <a href="../../reference/views/breakpoints/ref-uncaught_contextaction.htm">right-clicking</a> an exception breakpoint.</p>
-<p><img src="images/ref-breakpoint_uncaught.PNG" alt="Exception breakpoint uncaught option"></p>
-<p>&nbsp;</p>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts" ></p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../tasks/task-catching_exceptions.htm">Catching exceptions</a><br>
-  <a href="../../tasks/tasks-create-exception-filter-expression.htm">Creating Exception Breakpoint Filters</a> <br>
-  <a href="../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-</p>
-<p> <img border="0" src="../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../views/breakpoints/ref-addexception_viewaction.htm">Add Java exception breakpoint</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/images/c-quickfix.png b/bundles/org.eclipse.jdt.doc.user/reference/images/c-quickfix.png
deleted file mode 100644
index 1eb9de7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/images/c-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/images/contentassist.png b/bundles/org.eclipse.jdt.doc.user/reference/images/contentassist.png
deleted file mode 100644
index 4c317e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/images/contentassist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/images/ref-breadcrumb.png b/bundles/org.eclipse.jdt.doc.user/reference/images/ref-breadcrumb.png
deleted file mode 100644
index d2e1f9a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/images/ref-breadcrumb.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/add_class_load_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/add_class_load_dialog.PNG
deleted file mode 100644
index 77f849a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/add_class_load_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_as.PNG b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_as.PNG
deleted file mode 100644
index 000f524..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_as.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_dialog.PNG
deleted file mode 100644
index 055b53e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_history.PNG b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_history.PNG
deleted file mode 100644
index 4ce28d3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-debug_history.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_as.PNG b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_as.PNG
deleted file mode 100644
index 68ad01f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_as.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_dialog.PNG
deleted file mode 100644
index bd92b77..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_history.PNG b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_history.PNG
deleted file mode 100644
index c1fb2ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/images/ref-run_history.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-add_class_load_breakpoint.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-add_class_load_breakpoint.htm
deleted file mode 100644
index 736c7ff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-add_class_load_breakpoint.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Add Class Load Breakpoint</title>
-</head>
-<body>
-<h1> Add Class Load Breakpoint </h1>
-<p> Select the <strong>Add Class Load Breakpoint</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/obj16/class_obj.png" alt="Add Class Load Breakpoint"> ] to add a Java class load breakpoint. </p>
-<p>In the resulting dialog: </p>
-<ul>
-  <li> In the <strong>Choose a Type </strong> field, type a string that is contained in the name of the exception you want to add. You can use wildcards as needed
-    (&quot;<em>*</em> &quot; for any string and &quot;<em>?</em> &quot; for any character). </li>
-  <li> In the <strong>Matching items </strong> list , select the exception you want to add. </li>
-</ul>
-<p>The <strong>Add Class Load Breakpoint Dialog</strong>.</p>
-<p><img src="../../../reference/menus/run/images/add_class_load_dialog.PNG" alt="Add Class Load Breakpoint Dialog"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p><a href="../../../tasks/task-catching_exceptions.htm">Catching Java exceptions</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a> <br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../concepts/concept-java-editor.htm">Java Editor</a><br>
-  <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-addwatch.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-addwatch.htm
deleted file mode 100644
index a64414f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-addwatch.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Watch Expression</title>
-</head>
-<body>
-<h1> Watch Expression</h1>
-<p> Select the <strong>Watch Expression </strong>command [ <img src="../../../images/org.eclipse.debug.ui/obj16/expression_obj.png" alt="Add Watch Expression"> ] to  create a new expression  from the current text selection and add it to the <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong>.</p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> <br>
-  <a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_as.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_as.htm
deleted file mode 100644
index e977c9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_as.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Debug As</title>
-</head>
-<body>
-<h1> Debug As </h1>
-<p> Select the <strong>Debug As </strong>command  to  select a way to launch the current selection from the resulting fly-out menu.</p>
-<p>An example  fly-out menu for the <strong>Debug As</strong> command. </p>
-<p><img src="../../../reference/menus/run/images/ref-debug_as.PNG" alt="Debug As Fly-Out Menu"></p>
-<p>&nbsp;</p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_history.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_history.htm
deleted file mode 100644
index 159d958..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-debug_history.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Debug History</title>
-</head>
-<body>
-<h1> Debug History </h1>
-<p> Select the <strong>Debug History </strong>command  to view a listing of the recent launch configurations for the run mode.</p>
-<p>An example fly-out menu for the <strong>Debug History </strong> command. </p>
-<p><img src="../../../reference/menus/run/images/ref-debug_history.PNG" alt="Debug History Fly-Out"></p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-dll_debug.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-dll_debug.htm
deleted file mode 100644
index eef56e9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-dll_debug.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-<title>Debug Last Launched / Debug</title>
-</head>
-<body>
-<h1> Debug Last Launched / Debug </h1>
-<p> Select the <strong>Debug Last Launched / Debug </strong>command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/debuglast_co.png" alt="Debug Last Launched"> ] to re-launch the last configuration or launch the current selection in <em>debug</em> mode. You can also use the keyboard shortcut <em><strong>F11</strong> </em></p>
-<p>New in 3.3 is the ability to launch the selected resource. This feature shares the <strong>Debug Last Launched</strong> command, so when it is enabled, it in effect replaces the the <strong>Debug Last Launched</strong> with the <strong>Debug</strong> command. </p>
-<p>The preference for launching last or launching the selected resource can be changed on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Heap Walking preference page"> <strong>Run/Debug &gt; Launching</strong></a> preference page. </p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks"></p>
-<p><a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Adding Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img border="0" src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../preferences/run-debug/ref-run_debug.htm">Debug Preferences</a><br>
-  <a href="../../ref-toolbar-run.htm">Run and Debug toolbar actions</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-menu-run.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-menu-run.htm
deleted file mode 100644
index 5ec5b55..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-menu-run.htm
+++ /dev/null

@@ -1,238 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Run Menu Actions</title>
-</head>
-<body>
-<h1>Run Menu Actions</h1>
-<p>The <strong>Run Menu</strong>, found on the main menu of the <strong>Eclipse</strong> workbench contains all of the actions required run, debug, step through code and work with breakpoints. Different parts of the<br>
-  menu are visible at different times, as each <a href="../../../concepts/concept-java-perspective.htm">perspective</a> can be customized to show only specific capabilities.</p>
-<p>The <strong>Run Menu </strong>commands. </p>
-<table border="1" cellpadding="5" cellspacing="0" summary="The actions available in the Run Menu">
-  <caption>
-  Run Menu Commands
-  </caption>
-  <thead>
-    <tr>
-      <th width="71" colspan="1" rowspan="1"> <p> Command </p></th>
-      <th width="215" colspan="1" rowspan="1"> <p> Name </p></th>
-      <th width="862" colspan="1" rowspan="1"> <p> Description </p></th>
-      <th width="118" colspan="1" rowspan="1"> <p> Shortcut </p></th>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png" alt="Add Java Exception Breakpoint"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../views/breakpoints/ref-addexception_viewaction.htm"><strong>Add Java Exception Breakpoint</strong></a> </td>
-      <td colspan="1" valign="top" align="left">Opens the Add Java Exception dialog to select the exception breakpoint type to create </td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/class_obj.png" alt="Add Class Load Breakpoint"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/menus/run/ref-add_class_load_breakpoint.htm">Add Class Load Breakpoint </a></strong></td>
-      <td colspan="1" valign="top" align="left">Opens the Select Type dialog to select the Java type to add a class load breakpoint to </td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png" alt="All Instances"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/views/shared/ref-allinstances.htm">All Instances...</a></strong> </td>
-      <td colspan="1" valign="top" align="left">Displays all of the instances of the selected type in the current VM in a popup (only available with a Java 1.6 VM) </td>
-      <td>Ctrl + Shift + N </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_references.png" alt="All References"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/views/shared/ref-allreferences.htm">All References...</a></strong></td>
-      <td colspan="1" valign="top" align="left">Displays all of the references of the selected type in the current VM in a popup (only available with a Java 1.6 VM)</td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-debug_as.htm">Debug As</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Presents a sub menu of registered debug launch shortcuts. Launch shortcuts provide support for workbench or active editor selection sensitive launching.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/menus/run/ref-debug_history.htm"><strong>Debug History </strong></a></td>
-      <td colspan="1" valign="top" align="left">Presents a sub menu of the recent history of launch configurations launched in debug mode</td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/debuglast_co.png" alt="Debug Last Launched"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-dll_debug.htm">Debug Last Launched / Debug</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Allows you to quickly repeat the most recent launch in debug mode or to debug the current selection, if that mode is supported (based on your current launch settings).</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>F11</p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" alt="Display"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/views/shared/ref-display.htm">Display</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Uses the Display view to show the result of evaluating the selected expression in the context of a stack frame or variable in that thread. If the current active part is a Java Snippet Editor, the result is displayed there.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Ctrl + Shift + D</p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png" alt="Execute"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/views/shared/ref-execute.htm">Execute</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Within the context of the Java snippet editor, this command allows you to evaluate an expression but does not display a result.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Ctrl + E</p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/views/shared/ref-forcereturn.htm">Force Return</a></strong> </td>
-      <td colspan="1" valign="top" align="left">Forces the current method to return with the specified value </td>
-      <td colspan="1" valign="top" align="left">Alt + Shift + F </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" alt="Inspect"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/views/shared/ref-inspect.htm">Inspect</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Uses the Expressions view to show the result of inspecting the selected expression or variable in the context of a stack frame or variable in that thread.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Ctrl + Shift + I</p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png" alt="Open Debug Dialog"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-open_debug_dialog.htm">Open Debug Dialog...</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>This command opens the launch configuration dialog to manage debug mode launch configurations.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/run_exc.png" alt="Open Run Dialog"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-open_run_dialog.htm">Open Run Dialog...</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Opens the launch configuration dialog to manage run mode launch configurations.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../views/breakpoints/ref-removeall_viewaction.htm"><strong>Remove All Breakpoints</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Removes all of the breakpoints from the current workspace </td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/resume_co.png" align="middle"  alt="Resume"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../views/debug/ref-resume.htm">Resume</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Resumes a suspended thread. </p></td>
-      <td>F8</td>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-run_as.htm">Run As</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Presents a sub menu of registered run launch shortcuts. Launch shortcuts provide support for workbench or active editor selection sensitive launching.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-run_history.htm">Run History</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Presents a sub menu of the recent history of launch configurations launched in run mode</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/runlast_co.png" alt="Run Last Launched"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-rll_run.htm">Run Last Launched / Run</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Allows you to quickly repeat the most recent launch in run mode or quickly run the selected resource, if that mode is supported (based on your current launch settings). </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Ctrl + F11</p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/runtoline_co.png" alt="Run To Line"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/menus/run/ref-run_to_line.htm">Run To Line</a></strong> </td>
-      <td colspan="1" valign="top" align="left">Executes the program to the currently selected line in the editor </td>
-      <td>Ctrl + R </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" alt="Step Into"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> <a href="../../views/debug/ref-stepinto.htm"><strong>Step Into</strong></a> </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps into the current statement. </p></td>
-      <td>F5</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/menus/run/ref-step_into_selection.htm">Step Into Selection</a> </strong></td>
-      <td colspan="1" valign="top" align="left">Steps into the selected statement in the editor </td>
-      <td>Ctrl + F5 </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepover_co.png" alt="Step Over"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../views/debug/ref-stepover.htm">Step Over </a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps over the highlighted statement. Execution will continue 
-          at the next line either in the same method or (if you are at the end of 
-          a method) it will continue in the method from which the current method 
-          was called. </p>
-        <p> The cursor jumps to the declaration of the method and selects this line. </p></td>
-      <td>F6</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" alt="Step Return"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> <a href="../../views/debug/ref-stepreturn.htm"><strong>Step  Return</strong></a> </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps out of the current method. This option stops execution 
-          after exiting the current method. </p></td>
-      <td>F7</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/suspend_co.png" alt="Suspend"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../views/debug/ref-suspend.htm">Suspend</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Suspends the selected thread of a target so that you can 
-          browse or modify code, inspect data, step, and so on. </p></td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_co.png" alt="Terminate"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../views/debug/ref-terminate.htm">Terminate</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Terminates the selected debug target. </p></td>
-      <td>Ctrl + F2 </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/brkp_obj.png" alt="Toggle Breakpoint"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/menus/run/ref-toggle_breakpoint.htm">Toggle Breakpoint </a></strong></td>
-      <td colspan="1" valign="top" align="left">Toggles the appropriate type of breakpoint based on what is currently selected </td>
-      <td>Ctrl + Shift + B </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/brkp_obj.png" alt="Toggle Breakpoint"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/menus/run/ref-toggle_line_breakpoint.htm">Toggle Line Breakpoint</a> </strong></td>
-      <td colspan="1" valign="top" align="left">Toggles a line breakpoint on the current executable line of code </td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/brkp_obj.png" alt="Toggle Breakpoint"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/menus/run/ref-toggle_method_breakpoint.htm">Toggle Method Breakpoint</a> </strong></td>
-      <td colspan="1" valign="top" align="left">Toggles a method breakpoint on the currently selected method declaration </td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/readwrite_obj.png" alt="Toggle Watchpoint"></td>
-      <td colspan="1" valign="top" align="left"><strong><a href="../../../reference/menus/run/ref-toggle_watchpoint.htm">Toggle Watchpoint</a> </strong></td>
-      <td colspan="1" valign="top" align="left">Toggles a watchpoint on the currently selected field </td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepbystep_co.png" alt="Use Step Filters"> </td>
-      <td colspan="1" valign="top" align="left"><a href="../../views/debug/ref-usestepfilters.htm"><strong>Use Step Filters</strong></a></td>
-      <td colspan="1" valign="top" align="left">Toggles 
-        step filters on/off. When on, all step functions apply step filters.</td>
-      <td>Shift + F5 </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/watch_exp.png" alt="Watch" width="16" height="16"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong><a href="../../../reference/menus/run/ref-addwatch.htm">Watch</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Used to create a watch item. A watch item is an expression in the Expressions view whose value is updated as you debug.</p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-jdt.htm">Java development tools (JDT)</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks"></p>
-<p><a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Adding Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img border="0" src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../preferences/run-debug/ref-run_debug.htm">Debug Preferences</a><br>
-  <a href="../../ref-toolbar-run.htm">Run and Debug toolbar actions</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_debug_dialog.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_debug_dialog.htm
deleted file mode 100644
index 12d8475..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_debug_dialog.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Open Debug Dialog</title>
-</head>
-<body>
-<h1>Open Debug Dialog... </h1>
-<p> Select the <strong>Open Debug Dialog...  </strong>command  [ <img src="../../../images/org.eclipse.jdt.debug.ui/etool16/debug_exc.png" alt="Open Debug Dialog"> ] to open the launch configuration dialog, displaying all configurations that support the <em>debug</em> mode. </p>
-<p>The launch configuration dialog opened in <em>debug</em> mode:</p>
-<p><img src="../../../reference/menus/run/images/ref-debug_dialog.PNG" alt="Launch Dialog In Debug Mode"></p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_run_dialog.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_run_dialog.htm
deleted file mode 100644
index 90d44c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-open_run_dialog.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Open Run Dialog</title>
-</head>
-<body>
-<h1> Open Run Dialog </h1>
-<p> Select the <strong>Open Run Dialog... </strong>command  [ <img src="../../../images/org.eclipse.jdt.debug.ui/etool16/run_exc.png" alt="Open Run Dialog"> ] to open the launch configuration dialog, displaying all configurations that support the <em>run</em> mode. </p>
-<p>The launch configuration dialog opened in <em>run</em> mode:</p>
-<p><img src="../../../reference/menus/run/images/ref-run_dialog.PNG" alt="Launch Dialog In Run Mode"></p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-rll_run.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-rll_run.htm
deleted file mode 100644
index d122696..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-rll_run.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-<title>Run Last Launched / Run</title>
-</head>
-<body>
-<h1> Run Last Launched / Run </h1>
-<p> Select the <strong>Run Last Launched / Run </strong>command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/runlast_co.png" alt="Run Last Launched"> ] to re-launch the last configuration or launch the current selection in  <em>run</em> mode. You can also use the keyboard shortcut <em><strong>Ctrl + F11</strong> </em></p>
-<p>New in 3.3 is the ability to launch the selected resource. This feature shares the <strong>Run Last Launched</strong> command, so when it is enabled, it in effect replaces the the <strong>Run Last Launched</strong> with the <strong>Run</strong> command. </p>
-<p>The preference for launching last or launching the selected resource can be chnaged on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Heap Walking preference page"> <strong>Run/Debug &gt; Launching</strong></a> preference page. </p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks"></p>
-<p><a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Adding Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img border="0" src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../preferences/run-debug/ref-run_debug.htm">Debug Preferences</a><br>
-  <a href="../../ref-toolbar-run.htm">Run and Debug toolbar actions</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_as.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_as.htm
deleted file mode 100644
index 612d6df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_as.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Run As</title>
-</head>
-<body>
-<h1> Run As </h1>
-<p> Select the <strong>Run As </strong>command  to  select a way to launch the current selection from the resulting fly-out menu.</p>
-<p>An example fly-out menu for the <strong>Run As</strong> command. </p>
-<p><img src="../../../reference/menus/run/images/ref-run_as.PNG" alt="Run As Fly-Out Menu"></p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_history.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_history.htm
deleted file mode 100644
index e467b4a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_history.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Run History</title>
-</head>
-<body>
-<h1> Run History </h1>
-<p> Select the <strong>Run History </strong>command  to view a listing of the recent launch configurations for the run mode.</p>
-<p>An example fly-out menu for the <strong>Run History </strong> command. </p>
-<p><img src="../../../reference/menus/run/images/ref-run_history.PNG" alt="Run History Fly-Out"></p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_to_line.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_to_line.htm
deleted file mode 100644
index 33b9506..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-run_to_line.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Run To Line</title>
-</head>
-<body>
-<h1> Run To Line </h1>
-<p> Select the <strong>Run To Line </strong>command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/runtoline_co.png" alt="Run To Line"> ] to have program execution run to the   line number of the current caret position. You can also use the shortcut <strong><em>Ctrl + R</em> </strong></p>
-<p>You must have program execution suspended for this command to be available. </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ><br>
-  <br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../concepts/concept-java-editor.htm">Java Editor</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../../reference/views/debug/ref-relaunch.htm">Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated</a> <br>
-  <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a><br>
-  <a href="../../../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-step_into_selection.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-step_into_selection.htm
deleted file mode 100644
index 5c9dc14..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-step_into_selection.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Step into Selection</title>
-</head>
-<body>
-<h1> Step Into Selection </h1>
-<p> Select the <strong>Step Into Selection </strong>command to step into the currently selected statement in the active editor. </p>
-<p>You must have program execution suspended for this command to be available. </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p><a href="../../../tasks/task-resuming_threads.htm">Resuming</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../concepts/concept-java-editor.htm">Java Editor</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../../reference/views/debug/ref-relaunch.htm">Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated</a> <br>
-  <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a><br>
-  <a href="../../../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_breakpoint.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_breakpoint.htm
deleted file mode 100644
index 28c6d23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_breakpoint.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Toggle Breakpoint</title>
-</head>
-<body>
-<h1> Toggle Breakpoint</h1>
-<p> Select the <strong>Toggle Breakpoint </strong>command [<img src="../../../images/org.eclipse.debug.ui/obj16/brkp_obj.png" alt="Toggle Breakpoints">] to  create a new breakpoint at the given location. You can also use the global keyboard shortcut <strong><em>Ctrl + Shift + B</em> </strong></p>
-<p>Depending on the location and/or selection in the source file, this command will set the correct type of breakpoint for given the location/selection. </p>
-<p>For example, if you have the name of a class selected and activate the command, you will get a class load breakpoint on that class; alternatively, if you have a field selected and activate the command, you will get a watchpoint on the field. </p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../concepts/concept-java-editor.htm">Java Editor</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/views/breakpoints/ref-addexception_viewaction.htm">Add Java Exception Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-add_class_load_breakpoint.htm">Add Class Load Breakpoint</a> <br>
-  <a href="../../../reference/menus/run/ref-toggle_line_breakpoint.htm">Toggle Line Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-toggle_method_breakpoint.htm">Toggle Method Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-toggle_watchpoint.htm">Toggle Watchpoint</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_line_breakpoint.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_line_breakpoint.htm
deleted file mode 100644
index 2a5842b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_line_breakpoint.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Toggle Line Breakpoint</title>
-</head>
-<body>
-<h1> Toggle Line Breakpoint</h1>
-<p> Select the <strong>Toggle Line Breakpoint </strong>command [<img src="../../../images/org.eclipse.debug.ui/obj16/brkp_obj.png" alt="Toggle Breakpoints">] to  create a new line breakpoint at the given location.</p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../concepts/concept-java-editor.htm">Java Editor</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/views/breakpoints/ref-addexception_viewaction.htm">Add Java Exception Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-add_class_load_breakpoint.htm">Add Class Load Breakpoint </a><br>
-  <a href="../../../reference/menus/run/ref-toggle_breakpoint.htm">Toggle  Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-toggle_method_breakpoint.htm">Toggle Method Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-toggle_watchpoint.htm">Toggle Watchpoint</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_method_breakpoint.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_method_breakpoint.htm
deleted file mode 100644
index b4dc725..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_method_breakpoint.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Toggle Method Breakpoint</title>
-</head>
-<body>
-<h1> Toggle Method Breakpoint</h1>
-<p> Select the <strong>Toggle Method Breakpoint </strong>command [<img src="../../../images/org.eclipse.debug.ui/obj16/brkp_obj.png" alt="Toggle Breakpoints">] to  create a new method breakpoint for the currently selected method in the editor or in the <a href="../../../reference/views/ref-view-outline.htm"><strong>Outline View</strong></a>.</p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../concepts/concept-java-editor.htm">Java Editor</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/views/breakpoints/ref-addexception_viewaction.htm">Add Java Exception Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-add_class_load_breakpoint.htm">Add Class Load Breakpoint</a> <br>
-  <a href="../../../reference/menus/run/ref-toggle_breakpoint.htm">Toggle Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-toggle_line_breakpoint.htm">Toggle Line Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-toggle_watchpoint.htm">Toggle Watchpoint</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_watchpoint.htm b/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_watchpoint.htm
deleted file mode 100644
index c542cdc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/menus/run/ref-toggle_watchpoint.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Toggle Watchpoint</title>
-</head>
-<body>
-<h1> Toggle Watchpoint </h1>
-<p> Select the <strong>Toggle Watchpoint </strong>command [ <img src="../../../images/org.eclipse.debug.ui/obj16/readwrite_obj.png" alt="Toggle Watchpoint"> ] to  create a new watchpoint on the selected field in either the editor or the <a href="../../../reference/views/ref-view-outline.htm"><strong>Outline View</strong></a>.</p>
-<p>Note that you cannot set a watchpoint on a <code>final</code> or a <code>static final</code> field; if you try to do so you will get a line breakpoint instead. </p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p><a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote Debugging</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching exceptions</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../concepts/concept-java-editor.htm">Java Editor</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/views/breakpoints/ref-addexception_viewaction.htm">Add Java Exception Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-add_class_load_breakpoint.htm">Add Class Load Breakpoint</a> <br>
-  <a href="../../../reference/menus/run/ref-toggle_breakpoint.htm">Toggle Breakpoint</a> <br>
-  <a href="../../../reference/menus/run/ref-toggle_line_breakpoint.htm">Toggle Line Breakpoint</a><br>
-  <a href="../../../reference/menus/run/ref-toggle_method_breakpoint.htm">Toggle Method Breakpoint</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-member-sort-order.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-member-sort-order.htm
deleted file mode 100644
index 5c09781..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-member-sort-order.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Member Sort Order Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Member Sort Order Preferences</h1>
-<p>Indicate your preferences for the Member Sort Order settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.MembersOrderPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Member Sort Order preference page"><b> Java &gt; Appearance &gt; Member Sort Order </b></a> preference page.</p>
-<p>This settings are used by Java views as well as by the Sort Members Action.</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Member sort order settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">Choose the order in which members will be displayed.</td>
-			<td valign="top">
-			<dl>
-				<dt><strong>Up</strong></dt>
-				<dd>Move members of selected category closer to the beginning of a type.</dd>
-				<dt><strong>Down</strong></dt>
-				<dd>Move members of selected category closer to the end of a type.</dd>
-			</dl>
-			</td>
-			<td valign="top">Types, Static Fields, Static Initializers, Static Methods, Fields, Initializers, Constructors, Methods</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Sort members in same category by visibility</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, members of same category are sorted by visibility within the category.</p>
-			<dl>
-				<dt><strong>Up</strong></dt>
-				<dd>Move members of selected visibility closer to the beginning of a category.</dd>
-				<dt><strong>Down</strong></dt>
-				<dd>Move members of selected visibility closer to the end of a category.</dd>
-			</dl>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			<p>Public, Private, Protected, Default</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p><a href="../../../../concepts/concept-java-views.htm">Java views</a></p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/views/ref-view-package-explorer.htm">Package Explorer view</a><br>
-<a href="../../../../reference/ref-menu-source.htm">Source Actions</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-type-filters.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-type-filters.htm
deleted file mode 100644
index cbc9ed3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/appearance/ref-preferences-type-filters.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Type Filters</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Type Filters Preferences</h1>
-<p>Indicate your preferences for the Type Filters settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.TypeFilterPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Type Filters	preference page"><b> Java &gt; Appearance &gt; Type Filters </b></a> preference page.</p>
-<p>Specify types and packages to hide in the 'Open Type' dialog and content assist or quick fix proposals on this preference site.
-If a qualified type name or a package match one of the checked entries in the list, they will be hidden.
-</p>
-<p>The default is to hide nothing.</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="Enabled type filters">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">Add</td>
-			<td valign="top">Adds a new entry to the list. Entries will be compared against qualified type name (using dots as package name separators) and can use wild cards ('*' and '?')</td>
-		</tr>
-		<tr>
-			<td valign="top">Add Packages</td>
-			<td valign="top">Adds a new entry to the list from the list of existing packages currently in the workspace. </td>
-		</tr>
-		<tr>
-			<td valign="top">Edit</td>
-			<td valign="top">Edits the currently selected entry</td>
-		</tr>
-		<tr>
-			<td valign="top">Remove</td>
-			<td valign="top">Removes the currently selected entries</td>
-		</tr>
-		<tr>
-			<td valign="top">Check All</td>
-			<td valign="top">Sets the checkmark on all entries</td>
-		</tr>
-		<tr>
-			<td valign="top">Uncheck All</td>
-			<td valign="top">Removes the checkmark on all entries</td>
-		</tr>					
-	</tbody>
-</table>
-
-
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p><a href="../../../../concepts/concept-quickfix-assist.htm">Quick fix</a></p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/ref-dialog-open-type.htm">Open type</a><br>
-<a href="../../../../reference/ref-java-editor-code-assist.htm">Content/Code assist</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm
deleted file mode 100644
index 3166e73..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm
+++ /dev/null

@@ -1,117 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Classpath Variables Preferences
-    </title>
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Classpath Variables Preferences
-    </h1>
-    <h2 class="Head">
-      Configurable variables
-    </h2>
-    <p>
-      Classpath variables can be used in a Java Build Path to avoid a reference to the local file system. Using a variable entry, the classpath only contains a variable and the
-      build path can be shared in a team.
-      The value of such variables is configured on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ClasspathVariablesPreferencePage)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Classpath Variables preference page">
-      <b>Java &gt; Build Path &gt; Classpath Variables</b></a> preference page.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Classpath variables">
-      <caption>
-        &nbsp;<br>
-      </caption>
-      <tr>
-        <th>
-          <p>
-            Command
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            <strong>New...</strong>
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Adds a new variable entry. In the resulting dialog, specify a name and path for the new variable. You can click the&nbsp;<strong>File</strong>
-            or&nbsp;<strong>Folder</strong> buttons to browse for a path.&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            <strong>Edit...</strong>
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Allows you to edit the selected variable entry. In the resulting dialog, edit the name and/or path for the variable. You can click the&nbsp;<strong>File</strong>
-            or&nbsp;<strong>Folder</strong> buttons to browse for a path.&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            <strong>Remove</strong>
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Removes the selected variable entry.&nbsp;
-          </p>
-        </td>
-      </tr>
-    </table>
-    <h2 class="Head">
-      Reserved class path variables
-    </h2>
-    <p>
-      Certain class path variables are set internally and can not be changed in the Classpath variables preferences:
-    </p>
-    <ul>
-      <li>
-        JRE_LIB: The archive with the runtime JAR file for the currently used JRE.
-      </li>
-      <li>
-        JRE_SRC: The source archive for the currently used JRE.
-      </li>
-      <li>
-        JRE_SRCROOT: The root path in the source archive for the currently used JRE.
-      </li>
-    </ul>
-    <p>
-      These variables are deprecated and should not be used anymore. Instead <a href="../../../ref-properties-build-path.htm">use a JRE System Library</a>.
-    </p>
-    <p>
-      <img src="../../../../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../../../../concepts/concept-classpath-variables.htm">Classpath variables</a>
-    </p>
-    <p>
-      <img src="../../../../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../../../preferences/java/ref-preferences-installed-jres.htm">Installed JREs</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-user-libraries.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-user-libraries.htm
deleted file mode 100644
index 9a64d1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/buildpath/ref-preferences-user-libraries.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>User Libraries</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>User Libraries Preferences</h1>
-<p>Indicate your preferences for the User Libraries settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.UserLibraryPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the User Libraries preference page">
-<b> Java &gt; Build Path &gt; User Libraries </b></a> preference page.</p>
-<p>A user library is a set of JAR files. A user library can be added to a projects build path
-through the build path properties page. The User Libraries preference page allows to define,
-edit, import, export, or remove user libraries.</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="User libararies">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">New...</td>
-			<td valign="top">Creates a new user library</td>
-		</tr>
-		<tr>
-			<td valign="top">Edit...</td>
-			<td valign="top">Edits the currently selected library, JAR or JAR attribute</td>
-		</tr>
-		<tr>
-			<td valign="top">Add JARs...</td>
-			<td valign="top">Adds one or more JARs to the currently selected user library</td>
-		</tr>		
-		
-		<tr>
-			<td valign="top">Remove..</td>
-			<td valign="top">Removes the currently selected user library or JAR</td>
-		</tr>
-		<tr>
-			<td valign="top">Up</td>
-			<td valign="top">Moves the currently selected JAR up in the list of JARs of a user library. The order can be important if more than one JAR contain a type with the same qualified name.</td>
-		</tr>
-		<tr>
-			<td valign="top">Down</td>
-			<td valign="top">Moves the currently selected JAR down in the list of JARs of a user library. The order can be important if more than one JAR contain a type with the same qualified name.</td>
-		</tr>
-		<tr>
-			<td valign="top">Import...</td>
-			<td valign="top">Adds new libraries from an import file</td>
-		</tr>
-		<tr>
-			<td valign="top">Export...</td>
-			<td valign="top">Exports libraries to an import file</td>
-		</tr>			
-			
-	</tbody>
-</table>
-
-
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/ref-properties-build-path.htm">Java Build Path page</a><br></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-cleanup.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-cleanup.htm
deleted file mode 100644
index f3c0796..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-cleanup.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Clean Up Preferences
-    </title>
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Clean Up Preferences
-    </h1>
-
-<p>The
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CleanUpPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Clean Up preference page">
-<b>Java &gt; Code Style &gt; Clean Up</b></a> preference page
-lets you manage your code clean up profiles for the Java code clean up.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="All options">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Active profile</p>
-			</td>
-			<td valign="top">
-			<p>Selects the profile active for the workspace or current project.</p>
-			</td>
-		</tr>	
-		<tr>
-			<td valign="top" width="25%">
-			<p>Edit...</p>
-			</td>
-			<td valign="top">
-			<p>Shows a dialog which displays the settings stored in the active profile. Only user-defined profiles can be modified.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Remove</p>
-			</td>
-			<td valign="top">
-			<p>Removes the selected profile. This action is only available on user-defined profiles.</p>
-			</td>
-		</tr>		
-		<tr>
-			<td valign="top" width="25%">
-			<p>New...</p>
-			</td>
-			<td valign="top">
-			<p>Shows the dialog to create a new profile. The dialog requires you to enter a name for the new profile. Additionally, you may select a built-in or user-defined existing profile to base your new profile on.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Import...</p>
-			</td>
-			<td valign="top">
-			<p>Imports profiles from the file system.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Details</p>
-			</td>
-			<td valign="top">
-			<p>Displays a summary of the enabled options of the active profile</p>
-			</td>
-		</tr>	
-	</tbody>
-</table>
-<p>
-Disable <strong>Show profile selection dialog for the 'Source &gt; Clean Up' action</strong> to apply the active profile when you invoke <strong>Source &gt; Clean Up</strong> without being disturbed by a dialog. 
-</p>
-    <p>
-      <img border="0"  src="../../../../images/ngrelr.png" alt="Related reference">
-	</p>
-	<p>
-      <a href="../../../views/ref-java-editor.htm">Java editor</a><br>
-       <a href="../../../preferences/java/ref-preferences-editor.htm">Java editor preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-code-templates.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-code-templates.htm
deleted file mode 100644
index 9568e2c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-code-templates.htm
+++ /dev/null

@@ -1,347 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Code Templates Preferences
-    </title>
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Code Templates Preferences
-    </h1>
-<p>The
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeTemplatePreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Code Templates preference page">
-<b>Java &gt; Code Style &gt; Code Templates</b></a> preference page
-lets you configure the format of newly generated code and comments.</p>
-
-
-
-<h2>Code and Comments</h2>
-<p>The code and comment page contains code templates that are used by actions that generate code. Templates contain variables that are substituted when the template is applied. Some variables are available in all templates, some are specific to templates.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="Code and Comments">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>			
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Edit...</p>
-			</td>
-			<td valign="top">
-			<p>Opens the <a href="#code-template-dialog">Code Template dialog</a> to edit the currently selected code template.</p>
-			</td>
-			<td valign="top">n/a</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Import...</p>
-			</td>
-			<td valign="top">
-			<p>Imports code templates from the file system.</p>
-			</td>
-			<td valign="top">n/a</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Export...</p>
-			</td>
-			<td valign="top">
-			<p>Exports all selected code templates to the file system.</p>
-			</td>
-			<td valign="top">n/a</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Export All...</p>
-			</td>
-			<td valign="top">
-			<p>Exports all code templates to the file system.</p>
-			</td>
-			<td valign="top">n/a</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Automatically add comments for new methods and types</p>
-			</td>
-			<td valign="top">
-			<p>If selected, newly generated methods and types are automatically generated with comments where appropriate. The formats of the generated comments are
-			defined by the <a href="#comment-templates">Comment Templates</a>.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>		
-	</tbody>
-</table>
-
-
-<a name="comment-templates"></a>
-<h2>Comment Templates</h2>
-
-<p>Comment templates can   contain the variable <b>${tags}</b> that will be substituted by the standard Javadoc tags (@param, @return..) for the commented element.
-The 'Overriding method' comment can additionally contain the template <b>${see_to_overridden}</b></p>
-
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="Comment Templates">
-	<thead>
-		<tr>
-			<th>
-			<p>Template Name</p>
-			</th>
-			<th>
-			<p>Specifies</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Files</p>
-			</td>
-			<td valign="top">
-			<p>Header comment for new files.</p>
-			<p>Note that this template can be referenced in the 'New Java File' template  with <b>${filecomment}</b>.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Types</p>
-			</td>
-			<td valign="top">
-			<p>The comment for new types.</p>
-			<p> Note that this template can be referenced in the 'New Java File' template with <b>${typecomment}</b>.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Fields</p>
-			</td>
-			<td valign="top">
-			<p>The comment for new fields.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Constructors</p>
-			</td>
-			<td valign="top">
-			<p>The comment for new constructors.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Methods</p>
-			</td>
-			<td valign="top">
-			<p>The comment for new methods that do not override an method in a base class and that do not delegate to any other method.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Overriding methods</p>
-			</td>
-			<td valign="top">
-			<p>The comment for new methods that override an method in a base class.</p>
-			<p>By default the comment is defined as a non-Javadoc comment (Javadoc will replace this comment with the comment of the overridden method). 
-			You can change this to a real Javadoc comment if you want</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Delegating methods</p>
-			</td>
-			<td valign="top">
-			<p>The comment for new methods which delegate to existing methods.</p>
-			<p>Such methods can be created with the <strong>Source &gt; Generate Delegate Methods...</strong> action.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Getters</p>
-			</td>
-			<td valign="top">
-			<p>The comment for getter methods.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Setters</p>
-			</td>
-			<td valign="top">
-			<p>The comment for setter methods.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<h2>Code Templates</h2>
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="Code Templates">
-	<thead>
-		<tr>
-			<th>
-			<p>Template Name</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>New Java files</p>
-			</td>
-			<td valign="top">
-			<p>Used by the New Type wizards when a new Java file is created.</p> 
-			<p>The template can specify where comments are added. Note that the template can contain the variable <b>${typecomment}</b> and <b>${filecomment}</b> that will be substituted by the evaluation of the <b>Types</b> respectively <b>Files</b> comment template.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Class body</p>
-			</td>
-			<td valign="top">
-			<p>Used by the New Class wizards when a new Java class is created.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Interface body</p>
-			</td>
-			<td valign="top">
-			<p>Used by the New Interface wizards when a new Java interface is created.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Enum body</p>
-			</td>
-			<td valign="top">
-			<p>Used by the New Enum wizards when a new Java enum is created.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Annotation body</p>
-			</td>
-			<td valign="top">
-			<p>Used by the New Annotation wizards when a new Java annotation is created.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Method body</p>
-			</td>
-			<td valign="top">
-			<p>The 'Method body'  templates are used when new method with a body is created that still needs some code to complete its functionality.</p> 
-			<p>It contains the variable <b>${body_statement}</b> that resolves to a return statement or/and a super-call.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Constructor body</p>
-			</td>
-			<td valign="top">
-			<p>The 'Constructor body' templates are used when new method or constructor with body is created.</p>
-			<p>It contains the variable <b>${body_statement}</b> that resolves  a super call.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Getter body</p>
-			</td>
-			<td valign="top">
-			<p>The 'Getter body' templates are used when new getter method is created.</p>
-			<p>It contains the variable <b>${body_statement}</b> that resolves to the appropriate return statement.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Setter body</p>
-			</td>
-			<td valign="top">
-			<p>The 'Setter body' templates are used when new setter method is created.</p> 
-			<p>It contains the variable <b>${body_statement}</b> that resolves to the appropriate assignment statement.</p> 
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Catch block body</p>
-			</td>
-			<td valign="top">
-            <p>The 'Catch block body' template is used when a catch block body is created.</p> 
-            <p>It can use the variables <b>${exception_type}</b> and <b>${exception_var}</b>.</p> 
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<a name="code-template-dialog"></a>
-<h2>Code Template dialog</h2>
-
-<p>The following fields and buttons appear in the dialog:</p>
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Code Template dialog">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Description</p>
-			</td>
-			<td valign="top">
-			<p>A description of the template</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Pattern</p>
-			</td>
-			<td valign="top">
-			<p>The template pattern.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Insert Variables...</p>
-			</td>
-			<td valign="top">
-			<p>Displays a list of pre-defined template specific variables.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<p>
-      <img border="0"  src="../../../../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../../../ref-menu-source.htm">Source actions</a><br>
-	  <a href="../../../views/ref-java-editor.htm">Java editor</a><br>
-	  <a href="../../../preferences/java/ref-preferences-editor.htm">Java editor preferences</a><br>
-	  <a href="../../../preferences/java/editor/ref-preferences-templates.htm">Templates preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-formatter.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-formatter.htm
deleted file mode 100644
index b109e46..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-formatter.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Code Formatter Preferences
-    </title>
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Code Formatter Preferences
-    </h1>
-
-<p>The
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeFormatterPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Formatter preference page">
-<b>Java &gt; Code Style &gt; Formatter</b></a> preference page
-lets you manage your code formatter profiles for the Java code formatter.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="Formatter profile">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Active profile</p>
-			</td>
-			<td valign="top">
-			<p>Selects the profile active for the workspace or current project.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Edit...</p>
-			</td>
-			<td valign="top">
-			<p>Shows a dialog which displays the settings stored in the active profile. Only user-defined profiles can be modified.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Remove</p>
-			</td>
-			<td valign="top">
-			<p>Removes the selected profile. This action is only available on user-defined profiles.</p>
-			</td>
-		</tr>			
-		<tr>
-			<td valign="top" width="25%">
-			<p>New...</p>
-			</td>
-			<td valign="top">
-			<p>Shows the dialog to create a new profile. The dialog requires you to enter a name for the new profile. Additionally, you may select a built-in or user-defined existing profile to base your new profile on.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Import...</p>
-			</td>
-			<td valign="top">
-			<p>Imports profiles from the file system.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Details</p>
-			</td>
-			<td valign="top">
-			<p>Displays a sample how the active profile formats a Java code snippet</p>
-			</td>
-		</tr>			
-	</tbody>
-</table>
-<p>
-  To change your formatter options you can either select one of the built-in profiles or create a new profile.
-  To create a new profile select <strong>New...</strong>. You can then edit the new profile by selecting <strong>Edit...</strong>.
-</p>
-<p>
-  If your project is shared, e.g. through CVS, and uses a formatter profile which is not managed by yourself
-  (you have not created the profile) then the profile will be marked as <strong>Unmanaged Profile</strong>. You are not allowed
-  to change such a profile, only the creator (manager) of the profile can change it.
-</p>
-    <p>
-      <img border="0"  src="../../../../images/ngrelr.png" alt="Related reference">
-	</p>
-	<p>
-      <a href="../../../views/ref-java-editor.htm">Java editor</a><br>
-       <a href="../../../preferences/java/ref-preferences-editor.htm">Java editor preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-organize-imports.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-organize-imports.htm
deleted file mode 100644
index 0a88b95..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/codestyle/ref-preferences-organize-imports.htm
+++ /dev/null

@@ -1,264 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Organize Imports Preferences
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Organize Imports Preferences
-    </h1>
-    <p>
-      The
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ImportOrganizePreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Organize Imports preference page">
-      <b>Java &gt; Code Style &gt; Organize Imports</b></a> preference page
-      defines how the Organize Imports command generates the import statements in a compilation unit.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Organize imports settings">
-      <thead>
-        <tr>
-          <th rowspan="1" colspan="1">
-            <p>
-              Option
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Description
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Import order list
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This list of prefixes shows the sequential order for packages imported into a Java compilation unit. Each entry defines a block. Different blocks are separated by a
-              spacer line.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              java<br>
-              javax<br>
-              org<br>
-              com
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              New...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Adds a package name prefix to the import order list. In the resulting dialog, type a package name or package name prefix.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-         <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              New Static...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Adds a package name prefix to the import order list. In the resulting dialog, type a package name or package name prefix.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Edit...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Edits the currently selected entry in the import order list. In the resulting dialog, type a package name or package name prefix.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Remove
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Removes the currently selected entry from the import order list.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Up
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Moves the selected package name prefix up in the import order list.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Down
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Moves the selected package name prefix down in the import order list.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Import...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Loads a list of package name prefixes from a file.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Export...
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Saves the list of package name prefixes to a file.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Number of imports needed for .*
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              The number of import statements that are allowed for types in the same package before <em>&lt;package&gt;.*</em> is used.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              99
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Number of static imports needed for .*
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              The number of static import statements that are allowed for static members of the same type before <em>type</em> is used.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              99
-            </p>
-          </td>
-        </tr>        
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Do not create imports for types starting with a lower case letter
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              If enabled, types starting with a lowercase letter are not imported.
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0"  src="../../../../images/ngrelr.png" alt="Related reference">
-	</p>
-	<p>
-      <a href="../../../ref-menu-source.htm">Source actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-building.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-building.htm
deleted file mode 100644
index d29a243..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-building.htm
+++ /dev/null

@@ -1,160 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Building Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Building Preferences</h1>
-<p>Indicate your preferences for the Building settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaBuildPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Building preference page"><b> Java &gt; Compiler &gt; Building </b></a> preference page.</p>
-<h3>General</h3>
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="General section">
-	<tr>
-		<th>
-		<p>Option</p>
-		</th>
-		<th>
-		<p>Description</p>
-		</th>
-		<th>
-		<p>Default</p>
-		</th>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Maximum number of reported problems per compilation unit</p>
-		</td>
-		<td valign="top">
-		<p>Specifies how many problems should be reported for a compilation unit.</p>
-		</td>
-		<td valign="top">
-		<p>100</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Enable use of exclusion patterns in source folders</p>
-		</td>
-		<td valign="top">
-		<p>When disabled, no entry on a project classpath can be associated with an exclusion pattern.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Enable use of multiple output locations for source folders</p>
-		</td>
-		<td valign="top">
-		<p>When disabled, no entry on a project classpath can be associated with a specific output location, preventing thus usage of multiple output locations.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-</table>
-<h3>Build path problems</h3>
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Build path problems section">
-	<tr>
-		<td valign="top">
-		<p>Abort build when build path errors occur</p>
-		</td>
-		<td valign="top">
-		<p>Allow to toggle the builder to abort if the classpath is invalid.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Incomplete build path</p>
-		</td>
-		<td valign="top">
-		<p>Indicate the severity of the problem reported when an entry on the classpath does not exist, is not legitimate or is not visible (e.g. a reference project is closed).</p>
-		</td>
-		<td valign="top">
-		<p>Error</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Circular dependencies</p>
-		</td>
-		<td valign="top">
-		<p>Indicate the severity of the problem reported when a project is involved in a cycle.</p>
-		</td>
-		<td valign="top">
-		<p>Error</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Incompatible required binaries</p>
-		</td>
-		<td valign="top">
-		<p>Indicated the severity of the problem reported when a project requires incompatible binaries.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-</table>
-<h3>Output folder</h3>
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Output folder section">
-	<tr>
-		<td valign="top">
-		<p>Duplicated resources</p>
-		</td>
-		<td valign="top">
-		<p>Indicate the severity of the problem reported when more than one occurrence of a resource is to be copied into the output location.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Scrub output folders when cleaning projects</p>
-		</td>
-		<td valign="top">
-		<p>Indicate whether the Java Builder is allowed to clean the output folders when performing full build operations.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Rebuild class files modified by others</p>
-		</td>
-		<td valign="top">
-		<p>Indicate whether class files which have been modified by others should be rebuilded to undo the modification.</p>
-		</td>
-		<td valign="top">
-		<p>Off</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Filtered resources</p>
-		</td>
-		<td valign="top">
-		<p>A comma separated list of file patterns which are not copied to the output folder.&nbsp;</p>
-		</td>
-		<td valign="top">
-		<p>Empty</p>
-		</td>
-	</tr>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p><a href="../../../../concepts/concept-java-builder.htm">Java builder</a><br>
-<a href="../../../../concepts/concept-inclusion-exclusion-patterns.htm">Inclusion and exclusion patterns</a><br>
-<a href="../../../../concepts/concept-build-classpath.htm">Build classpath</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
deleted file mode 100644
index 904780c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-errors-warnings.htm
+++ /dev/null

@@ -1,718 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Compiler Errors/Warnings Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Compiler Errors/Warnings Preferences</h1>
-<p>Indicate your preferences for the Errors/Warnings settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page"> <b> Java &gt; Compiler &gt; Errors/Warnings </b></a> preference page.</p>
-<h3>Code style</h3>
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Code style section">
-	<tr>
-		<th>
-		<p>Option</p>
-		</th>
-		<th>
-		<p>Description</p>
-		</th>
-		<th>
-		<p>Default</p>
-		</th>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Non-static access to a static member</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a static field or method is accessed with an expression receiver. A reference to a static member should be qualified with a type name.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Indirect access to a static member</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a static field or method is indirectly accessed. A static field of an interface should be qualified with the declaring type name.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unqualified access to instance field</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a field access which is not qualified (e.g. misses a 'this').</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Undocumented empty block</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an empty block statement with no explaining comment.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Access to a non-accessible member of an enclosing type</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it emulates access to a non-accessible member of an enclosing type. Such accesses can have performance implications.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Method with a constructor name</p>
-		</td>
-		<td valign="top">
-		<p>Naming a method with a constructor name is generally considered poor style programming. When this option is enabled, the compiler will signal such scenario either as an error or a warning.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Parameter assignment</p>
-		</td>
-		<td valign="top">
-		<p>Assigning a value to a parameter is generally considered poor style programming. When this option is enabled, the compiler will signal such scenario either as an error or a warning.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Non-externalized strings</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning for non externalized String literal (i.e. non tagged with //$NON-NLS-&lt;n&gt;$) or for non externalized String tags which do not belong to a String.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-</table>
-
-<h3>Potential programming problems</h3>
-
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Potential programming problems section">
-	<tr>
-		<td valign="top">
-		<p>Serializable class without serialVersionUID</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a type implementing 'java.io.Serializable' does not contain a serialVersionUID field.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Assignment has no effect (e.g. 'x = x')</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever an assignment has no effect (e.g. 'x = x').</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Possible accidental boolean assignment (e.g. 'if (a = b)')</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a possible accidental boolean assignment (e.g. 'if (a = b)').</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>'finally' does not complete normally</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a 'finally' statement does not complete normally (e.g. contains a return statement).</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Empty statement</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an empty statement (e.g. a superfluous semicolon).</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Using a char array in string concatenation</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a char[] expression is used in String concatenations,</p>
-		<code>"hello" + new char[]{'w','o','r','l','d'}</code></td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Hidden catch blocks</p>
-		</td>
-		<td valign="top">
-		<p>Locally to a try statement, some catch blocks may hide others , e.g.</p>
-		<code>try { throw new java.io.CharConversionException();</code><br>
-		<code>} catch (java.io.CharConversionException e) {</code><br>
-		<code>} catch (java.io.IOException e) {}.</code><br>
-		<br>
-		<p>When enabled, the compiler will issue an error or a warning for hidden catch blocks corresponding to checked exceptions.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Inexact type match for vararg arguments</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an inexact type match for vararg arguments.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Boxing and unboxing conversions</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a boxing or unboxing conversion. Autoboxing may affects performance negatively.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Enum type constant not covered on 'switch'</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a switch statement which does not contain case statements for every enum constant of the referenced enum.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>'switch' case fall-through</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a switch case without a 'break' statement. Empty switch cases are allowed.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Null pointer access</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning when it encounters that a local variable which is certainly null is dereferenced. Note that the analysis can not find all null pointer accesses, see <strong>Potential null pointer access</strong>.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Potential null pointer access</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning when it encounters that a local variable which may be null is dereferenced. Note that the analysis is fairly conservative, it only considers cases where there is something suspicious.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Comparing identical</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning if a comparisonis involving identical operands (e.g 'x == x')..</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-</table>
-
-<h3>Name shadowing and conflicts</h3>
-
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Name shadowing and conflicts section">
-	<tr>
-		<td valign="top">
-		<p>Field declaration hides another field or variable</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning if a field declaration hides another inherited field.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Local variable declaration hides another field or variable</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning if a local variable declaration hides another field or variable.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Include constructor or setter method parameters</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler additionally will issue an error or a warning if a constructor or setter method parameter hides another field or variable.</p>
-		</td>
-		<td valign="top">
-		<p>Off</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Type parameter hides another type</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning if i.e. a type parameter of an inner class hides an outer type.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Method does not override package visible method</p>
-		</td>
-		<td valign="top">
-		<p>A package default method is not visible in a different package, and thus cannot be overridden. When this option is enabled, the compiler will signal such scenario either as an error or a warning.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Interface method conflicts with protected 'Object' method</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever an interface defines a method incompatible with a non-inherited Object method. Until this conflict is resolved, such an interface cannot be implemented, e.g.</p>
-		<code>interface I {</code><br>
-		<code>&nbsp;&nbsp;&nbsp;int clone();</code><br>
-		<code>}</code><br>
-		<br>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-</table>
-
-<h3>Deprecated and restricted API</h3>
-
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Deprecated and restricted API section">
-	<tr>
-		<td valign="top">
-		<p>Deprecated API</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will signal use of deprecated API either as an error or a warning.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Signal use of deprecated API inside deprecated code</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will signal use of deprecated API inside deprecated code. The severity of the problem is controlled with option "Deprecated API".</p>
-		</td>
-		<td valign="top">
-		<p>Off</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Signal overriding or implementing deprecated method</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will signal overriding or implementing a deprecated method The severity of the problem is controlled with option "Deprecated API".</p>
-		</td>
-		<td valign="top">
-		<p>Off</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Forbidden reference (access rules)</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will signal a forbidden reference specified in the access rules.</p>
-		</td>
-		<td valign="top">
-		<p>Error</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Discouraged reference (access rules)</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will signal a discouraged reference specified in the access rules.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-</table>
-
-<h3>Unnecessary code</h3>
-
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Unnecessary code section">
-	<tr>
-		<td valign="top">
-		<p>Local variable is never read</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a local variable is declared but never used within its scope.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Parameter is never read</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a parameter is declared but never used within its scope.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Ignore in overriding and implementing methods</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will not issue an error or a warning whenever a parameter is declared but never used within its scope in a method that overrides or implements another method.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Ignore parameters documented with '@param' tag</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will not issue an error or a warning whenever an unread parameter is documented with an '@param' tag.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unused import</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning for unused import reference.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unused local or private members</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a local or private member is declared but never used within the same unit.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Redundant null check</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever a local variable which can not be null is tested for null.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unnecessary 'else' statement</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an unnecessary else statement (e.g. if (condition) return; else doSomething();).</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unnecessary cast or 'instanceof' operation</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an unnecessary cast or 'instanceof' operation (e.g. if (object instanceof Object) return;).</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unnecessary declaration of thrown exception</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an unnecessary declaration of a thrown exception.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Ignore in overriding and implementing methods</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will not issue an error or a warning whenever it encounters an unnecessary declaration of a thrown exception in a method that overrides or implements another method.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Ignore exceptions documented with '@throws' or '@exception' tags</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will not issue an error or a warning whenever an an unnecessary declaration of a thrown exception is documented with an '@throws' or '@exception' tag.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Ignore 'Exception' and 'Throwable'</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will not issue an error or a warning whenever it encounters an unnecessary declaration of 'Exception' and 'Throwable' exception</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>	
-	<tr>
-		<td valign="top">
-		<p>Unused 'break' or 'continue' label</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an unused 'break' or 'continue' label.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Redundant super interface</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a type which
-		   explicitly implements an interface that is already implemented by any of its supertypes.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-</table>
-
-<h3>Generic types</h3>
-
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Generic types section">
-	<tr>
-		<td valign="top">
-		<p>Unchecked generic type operation</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an unchecked generic type operation.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Usage of a raw type</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a usage of a raw type (i.e. List instead of List&lt;String&gt;).</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Generic type parameter declared with a final type bound</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a type bound involving a final type.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-</table>
-
-<h3>Annotations</h3>
-
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Annotations section">
-	<tr>
-		<td valign="top">
-		<p>Missing '@Override' annotation</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a method overriding another implemented method, and the '@Override' annotation is missing.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top" style="padding-left: 2em;">
-		<p>Include implementations of interface methods (1.6 or higher)</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will also issue an error or a warning whenever it encounters a method overriding or implementing
-		a method declared in an interface, and the '@Override' annotation is missing.<br>
-		Note that '@Override' is only allowed on such methods if the compiler compilance level is 1.6 or higher, so this error or
-		warning will never appear in 1.5 code.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>	
-	<tr>
-		<td valign="top">
-		<p>Missing '@Deprecated' annotation</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a deprecated type without additional '@Deprecated' annotation.</p>
-		</td>
-		<td valign="top">
-		<p>Ignore</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Annotation is used as super interface</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters a type implementing an annotation. Although possible, this is considered bad practice.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unhandled token in '@SuppressWarnings'</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an unhandled token in a '@SuppressWarnings' annotation.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>
-	<tr>
-		<td valign="top">
-		<p>Unused '@SuppressWarnings' token</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will issue an error or a warning whenever it encounters an unused token in a '@SuppressWarnings' annotation.</p>
-		</td>
-		<td valign="top">
-		<p>Warning</p>
-		</td>
-	</tr>	
-	<tr>
-		<td valign="top">
-		<p>Enable '@SuppressWarnings' annotations</p>
-		</td>
-		<td valign="top">
-		<p>When enabled, the compiler will process '@SuppressWarnings' annotations.</p>
-		</td>
-		<td valign="top">
-		<p>On</p>
-		</td>
-	</tr>
-</table>
-
-<p>When <strong>Treat errors like fatal compile errors</strong> is enabled, all generated errors, fatal or configurable, lead to non-executable code.
-If disabled, then your code can be executed as long as it has no fatal error (i.e. syntax error).</p>
-
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p><a href="../../../../../org.eclipse.platform.doc.user/concepts/cprbview.htm">Problems View</a><br>
-<a href="../../../../concepts/concept-quickfix-assist.htm">Quick Fix</a><br>
-<a href="../../../../concepts/concept-java-builder.htm">Java builder</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-javadoc.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-javadoc.htm
deleted file mode 100644
index f1629e3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-javadoc.htm
+++ /dev/null

@@ -1,178 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Compiler Javadoc Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Compiler Javadoc Preferences</h1>
-<p>Indicate your preferences for the Javadoc settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavadocProblemsPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Javadoc preference page">
-<b> Java &gt; Compiler &gt; Javadoc </b></a> preference page.</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Javadoc settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Process Javadoc comments (includes search and refactoring)</p>
-			</td>
-			<td valign="top">
-			<p>The builder detects problems in Javadoc comments if this option
-			is enabled. For search and refactoring to work on Javadoc comments it is also
-			required to enable this option.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Malformed Javadoc comments</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, the compiler will issue an error or warning whenever it encounters a malformed Javadoc comment.</p>
-			</td>
-			<td valign="top">
-			<p>Ignore</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">
-			<p>Only consider members as visible as</p>
-			</td>
-			<td valign="top">
-			<p>The compiler does only check members with the specified or a broader visibility.</p>
-			</td>
-			<td valign="top">
-			<p>Public</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">
-			<p>Validate tag arguments (@param, @throws, @exception, @see, @link)</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, the compiler will issue an error or warning whenever it encounters an error in a Javadoc comment tag argument for @param, @throws, @exception, @see or @link.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 2em;">
-			<p>Report non visible references</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, the compiler will issue an error or warning whenever it encounters a reference to a non visible element.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 2em;">
-			<p>Report deprecated references</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, the compiler will issue an error or warning whenever it encounters a reference to a deprecated element.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">
-			<p>Missing tag descriptions</p>
-			</td>
-			<td valign="top">
-			<p>Choose between 'Validate all standard tags', 'Validate @return tags' and 'Ignore'. When enabled, the compiler will issue an error or warning whenever it encounters a missing tag description</p>
-			</td>
-			<td valign="top">
-			<p>'Validate @return tags'</p>
-			</td>
-		</tr>		
-		
-		<tr>
-			<td valign="top">
-			<p>Missing Javadoc tags</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, the compiler will issue an error or warning whenever it encounters a missing Javadoc tag (i.e. missing @param tag for a parameter).</p>
-			</td>
-			<td valign="top">
-			<p>Ignore</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">
-			<p>Only consider members as visible as</p>
-			</td>
-			<td valign="top">
-			<p>The compiler does only check members with the specified or a broader visibility.</p>
-			</td>
-			<td valign="top">
-			<p>Public</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">
-			<p>Check overriding and implementing methods</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, also overriding and implementing methods are checked for missing Javadoc tags.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Missing Javadoc comments</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, the compiler will issue an error or warning whenever it encounters a missing Javadoc comment for a Java member.</p>
-			</td>
-			<td valign="top">
-			<p>Ignore</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">
-			<p>Only consider members as visible as</p>
-			</td>
-			<td valign="top">
-			<p>The compiler does only check members with the specified or a broader visibility.</p>
-			</td>
-			<td valign="top">
-			<p>Public</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">
-			<p>Check overriding and implementing methods</p>
-			</td>
-			<td valign="top">
-			<p>When enabled, also overriding and implementing methods are checked for missing Javadoc comments.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-task-tags.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-task-tags.htm
deleted file mode 100644
index 720d2c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/compiler/ref-preferences-task-tags.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Java Task Tags Preferences
-    </title>
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Java Task Tags Preferences
-    </h1>
-    <p>
-      Task tags can be configured on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.TodoTaskPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Task Tags preference page">
-      <b>Java &gt; Compiler &gt; Task Tags</b></a> preference page.
-      When the tag list is not empty, the compiler will issue a task marker whenever it encounters
-      one of the corresponding tag inside any comment in Java source code.
-      Generated task messages will include the tag, range
-      until the next line separator, comment ending or non-empty tag, and 
-      will be trimmed. If the same line of code carries multiple
-      tags, they will be reported separately.
-    </p>
-    <p>
-        See the <a href="../ref-preferences-compiler.htm">Compiler preference page</a> for information on how to enable task tags in your source code.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Task tags settings">
-      <caption>
-      </caption>
-      <tr>
-        <th>
-          <p>
-            Action
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            New...
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Adds a new task tag. In the resulting dialog, specify a name and priority for the new task tag.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Remove
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Removes the selected task tag.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Edit...
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Allows you to edit the selected task tag. In the resulting dialog, edit the name and/or priority for the task tag.
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Default
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Sets the currently selected task tag as the default task tag. The default task tag is the one that is used in the 
-            code templates as specified on the <a href="../codestyle/ref-preferences-code-templates.htm">Code Templates preference page</a>.
-            The default task tag is displayed in bold font.
-          </p>
-        </td>
-      </tr>
-    </table>
-    <p>
-    Case sensitivity of the task tags can be specified at the bottom of the preference page using the option
-    <strong>Case sensitive task tag names</strong>.
-	</p>
-        <p>
-     <img border="0"  src="../../../../images/ngrelr.png" alt="Related reference"></p>
-     <p>
-     <a href="../ref-preferences-compiler.htm">Java compiler preferences</a><br>
-     <a href="../codestyle/ref-preferences-code-templates.htm">Code template preferences</a>
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-debug.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-debug.htm
deleted file mode 100644
index e77035f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-debug.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Java Debug Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Java Debug Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaDebugPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java Debug preference page"> <b>Java &gt; Debug</b></a> preference page.</p>
-<p>These options apply to java specific debuggers and have to do with suspending options and hot code replace. </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Suspend execution on uncaught exceptions </td>
-      <td colspan="1" valign="top" align="left"><p>This option controls if a program will suspend if an uncaught exception is thrown. </p>
-      <p>For example if you try to call a method on a null object and a NullPointerException is thrown, with this option on your prgram will suspend at the location the exception was thrown </p></td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Suspend execution on compilation errors </td>
-      <td colspan="1" valign="top" align="left">This option controls if a program will suspend when a compilation error is encountered </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Suspend on breakpoints during evaluations </td>
-      <td colspan="1" valign="top" align="left">This options controls if breakpoints will suspend during an evaluation of code containing a breakpoint. For more information about evaluations go <a href="../../../../tasks/task-evaluating_expressions.htm">here</a> </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Open popup when suspended on exception </td>
-      <td colspan="1" valign="top" align="left">This option controls if a popup window will be displayed when execution of a program stops on an exception. The exception the program suspended on is made available for inspection in the popup</td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Default suspend policy for new breakpoints </td>
-      <td colspan="1" valign="top" align="left">This option allows the default suspend policy to be set for new breakpoints. The suspend policy is used by breakpoints to tell the VM what to suspend, in this case either the thread the breakpoint is active in or the entire running VM </td>
-      <td colspan="1" valign="top" align="left">Suspend Thread </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Show error when hot code replace fails </td>
-      <td colspan="1" valign="top" align="left">This option controls if the user will be presented with an error dialog when a hot code replace fails </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Show error when hot code replace is not supported </td>
-      <td colspan="1" valign="top" align="left">This option controls if the user will be presented with an error dialog when hot code replace is not supported, and the user has made and saved changes to currently running code </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Show error when obsolete methods remain after hot code replace </td>
-      <td colspan="1" valign="top" align="left">This option controls if the user will be presented with an error dialog when a hot code replace completed, but there were obsolete methods left over </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Replace class files containing compilation errors </td>
-      <td colspan="1" valign="top" align="left">This option controls is class files containing compilation errors will be replaced </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Debugger timeout </td>
-      <td colspan="1" valign="top" align="left">This option describes the length of time (in milliseconds) the debugger will wait trying to communicate with a running VM before giving up and disconnecting </td>
-      <td colspan="1" valign="top" align="left">3000</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Launch timeout </td>
-      <td colspan="1" valign="top" align="left">This option describes the length of time (in milliseconds) that a launch will wait to complete the launching process before giving up and terminating. This option has no bearing on the length of time a program will run, only how long the process of <em>trying</em> to run a program will wait </td>
-      <td colspan="1" valign="top" align="left">20000</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Warn when unable to install breakpoint due to missing line number attributes </td>
-      <td colspan="1" valign="top" align="left">This option controls if the user will be notified if they try to set a line breakpoint on a line that has invalid line information </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/preferences/java/debug/ref-detail_formatters.htm">Detail Formatters Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-heap_walking.htm">Heap Walking Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-logical_structures.htm">Logical Structures Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-primitive_display_options.htm">Primitive Display Preferences</a> <br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-step_filtering.htm">Step Filtering Preferences </a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-detail_formatters.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-detail_formatters.htm
deleted file mode 100644
index 7196df1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-detail_formatters.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Detail Formatters Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Detail Formatters Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaDetailFormattersPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Detail Formatters preference page"> <b>Java &gt; Debug &gt; Detail Formaters</b></a> preference page.</p>
-<p>Thess preferences are used to create and manage detail formatters, which are used in the details panes of variables views, or for varibale labels themselves. </p>
-<table border="1" cellspacing="0" cellpadding= "5" summary="Detail formatters preferences">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Types with detial formatters </td>
-      <td colspan="1" valign="top" align="left">The listing of types that currently have detail formatters (the list itself), and trhe enabled state of the detail formatter, i.e. if it is on use (the checked state of a list item) </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Add button </td>
-      <td colspan="1" valign="top" align="left">Used to add a new detail formatter to the current listing </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Edit button </td>
-      <td colspan="1" valign="top" align="left">Used to edit the selected detail formatter </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Remove button </td>
-      <td colspan="1" valign="top" align="left">Used to remove the selected detail formatter </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Detail formatter code snippet for selected type </td>
-      <td colspan="1" valign="top" align="left">Displays the current code snippet in use for the detail formatter of the selected type. This field is not editable, the only way to edit a detila formatter is to use the Edit... button </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Show variables details </td>
-      <td colspan="1" valign="top" align="left"><p>This option controls where you want to see the detial formatter appear, you have one of three choices:</p>
-        <ul>
-          <li>As a label for variables with detail formatters - will appear as the primary display label only for associated variables the have detial formatters </li>
-          <li>As a label for all variables - will appear for all associated variables, regardless of them having detail formatters already </li>
-          <li>In detail pane only - will only appear in variables view detials panes and nowhere else </li>
-      </ul></td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../../reference/preferences/java/debug/ref-heap_walking.htm">Heap Walking Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-logical_structures.htm">Logical Structures Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-primitive_display_options.htm">Primitive Display Preferences</a> <br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-step_filtering.htm">Step Filtering Preferences </a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-execution_environments.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-execution_environments.htm
deleted file mode 100644
index 040a471..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-execution_environments.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Execution Environments Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Execution Environments Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.jreProfiles)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Execution Environments preference page"> <b>Java &gt; Execution Environments</b></a> preference page.</p>
-<p>These preferences describe all of the available execution environments,  allowing default JRE installations to be specified for any given environment. </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Execution environments </td>
-      <td colspan="1" valign="top" align="left">The listing of all available execution environments </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Compatible JREs </td>
-      <td colspan="1" valign="top" align="left"><p>The listing of compatible JRE installations that are compatible with the selected execution environment. You can select one (or none) of the installations to use as the default for the selected execution environment </p>
-        <p>Any JRE installations that perfectly match the execution environment are marked with a label '(perfect match)'</p></td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Environment description </td>
-      <td colspan="1" valign="top" align="left">Provides a description of the selected execution environment </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-heap_walking.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-heap_walking.htm
deleted file mode 100644
index 002175f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-heap_walking.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Heap Walking Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Heap Walking Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.heapWalking)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Heap Walking preference page"> <b>Java &gt; Debug &gt; Heap Walking</b></a> preference page.</p>
-<p>These preferences allow count settings for Java 1.6 heap walking features to be changed.</p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Maximum instances to display </td>
-      <td colspan="1" valign="top" align="left">The maximum number of type instances to display using the <a href="../../../../reference/views/shared/ref-allinstances.htm">all instances command</a>. Entering zero will always show all of the instances of the selected type in the current VM </td>
-      <td colspan="1" valign="top" align="left">100</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Maximum references to display </td>
-      <td colspan="1" valign="top" align="left">The maximum number of type references to display using the <a href="../../../../reference/views/shared/ref-allreferences.htm">all references command</a>. Entering zero will always show all of the references to the selected type in the current VM </td>
-      <td colspan="1" valign="top" align="left">100</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/preferences/java/debug/ref-detail_formatters.htm">Detail Formatters Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-logical_structures.htm">Logical Structures Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-primitive_display_options.htm">Primitive Display Preferences</a> <br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-step_filtering.htm">Step Filtering Preferences </a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-installed_jres.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-installed_jres.htm
deleted file mode 100644
index 580c3be..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-installed_jres.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Installed JREs Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Installed JREs Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.preferences.VMPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Installed JREs preference page"> <b>Java &gt; Installed JREs</b></a> preference page.</p>
-<p>This page allows a <a href="../../../../tasks/task-assign_default_jre.htm">default JRE to be selected</a> as well as adding new JRE installations. </p>
-<table border="1" cellspacing="0" cellpadding= "5" summary="Installed JREs Preferences">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Installed JREs </td>
-      <td colspan="1" valign="top" align="left">The current listing of installed JREs, allowing you to select the one to act as the workspace default </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> <a href="../../../../tasks/task-add_new_jre.htm">Add...</a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Adds a new JRE 
-          definition to the workbench.</p></td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> <a href="../../../../tasks/tasks-JREs.htm">Edit...</a> </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Allows you to 
-          edit the selected JRE. </p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Duplicate...</td>
-      <td colspan="1" valign="top" align="left">Creates a new JRE with the same 
-        attributes as the selected JRE.</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><a href="../../../../tasks/tasks-deleteJRE.htm">Remove</a></td>
-      <td colspan="1" valign="top" align="left">Removes the selected JRE from 
-        the workbench.</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Search... </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Automatically 
-          searches for JREs installed in the local file system and creates corresponding 
-          JRE definitions in the workspace.</p></td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/concept-classpath-variables.htm">Classpath Variables</a><br>
-  <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/tasks-JREs.htm">Working with JREs</a><br>
-  <a href="../../../../tasks/task-add_new_jre.htm">Adding a new JRE definition</a><br>
-  <a href="../../../../tasks/tasks-deleteJRE.htm">Deleting a JRE definition</a><br>
-  <a href="../../../../tasks/task-assign_default_jre.htm">Assigning the default JRE for the workbench</a><br>
-  <a href="../../../../tasks/task-choose_config_jre.htm">Choosing a JRE for launching a project</a><br>
-  <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../../reference/preferences/java/debug/ref-execution_environments.htm">Execution Environment Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../../reference/ref-properties-source-attachment.htm">Source Attachment</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-logical_structures.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-logical_structures.htm
deleted file mode 100644
index 4c3519f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-logical_structures.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Logical Structures Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Logical Structures Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaLogicalStructuresPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Logical Structures preference page"> <b>Java &gt; Debug &gt; Logical Structures</b></a> preference page.</p>
-<p>These preferences are used to add, edit and remove logical structures, which are used to display collection-type objects </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Logical Structures </td>
-      <td colspan="1" valign="top" align="left">Shows a listing of all of the current logical structures available. Note that logical structures with a yellow background cannot be edited or removed </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Add button </td>
-      <td colspan="1" valign="top" align="left">Used to add a new logical structure to the listing </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Edit button </td>
-      <td colspan="1" valign="top" align="left">Used to edit the selected logical structure </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Remove button </td>
-      <td colspan="1" valign="top" align="left">Used to remove the selected logical structure</td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Preview</td>
-      <td colspan="1" valign="top" align="left">Shows the code snippet to the selected logical structure. This preview is not editable, you must use the <strong>Edit... </strong>button to edit a logical structure </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/preferences/java/debug/ref-detail_formatters.htm">Detail Formatters Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-heap_walking.htm">Heap Walking Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-primitive_display_options.htm">Primitive Display Preferences</a> <br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-step_filtering.htm">Step Filtering Preferences </a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-primitive_display_options.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-primitive_display_options.htm
deleted file mode 100644
index f544e46..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-primitive_display_options.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Primitive Display Options Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Primitive Display Options Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaPrimitivesPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Primitive Display Options preference page"> <b>Java &gt; Debug &gt; Primitive Display Options</b></a> preference page.</p>
-<p>These preferences effect how primitive values are displayed (int, double, etc). </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Display hexadecimal values (byte, short, char, int, long) </td>
-      <td colspan="1" valign="top" align="left">This option controls whether hexadecimal values will be displayed for the primitive types byte, short, char, int and long </td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Display ASCII char value (byte, short, int, long) </td>
-      <td colspan="1" valign="top" align="left">This option controls whether ASCII char values will be displayed for the primitive types byte, short, int and long </td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Display unsigned values (byte) </td>
-      <td colspan="1" valign="top" align="left">This option controls whether unsigned values will be displayed for bytes </td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/preferences/java/debug/ref-detail_formatters.htm">Detail Formatters Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-heap_walking.htm">Heap Walking Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-logical_structures.htm">Logical Structures Preferences</a> <br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-step_filtering.htm">Step Filtering Preferences </a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-step_filtering.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-step_filtering.htm
deleted file mode 100644
index 6b99bdb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/debug/ref-step_filtering.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Step Filtering Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Step Filtering Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaStepFilterPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Step Filtering preference page"> <b>Java &gt; Debug &gt; Step Filtering</b></a> preference page.</p>
-<p>These preferences are used to configure step filters and step filtering options. </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Use step filters </td>
-      <td colspan="1" valign="top" align="left">This option controls is step filtering should be enabled or not. See also the step <a href="../../../../reference/views/debug/ref-usestepfilters.htm">filtering command</a> in the <a href="../../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong> </a></td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Defined step filters </td>
-      <td colspan="1" valign="top" align="left">This is a listing of all of the defined step filters (the listing itself) and whether the step filters are in use or not (the checked state of step filter) </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Add Filter button </td>
-      <td colspan="1" valign="top" align="left">Used to add a new step filter that is based on a regular expression </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Add Class button </td>
-      <td colspan="1" valign="top" align="left">Used to add a new Java class to the listing of step filters </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Add Packages button </td>
-      <td colspan="1" valign="top" align="left">Used to add new Java packages to the listing of step filters </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Remove button </td>
-      <td colspan="1" valign="top" align="left">Used to remove the selected step filter(s) </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Select All button </td>
-      <td colspan="1" valign="top" align="left">Used to set all defined step filters as enabled (or checked) </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Deselect All button </td>
-      <td colspan="1" valign="top" align="left">Used to set all defined step filters as disabled (or unchecked) </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Filter synthetic methods </td>
-      <td colspan="1" valign="top" align="left">This option controls if synthetic method should always be filtered or not while stepping. This option requires that the VM used support synthetic methods </td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Filter static initializers </td>
-      <td colspan="1" valign="top" align="left">This option controls if static initializers should always be filtered or not while stepping </td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Filter constructors </td>
-      <td colspan="1" valign="top" align="left">This option controls if constructors should always be filtered or not while stepping </td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Step through filters </td>
-      <td colspan="1" valign="top" align="left"><p>This option controls step filters to always return from 
-          a filtered location or step through to a non-filtered location. </p>
-        <p>For 
-          example, if <code>java.util</code> is a filtered location, stepping 
-          into code in <code>HashMap</code> could result in a call-back to your 
-          application code to check the equality of an object. If you choose to <strong>Step through filters</strong> a step into would end up in your 
-          application code. However, when the <strong>Step through filters</strong> option is disabled, a step into <code>HashMap</code> would behave like 
-          a step over.</p></td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/preferences/java/debug/ref-detail_formatters.htm">Detail Formatters Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-heap_walking.htm">Heap Walking Preferences</a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../../reference/preferences/java/debug/ref-logical_structures.htm">Logical Structures Preferences</a> <br>
-  <a href="../../../../reference/preferences/java/debug/ref-primitive_display_options.htm">Primitive Display Preferences</a> <br>
-  <a href="../../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-advanced.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-advanced.htm
deleted file mode 100644
index bf396f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-advanced.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Advanced Java Content Assist Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Advanced Java Content Assist Preferences</h1>
-<p>Indicate your preferences for the Advanced settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferenceAdvanced)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Advanced preference page"> <b>Java &gt; Editor &gt; Content Assist &gt; Advanced</b></a> preference page.</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Advanced content assist settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Select the proposal kinds contained in the 'default' content assist list</p>
-			</td>
-			<td valign="top">
-			<p>Select all the proposal kinds which are contained in the content assist list when invoking content assist the first time with Ctrl+Space.</p>
-			</td>
-			<td valign="top">
-			<p>Other Java Proposals, SWT Template Proposals, Template Proposals, Type Proposals</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Content assist cycling</p>
-			</td>
-			<td valign="top">
-			<p>Select the proposal kinds to cycle through and the cycle order when repeatedly invoking content assist (Ctrl+Space). Select a proposal kind and invoke Up or Down to change the order.</p>
-			</td>
-			<td valign="top">
-			<p>Template Proposals, SWT Template Proposals</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Timeout for fetching a parameter name from attached Javadoc</p>
-			</td>
-			<td valign="top">
-			<p>If a parameter name could not be fetched from attached Javadoc within the specified amount of time then the attempt to fetch it is abandoned. Increase the value if you have problems fetching the name, for instance due to a slow network connection.</p>
-			</td>
-			<td valign="top">
-			<p>50 ms</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/ref-java-editor-code-assist.htm">Content/Code Assist</a><br>
-<a href="../../../../reference/preferences/java/editor/ref-preferences-content-assist.htm">Content Assist preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-favorites.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-favorites.htm
deleted file mode 100644
index b5ace51..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist-favorites.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Content Assist Favorites Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Content Assist Favorites Preferences</h1>
-<p>Indicate your preferences settings for the content assist for static members on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistStaticMembersPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Advanced preference page"><b>Java &gt; Editor &gt; Content Assist &gt; Favorites</b></a> preference page.</p>
-<p>You can define a list of static members and types containing static members on this page. Content assist will propose those members even if the
-import is missing.</p>
-<p>To see the static import proposals, make sure <strong>Use static imports</strong> is enabled on the 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Content Assist preference page">
-Content Assist preference page</a>
-</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="Static import favorites">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>New Type</p>
-			</td>
-			<td valign="top">
-			<p>Add a new type to the list. All static members declared by the added type will be proposed by content assist.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>New Member</p>
-			</td>
-			<td valign="top">
-			<p>Add a static member to the list. The member will be proposed by content assist.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Edit</p>
-			</td>
-			<td valign="top">
-			<p>Edit the selected entry.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Remove</p>
-			</td>
-			<td valign="top">
-			<p>Removes the selected entry from the list.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/ref-java-editor-code-assist.htm">Content/Code assist</a><br>
-<a href="../../../../reference/preferences/java/editor/ref-preferences-content-assist.htm">Content assist preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist.htm
deleted file mode 100644
index 592cbd6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-content-assist.htm
+++ /dev/null

@@ -1,200 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Content Assist Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Content Assist Preferences</h1>
-<p>Indicate your preferences for the Content Assist settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Content Assist preference page">
-<b> Java &gt; Editor &gt; Content Assist </b></a> preference page.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Content Assist settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">Completion inserts/Completion overwrites</td>
-			<td valign="top">
-			<p>If <strong>Completion inserts</strong> is on, the completion text is inserted at the caret position, so it never overwrites any existing text. <br>
-			If <strong>Completion overwrites</strong> is on, the completion text replaces the characters following the caret position until the end of the word.</p>
-			<p>Note that pressing <strong>Ctrl</strong> when applying a completion proposal toggles between the two insertion modes.</p>
-			</td>
-			<td valign="top">
-			<p>Completion inserts</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Insert single proposals automatically</td>
-			<td valign="top">
-			<p>If enabled, code assist will choose and insert automatically single proposals.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Insert common prefixes automatically</td>
-			<td valign="top">
-			<p>If enabled, code assist will automatically insert the common prefix of all possible completions similar to Unix shell expansion. This can be used repeatedly, even while the code assist window is being displayed.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Add import instead of qualified name</td>
-			<td valign="top">
-			<p>If enabled, type proposals which are in other packages will invoke the addition of the corresponding import declaration. Otherwise, the type will be inserted fully qualified.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Use static imports</td>
-			<td valign="top">
-			<p>If enabled, method proposals for static methods will invoke the addition of the corresponding static import declaration. Otherwise, a non static import for the declaring type will be added.
-			</p>
-			<p>Add the method or type containing the method to the <a href="ref-preferences-content-assist-favorites.htm">Favorites</a> preference page to get a proposal for such methods.
-			</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Fill method arguments and show guessed arguments</td>
-			<td valign="top">
-			<p>If enabled, code assist will add argument when completing a method. It will also offer matching variables, fields or method invocations from the context where a method proposal is inserted.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">Insert parameter names</td>
-			<td valign="top">
-			<p>If selected, code assist will fill the arguments with the parameter names used in the method declaration.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 1em;">Insert best guessed arguments</td>
-			<td valign="top">
-			<p>If selected, code assist will fill the arguments with the best matching variable, field or method invocation from the context where a method proposal is inserted.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>		
-		<tr>
-			<td valign="top">Sort proposals</td>
-			<td valign="top">
-			<p>Select how the proposals should be sorted in the content assist pop up.</p>
-			</td>
-			<td valign="top">
-			<p>by relevance</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Hide proposals not visible in the invocation context</td>
-			<td valign="top">
-			<p>If enabled, the Java element proposals are limited by the rules of visibility. For example, private field proposals of other classes would not be displayed.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Show camel case matches</td>
-			<td valign="top">
-			<p>If enabled, camel case matches are displayed (i.e. NPE is expanded to NullPointerException).</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Hide forbidden references</td>
-			<td valign="top">
-			<p>If enabled, references to Java elements forbidden by access rules are not displayed.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Hide discouraged references</td>
-			<td valign="top">
-			<p>If enabled, references to Java elements discouraged by access rules are not displayed.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Hide deprecated references</td>
-			<td valign="top">
-			<p>If enabled, references to deprecated Java elements are not displayed.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Enable auto activation</td>
-			<td valign="top">
-			<p>If enabled, code assist can be invoked automatically.</p>
-			<p>The condition for automatic invocation is specified with the preferences <strong>Auto activation delay</strong>, <strong>Auto activation triggers for Java</strong> and <strong>Auto activation triggers for Javadoc</strong>.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Auto activation delay</td>
-			<td valign="top">
-			<p>If the time starting when an auto activation trigger character is encountered until a new character is typed exceeds the auto activation delay, code assist is invoked.</p>
-			</td>
-			<td valign="top">200</td>
-		</tr>
-		<tr>
-			<td valign="top">Auto activation triggers for Java</td>
-			<td valign="top">
-			<p>If one of the trigger characters is typed inside Java source code (but not inside a Javadoc comment) and no other character is typed before the auto activation delay times out, the code assist is invoked.</p>
-			</td>
-			<td valign="top">
-			<p>'.'</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">Auto activation triggers for Javadoc</td>
-			<td valign="top">
-			<p>If one of the trigger characters is typed inside a Java doc and no other character is typed before the auto activation delay times out, the code assist is invoked.</p>
-			</td>
-			<td valign="top">
-			<p>'@#'</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/ref-java-editor-code-assist.htm">Content/Code Assist</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-edit-template-dialog.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-edit-template-dialog.htm
deleted file mode 100644
index d3b3d37..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-edit-template-dialog.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>Java Editor Templates Preferences</title>
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"></script>
-  </head>
-  
-  <body>
-    <h1><a name="dialog_help">Java Editor Templates Preferences</a></h1>
-    <p>The following fields and buttons appear in the dialog:</p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Editor templates">
-      <thead>
-        <tr>
-          <th>Option</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody valign="baseline">
-        <tr>
-          <td>Name</td>
-          <td>The name of the template.</td>
-        </tr>
-        <tr>
-          <td>Context</td>
-          <td>The context determines where the template can be used and the set of available pre-defined template variables. The Java editor defines a context for Java and Javadoc areas.
-          <ul>
-          <li><strong>Javadoc</strong>: Proposal is only offered in Javadoc comments</li>
-          <li><strong>Java</strong>: Proposal is only offered in Java code</li>
-          <li><strong>Java type members</strong>: Proposal is only offered when completing a Java type member</li>
-          <li><strong>Java statement</strong>: Proposal is only offered when completing a Java statement</li>
-          <li><strong>SWT</strong>: Proposal is only offered when completing in Java code with SWT on the build path</li>
-          <li><strong>SWT type members</strong>: Proposal is only offered when completing a Java type member with SWT on the build path</li>
-          <li><strong>SWT statement</strong>: Proposal is only offered when completing a Java statement with SWT on the build path</li>
-          </ul>
-          </td>
-        </tr>
-        <tr>
-          <td>Automatically insert</td>
-          <td>If selected, code assist will automatically insert the template if it is the only proposal available at the caret position.</td>
-        </tr>
-        <tr>
-          <td>Description</td>
-          <td>A description of the template, which is displayed to the user when choosing the template.</td>
-        </tr>
-        <tr>
-          <td>Pattern</td>
-          <td>The template pattern.</td>
-        </tr>
-        <tr>
-          <td>Insert Variables...</td>
-          <td>Displays a list of pre-defined context specific <a href="../../../../concepts/concept-template-variables.htm">template variables.</a></td>
-        </tr>
-      </tbody>
-    </table>
-
-    <p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p><a href="../../../../concepts/concept-editor-templates.htm">Templates</a><br>
-        <a href="../../../../concepts/concept-template-variables.htm">Templates variables</a>
-    </p>
-    <p><img border="0"  src="../../../../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-      <a href="ref-preferences-templates.htm">Templates preferences</a><br>
-      <a href="../../../../reference/ref-java-editor-code-assist.htm">Java content assist</a><br>
-      <a href="../compiler/ref-preferences-task-tags.htm">Task tag preferences</a><br>
-      <a href="../codestyle/ref-preferences-code-templates.htm">Code templates preferences</a><br>
-      <a href="../ref-preferences-code-style.htm">Code style preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-folding.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-folding.htm
deleted file mode 100644
index 4870657..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-folding.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Editor Folding Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Editor Folding Preferences</h1>
-<p>Indicate your preferences for the Folding settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.FoldingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Folding preference page"><b> Java &gt; Editor &gt; Folding </b></a> preference page.</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Folding settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Enable folding</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, different sections in the Java editor can be folded and expanded.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Comments</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, comments are folded when opening a new editor.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Header Comments</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, header Comments are folded when opening a new editor.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Inner types</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, inner types are folded when opening a new editor.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Members</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, Java members are folded when opening a new editor.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Imports</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, imports are folded when opening a new editor.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../ref-preferences-editor.htm">Java Editor preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-hovers.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-hovers.htm
deleted file mode 100644
index 0c3dce2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-hovers.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Hovers Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Hovers Preferences</h1>
-<p>Indicate your preferences for the Hovers settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorHoverPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Hovers preference page">
-<b> Java &gt; Editor &gt; Hovers </b></a> preference page.</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Hovers settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Expand vertical ruler icons upon hovering</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, when there are multiple icons per line shown on vertical ruler, then the icons
-			are expanded when hovering over it. This allows to see all icons. Changing this preference does
-			not affect already opened editors.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Text Hover key modifier preferences</p>
-			</td>
-			<td valign="top">
-			<p>The selected hovers in this list are used to generate the hover content. A key modifier can be given to
-			each hover type to force the editor to only evaluate this hover when pressing the assigned key modifier.</p>
-			</td>
-			<td valign="top">
-			<p>Combined Hover, Source (with Shift)</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../ref-preferences-editor.htm">Java editor preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-mark-occurrences.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-mark-occurrences.htm
deleted file mode 100644
index 0027bf1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-mark-occurrences.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Mark Occurrences Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Mark Occurrences Preferences</h1>
-<p>Indicate your preferences for the Mark Occurrences settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.MarkOccurrencesPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Mark Occurrences preference page"> <b>Java &gt; Editor &gt; Mark Occurrences</b></a> preference page.</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Mark occurrences settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Mark occurrences of the selected element in the current file</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, then you'll see within a file, where a variable, method, type or other element is referenced.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p>A list of elements can be enabled and disabled on this preference page. All are enabled by default.</p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../../reference/preferences/java/ref-preferences-editor.htm">Java Editor preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-save-actions.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-save-actions.htm
deleted file mode 100644
index 03c557c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-save-actions.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Save Actions Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Save Actions Preferences</h1>
-<p>Indicate your preferences for the Save Actions settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.SaveParticipantPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Save Actions preference page"> <b>Java &gt; Editor &gt; Save Actions</b></a> preference page.</p>
-<p>A set of actions which are executed on each save of the Java editor can be specified on this page.
-</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Save sctions settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Perform the selected actions on save</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, then the selected actions below will be executed on save.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Format source code</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, then the source code will be formatted on each save. The code will be formatted according to the
-			active profile selected on the <a href="../../../preferences/java/codestyle/ref-preferences-formatter.htm"><b>Java &gt; Code Style &gt; Formatter</b></a> preference page.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" style="padding-left: 2em;">
-			<p>Format all lines</p>
-			</td>
-			<td valign="top">
-			<p>If selected, all lines in the file will be formatted on save.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>		
-		<tr>
-			<td valign="top" style="padding-left: 2em;">
-			<p>Format edited lines</p>
-			</td>
-			<td valign="top">
-			<p>If selected, only the lines that have been modified since the last save are formatted on save.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>		
-		<tr>
-			<td valign="top">
-			<p>Organize imports</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, then the imports will be organized on each save. Change the organize import settings on the
-			 <a href="../../../preferences/java/codestyle/ref-preferences-organize-imports.htm"><b>Java &gt; Code Style &gt; Organize Imports</b></a> preference page.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Additional actions</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, then additional actions will be executed on save. To add and remove actions select <b>Configure...</b>.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../ref-preferences-editor.htm">Java editor preference page</a><br>
-<a href="../codestyle/ref-preferences-cleanup.htm">Clean Up preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-syntax-coloring.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-syntax-coloring.htm
deleted file mode 100644
index 671039a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-syntax-coloring.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Syntax Coloring Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Syntax Coloring Preferences</h1>
-<p>Indicate your preferences for the Syntax Coloring settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorColoringPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Syntax Coloring preference page"><b> Java &gt; Editor &gt; Syntax Coloring </b></a> preference page.</p>
-    <p>
-      Syntax Coloring specifies how Java source code is rendered. Note that general 
-      text editor settings such as the background color can be configured on the general 'Text Editors' preference pages. Fonts
-      may be configured on the general 'Colors and Fonts' preference page.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Syntax coloring setting">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            Element
-          </td>
-          <td valign="top">
-            <p>
-              Each category (<strong>Java</strong>, <strong>Javadoc</strong> and <strong>Comments</strong>)
-              contains a list of language elements that may be rendered with its own color and style.
-            </p>
-            <p>
-            Note that some semantic highlighting options can be disabled by the user in order to
-            ensure editor performance on low-end systems.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              default colors and styles
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Preview
-          </td>
-          <td valign="top">
-            <p>
-              Displays the preview of a Java source code respecting the current colors and styles.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p><a href="../../../../concepts/concept-java-editor.htm">Java editor</a></p>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../ref-preferences-editor.htm">Java editor preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-templates.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-templates.htm
deleted file mode 100644
index 92ae38b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-templates.htm
+++ /dev/null

@@ -1,160 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java Editor Templates Preferences
-    </title>
-    <link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"></script>
-  </head>
-  <body>
-    <h1>
-      Java Editor Templates Preferences
-    </h1>
-    <p>
-      The
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaTemplatePreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Templates preference page">
-      <b>Java &gt; Editor &gt; Templates</b></a> preference page
-      allows to create new and edit existing templates. A template is a convenience for the programmer to quickly insert often reoccurring source
-      code patterns.
-    </p>
-    <p>
-      The following buttons allow manipulation and configuration of templates:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Templates options">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Action
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              New...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens the <a href="ref-preferences-edit-template-dialog.htm">Template dialog</a> to create a new template.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Edit...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens the <a href="ref-preferences-edit-template-dialog.htm">Template dialog</a> to edit the currently selected template.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Remove
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Removes all selected templates.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Restore Removed
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Restores any preconfigured templates that have been removed.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Revert to Default
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Restores any preconfigured templates to their default. This does not modify user-created templates.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Import...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Imports templates from the file system.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Export...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Exports all selected templates to the file system.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Use code formatter
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the template is formatted according to the code formatting rules specified in the <a href="../codestyle/ref-preferences-formatter.htm">Code Formatter preferences</a>, prior to insertion.
-              Otherwise, the template is inserted as is, but correctly indented.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../../../../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../../../../concepts/concept-editor-templates.htm">Templates</a><br>
-      <a href="../../../../concepts/concept-template-variables.htm">Template variables</a><br>
-    </p>
-    <p>
-      <img border="0"  src="../../../../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="ref-preferences-edit-template-dialog.htm">Template editing</a><br>
-      <a href="../../../../reference/ref-java-editor-code-assist.htm">Java content assist</a><br>
-      <a href="../compiler/ref-preferences-task-tags.htm">Task tag preferences</a><br>
-      <a href="../codestyle/ref-preferences-code-templates.htm">Code templates preferences</a><br>
-      <a href="../ref-preferences-code-style.htm">Code style preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-typing.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-typing.htm
deleted file mode 100644
index b125feb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/editor/ref-preferences-typing.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Editor Typing Preferences</title>
-<link rel="stylesheet" href="../../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Editor Typing Preferences</h1>
-<p>Indicate your preferences for the Typing settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.SmartTypingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Typing preference page"><b> Java &gt; Editor &gt; Typing </b></a> preference page.</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Typing settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Automatically close</p>
-			</td>
-			<td valign="top">
-			<p>Select for which characters a closing character should be inserted when typing the opening character.</p>
-			</td>
-			<td valign="top">
-			<p>All on</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Automatically insert at correct position</p>
-			</td>
-			<td valign="top">
-			<p>Select which characters should be automatically inserted when they are required.</p>
-			</td>
-			<td valign="top">
-			<p>All off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Tab key adjusts the indentation of the current line</p>
-			</td>
-			<td valign="top">
-			<p>If enabled then the tab key can be used to indent the current line.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Adjust indentation</p>
-			</td>
-			<td valign="top">
-			<p>When pasting Java code from the clipboard adjust its indentation to the current
-			indentation level.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Update imports</p>
-			</td>
-			<td valign="top">
-			<p>When pasting Java code from the clipboard add the required import statements to the import section.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Wrap automatically</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, string literals are wrapped when they exceed the max line length.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Escape text when pasting into a string literal</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, special characters in pasted strings are escaped when they are pasted into an existing string literal.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../ref-preferences-editor.htm">Java editor preference page</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-appearance.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-appearance.htm
deleted file mode 100644
index 5c1d848..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-appearance.htm
+++ /dev/null

@@ -1,188 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>Java Appearance Preferences</title>
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Java Appearance Preferences
-    </h1>
-    <p>
-      The appearance of Java elements in views can be configured on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-      <b>Java &gt; Appearance</b></a> preference page and on its sub pages:
-     </p>
-     <ul>
-      <li><a href="appearance/ref-preferences-member-sort-order.htm">Member sort order</a></li>
-      <li><a href="appearance/ref-preferences-type-filters.htm">Type filters</a></li>
-     </ul>
-    <p> 
-      The options are:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Appearance preference page">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-               Show method return types
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, methods displayed in views show the return type.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show method type parameters
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, methods displayed in views show their type parameters.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show categories
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, method, field and type labels contain the categories specified in their Javadoc comment.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>        
-        <tr>
-          <td valign="top">
-            <p>
-              Show members in Package Explorer
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, Java elements below the level of Java files and Class files are displayed as well.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Fold empty packages in hierarchical layout
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, empty packages which do not contain resources or other child elements are folded.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Compress package name segments
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, package names, except for the final segment, are compressed according to the compression pattern.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Stack views vertically in the Java Browsing perspective
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, views in Java Browsing perspective will be stacked vertically, rather than horizontally.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    Note: The <b>Colored Labels</b> settings is now available on the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the General Appearance preference page">
-    General &gt; Appearance</a> preference page.
-    
-    
-    <p>
-      <img src="../../../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../../../concepts/concept-java-views.htm">Java views</a>
-    </p>
-    <p>
-     <img border="0"  src="../../../images/ngrelr.png" alt="Related reference"></p>
-     <p>
-     <a href="../../views/ref-view-package-explorer.htm">Package Explorer view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-build-path.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-build-path.htm
deleted file mode 100644
index f1eb194..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-build-path.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Java Build Path Preferences</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Java Build Path Preferences</h1>
-<p>Indicate your preferences for the Build Path settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.BuildPathPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Build Path preference page"> <b> Java &gt; Build Path </b></a> preference page and its sub pages:
-</p>
- <ul>
-  <li><a href="buildpath/ref-preferences-classpath-variables.htm">Classpath Variables</a></li>
-  <li><a href="buildpath/ref-preferences-user-libraries.htm">User Libraries</a></li>
- </ul>
- 
- <p>The options are:</p>
- 
-<table border="1" cellspacing="0" cellpadding="5" summary="Build Path settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Option</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">Source and output folder</td>
-			<td valign="top">
-			<dl>
-				<dt><strong>Project</strong></dt>
-				<dd>Use the project root folder as the folder where Java source files and the generated class files are stored by default.</dd>
-				<dt><strong>Folders</strong></dt>
-				<dd>Specify separate source and output folders to store the Java source files separated from the generated class files.</dd>
-			</dl>
-			</td>
-			<td valign="top">Folders<br>Source Folder: src<br>Output Folder: bin</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>As JRE library use</p>
-			</td>
-			<td valign="top">
-			<p>Select what kind of JRE library should be used for newly created Java projects.</p>
-			</td>
-			<td valign="top">
-			<p>JRE container</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p><a href="../../../concepts/concept-classpath-variables.htm">Classpath variables</a><br>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../reference/ref-wizard-java-project.htm">New Java project wizard</a><br></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-code-style.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-code-style.htm
deleted file mode 100644
index 6135cd9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-code-style.htm
+++ /dev/null

@@ -1,139 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java Code Style Preferences
-    </title>
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Java Code Style Preferences
-    </h1>
-<p>The
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeStylePreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Code Style preference page">
-<b>Java &gt; Code Style</b></a> preference page
-allows to configure naming conventions, style rules and comment settings.
-These preferences are used when new code has to be generated.
-</p>
-
-<p>Sub pages offer more code style settings:</p>
- <ul>
-  <li><a href="codestyle/ref-preferences-cleanup.htm">Clean Up</a></li>
-  <li><a href="codestyle/ref-preferences-code-templates.htm">Code Templates</a></li>
-  <li><a href="codestyle/ref-preferences-formatter.htm">Formatter</a></li>
-  <li><a href="codestyle/ref-preferences-organize-imports.htm">Organize Imports</a></li>
- </ul>
- 
- <p>The options are:</p>
-
-
-<h2 class="Head">Naming Conventions</h2>
-<p>The list defines the naming conventions for fields (static and non-static), parameters and local variables. For each variable type it is possible to configure a list of prefix or suffix or both.<br>
-Naming conventions are used by all actions and 'Quick Fix' proposals that create fields, parameters and local variables, in particular the 
-<a href="../../ref-menu-source.htm">Source actions</a>.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="Naming conventions">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Edit...</p>
-			</td>
-			<td valign="top">
-			<p>Opens a dialog to edit the list of prefix and suffixes for the currently selected variable type</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<h2 class="Head">Code Conventions</h2>
-<p>The following settings specify how newly generated code should look like. The names of getter methods can be specified as well as the format of field accesses, method comments, annotations and exception variables.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="Code Conventions">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-			<th>
-			<p>Default</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Qualify all generated field accesses with 'this.'</p>
-			</td>
-			<td valign="top">
-			<p>If selected, field accesses are always prefixed with 'this', regardless whether the name of the field is unique in the scope of the field access or not.</p>
-			</td>
-			<td valign="top">
-			<p>Off</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Use 'is' prefix for getters that return boolean</p>
-			</td>
-			<td valign="top">
-			<p>If selected, the names of getter methods of boolean type are prefixed with 'is' rather than 'get'.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Add '@Override' annotation for overriding methods</p>
-			</td>
-			<td valign="top">
-			<p>If selected, methods which override an already implemented method are annotated with an '@Override' annotation. See the
-			<a href="../../../reference/preferences/java/ref-preferences-compiler.htm">Compiler preference page</a> for settings related to annotations.</p>
-			</td>
-			<td valign="top">
-			<p>On</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Exception variable name in catch blocks</p>
-			</td>
-			<td valign="top">
-			<p>Specify the name of the exception variable declared in catch blocks.</p>
-			</td>
-			<td valign="top">
-			<p>e</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<p>
-      <img border="0"  src="../../../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../../../reference/ref-menu-source.htm">Source actions</a><br>
-	  <a href="../../../reference/views/ref-java-editor.htm">Java editor</a><br>
-	  <a href="ref-preferences-editor.htm">Java editor preferences</a><br>
-	  <a href="ref-preferences-compiler.htm">Java compiler preferences</a><br>
-	  <a href="codestyle/ref-preferences-code-templates.htm">Code templates preferences</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-compiler.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-compiler.htm
deleted file mode 100644
index 8d1151a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-compiler.htm
+++ /dev/null

@@ -1,265 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Java Compiler Preferences
-    </title>
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Java Compiler Preferences
-    </h1>
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CompliancePreferencePage)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java Compiler preference page">
-    <b>Java &gt; Compiler</b></a> preference page
-    lets you configure the various settings related to compiling of Java source code and class file generation.</p>
-<p>Sub pages offer more compiler settings:</p>
- <ul>
-  <li><a href="compiler/ref-preferences-building.htm">Building</a></li>
-  <li><a href="compiler/ref-preferences-errors-warnings.htm">Error/Warnings</a></li>
-  <li><a href="compiler/ref-preferences-javadoc.htm">Javadoc</a></li>
-  <li><a href="compiler/ref-preferences-task-tags.htm">Task Tags</a></li>
- </ul>
- 
-<p>The options are:</p>
-
-<h3>JDK Compliance</h3>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="JDK Compliance">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Compiler compliance level
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specifies the compiler compliance level.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            1.4
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Use default compliance settings
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, the default compliance settings for the compiler compliance level are applied.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Generated class files compatibility
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specifies the generated class file compatibility.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            1.2
-          </p>
-        </td>
-      </tr>
-        <tr>
-        <td valign="top">
-          <p>
-            Source compatibility
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specifies the compatibility of the accepted source code.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            1.3
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Disallow identifiers called 'assert'
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever 'assert' is used as an identifier (reserved keyword in J2SE 1.4).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-            <tr>
-        <td valign="top">
-          <p>
-            Disallow identifiers called 'enum'
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            When enabled, the compiler will issue an error or a warning whenever 'enum' is used as an identifier (reserved keyword in J2SE 1.5).
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Warning
-          </p>
-        </td>
-      </tr>
-          </table>
-          <h3>Classfile generation</h3>
-           <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Classfile generation">   
-      <tr>
-        <td valign="top">
-          <p>
-            Add variable attributes to generated class files
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, variable attributes are added to the class file. This will enable local variable names to be displayed in the debugger (in places where variables are
-            definitely assigned) The resulting .class file is then bigger.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Add line number attributes to generated class files
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, line number information is added to the class file. This will enable source code highlighting in the debugger.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Add source file name to generated class file
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, the source file name is added to the class file. This will enable the debugger to present the corresponding source code.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Preserve unused local variables
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, unused local variables (i.e. never read) are not stripped from the class file. If stripped this potentially alters debugging.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            On
-          </p>
-        </td>
-      </tr>
-       <tr>
-        <td valign="top">
-          <p>
-            Inline finally blocks
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            If enabled, finally blocks are inlined in the generated class files. This positively affects performance, but may result in larger class files.
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Off
-          </p>
-        </td>
-      </tr>
-    </table>
-    <p>
-      <img src="../../../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../../../concepts/concept-java-builder.htm">Java builder</a>
-    </p>
-    <p>
-      <img src="../../../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-       <a href="../../../tasks/tasks-JREs.htm">Working with JREs</a>
-    </p>
-    <p>
-      <img border="0"  src="../../../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="buildpath/ref-preferences-classpath-variables.htm">Classpath variables preferences</a><br>
-	  <a href="../../../reference/ref-properties-build-path.htm">Java build path properties</a><br>
-	  <a href="compiler/ref-preferences-building.htm">Building preference page</a><br>
-	  <a href="compiler/ref-preferences-errors-warnings.htm">Errors/Warnings preference page</a><br>
-	  <a href="compiler/ref-preferences-javadoc.htm">Javadoc preference page</a><br>
-	  <a href="../../../reference/preferences/java/compiler/ref-preferences-task-tags.htm">Task tags preference page</a>
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-editor.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-editor.htm
deleted file mode 100644
index ec7597e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-editor.htm
+++ /dev/null

@@ -1,184 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <title>
-      Java Editor Preferences
-    </title>
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Java Editor Preferences
-    </h1>
-    <p>
-      The following Java editor preferences can be set on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java Editor preference page">
-      <b>Java &gt; Editor</b></a> preference page
-      and its sub-pages.
-    </p>
-    <ul>
-      <li><a href="editor/ref-preferences-content-assist.htm">Content Assist</a>
-      <ul>
-      <li><a href="editor/ref-preferences-content-assist-advanced.htm">Advanced</a></li>
-      <li><a href="editor/ref-preferences-content-assist-favorites.htm">Favorites</a></li>
-      </ul>
-      </li>
-      <li><a href="editor/ref-preferences-folding.htm">Folding</a></li>
-      <li><a href="editor/ref-preferences-hovers.htm">Hovers</a></li>
-      <li><a href="editor/ref-preferences-mark-occurrences.htm">Mark Occurrences</a></li>
-      <li><a href="editor/ref-preferences-save-actions.htm">Save Actions</a></li>
-      <li><a href="editor/ref-preferences-syntax-coloring.htm">Syntax Coloring</a></li>
-      <li><a href="editor/ref-preferences-templates.htm">Templates</a></li>
-      <li><a href="editor/ref-preferences-typing.htm">Typing</a></li>
-    </ul>
-    <p>
-      Note that some options that are generally applicable to text editors can be configured on the text editor preference page.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="General editor settings">
-      <thead>
-        <tr>
-          <th>Option</th>
-          <th>Description</th>
-          <th>Default</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-          Smart caret positioning in Java names (overrides platform behavior)
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, there are additional word boundaries inside <tt>|Camel|Case|</tt> Java names.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Report problems as you type
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the editor marks errors and warnings as you type, even if you do not save the editor contents. The problems are updated after a short delay.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Highlight matching brackets
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, whenever the cursor is next to a parenthesis, bracket or curly braces, its opening or closing counter part is highlighted.
-            </p>
-            <p>
-              The color of the bracket highlight is specified with <strong>Appearance color options</strong>.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              On
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Light bulb for quick assists
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, a <img src="../../../images/org.eclipse.jdt.ui/obj16/quickassist_obj.png" alt="light bulb">  shows up in the vertical ruler whenever a <strong>quick assist</strong> is available. See the <a href="../../ref-java-editor-quickassist.htm">quick assist section</a> for a list of the available assists.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-          Only show the selected Java element
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, the Java editor will only show the selected Java element which is currently selected (i.e. in the Outline View or the Package Explorer).
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Appearance color options
-          </td>
-          <td valign="top">
-            <p>
-              The colors of various Java editor appearance features are specified here.
-            </p>
-            <dl>
-              <dt>Matching brackets highlight</dt>
-              <dd>The color of brackets highlight.</dd>
-            
-              <dt>Parameter hints background</dt>
-              <dd>The background color of the parameter hint window</dd>
-            	
-              <dt>Parameter hints foreground</dt>
-              <dd>The foreground color of the parameter hint window</dd>
-            
-              <dt>Completion overwrite background</dt>
-              <dd>The background color of the completion overwrite window</dd>
-           		
-           	  <dt>Completion overwrite foreground</dt>
-              <dd>The foreground color of the completion overwrite window</dd>
-              
-              <dt>Source hover background</dt>
-              <dd>The background color for the source hover. The source hover shows the source code of the element under the mouse pointer.</dd>
-            </dl>
-          </td>
-          <td valign="top">
-            <p>
-              default colors
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../../../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../../../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../../../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../../../reference/views/ref-java-editor.htm">Java editor</a><br>
-      <a href="codestyle/ref-preferences-formatter.htm">Code formatter preferences</a><br>
-      <a href="../../../reference/views/ref-view-outline.htm">Java outline</a><br>
-      <a href="../../../reference/ref-java-editor-code-assist.htm">Java content assist</a><br>
-      <a href="../../../reference/ref-java-editor-quickfix.htm">Quick Fix</a><br>
-      <a href="../../../reference/ref-java-editor-quickassist.htm">Quick Assist</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-installed-jres.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-installed-jres.htm
deleted file mode 100644
index 3474565..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-installed-jres.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Installed JREs
-    </title>
-  </head>
-  <body>
-    <h1>
-      Installed JREs
-    </h1>
-    <p>
-      Check the box for the JRE that you want to act as your default for running and debugging Java programs in the workbench.
-    </p>
-    <p>
-      This JRE defines the values for the three reserved classpath variables (JRE_LIB, JRE_SRC, JRE_SRCROOT).
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-junit.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-junit.htm
deleted file mode 100644
index e87cdbd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-junit.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      JUnit Preferences
-    </title>
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      JUnit Preferences
-    </h1>
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.junit.preferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the JUnit preference page">
-    <b>Java &gt; JUnit</b></a> preference page
-    lets you configure the stack trace filter patterns for JUnit. The patterns are used in the <i>JUnit</i> view to control which entries are visible in stack traces.</p>
-    
-<table border="1" cellspacing="0" cellpadding="5" width="600" summary="JUnit settings">
-	<thead>
-		<tr>
-			<th>
-			<p>Action</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Enable assertions for new JUnit launch configurations</p>
-			</td>
-			<td valign="top">
-			<p>If enabled, then JUnit test will be launched with assertions enabled.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%">
-			<p>Add Filter</p>
-			</td>
-			<td valign="top">
-			<p>Allows to add a custom filter pattern. This action inserts an empty pattern which can be edited.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Add Class...</p>
-			</td>
-			<td valign="top">
-			<p>Allows to add classes to be filtered. This action opens the <strong>Open Type</strong> dialog to choose a type to be filtered in the stack traces.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Add Packages...</p>
-			</td>
-			<td valign="top">
-			<p>Allows to add packages to be filtered. This action opens a package selection dialog to choose the packages to be filtered in the stack traces.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Remove</p>
-			</td>
-			<td valign="top">
-			<p>Removes the currently selected stack trace filter pattern.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Enable All</p>
-			</td>
-			<td valign="top">
-			<p>Enables all stack trace filter patterns.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Disable All</p>
-			</td>
-			<td valign="top">
-			<p>Disables all stack trace filter patterns.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-    <p>
-      <img src="../../../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../../../gettingStarted/qs-junit.htm">Using JUnit</a>
-    </p>
-    <p>
-      <img src="../../../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../../../reference/ref-dialog-open-type.htm">Open type</a>
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-properties-files-editor.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-properties-files-editor.htm
deleted file mode 100644
index 10e7fb8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/java/ref-preferences-properties-files-editor.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Properties Files Editor Preferences</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Properties Files Editor Preferences</h1>
-<p>Indicate your preferences for the Properties Files Editor settings on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.PropertiesFileEditorPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Properties Files Editor preference page">
-<b> Java &gt; Properties Files Editor </b></a> preference page.</p>
-
-    <p>
-      Syntax coloring specifies how the content of '.properties' files rendered. Note that general 
-      text editor settings such as the background color can be configured on the general 'Text Editors' preference pages.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Properties files editor settings">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            Element
-          </td>
-          <td valign="top">
-            <p>
-              A list of elements that may be rendered with its own foreground color and style.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              default colors and styles
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Preview
-          </td>
-          <td valign="top">
-            <p>
-              Displays the preview of a properties file respecting the current colors and styles.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              n/a
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/ref-preferences-java.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/ref-preferences-java.htm
deleted file mode 100644
index a5f44c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/ref-preferences-java.htm
+++ /dev/null

@@ -1,205 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java Preferences
-    </title>
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Java Preferences
-    </h1>
-    
-    <p>
-      The following Java preferences can be set on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaBasePreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java preference page">
-      <b>Java</b></a> preference page
-      and its sub-pages.
-    </p>
-    <ul>
-      <li><a href="java/ref-preferences-appearance.htm">Appearance</a></li>
-      <li><a href="java/ref-preferences-build-path.htm">Build Path</a></li>
-      <li><a href="java/ref-preferences-code-style.htm">Code Style</a></li>
-      <li><a href="java/ref-preferences-compiler.htm">Compiler</a></li>
-      <li><a href="java/debug/ref-debug.htm">Debug</a></li>
-      <li><a href="java/ref-preferences-editor.htm">Editor</a></li>
-      <li><a href="java/ref-preferences-installed-jres.htm">Installed JREs</a></li>
-      <li><a href="java/ref-preferences-junit.htm">JUnit</a></li>
-      <li><a href="java/ref-preferences-properties-files-editor.htm">Properties File Editor</a></li>
-    </ul>
-    
-    <table border="1" cellspacing="0" cellpadding="5" summary="General Java settings">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-
-         <tr>
-          <td valign="top">
-            Action on double click in the Package Explorer
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Go into the selected element</strong>
-              </dt>
-              <dd>
-                When you double click a container, a <strong>Go Into</strong> command is executed.
-                <br>
-                See <strong>Go Into</strong> from the <a href="../ref-menu-navigate.htm">Navigate</a> menu.
-              </dd>
-              <dt>
-                <strong>Expand the selected element</strong>
-              </dt>
-              <dd>
-                 When you double click a container, it is expanded and its children are revealed.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-            Expand the selected element
-          </td>
-        </tr>
-      
-        <tr>
-          <td valign="top">
-            When opening a Type Hierarchy
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Open a new Type Hierarchy Perspective</strong>
-              </dt>
-              <dd>
-                  Opens a new Type Hierarchy perspective whenever a Type Hierarchy view is opened.
-              </dd>
-              <dt>
-                <strong>Show the Type Hierarchy View in the current perspective</strong>
-              </dt>
-              <dd>
-                  The Type Hierarchy view is displayed in the current perspective.
-              </dd>
-            </dl>
-             <em>Note: On the Workbench preferences page, you can choose whether new perspectives open in a new window, in the current window, or as a replacement for the current
-            perspective.</em>
-          </td>
-          <td valign="top">
-            Show the Type Hierarchy View in the current perspective
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            Refactoring Java code
-          </td>
-          <td valign="top">
-             <dl>
-              <dt>
-                <strong>Save all modified resources automatically prior to refactoring</strong>
-              </dt>
-              <dd>
-                  If this option is turned off, refactorings may prompt to save modified files if required.
-                  If it is turned on, all modified files are saved without prompting prior to opening a refactoring wizard.
-              </dd>
-              </dl>
-          </td>
-          <td valign="top">
-            Off
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">&nbsp;
-          </td>
-          <td valign="top">
-             <dl>
-              <dt>
-                <strong>Rename in editor without dialog</strong>
-              </dt>
-              <dd>
-                  If this option is turned on, then the rename refactoring will not show a dialog if invoked inside a Java editor.
-                  Instead the new name for the element to rename can be typed into the editor right away.
-              </dd>
-              </dl>
-          </td>
-          <td valign="top">
-            On
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="top">
-            Search
-          </td>
-          <td valign="top">
-             <dl>
-              <dt>
-                <strong>Use reduced search menu</strong>
-              </dt>
-              <dd>
-                  If this option is turned on, the search context menus show only the most frequently used search actions.
-              </dd>
-              </dl>
-          </td>
-          <td valign="top">
-            On
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            Java dialogs
-          </td>
-          <td valign="top">
-             <dl>
-              <dt>
-                <strong>Clear all 'do not show again' settings and show all hidden dialogs again</strong>
-              </dt>
-              <dd>
-                  If pressed, all 'do not show' settings are cleared.
-              </dd>
-              </dl>
-          </td>
-          <td valign="top">
-			Button
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../../concepts/concept-java-views.htm">Java views</a>
-    </p>
-    <p>
-      <img src="../../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../../reference/views/ref-view-package-explorer.htm">Package explorer view</a><br>
-      <a href="../../reference/views/ref-type-hierarchy.htm">Type hierarchy view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-default_launchers.PNG b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-default_launchers.PNG
deleted file mode 100644
index c2d4b1c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-default_launchers.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-ext_string_subbed.PNG b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-ext_string_subbed.PNG
deleted file mode 100644
index 25a78cb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-ext_string_subbed.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-lcd_string_subbed.PNG b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-lcd_string_subbed.PNG
deleted file mode 100644
index 0bd756d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-lcd_string_subbed.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_dialog.PNG
deleted file mode 100644
index e83ba34..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_sub.PNG b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_sub.PNG
deleted file mode 100644
index a5b2ad3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/images/ref-string_sub.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-console.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-console.htm
deleted file mode 100644
index 009c192..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-console.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Console Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Console Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ConsolePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page"> <b>Run/Debug &gt; Console</b></a> preference page.  </p>
-<p>The console displays output from running applications, and allows keyboard input to be read by
-  running applications. </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Fixed width console </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This preference controls whether the console has a fixed character width. 
-          When on, a maximum character width must also be specified. Some applications 
-          write long lines to the console which require horizontal scrolling to 
-          read. This can be avoided by setting the console to use a fixed width, 
-          automatically wrapping console output. </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Off </p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Limit console output</td>
-      <td colspan="1" valign="top" align="left">This preference limits the number 
-        of characters buffered in the console. When on, a maximum buffer size must 
-        also be specified. When console output surpasses the specified maximum, 
-        output is truncated from the beginning of the buffer.</td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Displayed Tab Width </td>
-      <td colspan="1" valign="top" align="left">Allows the default width, in characters, of a tab to be specified </td>
-      <td colspan="1" valign="top" align="left">8</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Show When Program Writes to Standard Out </td>
-      <td colspan="1" valign="top" align="left">This preference will force the console to show when something is written to the system out stream. A forced-show can mean that a console will be opened, or that the console will be brought to the top if it is already open. </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Show When Program Writes to Standard Error </td>
-      <td colspan="1" valign="top" align="left">This preference will force the console to show when something is written to the system err stream. A forced-show can mean that a console will be opened, or that the console will be brought to the top if it is already open. </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Standard Out Text Color </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This preference controls the colour of text written to the standard output 
-          stream by an application. </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Black </p></td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Standard Error Text Color </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This preference controls the colour of text written to the standard error 
-          stream by an application. </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Red </p></td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Standard In Text Color </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This preference controls the colour of text typed into the console to 
-          be read by an application. </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Green </p></td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Background Colour </td>
-      <td colspan="1" valign="top" align="left">This preference controls the colour of the background of the console </td>
-      <td colspan="1" valign="top" align="left">White</td>
-    </tr>
-  </tbody>
-</table>
-<p> You can also click the <strong>Change</strong> button to set the font for the Console. </p>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-<a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a>
-</p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a><br>
-  <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a>  <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-perspectives.htm">Perspectives Preferences</a>  <br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-string_substitution.htm">String Substitution Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-view_management.htm">View Management Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-default_launchers.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-default_launchers.htm
deleted file mode 100644
index a1ff44a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-default_launchers.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Default Launchers Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Default Launchers Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchDelegatesPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Default Launchers preference page"> <b>Run/Debug &gt; Launching &gt; Default Launchers</b></a> preference page.</p>
-<p>The <strong>Default Launchers</strong> preference allows you to select what launch tooling is to be used if more than one kind of tooling exists for the same thing, for example, consider using two profilers at the same time for Java programs. For the most part, this page remains disabled, as concurrent overlapping tooling is very rare, but in the event there is overlap, the page will enable and present the user with the launch types that conflict and what modes they conflict on.</p>
-<p>The following image shows the page with conflicting tooling for Java types in the <em>run</em>, <em>debug</em> and <em>Alternate2</em> modes. In this example a preferred launcher can be selected independently for each of the conflicting modes. </p>
-<p><img src="../../../reference/preferences/run-debug/images/ref-default_launchers.PNG" alt="Default Launchers Example"> </p>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launch_configurations.htm">Launch Configurations Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launch_configurations.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launch_configurations.htm
deleted file mode 100644
index 13487f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launch_configurations.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Launch Configurations Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Launch Configurations Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchConfigurations)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launch Configurations preference page"> <b>Run/Debug &gt; Launching &gt; Launch Configurations</b></a> preference page.</p>
-<p>This page allows you set filtering options that are used throughout the workbench  to limit the exposure of certain kinds of launch configurations. These filtering setting effect the launch dialog, launch histories and the workbench. </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Filter configurations in closed projects </td>
-      <td colspan="1" valign="top" align="left">Filter out configurations that are associated with a project that is currently closed </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Filters configuration in deleted or missing projects </td>
-      <td colspan="1" valign="top" align="left">Filter out configurations that are associated with a project that has been deleted or are simply no longer available (not in the workspace, etc) </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Apply windows working set </td>
-      <td colspan="1" valign="top" align="left">Applies the filtering from any working sets currently active to the visibility of configurations associated to resources in the active working sets. i.e. if project P has two configurations associated with it, but is not in the currently active working set, the configurations do not appear in the UI, much like P does not. </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Filter check configuration types </td>
-      <td colspan="1" valign="top" align="left">Filter all configurations of the selected type regardless of the other filtering options. For example if you specify to filter Java type configurations, all Java type configurations will be filtered from the UI, not just ones that fall under the other filtering categories. </td>
-      <td colspan="1" valign="top" align="left">Off</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Delete configurations when associated project is deleted </td>
-      <td colspan="1" valign="top" align="left">Any launch configurations associated with a project being deleted will also be deleted if this option is enabled. Once deleted the configurations are not recoverable. </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Migration</td>
-      <td colspan="1" valign="top" align="left"><p>As Eclipse matures and new features are added to the launching framework, there sometimes exists the need to make changes to launch configurations. Some of these changes are made automatically, but those that are not (nonreversible ones) are left up to the end-user. </p>
-        <p>The migration section allows users to self-migrate any launch configurations that require it. Upon pressing the <strong>Migrate...</strong> button, if there are any configurations requiring migration, they are presented to the user, and the user can select the ones they want to migrate. Configuration migration is not un-doable. </p></td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../reference/preferences/run-debug/ref-default_launchers.htm">Default Launchers Preferences</a><br>
-  <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launching.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launching.htm
deleted file mode 100644
index 16df8f5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-launching.htm
+++ /dev/null

@@ -1,139 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-<title>Launching Preferences</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Launching Preferences </h1>
-<p>These preferences allow you to configure options related to launching programs in general, and govern such things as waiting for builds, saving files before launching, etc. </p>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launching preference page"> <b>Run/Debug &gt; Launching</b></a> preference page. </p>
-<table border="1" cellspacing="0" cellpadding="5" >
-  <tbody>
-    <tr>
-      <th> <p> Option </p></th>
-      <th> <p> Description </p></th>
-      <th> <p> Default </p></th>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Save required dirty editors before launching </td>
-      <td align="left" valign="top"><p>This option controls whether the user will 
-          be prompted to save any dirty editors before an application is launched. 
-          The allowable settings are: </p>
-        <ul>
-          <li> Always - when this option is selected, the user is never prompted 
-            to save dirty editors, and editors are automatically saved. </li>
-          <li>Never - when this option is selected, the user is never prompted 
-            to save dirty editors, and editors are not automatically saved. </li>
-          <li> Prompt - when this option is selected, the user is prompted to 
-            save dirty editors before launching an application.</li>
-        </ul></td>
-      <td align="left" valign="top">Prompt </td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Wait for ongoing build to complete before 
-        launching </td>
-      <td align="left" valign="top"><p>This option controls whether a launch will 
-          wait for an already executing build to complete before launching an 
-          application. The allowable settings are:</p>
-        <ul>
-          <li>Always - when this option is selected, a launch will always wait 
-            for the pending build to complete</li>
-          <li>Never - when this option is selected, a launch will never wait for 
-            the pending build to complete</li>
-          <li>Prompt - when this option is selected, the user is prompted to wait 
-            for the pending build to complete when they launch</li>
-        </ul></td>
-      <td align="left" valign="top">Always</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Launch in debug mode whenever the workspace 
-        contains breakpoints</td>
-      <td align="left" valign="top"><p>This option controls whether a launch will 
-          be performed in debug mode, even when run is pressed, when the workspace 
-          contains breakpoints. The allowable options are:</p>
-        <ul>
-          <li>Always - when this option is selected, a launch will always be performed 
-            in debug mode when breakpoints are present, no matter which launch 
-            button is pressed (run or debug)</li>
-          <li>Never - when this option is selected, a launch will always be performed 
-            in the user specified mode</li>
-          <li>Prompt - when this option is selected, the user is prompted to launch 
-            in debug mode when the workspace contains breakpoints</li>
-        </ul></td>
-      <td align="left" valign="top">Never</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Continue launch if project contains errors</td>
-      <td align="left" valign="top"><p>This option controls whether a launch should 
-          be performed when a related project contains an error. The allowable 
-          options are:</p>
-        <ul>
-          <li>Always - when this option is selected, a launch will continue in 
-            the face of compilation errors</li>
-          <li>Prompt - when this option is selected, the user is prompted to proceed 
-            with a launch when relevant compilation errors are in an associated 
-            project </li>
-        </ul></td>
-      <td align="left" valign="top">Prompt</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"><p> Build (if required) before launching </p></td>
-      <td align="left" valign="top"><p> If the workspace requires building, an 
-          incremental build will be performed prior to launching an application. </p></td>
-      <td align="left" valign="top"><p> On </p></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"><p> Remove terminated launches when a new 
-          launch is created </p></td>
-      <td align="left" valign="top"><p> When an application is launched, all 
-          terminated applications in the Debug view are automatically cleared. </p></td>
-      <td align="left" valign="top"><p> On</p></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"><p> Size of recently launched applications 
-          list </p></td>
-      <td align="left" valign="top"><p> This option controls how many launches 
-          will appear in the Run/Debug pull-down launch history menus.</p></td>
-      <td align="left" valign="top"><p> 10</p></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Launch Operation </td>
-      <td align="left" valign="top"><p>New in 3.3 is the ability to launch the selected resource or editor. The launch operation preference allows users to switch between using the old 'always launch last' behavior and the new 'launch selected resource or editor' behavior.</p>
-        <p>If the preference  to use launch selected resource or editor is selected, you can then customize what happens if the selected resource or editor is not launchable. </p>
-        <p>There are two choices for this </p>
-        <ol>
-          <li> try to launch the parent project of the resource or editor </li>
-          <li>launch the previous thing you launched. </li>
-        </ol></td>
-      <td align="left" valign="top">Launch Selected with Launch Project </td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../reference/ref-toolbar-run.htm">Run and Debug toolbar actions</a><br>
-<a href="../../../reference/preferences/run-debug/ref-console.htm">Console Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-default_launchers.htm">Default Launchers Preferences</a><br>
-  <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launch_configurations.htm">Launch Configurations Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-perspectives.htm">Perspectives Preferences</a> <br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-string_substitution.htm">String Substitution Preferences</a><br>
-<a href="../../../reference/preferences/run-debug/ref-view_management.htm">View Management Preferences</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-perspectives.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-perspectives.htm
deleted file mode 100644
index 7fdb944..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-perspectives.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Perspectives Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Perspectives Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.PerspectivePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Run/Debug Perspectives preference page"><b> Run/Debug &gt; Perspectives</b></a> preference page.</p>
-<p>The preferences on this page allow you to set which, if any perspectives are automatically opened when launchers are used in certain modes </p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Open the associated perspective when launching </td>
-      <td colspan="1" valign="top" align="left"><p>This option controls if the specified perspective will be switched to automatically or not when launching</p>
-        <ul>
-          <li>Always - the specified perspective will always be opened</li>
-          <li>Never - the specified perspective will never be opened</li>
-          <li>Prompt - the user will be prompted to switch to the specified perspective </li>
-        </ul></td>
-      <td colspan="1" valign="top" align="left">Never</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Open the associated perspective when an application suspends </td>
-      <td colspan="1" valign="top" align="left"><p>This option controls if the specified perspective will be switched to when the application susupends </p>
-        <ul>
-          <li>Always - the specified perspective will always be opened</li>
-          <li>Never - the specified perspective will never be opened</li>
-          <li>Prompt - the user will be prompted to switch to the specified perspective </li>
-        </ul></td>
-      <td colspan="1" valign="top" align="left">Prompt</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Launcher / Perspective choices </td>
-      <td colspan="1" valign="top" align="left">This option area allows you to customize what perspective will be opened for a given launch and mode that it supports. For example, you can say that you want to open the Java perspective when using the Java JDT launcher in the run mode only. </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../reference/preferences/run-debug/ref-console.htm">Console Preferences</a><br>
-  <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-string_substitution.htm">String Substitution Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-view_management.htm">View Management Preferences</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-run_debug.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-run_debug.htm
deleted file mode 100644
index 6eab835..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-run_debug.htm
+++ /dev/null

@@ -1,109 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-<title>Debug preferences</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Debug Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.DebugPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Run/Debug preference page"> <b>Run/Debug</b></a> preference page. </p>
-<p>The preferences here are generic to all debuggers, and govern stylistic and prompting options</p>
-<table border="1" cellspacing="0" cellpadding="5" >
-  <tbody>
-    <tr>
-      <th> <p> Option </p></th>
-      <th> <p> Description </p></th>
-      <th> <p> Default </p></th>
-    </tr>
-    <tr>
-      <td align="left" valign="top"><p> Reuse editor when displaying source code </p></td>
-      <td align="left" valign="top"><p> The debugger displays source code in 
-          an editor when stepping through an application. When this option is 
-          on, the debugger will reuse the editor that it opened to display source 
-          from different source files. This prevents the debugger from opening 
-          an excessive number of editors. When this option is off, the debugger 
-          will open a new editor for each source file that needs to be displayed. </p></td>
-      <td align="left" valign="top"><p> On </p></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Activate the workbench when when a breakpoint 
-        is hit</td>
-      <td align="left" valign="top">This option brings attention to the debugger 
-        when a breakpoint is encountered, by activating the associated window. 
-        The visual result varies from platform to platform. For example, on Windows, 
-        the associated window's title bar will flash.</td>
-      <td align="left" valign="top">On</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Activate the debug view when a breakpoint 
-        is hit</td>
-      <td align="left" valign="top">This option brings attention to the debug 
-        view when a breakpoint is encountered. If the view is already open it 
-        will be activated. If the view is not already open it will be opened automatically.</td>
-      <td align="left" valign="top">On</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Skip breakpoints during a 'Run to Line' operation</td>
-      <td align="left" valign="top">This option controls whether breakpoints are 
-        ignored when performing a 'Run to Line' operation. When the option is 
-        on, the debugger does not suspend at breakpoints encountered when a 'Run 
-        to Line' operation is invoked. When the option is off, breakpoints behave 
-        normally. </td>
-      <td align="left" valign="top">Off</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Prompt for conformation when deleting all breakpoints </td>
-      <td align="left" valign="top">This option controls whether you will be prompted for confirmation when you try to delete all of your breakpoints</td>
-      <td align="left" valign="top">On</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Prompt for confirmation when deleting breakpoint containers </td>
-      <td align="left" valign="top">This option controls if you will be prompted for confirmation when you try to delete a breakpoint container, e.g. a breakpoint working set </td>
-      <td align="left" valign="top">On</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Changed value colour </td>
-      <td align="left" valign="top">This option allows you to change the colour of a changed value in the variables view, expressions view, memory view, anywhere running program variables are rendered </td>
-      <td align="left" valign="top">Red</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Changed value background colour </td>
-      <td align="left" valign="top">This option allows you to change the selection colour  of a changed variable, e.g. in the variables view showing columns </td>
-      <td align="left" valign="top">Yellow</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Memory unbuffered colour </td>
-      <td align="left" valign="top">This option allows you to change the rendering colour of unbuffered memory blocks in the memory view </td>
-      <td align="left" valign="top">Grey</td>
-    </tr>
-    <tr>
-      <td align="left" valign="top">Memory buffered colour </td>
-      <td align="left" valign="top">This option allows you to change the rendering colour of buffered memory blocks in the memory view </td>
-      <td align="left" valign="top">Black</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../reference/preferences/run-debug/ref-console.htm">Console Preferences</a><br>
-  <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-perspectives.htm">Perspectives Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-string_substitution.htm">String Substitution Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-view_management.htm">View Management Preferences</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-string_substitution.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-string_substitution.htm
deleted file mode 100644
index 406dd7d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-string_substitution.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>String Substitution Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> String Substitution Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.StringVariablePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the String Substitution preference page"> <b>Run/Debug &gt; String Substitution</b></a> preference page.</p>
-<p>This preference page is used solely for the purpose of creating string variables to be reused in other locations that accept string variable substitution. </p>
-<p>The platform SDK for Eclipse uses string variables in the launch dialog for setting program and VM arguments for certain types of launch configurations, as well as allowing substitutions for Ant targets in the External Tools launch dialog. Consider the following screen shot which shows the <strong>String Substitution</strong> preference page with a new <em>TEST</em> string variable created. </p>
-<p><img src="../../../reference/preferences/run-debug/images/ref-string_sub.PNG" alt="String Substitution Page With Example TEST Variable"></p>
-<p>In this case the <em>TEST</em> variable does nothing, but in the 'real' world it could point to a directory or program that you would like to reuse the path for in configurations, etc.</p>
-<p>If we now want to leverage this new variable, we can do so from the launch dialog on the arguments tab (for those configurations that have a standard arguments tab), by selecting the <strong>Variables...</strong> button for either the program or VM arguments text area. Selecting the Variables button opens a dialog with a listing of all of the string variables available. </p>
-<p>In the following screen shot we can see the <em>TEST</em> variable available in the list.</p>
-<p><img src="../../../reference/preferences/run-debug/images/ref-string_dialog.PNG" alt="String Variable Selection Dialog"> </p>
-<p>We can now select the <em>TEST</em> variable and insert in as an argument if we wish, as shown in the following screen shot.</p>
-<p><img src="../../../reference/preferences/run-debug/images/ref-lcd_string_subbed.PNG" alt="Launch Dialog With Substituted String"> </p>
-<p>The other mentioned platform use of string substitution in in the External Tools launch dialog, used with Ant configurations, as shown in the following screen shot.</p>
-<p><img src="../../../reference/preferences/run-debug/images/ref-ext_string_subbed.PNG" alt="Ant Configuration Using String Substitution"> </p>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../reference/preferences/run-debug/ref-console.htm">Console Preferences</a><br>
-  <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-perspectives.htm">Perspectives Preferences</a> <br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-view_management.htm">View Management Preferences</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-view_management.htm b/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-view_management.htm
deleted file mode 100644
index 15322c4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-view_management.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>View Management Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> View Management Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ViewManagementPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the View Management preference page"> <b>Run/Debug &gt; View Management</b></a> preference page.</p>
-<p>These preferences allow you to configure which views will actively support automatic view opening.</p>
-<table border="1" cellspacing="0" cellpadding= "5">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">Perspectives</td>
-      <td colspan="1" valign="top" align="left">The listing of perspectives to select which ones will support automatic view opening </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Do not automatically open/close views which have been manually opened/closed </td>
-      <td colspan="1" valign="top" align="left">This option controls if views manually opened/closed will be effected by view managment </td>
-      <td colspan="1" valign="top" align="left">On</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Reset button </td>
-      <td colspan="1" valign="top" align="left">Resets the listing of supporting perspectives. </td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p> <a href="../../../reference/preferences/run-debug/ref-console.htm">Console Preferences</a><br>
-  <a href="../../../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs Preferences</a> <br>
-  <a href="../../../reference/preferences/java/debug/ref-debug.htm">Java Debug Preferences </a><br>
-  <a href="../../../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-perspectives.htm">Perspectives Preferences</a> <br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Run/Debug Preferences</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-string_substitution.htm">String Substitution Preferences</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/propertypages/images/rundebug-proppage.PNG b/bundles/org.eclipse.jdt.doc.user/reference/propertypages/images/rundebug-proppage.PNG
deleted file mode 100644
index 7b34667..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/propertypages/images/rundebug-proppage.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/propertypages/ref-properties-rundebug.htm b/bundles/org.eclipse.jdt.doc.user/reference/propertypages/ref-properties-rundebug.htm
deleted file mode 100644
index 4957f43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/propertypages/ref-properties-rundebug.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Run / Debug Properties Page</title>
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Run / Debug Properties Page</h1>
-    <p>This property page allows you to view and manage all launch configurations that apply to the pages' corresponding resource.</p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Run/Debug property page">
-      <thead>
-        <tr>
-          <th>Option</th>
-          <th>Description</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">Launch Configuration List</td>
-          <td valign="top">The list shows all of the launch configurations in the current workspace that apply to the property pages' corresponding resource.</td>
-        </tr>
-        <tr>
-          <td valign="top">New...</td>
-          <td valign="top">The <b>New...</b> button can be used to create a new launch configuration that applies to the corresponding resource. When selected, the New... button will present you with a
-          dialog of all of the launch configuration types that can be used to make a configuration that applies to the corresponding resource.</td>
-        </tr>
-        <tr>
-          <td valign="top">Duplicate</td>
-          <td valign="top">The <b>Duplicate</b> button is used to make an identical copy of a selected launch configuration.</td>
-        </tr>
-        <tr>
-          <td valign="top">Edit...</td>
-          <td valign="top">The <b>Edit...</b> button will open the launch configuration edit dialog, allowing you to change the selected launch configuration.</td>
-        </tr>
-        <tr>
-          <td valign="top">Delete</td>
-          <td valign="top">The <b>Delete</b> button is used to delete the selected launch configuration.</td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-	<p><img src="images/rundebug-proppage.PNG" alt="Run / Debug Property Page"></p>
-	<p><img src="../../images/ngrelc.png" alt="Related concepts"></p>
-		<p>
-			<a href="../../concepts/clocdbug.htm">Local Debugging</a><br>
-			<a href="../../concepts/cremdbug.htm">Remote Debugging</a>
-		</p>
-    <p><img src="../../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-	<p> 
-		<a href="../../tasks/task-launching_java_program.htm">Launching a Java Program</a><br>
-		<a href="../../tasks/tasks-debug-launch.htm">Launching a Java program in debug mode</a><br>
-		<a href="../../tasks/task-preparing_to_debug.htm">Preparing to Debug</a><br>
-		<a href="../../tasks/task-relaunch_program.htm">Re-launching a program</a><br>
-		<a href="../../tasks/task-launching_java_applet.htm">Launching a Java applet</a><br>
-		<a href="../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-		<a href="../../tasks/task-remotejava_launch_config.htm">Using the remote Java application launch configuration</a>
-	</p>
-	<p><img src="../../images/ngrelr.png" alt="Related reference"></p>
-	<p>
-		<a href="../ref-toolbar-run.htm">Run and Debug toolbar actions</a><br>
-	</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-actions-toolbar.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-actions-toolbar.htm
deleted file mode 100644
index c223cdd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-actions-toolbar.htm
+++ /dev/null

@@ -1,201 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Java Toolbar Actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java Toolbar Actions
-    </h1>
-    <br>
-     <br>
-     
-    <table border="1" cellspacing="0" cellpadding="5" summary="Java Toolbar Actions">
-      <caption>
-        Java Actions<br>
-      </caption>
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Toolbar Button
-            </p>
-          </th>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            Description
-          </th>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.ui/etool16/newjprj_wiz.png" alt="Create a Java Project"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java project.
-            </p>
-            <br>
-             <a href="ref-wizard-java-project.htm">See new Java project wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.ui/etool16/newpack_wiz.png" alt="Create a Java Package"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Package
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java package.
-            </p>
-            <br>
-             <a href="ref-wizard-package.htm">See new Java package wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.ui/etool16/newclass_wiz.png" alt="Create a Java Class"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Class
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java class.
-            </p>
-            <br>
-             <a href="ref-wizard-class.htm">See new Java class wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.ui/etool16/newenum_wiz.png" alt="Create a Java Enum"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java enum
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java enum.
-            </p>
-            <br>
-             <a href="ref-wizard-enum.htm">See new Java enum wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.ui/etool16/newint_wiz.png" alt="Create a Java Interface"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java Interface
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java interface.
-            </p>
-            <br>
-             <a href="ref-wizard-interface.htm">See new Java interface wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.ui/etool16/newannotation_wiz.png" alt="Create a Java annotation"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java annotation
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new Java annotation.
-            </p>
-            <br>
-             <a href="ref-wizard-annotation.htm">See new Java annotation wizard</a>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.junit/etool16/new_testcase.png" alt="Create a JUnit test case"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a JUnit test case
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command helps you create a new JUni test case.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../images/org.eclipse.jdt.ui/etool16/opentype.png" alt="Open Type"></p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Open Type
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              This command allows you to browse the workspace for a type to open in the defined default Java editor. You can optionally choose to display the type simultaneously
-              in the Hierarchy view. See <a href="ref-dialog-open-type.htm">Open Type dialog</a>. 
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <br>
-       <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-     <a href="../tasks/tasks-76.htm">Opening an editor on a type</a> 
-    <p>
-       <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="ref-wizard-java-project.htm">New Java project wizard</a><br>
-       <a href="ref-wizard-package.htm">New Java package wizard</a><br>
-       <a href="ref-wizard-class.htm">New Java class wizard</a><br>
-       <a href="ref-wizard-enum.htm">New Java enum wizard</a><br>
-       <a href="ref-wizard-interface.htm">New Java interface wizard</a><br>
-       <a href="ref-wizard-annotation.htm">New Java annotation wizard</a><br>
-       <a href="ref-wizard-scrapbook.htm">New Java scrapbook page wizard</a><br>
-       <a href="views/ref-viewsandeditors.htm">Views and editors</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm
deleted file mode 100644
index 6262ed4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-automaticProcessorOptions.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005-2007 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Automatic Processor Options
-    </title>
-  </head>
-  <body>
-    <h1>
-      Automatic Processor Options
-    </h1>
-    <p>Annotation processor options are configured in the 
-    <a href="ref-apt-config.htm">Annotation Processing preference dialog</a>.  Certain options 
-    are automatically provided to processors using the Java 5 Mirror API; entering them in the Annotation Processing 
-    preference dialog will have no effect, since the automatically provided values will 
-    override any values set there.  The automatic options include the following:</p>
-    <dl>
-    	<dt><strong>-classpath</strong></dt>
-    	<dd>
-    		The compiler classpath.  All entries are absolute paths, not workspace-relative.
-    	</dd>
-    	<dt><strong>-sourcepath</strong></dt>
-    	<dd>
-    		The compiler source path.  All entries are absolute paths, not workspace-relative.
-    	</dd>
-    	<dt><strong>-d</strong></dt>
-    	<dd>
-    		The absolute path of the compiler binary output directory, into which .class files are 
-    		built.
-    	</dd>
-    	<dt><strong>-s</strong></dt>
-    	<dd>
-    		The absolute path of the generated source directory, into which annotation processors 
-    		will generate files.
-    	</dd>
-    	<dt><strong>-source</strong></dt>
-    	<dd>
-    		The compiler -source option.  Typically a string such as &quot;5.0&quot;.
-    	</dd>
-    	<dt><strong>-target</strong></dt>
-    	<dd>
-    		The compiler -target option.  Typically a string such as &quot;5.0&quot;.
-    	</dd>
-    	<dt><strong>phase</strong></dt>
-    	<dd>
-    	    The string <code>RECONCILE</code>, <code>BUILD</code>, or <code>OTHER</code>, depending
-    	    on whether the processor has been called during editing, during a build, or outside the
-    	    context of compilation, respectively. This option is only provided when running in the Eclipse IDE.
-    	</dd>
-    </dl>
-    <p>Except for <code>phase</code>, there are no automatically provided options for processors 
-    using the Java 6 annotation processing API, because the JavaFileManager methods provide the same functionality.</p> 
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm
deleted file mode 100644
index e9cf285..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-config.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005-2007 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Annotation Processing Preferences
-    </title>
-  </head>
-  <body>
-    <h1>
-      Annotation Processing
-    </h1>
-    <p>Annotation processors are utility programs that can generate additional Java code or other files, 
-    and produce problem markers,
-    based on Java 5 (JSR-175) annotations. Processors can be based on either the 
-    <a href="http://java.sun.com/j2se/1.5.0/docs/guide/apt/mirror/overview-summary.html">Java 5 Mirror APIs</a> or the
-    <a href="http://java.sun.com/javase/6/docs/api/javax/annotation/processing/package-summary.html">Java 6 
-    annotation processing APIs</a>. The Annotation Processing preference pane permits configuration 
-    of preferences that apply to all processors in a project or workspace.  The <a href="ref-apt-factoryPath.htm">
-    Factory Path preference pane</a> specifies which processors are enabled and permits configuration of 
-    individual processors.</p>
-    <h2>
-        Enable annotation processing
-    </h2>
-    <p>Annotation processing is turned off by default, and must be turned on by checking this checkbox
-    for each project that needs it.  It is only necessary to enable annotation processing in a project
-    in order to have annotation processors operate on that project's code.  The mere presence of 
-    annotations in code does not mean that annotation processing is required; for example, the 
-    <code>@Deprecated</code> and <code>@Override</code> annotations do not typically require processing.</p> 
-    <h2>
-    	Enable processing in editor
-    </h2>
-    <p>When this option is enabled, processors will run whenever changes are made in the Java editor,
-    as well as whenever the project is built. Enabling processors to run in the editor allows them to
-    generate contribute errors and warnings as you type. For instance, processors can red-squiggle
-    a bad annotation value to indicate a semantic problem that the compiler alone would not be able to discover.
-    However, some annotation processors are slow enough that running them in the editor interferes with
-    the usability of the editor. In this situation, disabling this option can improve performance of 
-    the editor. Processors will still run whenever the project is built. This option does not apply to
-    Java 6 annotation processors, which Eclipse can (for now) only run during a build.</p>
-    <h2>
-    	Generated source directory
-    </h2>
-    <p>Files will be generated on disk relative to the specified directory.  By default this directory
-    is named &quot;.apt_generated&quot;, which since it starts with a '.' causes it to be filtered out 
-    of the Package Explorer view.  
-    Generated files have the &quot;derived&quot; bit set; when a project is cleaned, all derived files under the
-    generated source directory will be removed.  It is recommended to only
-    use this directory for files generated by processors; do not place any manually created files under
-    this directory, and do not use a pre-existing directory as the generated source directory.</p>
-    <h2>
-    	Processor options
-    </h2>
-    <p>Options entered here will be available via the AnnotationProcessorEnvironment interface (for Java
-    5 processors) or the ProcessingEnvironment interface (for Java 6 processors).  
-    Certain options are automatically provided to Java 5 processors; entering them in this dialog
-    will have no effect, since the automatically provided values will override any values set here.  
-    The automatic options are described <a href="ref-apt-automaticProcessorOptions.htm">here</a>. More
-    information about processor options is in the topic on <a href="ref-apt-processorOptionsInput.htm">the
-    Processor Options input dialog</a>.</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm
deleted file mode 100644
index 5602aef..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPath.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Factory Path Preferences
-    </title>
-  </head>
-  <body>
-    <h1>
-      Factory Path Preferences
-    </h1>
-    <p>Annotation processors can generate additional Java code or other files, and produce problem markers,
-    based on Java 5 (JSR-175) annotations.  The <a href="ref-apt-config.htm">Annotation Processing preference
-    pane</a> permits configuration of preferences that apply to all processors in a project or workspace.  
-    The Factory Path preference pane specifies which processors are enabled and permits configuration of 
-    individual processors. <i>Settings in the Factory Path preference pane will only have an effect if
-    annotation processing is enabled in the Annotation Processing preference pane.</i></p>
-    <p>The pane displays a list of all the plugins and jar files that contain annotation processors that
-    may be applied to the project.  To add or remove jar files from the list, use the corresponding buttons.
-    Jar files may be specified by absolute path using the Add External Jars... button, or by path relative
-    to a classpath variable using the Add Variable... button.  All installed plugins that extend the
-    org.eclipse.jdt.apt.annotationProcessorFactory extension point are also displayed in the list.</p>
-    <p>To enable a particular plugin or jar file, select the corresponding checkbox within the list.
-    Processors within plugins and jars that are not checked will not be executed.  If more than one processor
-    claims the same annotation, only first one on the list will be served that annotation.  To reorder the
-    list, use the Up and Down buttons.</p>
-    <p>The Advanced... button leads to the <a href="ref-apt-factoryPathOptions.htm">Advanced Factory Path Options
-    dialog</a>, which is used to view the individual processors within a plugin or jar file
-    and to configure additional options. If a plugin or jar file on the factory path is known to contain
-    processors but it does not show any contents in the Advanced Factory Path Options dialog, it may be missing
-    the META-INF/services entry or plugin.xml entry that is required to declare the processors. More
-    information about developing annotation processors is available in the 
-    <a href="jdt_apt_getting_started.htm">Getting Started with APT</a> topic.</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm
deleted file mode 100644
index 2c9c549..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-factoryPathOptions.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005-2007 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Advanced Factory Path Options Dialog
-    </title>
-  </head>
-  <body>
-    <h1>
-      Advanced Factory Path Options Dialog
-    </h1>
-    <p>The Advanced Factory Path Options dialog is reached from the <a href="ref-apt-factoryPath.htm">Factory Path</a>
-    preferences pane.  It is used to view the individual processors within a plugin or jar file
-    and to configure additional options.  Options on this dialog do not normally need to be changed from
-    the default.</p>
-    <dl>
-    <dt><strong>Run this container's processors in batch mode</strong></dt>
-    <dd>
-    When this option is selected, the processors and processor factories in this jar will be run in  
-    a mode that enhances compatibility with the Sun(TM) command-line tool apt.  In this mode, 
-    processor classes are loaded at the beginning of a build, executed over the full set of Java types,
-    and then unloaded, as they would be when running apt at the command line.  Processors run in this
-    mode are only run during a full build, not during incremental builds.
-    This option is only configurable for jar files; for plugins it is always set to false.  
-    This option only applies to processors using the Java 5 Mirror APIs. It does not affect processors
-    using the Java 6 annotation processing APIs.
-    </dd>
-    </dl>
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm
deleted file mode 100644
index 5cf011a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-apt-processorOptionsInput.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-	<meta name="copyright" content="Copyright (c) 2005-2007 BEA Systems, Inc. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html" >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Processor Option Input Dialog
-    </title>
-  </head>
-  <body>
-    <h1>
-      Processor Option Input Dialog
-    </h1>
-    <p>The Processor Option input dialog is reached from the <a href="ref-apt-config.htm">Annotation Processing
-    preferences pane</a>.  It allows processor options to be added or modified.</p>  
-    <p>Options entered here will be presented to processors using the Java 5 Mirror APIs through the 
-    AnnotationProcessorEnvironment interface, or to processors using the Java 6 annotation processing
-    APIs through the ProcessingEnvironment interface.  For Java 5 processors, in order to be compatible
-    with other implementations of this API, each option will be presented in two forms: as a key/value 
-    pair, and as a combined key corresponding to the command-line form of the option, namely 
-    &quot;-Akey=value&quot;. For instance, an option with key &quot;foo&quot; and value &quot;bar&quot; would be presented
-    both that way and as key &quot;-Afoo=bar&quot;, value null. For Java 6 processors, the options are
-    simply presented as a map of key/value pairs, without the -A and without the combined -Akey=value form.</p>
-    <p>Option values representing paths may begin with a percent-delimited token such as <code>%FOO%/</code>.  
-    If the token is the name of a classpath variable, it will be replaced with the current
-    value of the variable at processor execution time.  The special value <code>ROOT</code> expands
-    to the absolute path of the workspace.  For example, <code>%ROOT%/foo/bar.xml</code> might 
-    expand to <code>d:/my_workspace/foo/bar.xml</code>, and <code>%JRE_LIB%/rt.jar</code> might 
-    expand to <code>c:/jdk1.5.0/lib/rt.jar</code>.  Similarly, the special value <code>PROJECT.DIR</code>
-    expands to the absolute path of the current project.</p>
-    <p>Certain options are automatically provided to the processors; entering them in this dialog
-    will have no effect, since the automatically provided values will override any values set here.  
-    The automatic options are described <a href="ref-apt-automaticProcessorOptions.htm">here</a>.</p>
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-configure-working-sets.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-configure-working-sets.htm
deleted file mode 100644
index 86c34c8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-configure-working-sets.htm
+++ /dev/null

@@ -1,192 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Configure Working Sets dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Configure Working Sets dialog
-    </h1>
-    <p>
-     The Configure Working Sets dialog provides means to configure the contents and order of the working sets along with creating new ones 
-     and removing existing working sets.
-    </p>
-	<p>
-     Use <strong>Configure Working Sets...</strong> from the Package Explorer's view menu when it is showing working sets as top level elements. 
-	</p>
-    <p>
-      The dialog presents a list of working sets, whose visibility in the Package Explorer can be configured by checking or unchecking it and the order can be configured
-      either manually, by moving them up or down in the list, or by having them automatically sorted. Working sets can also be created or removed and their 
-      contents can be configured. 
-    </p>
-    <p>
-      After pressing <strong>OK</strong>, the checked working sets will be visible in the Package Explorer with their configured contents and order.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Override methods settings">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select and sort working sets visible in Package Explorer
-          </p>
-        </td>
-        <td valign="top">
-          Lists all the working sets, checked if they are currently active and visible in the Package Explorer, unchecked otherwise.
-        </td>
-        <td valign="top">
-          <p>n/a</p>
-        </td>
-      </tr>      
-	  <tr>
-        <td valign="top">
-          <p>
-            Up
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Moves the selected working sets up in the list. Enabled only when <strong>Sort working sets</strong> is disabled.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-	   <tr>
-        <td valign="top">
-          <p>
-            Down
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Moves the selected working sets down in the list. Enabled only when <strong>Sort working sets</strong> is disabled.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Selects all working sets.
-          </p>
-        </td>
-        <td valign="top">
-                <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Deselect All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Deselects all working sets.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            New
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Creates a new working set.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>        
-      </tr>      
-      <tr>
-        <td valign="top">
-          <p>
-            Edit
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Edits the contents of a working set.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            Remove
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Removes one or more working sets.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            Sort working sets
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Sorts the working sets alphabetically below the <b>Other Projects</b> working set.
-          </p>
-        </td>
-        <td valign="top">
-        <p>Off</p>
-        </td> 
-      </tr>	  
-    </table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-dialog-working-set-assignments.htm">Working Set Assignments dialog</a><br>	  
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm
deleted file mode 100644
index 6f0614d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-gettersetter.htm
+++ /dev/null

@@ -1,154 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Create Getters and Setters
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Create Getters and Setters
-    </h1>
-    <p>
-      This dialog lets select the getter and setter methods to create.
-    </p>
-	<p>
-     Use <strong>Generate Getters and Setters</strong> from the <a href="ref-menu-source.htm">Source menu</a> or the context menu on a selected field or type, or a text selection in
-    a type to open the dialog.
-     The Generate Getters and Setters dialog shows getters and setters for all fields of the selected type. The methods are grouped by the type's fields. 
-	 </p>
-    <p>
-      The names of the getter and setter methods are derived from the field name. If you use a prefix or suffix for fields (e.g. fValue, _value, val_m), you can specify the
-      suffixes and prefixes in the <a href="preferences/java/ref-preferences-code-style.htm">Code Style</a> preference page (Windows &gt; Preferences &gt; Java &gt; Code Style).
-    </p>
-    <p>
-      When pressing&nbsp;<strong>OK</strong>, all selected getters and setters are created.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Getter/Setter options">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select getters and setters to create
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            A tree containing getter and setter methods that can be created. Getters and setters are grouped by field their associated field.&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Select all getter and setter methods
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Deselect All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Deselect all getter and setter methods
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select Getters
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Select all getter methods
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Insertion point
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Defines where in the type body the new methods are inserted
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Sort by
-          </p>
-        </td>
-        <td valign="top">
-            Defines how to sort the new methods:<br>
-            <ul>
-            <li>in getter/setter pairs</li>
-            <li>first getters, then setters</li>
-            </ul>
-          
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Access modifiers
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Defines the access modifiers of the new methods
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Generate method comments
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Controls whether Javadoc comments are added to the created methods.
-            The comment templates are defined on the <a href="preferences/java/codestyle/ref-preferences-code-templates.htm">Code Templates</a> preference page.
-          </p>
-        </td>
-      </tr>      
-    </table>
-	  <p>
-	  <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	  </p>
-	  <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a>
-	</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm
deleted file mode 100644
index d1b14ff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-element-filters.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java Element Filters Dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java Element Filters Dialog
-    </h1>
-    <p>
-      This dialog lets you define Java element filters for the Package Explorer view and other Java views.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Filter dialog options">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-             Name filter patterns
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If enabled, a comma separated list of patterns can be specified additionally.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Off
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Select the elements to exclude from the view
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              List of pre-defined filters which can be enabled.
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              	.* resources,<br>
-              	Empty library containers<br>
-			  	Empty parent packages,<br>
-				Import declarations,<br>
-				Inner class files,<br>
-				Package declarations,<br>
-				Synthetic members
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      The <strong>Filter description</strong> field displays the description for the currently selected filter.
-    </p>
-    
-    <p><img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-    <p>
-     <a href="../concepts/concept-java-views-filtering.htm">Filtering elements</a>
-    </p>
-
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/views/ref-view-package-explorer.htm">Package explorer view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-search.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-search.htm
deleted file mode 100644
index c382fe6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-java-search.htm
+++ /dev/null

@@ -1,159 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Search Tab</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Search Tab</h1>
-
-    <p>This tab in the Search dialog allows you to search for Java elements. To show the tab invoke <b>Search &gt; Java</b>.</p>
-
-    <h2>Search string</h2>
-
-    <p>In this field, type the expression for which you wish to search, using the wildcard characters mentioned in the dialog as needed. This field is initialized based on the
-    current selection.</p>
-
-    <ul>
-      <li>Depending on what is searched for, the search string should describe the element:
-      <ul>
-        <li>Type: the type name (may be qualified or not).<br>
-        	<i>Examples:</i>
-        	<ul>
-        		<li><i>org.eclipse.jdt.internal.core.JavaElement</i></li>
-        		<li><i>MyClass.Inner</i></li>
-        		<li><i>Foo</i></li>
-        	</ul>
-        </li>
-        <li>Method: the defining type name (may be qualified or not as for Type search, optional), the method selector and its parameters (optional).<br>
-        	<i>Examples:</i>
-        	<ul>
-        		<li><i>org.eclipse.jdt.internal.core.JavaElement.getHandleFromMemento(MementoTokenizer, WorkingCopyOwner)</i></li>
-        		<li><i>equals(Object)</i></li>
-        		<li><i>foo</i></li>
-        	</ul>
-        </li>
-        <li>Package: the package name for a package (e.g. org.eclipse.jdt.internal.core)</li>
-        <li>Constructor: the defining type name (may be qualified or not as for Type search, optional) and the constructor parameters (optional).<br>
-        	<i>Examples:</i>
-        	<ul>
-        		<li><i>org.eclipse.jdt.internal.core.JavaElement(JavaElement, String)</i></li>
-        		<li><i>Foo</i></li>
-        	</ul>
-             Note that the constructor name should not be entered as it is always the same as the type name.
-        </li>
-        <li>Field: the defining type name (qualified or not as for Type search, optional) and the field name.<br>
-        	<i>Examples:</i>
-        	<ul>
-        		<li><i>org.eclipse.jdt.internal.core.JavaElement.name</i></li>
-        		<li><i>foo</i></li>
-        	</ul>
-        </li>
-      </ul>
-      </li>
-      <li>From the drop-down menu, you can choose to repeat (or modify) a recent search.<br>
-       Select the <span class="control">Case sensitive</span> field to force a case aware search. <span class="control">Case sensitive</span> is enabled when a custom search
-      string is entered.</li>
-    </ul>
-
-    <h2 class="Head">Search For</h2>
-
-    <p>Select to search for one of the following kinds of elements:</p>
-
-    <ul>
-      <li>Type</li>
-
-      <li>Method</li>
-
-      <li>Package</li>
-
-      <li>Constructor</li>
-
-      <li>Field</li>
-    </ul>
-
-    <h2 class="Head">Limit To</h2>
-
-    <p>Select to limit your search results to one of the following kinds of matches:</p>
-
-    <ul>
-      <li>Declarations</li>
-
-      <li>Implementors (available only when searching for types)</li>
-
-      <li>References</li>
-
-      <li>All occurrences</li>
-
-      <li>Read access (available only when searching for fields)</li>
-
-      <li>Write access (available only when searching for fields)</li>
-      
-      <li>Match locations (available only when searching for types).<br>
-        Match locations allow to further narrow the location of matches. Select the location
-        where to search for the type reference.
-        <ul>
-        <li>Super class declarations</li>
-		<li>Annotations</li>
-		<li>Field types</li>
-		<li>Local variable types</li>       
-        <li>Method return types</li>
-		<li>Method parameter types</li>
-		<li>Thrown exception types</li>
-		<li>Type parameter bounds</li>
-        <li>Wildcard bounds</li>
-		<li>Type argument</li>
-		<li>Cast expressions</li>
-		<li>Catch clauses</li>
-		<li>Class instance creations</li>
-		<li>'instanceof' checks</li>		
-		</ul>
-      </li>
-    </ul>
-
-    <h2 class="Item">Search In</h2>
-   
-	<p>Select where in the scope to search for results</p>
-	
-	<ul>
-		<li>Sources: Search in all source files in the scope</li>
-		<li>Required projects: Search in all required projects</li>
-		<li>JRE libraries: Search in JRE libraries on the build path</li>
-		<li>Application libraries: Search in libraries on the build path</li>
-	</ul>
-
-    <h2 class="Item">Scope</h2>
-
-    <p>Select to limit your search results to one of the following scope</p>
-
-    <ul>
-      <li>Workspace</li>
-
-      <li>Selected resources</li>
-      
-      <li>Enclosing Projects</li>
-
-      <li>Working Set</li>
-    </ul>
-
-    <p>Press <span class="control">Choose</span> to select or create a working set.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concept-java-search.htm">Java search</a></p>
-	<p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-menu-search.htm">Search</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm
deleted file mode 100644
index 98e3795..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-javadoc-location.htm
+++ /dev/null

@@ -1,186 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Javadoc Location Dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Javadoc Location Dialog
-    </h1>
-    <p>
-      This dialog lets you define the location of the Javadoc documentation for a JAR or a Java project.
-    </p>
-	<p>
-     You can reach this dialog the following ways: 
-	</p>
-    <ul>
-      <li>
-        Select a JAR or Java project, open the context menu and select Properties &gt; Javadoc Location or use&nbsp;<strong>Properties</strong> from the <a href=
-        "ref-menu-file.htm">File menu</a>
-      </li>
-      <li>
-        In the Javadoc generation wizard, on the Standard doclet settings page, choose&nbsp;<strong>Configure</strong>
-      </li>
-    </ul>
-	<p>
-    Javadoc can be attached to JARs, class folders or Java projects. For projects it documents the elements of all source folders, 
-	for JARs and class folders, elements contained in the JAR are documented. The location is used by 
-	</p>
-    <ul>
-      <li>
-        <strong>Open External Javadoc</strong> in the <a href="ref-menu-navigate.htm">Navigate menu</a> to find the Javadoc location of an element
-      </li>
-      <li>
-        Context Help (F1) to point to a Javadoc location
-      </li>
-      <li>
-        <a href="ref-export-javadoc.htm">Javadoc Export Wizard</a> to link to other documentation or as default destination for a project's documentation
-      </li>
-    </ul>
-	<p>
-    Valid locations are URLs that point to a folder containing the API documentation's&nbsp;<em>index.html</em> and&nbsp;<em>package-list</em> file. Examples are: 
-	</p>
-    <blockquote>
-      file:///M:/JAVA/JDK1.2/DOCS/API/<br>
-       http://java.sun.com/j2se/1.4/docs/api/
-    </blockquote>
-    
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Javadoc location settings">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Javadoc URL
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specify the location of the generated Javadoc documentation. You can&nbsp;<strong>Browse</strong> in the local file system for a Javadoc location (will result in a
-            file:// URL)&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          &lt;empty&gt;
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Validate
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Validate the current location by trying to access the&nbsp;<em>index.html</em> and&nbsp;<em>package-list</em> file with the given URL. If the validation was
-            successful, you can directly open the documentation.&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          <p>&nbsp;
-            
-          </p>
-        </td>
-      </tr>
-    </table>
-
- 	<p>
-    Javadoc for JARs and class folders can also be located inside an archive available on the local file system. In that case the location of the archive as well as the location
-    of the doc inside the archive has to be specified.
-	</p>   
-
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Javadoc location settings">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Archive location
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specify the location of the archive that contains the generated Javadoc documentation. You can&nbsp;<strong>Browse</strong> in the local file system for a Javadoc location 
-          </p>
-        </td>
-        <td valign="top">
-          &lt;empty&gt;
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Path within archive
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Specify the path inside the archive that contains the generated Javadoc documentation. You can&nbsp;<strong>Browse</strong> to see the content of the archive.
-          </p>
-        </td>
-        <td valign="top">
-          &lt;empty&gt;
-        </td>
-      </tr>      
-      <tr>
-        <td valign="top">
-          <p>
-            Validate
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Validate the current location by trying to access the&nbsp;<em>index.html</em> and&nbsp;<em>package-list</em> file with the given URL. If the validation was
-            successful, you can directly open the documentation.&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          <p>&nbsp;
-            
-          </p>
-        </td>
-      </tr>
-    </table>
-
-
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-open-type.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-open-type.htm
deleted file mode 100644
index 040b7a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-open-type.htm
+++ /dev/null

@@ -1,154 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Open Type
-    </title>
-  </head>
-  <body>
-    <h1>
-      Open Type
-    </h1>
-    <p>
-      This dialog allows you to browse the workbench for a type to open in an editor or type hierarchy
-    </p>
-<!-- Note: keep ref-dialog-open-type.htm and ref-dialog-type-selection.htm in sync when making changes here -->
-<!-- =========================================== snip ======================================= -->
-    <ul>
-      <li>
-        <strong>Enter type name prefix or pattern</strong>: In this field, type the first few
-        characters of the type you want to select.
-        <p>The following pattern kinds are supported:
-        </p>
-        <strong>Wildcards</strong>:<br>
-        <ul>
-          <li>
-            <em>&quot;*&quot;</em> for any string and <em>&quot;?&quot;</em> for any character
-          </li>
-          <li>
-            terminating <em>&quot;&lt;&quot;</em> or <em>&quot; &quot;</em> (space)
-            to prevent the automatic prefix matching, e.g. <em>&quot;java.*Access&lt;&quot;</em>
-            to match <code>java.util.RandomAccess</code> but not <code>java.security.AccessControlContext</code>
-          </li>
-        </ul>
-        <strong>Camel case</strong>:<br>
-        <ul>
-          <li>
-            <em>&quot;TZ&quot;</em> for types containing <em>&quot;T&quot;</em> and <em>&quot;Z&quot;</em>
-            as upper-case letters in camel-case notation, e.g. <code>java.util.TimeZone</code>
-          </li>
-          <li>
-            <em>&quot;NuPoEx&quot;</em> or <em>&quot;NuPo&quot;</em> for types containing <em>&quot;Nu&quot;</em>, <em>&quot;Po&quot;</em>,
-            (and <em>&quot;Ex&quot;</em>) as parts in camel-case notation, e.g.
-            <code>java.lang.NullPointerException</code>
-          </li>
-          <li>
-              terminating &quot;&lt;&quot; or &quot; &quot; (space) to fix the number of camel-case parts,
-              e.g. &quot;HMap&lt;&quot; and &quot;HaMap&lt;&quot;
-              match &quot;HashMap&quot; and &quot;HatMapper&quot;, but not
-              &quot;HashMapEntry&quot; nor &quot;Hashmap&quot;.
-          </li>
-        </ul>
-        <p>
-        Both pattern kinds also support <strong>package prefixes</strong>, e.g.
-        <em>&quot;j.util.*Map&lt;&quot;</em>.
-        </p>
-        <br>
-      </li>
-      <li>
-        <strong>Matching items</strong>: This list displays matches for the pattern you type in the <strong>Enter type name prefix or pattern</strong> field.
-        Recently opened types show up in a history section at the top of the list.
-      </li>
-    </ul>
-    <p>
-      The behavior of the <strong>Open Type</strong> dialog can be further customized using the dialog menu:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Open type options">
-      <caption>
-        Open Type Options
-      </caption>
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-
-        <tr>
-          <td valign="top">
-            Show Status Line
-          </td>
-          <td valign="top">
-            When selected, the <strong>Open Type</strong> dialog shows an additional bar at the bottom of the dialog which displays the package and containing
-            JRE of the selected type
-          </td>
-          <td valign="top">
-            Show status line
-          </td>
-        </tr>
-      
-        <tr>
-          <td valign="top">
-            Working Set actions
-          </td>
-          <td valign="top">
-            The search scope can be restricted by selecting one or more working sets
-            or the global Window Working Set.
-          </td>
-          <td valign="top">
-            Show all types in the workspace.
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">
-            Type Filters...
-          </td>
-          <td valign="top">
-            Types are hidden if they match the global Java type filters.
-          </td>
-          <td valign="top">
-            Show all types in the workspace.
-          </td>
-        </tr>
-
-      </tbody>
-    </table>
-<!-- =========================================== snip ======================================= -->
-    
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-76.htm">Opening an editor on a type</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm">Working sets</a><br>
-      <a href="../reference/preferences/java/appearance/ref-preferences-type-filters.htm">Type filters</a><br>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm
deleted file mode 100644
index 40fcf54..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-override-method.htm
+++ /dev/null

@@ -1,155 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Override Methods
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Override Methods
-    </h1>
-    <p>
-      This dialog lets you define methods to override.
-    </p>
-	<p>
-     Use <strong>Override/Implement Methods</strong> from the <a href="ref-menu-source.htm">Source menu</a> or the context menu on a selected type or on a text selection in a type. 
-	</p>
-    <p>
-      The dialog presents all methods that can be overridden from supertypes or implemented from interfaces. Abstract methods or unimplemented methods are selected by default.
-    </p>
-    <p>
-      The tree view groups methods by the type declaring the method. If more than one type in the hierarchy declare the same method, the method is only shown once, grouped to the
-      first type in the list of supertypes that implements or defines this method.
-    </p>
-    <p>
-      The flat view shows only methods, sorted alphabetically.
-    </p>
-    <p>
-      When pressing&nbsp;<strong>OK</strong>, method stubs for all selected methods are created.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Override methods settings">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select methods to override or implement
-          </p>
-        </td>
-        <td valign="top">
-          Select methods to override or implement
-        </td>
-        <td valign="top">
-          Abstract methods from superclasses and unimplemented methods from interfaces are selected
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Group methods by types
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Shows methods grouped by a list of the super types in which they are declared.&nbsp;
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            selected&nbsp;
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Select all methods
-          </p>
-        </td>
-        <td valign="top">
-                <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Deselect All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Deselect all methods
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Insertion point
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Defines where in the type body the new methods are inserted
-          </p>
-        </td>
-        <td valign="top">
-                <p>Last member or location of the cursor position if invoked from editor</p>
-        </td>        
-      </tr>      
-      <tr>
-        <td valign="top">
-          <p>
-            Generate method comments
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Controls whether Javadoc comments are added to the created methods.
-            The comment templates are defined on the <a href="preferences/java/codestyle/ref-preferences-code-templates.htm">Code Templates</a> preference page.
-          </p>
-        </td>
- 
-        <td valign="top">
-        <p>off</p>
-        </td> 
-      </tr>                     
-    </table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-tostring.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-tostring.htm
deleted file mode 100644
index 34a9a52..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-tostring.htm
+++ /dev/null

@@ -1,285 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) 2008, 2009 Mateusz Matela and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Generate toString() dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Generate toString() dialog
-    </h1>
-    <p>
-     The Generate toString() dialog provides means to include specific member fields and methods in generated toString() method.
-    </p>
-	<p>
-     Use <strong>Generate toString()...</strong> from the <a href="ref-menu-source.htm">Source menu</a> or the context menu on a selected type or on a text selection in a type. 
-	</p>
-    <p>
-      The members to be considered for inclusion in the toString() output are:
-      </p>
-      <ul><li>fields (non-static)</li>
-      <li>argument-less methods (non-static, non-void)</li>
-      <li>inherited fields and methods (fulfilling adequate conditions)</li></ul> 
-    <p>
-      When pressing&nbsp;<strong>OK</strong>, the toString() method printing out all selected members and eventually helper methods are created.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Override methods settings">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select fields and methods to include in the toString() method
-          </p>
-        </td>
-        <td valign="top">
-          For convenience, members are divided into up to four groups: Fields, Inherited fields, Methods and Inherited methods. Checking or unchecking a group affects the state of all it's members.
-        </td>
-        <td valign="top">
-          Only fields which are non-transient and not inherited.
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Select all fields and methods.
-          </p>
-        </td>
-        <td valign="top">
-                <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Deselect All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Deselect all fields and methods.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            Up
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Move the element with focus up the list. A member can be moved only within its group. Groups can also be moved.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-	   <tr>
-        <td valign="top">
-          <p>
-            Down
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Move the element with focus down the list. A member can be moved only within its group. Groups can also be moved.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Sort
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Sort elements in every group in lexicographical order.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Insertion point
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Defines where in the type body the generated methods are inserted. If a method already exists in a class and is overwritten, its position will not be changed (this option will have no effect).
-          </p>
-        </td>
-        <td valign="top">
-                <p>Last member or location of the cursor position if invoked from editor</p>
-        </td>        
-      </tr>      
-      <tr>
-        <td valign="top">
-          <p>
-            Generate method comments
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Controls whether a comment is added to the created toString() method. Generated comment just points to a javadoc comment for <code>java.lang.Object#toString()</code>.
-          </p>
-        </td>
-        <td valign="top">
-        <p>off</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            String format
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Defines which template is used to format the toString() output. A template determines what information about a class is added, how the fields are separated, and so on. For more information about templates, see <a href="ref-tostring-templates.htm">toString() generator: format templates</a> topic.
-          </p>
-        </td>
-        <td valign="top">
-        <p>Default template</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            Edit...
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Opens a dialog that lets you add, remove or change string format templates (see above).
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            Code style
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Defines the method code style, that is what libraries/mechanisms it uses to create output. For more information, see <a href="ref-tostring-styles.htm">toString() generator: code styles</a> topic.
-          </p>
-        </td>
-        <td valign="top">
-        <p>String concatenation</p>
-        </td> 
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Configure...
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Opens a dialog that lets you configure more options related to selected code style. Currently this button is only active for <a href="ref-tostring-styles.htm#custombuilder">Custom toString() builder</a> code style.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            Skip null values
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Controls whether the toString() method skips members that have no value (nulls). How it is accomplished depends on selected code style (see above).
-          </p>
-        </td>
-        <td valign="top">
-        <p>off</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            List contents of arrays instead of using native toString()
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Controls whether the toString() method lists items contained by arrays instead of using their default toString(). See <a href="ref-tostring-listcontent.htm">toString() generator: listing content</a> for details.
-          </p>
-        </td>
-        <td valign="top">
-        <p>off</p>
-        </td> 
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            Limit number of items in arrays/collections/maps
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Controls whether the toString() method limits the number of elements printed for arrays, <code>Collection</code>s and <code>Map</code>s, and what the limit is. It doesn't work for arrays if "Ignore arrays' default toString()" option is off. See <a href="ref-tostring-listcontent.htm">toString() generator: listing content</a> for details.
-          </p>
-        </td>
-        <td valign="top">
-        <p>off</p>
-        </td> 
-      </tr>
-    </table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a><br>
-	  <a href="ref-tostring-templates.htm">toString() generator: format templates</a><br>
-	  <a href="ref-tostring-styles.htm">toString() generator: code styles</a><br>
-	  <a href="ref-tostring-listcontent.htm">toString() generator: content listing</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-type-selection.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-type-selection.htm
deleted file mode 100644
index 45c1bf5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-type-selection.htm
+++ /dev/null

@@ -1,155 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Type Selection Dialog
-    </title>
-  </head>
-  <body>
-    <h1>
-      Type Selection Dialog
-    </h1>
-    <p>
-      Type selection dialogs allow you to browse the workbench for a type.
-    </p>
-<!-- Note: keep ref-dialog-open-type.htm and ref-dialog-type-selection.htm in sync when making changes here -->
-<!-- =========================================== snip ======================================= -->
-    <ul>
-      <li>
-        <strong>Enter type name prefix or pattern</strong>: In this field, type the first few
-        characters of the type you want to select.
-        <p>The following pattern kinds are supported:
-        </p>
-        <strong>Wildcards</strong>:<br>
-        <ul>
-          <li>
-            <em>&quot;*&quot;</em> for any string and <em>&quot;?&quot;</em> for any character
-          </li>
-          <li>
-            terminating <em>&quot;&lt;&quot;</em> or <em>&quot; &quot;</em> (space)
-            to prevent the automatic prefix matching, e.g. <em>&quot;java.*Access&lt;&quot;</em>
-            to match <code>java.util.RandomAccess</code> but not <code>java.security.AccessControlContext</code>
-          </li>
-        </ul>
-        <strong>Camel case</strong>:<br>
-        <ul>
-          <li>
-            <em>&quot;TZ&quot;</em> for types containing <em>&quot;T&quot;</em> and <em>&quot;Z&quot;</em>
-            as upper-case letters in camel-case notation, e.g. <code>java.util.TimeZone</code>
-          </li>
-          <li>
-            <em>&quot;NuPoEx&quot;</em> or <em>&quot;NuPo&quot;</em> for types containing <em>&quot;Nu&quot;</em>, <em>&quot;Po&quot;</em>,
-            (and <em>&quot;Ex&quot;</em>) as parts in camel-case notation, e.g.
-            <code>java.lang.NullPointerException</code>
-          </li>
-          <li>
-              terminating &quot;&lt;&quot; or &quot; &quot; (space) to fix the number of camel-case parts,
-              e.g. &quot;HMap&lt;&quot; and &quot;HaMap&lt;&quot;
-              match &quot;HashMap&quot; and &quot;HatMapper&quot;, but not
-              &quot;HashMapEntry&quot; nor &quot;Hashmap&quot;.
-          </li>
-        </ul>
-        <p>
-        Both pattern kinds also support <strong>package prefixes</strong>, e.g.
-        <em>&quot;j.util.*Map&lt;&quot;</em>.
-        </p>
-        <br>
-      </li>
-      <li>
-        <strong>Matching items</strong>: This list displays matches for the pattern you type in the <strong>Enter type name prefix or pattern</strong> field.
-        Recently opened types show up in a history section at the top of the list.
-      </li>
-    </ul>
-    <p>
-      The behavior of the <strong>Open Type</strong> dialog can be further customized using the dialog menu:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Type selection options">
-      <caption>
-        Type selection options
-      </caption>
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-          <th>
-            <p>
-              Default
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-
-        <tr>
-          <td valign="top">
-            Show Status Line
-          </td>
-          <td valign="top">
-            When selected, the <strong>Open Type</strong> dialog shows an additional bar at the bottom of the dialog which displays the package and containing
-            JRE of the selected type
-          </td>
-          <td valign="top">
-            Show status line
-          </td>
-        </tr>
-      
-        <tr>
-          <td valign="top">
-            Working Set actions
-          </td>
-          <td valign="top">
-            The search scope can be restricted by selecting one or more working sets
-            or the global Window Working Set.
-          </td>
-          <td valign="top">
-            Show all types in the workspace.
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">
-            Type Filters...
-          </td>
-          <td valign="top">
-            Types are hidden if they match the global Java type filters.
-          </td>
-          <td valign="top">
-            Show all types in the workspace.
-          </td>
-        </tr>
-
-      </tbody>
-    </table>
-<!-- =========================================== snip ======================================= -->
-    
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="../tasks/tasks-76.htm">Opening an editor on a type</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../../org.eclipse.platform.doc.user/concepts/cworkset.htm">Working sets</a><br>
-      <a href="../reference/preferences/java/appearance/ref-preferences-type-filters.htm">Type filters</a><br>
-      <a href="../reference/ref-dialog-open-type.htm">Open type</a><br>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-working-set-assignments.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-working-set-assignments.htm
deleted file mode 100644
index ce3a80f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-dialog-working-set-assignments.htm
+++ /dev/null

@@ -1,144 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Working Set Assignments dialog
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Working Set Assignments dialog
-    </h1>
-    <p>
-     The Working Set Assignments dialog provides means to check or uncheck one or more working sets from the list of existing working sets in order to assign
-     them to the previously selected resources.
-    </p>
-	<p>
-     To open this dialog select <strong>Assign Working Sets...</strong> from the Package Explorer's context menu. 
-	</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Override methods settings">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-        <th>
-          <p>
-            Default
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select working sets for
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-          A list of the existing working sets. If <strong>Show only Package Explorer working sets</strong> is available and checked then this
-          list will only show the working sets that are configured to appear in the Package Explorer.
-          One or more working sets can be checked or unchecked for the selected resources.
-        </p>
-        </td>
-        <td valign="top">
-          <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Select All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Selects all working sets.
-          </p>
-        </td>
-        <td valign="top">
-                <p>n/a</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Deselect All
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Deselects all working sets.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-	  <tr>
-        <td valign="top">
-          <p>
-            New...
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Creates a new working set.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>
-      </tr>
-	   <tr>
-        <td valign="top">
-          <p>
-            Show only Package Explorer working sets
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            This option is only visible if the Package Explorer shows working sets as top level elements. If checked, the dialog only shows those working sets that are currently configured to appear in the Package Explorer.
-          </p>
-        </td>
-        <td valign="top">
-        <p>On</p>
-        </td>
-      </tr>
-      <tr>
-        <td valign="top">
-          <p>
-            Configure Package Explorer working sets
-          </p>
-        </td>
-        <td valign="top">
-          <p>
-            Opens the <strong>Configure Working Sets</strong> dialog. This option is only available if the Package Explorer shows working sets as top level elements.
-          </p>
-        </td>
-        <td valign="top">
-        <p>n/a</p>
-        </td>        
-      </tr>	 
-    </table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-dialog-configure-working-sets.htm">Configure Working Sets dialog</a><br>	  
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm
deleted file mode 100644
index 2b31c5d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm
+++ /dev/null

@@ -1,305 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      JAR File Exporter
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      JAR File Exporter
-    </h1>
-    <p>
-      The
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.jdt.internal.ui.jarpackager.JarPackageWizard)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the JAR export wizard">
-      <b>Jar Export</b></a> wizard
-      allows you to create a JAR file.
-    </p>
-    <h2>
-      JAR package specification
-    </h2>
-	<p>
-	  JAR Specification Options:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="JAR specification options">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select the resources to export
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              In the list, check or clear the boxes to specify exactly the files that you want to export to the JAR file. This list is initialized by the workbench selection.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Export generated class files and resources
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If enabled, then generated class files and resources are included in the JAR.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Export all output folders for checked projects
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If enabled, then all output folders are included in the JAR.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Export Java source files and resources
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If enabled, then Java source files and resources are included in the JAR.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Export refactorings for checked projects
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If enabled, then refactoring scripts for the selected projects are included in the JAR. This allows
-              clients to migrate to the new JAR by executing all the stored refactorings in the JAR.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select the export destination
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Enter an external file system path and name for a JAR file (either new or existing). Either type a valid file path in the field or click Browse to select a file via
-              a dialog.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Options
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              You can select any of the following options:
-            </p>
-            <ul>
-              <li>
-                <strong>Compress the contents of the JAR file&nbsp;</strong>: to create a compressed JAR file
-              </li>
-              <li>
-                <strong>Add directory entries</strong>: adds an entry for each directory to the JAR file, even if the directory does only contain subdirectories.
-              </li>
-              <li>
-                <strong>Overwrite existing files without warning</strong> : if an existing file might be overwritten, you are prompted for confirmation. This option is applied to
-                the JAR file, the JAR description, and the manifest file.
-              </li>
-            </ul>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2>
-      JAR packaging options
-    </h2>
-	<p>
-        JAR Options:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="JAR options">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select options for handling problems
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Choose whether to export classes with certain problems:
-            </p>
-            <ul>
-              <li>
-                Export class files with compile errors
-              </li>
-              <li>
-                Export class files with compile warnings
-              </li>
-            </ul>
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Create source folder structure
-          </td>
-          <td>
-            Selected this option if you want the source folder structure to be rebuilt in the JAR. This option is only enabled when source files but no class files are
-            exported.&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Build projects if not build automatically
-          </td>
-          <td>
-            Select this option to force a rebuild before exporting. It is recommended to build be before exporting so the exported class files are up to date.
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Save the description of this JAR in the workspace
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              If you select this option, you can create a file in the workbench describing the JAR file you are creating. Either type and/or browse to select a path and name for
-              this new file.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2>
-      JAR manifest specification
-    </h2>
-	<p>
-        JAR Manifest Specification Options (Available when class file are exported):
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="JAR manifest specification">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Specify the manifest
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Choose the source of the manifest file for this JAR file:
-            </p>
-            <ul>
-              <li>
-                <b>Generate the manifest file</b> (you can also choose either to save or reuse and save the new manifest file)
-              </li>
-              <li>
-                <b>Use existing manifest from workspace</b>
-              </li>
-            </ul>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Seal contents
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Choose which packages in the JAR file must be sealed:
-            </p>
-            <ul>
-              <li>
-                <b>Seal the JAR</b> to seal the entire JAR file; click&nbsp;<strong>Details</strong> to exclude selectively
-              </li>
-              <li>
-                <b>Seal some packages</b> click&nbsp;<strong>Details</strong> to choose selectively
-              </li>
-            </ul>
-             <em>Note: This option is only available if the manifest is generated.</em>
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Select the class of the application entry point&nbsp;
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Type or click&nbsp;<strong>Browse</strong> to select the main class for the JAR file, if desired.
-            </p>
-             <em>Note: This option is only available if the manifest is generated.</em>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-32.htm">Creating JAR files</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-menu-file.htm">File actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm
deleted file mode 100644
index 1aaf7aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm
+++ /dev/null

@@ -1,378 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Javadoc Generation
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Javadoc Generation
-    </h1>
-    <p>
-      The
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.jdt.internal.ui.javadocexport.JavadocWizard)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Javadoc wizard">
-      <b>Javadoc Generation</b></a> wizard
-      allows you to generate Javadoc. It is a user interface for the javadoc.exe tool available in the Java JDK. Visit <a href=
-      "http://java.sun.com/j2se/1.4/docs/tooldocs/javadoc/index.html" target="_blank">Sun's Javadoc Tool</a> page for a complete documentation of the Javadoc tool.
-	</p>
-    <h2>
-      First page
-    </h2>
-	<p>
-        Type Selection:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="First page options">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Javadoc command
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Specify which command to use to generate the javadoc.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Select types for which Javadoc will be generated
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            In the list, check or clear the boxes to specify exactly the types that you want to export. This list is initialized by the workbench selection.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Create Javadoc for members with visibility
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <ul>
-            <li>
-              <strong>Private</strong>: All members will be documented
-            </li>
-            <li>
-              <strong>Package</strong>: Only members with default, protected or public visibility will be documented
-            </li>
-            <li>
-              <strong>Protected</strong>: Only members with protected or public visibility will be documented
-            </li>
-            <li>
-              <strong>Public</strong>: Only members with public visibility will be documented (default)
-            </li>
-          </ul>
-          <br>
-          <br>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Use standard doclet
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Start the Javadoc command with the standard doclet (default)&nbsp;
-          </p>
-          <ul>
-            <li>
-              <strong>Destination</strong>: select the destination to which the standard doclet will write the generated documentation. The destination is a doclet specific
-              argument, and therefore not enabled when using a custom doclet.
-            </li>
-          </ul>
-          <br>
-          <br>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Use custom doclet
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Use a custom doclet to generate documentation&nbsp;
-          </p>
-          <ul>
-            <li>
-              <strong>Doclet name</strong>: Qualified type name of the doclet
-            </li>
-            <li>
-              <strong>Doclet class path</strong>: Classpath needed by the doclet class
-            </li>
-          </ul>
-          <br>
-          <br>
-        </td>
-      </tr>
-    </table>
-	
-    <h2>
-      Standard doclet arguments
-    </h2>
-	<p>
-        Standard Doclet Arguments (available when&nbsp;<strong>Use standard doclet</strong> has been selected):
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Standard doclet arguments">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Document title
-          </p>
-        </td>
-        <td align="left" valign="top">
-          Specify a document title.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Generate use page
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Use page.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Generate hierarchy tree
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Tree page.
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Generate navigator bar
-          </p>
-        </td>
-        <td align="left" valign="top">
-          Selected this option if you want the documentation to contain a navigation bar (header and footer).
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Generate index
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Index page.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Separate index per letter
-        </td>
-        <td>
-          Create an index per letter. Enabled when <strong>Generate Index</strong> is selected.&nbsp;
-        </td>
-      </tr>
-      <tr>
-        <td>
-          @author
-        </td>
-        <td>
-          Selected this option if you want to the @author tag to be documented.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          @version
-        </td>
-        <td>
-          Selected this option if you want to the @version tag to be documented.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          @deprecated
-        </td>
-        <td>
-          Selected this option if you want to the @deprecated tag to be documented.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          deprecated list
-        </td>
-        <td>
-          Selected this option if you want the documentation to contain a Deprecated page. Enabled when the&nbsp;<strong>@deprecated</strong> option is selected.
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Select referenced archives and projects to which links should be generated
-        </td>
-        <td>
-          Specify to which other documentation Javadoc should create links when other types are referenced.&nbsp; 
-          <ul>
-            <li>
-              Select All: Create links to all other documentation locations
-            </li>
-            <li>
-              Clear All: Do not create links to other documentation locations
-            </li>
-            <li>
-              Configure: Configure the Javadoc location of a referenced JAR or project.
-            </li>
-          </ul>
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Style sheet
-        </td>
-        <td>
-          Select the style sheet to use
-        </td>
-      </tr>
-    </table>
-     
-    <h2>
-      General arguments
-    </h2>
-	<p>
-        General Javadoc Options:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="General Javadoc Options">
-      <tr>
-        <th>
-          <p>
-            Option
-          </p>
-        </th>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Overview
-          </p>
-        </td>
-        <td align="left" valign="top">
-          Specifies that Javadoc should retrieve the text for the overview documentation from the given file. It will be placed in overview-summary.html.
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            VM options
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Add any number of extra VM options here.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Extra Javadoc options
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Add any number of extra options here: Custom doclet options or JRE 1.4 compatibility options.<br>
-             Note that arguments containing spaces must enclosed in quotes. For arguments specifying html code (e.g. -header) use the &amp;&nbsp; or &amp;&quot; to avoid spaces and
-            quotes.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            JRE source compatibility
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            The JRE source compatibility to be accepted by the javadoc tool.
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Save the settings of this Javadoc export as an Ant script
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Specify to store an Ant script that will perform the specified Javadoc export without the need to use the wizard. Existing Ant script can be modified with this wizard
-            (Use Open Javadoc wizard' from the context menu on the generated Ant script)
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Open generated index file in browser
-        </td>
-        <td>
-          Opens the generated index.html file in the browser (Only available when using the standard doclet)
-        </td>
-      </tr>
-    </table>
-    <p>
-      Press&nbsp;<strong>Finish</strong> to start the Javadoc generation.
-       If the destination is different to the location configured the project's <a href="ref-dialog-javadoc-location.htm"> Javadoc Location page</a> , you will be asked if you
-      want to set the project's Javadoc location to the new destination folder. By doing this, all invocations of Open External Javadoc will use the now created
-      documentation.
-    </p>
-    <p>
-      A new process will be started and the generation performed in the background. Open the <a href="views/console/ref-console_view.htm">Console view</a> (Window &gt; Show View &gt; Console) to see the
-      progress and status of the generation.
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/ref-menu-file.htm">File actions</a><br>
-       <a href="../reference/ref-dialog-javadoc-location.htm">Javadoc location properties</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-icons.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-icons.htm
deleted file mode 100644
index f93b1de..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-icons.htm
+++ /dev/null

@@ -1,1560 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      JDT Icons
-    </title>
-  </head>
-  <body>
-    <h1>
-      JDT Icons
-    </h1>
-    <h2>
-      Objects
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300"
-        summary="Objects">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jcu_obj.png"  alt="Compilation Unit (*.java file)"><br>
-          </td>
-          <td valign="top">
-            compilation unit (*.java file)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jcu_resource_obj.png"  alt="File ending with .java"><br>
-          </td>
-          <td valign="top">
-            Java file which is not on a build path<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/classf_obj.png"  alt="class file"><br>
-          </td>
-          <td valign="top">
-            class file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/file_obj.png"  alt="file without icon assigned to its type"><br>
-          </td>
-          <td valign="top">
-            file without icon assigned to its type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/unknown_obj.png"  alt="unknown object"><br>
-          </td>
-          <td valign="top">
-            unknown object<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.debug.ui/obj16/jsbook_obj.png"  alt="Java scrapbook page (*.jpage file)"><br>
-          </td>
-          <td valign="top">
-            Java scrapbook page (*.jpage file)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.debug.ui/obj16/jsbook_run_obj.png"  alt="Java scrapbook page (evaluation in progress)"><br>
-          </td>
-          <td valign="top">
-            Java scrapbook page (evaluation in progress)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_desc_obj.png"  alt="JAR description file"><br>
-          </td>
-          <td valign="top">
-            JAR description file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/testfile_obj.gif"  alt="JUnit test result file"><br>
-          </td>
-          <td valign="top">
-            JUnit test result file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jworkingSet_obj.png"  alt="Java working set"><br>
-          </td>
-          <td valign="top">
-            Java working set<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/java_model_obj.png"  alt="Java model"><br>
-          </td>
-          <td valign="top">
-            Java model<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/library_obj.png"  alt="Library container"><br>
-          </td>
-          <td valign="top">
-           library container<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_lsrc_obj.png"  alt="JAR file with attached source"><br>
-          </td>
-          <td valign="top">
-            JAR file with attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_l_obj.png"  alt="JAR file without attached source"><br>
-          </td>
-          <td valign="top">
-            JAR file without attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/cf_src_obj.png"  alt="Class folder with attached source"><br>
-          </td>
-          <td valign="top">
-            class folder with attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/cf_obj.png"  alt="Class folder without attached source"><br>
-          </td>
-          <td valign="top">
-            class folder without attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/packagefolder_obj.png"  alt="source folder"><br>
-          </td>
-          <td valign="top">
-            source folder<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/package_obj.png"  alt="package"><br>
-          </td>
-          <td valign="top">
-            package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/empty_pack_obj.png"  alt="empty package"><br>
-          </td>
-          <td valign="top">
-            empty package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/logical_package_obj.png"  alt="logical package"><br>
-          </td>
-          <td valign="top">
-            logical package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/empty_logical_package_obj.png"  alt="empty logical package"><br>
-          </td>
-          <td valign="top">
-            empty logical package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/empty_pack_fldr_obj.png"  alt="package only containing non Java resources"><br>
-          </td>
-          <td valign="top">
-            package only containing non Java resources<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/packd_obj.png"  alt="package declaration"><br>
-          </td>
-          <td valign="top">
-            package declaration<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/impc_obj.png"  alt="import container"><br>
-          </td>
-          <td valign="top">
-            import container<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/imp_obj.png"  alt="import"><br>
-          </td>
-          <td valign="top">
-            import<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/class_obj.png"  alt="Class (public)"><br>
-          </td>
-          <td valign="top">
-            class (public)<br>
-          </td>
-        </tr>
-
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/int_obj.png"  alt="Interface (public)"><br>
-          </td>
-          <td valign="top">
-            interface (public)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/enum_obj.png"  alt="Enum type (public)"><br>
-          </td>
-          <td valign="top">
-            enum type (public)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/annotation_obj.png"  alt="Annotation type (public)"><br>
-          </td>
-          <td valign="top">
-            annotation type (public)<br>
-          </td>
-        </tr>             
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/class_default_obj.png"  alt="package visible class"><br>
-          </td>
-          <td valign="top">
-            package visible class<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerclass_private_obj.png"  alt="private class"><br>
-          </td>
-          <td valign="top">
-            private class<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/innerclass_protected_obj.png"  alt="protected class"><br>
-          </td>
-          <td valign="top">
-            protected class<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_default_obj.png"  alt="default field (package visible)"><br>
-          </td>
-          <td valign="top">
-            default field (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_private_obj.png"  alt="private field"><br>
-          </td>
-          <td valign="top">
-            private field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_protected_obj.png"  alt="protected field"><br>
-          </td>
-          <td valign="top">
-            protected field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/field_public_obj.png"  alt="public field"><br>
-          </td>
-          <td valign="top">
-            public field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methdef_obj.png"  alt="default method (package visible)"><br>
-          </td>
-          <td valign="top">
-            default method (package visible)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methpri_obj.png"  alt="private method"><br>
-          </td>
-          <td valign="top">
-            private method<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methpro_obj.png"  alt="protected method"><br>
-          </td>
-          <td valign="top">
-            protected method<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/methpub_obj.png"  alt="public method"><br>
-          </td>
-          <td valign="top">
-            public method<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Object adornments
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300"
-        summary="Object adornments">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/java_ovr.png" alt="Java Overlay" ><br>
-          </td>
-          <td valign="top">
-            marks project as Java project<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/library_ovr.gif" alt="Java Overlay" ><br>
-          </td>
-          <td valign="top">
-            decorates files and folders if they are on the build path of their enclosing Java project<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/error_co.png" alt="Abstract Overlay" ><br>
-          </td>
-          <td valign="top">
-            this Java element causes an error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/warning_co.png" alt="Warning Overlay" ><br>
-          </td>
-          <td valign="top">
-            this Java element causes a warning<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/deprecated.png" alt="Deprecation Overlay" ><br>
-          </td>
-          <td valign="top">
-            this Java element is deprecated<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/constr_ovr.png" alt="Constructor Overlay" ><br>
-          </td>
-          <td valign="top">
-            constructor<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/abstract_co.png" alt="Abstract Overlay" ><br>
-          </td>
-          <td valign="top">
-            abstract member<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/final_co.png" alt="Final Overlay" ><br>
-          </td>
-          <td valign="top">
-            final member<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/static_co.png" alt="Static overlay" ><br>
-          </td>
-          <td valign="top">
-            static member<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/synch_co.png" alt="Synchronized Overlay" ><br>
-          </td>
-          <td valign="top">
-            synchronized member<br>
-          </td>
-        </tr>
-        <!--
-          native_co.png and volatile_co.png, and read.png and write.png are currently unused.
-          sync_impl.png and sync_over.png are self-explanatory combinations of the above overlays.
-        -->
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/run_co.png" alt="Run Overlay" ><br>
-          </td>
-          <td valign="top">
-            type with public static void main(String[] args)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/implm_co.png" alt="Implementor of interface overlay" ><br>
-          </td>
-          <td valign="top">
-            implements method from interface<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/over_co.png" alt="Overrides Overlay" ><br>
-          </td>
-          <td valign="top">
-            overrides method from super class<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/focus_ovr.png" alt="Focus Overlay" ><br>
-          </td>
-          <td valign="top">
-            type with focus in Type hierarchy<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/maxlevel_co.png" alt="Maximal Expansion Overlay" ><br>
-          </td>
-          <td valign="top">
-            maximal expansion level in Call Hierarchy<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/recursive_co.png" alt="Recursive Overlay" ><br>
-          </td>
-          <td valign="top">
-            recursive call in Call Hierarchy<br>
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/class_abs_tsk.png" alt="Abstract Compilation Unit" ><br>
-          </td>
-          <td valign="top">
-            compilation unit containing an abstract class as primary type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/interface_tsk.png" alt="Interface Compilation Unit" ><br>
-          </td>
-          <td valign="top">
-            compilation unit containing an interface as primary type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/enum_tsk.png" alt="Enum Compilation Unit" ><br>
-          </td>
-          <td valign="top">
-            compilation unit containing an enum as primary type<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/ovr16/annotation_tsk.png" alt="Annotation Compilation Unit" ><br>
-          </td>
-          <td valign="top">
-            compilation unit containing an annotation as primary type<br>
-          </td>
-        </tr>
-        
-        <!-- callee_co.png and caller_co.png are currently unused -->
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Build path
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300"
-        summary="Build path">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/envvar_obj.png"  alt="class path variable"><br>
-          </td>
-          <td valign="top">
-            class path variable<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_src_obj.png"  alt="JAR with attached source"><br>
-          </td>
-          <td valign="top">
-            JAR with attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jar_obj.png"  alt="JAR without attached source"><br>
-          </td>
-          <td valign="top">
-            JAR without attached source<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/library_obj.png"  alt="system library"><br>
-          </td>
-          <td valign="top">
-            system library<br>
-          </td>
-        </tr>
-         <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/cp_order_obj.png"  alt="build path ordering"><br>
-          </td>
-          <td valign="top">
-            build path ordering<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/inclusion_filter_attrib.png"  alt="inclusion filter"><br>
-          </td>
-          <td valign="top">
-            inclusion filter<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/exclusion_filter_attrib.png"  alt="exclusion filter"><br>
-          </td>
-          <td valign="top">
-            exclusion filter<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/access_restriction_attrib.png"  alt="access rules"><br>
-          </td>
-          <td valign="top">
-            access rules<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/javadoc_location_attrib.png"  alt="Javadoc location"><br>
-          </td>
-          <td valign="top">
-            Javadoc location<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/source_attach_attrib.png"  alt="source attachment"><br>
-          </td>
-          <td valign="top">
-            source attachment<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/native_lib_path_attrib.png"  alt="native library location"><br>
-          </td>
-          <td valign="top">
-            native library location<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/output_folder_attrib.png"  alt="output folder"><br>
-          </td>
-          <td valign="top">
-            output folder<br>
-          </td>
-        </tr>   
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Code assist
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300"
-        summary="Code assist">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/html_tag_obj.png"  alt="HTML tag"><br>
-          </td>
-          <td valign="top">
-            HTML tag<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jdoc_tag_obj.png"  alt="Javadoc tag"><br>
-          </td>
-          <td valign="top">
-            Javadoc tag<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/localvariable_obj.png"  alt="local variable"><br>
-          </td>
-          <td valign="top">
-            local variable<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/template_obj.png"  alt="template"><br>
-          </td>
-          <td valign="top">
-            template<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/template_swt_obj.png"  alt="SWT template"><br>
-          </td>
-          <td valign="top">
-            SWT template<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Compare
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300"
-        summary="Compare">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/compare_field.png"  alt="field"><br>
-          </td>
-          <td valign="top">
-            field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/compare_method.png"  alt="method"><br>
-          </td>
-          <td valign="top">
-            method<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Debugger
-    </h2>
-    
-    <table cellspacing="0" cellpadding="5" border="1" width="300"
-        summary="Debugger">
-      <colgroup> <col width="25px"> </colgroup>
-  <tbody> 
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/ldebug_obj.png"  alt="debug launch"><br>
-    </td>
-    <td valign="top"> debug launch<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/lrun_obj.png"  alt="run launch"><br>
-    </td>
-    <td valign="top"> run launch<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/terminatedlaunch_obj.png"  alt="terminated run launch"><br>
-    </td>
-    <td valign="top"> terminated run launch<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/osprc_obj.png"  alt="process"><br>
-    </td>
-    <td valign="top"> process<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/osprct_obj.png"  alt="terminated process"><br>
-    </td>
-    <td valign="top"> terminated process<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/debugt_obj.png"  alt="debug target"><br>
-    </td>
-    <td valign="top"> debug target<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/debugts_obj.png"  alt="suspended debug target"><br>
-    </td>
-    <td valign="top"> suspended debug target<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/debugtt_obj.png"  alt="terminated debug target"><br>
-    </td>
-    <td valign="top"> terminated debug target<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/thread_obj.png"  alt="thread"><br>
-    </td>
-    <td valign="top"> thread<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/threads_obj.png"  alt="suspended thread"><br>
-    </td>
-    <td valign="top"> suspended thread<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/stckframe_obj.png"  alt="stack frame"><br>
-    </td>
-    <td valign="top"> stack frame<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/stckframe_running_obj.png"  alt="running stack frame"><br>
-    </td>
-    <td valign="top"> running stack frame<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/warning_co.png"  alt="adornment that marks a stack frame that may be out of synch with the target VM as a result of an unsuccessful hot code replace"> 
-      <br>
-    </td>
-    <td valign="top"> adornment that marks a stack frame that may 
-      be out of synch with the target VM as a result of an unsuccessful hot code 
-      replace<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/ovr16/error.png"  alt="adornment that marks a stack frame that is out of synch with the target VM as a result of an unsuccessful hot code replace"> 
-      <br>
-    </td>
-    <td valign="top"> adornment that marks a stack frame that is out 
-      of synch with the target VM as a result of an unsuccessful hot code replace<br>
-    </td>
-  </tr>
-  <tr>
-    <td valign="middle" align="center"><img src="../images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png"  alt="adornment that marks a stack frame that may be out of synch with the target VM as a result of an unsuccessful hot code replace"></td>
-    <td valign="top">inspected object or primitive value</td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/expression_obj.png"  alt="evaluated expression"><br>
-    </td>
-    <td valign="top"> watch expression<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/localvariable_obj.png"  alt="local variable"><br>
-    </td>
-    <td valign="top"> local variable<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/monitor_obj.png"  alt="monitor"><br>
-    </td>
-    <td valign="top"> monitor<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/contention_ovr.png"  alt="a monitor in contention"><br>
-    </td>
-    <td valign="top"> a monitor in contention<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/contentionformonitor_ovr.png"  alt="in thread in contention for a monitor"><br>
-    </td>
-    <td valign="top"> a thread in contention for a monitor<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/owned_ovr.png"  alt="a monitor that is owned by a thread"><br>
-    </td>
-    <td valign="top"> a monitor that is owned by a thread<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/ownsmonitor_ovr.png"  alt="a thread that owns a monitor"><br>
-    </td>
-    <td valign="top"> a thread that owns a monitor<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/inst_ptr_top.png"  alt="current instruction pointer (top of stack)"><br>
-    </td>
-    <td valign="top"> current instruction pointer (top of stack)<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/inst_ptr.png"  alt="current instruction pointer"><br>
-    </td>
-    <td valign="top"> current instruction pointer<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/brkp_obj.png"  alt="enabled line breakpoint"><br>
-    </td>
-    <td valign="top"> enabled line breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.debug.ui/obj16/brkpd_obj.png"  alt="disabled line breakpoint"><br>
-    </td>
-    <td valign="top"> disabled line breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png"  alt="adornment that marks a line breakpoints as installed"><br>
-    </td>
-    <td valign="top"> adornment that marks a line breakpoints as installed<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/conditional_ovr.png"  alt="adornment that marks a breakpoint as conditional"><br>
-    </td>
-    <td valign="top"> adornment that marks a breakpoint as conditional<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/entry_ovr.png"  alt="adornment that marks an entry method breakpoint"><br>
-    </td>
-    <td valign="top"> adornment that marks an entry method breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/exit_ovr.png"  alt="adornment that marks an exit method breakpoint"><br>
-    </td>
-    <td valign="top"> adornment that marks an exit method breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/read_obj.png"  alt="field access watchpoint"><br>
-    </td>
-    <td valign="top"> field access watchpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/write_obj.png"  alt="field modification watchpoint"><br>
-    </td>
-    <td valign="top"> field modification watchpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png"  alt="field access and modification watchpoint"><br>
-    </td>
-    <td valign="top"> field access and modification watchpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png"  alt="adornment that marks a watchpoint as installed"><br>
-    </td>
-    <td valign="top"> adornment that marks a watchpoint as installed<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center" rowspan="1" colspan="2"> <br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/jexception_obj.png"  alt="exception breakpoint"><br>
-    </td>
-    <td valign="top"> exception breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/jrtexception_obj.png"  alt="runtime exception breakpoint"><br>
-    </td>
-    <td valign="top"> runtime exception breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/obj16/jexceptiond_obj.png"  alt="disabled exception breakpoint"><br>
-    </td>
-    <td valign="top"> disabled exception breakpoint<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/caught_ovr.png"  alt="adornment that marks an exception breakpoint as caught"><br>
-    </td>
-    <td valign="top"> adornment that marks an exception breakpoint 
-      as caught<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/uncaught_ovr.png"  alt="adornment that marks an exception breakpoint as uncaught"><br>
-    </td>
-    <td valign="top"> adornment that marks an exception breakpoint 
-      as uncaught<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/scoped_ovr.png"  alt="adornment that marks an exception breakpoint as scoped"><br>
-    </td>
-    <td valign="top"> adornment that marks an exception breakpoint 
-      as scoped<br>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="middle" align="center"> <img src="../images/org.eclipse.jdt.debug.ui/ovr16/installed_ovr.png"  alt="adornment that marks an exception breakpoint as installed"><br>
-    </td>
-    <td valign="top"> adornment that marks an exception breakpoint 
-      as installed<br>
-    </td>
-  </tr>
-  </tbody> 
-</table>
-    <br>
-     
-    <h2>
-      Editor
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/implm_co.png"  alt="implements"><br>
-          </td>
-          <td valign="top">
-            implements<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/over_co.png"  alt="overrides"><br>
-          </td>
-          <td valign="top">
-            overrides<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/quickassist_obj.png"  alt="quick assist available"><br>
-          </td>
-          <td valign="top">
-            quick assist available<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/searchm_obj.png"  alt="search match"><br>
-          </td>
-          <td valign="top">
-            search match<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-    
-    <h2>
-      JUnit
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/test.png"  alt="test"><br>
-          </td>
-          <td valign="top">
-            test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testrun.png"  alt="currently running test"><br>
-          </td>
-          <td valign="top">
-            currently running test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testok.png"  alt="successful test"><br>
-          </td>
-          <td valign="top">
-            successful test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testfail.png"  alt="failing test"><br>
-          </td>
-          <td valign="top">
-            failing test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testerr.png"  alt="test throwing an exception"><br>
-          </td>
-          <td valign="top">
-            test throwing an exception<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/testignored.png"  alt="ignored test"><br>
-          </td>
-          <td valign="top">
-            ignored test<br>
-          </td>
-        </tr>        
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuite.png"  alt="test suite"><br>
-          </td>
-          <td valign="top">
-            test suite<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuiterun.png"  alt="currently running test suite"><br>
-          </td>
-          <td valign="top">
-            currently running test suite<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuiteok.png"  alt="successfully completed test suite"><br>
-          </td>
-          <td valign="top">
-            successfully completed test suite<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuitefail.png"  alt="test suite with failing test"><br>
-          </td>
-          <td valign="top">
-            test suite with failing test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/tsuiteerror.png"  alt="test suite with exception throwing test"><br>
-          </td>
-          <td valign="top">
-            test suite with exception throwing test<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/exc_catch.png"  alt="caught exception"><br>
-          </td>
-          <td valign="top">
-            caught exception<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.junit/obj16/stkfrm_obj.png"  alt="stack frame element"><br>
-          </td>
-          <td valign="top">
-            stack frame element<br>
-          </td>
-        </tr>        
-        
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      NLS tools
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/skip.png"  alt="skipped NLS key"><br>
-          </td>
-          <td valign="top">
-            skipped NLS key<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/translate.png"  alt="translated NLS key"><br>
-          </td>
-          <td valign="top">
-            translated NLS key<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/never_translate.png"  alt="untranslated NLS key"><br>
-          </td>
-          <td valign="top">
-            untranslated NLS key<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Quick fix
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/quickfix_error_obj.png"  alt="quick fixable error"><br>
-          </td>
-          <td valign="top">
-            quick fixable error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/quickfix_warning_obj.png"  alt="quick fixable warning"><br>
-          </td>
-          <td valign="top">
-            quick fixable warning<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center" rowspan="1" colspan="2">
-            <br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/add_correction.png"  alt="add"><br>
-          </td>
-          <td valign="top">
-            add<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_change.png"  alt="change"><br>
-          </td>
-          <td valign="top">
-            change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_cast.png"  alt="change cast"><br>
-          </td>
-          <td valign="top">
-            change cast<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_move.png"  alt="move to another package"><br>
-          </td>
-          <td valign="top">
-            move to another package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/remove_correction.png"  alt="remove"><br>
-          </td>
-          <td valign="top">
-            remove<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_delete_import.png"  alt="remove import"><br>
-          </td>
-          <td valign="top">
-            remove import<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_rename.png"  alt="rename"><br>
-          </td>
-          <td valign="top">
-            rename<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/correction_linked_rename.png"  alt="rename in file"><br>
-          </td>
-          <td valign="top">
-            rename in file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jexception_obj.png"  alt="surround with try/catch"><br>
-          </td>
-          <td valign="top">
-            surround with try/catch<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Refactoring
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/change.png"  alt="general change"><br>
-          </td>
-          <td valign="top">
-            general change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/composite_change.png"  alt="composite change"><br>
-          </td>
-          <td valign="top">
-            composite change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/text_edit.png"  alt="text change"><br>
-          </td>
-          <td valign="top">
-            text change<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/file_change.png"  alt="file change"><br>
-          </td>
-          <td valign="top">
-            file change
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/fatalerror_obj.png"  alt="Stop error">
-          </td>
-          <td valign="top">
-            Stop error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/error_obj.png"  alt="Error"><br>
-          </td>
-          <td valign="top">
-            Error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/warning_obj.png"  alt="Warning"><br>
-          </td>
-          <td valign="top">
-            Warning<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/obj16/info_obj.png"  alt="Information"><br>
-          </td>
-          <td valign="top">
-            Information<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ltk.ui.refactoring/elcl16/filter_ps.png"  alt="Information"><br>
-          </td>
-          <td valign="top">
-            Change filter<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Search
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/jsearch_obj.png"  alt="Java Search"><br>
-          </td>
-          <td valign="top">
-            Java Search<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/search_decl_obj.png"  alt="search for declarations"><br>
-          </td>
-          <td valign="top">
-            search for declarations<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/search_ref_obj.png"  alt="search for references"><br>
-          </td>
-          <td valign="top">
-            search for references<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-     
-    <h2>
-      Search - Occurrences in File
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/occ_match.png"  alt="general match"><br>
-          </td>
-          <td valign="top">
-            a general match<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/occ_read.png"  alt="read access to local or field"><br>
-          </td>
-          <td valign="top">
-            read access to local or field<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/occ_write.png"  alt="write access to local or field"><br>
-          </td>
-          <td valign="top">
-			write access to local or field          
-		  </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-    
-    <h2>
-      Type hierarchy view
-    </h2>
-    <table cellspacing="0" cellpadding="5" border="1" width="300">
-      <colgroup> <col width="25px"> </colgroup>
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/classfo_obj.png"  alt="type from non selected package"><br>
-          </td>
-          <td valign="top">
-            type from non selected package<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.jdt.ui/obj16/intf_obj.png"  alt="interface from non selected package"><br>
-          </td>
-          <td valign="top">
-            interface from non selected package<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-<!-- currently unused in org.eclipse.jdt.ui/obj16:
-brkpi_obj.png
-classf_generate.png
-externalize.png
-ignore.png
-internalize.png
-jsbook_obj.png - from debug
-no_breakpoint.png
--->
-
-<!-- calculated, cannot copy from plugin, must take a screen shot:
-error_gray_obj.png
-warning_gray_obj.png
--->
-
-<!-- unsure what to do:
-jworkingSet_obj.png
--->
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-breadcrumb.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-breadcrumb.htm
deleted file mode 100644
index 0141b73..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-breadcrumb.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Java Editor Breadcrumb</title>
-  </head>
-
-  <body>
-    <h1>Java Editor Breadcrumb</h1>
-
-    <p>
-      The Java editor breadcrumb navigation bar shows the element at the current cursor position and all its parent elements.
-      The breadcrumb is embedded into the editor and show at the top of the editor.
-    </p> 
-    <p><img src="images/ref-breadcrumb.png"  border="0" alt="The Java editor breadcrumb bar"></p>
-    <p>To enable the breadcrumb invoke <strong>Toggle Java Editor Breadcrumb</strong> in the toolbar or press 
-      <strong>Alt+Shift+B</strong> in the Java editor.
-    </p>
-    <p>
-      The breadcrumb allows to invoke actions on any element shown in the breadcrumb. Actions can be invoked through
-      a context menu or through key bindings. To select an element in the breadcrumb either click on it or press
-      <strong>Alt+Shift+B</strong> in the Java editor and then use the <strong>left</strong> and <strong>right</strong>
-      arrow keys.
-    </p>
-    <p>
-      With the breadcrumb it is also possible to navigate to other elements in the workspace: Click on one of the 
-      arrows or any element to open a drop down window. The drop down shows all siblings 
-      of the element for which the drop down was opened. To open an element click on it. To open the drop down with the keyboard, 
-      select an element and press the <strong>down</strong> arrow key.
-    </p>
-    <p>
-      The enablement of the breadcrumb is remembered for each perspective. The breadcrumb can for example be enabled
-      in the debug perspective and be disabled in the Java perspective.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../concepts/concept-java-editor.htm">Java Editor</a><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../concepts/concept-java-views-decorators.htm">Java element decorations</a><br>
-       <a href="../concepts/concept-java-views-presentation.htm">Presentation options for Java views</a>
-    </p>
-    <p><img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-    <p>
-     <a href="../reference/views/ref-java-editor.htm">Java editor actions</a><br>
-     <a href="../reference/views/ref-view-outline.htm">Java outline</a><br>
-     <a href="../reference/views/ref-viewsandeditors.htm">Views and editors</a>
-    </p>    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-code-assist.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-code-assist.htm
deleted file mode 100644
index 1238cfa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-code-assist.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Content/Code Assist
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Content/Code Assist
-    </h1>
-    <p>
-      In the Java editor press <b>Ctrl + Space</b> on code to complete. This opens a list of available code completions. Some tips for using code assist are listed in the following paragraph:
-    </p>
-    <ul>
-      <li>
-        You can use the mouse or the keyboard (Up Arrow, Down Arrow, Page Up, Page Down, Home, End, Enter) to navigate and select lines in the list.
-      </li>
-      <li>
-        If you select a line in the content assist list, you can view Javadoc information for that line.
-      </li>
-      <li>
-        Clicking or pressing Enter on a selected line in the list inserts the selection into the editor.
-      </li>
-      <li>
-        You can access specialized content assist features inside Javadoc comments.
-      </li>
-    </ul>
-    <img src="images/contentassist.png"  alt="An editor showing a content assist and Javadoc window at the caret position"> <p>
-     Configure the behavior of the content assist in the <a href="preferences/java/ref-preferences-editor.htm">Java &gt; Editor &gt; Code Assist</a> preference page.<br>
-     </p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-       <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/ref-menu-edit.htm">Edit menu</a><br>
-       <a href="../reference/preferences/java/ref-preferences-editor.htm">Java editor preferences</a><br>
-       <a href="../reference/preferences/java/editor/ref-preferences-templates.htm">Templates preferences</a><br>
-    </p>
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickassist.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickassist.htm
deleted file mode 100644
index 180de3c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickassist.htm
+++ /dev/null

@@ -1,443 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="content-type">
-  <link rel="stylesheet" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Quick Assist</title>
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Quick Assist</h1>
-
-<p>Quick assists perform local code transformations. They are invoked on a selection or a single cursor in the Java editor and
-use the same shortcut as quick fixes (<b>Ctrl+1</b>), but quick assist are usually hidden when an error is around.
-To show them even with errors present on the same line, press <b>Ctrl+1</b> a second time.<br>
-<br>
-A selection of quick assists can be assigned to a direct shortcut. By default, these are:</p><ul>
-	<li>Rename in file: <b>Ctrl+2, R</b></li>
-	<li>Assign to local: <b>Ctrl+2, L</b></li>
-	<li>Assign to field: <b>Ctrl+2, F</b></li>
-</ul>
-<p>Assign more shortcuts or change the default shortcuts on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens keys preference page">
-<b>General &gt; Keys</b></a> preference page (in the 'Source' category).
-<br>
-<br>
-A quick assist light bulb can be turned on on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens Java editor preference page">
-<b>Java &gt; Editor</b></a> preference page.
-<br>
-</p>
-<table style="width: 100%; text-align: left;" border="2" cellpadding="5" summary="List of quick assists">
-  <tbody>
-    <tr>
-      <th style="vertical-align: top;" width="15%">Name</th>
-      <th colspan="3" rowspan="1"
- style="vertical-align: top; text-align: center;">Code example</th>
-      <th style="vertical-align: top;" width="15%">Invocation location</th>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Inverse if statement</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (x) a(); else b();</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (!x) b(); else a();</code></td>
-      <td style="vertical-align: top;" width="15%">On 'if' statements with 'else'
-block</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Inverse boolean expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>a &amp;&amp;
-!b </code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>!a || b</code></td>
-      <td style="vertical-align: top;" width="15%">On a boolean expression</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Remove extra parentheses</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if ((a == b)
-&amp;&amp; (c != d)&nbsp; {}</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a == b &amp;&amp; c !=
-d)&nbsp; {}</code></td>
-      <td style="vertical-align: top;" width="15%">On selected expressions</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Add paranoidal parentheses</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a == b
-&amp;&amp; c != d)&nbsp; {}</code> </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if ((a == b) &amp;&amp; (c != d)</code></td>
-      <td style="vertical-align: top;" width="15%">On selected expressions</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Join nested if statements</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) { if
-(b) {} }</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a &amp;&amp; b) {}</code></td>
-      <td style="vertical-align: top;" width="15%">On a nested if statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Swap nested if statements</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) { if
-(b) {} }</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (b) { if (a) {} }</code></td>
-      <td style="vertical-align: top;" width="15%">On a nested if statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Split if statement with and'ed
-expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a
-&amp;&amp; b) {}</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a) { if (b) {} }</code></td>
-      <td style="vertical-align: top;" width="15%">On an and'ed expression in a 'if'</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Split if statement with or'd
-expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a || b)
-x();</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (a) x();&nbsp; if (b) x();</code></td>
-      <td style="vertical-align: top;" width="15%">On an or'd expression in a 'if'</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Inverse conditional expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>x ? b : c</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>!x ? c : b</code></td>
-      <td style="vertical-align: top;" width="15%">On a conditional expression</td>
-    </tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Pull negation up</td>
-			<td style="vertical-align: top; text-align: right" width="34%"><code>b &amp;&amp; c</code></td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%"><code>!(!b || !c)</code></td>
-			<td style="vertical-align: top" width="15%">On a boolean expression</td>
-		</tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Push negation down</td>
-			<td style="vertical-align: top; text-align: right" width="34%">!(<code>b
-			&amp;&amp; c)</code></td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%">!<code>b || !c</code></td>
-			<td style="vertical-align: top" width="15%">On a negated boolean expression</td>
-		</tr>
-		<tr>
-      <td style="vertical-align: top;" width="15%">If-else assignment to
-conditional expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) x= 1;
-else x= 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>x= a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;" width="15%">On an 'if' statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">If-else return to conditional
-expression</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) return
-1; <br>
-			else return 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>return a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;" width="15%">On an 'if' statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Conditional expression
-assignment to If-else</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>x= a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (a) x= 1; else x= 2;</code></td>
-      <td style="vertical-align: top;" width="15%">On a conditional expression</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Conditional expression return to
-If-else</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>return&nbsp;
-a ? 1 : 2;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a) return 1; else return 2;</code></td>
-      <td style="vertical-align: top;" width="15%">On a conditional expression</td>
-    </tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Switch to If-else</td>
-			<td style="vertical-align: top; text-align: right" width="34%"><code>switch (kind) {<br>case 1: return -1;<br>case 2: return -2;<br>}</code>
-			</td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%"><code>if (kind == 1) {<br>&nbsp;&nbsp;return  
-			-1;<br>} else if (kind == 2) {<br>&nbsp;&nbsp;return -2;<br>}</code>
-			</td>
-			<td style="vertical-align: top" width="15%">On a statement</td>
-		</tr>
-	<tr>
-      <td style="vertical-align: top;" width="15%">Add missing case statements on enums</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>switch (e){<br>}</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>switch (e){<br> case E1: break;<br>case E2: break;<br>}</code></td>
-      <td style="vertical-align: top" width="15%">On a switch statement</td>
-    </tr>		
-	<tr>
-      <td style="vertical-align: top;" width="15%">Exchange operands</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>a + b</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>b + a</code></td>
-      <td style="vertical-align: top;" width="15%">On an infix operation</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Cast and assign</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (obj
-instanceof Vector) {<br>
-			}</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (obj instanceof Vector) {<br>
-&nbsp;Vector vec= (Vector)obj;</code><br>
-}</td>
-      <td style="vertical-align: top;" width="15%">on a instanceof expression in an 'if' or 'while' statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Pick out string</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>"abcdefgh"</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>"abc" + "de" + "fgh"</code></td>
-      <td style="vertical-align: top;" width="15%">select a part of a string literal</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Convert string concatination to StringBuilder (J2SE 5.0) or StringBuffer</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>"Hello " + name</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>StringBuilder builder= new StringBuilder();<br>builder.append("Hello ");<br>builder.append(name);</code></td>
-      <td style="vertical-align: top;" width="15%">select a string literal</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Convert string concatination to MessageFormat</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>"Hello " + name</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>MessageFormat.format("Hello {0}", name);</code></td>
-      <td style="vertical-align: top;" width="15%">select a string literal</td>
-    </tr>        
-    
-    <tr>
-      <td style="vertical-align: top;" width="15%">Split variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>int i= 0;</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> int i; i= 0;</code></td>
-      <td style="vertical-align: top;" width="15%">On a variable with initialization</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Join variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>int i; i= 0;</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> int i= 0</code></td>
-      <td style="vertical-align: top;" width="15%">On a variable without
-initialization</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Assign to variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>foo()</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>X x= foo();</code></td>
-      <td style="vertical-align: top;" width="15%">On an expression statement</td>
-    </tr>
-		<tr>
-			<td style="vertical-align: top" width="15%">Extract to local</td>
-			<td style="vertical-align: top; text-align: right" width="34%"><code>foo(<u>getColor()</u>);</code></td>
-			<td style="vertical-align: top">&gt;</td>
-			<td style="vertical-align: top" width="34%"><code>Color color= getColor();<br>foo(color);</code>
-			</td>
-			<td style="vertical-align: top" width="15%">On an expression</td>
-		</tr>
-		<tr>
-      <td style="vertical-align: top;" width="15%">Assign parameter to field</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>public A(int
-color) {}</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>Color fColor;<br>
-public A(int color) {<br>
-&nbsp;&nbsp;&nbsp; fColor= color;<br>
-}</code></td>
-      <td style="vertical-align: top;" width="15%">On a parameter</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Add finally block</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>try {<br>
-} catch (Expression e) {<br>
-}
-      </code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>try {<br>
-} catch (Expression e) {<br>
-} finally {}</code></td>
-      <td style="vertical-align: top;" width="15%">On a try/catch statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Add else block</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>if (a) b();</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>if (a) b(); else { }</code></td>
-      <td style="vertical-align: top;" width="15%">On a if statement</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Replace statement with block</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>f (a) b();</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code> if (a) { b(); }</code></td>
-      <td style="vertical-align: top;" width="15%">On a if statement </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Invert equals</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>a.equals(b)</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>b.equals(a)</code></td>
-      <td style="vertical-align: top;" width="15%">On a invocation of 'equals'</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Array initializer to Array
-creation</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>int[]
-i=&nbsp; { 1, 2, 3 }</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>int[] i= new int[] { 1, 2, 3 }</code></td>
-      <td style="vertical-align: top;" width="15%">On an array initializer</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Convert to 'enhanced for loop'
-(J2SE 1.5)</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>for (Iterator
-i= c.iterator();i.hasNext();) {<br>
-}<br>
-      </code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>for (x : c) {<br>
-}</code></td>
-      <td style="vertical-align: top;" width="15%">On a for loop</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Create method in super class</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><br></td>
-      <td style="vertical-align: top;"><br></td>
-      <td style="vertical-align: top;" width="34%"><br></td>
-      <td style="vertical-align: top;" width="15%">On a method declaration</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Unwrap blocks</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>{ a() }</code></td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>a()</code></td>
-      <td style="vertical-align: top;" width="15%">On blocks, if/while/for statements</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Rename in file</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><br></td>
-      <td style="vertical-align: top;"><br>
-      </td>
-      <td style="vertical-align: top;" width="34%"><br>
-      </td>
-      <td style="vertical-align: top;" width="15%">On identifiers</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Rename in workspace</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><br></td>
-      <td style="vertical-align: top;"><br>
-      </td>
-      <td style="vertical-align: top;" width="34%"><br>
-      </td>
-      <td style="vertical-align: top;" width="15%">On identifiers</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Extract to local variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%">
-			<code>a= b*8;</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>int x= a*8;<br>a= x;</code>
-      </td>
-      <td style="vertical-align: top;" width="15%">On expressions</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Extract to constant</td>
-      <td style="vertical-align: top; text-align: right;" width="34%">
-			<code>a= 8;</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>final static int CONST= 8;<br>a= CONST;</code>
-      </td>
-      <td style="vertical-align: top;" width="15%">On expressions</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Extract method</td>
-      <td style="vertical-align: top; text-align: right;" width="34%">
-			<code>int x= p * 5;</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>int x= getFoo(p);</code>
-      </td>
-      <td style="vertical-align: top;" width="15%">On expressions and statements</td>
-    </tr>       
-    <tr>
-      <td style="vertical-align: top;" width="15%">Inline local variable</td>
-      <td style="vertical-align: top; text-align: right;" width="34%">
-			<code>int a= 8, b= a;</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>int b= 8;</code>
-      </td>
-      <td style="vertical-align: top;" width="15%">On local variables</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Convert local variable to field</td>
-      <td style="vertical-align: top; text-align: right;" width="34%">
-			<code>void foo() { int a= 8; }</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>int a= 8; void foo() {}</code>
-      </td>
-      <td style="vertical-align: top;" width="15%">On local variables</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Convert anonymous to nested class</td>
-      <td style="vertical-align: top; text-align: right;" width="34%">
-			<code>new Runnable() { };</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>class RunnableImplementation implements Runnable { }</code>
-      </td>
-      <td style="vertical-align: top;" width="15%">On anonymous classes</td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;" width="15%">Replace with getter and setter (Encapsulate Field)</td>
-      <td style="vertical-align: top; text-align: right;" width="34%"><code>p.x;</code>
-      </td>
-      <td style="vertical-align: top;">&gt;</td>
-      <td style="vertical-align: top;" width="34%"><code>p.getX();</code>
-      </td>
-      <td style="vertical-align: top;" width="15%">On fields</td>
-    </tr>        
-  </tbody>
-</table>
-
-<p><img src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-<p>
-	<a href="../concepts/concept-java-editor.htm">Java Editor</a><br>
-	<a href="../concepts/concept-quickfix-assist.htm">Quick Fix and Quick Assist</a>
-</p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-	<a href="ref-java-editor-quickfix.htm">Quick Fix</a><br>
-	<a href="../reference/ref-jdt-actions.htm">JDT actions</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm
deleted file mode 100644
index 2a19625..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-java-editor-quickfix.htm
+++ /dev/null

@@ -1,185 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-
-    <title>Quick Fix</title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>Quick Fix</h1>
-
-    <p>The Java editor offers corrections to problems found while typing and after compiling. To show that
-    correction proposals are available for a problem or warning, a 'light bulb' is visible on the editor's annotation bar.<br><br>
-Left click on the light bulb or invoking <b>Ctrl+1 (Edit &gt; Quick Fix)</b> brings up the proposals for the problem at the cursor position.<br>
-Each quick fix shows a preview when selected in the proposal window.<br></p>
-<br>
-<p><img src="images/c-quickfix.png"  border="0" alt="Quick fix selection dialog"></p>
-
-<p>
-Some selected quick fixes can also be assigned with direct shortcuts. You can configure these shortcuts on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens keys preference page">
-<b>General &gt; Keys</b></a> preference page (in the 'Source' category). <br></p>
-
-<p>Some quick fixes offer to fix all problems of the same kind in the current file at once. The information text in proposal window
-contains this information for all applicable proposals. To fix all problems of the same kind, press <b>Ctrl + Enter</b>.
-</p>
-
-
-<p>The following quick fixes are available:</p>
-<table border="0" cellpadding="10" cellspacing="0" width="700" summary="List if quick fixes">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="right"><b>Package Declaration</b></td>
-			<td width="80%" valign="top" align="left">
-			<ul>
-				<li>Add missing package declaration or correct package declaration</li>
-				<li>Move compilation unit to package that corresponds to the package declaration</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Imports</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Remove unused, unresolvable or non-visible import</li>
-				<li>Invoke 'Organize imports' on problems in imports</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Types</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Create new class, interface, enum, annotation or type variable for references to types that can not be resolved</li>
-				<li>Change visibility for types that are accessed but not visible</li>
-				<li>Rename to a similar type for references to types that can not be resolved</li>
-				<li>Add import statement for types that can not be resolved but	exist in the project</li>
-				<li>Add explicit import statement for ambiguous type references (two import-on-demands for the same type)</li>
-				<li>If the type name is not matching with the compilation unit name either rename the type or rename the compilation unit</li>
-				<li>Remove unused private types</li>
-				<li>Add missing type annotation attributes</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Constructors</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Create new constructor for references to constructors that can not be resolved (this, super or new class creation)</li>
-				<li>Reorder, add or remove arguments for constructor references that mismatch parameters</li>
-				<li>Change method with constructor name to constructor (remove return type)</li>
-				<li>Change visibility for constructors that are accessed but not visible</li>
-				<li>Remove unused private constructor</li>
-				<li>Create constructor when super call of the implicit default constructor is undefined, not visible or throws an exception</li>
-				<li>If type contains unimplemented methods, change type modifier to 'abstract' or add the method to implement</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Methods</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Create new method for references to methods that can not be resolved</li>
-				<li>Rename to a similar method for references to methods that can not be resolved</li>
-				<li>Reorder or remove arguments for method references that mismatch parameters</li>
-				<li>Correct access (visibility, static) of referenced methods</li>
-				<li>Remove unused private methods</li>
-				<li>Correct return type for methods that have a missing return type or where the return type does not match the return statement</li>
-				<li>Add return statement if missing</li>
-				<li>For non-abstract methods with no body change to 'abstract' or add body</li>
-				<li>For an abstract method in a non-abstract type remove abstract modifier of the method or make type abstract</li>
-				<li>For an abstract/native method with body remove the abstract or native modifier or remove body</li>
-				<li>Change method access to 'static' if method is invoked inside a constructor invocation (super, this)</li>
-				<li>Change method access to default access to avoid emulated method access</li>
-				<li>Add 'synchronized' modifier</li>
-				<li>Override hashCode()</li>
-				<li>Open the 'Generate hashCode() and equals()' wizard</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Fields and variables</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Correct access (visibility, static) of referenced fields</li>
-				<li>Create new fields, parameters,  local variables or constants for references to  variables that can not be resolved</li>
-				<li>Rename to a variable with similar name for references that can not be resolved</li>
-				<li>Remove unused private fields</li>
-				<li>Correct non-static access of static fields</li>
-				<li>Add 'final' modifier to  local variables accessed in outer types</li>
-				<li>Change field access to default access to avoid emulated method access</li>
-				<li>Change local variable type to fix a type mismatch</li>
-				<li>Initialize a variable that has not been initialized</li>
-				<li>Create getter and setters for invisible or unused fields</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Exception Handling</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Remove unneeded catch block</li>
-				<li>Handle uncaught exception by surrounding with try/catch or adding catch block to a surrounding try block</li>
-				<li>Handle uncaught exception by adding a throw declaration to the parent method or by generalize an existing throw declaration</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Build Path Problems</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Add a missing JAR or library for an unresolvable type</li>
-				<li>Open the build path dialog for access restriction problems or missing binary classes.</li>
-				<li>Change project compliance and JRE to 1.5</li>
-				<li>Change workspace compliance and JRE to 1.5</li>
-			</ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="right"><b>Others</b></td>
-			<td valign="top" align="left">
-			<ul>
-				<li>Add cast or change cast to fix type mismatches</li>
-				<li>Let a type implement an interface to fix type mismatches</li>
-				<li>Add type arguments to raw references</li>
-				<li>Complete switch statements over enums</li>
-				<li>Remove dead code</li>
-				<li>Insert '//$FALL-THROUGH$'</li>
-				<li>Insert null check</li>
-				
-				
-				<li>For non-NLS strings open the NLS wizard or mark as non-NLS</li>
-				<li>Add missing @Override, @Deprecated annotations</li>
-				<li>Add missing Javadoc comments</li>
-				<li>Add missing Javadoc tags</li>
-				<li>Suppress a warning using @SuppressWarnings</li>
-			</ul>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-
-
-<p>Quick Assists are proposals available even if there is no problem or warning. See the <a href='ref-java-editor-quickassist.htm'>Quick Assist</a> page for more information.</p>
-<p>
-	<img src="../images/ngrelc.png"  alt="Related concepts" border="0"></p>
-	<p>
-	<a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-    <a href="../concepts/concept-quickfix-assist.htm">Quick fix and assist</a><br>
-	</p>
-	<p><img src="../images/ngrelr.png"  alt="Related reference" border="0"></p>
-	<p>
-    <a href="ref-java-editor-quickassist.htm">Quick Assist</a><br>
-	<a href="ref-jdt-actions.htm">JDT actions</a>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-actions.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-actions.htm
deleted file mode 100644
index 3e42db9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-actions.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      JDT Actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      JDT Actions
-    </h1>
-    <p>
-      JDT actions are available from
-    </p>
-    <ul>
-      <li>
-        Menu bar
-      </li>
-      <li>
-        Toolbar
-      </li>
-      <li>
-        Context menus in views
-      </li>
-    </ul>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-jdt-faq.htm">Frequently asked questions on JDT</a><br>
-       <a href="ref-jdt-glossary.htm">JDT glossary</a><br>
-       <a href="../reference/ref-menu-file.htm">File menu actions</a><br>
-       <a href="../reference/ref-menu-edit.htm">Edit menu actions</a><br>
-       <a href="../reference/ref-menu-source.htm">Source menu actions</a><br>
-       <a href="../reference/ref-menu-refactor.htm">Refactor menu actions</a><br>
-       <a href="../reference/ref-menu-navigate.htm">Navigate menu actions</a><br>
-       <a href="../reference/ref-menu-search.htm">Search menu actions</a><br>
-       <a href="../reference/ref-menu-project.htm">Project menu actions</a><br>
-       <a href="menus/run/ref-menu-run.htm">Run menu actions</a><br>
-       <a href="../reference/ref-actions-toolbar.htm">Java toolbar actions</a><br>
-       <a href="../reference/ref-toolbar-run.htm">Run and debug toolbar actions</a><br>
-       <a href="../reference/views/ref-java-editor.htm">Java editor actions</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-faq.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-faq.htm
deleted file mode 100644
index 1f8027a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-faq.htm
+++ /dev/null

@@ -1,161 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Frequently Asked Questions on JDT
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Frequently Asked Questions on JDT
-    </h1>
-    <h3>
-      Can I use a Java compiler other than the built-in one (javac for example) with the workbench?
-    </h3>
-    <p>
-      No. The JDT provides a number of sophisticated features including fully automatic incremental compilation, code snippet evaluation, code assist, type hierarchies, and hot
-      code replace. These features require special support found in the workbench Java compiler (an integral part of the JDT's incremental project builder), but not available
-      in standard Java compilers.
-    </p>
-    <h3>
-      Where do Java packages come from?
-    </h3>
-    <p>
-      A project contains only files and folders. The notion of a Java package is introduced by a Java project's class path (at the UI, the Package Explorer presents the
-      packages as defined by the classpath). <strong>Tip:</strong> If the package structure is not what you expect, check out your class path. The Java search infrastructure only
-      finds declarations for and references from Java elements on the class path.
-    </p>
-    <h3>
-      When do I use an internal versus an external JAR library file?
-    </h3>
-    <p>
-      An internal resource resides in some project in the workbench and is therefore managed by the workbench; like other resources, these resources can be version managed by the
-      workbench. An external resource is not part of the workbench and can be used only by reference. For example, a JRE is often external and very large, and there is no need to
-      associate it with a VCM system.
-    </p>
-    <h3>
-      When should I use source folders within a Java project?
-    </h3>
-    <p>
-      Each Java project locates its Java source files via one or more source type entries on the project's class path. Use source folders to organize the packages of a large
-      project into useful grouping, or to keep source code separate from other files in the same project. Also, use source folders if you have files (documentation for example)
-      which need not be on the build path.
-    </p>
-    <h3>
-      What are source attachments, How do I define one?
-    </h3>
-    <p>
-      Libraries are stored as JAR files containing binary class files (and perhaps other resources). These binary class files provide signature information for packages, classes,
-      methods, and fields. This information is sufficient to compile or run against, but contains far less information that the original source code. In order to make it easier to
-      browse and debug binary libraries, there is a mechanism for associating a corresponding source JAR (or ZIP) file with a binary JAR file.
-    </p>
-    <h3>
-      Why are all my resources duplicated in the output folder (bin, for example)?
-    </h3>
-    <p>
-      If your Java project is using source folders, then in the course of compiling the source files in the project, the Java compiler copies non-Java resources to the output
-      folder as well so that they will be available on the class path of the running program. To avoid certain resources to be copied to the output location you can set a resource
-      filter in the Java compiler preferences: <strong>Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong>
-    </p>
-    <h3>
-      How do I prevent having my documentation files from being copied to the project's output folder?
-    </h3>
-    <p>
-      Use source folders and put any resources that you do not want to be copied to the output folder into a separate folder that is not included on the class path.You can also
-      set a resource filter in the Java compiler preferences:<strong> Window &gt; Preferences &gt; Java &gt; Compiler &gt; Building</strong> to for example *.doc.
-    </p>
-    <h3>
-      How do I create a default package?
-    </h3>
-    <p>
-      You don't have to. Files in the root folder of a source folder or project are considered to be in the default package. In effect, every source folder has the capability
-      of having a fragment of the default package.
-    </p>
-    <h3>
-      What is refactoring?
-    </h3>
-    <p>
-      Refactoring means behavior-preserving program transformations. The JDT supports a number of transformations described in Martin Fowler's book <em>Refactoring: Improving
-      the Design of Existing Code</em>, Addison-Wisely 1999.
-    </p>
-    <h3>
-      When do I use Open Declaration (F3)?
-    </h3>
-    <p>
-      To find out the Java element that corresponds to the selected source range with the help of the compiler.
-    </p>
-    <h3>
-      Is the Java program information (type hierarchy, declarations, references, for example) produced by the Java builder? Is it still updated when auto-build is off?
-    </h3>
-    <p>
-      The Java program information is independent from the Java builder. It is automatically updated when performing resource changes or Java operations. In particular, all the
-      functionality offered by the Java tooling (for example, type hierarchies, code assisting, search) will continue to perform accurately when auto-build is off; for example,
-      when doing heavy refactoring which require to turn off the builders, you can still use code assist, which will reflect the latest changes (not yet build). Other than the
-      launching (that is, running and debugging) of programs, the only functionality which requires the Java builder is the evaluation of code snippets.
-    </p>
-    <h3>
-      After reopening a workbench, the first build that happens after editing a Java source file seems to take a long time. Why is that?
-    </h3>
-    <p>
-      The Java incremental project builder saves its internal state to a file when the workbench is closed. On the first build after the project is reopened, the Java incremental
-      project builder will restore its internal state. When this file is large, the user experiences an unusually long build delay.
-    </p>
-    <h3>
-      I can't see a type hierarchy for my class. What can I do?
-    </h3>
-    <p>
-      Check that you have your build class path set up properly. Setting up the proper build class path is an important task when doing Java development. Without the correct build
-      path, you will not be able to compile your code. In addition, you will not be able to search or look at the type hierarchies for Java elements.
-    </p>
-    <h3>
-      How do I turn off &quot;auto compile&quot; and do it manually when I want?
-    </h3>
-    
-<p> Clear the <strong>Build automatically</strong> checkbox on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Workspace preference page">
-<strong>General &gt; Workspace</strong></a> preference page.
-When you want to build, press <kbd>Ctrl+B</kbd>, 
-  or select <strong>Project &gt; Build All</strong> from the menu bar. </p>
-<p><b>Hint</b>: when you turn &quot;auto compile&quot; off and build manually, 
-  you may also want to select the
-  <strong>Save automatically before build</strong> checkbox on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Workspace preference page">
-  <strong>General &gt; Workspace</strong></a> preference page.
-</p>
-<h3>When I select a method or a field in the Outline view, only the source for 
-  that element is shown in the editor. What do I do to see the source of the whole 
-  file?</h3>
-<p>There is a toolbar button <b>Show Source of Selected Element Only</b> - all 
-  you have to do is un-press it.</p>
-<h3>Can I nest source folders?</h3>
-<p>Yes, you can use exclusion filters to create nested source folders.</p>
-<h3>Can I have separate output folders for each source folder?</h3>
-<p>Yes, select the <b>Allow output folders for source folders</b> checkbox in 
-  the <b>Java Build Path &gt; Source</b> property page of your Java project.</p>
-<h3>Can I have an output or source folder that is located outside of the workspace?</h3>
-<p>Yes, you can create a linked folder that points to the desired location and 
-  use that folder as the source or output folder in your Java project.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-properties-build-path.htm">Java build path page</a><br>
-       <a href="../reference/ref-jdt-glossary.htm">JDT glossary</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-glossary.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-glossary.htm
deleted file mode 100644
index 514bc09..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-jdt-glossary.htm
+++ /dev/null

@@ -1,153 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      JDT Glossary
-    </title>
-  </head>
-  <body>
-    <h1>
-      JDT Glossary
-    </h1>
-    <p>
-      <strong>CLASS file</strong>
-    </p>
-    <p>
-      A compiled Java source file.
-    </p>
-    <p>
-      <strong>compilation unit</strong>
-    </p>
-    <p>
-      A Java source file.
-    </p>
-    <p>
-      <strong>field</strong>
-    </p>
-    <p>
-      A field inside a type.
-    </p>
-    <p>
-      <strong>import container</strong>
-    </p>
-    <p>
-      Represents a collection of import declarations. These can be seen in the Outline view.
-    </p>
-    <p>
-      <strong>import declaration</strong>
-    </p>
-    <p>
-      A single package import declaration.
-    </p>
-    <p>
-      <strong>initializer</strong>
-    </p>
-    <p>
-      A static or instance initializer inside a type.
-    </p>
-    <p>
-      <strong>JAR file</strong>
-    </p>
-    <p>
-      JAR (Java archive) files are containers for compiled Java source files. They can be associated with an archive (such as, ZIP, JAR) as a source attachment. The children of
-      JAR files are packages. JAR files can be either compressed or uncompressed.
-    </p>
-    <p>
-      <strong>JAVA elements</strong>
-    </p>
-    <p>
-      Java elements are Java projects, packages, compilation units, class files, types, methods and fields.
-    </p>
-    <strong>JAVA file</strong><br>
-     <br>
-     
-    <p>
-      An editable file that is compiled into a byte code (CLASS) file.
-    </p>
-    <p>
-      <strong>Java projects</strong>
-    </p>
-    <p>
-      Projects which contain compilable Java source code and are the containers for source folders or packages.
-    </p>
-    <p>
-      <strong>JDT</strong>
-    </p>
-    <p>
-      Java development tools. Workbench components that allow you to write, edit, execute, and debug Java code.
-    </p>
-    <p>
-      <strong>JRE</strong>
-    </p>
-    <p>
-      Java runtime environment (for example, J9, JDK, and so on).
-    </p>
-    <p>
-      <strong>method</strong>
-    </p>
-    <p>
-      A method or constructor inside a type.
-    </p>
-    <p>
-      <strong>package declaration</strong>
-    </p>
-    <p>
-      The declaration of a package inside a compilation unit.
-    </p>
-    <p>
-      <strong>packages</strong>
-    </p>
-    <p>
-      A group of types that contain Java compilation units and CLASS files.
-    </p>
-    <p>
-      <strong>refactoring</strong>
-    </p>
-    <p>
-      A comprehensive code editing feature that helps you improve, stabilize, and maintain your Java code. It allows you to make a system-wide coding change without affecting the
-      semantic behavior of the system.
-    </p>
-    <p>
-      <strong>type</strong>
-    </p>
-    <p>
-      A type inside a compilation unit or CLASS file.
-    </p>
-    <p>
-      <strong>source folder</strong>
-    </p>
-    <p>
-      A folder that contains Java packages.
-    </p>
-    <p>
-      <strong>VCM</strong>
-    </p>
-    <p>
-      Version control management. This term refers to the various repository and versioning features in the workbench.
-    </p>
-    <p>
-      <strong>VM</strong>
-    </p>
-    <p>
-      Virtual machine.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/ref-jdt-faq.htm">Frequently asked questions on JDT</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-keybindings.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-keybindings.htm
deleted file mode 100644
index 651a7a1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-keybindings.htm
+++ /dev/null

@@ -1,237 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-List of JDT key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-
-<style type="text/css">
-<!--
-table tr td { padding: 3pt; }
--->
-</style>
-
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>List of JDT key bindings</h1>
-<p>The list of available key bindings in Eclipse depends on many factors, including
-what view or editor is selected, whether a dialog is open, what plug-ins are
-installed, and what operating and windowing system is being used.  At any
-time, you can obtain a list of available key bindings using Key Assist 
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.showKeyAssist")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help &gt; Key Assist...</b></a>
-or Ctrl+Shift+L).  The following tables list some 
-popular key bindings available in the Java development tools.</p>
-
-<h3><strong>Java editor actions</strong></h3>
-<table width="75%" border="1">
-  <colgroup>
-    <col width="126pt">
-    <col width="110pt">
-  </colgroup>
-  <tr><td>Add Block Comment</td>
-    <td>Ctrl+Shift+/</td>
-  </tr>
-  <tr>
-    <td>Add Import</td>
-    <td>Ctrl+Shift+M</td>
-  </tr>
-  <tr>
-    <td>Content Assist</td>
-    <td>Ctrl+Space</td>
-  </tr>
-  <tr>
-    <td>Content Assist (Simplified Chinese)</td>
-    <td>Alt+/</td>
-  </tr>
-  <tr>
-    <td>Expand Selection to Enclosing Element</td>
-    <td>Alt+Shift+Up Arrow</td>
-  </tr>
-	<tr>
-    <td>Expand Selection: Restore Last Selection</td>
-    <td>Alt+Shift+Down Arrow</td>
-  </tr>
-	<tr>
-    <td>Expand Selection to Next Element</td>
-    <td>Alt+Shift+Right Arrow</td>
-  </tr>
-	<tr>
-    <td>Expand Selection to Previous  Element</td>
-    <td>Alt+Shift+Left Arrow</td>
-  </tr>
-	<tr>
-    <td>Format</td>
-    <td>Ctrl+Shift+F</td>
-  </tr>
-	<tr>
-    <td>Next</td>
-    <td>Ctrl+. (Period)</td>
-  </tr>
-  	<tr>
-    <td>Open External Javadoc</td>
-    <td>Shift+F2</td>
-  </tr>
-	<tr>
-    <td>Open on Selection</td>
-    <td>F3</td>
-  </tr>
-	<tr>
-    <td>Open Type</td>
-    <td>Ctrl+Shift+T</td>
-  </tr>
-	<tr>
-    <td>Open Type Hierarchy</td>
-    <td>F4</td>
-  </tr>
-	<tr>
-    <td>Open Type in Hierarchy</td>
-    <td>Ctrl+Shift+H</td>
-  </tr>
-	<tr>
-    <td>Organize Imports</td>
-    <td>Ctrl+Shift+O</td>
-  </tr>
-	<tr>
-    <td>Parameter Hints</td>
-    <td>Ctrl+Shift+Space</td>
-  </tr>
-	<tr>
-    <td>Parameter Hints (Simplified Chinese)</td>
-    <td>Alt+?</td>
-  </tr>
-	<tr>
-    <td>Previous</td>
-    <td>Ctrl+, (Comma)</td>
-  </tr>
-	<tr>
-    <td>Quick Assist</td>
-    <td>Ctrl+1</td>
-  </tr>
-	<tr>
-    <td>Quick Fix</td>
-    <td>Ctrl+1</td>
-  </tr>
-	<tr>
-    <td>Redo</td>
-    <td>Ctrl+Y</td>
-  </tr>
-  <tr>
-    <td>Remove Block Comment</td>
-    <td>Ctrl+Shift+\</td>
-  </tr>
-	<tr>
-    <td>Search for Declarations in Workspace</td>
-    <td>Ctrl+G</td>
-  </tr>
-	<tr>
-    <td>Search for References in Workspace</td>
-    <td>Ctrl+Shift+G</td>
-  </tr>
-	<tr>
-    <td>Shift Right</td>
-    <td>Tab</td>
-  </tr>
-	<tr>
-    <td>Shift Left</td>
-    <td>Shift+Tab</td>
-  </tr>
-	<tr>
-    <td>Show Tooltip Description</td>
-    <td>F2</td>
-  </tr>
-  <tr>
-    <td>Toggle Comment</td>
-    <td>Ctrl+/</td>
-  </tr>
-  <tr>
-    <td>Undo</td>
-    <td>Ctrl+Z</td>
-  </tr>
-</table>
-
-<h3><strong>Debug actions</strong></h3>
-<table width="75%" border="1">
-  <colgroup>
-    <col width="126pt">
-    <col width="110pt">
-  </colgroup>
-  <tr> 
-    <td>Debug Last Launched</td>
-    <td>F11</td>
-  </tr>
-  <tr>
-    <td>Display</td>
-    <td>Ctrl+Shift+D</td>
-  </tr>
-  <tr>
-    <td>Inspect</td>
-    <td>Ctrl+Shift+I</td>
-  </tr>
-  <tr>
-    <td>Resume</td>
-    <td>F8</td>
-  </tr>
-	<tr>
-    <td>Run Last Launched</td>
-    <td>Ctrl+F11</td>
-  </tr>
-  <tr>
-    <td>Run Snippet</td>
-    <td>Ctrl+U</td>
-  </tr>
-  <tr>
-    <td>Run to Line</td>
-    <td>Ctrl+R</td>
-  </tr>
-	<tr>
-    <td>Run to Return</td>
-    <td>F7</td>
-  </tr>
-  <tr>
-    <td>Step Into</td>
-    <td>F5</td>
-  </tr>
-  <tr>
-    <td>Step into Selection</td>
-    <td>Ctrl+F5</td>
-  </tr>
-  <tr>
-    <td>Step Over</td>
-    <td>F6</td>
-  </tr>
-  <tr>
-    <td>Toggle Breakpoint</td>
-    <td>Ctrl+Shift+B</td>
-  </tr>
-</table>
-  
-<p>
-  <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-</p>
-<p>
-<a href="../../org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm">
-Navigating the user interface using the keyboard</a><br>
-<a href="../../org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm">
-Keys and accessibility for the workbench</a><br></p>
-
-<p>
-  <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-</p>
-<p>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-keybindings.htm">
-List of key bindings</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm
deleted file mode 100644
index 260d312..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-edit.htm
+++ /dev/null

@@ -1,362 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Edit actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Edit actions
-    </h1>
-	<p>
-        Edit menu commands shown when a Java editor is visible:
-	</p>     
-    <table border="1" cellspacing="0" cellpadding="5" summary="Edit actions">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Undo
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Revert the last change in the editor
-            </p>
-          </td>
-          <td>
-            Ctrl + Z
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Redo&nbsp;
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Revert an undone change
-            </p>
-          </td>
-          <td>
-            Ctrl + Y
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Cut
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Copies the currently selected text or element to the clipboard and removes the element. On elements, the remove is not performed before the clipboard is pasted.
-            </p>
-          </td>
-          <td>
-            Ctrl + X
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Copy
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Copies the currently selected text or elements to the clipboard
-            </p>
-          </td>
-          <td>
-            Ctrl + C
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Copy Qualified Name
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Copies the fully qualified name of the currently selected element to the clipboard
-            </p>
-          </td>
-          <td>
-            &nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Paste
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Paste the current content as text to the editor, or as a sibling or child element to the a currently selected element.&nbsp;
-            </p>
-          </td>
-          <td>
-            Ctrl + V
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Delete
-          </td>
-          <td>
-            Delete the current text or element selection.
-          </td>
-          <td>
-            Delete
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Select All
-          </td>
-          <td>
-            Select all the editor content.
-          </td>
-          <td>
-            Ctrl + A
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Expand Selection To
-          </td>
-          <td>
-            <ul>
-              <li>
-                Enclosing Element: Selects the enclosing expression, block, or method in the code. This action is aware of the Java syntax. It may not function properly when the code
-                has syntax errors. (Arrow Up)
-              </li>
-              <li>
-                Next Element: Selects the current and next elements. (Arrow Right)
-              </li>
-              <li>
-                Previous Element: Selects the current and previous elements. (Arrow Left)
-              </li>
-              <li>
-                Restore Last Selection: Restores the previous selection after an invocation of&nbsp;<em>Expand Selection To</em>. (Arrow Down)
-              </li>
-            </ul>
-          </td>
-          <td>
-            Alt + Shift + Arrow Keys
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Find / Replace
-          </td>
-          <td>
-            Open the Find / Replace dialog. Editor only.
-          </td>
-          <td>
-            Ctrl + F
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Find Next
-          </td>
-          <td>
-            Finds the next occurrence of the currently selected text. Editor only.
-          </td>
-          <td>
-            Ctrl + K
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Find Previous
-          </td>
-          <td>
-            Finds the previous occurrence of the currently selected text. Editor only.
-          </td>
-          <td>
-            Ctrl + Shift + K
-          </td>
-        </tr>
-        
-        <tr>
-          <td>
-            Incremental Find Next
-          </td>
-          <td>
-            Starts the incremental find mode. After invocation, enter the search text as instructed in the status bar. Editor only.
-          </td>
-          <td>
-            Ctrl + J
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Incremental Find Previous
-          </td>
-          <td>
-            Starts the incremental find mode. After invocation, enter the search text as instructed in the status bar. Editor only.
-          </td>
-          <td>
-            Ctrl + Shift + J
-          </td>
-        </tr>
-        
-        <tr align="left" valign="top">
-          <td>
-            Add Bookmark
-          </td>
-          <td>
-            Add a bookmark to the current text selection or selected element.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Add Task
-          </td>
-          <td>
-            Add a user defined task to the current text selection or selected element.
-          </td>
-          <td>&nbsp;
-          
-          </td>
-        </tr>
-        
-		<tr>
-          <td>
-            Smart Insert Mode
-          </td>
-          <td>
-			  Toggles the Insert Mode. When smart insert mode is disabled, typing aids like 
-			  automatic indentation, closing of brackets etc. are disabled.
-          </td>
-          <td>
-            Ctrl + Shift + Insert
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Show Tooltip Description
-          </td>
-          <td>
-            Shows the value of a hover that would appear at the current cursor location. The dialog shown is scrollable and does not shorten descriptions.
-          </td>
-          <td>
-            F2
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Content Assist
-          </td>
-          <td>
-            Opens a content assist dialog at the current cursor position.
-            By default content assist supports five different categories of 
-            proposals.
-            <ol>
-            <li>Default - union all of proposals</li>
-            <li>Type Proposals <i>(e.g. java.lang.String, List)</i></li>
-            <li>Other Java Proposals <i>(e.g. method or field names)</i></li>
-            <li>Template Proposals <i>(e.g. 'iterate over array' template)</i></li>
-            <li>Word Proposals <i>(Proposes words which have been typed already)</i></li>
-            </ol>
-            <p>
-            See the <a href="preferences/java/ref-preferences-editor.htm">Java Editor preference page</a>
-            for configuring the behavior of code assist and the contents of the <em>Default</em> proposal category.
-            </p><p>
-            See the <a href="preferences/java/editor/ref-preferences-templates.htm">Templates preference page</a> 
-            for available templates.</p>
-          </td>
-          <td>
-            Ctrl + Space
-          </td>
-        </tr>
-		  <!--tr>
-          <td>
-            Parameter Hints
-          </td>
-          <td>
-            Shows parameter type information if the cursor is within the argument list of a method call. The parameter information for the argument at the
-            cursor location is shown in bold.
-          </td>
-          <td>
-            Ctrl + Shift + Space
-          </td>
-        </tr -->
-		<tr>
-          <td>Word Completion</td>
-          <td>Proposes word completions for the current string based on all words
-          found in any open editor. Works in all text based editors.</td>
-          <td>Alt + /</td>
-        </tr>
-        <tr>
-          <td>
-            Quick Fix
-          </td>
-          <td>
-            Opens a dialog with possible solutions if the cursor is located near a problem indication.
-          </td>
-          <td>
-            Ctrl + 1
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Set Encoding
-          </td>
-          <td>
-            Toggles the encoding of the currently shown text content.
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-       <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-      </p>
-      <p>
-      <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-      <p>
-      <a href="views/ref-java-editor.htm">Java editor</a><br>
-       <a href="preferences/java/ref-preferences-editor.htm">Java editor preferences</a><br>
-       <a href="views/ref-view-outline.htm">Java outline</a><br>
-       <a href="views/ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm
deleted file mode 100644
index 04e451e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-file.htm
+++ /dev/null

@@ -1,310 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      File actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      File actions
-    </h1>
-    <p>
-        File menu commands:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="File actions">
-      <caption>
-      </caption>
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              New
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Create a Java element or a new resource. Configure which elements are shown in the submenu in <strong>Window &gt; Customize Perspective</strong>. In a Java perspective, by default
-              action for creating a <a href="ref-wizard-java-project.htm">project</a>, <a href="ref-wizard-package.htm">package</a>, <a href="ref-wizard-class.htm">class</a>, <a href="ref-wizard-interface.htm">interface</a>, <a href="ref-wizard-enum.htm">enum</a>, <a href="ref-wizard-annotation.htm">annotation</a>, <a href="ref-wizard-source-folder.htm">source
-              folder</a>, Java working set, JUnit test, file and folder are available.
-            </p>
-          </td>
-          <td>
-            Alt + Shift + N
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Open File
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Opens a file from the file system in an editor.
-            </p>
-          </td>
-          <td>&nbsp;
-          
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Close&nbsp;
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Close the current editor. If the editor contains unsaved data, a save request dialog will be shown.
-            </p>
-          </td>
-          <td>
-            Ctrl + W
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Close All
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Close all editors. If editors contains unsaved data, a save request dialog will be shown.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + W
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Save
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Save the content of the current editor. Disabled if the editor does not contain unsaved changes.
-            </p>
-          </td>
-          <td>
-            Ctrl + S
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Save As
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Save the content of the current editor under a new name.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Save All
-          </td>
-          <td>
-            Save the content of all editors with unsaved changes. Disabled if no editor contains unsaved changes.
-          </td>
-          <td>
-            Ctrl + Shift + S
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Revert
-          </td>
-          <td>
-            Revert the content of the current editor back to the content of the saved file. Disabled if the editor does not contain unsaved changes.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Move
-          </td>
-          <td>
-            Move a resource. Disabled on Java Elements. To move Java elements use <strong>Refactor &gt; Move</strong> (with updating all references to the file) or <strong><a href=
-            "ref-menu-edit.htm">Edit</a> &gt; Cut / Paste</strong> (no updating of references).
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Rename
-          </td>
-          <td>
-            Renames a resource. Disabled on Java Elements. To rename Java elements use <strong>Refactor &gt; Rename</strong> (with updating all references to the file).
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Refresh
-          </td>
-          <td>
-            Refreshes the content of the selected element with the local file system. When launched from no specific selection, this command refreshes all projects.
-          </td>
-          <td>
-            F5
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Convert Line Delimiters To
-          </td>
-          <td>
-            Convert the line delimiters of all the text files in the selection to the selected delimiter kind.
-          </td>
-          <td>&nbsp;
-          
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Print
-          </td>
-          <td>
-            Prints the content of the current editor. Enabled when an editor has the focus.
-          </td>
-          <td>
-            Ctrl + P
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Switch Workspace
-          </td>
-          <td>
-            Switch to another workspace.
-          </td>
-          <td>&nbsp;
-          
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Restart
-          </td>
-          <td>
-            Restarts the application.
-          </td>
-          <td>&nbsp;
-          
-          </td>
-        </tr>        
-        <tr>
-          <td>
-            Import
-          </td>
-          <td>
-            Opens the import wizard dialog. JDT does not contribute any import wizards.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Export
-          </td>
-          <td>
-            Opens the export wizard dialog. JDT contributes the <a href="ref-export-jar.htm">JAR file export wizard</a> and the <a href=
-            "ref-export-javadoc.htm">Javadoc generation wizard</a>.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Properties
-          </td>
-          <td>
-            Opens the property pages of the select elements. Opened on Java projects the <a href="ref-properties-build-path.htm">Java Build Path</a> page and the <a href=
-            "ref-dialog-javadoc-location.htm">Javadoc Location page</a> are available. For JAR archives, configure the JAR's <a href="ref-properties-source-attachment.htm">Source Attachment</a> and <a
-            href="ref-dialog-javadoc-location.htm">Javadoc Location</a> here.
-          </td>
-          <td>
-            Alt + Enter
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Exit
-          </td>
-          <td>
-            Exit Eclipse
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-      </p>
-      <p>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-      </p>
-      <p>
-       <a href="../tasks/tasks-32.htm">Creating JAR files</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-      <p>
-      <a href="ref-wizard-java-project.htm">New Java project wizard</a><br>
-	  <a href="ref-wizard-package.htm">New Java package wizard</a><br> 
-	  <a href="ref-wizard-class.htm">New Java class wizard</a><br>
-	  <a href="ref-wizard-enum.htm">New Java enum wizard</a><br>
-	  <a href="ref-wizard-interface.htm">New Java interface wizard</a><br>
-	  <a href="ref-wizard-annotation.htm">New Java annotation wizard</a><br>
-	  <a href="ref-export-jar.htm">JAR file exporter</a><br>
-	  <a href="ref-export-javadoc.htm">Javadoc generation</a><br>
-	  <a href="ref-dialog-javadoc-location.htm">Javadoc location properties</a><br>
-	  <a href="ref-properties-build-path.htm">Java build path properties</a><br>
-	  <a href="ref-properties-source-attachment.htm">Source attachment properties</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm
deleted file mode 100644
index bc380c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-navigate.htm
+++ /dev/null

@@ -1,335 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Navigate Actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Navigate Actions
-    </h1>
-	<p>
-        Navigate menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Navigate menu commands">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Go Into
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Sets the view input to the currently selected element. Supported by the <a href="views/ref-view-package-explorer.htm">Package Explorer</a> view.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Go To
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <ul>
-              <li>
-                Back: Sets the view input to the input back in history: Only enabled when a history exists (<strong>Go Into</strong> was used)
-              </li>
-              <li>
-                Forward: Sets the view input to the input forward in history: Only enabled when a history exists (<strong>Go Into</strong>,&nbsp; <strong>Go To &gt; Back</strong>
-                were used)
-              </li>
-              <li>
-                Up One Level: Sets the input of the current view to its input's parent element
-              </li>
-              <li>
-                Type: Browse for a type and reveal it in the current view. Supported by the Package Explorer view
-              </li>
-              <li>
-                Package: Browse for a package and reveal it in the current view. Supported by the Package Explorer view
-              </li>
-              <li>
-                Resource: Browse for a resource and reveal it in the current view.
-              </li>
-            </ul>
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Open Declaration
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Tries to resolve the element referenced at the current code selection and opens the file declaring the reference.&nbsp;
-            </p>
-          </td>
-          <td>
-            F3
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Open Type Hierarchy
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Tries to resolve the element referenced at the current code selection and opens the element in the <a href="views/ref-type-hierarchy.htm">Type Hierarchy</a> view. Invoked
-              on elements, opens the type hierarchy of the element. Supported in the Java editor and views showing Java elements.
-            </p>
-          </td>
-          <td>
-            F4
-          </td>
-        </tr>
-		<tr>
-          <td align="left" valign="top">
-            <p>
-              Open Call Hierarchy
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-				Tries to resolve the method referenced at the current code selection and opens the element in the <a href="views/ref-call-hierarchy.htm">Call Hierarchy</a> view.
-			</p>
-          </td>
-          <td>
-            Ctrl + Alt + H
-          </td>
-        </tr>
-		  
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Open Super Implementation
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Open an editor for the super implementation of the currently selected method or method surrounding the current cursor position. No editor is opened if no method is
-              selected or the method has no super implementation.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Open External Javadoc
-          </td>
-          <td>
-            Opens the Javadoc documentation of the currently selected element or text selection. The location of the Javadoc of a JAR or a project is specified in the <a href=
-            "ref-dialog-javadoc-location.htm">Javadoc location property page</a> on projects or JARs. Note that this external Javadoc documentation may not be up to date with the
-            Javadoc specified in the current code. You can create Javadoc documentation for source files in a Java project using the <a href="ref-export-javadoc.htm">Javadoc
-            export wizard</a>.&nbsp;
-          </td>
-          <td>
-            Shift + F2
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Open Type
-          </td>
-          <td>
-            Brings up the <a href="ref-dialog-open-type.htm">Open Type</a> dialog to open a type in the editor. The Open Type selection dialog shows all types existing in the workspace.
-          </td>
-          <td>
-            Ctrl + Shift + T
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Open Type In Hierarchy
-          </td>
-          <td>
-            Brings up the Open Type dialog to open a type in the editor and the <a href="views/ref-type-hierarchy.htm">Type Hierarchy</a> view. The Open Type selection dialog
-            shows all types that exist in the workspace.
-          </td>
-          <td>
-            Ctrl + Shift + H
-          </td>
-        </tr>
-		<tr>
-          <td align="left" valign="top">
-            <p>
-              Open Resource
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>Opens the Open Resource dialog to open any resource in your workspace.</p>
-          </td>
-          <td>
-            Ctrl + Shift + R
-          </td>
-        </tr>
-		<tr>
-          <td align="left" valign="top">
-            <p>
-              Show In Breadcrumb
-            </p>
-          </td>
-          <td align="left" valign="top">
-            Shows the currently selected element in the breadcrub bar of the Java editor.
-          </td>
-          <td>
-            Ctrl + Shift + B
-          </td>
-        </tr>        
-        <tr align="left" valign="top">
-          <td>Show In</td>
-          <td>
-			  Choose to show the currently selected element in 
-			  <ul>
-				  <li>Package Explorer</li>
-				  <li>History</li>
-				  <li>Navigator</li>
-				  <li>Outline</li>
-			  </ul>
-		  </td>
-          <td>Alt + Shift + W</td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Quick Outline
-          </td>
-          <td>
-            Opens the lightweight outliner for the currently selected type.
-          </td>
-          <td>Ctrl + O
-          </td>
-        </tr>
-	   <tr align="left" valign="top">
-          <td>
-            Quick Type Hierarchy
-          </td>
-          <td>
-            Opens the lightweight hierarchy viewer for the currently selected type.
-          </td>
-          <td>Ctrl + T
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Next / Next Annotation / <a href="views/debug/ref-nextthread.htm">Next Thread</a>
-          </td>
-          <td>
-            Selects the next annotation in the Java editor.  Selects the next suspended thread in the <a href="views/debug/ref-debug_view.htm">Debug View</a>.
-          </td>
-          <td>
-            Ctrl + .
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Previous / Previous Annotation / <a href="views/debug/ref-previousthread.htm">Previous Thread</a>
-          </td>
-          <td>
-            Selects the previous annotation in the java editor. Selects the previous suspended thread in the <a href="views/debug/ref-debug_view.htm">Debug View</a>.
-          </td>
-          <td>
-            Ctrl + ,
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Last Edit Location
-          </td>
-          <td>
-            Reveals the location where the last edit occurred.
-          </td>
-          <td>
-            Ctrl + Q
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Go to Line
-          </td>
-          <td>
-            Opens an a dialog which allows entering the line number to which the editor should jump to. Editor only.
-          </td>
-          <td>
-            Ctrl + L
-          </td>
-        </tr>
-		<tr>
-          <td>
-			  Back
-          </td>
-          <td>Reveals the previous editor location in the location history.</td>
-          <td>
-            Alt + Left
-          </td>
-        </tr>
-		<tr>
-          <td>
-			  Forward
-		  </td>
-          <td>Reveals the next editor location in the location history.</td>
-          <td>
-            Alt + Right
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-      </p>
-      <p>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-      </p>
-      <p>
-    <a href="../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-     <a href="../tasks/tasks-74.htm">Showing an element in the package explorer</a><br>
-     <a href="../tasks/tasks-75.htm">Opening a type in the package explorer</a><br>
-     <a href="../tasks/tasks-76.htm">Opening an editor on a type</a><br>
-     <a href="../tasks/tasks-77.htm">Opening a package</a><br>
-    </p> 
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-      <p>
-      <a href="views/ref-view-package-explorer.htm">Package explorer view</a><br>
-	  <a href="views/ref-type-hierarchy.htm">Type hierarchy view</a><br>
-	  <a href="ref-dialog-javadoc-location.htm">Javadoc location properties</a><br>
-	  <a href="ref-export-javadoc.htm">Javadoc export wizard</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm
deleted file mode 100644
index daa1b42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-project.htm
+++ /dev/null

@@ -1,172 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Project Actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Project Actions
-    </h1>
-	<p>
-        Project menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Project menu commands">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Open Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Shows a dialog that can be used to select a closed project and open it
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Close Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Closes the currently selected projects
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Build All
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Builds all projects in the workspace. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-            </p>
-          </td>
-          <td>
-            Ctrl + B&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Build Project
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Builds the currently selected project. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Build Working Set
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Builds the projects contained in the currently selected working set. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Clean...
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Shows a dialog where the projects to be cleaned can be selected.
-            </p>
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Build Automatically
-          </td>
-          <td>
-           	If selected, all modified files are automatically rebuilt if saved. This is an incremental build, meaning that the builder analyzes the changes since the last time of build and minimizes the
-              number of changed files.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Generate Javadoc...
-          </td>
-          <td>
-            Opens the Generate Javadoc wizard on the currently selected project.
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Properties
-          </td>
-          <td>
-            Opens the property pages on the currently selected project.
-          </td>
-          <td>&nbsp;
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-       <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-       </p>
-       <p>
-      <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-       <a href="../concepts/concept-java-builder.htm">Java builder</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm
deleted file mode 100644
index 6d00b6f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-refactor.htm
+++ /dev/null

@@ -1,619 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title>Refactor Actions</title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1"
-	type="text/css">
-</head>
-<body>
-<h1>Refactor Actions</h1>
-<p>Refactor menu commands:</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Refactor menu commands">
-	<tbody>
-		<tr>
-			<th>
-			<p>Name</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-		<tr>
-			<td align="left" valign="top">
-			<p>Rename</p>
-			</td>
-			<td align="left" valign="top">Renames the selected element and
-			(if enabled) corrects all references to the elements (also in other
-			files). <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Rename refactorings">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Methods, method parameters, fields, local variables,
-						types, type parameters, enum constants, compilation units,
-						packages, source folders, projects and on a text selection
-						resolving to one of these element types</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Shortcut:</td>
-						<td align="left" valign="top">Alt + Shift + R</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">Renaming a type does allow to
-						rename similarly named variables and methods. Enable 'Update
-						similarly named variables and methods' in the Rename Type dialog.
-						Select 'Configure...' to configure the strategy for matching type
-						names. <br>
-						<br>
-						Renaming a package does allow to rename its subpackages. Enable
-						'Rename subpackages' in the Rename Package dialog.<br>
-						<br>						
-						Enable 'Keep original method as delegate to changed method' to keep the original method.
-						Optionally you can deprecate the old method.
-					</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top">
-			<p>Move</p>
-			</td>
-
-			<td align="left" valign="top">Moves the selected elements and
-			(if enabled) corrects all references to the elements (also in other
-			files). <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Move refactorings">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Instance method (which can be moved to a component), one
-						or more static methods, static fields, types, compilation units,
-						packages, source folders and projects and on a text selection
-						resolving to one of these element types</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Shortcut:</td>
-						<td align="left" valign="top">Alt + Shift + V</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">You can use Drag &amp; Drop in
-						the Package Explorer to start this refactoring.</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top">Change Method Signature</td>
-			<td>Changes parameter names, parameter types, parameter order
-			and updates all references to the corresponding method. Additionally,
-			parameters and thrown exceptions can be removed or added and method return type and
-			method visibility can be changed. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Change Method Signature refactorings">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Methods or on text selection resolving to a method</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Shortcut:</td>
-						<td align="left" valign="top">Alt + Shift + C</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">Enable 'Keep original method as
-						delegate to changed method' in the Change Method Signature dialog
-						to keep the original method.</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-		<tr align="left" valign="top">
-			<td>Extract Method</td>
-			<td>Creates a new method containing the statements or expression
-			currently selected and replaces the selection with a reference to the
-			new method. This feature is useful for cleaning up lengthy,
-			cluttered, or overly-complicated methods. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Extract Method refactorings">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>You can use&nbsp;<em>Expand Selection to</em> from the <a
-							href="ref-menu-edit.htm">Edit</a> menu to get a valid selection
-						range.
-						<br>This refactoring is also available as <a href="ref-java-editor-quickassist.htm">quick assist</a> on
-						statements and expressions selected in the editor.
-						</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Shortcut:</td>
-						<td align="left" valign="top">Alt + Shift + M</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-
-		<tr align="left" valign="top">
-
-			<td>Extract Local Variable</td>
-			<td>Creates a new variable assigned to the expression currently
-			selected and replaces the selection with a reference to the new
-			variable. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Extract local variable refactorings">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Text selections that resolve to local variables. You can
-						use&nbsp;<em>Expand Selection to</em> from the <a
-							href="ref-menu-edit.htm">Edit</a> menu to get a valid selection
-						range.
-						<br>This refactoring is also available as <a href="ref-java-editor-quickassist.htm">quick assist</a> on
-						expressions selected in the editor.
-						</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Shortcut:</td>
-						<td align="left" valign="top">Alt + Shift + L</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-		<tr>
-
-			<td align="left" valign="top">Extract Constant</td>
-
-			<td>Creates a static final field from the selected expression
-			and substitutes a field reference, and optionally rewrites other
-			places where the same expression occurs. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Extract Constant refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Constant expressions or text selections which resolve to
-						constant expressions
-						<br>This refactoring is also available as <a href="ref-java-editor-quickassist.htm">quick assist</a> on
-						expressions selected in the editor.
-						</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-		<tr align="left" valign="top">
-
-			<td align="left" valign="top">Inline</td>
-
-			<td>Inline local variables, methods or constants. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Inline refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Methods, static final fields and text selections that
-						resolve to methods, static final fields or local variables
-						<br>This refactoring is also available as <a href="ref-java-editor-quickassist.htm">quick assist</a> on
-						local variables selected in the editor.
-						</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Shortcut:</td>
-						<td align="left" valign="top">Alt + Shift + I</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-
-		<tr>
-
-			<td align="left" valign="top">Convert Anonymous Class to Nested</td>
-
-			<td>Converts an anonymous inner class to a member class. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Convert Anonymous Class to Nested refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Anonymous inner classes</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-		<tr>
-
-			<td align="left" valign="top">Convert Member Type to Top Level</td>
-
-			<td>Creates a new Java compilation unit for the selected member
-			type, updating all references as needed. For non-static member types,
-			a field is added to allow access to the former enclosing instance, if
-			necessary. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Convert Member Type to Top Level refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Member types or text resolving to a member type.
-						<br>This refactoring is also available as <a href="ref-java-editor-quickassist.htm">quick assist</a> on
-						member classes selected in the editor.
-						</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-
-			<td align="left" valign="top">Convert Local Variable to Field</td>
-
-			<td>Turn a local variable into a field. If the variable is
-			initialized on creation, then the operation moves the initialization
-			to the new field's declaration or to the class's constructors. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Convert Local Variable to Field refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Text selections that resolve to local variables.
-						<br>This refactoring is also available as <a href="ref-java-editor-quickassist.htm">quick assist</a> on
-						local variables selected in the editor.
-						</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Extract Superclass</td>
-			<td>Extracts a common superclass from a set of sibling types.
-			The selected sibling types become direct subclasses of the extracted
-			superclass after applying the refactoring. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Extract Superclass refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Types</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">Enable 'Use the extracted class
-						where possible' to use the newly created class wherever possible.
-						See <em>Use Supertype Where Possible</em>.</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Extract Interface</td>
-			<td>Creates a new interface with a set of methods and makes the
-			selected class implement the interface. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Extract Interface refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Types</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">Enable 'Use the extracted
-						interface type where possible' to use the newly created interface
-						wherever possible. See <em>Use Supertype Where Possible</em>.</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Use Supertype Where Possible</td>
-			<td>Replaces occurrences of a type with one of its supertypes
-			after identifying all places where this replacement is possible. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Use Supertype Where Possible refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Types</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Push Down</td>
-			<td>Moves a set of methods and fields from a class to its
-			subclasses. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Push Down refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>One or more methods and fields declared in the same type
-						or on a text selection inside a field or method</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Pull Up</td>
-			<td align="left" valign="top">Moves a field or method to a
-			superclass of its declaring class or (in the case of methods)
-			declares the method as abstract in the superclass. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Pull Up refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>One or more methods, fields and member types declared in
-						the same type or on a text selection inside a field, method or
-						member type</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Extract Class</td>
-			<td>Replaces a set of fields with new container object. All references to the fields are
-			updated to access the new container object.<br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Extract Class refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>The set of fields or a type containing fields</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">Enable 'Create Getter and Setters' to add
-						accessor methods to the new type</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Introduce Parameter Object</td>
-			<td>Replaces a set of parameters with a new class, 
-			and updates all callers of the method to pass an instance of the new
-			class as the value to the introduce parameter.<br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Introduce Parameter Object refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Methods or on text selection resolving to a method</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">Enable 'Keep original method as
-						delegate to changed method' in the Introduce Parameter Object dialog
-						to keep the original method.</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Introduce Indirection</td>
-			<td>Creates a static indirection method delegating to the
-			selected method. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Introduce Indirection refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Methods or on text selection resolving to a method</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td align="left" valign="top">Enable 'Redirect all method
-						invocations' to replace all calls to the original method by calls
-						to the indirection method.</td>
-					</tr>
-
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-		<tr>
-			<td align="left" valign="top">Introduce Factory</td>
-			<td>Creates a new factory method, which will call a selected
-			constructor and return the created object. All references to the
-			constructor will be replaced by calls to the new factory method. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Introduce Factory refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Constructor declarations</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-		<tr>
-			<td align="left" valign="top">Introduce Parameter</td>
-			<td>Replaces an expression with a reference to a new method
-			parameter, and updates all callers of the method to pass the
-			expression as the value of that parameter. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Introduce Parameter refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Text selections that resolve to expressions</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Encapsulate Field</td>
-			<td>Replaces all references to a field with getter and setter
-			methods. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Encapsulate Field refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Field or a text selection resolving to a field.
-						<br>This refactoring is also available as <a href="ref-java-editor-quickassist.htm">quick assist</a> on
-						field declarations and references selected in the editor.
-						</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top">Generalize Declared Type</td>
-			<td>Allows the user to choose a supertype of the reference's
-			current type. If the reference can be safely changed to the new type,
-			it is. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Generalize Declared Type refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Type references and declarations of fields, local
-						variables, and parameters with reference types</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Infer Generic Type Arguments</td>
-			<td>Replaces raw type occurrences of generic types by
-			parameterized types after identifying all places where this
-			replacement is possible. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Infer Generic Type Arguments refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Projects, packages, and types</td>
-					</tr>
-					<tr>
-						<td align="left" valign="top">Options:</td>
-						<td>'Assume clone() returns an instance of the receiver
-						type'. Well-behaved classes generally respect this rule, but if
-						you know that your code violates it, uncheck the box. <br>
-						<br>
-						'Leave unconstrained type arguments raw (rather than inferring
-						&lt;?&gt;)'. If there are no constraints on the elements of e.g.
-						ArrayList a, uncheck this box will cause Eclipse to still
-						provide a wildcard parameter, replacing the reference with
-						ArrayList&lt;?&gt;.</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Migrate JAR File</td>
-			<td>Migrates a JAR File on the build path of a project in your
-			workspace to a newer version, possibly using refactoring information
-			stored in the new JAR File to avoid breaking changes. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Migrate JAR File refactoring">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>JAR Files on build path</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Create Script</td>
-			<td>Creates a script of the refactorings that have been applied
-			in the workspace. Refactoring scripts can either be saved to a file
-			or copied to the clipboard. See <em>Apply Script</em>. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Create Script">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Always</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Apply Script</td>
-			<td>Applies a refactoring script to projects in your workspace.
-			Refactoring scripts can either be loaded from a file or from the
-			clipboard. See <em>Create Script</em>. <br>
-			<table border="0" cellspacing="1" cellpadding="5" summary="Apply Script">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Always</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">History</td>
-			<td>Browses the workspace refactoring history and offers the
-			option to delete refactorings from the refactoring history. <br>
-			<table border="0" cellspacing="1" cellpadding="1" summary="History">
-				<tbody>
-					<tr>
-						<td align="left" valign="top">Available:</td>
-						<td>Always</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-
-		</tr>
-
-	</tbody>
-</table>
-<p>Refactoring commands are also available from the context menus in
-many views and the Java editor.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts">
-</p>
-<p><a href="../concepts/concept-refactoring.htm">Refactoring support</a></p>
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p><a href="ref-wizard-refactorings.htm">Refactoring dialogs</a><br>
-<a href="preferences/ref-preferences-java.htm">Java preferences</a><br>
-</p>
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm
deleted file mode 100644
index 034ad6c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-search.htm
+++ /dev/null

@@ -1,338 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Search Actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Search Actions
-    </h1>
-	<p>
-        Search menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Search menu commands">
-      <tr>
-        <th>
-          <p>
-            Name
-          </p>
-        </th>
-        <th>
-          <p>
-            Function
-          </p>
-        </th>
-        <td>
-          <strong>Keyboard Shortcut</strong>
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td align="left" valign="top">
-          <p>
-            Search...
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Opens the search dialog
-          </p>
-        </td>
-        <td>
-          Ctrl + H
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            File...
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Opens the search dialog on the File search page
-          </p>
-        </td>
-        <td>&nbsp;
-          
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Java...
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Opens the search dialog on the Java search page
-          </p>
-        </td>
-        <td>&nbsp;
-          
-        </td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Text
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches for the selected text in the chosen scope:
-          </p>
-          <ul>
-            <li>Workspace (<b>Ctrl + Alt + G</b>)</li>
-            <li>Project</li>
-            <li>Hierarchy</li>
-            <li>Working Set</li>
-          </ul>
-        </td>
-        <td>&nbsp;
-          
-        </td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            References
-          </p>
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Finds all references to the selected Java element in the chosen scope:
-          </p>
-          <ul>
-            <li>Workspace (<b>Ctrl + Shift + G</b>)</li>
-            <li>Project</li>
-            <li>Hierarchy</li>
-            <li>Working Set</li>
-          </ul>
-        </td>
-        <td>&nbsp;
-        </td>
-      </tr>
-      <tr>
-        <td>
-          Declarations
-        </td>
-        <td>
-          <p>
-          Finds all declarations of the selected Java element in the chosen scope:
-          </p>
-          <ul>
-            <li>Workspace (<b>Ctrl + G</b>)</li>
-            <li>Project</li>
-            <li>Hierarchy</li>
-            <li>Working Set</li>
-          </ul>
-        </td>
-        <td>&nbsp;          
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td>
-          Implementors
-        </td>
-        <td>
-          <p>
-          Finds all implementors of the selected interface in the chosen scope:
-            (Workspace, Project or Working Set)
-          </p>
-          <ul>
-            <li>Workspace</li>
-            <li>Project</li>
-            <li>Working Set</li>
-          </ul>            
-        </td>
-        <td>&nbsp;
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td>
-          Read Access
-        </td>
-        <td>
-          <p>
-          Finds all read accesses to the selected field in the chosen scope:
-          </p>
-          <ul>
-            <li>Workspace</li>
-            <li>Project</li>
-            <li>Hierarchy</li>
-            <li>Working Set</li>
-          </ul>  
-        </td>
-        <td>&nbsp;   
-        </td>
-      </tr>
-      <tr align="left" valign="top">
-        <td>
-          Write Access
-        </td>
-        <td>
-          <p>
-          Finds all write accesses to the selected field in the chosen scope:
-          </p>
-          <ul>
-            <li>Workspace</li>
-            <li>Project</li>
-            <li>Hierarchy</li>
-            <li>Working Set</li>
-          </ul>  
-        </td>
-        <td>&nbsp;
-        </td>
-      </tr>
-
-      <tr>
-        <td valign="top">
-          <p>Occurrences in File</p>
-        </td>
-
-        <td valign="top">
-          <p>Finds all occurrences of the selected Java element in its file
-          </p>
-          <ul>
-            <li>Identifier: Occurrences of all identifiers resolving to the selected element</li>
-            <li>Implementing Methods: All methods implemented by the selected super-interface declaration</li>
-            <li>Throwing Exceptions: All statements that possible throw the selected declared exception</li>
-            <li>Method Exits: All statements that can exit the method of the selected return type</li>
-            <li>Break/Continue Target: The targets of the selected break and continue statement</li>
-          </ul>  
-        </td>
-        <td>
-        	Ctrl + Shift + U
-        </td>
-
-      </tr>
-      
-      <tr>
-        <td valign="top">
-          <p>Referring Tests</p>
-        </td>
-        <td valign="top">
-          <p>Finds all JUnit tests that refer to the currently selected type</p>
-        </td>
-        <td>&nbsp;
-        </td>
-      </tr>
-     
-    </table>
-	
-	<p>
-        Search scopes submenu:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Search scopes submenu">
-      <tr>
-        <th>
-          <p>
-            Scope
-          </p>
-        </th>
-        <td>
-          <strong>Availability</strong>
-        </td>
-        <th>
-          <p>
-            Description
-          </p>
-        </th>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Workspace
-          </p>
-        </td>
-        <td>
-          all elements
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in the full workspace
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Project
-          </p>
-        </td>
-        <td>
-          all elements
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in the project enclosing the selected element
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Hierarchy
-          </p>
-        </td>
-        <td>
-          types and members
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in the type's hierarchy
-          </p>
-        </td>
-      </tr>
-      <tr>
-        <td align="left" valign="top">
-          <p>
-            Workings Set
-          </p>
-        </td>
-        <td>
-          all elements
-        </td>
-        <td align="left" valign="top">
-          <p>
-            Searches in a working set
-          </p>
-        </td>
-      </tr>
-    </table>
-    <p>
-      Scopes can be saved and names in the working set dialog. Existing instances of working sets 
-	  are also available in the Search Scope submenu
-    </p>
-    <p>
-      A Java search can also be conducted via the context menu of all Java views.
-      The search context menu is also available in the Java editor. The search is only performed if the currently selected text can be resolved to a Java element.
-    </p>
-    <p>
-      The type of the selected Java element defines which search context menus are available. The Java editor does not constrain the list of available Java searches based on the
-      selection.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-      </p>
-      <p>
-      <a href="../concepts/concept-java-search.htm">Java search</a>
-    </p>
-    <p>
-       <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-       </p>
-       <p>
-     <a href="../reference/ref-dialog-java-search.htm">Java search tab</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm
deleted file mode 100644
index 7a2275d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-menu-source.htm
+++ /dev/null

@@ -1,370 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Source Actions
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Source Actions
-    </h1>
-	<p>
-        Source menu commands:
-	</p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Source menu commands">
-      <tbody>
-        <tr>
-          <th>
-            <p>
-              Name
-            </p>
-          </th>
-          <th>
-            <p>
-              Function
-            </p>
-          </th>
-          <td>
-            <strong>Keyboard Shortcut</strong>
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Toggle Comment
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Comment or uncomment all lines containing the current selection.
-            </p>
-          </td>
-          <td>
-            Ctrl + /
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td align="left" valign="top">
-            <p>
-              Add Block Comment
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Adds a block comment around all lines containing the current selection.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + /
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Remove Block Comment
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Removes a block comment from all lines containing the current selection.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + \
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Generate Element Comment
-          </td>
-          <td>
-          	Adds a comment to the selected element. See the	<a href="../reference/preferences/java/codestyle/ref-preferences-code-templates.htm">Code templates preference page</a> 
-          	to specify the format of the generated comments. Available on types, fields, constructors, and methods.
-          </td>
-          <td>
-          Alt + Shift + J
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Shift Right
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Increments the level of indentation of the currently select lines. Only activated when the selection covers multiple lines or a single whole line.
-            </p>
-          </td>
-          <td>&nbsp;
-           
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Shift Left
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Decrements the level of indentation of the currently select lines. Only activated when the selection covers multiple lines or a single whole line.
-            </p>
-          </td>
-          <td>&nbsp;
-         
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Correct Indentation
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Corrects the indentation of the lines denoted by the current text selection.
-            </p>
-          </td>
-          <td>
-          	Ctrl + I
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Format
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Uses the code formatter to format the current text selection. The formatting options are configured on the <a href="preferences/java/codestyle/ref-preferences-formatter.htm">Code Formatter preference page</a>.
-            </p>
-          </td>
-          <td>
-            Ctrl + Shift + F
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Format Element
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Uses the code formatter to format the Java element comprising the current text selection. The Format Element action works on method and type level. The formatting options are configured on the <a href="preferences/java/codestyle/ref-preferences-formatter.htm">Code Formatter preference page</a>.
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-		<tr align="left" valign="top">
-          <td>
-            Add Import
-          </td>
-          <td>
-            Creates an import declaration for a type reference currently selected. If the type reference if qualified, the qualification will be removed if possible. If the
-            referenced type name can not be mapped uniquely to a type of the current project you will be prompted to specify the correct type. Add Import tries to follow the
-            import order as specified in the <a href="preferences/java/codestyle/ref-preferences-organize-imports.htm">Organize Import preference page</a>
-          </td>
-          <td>
-            Ctrl + Shift + M
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Organize Imports
-          </td>
-          <td>
-            Organizes the import declarations in the compilation unit currently open or selected. Unnecessary import declarations are removed, and required import declarations are
-            ordered as specified in the <a href="preferences/java/codestyle/ref-preferences-organize-imports.htm">Organize Imports preference page</a>. Organize imports can be
-            executed on incomplete source and will prompt you when a referenced type name can not be mapped uniquely to a type in the current project.<br>
-             You can also organize multiple compilation units by invoking the action on a package or selecting a set of compilation units.
-          </td>
-          <td>
-            Ctrl + Shift + O
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Sort Members
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-              Sorts the members of a type according to the sorting order specified in the
-              <a href="./preferences/java/appearance/ref-preferences-member-sort-order.htm">Member Sort Order preference page</a>
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td align="left" valign="top">
-            <p>
-              Clean Up
-            </p>
-          </td>
-          <td align="left" valign="top">
-            <p>
-            Performs various changes in order to clean up your code according to the settings specified in the
-            <a href="./preferences/java/codestyle/ref-preferences-cleanup.htm">Clean Up preference page</a>
-            </p>
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Override/Implement Methods
-          </td>
-          <td>
-            Opens the <a href="ref-dialog-override-method.htm">Override Method dialog</a> that allows you to override or implement a method in the current type. Available on types
-            or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Generate Getter and Setter
-          </td>
-          <td>
-            Opens the <a href="ref-dialog-gettersetter.htm">Generate Getters and Setters dialog</a> that allows you to create Getters and Setters for fields in the current type.
-            Available on fields and types or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Generate Delegate Methods
-          </td>
-          <td>
-            Opens the Generate Delegate Methods dialog that allows you to create method delegates for fields 
-            in the current type. Available on fields and types with fields.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Generate hashCode() and equals()
-          </td>
-          <td>
-            Opens the Generate HashCode and Equals dialog that allows you to start
-			  and control the generation of hashCode and equals methods in the
-			  current type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Generate toString()
-          </td>
-          <td>
-            Opens the <a href="ref-dialog-tostring.htm">Generate toString() dialog</a> that allows you to start
-			  and control the generation of a toString() method in the current type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Generate Constructor using Fields
-          </td>
-          <td>
-            Adds constructors which initialize fields for the currently selected types. Available on types, fields or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Add Constructor from Superclass
-          </td>
-          <td>
-            Adds constructors as defined in the super class for the currently selected types. Available on types or on a text selection inside a type.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Surround With
-          </td>
-          <td>
-			  Surround the selected statements with a code template. Create your 
-			  own templates on the <a href="preferences/java/editor/ref-preferences-templates.htm">Template preference page</a>.
-			  Further, you can use&nbsp;<em>Expand
-            Selection to</em> from the <a href="ref-menu-edit.htm">Edit</a> menu to get a valid selection range.
-          </td>
-          <td>
-            Alt + Shift + Z
-          </td>
-        </tr>
-        <tr>
-          <td>
-            Externalize Strings
-          </td>
-          <td>
-            Opens the Externalize strings wizard. This wizards allows you to replace all strings in the code by statements accessing a property file.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-        <tr align="left" valign="top">
-          <td>
-            Find Broken Externalized Strings
-          </td>
-          <td>
-			  Searches for broken externalized strings in a selected property file, package, project or set of projects.
-          </td>
-          <td>&nbsp;
-            
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-       <img  src="../images/ngrelc.png" alt="Related concepts" border="0"></p>
-       <p>
-    <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-     <a href="../concepts/concept-string-externalization.htm">String externalization</a><br>
-     <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a></p>
-    <p>
-       <img border="0"  src="../images/ngrelt.png" alt="Related tasks"></p>
-       <p>
-      <a href="../tasks/tasks-206.htm">Externalizing strings</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="views/ref-java-editor.htm">Java editor</a><br>
-       <a href="preferences/java/ref-preferences-editor.htm">Java editor preferences</a><br>
-       <a href="views/ref-view-outline.htm">Java outline</a><br>
-       <a href="views/ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-build-path.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-build-path.htm
deleted file mode 100644
index 57dd325..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-build-path.htm
+++ /dev/null

@@ -1,316 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Build Path</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Build Path</h1>
-
-    <p>The options in this page indicate the build path settings for a Java project. You can reach this page through the project properties (Project &gt; Properties &gt; Java Build Path) from the context menu on a created project or the <a href="ref-menu-file.htm">File
-      menu</a> of the workbench.</p>
-
-    <p>The build class path is a list of paths visible to the compiler when building the project.</p>
-
-    <h2>Source tab</h2>
-
-    <p>Source folders are top-level folders in the project hierarchy. They are the root of packages containing .java files. 
-    The compiler will translate the contained files to .class files that will be written to the output folder.</p>
-<p>Source folders allow to structure the project, for example to separate 
-test from the application in two source folders. Within a source folder, a more detailed structuring can be acived by using packages.</p> 
-<p>Each source folder can define an exclusion filter to specify which 
-resources inside the folder should not be visible to the compiler.</p>
-<p>Resources existing in source folders are copied to the output folder unless the setting in the <a href="preferences/java/compiler/ref-preferences-building.htm">Java &gt; Compiler &gt; Building</a> preference
-    page specifies that the resource is filtered. The output folder is defined per project except if a source folder specifies its own output folder.</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="Source folder options" width="600">
-	<caption>Source folder options:<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Option</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top" width="20%">Add Folder</td>
-
-			<td align="left" valign="top">Creates a new folder to contain source</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top" width="20%">Link Source</td>
-
-			<td align="left" valign="top">Creates a new folder that links to an location outside of the workspace</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top">Edit</td>
-
-			<td align="left" valign="top">Allows to modify the currently selected
-			source folder or source folder attribute.</td>
-		</tr>
-
-		<tr>
-			<td>Remove</td>
-
-			<td>Removes the selected folders from the class path. This does not
-			delete the folders nor their contents.</td>
-		</tr>
-		<tr>
-			<td>Allow output folder per source folder</td>
-			<td>Shows/Hides the 'output folder' attribute of the source folders</td>
-		</tr>
-		
-	</tbody>
-</table>
-<br>
-<table border="1" cellspacing="0" cellpadding="5" summary="Source folder attributes" width="600">
-	<caption>Source folder attributes:<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Attribute</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top" width="20%">Exclusion filter</td>
-
-			<td align="left" valign="top">Selects which resources are not visible to the compiler</td>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Output folder</td>
-
-			<td align="left" valign="top">Only available when <b>Allow output
-			folder per source folder</b> is checked. Defines a source folder specific output location. If not set the project's default output folder is used.</td>
-		</tr>
-		<tr>
-			<td align="left" valign="top">Native library location</td>
-
-			<td align="left" valign="top">Defines the folder that contains the native libararies
-			  (for example 'dll' or 'o' files) required at runtime by the sources in the source folder.
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-    <p>At the bottom of this page, the <b>Default output folder</b> field allows you to enter a path to a folder path where the compilation output for this
-    project will reside. The default output is used for source folders that do not specify an own output folder. Use <b>Browse</b> to select an existing location from the current project.</p>
-    
-    <h2>Projects tab</h2>
-
-    <p>In the <b>Required projects on the build path</b> list, you can add project dependencies by selecting other workbench
-    projects to add to the build path for this new project.</p>
-
-    <p>Adding a required project indirectly adds all its classpath entries marked as 'exported'. Setting a classpath entry as exported is done in the Order and Export tab.</p>
-
-    <p>The projects selected here are automatically added to the referenced projects list. The referenced project list is used to determine the build order. A project is always
-    build after all its referenced projects are built.</p>
-    
-    <table border="1" cellspacing="0" cellpadding= "5" summary="Project entry options" width="600">
-
-	<tbody>
-		<tr>
-			<th>Action</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="middle" width="20%">Add</td>
-
-			<td align="left" valign="top">Add another project in the workspace to the build path of this project.</td>
-		</tr>
-		
-		<tr>
-			<td align="left" valign="middle" width="20%">Edit</td>
-
-			<td align="left" valign="top">Edit the classpath attribute of a required project.</td>
-		</tr>
-		
-		<tr>
-			<td align="left" valign="middle" width="20%">Remove</td>
-
-			<td align="left" valign="top">Removes the selected required projects from the list.</td>
-		</tr>
-		
-	</tbody>
-</table>
-<table border="1" cellspacing="0" cellpadding="5" summary="Project entry attributes"
-	width="600">
-	<caption>Project entry attributes:<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Attribute</th>
-
-			<th>Description</th>
-		</tr>
-		
-		<tr>
-			<td align="left" valign="top">Native library location</td>
-
-			<td align="left" valign="top">Specifies where native library required for the project to operate can be found.</td>
-		</tr>
-		
-		<tr>
-			<td align="left" valign="top">Access rules</td>
-
-			<td align="left" valign="top">Specifies access rules for project contained in the library. This allows to hide content of a project.</td>
-		</tr>
-	</tbody>
-</table>
-
-    <h2>Libraries tab</h2>
-
-    <p>On this page, you can add libraries to the build path.</p>
-    <p>By default, the library list contains an entry representing the Java runtime library.  This entry points to the JRE
-    selected as the default JRE. The default JRE is configured in the <a href="preferences/java/debug/ref-installed_jres.htm">Java &gt; Debug &gt; Installed JREs</a> preferences page.</p>
-
-    <table border="1" cellspacing="0" cellpadding= "5" summary="Libraries tab options" width="600">
-      <caption>
-        Libraries tab options:<br>
-      </caption>
-
-      <tbody>
-        <tr>
-          <th width="20%">Option</th>
-
-          <th>Description</th>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add JARs</td>
-
-          <td align="left" valign="top">Allows you to navigate the workbench hierarchy and select JAR files to add to the build path.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add External JARs</td>
-
-          <td align="left" valign="top">Allows you to navigate the file system (outside the workbench) and select JAR files to add to the build path.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Add Variable</td>
-
-          <td align="left" valign="top">Allows you to add classpath variables to the build path. Classpath variables are an indirection to JARs with the benefit of avoiding local
-          file system paths in a classpath. This is needed when projects are shared in a team.<br>
-           Variables can be created and edited in the <a href="preferences/java/buildpath/ref-preferences-classpath-variables.htm">Java &gt; Build Path &gt; Classpath Variables</a> preference page.</td>
-        </tr>
-
-        <tr>
-          <td>Add Library</td>
-
-          <td>Allows to add a predefined libraries like the JRE System Library. Such libraries can stand for an arbitrary number of entries (visible as children node of the library node)</td>
-        </tr>
-
-        <tr>
-          <td>Add Class Folder</td>
-
-          <td>Allows to navigate the workbench hierarchy and select a class folder for the build path. The selection dialog also allows you to create a new folder.</td>
-        </tr>
-
-        <tr>
-          <td>Add External Class Folder</td>
-
-          <td>Allows to navigate the file system (outside the workbench) and select a class folder for the build path. The selection dialog also allows you to create a new folder.</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Edit</td>
-
-          <td align="left" valign="top">Allows you to modify the currently selected library entry or entry attribute</td>
-        </tr>
-
-        <tr>
-          <td align="left" valign="top">Remove</td>
-
-          <td align="left" valign="top">Removes the selected element from the build path. This does not delete the resource.</td>
-        </tr>
-        
-        <tr>
-          <td align="left" valign="top">Migrate JAR File</td>
-
-          <td align="left" valign="top">Migrate a JAR on the build path to a newer version. If the newer version contains refactoring scripts
-          the refactoring stored in the script will be executed.</td>
-        </tr>
-      </tbody>
-    </table>
-
-    <p>&nbsp;Libraries have the following attributes (presented as library entry children nodes):</p>
-
-<table border="1" cellspacing="0" cellpadding="5" summary="Library entry attributes"
-	width="600">
-	<caption>Library entry attributes:<br>
-	</caption>
-
-	<tbody>
-		<tr>
-			<th>Attribute</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top" width="20%">Javadoc location</td>
-
-			<td align="left" valign="top">Specifies where the library's Javadoc documentation can be found. If specified you can use <b>Shift+F2</b> on an element of this library to open its documentation.</td>
-		</tr>
-
-		<tr>
-			<td align="left" valign="top">Source attachment</td>
-
-			<td align="left" valign="top">Specifies where the library's source can be found.</td>
-		</tr>
-		
-		<tr>
-			<td align="left" valign="top">Native library location</td>
-
-			<td align="left" valign="top">Specifies where native library required for the library to operate can be found.</td>
-		</tr>
-		
-		<tr>
-			<td align="left" valign="top">Access rules</td>
-
-			<td align="left" valign="top">Specifies access rules for resources contained in the library. This allows to hide content of a library.</td>
-		</tr>
-	</tbody>
-</table>
-
-<h2>Order and Export tab</h2>
-
-    <p>In the <b>Build class path order</b> list, you can click the <b>Up</b> and <b>Down</b> buttons to move the selected path entry up or down in the build path order for this new project.</p>
-
-    <p>Checked list entries are marked as exported. Exported entries are visible to projects that require the project. Use the <b>Select
-    All</b> and <b>Deselect All</b> to change the checked state of all entries. Source folders are always exported,
-    and can not be deselected.</p>
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concept-build-classpath.htm">Build classpath</a><br>
-     <a href="../concepts/concept-classpath-variables.htm">Classpath variables</a><br>
-    </p>
-     <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-jdt-faq.htm">Frequently asked questions on JDT</a><br>
-     <a href="../reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm">Classpath variables preferences</a><br>
-     <a href="../reference/preferences/java/ref-preferences-build-path.htm">Build path preferences</a><br>
-     <a href="../reference/preferences/java/ref-preferences-compiler.htm">Compiler preferences</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm
deleted file mode 100644
index da2a1e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-compiler.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Compiler page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Compiler Page</h1>
-
-    <p>The options in this page indicate the compiler settings for a Java project.<br>
-     You can reach this page through the</p>
-
-    <ul>
-      <li>Java Compiler property page (File &gt; Properties &gt; Java Compiler) from the context menu on a created project or the <a href="ref-menu-file.htm">File
-      menu</a></li>
-    </ul>
-
-	<p> A project can either reuse workspace default settings or use its own custom settings.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Compiler property page">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Enable project specific settings
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Once selected, compiler settings can be configured for this project. 
-              All <a href="../reference/preferences/java/ref-preferences-compiler.htm">Java compiler preferences</a> can be customized.
-              At any time, it is possible to revert to workspace defaults, by using the button <strong>Restore Defaults</strong>.  
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concept-build-classpath.htm">Build classpath</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-    <p>
-     <a href="../reference/preferences/java/ref-preferences-compiler.htm">Java compiler preferences</a><br>
-     <a href="../reference/ref-properties-build-path.htm">Java Build Path properties</a><br>
-     <a href="../reference/ref-jdt-faq.htm">Frequently asked questions on JDT</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-source-attachment.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-source-attachment.htm
deleted file mode 100644
index 68453a6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-source-attachment.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Source Attachment Property Page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>Source Attachment Property Page</h1>
-
-    <p>To browse the source of a type contained in library you can attach a source archive or source folder to this library. The editor will then show the source instead of a the decompiled code.
-    Setting the source attachment also allows source level stepping with the debugger.</p>
-
-    <p>The Source Attachment dialog can be reached in several ways:</p>
-
-    <ul>
-      <li>Select a JAR in the Package Explorer and choose <b>Properties &gt; Java Source Attachment</b> from the context
-	menu or the <a href="ref-menu-project.htm">Project menu</a></li>
-
-      <li>Open the Java Build Path page of a project (<b>Projects &gt;
-	Properties &gt; Java Build Path</b>). On the <b>Libraries</b> page  expand the library's  node and select the <b>Source
-	attachment</b> attribute and press <b>Edit</b></li>
-	<li>Open an editor on a class file. If the
-	source attachment has not already been configured for this JAR, the
-	editor contains a button <span class="control">Attach Source</span></li>
-</ul>
-
-    <p>Depending of how a JAR was contributed to the classpath, you can see different types of Source attachment dialogs:</p>
-
-    
-
-    <h2>JAR</h2>
-
-<p>In the <span class="control">Location path</span> field, enter the path of an archive or a folder containing the source. Use either the <b>Workspace</b>, <b>External
-File</b> or the <b>External Folder</b> button to browse for a location.</p>
-
-<h2>Variable</h2>
-
-<p>In the <span class="control">Location Variable Path</span> field
-enter a <i>variable path</i> that points to the source attachment's location.
-A variable path has as first segment a variable (which will resolve to a
-folder or file), the rest is an optional path extension (e.g.<em>MYVARIABLE/src.jar</em>
-). Use either the <span class="control">Variable</span> button to select
-an existing variable and the <span class="control">Extension</span>
-button to select the extension path. The <span class="control">Extension</span>
-button is only enabled when the variable can be extended (resolves to a
-folder)</p>
-
-<p><var>JRE_SRC</var> is a reserved variable that points to a JRE selected in the <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs preference page</a>
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.preferences.VMPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Installed JRE preference page">
-<span class="control">Java &gt; Installed JREs</span></a>).
-Go to this preference page to configure the source attachment for the JRE's library..</p>
-
-    
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concept-build-classpath.htm">Build classpath</a></p>
-     <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs preferences</a><br>
-     <a href="../reference/ref-properties-build-path.htm">Java build path properties</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm
deleted file mode 100644
index 4763ab9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-properties-task-tags.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Java Task Tags Page</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Java Task Tags Page</h1>
-
-    <p>The options in this page indicate the task tags for a Java project.<br>
-     You can reach this page through the</p>
-
-    <ul>
-      <li>Java task tags property page (File &gt; Properties &gt; Java Compiler &gt; Task Tags) from the context menu on a created project or the <a href="ref-menu-file.htm">File
-      menu</a></li>
-    </ul>
-
-	<p> A project can either reuse workspace default settings or use its own custom settings.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Task Tags property page">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Enable project specific settings
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Once selected, task tags can be configured for this project as in the <a href="../reference/preferences/java/compiler/ref-preferences-task-tags.htm">Task tags preference page</a>.
-              At any time, it is possible to revert to workspace defaults, by using the button <strong>Restore Defaults</strong>.  
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-
-<p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-      </p>
-    <p>
-     <a href="../reference/preferences/java/compiler/ref-preferences-task-tags.htm">Task tag preferences</a>
-    </p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-refactoring-extract-method.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-refactoring-extract-method.htm
deleted file mode 100644
index 0b7e27a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-refactoring-extract-method.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Extract Method Errors
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Extract Method Errors
-    </h1>
-    <p>
-      When you attempt to extract a method, you may get one or more of the following common errors:
-    </p>
-    <ul>
-      <li>
-        <code>Selected block references a local type declared outside the selection</code> A local type declaration is not part of the selection but is referenced by one of the
-        statements selected for extraction. Either extend the selection that it includes the local type declaration or reduce the selection that no reference to the local type
-        declaration is selected.<br>
-      </li>
-      <li>
-        <code>A local type declared in the selected block is referenced outside the selection</code> The selection covers a local type declaration but the type is also referenced
-        outside the selected statements. Either extend the selection that is includes all references to the local type or reduce the selection that the local type declaration
-        isn't selected.<br>
-      </li>
-      <li>
-        <code>Ambiguous return value: selected block contains more than one assignment to local variable</code> More than one assignment to a local variable was found inside the
-        selected block. Either reduce the selection that only one assignment is selected or extend the selection that at least all reference except of one to the local variables
-        are covered by the selection too.<br>
-      </li>
-      <li>
-        <code>Ambiguous return value: expression access to local and return statement selected</code> The selected statement generates more than one return value. This is for
-        example the case if an expression is selected and an expression's argument is modified as well. To remedy this problem extend the selection to cover the read access of
-        the modified argument as well.<br>
-      </li>
-      <li>
-        <code>Selection contains a break statement but the corresponding break target isn't selected</code> To remedy the problem either extend the selection to include the
-        break / continue target or reduce the selection that the break / continue statement isn't covered by the selection.<br>
-      </li>
-      <li>
-        <code>Selection contains a continue statement but the corresponding continue target isn't selected</code> To remedy the problem either extend the selection to include
-        the break / continue target or reduce the selection that the break / continue statement isn't covered by the selection.<br>
-      </li>
-      <li>
-        <code>Selection starts inside a comment</code> Parts of a comment cannot be extracted. Either extend the selection that it covers the whole comment or reduce the selection
-        that the comment isn't covered at all.<br>
-      </li>
-      <li>
-        <code>Selection ends inside a comment</code> Parts of a comment can't be extracted. Either extend the selection that it covers the whole comment or reduce the
-        selection that the comment isn't covered at all.<br>
-      </li>
-      <li>
-        <code>Cannot extract selection that ends in the middle of a statement</code> Adjust selection so 
-        that it fully covers a set of statements or expressions. The users can extend the selection to 
-        a valid range using the <strong>Expand Selection to</strong> in the <a href="ref-menu-edit.htm">Edit menu.</a><br>
-        <a href="ref-menu-edit.htm"></a>
-      </li>
-    </ul>
-    <img src="../images/ngrelc.png" alt="Related concepts" border="0" > 
-    <p>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a><br>
-      <a href="../concepts/concept-refactoring.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-menu-source.htm">Source menu</a><br>
-      <a href="ref-menu-refactor.htm">Refactor menu</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-toolbar-run.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-toolbar-run.htm
deleted file mode 100644
index a6b2e0c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-toolbar-run.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Run and Debug toolbar actions</title>
-</head>
-<body>
-<h1> Run and Debug toolbar actions </h1>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-  Run and Debug toolbar actions
-  </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Toolbar Button </p></th>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> Description </th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../images/org.eclipse.debug.ui/etool16/run_exc.png" align="middle"  alt="Run button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../reference/menus/run/ref-rll_run.htm">Run</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This command re-launches the most recently launched application, or launches the selected resource or active editor depending on the <a href="../reference/preferences/run-debug/ref-launching.htm">launch operation</a> preference settings found on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <b>Run/Debug &gt; Launching</b></a> preference page</p></td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../images/org.eclipse.debug.ui/etool16/debug_exc.png" align="middle"  alt="Debug button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../reference/menus/run/ref-dll_debug.htm">Debug</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This command re-launches the most recently launched application under debugger control,  or launches the selected resource or active editor depending on the <a href="../reference/preferences/run-debug/ref-launching.htm">launch operation</a> preference settings found on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <b>Run/Debug &gt; Launching</b></a> preference page</p></td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/clocdbug.htm">Local Debugging</a><br>
-  <a href="../concepts/cremdbug.htm">Remote Debugging</a> </p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../tasks/task-running_and_debugging.htm">Running and Debugging</a><br>
-  <a href="../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../tasks/task-add_line_breakpoints.htm">Line breakpoints</a><br>
-  <a href="../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../tasks/task-catching_exceptions.htm">Catching exceptions</a> </p>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related Reference" > </p>
-<p> <a href="../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug Preferences</a><br>
-  <a href="../reference/preferences/run-debug/ref-launching.htm">Launching Preferences</a> <br>
-  <a href="../reference/menus/run/ref-menu-run.htm">Run menu actions</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-listcontent.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-listcontent.htm
deleted file mode 100644
index b697f60..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-listcontent.htm
+++ /dev/null

@@ -1,142 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) 2008, 2009 Mateusz Matela, IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      toString() Generator: Content Listing
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      toString() Generator: Content Listing
-    </h1>
-<p>This topic discusses how toString() generator lists contents of arrays and how it limits number of items listed in <code>Collection</code>s and <code>Map</code>s. Used method depends not only on the member type, but also on selected JDK compatibility of the project.</p>
-<h2>Listing contents of Arrays</h2>
-<ul>
-<li><h3>Without limiting number of elements</h3>
-For JDK1.5 and later, generated method uses <code>Arrays.toString()</code>. As this method is not available in JDK1.4, <code>Arrays.asList()</code> is used instead in this case, but only for non-primitive arrays. Primitive arrays are handled with a helper method, showed below.</li>
-<li><h3>Limiting number of elements</h3>
-If the array enclose a non-primitive type, the same solution is used for all versions of JDK: <code>Arrays.asList()</code> with <code>List.subList()</code>. For example, for a member named anArray, generated code looks like this: <code>Arrays.asList(anArray).subList(0, Math.min(anArray.length, maxLen))</code><br>
-In case of primitive arrays, <code>Arrays.asList()</code> cannot be used so in JDK1.5 or lower a helper method is used instead. In JDK1.6 there's another solution: <code>Arrays.toString(Arrays.copyOf(anArray, Math.min(anArray.length, maxLen))</code>. Although copying an array is not an optimal solution, the copied part is usually rather small and efficiency is not affected. A good thing is that a helper method can be avoided.</li>
-<li><h3>Helper method</h3>
-A helper method returns a string listing items of a given array, in the form of <code>[1, 2, 3]</code>. The method iterates over the array and uses <code>instanceof</code> to determine its enclosing type. To make the code shorter, it checks only for types that can actually be passed to it.
-<pre>private String arrayToString(Object array, int len, int maxLen) {
-	StringBuffer stringBuffer = new StringBuffer();
-	len = Math.min(len, maxLen);
-	stringBuffer.append("[");
-	for (int i = 0; i &lt; len; i++) {
-		if (i &gt; 0)
-			stringBuffer.append(", ");
-		if (array instanceof float[])
-			stringBuffer.append(((float[]) array)[i]);
-		if (array instanceof int[])
-			stringBuffer.append(((int[]) array)[i]);
-		if (array instanceof Object[])
-			stringBuffer.append(((Object[]) array)[i]);
-	}
-	stringBuffer.append("]");
-	return stringBuffer.toString();
-}</pre>
-<b>NOTES:</b><ul><li>This method is overwritten every time the generator runs.</li>
-<li>If the number of items is not limited, the method doesn't take the <code>maxLen</code> argument and doesn't use <code>Math.min()</code></li>
-<li>StringBuffer or StringBuilder is used depending on selected JDK compatibility</li>
-</ul>
-</li></ul>
-
-<h2>Listing limited contents of <code>List</code>s</h2>
-<p>The same solution is used for all JDK versions: <code>aList.subList(0, Math.min(aList.size(), maxLen))</code></p>
-
-<h2>Listing limited contents of <code>Collection</code>s (helper method)</h2>
-<p>A <code>Collection</code> cannot be turned into a <code>List</code> without copying its contents (assuming iy isn't a <code>List</code> already), so a helper method is used to iterate over first <code>maxLen</code> elements and build a string out of them:</p>
-<pre>private String toString(Collection collection, int maxLen) {
-	StringBuffer stringBuffer = new StringBuffer();
-	stringBuffer.append("[");
-	int i = 0;
-	for (Iterator iterator = collection.iterator(); iterator.hasNext() &amp;&amp; i &lt; maxLen; i++) {
-		if (i &gt; 0)
-			stringBuffer.append(", ");
-		stringBuffer.append(iterator.next());
-	}
-	stringBuffer.append("]");
-	return stringBuffer.toString();
-}</pre>
-<b>NOTES:</b><ul><li>This method is not overwritten every time the generator runs, so it can be easily customized by hand.</li>
-<li>StringBuilder or StringBuffer is used depending on selected JDK compatibility</li>
-</ul>
-
-<h2>Listing limited contents of <code>Map</code>s</h2>
-<p>In case  of <code>Map</code>s, the same helper method is used as for <code>Collection</code>s only that <code>map.entrySet()</code> is passed to it.</p>
-
-<h2>Summary</h2>
-<p>This table sums up what methods are used in different conditions:</p>
-<table border="10">
-<tr>
-<td></td>
-<th><code>java.util.List</code></th>
-<th><code>java.util.Collection</code></th>
-<th><code>java.util.Map</code></th>
-<th>Array of primitive type</th>
-<th>Array of non-primitive type</th>
-</tr>
-<tr>
-<th>jdk 1.4</th>
-<td>-</td>
-<td>-</td>
-<td>-</td>
-<td>helper method <code>arrayToString(array, len)</code></td>
-<td><code>Arrays.asList(array)</code></td>
-</tr>
-<tr>
-<th>jdk 1.4/1.5, limit elements</th>
-<td><code>member.subList()</code></td>
-<td>helper method <code>toSting(collection, maxLen)</code></td>
-<td>helper method <code>toString(collection, maxLen)</code> with <code>map.entrySet()</code></td>
-<td>helper method <code>arrayToString(array, len, maxLen)</code></td>
-<td><code>Arrays.asList(array).subList()</code></td>
-</tr>
-<tr>
-<th>jdk 1.5</th>
-<td>-</td>
-<td>-</td>
-<td>-</td>
-<td><code>Arrays.toString()</code></td>
-<td><code>Arrays.asList(array)</code></td>
-</tr>
-<tr>
-<th>jdk 1.6</th>
-<td>-</td>
-<td>-</td>
-<td>-</td>
-<td><code>Arrays.toString()</code></td>
-<td><code>Arrays.toString()</code></td>
-</tr>
-<tr>
-<th>jdk 1.6, limit elements</th>
-<td><code>member.subList()</code></td>
-<td>helper method <code>toSting(Collection)</code></td>
-<td>helper method <code>toString(Collection)</code> with <code>map.entrySet()</code></td>
-<td><code>Arrays.toString(Arrays.copyOf(member, ...))</code></td>
-<td><code>Arrays.asList(array).subList()</code></td>
-</tr>
-</table>
-
-
-<h2>Additional notes</h2><ul>
-<li>If a helper method must be generated for at least one member, it is also used for other members when possible. For example, a <code>List</code> is usually handled with <code>subList()</code> method, but if there's another member of <code>Collection</code> (not <code>List</code>) type and toString(collection) is generated, <code>List</code>s are also passed to it. This way the code is shorter and more consistent.</li>
-<li>Where necessary, the code responsible for listing contents is surrounded with null-checking code, for example: <code>array != null ? Arrays.asList(array) : null</code></li>
-<li>If maximum number of listed items is set to 0, the generator uses simple string literal (<code>"[]"</code>) instead of methods described above.</li>  
-</ul>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-	  <a href="ref-dialog-tostring.htm">Generate toString() dialog</a><br>
-	  <a href="ref-tostring-templates.htm">toString() Generator: Format Templates</a><br>
-	  <a href="ref-tostring-styles.htm">toString() Generator: Code Styles</a>
-    </p>
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-styles.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-styles.htm
deleted file mode 100644
index ab5404c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-styles.htm
+++ /dev/null

@@ -1,139 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) 2008, 2009 Mateusz Matela, IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      toString() Generator: Code Styles
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      toString() Generator: Code Styles
-    </h1>
-<p>
-Code style determines how the generated method works and what classes it uses. There are several code styles available to chose from the combo box in generator's <a href="ref-dialog-tostring.htm">dialog</a>:</p>
-<ul>
-<li><h3>String concatenation</h3>
-This style uses simple sum expressions so it's very efficient (compiler uses StringBuilder/StringBuffer to optimize the code) and relatively easy to read and modify. Here's an example outcome in the simplest case:
-<pre>return "FooClass [aFloat=" + aFloat + ", aString=" + aString + ", anInt=" + anInt 
-  + ", anObject=" + anObject + "]";</pre>
-With "Skip null values" option turned on, the code becomes a little harder to read:
-<pre>return "FooClass [aFloat=" + aFloat + ", "
-  + (aString != null ? "aString=" + aString + ", " : "") 
-  + "anInt=" + anInt + ", " 
-  + (anObject != null ? "anObject=" + anObject : "") + "]";</pre>
-</li>
-<li><h3>StringBuilder/StringBuffer</h3>
-This style uses StringBuilder if the project is compatible with JDK1.5 or later and StringBuffer otherwise. StringBuilder is faster (because of lack of synchronization), but only available since JDK1.5.
-<pre>StringBuilder builder = new StringBuilder();
-builder.append("FooClass [aFloat=");
-builder.append(aFloat);
-builder.append(", aString=");
-builder.append(aString);
-builder.append(", anInt=");
-builder.append(anInt);
-builder.append(", anObject=");
-builder.append(anObject);
-builder.append("]");
-return builder.toString();</pre>
-The <b>"Skip null values"</b> option doesn't obfuscate the code as much as previously:
-<pre>StringBuilder builder = new StringBuilder();
-builder.append("FooClass [aFloat=");
-builder.append(aFloat);
-builder.append(", ");
-if (aString != null) {
-	builder.append("aString=");
-	builder.append(aString);
-	builder.append(", ");
-}
-builder.append("anInt=");
-builder.append(anInt);
-builder.append(", ");
-if (anObject != null) {
-	builder.append("anObject=");
-	builder.append(anObject);
-}
-builder.append("]");
-return builder.toString();</pre>
-</li>
-<li><h3>StringBuilder/StringBuffer with chained calls</h3>
-Style very similar to the previous one only that append methods are called in chain. This makes the code shorter and probably easier to read.
-<pre>StringBuilder builder = new StringBuilder();
-builder.append("FooClass [aFloat=").append(aFloat).append(", aString=").append(aString)
-		.append(", anInt=").append(anInt).append(", anObject=").append(anObject).append("]");
-return builder.toString();</pre>
-With <b>"Skip null values"</b> switched on, the chain must be broken:
-<pre>StringBuilder builder = new StringBuilder();
-builder.append("FooClass [aFloat=").append(aFloat).append(", ");
-if (aString != null) {
-	builder.append("aString=").append(aString).append(", ");
-}
-builder.append("anInt=").append(anInt).append(", ");
-if (anObject != null) {
-	builder.append("anObject=").append(anObject);
-}
-builder.append("]");
-return builder.toString();</pre>
-</li>
-<li><h3>String.format()/MessageFormat</h3>
-This style is very pleasant for relatively short list of elements, but with longer ones it becomes hard to see which fields are associated with which variables. Unfortunately, the <b>"Skip null values"</b> option cannot be used with this style.
-<pre>return String.format("FooClass [aFloat=%s, aString=%s, anInt=%s, anObject=%s]",
-  aFloat, aString, anInt, anObject);</pre>
-Because there's no <code>String.format()</code> in JDK 1.4 and ealier, <code>MessageFormat.format()</code> is used instead:
-<pre>return MessageFormat.format("FooClass [aFloat={0}, aString={1}, anInt={2}, anObject={3}]", 
-  new Object[] { new Float(aFloat), aString, new Integer(anInt), anObject });</pre>
-</li>
-<li><h3><a name="custombuilder">Custom toString() builder</a></h3>
-<p>This style uses an external class to build a result string. It can use classes that fulfill the following conditions:</p>
-<ul>
-<li>Provide a public constructor taking a single <code>Object</code> as parameter - it will be passed an object for which the toString() method is called</li>
-<li>Provide methods for appending member information - these are methods with specified name, that take an <code>Object</code> and (optionally) a <code>String</code> (in any order)</li>
-<li>Provide a method for retrieving result - that is a method taking no arguments and returning a <code>String</code></li>
-</ul>
-
-<p>Custom builder requires some additional configuration to work properly. All necessary options can be entered in a dialog box showing up after clicking 'Configure...' button. These options include:</p>
-<ul>
-<li><b>Builder class</b> - a fully qualified name of a class to use. It can be typed in manually or selected from a class search dialog box
-(in this case it's automatically checked if selected class meets the requirements).
-It can be a class declared either directly in current project or in one of included libraries - 
-it just has to be accessible on the build path. For example, ToStringBuilder from the Apache Commons Lang library or
-ToStringCreator from the Spring Framework work very well with this mechanism.</li>
-<li><b>Builder label</b> - any valid java identifier. It will be used to reference the builder object.</li>
-<li><b>Append method</b> - the name of methods to use for appending items. If the class provides many methods with this name, methods taking two arguments (one of them must be <code>String</code>) are preferred over those taking a single argument (additionally, the <code>String</code> argument shall preferably be the first one). If there are versions of the method that take specific argument types, they are also used when possible.</li>
-<li><b>Result method</b> - the name of a method to use for retrieving final result.</li>
-<li><b>Chain invocations</b> - determines whether calls to the <b>append</b> methods should form chains. This option takes effect only for methods that have proper return type (that is, the builder class, or a subclass).</li>
-</ul>
-
-<p>For example, suppose your builder class looks like this:</p>
-<pre>package org.foo.ToStringBuilder2;
-
-public class ToStringBuilder2 {
-	public ToStringBuilder2(Object o) {...}
-	public ToStringBuilder2 appendItem(String s, Object o) {...}
-	public ToStringBuilder2 appendItem(String s, float f) {...}
-	public String getString() {...}
-}</pre>
-<p>
-Of course in this case <b>builder class</b> should be set to <code>"org.foo.ToStringBuilder2"</code>, <b>builder label</b> can be for example <code>"builder"</code>, <b>append method</b> is <code>"appendItem"</code> and <b>result method</b> is <code>"getString"</code>. With <b>chain invocations</b> selected, generated method will look like this:
-</p>
-<pre>ToStringBuilder2 builder = new ToStringBuilder2(this);
-builder.append("aFloat", aFloat).append("aString", aString).append("anInt", new Integer(anInt))
-		.append("anObject", anObject);
-return builder.getString();</pre>
-
-<p>Note that a primitive variable <code>anInt</code> was passed to the builder using wrapper type. This is done for projects using JDK 1.4 and earlier (for later JDKs the compiler does it automatically). In case of <code>aFloat</code> there was a specific method in builder class so no wrapping was required.</p>
-</li>
-</ul>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-	  <a href="ref-dialog-tostring.htm">Generate toString() dialog</a><br>
-	  <a href="ref-tostring-templates.htm">toString() Generator: Format Templates</a><br>
-	  <a href="ref-tostring-listcontent.htm">toString() Generator: Content Listing</a>
-    </p>
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-templates.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-templates.htm
deleted file mode 100644
index c5d2064..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-tostring-templates.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) 2008, 2009 Mateusz Matela, IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      toString() Generator: Format Templates
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      toString() Generator: Format Templates
-    </h1>
-<p>Format templates are used by a simple mechanism that allows you to change format of generated method's output string: beginning, ending, separator, and so on. They look similar to JDT code templates but they don't affect the generated code directly (<a href="ref-tostring-styles.htm">Code Styles</a> are used for that). Here's a list of available template variables:</p>
-<table border="1">
-<tr><td><b>${object.className}</b></td><td>inserts the class name as a simple String</td></tr>
-<tr><td><b>${object.getClassName}</b></td><td>inserts a call to <code>this.getClass.getName()</code></td></tr>
-<tr><td><b>${object.superToString}</b></td><td>inserts a call to <code>super.toString()</code></td></tr>
-<tr><td><b>${object.hashCode}</b></td><td>inserts a call to <code>this.hashCode()</code></td></tr>
-<tr><td><b>${object.identityHashCode}</b></td><td>inserts a call to <code>System.identityHashCode(this)</code></td></tr>
-<tr><td><b>${member.name}</b></td><td>inserts the first member's name</td></tr>
-<tr><td><b>${member.name()}</b></td><td>inserts the first member's name followed by parenthesis in case of methods</td></tr>
-<tr><td><b>${member.value}</b></td><td>inserts the first member's value</td></tr>
-<tr><td><b>${otherMembers}</b></td><td>inserts the remaining members. For each member, the template fragment between the first and the last <b>${member.*}</b> variable is evaluated and appended to the result. The characters between the last <b>${member.*}</b> and <b>${otherMembers}</b> define the separator that is inserted between members (<b>${otherMembers}</b> must stand after the last <b>${member.*}</b> variable).</td></tr></table>
-<p>For the template to work properly, the <b>${otherMembers}</b> variable must be used exactly once in a template and cannot be followed by any <b>${member.*}</b> variable. <b>${object.*}</b> variables can be placed anywhere in the template, although if one is placed in a member related fragment (that is between the first <b>${member.*}</b> variable and <b>${otherMembers}</b>), it will be repeated for every member, which is probably not a sensible solution.</p>
-<p>The description above might seem complicated, but the template format itself is very easy to use. It should all become clear after seeing some working examples.</p>
-<h2>Template examples</h2>
-<ol><li><p>The default template is a good example:</p>
-<pre>${class.name} [${member.name()}=${member.value}, ${otherMembers}]</pre>
-<p>The output string for this template looks like this:</p>
-<pre>FooClass[aFloat=1.0, aString=hello, anInt=10, anObject=null, aCharMethod()=a]</pre>
-</li>
-<li><p>Multiple line output is also available:</p>
-<pre>${object.getClassName} {
-	${member.name}: ${member.value}
-	${otherMembers}
-}</pre> 
-<p>Example result:</p>
-<pre>FooClass {
-	aFloat: 1.0
-	aString: hello
-	anInt: 10
-	anObject: null
-	aCharMethod: a
-}</pre>
-</li>
-<li><p>If you enclose a member in braces, don't forget to do the same with <b>${otherMembers}</b> variable:</p>
-<pre>{${member.name}=${member.value}},
-{${otherMembers}}</pre>
-<p>Here's the effect:</p>
-<pre>{aFloat=1.0},
-{aString=hello},
-{anInt=10},
-{anObject=null},
-{aCharMethod=a}</pre>
-</li>
-<li><p><b>${object.*}</b> variables can be used at the beginning and at the end of the template:</p>
-<pre>${object.getClassName} (hashcode:${object.hashCode})
-	members: ${member.name} = ${member.value}; ${otherMembers}
-[super: ${object.superToString}]</pre>
-<p>This template would result in an output similar to this:</p>
-<pre>FooClass (hashCode:232198409832)
-	members: aFloat = 1.0; aString = hello; anInt = 10; anObject = null; aCharMethod = a
-[super: SuperFooClass[aField=null]]</pre>
-</li>
-</ol>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-	  <a href="ref-dialog-tostring.htm">Generate toString() dialog</a><br>
-	  <a href="ref-tostring-styles.htm">toString() Generator: Code Styles</a><br>
-	  <a href="ref-tostring-listcontent.htm">toString() Generator: Content Listing</a>
-    </p>
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-annotation.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-annotation.htm
deleted file mode 100644
index ded3174..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-annotation.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Annotation Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Java Annotation Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.NewAnnotationCreationWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Annotation Type wizard">
-    <b>New Java Annotation Type</b></a> wizard
-    helps you to create a new Java Annotation in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="Java Annotation options">
-      <caption>
-        Java Annotation Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new annotation. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new annotation. You can select either this option or the Enclosing Type option, below. Either type a valid
-        package name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new annotation. You can select either this option or the Package option, above.
-        Either type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new annotation.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new annotation.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new class where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-class.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-class.htm
deleted file mode 100644
index 36a4578..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-class.htm
+++ /dev/null

@@ -1,143 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Class Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Java Class Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.NewClassCreationWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Class wizard">
-    <b>New Java Class</b></a> wizard
-    helps you to create a new Java class in in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="New Java class settings">
-      <caption>
-        Java Class Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new class. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new class. You can select either this option or the Enclosing Type option, below. Either type a valid package
-        name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new class. You can select either this option or the Package option, above. Either
-        type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new class.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new class.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-
-            <li>abstract</li>
-
-            <li>final</li>
-
-            <li>static (only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Superclass</td>
-
-        <td align="left" valign="top">Type or click <span class="control">Browse</span> to select a superclass for this class.</td>
-
-        <td align="left" valign="top">The type (not the compilation unit!) that was selected when the wizard has been started or &lt;java.lang.Object&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Interfaces</td>
-
-        <td align="left" valign="top">Click <span class="control">Add</span> to choose interfaces that the new class implements.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Which method stubs would you like to create?</td>
-
-        <td align="left" valign="top">
-          <p>Choose the method stubs to create in this class:</p>
-
-          <ul>
-            <li>public static void main(String [] args): Adds a main method stub to the new class.</li>
-
-            <li>Constructors from superclass: Copies the constructors from the new class's superclass and adds these stubs to the new class.</li>
-
-            <li>Inherited abstract methods: Adds to the new class stubs of any abstract methods from superclasses or methods of interfaces that need to be implemented.</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">Inherited abstract methods enabled</td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new class where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-	<p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-	<p>
-     <a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-enum.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-enum.htm
deleted file mode 100644
index c4ebb3a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-enum.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Enum Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Java Enum Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.NewEnumCreationWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Enum Type wizard">
-    <b>New Java Enum Type</b></a> wizard
-    helps you to create a new Java enum in in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="New Java enum options">
-      <caption>
-        Java Enum Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new enum. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new enum. You can select either this option or the Enclosing Type option, below. Either type a valid package
-        name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new enum. You can select either this option or the Package option, above. Either
-        type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new enum.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new enum.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Interfaces</td>
-
-        <td align="left" valign="top">Click <span class="control">Add</span> to choose interfaces that the new enum implements.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new enum where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a>
-     </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm
deleted file mode 100644
index 3ae6265..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-externalize-strings.htm
+++ /dev/null

@@ -1,313 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Externalize Strings Wizard
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Externalize Strings Wizard
-    </h1>
-    <p>
-      The Externalize Strings wizard allows you to refactor a compilation unit such that strings used in the compilation unit can be translated to different languages. The wizard can be invoked on new, unprocessed files, but also modify
-      already translated pages. It also allows you
-      revert changes done by a previous invocation of the wizard.
-    </p>
-    <p>
-      On the first page of the wizard you can specify how the strings found in the compilation unit should be externalized. It is also possible to internalize strings
-      which have been externalized before. 
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Externalize strings wizard settings">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Field
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Use Eclipse's string externalization mechanism
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              If unchecked the standard externalization mechanism is used, otherwise the new
-              <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/documents/3.1/message_bundles.html">Eclipse string externalization mechanism</a> is used.
-              <br><em>Note:</em> This field is only present if the project build path contains the <code>org.eclipse.osgi.util.NLS</code> class.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Enter common prefix for generated keys
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies an optional prefix for all newly generated key. A good practice is to use the name of the compilation unit so entries in the property files can easily be grouped.
-            </p>
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">
-            <p>
-              Strings to externalize
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Displays the list of all strings in the file. When non-externalized strings are found, the list ill be filtered to only show the new strings with proposed keys and values. To control this filter, use the checkbox on top of the table.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Externalize
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Marks the selected strings to be externalized. Externalized strings will be placed in a property file
-              and the code will be changed to a lookup to the property file.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Ignored
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Marks the selected strings to be ignored from externalization. These strings
-              will be marked with a '//$NON_NLS' comment and the compiler will ignore this
-              string when warning about non-externalized strings.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Internalize
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Marks the selected strings to be internalized again: This brings the code
-              back in its original state before the externalize wizard was applied: The entry
-              in the property file will be removed, and a '//$NON_NLS' comment
-              will be removed.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Edit...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens a dialog for entering a new key.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Context
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Displays the occurrence of the string in the context of the compilation unit.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Accessor class
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The class used to access the property file. Press <strong>Configure...</strong> to open the <strong>Configure Accessor Class</strong> dialog.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2 class="Head">
-      Configure Accessor Class
-    </h2>
-    <p>
-      This dialog specifies the name and location of the property file and its accessor class. An accessor class is used to retrieve strings
-      stored in the property file given a key.
-    </p>
-    <p>
-    Accessor class settings:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Accessor class settings">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      
-      <tbody>
-      	<tr>
-          <td valign="top">
-            <p>
-              Source folder
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The source folder to store the accessor class in.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Package
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The location for the accessor class.
-            </p>
-          </td>
-        </tr>
-      	<tr>
-          <td valign="top">
-            <p>
-              Class name
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The name of the class to access the resource bundle.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Substitution pattern
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Specifies the source pattern to replace the string to externalize with.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-    Property file settings:
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Property file settings">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Option
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      
-      <tbody>
-      	<tr>
-          <td valign="top">
-            <p>
-              Source folder
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The source folder to store the property file in.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Package
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The location for the property file.
-            </p>
-          </td>
-        </tr>
-      	<tr>
-          <td valign="top">
-            <p>
-              Property file name
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              The name of the property file.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ></p>
-      <p>
-      <a href="../concepts/concept-string-externalization.htm">String externalization</a><br>
-      <a href="http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-core-home/documents/3.1/message_bundles.html">Eclipse string externalization mechanism</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" ></p>
-      <p>
-      <a href="../tasks/tasks-206.htm">Externalizing strings</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="../reference/ref-menu-source.htm">Source actions</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-interface.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-interface.htm
deleted file mode 100644
index a82caec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-interface.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Interface Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Java Interface Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.NewInterfaceCreationWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Interface wizard">
-    <b>New Java Interface</b></a> wizard
-    helps you to create a new Java interface in a Java project.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="New Java interface options">
-      <caption>
-        Java Interface Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Enter a source folder for the new interface. Either type a valid source folder path or click <span class="control">Browse</span> to select a
-        source folder via a dialog.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Package</td>
-
-        <td align="left" valign="top">Enter a package to contain the new interface. You can select either this option or the Enclosing Type option, below. Either type a valid
-        package name or click <span class="control">Browse</span> to select a package via a dialog.</td>
-
-        <td align="left" valign="top">The package of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enclosing type</td>
-
-        <td align="left" valign="top">Select this option to choose a type in which to enclose the new interface. You can select either this option or the Package option, above.
-        Either type a valid name in the field or click <span class="control">Browse</span> to select a type via a dialog.</td>
-
-        <td align="left" valign="top">The type or the primary type of the compilation unit that was selected when the wizard has been started or &lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new interface.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Modifiers</td>
-
-        <td align="left" valign="top">
-          <p>Select one or more access modifiers for the new interface.</p>
-
-          <ul>
-            <li>Either public, default, private, or protected (private and protected are only available if you specify an enclosing type)</li>
-
-            <li>static (only available if you specify an enclosing type)</li>
-          </ul>
-        </td>
-
-        <td align="left" valign="top">public</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Extended interfaces</td>
-
-        <td align="left" valign="top">Click Add to choose interfaces that the new interface extends.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">Do you want to add comments?</td>
-
-        <td align="left" valign="top">When selected, the wizard adds comments to the new class where appropriate.</td>
-
-        <td align="left" valign="top">Do not add comments</td>
-      </tr>
-      
-    </table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a>
-     </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-java-project.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-java-project.htm
deleted file mode 100644
index 15c9ab6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-java-project.htm
+++ /dev/null

@@ -1,284 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Project Wizard</title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Java Project Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.JavaProjectWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Project wizard">
-    <b>New Java Project</b></a> wizard
-    helps you create a new Java project in the workbench.</p>
-
-    <h2>Project name page</h2>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="Project name page">
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Project name</td>
-
-        <td align="left" valign="top">Type a name for the new project.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-
-         <tr>
-          <td valign="top">
-            Contents
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Create new project in workspace:</strong>
-              </dt>
-              <dd>
-                When selected, the New Project Wizard will create a new project with the specified name in the workspace.
-              </dd>
-              <dt>
-                <strong>Create project from existing source:</strong>
-              </dt>
-              <dd>
-                 When selected, you can specify the location from which the New Java Project Wizard will retrieve
-                 an existing Java project. In this case the wizard will analyze the existing project and set up the
-                 build path automatically.
-                 <br>Click on <strong>Browse...</strong> to browse for a location of an existing Java project.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-             workspace
-          </td>
-        </tr>
-      
-         <tr>
-          <td valign="top">
-            JRE
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Use default JRE:</strong>
-              </dt>
-              <dd>
-                When selected, the New Java Project Wizard creates a new Java project which uses the workspace default JRE.
-                The default JRE can be configured on the <a href="./preferences/java/debug/ref-installed_jres.htm">Java &gt; Installed JREs</a> preference page.<br>
-                The project will also use the default compiler compliance which can be configured on the <a href="preferences/java/ref-preferences-compiler.htm">Java &gt; Compiler</a> preference page.<br>
-                Click on <b>Configure default...</b> to configure the default JRE and compiler compliance.
-              </dd>
-              <dt>
-                <strong>Use project specific JRE:</strong>
-              </dt>
-              <dd>
-                 When selected, you can explicitly specify the JRE to be used for the new Java project. The new project will use a compiler compliance
-                 which matches the version of the selected JRE.
-              </dd>
-              <dt>
-                <strong>Use an execution environment JRE:</strong>
-              </dt>
-              <dd>
-                 When selected, you can specify an execution environment to be used for the new Java project. The new project will use a compiler compliance
-                 which fits best the selected execution environment.<br>
-                 Execution environments can be configured on the <a href="preferences/java/debug/ref-execution_environments.htm">Java &gt; Installed JREs &gt; Execution Environments</a> preference page.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-            Use default JRE
-          </td>
-        </tr>
-      
-         <tr>
-          <td valign="top">
-            Project layout
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Use project folder as root for sources and class files:</strong>
-              </dt>
-              <dd>
-                When selected, the project folder is used both as source folder and as output folder for class files.
-              </dd>
-              <dt>
-                <strong>Create separate folders for sources and class files:</strong>
-              </dt>
-              <dd>
-                When selected, the New Java Project Wizard creates a source folder for Java source files and an output folder which holds the class files of the project.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-            Create separate folders for sources and class files
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">
-            Working sets
-          </td>
-          <td valign="top">
-            <dl>
-              <dt>
-                <strong>Add project to working sets:</strong>
-              </dt>
-              <dd>
-                When selected, the new project will be added to the working sets shown in <strong>Working Sets</strong> drop down field. The drop down field
-                shows a list of previous selected working sets.<br>
-                Click on <strong>Select...</strong> to select working sets to which to add the new project.
-              </dd>
-            </dl>
-          </td>
-          <td valign="top">
-            Depends on the context from which the wizard has been started
-          </td>
-        </tr>
-      
-    </table>
-
-    <h2>Java Build Path page</h2>
-
-    <p>You can skip this page by pressing <span class="control">Finish</span> on the first page. Otherwise press <span class="control">Next</span> to configure the Java build path.
-    </p>    
-    The Java build path consist of source, library and project entries. The user interface is the same as for the <a href="../reference/ref-properties-build-path.htm">Build Path</a> property page, except for
-    the source tab:
-
-    <h2>Source tab</h2>
-
-    <p>Source folders are top-level folders in the project hierarchy. They are the root of packages containing .java files. 
-    The compiler will translate the contained files to .class files that will be written to the output folder.</p>
-<p>Source folders allow to structure the project, for example to separate 
-test from the application in two source folders. Within a source folder, a more detailed structuring can be acived by using packages.</p> 
-<p>Each source folder can define an exclusion filter to specify which 
-resources inside the folder should not be visible to the compiler.</p>
-<p>Resources existing in source folders are copied to the output folder unless the setting in the <a href="preferences/java/compiler/ref-preferences-building.htm">Java &gt; Compiler &gt; Building</a> preference
-    page specifies that the resource is filtered. The output folder is defined per project except if a source folder specifies its own output folder.</p>
-
-    <p>The tree shows the project as it will look like when switching to the package explorer. Several operations can be executed 
-	on this tree to change the structure of the project.</p>
-
-<table border="1" cellspacing="0" cellpadding= "5" summary="Source folder options" width="600">
-
-	<tbody>
-		<tr>
-			<th>Icon</th>
-
-			<th>Option</th>
-
-			<th>Description</th>
-		</tr>
-
-		<tr>
-			<td align="center" valign="middle" width="5%"><img src="../images/org.eclipse.jdt.ui/etool16/newpackfolder_wiz.gif" alt="Add to build path" border="0" ></td>
-
-			<td align="center" valign="middle" width="20%">Add source folder</td>
-
-			<td align="left" valign="top">Add a folder to the Java build path as source folder.</td>
-		</tr>
-		
-		<tr>
-			<td align="center" valign="middle" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/add_linked_source_to_buildpath.gif" alt="Link additional source to project" border="0" ></td>
-
-			<td align="center" valign="middle" width="20%">Link additional source to project</td>
-
-			<td align="left" valign="top">Add a link to a folder in the file system as source folder to the Java build path.
-			</td>
-		</tr>
-		
-		<tr>
-			<td align="center" valign="middle" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/remove_as_source_folder.gif" alt="Remove from buildpath" border="0" ></td>
-
-			<td align="center" valign="middle" width="20%">Remove from buildpath</td>
-
-			<td align="left" valign="top">Remove a source folder from the Java build path and change it into a normal folder.</td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="middle" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/exclusion_filter_attrib.png" alt="Exclude" border="0" ></td>
-
-			<td align="center" valign="middle" width="20%">Exclude</td>
-
-			<td align="left" valign="top">Add a resource to the exclusion filter of it's parent source folder. 
-			The excluded resource and all its children are no longer visible to the compiler.
-			</td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="middle" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/inclusion_filter_attrib.png" alt="Include" border="0" ></td>
-
-			<td align="center" valign="middle" width="20%">Include</td>
-
-			<td align="left" valign="top">Includes a previously excluded resource.</td>
-
-		</tr>
-
-		<tr>
-			<td align="center" valign="middle" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/configure_buildpath_filters.png" alt="Configure source folder properties" border="0" ></td>
-
-			<td align="center" valign="middle" width="20%">Configure source folder properties</td>
-
-			<td align="left" valign="top"><p>The edit source folder property menu has two actions</p>
-				<ol>
-				<li><strong>Configure Inclusion / Exclusions Filters</strong>: Customize the inclusion and exclusion filters by defining string patterns.
-				It is possible to use wildcard in patters (i.e. to exclude all java files which 
-				start with &quot;Test&quot; write &quot;Test*.java&quot;).</li>
-				<li><strong>Configure Output Folder</strong>: Change the output folder for a source folder. This action is only enabled if
-				<strong>Allow output folders for source folders</strong> is enabled.</li>
-				</ol></td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="middle" width="05%"><img src="../images/org.eclipse.jdt.ui/elcl16/clear_co.png" alt="Undo all changes" border="0" ></td>
-
-			<td align="center" valign="middle" width="20%">Undo all changes</td>
-
-			<td align="left" valign="top">All changes that have been applied to the project in this wizard will be withdrawn and the original 
-				state of the project is reconstructed.
-			</td>
-		</tr>
-
-		<tr>
-			<td align="center" valign="middle" width="05%">&nbsp;</td>
-
-			<td align="center" valign="middle" width="20%">Allow output folders for source folders</td>
-
-			<td align="left" valign="top">If enabled, each source folder can have its own output folder. Otherwise all source folders will use the
-			default output folder.</td>
-		</tr>
-	</tbody>
-</table>
-
-<p>A shorter description of all operations is visible in the <strong>Details</strong> pane below the project tree.</p>
-    
-    <h2>Library tab, Project tab and Order Tab</h2>
-    See <a href="../reference/ref-properties-build-path.htm">Build Path</a> property page for more details.
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concept-java-project.htm">Java projects</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a>
-    </p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-package.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-package.htm
deleted file mode 100644
index 8cbe974..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-package.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Package Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Java Package Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.NewPackageCreationWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Package wizard">
-    <b>New Java Package</b></a> wizard
-    helps you create a folder corresponding to a new Java package. The corresponding folder of the default package always exists, and therefore doesn't have to be
-    created.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="Java Package Options">
-      <caption>
-        Java Package Options<br>
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Source folder</td>
-
-        <td align="left" valign="top">Type or browse to select a container (project or folder) for the new package.</td>
-
-        <td align="left" valign="top">The source folder of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Name</td>
-
-        <td align="left" valign="top">Type a name for the new package</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-    </table>
-
-     <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-     <p><a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-refactorings.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-refactorings.htm
deleted file mode 100644
index cece44f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-refactorings.htm
+++ /dev/null

@@ -1,116 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Refactoring Wizard
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Refactoring Wizard
-    </h1>
-    <p>
-      A dialog based user interface guides you through the steps necessary to execute a selected refactoring.
-      Depending on the complexity of the refactoring, either a wizard or a simple dialog is used to gather information that is required for the refactoring.
-    </p>
-
-    <h2>
-      Input pages
-    </h2>
-    <p>
-      The input pages gather information that is required for the refactoring. 
-      After you have provided the required input you can click <strong>Ok</strong> or <strong>Finish</strong> to carry out the refactoring without previewing
-      the results. If you want to preview the changes press <strong>Preview</strong> or <strong>Next</strong></p>
-    <h2>
-      Preview page
-    </h2>
-    <p>
-      The JDT allows you to preview the results of a refactoring action before you execute it.
-    </p>
-    <p>
-      The preview page consists of two parts:
-    </p>
-    <ul>
-      <li>
-        <p>A tree at the top containing all Java elements affected by the refactoring. Each top-level 
-        node in the tree represents one compilation unit.</p>
-        <p>Some refactorings allow to filter the tree by different kind of changes made by the refactoring.
-        Use the <b>Filter Changes</b> drop down to change the filtering.</p>
-      </li>
-      <li>
-        A compare viewer at the bottom. The left side of the compare viewer shows the original, the right side displays the refactored source.
-      </li>
-    </ul>
-    <h2>
-      Problem page
-    </h2>
-    <p>
-      The Refactoring Problem page indicates if there are suspected, potential, or definite problems with the refactoring action you are attempting.
-    </p>
-    <p>
-      Four types of problems are possible:
-    </p>
-    <dl>
-      <dt>
-        Information
-      </dt>
-      <dd>
-        A problem described as Information will not affect the refactoring in any way, nor will it negatively affect the code in the workbench. You can most likely ignore this type of
-        problem.
-      </dd>
-      <dt>
-        Warnings
-      </dt>
-      <dd>
-        Warnings attempt to predict compiler warnings. This type of problem most likely will not negatively affect the code in your workbench.
-      </dd>
-      <dt>
-        Errors
-      </dt>
-      <dd>
-        A problem described as an Error is very likely to cause compiler errors or change your workbench code semantically. You can choose to continue with the refactoring in spite of these
-        errors, although it is not recommended.
-      </dd>
-      <dt>
-        Stop problems
-      </dt>
-      <dd>
-        This type of problem prevents the refactoring from taking place. For example, if you select a comment and choose the Extract Method command from it, the
-        workbench will issue a stop problem on the refactoring attempt because you cannot extract a comment.
-	  </dd>
-    </dl>
-    <p>
-      If there aren't any stop problems then the refactoring can be carried out by pressing the <strong>
-      Finish</strong> button. To preview the results of the refactoring action, press the
-      <strong>Next &gt;</strong> button.
-    </p>
-
-    <h2>
-    	Refactoring without Dialog
-    </h2>
-    <p>
-    	It is also possible to rename a Java element without showing a dialog. This can be enabled and disabled on the
-    	<a href="preferences/ref-preferences-java.htm">Java</a> preference page. If enabled, then the new name for an Java element 
-    	can be typed into the editor when the rename refactoring is invoked.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concept-refactoring.htm">Refactoring support</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="ref-menu-refactor.htm">Refactoring actions</a><br>
-      <a href="ref-icons.htm">Icons</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-scrapbook.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-scrapbook.htm
deleted file mode 100644
index edefc27..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-scrapbook.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Java Scrapbook Page Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Java Scrapbook Page Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.debug.ui.snippetEditor.NewSnippetFileCreationWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Scrapbook wizard">
-    <b>New Java Scrapbook Page</b></a> wizard
-    helps you to create a new Java scrapbook page in a project.</p>
-
-    <table border="1" cellspacing="0" cellpadding= "5" summary="Create Java Scrapbook Page Options">
-      <caption>
-        Create Java Scrapbook Page Options
-      </caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Enter or select the parent folder</td>
-
-        <td align="left" valign="top">Type or browse the hierarchy below to select a container (project or folder) for the scrapbook page.</td>
-
-        <td align="left" valign="top">The container of the selected element</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">File name</td>
-
-        <td align="left" valign="top">Type a name for the new file. The "<em>.jpage</em> " extension is appended automatically when not added already.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-    </table>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ></p>
-    <p>
-     <a href="../reference/views/ref-view-scrapbook.htm">Java scrapbook page</a><br>
-     <a href="../reference/ref-menu-file.htm">File actions</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-source-folder.htm b/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-source-folder.htm
deleted file mode 100644
index 367b231..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/ref-wizard-source-folder.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>New Source Folder Wizard</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-
-  <body>
-    <h1>New Source Folder Wizard</h1>
-
-    <p>The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.ui.wizards.NewSourceFolderCreationWizard)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Source Folder wizard">
-    <b>New Source Folder</b></a> wizard
-    helps you to create a new source folder to a Java project.</p>
-
-    <p>Note that a new source folder can not be nested in existing source folders or in an output folder. You can choose to add exclusion filters to the other nesting source folders or the
-    wizard will suggest to replace the nesting classpath entry with the new created entry. The wizard will also suggest to change the output location.</p>
-
-    <table border="1" cellspacing="0" cellpadding="5" summary="New Source Folder options">
-      <caption>
-        New Source Folder Options</caption>
-
-      <tr>
-        <th>Option</th>
-
-        <th>Description</th>
-
-        <th>Default</th>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Project name</td>
-
-        <td align="left" valign="top">Enter a project to contain the new source folder. Either type a valid project name or click <span class="control">Browse</span> to select a
-        project via a dialog.</td>
-
-        <td align="left" valign="top">The project of the element that was selected when the wizard has been started.</td>
-      </tr>
-
-      <tr>
-        <td align="left" valign="top">Folder name</td>
-
-        <td align="left" valign="top">Type a path for the new source folder. The path is relative to the selected project.</td>
-
-        <td align="left" valign="top">&lt;blank&gt;</td>
-      </tr>
-      
-      <tr>
-        <td align="left" valign="top">Update exclusion filter in other source folders to solve nesting</td>
-
-        <td align="left" valign="top">Select to modify existing source folder's exclusion filters to solve nesting problems. For example if there is an existing source folder <i>src</i> and a folder <i>src/inner</i> is created, the source folder <i>src</i> will be updated to have a exclusion filter <i>src/inner</i>.</td>
-
-        <td align="left" valign="top">Off</td>
-      </tr>
-    </table>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-    <p>
-     <a href="../concepts/concept-java-project.htm">Java projects</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-     <a href="../reference/ref-menu-file.htm">File actions</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views-breakpoint_set_hitcount_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views-breakpoint_set_hitcount_dialog.PNG
deleted file mode 100644
index d8957d1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views-breakpoint_set_hitcount_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_accesscontext.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_accesscontext.PNG
deleted file mode 100644
index 35522f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_accesscontext.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_addexceptiondialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_addexceptiondialog.PNG
deleted file mode 100644
index 0e1e4e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_addexceptiondialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_caughtcontext.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_caughtcontext.PNG
deleted file mode 100644
index 28a2045..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_caughtcontext.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_defaultworkingset_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_defaultworkingset_dialog.PNG
deleted file mode 100644
index 704b26b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_defaultworkingset_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_entrycontext.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_entrycontext.PNG
deleted file mode 100644
index 72dcf5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_entrycontext.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_exitcontext.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_exitcontext.PNG
deleted file mode 100644
index ea4669f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_exitcontext.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbyadvanced_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbyadvanced_dialog.PNG
deleted file mode 100644
index 735365a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbyadvanced_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbymenu.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbymenu.PNG
deleted file mode 100644
index b97167b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_groupbymenu.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_modcontext.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_modcontext.PNG
deleted file mode 100644
index 3d84dcd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_modcontext.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties.PNG
deleted file mode 100644
index ef998cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties_dialog.PNG
deleted file mode 100644
index 00a7fec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_properties_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_select_default_workingset_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_select_default_workingset_dialog.PNG
deleted file mode 100644
index fa0fca1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_select_default_workingset_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_skipall_example.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_skipall_example.PNG
deleted file mode 100644
index c5d7657..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_skipall_example.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_uncaughtcontext.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_uncaughtcontext.PNG
deleted file mode 100644
index 178c980..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_uncaughtcontext.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingset_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingset_dialog.PNG
deleted file mode 100644
index 704b26b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingset_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingsets.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingsets.PNG
deleted file mode 100644
index a3f8b8b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoint_workingsets.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoints_view.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoints_view.PNG
deleted file mode 100644
index a14dde8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/images/ref-views_breakpoints_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-access_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-access_contextaction.htm
deleted file mode 100644
index 0397fd6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-access_contextaction.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Watchpoint Access</title>
-</head>
-<body>
-<h1>Watchpoint Access</h1>
-<p>Select the <strong>Access</strong> command  to change if the currently selected watchpoint will suspend when its associated field is accessed or read.</p>
-<p><img src="images/ref-views_breakpoint_accesscontext.PNG" alt="Watchpoint Access"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-access_option.htm">Watchpoint Access Option</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-addexception_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-addexception_viewaction.htm
deleted file mode 100644
index b9fc53b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-addexception_viewaction.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Add Java Exception Breakpoint</title>
-</head>
-<body>
-<h1> Add Java Exception Breakpoint </h1>
-<p> Select the <strong>Add Exception Breakpoint</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png" alt="Add Java Exception Breakpoint"> ] to add a Java exception breakpoint. </p>
-<p>In the resulting dialog: </p>
-<ul>
-  <li> In the <strong>Choose an Exception</strong> field, type a string that is contained in the name of the exception you want to add. You can use wildcards as needed
-    (&quot;<em>*</em> &quot; for any string and &quot;<em>?</em> &quot; for any character). </li>
-  <li> In the <strong>Matching types</strong> list , select the exception you want to add. </li>
-  <li> Select <strong>Caught</strong> and <strong>Uncaught</strong> as needed to indicate on which exception type you want to suspend the program. </li>
-</ul>
-<p>The <strong>Add Java Exception Breakpoint Dialog</strong>.</p>
-<p> <img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_addexceptiondialog.PNG" alt="Add Java Exception Breakpoint Dialog"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p><a href="../../../tasks/task-catching_exceptions.htm">Catching Java exceptions</a><br>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a> <br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> <br>
-  <a href="../../../reference/breakpoints/ref-caught_option.htm">Caught Exception Option</a><br>
-  <a href="../../../reference/breakpoints/ref-uncaught_option.htm">Uncaught Exception Option</a></p>
-<p> <br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-breakpoints_view.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-breakpoints_view.htm
deleted file mode 100644
index 1f13412..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-breakpoints_view.htm
+++ /dev/null

@@ -1,221 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoints View</title>
-</head>
-<body>
-<h1> Breakpoints View </h1>
-<p> The <strong>Breakpoints View</strong> lists all the breakpoints you currently have set in your workspace. </p>
-<p>You can double-click a breakpoint to display its location in the editor (if applicable). You can also enable or disable breakpoints, delete them, add new ones, group them by working set, or set hit counts. </p>
-<p>In the example shown below the <strong><a href="../../../reference/views/breakpoints/ref-groupby_viewaction.htm">Group by &gt; Breakpoint Types</a></strong> option is turned on.</p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoints_view.PNG" alt="Breakpoints View"> </p>
-<p>The commands available in the <strong>Breakpoints View</strong> are listed below.</p>
-<table border="1" cellpadding="5" cellspacing="0" summary="The commands available in the Breakpoints View">
-  <caption>
-  Breakpoints View Commands
-  </caption>
-  <thead>
-    <tr>
-      <th width="71" colspan="1" rowspan="1"> <p> Command </p></th>
-      <th width="209" colspan="1" rowspan="1"> <p> Name </p></th>
-      <th width="540" colspan="1" rowspan="1"> <p> Description </p></th>
-      <th width="193" colspan="1" rowspan="1"> <p> Availability </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-access_contextaction.htm"><strong>Access</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if the selected watchpoint should suspend on access to its associated field. </td>
-      <td colspan="1" valign="top" align="left">Context menu</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/exc_catch.png" alt="Add Exception Breakpoint"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-addexception_viewaction.htm"><strong>Add Exception Breakpoint</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Opens the create exception breakpoint dialog.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-properties_contextaction.htm"><strong>Breakpoint Properties...</strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the breakpoints properties dialog. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-caught_contextaction.htm"><strong>Caught</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if the selected exception breakpoint should suspend when the specified type of exception is caught. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/collapseall.png" alt="Collapse All"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-collapseall.htm"><strong>Collapse All</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Collapses all of the items in the view.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-copy.htm"><strong>Copy</strong></a></td>
-      <td colspan="1" valign="top" align="left">Copies the selected breakpoints to the system clipboard. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/disabled_co.png" alt="Disabled"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-disable_contextaction.htm"><strong>Disable</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes the selected breakpoint(s) to be disabled.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/enabled_co.png" alt="Enable"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-enable_contextaction.htm"><strong>Enable</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes the selected breakpoint(s) to be enabled.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-entry_contextaction.htm"><strong>Entry</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if the selected method breakpoint should suspend on entry to the associated method. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-exit_contextaction.htm"><strong>Exit</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if the selected method breakpoint should suspend on exit from the associated method. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/expandall.png" alt="Expand All"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-expandall_viewaction.htm"><strong>Expand All</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Expands all of the items in the view.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/export_brkpts.png" alt="Export Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-export_contextaction.htm"><strong>Export Breakpoints...</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Opens the export breakpoints wizard.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.ui/elcl16/goto_input.png" alt="Go to File"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-gotofile_viewaction.htm"><strong>Go to File </strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the corresponding location of the breakpoint in the java editor. </td>
-      <td colspan="1" valign="top" align="left">Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-groupby_viewaction.htm"><strong>Group By... </strong></a></td>
-      <td colspan="1" valign="top" align="left">Allows you to select an alternate grouping for your breakpoints or create your own. </td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png" alt="Hit Count"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-hitcount_contextaction.htm"><strong>Hit Count</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Allows you to set or change the hit count for the selected breakpoint.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/import_brkpts.png" alt="Import Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-import_contextaction.htm"><strong>Import Breakpoints... </strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the import breakpoints wizard. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/synced.png" alt="Link with View"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-linkwith_viewaction.htm"><strong>Link with View </strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if the breakpoints should be linked to the Debug View. </td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-modification_contextaction.htm"><strong>Modification</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if the selected watchpoint should suspend when its associated field is modified. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/paste_edit.png" alt="Paste Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-paste.htm"><strong>Paste</strong></a></td>
-      <td colspan="1" valign="top" align="left">Pastes copied breakpoints into the view.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-removeall_viewaction.htm"><strong>Remove All </strong></a></td>
-      <td colspan="1" valign="top" align="left">Removes all breakpoints from the view. </td>
-      <td colspan="1" valign="top" align="left">Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/rem_co.png" alt="Remove Selected Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-remove_viewaction.htm"><strong>Remove Selected Breakpoints</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Removes only the selected breakpoint(s) from the view.</td>
-      <td colspan="1" valign="top" align="left">Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-selectall.htm"><strong>Select All </strong></a></td>
-      <td colspan="1" valign="top" align="left">Selects all of the breakpoints in the view.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/brkp_grp.png" alt="Select Defautl Working Sets"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-selectdefaultws_viewaction.htm"><strong>Select Default Working Set</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Allows you to choose which working set will be the default one. </td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/package_obj.png" alt="Show Qualified Names"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-showqualified.htm"><strong>Show Qualified Names</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Changes if qualified names are shown or not.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/debugt_obj.png" alt="Show Supported Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-showsupported_viewaction.htm"><strong>Show Supported Breakpoints </strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if only supported breakpoints should be shown or not. </td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/skip_brkp.png" alt="Skip All Breakpoints"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-skipall_viewaction.htm"><strong>Skip All </strong></a></td>
-      <td colspan="1" valign="top" align="left">Sets all breakpoints to be skipped.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/suspend_co.png" alt="Suspend..."></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-suspendpolicy_contextaction.htm"><strong>Suspend </strong></a></td>
-      <td colspan="1" valign="top" align="left">Allows you to choose what to suspend when the selected breakpoint is hit.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-uncaught_contextaction.htm"><strong>Uncaught</strong></a></td>
-      <td colspan="1" valign="top" align="left">Changes if the selected exception breakpoint should suspend when the specified type of exception is not caught. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/breakpoints/ref-workingsets_viewaction.htm"><strong>Working Sets... </strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the working sets dialog.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a> <br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-apply_hit_count.htm">Applying hit counts</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching Java exceptions</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-enable_disable_breakpoints.htm">Enabling and disabling breakpoints</a><br>
-  <a href="../../../tasks/task-manage_conditional_breakpoint.htm">Managing conditional breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../ref-viewsandeditors.htm">Views and editors</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-caught_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-caught_contextaction.htm
deleted file mode 100644
index 7ff9eae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-caught_contextaction.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Exception Breakpoint Caught</title>
-</head>
-<body>
-<h1>Exception Breakpoint Caught</h1>
-<p>Select the <strong>Caught</strong> command  to change if the currently selected Java exception breakpoint will suspend on caught exceptions of the same type. </p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_caughtcontext.PNG" alt="Exception Breakpoint Caught"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching Java exceptions</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-caught_option.htm">Caught Exception Option</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-disable_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-disable_contextaction.htm
deleted file mode 100644
index a41ca9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-disable_contextaction.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Disable Breakpoints</title>
-</head>
-<body>
-<h1>Disable Breakpoints </h1>
-<p>Select the <strong>Disable</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/disabled_co.png" alt="Disable Breakpoints"> ] to disable the currently selected breakpoint(s). </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-enabled_option.htm">Breakpoint Enabled Option</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-enable_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-enable_contextaction.htm
deleted file mode 100644
index a86766c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-enable_contextaction.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Enable Breakpoints</title>
-</head>
-<body>
-<h1>Enable Breakpoints </h1>
-<p>Select the <strong>Enable</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/enabled_co.png" alt="Enable Breakpoints"> ] to enable the currently selected breakpoint(s). </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Realted Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-enabled_option.htm">Breakpoint Enabled Option</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-entry_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-entry_contextaction.htm
deleted file mode 100644
index b1bd494..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-entry_contextaction.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Method Breakpoint Entry</title>
-</head>
-<body>
-<h1>Method Breakpoint Entry </h1>
-<p>Select the <strong>Entry</strong> command  to change if the selected method breakpoint will suspend on entry to the associated method. </p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_entrycontext.PNG" alt="Method Breakpoint Entry"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-entry_option.htm">Method Breakpoint Entry Option</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-exit_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-exit_contextaction.htm
deleted file mode 100644
index 29ec8cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-exit_contextaction.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Method Breakpoint Exit</title>
-</head>
-<body>
-<h1>Method Breakpoint Exit </h1>
-<p>Select the <strong>Exit</strong> command  to change if the selected method breakpoint will suspend on exit from the associated method.</p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_exitcontext.PNG" alt="Method Breakpoint Exit"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-exit_option.htm">Method Breakpoint Exit Option</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-expandall_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-expandall_viewaction.htm
deleted file mode 100644
index 7392da0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-expandall_viewaction.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Expand All</title>
-</head>
-<body>
-<h1>Expand All </h1>
-<p> Select the <strong>Expand All</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/expandall.png" alt="Expand All"> ] to expand all of the items in the <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a>.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p> <img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-export_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-export_contextaction.htm
deleted file mode 100644
index 610da43..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-export_contextaction.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Export Breakpoints</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Export Breakpoints </h1>
-<p>Select the <strong>Export Breakpoints... </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/export_brkpts.png" alt="Export Breakpoints"> ] to start the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.debug.internal.ui.importexport.breakpoints.WizardExportBreakpoints)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Breakpoints export wizard"> <b>Export Breakpoints</b></a> wizard which will help you  export breakpoints to a file.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/wizards/ref-export_breakpoints.htm">Export Breakpoints wizard</a> <br>
-  <a href="../../../reference/wizards/ref-import_breakpoints.htm">Import Breakpoints wizard </a><br>
-  <a href="../../../reference/views/breakpoints/ref-import_contextaction.htm">Import Breakpoints command </a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-gotofile_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-gotofile_viewaction.htm
deleted file mode 100644
index cdd65f1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-gotofile_viewaction.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Go to File for Breakpoint</title>
-</head>
-<body>
-<h1>Go to File for Breakpoint </h1>
-<p>Select the <strong>Go to File</strong> command [ <img src="../../../images/org.eclipse.jdt.ui/elcl16/goto_input.png" alt="Go to File"> ] to open the associated resource for the breakpoint, make it active and highlight the location of the breakpoint. If the resource is already open it is made active  and the breakpoint location is highlighted. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-groupby_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-groupby_viewaction.htm
deleted file mode 100644
index 5269a87..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-groupby_viewaction.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Group Breakpoints By</title>
-</head>
-<body>
-<h1>Group Breakpoints By</h1>
-<p>Select the <strong>Group By</strong> view menu item to group the breakpoints in the <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a> in one of a choice of predefined orderings. </p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_groupbymenu.PNG" alt="Group Breakpoints By"></p>
-<p>The orderings are as follows:</p>
-<ul>
-  <li><strong>Breakpoints</strong> - a standard list of all breakpoints</li>
-  <li><strong>Breakpoint Types</strong> - all breakpoints organized into their respective types</li>
-  <li><strong>Breakpoint Working Sets</strong> - all breakpoints are organized into the working sets they belong to</li>
-  <li><strong>Files</strong> - all breakpoints are organized by the files that they belong to </li>
-  <li><strong>Projects</strong> - all breakpoints are organized by the project that they belong to </li>
-  <li><strong>Resource Working Sets</strong> - all breakpoints are organized by the resource working sets that they belong to</li>
-  <li><strong>Advanced...</strong>- See below. </li>
-</ul>
-<p>The <strong>Advanced...</strong> command opens a dialog that allows you to specify multiple levels of groupings for your breakpoints. For example you could have breakpoint grouped by type, which are then further grouped by resource working set, which are then further grouped by projects. </p>
-<p>Below is the <strong>Group Breakpoints </strong>dialog.</p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_groupbyadvanced_dialog.PNG" alt="Advanced Breakpoint Grouping Dialog"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  Create a breakpoint working set <br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-hitcount_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-hitcount_contextaction.htm
deleted file mode 100644
index a112575..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-hitcount_contextaction.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Hit Count</title>
-</head>
-<body>
-<h1> Breakpoint Hit Count </h1>
-<p>Select the <strong>Hit Count</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/sethitcount_co.png" alt="Hit Count"> ]  to edit the hit count for the currently selected breakpoint.</p>
-<p>The command opens the <strong>Set Breakpoint Hit Count</strong> dialog which allows you to enter an integer value hit count to apply to the selected breakpoint.</p>
-<p>The <strong>Set Breakpoint Hit Count Dialog</strong>.  </p>
-<p><img  src="../../../reference/views/breakpoints/images/ref-views-breakpoint_set_hitcount_dialog.PNG" alt="Set Hit Count Dialog" width="399" height="194"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-hitcount_option.htm">Breakpoint Hit Count Option</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-import_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-import_contextaction.htm
deleted file mode 100644
index 85f222d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-import_contextaction.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Import Breakpoints</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Import Breakpoints </h1>
-<p>Select the <strong>Import Breakpoints... </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/import_brkpts.png" alt="Import Breakpoints"> ] to start the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.debug.internal.ui.importexport.breakpoints.WizardImportBreakpoints)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Breakpoints import wizard"> <b>Import Breakpoints</b></a> wizard which will help you  import breakpoints into your workspace. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/wizards/ref-export_breakpoints.htm">Export Breakpoints wizard</a> <br>
-  <a href="../../../reference/wizards/ref-import_breakpoints.htm">Import Breakpoints wizard </a><br>
-  <a href="../../../reference/views/breakpoints/ref-export_contextaction.htm">Export Breakpoints command </a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-linkwith_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-linkwith_viewaction.htm
deleted file mode 100644
index 651934b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-linkwith_viewaction.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Link Breakpoints View with Debug View</title>
-</head>
-<body>
-<h1>Link Breakpoints View with Debug View </h1>
-<p> Select the <strong>Link with Debug View</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/synced.png" alt="Link Breakpoints View with Debug View"> ] to have the <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a> be updated with information from the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. When an application suspends on a breakpoint in the <strong>Debug View</strong>, the associated breakpoint will be highlighted in the <strong>Breakpoints View</strong>.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-modification_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-modification_contextaction.htm
deleted file mode 100644
index 1e449cb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-modification_contextaction.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Watchpoint Modification</title>
-</head>
-<body>
-<h1>Watchpoint Modification </h1>
-<p>Select the <strong>Modification</strong> command  to change if the currently selected watchpoint will suspend when its associated field is modified or written to. </p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_modcontext.PNG" alt="Watchpoint Modification "> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-modification_option.htm">Watchpoint Modification Option</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-properties_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-properties_contextaction.htm
deleted file mode 100644
index 6c43e21..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-properties_contextaction.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Properties...</title>
-</head>
-<body>
-<h1> Breakpoint Properties...</h1>
-<p> Select the <strong>Breakpoint Properties...</strong> command to open the breakpoint properties dialog for the currently selected breakpoint.</p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_properties.PNG" alt="Breakpoint properties context menu item"></p>
-<p>There are separate properties for each type of breakpoint, thus resulting in varying properties dialogs. The example given below is for a line breakpoint.</p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_properties_dialog.PNG" alt="Breakpoint Properties Dialog"></p>
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-apply_hit_count.htm">Applying hit counts</a><br>
-  <a href="../../../tasks/task-catching_exceptions.htm">Catching Java exceptions</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-enable_disable_breakpoints.htm">Enabling and disabling breakpoints</a><br>
-  <a href="../../../tasks/task-manage_conditional_breakpoint.htm">Managing conditional breakpoints</a><br>
-  <a href="../../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a> </p>
-<p><img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-condition_option.htm">Condition option </a><br>
-  <a href="../../../reference/breakpoints/ref-enabled_option.htm">Enabled option </a><br>
-  <a href="../../../reference/breakpoints/ref-hitcount_option.htm">Hit count option </a><br>
-  <a href="../../../reference/breakpoints/ref-caught_option.htm">Exception breakpoint caught option</a><br>
-  <a href="../../../reference/breakpoints/ref-suspendsubclass_option.htm">Exception breakpoint suspend on subclass option </a><br>
-  <a href="../../../reference/breakpoints/ref-uncaught_option.htm">Exception breakpoint uncaught option </a><br>
-  <a href="../../../reference/breakpoints/ref-entry_option.htm">Method breakpoint entry option</a><br>
-  <a href="../../../reference/breakpoints/ref-exit_option.htm">Method breakpoint exit option</a><br>
-  <a href="../../../reference/breakpoints/ref-suspendpolicy_option.htm">Suspend Policy </a><br>
-  <a href="../../../reference/breakpoints/ref-access_option.htm">Watchpoint access option</a><br>
-  <a href="../../../reference/breakpoints/ref-modification_option.htm">Watchpoint modification option</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-remove_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-remove_viewaction.htm
deleted file mode 100644
index 6230704..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-remove_viewaction.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Remove Selected Breakpoint</title>
-</head>
-<body>
-<h1> Remove Selected Breakpoint</h1>
-<p> Select the <strong>Remove</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/rem_co.png" alt="Remove Selected Breakpoint"> ] to remove the selected breakpoint(s) from the <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a>. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-removeall_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-removeall_viewaction.htm
deleted file mode 100644
index 649f855..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-removeall_viewaction.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Remove All Breakpoints</title>
-</head>
-<body>
-<h1> Remove All Breakpoints </h1>
-<p> Select the <strong>Remove All</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All Breakpoints"> ] to remove all breakpoints from the <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a>. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-selectdefaultws_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-selectdefaultws_viewaction.htm
deleted file mode 100644
index 5a0daec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-selectdefaultws_viewaction.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Select Default Breakpoint Working Set</title>
-</head>
-<body>
-<h1> Select Default Breakpoint Working Set </h1>
-<p> Choose the <strong>Select Default Working Set...</strong> command  [ <img src="../../../images/org.eclipse.debug.ui/obj16/brkp_grp.png" alt="Select Default Working Set"> ] to select a default working set.</p>
-<p>The command opens the <strong>Select Default Working Set</strong> dialog, which is then used to select a working set to be the default.</p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_select_default_workingset_dialog.PNG" alt="Select Default Working Set Dialog"></p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts" ></p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  Create Working set <br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="related Reference"></p>
-<p><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-showsupported_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-showsupported_viewaction.htm
deleted file mode 100644
index e5a4182..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-showsupported_viewaction.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show supported Breakpoints</title>
-</head>
-<body>
-<h1>Show Supported Breakpoints</h1>
-<p>Select the <strong>Show Supported Breakpoints</strong> command [ <img src="../../../images/org.eclipse.debug.ui/obj16/debugt_obj.png" alt="Show Supported Breakpoints"> ] to indicate if only breakpoints applicable to the current debug target should be visible in the <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a>.</p>
-<p>Example: If you have C/C++ and Java breakpoints, with this option turned on you will only see those breakpoints applicable to what you are currently debugging. Meaning that when you are debugging a Java program the <strong>Breakpoints View</strong> will only display Java breakpoints.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-skipall_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-skipall_viewaction.htm
deleted file mode 100644
index 922933f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-skipall_viewaction.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Skip All Breakpoints</title>
-</head>
-<body>
-<h1>Skip All Breakpoints</h1>
-<p> Select the <strong>Skip All Breakpoints</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/skip_brkp.png" alt="Skip All Breakpoints"> ] to mark all  breakpoints in the current view  as  skipped. Breakpoints marked as skipped will not suspend execution. </p>
-<p>The <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a> showing all breakpoints marked as  skipped.</p>
-<p> <img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_skipall_example.PNG" alt="Skip All Breakpoints  - Toggled On"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-suspendpolicy_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-suspendpolicy_contextaction.htm
deleted file mode 100644
index ad9404b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-suspendpolicy_contextaction.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint Suspend</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Breakpoint Suspend </h1>
-<p> Select the <strong>Suspend</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/suspend_co.png" alt="Breakpoint Suspend"> ] to change the suspend policy of a breakpoint between suspending 
-  the entire VM and the thread in which the breakpoint suspended.</p>
-<p>There is only one menu item visible at any one given time, showing you which suspend policy you <em>will be changing to</em> should you select it. </p>
-<p>You can change the default suspend policy for all newly created breakpoints on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaDebugPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java Debug preference page"> <strong>Java &gt; Debug</strong></a> preference page. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-suspendpolicy_option.htm">Breakpoint Suspend Policy Option</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-uncaught_contextaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-uncaught_contextaction.htm
deleted file mode 100644
index 05186c3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-uncaught_contextaction.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Exception Breakpoint Uncaught</title>
-</head>
-<body>
-<h1>Exception Breakpoint Uncaught </h1>
-<p>Select the <strong>Uncaught</strong> command  to change if the selected Java exception breakpoint will suspend for uncaught exceptions of the same type.</p>
-<p><img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_uncaughtcontext.PNG" alt="Uncaught context action"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a><br>
-  <a href="../../../reference/breakpoints/ref-uncaught_option.htm">Exception Breakpoint Uncaught Option</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-workingsets_viewaction.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-workingsets_viewaction.htm
deleted file mode 100644
index c6351b7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/breakpoints/ref-workingsets_viewaction.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breakpoint View Working Sets</title>
-</head>
-<body>
-<h1> Breakpoint View Working Sets</h1>
-<p> Select the <strong>Working Sets...</strong> command to open the working sets dialog, which allows you to add/remove/edit working sets. </p>
-<p>The <strong>Working Set...</strong> command.</p>
-<p> <img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_workingsets.PNG" alt="The working sets command"></p>
-<p>The <strong>Select Working Set</strong> dialog.</p>
-<p> <img src="../../../reference/views/breakpoints/images/ref-views_breakpoint_workingset_dialog.PNG" alt="Working sets dialog"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  Create Working set <br>
-  <a href="../../../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a></p>
-<p><img src="../../../images/ngrelr.png" alt="related Reference"></p>
-<p><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-console_view.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-console_view.PNG
deleted file mode 100644
index c142ef2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-console_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-cvs_console.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-cvs_console.PNG
deleted file mode 100644
index babf2c3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-cvs_console.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-format_context.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-format_context.PNG
deleted file mode 100644
index a93a44a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-format_context.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-open_console_menu.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-open_console_menu.PNG
deleted file mode 100644
index 49ced3f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-open_console_menu.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-openlink_context.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-openlink_context.PNG
deleted file mode 100644
index a5fc075..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-openlink_context.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-prefs_context.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-prefs_context.PNG
deleted file mode 100644
index 8f74cb4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-prefs_context.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-removeterminated_context.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-removeterminated_context.PNG
deleted file mode 100644
index b56dedd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-removeterminated_context.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-stacktrace_console.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-stacktrace_console.PNG
deleted file mode 100644
index 08c2520..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/images/ref-stacktrace_console.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-autoformat_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-autoformat_action.htm
deleted file mode 100644
index 34d7121..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-autoformat_action.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Console Autoformat</title>
-</head>
-<body>
-<h1> Console Autoformat</h1>
-<p> Select the <strong>Autoformat </strong> command [<img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/autoform_menu.png" alt="Autoformat Console" width="16" height="16">] to automatically reformat any stacktrace pasted into the <a href="../../../reference/views/console/ref-stacktrace_console.htm"><strong>Stacktrace Console</strong></a>.</p>
-<p>This command is only available to stacktrace consoles. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a><br>
-   <a href="../../../reference/views/console/ref-display_action.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-clear_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-clear_action.htm
deleted file mode 100644
index 5108b59..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-clear_action.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Clear Console</title>
-</head>
-<body>
-<h1> Clear Console</h1>
-<p> Select the <strong>Clear Console</strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/clear_co.png" alt="Clear Console"> ] to clear all of the  contents in the <strong><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> </strong>. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><a href="../breakpoints/ref-breakpoints_view.htm"></a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm"> Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm
deleted file mode 100644
index 0b2f603..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Console View</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Console View </h1>
-<p> The <strong>Console View</strong> displays a variety of console types depending on the type of development and the current set of user settings. </p>
-<p><img src="../../../reference/views/console/images/ref-console_view.PNG" alt="Console View"></p>
-<p>The three consoles that are provided by default with the Eclipse Platform are:</p>
-<ul>
-  <li>The <a href="../../../reference/views/console/ref-process_console.htm"><strong>Process Console</strong></a></li>
-  <li>The <a href="../../../reference/views/console/ref-stacktrace_console.htm"><strong>Stacktrace Console</strong></a></li>
-  <li>The <a href="../../../reference/views/console/ref-cvs_console.htm"><strong>CVS Console</strong></a></li>
-</ul>
-<p> You can change settings for consoles on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ConsolePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page"> <strong>Run/Debug &gt; Console</strong></a> preference page. </p>
-<p>The commands available in the <strong>Console View</strong> are listed below.</p>
-<table border="1" cellpadding="5" cellspacing="0" summary="The commands available in the console view">
-  <caption>
-  Console View Commands
-  </caption>
-  <thead>
-    <tr>
-      <th width="71" colspan="1" rowspan="1"> <p> Command </p></th>
-      <th width="209" colspan="1" rowspan="1"> <p> Name </p></th>
-      <th width="540" colspan="1" rowspan="1"> <p> Description </p></th>
-      <th width="193" colspan="1" rowspan="1"> <p> Availability </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/clear_co.png" alt="Clear Console"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> <a href="../../../reference/views/console/ref-clear_action.htm"><strong>Clear Console </strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Clears the currently active console, and is available as both a view command and a contextual menu item. </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"> Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/console_view.png" alt="Display Selected Console"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-display_action.htm"><strong>Display Selected Console</strong></a> </td>
-      <td colspan="1" valign="top" align="left">Opens a listing of current consoles and allows you to select which one you would like to see. </td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/new_con.png" alt="Open Console"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-open_action.htm"><strong>Open Console</strong></a> </td>
-      <td colspan="1" valign="top" align="left">Opens a new console of the selected type. </td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/pin.png" alt="Pin Current Console"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-pin_action.htm"><strong>Pin</strong></a></td>
-      <td colspan="1" valign="top" align="left">Pins the current console to remain on top of all other consoles. </td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/lock_co.png" alt="Scroll Lock"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-scrolllock_action.htm"><strong>Scroll Lock</strong></a> </td>
-      <td colspan="1" valign="top" align="left">Changes if scroll lock should be enabled or not in the current console.</td>
-      <td colspan="1" valign="top" align="left">Context menu and view action </td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><a href="../breakpoints/ref-breakpoints_view.htm"></a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/preferences/run-debug/ref-console.htm">Console Preferences</a><br>
-<a href="../../../reference/views/console/ref-cvs_console.htm">  CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a> <br>
-  <a href="../ref-viewsandeditors.htm">Views and editors</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-cvs_console.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-cvs_console.htm
deleted file mode 100644
index a9dbbfc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-cvs_console.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>CVS Console</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>CVS Console</h1>
-<p> The <strong>CVS Console </strong>displays the output from current and recent CVS operations. </p>
-<p><img src="../../../reference/views/console/images/ref-cvs_console.PNG" alt="CVS Console"><br>
-</p>
-<p>The extra commands available in the <strong>CVS Console</strong> are listed below.</p>
-<table border="1" cellpadding="5" cellspacing="0" summary="The commands available in the console view">
-  <caption>
-  CVS Console Commands
-  </caption>
-  <thead>
-    <tr>
-      <th width="71" colspan="1" rowspan="1"> <p> Command </p></th>
-      <th width="209" colspan="1" rowspan="1"> <p> Name </p></th>
-      <th width="540" colspan="1" rowspan="1"> <p> Description </p></th>
-      <th width="193" colspan="1" rowspan="1"> <p> Availability </p></th>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy Selected Console Material"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-copy.htm"><strong>Copy</strong></a></td>
-      <td colspan="1" valign="top" align="left">Copies the selected material from the console onto the system clipboard.</td>
-      <td colspan="1" valign="top" align="left">Context menu</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/cut_edit.png" alt="Cut Selected Console Material"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-cut.htm"><strong>Cut</strong></a></td>
-      <td colspan="1" valign="top" align="left">Copies the selected material to the system clipboard and removes it from the console. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-findreplace.htm"><strong>Find/Replace</strong></a></td>
-      <td colspan="1" valign="top" align="left">Allows you to search for and replace a specified expression. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-openlink_action.htm"><strong>Open Link </strong></a></td>
-      <td colspan="1" valign="top" align="left">Allows you to follow the hyperlink which was right-clicked on in the current stacktrace.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/paste_edit.png" alt="Paste Into Console"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-paste.htm"><strong>Paste</strong></a></td>
-      <td colspan="1" valign="top" align="left">Pastes material saved on the system clipboard into the current console. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-selectall.htm"><strong>Select All </strong></a></td>
-      <td colspan="1" valign="top" align="left">Selects all of the contents of the current console.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-display_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-display_action.htm
deleted file mode 100644
index b571b56..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-display_action.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Display Selected Console</title>
-</head>
-<body>
-<h1> Display Selected Console </h1>
-<p> Select the <strong>Display Selected Console </strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/console_view.png" alt="Display Selected Console"> ] to bring the console selected from the resulting list into focus.</p>
-<p>Note: this command is only enabled if you have more than one console open. </p>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-format_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-format_action.htm
deleted file mode 100644
index c4b3a08..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-format_action.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Console Format</title>
-</head>
-<body>
-<h1>Console Format</h1>
-<p> Select the <strong>Format </strong> command to reformat the current stacktrace in the <a href="../../../reference/views/console/ref-stacktrace_console.htm"><strong>Stacktrace Console</strong></a>. You can also use the keyboard shortcut <em><strong>Ctrl+Shift+F</strong></em>. </p>
-<p>This command is only available to stacktrace consoles. </p>
-<p><img src="../../../reference/views/console/images/ref-format_context.PNG" alt="Format Console"></p>
-<p> <img src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a><br>
-  <a href="../../../reference/views/console/ref-display_action.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-open_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-open_action.htm
deleted file mode 100644
index 285ca1a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-open_action.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Open Console</title>
-</head>
-<body>
-<h1> Open Console </h1>
-<p> Select the <strong>Open Console </strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/new_con.png" alt="Open Console"> ] to open a new specific type of console  in the <strong><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> </strong>. </p>
-<p>The resulting menu from selecting the drop down arrow on the command.</p>
-<p> <img src="../../../reference/views/console/images/ref-open_console_menu.PNG" alt="Open Console Command Menu"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-openlink_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-openlink_action.htm
deleted file mode 100644
index 9bfea3c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-openlink_action.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Open Link</title>
-</head>
-<body>
-<h1> Open Link</h1>
-<p> Select the <strong>Open Link </strong> command to follow a detected hyperlink in the <a href="../../../reference/views/console/ref-stacktrace_console.htm"><strong>Stacktrace Console</strong></a> or the <a href="../../../reference/views/console/ref-cvs_console.htm"><strong>CVS Console</strong></a>. </p>
-<p><img src="../../../reference/views/console/images/ref-openlink_context.PNG" alt="Open Link"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-pin_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-pin_action.htm
deleted file mode 100644
index a5cf37d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-pin_action.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Pin Console
-    </title>
-  </head>
-  <body>
-    <h1>
-      Pin Console </h1>
-    <p>
-      Select the <strong>Pin Console </strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/pin.png" alt="Pin Console"> ] to ensure that the current console remains on top of all other consoles.</p>
-    <p>For example if you had two consoles, say a <a href="../../../reference/views/console/ref-process_console.htm"><strong>Process Console</strong></a> and a <a href="../../../reference/views/console/ref-stacktrace_console.htm"><strong>Stacktrace Console</strong></a>, and you had the stacktrace console pinned, even if output is written to the process console it will not come to focus in front of the stacktrace console. </p>
-    <p>
-      <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
- <p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-prefs_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-prefs_action.htm
deleted file mode 100644
index a5fc431..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-prefs_action.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Console Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1> Console Preferences </h1>
-<p> Select the <strong>Preferences...</strong> command to open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ConsolePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page"> <strong>Run/Debug &gt; Console</strong></a> preference page. </p>
-<p>This command only applies to the <strong><a href="../../../reference/views/console/ref-process_console.htm">Process Console</a></strong>. </p>
-<p><img src="../../../reference/views/console/images/ref-prefs_context.PNG" alt="Console Preferences menu Item"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-process_console.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-process_console.htm
deleted file mode 100644
index edae445..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-process_console.htm
+++ /dev/null

@@ -1,116 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Process Console</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Process Console</h1>
-<p> The <strong>Process Console </strong> shows the output of a process and allows you to provide keyboard 
-  input to a process. </p>
-<p><img src="../../../reference/views/console/images/ref-console_view.PNG" alt="Process Console"></p>
-<p>The <strong>Process Console</strong> shows three different kinds of text:</p>
-<ul>
-  <li> Standard output </li>
-  <li> Standard error </li>
-  <li> Standard input </li>
-</ul>
-<p> You can choose the different colors for these kinds of text on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ConsolePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page"> <strong>Run/Debug &gt; Console</strong></a> preference page. </p>
-<p>The extra commands available in the <strong>Process Console</strong> are listed below.</p>
-<table border="1" cellpadding="5" cellspacing="0" summary="The commands available in the console view">
-  <caption>
-  Process Console Commands
-  </caption>
-  <thead>
-    <tr>
-      <th width="71" colspan="1" rowspan="1"> <p> Command </p></th>
-      <th width="209" colspan="1" rowspan="1"> <p> Name </p></th>
-      <th width="540" colspan="1" rowspan="1"> <p> Description </p></th>
-      <th width="193" colspan="1" rowspan="1"> <p> Availability </p></th>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy Selected Console Material"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-copy.htm"><strong>Copy</strong></a></td>
-      <td colspan="1" valign="top" align="left">Copies the selected material from the console onto the system clipboard.</td>
-      <td colspan="1" valign="top" align="left">Context menu</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/cut_edit.png" alt="Cut Selected Console Material"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-cut.htm"><strong>Cut</strong></a></td>
-      <td colspan="1" valign="top" align="left">Copies the selected material to the system clipboard and removes it from the console. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-findreplace.htm"><strong>Find/Replace</strong></a></td>
-      <td colspan="1" valign="top" align="left">Allows you to search for and replace s specified expression. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/paste_edit.png" alt="Paste Into Console"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-paste.htm"><strong>Paste</strong></a></td>
-      <td colspan="1" valign="top" align="left">Pastes material saved on the system clipboard into the current console. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-prefs_action.htm"><strong>Preferences...</strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the <strong>Console Preference</strong> <strong>Page</strong>, allowing you to customize you consoles.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All Terminatede Launches"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-removeallterminated_action.htm"><strong>Remove All Terminated Launches</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Removes all of the terminated launches from the current console.</td>
-      <td colspan="1" valign="top" align="left">Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/rem_co.png" alt="Remove Current Launch"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-removelaunch_action.htm"><strong>Remove Launch</strong></a> </td>
-      <td colspan="1" valign="top" align="left">Removes the current launch from the console.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_co.png" alt="Terminate"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-terminate_action.htm"><strong>Terminate</strong></a></td>
-      <td colspan="1" valign="top" align="left">Terminates the running launch in the current console.</td>
-      <td colspan="1" valign="top" align="left">View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-selectall.htm"><strong>Select All </strong></a></td>
-      <td colspan="1" valign="top" align="left">Selects all of the contents of the current console.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/writeout_co.png" alt="Show Console When Standard Out Changes"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-show_out_action.htm"><strong>Show Console When Standard Out Changes</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Will open (if needed) and bring a console to the front when information is written to the System.out stream </td>
-      <td colspan="1" valign="top" align="left">View Action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/writeerr_co.png" alt="Show Console When Standard Error Changes"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-show_err_action.htm"><strong>Show Console When Standard Error Changes</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Will open (if needed) and bring a console to the front when information is written to the System.err stream </td>
-      <td colspan="1" valign="top" align="left">View Action </td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-<a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a><br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removeallterminated_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removeallterminated_action.htm
deleted file mode 100644
index 00f9c7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removeallterminated_action.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Remove All Terminated Launches</title>
-</head>
-<body>
-<h1>Remove All Terminated Launches </h1>
-<p> Select the <strong>Remove All Terminated </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All Terminated Launches"> ] to remove all of the terminated launches from the <strong><a href="../../../reference/views/console/ref-process_console.htm">Process Console</a></strong>.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removelaunch_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removelaunch_action.htm
deleted file mode 100644
index 1c63166..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-removelaunch_action.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Remove Launch</title>
-</head>
-<body>
-<h1> Remove Launch</h1>
-<p> Select the <strong>Remove Launch </strong> command  [ <img src="../../../images/org.eclipse.ui.console/elcl16/rem_co.png" alt="Remove Current Launch"> ] to remove the current launch from the <strong><a href="../../../reference/views/console/ref-process_console.htm">Process Console</a></strong>.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-scrolllock_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-scrolllock_action.htm
deleted file mode 100644
index fb02dde..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-scrolllock_action.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Scroll Lock</title>
-</head>
-<body>
-<h1> Scroll Lock </h1>
-<p> Select the <strong>Scroll Lock </strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/lock_co.png" alt="Scroll Lock"> ] to change whether scroll lock should be enabled or disabled for all open consoles.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_err_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_err_action.htm
deleted file mode 100644
index 2b22999..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_err_action.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Console When Standard Error Changes</title>
-</head>
-<body>
-<h1> Show Console When Standard Error Changes </h1>
-<p> Select the <strong>Show Console When Standard Error Changes </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/writeerr_co.png" alt="Show On Standard Error"> ] to have a console opened (if not open already) and brought to the front if the associated process of the current <a href="../../../reference/views/console/ref-process_console.htm"><strong>Process Console</strong></a> writes to Standard.err.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_out_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_out_action.htm
deleted file mode 100644
index c5ae5d6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-show_out_action.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Console When Standard Out Changes</title>
-</head>
-<body>
-<h1> Show Console When Standard Out Changes </h1>
-<p> Select the <strong>Show Console When Standard Out Changes </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/writeout_co.png" alt="Show on Standard Out"> ] to have a console opened (if not open already) and brought to the front if the associated process of the current <a href="../../../reference/views/console/ref-process_console.htm"><strong>Process Console</strong></a> writes to Standard.out.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-stacktrace_console.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-stacktrace_console.htm
deleted file mode 100644
index f056efc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-stacktrace_console.htm
+++ /dev/null

@@ -1,93 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Stacktrace Console</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Stacktrace Console </h1>
-<p> The <strong>Stacktrace Console</strong> displays a Java stacktrace in a nicely formatted manner, providing hyperlink support to quickly jump to source code locations. </p>
-<p><img src="../../../reference/views/console/images/ref-stacktrace_console.PNG" alt="Stacktrace Console"><br>
-</p>
-<p>The extra commands available in the  <strong>Stacktrace Console</strong> are listed below.</p>
-<table border="1" cellpadding="5" cellspacing="0" summary="The commands available in the console view">
-  <caption>
-  Stacktrace Console Commands
-  </caption>
-  <thead>
-    <tr>
-      <th width="71" colspan="1" rowspan="1"> <p> Command </p></th>
-      <th width="209" colspan="1" rowspan="1"> <p> Name </p></th>
-      <th width="540" colspan="1" rowspan="1"> <p> Description </p></th>
-      <th width="193" colspan="1" rowspan="1"> <p> Availability </p></th>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/autoform_menu.png" alt="Auto Format"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-autoformat_action.htm"><strong>Auto Format</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Automatically formats stacktraces when pasted into a stacktrace console </td>
-      <td colspan="1" valign="top" align="left">View Action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy Selected Console Material"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-copy.htm"><strong>Copy</strong></a></td>
-      <td colspan="1" valign="top" align="left">Copies the selected material from the console onto the system clipboard.</td>
-      <td colspan="1" valign="top" align="left">Context menu</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/cut_edit.png" alt="Cut Selected Console Material"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-cut.htm"><strong>Cut</strong></a></td>
-      <td colspan="1" valign="top" align="left">Copies the selected material to the system clipboard and removes it from the console. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-findreplace.htm"><strong>Find/Replace</strong></a></td>
-      <td colspan="1" valign="top" align="left">Allows you to search for and replace s specified expression. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-format_action.htm"><strong>Format</strong></a></td>
-      <td colspan="1" valign="top" align="left">Reformats the current stacktrace. This command in only available to stacktrace consoles. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/console/ref-openlink_action.htm"><strong>Open Link </strong></a></td>
-      <td colspan="1" valign="top" align="left">Allows you to follow the hyperlink which was right-clicked on in the current stacktrace.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/paste_edit.png" alt="Paste Into Console"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-paste.htm"><strong>Paste</strong></a></td>
-      <td colspan="1" valign="top" align="left">Pastes material saved on the system clipboard into the current console. </td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-selectall.htm"><strong>Select All </strong></a></td>
-      <td colspan="1" valign="top" align="left">Selects all of the contents of the current console.</td>
-      <td colspan="1" valign="top" align="left">Context menu </td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-<a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a><br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-terminate_action.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-terminate_action.htm
deleted file mode 100644
index f5643a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/console/ref-terminate_action.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Terminate
-    </title>
-  </head>
-  <body>
-    <h1>
-      Terminate    </h1>
-    <p>
-      Select the <strong>Terminate</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_co.png" alt="Terminate"> ] to terminate the process that is associated with the current <a href="../../../reference/views/console/ref-process_console.htm"><strong>Process Console</strong></a>.</p>
-    <p>
-      <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-  <a href="../../../reference/views/ref-viewsandeditors.htm">Views and editors</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/console/ref-console_view.htm">Console View</a> <br>
-  <a href="../../../reference/views/console/ref-cvs_console.htm">CVS Console</a><br>
-  <a href="../../../reference/views/console/ref-process_console.htm">Process Console</a><br>
-  <a href="../../../reference/views/console/ref-stacktrace_console.htm">Stacktrace Console</a></p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb.png b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb.png
deleted file mode 100644
index 1d1d665..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb_drop_down.png b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb_drop_down.png
deleted file mode 100644
index 9c017f2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-breadcrumb_drop_down.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-configdialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-configdialog.PNG
deleted file mode 100644
index 70ddf16..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-configdialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-debug_view.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-debug_view.PNG
deleted file mode 100644
index 18b5e2f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-debug_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editlaunchconfig.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editlaunchconfig.PNG
deleted file mode 100644
index d24678f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editlaunchconfig.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editstepfilters.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editstepfilters.PNG
deleted file mode 100644
index 5089fa5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-editstepfilters.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filterpackage.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filterpackage.PNG
deleted file mode 100644
index daf0b90..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filterpackage.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filtertype.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filtertype.PNG
deleted file mode 100644
index 79b7160..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-filtertype.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-find_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-find_dialog.PNG
deleted file mode 100644
index 8728462..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-find_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-lookupsource.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-lookupsource.PNG
deleted file mode 100644
index 52bc4ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-lookupsource.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_supported.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_supported.PNG
deleted file mode 100644
index 00db8ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_supported.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_unsupported.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_unsupported.PNG
deleted file mode 100644
index bb3bf30..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-monitors_unsupported.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclared.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclared.PNG
deleted file mode 100644
index 13b5199..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclared.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclaredhier.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclaredhier.PNG
deleted file mode 100644
index 08026e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-opendeclaredhier.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties.PNG
deleted file mode 100644
index 5fd1efa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog.PNG
deleted file mode 100644
index 62b9dd2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog2.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog2.PNG
deleted file mode 100644
index 0bb24ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-properties_dialog2.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-sourcelookupdialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-sourcelookupdialog.PNG
deleted file mode 100644
index 7aa40b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-sourcelookupdialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmanagement.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmanagement.PNG
deleted file mode 100644
index 8ed55d3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmanagement.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmng_menu.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmng_menu.PNG
deleted file mode 100644
index 5672145..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/images/ref-viewmng_menu.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-breadcrumb.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-breadcrumb.htm
deleted file mode 100644
index 00827be..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-breadcrumb.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Debug Breadcrumb</title>
-</head>
-<body>
-<h1> Debug Breadcrumb </h1>
-<p> Debug Breadcrumb is a compact presentation of the currently active debug context and its parents. </p>  
-<p> <img src="images/ref-breadcrumb.png" alt="Debug Breadcrumb"> </p>
-<p> To enable the Debug Breadcrumb, change the <a href="../ref-debug_view.htm"><strong>Debug View</strong></a> layout to Breadcrumb (Select <strong>Layout-&gt;Breadcrumb</strong> in the Debug View menu).  Alternatively, resize the Debug View such that the height of the view is small enough to fit only one line of text.  This will cause the view to change over to the Breadcrumb layout automatically. </p>
-<p> The Debug Breadcrumb allows to invoke actions on any element shown in the breadcrumb.  Actions can be invoked through the context menu or through key bindings.  To select an element in the breadcrumb click on it or activate the Debug view and use the <strong>left</strong> and <strong>right</strong> arrow keys.</p>
-<p> You can also change the active debug context using the breadcrumb. Click on one of the arrows or any element top open a drop-down window. The drop-down shows all the siblings of the element for which the drop-down was opened.  Click on an element to make it the new active debug context.  To open the drop-down with the keyboard, select and element and press the <strong>down</strong> key.</p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="ref-debug_view.htm">Debug View</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-debug_view.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-debug_view.htm
deleted file mode 100644
index 8301b74..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-debug_view.htm
+++ /dev/null

@@ -1,274 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Debug View</title>
-</head>
-<body>
-<h1> Debug View </h1>
-<p> The <strong>Debug View</strong> allows you to manage the debugging or running of a program in the workbench. It displays the stack frame for the suspended threads for each target you are
-  debugging. Each thread in your program appears as a node in the tree. It displays the process for each target you are running. </p>
-<p>If the thread is suspended, its stack frames are shown as child elements. </p>
-<p><img src="../../../reference/views/debug/images/ref-debug_view.PNG" alt="Debug View"></p>
-<p>The <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm"><strong>Execution Control Commands</strong></a> allow you to debug your program, starting, stopping and stepping through the code.</p>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-  Debug View Commands
-  </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> <p> Name </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Availability </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"> &nbsp; </td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><strong> <a href="ref-layout_automatic.htm">Automatic</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Configures the debug view to switch layout between a tree and a breadcrumb viewer automatically when the view is resized. </p></td>
-      <td>View action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"> &nbsp; </td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><strong> <a href="ref-layout_breadcrumb_auto_expand.htm">Auto-Expand Breadcrumb</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Configures the Debug Breadcrumb Drop-down to automatically expand elements when opened. </p></td>
-      <td>View action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"> &nbsp; </td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><strong> <a href="ref-layout_breadcrumb.htm">Breadcrumb</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Configures the debug view layout to use a breadcrumb viewer. </p></td>
-      <td>View action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy Stack command in context menu"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><strong> <a href="../../../reference/views/shared/ref-copy.htm">Copy Stack</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Copies the selected stack of suspended threads as well 
-          as the state of the running threads to the clipboard. </p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/disconnect_co.png" alt="Disconnect button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-disconnect.htm">Disconnect</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Disconnects the debugger from the selected debug target 
-          when debugging remotely. </p></td>
-      <td>Context menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><img src="../../../images/org.eclipse.debug.ui/elcl16/drop_to_frame.png" alt="Copy Stack command in context menu"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> <a href="../../../reference/views/debug/ref-droptoframe.htm"><strong>Drop to Frame</strong></a> </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This command lets you drop back and reenter a specified stack frame. 
-          This feature is similar to &quot;running backwards&quot; and restarting 
-          your program part-way through. </p>
-        <p> To drop back and reenter a specified stack frame, select the stack frame 
-          that you want to &quot;drop&quot; to, and select <strong>Drop to Frame</strong>. </p>
-        <p> Some caveats apply to this feature: </p>
-        <ul>
-          <li> You cannot drop past a native method on the stack. </li>
-          <li> Global data are unaffected and will retain their current values. 
-            For example, a static vector containing elements will not be cleared. </li>
-        </ul>
-        <em>Note: This command is only enabled if the underlying VM supports this 
-        feature.</em> </td>
-      <td>Context menu and view action</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-editlaunchconfig.htm"><strong>Edit [configuration name]...</strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the launch configuration dialog on the associated launch configuration, allowing you to make changes. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-editstepfilters.htm"><strong>Edit Step Filters</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Opens the Step Filtering preference page to allowing editing of step filters </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png" alt="Edit Source Lookup" ></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-editsourcelookup.htm"><strong>Edit Source Lookup </strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the source lookup dialog, allowing you to make changes. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-filterpackage.htm"><strong>Filter Package </strong></a></td>
-      <td colspan="1" valign="top" align="left">Adds the containing package for the  type from the current suspended execution to the listing of step filters </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-filtertype.htm"><strong>Filter Type </strong></a></td>
-      <td colspan="1" valign="top" align="left">Adds the type from the current suspended execution to the listing of step filters </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/shared/ref-find.htm"><strong>Find...</strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the debug view element searching dialog.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-lookupsource.htm"><strong>Lookup Source</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Forces source lookup to take place </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-opendeclared.htm"><strong>Open Declared Type </strong></a></td>
-      <td colspan="1" valign="top" align="left">Opens the declared type for the selected stack frame in a new editor. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-opendeclaredhier.htm"><strong>Open Declared Type Hierarchy</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Opens the type hierarchy for the declared type of the selected stack frame. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-properties.htm">Properties</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This command displays the properties of the selected launch. It also 
-          allows you to view the full command line for a selected process. </p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/runlast_co.png" alt="Relaunch command in context menu"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-relaunch.htm">Relaunch</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This command relaunches the selected debug target. </p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All Terminated Launches button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated Launches </a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Clears all terminated debug targets from the view display. </p></td>
-      <td>Context menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/resume_co.png" align="middle"  alt="Resume button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-resume.htm">Resume</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Resumes a suspended thread. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png" alt="Show Monitors"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-showmonitors.htm"><strong>Show Monitors</strong> </a></td>
-      <td colspan="1" valign="top" align="left"><p>This option can be toggled to display or hide monitors. </p>
-        <p><em>Note: this command will only display monitor information if the underlying VM supports it.</em> </p></td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/package_obj.png" alt="Show Qualified Names button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/shared/ref-showqualified.htm">Show Qualified Names </a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> This option can be toggled to display or hide qualified names. </p></td>
-      <td>View action</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/thread_obj.png" alt="Show System Threads"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-showsystemthreads.htm"><strong>Show System Threads</strong> </a></td>
-      <td colspan="1" valign="top" align="left">This option can be toggled to display or hide system threads </td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/threadgroup_obj.png" alt="Show Thread Groups"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-showthreadgroups.htm"><strong>Show Thread Groups</strong> </a></td>
-      <td colspan="1" valign="top" align="left">This option can be toggled to display or hide thread groups </td>
-      <td>View action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" alt="Step Into button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> <a href="../../../reference/views/debug/ref-stepinto.htm"><strong>Step Into</strong></a> </p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps into the highlighted statement. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepover_co.png" alt="Step Over button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-stepover.htm">Step Over </a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps over the highlighted statement. Execution will continue 
-          at the next line either in the same method or (if you are at the end of 
-          a method) it will continue in the method from which the current method 
-          was called. </p>
-        <p> The cursor jumps to the declaration of the method and selects this line. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" alt="Run to Return button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-stepreturn.htm">Step  Return</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps out of the current method. This option stops execution 
-          after exiting the current method. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/suspend_co.png" align="middle"  alt="Suspend button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-suspend.htm">Suspend</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Suspends the selected thread of a target so that you can 
-          browse or modify code, inspect data, step, and so on. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_co.png" align="middle"  alt="Terminate button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-terminate.htm">Terminate</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Terminates the selected debug target. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_all_co.png" alt="Terminate All command in context menu"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Terminates all active launches in the view. </p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/etool16/term_restart.png" alt="Terminate and Relaunch"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-terminaterelaunch.htm"><strong>Terminate and Relaunch</strong> </a></td>
-      <td colspan="1" valign="top" align="left">Terminates the selected debug target and relaunches it. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png" alt="Terminate &amp; Remove command in context menu"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove </a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Terminates the selected debug target and removes it from 
-          the view. </p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"> &nbsp; </td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><strong> <a href="ref-layout_tree.htm">Tree</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Configures the debug view layout to use a tree viewer. </p></td>
-      <td>View action</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepbystep_co.png" alt="Step with Filters button"> </td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-usestepfilters.htm"><strong>Use Step Filters</strong></a></td>
-      <td colspan="1" valign="top" align="left">Toggles 
-        step filters on/off. When on, all step functions apply step filters.</td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../preferences/run-debug/ref-run_debug.htm">Debug Preferences</a><br>
-  <a href="../ref-viewsandeditors.htm">Views and editors</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-disconnect.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-disconnect.htm
deleted file mode 100644
index bc05b70..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-disconnect.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Disconnect</title>
-</head>
-<body>
-<h1> Disconnect</h1>
-<p> Select the <strong>Disconnect</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/disconnect_co.png" alt="Disconnect"> ] to terminate the connection between the debugger and the remote debug target. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-droptoframe.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-droptoframe.htm
deleted file mode 100644
index d37f663..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-droptoframe.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Drop to Frame</title>
-</head>
-<body>
-<h1> Drop to Frame </h1>
-<p> Select the <strong>Drop to Frame</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/drop_to_frame.png" alt="Drop to Frame"> ] to re-enter the selected stack frame in the <strong><a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a></strong>. </p>
-<p>Note this command is only available if the current VM supports drop to frame and the selected stackframe is not the top frame or a frame in a native method. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editlaunchconfig.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editlaunchconfig.htm
deleted file mode 100644
index 492e018..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editlaunchconfig.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Edit...</title>
-</head>
-<body>
-<h1> Edit... </h1>
-<p> Select the<strong> Edit... </strong>command  to open the <strong>Launch Configuration Dialog</strong>, and allow you to edit the launch configuration for the selected  target.</p>
-<p><img src="../../../reference/views/debug/images/ref-editlaunchconfig.PNG" alt="Edit Launch Configuration"></p>
-<p>The resulting launch configuration dialog, in this example a Java Application type.</p>
-<p><img src="../../../reference/views/debug/images/ref-configdialog.PNG" alt="Launch Configuration Dialog"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editsourcelookup.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editsourcelookup.htm
deleted file mode 100644
index cd2dfe9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editsourcelookup.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Edit Source Lookup</title>
-</head>
-<body>
-<h1> Edit Source Lookup </h1>
-<p> Select the <strong>Edit Source Lookup... </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/edtsrclkup_co.png" alt="Edit Source Lookup"> ] to open the <strong>Source Path Dialog</strong>, which allows you to make changes to the source lookup path of the selected debug target. </p>
-<p>The <strong>Source Path Dialog</strong>:</p>
-<p><img src="../../../reference/views/debug/images/ref-sourcelookupdialog.PNG" alt="Source Lookup Dialog"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editstepfilters.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editstepfilters.htm
deleted file mode 100644
index af96ff1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-editstepfilters.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Edit Step Filters</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Edit Step Filters </h1>
-<p> Select the <strong>Edit Step Filters </strong> command  to open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaStepFilterPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Step Filtering preference page"> <strong>Java &gt; Debug &gt; Step Filtering</strong></a> preference page, which allows you to add and configure   step filters. </p>
-<p><img src="../../../reference/views/debug/images/ref-editstepfilters.PNG" alt="Edit Step Filters"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a> <br>
-  <a href="../../../reference/views/debug/ref-filterpackage.htm">Filter Package Command</a> <br>
-  <a href="../../../reference/views/debug/ref-filtertype.htm">Filter Type Command</a> <br>
-  <a href="../../../reference/views/debug/ref-usestepfilters.htm">Use Step Filters Command</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-executioncontrolcommands.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-executioncontrolcommands.htm
deleted file mode 100644
index 83c52bf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-executioncontrolcommands.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Execution Control Commands</title>
-</head>
-<body>
-<h1> Execution Control Commands </h1>
-<p> Execution control commands allow you to change the execution state of code being executed.</p>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-  Java Execution Control Commands
-  </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> <p> Name </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Availability </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/resume_co.png" align="middle"  alt="Resume button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-resume.htm">Resume</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Resumes a suspended thread. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" alt="Step Into button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-stepinto.htm">Step Into</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps into the highlighted statement. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepover_co.png" alt="Step Over button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-stepover.htm">Step Over</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps over the highlighted statement. Execution will continue 
-          at the next line either in the same method or (if you are at the end of 
-          a method) it will continue in the method from which the current method 
-          was called. </p>
-        <p> The cursor jumps to the declaration of the method and selects this line. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" alt="Run to Return button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-stepreturn.htm">Step  Return</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Steps out of the current method. This option stops execution 
-          after exiting the current method. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/suspend_co.png" align="middle"  alt="Suspend button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-suspend.htm">Suspend</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Suspends the selected thread of a target so that you can 
-          browse or modify code, inspect data, step, and so on. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_co.png" align="middle"  alt="Terminate button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-terminate.htm">Terminate</a> </strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Terminates the selected debug target. </p></td>
-      <td>Context menu, Run menu and view action</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/etool16/term_restart.png" alt="Terminate and Relaunch"></td>
-      <td colspan="1" valign="top" align="left"><a href="../../../reference/views/debug/ref-terminaterelaunch.htm"><strong>Terminate &amp; Relaunch </strong></a></td>
-      <td colspan="1" valign="top" align="left">Terminates the selected debug target and relaunches it. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png" alt="Terminate &amp; Remove command in context menu"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate &amp; Remove </a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Terminates the selected debug target and removes it from 
-          the view. </p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_all_co.png" alt="Terminate All command in context menu"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><strong> <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Terminates all active launches in the view. </p></td>
-      <td>Context menu</td>
-    </tr>
-  </tbody>
-</table>
-<p>See the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a> for more information. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filterpackage.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filterpackage.htm
deleted file mode 100644
index 420613a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filterpackage.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Filter Package</title>
-</head>
-<body>
-<h1> Filter Package </h1>
-<p> Select the <strong>Filter Package </strong> command  to add the package of the selected stack frame to the list of items to be filtered via step filtering. </p>
-<p>For example, if the currently selected stack frame is of type <em><strong>java.lang.Object</strong></em>, and you select the <strong>Filter Package </strong> command then <em><strong>java.lang.*</strong></em> will be added to the list of types to be filtered via step filtering.</p>
-<p><strong>Warning</strong>: You can inadvertently filter out more than you expect when using this command, take care in its use. </p>
-<p><img src="../../../reference/views/debug/images/ref-filterpackage.PNG" alt="Filter Package"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a> <br>
-  <a href="../../../reference/views/debug/ref-editstepfilters.htm">Edit Step Filters Command</a><br>
-  <a href="../../../reference/views/debug/ref-filtertype.htm">Filter Type Command</a> <br>
-  <a href="../../../reference/views/debug/ref-usestepfilters.htm">Use Step Filters Command</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filtertype.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filtertype.htm
deleted file mode 100644
index a7f68c5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-filtertype.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Filter Type</title>
-</head>
-<body>
-<h1> Filter Type </h1>
-<p> Select the <strong>Filter Type </strong> command  to add the type associated with the selected stack frame to the list of types to be filtered via step filtering. </p>
-<p>For example, if the currently selected stack frame is associated with the type <em><strong>java.lang.Object</strong></em>, and you select the <strong>Filter Type</strong> command then <em><strong>java.lang.Object</strong></em> will be added to the list of types to be filtered via step filtering.</p>
-<p><img src="../../../reference/views/debug/images/ref-filtertype.PNG" alt="Filter Type"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Step Commands</a> <br>
-  <a href="../../../reference/views/debug/ref-editstepfilters.htm">Edit Step Filters Command</a> <br>
-  <a href="../../../reference/views/debug/ref-usestepfilters.htm">Use Step Filters Command</a><br>
-  <a href="../../../reference/views/debug/ref-filterpackage.htm">Filter Package Command</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_automatic.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_automatic.htm
deleted file mode 100644
index c3d50f7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_automatic.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Automatic Layout</title>
-</head>
-<body>
-<h1> Automatic Layout</h1>
-<p> Select the <strong>Layout -&gt; Automatic</strong> command from the view menu in <a href="ref-debug_view.htm"><strong>Debug View</strong></a>.  This causes the view layout to automatically switch between a breadcrumb and a tree viewer when the view is resized.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br></p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="ref-breadcrumb.htm">Debug Breadcrumb</a><br>
-  <a href="ref-layout_breadcrumb.htm">Breadcrumb Layout</a><br>
-  <a href="ref-layout_tree.htm">Tree Layout</a><br>
-  <a href="ref-layout_breadcrumb_auto_expand.htm">Auto-Expand Breadcrumb</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb.htm
deleted file mode 100644
index 15ccaff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Breadcrumb Layout</title>
-</head>
-<body>
-<h1> Breadcrumb Layout</h1>
-<p> Select the <strong>Layout -&gt; Breadcrumb</strong> command from the view menu in <a href="ref-debug_view.htm"><strong>Debug View</strong></a>.  This causes the view to show debug elements in a breadcrumb viewer.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br></p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="ref-breadcrumb.htm">Debug Breadcrumb</a><br>
-  <a href="ref-layout_automatic.htm">Automatic Layout</a><br>
-  <a href="ref-layout_tree.htm">Tree Layout</a><br>
-  <a href="ref-layout_breadcrumb_auto_expand.htm">Auto-Expand Breadcrumb</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb_auto_expand.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb_auto_expand.htm
deleted file mode 100644
index e07d91c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_breadcrumb_auto_expand.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Auto-Expand Breadcrumb</title>
-</head>
-<body>
-<h1>Auto-Expand Breadcrumb</h1>
-<p> Select the <strong>Layout -&gt; Auto-Expand Breadcrumb</strong> to configure the breadcrumb so that the drop-down will automatically restore the expanded state of elements when the drop-down is opened.</p>
-<p> <img src="images/ref-breadcrumb_drop_down.png" alt="Breadcrumb Drop-down"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br></p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="ref-breadcrumb.htm">Debug Breadcrumb</a><br>
-  <a href="ref-layout_tree.htm">Tree Layout</a><br>
-  <a href="ref-layout_breadcrumb.htm">Breadcrumb Layout</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_tree.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_tree.htm
deleted file mode 100644
index 320d4fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-layout_tree.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Tree Layout</title>
-</head>
-<body>
-<h1> Tree Layout</h1>
-<p> Select the <strong>Layout -&gt; Tree</strong> command from the view menu in <a href="ref-debug_view.htm"><strong>Debug View</strong></a>.  This causes the view to show debug elements in a tree viewer.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br></p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="ref-breadcrumb.htm">Debug Breadcrumb</a><br>
-  <a href="ref-layout_automatic.htm">Automatic Layout</a><br>
-  <a href="ref-layout_breadcrumb.htm">Breadcrumb Layout</a><br>
-  <a href="ref-layout_breadcrumb_auto_expand.htm">Auto-Expand Breadcrumb</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-lookupsource.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-lookupsource.htm
deleted file mode 100644
index e027d55..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-lookupsource.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Lookup Source</title>
-</head>
-<body>
-<h1> Lookup Source </h1>
-<p> Select the<strong> Lookup Source </strong>command  to force a source lookup to take place. If the requested source file is not open, it will be opened and the corresponding line of execution will be highlighted. </p>
-<p><img src="../../../reference/views/debug/images/ref-lookupsource.PNG" alt="Lookup Source"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-editsourcelookup.htm">Edit Source Lookup</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclared.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclared.htm
deleted file mode 100644
index 30e8967..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclared.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Open Declared Type</title>
-</head>
-<body>
-<h1> Open Declared Type </h1>
-<p> Select the <strong>Open Declared Type</strong> command  to open an editor on the declared type of the currently selected stack frame in the <strong><a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a></strong>.</p>
-<p><img src="../../../reference/views/debug/images/ref-opendeclared.PNG" alt="Open Declared Type"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclaredhier.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclaredhier.htm
deleted file mode 100644
index 5eec532..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-opendeclaredhier.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Open Declared Type Hierarchy</title>
-</head>
-<body>
-<h1> Open Declared Type Hierarchy </h1>
-<p> Select the <strong>Open Declared Type Hierarchy </strong>command  to open the declared type of the currently selected stack frame in the <strong>Type Hierarchy View</strong><strong>.</strong></p>
-<p><img src="../../../reference/views/debug/images/ref-opendeclaredhier.PNG" alt="Open Declared Type Hierarchy"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p><a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-properties.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-properties.htm
deleted file mode 100644
index 9759d3f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-properties.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Properties</title>
-</head>
-<body>
-<h1> Properties </h1>
-<p> Select the <strong>Properties</strong> command to open the properties dialog for the selected debug target, thread, thread group, process or stackframe. </p>
-<p><img src="../../../reference/views/debug/images/ref-properties.PNG" alt="Debug Target Properties"></p>
-<p>From the resulting dialog you can copy information about the selected debug target and view the actual command line used to run the target.</p>
-<p><img src="../../../reference/views/debug/images/ref-properties_dialog.PNG" alt="Properties Dialog"> </p>
-<p>You can also view the capabilities of the VM used to launch the associated target</p>
-<p><img src="../../../reference/views/debug/images/ref-properties_dialog2.PNG" alt="Properties Dialog Showing Capabilities"> </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-relaunch.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-relaunch.htm
deleted file mode 100644
index 47a7915..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-relaunch.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Relaunch</title>
-</head>
-<body>
-<h1> Relaunch </h1>
-<p> Select the <strong>Relaunch</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/runlast_co.png" alt="Relaunch"> ]  to relaunch the selected debug target in the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated Launches</a> <br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/debug/ref-terminate.htm">Terminate</a><br>
-  <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a><br>
-  <a href="../../../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-removeallterminated.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-removeallterminated.htm
deleted file mode 100644
index 618bebb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-removeallterminated.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Remove All Terminated</title>
-</head>
-<body>
-<h1> Remove All Terminated</h1>
-<p> Select the <strong>Remove All Terminated</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remoce All Terminated Launches"> ] to clear the <strong><a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a></strong> of all terminated launches.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-relaunch.htm">Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-terminate.htm">Terminate</a><br>
-  <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a><br>
-  <a href="../../../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-resume.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-resume.htm
deleted file mode 100644
index cbc5f80..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-resume.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Resume</title>
-</head>
-<body>
-<h1> Resume</h1>
-<p> Select the <strong>Resume</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/resume_co.png" alt="Resume"> ] to resume the execution of the currently suspended debug target.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showmonitors.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showmonitors.htm
deleted file mode 100644
index e32d0db..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showmonitors.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Monitors</title>
-</head>
-<body>
-<h1> Show Monitors </h1>
-<p> Select the <strong>Show Monitors </strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/obj16/thread_and_monitor_obj.png" alt="Show Monitors"> ] to change if monitor information will be shown for suspended threads.</p>
-<p>Note: The display of monitor information must be supported by the underlying VM. If using an IBM or SUN VM, any version greater than 1.4 will support monitor information.</p>
-<p>Consider the following code example:</p>
-<pre>
-/**
- * Hello World
- */
-public class HelloWorld {
-
-
-	 public static void main(String[] args) {
-		Object mutex = new Object();
-		synchronized (mutex) {
-			System.out.println("Hello World!");
-		}
-	 }
-} 
-</pre>
-<p>If the above code snippet is run on a supporting VM with <strong>Show Monitors</strong> selected, the monitor information is represented as a 'key' and appearing before any stack frames as a child of a suspended thread. </p>
-<p><img src="../../../reference/views/debug/images/ref-monitors_supported.PNG" alt="Monitor Information"></p>
-<p>If however, we run the same snippet on an unsupported VM with <strong>Show Monitors</strong> selected, we are alerted that monitor information is not supported by the VM. </p>
-<p><img src="../../../reference/views/debug/images/ref-monitors_unsupported.PNG" alt="Monitors Not Supported"></p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-showsystemthreads.htm">Show System Threads</a><br>
-  <a href="../../../reference/views/debug/ref-showthreadgroups.htm">Show Thread Groups</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showsystemthreads.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showsystemthreads.htm
deleted file mode 100644
index dba0e79..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showsystemthreads.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show System Threads</title>
-</head>
-<body>
-<h1> Show System Threads </h1>
-<p> Select the <strong>Show System Threads </strong> command [ <img src="../../../images/org.eclipse.debug.ui/obj16/thread_obj.png" alt="Show System Threads"> ] to change if system threads should be shown in the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-showmonitors.htm">Show Monitors</a><br>
-  <a href="../../../reference/views/debug/ref-showsystemthreads.htm">Show System Threads</a><br>
-  <a href="../../../reference/views/debug/ref-showthreadgroups.htm">Show Thread Groups</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showthreadgroups.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showthreadgroups.htm
deleted file mode 100644
index 3be92c6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-showthreadgroups.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Thread Groups</title>
-</head>
-<body>
-<h1> Show Thread Groups </h1>
-<p> Select the <strong>Show Thread Groups </strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/obj16/threadgroup_obj.png" alt="Show Thread Groups"> ] to change if  thread groups should be used to organize threads displayed in the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-showmonitors.htm">Show Monitors</a><br>
-  <a href="../../../reference/views/debug/ref-showsystemthreads.htm">Show System Threads</a><br>
-  <a href="../../../reference/views/debug/ref-showthreadgroups.htm">Show Thread Groups</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepinto.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepinto.htm
deleted file mode 100644
index a6eeb0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepinto.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Step Into</title>
-</head>
-<body>
-<h1> Step Into </h1>
-<p> Select the <strong>Step Into </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" alt="Step Into"> ] to step into the next method call at the currently executing line of code. </p>
-<p>To step into a method you must have execution suspended and be stepping through code. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/debug/ref-stepreturn.htm">Step Return</a><br>
-  <a href="../../../reference/views/debug/ref-stepover.htm">Step Over</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepover.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepover.htm
deleted file mode 100644
index beca515..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepover.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Step Over</title>
-</head>
-<body>
-<h1> Step Over </h1>
-<p> Select the <strong>Step Over </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/stepover_co.png" alt="Step Over"> ] to step over the next method call (without entering it) at the currently executing line of code. Even though the method is never stepped into, the method will be executed normally.</p>
-<p>To step over a method you must have execution suspended and be stepping through code. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/debug/ref-stepreturn.htm">Step Return</a><br>
-  <a href="../../../reference/views/debug/ref-stepinto.htm">Step Into</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepreturn.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepreturn.htm
deleted file mode 100644
index 0758a09..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-stepreturn.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Step Return</title>
-</head>
-<body>
-<h1> Step Return </h1>
-<p> Select the <strong>Step Return </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" alt="Step Return"> ] to return from a method which has been stepped into. Even though we return from the method, the remainder of the code inside the method will be executed normally.</p>
-<p>To step return from a method you must have execution suspended and be stepping through code. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/debug/ref-stepinto.htm">Step Into</a> <br>
-  <a href="../../../reference/views/debug/ref-stepover.htm">Step Over</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-suspend.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-suspend.htm
deleted file mode 100644
index a68e86d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-suspend.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Suspend</title>
-</head>
-<body>
-<h1> Suspend</h1>
-<p> Select the <strong>Suspend</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/suspend_co.png" alt="Suspend"> ] to halt the execution of the currently selected thread in a debug target. Once the selected thread  is suspended you can then examine its stack frames. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-resume.htm">Resume</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminate.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminate.htm
deleted file mode 100644
index 0bd9c4d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminate.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Terminate</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>Terminate </h1>
-<p> Select the <strong>Terminate</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_co.png" alt="Terminate selected debug target"> ] to terminate the launch associated with the selected debug target. </p>
-<p>Once a launch is terminated it can be automatically removed  from the <strong><a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a></strong>. To change this setting use the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launching preference page"> <strong>Run/Debug &gt; Launching</strong></a> preference page.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-relaunch.htm">Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated</a> <br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a><br>
-  <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a><br>
-  <a href="../../../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateall.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateall.htm
deleted file mode 100644
index 5b611e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateall.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Terminate all</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Terminate/Disconnect All </h1>
-<p> Select the <strong>Terminate/Disconnect All</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_all_co.png" alt="Terminate All"> ] to terminate all the running debug targets in the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>.  If the target cannot be terminated, it will be disconnected.</p>
-<p>Once a launch is terminated it can be automatically removed  from the <strong>Debug View</strong>. To change this setting use the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launching preference page"> <strong>Run/Debug &gt; Launching</strong></a> preference page.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-relaunch.htm">Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated</a> <br>
-  <a href="../../../reference/views/debug/ref-terminate.htm">Terminate</a><br>
-  <a href="../../../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateandremove.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateandremove.htm
deleted file mode 100644
index 4d112ef..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminateandremove.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Terminate and Remove</title>
-</head>
-<body>
-<h1> Terminate and Remove </h1>
-<p> Select the <strong>Terminate and Remove</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/terminate_rem_co.png" alt="Terminate and Remove"> ] to terminate the launch associated with the selected debug target and remove it from the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. </p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-relaunch.htm">Relaunch</a><br>
-  <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated</a> <br>
-  <a href="../../../reference/views/debug/ref-terminate.htm">Terminate</a><br>
-  <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a> <br>
-  <a href="../../../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminaterelaunch.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminaterelaunch.htm
deleted file mode 100644
index 33a2970..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-terminaterelaunch.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Terminate and Relaunch</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Terminate and Relaunch </h1>
-<p> Select the <strong>Terminate and Relaunch</strong> command [ <img src="../../../images/org.eclipse.debug.ui/etool16/term_restart.png" alt="Terminate and Relaunch"> ]  to first terminate the selected debug target and secondly, relaunch it.</p>
-<p>Once a launch is terminated it can be automatically removed  from the <strong>Debug View</strong>. To change this setting use the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launching preference page"> <strong>Run/Debug &gt; Launching</strong></a> preference page.</p>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-removeallterminated.htm">Remove All Terminated Launches</a> <br>
-  <a href="../../../reference/views/debug/ref-terminate.htm">Terminate</a><br>
-  <a href="../../../reference/views/debug/ref-terminateall.htm">Terminate/Disconnect All</a><br>
-  <a href="../../../reference/views/debug/ref-terminateandremove.htm">Terminate and Remove</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-usestepfilters.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-usestepfilters.htm
deleted file mode 100644
index b6b68cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/debug/ref-usestepfilters.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Use Step Filters</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Use Step Filters </h1>
-<p> Select the <strong>Use Step Filters </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/stepbystep_co.png" alt="Use Step Filters"> ] to change whether step filters should be used in the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. You can also use the keyboard shortcut <em><strong>Shift+F5</strong></em>. </p>
-<p>Step filters are commonly used to filter out types that you do not wish to see or step through while debugging.</p>
-<p>For example, if you did not want to the see or step through anything from the class <em><strong>java.lang.Object</strong></em>, you would add this to the list of filtered types. Adding types to the list of those to be filtered can be done in one of two ways:</p>
-<ol>
-  <li>Via the context menu - Right click on the stack frame for the type you wish to filter and use the <strong><a href="../../../reference/views/debug/ref-filtertype.htm">Filter Type</a></strong> or <strong><a href="../../../reference/views/debug/ref-filterpackage.htm">Filter Package</a></strong> command. </li>
-  <li>Via the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaStepFilterPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Step Filtering preference page"> <strong>Java &gt; Debug &gt; Step Filtering</strong></a> preference page. </li>
-</ol>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../../../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../../../concepts/cremdbug.htm">Remote debugging</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../../../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-  <a href="../../../tasks/task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../../../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../../../tasks/task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="../../../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../../../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../../../tasks/task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../../../reference/views/debug/ref-debug_view.htm">Debug View</a><br>
-  <a href="../../preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../../../reference/views/debug/ref-executioncontrolcommands.htm">Execution Control Commands</a><br>
-  <a href="../../../reference/views/debug/ref-editstepfilters.htm">Edit Step Filters</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/display/images/ref-display_view.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/display/images/ref-display_view.PNG
deleted file mode 100644
index ec18622..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/display/images/ref-display_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-clear.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-clear.htm
deleted file mode 100644
index 3903e34..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-clear.htm
+++ /dev/null

@@ -1,17 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Clear</title>
-</head>
-<body>
-<h1> Clear </h1>
-<p> Select the <strong>Clear</strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/clear_co.png" alt="Clear the view"> ] to remove all of the contents from the view. </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="ref-display_view.htm">Display View</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-display_view.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-display_view.htm
deleted file mode 100644
index 32560eb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/display/ref-display_view.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Display View</title>
-</head>
-<body>
-<h1> Display View </h1>
-<p> The <strong>Display View</strong> displays the result of evaluating an expression in the context of the current stack frame. You can evaluate and display a selection either from the editor or
-  directly from the <strong>Display View</strong>.</p>
-<p><img src="../../../reference/views/display/images/ref-display_view.PNG" alt="Display View"></p>
-<p>The commands available in the display view are listed below.</p>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-  Display View Commands
-  </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> <p> Name </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Availability </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/clear_co.png" alt="Clear View"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><strong><a href="../../../reference/views/display/ref-clear.htm">Clear</a></strong></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Clears the current contents of the view. </p></td>
-      <td>Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy Selected Statements"></td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-copy.htm">Copy</a></strong></td>
-      <td colspan="1" valign="top" align="left" >Copies the selected statements to the system clipboard. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/metharg_obj.png" alt="Content Assist"></td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-contentassist.htm">Content Assist </a></strong></td>
-      <td colspan="1" valign="top" align="left" >Opens the content assist popup for context sensitive coding assistance </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/cut_edit.png" alt="Cut Selected Statements"></td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-cut.htm">Cut</a></strong></td>
-      <td colspan="1" valign="top" align="left" >Copies the selected statements to the system clipboard and removes them from the view. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" alt="Display Result"></td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-display.htm">Display </a></strong></td>
-      <td colspan="1" valign="top" align="left" >Displays the result of the selected statement inline in the view. </td>
-      <td>Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png" alt="Evaluate Result" ></td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-execute.htm">Execute</a></strong></td>
-      <td colspan="1" valign="top" align="left" >Runs the selected statement. This action is analogous to running the statement in normal code. </td>
-      <td>Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-findreplace.htm">Find/Replace</a></strong></td>
-      <td colspan="1" valign="top" align="left" >Allows you to search for and replace specific statements, or portions of statements </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" alt="Inspect Result"></td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-inspect.htm">Inspect Result</a></strong> </td>
-      <td colspan="1" valign="top" align="left" >Allows you to inspect what the return value of the selected statement will be. </td>
-      <td>Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/paste_edit.png" alt="Paste"></td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-paste.htm">Paste</a></strong></td>
-      <td colspan="1" valign="top" align="left" >Copies material from the system clipboard into the view </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><strong><a href="../../../reference/views/shared/ref-selectall.htm">Select All</a></strong> </td>
-      <td colspan="1" valign="top" align="left" >Selects all of the statements in the view </td>
-      <td>Context menu </td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../ref-viewsandeditors.htm">Views and editors</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-addwatchexpression_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-addwatchexpression_dialog.PNG
deleted file mode 100644
index f8a03f8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-addwatchexpression_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-convert.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-convert.PNG
deleted file mode 100644
index 37fd021..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-convert.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-disable.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-disable.PNG
deleted file mode 100644
index e62ad02..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-disable.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit.PNG
deleted file mode 100644
index 07dea79..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit_dialog.PNG
deleted file mode 100644
index 3bf246a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-edit_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-enable.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-enable.PNG
deleted file mode 100644
index 51be452..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-enable.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-expressions_view.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-expressions_view.PNG
deleted file mode 100644
index 93f4b98..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-expressions_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-java.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-java.PNG
deleted file mode 100644
index 2169603..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-java.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-reevaluate.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-reevaluate.PNG
deleted file mode 100644
index 3a9180b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/images/ref-reevaluate.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-addwatch.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-addwatch.htm
deleted file mode 100644
index 7b88c08..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-addwatch.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Add Watch Expression</title>
-</head>
-<body>
-<h1> Add Watch Expression</h1>
-<p> Select the <strong>Add Watch Expression </strong>command [ <img src="../../../images/org.eclipse.debug.ui/obj16/expression_obj.png" alt="Add Watch Expression"> ] to open the create new expression dialog, which allows you to create a new watch expression and add it to the <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong>.</p>
-<p>The add watch expression dialog.</p>
-<p><img src="../../../reference/views/expressions/images/ref-addwatchexpression_dialog.PNG" alt="Add Watch Expression Dialog"></p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-convert.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-convert.htm
deleted file mode 100644
index 33bb394..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-convert.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Convert to Watch Expression</title>
-</head>
-<body>
-<h1> Convert to Watch Expression</h1>
-<p> Select the <strong>Convert to Watch Expression </strong> command to convert the currently selected inspect expression to a watch expression.</p>
-<p><em><strong>Note</strong></em>: the inspect expression is removed from the view once the watch expression is created.</p>
-<p><img src="../../../reference/views/expressions/images/ref-convert.PNG" alt="Convert to Watch Expression"> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-disable.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-disable.htm
deleted file mode 100644
index 6a0bfe3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-disable.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Disable Watch Expression</title>
-</head>
-<body>
-<h1> Disable Watch Expression</h1>
-<p> Select the <strong>Disable</strong> command to disable the selected watch expression.</p>
-<p><img src="../../../reference/views/expressions/images/ref-disable.PNG" alt="Disable Watch Expression"></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-  <a href="../../../reference/views/expressions/ref-enable.htm">Enable Watch Expression</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-edit.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-edit.htm
deleted file mode 100644
index be4fa09..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-edit.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Edit Watch Expression...</title>
-</head>
-<body>
-<h1> Edit Watch Expression...</h1>
-<p> Select the <strong>Edit Watch Expression ...</strong> command to open the editing dialog for the selected watch expression.</p>
-<p>The edit watch expression command.</p>
-<p><img src="../../../reference/views/expressions/images/ref-edit.PNG" alt="Edit Watch Expression"></p>
-<p>The resulting edit dialog. </p>
-<p><img src="../../../reference/views/expressions/images/ref-edit_dialog.PNG" alt="Edit Watch Expression Dialog"></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-enable.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-enable.htm
deleted file mode 100644
index 40461e1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-enable.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Enable Watch Expression</title>
-</head>
-<body>
-<h1> Enable Watch Expression</h1>
-<p> Select the <strong>Enable</strong> command to enable the selected watch expression. The expression must be disabled for this command to be available. </p>
-<p><img src="../../../reference/views/expressions/images/ref-enable.PNG" alt="Enable Watch Expression"></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-<a href="../../../reference/views/expressions/ref-disable.htm">Disable Watch Expression</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-expressions_view.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-expressions_view.htm
deleted file mode 100644
index 01b413e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-expressions_view.htm
+++ /dev/null

@@ -1,208 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Expressions View</title>
-</head>
-<body>
-<h1> Expressions View </h1>
-<p> Data can be inspected in the <strong>Expressions View</strong>. You can inspect data from a 
-  scrapbook page, a stack frame of a suspended thread, and other places. The Expressions 
-  View opens automatically when an item is added to the view. Entries in the Expressions View can be selected to have more detailed information be displayed in the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a>. When debugging a Java program, data that contains variables can be expanded to show the variables and the fields the variables contain.</p>
-<p>The Expressions View. The <a href="../../../reference/views/shared/ref-detailpane.htm"></a> detail pane is the  area at the bottom of the view displaying text..</p>
-<p><img src="../../../reference/views/expressions/images/ref-expressions_view.PNG" alt="Expressions View"></p>
-<p>There are many commands available in the Expressions View:</p>
-<ul>
-  <li><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm"><strong>View Display Commands</strong></a> affect what data and variables are displayed and how they are presented.</li>
-  <li>The <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> has many commands available by right clicking on it.</li>
-  <li><a href="../../../reference/views/shared/ref-viewlayoutcommands.htm"><strong>View Layout Commands</strong></a> affect how the detail pane is oriented.</li>
-  <li>Other commands are listed below. </li>
-</ul>
-<table border="1" cellpadding="5" cellspacing="0">
-  <caption>
-  Variables View Commands
-  </caption>
-  <thead>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/expression_obj.png" alt="Add Watch Expression"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-addwatch.htm"><strong>Add Watch Expression</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to add a watch expression.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png" alt="All References"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-allinstances.htm"><strong>All Instances</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens a popup dialog displaying a list of all instances of the selected Java type. Your Java virtual machine must support instance retrieval. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_references.png" alt="All References"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-allreferences.htm"><strong>All References</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens a popup dialog displaying a list of all Java objects that have references to the selected variable. Your Java virtual machine must support reference retrieval. </td>
-      <td>Context menu </td>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png" alt="Change Value"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-changevarvalue.htm"><strong>Change Value...</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to change the value for the underlying selected variable.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/collapseall.png" alt="Collapse All"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-collapseall.htm"><strong>Collapse All</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Collapses all the the currently expanded variables.</td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy Expressions"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><a href="../../../reference/views/shared/ref-copy.htm"><strong>Copy Expressions </strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Copies the selected  expressions and variables to the system clipboard.</p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-convert.htm"><strong>Convert to Watch Expression</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Converts the selected inspect expression to a corresponding watch expression.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-disable.htm"><strong>Disable</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Disables a currently enabled expression.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" >Edit Logical Structure </td>
-      <td colspan="1" valign="top" align="left" >Allow you to edit the logical structure of the selected variable </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-edit.htm"><strong>Edit Watch Expression</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to edit the currently selected expression.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-enable.htm"><strong>Enable</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Enables a currently disabled expression.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-find.htm"><strong>Find...</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens the search dialog to find elements in the variables view.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png" alt="Inspect"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-inspectvariable.htm"><strong>Inspect</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Creates a new inspect expression for the selected variable and adds it to the view.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Instance Breakpoints...</td>
-      <td colspan="1" valign="top" align="left">Allows you to filter existing breakpoints to the selected variable instance.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-preferences.htm"><strong>Java Preferences...</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens several preference pages containing options that affect the  view. </td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">New Detail Formatter...</td>
-      <td colspan="1" valign="top" align="left">Allows you to create your own detail formatter for that type of variable.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Actual Type </td>
-      <td colspan="1" valign="top" align="left">Opens the actual type of the selected variable.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Actual Type Hierarchy </td>
-      <td colspan="1" valign="top" align="left">Opens the actual type hierarchy for the actual type of the selected variable. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Declared Type </td>
-      <td colspan="1" valign="top" align="left">Opens the declared type for the selected variable in a new editor. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Declared Type Hierarchy </td>
-      <td colspan="1" valign="top" align="left">Opens the type hierarchy for the declared type of the selected variable. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-reevaluate.htm"><strong>Reevaluate Expression</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Reevaluates the currently selected expression.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/rem_co.png" alt="remove Selected Expression(s)"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-remove.htm"><strong>Remove</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Removes the currently selected expression(s) from the view.</td>
-      <td>Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/expressions/ref-removeall.htm"><strong>Remove All</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Removes all of the expressions from the view. </td>
-      <td>Context menu and view action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-selectall.htm"><strong>Select All</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Selects all of the variables in the view.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" >Show Structure As... </td>
-      <td colspan="1" valign="top" align="left" >Allows you to select a different formatter for showing the selected logical structure type variable. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" >Show Details As... </td>
-      <td colspan="1" valign="top" align="left" >Allows you to select a different detail pane for showing detailed information about selected variables. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png" alt="Toggle Watchpoint"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-togglewp.htm"><strong>Toggle Watchpoint </strong></a></td>
-      <td colspan="1" valign="top" align="left" > Creates a new watchpoint on the currently selected field or removes the watchpoint if one already exists. </td>
-      <td>Context menu </td>
-    </tr>
-  </tbody>
-</table>
-<p><img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../../../concepts/cscrapbook.htm">Scrapbook</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a><br>
-  <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p><a href="../../views/shared/ref-detailpane.htm">Detail Pane<br>
-  </a><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a><br>
-  <a href="../../../reference/views/shared/ref-viewlayoutcommands.htm">View Layout Commands</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-inspect.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-inspect.htm
deleted file mode 100644
index c79591c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-inspect.htm
+++ /dev/null

@@ -1,17 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Inspect Watchpoint Variable</title>
-</head>
-<body>
-<h1> Inspect Watchpoint Variable </h1>
-<p> Select the <strong>Inspect</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png" alt="Inspect Watchpoint Variable"> ] to inspect the selected variable in the <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong>. You can also use the keyboard shortcut <em><strong>Ctrl+Shift+I</strong></em>. </p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-reevaluate.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-reevaluate.htm
deleted file mode 100644
index 87cb0d2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-reevaluate.htm
+++ /dev/null

@@ -1,18 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Reevaluate Watch Expression</title>
-</head>
-<body>
-<h1> Reevaluate Watch Expression </h1>
-<p> Select the <strong>Reevaluate Watch Expression </strong> command to force the selected watch expression to be evaluated.</p>
-<p><img src="../../../reference/views/expressions/images/ref-reevaluate.PNG" alt="Reevaluate Watch Expression"></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-remove.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-remove.htm
deleted file mode 100644
index 6f6b793..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-remove.htm
+++ /dev/null

@@ -1,18 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Remove Selected Expressions</title>
-</head>
-<body>
-<h1> Remove Selected Expressions</h1>
-<p> Select the <strong>Remove</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/rem_co.png" alt="Remove Selected Expressions"> ] to remove the selected watch expression(s) from the <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong>.</p>
-<p>You can also perform this same action by selecting the expression(s) that you wish to remove and pressing the <strong>Delete</strong> key.</p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-removeall.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-removeall.htm
deleted file mode 100644
index e141568..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/expressions/ref-removeall.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css"> 
-    <title>
-      Remove All Expressions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Remove All Expressions </h1>
-    <p>
-    Select the <strong>Remove All Expressions</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/rem_all_co.png" alt="Remove All Expressions"> ] the remove all of the expressions from the <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong>.</p>
-    <p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-    <p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-call-hierarchy.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/ref-call-hierarchy.htm
deleted file mode 100644
index 58071d5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-call-hierarchy.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Call Hierarchy View</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>Call Hierarchy View</h1>
-<p>The Call Hierarchy view shows callers and callees for a selected Java member.</p>
-<table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Call hierarchy">
-	<caption>Call Hierarchy commands:</caption>
-	<thead>
-		<tr>
-			<th>
-			<p>Command</p>
-			</th>
-			<th>
-			<p>Description</p>
-			</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td valign="top">
-			<p>Refresh</p>
-			</td>
-			<td valign="top">
-			<p>Refresh the whole hierarchy</p>
-			</td>
-		</tr>	
-	
-		<tr>
-			<td valign="top">
-			<p>Cancel Current Search</p>
-			</td>
-			<td valign="top">
-			<p>Cancel the current running search. Useful for long running searches.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Show Caller Hierarchy</p>
-			</td>
-			<td valign="top">
-			<p>Show all callers in the search scope of the selected member.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Show Callee Hierarchy</p>
-			</td>
-			<td valign="top">
-			<p>Show all members which are called by the currently selected member.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Show History List</p>
-			</td>
-			<td valign="top">
-			<p>This menu displays a history of previously displayed call hierarchies.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Layout</p>
-			</td>
-			<td valign="top">
-			<p>Specifies the layout of the call hierarchy views</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Field Accesses</p>
-			</td>
-			<td valign="top">
-			<p>Specifies which field accesses to show: Read or write accesses, or both</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Search Scope</p>
-			</td>
-			<td valign="top">
-			<p>Defines the scope for the search for callers.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Filters</p>
-			</td>
-			<td valign="top">
-			<p>Specifies the patterns whose matching members will be hidden from the view.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Expand with Constructors (context menu)</p>
-			</td>
-			<td valign="top">
-			<p>Expands and replaces an instance method's normal children with:</p>
-			<ul> 
-				<li>the constructors of the method's declaring class</li> 
-				<li>a node that contains the direct callers of the method</li>
-			</ul>
-			<p>This is especially useful for methods in anonymous classes.</p>	   
-			</td>
-		</tr>
-		<tr>
-			<td valign="top">
-			<p>Expand with Constructors...</p>
-			</td>
-			<td valign="top">
-			<p>Specifies the list of types whose instance methods are expanded with constructors by default. The feature can also be 
-			enabled or disabled for all methods declared in anonymous types at once using the <strong>All methods 
-			in anonymous types</strong> option.</p>
-			</td>
-		</tr>
-	</tbody>
-</table>
-<p><img border="0" src="../../images/ngrelr.png" alt="Related reference"></p>
-<p><a href="ref-viewsandeditors.htm">Views and editors</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm
deleted file mode 100644
index 2738a3a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-java-editor.htm
+++ /dev/null

@@ -1,261 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Java editor
-    </title>
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Java editor
-    </h1>
-    <h2 class="Head">
-      Toolbar actions
-    </h2>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Toolbar actions">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Toolbar Button
-            </p>
-          </th>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-        <td align="center" valign="top">
-            <p><img src="../../images/org.eclipse.jdt.ui/etool16/toggle_breadcrumb.gif" alt="Toggle Java Editor Breadcrumb"></p>
-          </td>
-          <td valign="top">
-            <p>
-              Toggle Java Editor Breadcrumb
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This button enables the Java editor breadcrumb.
-            </p>
-            <p>
-              The enablement is remembered for each perspective separately.
-            </p>
-          </td>
-        </tr>
-      
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../../images/org.eclipse.jdt.ui/etool16/mark_occurrences.png" alt="Toggle Mark Occurrences"></p>
-          </td>
-          <td valign="top">
-            <p>
-              Toggle Mark Occurrences
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Turns <a href="../preferences/java/editor/ref-preferences-mark-occurrences.htm">mark occurrences</a> on and off in the Java editor.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../../images/org.eclipse.ui.workbench.texteditor/etool16/block_selection_mode.gif" alt="Toggle Block Selection Mode"></p>
-          </td>
-          <td valign="top">
-            <p>
-              Toggle Block Selection Mode
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This button enables block (aka column) selection mode in the editor.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../../images/org.eclipse.ui.editors/etool16/show_whitespace_chars.gif" alt="Show Whitespace Characters"></p>
-          </td>
-          <td valign="top">
-            <p>
-              Show Whitespace Characters
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This button enables the display of whitespace characters in an editor.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../../images/org.eclipse.jdt.ui/etool16/segment_edit.png" alt="Show Source of Selected Element Only"></p>
-          </td>
-          <td valign="top">
-            <p>
-              Show Source of Selected Element Only
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This button enabled display of a segmented view of the source of a compilation unit.
-            </p>
-            <p>
-              This button is only shown if you <a href="../../../org.eclipse.platform.doc.user/tasks/tasks-9k.htm">customize your perspective</a> to show the <strong>Editor Presentation</strong> actions.
-            </p>
-            <p>
-              For example, if a method is selected in the Outline view, the <strong>Show Source Of Selected Element Only</strong> option causes only that method to be displayed in
-              the editor, as opposed to the entire class.
-            </p>
-            <p>
-                <strong>Off</strong>:
-                The entire compilation unit is displayed in the editor, with the selected Java element highlighted in the marker bar with a range indicator.</p>
-            <p>
-                <strong>On</strong>:
-                Only the selected Java element is displayed in the editor, which is linked to the selection in the Outline or Hierarchy view.</p>
-          </td>
-        </tr>
-        
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../../images/org.eclipse.ui.editors/etool16/next_nav.png" alt="Go to Next Problem"></p>
-          </td>
-          <td valign="top">
-            <p>
-              Go to Next Problem
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command navigates to the next problem marker in the active editor.
-            </p>
-          </td>
-        </tr>
-        
-        <tr>
-          <td align="center" valign="top">
-            <p><img src="../../images/org.eclipse.ui.editors/etool16/prev_nav.png" alt="Go to Previous Problem"></p>
-          </td>
-          <td valign="top">
-            <p>
-              Go to Previous Problem
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command navigates to the previous problem marker in the active editor.
-            </p>
-          </td>
-        </tr>
-        
-      </tbody>
-    </table>
-    <h2 class="Head">
-      Key binding actions
-    </h2>
-    <p>
-      The following actions can only be reached through key bindings. The <strong>Key bindings</strong> field in <strong>Window &gt; Preferences &gt; General &gt;
-      Keys </strong> must be set to 'Emacs'.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Key binding actions">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Key binding
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Alt</kbd>+<kbd>0</kbd> <kbd>Ctrl</kbd>+<kbd>K</kbd>, <kbd>Esc</kbd> <kbd>0</kbd> <kbd>Ctrl</kbd>+<kbd>K</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Deletes from the cursor position to the beginning of the line.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Ctrl</kbd>+<kbd>K</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Deletes from the cursor position to the end of the line.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Ctrl</kbd>+<kbd>Space</kbd>, <kbd>Ctrl</kbd>+<kbd>2</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Sets a mark at the current cursor position.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              <kbd>Ctrl</kbd>+<kbd>X</kbd> <kbd>Ctrl</kbd>+<kbd>X</kbd>
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Swaps the cursor and mark position if any.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../../images/ngrelt.png" alt="Related tasks" border="0" >
-      </p>
-      <p>
-       <a href="../../tasks/tasks-73.htm">Opening an editor for a selected element</a>
-    </p>
-    <p>
-      <img src="../../images/ngrelr.png"  alt="Related reference"></p>
-      <p>
-      <a href="ref-view-outline.htm">Java outline</a><br>
-      <a href="../../reference/preferences/java/ref-preferences-editor.htm">Java editor preferences</a><br>
-      <a href="../../reference/ref-jdt-actions.htm">JDT actions</a><br>
-      <a href="ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-type-hierarchy.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/ref-type-hierarchy.htm
deleted file mode 100644
index 7610ac6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-type-hierarchy.htm
+++ /dev/null

@@ -1,224 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <title>
-      Type Hierarchy View
-    </title>
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Type Hierarchy View
-    </h1>
-    <p>
-      This view shows the hierarchy of a type. The Type Hierarchy view consists of two panes:
-    </p>
-    <ul>
-      <li>
-        Type Hierarchy tree pane
-      </li>
-      <li>
-        Member list pane (optional)
-      </li>
-    </ul>
-    <h2 class="Head">
-      Type Hierarchy tree pane toolbar buttons
-    </h2>
-    <p>
-    The type hierarchy tree shows supertypes, suptypes or both of a given type depending on the selection made in the
-    toolbar.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Hierarchy viewer">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Previous Hierarchy Inputs
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This menu displays a history of previously displayed type hierarchies.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show the Type Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command displays the type in its full context (i.e., superclasses and subclasses) in the Hierarchy view. To see for which type the hierarchy is shown, hover
-              over the view title (e.g., &quot;Types&quot;).
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show the Supertype Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command displays the supertypes and the hierarchy of all implemented interfaces of the type in the Hierarchy view. The tree starts at the selected type and
-              displays the result of traversing up the hierarchy.
-            </p>
-             <em>Note: The selected type is always at the top level, in the upper-left corner.</em>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show the Subtype Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This command displays the subtypes of the selected class and/or all implementors of the interface in the Hierarchy view. The tree starts at the selected type and
-              displays the result of traversing down the hierarchy
-            </p>
-             <em>Note: The selected type is always at the top level, in the upper-left corner.</em>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Layout &gt; Hierarchy View Only
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Hides the member list pane.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h2 class="Head">
-      Member list pane toolbar buttons
-    </h2>
-    <p>
-      The member list pane displays the members of the currently selected type in the type hierarchy tree pane.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Member viewer">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Lock View and Show Members in Hierarchy
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows the members implementing the selected method Only types implementing the method are shown.
-            </p>
-            <p>
-              When the view is locked, the member list pane no longer tracks the selection in the hierarchy pane above.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Show All Inherited Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides all methods and fields inherited by base classes. When this option is set, the name of the type that defines the method is appended to the method
-              name.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Sort Members by the Defining Type
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Sorts the members according to the type in which they are defined.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Fields
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the fields.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Static Fields and Methods
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Non-Public Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0"  src="../../images/ngrelr.png" alt="Related reference"></p>
-      <p>
-      <a href="ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm
deleted file mode 100644
index 120ea07..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm
+++ /dev/null

@@ -1,139 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Java outline
-    </title>
-  </head>
-  <body>
-    <h1>
-      Java outline
-    </h1>
-    <p>
-      This view displays an outline of the structure of the currently-active Java file in the editor area.
-    </p>
-    <h2 class="Head">
-      Toolbar buttons
-    </h2>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Outline view">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Go into Top Level Type
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Makes the top level type of the compilation unit the new input for this view.
-              Package declaration and import statements are no longer shown.
-            </p>
-         </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Sort
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              This option can be toggled to either sort the outline elements in alphabetical order or sequential order, as defined 
-              on the <a href="../preferences/java/appearance/ref-preferences-member-sort-order.htm"><b>Java &gt; Appearance &gt; Member Sort Order</b></a> preference page.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Fields
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the fields.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-             Hide Static Fields and Methods
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Non-Public Members
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the static fields and methods.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Hide Local Types
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows or hides the local types.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img src="../../images/ngrelc.png" alt="Related concepts" border="0" ></p>
-      <p>
-      <a href="../../concepts/concept-java-editor.htm">Java editor</a><br>
-      <a href="../../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../../concepts/concept-java-views-filtering.htm">Filtering in Java views</a><br>
-       <a href="../../concepts/concept-java-views-decorators.htm">Java element decorations</a><br>
-       <a href="../../concepts/concept-java-views-sorting.htm">Sorting elements in Java views</a><br>
-       <a href="../../concepts/concept-java-views-presentation.htm">Presentation options for Java views</a>
-    </p>
-    <p>
-       <img border="0" src="../../images/ngrelt.png" alt="Related tasks" ></p>
-       <p>
-       <a href="../../tasks/tasks-64.htm">Restoring a deleted workbench element</a><br>
-       <a href="../../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../../images/ngrelr.png" alt="Related reference" ></p>
-      <p>
-      <a href="../../reference/ref-dialog-override-method.htm">Override methods</a><br>
-       <a href="ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-package-explorer.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-package-explorer.htm
deleted file mode 100644
index 929e62f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-package-explorer.htm
+++ /dev/null

@@ -1,167 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Package Explorer View
-    </title>
-  </head>
-  <body>
-    <h1>
-      Package Explorer View
-    </h1>
-    <p>
-      The Package Explorer view, shown by default in the Java perspective, shows the Java element hierarchy of the Java projects in your workbench. It provides you with a
-      Java-specific view of the resources shown in the Navigator. The element hierarchy is derived from the project's build paths.
-    </p>
-    <p>
-      For each project, its source folders and referenced libraries are shown in the tree. You can open and browse the contents of both internal and external JAR files. Opening a
-      Java element inside a JAR opens the CLASS file editor, and if there is a source attachment for the JAR file, its corresponding source is shown.
-    </p>
-    <h1>
-      Toolbar buttons
-    </h1>
-    <table border="1" cellspacing="0" cellpadding="5" width="100%" summary="Toolbar buttons">
-      <thead>
-        <tr>
-          <th>
-            <p>
-              Command
-            </p>
-          </th>
-          <th>
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td valign="top">
-            <p>
-              Back
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Navigates to the most recently-displayed state of the view with a different element at the top level.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Forward
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Navigates to the state of the view with a different element at the top level that was displayed immediately after the current state.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Up
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Navigates to the parent container of the package that is currently displayed at the top level in the view.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Collapse All
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Collapses all tree nodes.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Link with Editor
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-            Links the package explorer's selection to the active editor.</p>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Top Level Elements &gt; Projects
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows project as top level elements in the Package Explorer. Only projects which are
-              part of the currently active working sets are shown. Following actions can be used
-              to configure the active working sets:
-			</p>
-              <ul>
-              	<li><b>Select Working Set:</b> Opens the <strong>Select Working Set</strong> dialog to allow selecting the working set from which elements should be shown.</li>
-              	<li><b>Deselect Working Set:</b> Deselect the active working sets. All elements are shown after invoking this action</li>
-              	<li><b>Edit Active Working Set:</b> Opens the <strong>Edit Working Set</strong> wizard to edit the currently active working set</li>
-              </ul>
-          </td>
-        </tr>
-        <tr>
-          <td valign="top">
-            <p>
-              Top Level Elements &gt; Working Sets
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Shows Working Sets as top level elements in the Package Explorer. 
-			</p>
-			<p>
-			  The <b>Configure Working Sets...</b> action can be used to open a dialog which allows to configure the visible working sets. 
-			</p>
-          </td>
-        </tr>
-        
-        <tr>
-          <td valign="top">
-            <p>
-              Filters...
-            </p>
-          </td>
-          <td valign="top">
-            <p>
-              Opens the <a href="../ref-dialog-java-element-filters.htm"><strong>Java element filters</strong></a> dialog.
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0" src="../../images/ngrelc.png" alt="Related concepts" ></p>
-      <p>
-       <a href="../../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-       <a href="../../../org.eclipse.platform.doc.user/concepts/cworkset.htm">Working sets</a>
-    </p>
-    <p>
-      <img border="0" src="../../images/ngrelr.png" alt="Related reference" ></p>
-      <p>
-      <a href="../../reference/ref-dialog-java-element-filters.htm">Java element filters dialog</a><br>
-       <a href="ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-scrapbook.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-scrapbook.htm
deleted file mode 100644
index 8fdaa8c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-view-scrapbook.htm
+++ /dev/null

@@ -1,147 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Java Scrapbook Page
-    </title>
-  </head>
-  <body>
-    <h1>
-      Java Scrapbook Page
-    </h1>
-    <p>
-      The scrapbook allows Java expressions to be run, inspected, and displayed, under the control of the debugger.
-    </p>
-    <p>
-      <strong>Note:</strong> Content assist (such as code assist) is available on scrapbook pages.
-    </p>
-    <table border="1" cellspacing="0" cellpadding="5" summary="Scrapbook options">
-      <caption>
-        Java Scrapbook page buttons
-      </caption>
-      <thead>
-        <tr>
-          <th rowspan="1" colspan="1">
-            <p>
-              Command
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Name
-            </p>
-          </th>
-          <th rowspan="1" colspan="1">
-            <p>
-              Description
-            </p>
-          </th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../../images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png" align="middle"  alt="Run Snippet button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Run Snippet
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Running an expression evaluates an expression but does not display a result.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" align="middle"  alt="Display button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Display
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Displaying shows the result of evaluating an expression as a string in the scrapbook editor.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" align="middle"  alt="Inspect button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Inspect
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Inspecting shows the result of evaluating an expression in the Expressions view.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../../images/org.eclipse.jdt.debug.ui/etool16/term_sbook.png" align="middle"  alt="Terminate button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Terminate
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This command terminates the Java VM that is used to evaluate expressions.
-            </p>
-          </td>
-        </tr>
-        <tr>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <img src="../../images/org.eclipse.jdt.ui/obj16/impc_obj.png" align="middle"  alt="Set the import Declarations button">
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              Set the Import Declarations
-            </p>
-          </td>
-          <td rowspan="1" colspan="1" valign="top" align="left">
-            <p>
-              This commands sets the import declarations to be used for the context of evaluating the code
-            </p>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <p>
-      <img border="0" src="../../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../../concepts/cscrapbook.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../../tasks/task-create_scrapbook_page.htm">Creating a Java scrapbook page</a><br>
-       <a href="../../tasks/task-display_evaluation_result.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="../../tasks/task-inspect_evaluation_result.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="../../tasks/task-executing_an_expression.htm">Executing an expression</a>
-    </p>
-    <p>
-       <img src="../../images/ngrelr.png"  alt="Related reference">
-    </p>
-    <p>
-      <a href="../../reference/ref-wizard-scrapbook.htm">New Java scrapbook page wizard</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-viewsandeditors.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/ref-viewsandeditors.htm
deleted file mode 100644
index 32a1553..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/ref-viewsandeditors.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-     Java Views and Editors
-    </title>
-  </head>
-  <body>
-    <h1>
-      Java Views and Editors    </h1>
-    <p>
-      <img border="0" src="../../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../../concepts/concept-java-editor.htm">Java editor</a><br>
-       <a href="../../concepts/concept-java-views.htm">Java views<br>
-      </a> <a href="../../concepts/concept-jdt.htm">Java development tools (JDT)</a> <a href="../../concepts/concept-java-views.htm">
-      </a>
-    </p>
-    <p>
-      <img border="0" src="../../images/ngrelt.png" alt="Related tasks" >
-    </p>
-    <p>
-      <a href="../../tasks/tasks-consoleAppearance.htm">Changing the appearance of the console view</a><br>
-       <a href="../../tasks/tasks-73.htm">Opening an editor for a selected element</a><br>
-       <a href="../../tasks/tasks-76.htm">Opening an editor on a type</a>
-    </p>
-    <p>
-      <img border="0" src="../../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../views/ref-java-editor.htm">Java editor actions</a><br>
-       <a href="breakpoints/ref-breakpoints_view.htm">Breakpoints view</a><br>
-       <a href="console/ref-console_view.htm">Console view</a><br>
-       <a href="debug/ref-debug_view.htm">Debug view</a><br>
-       <a href="display/ref-display_view.htm">Display view</a><br>
-       <a href="expressions/ref-expressions_view.htm">Expressions view</a><br>
-       <a href="../views/ref-java-editor.htm">Java editor</a><br>
-       <a href="ref-view-package-explorer.htm">Package explorer view</a><br>
-       <a href="variables/ref-variables_view.htm">Variables view</a><br>
-       <a href="ref-view-outline.htm">Java outline</a><br>
-       <a href="../views/ref-view-scrapbook.htm">Java scrapbook Page</a><br>
-       <a href="ref-type-hierarchy.htm">Type hierarchy view</a><br>
-       <a href="ref-call-hierarchy.htm">Call hierarchy view</a>
-    </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-action.png b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-action.png
deleted file mode 100644
index cb8beb8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-action.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-code.png b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-code.png
deleted file mode 100644
index d3b2449..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/force-return-code.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeobjectvalue.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeobjectvalue.PNG
deleted file mode 100644
index 9c8fc9c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeobjectvalue.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeprimitivevalue.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeprimitivevalue.PNG
deleted file mode 100644
index 9a54527..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changeprimitivevalue.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changestringvalue.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changestringvalue.PNG
deleted file mode 100644
index fedd6ff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-changestringvalue.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-contentassist.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-contentassist.PNG
deleted file mode 100644
index 7008db4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-contentassist.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane.PNG
deleted file mode 100644
index ce2a71e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane_dialog.PNG
deleted file mode 100644
index 11eb8ad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-detailpane_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-displayresult.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-displayresult.PNG
deleted file mode 100644
index 047d177..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-displayresult.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-find_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-find_dialog.PNG
deleted file mode 100644
index e3f0c55..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-find_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-findreplace_dialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-findreplace_dialog.PNG
deleted file mode 100644
index c3a7d20..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-findreplace_dialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-inspectresult.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-inspectresult.PNG
deleted file mode 100644
index da23b0a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-inspectresult.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-javapreferences.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-javapreferences.PNG
deleted file mode 100644
index bbed127..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-javapreferences.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectcolumnsdialog.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectcolumnsdialog.PNG
deleted file mode 100644
index 0b18656..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectcolumnsdialog.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectedstatement.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectedstatement.PNG
deleted file mode 100644
index 8012eb4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-selectedstatement.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-showreferences.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-showreferences.PNG
deleted file mode 100644
index 89f2909..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-showreferences.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewdisplaycommands.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewdisplaycommands.PNG
deleted file mode 100644
index bd1b8e6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewdisplaycommands.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewlayoutmenu.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewlayoutmenu.PNG
deleted file mode 100644
index c7e16a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/images/ref-viewlayoutmenu.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allinstances.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allinstances.htm
deleted file mode 100644
index 673e603..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allinstances.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>All Instances</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> All Instances </h1>
-<p> Select the <strong>All Instances </strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png" alt="All References"> ]  to open a popup containing a list of all Java object instances of the selected type that exist in the current debug target. The command has a keyboard shortcut of <em><strong>Ctrl+Shift+N</strong></em>. This command is only available if the Java virtual machine you are currently using supports instance retrieval. </p>
-<p>The type to search for can be selected in several ways:</p>
-<ul>
-  <li>In the <a href="../../../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a>, highlight or place the cursor in the name of a type or a constructor for a type.</li>
-  <li>In the <a href="../../../reference/views/ref-view-outline.htm"><strong>Outline View</strong></a>, select a type or constructor.</li>
-  <li>In the <a href="../expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> or <a href="../variables/ref-variables_view.htm"><strong>Variables View</strong></a>, select a Java object variable. </li>
-</ul>
-<p>Once the popup has opened, you can move the list to the <a href="../expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> by pressing <em><strong>Ctrl+Shift+I</strong></em>.</p>
-<p>There is a maximum number of instances the virtual machine will return. This maximum can be changed on the  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.HeapWalkingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Heap Walking preference page"> <strong>Java &gt; Debug &gt; Heap Walking</strong></a> preference page.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a></li>
-  <li><a href="../../../reference/views/ref-view-outline.htm"><strong>Outline View</strong></a><strong> </strong></li>
-  <li><a href="../expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img border="0" src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allreferences.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allreferences.htm
deleted file mode 100644
index 5c962b6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-allreferences.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>All References</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> All References </h1>
-<p> Select the <strong>All References... </strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_references.png" alt="All References"> ]  to open a popup containing a list of all Java objects in the current debug target that have references to the selected variable. The selected variable in the view must be a Java object. This command is only available if the Java virtual machine you are currently using supports reference retrieval.</p>
-<p>Once the popup has opened, you can move the list to the <a href="../expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> by pressing <em><strong>Ctrl+Shift+I</strong></em>.</p>
-<p>There is a maximum number of references the virtual machine will return. This maximum can be changed on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.HeapWalkingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Heap Walking preference page"> <strong>Java &gt; Debug &gt; Heap Walking</strong></a> preference page.</p>
-<p>This command applies to:</p>
-<ul><li><a href="../expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img border="0" src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a><br>
-  <a href="../../../reference/menus/run/ref-menu-run.htm">Run Menu</a></p></body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-assignvalue.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-assignvalue.htm
deleted file mode 100644
index 07ae3ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-assignvalue.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Assign Value</title>
-</head>
-<body>
-<h1> Assign Value</h1>
-<p> Select the <strong>Assign Value</strong> command to assign a new value to the currently selected variable by evaluating the text in the detail pane. </p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-changevarvalue.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-changevarvalue.htm
deleted file mode 100644
index 2d73003..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-changevarvalue.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Change Variable Value</title>
-</head>
-<body>
-<h1> Change Variable Value </h1>
-<p> Select the <strong>Change Value...</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png" alt="Change Variable Value"> ] to open a dialog in which you can change the value of the the selected variable or register.</p>
-<p>In the <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>, if variables are displayed in the column form, variable values can also can be changed by directly editing the value in the column.</p>
-<p>When debugging a Java program, there are three different types of dialogs that this command can open.</p>
-<p>The <strong>Change Primitive Value Dialog</strong> is used to change the value of a primitive such as an int, long, or char.</p>
-<p><img src="../../../reference/views/shared/images/ref-changeprimitivevalue.PNG" alt="Change Primitive Value Dialog"></p>
-<p>The <strong>Change Object Value Dialog</strong> is used to change the value of an Object. There are two forms of this dialog.</p>
-<p>For most objects you must enter an expression that will be evaluated to generate the resulting value.</p>
-<p><img src="../../../reference/views/shared/images/ref-changeobjectvalue.PNG" alt="Change Object Value Dialog - Expression"></p>
-<p>However, when editing Java Strings, you may also enter literal text.</p>
-<p><img src="../../../reference/views/shared/images/ref-changestringvalue.PNG" alt="Change Object Value Dialog - Literal Text"></p>
-<p>This command applies to:</p>
-<ul><li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Registers View </li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-collapseall.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-collapseall.htm
deleted file mode 100644
index 6eaa8ba..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-collapseall.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Collapse All</title>
-</head>
-<body>
-<h1> Collapse All </h1>
-<p> Select the <strong>Collapse All </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/collapseall.png" alt="Collapse All"> ] to collapse all of the currently elements in the view.</p>
-<p>This command applies to:</p>
-<ul>
-  <li> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a></li>
-  <li> <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li> Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-contentassist.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-contentassist.htm
deleted file mode 100644
index 34264d3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-contentassist.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Content Assist</title>
-</head>
-<body>
-<h1> Content Assist </h1>
-<p> Select the <strong>Content Assist </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/metharg_obj.png" alt="Content Assist"> ] to open the <strong>Content Assist</strong> popup dialog. You can also use the keyboard shortcut <em><strong>Ctrl+Spacebar</strong></em> within the view. </p>
-<p>The resulting dialog provides you with context sensitive coding help by making available a listing of all applicable java code elements for the location content assist was activated.</p>
-<p><img src="../../../reference/views/shared/images/ref-contentassist.PNG" alt="Content Assist Popup Dialog"></p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a></li>
-  <li><a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)<a href="../../../reference/views/shared/ref-detailpane.htm"></a></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-copy.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-copy.htm
deleted file mode 100644
index b02adf6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-copy.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Copy</title>
-</head>
-<body>
-<h1> Copy </h1>
-<p> Select the <strong>Copy</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy"> ] to copy the selected contents from the view onto the system clipboard. You can also use the standard keyboard shortcut <em><strong>Ctrl+C</strong></em>.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View </strong></a></li>
-  <li> <a href="../../../reference/views/console/ref-console_view.htm"><strong>Console View</strong></a></li>
-  <li><a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a></li>
-  <li> <a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View </strong></a></li>
-  <li> <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li> Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-</ul>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-cut.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-cut.htm
deleted file mode 100644
index a99c2c9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-cut.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-   <head>
-      <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-      <meta http-equiv="Content-Style-Type" content="text/css">
-      <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-      <title>Cut</title>
-   </head>
-   <body>
-      <h1> Cut </h1>
-      <p> Select the <strong>Cut</strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/cut_edit.png" alt="Cut"> ] to copy the selected contents from the view to the system clipboard and remove the selection from the view. You can also use the standard keyboard shortcut <em><strong>Ctrl+X</strong></em>.</p>
-      <p>This command applies to:</p>
-      <ul>
-         <li><a href="../../../reference/views/console/ref-console_view.htm"><strong>Console View</strong></a></li>
-         <li><a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a></li>
-         <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-      </ul>
-      <p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-detailpane.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-detailpane.htm
deleted file mode 100644
index 833c59e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-detailpane.htm
+++ /dev/null

@@ -1,124 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Detail Pane</title>
-</head>
-<body>
-<h1> Detail Pane </h1>
-<p> The <strong>Detail Pane</strong> displays detailed information about a selection 
-  in the following views:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Registers View </li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p>The <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> with the detail pane highlighted.</p>
-<p><img src="../../../reference/views/shared/images/ref-detailpane.PNG" alt="Detail Pane"></p>
-<p>By default, the <strong>Detail Pane</strong> displays  information as marked up text (text is highlighted, bolded, underlined, etc. according to tool specific settings).  For example, 
-  when debugging a Java program, the <strong>Detail Pane</strong> displays <code>toString()</code> value of Java objects.</p>
-<p>If other types of detail panes are available, they can be accessed by right clicking on a variable and going to the &quot;Show Details As&quot; menu. This menu will not be available unless there is more than one possible type of detail pane for the current selection. The marked up text viewer detail pane that is available by default is the only detail pane provided by the Eclipse platform.</p>
-<p>A number of commands are available in the default <strong>Detail Pane</strong>. They are accessed by right-clicking the <strong>Detail Pane</strong> to open up a context menu. </p>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-    Detail Pane Commands
- </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> <p> Name </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Availability </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-assignvalue.htm"><strong>Assign Value </strong></a></td>
-      <td colspan="1" valign="top" align="left" > Assigns a new value to the currently selected variable by evaluating the text in the detail pane.</td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/metharg_obj.png" alt="Content Assist"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-contentassist.htm"><strong>Content Assist</strong></a></td>
-      <td colspan="1" valign="top" align="left" > Opens the <strong>Content Assist</strong> popup dialog, offering  code completion help. </td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/cut_edit.png" alt="Cut"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-cut.htm"><strong>Cut</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Copies the selected material to the system clipboard and removes it from the detail pane. </td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-copy.htm"><strong>Copy</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Copies the selected material from the detail pane onto the system clipboard.</td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" alt="Display Result"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-display.htm"><strong>Display</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Evaluates the selected text and displays the result in a popup dialog. </td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png" alt="Execute Selected Statement"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-execute.htm"><strong>Execute</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Executes the selected text as normal Java code. </td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-findreplace.htm"><strong>Find/Replace</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to search for and replace a specified expression.</td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-forcereturn.htm"><strong>Force Return </strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to immediately return from the method in which execution is suspended. </td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" alt="Inspect"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-inspect.htm"><strong>Inspect</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to inspect what the return value of the selected statement will be.</td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-maxlength.htm"><strong>Max Length </strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens a dialog allowing you 
-  to change the maximum number of characters displayed in the detail pane. </td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.ui.console/elcl16/paste_edit.png" alt="Paste"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-paste.htm"><strong>Paste</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Pastes material saved on the system clipboard into the detail pane.</td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-selectall.htm"><strong>Select All</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Selects all text in the detail pane. </td>
-      <td>Context menu </td>
-	</tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-wrap.htm"><strong>Wrap Text</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Change if the text displayed in the detail pane should  wrap at the predefined width or not.</td>
-      <td>Context menu </td>
-	</tr>    
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-  <a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-display.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-display.htm
deleted file mode 100644
index 941be0d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-display.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Display Result</title>
-</head>
-<body>
-<h1> Display </h1>
-<p> Select the <strong>Display</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/etool16/disp_sbook.png" alt="Display Result"> ] to have the selected statement evaluated and the results displayed inline in the <a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a> or in a popup dialog (that can be moved to the Display View).</p>
-<p>For example, consider we have the following statement selected in the Display View:</p>
-<p><img src="../../../reference/views/shared/images/ref-selectedstatement.PNG" alt="Selected Statement"> </p>
-<p>After we select the <strong>Display </strong> command we notice that the result is inserted inline in the view. In the following case though, a <em><strong>println()</strong></em> statement does not have an explicit return value, so that is what is written in the view. </p>
-<p><img src="../../../reference/views/shared/images/ref-displayresult.PNG" alt="Display command result"></p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a></li>
-  <li><a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)<a href="../../../reference/views/shared/ref-detailpane.htm"></a></li>
-  <li><a href="../../../reference/menus/run/ref-menu-run.htm"><strong>Run Menu</strong></a><strong> </strong></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-execute.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-execute.htm
deleted file mode 100644
index 3580d84..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-execute.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Execute</title>
-</head>
-<body>
-<h1> Execute </h1>
-<p> Select the <strong>Execute</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/etool16/run_sbook.png" alt="Execute Selected Statement"> ] to have the selected statement executed as though it was run in normal Java code.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a></li>
-  <li><a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-  <li><a href="../../../reference/menus/run/ref-menu-run.htm"><strong>Run Menu</strong></a><strong> </strong></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-find.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-find.htm
deleted file mode 100644
index b38470b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-find.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Find...</title>
-</head>
-<body>
-<h1> Find... </h1>
-<p> Select the <strong>Find...</strong> command to open the <strong>Find Dialog</strong> which allows you to search for specific elements within the view. You can also use the keyboard shortcut <em><strong>Ctrl+F</strong></em>. </p>
-<p>The <strong>Find Dialog</strong>:</p>
-<p><img src="../../../reference/views/shared/images/ref-find_dialog.PNG" alt="Find Dialog"></p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a></li>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View </strong></a></li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-findreplace.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-findreplace.htm
deleted file mode 100644
index 1aab106..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-findreplace.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Find/Replace</title>
-</head>
-<body>
-<h1> Find/Replace </h1>
-<p> Select the <strong>Find/Replace</strong> command to search for and replace specific statements or portions of statements. You can also use the keyboard shortcut <em><strong>Ctrl+F</strong></em>. </p>
-<p>The resulting find/replace dialog.</p>
-<p><img src="../../../reference/views/shared/images/ref-findreplace_dialog.PNG" alt="Find/Replace Dialog"> </p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/console/ref-console_view.htm"><strong>Console View</strong></a><strong> </strong></li>
-  <li><a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a><strong> </strong></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-</ul>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-forcereturn.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-forcereturn.htm
deleted file mode 100644
index 671daec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-forcereturn.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Force Return</title>
-</head>
-<body>
-<h1> Force Return </h1>
-<p> Select the <strong>Force Return </strong> command  to return from the current method with the speified value.</p>
-<p>You can force an early return from a method (only 
-  available when debugging on a Java SE 6 virtual machine). This returns 
-  a value from the current stack frame without executing any more instructions 
-  in the method and releases any locks obtained by synchronized blocks. 
-  A return value is created by selecting an expression and <strong>Force 
-  Return</strong> (<strong>Alt+Shift+F</strong>). This action is available 
-  from the Java editor's context menu, top level <a href="../../../reference/menus/run/ref-menu-run.htm"><strong>Run</strong></a> menu, in the <a href="../../../reference/views/display/ref-display_view.htm"><strong>Display 
-  View</strong></a>, and in the <strong><a href="../../../reference/views/shared/ref-detailpane.htm">detail pane</a></strong> of the <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>.</p>
-<p>Forcing an early return from a non-void method requires an expression 
-  to be evaluated. For example, if a method was going to return false 
-  you could return a value of true by selecting an expression in the <strong>Display 
-  View</strong> and invoking <strong>Force Return</strong>. In the following example, <code>elementCount</code> is not equal to zero, and would return false 
-  (see debug hover showing the value of <code>elementCount</code>).</p>
-<p><img src="images/force-return-code.png" alt="Force Return Example"></p>
-<p>From the<strong> Display View</strong>, we could enter the value we want returned, select it and use the <strong>Force Return</strong> command to force the method <code>isEmpty()</code> to return with that value (in the following example we will force <code>isEmpty()</code> to return with the value <code>true</code>). </p>
-<p><img src="images/force-return-action.png" alt="Force Return Action in the Display View"></p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a></li>
-  <li><a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-  <li><a href="../../../reference/menus/run/ref-menu-run.htm"><strong>Run Menu</strong></a><strong> </strong></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-horizview.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-horizview.htm
deleted file mode 100644
index be4c54c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-horizview.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Horizontal View Orientation</title>
-</head>
-<body>
-<h1> Horizontal View Orientation </h1>
-<p> Select the <strong>Horizontal View Orientation </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/det_pane_right.png" alt="Horizontal View Orientation"> ] to reveal the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> and set it in a horizontal alignment within the view.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Memory View</li>
-  <li>Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewlayoutcommands.htm">View Layout Commands<br>
-</a><a href="../../../reference/views/shared/ref-detailpane.htm">Detail Pane</a><br>
-  <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-<a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspect.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspect.htm
deleted file mode 100644
index 52b9a0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspect.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Inspect Selected Statement</title>
-</head>
-<body>
-<h1> Inspect Selected Statement </h1>
-<p> Select the <strong>Inspect</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" alt="Inspect"> ]  to evaluate the selected expression and have its result displayed in a  popup box.</p>
-<p><img src="../../../reference/views/shared/images/ref-inspectresult.PNG" alt="Inspect Resulting Popup"> </p>
-<p>You can also move the inspected statement to the <a href="../expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> by pressing <em><strong>Ctrl+Shift+I</strong></em> once the popup has been opened. </p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a></li>
-  <li><a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a><strong> </strong></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-  <li><a href="../../../reference/menus/run/ref-menu-run.htm"><strong>Run Menu</strong></a><strong> </strong></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspectvariable.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspectvariable.htm
deleted file mode 100644
index 24f0c9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-inspectvariable.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Inspect Selected Variable</title>
-</head>
-<body>
-<h1> Inspect Selected Variable </h1>
-<p> Select the <strong>Inspect</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/etool16/insp_sbook.png" alt="Inspect"> ]  to create an inspect expression associated with the selected variable and add it to the <a href="../expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a>.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related Tasks"></p>
-<p><a href="../../../tasks/task-evaluating_expressions.htm">Evaluating Expressions</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-maxlength.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-maxlength.htm
deleted file mode 100644
index 13dd411..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-maxlength.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">    <title>
-      Max Detail Pane Length
-    </title>
-  </head>
-  <body>
-    <h1>
-      Max Detail Pane Length</h1>
-    <p> The <strong>Max Length... </strong> command to opens a dialog allowing you 
-  to change the maximum number of characters displayed in the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a></p>
-    
-<p>This command applies to:</p>
-    <ul>
-       <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-    </ul>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-paste.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-paste.htm
deleted file mode 100644
index 341e707..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-paste.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Paste</title>
-</head>
-<body>
-<h1> Paste</h1>
-<p> Select the <strong>Paste</strong> command [ <img src="../../../images/org.eclipse.ui.console/elcl16/paste_edit.png" alt="Paste"> ] to copy material from the system clipboard into the current view. You can also use the standard keyboard shortcut <em><strong>Ctrl+V</strong></em>.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View </strong></a></li>
-  <li> <a href="../../../reference/views/console/ref-console_view.htm"><strong>Console View</strong></a></li>
-  <li> <a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View </strong></a></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-</ul>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-preferences.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-preferences.htm
deleted file mode 100644
index ae0f131..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-preferences.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>View Java Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> View Java Preferences</h1>
-<p> Select the<strong> Java Preferences... </strong> command to open the preference pages containing options relating to the <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> and the <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong>.</p>
-<p><img src="../../../reference/views/shared/images/ref-javapreferences.PNG" alt="Preferences"></p>
-<p>There are four pages in total that are shown, all as entries in the tree on the left hand side of the <strong>Preferences Dialog</strong>.</p>
-<p>These pages are:</p>
-<ul>
-  <li>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaDetailFormattersPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Detail Formatters preference page"> <strong>Java &gt; Debug &gt; Detail Formatters</strong></a> preference page.</li>
-  <li>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.HeapWalkingPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Heap Walking preference page"> <strong>Java &gt; Debug &gt; Heap Walking</strong></a> preference page. </li>
-  <li>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaLogicalStructuresPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Logical Structures preference page"> <strong>Java &gt; Debug &gt; Logical Structures</strong></a> preference page. </li>
-  <li>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaPrimitivesPreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Primitive Display Options preference page"> <strong>Java &gt; Debug &gt; Primitive Display Options</strong></a> preference page. </li>
-</ul>
-<p>This command applies to:</p>
-<ul><li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectall.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectall.htm
deleted file mode 100644
index 46b213d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectall.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Select All</title>
-</head>
-<body>
-<h1> Select All </h1>
-<p> Choose this command to select all of the content in the view. You can also use the standard keyboard shortcut <em><strong>Ctrl+A</strong></em>.</p>
-<p>This command applies to:</p>
-<ul>
-  <li> <a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a></li>
-  <li><a href="../../../reference/views/console/ref-console_view.htm"><strong>Console View</strong></a></li>
-  <li> <a href="../../../reference/views/display/ref-display_view.htm"><strong>Display View</strong></a></li>
-  <li> <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li> Registers View </li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-</ul>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectcolumns.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectcolumns.htm
deleted file mode 100644
index 5b9e012..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-selectcolumns.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Select Columns</title>
-</head>
-<body>
-<h1> Select Columns </h1>
-<p> Select the <strong>Select Columns...</strong> command to open a dialog that will allow you to choose which columns to display in the <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>.</p>
-<p>In the resulting dialog you can select which columns will be displayed. </p>
-<p><img src="../../../reference/views/shared/images/ref-selectcolumnsdialog.PNG" alt="Select Columns Dialog"></p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewlayoutcommands.htm">View Layout Commands</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showcolumns.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showcolumns.htm
deleted file mode 100644
index de00384..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showcolumns.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Columns</title>
-</head>
-<body>
-<h1> Show Columns </h1>
-<p> Select the <strong>Show Columns </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/prop_ps.png" alt="Show Columns"> ] to change if columns should be used to display variable information in the<a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>. If Show Columns is turned on, the Select Columns command will be available, allowing you to choose which columns are visible.</p>
-<p>This command applies to:</p>
-<ul><li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewlayoutcommands.htm">View Layout Commands</a><br>
-</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showconstants.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showconstants.htm
deleted file mode 100644
index ef99b51..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showconstants.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Constants</title>
-</head>
-<body>
-<h1> Show Constants </h1>
-<p> Select the <strong>Show Constants</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png" alt="Show Constants"> ] to change if constants should be shown in the view or not.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a><br>
-</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showlogical.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showlogical.htm
deleted file mode 100644
index 188d771..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showlogical.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Logical Structures</title>
-</head>
-<body>
-<h1> Show Logical Structures </h1>
-<p> Select the <strong>Show Logical Structures </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png" alt="Show Logical Structures"> ] to change if logical structures should be shown in the view or not.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a><br>
-</p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-shownull.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-shownull.htm
deleted file mode 100644
index b6dfd11..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-shownull.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Null Array Entries</title>
-</head>
-<body>
-<h1> Show Null Array Entries </h1>
-<p> Select the <strong>Show Null Array Entries </strong> command  to change if null array entries should be shown in the view or not.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li> <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showqualified.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showqualified.htm
deleted file mode 100644
index faf78af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showqualified.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Qualified Names</title>
-</head>
-<body>
-<h1> Show Qualified Names </h1>
-<p> Select the <strong>Show Qualified Names</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/obj16/package_obj.png" alt="Show Qualified Names"> ] the change whether qualified names should be shown in the view or not.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a></li>
-  <li> <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong></li>
-  <li> <strong><a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a></strong> </li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showreferences.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showreferences.htm
deleted file mode 100644
index 31bad15..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showreferences.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show References</title>
-</head>
-<body>
-<h1>Show References</h1>
-<p> Select the <strong>Show References</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_references.png" alt="Show All References"> ] to change if references should be displayed as variables in the view. When turned on, each Java variable that supports references will have a new child item with the name &quot;'&lt;variable name&gt;' referenced from:&quot;. This new variable contains a list of all Java objects that hold a reference to the parent object. You can get a text list in the detail pane by clicking on the reference list variable or explore the details of each referencing object by expanding the variables. </p>
-<p>References will only appear in the view if the Java Virtual Machine you are using supports reference retrieval.</p>
-<p>This command applies to:</p>
-<ul>
-  <li> <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-</ul>
-<p>The   Variables View with Show References turned on. In this case, the Map is references by one object, a HashMap$EntrySet. </p>
-<p><img src="../../../reference/views/shared/images/ref-showreferences.PNG" alt="Show References"></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showstatic.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showstatic.htm
deleted file mode 100644
index c41f8e0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showstatic.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Static Fields</title>
-</head>
-<body>
-<h1> Show Static Fields </h1>
-<p> Select the <strong>Show Static Fields</strong> command [ <img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/static_co.png" alt="Show Static Fields"> ] to change if static fields should be shown in the view or not.</p>
-<p>This command applies to:</p>
-<ul>
-  <li> <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showtypenames.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showtypenames.htm
deleted file mode 100644
index c20ebc6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-showtypenames.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Show Type Names</title>
-</head>
-<body>
-<h1> Show Type Names </h1>
-<p> Select the <strong>Show Type Names</strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/tnames_co.png" alt="Show Type Names"> ] to change if type names should be shown in the view or not.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-togglewp.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-togglewp.htm
deleted file mode 100644
index 7f0adec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-togglewp.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Toggle Field Watchpoint</title>
-</head>
-<body>
-<h1>Toggle Field Watchpoint </h1>
-<p> Select the <strong>Toggle Watchpoint  </strong>command [ <img src="../../../images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png" alt="Toggle Watchpoint"> ] to  create a new watchpoint on the currently selected field. Whenever that field is accessed or modified, execution will be suspended. If the selected field already has a watchpoint, selecting this command will remove it. You must select a Java field object to use this command.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" ></p>
-<p> <a href="../../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-  <a href="../../../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a>
-  <p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-vertview.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-vertview.htm
deleted file mode 100644
index 6891f0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-vertview.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Vertical View Orientation</title>
-</head>
-<body>
-<h1> Vertical View Orientation </h1>
-<p> Select the <strong>Vertical  View Orientation </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/det_pane_under.png" alt="Vertical View Orientation"> ] to reveal the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> and set it in a vertical alignment within the view.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Memory View</li>
-  <li> Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> </li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewlayoutcommands.htm">View Layout Commands</a><br>
-  <a href="../../../reference/views/shared/ref-detailpane.htm">Detail Pane</a><br>
-    <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-  <a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewdisplaycommands.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewdisplaycommands.htm
deleted file mode 100644
index c71fb30..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewdisplaycommands.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Variable Display Commands</title>
-</head>
-<body>
-<h1> Variable Display Commands </h1>
-<p> View display commands affect what variables are displayed in the view and how they are presented. </p>
-<p>These commands apply to (some commands apply to additional views):</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p>The <strong>Show Type Names</strong> and <strong>Show Logical Structures</strong> commands are available on the view toolbar. The other actions can be found in the drop down menu of the view as shown below. </p>
-<p><img src="../../../reference/views/shared/images/ref-viewdisplaycommands.PNG" alt="View Display Commands"></p>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-  View Display Commands 
-  </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> <p> Name </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Availability </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/constant_co.png" alt="Show Constants"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><a href="../../../reference/views/shared/ref-showconstants.htm"><strong>Show Constants</strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Changes whether constants should be shown in the view.</p></td>
-      <td>View action</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/var_cntnt_prvdr.png" alt="Show Logical Structures"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><a href="../../../reference/views/shared/ref-showlogical.htm"><strong>Show Logical Structures</strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Changes whether logical structures should be shown in the view.</p></td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><a href="../../../reference/views/shared/ref-shownull.htm"><strong>Show Null Array Entries</strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Change whether null array entries should be shown in the view.</p>        </td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/package_obj.png" alt="Show Qualified Names"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><a href="../../../reference/views/shared/ref-showqualified.htm"><strong>Show Qualified Names </strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Changes whether qualified names should be shown in the view.</p></td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_references.png" alt="Run to Return button"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><a href="../../../reference/views/shared/ref-showreferences.htm"><strong>Show References</strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p>Changes whether references to variables should be displayed  in the view. Your Java virtual machine must support reference retrieval. </p></td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/static_co.png" alt="Show Static Fields"> </td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><a href="../../../reference/views/shared/ref-showstatic.htm"><strong>Show Static Fields</strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Changes whether static fields should be shown in the view.</p></td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/tnames_co.png" alt="Show Type Names"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p><a href="../../../reference/views/shared/ref-showtypenames.htm"><strong>Show Type Names</strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left"><p> Changes whether type names should be shown in the view.</p></td>
-      <td>View action </td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-  <a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a><br>
-  <a href="../../../reference/views/shared/ref-detailpane.htm">Detail Pane</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewlayoutcommands.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewlayoutcommands.htm
deleted file mode 100644
index 75d5aa5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewlayoutcommands.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>View Layout Commands</title>
-</head>
-<body>
-<h1> View Layout Commands </h1>
-<p>View layout commands affect the orientation of the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> in the view. In addition, the <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> has commands that allow you to change  column settings. </p>
-<p>These commands apply to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Registers View </li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p>The commands are available under the Layout menu, which is shown below in the Variables View. </p>
-<p><img src="../../../reference/views/shared/images/ref-viewlayoutmenu.PNG" alt="View Layout Menu"></p>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-  Detail Pane Display Commands
-  </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> <p> Name </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Availability </p></th>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/prop_ps.png" alt="Show Columns"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-showcolumns.htm"><strong>Show Columns </strong></a></td>
-      <td colspan="1" valign="top" align="left" >Changes if columns should be shown in the view or not. Variables View only. </td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-selectcolumns.htm"><strong>Select Columns... </strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to select which columns are shown when columns are visible. Variables View only. </td>
-      <td>View action </td>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/det_pane_right.png" alt="Horizontal Detail Pane alignment"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-horizview.htm"><strong>Horizontal View Orientation</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Displays the detail pane at the right side of the view, aligning the parts of the view horizontally. </td>
-      <td>View action </td>
-	</tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/det_pane_under.png" alt="Vertical Detail Pane alignment"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><a href="../../../reference/views/shared/ref-vertview.htm"><strong>Vertical View Orientation </strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" >Displays the detail pane at the bottom of the view, aligning the parts of the view vertically.</td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/det_pane_hide.png" alt="View Only"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-viewonly.htm"><strong>View Only</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Hides the detail pane. </td>
-      <td>View action </td>
-    </tr>
-  </tbody>
-</table>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p> <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-  <a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewonly.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewonly.htm
deleted file mode 100644
index 0f6c23c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-viewonly.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>View Only</title>
-</head>
-<body>
-<h1> View Only </h1>
-<p> Select the <strong> View Only </strong> command [ <img src="../../../images/org.eclipse.debug.ui/elcl16/det_pane_hide.png" alt="Expression View Only"> ] to hide the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> within the view. The name of the command will change based on the current view. For example, in the <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>, the command is named 'Variables View Only'. </p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a></li>
-  <li>Registers View</li>
-  <li><a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a></li>
-</ul>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/shared/ref-viewlayoutcommands.htm">View Layout Commands</a><br>
-  <a href="../../../reference/views/shared/ref-detailpane.htm">Detail Pane</a><br>
-  <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-  <a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a><br>
-  <a href="../../../reference/views/shared/ref-detailpane.htm"></a></p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-wrap.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-wrap.htm
deleted file mode 100644
index e01b341..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/shared/ref-wrap.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Wrap Text</title>
-</head>
-<body>
-<h1> Wrap Text</h1>
-<p> Select the <strong>Wrap Text</strong> command to change if the text displayed in the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> should wrap at the predefined width or not.</p>
-<p>This command applies to:</p>
-<ul>
-  <li><a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../../../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../../../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-</ul>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/variables/images/ref-variables_view.PNG b/bundles/org.eclipse.jdt.doc.user/reference/views/variables/images/ref-variables_view.PNG
deleted file mode 100644
index abb3793..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/variables/images/ref-variables_view.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-createwatch.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-createwatch.htm
deleted file mode 100644
index 15a444e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-createwatch.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Create Watch Expression</title>
-</head>
-<body>
-<h1> Create Watch Expression</h1>
-<p> Select the <strong>Create Watch Expression </strong>command [ <img src="../../../images/org.eclipse.debug.ui/obj16/expression_obj.png" alt="Add Watch Expression"> ] to  create a new expression  based on the selected variable and add it to the <strong><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a></strong>.</p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a></p>
-<p><img src="../../../images/ngrelr.png" alt="Related Reference"></p>
-<p><a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a> <br>
-  <a href="../../../reference/views/variables/ref-variables_view.htm">Variables View</a> </p>
-<p>&nbsp;</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-variables_view.htm b/bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-variables_view.htm
deleted file mode 100644
index 4974895..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/views/variables/ref-variables_view.htm
+++ /dev/null

@@ -1,170 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Variables View</title>
-</head>
-<body>
-<h1> Variables View </h1>
-<p> The <strong>Variables View </strong>displays information about the variables associated with the stack frame selected in the <a href="../../../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. When debugging a Java program, variables can be selected to have more detailed information be displayed in the <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a>. In addition, Java objects can be expanded to show the fields that variable contains. </p>
-<p>The Variables View, shown with columns. The <a href="../../../reference/views/shared/ref-detailpane.htm"></a> detail pane the area at the bottom of the view displaying text. </p>
-<p><img src="../../../reference/views/variables/images/ref-variables_view.PNG" alt="Variables View with columns"></p>
-<p>There are many commands available in the Variables View:</p>
-<ul>
-<li><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm"><strong>View Display Commands</strong></a> affect what variables are displayed and how they are presented.</li>
-<li>The <a href="../../../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> has many commands available by right clicking on it.</li>
-<li><a href="../../../reference/views/shared/ref-viewlayoutcommands.htm"><strong>View Layout Commands</strong></a> affect how the detail pane is oriented and whether columns are displayed.</li>
-<li>Other commands are listed below. </li>
-</ul>
-<table border="1" cellspacing="0" cellpadding="5">
-  <caption>
-  Variables View Commands
-  </caption>
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1"> <p> Command </p></th>
-      <th rowspan="1" colspan="1"> <p> Name </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1"> <p> Availability </p></th>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_instances.png" alt="All References"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-allinstances.htm"><strong>All Instances</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens a popup dialog displaying a list of all instances of the selected Java type. Your Java virtual machine must support instance retrieval. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/elcl16/all_references.png" alt="All References"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-allreferences.htm"><strong>All References</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens a popup dialog displayinga list of all Java objects that have references to the selected variable. Your Java virtual machine must support reference retrieval. </td>
-      <td>Context menu </td>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/changevariablevalue_co.png" alt="Change Value"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-changevarvalue.htm"><strong>Change Value...</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to change the value for the underlying selected variable.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/collapseall.png" alt="Collapse All"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-collapseall.htm"><strong>Collapse All</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Collapses all the the currently expanded variables.</td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/elcl16/copy_edit_co.png" alt="Copy Expressions"></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p><a href="../../../reference/views/shared/ref-copy.htm"><strong>Copy Variables</strong></a></p></td>
-      <td rowspan="1" colspan="1" valign="top" align="left" ><p> Copies the selected  variables to the system clipboard.</p></td>
-      <td>Context menu</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.debug.ui/obj16/expression_obj.png" alt="Add Watch Expression"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/variables/ref-createwatch.htm"><strong>Create Watch Expression </strong></a></td>
-      <td colspan="1" valign="top" align="left" >Allows you to create a watch expression for the selected variable.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" >Edit Logical Structure </td>
-      <td colspan="1" valign="top" align="left" >Allow you to edit the logical structure of the selected variable </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-find.htm"><strong>Find...</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens the search dialog to find elements in the variables view.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/insp_sbook.png" alt="Inspect"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-inspectvariable.htm"><strong>Inspect</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Creates a new inspect statement for the selected variable and adds it to the expressions view.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Instance Breakpoints...</td>
-      <td colspan="1" valign="top" align="left">Allows you to filter existing breakpoints to the selected variable instance.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-preferences.htm"><strong>Java Preferences...</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Opens several preference pages containing options that affect the  view. </td>
-      <td>View action </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">New Detail Formatter...</td>
-      <td colspan="1" valign="top" align="left">Allows you to create your own detail formatter for that type of variable.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Actual Type </td>
-      <td colspan="1" valign="top" align="left">Opens the actual type of the selected variable.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Actual Type Hierarchy </td>
-      <td colspan="1" valign="top" align="left">Opens the actual type hierarchy for the actual type of the selected variable. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Declared Type </td>
-      <td colspan="1" valign="top" align="left">Opens the declared type for the selected variable in a new editor. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left">Open Declared Type Hierarchy </td>
-      <td colspan="1" valign="top" align="left">Opens the type hierarchy for the declared type of the selected variable. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-selectall.htm"><strong>Select All</strong></a></td>
-      <td colspan="1" valign="top" align="left" >Selects all of the variables in the view.</td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" >Show Structure As... </td>
-      <td colspan="1" valign="top" align="left" >Allows you to select a different formatter for showing the selected logical structure type variable. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-      <td colspan="1" valign="top" align="left" >Show Details As... </td>
-      <td colspan="1" valign="top" align="left" >Allows you to select a different detail pane for showing detailed information about selected variables. </td>
-      <td>Context menu </td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left"><img src="../../../images/org.eclipse.jdt.debug.ui/obj16/readwrite_obj.png" alt="Toggle Watchpoint"></td>
-      <td colspan="1" valign="top" align="left" ><a href="../../../reference/views/shared/ref-togglewp.htm"><strong>Toggle Watchpoint </strong></a></td>
-      <td colspan="1" valign="top" align="left" > Creates a new watchpoint on the currently selected field or removes the watchpoint if one already exists. </td>
-      <td>Context menu </td>
-    </tr>
-  </tbody>
-</table>
-<p> <img border="0" src="../../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../../concepts/concept-java-views.htm">Java views</a><br>
-  <a href="../../../concepts/concept-java-perspective.htm">Java perspectives</a> </p>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="../../../tasks/task-suspending_threads.htm">Suspending threads</a><br>
-  <a href="../../../tasks/task-evaluating_expressions.htm">Evaluating expressions</a> </p>
-<p> <img border="0" src="../../../images/ngrelr.png" alt="Related reference" > </p>
-<p><a href="../../views/shared/ref-detailpane.htm">Detail Pane<br>
-  </a><a href="../../../reference/views/shared/ref-viewdisplaycommands.htm">View Display Commands</a><br>
-  <a href="../../../reference/views/shared/ref-viewlayoutcommands.htm">View Layout Commands</a><br>
-  <a href="../../../reference/views/expressions/ref-expressions_view.htm">Expressions View</a><br>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_breakpoints.htm b/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_breakpoints.htm
deleted file mode 100644
index 6c74735..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_breakpoints.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title>Export Breakpoints Wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Export Breakpoints Wizard</h1>
-<p>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.debug.internal.ui.importexport.breakpoints.WizardExportBreakpoints)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Breakpoint export wizard"> <b>Export Breakpoints</b></a> wizard
-  helps you to export breakpoints to a file.</p>
-<h2>Export breakpoints page</h2>
-<table border="1" cellspacing="0" cellpadding="5" summary="Export breakpoints page">
-  <tr>
-    <th >Option</th>
-    <th >Description</th>
-    <th >Default</th>
-  </tr>
-  <tr>
-    <td align="left" valign="top">Breakpoint List</td>
-    <td align="left" valign="top">Select the breakpoints that you wish to export, and de-select those that you do not. </td>
-    <td align="left" valign="top"><p><strong>There can be two possible defaults: </strong></p>
-      <p>If the wizard is invoked from the breakpoints view and any breakpoints are selected, those same ones will be checked by default.</p>
-      <p>If the wizard is invoked via the <strong><a href="../../reference/ref-menu-file.htm">File</a></strong> menu  than nothing will be selected. </p></td>
-  </tr>
-  <tr>
-    <td valign="top"> To File </td>
-    <td valign="top">The file to export the breakpoints to, you can also click <strong>Browse...</strong> to search for a location to export to. </td>
-    <td valign="top"><p><strong>There can be two possible defaults:</strong></p>
-      <p>If you have never exported breakpoints before it will be blank</p>
-      <p>If you have exported breakpoints before the last file name you exported to will be automatically inserted. </p></td>
-  </tr>
-  <tr>
-    <td valign="top">Overwrite</td>
-    <td valign="top"><dl>
-        <dt> <strong>Overwrite existing file without warning :</strong> </dt>
-        <dd> When selected, if the file you wish to export to already exists, it will be overwritten automatically by the wizard. </dd>
-      </dl></td>
-    <td valign="top"> not selected </td>
-  </tr>
-</table>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding Line Breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing Line Breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java Program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and Debugging</a></p>
-<p> <img src="../../images/ngrelr.png" alt="Related reference" border="0" > </p>
-<p> <a href="../../reference/ref-menu-file.htm">File actions</a><br>
-  <a href="../../reference/wizards/ref-import_breakpoints.htm">Importing Breakpoints </a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_launch_configs.htm b/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_launch_configs.htm
deleted file mode 100644
index 4870aea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-export_launch_configs.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title>Export Launch Configurations Wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Export Launch Configurations Wizard</h1>
-<p>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.debug.ui.export.launchconfigurations)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launch Configutrations export wizard"> <b>Export Launch Configurations</b></a> wizard
-  helps you to export breakpoints to a file.</p>
-<h2>Export launch configurations page</h2>
-<table border="1" cellspacing="0" cellpadding="5" summary="Export breakpoints page">
-  <tr>
-    <th >Option</th>
-    <th >Description</th>
-    <th >Default</th>
-  </tr>
-  <tr>
-    <td align="left" valign="top">Launch configuration list</td>
-    <td align="left" valign="top">Select the launch configurations that you wish to export, and de-select those that you do not. </td>
-    <td align="left" valign="top">None</td>
-  </tr>
-  <tr>
-    <td valign="top">Select All</td>
-    <td valign="top">Can be used to quickly select all launch configurations in the list.</td>
-    <td valign="top">None</td>
-  </tr>
-  <tr>
-    <td valign="top">Deselect All</td>
-    <td valign="top">Can be used to quickly deselect all launch configurations in the list.</td>
-    <td valign="top">None</td>
-  </tr>
-  <tr>
-    <td valign="top">Location</td>
-    <td valign="top">The folder to export the launch configurations to.</td>
-    <td valign="top">None</td>
-  </tr>
-  <tr>
-    <td valign="top">Browse...</td>
-    <td valign="top">The <strong>Browse...</strong> button allows you to search for a specific folder to export launch configurations to.</td>
-    <td valign="top">None</td>
-  </tr>
-  <tr>
-    <td valign="top">Overwrite existing file(s) without warning</td>
-    <td valign="top">When selected, if the location already contains a launch configuration being exported, it will be overwritten automatically by the wizard.</td>
-    <td valign="top">Not Selected</td>
-  </tr>
-</table>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" ></p>
-<p><a href="../../tasks/task-launching_java_program.htm">Launching a Java Program</a><br>
-<a href="../../tasks/task-running_and_debugging.htm">Running and Debugging</a></p>
-<p><img src="../../images/ngrelr.png" alt="Related reference" border="0" > </p>
-<p><a href="../../reference/ref-menu-file.htm">File actions</a><br>
-  <a href="../../reference/wizards/ref-import_launch_configs.htm">Importing Launch Configurations</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_breakpoints.htm b/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_breakpoints.htm
deleted file mode 100644
index 4da49d2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_breakpoints.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title>Import Breakpoints Wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Import Breakpoints Wizard</h1>
-<p>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.debug.internal.ui.importexport.breakpoints.WizardImportBreakpoints)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Breakpoint import wizard"> <b>Import Breakpoints</b></a> wizard
-  helps you to import breakpoints from a file.</p>
-<h2>Import breakpoints page</h2>
-<table border="1" cellspacing="0" cellpadding="5" summary="Import breakpoints page">
-  <tr>
-    <th >Option</th>
-    <th >Description</th>
-    <th >Default</th>
-  </tr>
-  <tr>
-    <td align="left" valign="top">From...</td>
-    <td align="left" valign="top">Type the name of the file to import from, or click the <strong>Browse...</strong> button to search for a file.</td>
-    <td align="left" valign="top">&lt;blank&gt;</td>
-  </tr>
-  <tr>
-    <td valign="top"> Update... </td>
-    <td valign="top"><dl>
-        <dt> <strong>Automatically update existing breakpoints </strong> </dt>
-        <dd> When selected, any breakpoints that already exist in your workspace will be overwritten by those being imported from the file. </dd>
-      </dl></td>
-    <td valign="top">not selected </td>
-  </tr>
-  <tr>
-    <td valign="top"> Create... </td>
-    <td valign="top"><dl>
-        <dt> <strong>Automatically create breakpoints workingsets:</strong> </dt>
-        <dd> When selected, if an imported breakpoint indicates it belongs to a working sets that does not exist in your workspace, the workingset will be created for you and the breakpoint added to it. </dd>
-      </dl></td>
-    <td valign="top"> not selected </td>
-  </tr>
-</table>
-<p> <img border="0" src="../../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../../concepts/cbrkpnts.htm">Breakpoints</a> </p>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> <a href="../../tasks/task-add_line_breakpoints.htm">Adding Line Breakpoints</a><br>
-  <a href="../../tasks/task-remove_line_breakpoints.htm">Removing Line Breakpoints</a><br>
-  <a href="../../tasks/task-launching_java_program.htm">Launching a Java Program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and Debugging</a></p>
-<p> <img src="../../images/ngrelr.png" alt="Related reference" border="0" > </p>
-<p> <a href="../../reference/ref-menu-file.htm">File actions</a><br>
-  <a href="../../reference/wizards/ref-export_breakpoints.htm">Exporting Breakpoints</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_launch_configs.htm b/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_launch_configs.htm
deleted file mode 100644
index c48999e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/reference/wizards/ref-import_launch_configs.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title>Import Launch Configurations Wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Import Launch Configurations Wizard</h1>
-<p>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.debug.ui.import.launchconfigurations)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launch Configurations import wizard"> <b>Import Launch Configurations</b></a> wizard
-  helps you to import breakpoints from a file.</p>
-<h2>Import launch configurations page</h2>
-<table border="1" cellspacing="0" cellpadding="5" summary="Import launch configurations page">
-  <tr>
-    <th >Option</th>
-    <th >Description</th>
-    <th >Default</th>
-  </tr>
-  <tr>
-    <td align="left" valign="top">From Directory</td>
-    <td align="left" valign="top">The folder to import launch configurations from.</td>
-    <td align="left" valign="top">None</td>
-  </tr>
-  <tr>
-    <td align="left" valign="top">Browse...</td>
-    <td align="left" valign="top">The <strong>Browse...</strong> button allows you to search for a specific folder to import launch configurations from.</td>
-    <td align="left" valign="top">None</td>
-  </tr>
-  <tr>
-    <td valign="top">Overwrite existing launch configurations without warning</td>
-    <td valign="top">When selected, any launch configurations that already exist in your workspace will be overwritten by those being imported.</td>
-    <td valign="top">Not Selected</td>
-  </tr>
-</table>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks" ></p>
-<p><a href="../../tasks/task-launching_java_program.htm">Launching a Java Program</a><br>
-  <a href="../../tasks/task-running_and_debugging.htm">Running and Debugging</a></p>
-<p> <img src="../../images/ngrelr.png" alt="Related reference" border="0" > </p>
-<p> <a href="../../reference/ref-menu-file.htm">File actions</a><br>
-  <a href="../../reference/wizards/ref-export_launch_configs.htm">Exporting Launch Configurations</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add-exception-breakpoint.PNG b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add-exception-breakpoint.PNG
deleted file mode 100644
index 882648c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add-exception-breakpoint.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_ee_file.PNG b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_ee_file.PNG
deleted file mode 100644
index e05882e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_ee_file.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_std_vm.PNG b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_std_vm.PNG
deleted file mode 100644
index bd76dfc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-add_jre_std_vm.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-add-monitor.gif b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-add-monitor.gif
deleted file mode 100644
index 252d7eb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-add-monitor.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-det-pane.gif b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-det-pane.gif
deleted file mode 100644
index d590470..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-det-pane.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-link-panes.gif b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-link-panes.gif
deleted file mode 100644
index 870934b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-link-panes.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-new.gif b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-new.gif
deleted file mode 100644
index 9d05088..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-new.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-pin.gif b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-pin.gif
deleted file mode 100644
index ec50b70..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-pin.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-remove-monitor.gif b/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-remove-monitor.gif
deleted file mode 100644
index 2cd9c54..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/task-memory-remove-monitor.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-199a.png b/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-199a.png
deleted file mode 100644
index e550901..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-199a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-46.png b/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-46.png
deleted file mode 100644
index 6c9f90f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-46.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-exception-filtering-add.PNG b/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-exception-filtering-add.PNG
deleted file mode 100644
index 14ad0aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-exception-filtering-add.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-excetpion-filtering-page.PNG b/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-excetpion-filtering-page.PNG
deleted file mode 100644
index 70cd96f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks-excetpion-filtering-page.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_200a.png b/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_200a.png
deleted file mode 100644
index 7914299..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_200a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_201a.png b/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_201a.png
deleted file mode 100644
index 8dfc914..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/images/tasks_201a.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-add_line_breakpoints.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-add_line_breakpoints.htm
deleted file mode 100644
index 096d9fd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-add_line_breakpoints.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adding Line Breakpoints</title>
-</head>
-<body>
-<h1> Adding Line Breakpoints </h1>
-<p> Line breakpoints are set on an executable line of a program. </p>
-<ol>
-  <li> In the editor area, open the file where you want to add the breakpoint. </li>
-  <li> Directly to the left of the line where you want to add the breakpoint, 
-    open the marker bar (vertical ruler) pop-up menu and select <strong>Toggle 
-    Breakpoint.</strong>&nbsp;&nbsp; You can also double-click on the marker bar 
-    next to the source code line.&nbsp; A new breakpoint marker appears on the 
-    marker bar, directly to the left of the line where you added the breakpoint. </li>
-</ol>
-<p>Also, the new breakpoint appears in the <a href="../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a> list. </p>
-<p> While the breakpoint is enabled, thread execution suspends before that line of code is executed. The debugger selects
-  the thread that has suspended and displays the thread's stack
-  frames. The line where the breakpoint was set is highlighted in the editor in the <strong>Debug Perspective</strong>. </p>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-</p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="task-apply_hit_count.htm">Applying hit counts</a><br>
-  <a href="task-catching_exceptions.htm">Catching Java exceptions</a><br>
-  <a href="task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="task-enable_disable_breakpoints.htm">Enabling and disabling breakpoints</a><br>
-  <a href="task-manage_conditional_breakpoint.htm">Managing conditional breakpoints</a><br>
-  <a href="task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../tasks/task-stepping.htm">Stepping through the execution of a program</a> </p>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-add_new_jre.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-add_new_jre.htm
deleted file mode 100644
index 0a3b94a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-add_new_jre.htm
+++ /dev/null

@@ -1,121 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Adding a new JRE definition
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Adding a new JRE definition
-    </h1>
-    <p>
-    In your workspace you can have any number of JRE definitions. You can also add as many JRE definitions as you want.</p>
-    <h2> To add a new JRE definition: </h2>
-    
-    <ol>
-  <li> Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.preferences.VMPreferencePage)")'> 
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Installed JREs preference page"> 
-    <strong>Java &gt; Installed JREs</strong></a> preference page. </li>
-  <li> Select the&nbsp;<strong>Add...</strong> button. The Add JRE wizard opens. </li>
-  <li> You will have to select the type of JRE you would like to create:
-  <ul>
-  	<li> <a href="#StdVM"><strong>Standard VM</strong></a> - You will select a folder where the JRE is installed.  The details of the JRE will be determined
-	by scanning the location.  You can further customize the JRE install, specifying vm arguments, source attachments, etc.</li>
-	<li> <a href="#StdVM1x"><strong>Standard VM 1.x.x</strong></a> - Same options as a standard VM install, but the install is customized to handle the 1.x.x install</li>
-	<li> <a href="#EEFile"><strong>Execution Environment Description</strong></a> - You will select an execution environment (EE) file that describes all the details required to set up the JRE.  You will be able
-	to customize some aspects of the install.</li>
-  </ul>
-  </li>
-  </ol>
-  
-  <a name="StdVM"></a>
-  <h2>Standard VM:</h2>
-  
-  <ol>
-  <li> In the <strong>JRE home</strong> field, click <strong>Browse... 
-    </strong> to select a path to the root directory of a JRE installation 
-    (usually the directory containing the <em>bin</em> and <em>lib</em> 
-    directories for the JRE). You may also type a folder name 
-    into this field.</li>
-  <li> In the <strong>JRE name</strong> field, type a name for the new JRE 
-    definition. All JREs of the same type must have a unique name. </li>
-  <li> In the <strong>Default VM Arguments</strong> field, you can add/edit the default
-  arguments that will be passed to the VM when launching.</li>
-  <li> The default libraries appear for the JRE in the JRE system libraries list. 
-    You can modify the libraries as desired. 
-    <ul>
-      <li>Source and javadoc locations can be specified for the referenced JARs. 
-        The Javadoc location is used by the Javadoc export wizard as a default 
-        value and by the 'Open External Javadoc' action. </li>
-      <li>Jars can be added, removed, and reordered.</li>
-    </ul>
-  </li>
-  <li> Click <strong>Finish</strong> when you are done. </li>
-</ol>
-
-  <img src="../tasks/images/task-add_jre_std_vm.PNG" alt="Add Standard VM JRE" width="419" height="552">
-  
-  <a name="StdVM1x"></a>
-  <h2>Standard 1.1.x VM:</h2>
-  
-  <p> Follow the same steps as for <a href="#StdVM"><strong>Standard VM</strong></a> JREs.</p>
-  
-  <a name="EEFile"></a>
-  <h2>Execution Environment Files:</h2>
-  
-	<p>For more information on EE File structure see the <a href="http://wiki.eclipse.org/index.php/Execution_Environment_Descriptions">Wiki Page</a>.</p>
-
-	<ol>
-  <li> In the <strong>Definition home directory</strong> field, click <strong>File... 
-    </strong> to select a execution environment description file to load the JRE
-	installation from.  You may also type a file path into this field.</li>
-  <li> In the <strong>JRE name</strong> field, type a name for the new JRE 
-    definition. All JREs of the same type must have a unique name. </li>
-  <li> In the <strong>Default VM Arguments</strong> field, you can add/edit the default
-  arguments that will be passed to the VM when launching.</li>
-  <li> The default libraries appear for the JRE in the JRE system libraries list. 
-    You can modify the libraries as desired. 
-    <ul>
-      <li>Source and javadoc locations can be specified for the referenced JARs. 
-        The Javadoc location is used by the Javadoc export wizard as a default 
-        value and by the 'Open External Javadoc' action. </li>
-      <li>Jars can be added, removed, and reordered.</li>
-    </ul>
-  </li>
-  <li> Click <strong>Finish</strong> when you are done. </li>
-</ol>
-
-<img src="../tasks/images/task-add_jre_ee_file.PNG" alt="Add EE File JRE" width="419" height="593">
-
-    <p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-  </p>
-    <p>     
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0">
-    </p>
-    <p>
-      <a href="../tasks/tasks-JREs.htm">Working with JREs</a><br>
-      <a href="tasks-deleteJRE.htm">Deleting a JRE definition</a><br>
-      <a href="../tasks/task-assign_default_jre.htm">Choosing a default JRE</a><br>
-      <a href="../tasks/task-choose_config_jre.htm">Choosing a JRE for launching a project</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-apply_hit_count.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-apply_hit_count.htm
deleted file mode 100644
index 40e5328..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-apply_hit_count.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Applying Hit Counts
-    </title>
-  </head>
-  <body>
-    <h1>
-      Applying Hit Counts
-    </h1>
-    <p>
-      A hit count can be applied to line breakpoints, exception breakpoints, watchpoints and method breakpoints. When a hit count is applied to a breakpoint, the breakpoint
-      suspends execution of a thread the <em>n</em>th time it is hit, but never again, until it is re-enabled or the hit count is changed or disabled.
-    </p>
-    <p>
-      To set a hit count on a breakpoint:
-    </p>
-    <ol>
-      <li>
-        Select the breakpoint to which a hit count is to be added.
-      </li>
-      <li>
-        From the breakpoint's pop-up menu, select <strong><a href="../reference/views/breakpoints/ref-hitcount_contextaction.htm">Hit Count</a></strong>.      </li>
-      <li>
-        In the <strong>Enter the new hit count for the breakpoint</strong> field, type the number of times you want to hit the breakpoint before suspending
-        execution.<br>
-        <br>
-         <strong>Note:</strong> When the breakpoint is hit for the <em>n</em>th time, the thread that hit the breakpoint suspends. The breakpoint is disabled until either it is
-        re-enabled or its hit count is changed.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-       <a href="../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-       <a href="../tasks/task-enable_disable_breakpoints.htm">Enabling and disabling breakpoints</a><br>
-       <a href="../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-assign_default_jre.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-assign_default_jre.htm
deleted file mode 100644
index ef42c23..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-assign_default_jre.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Assigning the default JRE for the workbench
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Assigning the default JRE for the workbench
-    </h1>
-    
-<p> The default JRE is used for compiling and launching Java programs in all projects 
-  unless you specifically <a href="task-choose_config_jre.htm">override the default JRE</a> on a project's build path or 
-  on a launch configuration.</p>
-    <p>
-      Here is how you can change the default JRE:
-    </p>
-    <ol>
-      <li>
-        Open the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.preferences.VMPreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Installed JREs preference page">
-        <strong>Java &gt; Installed JREs</strong></a> preference page.
-      </li>
-      <li>
-        Check the box on the line for the JRE that you want to assign as the default JRE in your workbench.
-        If the JRE you want to assign as the default does not appear in the list, you must <a href="task-add_new_jre.htm">add it</a>.
-      </li>
-      <li>
-        Click <strong>OK</strong>.
-      </li>
-    </ol>
-    
-<strong>Note</strong>: Changing the default JRE may cause a build to occur if 
-you have auto build enabled (<strong>Project &gt; Build Automatically</strong> 
-or in the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'> 
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Workspace preference page"> <strong>General &gt; 
-Workspace</strong></a> preference page). 
-
-	<p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-     </p>
-    <p>     
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0">
-    </p>
-    <p>
-      <a href="../tasks/tasks-JREs.htm">Working with JREs</a><br>
-      <a href="../tasks/task-add_new_jre.htm">Adding a new JRE definition</a><br>
-      <a href="tasks-deleteJRE.htm">Deleting a JRE definition</a><br>
-      <a href="../tasks/task-choose_config_jre.htm">Choosing a JRE for launching a project</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-catching_exceptions.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-catching_exceptions.htm
deleted file mode 100644
index c16ca3b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-catching_exceptions.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Catching Java Exceptions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Catching Java Exceptions
-    </h1>
-    <p>
-      It is possible to suspend the execution of thread when an exception is thrown by specifying an
-      exception breakpoint. Execution can be suspended at locations where the exception is
-      uncaught, caught, or both.
-    </p>
-    <ol>
-      <li>
-        Choose <strong>Add Java Exception Breakpoint</strong>  from the
-        <a href="../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a> or the workbench <strong>Run</strong> menu.&nbsp;&nbsp;      </li>
-      <li>
-        A dialog listing all of the available exceptions is presented (see the following figure).<br>
-        <br>
-        <img src="../tasks/images/task-add-exception-breakpoint.PNG" alt="Add Exception Breakpoint Dialog"><br>
-        <br>
-      </li>
-      <li>
-        Type the name of the exception you want to catch or select it from the list.      </li>
-      <li>
-        At the bottom of the page, use the checkboxes to specify how you want execution to suspend at locations where the exception is thrown. 
-        <ul>
-          <li>
-            Select <strong>Caught</strong> if you want execution to suspend at locations where the exception
-            is thrown and caught by a <code>catch</code> clause.          </li>
-          <li>
-            Select <strong>Uncaught</strong> if you want execution to suspend at locations where the exception is uncaught.          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      <strong>Note:</strong> Exception breakpoints can be enabled and disabled and have hit counts
-    just like regular breakpoints.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a><br>
-       <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-    <img border="0" src="../images/ngrelt.png" alt="Related tasks" ></p>
-    <p><a href="../tasks/tasks-create-exception-filter-expression.htm">Creating Exception Breakpoint Filters</a> <br>
-      <a href="../tasks/task-suspending_threads.htm">Suspending threads</a><br>
-      <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-      <a href="../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-      <a href="../tasks/task-enable_disable_breakpoints.htm">Enabling and disabling breakpoints</a><br>
-      <a href="../tasks/task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a> <br> 
-	  <a href="../reference/views/breakpoints/ref-addexception_viewaction.htm">Add Java exception breakpoint</a><br></p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-choose_config_jre.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-choose_config_jre.htm
deleted file mode 100644
index a4261aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-choose_config_jre.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Choosing a JRE for a launch configuration
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Choosing a JRE for a launch configuration
-    </h1>
-    <p>
-      Instead of using the default JRE for running and debugging all <strong>Java Application</strong> launch configurations, you can specifically assign a JRE for launching an individual
-      configuration.    </p>
-    <ol>
-      <li>
-        With a Java Application configuration selected in the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenRunConfigurations")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Launch Configuration dialog">
-        <strong>Launch Configuration Dialog</strong></a>, select the JRE tab.
-      </li>
-      <li>
-        In the list of available JREs, select the JRE you want to use to launch this configuration and click <strong>Apply</strong>, then <strong>Run</strong> or <strong>Debug</strong>.      </li>
-    </ol>
-    <p>
-      <strong>Note</strong>: Changing the JRE used for running does not affect the way Java source is compiled. You can adjust the build path to compile against custom
-      libraries.&nbsp;
-    </p>
-    
-	<p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-     </p>
-    <p>     
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0">
-    </p>
-    <p>
-      <a href="../tasks/tasks-JREs.htm">Working with JREs</a><br>
-      <a href="../tasks/task-add_new_jre.htm">Adding a new JRE definition</a><br>
-      <a href="tasks-deleteJRE.htm">Deleting a JRE definition</a><br>
-      <a href="../tasks/task-assign_default_jre.htm">Choosing a default JRE</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-create_scrapbook_page.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-create_scrapbook_page.htm
deleted file mode 100644
index 2a06169..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-create_scrapbook_page.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Creating a Java Scrapbook Page
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Creating a Java Scrapbook Page
-    </h1>
-    <p>
-      The scrapbook allows Java expressions, to be run, inspected, and displayed under the control of the debugger. Breakpoints and exceptions
-      behave as they do in a regular debug
-      session.
-    </p>
-    <p>
-      Code is edited on a scrapbook page.&nbsp; A VM is launched for each scrapbook page in which expressions are being evaluated. The first time an expression is evaluated in a scrapbook page after it is opened, a VM is
-      launched. The VM for a page will remain active until the page is closed, terminated explicitly (in the debugger or via the <strong>Stop the Evaluation</strong> button in the
-      editor toolbar), or when a <em>System.exit()</em> is evaluated.
-    </p>
-    <p>
-      There are several ways to open the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.debug.ui.snippetEditor.NewSnippetFileCreationWizard)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Java Scrapbook wizard">
-      <strong>New Java Scrapbook Page</strong></a> wizard.
-    </p>
-        
-<ul>
-  <li> Create a file with a <strong>.jpage</strong> extension</li>
-  <li> From the menu bar, select <strong>File</strong> &gt; <strong>New</strong> 
-    &gt; <strong>Other...</strong>. Then select <strong>Java</strong> &gt; <strong>Java 
-    Run/Debug</strong> &gt; <strong>Scrapbook Page</strong>. Then click <strong>Next</strong>. 
-  </li>
-</ul>
-    Once you've opened the New Java Scrapbook Page wizard:.
-    <ol>
-      <li>
-        In the <strong>Enter or select the folder</strong> field, type or click <strong>Browse</strong> to select the container for the new page.
-      </li>
-      <li>
-        In the <strong>File name</strong> field, type a name for the new page. The <em>.jpage</em> extension will be added automatically if you do not type it
-        yourself.
-      </li>
-      <li>
-        Click <strong>Finish</strong> when you are done. The new scrapbook page opens in an editor.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cscrapbook.htm">Scrapbook</a><br>
-       <a href="../concepts/concept-java-project.htm">Java projects</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-       <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/ref-view-scrapbook.htm">Java scrapbook page</a>    </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-disconnect_remote_debug.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-disconnect_remote_debug.htm
deleted file mode 100644
index 9525221..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-disconnect_remote_debug.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Disconnecting from a VM
-    </title>
-  </head>
-  <body>
-    <h1>
-      Disconnecting from a VM
-    </h1>
-    <p>
-      To disconnect from a VM that was connected to with a <strong>Remote Java Application</strong> launch configuration:    </p>
-    <ol>
-      <li>
-        In the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>, select the launch.      </li>
-      <li>
-        Click the <strong><a href="../reference/views/debug/ref-disconnect.htm">Disconnect</a></strong> button [ <img src="../images/org.eclipse.debug.ui/elcl16/disconnect_co.png" alt="Disconnect"> ] in the view toolbar. </li>
-    </ol>
-    <p>Communication with the VM is terminated, and all threads in the remote VM are
-    resumed. Although the remote VM continues to execute, the debug session is now terminated. </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cdebugger.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/task-remotejava_launch_config.htm">Connecting to a remote VM with the Remote Java application launch configuration</a><br>
-       <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-display_evaluation_result.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-display_evaluation_result.htm
deleted file mode 100644
index 41415bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-display_evaluation_result.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Displaying the result of evaluating an expression
-    </title>
-  </head>
-  <body>
-    <h1>
-      Displaying the result of evaluating an expression
-    </h1>
-    <p>
-      Displaying shows the result of evaluating an expression in the scrapbook editor.
-    </p>
-    <ol>
-      <li>
-        In the scrapbook page, either type an expression or highlight an existing expression to be displayed. For example: <code>System.getProperties();</code>
-      </li>
-      <li>
-        Click the <strong>Display</strong> button in the toolbar (or select <strong>Display</strong> from the selection's pop-up menu.)
-      </li>
-      <li>
-        The result of the evaluation appears highlighted in the scrapbook editor. The result displayed is either 
-        <ul>
-          <li>
-            the value obtained by sending <code>toString()</code> to the result of the evaluation, or
-          </li>
-          <li>
-            when evaluating a primitive data type (e.g., an <em>int</em> ), the result is the simple value of the result.
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      For example:
-    </p>
-    <ul>
-      <li>
-        Type and highlight <code>new java.util.Date()</code> in the editor, and click <strong>Display</strong>. A result such as <code>(java.util.Date) Tue Jun 12
-        14:03:17 CDT 2001</code> appears in the editor.
-      </li>
-      <li>
-        As another example, type and highlight <code>3 + 4</code> in the editor, and press <strong>Display</strong>. The result <code>(int) 7</code> is displayed in the
-        editor.
-      </li>
-    </ul>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cscrapbook.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/task-executing_an_expression.htm">Executing an expression</a><br>
-       <a href="task-inspect_evaluation_result.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="../tasks/task-view_runtime_exceptions.htm">Viewing runtime exceptions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/ref-view-scrapbook.htm">Java scrapbook page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-enable_disable_breakpoints.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-enable_disable_breakpoints.htm
deleted file mode 100644
index 5e1d7a9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-enable_disable_breakpoints.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Enabling and disabling breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Enabling and disabling breakpoints
-    </h1>
-    <p>
-      Breakpoints can be enabled and disabled as needed.&nbsp; When a breakpoint is enabled, thread execution suspends before that line of code is executed.&nbsp;
-      When a breakpoint is disabled, thread execution is not suspended by the
-      presence of the breakpoint.
-    </p>
-    
-<p> To disable a breakpoint in the <strong><a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></strong>: </p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong><a href="../reference/views/breakpoints/ref-disable_contextaction.htm">Disable</a></strong>, 
-    or deselect the breakpoint's checkbox.</li>
-  <li> The breakpoint image will change to a white circle and its checkbox will 
-    be empty.</li>
-</ol>
-<p>To disable a breakpoint in the marker bar of an editor: </p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong>Disable Breakpoint</strong>.</li>
-  <li> The breakpoint image will change to a white circle.</li>
-</ol>
-<p>To enable the breakpoint in the <strong><a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></strong>:</p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong><a href="../reference/views/breakpoints/ref-enable_contextaction.htm">Enable</a></strong>, 
-    or select the breakpoint's checkbox. </li>
-  <li> The breakpoint image will change back to a blue circle, and its checkbox 
-    will be checked.</li>
-</ol>
-<p>To enable a breakpoint in the marker bar of an editor: </p>
-<ol>
-  <li> Open the breakpoint's context menu and select <strong>Enable Breakpoint</strong>.</li>
-  <li> The breakpoint image will change to a white circle.</li>
-</ol>
-<p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-    <a href="../concepts/cdebugger.htm">Debugger</a><br>
-     <a href="../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-     <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-  </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-apply_hit_count.htm">Applying hit counts</a><br>
-       <a href="task-catching_exceptions.htm">Catching Java exceptions</a><br>
-       <a href="../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-       <a href="task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-       <a href="task-manage_conditional_breakpoint.htm">Managing conditional breakpoints</a><br>
-       <a href="../tasks/task-stepping.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a>    </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-evaluating_expressions.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-evaluating_expressions.htm
deleted file mode 100644
index 49fd19b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-evaluating_expressions.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Evaluating expressions</title>
-</head>
-<body>
-<h1> Evaluating expressions </h1>
-<p>When the VM suspends a thread (due to hitting a breakpoint or stepping through 
-  code), you can evaluate expressions in the context of a stack frame. </p>
-<ol>
-  <li> Select the stack frame in which an evaluation is to be performed. The evaluation context will be the currently selected variable in the view. If no variable 
-    is selected, the selected stack frame will be the context. </li>
-  <li> Expressions can be entered and evaluated in the following areas:
-    <ul>
-      <li> <strong><a href="../reference/views/display/ref-display_view.htm">Display View</a></strong> </li>
-      <li> <a href="../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a> (in the <a href="../reference/views/expressions/ref-expressions_view.htm"><strong>Expressions View</strong></a> and <a href="../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>)</li>
-      <li><a href="../concepts/concept-java-editor.htm"><strong>Java Editor</strong></a> when it is displaying source and it is not read-only </li>
-    </ul>
-  </li>
-  <li> Select the expression to be evaluated and select <a href="../reference/views/shared/ref-display.htm"><strong>Display</strong></a>, <a href="../reference/views/shared/ref-inspect.htm"><strong>Inspect</strong></a> or <a href="../reference/views/shared/ref-execute.htm"><strong>Execute</strong></a> from the context pop-up 
-    menu. The result of a <strong>Display</strong> or <strong>Inspect </strong>evaluation 
-    is shown in a popup window. Note that <strong>Execute</strong> does not display 
-    a result - the expression is just executed.</li>
-  <li>The result popup window can be dismissed by clicking outside of the popup 
-    window or by pressing <em><strong>Esc</strong></em>. The result can be persisted to 
-    the Display view (if <strong>Display</strong> was chosen) or Expressions view 
-    (if <strong>Inspect</strong> was chosen) by pressing the key sequence shown 
-    at the bottom of the popup window. For example, to move the result of an <strong>Inspect </strong>evaluation to the Expressions view press <em><strong>Ctrl-Shift-I</strong></em>. 
-    Note that when the <strong>Display</strong> action is used from the Display 
-    view the result is written to the Display view rather than a popup</li>
-</ol>
-<p><strong>Note:</strong> Evaluations cannot be performed in threads that have been manually suspended.</p>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/concept-java-editor.htm">Java editor</a> </p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="../tasks/task-suspending_threads.htm">Suspending threads</a><br>
-  <a href="../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a> </p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/views/shared/ref-detailpane.htm">Detail Pane</a><br>
-  <a href="../reference/views/display/ref-display_view.htm">Display view</a><br>
-  <a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a><br>
-  <a href="../reference/views/variables/ref-variables_view.htm">Variables view</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-executing_an_expression.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-executing_an_expression.htm
deleted file mode 100644
index 5a16be0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-executing_an_expression.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Executing an expression
-    </title>
-  </head>
-  <body>
-    <h1>
-      Executing an expression
-    </h1>
-    <p>
-      Executing an expression evaluates an expression but does not display a result.
-    </p>
-    <p>
-      If you select the expression to execute and click the <strong>Execute</strong> button in the toolbar, no result is
-      displayed, but the code is executed.&nbsp;&nbsp;
-    </p>
-    <p>
-      For example, if you type and highlight <code>System.out.println(&quot;Hello World&quot;)</code>, and click the <strong>Execute</strong> button, <em>Hello World</em>
-      appears in the Console view, but no result is displayed in the scrapbook editor or the Expressions view.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-display_evaluation_result.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="task-inspect_evaluation_result.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="../tasks/task-view_runtime_exceptions.htm">Viewing runtime exceptions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a><br>
-       <a href="../reference/views/console/ref-console_view.htm">Console view</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-inspect_evaluation_result.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-inspect_evaluation_result.htm
deleted file mode 100644
index dc3f045..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-inspect_evaluation_result.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Inspecting the result of evaluating an expression
-    </title>
-  </head>
-  <body>
-    <h1>
-      Inspecting the result of evaluating an expression
-    </h1>
-    <p>
-      Inspecting shows the result of evaluating an expression in the Expressions view.
-    </p>
-    <ol>
-      <li>
-        In the scrapbook page, either type an expression or highlight an existing expression to be inspected. For example: <code>System.getProperties();</code>
-      </li>
-      <li>
-        Click the <strong>Inspect</strong> button in the toolbar (or select <strong>Inspect</strong> from the selection's pop-up
-        menu).
-      </li>
-      
-  <li> The result of the inspection appears in a pop-up.&nbsp; </li>
-      <li>
- The result can be inspected like a variable in the debugger (for
-        example, children of the result can be expanded).
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cscrapbook.htm">Scrapbook</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/task-create_scrapbook_page.htm">Creating a Java scrapbook page</a><br>
-       <a href="../tasks/task-display_evaluation_result.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="../tasks/task-executing_an_expression.htm">Executing an expression</a><br>
-       <a href="../tasks/task-view_runtime_exceptions.htm">Viewing runtime exceptions</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/expressions/ref-expressions_view.htm">Expressions view</a><br>
-       <a href="../reference/views/ref-view-scrapbook.htm">Java scrapbook page</a>    </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-inspecting.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-inspecting.htm
deleted file mode 100644
index b753aa2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-inspecting.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Inspecting values
-    </title>
-  </head>
-  <body>
-    <h1>
-      Inspecting values
-    </h1>
-    <p>
-      When a stack frame is selected, you can see the visible variables in that
-      stack frame in the <a href="../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a>.    </p>
-    <p>
-      The Variables view shows the value of primitive types.&nbsp; Complex
-      variables can be examined by expanding them to show their members.
-    </p>
-     <p><img src="../images/ngrelr.png" alt="Related Reference"></p>
-  <p><a href="../reference/views/expressions/ref-inspect.htm">Inspecting Values in the Expressions View</a><br>
-  <a href="../reference/views/shared/ref-inspect.htm">Inspecting Values in the Variables View</a><br>
-  <a href="../reference/views/shared/ref-inspect.htm">Inspecting Values in other views </a></p>
-  <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_applet.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_applet.htm
deleted file mode 100644
index 58c829f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_applet.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Launching a Java applet
-    </title>
-  </head>
-  <body>
-    <h1>
-      Launching a Java applet
-    </h1>
-    <p>If your Java program is structured as an applet, you can use the <strong> Java
-    Applet </strong>launch configuration.&nbsp; This launch configuration uses information
-    derived from the workbench preferences and your program's Java project to launch the program.
-    </p>
-    
-<ol>
-  <li> In the <strong>Package Explorer</strong>, select the Java compilation unit 
-    or class file containing the applet you want to launch. </li>
-  <li>Press the <strong>Run</strong> [ <img src="../images/org.eclipse.debug.ui/etool16/run_exc.png" width="16" height="16"> 
-    ] button in the workbench toolbar or select <strong>Run &gt; Run</strong> 
-    from the workbench menu. Alternatively, select <strong>Run As &gt; Java Applet</strong> 
-    from the <strong>Package Explorer</strong> pop-up menu, select <strong>Run 
-    &gt; Run As &gt; Java Applet </strong>in the workbench menu bar, or select 
-    <strong>Run As &gt; Java Applet </strong>in the drop-down menu on the <strong>Run</strong> 
-    tool bar button.&nbsp; </li>
-  <li> Your program is now launched. </li>
-</ol>
-    <p>You can also launch a Java applet by selecting a project instead of the
-    compilation unit or class file.&nbsp; You will be prompted to select a class
-    from those classes that extend Applet.&nbsp; (If only one applet class is
-        found in the project, that class is launched as if you selected it.)</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-       <a href="../concepts/cdebugger.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-       <a href="task-relaunch_program.htm">Re-launching a program</a><br>
-       <a href="task-running_and_debugging.htm">Running and debugging</a><br>
-       <a href="task-stepping.htm">Stepping through the execution of a program</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_program.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_program.htm
deleted file mode 100644
index 5fbd66b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-launching_java_program.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Launching a Java Program
-    </title>
-  </head>
-  <body>
-    <h1>
-      Launching a Java Program
-    </h1>
-    
-<p>The simplest way to launch a Java program is to run it using a<strong> Java 
-  Application </strong> launch configuration.&nbsp;This launch configuration type 
-  uses information derived from the workbench preferences and your program's Java 
-  project to launch the program. </p>
-    
-<ol>
-  <li> In the <strong>Package Explorer</strong>, select the Java compilation unit 
-    or class file with the main method you want to launch. </li>
-  <li>Press the <strong>Run</strong> [ <img src="../images/org.eclipse.debug.ui/etool16/run_exc.png" width="16" height="16"> 
-    ] button in the workbench toolbar or select <strong>Run &gt; Run</strong> 
-    from the workbench menu bar. Alternatively, select <strong>Run As &gt; Java 
-    Application</strong> in the <strong>Package Explorer</strong> pop-up menu, 
-    or select <strong>Run &gt; Run As &gt; Java Application </strong>in the workbench 
-    menu bar, or select <strong>Run As &gt; Java Application </strong>in the drop-down 
-    menu on the <strong>Run</strong> tool bar button.</li>
-  <li> Your program is now launched, and text output is shown in the <a href="../reference/views/console/ref-console_view.htm"><strong>Console 
-    View</strong></a>. </li>
-</ol>
-    
-<p>You can also launch a Java program by selecting a project instead of the compilation 
-  unit or class file.&nbsp; You will be prompted to select a class from those 
-  classes that define a <em>main</em> method.&nbsp; (If only one class with a 
-  main method is found in the project, that class is launched as if you selected 
-  it.)</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-       <a href="../concepts/cdebugger.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-remotejava_launch_config.htm">Connecting to a remote VM with the Java Remote Application launcher</a><br>
-       <a href="task-relaunch_program.htm">Re-launching a program</a><br>
-       <a href="task-running_and_debugging.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="task-stepping.htm">Stepping through the execution of a program</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-	  <a href="../reference/views/console/ref-console_view.htm">Console View</a> <br>
-      <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-manage_conditional_breakpoint.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-manage_conditional_breakpoint.htm
deleted file mode 100644
index b4ffa39..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-manage_conditional_breakpoint.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title> Managing conditional breakpoints </title>
-  </head>
-<body>
-<h1> Managing conditional breakpoints </h1>
-<p> 
-      A conditional expression can be applied to a line breakpoint such that the
-      breakpoint suspends execution of a thread in one of these cases: </p>
-<ul>
-  <li>when the result of the expression is true</li>
-  <li>when the result of the expression changes</li>
-</ul>
-<p>A conditional expression can contain arbitrary Java code and may contain more than one statement, allowing breakpoint conditions to implement features like tracing. For example, a condition can execute a print statement and then return a hard coded value to never suspend (&quot;<code>System.out.println(...); return false;</code>&quot;).</p>
-<p>To set a condition on a breakpoint: </p>
-<ol>
-      <li>
-        Find the breakpoint to which an enabling condition is to be applied (in
-        the <a href="../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a> or in the editor marker bar).      </li>
-      <li>
-        From the breakpoint's pop-up menu, select <strong><a href="../reference/views/breakpoints/ref-properties_contextaction.htm">Breakpoint
-        Properties...</a></strong>.&nbsp; The Breakpoint properties dialog will open.      </li>
-  <li> In the properties dialog, check the <strong><a href="../reference/breakpoints/ref-condition_option.htm">Enable Condition</a></strong> checkbox.&nbsp; </li>
-  <li> In the <strong><a href="../reference/breakpoints/ref-condition_option.htm">Condition</a></strong> field enter the expression for 
-    the breakpoint condition. </li>
-  <li> Do one of the following:
-    <ul>
-      <li>If you want the breakpoint to stop every time the condition evaluates
-        to <em>true</em>, select the <strong>condition is 'true' </strong>option.&nbsp;
-        The expression provided must be a boolean expression.</li>
-      <li>If you want the breakpoint to stop only when the result of the
-        condition changes, select the <strong>value of condition changes </strong>option.</li>
-    </ul>
- </li>
-  <li> Select <strong>OK</strong> to close the dialog and commit the changes. While 
-    the breakpoint is enabled, thread execution suspends before that line of code 
-    is executed if the breakpoint condition evaluates to <em>true</em>.&nbsp; 
-  </li>
-</ol>
-<p>
-    A conditional breakpoint has a question mark overlay on the breakpoint icon.</p>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-  <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-</p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" > 
-  <br>
-  <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-  <a href="task-apply_hit_count.htm">Applying hit counts</a><br>
-  <a href="task-catching_exceptions.htm">Catching Java exceptions</a><br>
-  <a href="../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-  <a href="task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-  <a href="../tasks/task-stepping.htm">Stepping through the execution of a program</a> 
-</p>  
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a></p>
-<p>&nbsp;</p>
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-add.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-add.htm
deleted file mode 100644
index 35b61cf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-add.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Adding a variable, expression, or register to the Memory view</title>
-  </head>
-  
-<body>
-
-<h1>Adding a variable, expression, or register to the Memory view</h1>
-
-  <p>You can add a register, variable name, or expression (such as a raw address, for example, 0x00000234) to a memory monitor from the Memory view.</p>
-
-  <p>To add a new memory monitor from the Memory view:</p>
-
-  <ol>
-    <li>Click the Memory view <strong>Add Memory Monitor</strong> push button (<img src="images/task-memory-add-monitor.gif" alt="Add Memory Monitor button">). This button is located in the <strong>Monitors</strong> pane.</li>
-    <li>In the  Monitor Memory dialog box, enter the address or expression in the field (expressions must evaluate to an address). This entry does not need to be case-sensitive. Alternatively, if you have previously monitored the address or expression when debugging this application, choose it from the pull down list. Depending on the debug engine that the debugger user interface is connected to, examples of valid expressions include register names, variables, and HEX addresses.
-      <p><strong>Note:</strong> When adding a register to a memory monitor, the Registers view is a convenient location to see the names of all registers in your application. You can make note of the name of a register from the view and then use it when adding a memory monitor.</p>
-    </li>
-    <li>Click <strong>OK</strong>.</li>
-  </ol>
-
-  <p>After adding the new memory monitor you can choose the memory format that you want to display in the <strong>Renderings</strong> pane.</p>
-  
-  <p>You can also add a new memory monitor from the Memory view <strong>Renderings</strong> pane:</p>
-  
-  <ol>
-    <li>Click the Memory view <strong>Add Rendering(s)</strong> push button (<img alt="Add Memory Monitor button" src="images/task-memory-add-monitor.gif">). This button is located in the <strong>Renderings</strong> pane.</li>
-    <li>In the Add Memory Rendering dialog box, select an existing memory monitor from the pull-down list - or add a new memory monitor by clicking <strong>Add New</strong>. If you add a new memory monitor, you will be prompted via the Monitor Memory dialog box to enter an address or expression to monitor. Click <strong>OK</strong> to return to the Add Memory Rendering dialog box.</li>
-    <li>Do one of the following:
-      <ul>
-        <li>Select the memory rendering that you want to display for the memory monitor and click <strong>OK</strong>.</li>
-        <li>Click <strong>Cancel</strong> and then choose the memory rendering that you want to display right from the <strong>Renderings</strong> pane.</li>
-      </ul>
-    </li>
-  </ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-change.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-change.htm
deleted file mode 100644
index 95a891d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-change.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Changing the contents of a memory location</title>
-  </head>
-  
-<body>
-
-<h1>Changing the contents of a memory location</h1>
-
-  <p>To change the contents of a memory location in a memory monitor in the Memory view:</p>
-
-  <ol>
-    <li>In the <strong>Monitors</strong> pane, select the memory monitor that contains the memory location that you want to edit. Memory will appear in the <strong>Renderings</strong> pane, where you will perform all other steps. If you have added multiple renderings, select the tab that contains the rendering that you want to edit.</li>
-    <li>Scroll down to the memory location you want to change. Alternatively, right-click in the monitor and choose the <strong>Go to Address</strong> pop-up menu item. This will open a Go To Address section at the bottom of the rendering, in which you can enter an address that you want to jump to.</li>
-    <li>Select the row containing the value that you want to change and then double-click the value that you want to change.
-      <p><strong>Tip:</strong> If the rendering is currently in focus, you do not need to double-click the value that you want to change to be able to edit it. Rather, you can simply start typing the change and the editor will activate.</p>
-    </li>
-    <li>Enter a valid value for that memory location.</li>
-    <li>Press <strong>Enter</strong> to submit the change. The debugger checks for a valid value.</li>
-  </ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-inspect.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-inspect.htm
deleted file mode 100644
index 25a6b04..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-inspect.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Inspecting memory in the Memory view</title>
-  </head>
-  
-<body>
-
-<h1>Inspecting memory in the Memory view</h1>
-
-  <p>With the Memory view, you can look at the contents of memory at a specific address. The address can be obtained from an expression that references a variable or a register. When you monitor memory, you can set the monitor to be rendered in various data formats.</p>
-
-  <p>The Memory view is comprised of two portions:</p>
-  
-  <ul>
-    <li>The <strong>Monitors</strong> pane is located on the left-hand side of the view. This portion of the view contains a list of expressions, variables, and registers that you have added for monitoring.</li>
-    <li>The <strong>Renderings</strong> pane is located on the right-hand side of the view (if the view is set to horizontal orientation). You use it to set the data format (or formats) that you want displayed for monitored memory.</li>
-  </ul>
-  
-  <p>When you monitor an address or expression from the <strong>Monitors</strong> pane, the <strong>Renderings</strong> pane becomes populated with a set of default renderings provided by your debugger. When you monitor an address or expression from the <strong>Renderings</strong> pane, the pane becomes populated with a list of renderings from which you can choose one to display.</p>
-  
-  <p>You can monitor multiple variables, expressions, and registers in the Memory view - and you can add multiple renderings to the <strong>Renderings</strong> pane. In the <strong>Monitors</strong> pane, each variable, expression, or register that you have added is listed. In the <strong>Renderings</strong> pane, only the memory rendering(s) for the currently-selected monitor in the Memory view is displayed (multiple renderings are separated by tabs or a split pane).</p>
-  
-  <p>You can set the two panes in the Memory view to display in a horizontal orientation (side-by-side) or in a vertical orientation (top-to-bottom). To set the layout of the view, click the Memory view down-arrow icon and select <strong>Layout</strong> from the menu. This will open a submenu, from which you can choose the orientation that you want to display.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-monitors.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-monitors.htm
deleted file mode 100644
index ef50ef2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-monitors.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Working with memory monitors</title>
-  </head>
-  
-<body>
-
-<h1>Working with memory monitors</h1>
-
-  <p>To view the contents of memory from the Memory view:</p>
-
-  <ol>
-    <li>In the <strong>Monitors</strong> pane, select the memory monitor that contains the memory location that you want to view. Memory will appear in the <strong>Renderings</strong> pane, where you will perform all other steps. If you have added multiple renderings, select the tab that contains the rendering that you want to view.</li>
-    <li>If desired, split the <strong>Renderings</strong> pane by selecting the <strong>Toggle Split Pane</strong> push button (<img src="images/task-memory-det-pane.gif" alt="Toggle Split Pane push button">). By default, the Memory view only displays one rendering pane. When you click <strong>Toggle Split Pane</strong>, a second rendering opens and displays as a split pane.</li>
-    <li>If necessary, use the scroll bar in the rendering to view memory locations above or below the base address of the memory monitor being shown by the current rendering. Alternatively, you can right-click in the rendering and choose the <strong>Go to Address</strong> pop-up menu item or hit Ctrl+G. This will open a section at the bottom of the rendering, in which you can perform the following actions:
-      <ul>
-        <li>Select the <strong>Go to Address</strong> pull-down menu item and then enter an address that you want to jump to. The rendering will be positioned so that the address entered is visible and selected.</li>
-        <li>Select the <strong>Go to Offset</strong> pull-down menu item and then enter the offset. The rendering will be positioned so that the address of the expression (base address), plus the offset entered, is visible and selected. A negative value will position the rendering back from the base address.</li>
-        <li>Select the <strong>Jump Memory Units</strong> pull-down menu item. This function takes the currently-selected address and adds the number of memory units that you specify to it. The resulting address is selected. A negative value will position the rendering back from the current address.</li>
-      </ul>
-      <p>For all of these entries, you can input them as HEX by selecting the <strong>Input as Hex</strong> check box (if this check box is not selected, input will be decimal). Once you have made the entry in the field, hit Enter or click <strong>OK</strong> to go to the location in the rendering. To close this section, click <strong>Cancel</strong> or hit Ctrl+G.</p>
-      <p><strong>Note:</strong> Input is also treated as HEX if it is prefixed with <code>0x</code>.</p>
-    </li>
-    <li>If you want, change the width of any column by clicking the left or right side of its header cell and dragging it to alter the width of the column - or right-click inside the rendering and select <strong>Resize to Fit</strong> from the pop-up menu so that all columns are re-sized so that all text within them can be viewed. Alternatively, you can right-click inside the rendering and select <strong>Format</strong> from the pop-up menu. This will open the Format dialog box. In this dialog box, you can set the number of units per row and the number of units per column. As you make these settings, a <strong>Preview</strong> window in the dialog box displays the rendering layout that you are setting. To save these settings as the default layout, click <strong>Save as Defaults</strong>.</li>
-    <li>You can also hide elements of the Memory view for easier viewing:
-      <ul>
-        <li>You can hide the <strong>Monitors</strong> pane by deselecting the <strong>Toggle Memory Monitors Pane</strong> toggle.</li>
-        <li>You can hide the <strong>Address</strong> column by right-clicking inside the rendering and selecting <strong>Hide Address Column</strong>. To restore a the address column when it is hidden, right-click inside the rendering and select <strong>Show Address Column</strong> from the pop-up menu.</li>
-      </ul>
-    </li>
-  </ol>
-
-  <p>If you are in a memory rendering and move away from the address that you originally set to monitor, choosing the <strong>Reset to Base Address</strong> pop-up menu item will position the cursor back to the base address of the memory monitor. Alternatively, you can reset all renderings for a memory monitor by right-clicking the monitor and selecting <strong>Reset</strong> (or, you can select multiple monitors and choose this action). When you reset a monitor, by default, the visible renderings will be reset to the base address. To reset all renderings in the current Memory view to the base address, modify the Memory view preferences.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-add.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-add.htm
deleted file mode 100644
index ca2473c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-add.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Adding multiple memory renderings and removing renderings</title>
-  </head>
-
-<body>
-
-<h1>Adding multiple memory renderings and removing renderings</h1>
-
-  <p>When you add a variable, expression, or register to the Memory view, you can do so multiple times, each time adding a new (or the same) rendering. Alternatively, once you have added a memory monitor and rendering, you can go to the <strong>Renderings</strong> pane and click the <strong>Add Rendering(s)</strong> push button (<img alt="Add Rendering(s) push button" src="images/task-memory-add-monitor.gif">). This will prompt you with a dialog to select the rendering that you want to add to the view. In this dialog, you can select more than one rendering by using the keyboard Shift or Ctrl keys - doing this will cause a rendering to be opened for each rendering format that is selected. When you add multiple memory renderings, they are separated by tabs.</p>
-
-  <p>You can also split the <strong>Memory Renderings</strong> pane by selecting the <strong>Toggle Split Pane</strong> push button (<img alt="Toggle Split Pane push button" src="images/task-memory-det-pane.gif">). When the <strong>Renderings</strong> pane is split, you can view two renderings side-by-side.</p>
-
-  <p>When you have multiple memory renderings for a memory monitor, you can set the renderings to be linked with one another. To do this, select the <strong>Link Memory Rendering Panes</strong> push button (<img alt="Link Memory Rendering Panes push button" src="images/task-memory-link-panes.gif">). When renderings are linked, they are synchronized with each other (for example, if you change the column size in one rendering, the column size in the other rendering will also change - or if you scroll or move the cursor in one rendering, the other rendering will scroll or follow the same cursor movement). Linking memory renderings only applies to the current Memory view. If you have multiple Memory views open, they do not link to each other.</p>
-
-  <p>To remove a rendering, select it in the <strong>Renderings</strong> pane and click <strong>Remove Rendering</strong> (<img alt="Remove Memory Monitor push button" src="images/task-memory-remove-monitor.gif">). When you remove all memory renderings for a monitored expression, variable, or register, the <strong>Renderings</strong> pane will be populated with the memory rendering selection list. From this list, you can select the data format that you want to use for the memory rendering and then click <strong>Add Rendering(s)</strong>.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-views.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-views.htm
deleted file mode 100644
index a0b2945..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-multiple-views.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Working with multiple Memory views</title>
-  </head>
-
-<body>
-
-<h1>Working with multiple Memory views</h1>
-
-  <p>You can add additional Memory views to the workbench. To do this, click <strong>New Memory View</strong> (<img alt="New Memory View icon" src="images/task-memory-new.gif">). When you have multiple Memory views open, you cannot link their renderings to each other. However, you can pin the contents of a Memory view so that memory renderings that are added to one view do not affect the other view. To pin a memory monitor, ensure that the <strong>Pin Memory Monitor</strong> button (<img alt="Pin Memory Monitor icon" src="images/task-memory-pin.gif">) in the Memory view is toggled on. If you then go to another Memory view and add a memory monitor, it will show up in both Memory views, however, the memory rendering that is currently displayed in the pinned monitor will not change.</p>
-  
-  <p>When you add a new Memory view, its <strong>Renderings</strong> pane will be populated with the memory rendering selection list. From this list, you can select the data format that you want to use for the memory rendering and then click <strong>Add Rendering(s)</strong>.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-preference.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-preference.htm
deleted file mode 100644
index 16a0dff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-preference.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Memory view preferences</title>
-  </head>
-  
-<body>
-
-<h1>Memory view preferences</h1>
-
-  <p>You can set table rendering, codepage, and padded string preferences for memory renderings. In addition, you can modify the preferred behavior for resetting memory renderings.</p>
-
-  <p>Memory view preference dialog boxes are opened from the Memory view down-arrow icon menu. To open the Memory view Preferences dialog box, click the Memory view down-arrow icon and select <strong>Preferences</strong> from the menu. To open the Memory view table renderings Preferences dialog box, click the Memory view down-arrow icon and select <strong>Table Renderings Preferences</strong> from the menu.</p><p>To restore any changes that you make in the preferences to their default settings, click <strong>Restore Defaults</strong>.</p>
-
-  <h2>Preferences: Reset Memory Monitor</h2>
-
-  <p>You can reset a rendering to the base address if you have moved away from it. When you reset a rendering to the base address, you can set it to reset only the visible renderings - or you can set it to reset all renderings. If you choose to reset all renderings, performance of the reset operation can be negatively impacted. To set this preference, open the Preferences dialog box and then select the <strong>Reset Memory Monitor</strong> node. In the Reset Memory Monitor page, choose the appropriate radio button.</p>
-
-  <h2>Preferences: Padded String</h2>
-
-  <p>The padded string is the string that will appear in memory contents when memory cannot be retrieved. To set the padded string, open the Preferences dialog box and select the <strong>Padded String</strong> node. In the Padded String page, specify the string that you want to display when memory contents cannot be determined.</p>
-
-  <h2>Preferences: Select Codepages</h2>
-
-  <p>When monitoring ASCII and EBCDIC text-based renderings (and mapped memory, if it is available in the product that you installed this debugger with) in the <strong>Renderings</strong> pane, you can set the codepage in which you want the rendering to be displayed.</p><p>To set the codepage for rendering memory to ASCII/EBCDIC, open the Preferences dialog box and select the <strong>Select Codepages</strong> node. In the Select Codepages page, specify the codepage of the character set that you want to change (for ASCII renderings, EBCDIC renderings, or both).</p>
-
-  <h2>Table Renderings Preferences</h2>
-
-  <p>To set preferences for memory renderings that are displayed in a table, click the Memory view down-arrow icon and select <strong>Table Renderings Preferences</strong>. In the resulting preferences dialog box, there are two options:</p>
-  
-  <ul>
-    <li><strong>Automatic</strong> radio button: Select this if you want the debugger to automatically preload a buffer of memory before and after the visible region in the Memory view. When you select this setting, you can easily scroll away from the visible region of memory with scroll and page up/down actions.
-      <p>If the buffer size is large, the performance of refreshing the Memory view can be negatively impacted (the Memory view refreshes when there is a potential for memory change - so, for example, the Memory view refreshes when you step, suspend after running, change a variable or register, or modify memory). This is because a request for more memory must be made from the debug engine for each refresh. On the other hand, if the buffer size is too small, the performance of scrolling can be negatively impacted. This is because a request for more memory must be made from the debug engine when the buffer is exhausted. Given this performance trade-off, you need to set this option to suit your needs.</p>
-    </li>
-    <li><strong>Manual</strong> radio button: If you select this setting, then the number of lines per page that you specify will be loaded into the <strong>Renderings</strong> pane. When using this setting, you have more control in choosing exactly what you want to monitor, however, you will not be able to scroll outside the buffer defined by this page size setting. Instead, to view memory from the next page or previous page, you must right-click to use the <strong>Previous Page</strong> and <strong>Next Page</strong> actions from the pop-up menu.
-      <p>If the buffer size is large, the performance of refreshing the Memory view can be negatively impacted (the Memory view refreshes when there is a potential for memory change - so, for example, the Memory view refreshes when you step, suspend after running, change a variable or register, or modify memory). This is because a request for more memory must be made from the debug engine for each refresh.</p>
-    </li>
-  </ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-remove.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-remove.htm
deleted file mode 100644
index f24ecd7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-memory-remove.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-    <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>Removing memory monitors from the Memory view</title>
-  </head>
-  
-<body>
-
-<h1>Removing memory monitors from the Memory view</h1>
-
-  <p>To remove a memory monitor from the Memory view:</p>
-
-  <ol>
-    <li>Select the memory monitor that you want to remove (by selecting it in the list in the <strong>Monitors</strong> pane).</li>
-    <li>Click the <strong>Remove Memory Monitor</strong> push button (<img alt="Remove Memory Monitor button" src="images/task-memory-remove-monitor.gif">).</li>
-  </ol>
-
-  <p>To remove multiple memory monitors, select them using the keyboard Ctrl or Shift keys, and then click <strong>Remove Memory Monitor</strong>. To remove all memory monitors, click <strong>Remove All</strong>.</p>
-
-  <p><strong>Note:</strong> If you have added multiple renderings for a memory monitor, all renderings will be removed when you choose to remove the monitor.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-preparing_to_debug.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-preparing_to_debug.htm
deleted file mode 100644
index a57018b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-preparing_to_debug.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Preparing to Debug</title>
-</head>
-<body>
-<h1> Preparing to Debug </h1>
-<p> You can make your programs easier to debug by following these guidelines: </p>
-<ul>
-  <li> Where possible, do not put multiple statements on a single line, because some debugger features operate on a line basis. For example, you cannot step over or set line
-    breakpoints on more than one statement on the same line. </li>
-  <li> Attach source code to JAR files if you have the source code. </li>
-</ul>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-  <a href="../concepts/clocdbug.htm">Local debugging</a> </p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="task-running_and_debugging.htm">Running and debugging</a> </p>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-  <a href="../reference/menus/run/ref-menu-run.htm">Run Menu </a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-relaunch_program.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-relaunch_program.htm
deleted file mode 100644
index 10fd3fb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-relaunch_program.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Re-launching a program
-    </title>
-  </head>
-  <body>
-    <h1>
-      Re-launching a program
-    </h1>
-    <p>
-      The workbench keeps a history of each launched and debugged program. To
-      relaunch a program, do one of the following:
-    </p>
-    <ul>
-      <li>
-        Select a previous launch from <strong>Run</strong> or <strong>Debug</strong> button pull-down menus.
-      </li>
-      <li>
-        From the menu bar, select <strong>Run</strong> &gt; <strong>Run History</strong> or <strong>Run</strong> &gt; <strong>Debug History</strong> and select a previous launch
-        from these sub-menus.
-      </li>
-      <li>
-        In the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>, select a process that you want to relaunch, and select <strong><a href="../reference/views/debug/ref-relaunch.htm">Relaunch</a></strong> from the process's pop-up menu.      </li>
-    </ul>
-    <p>
-      To relaunch the most recent launch, do one of the following:
-    </p>
-    <ul>
-      <li>
-        Click the <strong>Run</strong> or <strong>Debug</strong>  buttons
-        (without using the button pull-down menu).
-      </li>
-      
-  <li> Select <strong>Run</strong> &gt; <strong>Run Last Launched</strong> (<kbd>Ctrl+F11</kbd>), 
-    or <strong>Run</strong> &gt; <strong>Debug Last Launched</strong> (<kbd>F11</kbd>)
-    from the workbench menu bar. 
-  </li>
-    </ul>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-launching_java_program.htm">Launching a Java program</a><br>
-       <a href="task-running_and_debugging.htm">Running and debugging</a>
-    </p>
-  <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-    <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a>
-      <br>
-      <a href="../reference/views/debug/ref-relaunch.htm">Relaunch command</a><br>
-    <a href="../reference/views/debug/ref-terminaterelaunch.htm">Terminate and Relaunch command  </a></p>
-  <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-remotejava_launch_config.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-remotejava_launch_config.htm
deleted file mode 100644
index b16fddf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-remotejava_launch_config.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Using the remote Java application launch configuration</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Using the remote Java application launch configuration </h1>
-<p>The <strong>Remote Java Application </strong> launch configuration should
-  be used when debugging an application that is running on a remote VM.&nbsp;
-  Since the application is started on the remote system, the launch configuration
-  does not specify the usual information about the JRE, program arguments, or
-  VM arguments.&nbsp; Instead, information about connecting to the application
-  is supplied. </p>
-<p>To create a <strong>Remote Java Application</strong> launch configuration,
-  do the following: </p>
-<ol>
-  <li> Select <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenDebugConfigurations")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Debug Launch Configuration dialog"> <strong>Run &gt; Debug Configurations...</strong></a> from
-    the workbench menu bar (or <strong>Debug Configurations...</strong> from the drop-down menu
-    on the <strong>Debug</strong> tool bar button) to show the launch configuration
-    dialog. </li>
-  <li> Select the <strong>Remote Java Application</strong> in the list of configuration
-    types on the left. </li>
-  <li> Click the <strong>New</strong> toolbar button. A new remote launch configuration
-    is created and three tabs are shown: <strong>Connect</strong>, <strong>Source</strong>,
-    and <strong>Common</strong>. </li>
-  <li> In the <strong>Project</strong> field of the <strong>Connect</strong> tab,
-    type or browse to select the project to use as a reference for the launch
-    (for source lookup). A project does not need to be specified. </li>
-  <li> The <strong>Connection Type</strong> field of the <strong>Connect</strong> tab
-    allows you to choose how you will connect to the virtual machine. In most
-    cases, you will be attaching to the vm at a specific location, in which case
-    select <em>Standard (Socket Attach)</em>. the rest of these instructions
-    assume you have chosen this option. The <em>Standard (Socket Listen)</em> connection
-    type creates a launch that will listen for incoming connections from a remote
-    VM. You will need to specify a port that the launch will listen at.</li>
-  <li> In the <strong>Host</strong> field of the <strong>Connect</strong> tab,
-    type the IP address or domain name of the host where the Java program is
-    running.<br>
-    If the program is running on the same machine as the workbench, type <em>localhost</em>. </li>
-  <li> In the <strong>Port</strong> field of the <strong>Connect</strong> tab,
-    type the port where the remote VM is accepting connections. Generally, this
-    port is specified when the remote VM is launched. </li>
-  <li> The <strong>Allow termination of remote VM</strong> flag is a toggle that
-    determines whether the <strong>Terminate</strong> command is enabled in the
-    debugger. Select this option if you want to be able to terminate the VM to
-    which you are connecting. </li>
-  <li> Click <strong>Debug</strong>. The launch attempts to connect to a VM at
-    the specified address and port, and the result is displayed in the Debug
-    view. If the launcher is unable to connect to a VM at the specified address,
-    an error message appears. </li>
-</ol>
-<p>Specific instructions for setting up the remote VM should be obtained from
-  your VM provider.&nbsp;</p>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/cremdbug.htm">Remote Debugging</a> </p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a> </p>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-remove_line_breakpoints.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-remove_line_breakpoints.htm
deleted file mode 100644
index f8aed80..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-remove_line_breakpoints.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Removing Line Breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Removing Line Breakpoints
-    </h1>
-    <p>
-      Breakpoints can be easily removed when you no longer need them.
-    </p>
-    <ol>
-      <li>
-        In the editor area, open the file where you want to remove the breakpoint.
-      </li>
-      
-  <li> Directly to the left of the line where you want to remove the breakpoint, 
-    open the marker bar pop-up menu and select <strong>Toggle Breakpoint</strong>. 
-    The breakpoint is removed from the workbench.&nbsp; You can also double-click 
-    directly on the breakpoint icon to remove it. </li>
-    </ol>
-    Breakpoints can also be removed in the <strong><a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints View</a></strong>. Select the breakpoint(s) to be removed and from the context menu select <strong><a href="../reference/views/breakpoints/ref-remove_viewaction.htm">Remove</a></strong>.<br>
-     All breakpoints can be removed from the workbench using the <strong><a href="../reference/views/breakpoints/ref-removeall_viewaction.htm">Remove All</a></strong> action in the context menu of the <strong>Breakpoints View</strong>.
-     <p>If you find yourself frequently adding and removing a breakpoint in the
-    same place, consider disabling the breakpoint when you don't need it (using <strong><a href="../reference/views/breakpoints/ref-disable_contextaction.htm">Disable
-    Breakpoint</a> </strong>in the breakpoint context menu or the <strong>Breakpoints View</strong>)
-    and enabling it when needed again.&nbsp;&nbsp;</p>
-     <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-    <a href="../concepts/cdebugger.htm">Debugger</a><br>
-     <a href="../concepts/concept-java-perspective.htm">Java perspectives</a><br>
-     <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-    </p>
-	<p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-       <a href="task-enable_disable_breakpoints.htm">Enabling and disabling breakpoints</a><br>
-       <a href="task-apply_hit_count.htm">Applying hit counts</a><br>
-       <a href="task-catching_exceptions.htm">Catching Java exceptions</a><br>
-       <a href="task-manage_conditional_breakpoint.htm">Managing conditional breakpoints</a><br>
-       <a href="task-set_method_breakpoints.htm">Setting method breakpoints</a><br>
-       <a href="../tasks/task-stepping.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a>    </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-resuming_threads.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-resuming_threads.htm
deleted file mode 100644
index d3460f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-resuming_threads.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Resuming the execution of suspended threads
-    </title>
-  </head>
-  <body>
-    <h1>
-      Resuming the execution of suspended threads
-    </h1>
-    <p>
-      To resume the execution of a suspended threads:
-    </p>
-    <ol>
-      <li>
-        Select the thread or its stack frame in the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>.      </li>
-      <li>
-        Click the <strong><a href="../reference/views/debug/ref-resume.htm">Resume</a></strong> button [ <img src="../images/org.eclipse.debug.ui/elcl16/resume_co.png" alt="Resume"> ] in the  view toolbar (or press the <em><strong>F8</strong></em> key). </li>
-    </ol>
-    <p>The thread resumes its execution and stack
-    frames are no longer displayed for the thread.&nbsp; The <a href="../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> is also cleared.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cdebugger.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-evaluating_expressions.htm">Evaluating expressions</a><br>
-       <a href="task-stepping.htm">Stepping through the execution of a program</a><br>
-       <a href="../tasks/task-suspending_threads.htm">Suspending threads</a>
-    </p>
-  <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-    <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a>
-      <br>
-      <a href="../reference/views/debug/ref-resume.htm">Resume command</a><br>
-    <a href="../reference/views/debug/ref-suspend.htm">Suspend command</a><br>
-  <a href="../reference/views/variables/ref-variables_view.htm">Variables View</a></p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-running_and_debugging.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-running_and_debugging.htm
deleted file mode 100644
index e314d28..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-running_and_debugging.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Running and Debugging</title>
-</head>
-<body>
-<h1> Running and Debugging </h1>
-<p> You may launch your Java programs from the workbench.&nbsp; The programs may be launched in either run or debug mode. </p>
-<ul>
-  <li> In run mode, the program executes, but the execution may not be suspended or examined. </li>
-  <li> In debug mode, execution may be suspended and resumed, variables may be inspected, and expressions may be evaluated. </li>
-</ul>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-  <a href="../concepts/clocdbug.htm">Local debugging</a> </p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="../tasks/tasks-9.htm">Changing debugger launch options</a><br>
-  <a href="../tasks/task-choose_config_jre.htm">Choosing a JRE for launching a project</a><br>
-  <a href="task-create_scrapbook_page.htm">Creating a Java scrapbook page</a><br>
-  <a href="task-disconnect_remote_debug.htm">Disconnecting from a VM</a><br>
-  <a href="../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="task-preparing_to_debug.htm">Preparing to debug</a><br>
-  <a href="task-relaunch_program.htm">Re-launching a program</a><br>
-  <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-  <a href="task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-  <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-  <a href="task-stepping.htm">Stepping through the execution of a program</a><br>
-  <a href="task-suspending_threads.htm">Suspending threads</a> </p>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-  <a href="../reference/menus/run/ref-menu-run.htm">Run Menu </a><br>
-  <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-  <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug Preferences</a><br>
-  <a href="../reference/preferences/run-debug/ref-console.htm">Console Preferences</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_content_assist.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_content_assist.htm
deleted file mode 100644
index 9357748..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_content_assist.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Using code assist
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using code assist
-    </h1>
-    <p>
-      The scrapbook editor supports code assist similarly to the regular Java
-      editor.
-    </p>
-    <p>
-      For example, type&nbsp;<em>TestCase&nbsp;</em>in the scrapbook editor and press <em><strong>Ctrl+Space</strong></em>. Code assist prompts you with possible completions.    </p>
-    <img src="images/tasks-46.png"  alt="A Java editor with a content assist window at the caret position"> 
-    <p>&nbsp;</p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_error_reporting.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_error_reporting.htm
deleted file mode 100644
index 7e29b7a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-scrapbook_error_reporting.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">   
-	 <title>
-      Scrapbook error reporting
-    </title>
-  </head>
-  <body>
-    <h1>
-      Scrapbook error reporting
-    </h1>
-    <p>
-      Java scrapbook errors are reported in the scrapbook page editor.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/task-view_compilation_errors.htm">Viewing compilation errors</a><br>
-      <a href="../tasks/task-view_runtime_exceptions.htm">Viewing runtime exceptions</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-set_method_breakpoints.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-set_method_breakpoints.htm
deleted file mode 100644
index d4e45fd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-set_method_breakpoints.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Setting Method Breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Setting Method Breakpoints
-    </h1>
-    <p>
-      Method breakpoints are used when working with types that have no source
-    code (binary types).
-    </p>
-    <ol>
-      <li>
-        Open the class in the <strong>Outline View</strong>, and select the method where you want to add a method breakpoint.      </li>
-      
-      <li> From the method's pop-up menu, select <strong>Toggle Method Breakpoint</strong>. 
-  </li>
-      <li>
-        A breakpoint appears in the <a href="../reference/views/breakpoints/ref-breakpoints_view.htm"><strong>Breakpoints View</strong></a>. If source exists for the class, then a breakpoint also appears in the marker bar in the file's editor for the method that
-        was selected.      </li>
-      <li>
-        While the breakpoint is enabled, thread execution suspends when the method is entered, before any line in the method is executed.&nbsp;
-      </li>
-    </ol>
-    <p>Method breakpoints can also be setup to break on method exit.&nbsp; In the Breakpoints view, select the breakpoint and toggle the
-    <strong><a href="../reference/views/breakpoints/ref-exit_contextaction.htm">Exit</a></strong>&nbsp; item in its context menu.</p>
-    <p>Method breakpoints can be <a href="../reference/views/breakpoints/ref-remove_viewaction.htm">removed</a>, <a href="../reference/views/breakpoints/ref-enable_contextaction.htm">enabled</a>, and <a href="../reference/views/breakpoints/ref-disable_contextaction.htm">disabled</a> just like line
-    breakpoints.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-       <a href="../tasks/task-remove_line_breakpoints.htm">Removing breakpoints</a><br>
-       <a href="../tasks/task-enable_disable_breakpoints.htm">Enabling and disabling breakpoints</a><br>
-       <a href="task-apply_hit_count.htm">Applying hit counts</a><br>
-       <a href="task-catching_exceptions.htm">Catching Java exceptions</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/breakpoints/ref-breakpoints_view.htm">Breakpoints view</a><br>
-       <a href="../reference/views/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-stepping.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-stepping.htm
deleted file mode 100644
index d993757..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-stepping.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Stepping through the execution of a Java program
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Stepping through the execution of a Java program
-    </h1>
-    <p>
-      When a thread is suspended, the step controls can be used to step through the execution of the program line-by-line.
-      If a breakpoint is encountered while performing a step operation,&nbsp;
-      the execution will suspend at the breakpoint and the step operation is
-      ended.
-    </p>
-    <h2>
-      Step over
-    </h2>
-    <ol>
-      <li>
-        Select a stack frame in the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. The current line of execution in that stack frame is highlighted in the editor in the <strong>Debug Perspective</strong>.      </li>
-      <li>
-        Click the <strong><a href="../reference/views/debug/ref-stepover.htm">Step Over</a></strong> button [ <img src="../images/org.eclipse.debug.ui/elcl16/stepover_co.png" alt="Step Over"> ] in the  view toolbar, or press the <em><strong>F6</strong></em> key. The currently-selected line is executed and
-        suspends on the next executable line.      </li>
-    </ol>
-    <h2>
-      Step into
-    </h2>
-    <ol>
-      <li>
-        Select a stack frame in the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. The current line of execution in the selected frame is highlighted in the editor in the <strong>Debug Perspective</strong>.      </li>
-      
-  <li> Click the <strong><a href="../reference/views/debug/ref-stepinto.htm">Step 
-    Into</a></strong> button [ <img src="../images/org.eclipse.debug.ui/elcl16/stepinto_co.png" alt="Step Into"> 
-    ] in the view toolbar, or press the <strong><em>F5</em></strong> key. The 
-    next expression on the currently-selected line to be executed is invoked, 
-    and execution suspends at the next executable line in the method that is invoked. 
-  </li>
-    </ol>
-    
-<h2> Step into Selection</h2>
-<ol>
-  <li> Select a stack frame in the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. The current line of execution in 
-    the selected frame is highlighted in the editor in the <strong>Debug Perspective</strong>.  </li>
-  <li>In the <a href="../reference/views/ref-java-editor.htm"><strong>Java Editor</strong></a>, within the current line of execution, place the cursor 
-    on the name of a method that you would like to step into.</li>
-  <li> Click the <strong>Step into Selection </strong>action in the Run menu or 
-    Java editor context menu, or press the <em><strong>Ctrl-F5</strong></em> key. Execution resumes 
-    until the selected method is invoked. </li>
-</ol>
-    <h2>
-      Step with filters
-    </h2>
-    
-<ol>
-  <li>Toggle the <strong><a href="../reference/views/debug/ref-usestepfilters.htm">Use Step Filters</a></strong> button [ <img src="../images/org.eclipse.debug.ui/elcl16/stepbystep_co.png" alt="Use Step Filters"> ] in the Debug view toolbar, 
-    or use <em><strong>Shift+F5</strong></em>. When the action is toggled on, each of the step 
-    actions (over, into, return) will apply the set of step filters which are 
-    defined in the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaStepFilterPreferencePage)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Step Filtering preference page">
-    <strong>Java &gt; Debug &gt; Step Filtering</strong></a> preference page. When a step action is invoked, 
-    stepping will continue until an unfiltered location is reached or a breakpoint 
-    is encountered.</li>
-</ol>
-    <h2>
-      Step Return
-    </h2>
-    <ol>
-      <li>
-        Select a stack frame in the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>. The current line of execution in the selected frame is highlighted in the editor in the <strong>Debug Perspective</strong>.      </li>
-      <li>
-        Click the <strong><a href="../reference/views/debug/ref-stepreturn.htm">Step Return</a></strong> button [ <img src="../images/org.eclipse.debug.ui/elcl16/stepreturn_co.png" alt="Step Return"> ] in the  view toolbar or press the <em><strong>F7</strong></em> key. Execution resumes until the next return
-        statement in the current method is executed, and execution suspends on the next executable line.      </li>
-    </ol>
-    <h2>
-      Run to line
-    </h2>
-    <p>
-      When a thread is suspended, it is possible to resume execution until a specified line is executed. This is a convenient way to suspend execution at a line without setting a
-      breakpoint.
-    </p>
-    <ol>
-      <li>
-        Place your cursor on the line at which you want the program to run.      </li>
-      <li>
-        Select the <strong>Run to Line</strong> command [ <img src="../images/org.eclipse.debug.ui/elcl16/runtoline_co.png" alt="Run To Line"> ] from the pop-up menu or use
-        <em><strong>Ctrl+R</strong></em>. Program execution is resumed and suspends just before the specified line is to be executed.      </li>
-    </ol>
-    <p>It is possible that the line will never be hit and that the program will not suspend.&nbsp;</p>
-    <p> Breakpoints and exceptions can cause the thread to suspend before reaching the specified
-        line.</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cbrkpnts.htm">Breakpoints</a><br>
-       <a href="../concepts/concept-java-perspective.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-       <a href="../tasks/task-add_line_breakpoints.htm">Adding breakpoints</a><br>
-       <a href="../tasks/task-launching_java_program.htm">Launching a Java program</a><br>
-       <a href="../tasks/task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-       <a href="../tasks/task-running_and_debugging.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="../tasks/task-suspending_threads.htm">Suspending threads</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a>    </p>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-suspending_threads.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-suspending_threads.htm
deleted file mode 100644
index dd6042f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-suspending_threads.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Suspending Threads
-    </title>
-  </head>
-  <body>
-    <h1>
-      Suspending Threads
-    </h1>
-    <p>
-      To suspend an executing thread:
-    </p>
-    <ol>
-      <li>
-        Select the thread in the <a href="../reference/views/debug/ref-debug_view.htm"><strong>Debug View</strong></a>.      </li>
-      <li>
-      Click the <strong><a href="../reference/views/debug/ref-suspend.htm">Suspend</a></strong> button  [ <img src="../images/org.eclipse.debug.ui/elcl16/suspend_co.png" alt="Suspend"> ]  in the  view toolbar.</li>
-    </ol>
-    <p>The thread suspends its execution. The current call stack for the thread is
-    displayed, and the current line of execution is highlighted in the editor in the <strong>Debug Perspective</strong>. </p>
-    <p>
-      When a thread suspends, the top stack frame of the thread is automatically
-      selected.&nbsp; The <a href="../reference/views/variables/ref-variables_view.htm"><strong>Variables View</strong></a> shows the stack frame's variables and
-      their values.&nbsp; Complex variables can be further examined by expanding
-      them to show the values of their members.    </p>
-    <p>
-      When a thread is suspended and the cursor is hovered over a variable in the Java editor, the value of that variable is displayed.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/cdebugger.htm">Debugger</a><br>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-       <a href="../concepts/concept-java-perspective.htm">Java perspectives</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-catching_exceptions.htm">Catching Java exceptions</a><br>
-       <a href="task-evaluating_expressions.htm">Evaluating expressions</a><br>
-       <a href="task-resuming_threads.htm">Resuming the execution of suspended threads</a><br>
-       <a href="task-stepping.htm">Stepping through the execution of a program</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-      <a href="../reference/views/debug/ref-resume.htm">Resume command</a> <br>
-      <a href="../reference/views/debug/ref-suspend.htm">Suspend command</a> <br>
-       <a href="../reference/views/variables/ref-variables_view.htm">Variables view</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-view_compilation_errors.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-view_compilation_errors.htm
deleted file mode 100644
index ac6c503..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-view_compilation_errors.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing compilation errors
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing compilation errors
-    </h1>
-    <p>
-      If you try to evaluate an expression containing a compilation error, it
-      will be reported in the scrapbook editor.
-    </p>
-    <p>
-      For example, type and select the (invalid) expression <code>System.println(&quot;hi&quot;)</code> in the editor and click <strong>Execute</strong> in the toolbar.
-    </p>
-    <p>
-      The error message <em>The method println(java.lang.String) is undefined for the type java.lang.System</em> appears in the editor at the point of the error.
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/task-view_runtime_exceptions.htm b/bundles/org.eclipse.jdt.doc.user/tasks/task-view_runtime_exceptions.htm
deleted file mode 100644
index 226b310..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/task-view_runtime_exceptions.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Viewing runtime exceptions
-    </title>
-  </head>
-  <body>
-    <h1>
-      Viewing runtime exceptions
-    </h1>
-    <p>
-      If an expression you evaluate causes a runtime exception, the exception will be reported in the editor. For example:
-    </p>
-    <p>
-      Type and select the expression <code>Object x = null; x.toString()</code> in the editor and click <strong>Display</strong> in the toolbar.
-    </p>
-    <p>
-      The error message:
-    </p>
-    <p>
-      <em>An exception occurred during evaluation: java.lang.NullPointerException</em>
-    </p>
-    <p>
-      will be displayed in the editor.
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-display_evaluation_result.htm">Displaying the result of evaluating an expression</a><br>
-       <a href="task-inspect_evaluation_result.htm">Inspecting the result of evaluating an expression</a><br>
-       <a href="task-executing_an_expression.htm">Executing an expression</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm
deleted file mode 100644
index c555f95..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-188.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Finding Strings to Externalize</title>
-  </head>
-
-  <body>
-    <h1>Finding Strings to Externalize</h1>
-
-    <p>To find strings to externalize:</p>
-
-    
-<ul>
-  <li>In a Java view (e.g. Package Explorer), select a set of packages, source 
-    folders or projects.</li>
-  <li>From the menu bar, select <span class="control">Source &gt; Externalize Strings...</span></li>
-  <li>A dialog comes up with a list of all compilation units that have some non-externalized 
-    strings</li>
-  <li>In the dialog, you can double click on a listed compilation unit or press 
-    the <b>Externalize</b> button to open the <a href="../reference/ref-wizard-externalize-strings.htm">Externalize Strings wizard</a></li>
-</ul>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concept-string-externalization.htm">String externalization</a></p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-202.htm">Finding unused and incorrectly used keys in property files</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize strings wizard</a><br>
-     <a href="../reference/ref-menu-source.htm">Source menu</a></p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm
deleted file mode 100644
index 7e6153c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-202.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>Finding Unused and Incorrectly Used Keys in Property Files</title>
-  </head>
-
-  <body>
-    <h1>Finding Unused and Incorrectly Used Keys in Property Files</h1>
-
-    <p>Finding unused and incorrectly used keys in a property file:</p>
-
-    <ul>
-      <li>in a Java view (e.g. Package Explorer), select a set of packages, source folders, projects, message property files, or
-      resource bundle accessor classes</li>
-      <li>from the menu bar, select <span class="control">Source &gt; Find Broken Externalized Strings</span></li>
-    </ul>
-
-    <p>After the search is finished, the Search Result view displays a list of unused keys in the propertie files and all incorrect references to non-existing keys.</p>
-
-    <p><img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-     <a href="../concepts/concept-string-externalization.htm">String externalization</a><br>
-    </p>
-
-    <p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-     <a href="tasks-206.htm">Externalizing strings</a><br>
-     <a href="tasks-188.htm">Finding strings to externalize</a></p>
-
-    <p><img src="../images/ngrelr.png" alt="Related reference" border="0" ><br>
-     <a href="../reference/ref-wizard-externalize-strings.htm">Externalize strings wizard</a><br>
-     <a href="../reference/ref-menu-source.htm">Source menu</a><br>
-    </p>
-
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm
deleted file mode 100644
index 8819436..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-206.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-
-    <title>Externalizing Strings</title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-
-  <body>
-    <h1>Externalizing Strings</h1>
-    
-    <h3>Contents</h3>
-    <a href="tasks-188.htm">Finding strings to externalize</a><br>
-    <a href="tasks-202.htm">Finding unused and incorrectly used keys in property files</a>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm
deleted file mode 100644
index 5ee55d2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-230.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Using the Formatter Application
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Using the Formatter Application
-    </h1>
-    <p>
- 	The JDT has a command line Eclipse application that allows users to format Java source code either with 
- 	the Eclipse default code formatter options or with custom options.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-231.htm">Running the formatter application</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/preferences/java/codestyle/ref-preferences-formatter.htm">Code Formatter</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm
deleted file mode 100644
index 2d01d58..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-231.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Running the Formatter Application
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Running the Formatter Application
-    </h1>
-    <p>
-    Running the formatter application is as simple as running the org.eclipse.jdt.core.JavaCodeFormatter application from the commandline:</p>
-    <pre>
-    eclipse -vm &lt;path to virtual machine&gt; -application org.eclipse.jdt.core.JavaCodeFormatter [ OPTIONS ] &lt;files&gt;
-    </pre>
-    <table border="1" cellspacing="0" cellpadding="5" width="600" summary="">
-      <tr>
-        <td width="25%">&lt;files&gt;</td> 
-        <td>Java source files and/or directories to format. Only files ending with .java will be formatted in the given directory.</td>
-      </tr>
-    </table>
-    <table border="1" cellspacing="0" cellpadding="5" width="600" summary="">
-    	<thead>
-		<tr>
-			<th><p>OPTIONS</p></th>
-			<th><p>Description</p></th>
-		</tr>
-	    </thead>
-	    <tbody>
-		<tr>
-			<td valign="top" width="25%"><p>-config &lt;file&gt;</p></td>
-			<td valign="top"><p>Use the formatting style from the specified properties file. 
-			                    Refer to <a href="tasks-232.htm">Generating a config file for the formatter application</a>
-			                    for details.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%"><p>-help</p></td>
-			<td valign="top"><p>Display the help message.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%"><p>-quiet</p></td>
-			<td valign="top"><p>Only print error messages.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" width="25%"><p>-verbose</p></td>
-			<td valign="top"><p>Be verbose about the formatting job.</p>
-			</td>
-		</tr>
-		</tbody>
-	</table>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/preferences/java/codestyle/ref-preferences-formatter.htm">Code formatter</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm
deleted file mode 100644
index 95ed735..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-232.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) Red Hat Incorporated 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Generating a Config File for the Formatter Application
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Generating a Config File for the Formatter Application
-    </h1>
-    <p>
-    Generating a config file for the formatter application involves modifying the code formatter settings
-    for a Java project and copying org.eclipse.jdt.core.prefs out of the .settings directory for that project.
-    </p>
-    <ol>
-      <li>
-        Select a Java project, open the pop-up menu and choose <strong>Properties</strong>.
-      </li>
-
-      <li>
-        Select the <strong>Java Code Style &gt; Formatter</strong> page and check <strong>Enable project specific settings</strong>.
-      </li>
-      <li>
-        Select or edit a profile as explained above.
-      </li>
-
-      <li>
-        Click <strong>OK</strong> when you are done.
-      </li>
-      
-      <li>
-        Use either a file manager or the command line to copy <b><code>workspace/YourJavaProject/.settings/org.eclipse.jdt.core.prefs</code></b>
-        to a new location.
-      </li>
-      <li>
-        If the files you want to format are using 1.5 constructs, you must add the following lines inside the preference file you just created:
-        <blockquote><code>
-        	org.eclipse.jdt.core.compiler.compliance=1.5<br>
-		org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.5<br>
-		org.eclipse.jdt.core.compiler.source=1.5<br>
-		</code>
-        </blockquote>
-       </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/preferences/java/codestyle/ref-preferences-formatter.htm">Code formatter</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm
deleted file mode 100644
index 824bd3a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-32.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-	   Creating JAR Files
-    </title>
-  </head>
-  <body>
-    <h1>
-      Creating JAR Files
-    </h1>
-    <p>
-      You can create and regenerate JAR files in the workbench.
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-36.htm">Regenerating a JAR file</a><a href="tasks-36.htm"></a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm
deleted file mode 100644
index d74825a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-33.htm
+++ /dev/null

@@ -1,88 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Creating a New JAR File
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Creating a New JAR File
-    </h1>
-    <p>
-      To create a new JAR file in the workbench:
-    </p>
-    <ol>
-      <li>
-        In the Package Explorer, you can optionally pre-select one or more Java elements to export.
-        (These will be automatically selected in the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.jdt.internal.ui.jarpackager.JarPackageWizard)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the JAR export wizard">
-        <strong>JAR Package Specification</strong></a> wizard
-        page, described in Step 4.)
-      </li>
-      <li>
-        Either from the context menu or from the menu bar's <strong>File</strong> menu, select <strong>Export</strong>.
-      </li>
-      <li>
-        Expand the <strong>Java</strong> node and select <strong>JAR file</strong>. Click&nbsp;<strong>Next</strong>.
-      </li>
-      <li>
-        In the <strong>JAR File Specification</strong> page, select the resources that you want to export in the <strong>Select the resources to
-        export&nbsp;</strong>field.
-      </li>
-      <li>
-        Select the appropriate checkbox to specify whether you want to <strong>Export generated class files and resources</strong> or <strong>Export Java source files and
-        resources</strong>. <strong>Note</strong>: Selected resources are exported in both cases.
-      </li>
-      <li>
-        In the&nbsp;<strong>Select the export destination</strong> field, either type or click&nbsp;<strong>Browse</strong> to select a location
-        for the JAR file.
-      </li>
-      <li>
-        Select or clear the&nbsp;<strong>Compress the contents of the JAR file</strong> checkbox.
-      </li>
-      <li>
-        Select or clear the&nbsp;<strong>Overwrite existing files without warning</strong> checkbox. If you clear this checkbox,&nbsp;then you will be prompted
-        to confirm the replacement of each file that will be overwritten.
-      </li>
-      <li>
-        <strong>Note</strong>: The overwrite option is applied when writing the JAR file, the JAR description, and the manifest file.
-      </li>
-      <li>
-        You have two options:
-        <ul>
-          <li>
-            Click&nbsp;<strong>Finish</strong> to create the JAR file immediately.
-          </li>
-          <li>
-            Click&nbsp;<strong>Next</strong> to use the JAR Packaging Options page to <a href="tasks-34.htm">set advanced options</a>, create a JAR description, or <a href="tasks-35.htm">change the default
-            manifest</a>.
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>
-       <a href="tasks-34.htm">Setting advanced options</a><br>
-       <a href="tasks-35.htm">Defining the JAR file's manifest</a><br>
-       <a href="tasks-36.htm">Regenerating a JAR file</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm
deleted file mode 100644
index 17d5761..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-34.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Setting Advanced Options
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Setting Advanced Options
-    </h1>
-    <ol>
-      <li>
-        Follow the procedure for <a href="tasks-33.htm">creating a JAR file</a>, but click <strong>Next</strong> in the last step to go to the JAR Packaging Options page.
-      </li>
-      <li>
-        If you want to save the JAR file description, select the <strong>Save the description of this JAR in the workspace</strong> checkbox. A JAR file description can be used to
-        <a href="tasks-36.htm">regenerate a JAR file</a> without using the wizard.
-      </li>
-      <li>
-        The compiler is able to generate CLASS files even when source contains errors. You have the option to exclude CLASS (but not source) files with compile errors. These files
-        will be reported at the end, if reporting is enabled.
-      </li>
-      <li>
-        You can choose to exclude CLASS (but not source) files that have compile warnings. These files will be reported at the end.<br>
-         <strong>Note</strong>: This option does not automatically exclude class files with compile errors.
-      </li>
-      <li>
-        You can choose to include the source folder path by selecting the <strong>Create source folder structure</strong> checkbox.
-      </li>
-      <li>
-        Select the <strong>Build projects if not built automatically</strong> checkbox if you want the export to perform a build before creating the JAR file.
-      </li>
-      <li>
-        Click <strong>Finish</strong> to create the JAR file immediately or <strong>Next</strong> if you want to <a href="tasks-35.htm">change the default manifest</a>.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p>
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-35.htm">Defining the JAR file's manifest</a><br>
-       <a href="tasks-36.htm">Regenerating a JAR file</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>	  
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm
deleted file mode 100644
index b763247..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-35.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Defining the JAR File's Manifest
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Defining the JAR File's Manifest
-    </h1>
-    <p>
-      You can either define the important parts of the JAR file manifest directly in the wizard or choose to use a manifest file that already exists in your workbench.
-    </p>
-    <h2>
-      Creating a new manifest
-    </h2>
-    <ol>
-      <li>
-        Follow the procedure for <a href="tasks-33.htm">creating a JAR file</a>, but click&nbsp;<strong>Next</strong> in the last step to go to the JAR Packaging Options page.
-      </li>
-      <li>
-        Set any <a href="tasks-34.htm">advanced options</a> that you want to set, and then click&nbsp;<strong>Next</strong> again to go to the JAR Manifest Specification page.
-      </li>
-      <li>
-        If it is not already selected, click the&nbsp;<strong>Generate the manifest file</strong> button.
-      </li>
-      <li>
-        You can now choose to save the manifest in the workbench. This will save the manifest for later use. Click&nbsp;<strong>Save the manifest in the workspace</strong>, then
-        click&nbsp;<strong>Browse</strong> next to the&nbsp;<strong>Manifest file</strong> field to specify a path and file name for the
-        manifest.
-      </li>
-      <li>
-        If you decided to save the manifest file in the previous step and you chose to save the JAR description on the previous wizard page, then you can choose to reuse it in the
-        JAR description (by selecting the <strong>Reuse and save the manifest in the workspace</strong> checkbox). This means that the saved file will be used when the JAR file is
-        recreated from the JAR description.This option is useful if you want to modify or replace the manifest file before recreating the JAR file from the description.
-      </li>
-      <li>
-        You can choose to seal the JAR and optionally exclude some packages from being sealed or specify a list with sealed packages. By default, nothing is sealed.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Browse</strong> button next to the&nbsp;<strong>Main class</strong> field to specify the entry point for your
-        applications.<br>
-         <strong>Note</strong>: If your class is not in the list, then you forgot to select it at the beginning.
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong>. This will create the JAR, and optionally a JAR description and a manifest file.
-      </li>
-    </ol>
-    <h2>
-      Using an existing manifest
-    </h2>
-    You can use an existing manifest file that already exists in your workbench. 
-    <ol>
-      <li>
-        Follow the procedure for creating a JAR file, but click&nbsp;<strong>Next</strong> in the last step to go to the JAR Packaging Options page.
-      </li>
-      <li>
-        Set any advanced options that you want to set, and the click&nbsp;<strong>Next</strong> again to go to the JAR Manifest Specification page.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Use existing manifest from workspace</strong> radio button.
-      </li>
-      <li>
-        Click the&nbsp;<strong>Browse</strong> button to choose a manifest file from the workbench.
-      </li>
-      <li>
-        Click&nbsp;<strong>Finish</strong>. This will create the JAR and optionally a JAR description.
-      </li>
-    </ol>
-    <p>
-    <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-	</p>
-	<p> 
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-34.htm">Setting advanced options</a><br>
-       <a href="tasks-36.htm">Regenerating a JAR file</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-	</p>
-	<p>
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm
deleted file mode 100644
index d520ec5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-36.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Regenerating a JAR File
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Regenerating a JAR File
-    </h1>
-    <p>
-      You can use a JAR file description to regenerate a previously created JAR file.
-    </p>
-    <ol>
-      <li>
-        Select one or more JAR file descriptions in your workbench.
-      </li>
-      <li>
-        From the selection's pop-up menu, select&nbsp;<strong>Create JAR</strong>. The JAR file(s) are regenerated.
-      </li>
-    </ol>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-33.htm">Creating a new JAR file</a><br>
-       <a href="tasks-35.htm">Defining the JAR file's manifest</a><br>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/ref-export-jar.htm">JAR file exporter</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm
deleted file mode 100644
index 31de9ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-62.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Using the Local History
-    </title>
-  </head>
-  <body>
-    <h1>
-      Using the Local History
-    </h1>
-    <p>
-      The JDT extends the workbench concept of a local history in three ways:
-    </p>
-    <ul>
-      <li>
-        A file can be replaced with an edition from the local history in the Package Explorer view.
-      </li>
-      <li>
-        The JDT allows you to compare and/or replace individual Java elements (types and their members) with editions from the local history.
-      </li>
-      <li>
-        The JDT allows you to restore Java elements (and files) deleted from the workbench that have been kept in the local history.
-      </li>
-    </ul>
-    <p>
-      Note: Files and Java elements such as types and their members change in time. A 'snapshot' of what they look like a point in time (as saved in the local
-      history) is called an edition.
-    </p>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      	<a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a><br>
-       	<a href="../concepts/concept-java-views.htm">Java views</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-63.htm">Replacing a Java element with a local history edition</a><br>
-      <a href="tasks-63a.htm">Comparing a Java element with a local history edition</a><br>
-      <a href="tasks-64.htm">Restoring a deleted workbench element</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a>
-     </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm
deleted file mode 100644
index 6f8e64c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Replacing a Java Element With a Local History Edition
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Replacing a Java Element With a Local History Edition
-    </h1>
-    <ol>
-      <li>
-        Make sure that a Java view is visible.
-      </li>
-      <li>
-        Open a Java editor for the Java file in which you want to replace a Java element with an edition from the local history.
-      </li>
-      <li>
-        Activate the editor by clicking its tab in the editor area. The Outline view also displays the Java file.
-        <em>Note: The Package Explorer can be configured to show or not show
-        Java elements in files. Use the
-        <strong>Show Members in Package Explorer</strong> checkbox on the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-        <strong>Java &gt; Appearance</strong></a> preference page to set your preference.</em>
-      </li>
-      <li>
-        Select the element that you want to replace in the Outline or the Package Explorer.
-      </li>
-      <li>
-        From the element's pop-up menu, select <strong>Replace With &gt; Element from Local History</strong>.
-      </li>
-      <li>
-        In the upper pane of the resulting dialog, all available editions of the selected element in the local history are displayed.
-      </li>
-      <li>
-        Select an edition in the upper pane to view the differences between the selected edition and the edition in the workbench.
-      </li>
-      <li>
-        When you have identified the edition with which you want to replace the existing Java element, click <strong>Replace</strong>.
-      </li>
-      <li>
-        The local history edition replaces the current one in the editor. <em>Note: The changed compilation unit has not yet been saved at this point.</em>
-      </li>
-    </ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-62.htm">Using the local history</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/views/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm
deleted file mode 100644
index 72c7679..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-63a.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Comparing a Java Element With a Local History Edition
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Comparing a Java Element With a Local History Edition
-    </h1>
-    <ol>
-      <li>
-        Make sure that a Java view is visible.
-      </li>
-      <li>
-        Open a Java editor for the Java file in which you want to compare a Java element with an edition from the local history.
-      </li>
-      <li>
-        Activate the editor by clicking its tab in the editor area. The Outline view also displays the Java file.
-        <em>Note: The Package Explorer can be configured to show or not show
-        Java elements in files. Use the
-        <strong>Show Members in Package Explorer</strong> checkbox on the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-        <strong>Java &gt; Appearance</strong></a> preference page to set your preference.</em>
-      </li>
-      <li>
-        Select the element that you want to compare in the Outline or the Package Explorer.
-      </li>
-      <li>
-        From the element's pop-up menu, select <strong>Compare With &gt; Element from Local History</strong>.
-      </li>
-      <li>
-        The <strong>History</strong> view opens and shows all editions of the selected element available in the local history.
-      </li>
-      <li>
-        Select an edition in the hitory view to see the differences between the selected edition and the edition in the workbench in a comparison editor.
-      </li>
-      <li>
-        If you are done with the comparison, click close the comparison editor.
-      </li>
-    </ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-62.htm">Using the local history</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/views/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm
deleted file mode 100644
index b72c874..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-64.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Restoring a Deleted Workbench Element
-    </title>
-  </head>
-  <body>
-    <h1>
-      Restoring a Deleted Workbench Element
-    </h1>
-    <ol>
-      <li>
-        Ensure that a Java view that show Java elements inside files (such as the Outline view) is visible.
-      </li>
-      <li>
-        Open the compilation unit to which you want to add a previously removed Java element from the local history.
-      </li>
-      <li>
-        Activate the editor by clicking its tab in the editor area, and the Java view shows the content of the Java file.
-      </li>
-      <li>
-        In the Java view, select the element to whose container type you want to restore the deleted element.
-      </li>
-      <li>
-        From the type's pop-up menu in the Java view, select <strong>Restore from Local History</strong>.
-      </li>
-      <li>
-        In the upper left pane of the resulting dialog, all available editions of the selected element in the local history are displayed.
-      </li>
-      <li>
-        In the left pane check all elements that you want to replace.
-      </li>
-      <li>
-      	For every checked element select an edition in the right hand pane and view its content in the bottom pane.
-      </li>
-      <li>
-        When you have identified the edition that you want to restore, press <strong>Restore</strong>.
-        The local history editions are loaded into the editor.
-      </li>
-    </ol>
-    <p>
-      <img  src="../images/ngrelc.png" alt="Related concepts" border="0">
-    </p>
-    <p>
-      <a href="../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelt.png" alt="Related tasks">
-    </p>
-    <p>
-      <a href="tasks-62.htm">Using the local history</a>
-    </p>
-    <p>
-      <img border="0"  src="../images/ngrelr.png" alt="Related reference">
-    </p>
-    <p>
-      <a href="../reference/views/ref-view-outline.htm">Java outline</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm
deleted file mode 100644
index 757cca2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-72.htm
+++ /dev/null

@@ -1,19 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Navigating the JDT Workbench
-    </title>
-  </head>
-  <body>
-    <h1>
-      Navigating the JDT Workbench
-    </h1>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm
deleted file mode 100644
index 33bcedf..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-73.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Opening an Editor for a Selected Element
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening an Editor for a Selected Element
-    </h1>
-    <p>
-      You can select the name of a type, method, or field in the Java source editor or in the scrapbook and open an editor on the definition of the element.
-    </p>
-    <ol>
-      <li>
-        In the Java editor, select the name of a type, method, or field. You can also just click into the name once.
-      </li>
-      <li>
-        Do one of the following: 
-        <ul>
-          <li>
-            From the menu bar, select <strong>Navigate</strong> &gt; <strong>Open Declaration</strong>
-          </li>
-          <li>
-            From the editor's pop-up menu, select <strong>Open Declaration</strong>
-          </li>
-          <li>
-            Press <strong>F3</strong>
-          </li>
-        </ul>
-      </li>
-    </ol>
-    <p>
-      or
-    </p>
-    <ol>
-      <li>
-        Hold down the <strong>Ctrl</strong> key.
-      </li>
-      <li>
-        In the Java editor, move the mouse over the name of a type, method, or field until the name becomes underlined.
-      </li>
-      <li>
-        Click the hyperlink once.
-      </li>
-    </ol>
-    
-    <p>
-      If there are multiple definitions of the same name, a dialog is shown, and you can select one definition that you want to open. 
-      An editor opens containing the selected element.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-navigate.htm">Navigate menu</a><br>
-       <a href="../reference/views/ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm
deleted file mode 100644
index 7f52089..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-74.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Showing an Element in the Package Explorer View
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Showing an Element in the Package Explorer View
-    </h1>
-    <p>
-      You can reveal an element's location in the Package Explorer view
-    </p>
-    
-    <ul>
-      <li>
-        <ol>
-          <li>
-            Select a Java element or activate a Java editor.
-          </li>
-          <li>
-            From the menu bar, select <strong>Navigate</strong> &gt; <strong>Show In</strong> &gt; <strong>Package Explorer</strong>.
-            If the Package Explorer is not already open, then it opens in the
-            current perspective. The workbench navigates to the selected element (or the edited compilation unit).
-          </li>
-        </ol>
-      </li>
-      <li>
-        From the Java editor's pop-up menu, select 
-        <strong>Show In &gt; Package Explorer</strong>. The currently edited compilation unit will be revealed.
-      </li>
-    </ul>
-    <p>
-      <strong>Note:</strong> The element might not be revealed if Package Explorer filters are active or the
-      <strong>Show Members in Package Explorer</strong> preference is cleared on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-      <strong>Java &gt; Appearance</strong></a> preference page.
-    </p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-views.htm">Java views</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-executionArgs.htm">Setting execution arguments</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/preferences/ref-preferences-java.htm">Java preference page</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm
deleted file mode 100644
index bd37823..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-75.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Opening a Type in the Package Explorer View
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a Type in the Package Explorer View
-    </h1>
-    <p>
-      You can open the Package Explorer on any type that is included on a project's class path.
-    </p>
-    <ol>
-		<li>
-			From the menu bar, select <strong>Navigate &gt; Go To &gt; Type.</strong> The Go to Type dialog opens.
-		</li>
-		<li>
-			In the <strong>Choose a type</strong> field, begin typing an expression to narrow the list of available types, using wildcards as needed. As you
-      		type, the list is filtered to display only types that match the current expression.
-      	</li>
-		<li>
-			In the <strong>Matching items</strong> list, select a type. Hint: you can press the <Strong>Down</strong> key to move to the first type.
-		</li>
-		<li>
-			Click <strong>OK</strong> when you are done. The selected type is displayed in the Package Explorer.
-    	</li>
-    </ol>
-	
-	<p>
-	  <strong>Note:</strong> The Goto Type dialog maintains a history of recently opened types.
-	  These are shown when the dialog is opened and stay above a separator line when you start to type a filter expression.
-	</p>
-	
-	<p>
-		<strong>Note:</strong> Revealing may not be possible if Package Explorer filters are applied.
-	</p>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-      <a href="tasks-74.htm">Showing a type's compilation unit in the Package Explorer</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm
deleted file mode 100644
index 93944d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-76.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Opening an Editor on a Type
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening an Editor on a Type
-    </h1>
-    <p>
-      You can open an editor on any type in the workbench.
-    </p>
-    <ol>
-		<li>
-			Press <strong>Ctrl+Shift+T</strong> or, select <strong>Navigate</strong> &gt; <strong>Open Type</strong> from the menu bar. The Open Type dialog opens.
-		</li>
-		<li>
-			In the <strong>Enter type name prefix or pattern</strong> field, begin typing an expression to narrow the list of available types, using wildcards as needed. As you
-			type, the list is filtered to display only types that match the current expression. CamelCase notation is also supported; that means you aonly need to enter the capital letters
-			of the type name.
-		</li>
-		<li>
-			In the <strong>Matching items</strong> list, select a type. Hint: you can press the <Strong>Down</strong> key to move to the first type.
-		</li>
-		<li>
-			Click <strong>OK</strong> when you are done. An editor opens on the selected type.
-		</li>
-	</ol>
-	
-	<p>
-	  <strong>Note:</strong> The Open Type dialog maintains a history of recently opened types.
-	  These are shown when the dialog is opened and stay above a separator line when you start to type a filter expression.
-	</p>
-	
-    <p>
-      <strong>Note:</strong> If you open a type from a CLASS or JAR file, you will see a special editor showing only method signatures unless you have attached source to it.
-    </p>
-    
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-editor.htm">Java editor</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-    </p>
-    <p>
-       <a href="tasks-73.htm">Opening an editor for a selected element</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-      <a href="../reference/ref-dialog-open-type.htm">Open type dialog</a><br>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a><br>
-      <a href="../reference/views/ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm
deleted file mode 100644
index 0183bf4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-77.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <title>
-      Opening a Package
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Opening a Package
-    </h1>
-    <p>
-      To reveal a package in the tree of the Package Explorer:
-    </p>
-    <ol>
-		<li>
-			Select <strong>Navigate</strong> &gt; <strong>Go To</strong> &gt; <strong>Package</strong> from the menu bar. The Go to Package dialog opens.
-		</li>
-		<li>
-			Type a package name in the <strong>Choose a package</strong> field to narrow the list of available packages, using wildcards as needed. As you type,
-			the list is filtered to display only packages that match the current expression.
-		</li>
-		<li>
-			Select a package from the list, then click <strong>OK</strong>. The selected package is displayed in the Package Explorer.
-		</li>
-	</ol>
-    <p>
-      <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-    </p>
-    <p>
-      <a href="../concepts/concept-java-views.htm">Java views</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" ><a href="../reference/ref-menu-navigate.htm"></a>
-    </p>
-    <p>
-      <a href="../reference/ref-menu-navigate.htm">Navigate actions</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package explorer</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm
deleted file mode 100644
index 54d39d0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-9.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Changing the active perspective when launching</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Changing the active perspective when launching </h1>
-You can control which perspective becomes active when a program is launched 
-and when it suspends. The setting is configurable for each launch configuration 
-type, for each of the launch modes it supports.
-<p>To activate a particular perspective when a program is launched, do the following:</p>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.PerspectivePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Run/Debug Perspectives preference page"> <strong>Run/Debug &gt; Perspectives</strong></a> preference page. </li>
-  <li>Select the <strong>Always</strong> option for the <strong>Open the associated 
-    perspective when launching</strong> preference. This will cause the perspective 
-    associated with a program to become active whenever it is launched.</li>
-</ol>
-<p>To activate a particular perspective when a program is suspends, do the following:</p>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.PerspectivePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Run/Debug Perspectives preference page"> <strong>Run/Debug &gt; Perspectives</strong></a> preference page. </li>
-  <li> Select the <strong>Always</strong> option for the <strong>Open the associated 
-    perspective when an application suspends</strong> preference.&nbsp; This will 
-    cause the perspective associated with a program to become active whenever 
-    a program suspends.</li>
-</ol>
-<p>To associate a particular perspective with a program, do the following:</p>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.PerspectivePreferencePage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Run/Debug Perspectives preference page"> <strong>Run/Debug &gt; Perspectives</strong></a> preference page. </li>
-  <li>Select the type of application that you would like to 
-    associate a perspective with (for example, <strong>Java Application</strong>). </li>
-  <li>For each launch mode, select the desired perspective using the combo box.&nbsp;This 
-    will cause the perspective you choose to become active based on your preference 
-    settings (i.e. when a program is launched and/or when it suspends).</li>
-</ol>
-<p>If the specified perspective is not open at the time it needs to be activated, 
-  that perspective is created.&nbsp;</p>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/cremdbug.htm">Remote debugging</a><br>
-  <a href="../concepts/clocdbug.htm">Local debugging</a><br>
-  <a href="../concepts/concept-java-perspective.htm">Java perspectives</a> </p>
-<p> <img border="0" src="../images/ngrelt.png" alt="Related tasks" > <br>
-  <a href="task-running_and_debugging.htm">Running and debugging</a><br>
-  <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-  <a href="task-launching_java_program.htm">Launching a Java program</a><br>
-</p>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../reference/views/console/ref-console_view.htm">Console view</a><br>
-  <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-  <a href="../reference/menus/run/ref-menu-run.htm">Run Menu</a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm
deleted file mode 100644
index 1719d70..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-JREs.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Working with JREs
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-  </head>
-  <body>
-    <h1>
-      Working with JREs
-    </h1>
-    <p>
-      You can <a href="../tasks/task-add_new_jre.htm">install</a> as many different Java Runtime Environments (JREs) as you like. 
-      JREs are used to run and debug java programs.  Your JREs are managed on the
-      <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs</a> preference page.
-    </p>
-      
-    <p>
-      A JRE definition consists of:</p>
-      <ul>
-		  <li> The type of the JRE (e.g. Standard VM or Standard 1.x.x VM) </li>
-		  <li> A name </li>
-		  <li> The location where the JRE is installed </li>
-		  <li> The system libraries containing the Java system classes (like java.lang.Object). 
-		    Optionally, the system libraries can be associated with the source file containing 
-		    the source for the classes in the JRE's CLASS files and a javadoc location 
-		    (URL). </li>
-		  <li>Other information needed by the VM to build, run and debug applications.</li>
-	  </ul>
-	<p>You can <a href="../tasks/task-assign_default_jre.htm">switch</a> the default JRE for the workbench. 
-	The default JRE is used by default when building, running, and debugging applications.  Alternatively, 
-	projects may <a href="../tasks/task-choose_config_jre.htm">specify</a> a specific JRE that they should 
-	be built and run with.</p>
-  
-	<p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-     </p>
-    <p>     
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0">
-    </p>
-    <p>
-      <a href="../tasks/task-add_new_jre.htm">Adding a new JRE definition</a><br>
-     <a href="tasks-deleteJRE.htm">Deleting a JRE definition</a><br>
-      <a href="../tasks/task-assign_default_jre.htm">Choosing a default JRE</a><br>
-      <a href="../tasks/task-choose_config_jre.htm">Choosing a JRE for launching a project</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm
deleted file mode 100644
index 9ca44a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-consoleAppearance.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Changing the appearance of the console view
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Changing the appearance of the console view
-    </h1>
-    <p>
-      To set the types of output (and their colors) in the Console view:
-    </p>
-    <ol>
-      <li>
-        Open the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ConsolePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page">
-        <strong>Run/Debug &gt; Console</strong></a> preference page.
-      </li>
-      <li>
-        Checking the <strong>Show when program writes to standard out</strong> 
-        checkbox will make the Console view visible each
-        time new output is written to the console from the program's standard output stream. If there is no Console view in the current perspective, one will be created.
-      </li>
-      <li>
-        Checking the <strong>Show when program writes to standard err</strong> 
-        checkbox will make the Console view visible each
-        time new output is written to the console from the program's standard error stream. If there is no Console view in the current perspective, one will be created.
-      </li>
-      <li>
-        Click any of the color buttons to change the color for the corresponding
-        text stream.&nbsp;&nbsp;
-      </li>
-    </ol>
-    <p>To set the fonts used in the Console view:</p>
-    <ol>
-      <li>
-        Open the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Color and Fonts preference page">
-        <strong>General &gt; Appearance &gt; Colors and Fonts</strong></a> preference page.      </li>
-      <li>
-        Select <strong>Console font</strong> from the <strong>Debug</strong> category
-        and use the <strong>Change... </strong>button to change the font.&nbsp;
-        (The <strong>Detail Pane Text Font</strong> can be used to change the
-        font of the debugger's default <a href="../reference/views/shared/ref-detailpane.htm"><strong>Detail Pane</strong></a>).      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-    </p>
-    <p>
-      <a href="../concepts/cdebugger.htm">Debugger</a><br>
-       <a href="../concepts/concept-java-views.htm">Java views</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" >
-    </p>
-    <p>
-      <a href="../reference/views/console/ref-console_view.htm">Console view</a><br>
-       <a href="../reference/views/ref-viewsandeditors.htm">Views and editors</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-create-exception-filter-expression.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-create-exception-filter-expression.htm
deleted file mode 100644
index ef3b6be..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-create-exception-filter-expression.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Adding Line Breakpoints
-    </title>
-  </head>
-  <body>
-    <h1>
-      Create Exception Breakpoint Filtering    </h1>
-    <p>
-      Type name and package name filtering can be set up for Java exception breakpoints. This can be done from an exception breakpoints' <strong>Filtering</strong> properties page, as shown in the following figure.</p>
-    <p><img src="../tasks/images/tasks-excetpion-filtering-page.PNG" alt="Java Breakpoint Exception Filtering Properties Page"></p>
-    <p>Using the Filtering properties page there are four ways to add filtering for a Java exception breakpoint:</p>
-    <ol>
-      <li>You can select specific threads to restrict the breakpoint to (which must be done while in a debug session)</li>
-      <li>You can use the <strong>Add Class</strong> button to select a class via the <a href="../reference/ref-dialog-type-selection.htm">Type Selection Dialog</a></li>
-      <li>You can use the <strong>Add Package</strong> button to select a  package using a filtered <a href="../reference/ref-dialog-type-selection.htm">Type Selection Dialog</a></li>
-      <li>You can use the<strong> Add </strong>button to define your own pattern to match as a class and/or package filter</li>
-    </ol>
-    <h2>Defining Your Own Filter Pattern</h2>
-    <p>Using the Add button mentioned above, you can define your own pattern to be used as a filter for a Java exception breakpoint. Once pressed, you can then<br>
-  enter any expression in the new space in the <strong>Selected Locations</strong> list, as shown in the following figure.</p>
-    <p><img src="../tasks/images/tasks-exception-filtering-add.PNG" alt="Add Filter Pattern"></p>
-    <p>There are some rules to follow when creating your own pattern.</p>
-    <ol>
-      <li>Your pattern can only contain a '*' at the end </li>
-      <li>Your pattern must be fully qualified, E.g. <em>a.b.c.MyClass</em> </li>
-      <li>Your pattern cannot have spaces in it </li>
-    </ol>
-    <h2>Examples</h2>
-    <ul>
-      <li><em>a.b.c*</em> - would match everything in the package a.b.c</li>
-      <li><em>a.b.c.My* - </em> would match anything in the a.b.c package that started with 'My' </li>
-      <li><em>My*</em> - would match anything in the default package that started with 'My' </li>
-    </ul>
-    <p>&nbsp;</p>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm
deleted file mode 100644
index 7b5c8b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-debug-launch.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Launching a Java program in debug mode
-    </title>
-  </head>
-  <body>
-    <h1>
-      Launching a Java program in debug mode
-    </h1>
-    <p>
-      Launching a program in debug mode allows you to suspend and resume the
-      program, inspect variables, and evaluate expressions using the debugger.
-    </p>
-    <p>
-      To launch a Java program in debug mode,
-    </p>
-    
-<ol>
-  <li> In the <strong>Package Explorer</strong>, select the Java compilation unit 
-    or class file with the main method you want to launch. </li>
-  <li> Press the <strong>Debug</strong> [ <img src="../images/org.eclipse.debug.ui/etool16/debug_exc.png" width="16" height="16"> 
-    ] button in the workbench toolbar or select <strong>Run &gt; Debug</strong> 
-    from the workbench menu bar. Alternatively you can select <strong>Run &gt; 
-    Debug As &gt; Java Application</strong> from the workbench menu bar, or select 
-    <strong>Debug As &gt; Java Application </strong>in the <strong>Package Explorer</strong> 
-    pop-up menu or in the drop-down menu on the <strong>Debug</strong> tool bar 
-    button.</li>
-  <li> Your program is now launched and the launched process appears in the Debug 
-    view.&nbsp; </li>
-</ol>
-    <p>If you want your program to stop in the <em>main</em>  method so that you
-    can step through its complete execution, create a <strong> Java Application</strong>
-    launch configuration and check the <strong>Stop in main </strong>checkbox on
-    the <strong>Main </strong>tab.&nbsp;</p>
-    <p>You can also debug a Java program by selecting a project instead of the
-    compilation unit or class file.&nbsp; You will be prompted to select a class
-    from those classes that define a <em>main</em> method.&nbsp; (If only one class with a main method is
-        found in the project, that class is launched as if you selected it.)</p>
-    <p>
-      <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-      <a href="../concepts/concept-java-views.htm">Java views</a><br>
-       <a href="../concepts/concept-java-editor.htm">Java editor</a><br>
-       <a href="../concepts/cdebugger.htm">Debugger</a>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="task-remotejava_launch_config.htm">Connecting to a remote VM with the Java Remote Application launcher</a><br>
-       <a href="task-relaunch_program.htm">Re-launching a program</a><br>
-       <a href="task-running_and_debugging.htm">Running and debugging</a><br>
-       <a href="../tasks/tasks-executionArgs.htm">Setting execution arguments</a><br>
-       <a href="task-stepping.htm">Stepping through the execution of a program</a><br>
-    </p>
-    <p>
-      <img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-      <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-       <a href="../reference/views/ref-view-package-explorer.htm">Package Explorer</a><br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm
deleted file mode 100644
index a7c2baa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-deleteJRE.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-    <title>
-      Deleting a JRE definition
-    </title>
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Deleting a JRE definition
-    </h1>
-    <p>
-      <br>
-       You can delete Java runtime environment definitions that are available for executing Java programs in the workbench.
-    </p>
-    <ol>
-      <li>
-        Open the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.preferences.VMPreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Installed JREs preference page">
-        <strong>Java &gt; Installed JREs</strong></a> preference page.
-      </li>
-      <li>
-        Select the definition you want to delete and click&nbsp;<strong>Remove</strong>.
-      </li>
-      <li>
-        Check the box for the definition that you want to use as the default JRE for the workbench.
-      </li>
-    </ol>
-	<p>
-     <img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-     </p>
-    <p>     
-      <a href="../concepts/concept-jdt.htm">Java development tools (JDT)</a>
-    </p>
-    <p>
-      <img src="../images/ngrelt.png" alt="Related tasks" border="0">
-    </p>
-    <p>
-      <a href="../tasks/tasks-JREs.htm">Working with JREs</a><br>
-      <a href="../tasks/task-add_new_jre.htm">Adding a new JRE definition</a><br>
-      <a href="../tasks/task-assign_default_jre.htm">Choosing a default JRE</a><br>
-      <a href="../tasks/task-choose_config_jre.htm">Choosing a JRE for launching a project</a>
-    </p>
-    <p>
-      <img src="../images/ngrelr.png" alt="Related reference" border="0" >
-    </p>
-    <p>
-       <a href="../reference/preferences/java/debug/ref-installed_jres.htm">Installed JREs preference page</a>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm
deleted file mode 100644
index 507ac95..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-executionArgs.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-  <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-    <meta http-equiv="Content-Style-Type" content="text/css">
-    <link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>
-      Setting execution arguments
-    </title>
-    <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  </head>
-  <body>
-    <h1>
-      Setting execution arguments
-    </h1>
-    <p>
-      If you want to specify execution arguments for your program, you must
-      define a launch configuration that specifies the arguments.
-    </p>
-    <ol>
-      <li>
-        Select
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenRunConfigurations")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Run Launch Configurations dialog">
-        <strong>Run &gt; Run Configurations...</strong></a> or
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenDebugConfigurations")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Debug Launch Configurations dialog">
-        <strong>Run &gt; Debug Configurations...</strong></a>
-        from the workbench <strong>Run</strong>
-        menu to open the list of launch configurations.&nbsp;&nbsp; Launch
-        configurations for Java programs are shown underneath <strong>Java
-        Application </strong>in this list.&nbsp;
-      </li>
-      
-  <li> Select an existing configuration or create a new launch configuration by 
-    pushing the <strong>New</strong> button after selecting <strong>Java Application</strong>. 
-  </li>
-      <li>
-        On the <strong>Arguments</strong> tab for the configuration, you can
-        specify the following fields as necessary: 
-        <ul>
-          <li>
-            <strong>Program Arguments</strong>: Application-specific values that your code is expecting (a user name or a URL for locating help files, for
-            example).
-          </li>
-          <li>
-            <strong>VM Arguments</strong>: Values meant to change the behavior of the Java virtual machine (VM). For example, you may need to tell the VM whether
-            to use a just-in-time (JIT) compiler, or you may need to specify the maximum heap size the VM should use. Refer to your VM's documentation for more information
-            about the available VM arguments.
-          </li>
-          
-      <li> <strong>Working Directory</strong>: The working directory used for 
-        the launched process. To change from using the default working directory, 
-        select <strong>Other </strong>and specify the workspace or local directory 
-        to use for the working directory of the launched process. </li>
-        </ul>
-      </li>
-      <li>
-        Click <strong>Apply</strong> or&nbsp; <strong>Close</strong> when you are done. Every time you launch this configuration, these execution
-        arguments will be used.
-      </li>
-    </ol>
-    <p>
-      <img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-      <a href="../tasks/tasks-java-local-configuration.htm">Creating a Java Application launch
-      configuration</a><br>
-      <a href="task-launching_java_program.htm">Launching a Java program</a><br>
-      <br>
-    </p>
-    
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm b/bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm
deleted file mode 100644
index 8b2bdb9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tasks/tasks-java-local-configuration.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Creating a Java application launch configuration</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> Creating a Java application launch configuration </h1>
-<p> When you choose <strong>Run &gt;Run As &gt;Java Application </strong>to
-  launch your class, you are running your class using a generic <strong>Java
-  Application</strong> launch configuration that derives most of the launch
-  parameters from your Java project and your workbench preferences.&nbsp; In
-  some cases, you will want to override the derived parameters or specify
-  additional arguments. </p>
-<p> You do this by creating your own <strong>Java Application</strong> launch
-  configuration.&nbsp; </p>
-<ol>
-  <li> Select <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenRunConfigurations")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Run Launch Configurations dialog"> <strong>Run &gt; Run Configurations...</strong></a> or <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenDebugConfigurations")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Debug Launch Configurations dialog"> <strong>Run &gt; Debug Configurations...</strong></a> from the workbench menu bar.&nbsp; This opens a dialog that lets you
-    create, modify, and delete launch configurations of different types. </li>
-  <li> Select <strong>Java Application</strong> in the left hand list of launch 
-    configuration types, and press the <strong>New</strong> button in the toolbar. 
-    This will create a new launch configuration for a Java application.&nbsp;The 
-    tabs on the right hand side allow you control specific aspects of the launch. </li>
-</ol>
-<blockquote>
-  <ul>
-    <li>The <strong>Main</strong> tab defines the class to be launched. Enter 
-      the name of the project containing the class to launch in the project field, 
-      and the fully qualified name of the main class in the Main class field.&nbsp;Check 
-      the <strong>Stop in main</strong> checkbox if you want the program to stop 
-      in the main method whenever the program is launched in debug mode.<br>
-      Note:&nbsp; You do not have to specify a project, but doing so allows a 
-      default classpath, source lookup path, and JRE to be chosen.</li>
-    <li>The <strong>Arguments</strong> tab defines the arguments to be passed 
-      to the application and to the virtual machine (if any). You can also specify 
-      the working directory to be used by the launched application.</li>
-    <li>The <strong>JRE</strong> tab defines the JRE used to run or debug the 
-      application. You can select a JRE from the already defined JREs, or define 
-      a new JRE.</li>
-    <li>The <strong>Classpath</strong> tab defines the location of class files 
-      used when running or debugging an application. By default, the user and 
-      bootstrap class locations are derived from the associated project's build 
-      path. You may override these settings here.</li>
-    <li>The <strong>Source</strong> tab defines the location of source files used 
-      to display source when debugging a Java application. By default, these settings 
-      are derived from the associated project's build path. You may override these 
-      settings here.</li>
-    <li>The <strong>Environment</strong> tab defines the environment variable 
-      values to use when running or debugging a Java application. By default, 
-      the environment is inherited from the Eclipse runtime. You may override 
-      or append to the inherited environment. </li>
-    <li>The <strong>Common</strong> tab defines general information about the 
-      launch configuration.&nbsp; You may choose to store the launch configuration 
-      in a specific file and specify which perspectives become active when the 
-      launch configuration is launched.</li>
-  </ul>
-</blockquote>
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" > </p>
-<p> <a href="../concepts/cdebugger.htm">Debugger</a><br>
-  <a href="../concepts/clocdbug.htm">Local debugging</a> </p>
-<p> <br>
-  <img border="0" src="../images/ngrelt.png" alt="Related tasks" > </p>
-<p> <a href="task-choose_config_jre.htm">Choosing a JRE for launching a project</a><br>
-  <a href="task-launching_java_program.htm">Launching a Java program</a><br>
-  <a href="tasks-executionArgs.htm">Setting execution arguments<br>
-  </a><a href="../tasks/tasks-9.htm">Changing debugger launch options</a> </p>
-<p> <img border="0" src="../images/ngrelr.png" alt="Related reference" > </p>
-<p> <a href="../reference/preferences/run-debug/ref-run_debug.htm">Debug preferences</a><br>
-  <a href="../reference/views/debug/ref-debug_view.htm">Debug view</a><br>
-  <a href="../reference/menus/run/ref-menu-run.htm">Run Menu </a> </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png b/bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png
deleted file mode 100644
index 6fc42f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/DeclarationView.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png b/bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png
deleted file mode 100644
index 5c43ecb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/advanced-highlighting.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png b/bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png
deleted file mode 100644
index a365c10..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/annotation-navigation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png b/bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png
deleted file mode 100644
index 14dda85..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/assign-to-casted-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/breadcrumb.png b/bundles/org.eclipse.jdt.doc.user/tips/images/breadcrumb.png
deleted file mode 100644
index 91a8bcd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/breadcrumb.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png b/bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png
deleted file mode 100644
index e7574ad..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/build-path-actions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png b/bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png
deleted file mode 100644
index b4e2189..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/call_hierarchy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-1.png b/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-1.png
deleted file mode 100644
index 34488e3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-2.png
deleted file mode 100644
index 258f0aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-3.png b/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-3.png
deleted file mode 100644
index a06981c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-5.png b/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-5.png
deleted file mode 100644
index fd624b3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-6.png b/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-6.png
deleted file mode 100644
index 3238dd8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-6.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-7.png b/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-7.png
deleted file mode 100644
index 97db0dc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/camel-case-nav-7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/cleanupprofiles.png b/bundles/org.eclipse.jdt.doc.user/tips/images/cleanupprofiles.png
deleted file mode 100644
index fe132b8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/cleanupprofiles.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png
deleted file mode 100644
index 122c7a0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-add-constructor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym1.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym1.png
deleted file mode 100644
index 2ba5bdb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym2.png
deleted file mode 100644
index b3310b9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-anonym2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png
deleted file mode 100644
index fefdf9b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal-inserted.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png
deleted file mode 100644
index 6f18eb3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-argument-proposal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png
deleted file mode 100644
index 9583feb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-fieldname.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png
deleted file mode 100644
index ab87f47..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-javadoc2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png
deleted file mode 100644
index fa9e113..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-newmethod.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png
deleted file mode 100644
index ca1e2d9..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png
deleted file mode 100644
index fb345bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-type-arg-guessing2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import-result.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import-result.png
deleted file mode 100644
index e9df57e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import-result.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import.png
deleted file mode 100644
index 4807555..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist-with-import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png
deleted file mode 100644
index 84cd0b0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png b/bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png
deleted file mode 100644
index e29f793..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/code-templates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png
deleted file mode 100644
index e030fa3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/codeassist-getter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/colored-labels.png b/bundles/org.eclipse.jdt.doc.user/tips/images/colored-labels.png
deleted file mode 100644
index ce96f42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/colored-labels.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png
deleted file mode 100644
index d31ca1b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-java.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png
deleted file mode 100644
index 7044e42..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compare-properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/completiononcamelcase.png b/bundles/org.eclipse.jdt.doc.user/tips/images/completiononcamelcase.png
deleted file mode 100644
index bc46994..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/completiononcamelcase.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png
deleted file mode 100644
index 5c27c51..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png
deleted file mode 100644
index 32ec61a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/compress-packages2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/content-assist-proposals.png b/bundles/org.eclipse.jdt.doc.user/tips/images/content-assist-proposals.png
deleted file mode 100644
index 7dbd8fd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/content-assist-proposals.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/content_assist_participant.png b/bundles/org.eclipse.jdt.doc.user/tips/images/content_assist_participant.png
deleted file mode 100644
index 7a9370e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/content_assist_participant.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png
deleted file mode 100644
index 4d355bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/create-getter-setter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/create-hashcode-equals.png b/bundles/org.eclipse.jdt.doc.user/tips/images/create-hashcode-equals.png
deleted file mode 100644
index 46d73df..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/create-hashcode-equals.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png
deleted file mode 100644
index ebd6bf7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/delegate-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png b/bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png
deleted file mode 100644
index 9a6ada3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-code-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png b/bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png
deleted file mode 100644
index 5f490af..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/editor-link-style-open.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png b/bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png
deleted file mode 100644
index 1be032d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/ff4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png b/bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png
deleted file mode 100644
index 4bd1f96..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/folding-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/gettersetter-quickassist.png b/bundles/org.eclipse.jdt.doc.user/tips/images/gettersetter-quickassist.png
deleted file mode 100644
index b0ace48..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/gettersetter-quickassist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/group-problems.png b/bundles/org.eclipse.jdt.doc.user/tips/images/group-problems.png
deleted file mode 100644
index 224be61..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/group-problems.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png b/bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png
deleted file mode 100644
index 7b44cce..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/hierarchy-lockview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png b/bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png
deleted file mode 100644
index 94a6de2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/hovergenericsignature.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png b/bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png
deleted file mode 100644
index c0eff70..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/inplace_outline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-always-false.png b/bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-always-false.png
deleted file mode 100644
index 9967b0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-always-false.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-compl-proposals.png b/bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-compl-proposals.png
deleted file mode 100644
index f16c976..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/instanceof-compl-proposals.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-hover.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-hover.png
deleted file mode 100644
index 420e07b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png
deleted file mode 100644
index 0ec480c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-location.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png
deleted file mode 100644
index cd45b4f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png
deleted file mode 100644
index 7d47ae4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-view.png b/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-view.png
deleted file mode 100644
index dad5a5b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/javadoc-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png b/bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png
deleted file mode 100644
index cc5588c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/juniterr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png b/bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png
deleted file mode 100644
index 81514e5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/junitsucc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/link-with-editor-in-occs.png b/bundles/org.eclipse.jdt.doc.user/tips/images/link-with-editor-in-occs.png
deleted file mode 100644
index 40a0677..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/link-with-editor-in-occs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png b/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png
deleted file mode 100644
index 58f280f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-replace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png b/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png
deleted file mode 100644
index 0d10ba6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/localhistory-restore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png b/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png
deleted file mode 100644
index ec04592..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/mark-occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png b/bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png
deleted file mode 100644
index c38d043..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/matching-brackets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png b/bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png
deleted file mode 100644
index 39b274b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/name-conventions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png b/bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png
deleted file mode 100644
index 9b894ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/new-class.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/new-project-with-ee.png b/bundles/org.eclipse.jdt.doc.user/tips/images/new-project-with-ee.png
deleted file mode 100644
index 1871524..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/new-project-with-ee.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/nls-problem-search.png b/bundles/org.eclipse.jdt.doc.user/tips/images/nls-problem-search.png
deleted file mode 100644
index 81ed8a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/nls-problem-search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/null-reference.png b/bundles/org.eclipse.jdt.doc.user/tips/images/null-reference.png
deleted file mode 100644
index 691676b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/null-reference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png b/bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png
deleted file mode 100644
index ae189bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/open-type-camel-case.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/activate-debug-view.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/activate-debug-view.png
deleted file mode 100644
index 66687de..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/activate-debug-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png
deleted file mode 100644
index acc2a81..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/args_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png
deleted file mode 100644
index 84059cc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/assign_value.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png
deleted file mode 100644
index a54b399..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_condition.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png
deleted file mode 100644
index 9be8a71..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/breakpoint_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png
deleted file mode 100644
index 9477552..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/context_menu_launch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/dbg-bread-crumb.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/dbg-bread-crumb.png
deleted file mode 100644
index 3248da1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/dbg-bread-crumb.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png
deleted file mode 100644
index 671bc78..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/deadlock.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png
deleted file mode 100644
index 96ebf8e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/def_vm_args.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png
deleted file mode 100644
index 4fe76ec..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/detail_formatter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png
deleted file mode 100644
index 469c160..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/env_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/hyperlink_step.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/hyperlink_step.png
deleted file mode 100644
index 7c05694..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/hyperlink_step.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png
deleted file mode 100644
index 1ac4d1d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/inspect_popup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png
deleted file mode 100644
index 22adec3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/perspective-prompt.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/perspective-prompt.png
deleted file mode 100644
index 1fff83f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/perspective-prompt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png
deleted file mode 100644
index cc53d55..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/process_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png
deleted file mode 100644
index 6af1776..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/scrapbook.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png
deleted file mode 100644
index 828eb82..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stack_trace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png
deleted file mode 100644
index 224ad8b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/step_into_selection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png
deleted file mode 100644
index e80ec81..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/stop_in_main.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png
deleted file mode 100644
index ac50f45..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/variable_hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/view-mngmt.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/view-mngmt.png
deleted file mode 100644
index af70f9f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/view-mngmt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png
deleted file mode 100644
index 5b2e865..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/watchpoint_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png b/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png
deleted file mode 100644
index fe8ccfd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/org.eclipse.jdt.debug.ui/word_wrap.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/organize-imports-on-save.png b/bundles/org.eclipse.jdt.doc.user/tips/images/organize-imports-on-save.png
deleted file mode 100644
index f61b863..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/organize-imports-on-save.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png
deleted file mode 100644
index 4f101c7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/override-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png b/bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png
deleted file mode 100644
index 9480c0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/package-explorer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png b/bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png
deleted file mode 100644
index 1ed0bd4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-compound.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png b/bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png
deleted file mode 100644
index dbb64ab..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-flat.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png b/bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png
deleted file mode 100644
index 81e45a3..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/packages-hierarchical.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png b/bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png
deleted file mode 100644
index bea48a2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/parameter-hints.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/potential-null-ref.png b/bundles/org.eclipse.jdt.doc.user/tips/images/potential-null-ref.png
deleted file mode 100644
index 69158e2..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/potential-null-ref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png b/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png
deleted file mode 100644
index 67e3326..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-jre.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png b/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png
deleted file mode 100644
index ab79a0b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/project-specific-settings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png
deleted file mode 100644
index c3d03aa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png
deleted file mode 100644
index 901319d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-assign-statement2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png
deleted file mode 100644
index 617ed32..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-catch-to-throws.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png
deleted file mode 100644
index b21c702..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-create-field.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png
deleted file mode 100644
index 8ecf462..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-remove-surrounding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png
deleted file mode 100644
index 3f79b12..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-assist-shortcuts.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png
deleted file mode 100644
index 20c5725..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-create-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png
deleted file mode 100644
index 0431faa..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-localrename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png
deleted file mode 100644
index 00224ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-uncaught-exception.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png
deleted file mode 100644
index a76e6f6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-fix-unimplemented-methods.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png
deleted file mode 100644
index ad1fca4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-outline-inherited.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png
deleted file mode 100644
index 4868db8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quick-refactoring-menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png
deleted file mode 100644
index 7a784a8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png
deleted file mode 100644
index 3307fae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png
deleted file mode 100644
index a83a985..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-addcast3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png b/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png
deleted file mode 100644
index f817d14..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/quickfix-change-signature.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/redundant-null-check.png b/bundles/org.eclipse.jdt.doc.user/tips/images/redundant-null-check.png
deleted file mode 100644
index 44b713a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/redundant-null-check.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/rich-problem-hover.png b/bundles/org.eclipse.jdt.doc.user/tips/images/rich-problem-hover.png
deleted file mode 100644
index 11cdef8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/rich-problem-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png b/bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png
deleted file mode 100644
index da5c678..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/search-returntype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png b/bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png
deleted file mode 100644
index e50933a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/smart-javadoc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png b/bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png
deleted file mode 100644
index 574424b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/sort-by-def.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png b/bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png
deleted file mode 100644
index 9dee4fd..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/spelling-correction-proposal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png b/bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png
deleted file mode 100644
index 078da49..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/ss4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png b/bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png
deleted file mode 100644
index 3392312..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/suppresswarningsR31.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png b/bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png
deleted file mode 100644
index 7c03bac..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/surroundwith.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/swt-templates.png b/bundles/org.eclipse.jdt.doc.user/tips/images/swt-templates.png
deleted file mode 100644
index 615dc3f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/swt-templates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png
deleted file mode 100644
index 9b8215a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/template-for-iter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png b/bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png
deleted file mode 100644
index 1fc6146..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/templates-create-method.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png b/bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png
deleted file mode 100644
index e7ca3b4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/todo-example.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png b/bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png
deleted file mode 100644
index 6fb0620..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/type-access-rules.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png b/bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png
deleted file mode 100644
index 0a2c9ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/type-filter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png b/bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png
deleted file mode 100644
index cd933ae..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/type-hierarchy-structured-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/type-indicator.png b/bundles/org.eclipse.jdt.doc.user/tips/images/type-indicator.png
deleted file mode 100644
index c550452..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/type-indicator.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png b/bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png
deleted file mode 100644
index 33b177c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/typing-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png
deleted file mode 100644
index d11788b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-i.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png
deleted file mode 100644
index a8bc066..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-opt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png
deleted file mode 100644
index cab1804..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png
deleted file mode 100644
index 5a7054b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-x2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png
deleted file mode 100644
index 3f854ff..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png
deleted file mode 100644
index f1b970e..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-deprecation-y2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png b/bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png
deleted file mode 100644
index c01b495..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/warn-privates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/images/working-set-selection.png b/bundles/org.eclipse.jdt.doc.user/tips/images/working-set-selection.png
deleted file mode 100644
index 01b0a07..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/images/working-set-selection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html b/bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html
deleted file mode 100644
index 2ab4fd4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/tips/jdt_tips.html
+++ /dev/null

@@ -1,2215 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<style type="text/css">
-ul {padding-left: 1.2em;}
-</style>
-<title>Tips and Tricks (JDT)</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-
-<h2>Tips and Tricks (JDT)</h2>
-<p>
-The following tips and tricks give some helpful ideas for increasing your productivity.
-See also <a href="../../org.eclipse.platform.doc.user/tips/platform_tips.html">Platform Tips and Tricks</a>
-for general Eclipse tips and <a href="../../org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html">What's New in 3.5 (JDT)</a> for
-features in this release.
-</p>
-<br>
-<p>
-<a href="#editing_section">Editing</a> &nbsp;&nbsp;|&nbsp;&nbsp;
-<a href="#refactor_section">Refactoring</a> &nbsp;&nbsp;|&nbsp;&nbsp;
-<a href="#navigation_section">Navigation</a> &nbsp;&nbsp;|&nbsp;&nbsp;
-<a href="#searching_section">Searching</a> &nbsp;&nbsp;|&nbsp;&nbsp;
-<a href="#views_section">Views</a> &nbsp;&nbsp;|&nbsp;&nbsp;
-<a href="#misc_section">Miscellaneous</a> &nbsp;&nbsp;|&nbsp;&nbsp;
-<a href="#debugging_section">Debugging</a>
-</p>
-<br>
-
-<h3><a name="editing_section"></a>Editing source</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670" bgcolor="white" summary="Editing source tips and tricks">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist</b></td>
-			<td valign="top" align="left" width="80%">Content assist provides you
-			with a list of suggested completions for partially entered strings.
-			In the Java editor press <b>Ctrl+Space</b> or use <b>Edit &gt;
-			Content Assist</b>.
-			<p><img src="images/code-assist.png" border="0" alt="Content assist selection dialog">
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist in
-			Javadoc comments</b></td>
-			<td valign="top" align="left" width="80%">Content assist is also
-			available in Javadoc comments.
-			<p><img src="images/code-assist-javadoc2.png" border="0" alt="Content assist for Javadoc comments"></p>
-			</td>
-		</tr>
-		<tr>
-		    <td width="20%" valign="top" align="left"><b>Content assist for static imports</b></td>
-		    <td valign="top" align="left" width="80%">To get content assist proposals for static members
-		      configure your list of favorite static members on the
-              <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferenceFavorites)")'> 
-                <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Favorites preference page">
-                <b>Java &gt; Editor &gt; Content Assist &gt; Favorites</b></a> preference page.
-		      <p>For example, if you have added <code>java.util.Arrays.*</code> to
-		        this list, then all static methods of this type matching the completion
-		        prefix will be added to the proposals list:</p>
-		      <p><img src="images/content-assist-proposals.png" alt="Content Assist proposals"></p></td>
-		  </tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Suppress types in content
-			assist</b></td>
-			<td valign="top" align="left" width="80%">
-			To exclude certain types from appearing in content assist, use the type
-			filter feature configured on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.TypeFilterPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the type filter preference page">
-			<b>Java &gt; Appearance &gt; Type Filters</b></a>
-			preference page. Types matching one of these filter patterns
-			will not appear in the Open Type dialog and will not be available to
-			content assist, quick fix and organize imports. These filter patterns
-			do not affect the Package Explorer and Hierarchy views.
-			<p><img border="0" src="images/type-filter.png" alt="Type filter preference page"></p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist for
-			variable, method parameter and field name completions</b></td>
-
-			<td valign="top" align="left" width="80%">
-			You can use content assist to speed up the creation of fields, method
-			parameters and local variables. With the cursor positioned after the
-			type name of the declaration, press <b>Ctrl+Space</b> or use <b>Edit &gt; Content Assist</b>.
-			<p><img src="images/code-assist-fieldname.png" alt="Suggestions for field names"></p>
-			<p>If you use a name prefix or suffix for fields, local variables or
-			method parameters, be sure to specify this in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeStylePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the code style preference page">
-			<b>Java &gt; Code Style</b></a>
-			preference page.</p>
-			</td>
-		</tr>
-		<tr>
-		    <td width="20%" valign="top" align="left"><b>Content assist for variable with unresolved type</b>
-		    </td>
-		    <td valign="top" align="left" width="80%">Code assist also works on accesses to
-		      types that are not imported yet. Depending on the
-              <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'>
-                <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Content Assist preference page">
-                <b>Java &gt; Editor &gt; Content Assist </b></a>
-              <b>&gt; Add import instead of qualified name</b> preference the editor
-		      will either automatically add imports or fully qualify the types for such
-		      proposals.
-		      <p>Pressing <b>;</b> in the following scenario:</p>
-		      <p>
-		      <img title="Content Assist For Variables With Unresolved Types" alt="Screenshot showing Content Assist for variables with unresolved types" src="images/code-assist-with-import.png">
-		      </p>
-		      <p>results in:</p>
-		      <p>
-		      <img title="Content Assist Result When Pressing ';'" alt="Screenshot showing the content assist result when pressing ';'" src="images/code-assist-with-import-result.png">
-		      </p>
-		    </td>
-		  </tr>
-		
-		<tr>
-		    <td width="20%" valign="top" align="left"><b>Content assist after instanceof condition</b></td>
-		    <td valign="top" align="left" width="80%">Content assist can propose members 
-		      available on types used in instanceof conditions.
-		      <p>
-		      <img title="Content Assist After instancoef Condition" alt="Screenshot showing Content Assist after instanceof condition" src="images/instanceof-compl-proposals.png">
-		      </p>
-		      <p>
-		      Eclipse will add the required cast for you when you select such a proposal.
-		      </p>
-		    </td>
-		  </tr>
-		  
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Parameter hints</b></td>
-			<td valign="top" align="left" width="80%">With the cursor in a method
-			argument, you can see a list of parameter hints. In the Java Editor
-			press <b>Ctrl+Shift+Space</b> or invoke <b>Edit &gt; Content Assist &gt; Parameter Hints</b>.
-			<p><img src="images/parameter-hints.png" border="0" alt="Parameter hint hover"></p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist on
-			anonymous classes</b></td>
-			<td valign="top" align="left" width="80%">Content assist also
-			provides help when creating an anonymous class. With the cursor
-			positioned after "new " and the beginning of an abstract class or interface name
-			press <b>Ctrl+Space</b> or invoke <b>Edit &gt; Content Assist &gt; Default</b>.
-			<p><img src="images/code-assist-anonym1.png" border="0" alt="Content assist for an anonymous class"></p>
-			This will create the body of the anonymous inner class including all
-			methods that need to be implemented.
-			<p>This also works if you place the caret after the opening parentheses of a class instance creation:</p>
-			<p><img src="images/code-assist-anonym2.png" border="0" alt="Content assist for an anonymous class"></p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Toggle between
-			inserting and replacing content assist</b></td>
-
-			<td valign="top" align="left" width="80%">When content assist is invoked
-			on an existing identifier, it can either replace the
-			identifier with the chosen completion or do an insert. The
-			default behavior (overwrite or insert) is defined in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the content assist preference page">
-			<b>Java &gt; Editor &gt; Content Assist</b></a> preference page.<br>
-			You can temporarily toggle the behavior while inside the content
-			assist selection dialog by pressing and holding the <b>Ctrl</b> key while
-			selecting the completion.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Incremental content assist</b></td>
-			
-			<td valign="top" align="left" width="80%">Content assist can also <b>Insert common prefixes automatically</b>, similar to 
-			Unix shell expansion. To enable that behavior, select the check box on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the content assist preference page">
-			<b>Java &gt; Editor &gt; Content Assist</b></a> preference page.
-			</td>
-		</tr>
-		<tr> 
-			<td width="20%" valign="top" align="left"><b>Camel case support in code completion</b>
-			</td>
-			<td valign="top" align="left" width="80%">Code completion supports camel case patterns. 
-			For example, completing on <tt>NPE</tt> or <tt>NuPoiE</tt> will propose <tt>NullPointerException</tt>. 
-			This support can be disabled using the <b>Show camel case matches</b> 
-			preference on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'> 
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Content Assist preference page"> 
-			<b>Java &gt; Editor &gt; Content Assist</b></a> preference page.
-			<p><img alt="Java editor completing on NPE" src="images/completiononcamelcase.png"> 
-			</p></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Customize content assist categories</b>
-			</td>
-			<td valign="top" align="left" width="80%">
-			Repeatedly invoking content assist <b>(Ctrl+Space)</b> cycles through different proposal
-			categories.
-			<p>
-				<img src="images/content_assist_participant.png" border="0" alt="Content assist with new method template proposals">
-			</p>
-			To configure which categories to show use the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferenceAdvanced)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the content assist preference page">
-			<b>Java &gt; Editor &gt; Content Assist &gt; Advanced</b></a> preference page.
-			<p>
-			You can also assign separate key shortcuts to your favorite proposal categories.
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create getters and
-			setters</b></td>
-			<td valign="top" align="left" width="80%">To create getter and setter
-			methods for a field, select the field's declaration and invoke <b>Source
-			&gt; Generate Getter and Setter</b>.
-			<p><img src="images/create-getter-setter.png" border="0" alt="Generate Getter and Setter dialog">
-</p>
-			If you use a name prefix or suffix be sure to specify this in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeStylePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the code style preference page">
-			<b>Java &gt; Code Style</b></a>
-			preference page.</td>
-		</tr>
-		
-		<tr>
-		    <td width="20%" valign="top" align="left"><b>Create getters and setters quick assist</b></td>
-		    <td valign="top" align="left" width="80%">A quick assist <b>(Ctrl+1)</b> is available on fields to
-		      create getters and setters. 
-		      <p>
-		      <img title="Create Getters and Setters Quick Assist" alt="Screen shot showing the create getters and setters quick assist" src="images/gettersetter-quickassist.png">
-		      </p>
-		    </td>
-		  </tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use content assist to
-			create getter and setters</b></td>
-			<td valign="top" align="left" width="80%">Another way to create
-			getters and setters is using content assist. Set the cursor in the
-			type body between members and press <b>Ctrl+Space</b> to get the proposals
-			that create a getter or setter method stub. <br>
-			<img border="0" src="images/codeassist-getter.png" alt="Content assist for creating a setter"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Delete getters and
-			setters together with a field</b></td>
-
-			<td valign="top" align="left" width="80%">When you delete a field
-			from within a view,
-			Eclipse can propose deleting its Getter and Setter methods.
-			If you use a name prefix or suffix for fields, be sure to specify this in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeStylePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the code style preference page">
-			<b>Java &gt; Code Style</b></a>
-			preference page.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create delegate methods</b></td>
-			<td valign="top" align="left" width="80%">To create a delegate method
-			for a field select the field's declaration and invoke <b>Source &gt;
-			Generate Delegate Methods</b>. This adds the selected methods
-			to the type that contains a forward call to delegated methods. This
-			is an example of a delegate method: <br>
-			<img src="images/delegate-method.png" border="0" alt="Delegate method example">
- 		</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create <code>hashCode()</code> and <code>equals()</code></b>
-			</td>
-
-			<td valign="top" align="left" width="80%">To create the methods <code>hashCode()</code> and <code>equals()</code>
-			invoke <b>Source &gt; Generate hashCode() and equals()</b>.
-			<p>
-				<img src="images/create-hashcode-equals.png" border="0" alt="Generate hashCode() and equals() dialog">
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use templates to create
-			a method</b></td>
-			<td valign="top" align="left" width="80%">Templates are shown together with the <b>Content
-			Assist (Ctrl+Space)</b> proposals.<br>
-			There are existing templates, such as 'private_method',
-			'public_method', 'protected_method' and more, but you can also
-			define new templates for method stubs.<br>
-			
-			<p>After applying a template, use the <b>Tab</b> key to navigate among the values to enter
-			(return type, name and arguments).<br>
-			<img src="images/templates-create-method.png" border="0" alt="Content assist with new method template proposals">
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use templates to create
-			SWT widgets</b></td>
-			<td valign="top" align="left" width="80%">On projects which have the SWT library on the classpath,
-			you can create SWT widgets with <b>Content Assist (Ctrl+Space)</b>
-			<p>To add, for example, an SWT button, type <i>Button</i> and press <strong>Ctrl+Space</strong>, 
-            select the <i>Button</i> SWT template, and press <strong>Enter</strong>.</p> 
-            <p> <img src="images/swt-templates.png" alt="Create a button with the Button template"> </p>
-            <p>To see all available templates go to the 
-		      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaTemplatePreferencePage)")'> 
-		          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Templates preference page">
-		      <b>Java &gt; Editor &gt; Templates</b></a> preference page or open the Templates view through <b>Window &gt; Show View &gt; Other...</b>.
-		      </p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create your own
-			templates</b></td>
-			<td width="80%" valign="top">
-			To create your own templates, go to the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaTemplatePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the editor templates preference page">
-			<b>Java &gt; Editor &gt; Templates</b></a> preference page and press the <b>New</b> button to
-			create a template. For example, a template to iterate backwards in an
-			array would look like this:
-			<p>
-			<img src="images/template-for-iter.png" alt="Template for an iterator"></p>
-		</td>	
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to create
-			a new method</b></td>
-			<td valign="top" align="left" width="80%">Start with the method
-			invocation and use <b>Quick Fix (Ctrl+1)</b> to create the method.
-			<p><img src="images/quick-fix-create-method.png" border="0" alt="'Create method' quick fix">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to change
-			a method signature</b></td>
-			<td valign="top" align="left" width="80%">Add an argument to a method
-			invocation at a call site. Then use <b>Quick Fix (Ctrl+1)</b> to add the
-			required parameter in the method declaration.
-			<p><img src="images/quickfix-change-signature.png" border="0" alt="'Change signature' quick fix">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use content assist to
-			create a constructor stub</b></td>
-			<td valign="top" align="left" width="80%">At the location where you
-			want to add the new constructor, use content assist after typing the
-			first letters of the constructor name.<br>
-			<img border="0" src="images/code-assist-add-constructor.png" alt="Create constructor with content assist"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create new fields from
-			parameters</b></td>
-			<td valign="top" align="left" width="80%">Do you need to create new
-			fields to store the arguments passed in the constructor? Use <b>Quick
-			Assist (Ctrl+1)</b> on a parameter to create the assignment and the
-			field declaration and let Eclipse propose a name according to your Code
-			Style preferences.<br>
-			<img border="0" src="images/quick-assist-create-field.png" alt="'Assign parameter to new field' quick assist"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use content assist to
-			override a method</b></td>
-			<td valign="top" align="left" width="80%">Invoke <b>Content Assist
-			(Ctrl+Space)</b> in the type body at the location where the method
-			should be added. Content assist will offer all methods that can be
-			overridden. A method body for the chosen method will be created.
-			<p><img src="images/code-assist-newmethod.png" border="0" alt="'Override method' content assist">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to add
-			unimplemented methods</b></td>
-			<td valign="top" align="left" width="80%">To implement a new
-			interface, add the 'implements' declaration first to the type.
-			Even without saving or building, the Java editor will underline the
-			type to signal that methods are missing and will show the Quick Fix
-			light bulb. Click on the light bulb or press <b>Ctrl+1 (Edit &gt;
-			Quick Fix)</b> to choose between adding the unimplemented methods or
-			making your class abstract.
-			<p><img src="images/quick-fix-unimplemented-methods.png" border="0" alt="Quick Fix offering 'Add unimplemented methods' proposal">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Clean Up to add
-			unimplemented methods</b></td>
-			<td valign="top" align="left" width="80%">When you add a new method to
-			an interface or an abstract method to an abstract class, Eclipse can generate
-			method stubs in all concrete subclasses at once. Invoke <b>Source &gt; Clean Up...</b>
-			on a set of Java elements, use a custom profile, and select on the <b>Configure...</b>
-			dialog to <b>Add unimplemented methods</b> on the <b>Missing Code</b> tab.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Override a method
-			from a base class</b></td>
-			<td valign="top" align="left" width="80%">To create a method that
-			overrides a method from a base class: <br>
-			Select the type where the methods should be added and invoke <b>Source &gt;
-			Override/Implement Methods</b>. This opens a dialog that lets you
-			choose which methods to override.
-			<p><img src="images/override-method.png" border="0" alt="'Override/Implement method' dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Rename in file</b></td><td valign="top" align="left" width="80%">To quickly do a rename that
-			doesn't require full analysis of dependencies in other files, use the
-			'Rename in file' Quick Assist. In the Java Editor, position the
-			cursor in an identifier of a variable, method or type and press <b>Ctrl+1
-			(Edit &gt; Quick Fix)</b><br>
-			The editor is switched to the linked edit mode (like templates) and
-			changing the identifier simultaneously changes all other references
-			to that variable, method or type.
-			<p><img src="images/quick-fix-localrename.png" border="0" alt="Changing multiple identifiers using 'Local Rename' quick fix">
-			</p>
-			You can also use the direct shortcut <b>Ctrl+2 R</b>. Use the 
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens keys preference page">
-			<b>General &gt; Keys</b></a> preference page
-			to configure shortcuts (in the 'Source' category).
-			</td>
-			
-		</tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use Quick Fix to handle
-			exceptions</b></td>
-			<td width="80%" valign="top">Dealing with thrown exceptions is 
-			easy. Unhandled exceptions are detected while typing and marked with
-			a red line in the editor.
-			<ul>
-				<li>Click on the light bulb or press <b>Ctrl+1</b> to surround the
-				call with a try catch block. If you want to include more statements
-				in the try block, select the statements and use <b>Source &gt;
-				Surround With &gt; Try/catch Block</b>. You can also select individual
-				statements by using <b>Edit &gt; Expand Selection To</b> and
-				selecting <b>Enclosing</b>, <b>Next</b> or <b>Previous</b>.</li>
-				<li>If the call is already surrounded with a try block, Quick Fix
-				will suggest adding the catch block to the existing block.</li>
-				<li>If you don't want to handle the exception, let Quick Fix add a
-				new thrown exception to the enclosing method declaration</li>
-
-			</ul>
-			<p><img src="images/quick-fix-uncaught-exception.png" border="0" alt="'Uncaught exception' quick fix proposals">
-</p>
-			At any time, you can convert a catch block to a thrown exception. Use
-			<b>Ctrl+1 (Edit &gt; Quick Fix)</b> on a catch block.<br>
-			<p><img src="images/quick-assist-catch-to-throws.png" border="0" alt="'Replace catch clause with throws' quick assist">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Less typing for
-			assignments</b></td>
-			<td width="80%" valign="top">Instead of typing an assignment, start
-			with the expression that will be assigned.
-			<p><img src="images/quick-assist-assign-statement.png" border="0" alt="'Assign statement to local variable' quick assist">
-</p>
-			Now use <b>Ctrl+1 (Edit &gt; Quick Fix)</b> and choose '<b>Assign
-			statement to new local variable</b>' and Quick Assist will guess a
-			variable name for you. <br>
-			<img src="images/quick-assist-assign-statement2.png" alt="Quick Assist Assignment" border="0"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Less work with cast
-			expressions</b></td>
-			<td width="80%" valign="top">Don't spend too much time with typing casts. Ignore them first and use quick assist to add them after
-			finishing the statement.
-			<p>
-			For example on assignments:<br>
-			<img border="0" src="images/quickfix-addcast1.png" alt="Add cast in assignment"> <br>
-			Or for method arguments:<br>
-			<img border="0" src="images/quickfix-addcast2.png" alt="Add cast for method arguments"> <br>
-			Or for method call targets:<br>
-			<img border="0" src="images/quickfix-addcast3.png" alt="Add cast in method call targets"></p></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Assign a casted
-			expression</b><br>
-			</td>
-			<td width="80%" valign="top">After an 'instanceof' check, it is very common to cast the expression and assign it to a new local variable. Invoke <b>Quick
-			Assist (Ctrl+1)</b> on the 'instanceof' keyword to save yourself some typing:<br>
-			<img border="0" src="images/assign-to-casted-quickfix.png"
-				alt="'Introduce new local with casted type' quick fix">
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Surround lines</b></td>
-			<td width="80%" valign="top">To surround statements with an if /
-			while / for statement or a block, select the lines to surround and
-			invoke <b>Source &gt; Surround With</b> or press <b>Alt+Shift+Z</b>. 
-			<p><img src="images/surroundwith.png" border="0" alt="'Surround with templates' quick assist">
-</p>
-			<p>The entries in the menu are derived from the normal editor templates: All
-			templates that contain the variable ${line_selection} will show up in the menu.</p> 
-			Templates can be configured on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaTemplatePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the editor templates preference page">
-			<b>Java &gt; Editor &gt; Templates</b></a> preference page. Edit the corresponding templates to customize the resulting code or
-			define your own surround-with templates.<br>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>More Quick Assists and Fixes</b><br>
-			</td>
-			<td width="80%" valign="top">Check out the <a
-				href="../reference/ref-java-editor-quickassist.htm">Quick Assist</a> page for a complete list of available code transformations. A list of quick fixes can be found <a
-				href="../reference/ref-java-editor-quickfix.htm">here</a>.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Shortcuts for Quick Fixes and Assists<br>
-			</b></td>
-			<td valign="top" align="left" width="80%">Some of the popular quick assists like
-			<b>Rename in file</b> and <b>Assign to local variable</b> can be invoked
-			directly with <b>Ctrl+2&nbsp;R</b> and <b>Ctrl+2&nbsp;L</b>. Check
-			the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens keys preference page">
-			<b>General &gt; Keys</b></a> preference page for more quick fixes and quick assists that support direct
-			invocation.
-			<p>Type "Quick Assist" or "Quick Fix" in the filter field:</p>
-			<p><img src="images/quick-assist-shortcuts.png" alt="Keys preference page with quick assist shortcuts"></p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Content assist can insert
-			argument names automatically</b></td>
-
-			<td width="80%" valign="top">
-			You can have content assist insert argument names automatically on
-			method completion. This behavior can be customized on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the content assist preference page">
-			<b>Java &gt; Editor &gt; Content Assist</b></a> preference page (see the
-			<b>Fill method arguments and show guessed arguments</b> checkbox.) For example, when
-			you select the second entry here, 
-			<p><img src="images/code-assist-argument-proposal.png" alt="content assist window">
-</p>
-			<p>content assist will automatically insert argument names:</p>
-			<p><img src="images/code-assist-argument-proposal-inserted.png" alt="content assist inserted argument names">
-</p>
-			<p>You can then use the <b>Tab</b> key to navigate between the
-			inserted names.</p>
-			<p>If you choose <b>Insert best guessed arguments</b>, the best guess will be filled in by default. The alternative
-			proposals are still available.
-			</p>
-			</td>
-
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Automatically insert
-			type arguments</b><br>
-			
-			</td>
-			<td width="80%" valign="top">Enabling <b>Fill method arguments and show guessed arguments</b> on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the content assist preference page">
-			<b>Java &gt; Editor &gt; Content Assist</b></a> preference page
-			is also useful when working with parameterized types in J2SE 5.0.<br>
-			<img border="0" src="images/code-assist-type-arg-guessing.png"
-				alt="Content assist on a parameterized type">
-			<br>results in:<br>
-			<img border="0" src="images/code-assist-type-arg-guessing2.png"
-				alt="Content assist guessed and inserted type argument">
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Remove surrounding
-			statement</b></td>
-			<td width="80%" valign="top">To remove a surrounding statement or
-			block, position the cursor at the opening or closing bracket and press <b>Ctrl+1
-			(Edit &gt; Quick Fix)</b>.
-			<p><img src="images/quick-assist-remove-surrounding.png" border="0" alt="'Remove surrounding statement' quick assist">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>How was that word spelled again?</b></td>
-			<td>You can enable spell-checking support in the Java editor on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Spelling)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the spelling preference page">
-			<b>General &gt; Editors &gt; Text Editors &gt; Spelling</b></a>
-			preference page. Spelling errors
-			are displayed in the Java editor and corresponding Quick Fixes are available:
-			<p><img alt="An example of a spelling correction proposal." title="Spelling Correction Proposal" src="images/spelling-correction-proposal.png" align="middle"></p>
-			<p>You can make the
-			dictionary also available to the content assist. A Quick Fix allows you to
-			add new words to the user dictionary on the fly.</p>
-				</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Structured selections</b></td>
-			<td width="80%" valign="top">The Structured Selection actions can be used to
-			enlarge the current selection to the next enclosing element:
-			<p>Highlight some text and press <b>Alt+Shift+Arrow Up</b> or select <b>Edit
-			&gt; Expand Selection To &gt; Enclosing Element</b> from the menu
-			bar - the selection will be expanded to the smallest Java-syntax
-			element that contains the selection. You can then further expand the
-			selection by invoking the action again (or other actions from the Expand Selection To menu).</p>
-			<p>This is for example helpful to select the enclosing identifier for renames,
-			or the select adjacent statements for a subsequent Extract Method refactoring.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Find the matching
-			bracket</b></td>
-			<td width="80%" valign="top">To find a matching bracket select an
-			opening or closing bracket and press <b>Ctrl+Shift+P</b> or select <b>Navigate &gt;
-			Go To &gt; Matching Bracket</b>. You can also <b>double click</b>
-			before an opening or after a closing bracket - this selects the text
-			between the two brackets.
-			<p><img src="images/matching-brackets.png" border="0" alt="Using 'double click' to select text between two brackets">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Smart Javadoc</b></td>
-			<td width="80%" valign="top">Type '/**' and press <b>Enter</b>. This
-			automatically adds a Javadoc comment stub containing the standard
-			@param, @return and @exception tags.
-			<p><img src="images/smart-javadoc.png" border="0" alt="Result of 'Smart Javadoc'">
-</p>
-			The templates for the new comment can be configured in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeTemplatePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the code templates preference page">
-			<b>Java &gt; Code Style &gt; Code Templates</b></a> preference page.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use the local history
-			to revert back to a previous edition of a method</b></td>
-			<td valign="top" align="left" width="80%">Whenever you edit a file,
-			its previous contents are kept in the local history. Java tooling
-			makes the local history available for Java elements, so you can
-			revert back to a previous edition of a single method instead of the
-			full file.
-			<p>Select an element (e.g. in the Outline view) and use <b>Replace With &gt; Local History</b>
-			to revert back to a previous edition of the element.</p>
-			<p><img src="images/localhistory-replace.png" border="0" alt="Replace form local history dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use the local history
-			to restore removed methods</b></td>
-			<td valign="top" align="left" width="80%">Whenever you edit a file,
-			its previous contents are kept in the local history. Java tooling
-			makes the local history available for Java elements, so you can
-			restore deleted methods selectively.
-			<p>Select a container (e.g. in the Outline view) and use <b>Restore from Local History</b> to
-			restore any removed members.</p>
-			<p><img src="images/localhistory-restore.png" border="0" alt="Restore from local history dialog">
-</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Customizable code
-			generation</b></td>
-			<td width="80%" valign="top" align="left">The
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeTemplatePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the code templates preference page">
-			<b>Java &gt; Code Style &gt; Code Templates</b></a> preference page
-			allows you to customize
-			generated code and comments in a similar way to normal templates.
-			These code templates are used whenever code is generated.<br>
-			<p><img
-				src="images/code-templates.png" border="0"
-				alt="Code templates preference page">
-			</p>
-			Since 3.1, it is possible to use project specific Code templates, that will also be shared in the team if your project is shared. Open the <b>Properties</b> on a project to enable project specific settings.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Create comments in your
-			code</b></td>
-			<td width="80%" valign="top" align="left">Comments can be added explicitly with <b>Source &gt; Generate Element Comment (Alt+Shift+J)</b> or automatically by various wizards, refactorings or quick fixes.<br>
-			Configure the comment templates on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeTemplatePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the code templates preference page">
-			<b>Java &gt; Code Style &gt; Code Templates</b></a> preference page.<br>
-			Enable or disable the automatic generation of comments either directly on the wizard (e.g. using <b>'Generate
-			Comment'</b> checkbox on the new Java type wizards) or by the <b>'Automatically
-			add new comments for new methods and types'</b> checkbox of the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeTemplatePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the code templates preference page">
-			<b>Java &gt; Code Style &gt; Code Templates</b></a> preference page.<br>
-			All these settings can also be configured on a per project basis. Open the <b>Properties</b> on a project to enable project specific settings.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Sort members</b></td>
-			<td width="80%" valign="top" align="left">You can <b>Sort Members</b>
-			of a Java compilation unit or a set of compilation units according to a category order defined in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.MembersOrderPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the member sort order preference page">
-			<b>Java &gt; Appearance &gt; Members Sort Order</b></a> preference page.<br>
-			You'll find the action under <b>Source &gt; Sort Members</b>.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Wrap strings</b></td>
-			<td width="80%" valign="top" align="left">
-			You can have String literals wrapped when you edit them. For
-			example, if you have code like this:
-			<pre>String message= &quot;This is a very long message.&quot;;</pre>
-
-			<p>position your caret after the word &quot;very&quot; and press <b>Enter</b>.
-			The code will be automatically changed to:</p>
-			<pre>String message= &quot;This is a very&quot; + 
-           &quot; long message.&quot;;</pre>
-			<p>This behavior can be customized in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.SmartTypingPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the typing preference page">
-			<b>Java &gt; Editor &gt; Typing</b></a> preference page.</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td valign="top" align="left"><b>Smart Typing and how to control it</b></td>
-			<td>
-			The Java editor's Smart Typing features ease your daily work. You can configure
-			them on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.SmartTypingPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the typing preference page">
-			<b>Java &gt; Editor &gt; Typing</b></a> preference page.
-			<p>
-			<img src="images/typing-preferences.png" border="0" alt="Java editor typing preference page" title="Typing Preference Page" align="middle">
-</p>
-			<p>
-			When you enable <b>Automatically insert Semicolons at correct
-			position</b>, typing a semicolon  automatically positions the cursor at the end of the statement before inserting the semicolon. This safes you some additional cursor navigation.<br>
-			You can
-			undo this automatic positioning by pressing backspace right afterwards.
-			</p>
-			</td>
-		</tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Fix your code
-			indentation with one key stroke</b></td>
-			<td width="80%" valign="top" align="left">A useful feature is <b>Source
-			&gt; Correct Indentation</b> or <b>Ctrl+I</b>.<br>
-			Select the code where the indents are incorrect and invoke the action.
-			<p>If nothing is selected, the action indents the current line.</p></td>
-		</tr>		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Fix your code
-			indentation on save</b></td>
-			<td width="80%" valign="top" align="left">Eclipse can correct the indentation
-			of your code when you save the editor.  Go to the 
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.SaveParticipantPreferencePage)")'> 
-		          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Save Actions preference page">
-		          <b>Java &gt; Editor &gt; Save Actions</b></a> preference page and
-		    <b>Configure...</b> <b>Additional actions</b>, and select to <b>Correct indentation</b> on
-		    the <b>Code Organizing</b> tab.
-		    </td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Quick menus for source and
-			refactoring actions</b></td>
-			<td align="left" valign="top">
-			The refactoring and source actions can be accessed via a quick
-			menu. Select the element to be manipulated in the Java editor or in a
-			Java view and press <b>Alt+Shift+S</b> for the quick source menu, 
-			<b>Alt+Shift+T</b> for the quick refactoring menu and <b>Alt+Shift+Z</b> for the surround with menu.
-			<p><img border="0" src="images/quick-refactoring-menu.png" alt="Quick refactoring menu"></p></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Find unused code</b></td>
-			<td width="80%" valign="top" align="left">The Java compiler detects
-			unreachable code, unused variables, parameters, imports and unused
-			private types, methods and fields. 
-			Change the settings for the detection on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the error/warning preference page">
-			<b>Java &gt; Compiler &gt; Error/Warnings</b></a>
-			preference page. These settings can also be specified per project, use: <b>Project &gt; Properties &gt; Java Compiler &gt;
-			Error/Warnings</b>.<p><img src="images/warn-privates.png" border="0" alt="Compiler preference page">
-            </p>
-			These problems are detected as you type, and a quick fix is
-			offered to remove the unneeded code.
-			You can also use <b>Source &gt; Clean Up...</b> to remove unused code.</td>
-		</tr>
-        <tr>
-          <td width="20%" valign="top" align="left"><b>Find problems with null</b>
-          </td>
-          <td width="80%" valign="top" align="left">The compiler can help you find problems with <code>null</code> in your code.
-            The
-            <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> 
-              <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-              <b>Java &gt; Compiler &gt; Errors/Warnings</b></a>
-            preference page has three options to detect problems:
-            <ul>
-              <li><b>Null pointer access</b> (in 'Potential programming problems')<br>
-                When this option is enabled, the compiler will issue an error or warning
-                  whenever a variable that is statically known to hold a null value
-                  is used to access a field or method, as shown in the example below:
-                <p><img src="images/null-reference.png" alt="Null pointer access example"></p><br>
-              </li>
-              <li><b>Potential null pointer access</b> (in 'Potential programming problems')<br>
-                When this option is enabled, the compiler will issue an error or a
-                  warning whenever a variable is statically known to potentially hold
-                  a null value, as shown in the example below:
-                <p><img src="images/potential-null-ref.png" alt="Potential null pointer access example"></p><br>
-              </li>
-              <li><b>Redundant null check</b> (in 'Unnecessary code')<br>
-                When enabled, the compiler will issue an error or a warning whenever
-                  a variable that is statically known to hold a null or a non-null
-                  value is tested against null, as shown in the examples below:
-                <p><img src="images/instanceof-always-false.png" alt="Redundant null check example (instanceof always false)"></p>
-                <br>
-                <p><img src="images/redundant-null-check.png" alt="Redundant null check example"></p>
-              </li>
-            </ul>
-      	</td>
-		</tr>
-        <tr>
-          <td width="20%" valign="top" align="left"><b>Find problems with externalized strings</b>
-          </td>
-          <td width="80%" valign="top" align="left">The <b>Source &gt; Find Broken Externalized Strings</b> action
-          finds undefined, unused and duplicate keys for you:
-                <p><img src="images/nls-problem-search.png" alt="Externalized string search result example"></p>
-      	</td>
-		</tr>
-      	<tr>
-          <td width="20%" valign="top" align="left"><b>Change problem severity in problem hover</b></td>
-          <td width="80%" valign="top" align="left">When a problem hover has been enriched
-          (by pressing F2 or moving the mouse into the hover),
-            an action to change the severity of the current problem is available. 
-            <p>
-            <img src="images/rich-problem-hover.png" alt="Enriched problem hover">
-            </p>
-            <p>Click on the button in the toolbar to go to the 
-            <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> 
-              <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-              <b>Java &gt; Compiler &gt; Errors/Warnings</b></a> preference page.
-            </p>
-      	</td>
-        </tr>
-      		<tr>
-			<td valign="top" align="left"><b>Javadoc comment handling</b></td>
-			<td>The Eclipse Java compiler can process Javadoc comments. Search
-			reports references in doc comments, and refactoring updates these
-			references as well. This feature is controlled from the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavadocProblemsPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Javadoc problems preference page">
-			<b>Java &gt; Compiler &gt; Javadoc</b></a>
-			preference page (or set for an individual
-			project using <b>Project &gt; Properties &gt; Java Compiler &gt;
-			Javadoc</b>).
-			<p><img src="images/javadoc-prefs.png" alt="Javadoc preference page">
-</p>When turned on, malformed Javadoc comments are marked in the Java editor and can be fixed using <b>Edit
-			&gt; Quick Fix (Ctrl+1)</b>: 
-			<p>
-			<img src="images/javadoc-quickfix.png" alt="Problems detected in Javadoc" title="Problems detected in Javadoc">
-</p></td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Suppress warnings</b></td>
-			<td>In J2SE 5.0 and later, you can suppress all optional compiler warnings using the <code>SuppressWarnings</code> annotation.<br>
-			In this example, <code>addAll()</code> is marked as an unused method. <b>Quick Fix (Ctrl+1)</b> is used to add a <code>SuppressWarnings</code> annotation so that the warning will not be shown for this method.<br>
-			<img src="images/suppresswarningsR31.png" border="0"
-				alt="Quick fix to add SuppressWarning annotation">
-			</td>
-		</tr>
-		
-		<tr>
-		   	<td valign="top" align="left"><b>Clean Ups</b>
-		   	</td>
-      		<td><b>Source &gt; Clean Up...</b> helps fixing multiple 
-          	problems at once and helps to establish a consistent code style. For instance, you can:
-        	<ul>
-          		<li>convert all <code>for</code> loops to enhanced <code>for</code> 
-            	loops where possible. </li>
-          		<li>mark all overriding methods in a whole project with an <code>@Override</code> annotation. </li>
-          		<li>organize imports</li>
-          		<li>format your code</li>
-          		<li>remove unnecessary code</li>
-        	</ul>
-        	
-        	<p>Clean Ups are organized in Clean Up profiles.
-        	  A profile can be attached to the workspace or to individual projects. 
-              Project settings can be shared in a team through a version control system. 
-              It is also possible to export and import each profile.</p>
-              <p> <img src="images/cleanupprofiles.png" alt="Clean Up preference page"></p>
-            <p>
-            Clean Ups can be executed as save actions on save. Go to the
-            <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.SaveParticipantPreferencePage)")'> 
-		          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Save Actions preference page">
-		          <b>Java &gt; Editor &gt; Save Actions</b></a> preference page to configure
-		    which clean ups to invoke on save.
-            </p>
-         	</td>
-    	</tr>
-  
-	</tbody>
-</table>
-
-<h3><a name="refactor_section"></a>Refactoring</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670" summary="Refactoring tips and tricks" bgcolor="white">
-	<tbody>
-			<tr>
-			<td width="20%" valign="top" align="left"><b>Scripting of refactorings</b>
-			</td>
-			<td valign="top" align="left" width="80%">
-			Most of the refactorings offered by JDT can not only be executed interactively, but also by a refactoring script.<br><br>
-        	Create a refactoring script from the refactoring history using <b>Refactor &gt; Create Script...</b>.<br><br>A refactoring script
-        	can then be applied later on an arbitrary workspace using <b>Refactor &gt; Apply Script...</b>.<br><br>
-        	Such refactoring scripts can be used in different scenarios such as automatic fixing of breaking API changes between software layers
-        	or providing patches with rich semantics.
-			</td>
-		</tr>
-					<tr>
-			<td width="20%" valign="top" align="left"><b>Safe JAR file migration</b>
-			</td>
-			<td valign="top" align="left" width="80%">
-			When exporting a JAR file from the workspace, the JAR Export Wizard offers the option
-			to include refactoring information into the JAR file.<br><br>
-			Use <b>File &gt; Export...</b> and select <b>JAR file</b>. On the first page of the JAR Export Wizard, select
-			<b>Export refactorings for checked projects</b>. Click on the link to select the refactorings to include.<br><br>
-			Clients are then able to migrate an old version of the JAR file to a new one using the <b>Refactor &gt; Migrate JAR File...</b> refactoring. This refactoring
-			automatically updates all code which is dependent on the old version of the JAR file to use  the new version of the JAR file.
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<h3><a name="searching_section"></a>Searching</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670" summary="Searching tips and tricks"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Locate variables and
-			their read/write access</b></td>
-			<td valign="top" align="left" width="80%"><a name="search_occurrences"></a>You can locate variables
-			and see their read/write status by selecting an identifier
-			(variable, method or type reference or declaration) and invoking <b>Search
-			&gt; Occurrences in File &gt; Identifier</b>. This marks all references of this
-			identifier in the same file. The results are also shown in the search
-			view with different colors for read or write access, along with icons 
-			showing the variable's read or write access.<br>
-			<p><img src="images/link-with-editor-in-occs.png"  border="0" alt="Read and write accesses to a field">
-</p>
-			<p>Alternatively, use the  <b><a href="#mark_occurrences">Mark
-			Occurrences</a></b> feature to dynamically highlight occurrences.
-			You can search over several files by using the general search
-			features (<b>Search &gt; References</b>).
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Search for methods with
-			a specific return type</b></td>
-			<td valign="top" align="left" width="80%">
-			To search for methods with a specific return type, use &quot;*
-			&lt;return type&gt;&quot; as follows:
-
-			<ul>
-				<li>Open the search dialog and click on the <b>Java Search</b> tab.</li>
-				<li>Type '*' and the return type, separated by a space, in the <b>Search
-				string</b>.</li>
-				<li>Select the <b>Case sensitive</b> checkbox.</li>
-				<li>Select <b>Method</b> and <b>Declarations</b> and then click <b>Search.</b></li>
-			</ul>
-			<p><img src="images/search-returntype.png"  border="0" alt="Search for method with given return type">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Filter search matches in Javadoc</b></td>
-			<td width="80%" valign="top" align="left">By default, <b>Java Search</b> finds references inside
-			Java code and Javadoc. If you don't want to see the references inside Javadoc, you can filter these
-			matches by enabling 'Filter Javadoc' in the view menu (triangle symbol) of the search view.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Filter potential search matches</b></td>
-			<td width="80%" valign="top" align="left">Potential matches occur when a compile-time problem
-			prevents the search engine from completely resolving the match. Filter these matches with <b>Filter Potential</b>
-			in the search view menu (triangle symbol).</td>
-		</tr>		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Trace method call chains
-			with the Call Hierarchy</b></td>
-			<td valign="top" align="left" width="80%">
-			Use the Call Hierarchy to follow long or complex
-			call chains without losing the original context: Just select a method
-			and invoke <b>Navigate &gt; Open Call Hierarchy (Ctrl+Alt+H)</b>.
-			<p><img src="images/call_hierarchy.png"  border="0" alt="Call Hierarchy View"></p>
-			<p>Methods from anonymous classes or special types like <code>Runnable</code> are
-			by default expanded with constructors, since it is often more interesting to
-			see where the object is created than where the method is invoked.
-			<b>Expand with Constructors</b> from the context menu toggles this behavior. The defaults can
-			be configured in the view menu.
-			</p>
-			</td>
-		</tr>
-		
-	</tbody>
-</table>
-<h3><a name="navigation_section"></a>Code navigation and reading</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670" summary="Code navigation and reading tips and tricks"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Open selection in
-			Java editor</b></td>
-			<td valign="top" align="left" width="80%">There are two ways how you
-			can open an element from a reference in the Java editor.
-			<ul>
-				<li>Select the reference in the code and press <b>F3 (Navigate &gt;
-				Open Declaration)</b></li>
-				<li>Hold <b>Ctrl</b>, move the mouse pointer over the reference, and click the hyperlink</li>
-			</ul>
-			<img src="images/editor-link-style-open.png"  border="0" alt="Hyperlink style navigation">
-<br>
-			<p>
-			Holding <b>Ctrl</b> on an overridable method shows a popup with an <b>Open Implementation</b> entry, which directly
-			opens the implementation in case there's only one, or shows all the concrete implementations for that method
-			in the hierarchy of its declaring type, using the quick type hierarchy.
-			</p>
-			The hyperlink style navigation can be configured on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.HyperlinkDetectorsPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the hyperlinking preference page">
-			<b>General &gt; Editors &gt; Text Editors &gt; Hyperlinking</b></a> preference page.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>In-place outlines</b></td>
-			<td valign="top" align="left" width="80%">Press <b>Ctrl+F3</b> in the
-			Java editor to pop up an in-place outline of the element at the
-			current cursor position. Or press <b>Ctrl+O (Navigate &gt; Quick
-			Outline)</b> to pop up an in-place outline of the current source
-			file.
-			<p><img src="images/inplace_outline.png"  border="0" alt="Inplace outline">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>In-place outlines show inherited members</b></td>
-			<td valign="top" align="left" width="80%">Press <b>Ctrl+O</b> or <b>Ctrl+F3</b>
-			 again to add inherited members to an open In-place outline. Inherited members have a gray label.
-			 Filter and sort the outline with the menu in the upper right corner.
-			<p><img src="images/quick-outline-inherited.png"  border="0" alt="Quick outline view"></p>
-            </td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>In-place hierarchy</b></td>
-			<td valign="top" align="left" width="80%">Find out which are the
-			possible receivers of a virtual call using the <b>Quick Type Hierarchy</b>.
-			Place the cursor inside the method call and press
-			<b>Ctrl+T (Navigate&nbsp;&gt;&nbsp;Quick Type Hierarchy)</b>.
-			The view shows all types that implement the method with a full icon.
-			<p><img border="0" src="images/type-hierarchy-structured-view.png"
-				 alt="Quick Type Hierarchy dialog">
-			</p>
-			<p>Press <b>Enter</b> to open the corresponding method in an editor. Press <b>Ctrl+T</b> again to switch
-			to the Supertype hierarchy.</p></td>
-		</tr>		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Java Editor Breadcrumb</b></td>
-			<td valign="top" align="left" width="80%">The Java Editor contains a breadcrumb navigation bar which 
-			shows the path to the element at the cursor position. The breadcrumb can be enabled via 
-			the <b>Toggle Breadcrumb</b> tool bar button or by pressing <b>Alt+Shift+B</b>.
-			<p><img border="0" src="images/breadcrumb.png" alt="Java Editor Breadcrumb">
-			</p>
-			<p>Each element in the breadcrumb can be selected and actions can be invoked through a 
-			context menu or keyboard short cuts. Furthermore the breadcrumb lets you navigate to other 
-			elements via drop-downs.
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Advanced highlighting</b></td>
-			<td align="left" valign="top">
-				The Java editor can highlight source code according to its
-				semantics (for example: static fields, local variables, static method
-				invocations). Have a look at the various options on the
-				<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorColoringPreferencePage)")'>
-				<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the syntax coloring preference page">
-				<b>Java &gt; Editor &gt; Syntax Coloring</b></a>
-				preference page.<p><img src="images/advanced-highlighting.png"  alt="An example of advanced highlighting." title="Advanced Highlighting" align="middle">
-</p>
-				
-			</td>
-
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Initially folded regions</b></td>
-			<td>You can specify which regions are folded by default when an editor is opened. Have a look at the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.FoldingPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the folding preference page">
-			<b>Java &gt; Editor &gt; Folding</b></a>
-			preference page to customize this.<p><img src="images/folding-preferences.png"  alt="Folding preference page" title="Folding Preference Page" align="middle">
-</p>
-				</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Mark occurrences</b></td>
-			<td valign="top" align="left" width="80%">
-			<a name="mark_occurrences"></a>When working in the
-			editor, turn on <b>Mark Occurrences</b> in the toolbar (<img src="../images/org.eclipse.jdt.ui/etool16/mark_occurrences.png"  alt="Picture of Mark Occurrences Toolbar Button" title="Picture of Mark Occurrences Toolbar Button">
-) or
-			press <b>Alt+Shift+O</b>. You'll see within a file, where a
-			variable, method or type is referenced.
-			<p>
-			<img border="0" src="images/mark-occurrences.png" alt="Editor with occurrences of 'info' marked"><br>
-			</p>
-			<p>Different colors are used to mark read and write accesses.</p>
-			<p>Selecting a return type shows you the method's exit points. Select an
-			exception to see where it is thrown.
-			Select a super class or interface to see the methods override or implement a method from the selected super type.</p>
-			<p>Fine tune 'mark occurrences' on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.MarkOccurrencesPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the mark occurrence page">
-			<b>Java &gt; Editor &gt; Mark Occurrences</b></a> preference page.
-			<br>
-			Change the color for to marker on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Annotations)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the annotations page">
-			<b>General &gt; Editors &gt; Text Editors &gt; Annotations</b></a> preference page.
-			</p>
-			<p>To show occurrences in the Search view, use the
-			<a href="#search_occurrences"><b>Search &gt; Occurrences</b></a> feature.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Go to next / previous
-			method</b></td>
-			<td valign="top" align="left" width="80%">To quickly navigate to the
-			next or previous method or field, use<br>
-			<b>Ctrl+Shift+Arrow Up (Navigate &gt; Go To &gt; Previous Member</b>)
-			or <b>Ctrl+Shift+Arrow Down (Navigate &gt; Go To &gt; Next Member)</b></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Control your navigation between annotations</b></td>
-			<td>
-			Use the Next / Previous Annotation toolbar buttons or <b>Navigate
-			&gt; Next Annotation</b> (<b>Ctrl+.</b>) and <b>Navigate &gt; Previous
-			Annotation</b> (<b>Ctrl+,</b>) to navigate between annotations
-			in a Java source file.
-			With the button drop-down menus,  you can configure on which annotations you want to stop:
-			<p><img src="images/annotation-navigation.png"  alt="Next/Previous annotation drop-down." title="Next/Previous Annotation Drop-Down" align="middle">
-</p>
-			
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Reminders in your Java
-			code</b></td>
-			<td valign="top" align="left" width="80%">When you tag a comment in
-			Java source code with "TODO" the Java compiler automatically creates
-			a corresponding task as a reminder. Opening the task navigates you
-			back to the "TODO" in the code. Use the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.TodoTaskPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the todo page">
-			<b>Java &gt; Compiler &gt; Task Tags</b></a>
-			preference page to configure any other special tags (like "FIXME") that you'd
-			like to track in the task list.<p><img src="images/todo-example.png"  border="0" alt="Task tags in editor and task view">
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Tricks in the Open Type dialog</b><br>
-			
-			</td>
-			<td valign="top" align="left" width="80%">
-			The Open Type dialog (<b>Navigate &gt; Open Type</b> or toolbar button) helps you navigate to a type
-			by its name.
-			<ul>
-				<li>To find types quickly, only type the capital letters of the type name:<br>
-				<code>IOOBE</code> finds <code>IndexOutOfBoundsException</code>.<br>
-				Or type the first few characters of each name part:<br>
-				<code>NuPoiE</code> finds <code>NullPointerException</code>.</li>
-				<li>To see all types ending with a given suffix, e.g. all Tests, use <tt>*Test&lt;</tt>
-				to not see all types containing <tt>Test</tt> somewhere else in the type name.</li>
-				<li>To open multiple types at once, select them in the list and click OK.</li>
-			</ul>
-			<img border="0" src="images/open-type-camel-case.png"
-				 alt="Open type dialog with camel case matching"></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b> Make hovers sticky</b></td>
-			<td valign="top" align="left" width="80%">You can open the text from
-			a hover in a scrollable window by pressing <b>F2 (Edit &gt; Show
-			Tooltip Description)</b> or by moving your mouse pointer into the hover. You can select and copy content from this
-			window, invoke actions, or follow links.
-			<p><img src="images/javadoc-hover.png"  border="0" alt="Window containing content of the hover">
-			</p>
-			<p> You can configure how to enrich the hover on the
-      		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.GeneralTextEditor)")'> 
-          	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Text Editors preference page">
-          	<b>General &gt; Editors &gt; Text Editors</b></a> preference page.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Hovers in the Java
-			editor</b></td>
-			<td valign="top" align="left" width="80%">You can see different hovers in the
-			Java editor by using the
-			modifier keys (<b>Shift</b>, <b>Ctrl</b>, <b>Alt</b>). <br> 
-			When you move the mouse over an identifier that has no warning or problem annotation in the Java editor, by
-			default a hover with the Javadoc extracted from the corresponding
-			source of this element is shown. If there's a problem annotation on the identifier then the hover
-			shows the corresponding message. Holding down the <b>Shift</b> key shows you
-			the source code:
-			<p><img src="images/editor-code-hover.png"  border="0" alt="Hover showing code of the element in the hover">
-			</p>
-			You can change this behavior and define the hovers for other modifier
-			keys in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorHoverPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the hovers page">
-			<b>Java &gt; Editor &gt; Hovers</b></a> preference page.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Generic method inferred signature</b><br>
-			</td>
-			<td valign="top" align="left" width="80%">You can use hover to show the inferred signature of a generic method.
-			<p><img src="images/hovergenericsignature.png" border="0" alt="Hover showing generic method inferred signature">
-			</p></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Open and configure
-			external Javadoc documentation</b></td>
-			<td valign="top" align="left" width="80%">If you want to open the
-			Javadoc documentation for a type, method or field with <b>Shift+F2
-			(Navigate &gt; Open External Javadoc)</b>, you first have to specify
-			the documentation locations to the elements parent library (JAR,
-			class folder) or project (source folder).<br>
-			For libraries, open the build path page (<b>Project &gt; Properties
-			&gt; Java Build Path</b>), go to the <b>Libraries</b>, and expand the
-			node of the library where you can edit the 'Javadoc location' node.
-			The documentation can be local on your file system in a folder or
-			archive, or on a web server.
-			<p><img src="images/javadoc-location.png"  border="0" alt="Configuring Javadoc location in the Java build path dialog">
-</p>
-			For types, methods or fields in source folders, go to the (<b>Project
-			&gt; Properties &gt; Javadoc Location</b>).</td>
-		</tr>
-	</tbody>
-</table>
-<h3><a name="views_section"></a>Java views</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td valign="top" align="left">
-			<b>Organizing workspace with many projects</b>
-			</td>
-			<td>Use <b>Top Level Elements &gt; Working Sets</b> in the Package Explorer's view menu to enable 
-a new mode that shows working sets as top level elements. This mode makes it 
-much easier to manage workspaces containing lots of projects.
-			<p><img alt="Package Explorer in Working Set mode"
-				src="images/package-explorer.png"></p>
-			<p>Use <b>Configure Working Sets...</b> from the Package Explorer's view
-			menu to configure which working sets get shown. The dialog lets you
-			create new Java working sets, define which working sets are shown and
-			in what order. If <b>Sort Working Sets</b> is not enabled, working sets can also be rearranged directly in the
-			Package Explorer using drag and drop.</p>
-			</td>
-		</tr>
-        <tr>
-          <td valign="top" align="left"><b>Assign working sets</b>
-		    </td>
-          <td>To assign an element to a different working
-            set, select the element in the Package Explorer and choose <b>Assign Working
-            Sets...</b> from the context menu.
-            <p> <img src="images/working-set-selection.png" alt="Screenshot showing the working set assignment dialog"> </p></td>
-        </tr>
-		<tr>
-			<td valign="top" align="left"><b>Declaration view</b></td>
-			<td>The Declaration view (
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.jdt.ui.SourceView)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Java Declaration view">
-			<b>Window &gt; Show View &gt; Other... &gt; Java &gt; Declaration</b></a>) shows the source of the
-			element selected in the Java editor or in a Java view.
-			<p><img src="images/DeclarationView.png"  title="Declaration view" alt="Declaration view">
-</p>
-			</td>
-		</tr>
-
-		<tr>
-			<td valign="top" align="left"><b>Javadoc view</b></td>
-			<td>The Javadoc view (
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.jdt.ui.JavadocView)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Javadoc view">
-			<b>Window &gt; Show View &gt; Other... &gt; Java &gt; Javadoc</b></a>) shows the Javadoc of the element
-			selected in the Java editor or in a Java view.
-			<p><img src="images/javadoc-view.png" title="Javadoc view" alt="Javadoc view">
-</p>
-			</td>
-		</tr><tr>
-			<td width="20%" valign="top" align="left"><b>Type Hierarchy view and method
-			 implementations&nbsp;/ definitions</b></td>
-			<td valign="top" align="left" width="80%">To find out 
-			which types in a hierarchy override a method, use the 'Show Members in
-			Hierarchy' feature:
-			<ol>
-				<li>Select the method to look at and press <b>F4 (Navigate &gt; Open
-				Type Hierarchy)</b>. This opens the type Hierarchy view on the
-				method's declaring type.</li>
-				<li>With the method selected in the Hierarchy view, press the 'Lock
-				View and Show Members in Hierarchy' tool bar button.</li>
-			</ol>
-				The Hierarchy view now shows only types that implement or define
-				the 'locked' method. You can for example see that <code>isEmpty()</code> is
-				defined in <code>List</code> and implemented in <code>ArrayList</code> and <code>Vector</code> but
-				not in <code>AbstractList</code>.
-			<p><img src="images/hierarchy-lockview.png" border="0" alt="Lock view and show members in Hierarchy">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Type Hierarchy view
-			supports grouping by defining type</b></td>
-			<td valign="top" align="left" width="80%">The type hierarchy method
-			view lets you sort the selected type's methods by its defining types.
-			For example, for <code>AbstractList</code> you can see that it contains methods
-			that were defined in Object, Collection and List:
-			<p><img src="images/sort-by-def.png"  border="0" alt="Sort members by the defining type in the type hierarchy">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Tricks in the type
-			hierarchy</b></td>
-			<td valign="top" align="left" width="80%">
-			<ul>
-				<li>Focus the type hierarchy on a new type by pressing <b>F4
-				(Navigate &gt; Open Type Hierarchy)</b> on an element or a selected
-				name.</li>
-				<li>You can open the Hierarchy view not only on types but also on
-				packages, source folders, JAR archives and Java projects.</li>
-				<li>You can Drag &amp; Drop an element onto the Hierarchy view to
-				focus on that element.</li>
-				<li>You can change the orientation (from the default vertical to
-				horizontal) of the Hierarchy view from the view's toolbar menu.</li>
-			</ul>
-			</td>
-		</tr>
-		
-		
-		<tr>
-			<td valign="top" align="left"><b>Structural compare of Java source</b>
-			</td>
-			<td valign="top" align="left">A structural comparison of Java source
-			ignores the textual order of Java elements like methods and fields
-			and shows more clearly which elements were changed, added, or removed. <br>
-			For initiating a structural comparison of Java files you have two
-			options:
-			<ul>
-				<li>Select two Java compilation units and choose <b>Compare With</b>
-				&gt; <b>Each Other</b> from the view's context menu. If the files
-				have differences, they are opened into a Compare Editor. The top
-				pane shows the differing Java elements; double clicking on one of
-				them shows the source of the element in the bottom pane.</li>
-				<li>In any context where a file comparison is involved (e.g. a CVS
-				Synchronization) a double click on a Java file not only shows the
-				content of the file in a text compare viewer, but it also performs a
-				structural compare and opens a new pane showing the results.</li>
-			</ul>
-			<p><img src="images/compare-java.png" alt="Structural compare of Java source">
-</p>
-			You can even ignore formatting changes when performing
-			the structural compare: turn on the <strong>Ignore Whitespace</strong>
-			option via the Compare Editor's toolbar button, or a compare viewer's context menu.</td>
-		</tr><tr>
-			<td valign="top" align="left"><b>Structural compare of property
-			files</b></td>
-
-			<td valign="top" align="left">A structural comparison of Java
-			property files (extension: .properties) ignores the textual order of
-			properties and shows which properties were changed, added, or
-			removed. <br>
-			For initiating a structural comparison of property files you have two
-			options:
-			<ul>
-				<li>Select two files in the Package Explorer or Navigator and choose
-				<b>Compare With</b> &gt; <b>Each Other</b> from the view's context
-				menu.</li>
-				<li>In any context where a file comparison is involved (e.g. a CVS
-				Synchronization) a double click on a property file not only shows
-				the content of the file in a text compare viewer, but it also
-				performs a structural compare and opens a new pane showing the
-				results.</li>
-			</ul>
-			<p><img src="images/compare-properties.png" alt="Structural compare of property files">
-</p>
-			</td>
-		</tr><tr>
-			<td width="20%" valign="top" align="left"><b>Hierarchical vs. flat
-			presentation of packages</b></td>
-			<td valign="top" align="left" width="80%">An option on the Java
-			Packages (and Package Explorer) view menu allows you to change the
-			way packages are displayed. <b>Package Presentation &gt; Hierarchical</b> displays packages in
-			a tree, with sub-packages below packages; <b>Package Presentation &gt; Flat</b> displays them
-			in the standard arrangement, as a flat list with all packages and
-			sub-packages as siblings.<br>
-			<table border="0">
-				<tbody>
-					<tr align="left" valign="top">
-						<td><img src="images/packages-flat.png" border="0" alt="Flat packages layout">
-</td>
-						<td><img src="images/packages-hierarchical.png" border="0" alt="Hierarchical package layout">
-</td>
-					</tr>
-				</tbody>
-			</table>
-			</td>
-		</tr><tr>
-			<td width="20%" valign="top" align="left"><b>Logical packages</b></td>
-			<td valign="top" align="left" width="80%">The Java Packages view
-			(Java Browsing perspective) coalesces packages of the same name
-			across source folders within a project. The screenshot shows the Packages view
-			containing a logical package.
-			<p><img src="images/packages-compound.png"  border="0" alt="Java browsing perspective containing a logical package" align="bottom">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Compress package names</b></td>
-			<td valign="top" align="left" width="80%">If your package names are
-			very long, you can configure a compressed name that appears in the viewers.
-			Configuration of the compression pattern is done in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.AppearancePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Appearance preference page">
-			<b>Java &gt; Appearance</b></a> preference page.
-			<p><img src="images/compress-packages1.png"  border="0" alt="Compression pattern configuration in the Java appearance preference page">
-</p>
-			Using this example, packages are rendered the following way:<p><img src="images/compress-packages2.png"  border="0" alt="Compressed package names">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Manipulating the Java
-			build path directly in the Package Explorer</b>		
-			</td>
-			<td valign="top" align="left" width="80%">Instead of manipulating the Java Build path on <b>Project
-			&gt; Properties &gt; Java Build Path</b>, use the actions in the Package Explorer's context menu.
-			<br>You can for example add new source folders, archives and libraries to the build path or in- and exclude file and folders from a source folder.
-			<p><img border="0" src="images/build-path-actions.png" 
-				alt="Build path context menu"></p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Paste code snippets to create a type</b>
-			</td>
-			<td valign="top" align="left" width="80%">You can paste a snippet of code containing a Java type directly
-			into a package or source folder to create a new compilation unit.
-			For example, select and copy this source code:
-			<pre>
-package pack;
-public class HelloWorld {
-    public static void main(String[] args) {
-        System.out.println("Hello World");
-    }
-}
-</pre>
-			Then select a source folder in the Package Explorer and use <b>Ctrl+V (Edit &gt; Paste)</b>.
-			This automatically creates a new package 'pack' and file 'HelloWorld.java' with the copied content.
-			<p>You can also paste a method or a set of statements; Eclipse will create the required enclosing
-			elements for you.</p>
-			<p>If you paste while nothing is selected in the Package Explorer, Eclipse
-			even creates a new Java Project and create the *.java file there.
-			Furthermore, the clipboard can also contain multiple package and type declarations,
-			in which case Eclipse will create all the necessary packages and *.java files on paste.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Paste patch into Package Explorer</b>
-			</td>
-			<td valign="top" align="left" width="80%">
-			What's the quickest way to apply a patch from Bugzilla? Just open the attachment,
-			copy the patch to the clipboard and paste it into the Package Explorer.
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Grouping Java problems</b>
-			
-			</td>
-			<td valign="top" align="left" width="80%">
-			Configure the Problems view to group Java problems into categories with <b>Group by &gt; Java Problem Type</b> 
-			in the view menu.
-      		<p><img border="0" alt="picture of Problems view with grouped problems" title="Problems view with grouped problems" src="images/group-problems.png"></p>
-      		You can control if a configurable error is intended to be fatal or not at the bottom of the
-      		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-			<b>Java &gt; Compiler &gt; Errors/Warnings</b></a> preference page.
-      		</td>
-		</tr>
-		<tr> 
-      		<td width="20%" valign="top" align="left"><b>Java type indicator</b>
-			
-			</td>
-      		<td valign="top" align="left" width="80%">
-      		Enable the <b>Java Type Indicator</b> on the 
-      		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Label Decoration preference page">
-			<b>General &gt; Appearance &gt; Label Decoration</b></a> preference page to find 
-          	out what the first type in a compilation unit or class file is. An adornment is shown for interfaces, annotations, and enums, while an ordinary class stays undecorated.
-        	<p><img title="Java Type Indicator Label Decorator" alt="Picture of Java Type Indicator Label Decorator" src="images/type-indicator.png"></p>
-        	</td>
-    	</tr>
-	</tbody>
-</table>
-<h3><a name="misc_section"></a>Miscellaneous</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670"
-	bgcolor="white">
-	<tbody>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Project specific
-			preferences</b></td>
-			<td valign="top" align="left" width="80%">All code style and compiler options can be defined  per project.<br>
-			Open the project property pages with <b>Project &gt; Properties</b> on a project or use the link on the workspace preferences (e.g. the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeStylePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Code Style preference page">
-			<b>Java &gt; Code Style</b></a> preference page)
-			to open a project property page and enable project specific settings.<br>
-			<p><img border="0" src="images/project-specific-settings.png"
-				alt="Project property page with 'Enable project specific settings' checkbox"></p>
-			The project specific settings are stored in a configuration file inside the project (in the '.settings' folder). When you share a project in a team, team members will also get these project specific settings.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Access rules</b><br>
-			</td>
-			<td valign="top" align="left" width="80%">Access rules give you the possibility to enforce API rules  for  types from referenced libraries. On the Java build path page (<b>Project
-			&gt; Properties &gt; Java Build Path</b>)  edit the 'Access Rules' node available on  referenced projects, archives, class folders and libraries.<br>
-			Packages or types in these references can be classified as:<ul>
-				<li>Accessible</li>
-				<li>Discouraged</li>
-				<li>Forbidden</li>
-			</ul>According to the settings on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Error/Warnings preference page">
-			<b>Java &gt; Compiler &gt; Errors/Warnings</b></a> preference page,
-			the compiler will mark discouraged and forbidden references with warning or errors.
-			<p><img border="0" src="images/type-access-rules.png" alt="Access rules configuration dialog"></p></td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>JUnit</b></td>
-			<td valign="top" align="left" width="80%">Select a JUnit test method
-			in a view and choose <b>Run &gt; JUnit Test</b> from the context menu or <b>Run
-			&gt; Run As &gt; JUnit Test</b> from the main menu. This
-			creates a launch configuration to run the selected test.</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Hide JUnit view until
-			errors or failures occur</b></td>
-
-			<td valign="top" align="left" width="80%">You can configure the JUnit view
-			to only open when there are errors or failures. To do so enable <b>Activate on Errors/Failures only</b>
-			in the JUnit view menu. That way, you can have
-			the view set as a fast view and never look at it when there are no
-			failing tests. While there are no problems in your tests you will see
-			this icon <img src="../images/org.eclipse.jdt.junit/prgss/ss4.png"  alt="Successfully running"> (the
-			number of small green squares will grow, indicating progress)
-			while running them and this icon <img src="../images/org.eclipse.jdt.junit/eview16/junitsucc.png"  alt="Successfully finished">
- after they are finished. If, however,
-			errors or failures occur, the icon will change to <img src="../images/org.eclipse.jdt.junit/prgss/ff4.png"  alt="Failure or error occurred">
- (or <img src="../images/org.eclipse.jdt.junit/eview16/juniterr.png"  alt="Finished with failure or error">
- if
-			tests are finished) and the JUnit view will appear.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Content assist in dialog fields</b>
-			</td>
-			<td>Content assist (<b>Ctrl+Space</b>) is also available in input fields
-			of various Java dialogs. Look for a small light bulb icon beside the
-			field when it has focus.
-			<p><img src="images/new-class.png"  alt="New Class Dialog">
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Smart caret positioning in dialogs showing Java names</b>
-			</td>
-			<td width="80%" valign="top" align="left">
-			Text fields for editing Java names support smart caret positioning. Use <b>Ctrl+Left</b> and <b>Ctrl+Right</b> to 
-			stop at camel case boundaries inside a name. Use <b>Ctrl+Shift+Left</b> and <b>Ctrl+Shift+Right</b> to extend the selection in small steps.
-			Use <b>Ctrl+Delete</b> to delete the next and <b>Ctrl+Backspace</b> to delete the previous part of a name.<br>
-
-		      <table border="0" cellpadding="2" cellspacing="2" width="100%">
-		        <tbody>
-		          <tr>
-		            <td valign="middle"><br>
-		            </td>
-		            <td valign="middle"><img alt="Smart caret positioning in dialog" src="images/camel-case-nav-1.png"></td>
-		          </tr>
-		          <tr>
-		            <td valign="middle"><b>Ctrl+Right:</b><br>
-		            </td>
-		            <td valign="middle"><img alt="Smart caret positioning in dialog" src="images/camel-case-nav-2.png"></td>
-		          </tr>
-		          <tr>
-		            <td valign="middle"><b>Ctrl+Shift+Right:</b><br>
-		            </td>
-		            <td valign="top"><img alt="Smart caret positioning in dialog" src="images/camel-case-nav-3.png"></td>
-		          </tr>
-		
-		          <tr>
-		            <td valign="middle"><b>write "Equal":</b><br>
-		            </td>
-		            <td valign="top"><img alt="Smart caret positioning in dialog" src="images/camel-case-nav-5.png"></td>
-		          </tr>
-		          <tr>
-		            <td valign="middle"><b>Ctrl+Delete:</b><br>
-		            </td>
-		
-		            <td valign="top"><img alt="Smart caret positioning in dialog" src="images/camel-case-nav-6.png"></td>
-		          </tr>
-		          <tr>
-		            <td valign="middle"><b>write "To":</b><br>
-		            </td>
-		            <td valign="top"><img alt="Smart caret positioning in dialog" src="images/camel-case-nav-7.png"></td>
-		          </tr>
-		        </tbody>
-		
-		      </table>
-
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Define prefixes or
-			suffixes for fields, parameters and local variables</b></td>
-			<td valign="top" align="left" width="80%">You can configure
-			the prefix or suffix for fields, static fields, parameters, and local variables. 
-			These settings on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeStylePreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Code Style preference page">
-			<b>Java &gt; Code Style</b></a> preference page are used
-			in content assist, quick fix, and refactoring whenever a variable
-			name is computed.
-			<p><img src="images/name-conventions.png"  border="0" alt="Name conventions in the code style preference page">
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Organize Imports works
-			on more than single files</b></td>
-			<td valign="top" align="left" width="80%">You can invoke <b>Source &gt; Organize
-			Imports</b> on sets of compilation units, packages, source folders or
-			Java projects.</td>
-		</tr>
-		  <tr>
-		    <td valign="top" align="left"><b>Organize imports on save</b>
-		    </td>
-		    <td>Eclipse can automatically organize imports whenever you save an editor.
-		        This feature can be enabled globally on the
-		        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.SaveParticipantPreferencePage)")'> 
-		          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Save Actions preference page">
-		          <b>Java &gt; Editor &gt; Save Actions</b></a> preference page.
-		        The save actions can also be configured per project, which
-		        makes it easy to enforce a project-wide standard by sharing
-		        the settings across a team:
-		      <p> <img src="images/organize-imports-on-save.png" alt="Save Action property page"> </p>
-		      <p>Besides organizing imports, save actions can also format code and
-		      perform other clean ups.</p>
-			 </td>
-		  </tr>
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Format selection</b></td>
-			<td valign="top" align="left" width="80%">Select multiple
-			Java files to format and choose <b>Source &gt; Format</b> to format them
-			all. The format action is also available on packages, source folders
-			or Java projects.
-			<p>
-			In the Java Editor, <b>Source &gt; Format (Ctrl+Shift+F)</b> formats just
-			the selected region. If nothing is selected, the whole file gets formatted.
-			</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Select execution environment 
-				for Java project</b>
-			</td>
-			<td>When you create a Java project that you want
-				to share with a team, it is a good idea to use an execution environment
-				instead of a specific JRE.
-			<p> Execution environments are symbolic representations of JREs with standardized
-			entries like 'J2SE-1.4', 'J2SE-1.5'. That means no file system path will
-			go into the shared build path.</p>
-			<p>JREs can be assigned to the environments on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.jreProfiles)")'> 
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Execution Environments preference page">
-			<b>Java &gt; Installed JREs &gt; Execution Environments</b></a> preference page.</p>
-			<p> <img alt="Screenshot of the 'New Java Project' wizard" src="images/new-project-with-ee.png"></p>
-			
-			<p>To set a project specific JRE of an existing project, open the
-			project's Java Build path property page <b>(Project &gt; Properties &gt; Java Build Path)</b>, then the<b> Libraries</b> page, select
-			'JRE System Library' and press <b>Edit</b>. In the 'Edit Library' dialog you can select either an Execution Environment, a project specific
-			JRE, or the workspace default JRE.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Use drag and drop</b></td>
-			<td valign="top" align="left" width="80%">
-			Drag and Drop is a handy replacement of <b>Edit &gt; Cut</b> and <b>Edit &gt; Paste</b> 
-			, or <b>Edit &gt; Copy</b> and <b>Edit &gt; Paste</b>. Hold
-			down the <b>Ctrl</b> key while dropping to change from move to copy.
-			<p>Important to know:</p>
-			<ul>
-			<li>If you move Java
-			compilation units between packages by Drag &amp; Drop, this will behave like a refactoring move - all missing
-			imports will be added and references updated
-			</li>
-			<li>
-			If you drag and drop source elements like types or methods, this will only copy or move the corresponding
-			source code - no references will be updated
-			</li>
-			</ul>
-			</td>
-		</tr>		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Propagating deprecation
-			tag</b></td>
-			<td width="80%" valign="top" align="left">
-			The Java compiler can be configured to diagnose deprecation using 
-			options on the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Error/Warnings preference page">
-			<b>Java &gt; Compiler &gt; Errors/Warnings</b></a> preference page.
-			<p><img src="images/warn-deprecation-opt.png"  border="0" alt="Compiler preference page">
-</p>
-			Using this configuration, the result is:
-			<p><img src="images/warn-deprecation-i.png"  border="0" alt="I.java"></p>
-			<p><img src="images/warn-deprecation-x.png"  border="0" alt="X.java"></p>
-			<p><img src="images/warn-deprecation-y.png"  border="0" alt="Y.java"></p>
-			If you're unable to fix a usage of a deprecated construct, we recommend that you
-			tag the enclosing method, field or type as deprecated.
-			This way, you acknowledge that you did override a deprecated construct,
-			 and the deprecation flag is propagated to further dependents.
-			<p><img src="images/warn-deprecation-x2.png"  border="0" alt="X.java"></p>
-			<p><img src="images/warn-deprecation-y2.png"  border="0" alt="Y.java"></p></td>
-		</tr>
-		
-
-		
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Recovering from abnormal
-			inconsistencies</b></td>
-			<td width="80%" valign="top" align="left">
-			In the rare event of a dysfunction, JDT could reveal some inconsistencies
-			such as:
-			<ul>
-				<li>missing results in a <b>Java Search</b> or <b>Open Type</b></li>
-				<li>invalid items in Package Explorer</li>
-			</ul>
-			<br>
-			To bring JDT into a consistent state again, the following actions need to be performed
-			in this exact order:
-			<ol>
-			<li>Close all projects using navigator <b>Close Project</b> menu action</li>
-			<li>Exit and restart Eclipse</li>
-			<li>Open all projects using navigator <b>Open Project</b> menu action</li>
-			<li>Manually trigger a clean build of entire workspace (<b>Project &gt;
-			 Clean...</b>)</li>
-			</ol>
-			</td>
-		</tr>
-	</tbody>
-</table>
-
-<h3><a name="debugging_section"></a>Debugging</h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670"
-	bgcolor="white">
-	<tbody>
-	<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Launching from the context menu</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			<p>You can run and debug Java applications from the context menu.
-			You can launch a source file, package, method, type, etc. by
-			choosing <b>Run As</b> (or <b>Debug As</b>)<b> &gt; Java Application</b>
-			from the context menu in a view or editor. Alternatively, you can
-			use the Java application launch shortcut key binding (<b>Alt+Shift+D, J</b>). The
-			top level <b>Run As</b> (or <b>Debug As</b>) actions are also
-			sensitive to the current selection or active editor.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/context_menu_launch.png"  alt="Context menu with launch option">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Evaluations in the
-			debugger</b></td>
-			<td width="80%" valign="top" align="left">
-			<p>Snippet evaluation is available from a number of places in the
-			debugger. Choosing <b>Display</b> or <b>Inspect</b> from the context
-			menu of the editor or <b>Variables view</b> will show the result in a
-			pop-up whose result can be sent to the <b>Display</b> or <b>Expressions
-			views</b>.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/inspect_popup.png"  alt="Result of an inspect in a pop-up">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>View management in non-Debug perspectives</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>The Debug view automatically manages debug related views based on the view selection 
-        (displaying Java views for Java stack frames and C views for C stack frames, 
-        for example). By default, this automatic view management only occurs in 
-        the Debug perspective, but you can enable it for other perspectives via 
-        the <b>View Management</b> preference page available from the <b>Debug 
-        view</b> toolbar pull down.</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Environment variables</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>You can specify the environment used to launch Java applications via 
-          the <b>Environment</b> tab.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/env_tab.png"  alt="Environment tab in the launch configuration dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>String substitutions</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>Variables are supported for many parameters of Java Application launch 
-          configurations. Most fields that support variables have a <b>Variables...</b> 
-          button next to them, such as the program and VM arguments fields. The 
-          <b>Main Type</b> field supports variables as well; the <i>${java_type_name}</i> 
-          variable allows you to create a configuration that will run the selected 
-          type.</p>
-		<p><img src="images/org.eclipse.jdt.debug.ui/args_tab.png"  alt="Arguments tab in the launch configuration dialog">
-		</p>
-			</td>
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Logical structures</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			
-      <p>The <b>Logical Structures</b> toggle on the <b>Variables view</b> toolbar 
-        presents alternate structures for common types. JDT provides logical views 
-        for Maps, Collections, and SWT Composites. You can define
-        logical structures for other types from the <b>Logical Structures</b>
-        preference page.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/logical_structure_toggle.png"  alt="Vector displayed as a logical structure in the variable view">
-</p>
-			</td>
-			
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left">
-      <p><b>Default VM arguments</b></p>
-    </td>
-			<td width="80%" valign="top" align="left">
-			<p>If you specify the same arguments to a certain VM frequently,
-			you can configure <b>Default VM Arguments</b> in the <b>Installed JREs</b>
-			preference page. This is more convenient than specifying them for
-			each launch configuration.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/def_vm_args.png"  alt="JRE preference page with default argument specified">
-</p>
-			</td>
-			
-		</tr>
-		<tr>
-			<td width="20%" valign="top" align="left"><b>Stop in main</b></td>
-			<td width="80%" valign="top" align="left">
-			You can use <b>Stop in main </b>in a Java Application launch
-			configuration to cause your program to stop at the first executable
-			line of the main method when you run it under debug mode.
-
-			<p><img src="images/org.eclipse.jdt.debug.ui/stop_in_main.png"  alt="Main tab with Stop in Main option selected">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Conditional breakpoints</b></td>
-			<td valign="top" align="left">You can use conditional breakpoints in
-			<b> Breakpoint Properties... </b>to control when a breakpoint
-			actually halts execution. You can specify whether you want the
-			breakpoint to suspend execution only when the condition is true, or
-			when the condition value changes.
-			<p><img src="images/org.eclipse.jdt.debug.ui/breakpoint_condition.png"  alt="Breakpoint condition editor in breakpoint properties dialog"></p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Disabling breakpoints</b></td>
-			<td valign="top" align="left">
-			If you find yourself frequently adding and removing a breakpoint
-			in the same place, consider disabling the breakpoint when you don't
-			need it and enabling it when needed again. This can be done using <b>Disable
-			Breakpoint </b>in the breakpoint context menu or by unchecking the
-			breakpoint in the <b>Breakpoints view</b>.
-			<p>You can also temporarily disable all breakpoints using the <b>Skip
-			All Breakpoints</b> action in the <b>Breakpoints view</b> toolbar.
-			This will tell the debugger to skip all breakpoints while maintaining
-			their current enabled state.</p>
-			<p><img src="images/org.eclipse.jdt.debug.ui/breakpoint_menu.png"  alt="Disable Breakpoint action in the ruler context menu">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Changing variable values</b></td>
-			<td valign="top" align="left">
-			
-      When a thread is suspended in the debugger, you can change the values 
-        of Java primitives and Strings in the <b>Variables</b> view. From the 
-        variable's context menu, choose <b>Change Variable Value</b>. You can 
-        also change the value by typing a new value into the Details pane and 
-        using the <strong>Assign Value </strong>action in the context menu (<b>CTRL+S</b> 
-        key binding).
-
-			<p><img src="images/org.eclipse.jdt.debug.ui/assign_value.png"  alt="Change variable value from detail pane">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Variable values in hover help</b></td>
-			<td valign="top" align="left">When a thread is suspended and the
-			cursor is placed over a variable in the Java editor, the value of
-			that variable is displayed as hover help.
-			<p><img src="images/org.eclipse.jdt.debug.ui/variable_hover.png"  alt="Variable value hover in the editor">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Drop to frame</b></td>
-			<td valign="top" align="left">
-			When stepping through your code, you might occasionally step too
-			far, or step over a line you meant to step into. Rather than
-			restarting your debug session, you can use the <b>Drop to Frame</b>
-			action to quickly go back to the beginning of a method. Select the
-			stack frame corresponding to the Java method you wish to restart, and
-			select <b>Drop to Frame</b> from <b>Debug view</b> toolbar or the
-			stack frame's context menu. The current instruction pointer will be
-			reset to the first executable statement in the method. This works for
-			non-top stack frames as well.
-			<p>Note that Drop to frame is only available when debugging with a
-			1.4 or higher VM, or the J9 VM. There are some situations where a JVM
-			may be unable to pop the desired frames from the stack. For example,
-			it is generally impossible to drop to the bottom frame of the stack
-			or to any frame below a native method.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Hot code replace</b></td>
-			
-    <td valign="top" align="left">The debugger supports Hot Code Replace when 
-      debugging with a 1.4 or higher VM, or the J9 VM. This lets you make changes 
-      to code you are currently debugging. Note that some changes such as new 
-      or deleted methods, class variables or inner classes cannot be hot swapped, 
-      depending on the support provided by a particular VM.</td>
-		</tr>
-		<tr>
-			
-      <td valign="top" align="left"><b>Stepping into selections and hyperlink 
-        debugging </b></td>
-			<td valign="top" align="left">
-			The Java debugger allows you to step into a single method within a
-			series of chained or nested method calls. Simply highlight the method
-			you wish to step into and select <b>Step into Selection</b> from the
-			Java editor context menu.
-			<p>This feature works in places other than the currently executing
-			line. Try debugging to a breakpoint and step into a method a few
-			lines below the current instruction pointer.</p>
-
-			
-        <p><img src="images/org.eclipse.jdt.debug.ui/step_into_selection.png"
-				alt="Stepping into selection"></p>
-        <p>You can also step into a method by using hyperlink navigation. Simply 
-          place the cursor over the method you wish to step into and use <strong>Ctrl+Alt+Click</strong> 
-          to step into the method (rather than <strong>Ctrl+Click</strong> which 
-          will navigate to the source code).</p>
-        <p><b><img src="images/org.eclipse.jdt.debug.ui/hyperlink_step.png" alt="Use Ctrl+Alt+Click to step into a method hyperlink"></b></p>
-        </td>
-		</tr>
-		<tr>
-			
-      <td valign="top" align="left"><b>Console pin and lock</b></td>
-      <td valign="top" align="left">Output displayed in the console can be locked 
-        to a specific process via the <strong>Pin Console</strong> action in the 
-        Console view toolbar. There's also a <strong>Scroll Lock </strong>action 
-        that stops the console from scrolling as new output is appended.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Creating watch items</b></td>
-			
-    <td valign="top" align="left">A watch item is an expression in the <b>Expressions</b> 
-      view whose value is updated as you debug. You can create watch items from 
-      the Java editor by selecting an expression or variable and choosing <b>Watch</b> 
-      from its context menu or the top-level <b>Run</b> menu.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Watch points</b></td>
-			<td valign="top" align="left">
-			
-      A watch point is a breakpoint that suspends execution whenever a specified 
-          field is accessed or modified. To set a watchpoint, select a field in 
-          the Outline view and choose <b>Toggle Watchpoint</b> from its context 
-          menu. To configure a watchpoint, select the watchpoint in the <b>Breakpoints</b> 
-          view and choose <b>Properties...</b> from its context menu. The most 
-          important properties for this type of breakpoint are the <b>Access</b> 
-          and <b>Modification</b> checkboxes which control when the breakpoint 
-          can suspend execution.
-			<p><img src="images/org.eclipse.jdt.debug.ui/watchpoint_properties.png"  alt="Breakpoint properties dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-
-			<td valign="top" align="left"><b>Threads and monitors</b></td>
-			<td valign="top" align="left">
-			The Java debugger optionally displays monitor information
-			in the <b>Debug</b> view. Use the <b>Show Monitors</b> action in the
-			Debug view drop down menu to show which	threads are holding locks and
-			which are waiting to acquire locks. Threads involved in a deadlock
-			are rendered in red.
-			<p><img src="images/org.eclipse.jdt.debug.ui/deadlock.png"
-				alt="Debug view showing deadlock cycles"></p>
-
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Step filters</b></td>
-			
-    <td valign="top" align="left">Step filters prevent the debugger from suspending 
-      in specified classes and packages when stepping into code. Step filters 
-      are established with the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaStepFilterPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Step Filtering preference page">
-      <b>Java &gt; Debug &gt; Step Filtering</b></a> preference page.
-      When the <b>Use Step Filters</b> toggle (on the debug 
-      toolbar and menu) is on, step filters are applied to all step actions. In 
-      the Debug view, the selected stack frame's package or declaring type can 
-      be quickly added to the list of filters by selecting <b>Filter Type</b> 
-      or <b>Filter Package</b> from the stack frame's context menu.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Using the scrapbook</b></td>
-			<td valign="top" align="left">
-			
-      If you want to experiment with API or test out a new algorithm, it's 
-        frequently easier to use a Java scrapbook page than create a new class. 
-        A scrapbook page is a container for random snippets of code that you can 
-        execute at any time without a context. To create a scrapbook page, create 
-        a new file with a <strong>.jpage</strong> extension (or use the
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.jdt.debug.ui.snippetEditor.NewSnippetFileCreationWizard)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the New Scrapbook wizard">
-        <b>New Scrapbook Page</b></a> wizard).
-        Enter whatever code you wish to execute and then select it. There are three 
-        ways to execute your code:
-
-			<ul>
-				
-          <li>Execute the selected code and place the returned result in an inspect 
-            popup</li>
-				<li>Execute the selected code and place the String result right in
-				the scrapbook page
-				<p><img src="images/org.eclipse.jdt.debug.ui/scrapbook.png"  alt="Scrapbook page displaying result">
-</p>
-				</li>
-				<li>Execute the selected code (and ignore any returned result)</li>
-			</ul>
-			<p>These actions are in the workbench toolbar and also in the
-			scrapbook page's context menu.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Editing<br>
-			launch<br>
-			configurations</b></td>
-			<td valign="top" align="left">Holding down the <b>Ctrl</b> key and
-			making a selection from the <b>Run</b> or <b>Debug</b> drop-down menu
-			opens the associated launch configuration for editing. The launch
-			configuration can also be opened from the context menu associated
-			with any item in the Debug view.</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Favorite launch configurations</b></td>
-			<td valign="top" align="left">
-			
-        Launch configurations appear in the Run/Debug drop-down menus in most 
-        recently launched order. However it is possible to force a launch configuration 
-        to always appear at the top of the drop-downs by making the configuration 
-        a 'favorite'. Use the <strong>Organize Favorites...</strong> action from 
-        the appropriate drop down menu to configure your favorite launch configurations.
-
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Detail formatters</b></td>
-			<td valign="top" align="left">
-			In the <b>Variables</b> &amp; <b>Expressions</b> views, the detail
-			pane shows an expanded representation of the currently selected
-			variable. By default, this expanded representation is the result of
-			calling <code>toString()</code> on the selected object, but you can create
-			a custom detail formatter that will be used instead by choosing <b>New
-			Detail Formatter</b> from the variable's context menu. This detail
-			formatter will be used for all objects of the same type. You can view
-			and edit all detail formatters in the
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaDetailFormattersPreferencePage)")'>
-			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Detail Formatters preference page">
-			<b>Java &gt; Debug &gt; Detail Formatters</b></a> preference page.
-			<p><img src="images/org.eclipse.jdt.debug.ui/detail_formatter.png"  alt="Detail formatter dialog">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Running code with compile errors</b></td>
-			<td valign="top" align="left">
-			You can run and debug code that did not compile cleanly. The only
-			difference between running code with and without compile errors is
-			that if a line of code with a compile error is executed, one of two
-			things will happen:
-			<ul>
-				<li>If the 'Suspend execution on compilation errors' preference on the
-				<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.JavaDebugPreferencePage)")'>
-				<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Debug preference page">
-				<b>Java &gt; Debug</b></a> preference page is set and you are
-				debugging, the debug session will suspend as if a breakpoint had
-				been hit. Note that if your VM supports Hot Code Replace, you could
-				then fix the compilation error and resume debugging</li>
-				<li>Otherwise, execution will terminate with a 'unresolved
-				compilation' error</li>
-			</ul>
-			<p>It is important to emphasize that as long as your execution path
-			avoids lines of code with compile errors, you can run and debug just
-			as you normally do.</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Word wrap in Variables view</b></td>
-			<td valign="top" align="left">The details area of the debugger's <b>Variables</b>
-			and <b>Expressions</b> views supports word wrap, available from the
-			view drop-down menu.
-			<p><img src="images/org.eclipse.jdt.debug.ui/word_wrap.png"  alt="Word wrap action in Variables view drop-down menu">
-</p>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Code assist in the debugger</b></td>
-			<td valign="top" align="left">
-			Code assist is available in many contexts beyond writing code in
-			the Java editor:
-			
-        <ul>
-          <li>When entering a <b>breakpoint condition</b></li>
-          <li>In the <b>Details</b> pane of the <b>Variables</b> &amp; <b>Expressions</b> 
-            view</li>
-          <li>When entering a <b>Detail Formatter</b> code snippet</li>
-          <li>When entering a <b>Logical Structure</b> code snippet</li>
-          <li>When entering code in a <b>Scrapbook</b> page</li>
-          <li>In the <b>Display</b> view</li>
-        </ul>
-			</td>
-		</tr>
-		<tr>
-			<td valign="top" align="left"><b>Command line details</b></td>
-
-			<td valign="top" align="left">You can always see the exact command
-			line used to launch a program in run or debug mode by selecting <b>Properties</b>
-			from the context menu of a process or debug target, even if the
-			launch has terminated.
-			<p><img src="images/org.eclipse.jdt.debug.ui/process_properties.png"  alt="Command line details"></p>
-			</td>
-		</tr>
-		<tr>
-          <td valign="top" align="left"><b>Stack trace<br>
-            hyperlinks</b></td>
-		  <td valign="top" align="left"> Java stack traces in the console appear with hyperlinks. When you place 
-		    the mouse over a line in a stack trace the pointer changes to the hand.
-		    Pressing the mouse button opens the 
-		    associated Java source file and positions the cursor at the corresponding 
-		    line. Pressing the mouse button on the exception name at the top of the 
-		    stack trace will create an exception breakpoint.
-		    <p><img src="images/org.eclipse.jdt.debug.ui/stack_trace.png"  alt="Stack traces in Console view with hyperlinks"> </p></td>
-	  </tr>
-		<tr>
-			<td valign="top" align="left"><b>Debugging in the Java perspective </b></td>
-			<td valign="top" align="left">
-			
-        You can debug in the Java perspective by configuring the <strong>Run/Debug &gt; View Management</strong> preferences. Select the perspectives you want to be debug from.
-        <p><img src="images/org.eclipse.jdt.debug.ui/view-mngmt.png" alt="View Management preference page"></p>
-        <p>Ensure the preference to activate the debug view when a breakpoint is hit is turned on (via the top level <strong>Run/Debug</strong> preference page).</p>
-        <p><img src="images/org.eclipse.jdt.debug.ui/activate-debug-view.png" alt="Run/Debug preference page" > </p>
-        <p>You can disable the perspective switching prompt on the <strong>Run/Debug &gt; Perspectives</strong> preference page. With these settings the Debug view will automatically open in the Java perspective when a breakpoint is hit. </p>
-        <p><img src="images/org.eclipse.jdt.debug.ui/perspective-prompt.png" alt="Perspectives preference page" > </p>
-        <p>By placing the Debug view at the top of the perspective and resizing it's height to the size of one element, the view will switch to a bread crumb presentation. This minimizes the amount of screen space the view consumes.</p>
-        <p><img src="images/org.eclipse.jdt.debug.ui/dbg-bread-crumb.png" alt="Debug view in bread crumb mode" ></p></td>
-		</tr>
-	</tbody>
-</table>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.jdt.doc.user/toc.xml b/bundles/org.eclipse.jdt.doc.user/toc.xml
deleted file mode 100644
index 9b1e3bb..0000000
--- a/bundles/org.eclipse.jdt.doc.user/toc.xml
+++ /dev/null

@@ -1,31 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="Java development user guide">
-    <topic label="Java development overview" href="gettingStarted/intro/overview.htm"/>
-	<topic label="Getting Started">
-		<link toc="topics_GettingStarted.xml" />
-	</topic>
-	<anchor id="jdt_getstart" />
-	<topic label="Concepts">
-		<link toc="topics_Concepts.xml" />
-	</topic>
-	<anchor id="jdt_concepts" />
-	<topic label="Tasks">
-		<link toc="topics_Tasks.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<anchor id="jdt_reference" />
-	
-	<topic label="Tips and tricks" href="tips/jdt_tips.html"/>
-	<topic label="What's new" href="whatsNew/jdt_whatsnew.html"/>
-	<topic label="Legal" href="notices.html"/>
-	<enablement>
-		<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.jdt.ui"/>
-	</enablement>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml b/bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml
deleted file mode 100644
index e9e82ca..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_Concepts.xml
+++ /dev/null

@@ -1,54 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Concepts -->
-<!-- ========================== -->
-<toc label="Concepts" href="concepts/concept-jdt.htm" >
-   <!-- <topic label="Overview" href="concepts/concept-jdt.htm"/> -->
-   <topic label="Java Projects" href="concepts/concept-java-project.htm"/>
-   <anchor id="c_javaprojects" />
-   <topic label="Java Builder" href="concepts/concept-java-builder.htm">
-      <anchor id="c_javabuilder" />
-      <topic label="Build Classpath" href="concepts/concept-build-classpath.htm">
-         <anchor id="c_buildclasspath" />
-         <topic label="Inclusion and Exclusion Patterns" href="concepts/concept-inclusion-exclusion-patterns.htm" />
-         <anchor id="c_filters" />
-         <topic label="Access Rules" href="concepts/concept-access-rules.htm" />
-         <anchor id="c_restrict" />
-         <topic label="Classpath Variables" href="concepts/concept-classpath-variables.htm" />
-         <anchor id="c_classpathvariables" />
-      </topic>
-   </topic>
-   <topic label="Java Perspectives" href="concepts/concept-java-perspective.htm"/>
-   <anchor id="c_javaperspective" />
-   <topic label="Java Views" href="concepts/concept-java-views.htm">
-      <anchor id="c_javaviews" />
-      <topic label="Filtering in Java Views" href="concepts/concept-java-views-filtering.htm"/>
-      <topic label="Sorting in Java Views" href="concepts/concept-java-views-sorting.htm"/>
-      <topic label="Java Element Decorations" href="concepts/concept-java-views-decorators.htm"/>
-      <topic label="Presentation Options for Java Views" href="concepts/concept-java-views-presentation.htm"/>
-   </topic>
-   <topic label="Java Editor" href="concepts/concept-java-editor.htm"/>
-   <anchor id="c_javaeditor" />
-   <topic label="Quick Fix and Assist" href="concepts/concept-quickfix-assist.htm"/>
-   <anchor id="c_quickfix" />   
-   <topic label="Templates" href="concepts/concept-editor-templates.htm" />
-   <anchor id="ctemplates" />
-   <topic label="Java Search" href="concepts/concept-java-search.htm"/>
-   <anchor id="c_javasearch" />
-   <topic label="Refactoring Support" href="concepts/concept-refactoring.htm"/>
-   <anchor id="c_refactoring" />
-   <topic label="Debugger" href="concepts/cdebugger.htm"/>
-   <anchor id="c_debugger" />
-   <topic label="Scrapbook" href="concepts/cscrapbook.htm"/>
-   <anchor id="c_scrapbook" />
-   <topic label="Local Debugging" href="concepts/clocdbug.htm" />
-   <anchor id="c_localdebug" />
-   <topic label="Remote Debugging" href="concepts/cremdbug.htm" />
-   <anchor id="c_remotedebug" />
-   <topic label="Breakpoints" href="concepts/cbrkpnts.htm" />
-   <anchor id="c_breakpoints" />
-   <topic label="String Externalization" href="concepts/concept-string-externalization.htm" />
-   <anchor id="c_nls" />
-  
-</toc>

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml b/bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml
deleted file mode 100644
index 2bf128d..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_GettingStarted.xml
+++ /dev/null

@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the GettingStarted -->
-<!-- ========================== -->
-<toc label="GettingStarted">
-   <topic label="Basic tutorial" href="gettingStarted/qs-BasicTutorial.htm"> 
-	   <topic label="Preparing Eclipse" href="gettingStarted/qs-2.htm"/>
-	   <topic label="Creating your first Java project" href="gettingStarted/qs-3.htm"/>
-	   <topic label="Browsing Java elements using the package explorer" href="gettingStarted/qs-4.htm"/>
-	   <topic label="Editing Java elements"> 
-		   <topic label="Opening a Java editor" href="gettingStarted/qs-OpenJavaEditor.htm"/>
-		   <topic label="Using quick views" href="gettingStarted/qs-Quickviews.htm" />
-		   <topic label="Adding new methods" href="gettingStarted/qs-AddMethod.htm"/>
-		   <topic label="Using content assist" href="gettingStarted/qs-ContentAssist.htm"/>
-		   <topic label="Identifying problems in your code" href="gettingStarted/qs-7.htm"/>
-		   <topic label="Using code templates" href="gettingStarted/qs-EditorTemplates.htm"/>
-		   <topic label="Organizing import statements" href="gettingStarted/qs-OrganizeImports.htm"/>
-		   <topic label="Using the local history" href="gettingStarted/qs-LocalHistory.htm"/>
-		   <topic label="Extracting a new method" href="gettingStarted/qs-ExtractMethod.htm"/>
-	   </topic>
-	   
-	   <topic label="Creating a Java class" href="gettingStarted/qs-9.htm"/>
-	   <topic label="Renaming Java elements" href="gettingStarted/qs-8.htm"/>
-	   <topic label="Moving and copying Java elements" href="gettingStarted/qs-10.htm"/>
-	   
-	   <topic label="Navigate to a Java element's declaration" href="gettingStarted/qs-Navigate.htm"/>
-	   <topic label="Viewing the type Hierarchy" href="gettingStarted/qs-6.htm"/>
-	   
-	   <topic label="Searching the workbench" href="gettingStarted/qs-11.htm"/>
-	   
-	   <topic label="Running your programs" href="gettingStarted/qs-12.htm"/>
-	   <topic label="Debugging your programs" href="gettingStarted/qs-13.htm"/>
-	   <topic label="Evaluating expressions" href="gettingStarted/qs-14.htm"/>
-	   <topic label="Evaluating snippets" href="gettingStarted/qs-15.htm"/>
-	   
-	   <topic label="Using the Java browsing perspective" href="gettingStarted/qs-Browsing.htm"/>
-	   
-	   <topic label="Writing and running JUnit tests" href="gettingStarted/qs-junit.htm"/>
-   </topic>
-   
-   <topic label="Project configuration tutorial" href="gettingStarted/qs-ProjectConfiguration.htm">
-	   <topic label="Detecting existing layout" href="gettingStarted/qs-DetectingExistingLayout.htm"/>
-	   <topic label="Organizing sources" href="gettingStarted/qs-OrganizingSources.htm"/>
-	   <topic label="Sibling products in a common source tree" href="gettingStarted/qs-WorkingWithExistingLayout1.htm"/>
-	   <topic label="Overlapping products in a common source tree" href="gettingStarted/qs-WorkingWithExistingLayout2.htm"/>
-	   <topic label="Product with nested tests" href="gettingStarted/qs-WorkingWithExistingLayout3.htm"/>
-	   <topic label="Products sharing a common source framework" href="gettingStarted/qs-WorkingWithExistingLayout4.htm"/>
-	   <topic label="Product nesting resources in output directory" href="gettingStarted/qs-WorkingWithExistingLayout5.htm"/>
-	   <topic label="Project using a source framework with restricted access" href="gettingStarted/qs-WorkingWithExistingLayout6.htm"/>
-   </topic>
-
-   <topic label="Eclipse and J2SE 5.0" href="gettingStarted/qs-with-j2se50.htm">
-   </topic>
-   <anchor id="javagetstart" />
-</toc>

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_Reference.xml b/bundles/org.eclipse.jdt.doc.user/topics_Reference.xml
deleted file mode 100644
index e805761..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_Reference.xml
+++ /dev/null

@@ -1,467 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<toc label="Reference">
-<!--
-	Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains 					this page.
-
-	All topics that fall under the reference section of the help system are defined here.
-	Topics are laid out in the order that they appear in the help system. Main topics are
-	ordered alphabetically (those with subtopics), trailing that are additional topics (those without
-	subtopics), which are also in alphabetical order.
--->
-<!--
-	Breakpoints
--->
-	<topic label="Breakpoints" href="concepts/cbrkpnts.htm">
-		<topic label="Condition Option" href="reference/breakpoints/ref-condition_option.htm"/>
-		<topic label="Enabled Option" href="reference/breakpoints/ref-enabled_option.htm"/>
-		<topic label="Exception Breakpoint Caught Option" href="reference/breakpoints/ref-caught_option.htm" />
-		<topic label="Exception Breakpoint Suspend on Subclass Option" href="reference/breakpoints/ref-suspendsubclass_option.htm"/>
-		<topic label="Exception Breakpoint Uncaught Option" href="reference/breakpoints/ref-uncaught_option.htm" />
-		<topic label="Hit Count Option" href="reference/breakpoints/ref-hitcount_option.htm" />
-		<topic label="Method Breakpoint Entry Option" href="reference/breakpoints/ref-entry_option.htm" />
-		<topic label="Method Breakpoint Exit Option" href="reference/breakpoints/ref-exit_option.htm" />
-		<topic label="Suspend Policy Option" href="reference/breakpoints/ref-suspendpolicy_option.htm"/>
-		<topic label="Watchpoint Modification Option" href="reference/breakpoints/ref-modification_option.htm" />
-		<topic label="Watchpoint Access Option" href="reference/breakpoints/ref-access_option.htm" />
-	</topic>
-<!--
-	Actions
--->
-	<topic label="Menus and Actions" href="reference/ref-jdt-actions.htm">
-		<topic label="File Menu Actions" href="reference/ref-menu-file.htm" />
-		<topic label="Edit Menu Actions" href="reference/ref-menu-edit.htm" />
-		<topic label="Source Menu Actions" href="reference/ref-menu-source.htm" />
-		<topic label="Refactor Menu Actions" href="reference/ref-menu-refactor.htm" />
-		<topic label="Navigate Menu Actions" href="reference/ref-menu-navigate.htm" />
-		<topic label="Search Menu Actions" href="reference/ref-menu-search.htm" />
-		<topic label="Project Menu Actions" href="reference/ref-menu-project.htm" />
-		<topic label="Run Menu Actions" href="reference/menus/run/ref-menu-run.htm" />
-		<topic label="Java Toolbar Actions" href="reference/ref-actions-toolbar.htm"/>
-		<topic label="Run and Debug Toolbar Actions" href="reference/ref-toolbar-run.htm" />
-		<topic label="Java Editor Actions" href="reference/views/ref-java-editor.htm" />
-	</topic>
-	
-<!--
-	Preferences
--->
-	<topic label="Preferences" >
-		<topic label="Java" href="reference/preferences/ref-preferences-java.htm" >
-			<topic label="Appearance" href="reference/preferences/java/ref-preferences-appearance.htm">
-				<topic label="Member Sort Order" href="reference/preferences/java/appearance/ref-preferences-member-sort-order.htm" />
-				<topic label="Type Filters" href="reference/preferences/java/appearance/ref-preferences-type-filters.htm" />
-			</topic>
-			<topic label="Build Path" href="reference/preferences/java/ref-preferences-build-path.htm">
-			<topic label="Classpath Variables" href="reference/preferences/java/buildpath/ref-preferences-classpath-variables.htm" />
-				<topic label="User Libraries" href="reference/preferences/java/buildpath/ref-preferences-user-libraries.htm" />
-			</topic>
-			<topic label="Code Style" href="reference/preferences/java/ref-preferences-code-style.htm">
-			    <topic label="Clean Up" href="reference/preferences/java/codestyle/ref-preferences-cleanup.htm" />
-				<topic label="Code Templates" href="reference/preferences/java/codestyle/ref-preferences-code-templates.htm" />
-				<topic label="Formatter" href="reference/preferences/java/codestyle/ref-preferences-formatter.htm" />
-				<topic label="Organize Imports" href="reference/preferences/java/codestyle/ref-preferences-organize-imports.htm" />
-			</topic>
-			<topic label="Compiler" href="reference/preferences/java/ref-preferences-compiler.htm">
-				<topic label="Building" href="reference/preferences/java/compiler/ref-preferences-building.htm" />
-				<topic label="Errors/Warnings" href="reference/preferences/java/compiler/ref-preferences-errors-warnings.htm" />
-				<topic label="Javadoc" href="reference/preferences/java/compiler/ref-preferences-javadoc.htm" />
-				<topic label="Task Tags" href="reference/preferences/java/compiler/ref-preferences-task-tags.htm" />
-			</topic>
-			<topic label="Debug" href="reference/preferences/java/debug/ref-debug.htm">
-				<topic label="Detail Formatters" href="reference/preferences/java/debug/ref-detail_formatters.htm"/>
-				<topic label="Heap Walking" href="reference/preferences/java/debug/ref-heap_walking.htm"/>
-				<topic label="Logical Structures" href="reference/preferences/java/debug/ref-logical_structures.htm"/>
-				<topic label="Primitive Display Options" href="reference/preferences/java/debug/ref-primitive_display_options.htm"/>
-				<topic label="Step Filtering" href="reference/preferences/java/debug/ref-step_filtering.htm"/>
-			</topic>
-			<topic label="Editor" href="reference/preferences/java/ref-preferences-editor.htm" >
-	  			<topic label="Content Assist" href="reference/preferences/java/editor/ref-preferences-content-assist.htm">
-	  				<topic label="Advanced" href="reference/preferences/java/editor/ref-preferences-content-assist-advanced.htm" />
-	  				<topic label="Favorites" href="reference/preferences/java/editor/ref-preferences-content-assist-favorites.htm" />
-	  			</topic>
-	  			<topic label="Folding" href="reference/preferences/java/editor/ref-preferences-folding.htm" />
-	  			<topic label="Hovers" href="reference/preferences/java/editor/ref-preferences-hovers.htm" />
-	  			<topic label="Mark Occurrences" href="reference/preferences/java/editor/ref-preferences-mark-occurrences.htm" />
-	  			<topic label="Save Actions" href="reference/preferences/java/editor/ref-preferences-save-actions.htm" />
-	  			<topic label="Syntax Coloring" href="reference/preferences/java/editor/ref-preferences-syntax-coloring.htm" />
-	  			<topic label="Templates" href="reference/preferences/java/editor/ref-preferences-templates.htm" />
-	  			<topic label="Typing" href="reference/preferences/java/editor/ref-preferences-typing.htm" />
-			</topic>
-			<topic label="Installed JREs" href="reference/preferences/java/debug/ref-installed_jres.htm">
-				<topic label="Execution Environments" href="reference/preferences/java/debug/ref-execution_environments.htm"/>
-			</topic>
-			<topic label="JUnit" href="reference/preferences/java/ref-preferences-junit.htm" />
-			<topic label="Properties Files Editor" href="reference/preferences/java/ref-preferences-properties-files-editor.htm" />
-		</topic>
-		<topic label="Run/Debug" href="reference/preferences/run-debug/ref-run_debug.htm">
-			<topic label="Console" href="reference/preferences/run-debug/ref-console.htm"/>
-			<topic label="Launching" href="reference/preferences/run-debug/ref-launching.htm">
-				<topic label="Default Launchers" href="reference/preferences/run-debug/ref-default_launchers.htm"/>
-				<topic label="Launch Configurations" href="reference/preferences/run-debug/ref-launch_configurations.htm"/>
-			</topic>
-			<topic label="Perspectives" href="reference/preferences/run-debug/ref-perspectives.htm"/>
-			<topic label="String Substitution" href="reference/preferences/run-debug/ref-string_substitution.htm"/>
-			<topic label="View Management" href="reference/preferences/run-debug/ref-view_management.htm"/>
-		</topic>
-	</topic>
-
-<!--
-	Property Pages
--->
-	<topic label="Property Pages">
-        <topic label="Javadoc Location" href="reference/ref-dialog-javadoc-location.htm" />
- 		<topic label="Java Build Path" href="reference/ref-properties-build-path.htm" />
- 		<topic label="Java Compiler" href="reference/ref-properties-compiler.htm" />
- 		<topic label="Java Task Tags" href="reference/ref-properties-task-tags.htm" />
-		<topic label="Source Attachment" href="reference/ref-properties-source-attachment.htm" />
-  <topic href="reference/propertypages/ref-properties-rundebug.htm" label="Run / Debug">
-  </topic>
-    </topic>
-	
-<!--
-	Refactoring
--->
-	<topic label="Refactoring" href="concepts/concept-refactoring.htm">
-		<topic label="Refactor Actions" href="reference/ref-menu-refactor.htm" />
-		<topic label="Refactor Wizard" href="reference/ref-wizard-refactorings.htm" />
-		<topic label="Extract Method Errors" href="reference/ref-refactoring-extract-method.htm" />
-	</topic>
-
-<!--
-	Search
--->
-	<topic label="Search" >
-		<topic label="Java Search Tab" href="reference/ref-dialog-java-search.htm" />
-		<topic label="Java Search Actions" href="reference/ref-menu-search.htm" />
-	</topic>
-
-<!--
-	Toolbar
--->	
-	<topic label="Toolbar">
-		<topic label="Java Toolbar Actions" href="reference/ref-actions-toolbar.htm"/>
-		<topic label="Java Editor Toolbar Actions" href="reference/views/ref-java-editor.htm" />
-		<topic label="Run and Debug Toolbar Actions" href="reference/ref-toolbar-run.htm" />
-	</topic>
-<!-- 
-	Views
- -->	
- 	<topic label="Views" href="reference/views/ref-viewsandeditors.htm">	
-<!--
-	Breakpoints View
--->
-	<topic label="Breakpoints View" href="reference/views/breakpoints/ref-breakpoints_view.htm">
-		<topic label="Access" href="reference/views/breakpoints/ref-access_contextaction.htm" />
-		<topic label="Add Java Exception Breakpoint" href="reference/views/breakpoints/ref-addexception_viewaction.htm" />
-		<topic label="Breakpoint Properties" href="reference/views/breakpoints/ref-properties_contextaction.htm" />
-		<topic label="Caught" href="reference/views/breakpoints/ref-caught_contextaction.htm" />
-		<topic label="Collapse All" href="reference/views/shared/ref-collapseall.htm"/>	
-		<topic label="Copy" href="reference/views/shared/ref-copy.htm" />
-		<topic label="Disable" href="reference/views/breakpoints/ref-disable_contextaction.htm" />
-		<topic label="Enable" href="reference/views/breakpoints/ref-enable_contextaction.htm" />
-		<topic label="Entry" href="reference/views/breakpoints/ref-entry_contextaction.htm" />
-		<topic label="Exit" href="reference/views/breakpoints/ref-exit_contextaction.htm" />
-		<topic label="Expand All" href="reference/views/breakpoints/ref-expandall_viewaction.htm"/>
-		<topic label="Export Breakpoints" href="reference/views/breakpoints/ref-export_contextaction.htm"/>
-		<topic label="Go to File for Breakpoint" href="reference/views/breakpoints/ref-gotofile_viewaction.htm" />
-		<topic label="Group By" href="reference/views/breakpoints/ref-groupby_viewaction.htm"/>
-		<topic label="Hit Count" href="reference/views/breakpoints/ref-hitcount_contextaction.htm"/>
-		<topic label="Import Breakpoints" href="reference/views/breakpoints/ref-import_contextaction.htm"/>
-		<topic label="Link with Debug View" href="reference/views/breakpoints/ref-linkwith_viewaction.htm"/>
-		<topic label="Modification" href="reference/views/breakpoints/ref-modification_contextaction.htm" />
-		<topic label="Paste" href="reference/views/shared/ref-paste.htm" />
-		<topic label="Remove Selected Breakpoints" href="reference/views/breakpoints/ref-remove_viewaction.htm" />
-		<topic label="Remove All Breakpoints" href="reference/views/breakpoints/ref-removeall_viewaction.htm" />
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm" />
-		<topic label="Select Default Working Set" href="reference/views/breakpoints/ref-selectdefaultws_viewaction.htm"/>
-		<topic label="Show Qualified Names" href="reference/views/shared/ref-showqualified.htm" /> 
-		<topic label="Show Supported Breakpoints" href="reference/views/breakpoints/ref-showsupported_viewaction.htm" /> 
-		<topic label="Skip All Breakpoints" href="reference/views/breakpoints/ref-skipall_viewaction.htm"/>
-		<topic label="Suspend Policy" href="reference/views/breakpoints/ref-suspendpolicy_contextaction.htm" />
-		<topic label="Working Sets..." href="reference/views/breakpoints/ref-workingsets_viewaction.htm"/>
-		<topic label="Uncaught" href="reference/views/breakpoints/ref-uncaught_contextaction.htm" />
-	</topic>
-		
-<!--
-	Console View
--->
-	<topic label="Console View" href="reference/views/console/ref-console_view.htm">
-		<topic label="CVS Console" href="reference/views/console/ref-cvs_console.htm">
-			<topic label="Copy" href="reference/views/shared/ref-copy.htm"/>
-			<topic label="Cut" href="reference/views/shared/ref-cut.htm"/>
-			<topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-			<topic label="Open Link" href="reference/views/console/ref-openlink_action.htm"/>
-			<topic label="Paste" href="reference/views/shared/ref-paste.htm"/>
-			<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		</topic>
-		<topic label="Process Console" href="reference/views/console/ref-process_console.htm">
-			<topic label="Copy" href="reference/views/shared/ref-copy.htm"/>
-			<topic label="Cut" href="reference/views/shared/ref-cut.htm"/>
-			<topic label="Console Preferences" href="reference/views/console/ref-prefs_action.htm"/>
-			<topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-			<topic label="Paste" href="reference/views/shared/ref-paste.htm"/>
-			<topic label="Remove All Terminated Launches" href="reference/views/console/ref-removeallterminated_action.htm"/>
-			<topic label="Remove Launch" href="reference/views/console/ref-removelaunch_action.htm"/>
-			<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-			<topic label="Show Console When Standard Out Changes"  href="reference/views/console/ref-show_out_action.htm"/>
-			<topic label="Show Console When Standard Error Changes"  href="reference/views/console/ref-show_err_action.htm"/>
-			<topic label="Terminate" href="reference/views/console/ref-terminate_action.htm"/>
-		</topic>
-		<topic label="Stacktrace Console" href="reference/views/console/ref-stacktrace_console.htm">
-			<topic label="Autoformat Console" href="reference/views/console/ref-autoformat_action.htm"/>
-			<topic label="Copy" href="reference/views/shared/ref-copy.htm"/>
-			<topic label="Cut" href="reference/views/shared/ref-cut.htm"/>
-			<topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-			<topic label="Format" href="reference/views/console/ref-format_action.htm"/>
-			<topic label="Open Link" href="reference/views/console/ref-openlink_action.htm"/>
-			<topic label="Paste" href="reference/views/shared/ref-paste.htm"/>
-			<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		</topic>
-		<topic label="Clear the Console" href="reference/views/console/ref-clear_action.htm"/>
-		<topic label="Display Selected Console" href="reference/views/console/ref-display_action.htm"/>
-		<topic label="Open Console" href="reference/views/console/ref-open_action.htm"/>
-		<topic label="Pin the Console" href="reference/views/console/ref-pin_action.htm"/>
-		<topic label="Scroll Lock" href="reference/views/console/ref-scrolllock_action.htm"/>
-	</topic>
-
-<!--
-	Debug View
--->
-	<topic label="Debug View" href="reference/views/debug/ref-debug_view.htm">
-		<topic label="Execution Control Commands" href="reference/views/debug/ref-executioncontrolcommands.htm">
-			<topic label="Resume" href="reference/views/debug/ref-resume.htm"/>
-			<topic label="Step Into" href="reference/views/debug/ref-stepinto.htm"/>
-			<topic label="Step Over" href="reference/views/debug/ref-stepover.htm"/>
-			<topic label="Step Return" href="reference/views/debug/ref-stepreturn.htm"/>
-			<topic label="Suspend" href="reference/views/debug/ref-suspend.htm"/>
-			<topic label="Terminate" href="reference/views/debug/ref-terminate.htm"/>
-			<topic label="Terminate/Disconnect All" href="reference/views/debug/ref-terminateall.htm"/>
-			<topic label="Terminate and Relaunch" href="reference/views/debug/ref-terminaterelaunch.htm"/>
-			<topic label="Terminate and Remove" href="reference/views/debug/ref-terminateandremove.htm"/>
-		</topic>
-		<topic label="Copy Stack" href="reference/views/shared/ref-copy.htm" />
-		<topic label="Disconnect" href="reference/views/debug/ref-disconnect.htm" />
-		<topic label="Drop to Frame" href="reference/views/debug/ref-droptoframe.htm" />
-		<topic label="Edit Launch Configuration" href="reference/views/debug/ref-editlaunchconfig.htm"/>
-		<topic label="Edit Source Lookup" href="reference/views/debug/ref-editsourcelookup.htm"/>
-		<topic label="Edit Step Filters" href="reference/views/debug/ref-editstepfilters.htm"/>
-		<topic label="Filter Package" href="reference/views/debug/ref-filterpackage.htm"/>
-		<topic label="Filter Type" href="reference/views/debug/ref-filtertype.htm"/>
-		<topic label="Find..." href="reference/views/shared/ref-find.htm"/>
-		<topic label="Lookup Source" href="reference/views/debug/ref-lookupsource.htm"/>
-		<topic label="Open Declared Type" href="reference/views/debug/ref-opendeclared.htm"/>
-		<topic label="Open Declared Type Hierarchy" href="reference/views/debug/ref-opendeclaredhier.htm"/>
-		<topic label="Properties" href="reference/views/debug/ref-properties.htm"/>
-		<topic label="Relaunch" href="reference/views/debug/ref-relaunch.htm"/>
-		<topic label="Remove All Terminated" href="reference/views/debug/ref-removeallterminated.htm"/>
-		<topic label="Show Monitors" href="reference/views/debug/ref-showmonitors.htm"/>
-		<topic label="Show Qualified Names" href="reference/views/shared/ref-showqualified.htm" />
-		<topic label="Show System Threads" href="reference/views/debug/ref-showsystemthreads.htm"/>
-		<topic label="Show Thread Groups" href="reference/views/debug/ref-showthreadgroups.htm"/>
-		<topic label="Use Step Filters" href="reference/views/debug/ref-usestepfilters.htm"/>
-	</topic>
-				
-<!--
-	Display View
--->
-	<topic label="Display View" href="reference/views/display/ref-display_view.htm">
-		<topic label="Clear" href="reference/views/display/ref-clear.htm"/>
-		<topic label="Content Assist" href="reference/views/shared/ref-contentassist.htm"/>
-		<topic label="Copy Selected Statements" href="reference/views/shared/ref-copy.htm"/>
-		<topic label="Cut Selected Statements" href="reference/views/shared/ref-cut.htm"/>
-		<topic label="Display" href="reference/views/shared/ref-display.htm"/>
-		<topic label="Execute Selected Statement" href="reference/views/shared/ref-execute.htm"/>
-		<topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-		<topic label="Inspect" href="reference/views/shared/ref-inspect.htm"/>
-		<topic label="Paste" href="reference/views/shared/ref-paste.htm"/>
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-	</topic>
-		
-<!--
-	Expressions View
--->
-	<topic label="Expressions View" href="reference/views/expressions/ref-expressions_view.htm">
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm">
-			<topic label="Assign Value" href="reference/views/shared/ref-assignvalue.htm"/>
-			<topic label="Content Assist" href="reference/views/shared/ref-contentassist.htm"/>
-			<topic label="Cut" href="reference/views/shared/ref-cut.htm"/>
-			<topic label="Copy" href="reference/views/shared/ref-copy.htm"/>
-			<topic label="Display" href="reference/views/shared/ref-display.htm"/>
-			<topic label="Execute" href="reference/views/shared/ref-execute.htm"/>
-			<topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-			<topic label="Force Return" href="reference/views/shared/ref-forcereturn.htm"/>
-			<topic label="Inspect" href="reference/views/shared/ref-inspect.htm"/>
-			<topic label="Max Length" href="reference/views/shared/ref-maxlength.htm"/>
-			<topic label="Paste" href="reference/views/shared/ref-paste.htm"/>
-			<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-			<topic label="Wrap Text" href="reference/views/shared/ref-wrap.htm"/>
-		</topic>
-		<topic label="View Display Commands" href="reference/views/shared/ref-viewdisplaycommands.htm">
-			<topic label="Show Contants" href="reference/views/shared/ref-showconstants.htm"/>
-			<topic label="Show Logical" href="reference/views/shared/ref-showlogical.htm"/>
-			<topic label="Show Null" href="reference/views/shared/ref-shownull.htm"/>
-			<topic label="Show Qualified" href="reference/views/shared/ref-showqualified.htm"/>
-			<topic label="Show References" href="reference/views/shared/ref-showreferences.htm"/>
-			<topic label="Show Static" href="reference/views/shared/ref-showstatic.htm"/>
-			<topic label="Show Type Names" href="reference/views/shared/ref-showtypenames.htm"/>
-		</topic>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm">
-			<topic label="Show Columns" href="reference/views/shared/ref-showcolumns.htm"/>
-			<topic label="Select Columns" href="reference/views/shared/ref-selectcolumns.htm"/>
-			<topic label="Horizontal View Orientation" href="reference/views/shared/ref-horizview.htm"/>
-			<topic label="Vertical View Orientation" href="reference/views/shared/ref-vertview.htm"/>
-			<topic label="View Only" href="reference/views/shared/ref-viewonly.htm"/>
-		</topic>
-		<topic label="Add Watch Expression" href="reference/views/expressions/ref-addwatch.htm"/>
-		<topic label="All Instances" href="reference/views/shared/ref-allinstances.htm"/>
-		<topic label="All References" href="reference/views/shared/ref-allreferences.htm"/>
-		<topic label="Change Variable Value" href="reference/views/shared/ref-changevarvalue.htm" /> 
-		<topic label="Collapse All" href="reference/views/shared/ref-collapseall.htm"/>	
-		<topic label="Copy Expressions" href="reference/views/shared/ref-copy.htm"/>	
-		<topic label="Convert to Watch Expression" href="reference/views/expressions/ref-convert.htm"/>
-		<topic label="Disable Selected Watch Expression" href="reference/views/expressions/ref-disable.htm"/>
-		<topic label="Edit Watch Expression" href="reference/views/expressions/ref-edit.htm"/>
-		<topic label="Enable Selected Watch Expression" href="reference/views/expressions/ref-enable.htm"/>
-		<topic label="Find..." href="reference/views/shared/ref-find.htm"/>
-		<topic label="Inspect Variable" href="reference/views/shared/ref-inspectvariable.htm" />
-		<topic label="Java Preferences" href="reference/views/shared/ref-preferences.htm"/>
-		<topic label="Reevaluate Watch Expression" href="reference/views/expressions/ref-reevaluate.htm"/>
-		<topic label="Remove Selected Expressions" href="reference/views/expressions/ref-remove.htm"/>
-		<topic label="Remove All Expressions" href="reference/views/expressions/ref-removeall.htm"/>
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		<topic label="Toggle Watchpoint" href="reference/views/shared/ref-togglewp.htm"/> 
-	</topic>
-<!--
-	Package Explorer
--->
-	<topic label="Package Explorer view" href="reference/views/ref-view-package-explorer.htm">
-		<topic label="Java Element Filters dialog" href="reference/ref-dialog-java-element-filters.htm" />
-	</topic>
-		
-<!--
-	Variables View
--->
-	<topic label="Variables View" href="reference/views/variables/ref-variables_view.htm">
-		<topic label="Detail Pane" href="reference/views/shared/ref-detailpane.htm">
-			<topic label="Assign Value" href="reference/views/shared/ref-assignvalue.htm"/>
-			<topic label="Content Assist" href="reference/views/shared/ref-contentassist.htm"/>
-			<topic label="Cut" href="reference/views/shared/ref-cut.htm"/>
-			<topic label="Copy" href="reference/views/shared/ref-copy.htm"/>
-			<topic label="Display" href="reference/views/shared/ref-display.htm"/>
-			<topic label="Execute" href="reference/views/shared/ref-execute.htm"/>
-			<topic label="Find/Replace" href="reference/views/shared/ref-findreplace.htm"/>
-			<topic label="Force Return" href="reference/views/shared/ref-forcereturn.htm"/>
-			<topic label="Inspect" href="reference/views/shared/ref-inspect.htm"/>
-			<topic label="Max Length" href="reference/views/shared/ref-maxlength.htm"/>
-			<topic label="Paste" href="reference/views/shared/ref-paste.htm"/>
-			<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-			<topic label="Wrap Text" href="reference/views/shared/ref-wrap.htm"/>
-		</topic>
-		<topic label="View Display Commands" href="reference/views/shared/ref-viewdisplaycommands.htm">
-			<topic label="Show Contants" href="reference/views/shared/ref-showconstants.htm"/>
-			<topic label="Show Logical" href="reference/views/shared/ref-showlogical.htm"/>
-			<topic label="Show Null" href="reference/views/shared/ref-shownull.htm"/>
-			<topic label="Show Qualified" href="reference/views/shared/ref-showqualified.htm"/>
-			<topic label="Show References" href="reference/views/shared/ref-showreferences.htm"/>
-			<topic label="Show Static" href="reference/views/shared/ref-showstatic.htm"/>
-			<topic label="Show Type Names" href="reference/views/shared/ref-showtypenames.htm"/>
-		</topic>
-		<topic label="View Layout Commands" href="reference/views/shared/ref-viewlayoutcommands.htm">
-			<topic label="Show Columns" href="reference/views/shared/ref-showcolumns.htm"/>
-			<topic label="Select Columns" href="reference/views/shared/ref-selectcolumns.htm"/>
-			<topic label="Horizontal View Orientation" href="reference/views/shared/ref-horizview.htm"/>
-			<topic label="Vertical View Orientation" href="reference/views/shared/ref-vertview.htm"/>
-			<topic label="View Only" href="reference/views/shared/ref-viewonly.htm"/>
-		</topic>
-		<topic label="All Instances" href="reference/views/shared/ref-allinstances.htm"/>
-		<topic label="All References" href="reference/views/shared/ref-allreferences.htm"/>
-		<topic label="Change Variable Value" href="reference/views/shared/ref-changevarvalue.htm" />
-		<topic label="Collapse All" href="reference/views/shared/ref-collapseall.htm"/>	
-		<topic label="Copy Variables" href="reference/views/shared/ref-copy.htm"/>
-		<topic label="Create Watch Expression" href="reference/views/variables/ref-createwatch.htm"/>
-		<topic label="Find..." href="reference/views/shared/ref-find.htm"/>
-		<topic label="Inspect Variable" href="reference/views/shared/ref-inspectvariable.htm"/>
-		<topic label="Java Preferences" href="reference/views/shared/ref-preferences.htm"/>
-		<topic label="Select All" href="reference/views/shared/ref-selectall.htm"/>
-		<topic label="Toggle Watchpoint" href="reference/views/shared/ref-togglewp.htm"/> 
-	</topic>
-
-<!--
-	Java Outline View
--->
-	<topic label="Java Outline View" href="reference/views/ref-view-outline.htm" />
-		
-<!--
-	Java Scrapbook Page
--->
-	<topic label="Java Scrapbook Page" href="reference/views/ref-view-scrapbook.htm" />
-		
-<!--
-	Java Type Hierarchy View
--->
-	<topic label="Type Hierarchy View" href="reference/views/ref-type-hierarchy.htm" />
-	<topic label="Call Hierarchy View" href="reference/views/ref-call-hierarchy.htm" />
-<!-- 
-	End views
- -->	
-	</topic>
-
-<!--
-	Java Editor
--->
-	<topic label="Java Editor" href="reference/views/ref-java-editor.htm">
-		<topic label="Java Content Assist" href="reference/ref-java-editor-code-assist.htm" />
-		<topic label="Quick fix" href="reference/ref-java-editor-quickfix.htm" />
-		<topic label="Quick assist" href="reference/ref-java-editor-quickassist.htm" />
-	</topic>
-		
-<!--
-	Wizards
--->
-    <topic label="Wizards and Dialogs">
-		<topic label="Create New Elements">
-			<topic label="New Java Project Wizard" href="reference/ref-wizard-java-project.htm">
-				<topic label="Java Build Path Page" href="reference/ref-properties-build-path.htm" />
-				<topic label="Attaching Source to JAR Files and Variables" href="reference/ref-properties-source-attachment.htm" />
-			</topic>
-			<topic label="New Java Package Wizard" href="reference/ref-wizard-package.htm" />
-			<topic label="New Java Class Wizard" href="reference/ref-wizard-class.htm" />
-			<topic label="New Java Enum Wizard" href="reference/ref-wizard-enum.htm" />
-			<topic label="New Java Interface Wizard" href="reference/ref-wizard-interface.htm" />
-			<topic label="New Java Annotation Wizard" href="reference/ref-wizard-annotation.htm" />
-			<topic label="New Source Folder Wizard" href="reference/ref-wizard-source-folder.htm" />
-			<topic label="New Java Scrapbook Page Wizard" href="reference/ref-wizard-scrapbook.htm" />
-		</topic>
-		<topic label="Export Breakpoints" href="reference/wizards/ref-export_breakpoints.htm"/>
-     <topic href="reference/wizards/ref-export_launch_configs.htm" label="Export Launch Configurations">
-     </topic>
-        <topic label="Externalize Strings wizard" href="reference/ref-wizard-externalize-strings.htm" />
-		<topic label="Import Breakpoints" href="reference/wizards/ref-import_breakpoints.htm"/>
-  <topic href="reference/wizards/ref-import_launch_configs.htm" label="Import Launch Configurations">
-  </topic>
-		<topic label="JAR File Exporter" href="reference/ref-export-jar.htm" />
-		<topic label="Javadoc Generation" href="reference/ref-export-javadoc.htm" />
-		<topic label="Java Element Filters" href="reference/ref-dialog-java-element-filters.htm" />
-        <topic label="Open Type Dialog" href="reference/ref-dialog-open-type.htm" />
-		<topic label="Create Getter and Setter" href="reference/ref-dialog-gettersetter.htm" />
-  <topic href="reference/ref-dialog-tostring.htm" label="Generate toString()">
-     <topic href="reference/ref-tostring-templates.htm" label="Format Templates">
-     </topic>
-     <topic href="reference/ref-tostring-styles.htm" label="Code Styles">
-     </topic>
-     <topic href="reference/ref-tostring-listcontent.htm" label="Content Listing">
-     </topic>
-  </topic>
-    	<topic label="Override Methods" href="reference/ref-dialog-override-method.htm" />
-    </topic>
-    
-<!--
-	Topics that do not fall under a main topic
--->
-    <topic label="Frequently-Asked Questions: JDT" href="reference/ref-jdt-faq.htm" />
-	<topic label="Glossary" href="reference/ref-jdt-glossary.htm" />
-	<topic label="Icons" href="reference/ref-icons.htm" />
-	<topic label="Available Quick Assists" href="reference/ref-java-editor-quickassist.htm"/>
-	<topic label="Available Quick Fixes" href="reference/ref-java-editor-quickfix.htm"/>
-	<topic label="List of JDT Key Bindings" href="reference/ref-keybindings.htm"/>
-</toc>

diff --git a/bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml b/bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml
deleted file mode 100644
index 34f0f0f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/topics_Tasks.xml
+++ /dev/null

@@ -1,119 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Tasks -->
-<!-- ========================== -->
-<toc label="Tasks">
-
-	<topic label="Customizing the Debugger and Console" >
-		<topic label="Changing the active perspective when launching" href="tasks/tasks-9.htm"></topic>
-		<topic label="Changing the appearance of the console view" href="tasks/tasks-consoleAppearance.htm"></topic>
-	</topic>
-	<anchor id="t_appearancejava" />
-
-	<topic label="Creating JAR Files" href="tasks/tasks-32.htm">
-		<topic label="Creating a new JAR file" href="tasks/tasks-33.htm"></topic>
-		<topic label="Setting advanced options" href="tasks/tasks-34.htm"></topic>
-		<topic label="Defining the JAR file&apos;s manifest" href="tasks/tasks-35.htm"></topic>
-		<topic label="Regenerating a JAR File" href="tasks/tasks-36.htm"></topic>
-	</topic>
-	<anchor id="t_createjar" />
-
-	<topic label="Using the Local History" href="tasks/tasks-62.htm">
-		<topic label="Comparing a Java element with a local history edition" href="tasks/tasks-63a.htm"></topic>
-		<topic label="Replacing a Java element with a local history edition" href="tasks/tasks-63.htm"></topic>
-		<topic label="Restoring a deleted workbench element" href="tasks/tasks-64.htm"></topic>
-	</topic>
-	<anchor id="t_localhistory" />
-
-	<topic label="Externalizing Strings" href="tasks/tasks-206.htm">
-		<topic label="Finding strings to externalize" href="tasks/tasks-188.htm"></topic>
-		<topic label="Finding unused and incorrectly used keys in property files" href="tasks/tasks-202.htm"></topic>
-	</topic>
-	<anchor id="t_externalizingstrings" />
-	
-	<topic label="Navigating the Workbench" >
-		<topic label="Opening an editor for a selected element" href="tasks/tasks-73.htm"></topic>
-		<topic label="Showing an element in the Package Explorer view" href="tasks/tasks-74.htm"></topic>
-		<topic label="Opening a type in the Package Explorer view" href="tasks/tasks-75.htm"></topic>
-		<topic label="Opening an editor on a type" href="tasks/tasks-76.htm"></topic>
-		<topic label="Opening a package" href="tasks/tasks-77.htm"></topic>
-	</topic>
-	<anchor id="t_navigatingjdt" />
-
-	<topic label="Working with JREs" href="tasks/tasks-JREs.htm">
-		<topic label="Assigning the default JRE for the workbench" href="tasks/task-assign_default_jre.htm"></topic>
-		<topic label="Adding a new JRE definition" href="tasks/task-add_new_jre.htm"></topic>
-		<topic label="Choosing a JRE for launching a project" href="tasks/task-choose_config_jre.htm"></topic>
-		<topic label="Deleting a JRE definition" href="tasks/tasks-deleteJRE.htm">	</topic>
-	</topic>
-	<anchor id="t_buildingjdt" />
-
-	<topic label="Running and Debugging" href="tasks/task-running_and_debugging.htm">
-		<topic label="Breakpoints" href="concepts/cbrkpnts.htm">
-			<topic label="Adding Line Breakpoints" href="tasks/task-add_line_breakpoints.htm"></topic>
-			<topic label="Removing Line Breakpoints" href="tasks/task-remove_line_breakpoints.htm"></topic>
-			<topic label="Enabling and Disabling Breakpoints" href="tasks/task-enable_disable_breakpoints.htm"></topic>
-			<topic label="Setting Method Breakpoints" href="tasks/task-set_method_breakpoints.htm"></topic>
-			<topic label="Applying Hit Counts" href="tasks/task-apply_hit_count.htm"></topic>
-			<topic label="Managing Conditional Breakpoints" href="tasks/task-manage_conditional_breakpoint.htm"></topic>
-			<topic label="Catching Java Exceptions" href="tasks/task-catching_exceptions.htm"></topic>
-			<topic label="Creating Exception Breakpoint Filters" href="tasks/tasks-create-exception-filter-expression.htm"></topic>
-		</topic>
-		<topic label="Local Debugging" href="concepts/clocdbug.htm">
-			<topic label="Preparing to Debug" href="tasks/task-preparing_to_debug.htm"></topic>
-			<topic label="Launching a Java program in Debug Mode" href="tasks/tasks-debug-launch.htm"></topic>
-			<topic label="Suspending Threads" href="tasks/task-suspending_threads.htm"></topic>
-			<topic label="Resuming Threads" href="tasks/task-resuming_threads.htm"></topic>
-			<topic label="Stepping through the execution of a program" href="tasks/task-stepping.htm"></topic>
-			<topic label="Inspecting Values" href="tasks/task-inspecting.htm"></topic>
-			<topic label="Evaluating expressions" href="tasks/task-evaluating_expressions.htm"></topic>
-		</topic>
-		<topic label="Remote Debugging" href="concepts/cremdbug.htm">
-			<topic label="Using the remote Java application launch configuration" href="tasks/task-remotejava_launch_config.htm"></topic>
-			<topic label="Disconnecting from a VM" href="tasks/task-disconnect_remote_debug.htm"></topic>
-		</topic>
-		<topic label="Creating a Java application launch configuration" href="tasks/tasks-java-local-configuration.htm"></topic>
-		<topic label="Launching a Java program" href="tasks/task-launching_java_program.htm"></topic>
-		<topic label="Launching a Java applet" href="tasks/task-launching_java_applet.htm"></topic>
-		<topic label="Setting execution arguments" href="tasks/tasks-executionArgs.htm"></topic>
-		<topic label="Relaunching a program" href="tasks/task-relaunch_program.htm"></topic>
-		<topic label="Inspecting memory in the Memory view" href="tasks/task-memory-inspect.htm">
-			<anchor id="MemoryView1"/>
-			<topic label="Adding a variable, expression, or register to the Memory view" href="tasks/task-memory-add.htm"/>
-			<anchor id="MemoryView2"/>
-			<topic label="Adding multiple memory renderings and removing renderings" href="tasks/task-memory-multiple-add.htm"/>
-			<anchor id="MemoryView3"/>
-			<topic label="Working with memory monitors" href="tasks/task-memory-monitors.htm"/>
-			<anchor id="MemoryView4"/>
-			<topic label="Changing the contents of a memory location" href="tasks/task-memory-change.htm"/>
-			<anchor id="MemoryView5"/>
-			<topic label="Memory view preferences" href="tasks/task-memory-preference.htm"/>
-			<anchor id="MemoryView6"/>
-			<topic label="Working with multiple Memory views" href="tasks/task-memory-multiple-views.htm"/>
-			<anchor id="MemoryView7"/>
-			<topic label="Removing memory monitors from the Memory view" href="tasks/task-memory-remove.htm"/>
-			<anchor id="MemoryView8"/>
-		</topic>
-	</topic>
-	
-	<topic label="Using the Scrapbook" href="concepts/cscrapbook.htm">
-		<topic label="Creating a Java Scrapbook Page" href="tasks/task-create_scrapbook_page.htm"></topic>
-		<topic label="Inspecting the result of evaluating an expression" href="tasks/task-inspect_evaluation_result.htm"></topic>
-		<topic label="Displaying the result of evaluating an expression" href="tasks/task-display_evaluation_result.htm"></topic>
-		<topic label="Running an expression" href="tasks/task-executing_an_expression.htm"></topic>
-		<topic label="Using code assist" href="tasks/task-scrapbook_content_assist.htm"></topic>
-		<topic label="Scrapbook error reporting" href="tasks/task-scrapbook_error_reporting.htm">
-			<topic label="Viewing compilation errors" href="tasks/task-view_compilation_errors.htm"></topic>
-			<topic label="Viewing runtime exceptions" href="tasks/task-view_runtime_exceptions.htm"></topic>
-		</topic>
-	</topic>
-	<anchor id="t_scrapbook" />
-	<topic label="Using the Formatter Application" href="tasks/tasks-230.htm">
-			<topic label="Running the formatter application" href="tasks/tasks-231.htm"></topic>
-			<topic label="Generating a config file for the formatter application" href="tasks/tasks-232.htm"></topic>
-	</topic>
-
-
-	
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-dot-dot-path.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-dot-dot-path.png
deleted file mode 100644
index b85c94a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-dot-dot-path.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-duplicate-entries.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-duplicate-entries.png
deleted file mode 100644
index 89ea67b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-duplicate-entries.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-invalid-dups.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-invalid-dups.png
deleted file mode 100644
index 61a686f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/build-path-invalid-dups.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/class-path-header.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/class-path-header.png
deleted file mode 100644
index 8cfa0c8..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/class-path-header.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/comparing-identical-values-example.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/comparing-identical-values-example.png
deleted file mode 100644
index 92ba73f..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/comparing-identical-values-example.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-deadcode-diagnosis.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-deadcode-diagnosis.png
deleted file mode 100644
index e473d0b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-deadcode-diagnosis.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-hashcode-diagnosis.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-hashcode-diagnosis.png
deleted file mode 100644
index 0099e68..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compiler-hashcode-diagnosis.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compliance-follows-ee.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compliance-follows-ee.png
deleted file mode 100644
index ba1d280..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/compliance-follows-ee.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/constructor-completion.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/constructor-completion.png
deleted file mode 100644
index a88a365..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/constructor-completion.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/delete-working-set.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/delete-working-set.png
deleted file mode 100644
index 1ed0b03..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/delete-working-set.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/dynamic-structure-compare.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/dynamic-structure-compare.png
deleted file mode 100644
index 0526010..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/dynamic-structure-compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/expand-with-constructors.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/expand-with-constructors.png
deleted file mode 100644
index 992c46a..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/expand-with-constructors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-after.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-after.png
deleted file mode 100644
index 585b8bc..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-after.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-before.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-before.png
deleted file mode 100644
index 4f7d731..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/formatter-join-lines-before.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/generate-tostring-dialog.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/generate-tostring-dialog.png
deleted file mode 100644
index b5ed978..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/generate-tostring-dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/hashcode-and-equals-wizard.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/hashcode-and-equals-wizard.png
deleted file mode 100644
index 6339dc6..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/hashcode-and-equals-wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jar-export.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jar-export.png
deleted file mode 100644
index 7c33331..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/jar-export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-assist.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-assist.png
deleted file mode 100644
index 9ad7b7b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hover.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hover.png
deleted file mode 100644
index d54890c..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hyperlinking.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hyperlinking.png
deleted file mode 100644
index f1127b1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-hyperlinking.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-outline.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-outline.png
deleted file mode 100644
index 6220cfe..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/java-compare-outline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-header-links.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-header-links.png
deleted file mode 100644
index ecf11e0..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-header-links.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-hover.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-hover.png
deleted file mode 100644
index baf4782..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/javadoc-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/junit-view-import.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/junit-view-import.png
deleted file mode 100644
index e46ed64..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/junit-view-import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missing-synchronized.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missing-synchronized.png
deleted file mode 100644
index b411ab4..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/missing-synchronized.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-implementation.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-implementation.png
deleted file mode 100644
index d9c8031..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-implementation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-junit-view.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-junit-view.png
deleted file mode 100644
index 79c92d7..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-junit-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-properties-file.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-properties-file.png
deleted file mode 100644
index 59e3db1..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-in-properties-file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png
deleted file mode 100644
index 81dac90..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/open-type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-in-workspace.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-in-workspace.png
deleted file mode 100644
index 3786c86..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/rename-in-workspace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/runnable-jar-in-jar-export.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/runnable-jar-in-jar-export.png
deleted file mode 100644
index 636205b..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/runnable-jar-in-jar-export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/sort-working-sets.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/sort-working-sets.png
deleted file mode 100644
index 4ec0ca5..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/sort-working-sets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch-case-fall-through.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch-case-fall-through.png
deleted file mode 100644
index 08646ea..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/switch-case-fall-through.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
deleted file mode 100644
index 8f19f46..0000000
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
+++ /dev/null

@@ -1,518 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
-	type="text/css">
-<style type="text/css">
-td {border-top: solid thin black;}
-td table tbody tr td {border-top: none;} /* no border for nested tables */
-img[alt] {background-color:#ffdddd;}
-tr {vertical-align: top;}
-ul {padding-left: 1.2em;}
-</style>
-<title>What's New in 3.5 (JDT)</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<h2>What's New in 3.5 (JDT)</h2>
-<p>Here are descriptions of some of the more interesting or significant changes made to the Java development tools
-for the 3.5 release of Eclipse. They are grouped into:</p>
-<ul>
-	<li><a href="#JavaEditor">Java Editor</a></li>
-	<li><a href="#JavaCompareEditor">Java Compare Editor</a></li>
-	<li><a href="#JavaRefactoring">Java Refactoring and Source Actions</a></li>
-	<li><a href="#JavaCompiler">Java Compiler</a></li>
-	<li><a href="#JavaViews">Java Views and Dialogs</a></li>
-</ul>
-<p>
-See also the <a href="../../org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html">Eclipse Platform What's New in 3.5</a>
-document for changes in the Platform.
-</p>
-<br>
-<!-- *************************************************** -->
-
-
-<table cellpadding="10" cellspacing="0" width="600" summary="New and noteworthy items">
-  <colgroup>
-  <col width="30%">
-  <col width="70%">
-  </colgroup>
-
-  <tbody>  
-    <!-- ******************* Java Editor ************************************* -->
-    <tr> 
-      <td colspan="2"><a name="JavaEditor"></a> <div style="font-size: 20px; font-weight: bold;"> 
-          Java Editor </div></td>
-    </tr>
-
-  <tr id="constructor-completion"> 
-    <td width="30%" valign="top" align="left">
-		<b>Constructor completion</b>
-	</td>
-    <td width="70%" valign="top">
-      Content Assist can now propose the available constructors of a class when
-         the completion happens in an allocation expression:
-      <p><img src="images/constructor-completion.png" alt="Constructor completion"></p>
-      <p>If the class is not already imported (as shown in the example above),
-      then the corresponding import will also be added.</p>
-    </td>
-  </tr>
-
-  <tr id="open-implementation">
-    <td width="30%" valign="top" align="left">
-        <b>Open Implementation hyperlink</b>
-    </td>
-    <td width="70%" valign="top">
-        An <b>Open Implementation</b> hyperlink has been added for overridable methods, which directly opens the implementation 
-        in case there's only one, or shows all the concrete implementations for that method in the hierarchy of its declaring type, using 
-        the quick type hierarchy. By default, the hyperlink appears when you hold down the <b>Ctrl</b> key
-        while hovering over an overridable method.
-       <p><img src="images/open-implementation.png" alt="Open Implementation hyperlink for methods" ></p>
-       <p>You can configure the modifier for this hyperlink on the
-       <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.HyperlinkDetectorsPreferencePage)")'>
-       <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the hyperlinking preference page">
-       <b>General &gt; Editors &gt; Text Editors &gt; Hyperlinking</b></a> preference page.</p>
-    </td>
-  </tr>
-  
-  <tr id="select-comment">
-    <td width="30%" valign="top" align="left">
-        <b>Select comment with double click</b>
-    </td>
-    <td width="70%" valign="top">
-		Double clicking on the beginning or end marker of a comment now selects the whole comment.
-    </td>
-  </tr>
-  
-    <tr id="rename-in-workspace">
-    <td width="30%" valign="top" align="left">
-        <b>Quick Fix to start Rename refactoring</b>
-    </td>
-    <td width="70%" valign="top">
-    	The <b>Rename</b> refactoring can now also be started via Quick Fix (<b>Ctrl+1</b>):
-       <p> <img src="images/rename-in-workspace.png" alt="Quick Fix 'Rename in workspace' in Java editor"></p>
-    </td>
-  </tr>
-
-  <tr id="javadoc-header-links">
-    <td width="30%" valign="top" align="left">
-        <b>Links in Javadoc headers</b>
-    </td>
-    <td width="70%" valign="top">
-        In the headers of Javadoc hovers and the Javadoc view, references to other types and members are now links.
-        You can click on a method return type or parameter type to quickly read the type's Javadoc.
-    	<p><img src="images/javadoc-header-links.png" alt="Javadoc hover with mouse over method return type"></p>
-    	And when you're done with reading, just click <b>Back</b> in the toolbar to see the original Javadoc again.
-    </td>
-  </tr>
-  
-  <tr id="open-in-properties-file">
-    <td width="30%" valign="top" align="left">
-        <b>Open in Properties File action in NLS Hover</b>
-    </td>
-    <td width="70%" valign="top">
-        The <b>NLS string hover</b> now has an <b>Open in Properties File </b> action in the toolbar which  
-        locates the selected NLS string in the corresponding properties file where it is defined. The action 
-        is activated in the toolbar with focus on the hover. 
-       <p><img src="images/open-in-properties-file.png" alt="Open in Properties File action in NLS hover"></p>        
-    </td>
-  </tr>
-  
-  <tr id="joinLine-formatter-option"> 
-    <td width="30%" valign="top" align="left">
-		<b>Formatter option to preserve user line breaks</b>
-    </td>
-    <td width="70%" valign="top">
-      The Java code formatter can now optionally preserve user line breaks by not joining lines in code or comments.
-      <p>For example, the wrapped lines of the <code>return</code> statement in following test case:</p>
-      <p><img src="images/formatter-join-lines-before.png" alt="Example of Code to Format"></p>  
-      <p>will be preserved by the formatter when the <b>Never join lines</b> preference is used and now produces the following result:</p>
-      <p><img src="images/formatter-join-lines-after.png" alt="Coded Formatted with Never Join Lines"></p>  
-      <p>This preference can be configured on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeFormatterPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the formatter preference page">
-      <b>Java &gt; Code Style &gt; Formatter</b></a> preference page.
-      		 See the <b>Never join lines</b> option on the <b>Line Wrapping</b> and <b>Comments</b> tab.</p>
-    </td>
-  </tr>
-
-   <!-- ******************* Java Compare Editor ************************************* -->
-
-     <tr> 
-      <td colspan="2"><a name="JavaCompareEditor"></a> <div style="font-size: 20px; font-weight: bold;"> 
-          Java Compare Editor</div></td>
-    </tr>
-   
-  <tr id="workspace_java-compare">
-    <td width="30%" valign="top" align="left">
-		<b>General editing enhancements</b></td>
-    <td width="70%" valign="top">
-		The Java Compare editor now supports new text editing features like move/copy/delete line and formatting.
-    </td>
-  </tr>
-
-    <tr id="java-compare-hyperlinking">
-    <td width="30%" valign="top" align="left">
-        <b>Hyperlinking (Ctrl+Click)</b>
-    </td>
-    <td width="70%" valign="top">
-    	<img src="images/java-compare-hyperlinking.png" alt="Hyperlinking">
-	</td>
-  </tr>
-  
-    <tr id="java-compare-content-assist">
-    <td width="30%" valign="top" align="left">
-        <b>Content Assist (Ctrl+Space)</b>
-    </td>
-    <td width="70%" valign="top">
-		<img src="images/java-compare-assist.png" alt="Content Assist">
-	</td>
-  </tr>
-  
-    <tr id="javadoc-on-hover">
-    <td width="30%" valign="top" align="left">
-        <b>Javadoc on hover</b>
-    </td>
-    <td width="70%" valign="top">
-		<img src="images/java-compare-hover.png" alt="Javadoc hovers">
-	</td>
-  </tr>
-  
-    <tr id="java-compare-quick-outline">
-    <td width="30%" valign="top" align="left">
-        <b>Quick Outline (Ctrl+O)</b>
-    </td>
-    <td width="70%" valign="top">
-		<img src="images/java-compare-outline.png" alt="Quick outline">
-    </td>
-  </tr>
-  
-    <tr id="java-compare-reconcile">
-    <td width="30%" valign="top" align="left">
-        <b>Reconcile Java compare structure while typing</b>
-    </td>
-    <td width="70%" valign="top">
-        The Java compare editor now updates its structure while you are typing inside the editor.
-        <p><img src="images/dynamic-structure-compare.png" alt="Dynamic structure comparison"></p>
-    </td>
-  </tr>
-  
-    
-  <!-- *************** Java Refactoring ************************************ -->
-    <tr> 
-      <td colspan="2"><a name="JavaRefactoring"></a> <div style="font-size: 20px; font-weight: bold;"> 
-          Java Refactoring and Source Actions</div></td>
-    </tr>
-
-  <tr id="generate-tostring">
-    <td width="30%" valign="top" align="left">
-        <b>Generate toString()</b>
-    </td>
-    <td width="70%" valign="top">
-        The new toString() generator allows you to quickly generate a toString() method for your class.
-        <b>Source</b> &gt; <b>Generate toString()...</b> offers several options to configure the
-        format of the resulting String and the style of the generated code in the toString() method body.
-       <p><img src="images/generate-tostring-dialog.png" alt="Generate toString() dialog"></p>
-    </td>
-  </tr>
-
-  <tr id="use-blocks">
-    <td width="30%" valign="top" align="left">
-        <b>Optionally use blocks when generating hashCode() and equals()</b>
-    </td>
-    <td width="70%" valign="top">
-    	The <b>Generate hashCode() and equals()</b> wizard now allows you to choose
-    	whether blocks are used for <code>if</code> statements:
-		<p><img src="images/hashcode-and-equals-wizard.png" alt="Generate hashCode() and equals() wizard"></p>
-    </td>
-  </tr>
-     
-    <!-- ******************* Java Compiler ************************************* -->
-    <tr> 
-      <td colspan="2"><a name="JavaCompiler"></a> <div style="font-size: 20px; font-weight: bold;"> 
-          Java Compiler </div></td>
-    </tr>
-
-    <TR id=compiler-diagnostic>
-      <TD vAlign=top align=left width="30%"><B>Comparing identical values</B> </TD>
-      <TD vAlign=top width="70%">Comparing identical values is now detected
-          by the compiler and reported as a warning by default:
-        <P><IMG alt="Comparing Identical Values Warning Example" 
-      src="images/comparing-identical-values-example.png"></p>
-        <P>You can configure this setting in the <B>Potential programming problems</B> section
-          on the
-          <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> 
-          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-          <b>Java &gt; Compiler &gt; Errors/Warnings</b></a> preference page,
-          or by clicking the <B>Configure Problem Severity</B> button in the
-          problem hover toolbar.</P></TD>
-    </TR>
-
-  <tr id="missing-synchronized">
-    <td width="30%" valign="top" align="left">
-        <b>Missing synchronized modifier</b>
-    </td>
-    <td width="70%" valign="top">
-    	The compiler now issues a warning when a method overrides a synchronized method
-    	but the method itself is not synchronized.
-    	<p><img src="images/missing-synchronized.png" alt="Problem hover with quick fix for missing synchronized modifier"></p>
-    	You can use the quick fix to add the <code>synchronized</code> modifier, and you can
-    	configure the problem severity on
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> 
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-        <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b></a> 
-    	in the <b>Potential programming problems</b> section.
-    </td>
-  </tr>
-
-  <tr id="switch-case-fall-through">
-    <td width="30%" valign="top" align="left">
-        <b>Suppress compiler problem for 'switch' case fall-through</b>
-    </td>
-    <td width="70%" valign="top">
-        The compiler problem for expected fall-throughs in switch case statements can now be suppressed by preceding
-        the following <code>case</code> statement with a comment that starts with $FALL-THROUGH$. This is especially
-		interesting for code that can't use the J2SE-5.0-style <code>@SuppressWarnings("fallthrough")</code> annotation.
-    	<p><img src="images/switch-case-fall-through.png" alt="Problem hover with quick fixes for switch case fall-through"></p>
-    	This problem is not reported by default. You can enable the <b>'switch' case fall-through</b> warning on
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> 
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-        <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b></a> 
-    	in the <b>Potential programming problems</b> section.
-    </td>
-  </tr>
-
-  <tr id="hash-code-compiler-diagnostic"> 
-    <td width="30%" valign="top" align="left">
-        <b>Missing hashCode() method</b>
-    </td>
-    <td width="70%" valign="top">
-    	The compiler can now detect whether a class overrides the <code>equals()</code> method
-    	without overriding the <code>hashCode()</code> method:
-    	<p><img src="images/compiler-hashcode-diagnosis.png" alt="Problem hover with quick fix for missing hashCode method"></p>
-    	<p>You can either use the quick fix to override the <code>hashCode()</code> method or the quick fix to regenerate both methods.</p>
-    	<p>This problem is not reported by default. You can enable it on
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> 
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-        <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b></a> 
-    	in the <b>Potential programming problems</b> section.</p>
-    </td>
-  </tr>
-
-  <tr id="deadCode-diagnostic"> 
-    <td width="30%" valign="top" align="left">
-		<b>Dead code</b>
-    </td>
-
-    <td width="70%" valign="top">
-      The compiler can now issue a warning if dead code is detected.
-      <p> For instance, <code>if (false) foo();</code> is not reported as truly unreachable code by the Java Language Specification. 
-             When this diagnostic is enabled, the invocation of foo() is signaled as dead code:</p>
-      <p><img src="images/compiler-deadcode-diagnosis.png" alt="Problem hover with quick fix for dead code"></p>
-      <p>This problem is reported as a warning by default.  You can configure the problem severity on
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'> 
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Errors/Warnings preference page">
-        <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b></a> 
-	    	in the <b>Potential programming problems</b> section</p>
-      <p>Note that dead code following an <code>if (constant variable)</code> statement, e.g. <code>if (DEBUG)</code>, is not reported.</p>
-    </td>
-  </tr>
-
-  <tr id="class-path-header"> 
-    <td width="30%" valign="top" align="left">
-		<b>Classpath resolution honors the 'Class-Path' header of JAR manifest file</b>
-    </td>
-    <td width="70%" valign="top">
-      The 'Class-Path' header of a JAR manifest is now honored in the Java model. JARs defined by 'Class-Path' are now automatically
-      added to the build path.
-      <p>For example, 'nested.jar' is a referenced library although it was not explicitly specified in the project build path
-      but through the manifest of 'lib.jar':</p>
-      <p><img src="images/class-path-header.png" alt="Class-Path Clause Example"></p>  
-    </td>
-  </tr>
-
-  <tr id="relative-build-path"> 
-    <td width="30%" valign="top" align="left">
-		<b>Build path supports ".."</b>
-    </td>
-    <td width="70%" valign="top">
-      The path of a library, variable or container entry can now be anywhere relative to the project,
-      e.g. if the library is on a sibling directory, its path can be specified using the ".." as follows:
-      <p><img src="images/build-path-dot-dot-path.png" alt="Parent Relative Path Example"></p>  
-    </td>
-  </tr>
-
-  <tr id="duplicate-build-path-diagnostic"> 
-    <td width="30%" valign="top" align="left">
-		<b>Build path resolution tolerates duplicate entries</b>
-    </td>
-    <td width="70%" valign="top">
-      Duplicate entries in the build path are now tolerated if the redundant entry is found while resolving the build path
-      and not at the raw level.
-      <p>For example, two user libraries used in the project build path referring to the same JAR file are tolerated:</p>
-      <p><img src="images/build-path-duplicate-entries.png" alt="Classpath Duplicate Entries Example"></p>
-      However, an error is reported if the same JAR file is directly specified twice:
-      <p><img src="images/build-path-invalid-dups.png" alt="Classpath Invalid Duplicate Entries Example"></p>
-    </td>
-  </tr>
-
-  <tr id="compliance-follows-execution-environment">
-    <td width="30%" valign="top" align="left">
-        <b>Compiler compliance follows execution environment</b>
-    </td>
-    <td width="70%" valign="top">
-        When you change the JRE on the build path of a Java project to an execution 
-        environment, Eclipse now automatically updates the compiler compliance settings 
-        on the <b>Java Compiler</b> properties page to use the settings defined by the execution environment.
-       <p><img src="images/compliance-follows-ee.png" alt="Java Compiler properties page"></p>
-       <p>Note that as of 3.5, an execution environment is the first choice when 
-       creating a new Java project or a launch configuration.</p>
-    </td>
-  </tr>
-
-   <!-- ******************* Java Views and Dialogs ************************************* -->
-     
-     <tr> 
-      <td colspan="2"><a name="JavaViews"></a> <div style="font-size: 20px; font-weight: bold;"> 
-          Java Views and Dialogs</div></td>
-    </tr>
-
-  <tr id="open-type">
-    <td width="30%" valign="top" align="left">
-        <b>Emphasized matching characters in Open Type dialog</b>
-    </td>
-    <td width="70%" valign="top">
-        The <b>Open Type</b> dialog now emphasizes the characters that match the pattern:
-       <p><img src="images/open-type.png" alt="Emphasized matching characters in Open Type dialog"></p>
-    </td>
-  </tr>
-
-  <tr id="sort-working-sets">
-    <td width="30%" valign="top" align="left">
-        <b>Sort working sets in Package Explorer</b>
-    </td>
-    <td width="70%" valign="top">
-        The <b>Configure Working Sets...</b> dialog now has a <b>Sort working sets</b> option to sort working sets alphabetically.
-	    The setting is preserved, so the working sets stay sorted, even as new working sets are added.
-       <p><img src="images/sort-working-sets.png" alt="Sort working sets in Package Explorer"></p>
-        You can enable working sets in the Package Explorer via the <b>Top Level Elements</b> &gt; <b>Working Sets</b> view menu.
-    </td>
-  </tr>
-
-  <tr id="delete-workingSets">
-    <td width="30%" valign="top" align="left">
-        <b>Delete working sets from the Package Explorer</b>
-    </td>
-    <td width="70%" valign="top">
-    	The <b>Delete</b> functionality is now enabled for working sets when the top level 
-    	elements are Working Sets in the Package Explorer. When deleting working sets, you can now either remove or
-    	just hide them from the Package Explorer: 
-       <p> <img src="images/delete-working-set.png" alt="Delete working sets from a Package Explorer"></p> 
-    </td>
-  </tr>
-
-  <tr id="paste-patch">
-    <td width="30%" valign="top" align="left">
-        <b>Paste patch into Package Explorer</b>
-    </td>
-    <td width="70%" valign="top">
-    	What's the quickest way to apply a patch from Bugzilla? Just open the attachment,
-    	copy the patch to the clipboard and paste it into the <b>Package Explorer</b>.
-    </td>
-  </tr>
-  
-  <tr id="expand-with-constructors">
-    <td width="30%" valign="top" align="left">
-        <b>Call Hierarchy can expand with constructors</b>
-    </td>
-    <td width="70%" valign="top">
-        In Callers mode, the Call Hierarchy now has an <b>Expand With Constructors</b> action in the context menu for instance methods.
-        <p>
-        This action replaces the normal children of the method with
-        </p>
-        <ul>
-        <li> the constructors of the method's declaring class</li>
-        <li> a node that contains the direct callers of the method.</li>
-        </ul>
-        This is useful for methods in anonymous classes, for example to follow the callers that create a <code>Runnable</code>,
-        instead of those which actually call its <code>run()</code> method.
-        <p><img src="images/expand-with-constructors.png" alt="Expand With Constructors"></p>
-        <p>Some methods (e.g. <code>java.lang.Runnable#run()</code>) are expanded with constructors by default.
-        The defaults can be configured in the view menu.</p>
-    </td>
-  </tr>
-  
-    <TR id=javadoc-hover>
-      <TD vAlign=top align=left width="30%"><B>Improved Javadoc view and hover</B> </TD>
-      <TD vAlign=top width="70%">The Javadoc view and hovers now support the <STRONG>{@inheritDoc}</STRONG> tag
-        and add links to overridden methods (like the Javadoc tool):
-        <P><img alt="Improved Javadoc hover" 
-      src="images/javadoc-hover.png"></p>
-        <P>Moreover, the message for deprecated elements now shows up on top,
-          and relative links are supported (for example, to embed images from
-          the 
-      "doc-files" directory or to link to <STRONG>{@docRoot}</STRONG>). </P></TD>
-    </TR>
-
-  <tr id="open-jar-export-wizard">
-    <td width="30%" valign="top" align="left">
-        <b>Open *.jardesc files with JAR Export Wizard</b>
-    </td>
-    <td width="70%" valign="top">
-        Opening *.jardesc files now launches the JAR Export Wizard by default.
-    	<p><img src="images/jar-export.png" alt="Open With &gt; JAR Export Wizard"></p>
-    	<p>The <b>Open JAR Packager...</b> action in the context menu is gone.</p>
-    </td>
-  </tr>
-
-  <tr id="open-in-junit-view">
-    <td width="30%" valign="top" align="left">
-        <b>Open test result files in JUnit view</b>
-    </td>
-    <td width="70%" valign="top">
-        JUnit test result files from Eclipse or the Ant JUnit tasks can now be opened in the JUnit view via
-        double click or via <b>Open With &gt; JUnit View</b>.
-    	<p><img src="images/open-in-junit-view.png" alt="Open With &gt; JUnit View"></p>
-    	<p>If the files are not inside your workspace, you can still open them
-    	from the JUnit view via the <b>Test Run History...</b> drop-down menu.
-    	And the <b>Import...</b> and <b>Export...</b> actions now always start at the most recently used location.</p>
-    	<p><img src="images/junit-view-import.png" alt="Test Run History... &gt; Import"></p>
-    </td>
-  </tr>
-  
-    <tr id="junit4.5">
-    <td width="30%" valign="top" align="left">
-        <b>JUnit 4.5</b>
-    </td>
-    <td width="70%" valign="top">
-    	The JUnit4 version shipped with Eclipse has been updated to 4.5.
-    	See their <a href="http://sourceforge.net/project/shownotes.php?release_id=618683&amp;group_id=15278">Release Notes</a>
-    	for the changes in version 4.5.
-    </td>
-  </tr>
-  
-  <tr id="jar-in-jar-exporter">
-    <td width="30%" valign="top" align="left">
-        <b>Runnable Jar-in-Jar exporter can package libraries</b>
-    </td>
-    <td width="70%" valign="top">
-    	The Runnable JAR File Export wizard can now also package the required libraries into the exported runnable JAR file
-    	or into a folder next to the JAR:
-       <p> <img src="images/runnable-jar-in-jar-export.png" alt="Runnable JAR File Export wizard"></p>
-       <p> The advantage of the second and third options is that the required libraries
-         will just be copied and don't need be repackaged. </p>
-    </td>
-  </tr>
-
-    <!-- ****************** END OF N&N TABLE ****************** -->
-  </tbody>
-</table>
-
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.pde.doc.user/.classpath b/bundles/org.eclipse.pde.doc.user/.classpath
deleted file mode 100644
index 73fb5bf..0000000
--- a/bundles/org.eclipse.pde.doc.user/.classpath
+++ /dev/null

@@ -1,5 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<classpath>
-    <classpathentry kind="src" path=""/>
-    <classpathentry kind="output" path="bin"/>
-</classpath>

diff --git a/bundles/org.eclipse.pde.doc.user/.cvsignore b/bundles/org.eclipse.pde.doc.user/.cvsignore
deleted file mode 100644
index 4559c72..0000000
--- a/bundles/org.eclipse.pde.doc.user/.cvsignore
+++ /dev/null

@@ -1,2 +0,0 @@
-pdeOptions.tmp.txt
-.project.screem

diff --git a/bundles/org.eclipse.pde.doc.user/.project b/bundles/org.eclipse.pde.doc.user/.project
deleted file mode 100644
index 7d8c4b1..0000000
--- a/bundles/org.eclipse.pde.doc.user/.project
+++ /dev/null

@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<projectDescription>

-	<name>org.eclipse.pde.doc.user</name>

-	<comment></comment>

-	<projects>

-	</projects>

-	<buildSpec>

-		<buildCommand>

-			<name>org.eclipse.pde.ManifestBuilder</name>

-			<arguments>

-			</arguments>

-		</buildCommand>

-		<buildCommand>

-			<name>org.eclipse.pde.SchemaBuilder</name>

-			<arguments>

-			</arguments>

-		</buildCommand>

-	</buildSpec>

-	<natures>

-		<nature>org.eclipse.pde.PluginNature</nature>

-	</natures>

-</projectDescription>


diff --git a/bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF b/bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index bae5149..0000000
--- a/bundles/org.eclipse.pde.doc.user/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,7 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.pde.doc.user; singleton:=true
-Bundle-Version: 3.6.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin

diff --git a/bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt b/bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt
deleted file mode 100644
index 20c2dc1..0000000
--- a/bundles/org.eclipse.pde.doc.user/aaa-how-to-add-things.txt
+++ /dev/null

@@ -1,10 +0,0 @@
-The information that was here has been moved to:
-
-http://wiki.eclipse.org/index.php/How_to_add_things_to_the_Eclipse_doc
-
-
-Differences for pde.doc.isv:
-
-- platformOptions.txt    -> pdeOptions.txt
-                            
-- overview-platform.html -> /reference/misc/overview-pde.html

diff --git a/bundles/org.eclipse.pde.doc.user/about.html b/bundles/org.eclipse.pde.doc.user/about.html
deleted file mode 100644
index 89f7b1a..0000000
--- a/bundles/org.eclipse.pde.doc.user/about.html
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2001, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page."/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>June 2, 2006</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise 
-indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available 
-at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is 
-being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was 
-provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/about.mappings b/bundles/org.eclipse.pde.doc.user/about.mappings
deleted file mode 100644
index bddaab4..0000000
--- a/bundles/org.eclipse.pde.doc.user/about.mappings
+++ /dev/null

@@ -1,6 +0,0 @@
-# about.mappings
-# contains fill-ins for about.properties
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# This file does not need to be translated.
-
-0=@build@
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/about.properties b/bundles/org.eclipse.pde.doc.user/about.properties
deleted file mode 100644
index e3fea02..0000000
--- a/bundles/org.eclipse.pde.doc.user/about.properties
+++ /dev/null

@@ -1,24 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2006 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-# about.properties
-# contains externalized strings for about.ini
-# java.io.Properties file (ISO 8859-1 with "\" escapes)
-# fill-ins are supplied by about.mappings
-# This file should be translated.
-
-blurb=Eclipse Plug-in Development Environment User Guide\n\
-\n\
-Version: {featureVersion}\n\
-Build id: {0}\n\
-\n\
-(c) Copyright IBM Corp. and others 2000, 2003.  All rights reserved.\n\
-Visit http://www.eclipse.org/pde
-

diff --git a/bundles/org.eclipse.pde.doc.user/apache_style.css b/bundles/org.eclipse.pde.doc.user/apache_style.css
deleted file mode 100644
index ecd9d3d..0000000
--- a/bundles/org.eclipse.pde.doc.user/apache_style.css
+++ /dev/null

@@ -1,66 +0,0 @@
-/*
- *  Licensed to the Apache Software Foundation (ASF) under one or more
- *  contributor license agreements.  See the NOTICE file distributed with
- *  this work for additional information regarding copyright ownership.
- *  The ASF licenses this file to You under the Apache License, Version 2.0
- *  (the "License"); you may not use this file except in compliance with
- *  the License.  You may obtain a copy of the License at
- *
- *      http://www.apache.org/licenses/LICENSE-2.0
- *
- *  Unless required by applicable law or agreed to in writing, software
- *  distributed under the License is distributed on an "AS IS" BASIS,
- *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- *  See the License for the specific language governing permissions and
- *  limitations under the License.
- *
- */
-h2 {
-  font-size: 200%;  
-  background-color: #ffffff;
-}
-
-h3 {
-  font-size: 130%;
-  color:     #ffffff;
-  background-color: #525D76;
-}
-
-h4 {
-  color:  #ffffff;
-  background-color: #828DA6;
-}
-
-td {
-   background-color: #eeeeee;
-   color:            #000000;
-}
-
-/* first row */
-table tr:first-child td {
-   background-color: #cccccc;
-   color:            #000000;
-}
-
-/* or th as first row */
-table th {
-   background-color: #cccccc;
-   color:            #000000;
-}
-
-pre {
-   background-color: #efefef;
-}
-
-/* code snippets in examples and tutorials */
-.code { 
-   background: #EFEFEF; 
-   margin-top: 
-}
-
-/* highlight console output */
-.output { 
-   color: #FFFFFF; 
-   background: #837A67; 
-}
-

diff --git a/bundles/org.eclipse.pde.doc.user/api_contexts.xml b/bundles/org.eclipse.pde.doc.user/api_contexts.xml
deleted file mode 100644
index 5fcb692..0000000
--- a/bundles/org.eclipse.pde.doc.user/api_contexts.xml
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/book.css b/bundles/org.eclipse.pde.doc.user/book.css
deleted file mode 100644
index 5b2e9c8..0000000
--- a/bundles/org.eclipse.pde.doc.user/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/build.properties b/bundles/org.eclipse.pde.doc.user/build.properties
deleted file mode 100644
index 1d0e0d7..0000000
--- a/bundles/org.eclipse.pde.doc.user/build.properties
+++ /dev/null

@@ -1,39 +0,0 @@
-###############################################################################
-#  Copyright (c) 2000, 2007 IBM Corporation and others.
-#  All rights reserved. This program and the accompanying materials
-#  are made available under the terms of the Eclipse Public License v1.0
-#  which accompanies this distribution, and is available at
-#  http://www.eclipse.org/legal/epl-v10.html
-# 
-#  Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-
-customBuildCallbacks=customBuildCallbacks.xml
-
-#the "index*/" entry only exists after the customBuildCallbacks run, we
-#use the '*' to avoid a warning
-bin.includes = META-INF/,\
-               about.html,\
-               about.ini,\
-               about.properties,\
-               about.mappings,\
-               api_contexts.xml,\
-               apache_style.css,\
-               book.css,\
-               concepts/,\
-               contexts_PDE.xml,\
-               guide/,\
-               images/,\
-               index*/,\
-               notices.html,\
-               plugin.properties,\
-               plugin.xml,\
-               reference/,\
-               schema.css,\
-               tasks/,\
-               tips/,\
-               toc.xml,\
-               topics_Reference.xml,\
-               topics_Tasks.xml,\
-               whatsNew/

diff --git a/bundles/org.eclipse.pde.doc.user/buildDoc.xml b/bundles/org.eclipse.pde.doc.user/buildDoc.xml
deleted file mode 100644
index 786e970..0000000
--- a/bundles/org.eclipse.pde.doc.user/buildDoc.xml
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/concepts/extension.htm b/bundles/org.eclipse.pde.doc.user/concepts/extension.htm
deleted file mode 100644
index bf6e5b0..0000000
--- a/bundles/org.eclipse.pde.doc.user/concepts/extension.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

-"http://www.w3.org/TR/html4/loose.dtd">

-<html lang="en">

-<head>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-<title>Extensions and Extension Points</title>

-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">

-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>

-</head>

-

-<body>

-<h1>Extensions and Extension Points</h1>

-

-<p>A basic rule for building modular software systems is to avoid tight 

-coupling between components.  If components are tightly integrated,

-it becomes difficult to assemble the pieces into

-different configurations or to replace a component with a different implementation

-without causing a ripple of changes across the system.</p>

-

-<p>Loose coupling in Eclipse is achieved partially through the mechanism 

-of <strong>extensions</strong> and <strong>extension points</strong>. 
-The simplest metaphor for describing extensions and extension points is electrical 
-outlets. The outlet, or socket,

-is the extension point; the plug, or light bulb that connects to it, the

-extension. As with electric outlets, extension points come in a wide

-variety of shapes and sizes, and only the extensions that are designed

-for that particular extension point will fit.</p>

-

-<p>When a plug-in wants to allow other plug-ins to extend or customize

-portions of its functionality, it will declare an extension

-point.  The extension point declares a contract, typically a combination 

-of XML markup and Java interfaces, that extensions must conform to.

-Plug-ins that want to connect to that extension point must implement

-that contract in their extension.  The key attribute is that the plug-in

-being extended knows nothing about the plug-in that is connecting to

-it beyond the scope of that extension point contract. This allows plug-ins

-built by different individuals or companies to interact seamlessly, even

-without their knowing much about one another.</p>

-

-<p>The Eclipse Platform has many applications of the extension 

-and extension point concept.  Some extensions are entirely

-<i>declarative</i>; that is, they contribute no code at all.  For example,

-one extension point provides customized key bindings,

-and another defines custom file annotations, called <i>markers</i>;

-neither of these extension points requires any code on behalf of the extension. 

-</p>
-
-<p>Another category of extension points is for overriding the default behavior of 

-a component.  For example, the Java development tools include a 

-code formatter but also supply an extension point for third-party 

-code formatters to be plugged in.  The resources plug-in has an

-extension point that allows certain plug-ins to replace the implementation

-of basic file operations, such as moving and deletion. </p>

-

-<p>Yet another category

-of extension points is used to group related elements in the user

-interface.  For example, extension points for providing views,

-editors, and wizards to the UI allow the base UI plug-in to group

-common features, such as

-putting all import wizards into a single dialog,

-and to define a consistent way of presenting UI contributions from a wide 

-variety of other plug-ins.</p>

-
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../guide/tools/editors/manifest_editor/extensions.htm">Extensions  (Plug-in Editor)</a><br>
-<a href="../guide/tools/editors/manifest_editor/extension_points.htm">Extension Points (Plug-in Editor)</a>
-</p>
-
-<p><img src="../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="plugin.htm">Plug-in</a>
-</p>
-
-</body>

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/concepts/feature.htm b/bundles/org.eclipse.pde.doc.user/concepts/feature.htm
deleted file mode 100644
index 89af499..0000000
--- a/bundles/org.eclipse.pde.doc.user/concepts/feature.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

-"http://www.w3.org/TR/html4/loose.dtd">

-<html lang="en">

-<head>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-<title>Feature</title>

-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">

-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>

-</head>

-

-<body>

-<h1>Feature</h1>

-
-<p>A <strong>Feature</strong> is used to package a group of plug-ins together into a single installable and updtable unit.</p>
-
-<p>Features have a manifest that provides basic information

-about the feature and its content. Content may include plug-ins, fragments and

-any other files that are important for the feature. A feature can also include other features.
-The delivery format for a feature is a JAR, but each included plug-in will be provided as a separate JAR.</p>
-

-<p>Once you have created your plug-ins and fragments you can create a new feature 
-by creating a <a href="../guide/tools/project_wizards/new_feature_project.htm">New Feature Project</a>.</p>
-
-<p>You can also create <a href="../guide/tools/project_wizards/new_feature_patch.htm">Feature Patches</a> in PDE.  A feature patch is developed in the same fashion as a normal feature, but is used to edit an existing feature rather than create a new one.</p>
-

-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../guide/tools/editors/feature_editor/feature_editor.htm">Feature Editor</a><br>
-<a href="../guide/tools/project_wizards/new_feature_project.htm">New Feature Project</a><br>
-<a href="../guide/tools/project_wizards/new_feature_patch.htm">New Feature Patch Project</a>
-</p>
-
-<p><img src="../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="plugin.htm">Plug-in</a><br>
-<a href="fragment.htm">Fragment</a><br>
-<a href="product.htm">Product</a><br>
-<a href="update_site.htm">Update Site</a>
-</p>

-
-</body>

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/concepts/fragment.htm b/bundles/org.eclipse.pde.doc.user/concepts/fragment.htm
deleted file mode 100644
index a1d2de1..0000000
--- a/bundles/org.eclipse.pde.doc.user/concepts/fragment.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

-"http://www.w3.org/TR/html4/loose.dtd">

-<html lang="en">

-<head>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-<title>Fragment</title>

-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">

-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>

-</head>

-

-<body>

-<h1>Fragment</h1>
-

-<p>A <strong>fragment</strong> is used to replace or extend the functionality of
-an existing plug-in.  A common use for fragments is to put environment (operating system,
-architecture, etc.) specific code into fragments.  Depending on the environment the 
-plug-in is installed in the base plug-in code along with the correct fragment can be installed.
-Fragments are also ideal for shipping features like language or maintenance packs that typically 

-trail the initial products for a few months.</p>
-

-<p>When a fragment is detected by the platform and its parent plug-in is found, 

-the fragment's libraries, extensions and extension points are &quot;merged&quot; with 

-those of the parent plug-in. </p>
-

-<p>While this merging mechanism is good from a runtime point of view,

-developers need to view fragments as separate entities while working on them.</p>
-

-<p>PDE provides full support for fragment development. Fragments can be viewed as

-&quot;limited plug-ins&quot;. They have all of the capability of regular

-plug-ins but have no concept of life-cycle. Fragments have no top-level class

-with &quot;startup&quot; and &quot;shutdown&quot; methods.</p>
-
-<p>To create a fragment use the <a href="../guide/tools/project_wizards/new_fragment_project.htm">New Fragment Project</a>
-wizard.  Editing fragments is very similar to editing plug-ins.</p>

-
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../guide/tools/editors/manifest_editor/editor.htm">Plug-in Editor</a><br>
-<a href="../guide/tools/project_wizards/new_fragment_project.htm">New Fragment</a>
-</p>
-
-<p><img src="../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="plugin.htm">Plug-in</a><br>
-<a href="feature.htm">Feature</a><br>
-</p>
-
-

-</body>

-

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/concepts/plugin.htm b/bundles/org.eclipse.pde.doc.user/concepts/plugin.htm
deleted file mode 100644
index a8005af..0000000
--- a/bundles/org.eclipse.pde.doc.user/concepts/plugin.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

-"http://www.w3.org/TR/html4/loose.dtd">

-<html lang="en">

-<head>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-<title>Plug-in</title>

-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">

-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>

-</head>

-

-<body>

-<h1>Plug-in</h1>

-

-<p>A <strong>plug-in</strong> is used to group your code into a modular, extendable and sharable unit.</p>
-
-<p>Plug-ins are <em>modular</em> as each plug-in contains some portion of code.  The plug-in specifies other plug-ins (or java packages) it requires to be available to run and it also specifies the set of java packages it provides.  An Eclipse based program or <a href="product.htm">product</a> will contain multiple plug-ins, which can be added, replaced or removed to alter the functionality of the program.</p>
-
-<p>Plug-ins are <em>extendable</em> using <a href="extension.htm">extensions and extension points</a>.  A plug-in can provide one or more extension points so other plug-ins can add to the functionality of the plug-in.  A plug-in may also provide extensions to connect to other plug-ins.</p>
-
-<p>Plug-ins are <em>sharable</em>.  A plug-in can be exported as a directory or as a jar which can be added to other applications.  Plug-ins can be grouped into <a href="feature.htm">features</a> which can be distributed and installed into applications.</p>
-
-<p>Eclipse plug-ins are based on OSGi bundles.  OSGi is used to manage the plug-ins in an Eclipse application.  A plug-in must contain a manifest file with valid OSGi headers for plug-in name and version.  Extensions and extension points functionality added by Eclipse in addition to OSGi.  To use extensions you must provide a plugin.xml file.  PDE provides a full featured <a href="../guide/tools/project_wizards/new_plugin_project.htm">project</a> and <a href="../guide/tools/editors/manifest_editor/editor.htm">editor</a> for creating and editing these files.</p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../guide/tools/editors/manifest_editor/editor.htm">Plug-in Editor</a><br>
-<a href="../guide/tools/project_wizards/new_plugin_project.htm">New Plug-in Project</a>
-</p>
-
-<p><img src="../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="fragment.htm">Fragment</a><br>
-<a href="feature.htm">Feature</a><br>
-</p>
-

-</body>

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/concepts/product.htm b/bundles/org.eclipse.pde.doc.user/concepts/product.htm
deleted file mode 100644
index dd619eb..0000000
--- a/bundles/org.eclipse.pde.doc.user/concepts/product.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

-"http://www.w3.org/TR/html4/loose.dtd">

-<html lang="en">

-<head>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-<title>Product</title>

-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">

-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>

-</head>

-

-<body>

-<h1>Product</h1>

-

-<p>An Eclipse based <strong>product</strong> is a stand-alone program built with the

-Eclipse platform.  A product may optionally be packaged and delivered as one or more

-<a href="feature.htm">features</a>, which are simply groupings of plug-ins that are 
-managed as a single entity by the Eclipse update mechanisms.</p>
-

-<p>Products include all the code and plug-ins needed to run them. This

-includes a Java runtime environment (JRE) and the Eclipse platform code.

-The plug-in code, JRE, and Eclipse platform are typically installed with a

-product-specific installation program. Product providers are free to use

-any installation tool or program that is appropriate for their needs. </p>
-

-<p>Once installed, the user launches the product and is presented with an

-Eclipse workbench configured specifically for the purpose supported by the

-product, such as web development, C++ program development, or any other

-purpose. The platform makes it easy to configure labels, about dialogs,

-graphics, and splash screens, so that the user has no concept of a platform

-workbench, but instead views the workbench as the main window of the product

-itself.</p>
-
-<p>PDE provides a <a href="../guide/tools/file_wizards/new_product_config.htm">product 
-configuration</a> file and associated <a href="../guide/tools/editors/product_editor/editor.htm">editor</a>
-to make it easy to create products in the correct format.</p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../guide/tools/editors/product_editor/editor.htm">Product Editor</a><br>
-<a href="../guide/tools/editors/product_editor/editor.htm">New Product Configuration</a>
-</p>
-
-<p><img src="../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="plugin.htm">Plug-in</a><br>
-<a href="fragment.htm">Fragment</a><br>
-<a href="feature.htm">Feature</a><br>
-</p>
-
-</body>

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/concepts/target.htm b/bundles/org.eclipse.pde.doc.user/concepts/target.htm
deleted file mode 100755
index f0f8844..0000000
--- a/bundles/org.eclipse.pde.doc.user/concepts/target.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Target Platform</title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Target Platform</h1>
-
-<p>The <strong>Target Platform</strong> refers to the plug-ins which your workspace will be built and run against.  It describes the platform that you are developing for.  When developing with PDE, the target platform is used to:</p>
-<ol>
-<li>Compile - Plug-ins in the workspace are built against the target platform so you do not have to have everything in your workspace</li>
-<li>Launch - When using PDE's launchers you can choose the set of plug-ins you want to launch.  By default the Eclipse Application Launcher will start with all plug-ins in the target, but will use workspace plug-ins instead when available</li>
-<li>Calculate Dependencies - PDE assists you in finding the plug-ins your plug-ins was include/require to compile correctly by looking at what is available in the target platform</li>
-<li>State - An OSGi state is created for the target platform so it can be used by other tooling.  The state can also be viewed in detail using the Target Platform State View</li>
-<li>Other Tools - Other PDE tools use the target platform to determine their options, such as the import wizards</li>
-</ol>
-
-<p>Whereas the target platform refers to your currently active bundles, a <em>Target Definition</em> is a way of determining the plug-ins to add to the state.  You can have multiple target definitions, but only one definition can be selected as the target platform.</p>
-
-<p>The target platform and your target definitions are managed on the Target Platform Preference Page.  This page lists all target definitions that PDE has access to and displays which definition is being used as your current target platform.  Target definitions can be created and edited here using the Target Definition Content Wizard.  To make for easier sharing among a development team, targets can also be created and edited in the workspace as xml files with the extension ".target".  These files can be edited using the target definition editor and can be created using the New Target Definition Wizard.</p>
-
-<p>By default PDE provides a default target platform which simply points to the plug-ins in your currently running Eclipse instance (often referred to as your host).  For Eclipse plug-in developers this might be all you need.  RCP developers must be more careful managing their target as adding dependencies increases the size and complexity of their application.  When creating a new target definition for RCP, consider using the RCP template (available with or without source).</p>
-
-<p>For up to the minute target troubleshooting help see the <a href="http://wiki.eclipse.org/PDE/Target_Definitions">Target Definitions Wiki Page</a>.</p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../guide/tools/preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="../guide/tools/target_shared/edit_target_wizard.htm">Edit Target Definition Wizard</a><br>
-<a href="../guide/tools/editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="../guide/tools/launchers/eclipse_application_launcher.htm">Eclipse Application Launcher</a><br>
-<a href="../guide/tools/launchers/eclipse_plugins.htm">Eclipse Application Launcher Plug-ins Tab</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/concepts/update_site.htm b/bundles/org.eclipse.pde.doc.user/concepts/update_site.htm
deleted file mode 100644
index 3600bdf..0000000
--- a/bundles/org.eclipse.pde.doc.user/concepts/update_site.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

-"http://www.w3.org/TR/html4/loose.dtd">

-<html lang="en">

-<head>

-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >

-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

-<title>Update Site</title>

-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">

-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>

-</head>

-

-<body>

-<h1>Update Site</h1>

-

-<p><strong>Update Sites</strong> are used to organize and export features so they
-can be installed into Eclipse applications.</p>
-
-<p>To create an update site you must develop a site.xml file and build the site.  PDE provides an 
-<a href="../guide/tools/editors/site_editor/site_editor.htm">editor</a> and 
-<a href="../guide/tools/project_wizards/new_update_site_project.htm">project</a> for 
-creating sites.  A site will contain one or more <a href="feature.htm">features</a> 
-organized into categories.</p>
-
-<p>When the site is built, the included features (along with all plug-ins part of those features) 
-will be exported into an installable form.  The exported plug-ins and features will be put into two
-folders &quot;plugins&quot; and &quot;features&quot;.  Two other files, &quot;content.xml&quot;
-and &quot;artifacts.xml&quot; will also be generated and contain metadata for the exported files
-that make installing easier.  These files, along with &quot;site.xml&quot;, collectively form an Eclipse update
-site.  To make the update site available to others you must make all these files available 
-in a shared directory or web site.</p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../guide/tools/editors/site_editor/site_editor.htm">Site Editor</a><br>
-<a href="../guide/tools/project_wizards/new_update_site_project.htm">New Update Site Project</a>
-</p>
-
-<p><img src="../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="feature.htm">Feature</a><br>
-<a href="plugin.htm">Plug-in</a><br>
-</p>
-
-</body>

-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/contexts_PDE.xml b/bundles/org.eclipse.pde.doc.user/contexts_PDE.xml
deleted file mode 100644
index 7a62e95..0000000
--- a/bundles/org.eclipse.pde.doc.user/contexts_PDE.xml
+++ /dev/null

@@ -1,1021 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Actions -->
-	<context id="open_manifest">
-		<description>This action opens the manifest files contained in the selected plug-in project(s).</description>
-	</context>
-	<context id="organize_manifest">
-		<description>This action organizes and cleans up the manifest files contained in the selected plug-in project(s).</description>
-		<topic label="Organizing Manifest Files" href="guide/tools/pde_actions/organize_manifests.htm"/>
-	</context>
-	<context id="update_classpath">
-		<description>PDE computes the classpath of this project by looking for dependencies in the workspace and enabled external plug-ins and fragments.</description>
-		<topic label="Updating Classpaths" href="guide/tools/pde_actions/update_classpaths.htm"/>
-	</context>
-	<context id="open_dependencies">
-		<description>This command opens the Dependencies view to show all the plug-ins needed to run the selected plug-in.</description>
-		<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-	</context>	
-	<context id="find_references">
-		<description>This command searches for all the plug-ins that directly depend on the selected plug-in and all the fragments which target it.</description>
-		<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-  <topic href="concepts/fragment.htm" label="Fragments"/>
-	</context>
-	<context id="create_plugin_jars">
-		<description>This command builds an Ant script which can then be used to build an executable version of the plug-in.</description>
-  <topic href="guide/tools/export_wizards/export_plugins.htm" label="Export plug-in"/>
-		<topic label="Build configuration" href="guide/tools/editors/manifest_editor/build.htm"/>
-		<topic label="Deploying a plug-in" href="tasks/ui_export_install_into_host.htm"/>
-	</context>
-	<context id="create_fragment_jars">
-		<description>This command builds an Ant script which can then be used to build an executable version of the fragment.</description>
-		<topic label="Generating Ant Scripts" href="tasks/pde_feature_generating_ant.htm"/>
-		<topic label="Build configuration" href="guide/tools/editors/manifest_editor/build.htm"/>
-		<topic label="Deploying a plug-in" href="tasks/ui_export_install_into_host.htm"/>
-	</context>
-	<context id="create_feature_jars">
-		<description>This command builds an Ant script which can then be used to build a feature.</description>
-		<topic label="Features" href="concepts/feature.htm"/>
-		<topic label="Build configuration" href="guide/tools/editors/manifest_editor/build.htm"/>
-	</context>	
-	<context id="migrate_action">
-		<description>This command migrates Eclipse 3.4 plug-ins and fragments to comply with Eclipse 3.5 guidelines.</description>
-		<topic label="FAQ" href="../org.eclipse.platform.doc.isv/porting/3.5/faq.html" />
-		<topic label="Incompatibilities" href="../org.eclipse.platform.doc.isv/porting/3.5/incompatibilities.html" />
-  <topic href="../org.eclipse.platform.doc.isv/porting/3.5/recommended.html" label="Recommended"/>
-	</context>	
-	<context id="build_site">
-		<description>This command builds all the features and plug-ins contained in this site.</description>
-  <topic href="concepts/update_site.htm" label="Update Site"/>
-		<topic label="Update Site Editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/tools/project_wizards/new_update_site_project.htm"/>
-	</context>	
-	<context id="preview_schema">
-		<description>This command transforms and renders the schema into HTML format.</description>
-  <topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Creating an extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
-		<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
-	</context>			
-    <context id="history_action">
-        <description>Choose this previously shown plug-in dependency, to open it again.</description>
- 
-    </context>
-    <context id="history_list_action">
-        <description>Choose to open a dialog with all previously shown plug-in dependencies.</description>
-    </context>
-    
-<!-- Dialogs -->
- 	<context id="fragment_add_target">
- 		<description>This wizard allows you to select the target plug-in for your fragment.</description>
-   <topic href="concepts/fragment.htm" label="Fragment"/>
-		<topic label="Fragment Project" href="guide/tools/project_wizards/new_fragment_project.htm"/>
-  <topic href="guide/tools/project_wizards/fragment_content.htm" label="Fragment Content"/>
-  <topic href="guide/tools/project_wizards/fragment_structure.htm" label="Fragment Structure"/>
-	</context>
-	<context id="schema_type_restriction">
-		<description>This wizard allows you to define the possible values for the selected attribute.</description>
-		<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
-		<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
-  		<topic label="Extension point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
-  		<topic label="Extension point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>		
-	</context>
-	<context id="new_restriction_dialog">
-		<description>This wizard allows you to define a new possible value for the selected attribute.</description>
-		<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
-		<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
-  		<topic label="Extension point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
-  		<topic label="Extension point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
-	</context>
-	<context id="filtered_schema_attribute_selection_dialog">
-		<description>This dialog allows you to select which attribute of which extension point the current identifier will be based on.</description>
-		<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
-		<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
-  		<topic label="Extension point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
-  		<topic label="Extension point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
-	</context>
-	<context id="search_page">
-		<description>On this page, you can search for references to and declarations of plug-ins, fragments and extension points.
-The search can be extended beyond workspace resources to include external plug-ins. </description>
-	</context>
-	
-	<context id="plugin_selection">
-		<description>This dialog allows you to select a plug-in.</description>
-  <topic href="concepts/plugin.htm" label="Plug-in"/>
-	</context>
-	<context id="feature_selection">
-		<description>This dialog allows you to select a feature.</description>
-  <topic href="concepts/feature.htm" label="Feature"/>
-	</context>
-	<context id="product_configuration_selection">
-		<description>This dialog allows you to select a product configuration to export.</description>
-		<topic label="Product Export" href="guide/tools/export_wizards/export_product.htm"/>
-	</context>
-	
-	<context id="execution_environment_selection">
-		<description>This dialog allows you to select one or more execution environment.</description>
-		<topic label="Plug-in Overview" href="guide/tools/editors/manifest_editor/overview.htm"/>
-	</context>
-	
-	<context id="import_packages">
-		<description>This dialog allows you to add one or more packages to the list of packages imported by your bundle.</description>
-		<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-	</context>
-	<context id="imported_package_properties">
-		<description>This dialog allows you to specify version rules, and whether the dependency on the selected package is optional or not.</description>
-		<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-	</context>
-	<context id="export_packages">
-		<description>This dialog allows you to add one or more packages to the list of packages exported by your bundle.</description>
-		<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
-	</context>
-	<context id="package_selection">
-		<description>This dialog allows you to select one or more packages to export.</description>
-		<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
-	</context>
-	<context id="exported_package_properties">
-		<description>This dialog allows you to declare a version number for the selected package.</description>
-		<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
-	</context>
-	
-	<context id="imported_plugin_properties">
-		<description>This dialog allows you to edit the properties of a plug-in dependency.</description>
-		<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-	</context>
-	
-	<context id="browse_extension_points_schemas">
-		<description>This dialog lists all the extension points schema defined in the current plug-in project.</description>
-  <topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extension point schema" href="guide/tools/file_wizards/new_schema.htm"/>
-	</context>
-	<context id="container_selection">
-		<description>This dialog allows you to select the project or folder in which you want to store your extension point schema.</description>
-		<topic label="Extension point schema" href="guide/tools/file_wizards/new_schema.htm"/>
-	</context>
-	
-	<context id="jar_selection">
-		<description>This dialog allows you to select a JAR archive to add to your library plug-in.</description>
-	</context>
-
-	<context id="add_library">
-		<description>This dialog allows you to select a library or a folder of your plug-in project and add it to your plug-in classpath.</description>
-		<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm#classpath" />
-	</context>
-	<context id="new_library">
-		<description>This dialog allows you to declare a new library to add to your plug-in classpath.</description>
-		<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm#classpath" />
-	</context>
-	<context id="unused_imports_dialog">
-		<description>This dialog lists every unused or redundant entry in the list of required plug-ins and imported packages, and offers to remove them.</description>
-		<topic label="Plug-in dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm" />
-		<topic label="Dependency analysis" href="guide/tools/editors/manifest_editor/dependencies.htm#dependency_analysis" />
-	</context>
-
-	<context id="log_eventdetails">
-		<description>This dialog shows detailed information about a logged event.</description>
-	</context>
-	<context id="log_filter">
-		<description>This dialog allows you to filter the Error Log view.</description>
-	</context>
-	
-	<context id="launcher_application_selection">
-		<description>This dialog allows you to select an application to launch.</description>
-		<topic label="Eclipse Application Launcher" href="guide/tools/launchers/eclipse_application_launcher.htm" />
-	</context>
-	
-	<context id="command_composer_dialog">
-		<description>This dialog allows you to select an executable command among the ones of your development environment.
-If the selected command has parameters, you are able to edit their values.</description>
-		<topic label="Simple Cheat Sheet Editor" href="guide/tools/editors/simple_cs_editor/editor.htm" />
-		<topic label="Command Section" href="guide/tools/editors/simple_cs_editor/section_command-details.htm" />
-	</context>
-
-	<context id="loop_dialog">
-		<description>This dialog lists all the cycles detected in the dependency graph of the selected plug-in.</description>
-		<topic label="Plug-in dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm" />
-	</context>
-
-	<context id="rename_dialog">
-		<description>This dialog allows you to rename the selected element.</description>
-	</context>
-
-	<context id="new_cs_category_name_dialog">
-		<description>This dialog allows you to create a new problem domain category for the cheat sheet being registered.</description>
-		<topic label="Register Cheat Sheet Wizard" href="guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm" />
-	</context>
-
-	<context id="plugin_import_finish_dialog">
-		<description>This dialog shows a list of plug-ins for which import was not possible (probably because they already exist in read-only projects of your workspace).</description>
-	</context>
-
-	<context id="spy_dialog">
-		<description>This dialog, called the "Plug-in Spy", allows you to introspect your environment and retrieve information about your current context (active page, active selection, ...).</description>
-	</context>
-	
-	<context id="filtered_plugin_artifacts_dialog">
-		<description>This dialog lists every plug-in, extension, extension point and exported package accessible in your development environment.
-You can select any item to open it in an editor.</description>
-	</context>
-
-<!-- START:  Launchers -->
-
-	<context id="launcher_basic">
-		<description>This page allows you to set the basic program arguments to run the configuration.</description>
-		<topic label="Eclipse Application Launcher Main Tab" 
-		       href="guide/tools/launchers/eclipse_main.htm"/>
-		<!-- Note:  This context ID is shared between the Eclipse Application Launcher Main tab 
-		            and JUnit Plug-in Test Launcher Main tab.  Limitation at this point which
-		            may cause confusion
-		  -->
-	</context>
-	<context id="launcher_advanced">
-		<description>This page allows you to run your configuration with only a subset of the plug-ins.</description>
-		<topic label="Eclipse Application Launcher Plug-ins Tab" 
-			   href="guide/tools/launchers/eclipse_plugins.htm"/>
-		<!-- Note:  This context ID is shared between the Eclipse Application Launcher Plug-ins tab 
-		            and Equinox OSGi Framework Launcher Plug-ins tab.  Limitation at this point which
-		            may cause confusion
-		  -->		
-	</context>
-	<context id="launcher_tracing">
-		<description>This page allows you to use tracing flags that will cause tracing information to be printed to the standard output (or the console view) when you run the configuration.</description>
-		<topic label="Launcher Tracing Tab" 
-			   href="guide/tools/launchers/tracing.htm"/>
-		<!-- Note:  Shared context ID between all Launchers that have a Tracing Tab -->
-	</context>
-	<context id="launcher_configuration">
-		<description>This page allows you to specify the plug-ins that are to be automatically installed, and optionally started, by the runtime.</description>
-		<topic label="Eclipse Application Launcher Configuration Tab" 
-		 	   href="guide/tools/launchers/configuration.htm"/>
-		<!-- Note:  This context ID is shared between the Eclipse Application Launcher Configuration tab 
-		            and JUnit Plug-in Test Launcher Configuration tab.  Limitation at this point which
-		            may cause confusion
-		  -->			
-	</context>
-	<context id="plugin_status_dialog">
-		<description>This dialog lists every unresolvable plug-in in your launch configuration, and the corresponding unsatisfied constraint(s).</description>
-		<topic label="Eclipse Application Launcher" href="guide/tools/launchers/eclipse_application_launcher.htm" />
-	</context>
-
-<!-- END:  Launchers -->	
-	
-    <context id="history_list_dialog">
-        <description>A dialog for re-opening previously viewed plug-in dependencies.</description>
-    </context>
-    	
-<!-- START:  Editors -->
-
-	<!-- Plugin Manifest Editor -->
-
-	<context id="manifest_source_page">
-		<description>This page allows you to edit the file content directly.</description>
-	</context>
-	<context id="manifest_plugin_overview">
-		<description>The Overview page shows you the plug-in at a glance.</description>
-  <topic href="concepts/plugin.htm" label="Plug-in"/>
-		<topic label="Plug-in Overview" href="guide/tools/editors/manifest_editor/overview.htm"/>
-	</context>
-	<context id="manifest_plugin_dependencies">
-		<description>The Dependencies page shows the dependencies that your plug-in has on other plug-ins.</description>
-		<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-	</context>
-	<context id="manifest_plugin_runtime">
-		<description>The Runtime page shows information about the plug-in's runtime libraries and OSGi plug-in activation settings.</description>
-		<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
-	</context>
-	<context id="manifest_plugin_extensions">
-		<description>The Extensions page shows all the extensions used by your plug-in.</description>
-  <topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extensions" href="guide/tools/editors/manifest_editor/extensions.htm" />
-	</context>
-	<context id="manifest_plugin_ext_points">
-		<description>The Extension points page shows all the extension points declared by the plug-in.</description>
-  <topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extension Points" href="guide/tools/editors/manifest_editor/extension_points.htm" />
-	</context>
-		
-	<context id="manifest_fragment_overview">
-		<description>The Overview page shows you the fragment at a glance.</description>
-		<topic label="Plug-in Overview" href="guide/tools/editors/manifest_editor/overview.htm"/>
-	</context>
-	<context id="manifest_fragment_dependencies">
-		<description>The Dependencies page shows the dependencies that your fragment has on other plug-ins.</description>
-		<topic label="Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-	</context>
-	<context id="manifest_fragment_runtime">
-		<description>The Runtime page shows information about the fragment's runtime libraries.</description>
-		<topic label="Runtime" href="guide/tools/editors/manifest_editor/runtime.htm" />
-	</context>
-	<context id="manifest_fragment_extensions">
-		<description>The Extensions page shows all the extensions used by your fragment.</description>
-		<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extensions" href="guide/tools/editors/manifest_editor/extensions.htm" />
-	</context>
-	<context id="manifest_fragment_ext_points">
-		<description>The Extension points page shows all the extension points declared by the fragment.</description>
-		<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extension Points" href="guide/tools/editors/manifest_editor/extension_points.htm" />
-	</context>
-	
-	<context id="build_page">
-		<description>This editor is used to edit the build configuration for a plug-in, fragment or a feature.</description>
-		<topic label="Build" href="guide/tools/editors/manifest_editor/build.htm"/>
-	</context>
-	<context id="build_add_library_dialog">
-		<description>This dialog allows you to add a new library to build. You can either select a library already declared in your plug-in classpath, or declare a new library.</description>
-		<topic label="Build" href="guide/tools/editors/manifest_editor/build.htm"/>
-	</context>
-	<context id="folder_add_selection">
-		<description>This dialog allows you to add a new source folder for the selected library. The content of this folder will be compiled into the library.</description>
-		<topic label="Build" href="guide/tools/editors/manifest_editor/build.htm"/>
-	</context>
-	
-	<!-- Extension Point Schema Editor -->
-	
-	<context id="schema_editor_main">
-		<description>This editor creates a schema for an extension point, to which all extensions extending this point must conform.</description>
-		<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
-		<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
-		<topic label="Extension Point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
-		<topic label="Extension Point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
-	</context>
-	<context id="schema_editor_doc">
-		<description>Documentation for the use of this extension point is entered on this page.</description>
-		<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extension point schema" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
-		<topic label="Extension point schema editor" href="guide/tools/editors/schema_editor/editor.htm"/>
-		<topic label="Extension Point schema definition page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
-		<topic label="Extension Point schema overview page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
-	</context>
-	
-	<!-- Feature Editor -->
-	
-	<context id="manifest_feature_overview">
-		<description>This page shows general information about the feature.</description>
-		<topic label="Feature Overview" href="guide/tools/editors/feature_editor/overview.htm"/>
-	</context>
-	<context id="manifest_feature_info">
-		<description>This page is used to edit the required description, license and copyright information.</description>
-		<topic label="Feature Information" href="guide/tools/editors/feature_editor/information.htm"/>
-	</context>
-	<context id="manifest_feature_content">
-		<description>This page shows the list of plug-ins and fragments that are included in the feature.</description>
-		<topic label="Included Plug-ins" href="guide/tools/editors/feature_editor/plugins.htm"/>
-	</context>
-	<context id="manifest_feature_advanced">
-		<description>This page lists all features included in this feature</description>
-		<topic label="Included Features" href="guide/tools/editors/feature_editor/included_features.htm"/>
-	</context>
-	<context id="manifest_feature_dependencies">
-		<description>This page lists all plug-ins and features that need to be installed before installing this feature. </description>
-		<topic label="Feature Dependencies" href="guide/tools/editors/feature_editor/dependencies.htm"/>
-	</context>
-	<context id="manifest_feature_installation">
-		<description>This page details installation options</description>
-		<topic label="Feature Installation" href="guide/tools/editors/feature_editor/installation.htm"/>
-	</context>	
-	<context id="feature_synchronize_versions">
-		<description>The versions of the plug-ins and fragments should be synchronized with that of the packaged feature.</description>
-		<topic label="Feature Overview" href="guide/tools/editors/feature_editor/overview.htm"/>
-	</context>
-	
-	<!-- Site Editor -->
-
-	<context id="manifest_site_overview" >
-		<description>This page shows the general information about the update site.</description>
-		<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
-	</context>
-	<context id="manifest_site_build">
-		<description>This page allows you to configure how this site will be built from features and plug-ins in the workspace.</description>
-		<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
-	</context>
-	<context id="manifest_site_features">
-		<description>This page lists all the features visible to the user when connecting to this site.</description>
-		<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
-	</context>
-	<context id="manifest_site_archives">
-		<description>This page lists all the archive mappings in this site.</description>
-		<topic label="Setting up an update site project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
-		<topic label="Building plug-ins and features using update site editor" href="guide/tools/editors/site_editor/site_editor.htm"/>
-	</context>
-		
-	<!-- Product Editor -->
-
-	<context id="overview_page">
-		<description>This page allows you to specify general information about the product, as well as test and export it.</description>
-  <topic href="concepts/product.htm" label="Product"/>
-		<topic label="Product Overview Page" href="guide/tools/editors/product_editor/overview.htm"/>
-	</context>
-	<context id="configuration_page">
-		<description>Select plug-ins or features belonging to the product.  Optionally specify custom config.ini file, or program arguments.</description>
-		<topic label="Product Configuration Page" href="guide/tools/editors/product_editor/configuration.htm"/>
-	</context>	
-	<context id="launching_page">
-		<description>Information on this page controls the native launcher properties and arguments for the product.</description>
-		<topic label="Product Launching Page" href="guide/tools/editors/product_editor/launching.htm"/>
-	</context>
-	<context id="branding_page">
-		<description>Information on this page controls branding of the product.</description>
-		<topic label="Product Branding Page" href="guide/tools/editors/product_editor/branding.htm"/>
-	</context>
-	<context id="splash_page">
-		<description>This page allows you to create and customize a splash screen for the product.</description>
-		<topic label="Product Splash Page" href="guide/tools/editors/product_editor/splash.htm"/>
-	</context>
-
-	<!-- Simple Cheat Sheet Editor -->
-
-	<context id="simple_cs_editor">
-		<description>This editor allows you to compose a simple cheat sheet, which presents a set of steps to help the user complete a certain task.</description>
-		<topic label="Simple Cheat Sheet Editor" href="guide/tools/editors/simple_cs_editor/editor.htm"/>
-	</context>
-
-	<!-- Composite Cheat Sheet Editor -->
-
-	<context id="composite_cs_editor">
-		<description>This editor allows you to compose a composite cheat sheet, which presents a set of tasks (represented by simple cheat sheets) to help the user achieve an overarching goal.</description>
-		<topic label="Composite Cheat Sheet Editor" href="guide/tools/editors/composite_cs_editor/editor.htm"/>
-	</context>
-
-	<!-- Register Cheat Sheet Wizard -->
-
-	<context id="register_cs">
-		<description>This wizard allows you to register a simple or composite cheat sheet with the Eclipse workbench to make it accessible through the Help menu.</description>
-		<topic label="Register Cheat Sheet Wizard" href="guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm"/>
-	</context>
-	
-	<!-- Category Editor -->
-	
-	<context id="category_editor">
-		<description>This editor is used to modify category definition files that are used to generate categories when exporting.</description>
-		<topic label="Category Editor" href="guide/tools/editors/category_editor/definition_page.htm"/>
-		<topic label="New Category Definition" href="guide/tools/file_wizards/new_category.htm"/>
-		<topic label="Feature Export" href="guide/tools/export_wizards/export_features.htm"/>
-	</context>
-	<context id="category_file_page">
-		<description>This wizard allows you to create a new category file used to generate categories when exporting.</description>
-		<topic label="New Category Definition" href="guide/tools/file_wizards/new_category.htm"/>
-		<topic label="Category Editor" href="guide/tools/editors/category_editor/definition_page.htm"/>
-		<topic label="Feature Export" href="guide/tools/export_wizards/export_features.htm"/>
-	</context>
-
-	<!-- Table of Contents Editor -->
-
-	<context id="toc_editor">
-		<description>This editor creates a Help table of contents, which allows you to organize how documentation is displayed to users of an Eclipse product.</description>
-		<topic label="Table of Contents Editor" href="guide/tools/editors/toc_editor/editor.htm"/>
-	</context>
-
-	<context id="register_toc">
-		<description>This wizard allows you to register a Help table of contents with the project's plugin.xml file.</description>
-  <topic href="guide/tools/editors/toc_editor/editor.htm" label="Table of Contents Editor"/>
-	</context>
- <context id="target_editor" title="Target Definition Editor">
-    <description>The Target Definition Editor is used to edit target definition files in the workspace, which should end with the extension &quot;.target&quot;. Target definition files can be created using the New Target Definition Wizard or by moving them to the workspace on the Target Platform Preference Page.</description>
-    <topic href="guide/tools/editors/target_editor/target_editor.htm" label="Target Definition Editor"/>
-    <topic href="guide/tools/editors/target_editor/definition_page.htm" label="Target Definition Editor Definition Page"/>
-    <topic href="guide/tools/editors/target_editor/content_page.htm" label="Target Definition Editor Content Page"/>
-    <topic href="guide/tools/editors/target_editor/environment_page.htm" label="Target Definition Editor Environment Page"/>
-    <topic href="concepts/target.htm" label="Target Platform"/>
- </context>
-<!-- Children of the PDEFormPage -->
-
-    <!-- PLACE HOLDER -->
-	<context id="target_editor_environment_page" title="Target Definition Editor Environment Page">
-		<description>The Enviroment Page in the Target Definition Editor is used to edit many settings in the definition affecting how the target will be compiled and run.</description>
-	</context>
-    <!-- PLACE HOLDER -->
-	<context id="target_editor_definition_page" title="Target Definition Editor Definition Page">
-		<description>The Definition Page in the Target Definition Editor is used to edit the most important settings in a target definition file. The Target Name is used to display your targets on the Target Platform Preference Page. The Locations section is used to add locations that contain plug-ins and works the same as the Location Tab on the Edit Target Wizard.</description>
-	</context>
- <context id="target_editor_content_page" title="Target Definition Editor Content Page">
-    <description>The Content Page in the Target Definition Editor is used to view and edit the set of plug-ins to be included in the target definition when set as the active target platform. The definition must contain one or more locations containing plug-ins and the definition must be resolved to edit the content. Only the plug-ins that are checked on this page will be included in the target. There are multiple options available to filter and sort the list to quickly check what you require.</description>
- </context>
-
-<!-- END:  Editors -->
-
-<!-- end Children of the PDEFormPage -->
-
-
-<!-- START:  Preference pages -->
-
-   <!-- Plug-in Development -->
-
-   <!-- one to one mapping -->
-   <context id="main_preference_page" >
-      <description>This page allows you to set Plug-in Development Environment general settings.</description>
-      <topic label="Preferences" href="guide/tools/preference_pages/preferences.htm"/>
-
-      <topic label="General Plug-in Development Preferences" href="guide/tools/preference_pages/plug_in_development.htm"/>
-   </context>
-
-   <!-- Compilers -->
-
-   <!-- one to one mapping -->
-   <context id="compilers_preference_page" >
-      <description>This page allows you to specify the behavior of the various manifest compilers.</description>
-	  <topic label="Compilers Preferences" href="guide/tools/preference_pages/compilers.htm"/>
-
-      <topic label="Plug-in Compiler Preferences" href="guide/tools/preference_pages/plugin_compiler.htm"/>
-      <topic label="Extension Point Schema Compiler Preferences" href="guide/tools/preference_pages/schema_compiler.htm"/>
-      <topic label="Feature and Update Site Compiler Preferences" href="guide/tools/preference_pages/feature_compiler.htm"/>	  
-   </context>
-
-   <!-- Editors -->
-
-   <!-- one to one mapping -->
-   <context id="editor_preference_page" >
-      <description>This page allows you to configure behavior and presentation of PDE multi-page editors.</description>
-      <topic label="Editors Preferences" href="guide/tools/preference_pages/editors.htm"/>	 
-   </context>
-
-   <!-- OSGi Frameworks -->
-
-   <!-- one to one mapping -->
-   <context id="osgi_preference_page" >
-      <description>This page allows you to manage the OSGi Framework settings.</description>
-      <topic label="OSGi Frameworks Preferences" href="guide/tools/preference_pages/osgi_frameworks.htm"/>	 
-   </context>
-	
-
-   <!-- Target Platform -->
-
-   <!-- one to one mapping -->
-   <context id="target_platform_preference_page" >
-      <description>The Target Platform preference page allows you to manage a set of target definitions and select one as the active target platform. A target definition consists of a set of plug-ins and environment settings. The active target platform is used to build and launch your workspace plug-ins.</description>
-      <topic href="guide/tools/preference_pages/target_platform.htm" label="Target Platform Preferences"/>
-      <topic href="concepts/target.htm" label="Target Platform"/>
-      <topic href="guide/tools/target_shared/new_target_wizard.htm" label="New Target Wizard"/>
-      <topic href="guide/tools/target_shared/edit_target_wizard.htm" label="Edit Target Wizard"/>
-      <topic href="guide/tools/target_shared/move_target_wizard.htm" label="Move Target Wizard"/>
-      <topic href="guide/tools/editors/target_editor/target_editor.htm" label="Target Editor"/>
-      <topic href="guide/tools/preference_pages/preferences.htm" label="PDE Preferences"/>
-   </context>
-    
-<!-- END:  Preference pages -->
-
-
-<!-- Property pages -->	
-	<context id="plugin_development_property_page">
-      <description>Parent property page for the other pde property pages.  Allows you to modify how the manifest editor is displayed for your project.</description>
-   </context>
-
-    <context id="selfhosting_property_page">
-      <description>This page allows you to exclude certain class folders from the project's classpath.</description>
-   </context>
-
-   <context id="compilers_property_page">
-      <description>This page allows you to specify the behavior of the various manifest compilers.  The settings are identical to the Compilers Preference Page, but will only apply to a single project.</description>
-      <topic label="Plug-in Compiler Preferences" href="guide/tools/preference_pages/plugin_compiler.htm"/>
-   </context>
-   
-<!-- START:  Views -->	
-
-	<context  id="plugins_view">
-		<description>The Plug-in View show the plug-ins and fragments that will be passed to the runtime workbench when running or debugging. If simple self-hosting is used, the view allows you to browse external plug-ins that are not part of the workspace.</description>
-	    <topic label="Plug-ins" href="guide/tools/views/plugins.htm"/>
-	</context>
-	<context id="dependencies_view">
-	 	<description>The Dependencies view shows all the plug-ins required to run the selected plug-in.</description>
-		<topic label="Plug-in Dependencies" href="guide/tools/views/plugin_dependencies.htm"/>
-	</context>
-	<context id="registry_view">
-		<description>The Plug-in Registry view shows a read-only view of the plug-in registry of the running platform.</description>
-		<topic label="Plug-in Registry" href="guide/tools/views/plugin_registry.htm"/>
-	</context>
-	<context id="log_view">
-		<description>The log view captures warnings and internal errors thrown by the internal platform or your code.</description>
-		<topic label="Error Log" href="guide/tools/views/error_log.htm"/>
-	</context>
-
-<!-- END:  Views -->	
-
-		
-<!-- Wizard pages -->
-
-	<!-- PLACE HOLDER -->
-	<context id="externalize_strings_page">
-		<description>This page allows you to extract translatable strings and store them in a properties file for multi-language support.</description>
-		<topic label="Externalizing Strings" href="guide/tools/pde_actions/externalize_strings.htm"/>
-	</context>
-
-	<!-- PLACE HOLDER -->
-	<context id="xhtml_conversion_page">
-		<description>This page allows you to convert existing help files into XHTML</description>
-	</context>
-
-<!-- START:  New Project Creation Wizard pages -->
-
-	<!-- New Plug-in Project -->
-
-	<context id="new_project_structure_page">
-		<description>This wizard helps you create a new plug-in project. If the plug-in is to contain resources only, create a simple project. Otherwise, create a Java project.</description>
-		<topic label="Plug-in Project Structure" 
-			   href="guide/tools/project_wizards/plugin_structure.htm"/>
-	</context>
-	<context id="new_project_required_data">
-		<description>Data entered on this page is used to customize the generated manifest file and top level plug-in Java class.</description>
-		<topic label="Plug-in Content"
-			   href="guide/tools/project_wizards/plugin_content.htm"/>
-	</context>
-	<context id="new_project_code_gen_page">
-		<description>For a quick start, use the code generation wizards to create a plug-in project containing a working extension.  You can customize a plug-in to contain any combination of the available extension templates by choosing the 'Custom Plug-in Wizard' option.</description>
-		<topic label="Templates"
-			   href="guide/tools/project_wizards/plugin_templates.htm"/>
-	</context>
-	
-	<!-- New Fragment Project -->
-	
-	<context id="new_fragment_structure_page">
-		<description>This wizard helps you create a new fragment project. If the fragment is to contain resources only, create a simple project. Otherwise, create a Java project.</description>
-		<topic label="Fragment Project Structure"
-			   href="guide/tools/project_wizards/fragment_structure.htm"/>
-	</context>
-	<context id="new_fragment_required_data">
-		<description>This page specifies the fragment's target plug-in and other data required to generate the fragment's manifest file.</description>
-		<topic label="Fragment Content"
-			   href="guide/tools/project_wizards/fragment_content.htm"/>
-	</context>	
-	
-	<!-- Plug-in From Existing JAR Archives Project -->
-	
-	<context id="new_library_plugin_jar_page">
-		<description>This wizard helps you create a new plug-in project from existing JAR archives. Use this page to specify archives to be included in the plug-in. The buttons allow adding JAR archives from the workspace or the file system.</description> 
-		<topic label="Plug-in From Existing JAR Archives"
-			   href="guide/tools/project_wizards/plugin_from_archives.htm"/>
-	</context>
-	<context id="new_library_plugin_structure_page">
-		<description>This wizard helps you create a new plug-in project from existing JAR archives. Data entered on this page is used to customize the generated manifest file.</description>
-		<topic label="Plug-in From Existing JAR Archives"
-			   href="guide/tools/project_wizards/plugin_from_archives.htm"/>
-	</context>
-	<context id="new_feature_main">
-		<description>This wizard creates a new feature project that can be used to package plug-ins.</description>	
-		<topic label="Features" href="concepts/feature.htm"/>
-		<topic label="Setting up a feature project" href="guide/tools/project_wizards/new_feature_project.htm"/>
-  <topic href="guide/tools/editors/feature_editor/feature_editor.htm" label="Feature editor"/>
-	</context>
-	
-	<!-- New Feature Project -->
-
-	<context id="new_feature_data">
-		<description>This page specifies basic data about the feature.</description>	
-		<topic label="Feature Project" 
-			   href="guide/tools/project_wizards/new_feature_project.htm"/>
-	</context>
-	<context id="new_feature_referenced_plugins">
-		<description>The plug-ins and fragments selected on this page will be packaged in the feature.</description>
-		<topic label="Feature Project" 
-			   href="guide/tools/project_wizards/new_feature_project.htm"/>
-	</context>
-	
-	<!-- New Feature Patch -->
-
-	<context id="new_patch_main">
-		<description>This wizard creates a patch to an existing feature.</description>	
-		<topic label="Features" href="concepts/feature.htm"/>
-		<topic label="Setting up a feature project" href="guide/tools/project_wizards/new_feature_project.htm"/>
-	</context>	
-	<context id="new_patch_data">
-		<description>This page specifies basic data about the patch and the feature it targets.</description>	
-		<topic label="Feature Patch" 
-			   href="guide/tools/project_wizards/new_feature_patch.htm"/>
-	</context>
-	<context id="new_patch_referenced_plugins">
-		<description>The plug-ins and fragments selected on this page will be packaged in the patch.</description>
-		<topic label="Features" href="concepts/feature.htm"/>
-		<topic label="Setting up a feature project" href="guide/tools/project_wizards/new_feature_project.htm"/>
-	</context>	
-	
-	<!-- New Update Site Project -->
-	
-	<context id="new_site_main">
-		<description>This wizard creates an update site project where you can publish features for the Update Manager to find.</description>
-		<topic label="Update Site Project" 
-			   href="guide/tools/project_wizards/new_update_site_project.htm"/>
-	</context>
-
-<!-- END:  New Project Creation Wizard pages -->
-
-<!-- START:  New File Creation Wizard pages -->
-	
-	<!-- New Extension Point Schema -->
-	
-	<context id="new_schema">
-		<description>All extensions that extend the specified extension point will be validated against this schema.</description>
-		<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
-		<topic label="Extension Point Schema" 
-			   href="guide/tools/file_wizards/new_schema.htm"/>
-	</context>
-
-	<!-- New Product Configuration -->
-	
-	<context id="product_file_page">
-		<description>This page allows you to create a new product configuration and initialize its content.</description>
-		<topic label="Product Configuration" 
-			   href="guide/tools/file_wizards/new_product_config.htm"/>
-	</context>
-
-	<!-- New Cheat Sheet -->
-	
-	<context id="cheat_sheet_page">
-		<description>This page allows you to create a new cheat sheet.</description>
-		<topic label="Cheat Sheet" 
-			   href="guide/tools/file_wizards/new_cheat_sheet.htm"/>
-	</context>
-
-	<!-- New Target Definition -->
-	
-	<context id="target_definition_page">
-		<description>This page allows you to create a new target definition. A target definition specifies all aspects of a target - including its location, constituent plug-ins and environment.</description>
-		<topic label="Target Definition" 
-			   href="guide/tools/file_wizards/new_target_definition.htm"/>
-	</context>
-
-	<!-- New Table of Contents -->
-	
-	<context id="toc_page">
-		<description>This page allows you to create a new table of contents.</description>
-		<topic label="Table of Contents" href="guide/tools/file_wizards/new_toc.htm"/>
-	</context>
-
-<!-- END:  New File Creation Wizard pages -->
-	
-	<context id="converted_projects">
-		<description>Select Java projects to which you want to add PDE capabilities.
-If the selected project does not contain a manifest file, PDE will generate a generic one.</description>
-		<topic label="Converting existing projects" href="guide/tools/pde_actions/convert_projects.htm"/>
-	</context>	
-
-	<context id="migrate_3_0">
-		<description>All pre-3.0 plug-ins must be migrated using this wizard to update their list of dependencies and add the 3.0 processing instruction.</description>
-	</context>	
-
-<!-- START:  New Import Wizard pages -->
-	
-	<!-- Plugins and Fragments -->
-	
-	<context id="plugin_import_first_page">
-		<description>This wizard allows you to import plug-ins into the workspace.  Source code, if found, will be attached to JARs. Importing plug-ins as binary projects with links is the fastest.  It will not import these plug-ins physically into the workspace. It will instead create links to those plug-ins on disk.  Note that deleting these binary linked projects will not delete the files that they map to on disk.</description>
-		<topic label="Plug-in Import" 
-			   href="guide/tools/import_wizards/import_plugins.htm"/>
-	</context>
-	<context id="plugin_import_second_page">
-		<description>This list shows the plug-ins and fragments found in the location specified on the previous page.</description>
-		<topic label="Plug-in Import" 
-			   href="guide/tools/import_wizards/import_plugins.htm"/>
-	</context>
-	<context id="plugin_import_express_page">
-		<description>For each one of the selected plug-ins, the wizard will import all its pre-requisites that do not already exist as shared projects in the workspace.</description>
-		<topic label="Plug-in Import" 
-			   href="guide/tools/import_wizards/import_plugins.htm"/>
-	</context>
-
-	<!-- Features -->
-	
-	<context id="feature_import_first_page">
-		<description>This page defines the location from which the features will be imported into the workspace. This wizard should only be used in conjunction with feature-based self-hosting.</description>	
-		<topic label="Feature Import" 
-			   href="guide/tools/import_wizards/import_wizards.htm"/>
-	</context>
-	<context id="feature_import_second_page">
-		<description>This list shows the features found in the location specified on the previous page.</description>
-		<topic label="Feature Import" 
-			   href="guide/tools/import_wizards/import_wizards.htm"/>
-	</context>
-
-<!-- END:  New Import Wizard pages -->
-	
-	<context id="template_selection">
-		<description>Customize the plug-in by choosing one or more template extensions.</description>
-	</context>		
-	<context id="template_editor">
-		<description>This template creates a sample XML editor with basic editing capabilities, syntax highlighting, etc.</description>
-	</context>
-	<context id="template_hello_world">
-		<description>This template creates a sample action set that adds a menu to the menu bar and a button to the toolbar.</description>
-	</context>
-	<context id="template_help">
-		<description>This template creates a sample Help Table of Contents.</description>
-	</context>
-	<context id="template_intro">
-		<description>This template creates a sample intro for product.</description>
-	</context>
-	<context id="template_multipage_editor">
-		<description>This template creates a multi-page editor that works on files with the chosen extension.</description>
-	</context>
-	<context id="template_new_wizard">
-		<description>This template creates a wizard that can create a new file in the workspace</description>
-	</context>
-	<context id="template_popup_menu">
-		<description>This template adds a popup menu to the specified target object.
- The menu will appear in all views where an object of the specified type is selected.</description>
-	</context>
-	<context id="template_preference_page">
-		<description>This template creates a page that is contributed to the Preferences.</description>
-	</context>
-	<context id="template_property_page">
-		<description>This template adds a property page to a resource that matches the specified filter, and will appear in the Properties dialog for that resource.</description>
- 	</context>
- 	<context id="template_view">
- 		<description>This template creates a workbench view and is contributed to the Workbench by creating a category.</description>
- 	</context>
- 	<context id="template_universal_welcome">
- 		<description>This template creates a contribution to the Universal Welcome in the section of your choice. For this to work, your product must use Universal Welcome.</description>
- 	</context>
- 	<context id="template_builder">
- 		<description>This template creates an incremental project builder and a project nature.  A popup action on the project configures or unconfigures the nature.</description>
- 	</context>
- 	<context id="manifest_add_dependencies">
- 		<description>This wizard allows you to add plug-ins as dependencies to your plug-in.
- Use the filter to accelerate your search for the plug-ins.</description>
-		<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-		<topic label="Creating a plug-in project" href="guide/tools/project_wizards/new_plugin_project.htm"/>
-	</context>
-	<context id="add_extensions_main">
-		<description>This wizard allows you to add an extension to one of the available extension points.
- You can also create a working template extension from the list of available templates.</description>
- 		<topic href="concepts/extension.htm" label="Extensions and Extension Points"/>
- 	</context>
- 	<context id="add_extensions_schema_based">
- 		<description>This wizard allows you to extend one of the available extension points.  To be able to extend an extension point, your plug-in has to import the plug-in where the point is declared.</description>
-		<topic label="Dependencies page" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-		<topic label="Extension point schema" href="guide/tools/editors/schema_editor/editor.htm"/>
- 	</context>
-  <context id="project_selection_dialog">
-     <description>This dialog is used to select a plugin project to configure specific settings for.</description>
-     <topic href="guide/tools/preference_pages/compilers.htm" label="Compilers Preferences"/>
-     <topic href="guide/tools/preference_pages/plugin_compiler.htm" label="Plug-in Compiler Preferences"/>
-  </context>
- 	<context id="java_attribute_wizard_page">
- 		<description>This wizard allows you to create a new Java class or select an existing one.</description>
- 	</context>
-	<context id="feature_portability_wizard">
-		<description>This wizard allows you to add constraints to ensure that your feature is not installed or shown in a context that does not match these constraints.</description>
-		<topic label="Feature manifest editor" href="guide/tools/editors/feature_editor/feature_editor.htm"/>
-	</context>		
-
-<!-- START:  Export Wizards -->
-	
-	<context id="plugin_export_wizard" >
-		<description>This wizard builds and exports the selected plug-ins and/or fragments into the specified location.</description>
-		<topic label="Plug-in Export" href="guide/tools/export_wizards/export_plugins.htm"/>
-  <topic href="guide/tools/export_wizards/export_features.htm" label="Feature Export"/>
-  <topic href="tasks/ui_export_install_into_host.htm" label="Export and Install into Running Host"/>
-	</context>
-	<context id="feature_export_wizard">
-		<description>This wizard builds and exports the selected features and the associated plug-ins into the specified location.</description>
-		<topic label="Feature Export" href="guide/tools/export_wizards/export_features.htm"/>
-  <topic href="guide/tools/export_wizards/export_plugins.htm" label="Plug-in Export"/>
-  <topic href="tasks/ui_export_install_into_host.htm" label="Export and Install into Running Host"/>
-	</context>
-	<context id="product_export_wizard">
-		<description>This page allows you to export a product to a destination outside the Eclipse workspace</description>
-  <topic href="concepts/product.htm" label="Product"/>
-		<topic label="Product Export" href="guide/tools/export_wizards/export_product.htm"/>
-	</context>
-
-<!-- END:  Export Wizards -->
-	
-	<context id="plugins_container_page">
-		<description>This page shows you the actual classpath entries that are managed by this dynamic classpath container. In case one of the library entries does not have source associated, you can add source by selecting 'Attach Source...' button.</description>
-	</context>		
- 	
- 	<!-- new help contents, need to be completed -->
- 	<context id="advanced_plugin_export_page">
-		<description>This page allows signing the JARs for added security.
-If present, the JNLP option allows generation of manifests for Java Web Start deployment.</description>
-	</context>
-	<context id="cross_platform_export_page">
-		<description>When exporting for multiple platforms, select the desired target platforms on this page.  A directory will be created for each selection.</description>
-	</context>
-	<context id="library_plugin_jars">
-		<description>Add JAR archives to include in the new plug-in.  JAR files can be imported from existing workspace projects, or external directories. </description>
-	</context>	
-	<context id="plugin_working_set">
-		<description>Create a new working set by selecting plug-ins or fragments that will belong to it.</description>
-	</context>
-	<context id="product_definitions_wizard_page">
-		<description>This wizard creates a new product extension.  A product must be assoicated with an application.</description>
-  <topic href="concepts/product.htm" label="Product"/>
-	</context>
-	<context id="project_names_page">
-		<description>Specify project name.</description>
-	</context>
-	<context id="required_plugins_container_page">
-		<description>The Plug-in Dependencies container is a read-only container managed by PDE.  This page shows the classpath entries that the container resolves to for this particular plug-in project.</description>
-		<topic label="Access Restrictions" href="guide/tools/editors/manifest_editor/access_rules.htm"/>
-	</context>
-	<context id="review_page">
-		<description>Review details of the selected sample.</description>
-	</context>
-	<context id="selection_page">
-		<description>Select the samples to create.</description>
-	</context>
- 	
- 	
-<!-- Wizards -->
-
-<!-- Editor Outline -->
-	<context id="outline_sort_action">
-		<description>This action sorts elements in the Outline View.</description>
-	</context>
-<!-- END Editor Outline -->
-	
-    <context id="ctx_help_editor" title="Context Help Editor">
-    	<description>This editor creates a context help XML file, which allows you to create and edit dynamic help entries.</description>
-    	<topic href="guide/tools/editors/ctx_help_editor/ctx_help_editor.htm" label="Context Help Editor"/>
-    </context>
-    
-<!-- Target related contexts -->    
-   <context id="target_platform_state" title="Target Platform State View">
-      <description>The Target Platform State view shows the current status of the resolver state in PDE.</description>
-      <topic href="guide/tools/views/target_platform_state.htm" label="Target Platform State View"/>
-   </context>
-   <context id="new_target_wizard" title="New Target Wizard">
-      <description>This wizard creates a new target definition that will be added to the Target Platform Preference Page. There are several options to initialize your target definition with data. The new target definition will be saved in the Eclipse preferences, to create a target definition in your workspace use the New Target Definition File Wizard.</description>
-      <topic href="guide/tools/target_shared/new_target_wizard.htm" label="New Target Wizard"/>
-   </context>
-   <context id="edit_target_wizard" title="Target Definition Wizard">
-      <description>This wizard is used to edit target definitions. It is opened when a target definition on the Target Platform Preference Page is edited or a new definition is created. This wizard provides the same functionality as the Target Editor.</description>
-      <topic href="guide/tools/target_shared/edit_target_wizard.htm" label="Edit Target Wizard"/>
-      <topic href="guide/tools/target_shared/edit_target_arguments_tab.htm" label="Argument Tab"/>
-      <topic href="guide/tools/target_shared/edit_target_content_tab.htm" label="Content Tab"/>
-      <topic href="guide/tools/target_shared/edit_target_environment_tab.htm" label="Environment Tab"/>
-      <topic href="guide/tools/target_shared/edit_target_implicit_tab.htm" label="Implicit Dependencies Tab"/>
-      <topic href="guide/tools/target_shared/edit_target_locations_tab.htm" label="Locations Tab"/>
-   </context>
-   <context id="edit_target_wizard_locations_tab" title="Target Definition Wizard Locations Tab">
-      <description>The Location Tab in the Edit Target Wizard is used to set the locations that provide the plug-ins included in the target definition. There are several types of locations, allowing for definitions to be constructed in different styles.</description>
-   </context>
-   <context id="edit_target_wizard_argument_tab" title="Target Definition Wizard Arguments Tab">
-      <description>The Arguments Tab in the Edit Target Wizard is used to set the default program and vm arguments for new PDE launch configurations.</description>
-   </context>
-   <context id="edit_target_wizard_content_tab" title="Target Definition Wizard Content Tab">
-      <description>The Content Tab in the Edit Target Wizard is used to set a subset of plug-ins to include in the target platform. The tab displays a list of all plug-ins available in the target definition&apos;s locations. Only the plug-ins checked on this tab will be included. There are multiple ways to organize and filter the list.</description>
-   </context>
-   <context id="edit_target_wizard_environment_tab" title="Target Definition Wizard Environment Tab">
-      <description>The Environment Tab in the Edit Target Wizard is used to set environment settings that affect how a target is compiled and run. The environment settings can also be edited on the Environment Page of the Target Editor.</description>
-   </context>
-   <context id="edit_target_wizard_implicit_tab" title="Target Definition Wizard Implicit Dependencies Tab">
-      <description>The Implicit Tab in the Edit Target Wizard is used to set the implicit dependencies of the target. Any plug-in marked as an implicit dependency will always be added as a required plug-in when PDE determines requirements. Implicit dependencies can also be edited on the Environment Page of the Target Editor.</description>
-   </context>
-   <context id="implicit_dependencies_selection_dialog" title="Implicit Dependencies Selection Dialog">
-      <description>The Implicit Dependencies Selection Dialog allows you to browse through the plug-ins in your target and add one or more of them as implicit dependencies.</description>
-      <topic href="guide/tools/target_shared/implicit_plugin_selection_dialog.htm" label="Implicit Dependencies Selection Dialog"/>
-   </context>
-   <context id="move_target_wizard" title="Move Target Wizard">
-      <description>This wizard moves a target definition stored in the Eclipse preferences to a file in the workspace. This wizard is accessed by pressing Move on the Target Platform Preference Page. You must choose a project or directory to create the file in and a filename. Target definition files must end in the file extension &quot;.target&quot;.</description>
-      <topic href="guide/tools/target_shared/move_target_wizard.htm" label="Move Target Definition"/>
-   </context>
-   <context id="import_arguments_dialog" title="Import Arguments">
-      <description>The Import Arguments dialog is used to copy the arguments used in installations in your target. Often, if you have an Eclipse installation in your target that requires certain vm arguments to launch, you will require the same arguments to launch.</description>
-      <topic href="guide/tools/target_shared/import_arguments_dialog.htm" label="Import Arguments"/>
-   </context>
-   <context id="add_location_wizard" title="Add Location Wizard">
-      <description>The Add Location Wizard is opened from the Location Tab or the Definition Page. It is used to add a new location to a target definition. On the first page you must select a type of location to add.</description>
-      <topic href="guide/tools/target_shared/location_add_wizard.htm" label="Add Location Wizard"/>
-   </context>
-   <context id="location_add_directory_wizard" title="Add Directory Location Wizard">
-      <description>The Directory Location Wizard is used to create and edit directory locations in target definitions.</description>
-      <topic href="guide/tools/target_shared/location_edit_directory_wizard.htm" label="Directory Location Wizard"/>
-   </context>
-   <context id="location_edit_directory_wizard" title="Edit Directory Location Wizard">
-      <description>The Directory Location Wizard is used to create and edit directory locations in target definitions.</description>
-      <topic href="guide/tools/target_shared/location_edit_directory_wizard.htm" label="Directory Location Wizard"/>
-   </context>
-   <context id="location_preview_wizard" title="Preview Contents">
-      <topic href="guide/tools/target_shared/location_preview.htm" label="Preview Location Contents"/>
-   </context>
-   <context id="location_add_feature_wizard" title="Add Feature Locations Wizard">
-      <description>The Add Feature Locations Wizard is opened from the Add Location Wizard. Select a folder containing features (it can also contain a folder called &quot;features&quot;). All features found in the directory will be adde to the list. Check the features you want to add to your target. When Finish is pressed locations will be added to your target for each selected feature. The plug-ins in the features will be added to your target.</description>
-      <topic href="guide/tools/target_shared/location_add_features_wizard.htm" label="Add Feature Locations Wizard"/>
-   </context>
-   <context id="location_edit_feature_wizard" title="Edit Feature Location Wizard">
-      <description>The Edit Feature Location Wizard allows you to view the details of a feature location in your target definition.</description>
-      <topic href="guide/tools/target_shared/location_edit_feature_wizard.htm" label="Edit Feature Location Wizard"/>
-   </context>
-   <context id="location_add_installation_wizard" title="Add Installation Location Wizard">
-      <description>The Installation Location Wizard is used to create and edit installation locations in target definitions.</description>
-      <topic href="guide/tools/target_shared/location_edit_installation_wizard.htm" label="Installation Location Wizard"/>		
-   </context>
-   <context id="location_edit_installation_wizard" title="Edit Installation Location Wizard">      
-      <description>The Installation Location Wizard is used to create and edit installation locations in target definitions.</description>
-      <topic href="guide/tools/target_shared/location_edit_installation_wizard.htm" label="Installation Location Wizard"/>
-   </context>
-   <context id="location_add_site_wizard" title="Add Software Site Location Wizard">
-      <description>The Software Site Location Wizard is used to create and edit software site locations in target definitions.</description>
-      <topic href="guide/tools/target_shared/location_edit_site_wizard.htm" label="Software Site Location Wizard"/>      
-   </context>
-   <context id="location_edit_site_wizard" title="Edit Software Site Location Wizard">
-      <description>The Software Site Location Wizard is used to create and edit software site locations in target definitions.</description>
-      <topic href="guide/tools/target_shared/location_edit_site_wizard.htm" label="Software Site Location Wizard"/>
-   </context>
-<!-- END Target related contexts -->
-</contexts>
-

diff --git a/bundles/org.eclipse.pde.doc.user/customBuildCallbacks.xml b/bundles/org.eclipse.pde.doc.user/customBuildCallbacks.xml
deleted file mode 100644
index 308dc6a..0000000
--- a/bundles/org.eclipse.pde.doc.user/customBuildCallbacks.xml
+++ /dev/null

@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<!-- ===================================================================== -->

-<!-- Custom targets called from a project's generated build.xml            -->

-<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.-->

-<!-- ===================================================================== -->

-<project name="Build specific targets and properties" default="noDefault">

-

-	<import file="${eclipse.pdebuild.templates}/plugins/customBuildCallbacks.xml" />

-	

-	<target name="noDefault">

-		<echo message="This file must be called with explicit targets" />

-	</target>

-	

-	<!-- ===================================================================== -->

-	<!-- Steps to do before the target gather.bin.parts                        -->

-	<!-- Available parameters :                                                -->

-	<!--  destination.temp.folder - the directory plugins will be collected to -->

-	<!--  feature.directory - the directory containing the resulting feature   -->

-	<!-- ===================================================================== -->

-	<target name="pre.gather.bin.parts">

-		<antcall target="build.index"/>	

-	</target>

-	

-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.platform.doc.user." if="eclipse.running">

-		<ant antfile="buildDoc.xml" />

-	</target>

-

-</project>


diff --git a/bundles/org.eclipse.pde.doc.user/guide/book.css b/bundles/org.eclipse.pde.doc.user/guide/book.css
deleted file mode 100644
index eb8753c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/book.css
+++ /dev/null

@@ -1 +0,0 @@
-@import "../../PRODUCT_PLUGIN/book.css";
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/compiler.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/compiler.png
deleted file mode 100644
index 1cd34fa..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/compiler.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/content_assist.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/content_assist.png
deleted file mode 100644
index fc5082b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/content_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/convert.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/convert.PNG
deleted file mode 100644
index 10e472e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/convert.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/discouraged.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/discouraged.png
deleted file mode 100644
index 82a1dad..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/discouraged.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/forbidden.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/forbidden.png
deleted file mode 100644
index 7e01539..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/forbidden.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/friend.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/friend.png
deleted file mode 100644
index 53d94d4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/friend.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/hidden.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/hidden.png
deleted file mode 100644
index d42e3aa..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/hidden.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/properties.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/properties.png
deleted file mode 100644
index 00b4830..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/visible.png b/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/visible.png
deleted file mode 100644
index c2fb399..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/access_restrictions/visible.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/category_editor/manage_categories.png b/bundles/org.eclipse.pde.doc.user/guide/images/category_editor/manage_categories.png
deleted file mode 100644
index 37b1b5f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/category_editor/manage_categories.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/dialog_cheat-sheet-selection.png b/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/dialog_cheat-sheet-selection.png
deleted file mode 100644
index 6975720..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/dialog_cheat-sheet-selection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_content.png b/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_content.png
deleted file mode 100644
index 6852807..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_content.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_enclosing-text.png b/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_enclosing-text.png
deleted file mode 100644
index ea9f754..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_enclosing-text.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_group.png b/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_group.png
deleted file mode 100644
index 55541b3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_group.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_task.png b/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_task.png
deleted file mode 100644
index 05bf7e4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_task.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_title.png b/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_title.png
deleted file mode 100644
index ab81eb2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/composite_cs_editor/section_title.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_command.png b/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_command.png
deleted file mode 100644
index e39347f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_command.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_filled.png b/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_filled.png
deleted file mode 100644
index 01f21c6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_filled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_second_topic.png b/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_second_topic.png
deleted file mode 100644
index 4c79a80..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_second_topic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_topic_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_topic_details.png
deleted file mode 100644
index 55960c2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/ctx_help_editor/help_context_topic_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/cross_platform.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/cross_platform.PNG
deleted file mode 100644
index c25f8d5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/cross_platform.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/destination.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/destination.png
deleted file mode 100644
index f6dc8c5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/destination.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/export_wizard_select.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/export_wizard_select.png
deleted file mode 100644
index 72ddaf1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/export_wizard_select.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/feature_available.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/feature_available.png
deleted file mode 100644
index 0ef272a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/feature_available.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/jar_signing.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/jar_signing.png
deleted file mode 100644
index 24c1193..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/jar_signing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_features.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_features.png
deleted file mode 100644
index cb23c09..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_features.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_plugins.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_plugins.png
deleted file mode 100644
index 8c5099f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/options_plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/plugin_available.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/plugin_available.png
deleted file mode 100644
index ca18ed3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/plugin_available.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/product.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/product.png
deleted file mode 100644
index da56c2e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/product.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/webstart_features.png b/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/webstart_features.png
deleted file mode 100644
index d876d08..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/export_wizards/webstart_features.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_properties.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_properties.png
deleted file mode 100644
index 421593b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_required.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_required.png
deleted file mode 100644
index 1d0c025..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/dependencies_required.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_details.png
deleted file mode 100644
index f8b763a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_included.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_included.png
deleted file mode 100644
index 55dc4ef..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/features_included.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_copyright.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_copyright.png
deleted file mode 100644
index 54b6b1e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_copyright.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_description.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_description.png
deleted file mode 100644
index f7128df..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_description.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_license.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_license.png
deleted file mode 100644
index 8bd8460..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_license.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_sites.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_sites.png
deleted file mode 100644
index 03addd6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/information_sites.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_environments.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_environments.png
deleted file mode 100644
index 86211e2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_environments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_general.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_general.png
deleted file mode 100644
index 71dd216..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/overview_general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins.png
deleted file mode 100644
index f3a3997..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins_details.png
deleted file mode 100644
index a2f1aa1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/feature_editor/plugins_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/feature_import.png b/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/feature_import.png
deleted file mode 100644
index e70c6e1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/feature_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_categories.png b/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_categories.png
deleted file mode 100644
index 22136a7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_categories.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_from_all.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_from_all.PNG
deleted file mode 100644
index cd78949..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/import_from_all.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import.png b/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import.png
deleted file mode 100644
index ed3494e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import_for_existing.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import_for_existing.PNG
deleted file mode 100644
index 2810b52..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/import_wizards/plugin_import_for_existing.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_arguments.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_arguments.png
deleted file mode 100644
index 8356ce3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_arguments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_common.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_common.png
deleted file mode 100644
index e2d6d71..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_common.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_configuration.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_configuration.png
deleted file mode 100644
index 742b564..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_configuration.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_environment.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_environment.png
deleted file mode 100644
index 70330f6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_environment.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_main.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_main.png
deleted file mode 100644
index 72fa9f9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_main.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_plugins.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_plugins.png
deleted file mode 100644
index a284295..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_tracing.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_tracing.png
deleted file mode 100644
index bd7e42c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_eclipse_tracing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_arguments.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_arguments.png
deleted file mode 100644
index 9098c5c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_arguments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_plugins.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_plugins.png
deleted file mode 100644
index abf65bf..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_settings.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_settings.png
deleted file mode 100644
index 44adb89..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_equinox_settings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_configuration.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_configuration.PNG
deleted file mode 100644
index fdf947f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_configuration.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_headless.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_headless.PNG
deleted file mode 100644
index 5acfb3b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_headless.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_main.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_main.png
deleted file mode 100644
index 20f4871..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_main.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_plugins.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_plugins.png
deleted file mode 100644
index c6d58b8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_test.png b/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_test.png
deleted file mode 100644
index 3683a71..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/launchers/launcher_junit_test.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer1.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer1.PNG
deleted file mode 100644
index 0a1f9df..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer1.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer2.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer2.PNG
deleted file mode 100644
index eef8f87..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/bundlizer2.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/category_definition.png b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/category_definition.png
deleted file mode 100644
index a9d337d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/category_definition.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature1.png b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature1.png
deleted file mode 100644
index 6d4cc4d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature2.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature2.PNG
deleted file mode 100644
index a6f0f5a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature2.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_explorer.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_explorer.PNG
deleted file mode 100644
index 10d3aa5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_explorer.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_patch.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_patch.PNG
deleted file mode 100644
index 00d89a6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/feature_patch.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment1.png b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment1.png
deleted file mode 100644
index 3501f92..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment2.png b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment2.png
deleted file mode 100644
index d28c892..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment_explorer.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment_explorer.PNG
deleted file mode 100644
index 9eda30c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/fragment_explorer.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_toc_wizard.png b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_toc_wizard.png
deleted file mode 100644
index def1d53..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_toc_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_wizards_projects.png b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_wizards_projects.png
deleted file mode 100644
index baba390..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/new_wizards_projects.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/other_category.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/other_category.PNG
deleted file mode 100644
index 6572959..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/other_category.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_content.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_content.PNG
deleted file mode 100644
index 8341a30..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_content.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_customize.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_customize.PNG
deleted file mode 100644
index 9992502..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_customize.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_explorer.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_explorer.PNG
deleted file mode 100644
index 06d2b30..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_explorer.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_structure.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_structure.PNG
deleted file mode 100644
index dc2779f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_structure.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_templates.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_templates.PNG
deleted file mode 100644
index fe822b3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/plugin_templates.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/product.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/product.PNG
deleted file mode 100644
index c7fd2b2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/product.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/schema.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/schema.PNG
deleted file mode 100644
index d23bc48..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/schema.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site.PNG
deleted file mode 100644
index ec1993e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site_explorer.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site_explorer.PNG
deleted file mode 100644
index 043de53..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/site_explorer.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/target.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/target.PNG
deleted file mode 100644
index 131c1e5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/target.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/wizard_new_cheat-sheet.png b/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/wizard_new_cheat-sheet.png
deleted file mode 100644
index 79145de..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/new_wizards/wizard_new_cheat-sheet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/actions_select.png b/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/actions_select.png
deleted file mode 100644
index f2e10f2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/actions_select.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/convert_project.png b/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/convert_project.png
deleted file mode 100644
index 96905ea..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/convert_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_selection.png b/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_selection.png
deleted file mode 100644
index 0f95ec5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_selection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_substitution.png b/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_substitution.png
deleted file mode 100644
index 78aec20..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/externalize_strings_substitution.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/organize_manifest.png b/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/organize_manifest.png
deleted file mode 100644
index da24d6d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/organize_manifest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/update_classpath.png b/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/update_classpath.png
deleted file mode 100644
index 1b74dc1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/pde_actions/update_classpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/binary_source.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/binary_source.png
deleted file mode 100644
index 52bea4c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/binary_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/classpath.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/classpath.png
deleted file mode 100644
index e05b8c8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/classpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_analysis.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_analysis.png
deleted file mode 100644
index d3f2c6d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_analysis.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_automated.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_automated.png
deleted file mode 100644
index b03f758..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_automated.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_imported.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_imported.png
deleted file mode 100644
index 769d013..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_imported.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_required.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_required.png
deleted file mode 100644
index 2411599..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/dependencies_required.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extension_points.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extension_points.png
deleted file mode 100644
index d463995..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extension_points.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_body.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_body.png
deleted file mode 100644
index 02fb1d7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_body.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_details.png
deleted file mode 100644
index c2e6c31..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/extensions_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/filter_pages.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/filter_pages.PNG
deleted file mode 100644
index a8947af..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/filter_pages.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_execution.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_execution.png
deleted file mode 100644
index be6bb8c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_execution.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_general.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_general.png
deleted file mode 100644
index 953d5bc..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/overview_general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime.png
deleted file mode 100644
index d7a7c23..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_classpath.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_classpath.png
deleted file mode 100644
index fb97e87..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_classpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_exported.png b/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_exported.png
deleted file mode 100644
index 80806dd..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/plugin_editor/runtime_exported.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_features.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_features.png
deleted file mode 100644
index a971239..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_features.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_plugin.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_plugin.png
deleted file mode 100644
index 339767c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_plugin.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_schemas.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_schemas.png
deleted file mode 100644
index 5a66f1f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/compilers_schemas.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_manifest.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_manifest.png
deleted file mode 100644
index ad4cc94..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_manifest.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_xml.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_xml.png
deleted file mode 100644
index 549632f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/editors_xml.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/osgi_frameworks.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/osgi_frameworks.png
deleted file mode 100644
index 85bd1e2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/osgi_frameworks.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/outline.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/outline.png
deleted file mode 100644
index 56d03ba..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/outline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/plugin_development.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/plugin_development.png
deleted file mode 100644
index bd9310c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/plugin_development.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_locations_group.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_locations_group.png
deleted file mode 100644
index 0b8e552..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_locations_group.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_preferences.png b/bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_preferences.png
deleted file mode 100644
index e74f314..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/preferences/target_preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_about.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_about.png
deleted file mode 100644
index 13e8888..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_about.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_welcome.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_welcome.png
deleted file mode 100644
index aa26b5a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_welcome.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_window.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_window.png
deleted file mode 100644
index ec2b797..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/branding_window.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_features.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_features.PNG
deleted file mode 100644
index c524907..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_features.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_file.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_file.png
deleted file mode 100644
index 737e349..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_plugins.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_plugins.png
deleted file mode 100644
index b541d58..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/configuration_plugins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_arguments.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_arguments.png
deleted file mode 100644
index feca7ed..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_arguments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_jre.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_jre.png
deleted file mode 100644
index cd16c3b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_jre.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_program.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_program.png
deleted file mode 100644
index aa98a8c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/launcher_program.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_definition.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_definition.png
deleted file mode 100644
index ff605f4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_definition.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_exporting.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_exporting.png
deleted file mode 100644
index e25fb45..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_exporting.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_testing.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_testing.png
deleted file mode 100644
index 3973602..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/overview_testing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_custom.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_custom.png
deleted file mode 100644
index 1b7f3aa..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_custom.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_location.png b/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_location.png
deleted file mode 100644
index 8721ab8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/product_editor/splash_location.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/editor_header.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/editor_header.png
deleted file mode 100644
index 7d6595e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/editor_header.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_1.png
deleted file mode 100644
index 26ccbb9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_2.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_2.png
deleted file mode 100644
index f0a8b6d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_3.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_3.png
deleted file mode 100644
index d685d16..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_4.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_4.png
deleted file mode 100644
index 0594d8b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_attribute-details_4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_compositor-details.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_compositor-details.png
deleted file mode 100644
index e5b909c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_compositor-details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_description.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_description.png
deleted file mode 100644
index da7f731..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_description.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_documentation.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_documentation.png
deleted file mode 100644
index 6cf9c49..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_documentation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_1.png
deleted file mode 100644
index 1d3407e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_2.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_2.png
deleted file mode 100644
index aa72af2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-details_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-reference-details.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-reference-details.png
deleted file mode 100644
index 3a44824..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_element-reference-details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_1.png
deleted file mode 100644
index 6e68cce..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_2.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_2.png
deleted file mode 100644
index d838650..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_extension-point-elements_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_general-information.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_general-information.png
deleted file mode 100644
index bc86e1c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_general-information.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_schema-inclusions.png b/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_schema-inclusions.png
deleted file mode 100644
index 8c3bbbb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/schema_editor/section_schema-inclusions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_1.png
deleted file mode 100644
index c493ed5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_2.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_2.png
deleted file mode 100644
index 567a7c2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_3.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_3.png
deleted file mode 100644
index 98be4b2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_details_3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_master.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_master.png
deleted file mode 100644
index 46e4fcf..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/dialog_composer_master.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/page_cheat-sheet_header.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/page_cheat-sheet_header.png
deleted file mode 100644
index 02e019e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/page_cheat-sheet_header.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_command_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_command_details.png
deleted file mode 100644
index 589654a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_command_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_id.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_id.png
deleted file mode 100644
index 7368f0f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_id.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_link.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_link.png
deleted file mode 100644
index 3f81070..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_link.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_none.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_none.png
deleted file mode 100644
index abc0954..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_help_details_none.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_details.png
deleted file mode 100644
index decf4da..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_master.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_master.png
deleted file mode 100644
index f8f0472..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_master.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_view.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_view.png
deleted file mode 100644
index 274d98a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_introduction_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_1.png
deleted file mode 100644
index 5fa2ddf..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_2.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_2.png
deleted file mode 100644
index aeb9e49..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_details_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_1.png
deleted file mode 100644
index fa7568f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_2.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_2.png
deleted file mode 100644
index 10c4235..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_master_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_1.png
deleted file mode 100644
index ec0a575..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_2.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_2.png
deleted file mode 100644
index b7ed1dd..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_step_view_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_details.png
deleted file mode 100644
index c424268..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_master.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_master.png
deleted file mode 100644
index dad253a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_master.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_view.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_view.png
deleted file mode 100644
index e9713a5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_sub-step_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_details.png
deleted file mode 100644
index bacf022..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_master.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_master.png
deleted file mode 100644
index 11fcd39..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_master.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_view.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_view.png
deleted file mode 100644
index a860eeb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/section_title_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_category.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_category.png
deleted file mode 100644
index 18b3555..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_category.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_cheat-sheet.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_cheat-sheet.png
deleted file mode 100644
index f102623..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_cheat-sheet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_selection.png b/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_selection.png
deleted file mode 100644
index 40471d1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/simple_cs_editor/wizard_register_selection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_description.png b/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_description.png
deleted file mode 100644
index e3bb599..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_description.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_mirrors.png b/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_mirrors.png
deleted file mode 100644
index 701cd2c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/archives_mirrors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_environment.png b/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_environment.png
deleted file mode 100644
index a2024d5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_environment.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_managing.png b/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_managing.png
deleted file mode 100644
index 71b75cb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/site_editor/map_managing.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/content_page.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/content_page.png
deleted file mode 100644
index 5907062..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/content_page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/definition_page.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/definition_page.png
deleted file mode 100644
index fddc2b7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/definition_page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/environment_page.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/environment_page.png
deleted file mode 100644
index 3b764c1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_editor/environment_page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_arguments_tab.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_arguments_tab.png
deleted file mode 100644
index 6dda9b7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_arguments_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_content_tab.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_content_tab.png
deleted file mode 100644
index ef88ed9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_content_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_environment_tab.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_environment_tab.png
deleted file mode 100644
index 6cf4d84..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_environment_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_implicit_tab.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_implicit_tab.png
deleted file mode 100644
index 253362e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_implicit_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_locations_tab.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_locations_tab.png
deleted file mode 100644
index 0fcfdfe..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_locations_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_wizard.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_wizard.png
deleted file mode 100644
index 74372fe..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/edit_target_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/import_arguments_dialog.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/import_arguments_dialog.png
deleted file mode 100644
index 40f5aa6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/import_arguments_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_application.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_application.png
deleted file mode 100644
index dbbed15..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_application.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_directory.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_directory.png
deleted file mode 100644
index 6b73eb4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_directory.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_features.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_features.png
deleted file mode 100644
index b3388c4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_features.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_site.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_site.png
deleted file mode 100644
index d7c6f19..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_add_site.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_preview.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_preview.png
deleted file mode 100644
index 80800ce..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_preview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_selection.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_selection.png
deleted file mode 100644
index 35e9d71..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_selection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_site_include.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_site_include.png
deleted file mode 100644
index 1457b5f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/location_site_include.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/move_target_wizard.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/move_target_wizard.png
deleted file mode 100644
index 4ee1c1a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/move_target_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard.png
deleted file mode 100644
index 96b966b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard_template.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard_template.png
deleted file mode 100644
index d2cd88b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/new_target_wizard_template.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/select_implicit.png b/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/select_implicit.png
deleted file mode 100644
index f530ee7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/target_shared/select_implicit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/api_filter_properties.png b/bundles/org.eclipse.pde.doc.user/guide/images/tasks/api_filter_properties.png
deleted file mode 100644
index fc4a085..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/api_filter_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/baseline_dialog.png b/bundles/org.eclipse.pde.doc.user/guide/images/tasks/baseline_dialog.png
deleted file mode 100644
index 06a1793..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/baseline_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/feature-jar.png b/bundles/org.eclipse.pde.doc.user/guide/images/tasks/feature-jar.png
deleted file mode 100644
index 0c48f25..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/feature-jar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/plugin_creation_wizard.png b/bundles/org.eclipse.pde.doc.user/guide/images/tasks/plugin_creation_wizard.png
deleted file mode 100644
index 47372df..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/tasks/plugin_creation_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/anchor_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/anchor_details.png
deleted file mode 100644
index 0c3eed0..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/anchor_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/book_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/book_details.png
deleted file mode 100644
index 590f5bd..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/book_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/link_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/link_details.png
deleted file mode 100644
index 9ee0d16..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/link_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/toc_section.png b/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/toc_section.png
deleted file mode 100644
index f6861ae..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/toc_section.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/topic_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/topic_details.png
deleted file mode 100644
index 94bfae6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/toc_editor/topic_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/all_views.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/views/all_views.PNG
deleted file mode 100644
index 1fd3da1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/all_views.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/error_log.png b/bundles/org.eclipse.pde.doc.user/guide/images/views/error_log.png
deleted file mode 100644
index b1b8614..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/error_log.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/error_log_details.png b/bundles/org.eclipse.pde.doc.user/guide/images/views/error_log_details.png
deleted file mode 100644
index d0a2c61..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/error_log_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/perspective.PNG b/bundles/org.eclipse.pde.doc.user/guide/images/views/perspective.PNG
deleted file mode 100644
index 760e217..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/perspective.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_1.png b/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_1.png
deleted file mode 100644
index bb27f38..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_flat_callees.png b/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_flat_callees.png
deleted file mode 100644
index b28e52d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_flat_callees.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_hierarchical_callers.png b/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_hierarchical_callers.png
deleted file mode 100644
index b88f8a6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_hierarchical_callers.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_state_status.png b/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_state_status.png
deleted file mode 100644
index 219349e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_dependencies_state_status.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_registry.png b/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_registry.png
deleted file mode 100644
index 744f022..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/images/views/plugin_registry.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm b/bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm
deleted file mode 100644
index 32227e3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/intro/pde_overview.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<title>Using the Plug-in Development Environment</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Plug-in Development Environment Overview</h1>
-
-<p> The Plug-in Development Environment (PDE) provides tools to create,
-develop, test, debug, build and deploy Eclipse plug-ins, fragments,
-features, update sites and RCP products. </p>
-
-<p>PDE also provides comprehensive OSGi tooling, which makes it an ideal
-environment for component programming, not just Eclipse plug-in
-development.</p>
-
-<p>PDE is broken into three main components:</p>
-<ul>
-<li><a href="#ui">UI</a> - A rich set of models, tools and editors to develop plug-ins and OSGi bundles</li>
-<li><a href="#api">API Tooling</a> - Tooling to assist API documentation and maintenence</li>
-<li><a href="#build">Build</a> - Ant based tools and scripts to automate build processes</li>
-</ul>
-
-<p>Discover the latest features in the <a href="../../whatsNew/pde_whatsnew.htm">What's New</a> section.</p>    		
-
-<a name="ui"></a>
-<h2> PDE UI </h2>
-
-<p>PDE UI provides a editors, wizards, launchers, views and other tools to create a full featured environment to develop and deploy Eclipse plug-ins, fragments, 
-features, update sites, RCP products and OSGi bundles.</p>
-
-<p>Some of the PDE tools include:</p>
-<ul>
-<li><b>Form-Based Manifest Editors</b>: Multi-page editors that centrally manage all manifest files of a plug-in or feature.</li>
-<li><b>RCP Tools</b>:  Wizards and a form-based editor that allow you to define, brand, test and export products to multiple platforms.</li>
-<li><b>New Project Creation Wizards</b>:  Create a new plug-in, fragment, feature, feature patch and update sites.</li>
-<li><b>Import Wizards</b>:  Import plug-ins and features from the file system.</li>
-<li><b>Export Wizards</b>:  Wizards that build, package and export plug-ins, fragments and products with a single click.</li>
-<li><b>Launchers</b>:  Test and debug Eclipse applications and OSGi bundles.</li>
-<li><b>Views</b>:  PDE provides views that help plug-in developers inspect different aspects of their development environment.</li>
-<li><b>Miscellaneous Tools</b>:  Wizards to externalize and clean up manifest files.</li>
-<li><b>Conversion Tools</b>:  Wizard to convert a plain Java project or plain JARs into a plug-in project.</li>
-<li><b>Integration with JDT</b>:  Plug-in manifest files participate in Java search and refactoring.</li>
-</ul>
-
-<p>To get started, try out the following cheat sheets:</p>
-<ul>
-<li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.pde.helloworld)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open plug-in cheat sheet"><strong>Creating an Eclipse Plug-in</strong></a></li>
-<li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.pde.rcpapp)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open RCP cheat sheet"><strong>Creating a Rich Client Application</strong></a></li>
-</ul>
-
-<a name="api"></a>
-<h2>PDE API Tooling</h2>
-
-<p>PDE API Tooling assists in the documentation and maintenance of APIs provided by plug-ins and OSGi bundles.</p>
-
-<p>Some of the features include:</p>
-<ul>
-<li><b>Compatibility Analysis </b>: Identify binary compatibility issues relative to a previous version of a plug-in.</li>
-<li><b>API Restriction Tags </b>: Javadoc tags are provided to explicitly define restrictions associated with types and members.</li>
-<li><b>Version Number Validation </b>: Identify invalid plug-in version numbers relative to a previous version of a plug-in.</li>
-<li><b>Javadoc <code>@since</code> Tag Validation </b>: Identify missing and invalid <code>@since</code> tags on types and members. </li>
-<li><b>API Leak Analysis </b>: Identify API types and methods that leak non-API types. </li>
-<li><b>Quick Fixes </b>: Quick fixes are provided to adjust plug-in versions and @since tags appropriately.<br>
-</li>
-</ul>
-
-<p>To get started, see the tasks:</p>
-<ul>
-<li><a href="../../tasks/api_tooling_setup.htm">Setting up API Tooling</a></li>
-<li><a href="../../tasks/api_tooling_baseline.htm">Setting up a baseline</a></li>
-<li><a href="../../tasks/api_tooling_options.htm">Changing options</a></li>
-<li><a href="../../tasks/api_tooling_create_filters.htm">Creating filters</a></li>
-<li><a href="../../tasks/api_tooling_remove_filters.htm">Removing filters</a></li>
-</ul>
-
-<a name="build"></a>
-<h2>PDE Build</h2>
-
-<p>PDE Build facilitates the automation of plug-in build processes. PDE Build produces Ant scripts based on development-time information provided by, for example, the plugin.xml and build.properties files. The generated Ant scripts, can fetch the relevant projects from	a CVS repository, build jars, Javadoc, source zips, put everything together in a format ready to ship and send it out to a remote location (e.g., a local network or a downloads server).</p>
-		  	
-<p>To get started, see the following:</p>
-<ul>
-<li><a href="../../tasks/pde_product_build.htm">Automated building of RCP applications from product configurations</a></li>
-<li><a href="../../tasks/pde_feature_build.htm">Automated building of features</a></li>
-<li><a href="../../tasks/pde_plugins_build.htm">Automated building of plug-ins</a></li>
-<li><a href="../../tasks/pde_feature_generating_ant.htm">Generating Ant scripts from PDE</a></li>
-<li><a href="../../tasks/pde_feature_generating_antcommandline.htm">Generating Ant scripts from scripts</a></li>
-<li><a href="../../tasks/pde_p2_builds.htm">Building p2 repositories and products.</a></li>
-<li><a href="../../reference/pde_builder_config.htm">Builder Configuration Properties</a></li>
-<li><a href="../../reference/pde_feature_generating_build.htm">Feature and Plug-in build properties</a></li>
-</ul>
-
-<p></p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/schema.css b/bundles/org.eclipse.pde.doc.user/guide/schema.css
deleted file mode 100644
index 00f9d01..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/schema.css
+++ /dev/null

@@ -1,66 +0,0 @@
-H6.CaptionFigColumn#header {
-	font-size:16px; 
-	display:inline
-}
-
-P.Note#copyright {
-	font-size: smaller; 
-	font-style: normal;
-	color: #336699; 
-	display:inline;
-	margin-top: 3.000000pt;
-	margin-bottom: 11.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 0.000000pt;
-}
-
-P.Code#dtd {
-	color: #800000; 
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 10.000000pt;
-}
-
-P.Code#dtdAttlist {
-	color: #800000; 
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 20.000000pt;
-}
-
-P.Code#tag {
-	color: #000080; 
-	display:inline;
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 0.000000pt;
-}
-
-P.Code#cstring {
-	color: #008000; 
-	display:inline;
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 0.000000pt;	
-}
-
-.ConfigMarkup#elementDesc {
-	color: black;
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 10.000000pt;
-}
-
-.ConfigMarkup#attlistDesc {
-	color: black;
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 32.000000pt;
-}
-

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/category_editor/definition_page.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/category_editor/definition_page.htm
deleted file mode 100755
index e87abd1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/category_editor/definition_page.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Category Editor</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Category Editor</h1>
-
-<p>The <strong>Category Editor</strong> is a single page editor used to modify category definition files.  These files provide a set of categories and specify features that belong to each category.  When exporting, a category definition file can be provided so that the exported metadata adds the exported features to the correct category.</p>
-
-<h2>Managing the Categories</h2>
-<p>Using the site editor, you can create <b>Categories</b> and add features to it.  A feature
-can appear in more than one category.</p>
-<p><img src="../../../images/category_editor/manage_categories.png" alt="Managing the Site" ></p>
-<p>To publish categories you can specify the category file when exporting a feature.</p>
-
-<p><img src="../../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../file_wizards/new_category.htm">New Category Definition File</a><br>
-<a href="../../export_wizards/export_features.htm">Feature Export</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/editor.htm
deleted file mode 100644
index 648ebda..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/editor.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-		<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Composite Cheat Sheet Editor</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Composite Cheat Sheet Editor</h2>
-		
-		<h3>About Cheat Sheets</h3>
-		
-		<p>
-			In general, cheat sheets help guide users through a complex set of instructions. 
-		   	There are two types of cheat sheets: simple and composite. 
-			Composite cheat sheets are used to organize and 
-			present tasks represented by simple cheat sheets to achieve a larger goal.
-		</p>
-
-		<p>
-			You can view and run cheat sheets using the <strong>Cheat Sheet View</strong>.
-			To open a cheat sheet in this view, click <strong>Help &gt; Cheat Sheets...</strong>
-		</p>
-
-		<h3>About This Editor</h3>
-		
-		<p>
-			The <strong>Composite Cheat Sheet Editor</strong> allows you to compose composite
-			cheat sheets and preview them in the <strong>Cheat Sheet View</strong>.  
-			This editor also allows you to create simple cheat sheets on the fly.
-		</p>
-
-		<h3>Editor Pages</h3>
-		
-		<p>
-			This editor is comprised of the following pages:
-		</p>
-
-		<ul>
-			<li>
-				<a href="page_cheat-sheet.htm">Composite Cheat Sheet Page</a>
-			</li>
-		</ul>
-
-		<h3>Global Editor Actions</h3>
-		
-		<p>
-			This editor provides the following global actions:
-		</p>
-		
-		<ul>
-			<li>
-				<a href="../simple_cs_editor/wizard_register-cheat-sheet.htm">Register Cheat Sheet Wizard</a>
-			</li>
-		</ul>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>Cheat sheet example:
-				<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.pde.rcpapp)")'>
-    				<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open plug-in cheat sheet"> Creating an Eclipse Plug-in
-				</a>
-			</li>		
-			<li>
-				Cheat sheet documentation: 
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm">Cheat Sheets</a>
-			</li>
-			<li>
-				<a href="../simple_cs_editor/editor.htm">Simple Cheat Sheet Editor</a>
-			</li>
-			<li>
-				<a href="../../file_wizards/new_cheat_sheet.htm">New Cheat Sheet Wizard</a>
-			</li>
-			<li>
-				<a href="http://www.eclipse.org/pde/pde-ui/articles/cheat_sheet_dev_workflow/index.html">
-				Recommended Work Flow for Cheat Sheet Development</a>
-			</li>
-		</ul>
-		
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/page_cheat-sheet.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/page_cheat-sheet.htm
deleted file mode 100644
index 7b3429e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/composite_cs_editor/page_cheat-sheet.htm
+++ /dev/null

@@ -1,374 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Composite Cheat Sheet Page</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Composite Cheat Sheet Page</h2>
-
-		<h3>About This Page</h3>
-		
-		<p>
-			This form page allows you to edit the structure, order and properties of cheat sheet elements.
-		</p>
-		<p>
-			The structure and order of cheat sheet elements are edited in 
-			the <strong>Content</strong> section.  
-			This section occupies the entire left-hand portion of the editor area. 
-		</p>
-		<p>
-			The properties of cheat sheet elements are edited in the <strong>Definition</strong> sections.
-			These sections are activated in the right-hand portion of the editor area depending
-			on the type of cheat sheet element selected in the <strong>Content</strong> section. 
-		</p>
-		
-		<h3>Page Sections</h3>
-		
-		<p>
-			This page is comprised of the following sections:
-		</p>		
-		
-		<ul>
-			<li>
-				<a href="#content">Content Section</a>
-			</li>
-			<li>
-				<a href="#title">Title Section</a>
-			</li>
-			<li>
-				<a href="#group">Group Section</a>
-			</li>	
-			<li>
-				<a href="#task">Task Section</a>
-			</li>		
-			<li>
-				<a href="#enclosing">Enclosing Text Section</a>
-			</li>							
-		</ul>
-
-		<a name="content"></a>
-		<h3>Content Section</h3>
-
-		<p>
-			This section allows you to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Visualize and edit the structure and order of the cheat sheet's 
-				elements.
-			</li>
-			<li>
-				Activate the corresponding <strong>Definition</strong> section used to edit the 
-				properties of a selected cheat sheet element.
-			</li>
-			<li>
-				Preview and test the edited cheat sheet within the 
-				<strong>Cheat Sheet</strong> view.
-			</li>
-		</ul>
-
-		<p>
-			This section is directly accessible through the <strong>Cheat Sheet</strong> form page.
-		</p>
-
-		<h3>Content Section Fields</h3>
-
-		<p>
-			Use the cheat sheet element viewer field to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Visualize the structure and order of the cheat sheet's 
-				title, groups and tasks
-				as they appear in the <strong>Cheat Sheet</strong> view.
-			</li>
-			<li>
-				Edit the structure and order of the cheat sheet's groups and tasks.
-			</li>
-			<li>
-				Activate the corresponding <strong>Definition</strong> section used to edit the 
-				properties of a selected title, group or task.
-			</li>
-		</ul>
-
-		<p>
-			This viewer contains the following nodes:
-		</p>
-
-		<ul>
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/cheatsheet_composite_obj.gif" alt="Root Cheat Sheet Node">
-				- Select the <em>Root</em> node, to activate the title <strong>Definition</strong> section. 
-			</li>
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/cheatsheet_taskgroup_obj.gif" alt="Group Cheat Sheet Node">
-				- Select the <em>Group</em> node, to activate the group <strong>Definition</strong> section. 
-			</li>
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/cheatsheet_simple_obj.gif" alt="Task Cheat Sheet Node">
-				- Select the <em>Task</em> node, to activate the task <strong>Definition</strong> section. 
-			</li>						
-		</ul>
-
-		<p>
-			<img src="../../../images/composite_cs_editor/section_content.png" alt="Content Section">
-		</p>
-
-		<h3>Content Section Actions</h3>
-		
-		<p>
-			Click the <strong>Add Task</strong> button to add a new task to the 
-			cheat sheet.
-			This action is available when a group or task node is selected.  
-			If a task node is selected, the new task will be added 
-			as the last child node of the task's parent group.  
-			If a group node is selected, the new task will be added
-			as the last child node of that group.		
-		</p>
-
-		<p>
-			Click the <strong>Add Group</strong> button to add a new group to the 
-			cheat sheet.
-			This action is available when a group or task node is selected.  
-			If a task node is selected, the new group will be added 
-			as the last child node of the task's parent group.  
-			If a group node is selected, the new group will be added
-			as the last child node of that group.	
-			Note:  In order to maintain cheat sheet validity, a new
-			group requires at least one child node.	
-		</p>		
-
-		<p>
-			Click the <strong>Remove</strong> button to remove a group or task.
-			This action is available when any of following nodes are selected:  
-			task, group.	
-			Note:  In order to maintain cheat sheet validity, 
-			neither the root node nor its immediate child group can be removed. 		
-		</p>
-
-		<p>
-			Click the <strong>Up</strong> button to move a group or task 
-			up one position in order above their respective siblings.
-			This action is available when a group or task node is selected.
-		</p>
-
-		<p>
-			Click the <strong>Down</strong> button to move a group or task 
-			down one position in order below their respective siblings.
-			This action is available when a group or task node is selected.
-		</p>
-
-		<p>
-			Click the <strong>Preview</strong> button to preview and test the saved or unsaved
-			contents of the edited cheat sheet in the <strong>Cheat Sheet</strong> view.  
-			This convenient action allows you to observe how the edited cheat sheet 
-			actually appears and operates within its deployed environment without having to
-			register the cheat sheet and launch another Eclipse runtime instance.		
-		</p>
-
-		<a name="title"></a>
-		<h3>Title Section</h3>
-
-		<p>
-			This <strong>Definition</strong> section allows you to edit the title of the cheat sheet. 
-			It is activated by selecting the root node in the <strong>Content</strong> section.
-		</p>
-		
-		<p>
-			<img src="../../../images/composite_cs_editor/section_title.png" alt="Title Section">
-		</p>
-
-		<h3>Title Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Name</strong> field to specify the cheat sheet title.
-		</p>
-
-		<a name="group"></a>
-		<h3>Group Section</h3>
-
-
-		<p>
-			This <strong>Definition</strong> section allows you to edit the properties of a group. 
-			It is activated by selecting a group node in the <strong>Content</strong> section.
-		</p>
-
-		<p>
-			<img src="../../../images/composite_cs_editor/section_group.png" alt="Group Section">
-		</p>
-
-		<h3>Group Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Name</strong> field to specify the title of the group.
-		</p>
-
-		<p>
-			Select a value from the <strong>Type</strong> field to change 
-			how the group is completed within the <strong>Cheat Sheet</strong>
-			view.  The following selections are available:
-		</p>
-		
-		<ul>
-			<li>
-				Set: The group is complete when all of its children are completed.
-			</li>
-			<li>
-				Sequence: The group is complete when all of its children are completed in order.
-			</li>
-			<li>
-				Choice: The group is complete when any one of its children are completed.
-			</li>
-		</ul>
-
-		<p>
-			Check the <strong>This group is optional</strong> field to make the 
-			completion of the group and all of its child tasks optional 
-			in the <strong>Cheat Sheet</strong> view.  
-			A non-optional group includes a <strong>Go To 'Task'</strong> 
-			action in the <strong>Cheat Sheet</strong> view to go to the group's first
-			child task.  
-			An optional group includes a <strong>Skip this group of tasks</strong>
-			action in the <strong>Cheat Sheet</strong> view to skip the group and
-			all of its child tasks.		
-		</p>
-
-		<a name="task"></a>
-		<h3>Task Section</h3>
-
-		<p>
-			This <strong>Definition</strong> section allows you to edit the properties of a task
-			and create simple cheat sheets on the fly.
-			It is activated by selecting a task node in the <strong>Content</strong> section.
-		</p>
-
-		<p>
-			<img src="../../../images/composite_cs_editor/section_task.png" alt="Task Section">
-		</p>
-
-		<h3>Task Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Name</strong> field to specify the title of the task.
-		</p>
-
-		<p>
-			Edit the <strong>Path</strong> field to specify the relative path from the composite
-			cheat sheet file being edited to an existing simple cheat sheet file.
-			The use of an absolute path to an existing simple cheat sheet file is forbidden.
-			Also, the simple cheat sheet file must be contained within the same plug-in
-			project as the composite cheat sheet file being edited.
-			Forward slashes ('/') are used to separate file segments on all platforms.
-		</p>
-
-		<p>
-			Check the <strong>This task is optional</strong> field to make the 
-			completion of the task optional in the <strong>Cheat Sheet</strong> view.  
-			A non-optional task includes a <strong>Start working on this task</strong> 
-			action in the <strong>Cheat Sheet</strong> view to go to the 
-			simple cheat sheet referred to by the task.  
-			An optional task includes a <strong>Skip this task</strong>
-			action in the <strong>Cheat Sheet</strong> view to skip the task.		
-		</p>
-
-		<h3>Task Section Actions</h3>
-
-		<p>
-			If the relative path specified in the <strong>Path</strong> 
-			field refers to an existing simple cheat sheet file, clicking on the
-			<strong>Path</strong> hyperlink opens that cheat sheet in the
-			<strong>Simple Cheat Sheet Editor</strong>.
-			If the relative path specified in the <strong>Path</strong> 
-			field refers to a non-existing simple cheat sheet file, clicking 
-			on the <strong>Path</strong> hyperlink opens a streamlined 
-			version of the <strong>New Cheat Sheet Wizard</strong>.
-			This version of the wizard can only create simple cheat sheets.
-			In the wizard, the <strong>File name</strong> field is automatically populated
-			with the simple cheat sheet file name from the <strong>Path</strong> 
-			field (if specified).
-		</p>		
-
-		<p>
-			Click the <strong>Browse</strong> button to open the 
-			<strong>Cheat Sheet Selection</strong> dialog in order to select
-			an existing simple cheat sheet file.
-			The dialog presents a hierarchical view of all simple cheat 
-			sheet files contained within the plug-in 
-			project that contains the composite cheat sheet file being edited.
-			After a selection is made, the relative path
-			from the composite cheat sheet file to the 
-			selected simple cheat sheet file is automatically computed and
-			entered into the <strong>Path</strong> field.
-		</p>
-
-		<p>
-			<img src="../../../images/composite_cs_editor/dialog_cheat-sheet-selection.png" alt="Cheat Sheet Selection Dialog">
-		</p>
-
-		<a name="enclosing"></a>
-		<h3>Enclosing Text Section</h3>
-
-		<p>
-			This section allows you to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Specify an introduction for a group or task.
-			</li>
-			<li>
-				Specify a conclusion for a group or task.
-			</li>
-		</ul>
-
-		<p>
-			This section is accessible by selecting a group or task node 
-			in the <strong>Content</strong> section.
-		</p>
-
-		<p>
-			<img src="../../../images/composite_cs_editor/section_enclosing-text.png" alt="Enclosing Text Section">
-		</p>
-
-		<h3>Enclosing Text Section Fields</h3>
-
-		<p>
-			Edit the <strong>Introduction</strong> field to specify an introduction for a group or task.
-			The text may be formatted using valid <em>Form Text Mark-up</em>.
-			For instance, to bold text, enclose text with HTML-style bold tags: &lt;b&gt;&lt;/b&gt;.
-		</p>
-
-		<p>
-			Edit the <strong>Conclusion</strong> field to specify a conclusion for a group or task.
-			The text may be formatted using valid <em>Form Text Mark-up</em>.
-			For instance, to break text, use HTML-style break tags: &lt;br/&gt;.			
-		</p>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="editor.htm">Composite Cheat Sheet Editor</a>
-			</li>
-			<li>
-				<a href="../simple_cs_editor/editor.htm">Simple Cheat Sheet Editor</a>
-			</li>		
-			<li>
-				<a href="../../file_wizards/new_cheat_sheet.htm">New Cheat Sheet Wizard</a>
-			</li>				
-			<li>
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm">
-					Form Text Mark-up
-				</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/ctx_help_editor/ctx_help_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/ctx_help_editor/ctx_help_editor.htm
deleted file mode 100644
index 612b83c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/ctx_help_editor/ctx_help_editor.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Context Help Editor</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-
-<body>
-<h2>Context Help Editor</h2>
-
-<p>
-Context-sensitive help is a mechanism that enables linking a user interface part with a specific help topic.  When the user activates the associated user interface part, the help page is displayed in the dynamic help area.  The user interface and the help pages are associated with each other in two ways: a static XML file or a dynamic context provider.  To associate pages statically, a context help xml file must be created.  The context help editor assists in the creation of these pages.
-</p>
-<p>
-The <strong>Definition</strong> page of the editor provides a graphical view of the xml file, separated into two columns.  The one on the left is titled <strong>Context Help</strong> and displays the xml elements in a tree format along with actions to add, move and remove them.  The other column provides more detailed information about the element selected in the left column and enables editing of the details.
-</p>
-<p>
-The <strong>Source</strong> page of the editor provides a textual view of the xml file.  The xml can be edited directly and changes, if valid, will be reflected on the graphical <strong>Definition</strong> page.
-</p>
-<ul>
-	<li>
-		<a href="#add-new-help">Adding new help contexts</a>
-	</li>
-	<li>
-		<a href="#add-help-command">Adding help topics and commands</a>
-	</li>
-	<li>
-		<a href="#remove-up-down">Remove, Up, Down commands</a>
-	</li>
-	<li>
-		<a href="#register">Registering the context help file</a>
-	</li>							
-</ul>
-
-<a name="add-new-help"></a>
-<h3>Adding new help contexts</h3>
-
-<p>
-<img src="../../../images/ctx_help_editor/help_context_filled.png" alt="Help context editor with filled fields" border=0 height=278 width=705>
-</p>
-<p>
-To add a new context, click the <strong>Add Context</strong> button.  This will add a new context entry to the xml and it will be displayed in the tree on the <strong>Definition</strong> page.  The new context will be selected, opening a detail section in the right column of the editor.  In this detail section you can provide more detailed information about the context including:
-</p>
-<ul>
-  <li>Help Context ID: ID that is passed to the UI element to associate the help</li>
-  <li>Description: Text that will be displayed to the user in the dynamic help to explain the basic function of the selected UI element.</li>
-  <li>Custom Page Title: By default the dynamic help displays the name of the selected UI element as the help title, entering text here will override the default.</li>
-</ul>
-
-<a name="add-help-command"></a>
-<h3>Adding help topics and commands</h3>
-
-Adding a context to the file will provide dynamic help with a basic description to display to the user.  Typically you will want to provide additional links to related topics in the help system.  To do this you must add topics and commands to the xml file.
-
-<p>
-<img src="../../../images/ctx_help_editor/help_context_topic_details.png" alt="Help context editor with filled detail fields" border=0 height=273 width=702>
-</p>
-<p>
-By clicking on the <strong>Add Topic</strong> button, you will add a new topic entry to the xml under one of the help contexts.  A topic will appear to the user as a link.  Once a new topic is created, you can select it to open the <strong>Topic Details</strong> section on the right column of the <strong>Definition</strong> page.  In the detail section you can change the label that will be displayed to the user and the location of the file that will be linked.  In most cases, the linked file will be an html page in the help system.  You can use the <strong>Browse...</strong> button to search for a file to link.
-</p>
-
-<p>
-In addition to topics, you may also want to add a command.  A command has the same appearance to the user as a topic.  However, when the link is activated, a code command is executed instead of a file being opened.  Commands can be used to open preference pages and execute other actions.
-</p>
-<p>
-<img src="../../../images/ctx_help_editor/help_context_command.png" alt="Help context editor add command" border=0 height=277 width=710>
-</p>
-<p>
-Clicking the <strong>Add Command</strong> button to add a new command.  You can edit the details of commands in the same way that you edit topics.
-</p>
-
-<a name="remove-up-down"></a>
-<h3>Remove, up, down Commands</h3>
-<p>
-There are three additional buttons on the <strong>Definition</strong> page, which enable manipulating with the items order on the context list or with deleting the items. 
-</p>
-<p>
-<img src="../../../images/ctx_help_editor/help_context_second_topic.png" alt="Help context with manipulating buttons" border=0 height=265 width=708>
-</p>
-<p>
-These buttons are:
-</p>
-<ul>
-  <li>Remove: Removes an item from the xml file</li>
-  <li>Up: Moves the selected items upwards one place in the tree</li>
-  <li>Down: Moves the selected items downwards one place in the in tree</li>
-</ul>
-
-<a name="register"></a>
-<h3>Registering the context help file</h3>
-
-For Eclipse to recognize the context help xml file as being a source for the dynamic help system, it must be registered via the <strong>org.eclipse.help.contexts</strong> extension point.  The editor provides a way to register the context help file automatically.  In the top righthand corner of the editor, there is a link called "Register this context help file".  Clicking on this link will add the correct entry to the plugin.xml file.
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/dependencies.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/dependencies.htm
deleted file mode 100644
index 3075a9a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/dependencies.htm
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Feature Dependencies</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Dependencies </h1>
-<p>The <strong>Dependencies</strong> page  lists all <strong>Required Features and Plug-ins</strong> that must be present   in the product before the <em>Update Manager</em> installs this feature. If any of these   pre-requisites are missing, the feature will not be installed.</p>
-<p><img src="../../../images/feature_editor/dependencies_required.png" alt="Dependencies" ></p>
-<p> The requirement   can be based solely on plug-in IDs, or further constrained using expected   versions and match rules.</p>
-<p><img src="../../../images/feature_editor/dependencies_properties.png" alt="Properties" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/feature_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/feature_editor.htm
deleted file mode 100644
index 13cd38f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/feature_editor.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Feature Manifest Editor</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Manifest Editor </h1>
-<p>PDE provides a form-based multi-page feature manifest editor that manages and edits the <em>feature.xml</em> file. </p>
-<p>For details on the individual editor pages, refer to the following documents:</p>
-<ul>
-  <li><a href="overview.htm">Feature Overview</a></li>
-  <li><a href="information.htm">Feature Information</a></li>
-  <li><a href="plugins.htm">Included Plug-ins</a></li>
-  <li><a href="included_features.htm">Included Features</a></li>
-  <li><a href="dependencies.htm">Feature Dependencies</a></li>
-  <li><a href="installation.htm">Feature Installation</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/included_features.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/included_features.htm
deleted file mode 100644
index 9ca766a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/included_features.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Included Features</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Included Features </h1>
-<p>The <strong>Included Features</strong> section references all features nested inside your feature and their associated properties.</p>
-
-<h2>Feature List</h2>
-<p>The <strong>Included Features</strong> list enumerates all the features that are directly nested in your feature. </p>
-<p><img src="../../../images/feature_editor/features_included.png" alt="Included Features"></p>
-<p>When your feature is built, all of its included features are recursively built and packaged as well.</p>
-
-<h2>Included Feature Details</h2>
-<p><img src="../../../images/feature_editor/features_details.png" alt="Included Feature Details"></p>
-<p>An included feature may be marked as <strong>optional</strong> using the <strong>The feature is optional</strong> option. Users may not choose to install optional features.  However, if users do choose to install optional features, they may safely disable them later on.  Please note that a missing optional feature is not treated as an error.</p>
-<p>An included feature can be updated by patches. By default, <em>Update Manager</em> searches for updates to an included feature at <strong>the update site for the parent feature</strong>; but, this setting can be overridden. </p>
-<p>If an included feature contains platform-specific code or resources, then environment   conditions should be specified and associated with that feature.</p>
-<p></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/information.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/information.htm
deleted file mode 100644
index c6fac83..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/information.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Feature Information</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Information</h1>
-<p>The main purpose of the <strong>Feature Information</strong> page is to specify information that is required by <em>Update Manager</em> to install the feature. </p>
-
-<h2>Feature Description</h2>
-<p>A <strong>Feature Description</strong> is a brief component description. </p>
-<p><img src="../../../images/feature_editor/information_description.png" alt="Description"></p>
-<p>Typically, a description is plain text and intended to be translated. Alternatively, you can provide the description in HTML format and point to it via a URL. The URL can be specified as   absolute or relative. If a relative URL is specified, it is assumed to be relative to (and packaged   in) the feature archive. </p>
-
-<h2>Copyright Notice </h2>
-<p>The feature <strong>Copyright Notice</strong> is typically provided as plain text and is intended to be translated. </p>
-<p><img src="../../../images/feature_editor/information_copyright.png" alt="Copyright"></p>
-<p>Alternatively, you can provide the copyright notice in HTML format and point to it via a URL. The URL can be specified as   absolute or relative. If a relative URL is specified, it is assumed to be relative to (and packaged   in) the feature archive. </p>
-
-<h2>License Agreement</h2>
-<p>The <strong>License Agreement</strong> is a feature <em>click-through</em> license. It is typically  simple text and is intended to be translated. </p>
-<p>The license is   displayed in a standard dialog with <strong>Accept</strong> and <strong>Reject</strong> actions during the   download and installation process. </p>
-<p><img src="../../../images/feature_editor/information_license.png" alt="License"></p>
-<p>Note that a <em>click-through</em> license must be   specified for any feature that will be selected for installation or update using   the <em>Update Manager</em>. When using nested features, only the nesting parent   (i.e. the feature selected for installation or update) must have <em>click-through</em> license <strong>Text</strong> defined. </p>
-<p><em><strong>Please note that the license text is required even if the Optional URL attribute is specified. </strong></em></p>
-
-<h2>Sites to Visit</h2>
-<p><strong>Sites to Visit</strong> specify the name and URL of sites to search for new features. </p>
-<p><img src="../../../images/feature_editor/information_sites.png" alt="Sites To Visit"></p>
-<p>In general, a provider can use <strong>Sites to Visit</strong> to reference its own site(s), or partner site(s) that offer complementary features. </p>
-<p>Eclipse uses this data simply as a way to distribute new site URLs to the clients. Sites that belong to   root features (at the top of the hierarchy) typically appear as <strong>Sites to Visit</strong>   in <em>Update Manager</em>. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/installation.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/installation.htm
deleted file mode 100644
index 77bd3f5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/installation.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Feature Installation</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Installation </h1>
-<p>The <strong>Installation</strong> page contains information used by <em>Update Manager</em> when installing the feature.</p>
-<p align="left" class="style2">Feature Data </p>
-<p>In addition to plug-ins, opaque data entries can be specified to carry custom feature information. These entries usually come together with custom install handlers. </p>
-<p>Install handlers can be used to perform non-standard install tasks and manipulate data entries once they are downloaded by the <em>Update Manager</em>. </p>
-<p>You can read more about this and other feature issues in the <em>Workbench User Guide</em>.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/overview.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/overview.htm
deleted file mode 100644
index ad23094..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/overview.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Feature Overview</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Overview</h1>
-<p>The <strong>Overview</strong> page serves a dual purpose:</p>
-<ol>
-  <li>It contains two main sections that define important properties of the feature: <strong>General Information</strong> and <strong>Supported Environments</strong>.</li>
-  <li>It functions as a quick reference on how to define, export and publish a feature by providing the <strong>Feature Content</strong>, <strong>Exporting</strong> and <strong>Publishing</strong> sections. These sections provide hyperlinks that, when clicked, navigate to other pages or invoke commands. </li>
-</ol>
-
-<h2>General Information </h2>
-<p><img src="../../../images/feature_editor/overview_general.png" alt="Feature Overview" > </p>
-<p>An<strong> ID</strong> is mandatory and must comply with the <a href="../../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">specifications</a>.</p>
-<p>A <strong>Version</strong> is mandatory and must be of the form <em>major.minor.</em><em>micro.qualifier</em> (e.g. 1.3.0). </p>
-<p>A <strong>Name</strong> is the translatable presentation name of the feature. This field is required. </p>
-<p>A <strong>Provider</strong> is the translatable name of the feature provider. This field is optional. </p>
-<p>A <strong>Branding   Plug-in</strong> stores branding information for primary features. If not explicitly set, Eclipse will assume that the branding plug-in   has the same identifier as the feature.</p>
-<p>The <strong>Update Site URL</strong> denotes a URL that is used by <em>Update Manager</em> when searching for feature updates.</p>
-<p>The <strong>Update Site Name</strong>  is the human-readable label of the referenced update site. </p>
-<p align="left" class="style2">Supported Environments</p>
-<p>By default, your feature is treated as universally portable. You can add   constraints by providing supported <strong>Operating Systems</strong>, <strong>Window Systems</strong>, <strong>Languages</strong> and/or   <strong>System Architectures</strong>. This information will be used to ensure that your feature   is not installed or shown in the context that does not match these constraints.</p>
-<p><img src="../../../images/feature_editor/overview_environments.png" alt="Feature Environments" ></p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/plugins.htm
deleted file mode 100644
index 8117830..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/feature_editor/plugins.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Included Plug-ins</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Included Plug-ins</h1>
-<p>The <strong>Plug-ins and Fragments</strong> page lists all the plug-ins and fragments that should be packaged in the feature and specifies their properties.</p>
-
-<h2>Plug-in List </h2>
-<p>The <strong>Plug-ins and Fragments</strong> list enumerates all the plug-ins and fragments that are included directly in the feature. </p>
-<p><img src="../../../images/feature_editor/plugins.png" alt="Plug-ins" ></p>
-<p>Press the <strong>Add...</strong> button to browse the list of available plug-ins to add to the list.</p>
-<p>The preferred versioning scheme for referenced plug-ins is to give them a <strong>0.0.0</strong> version. This is a special value that   will be replaced by the actual plug-in version when the feature is exported. This option is especially convenient when   plug-in versions contain a <em>qualifier</em> segment. </p>
-
-<h2>Plug-in Details </h2>
-<p><strong>Plug-in Details</strong> are used as guidelines by <em>Update Manager</em> to determine what, when and how to install the plug-ins included by a feature. </p>
-<p><img src="../../../images/feature_editor/plugins_details.png" alt="Plug-in Details" ></p>
-<p>The <strong>Download Size</strong> and <strong>Installation Size</strong> are optional hints specified to allow <em>Update Manager</em> to provide useful user feedback about the feature being installed.</p>
-<p>The <strong>Unpack the plug-in archive after installation</strong> option determines whether a plug-in is to be unpacked (i.e. flattened) or left in a JAR after installation.</p>
-<p>If a plug-in or fragment contains platform-specific code, then environment   conditions should be specified and associated with that plug-in or fragment.</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm
deleted file mode 100644
index cc7b873..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/access_rules.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link href="../../../../book.css" rel="stylesheet" type="text/css">
-<title>Access Rules</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-
-</head>
-
-<body>
-<h1>Access Rules</h1>
-<p>The Eclipse 3.1 runtime gives the plug-in developer the option
-  to control plug-in code visibility to downstream plug-ins on a per-package basis. </p>
-<p>A package may be classified as one of the following:</p>
-<ol>
-  <li>Accessible</li>
-  <li>Forbidden</li>
-  <li>Internal</li>
-  <li>Internal with friends</li>
-</ol>
-<p>PDE translates these runtime visibility rules into compiler access 
-  restriction rules at compile time. As a result, a violation of a visibility 
-  rule is flagged by the compiler as a warning or an error - depending on the severity 
-  of that violation. </p>
-<p>With this type of support at compile time, one is 
-  never caught by surprise by runtime class loading errors and is always 
-  aware of internal type references.</p>
-<h2>Accessible Packages</h2>
-<p>Accessible packages are visible to downstream plug-ins unconditionally.&nbsp;&nbsp; 
-  While API packages must clearly fall in this category, it is completely up to 
-  the developer to decide what other packages exported by the plug-in ought to 
-  be given this level of visibility.</p>
-<p>In order to declare a package as accessible, you must list it in 
-the <b>Exported Packages</b> section on the <b>Runtime</b> of the plug-in 
-manifest editor and leave the default visibility setting as-is.</p>
-<p><img src="../../../images/access_restrictions/visible.png" alt="Accessible Packages" ></p>
-<p align="center">&nbsp;</p>
-<h2>Forbidden Packages</h2>
-<p>You can hide a package from downstream plug-ins at all times by 
-  <b>excluding</b> it from the list in the <b> Exported Packages</b> section on 
-  the <b>Runtime</b> page of the plug-in manifest editor.</p>
-<p>References to types from a <em>forbidden</em> package result in class loading 
-  errors at runtime.</p>
-<p>To avoid such unpleasant situations:</p>
-<ol>
-  <li>The compiler will flag references to forbidden packages with an error.</li>
-  <li>Types from forbidden packages are NOT available 
-    as proposals in the content assist.</li>
-</ol>
-<p><em>Notes:</em></p>
-<ol>
-  <li> All plug-ins in the Eclipse SDK enumerate all their packages in the <strong>Exported 
-    Packages</strong> section; therefore, none of the packages in the SDK have forbidden 
-    access.</li>
-  <li> The severity level for forbidden references is set on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open problem severities preference page">
-<strong>Java &gt; Compiler &gt; Errors/Warnings &gt; Deprecated and restricted API</strong></a> preference 
-    page.
-    <p> It is strongly recommended that the severity of a forbidden reference 
-      is kept at error.</p>
-  </li>
-</ol>
-<p><img src="../../../images/access_restrictions/forbidden.png" alt="Forbidden preferences"  border="0"></p>
-<h2>Internal Packages</h2>
-<p>Internal packages are packages that are not intended for use by 
-  downstream plug-ins. <em><strong>These packages are visible to downstream plug-ins 
-  by</strong> <strong>default</strong></em>. </p>
-<p>Internal packages are hidden from downstream plug-ins only when 
-  Eclipse is launched in <em><strong>strict</strong></em> mode (i.e. when you 
-  launch with the <em>-Dosgi.resolverMode=strict</em> VM argument).</p>
-<p>Internal packages must be listed in the <b>Exported Packages</b> 
-  section on the <b>Runtime</b> page of the plug-in manifest editor with the <i> 
-  <b>hidden</b></i> option selected.</p>
-<p> <img src="../../../images/access_restrictions/hidden.png" alt="discouraged access" ></p>
-<p>Two measures are taken to discourage downstream plug-ins from 
-  referencing internal packages:</p>
-<ul>
-  <li>The compiler flags references to internal packages with a <em>warning</em>.</li>
-</ul>
-<p><img src="../../../images/access_restrictions/compiler.png" alt="discouraged access" ></p>
-<ul>
-  <li>Types from discouraged packages are available as content assist proposals; but, with a lower priority.</li>
-</ul>
-<p><img src="../../../images/access_restrictions/content_assist.png" alt="discouraged content assist" ></p>
-<p>The severity level for discouraged references can be set on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.ProblemSeveritiesPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the problem severities preference page">
-<strong>Java &gt; Compiler &gt; Errors/Warnings &gt; Deprecated and restricted API</strong></a> 
-preference page.</p>
-<p> <img src="../../../images/access_restrictions/discouraged.png" alt="Discouraged preferences"  border="0"></p>
-<h2>Internal packages with friends</h2>
-<p>It is important for a plug-in to be able to grant full access 
-  to its internal packages to designated &quot;friend&quot; plug-ins. For instance, 
-  the PDE code is split across multiple plug-ins, and the <em>org.eclipse.pde.ui</em> 
-  plug-in should have full access to <em>org.eclipse.pde.core</em>'s internal 
-  packages.</p>
-<p>In the example below, the the <em>org.eclipse.pde.ui</em> friend plug-in has full access to the <em>org.eclipse.pde.internal.core.bundle</em> 
-  package from the <em>org.eclipse.pde.core </em>plug-in.</p>
-<p><img src="../../../images/access_restrictions/friend.png" alt="Friends" ></p>
-<p>The friends are free to reference any type from the <em>org.eclipse.pde.internal.core.bundle</em> 
-  package with the compiler's blessing. </p>
-<p>On the other hand, if any other plug-in references a type from 
-  the <em>org.eclipse.pde.internal.core.bundle</em> package, the compiler flags 
-  the reference as a discouraged reference as described in the previous section.</p>
-<h2>How to enable access restrictions</h2>
-<p>To take advantage of the PDE access restriction support, the only 
-  requirement is that the plug-ins in question contain an OSGi bundle <em>MANIFEST.MF</em>. 
-  PDE will take care of the rest including the management of the plug-in classpath.</p>
-<p>If the plug-in does not contain a <em>MANIFEST.MF</em> file, that file 
-  can be created as follows:</p>
-<ol>
-  <li>Open the <em>plugin.xml</em> in the plug-in manifest editor.</li>
-  <li>In the <strong>Plug-in Content</strong> section of the <strong>Overview</strong> 
-    page, click on the '<strong>create an OSGi bundle manifest</strong>' link.</li>
-</ol>
-  <p><img src="../../../images/access_restrictions/convert.PNG" alt="convert to manifest.mf" ></p>
-  <h2>Inspecting access rules</h2>
-  <p>You can inspect the access restriction rules imposed on each 
-    classpath entry by PDE on the <strong>Java Build Path</strong> property page 
-    of your plug-in project. </p>
-  <p><img src="../../../images/access_restrictions/properties.png" alt="Java Build Path Properties" ></p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/automated_management.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/automated_management.htm
deleted file mode 100644
index 3959544..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/automated_management.htm
+++ /dev/null

@@ -1,13 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Automated Management of Dependencies</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-
-<body>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/build.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/build.htm
deleted file mode 100644
index 3af7d24..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/build.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Build</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Build</h1>
-<p>The <strong>Build </strong>page contains all the information needed to   build, package and export the plug-in. Although it appears as a page in the plug-in   manifest editor, changes made to it are written by PDE to the plug-in's <em>build.properties</em> file.  The <em>build.properties</em> file solely guides the build   process.</p>
-
-<h2>Runtime Information</h2>
-<p>The <strong>Runtime Information</strong> section lists all the libraries that you want to build. For each library, you must list the source folder(s) that will be   compiled into the library. </p>
-<p><img src="../../../images/plugin_editor/runtime.png" alt="Runtime" ></p>
-<p>If your plug-in declares more than one library, order them   correctly using the <strong>Up</strong> and <strong>Down</strong> button.  This will ensure that they get compiled in the correct   order.</p>
-
-<h2>Binary and Source Builds </h2>
-<p><img src="../../../images/plugin_editor/binary_source.png" alt="Binary and Source Builds"></p>
-
-<p>The <strong>Binary Build</strong> section is where you select all the files and folders that will make it into the packaged plug-in.</p>
-<p>The <strong>Source Build </strong>section has a specialized purpose and is   not commonly used or needed by the general population. It is only needed when you need to ship source in separate plug-ins and features rather than in binary plug-ins. See the <code>org.eclipse.pde.core.source</code> extension point for details.</p>
-
-<h2>Extra Classpath Entries </h2>
-<p>If you need extra libraries on the build path for   your source code to compile, you can add these required JARs in the <strong>Extra Classpath   Entries</strong> section. </p>
-<p><img src="../../../images/plugin_editor/classpath.png" alt="Extra Classpath"></p>
-<p>Please note that this section should be used to add libraries that are not required to be on the plug-in runtime classpath. </p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/dependencies.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/dependencies.htm
deleted file mode 100644
index 7c79bae..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/dependencies.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Dependencies</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Dependencies</h1>
-<p>The <strong>Dependencies</strong> page shows the dependencies that your plug-in has on other plug-ins. On this page, you must list all plug-ins that contribute code to your plug-in project and that are required to be on your project's classpath in order to compile. When you modify the list of dependencies and save the file, PDE will automatically update your classpath.</p>
-
-<h2>Required Plug-ins </h2>
-<p>The <strong>Required Plug-ins</strong> section specifies your plug-in project's dependencies on other plug-ins by explicitly enumerating these plug-ins. Your plug-in will not resolve or run at runtime if any of your plug-in dependencies are missing or unresolved. </p>
-<p><img src="../../../images/plugin_editor/dependencies_required.png" alt="Require-Bundle" ></p>
-<p>Press the <strong>Add...</strong> button to browse the list of all plug-ins that your plug-in may make a dependency on.</p>
-<p>The order of the plug-ins in the list is important because it dictates the   class loading order at runtime; therefore, use the <strong>Up</strong> and <strong>Down</strong> buttons to organize the list as appropriate.</p>
-<p>You can set several properties on each plug-in dependency by selecting a plug-in and clicking the <strong>Properties</strong> button:</p>
-<ul>
-  <li>You can make a plug-in dependency optional by selecting the <strong>Optional</strong> option.  When this option is enabled, it indicates to the runtime that your plug-in should run even if an optional plug-in dependency is missing or not resolved.</li>
-  <li>You  can select the <strong>Re-export this dependency</strong> option to re-export your dependency in order to make it automatically visible to any downstream plug-in that require it.  Please note that you should only re-export a given plug-in dependency only if your plug-in exposes one ore more API's from that dependency.</li>
-  <li>You can also specify the <strong>Minimum Version</strong> and <strong>Maximum Version</strong> of the plug-in dependency.</li>
-</ul>
-
-<h2>Imported Packages </h2>
-<p>The Eclipse runtime provides the flexibility of specifying a dependency on a package without explicitly identifying its originating plug-in. These packages are enumerated in the <strong>Imported Packages</strong> section. </p>
-<p><img src="../../../images/plugin_editor/dependencies_imported.png" alt="Import-Package" ></p>
-<p>Press the <strong>Add...</strong> button to browse the list of packages available to your plug-in for importing. PDE filters out packages contributed by plug-ins that are already on your plug-in classpath. </p>
-<p>You can set several properties on each package dependency:</p>
-<ul>
-  <li>You can make the dependency optional by selecting the <strong>Optional</strong> option.  When this option is enabled, this indicates to the runtime that your plug-in should run even if a package dependency is missing.</li>
-  <li>You can specify the <strong>Minimum Version</strong> and <strong>Maximum Version</strong> of the package you require.</li>
-</ul>
-
-<h2>Automated Management of Dependencies </h2>
-<p>The <strong>Automated Management of Dependencies</strong> section provides a new flexible workflow.  This workflow allows you to code your plug-in first and then have PDE analyze your code and automatically generate the list of plug-in dependencies. </p>
-<p><img src="../../../images/plugin_editor/dependencies_automated.png" alt="Automated Management" ></p>
-<p>Press the <strong>Add...</strong> button to add plug-ins to the list.  Consequently, this action will augment your development build path and your content assist scope accordingly.</p>
-<p>These dependencies do not get added to the <em>MANIFEST.MF</em> file immediately; however, you   can start coding right away as if they were.</p>
-<p>At any time, you can click the <strong>add dependencies</strong> hyperlink to have PDE analyze your code and generate the correct   dependencies in your <em>MANIFEST.MF</em> file via either the <strong>Require-Bundle</strong> or <strong>Import-Package</strong>   headers.</p>
-
-<a name="dependency_analysis"></a>
-<h2>Dependency Analysis</h2>
-<p>The <strong>Dependency Analysis</strong> section contains several useful features that help you examine and optimize your plug-in dependencies to make your plug-in run better. </p>
-<p><img src="../../../images/plugin_editor/dependencies_analysis.png" alt="Dependency Analysis"></p>
-<p>Since JARs from all the plug-ins listed as dependencies will be on your plug-in runtime classpath, it is very important not to list dependencies that are not required.  Otherwise, class loading performance will be detrimentally affected.  If you click the <strong>Find unused dependencies</strong> hyperlink, PDE will find unused and redundant entries in the list of required plug-ins and imported packages and offer to remove them. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/editor.htm
deleted file mode 100644
index ec572f1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/editor.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Manifest Editor</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Manifest Editor </h1>
-<p>PDE provides a single form-based multi-page plug-in manifest editor that manages all plug-in files: <em>MANIFEST.MF</em>, <em>plugin.xml</em>, <em>fragment.xml</em> and <em>build.properties</em>. The plug-in manifest editor is used as though a single file is being edited; while, PDE handles the task of writing the data to the different files on disk. </p>
-<p>For details on the individual editor pages, refer to the following documents:</p>
-<ul>
-  <li><a href="overview.htm">Plug-in Overview</a></li>
-  <li><a href="dependencies.htm">Plug-in Dependencies</a></li>
-  <li><a href="runtime.htm">Plug-in Runtime</a></li>
-  <li><a href="extensions.htm">Plug-in Extensions</a></li>
-  <li><a href="extension_points.htm">Plug-in Extension Points</a></li>
-  <li><a href="build.htm">Plug-in Build</a></li>
-</ul>
-
-<h2>Manifest Editor Presentation</h2>
-<p>By default, the plug-in manifest editor shows information and tabs on extensions, extension points and Equinox-specific <em>MANIFEST.MF</em> headers and attributes. If you do not wish to use these Eclipse-specific features, you can filter out these pages from the editor on the <strong>Plug-in Development</strong> property page of your plug-in project via <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.MainPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the main PDE preference page">
-<strong>Properties &gt; Plug-in Development</strong>
-</a> from   the context menu of plug-in projects. </p>
-
-<p><img src="../../../images/plugin_editor/filter_pages.PNG" alt="Editor Presentation" ></p>
-
-<h2>Relevant Links</h2>
-<ul>
-	<li><a href="../../../../../org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html">OSGi Bundle Manifest Headers</a>
-	</li>
-</ul>		
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extension_points.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extension_points.htm
deleted file mode 100644
index a67baef..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extension_points.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Extension Points</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Extension Points</h1>
-<p>Extension points define new function points for the platform that other   plug-ins can plug into. The <strong>Extension Points</strong> page is the place to add, remove and edit extension   points declared by your plug-in.</p>
-<p><img src="../../../images/plugin_editor/extension_points.png" alt="Extension Points" ></p>
-<p>An extension point has three attributes:</p>
-<UL>
-  <LI><strong>ID</strong> - a required attribute whose value is a simple name</LI>  
-  <LI><strong>Name</strong> - a required attribute whose value is a translatable string </LI>
-  <LI><strong>Schema</strong> - an optional attribute whose value is a relative path to the schema   corresponding to this extension point</LI>
-</UL>
-<p>Although the <strong>Schema</strong> attribute is optional, you are strongly encouraged to   provide a schema; since, PDE utilizes it to assist other developers in using your extension point.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extensions.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extensions.htm
deleted file mode 100644
index 4fec4d6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/extensions.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Extensions</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Extensions</h1>
-<p>Extensions are the central mechanism for contributing behavior to the   platform. Unless your plug-in is a documentation plug-in or a simple Java API library made available to   other plug-ins, new behavior is contributed as an extension.</p>
-<p>The <strong>Extensions</strong> page is where you can add, remove and modify the extensions   your plug-in contributes to the platform.</p>
-
-<h2>All Extensions</h2>
-<p>In the <strong>All  Extensions</strong> section, press <strong>Add...</strong> to view all the available extension points that you can extend. </p>
-<p><img src="../../../images/plugin_editor/extensions_details.png" alt="Extension Details" ></p>
-<p>Each extension point comes with an XML schema specifying its grammar. When you select a new extension, PDE extracts the grammar for the   corresponding extension point and populates the context menu of each element   selected in the <strong>All Extensions</strong> viewer with a list of valid child elements that you   can create.</p>
-<p>For each selected element in the body of an extension, PDE populates the   <strong>Extension Element Details</strong> section with all the valid attributes for that   element. Required attributes are denoted with an asterisk. </p>
-<p>When you hover your mouse over an attribute name, a tool tip box appears   showing the description of that attribute.</p>
-<p>When an attribute expects the name of a Java class as a value (e.g. the <em>class</em> attribute above), clicking on the name of the attribute will open the Java file specified - if it exists. If the file does not exist, then clicking on the <em>class</em> link will bring up the JDT New Class wizard to create a new Java class on the fly.</p>
-<p>Some extension elements do not have attributes. Instead they require a description which can be specified in the <strong>Body Text</strong> section: </p>
-<p><img src="../../../images/plugin_editor/extensions_body.png" alt="Body Text" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm
deleted file mode 100644
index d39bb9a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/overview.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Overview</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Overview</h1>
-<p>The <strong>Overview</strong> page serves a dual purpose:</p>
-<ol>
-  <li> It contains two main sections that define important plug-in properties: <strong>General Information</strong> and <strong>Execution Environments</strong>. </li>
-  <li>It functions as a quick reference on how to develop, test and deploy plug-ins by providing the <strong>Plug-in Content</strong>, <strong>Extensions</strong>, <strong>Testing</strong> and <strong>Exporting</strong> sections.  These sections provide hyperlinks that, when clicked,  navigate to other pages or invoke commands. </li>
-</ol>
-
-<h2>General Information</h2>
-<p><img src="../../../images/plugin_editor/overview_general.png" alt="General Overview" > </p>
-<p>An<strong> ID</strong> is mandatory and must comply with the <a href="../../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">plugin.dtd</a>.</p>
-<p>A <strong>Version</strong> is mandatory and must be of the form <em>major.minor.micro.qualifier</em> (e.g. 1.3.0).</p>
-<p>A<strong> Name</strong> is the translatable presentation name of the plug-in. This field is required. </p>
-<p>A<strong> Provider</strong> is the translatable name of the plug-in provider. This field is optional. </p>
-<p>A <strong>Platform filter</strong> is a valid LDAP string that must evaluate to true in a running system for the the plug-in to run. For example, the following filter indicates that the plug-in is designed to only run on platforms with a <em>win32</em> windowing system:  <strong>Eclipse-PlatformFilter: (ws=win32)</strong>.  If a   user attempts to run Eclipse on a platform that does not meet this requirement,   the plug-in will be silently ignored by the runtime. </p>
-<p>An <strong>Activator</strong> is a Java class that controls the plug-in's life cycle. It is only needed if you require work to be done on the startup or shutdown of your plug-in. </p>
-
-<h2>Execution Environments </h2>
-<p>A bundle execution environment specifies the minimum level of JRE required for   the plug-in to run. If the JRE used to run Eclipse does not meet the   requirement, the plug-in will not run. </p>
-<p><img src="../../../images/plugin_editor/overview_execution.png" alt="Execution Environments" ></p>
-<p>Press the <strong>Add...</strong> button to browse a list of available execution environments and add one that is most suitable for your plug-in. For example, if you declare <em>J2SE-1.4</em> as your plug-in's bundle execution environment, your plug-in will only run with a JRE version &gt;= 1.4.</p>
-<p>If your plug-in can run in an execution environment that is not a proper subset of the execution environment specified (e.g. <em>J2SE-1.4</em> and <em>CDC-1.1/Foundation-1.1</em>), both execution environments should be specified.</p>
-<p>During a plug-in export, the plug-in code is compiled against the JRE   associated with the first execution environment listed in the <em>MANIFEST.MF</em> file  .&nbsp; Click on the <strong>Configure JRE associations...</strong> link to open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.debug.ui.jreProfiles)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the JRE profiles preference page">
-<strong>Windows &gt; Preferences... &gt; Java &gt; Installed JREs &gt; Execution Environments</strong>
-</a>
- preference   page for a list of OSGi execution environments and their corresponding list of compatible JREs installed on the system.</p>
-<p>Whenever you update the list of execution environments for your plug-in, you should <strong>Update the classpath settings</strong> via the link to ensure you are compiling against the right JRE and have the settings that best match your first execution environment. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/runtime.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/runtime.htm
deleted file mode 100644
index 29e3417..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/runtime.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Runtime</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Runtime</h1>
-<p>The <strong>Runtime</strong> page shows all the packages that your   plug-in makes visible to other plug-ins and the libraries and folders that constitute the plug-in runtime classpath. </p>
-
-<h2>Exported Packages </h2>
-<p>The <strong>Exported Packages</strong> section lists all packages that your plug-in intends to expose to downstream clients. </p>
-<p><img src="../../../images/plugin_editor/runtime_exported.png" alt="Exported Packages" ></p>
-<p>You can set a <strong>Version</strong> on each exported package when you press <strong>Properties...</strong>. The version is of the form <em>major.minor.micro</em> (e.g. 1.3.0).</p>
-<p>Press <strong>Add...</strong> to see the list of packages available for export that are not already in your list.</p>
-<p>PDE can calculate the <em>uses</em> directive, as defined in the OSGi Specification, for all of your publicly exported packages. Press the <strong>Calculate Uses</strong> button to begin. Because this process involves code introspection, this might be a long running operation.</p>
-<p>You can control the visibility of each package to downstream clients in the <strong>Package Visibility</strong> section. Refer to the <a href="access_rules.htm">Access Rules</a> document for full details. </p>
-
-<a name="classpath"></a>
-<h2>Classpath</h2>
-<p>The <strong>Classpath</strong> section lists all the locations the runtime will search when loading classes from this plug-in. </p>
-<p><img src="../../../images/plugin_editor/runtime_classpath.png" alt="Classpath" ></p>
-<p><em><strong>Since JAR'd plug-ins are the recommended format for Eclipse 3.1 and up built plug-ins, it is recommended to leave this section blank.</strong></em></p>
-<p>Press <strong>New...</strong> to add the name of a library that has not been built yet.</p>
-<p>Press <strong>Add...</strong> to browse the current plug-in project and add an existing JAR or folder to the classpath.</p>
-<p>The order of the table entries dictate the class loading order; therefore, use the <strong>Up</strong> and <strong>Down</strong> buttons to organize your classpath accordingly.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/testing.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/testing.htm
deleted file mode 100644
index 28073cb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/manifest_editor/testing.htm
+++ /dev/null

@@ -1,18 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Testing</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Testing</h1>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/branding.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/branding.htm
deleted file mode 100644
index 677bf2d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/branding.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Branding</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Branding</h1>
-<p>The <strong>Branding</strong> page gives the product its identity by customizing the window images, <em>About</em> dialog and the welcome experience. </p>
-
-<h2>Window Images </h2>
-<p>The <strong>Window Images</strong> section specifies the images associated with a product. If the images supplied by you do not match the size requirements, PDE flags a warning at the top of the page. </p>
-<p><img src="../../../images/product_editor/branding_window.png" alt="Window Images" > </p>
-
-<h2>About Dialog </h2>
-<p>The <strong>About Dialog</strong> is customiable by providing a custom image and text. </p>
-<p><img src="../../../images/product_editor/branding_about.png" alt="About Image" ></p>
-<p>The <em>About dialog</em> text and image are also properties in the org.eclipse.core.runtime.products extension. </p>
-
-<h2>Welcome Page </h2>
-<p>It is recommended to ship a product with its own <strong>welcome page</strong> to introduce the features of the product to first-time users.</p>
-<p><img src="../../../images/product_editor/branding_welcome.png" alt="Intro" ></p>
-<p>Providing a <strong>welcome page</strong> (Intro) requires the binding of the product to an <em>org.eclipse.ui.intro</em> extension. </p>
-<p>The Intro ID combo box is populated with existing Intro identifiers defined by plug-ins in the workspace and in the target.</p>
-<p>You may also create a new Intro on the fly by pressing the New.. button. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/configuration.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/configuration.htm
deleted file mode 100644
index ac55c97..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/configuration.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Configuration</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Configuration</h1>
-<p>The <strong>Configuration</strong> page defines start level information for the product and the configuration file needed to run the product. </p>
-
-<h2>Start Levels</h2>
-<p>In the start level section, you can list plug-ins to be automatically started or started with a specific start level.</p>
-
-<h2>Configuration File </h2>
-<p>Upon startup, the runtime reads a configuration file named <EM>config.ini</EM> located in a <EM>configuration/</EM> subdirectory of the   configuration area of an Eclipse product. This file is a standard properties file that can configure many aspects of the runtime.   For a full list of the supported properties, refer to the <A href="../../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse   runtime options</A> document.</p>
-<p><img src="../../../images/product_editor/configuration_file.png" alt="Configuration File" ></p>
-<p>The <STRONG>Generate a default config.ini file </STRONG>is the   default option and is recommended unless you have some very specific needs. When   this option is selected, PDE generates a <EM>config.ini</EM> file with the   following properties:</p>
-<UL>
-  <LI><STRONG>osgi.bundles</STRONG> - lists all the bundles that should be   installed and optionally started once the system is up and running. This list is   based on the <EM>osgi.bundles</EM> key found in the <EM>${target_home}/configuration/config.ini</EM> file. (Note, the ${target_home}   variable is the location of the target platform).</li>   
-  <LI><STRONG>osgi.bundles.defaultStartLevel</STRONG> - denotes the default OSGi   start level at which a bundle should start. The default value is set to <STRONG>4.</STRONG></li>
-  <LI><STRONG>eclipse.product</STRONG> - specifies the ID of the product to launch. </LI>
-  <li><STRONG>osgi.splashPath</STRONG> - specifies one or more locations of the   splash screen. </LI>
-</UL>
-<p>You also have the option to <strong>use an existing config.ini file</strong> which will be copied by PDE to your final product as-is.</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/dependencies.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/dependencies.htm
deleted file mode 100755
index 18a5fea..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/dependencies.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Configuration</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Dependencies</h1>
-<p>The <strong>Dependencies</strong> page defines the content of the product. </p>
-
-<h2>Content</h2>
-<p>If the product is plugin-based, the <strong>Configuration</strong> page shows a <strong>Plug-ins and Fragments</strong> section where you list all the plug-ins that will make up the product. This section also provides <strong>New Plugin...</strong> and <strong>New Fragment...</strong> buttons to enable you to create new plug-ins and fragments on the fly. </p>
-<p><img src="../../../images/product_editor/configuration_plugins.png" alt="Configuration Plug-ins" > </p>
-<p>If the product is feature-based, the <strong>Configuration</strong> page shows a <strong>Features</strong> section where you list all the features that will make up the product. This section also provides a <strong>New Feature...</strong> button to enable you to create new features on the fly.</p>
-<p><img src="../../../images/product_editor/configuration_features.PNG" alt="Configuration Features" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/editor.htm
deleted file mode 100644
index 5e8e50b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/editor.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Configuration Editor</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Configuration Editor</h1>
-<p>Building an Eclipse product using PDE is centered around a product configuration, a <em>.product</em> file. This file manages all aspects of a product definition from its constituent plug-ins to configuration files to branding. </p>
-<p>The product configuration is entirely managed by PDE to simplify Eclipse product development. Its format is internal and is not intended to be read by tools other than PDE.</p>
-<p>PDE provides a form-based multi-page editor to manage the product configuration.</p>
-<p>For details on the <strong>Product Configuation Editor</strong>, refer to the following documents:</p>
-<ul>
-  <li><a href="overview.htm">Product Overview</a></li>
-  <li><a href="dependencies.htm">Product Dependencies</a></li>
-  <li><a href="configuration.htm">Product Configuration</a></li>
-  <li><a href="launching.htm">Product Launching</a></li>
-  <li><a href="splash.htm">Product Splash</a></li>
-  <li><a href="branding.htm">Product Branding</a></li>
-  <li><a href="licensing.htm">Product Licensing</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/launching.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/launching.htm
deleted file mode 100644
index 596c583..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/launching.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Launching</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Launching</h1>
-<p>The <strong>Launching</strong> page customizes the native launcher of your product and the launching arguments.</p>
-
-<h2>JRE</h2>
-<p>The <strong>Java Runtime Environment</strong> section allows you to bundle a JRE with your product automatically. </p>
-<p><img src="../../../images/product_editor/launcher_jre.png" alt="launcher jre" ></p>
-<p>The JRE will be placed in the <strong>jre</strong> directory at the root of your product. </p>
-
-
-<h2>Program Launcher</h2>
-<p>The <strong>Program Launcher</strong> section customizes the name and icon of the native launcher of the product. </p>
-<p><img src="../../../images/product_editor/launcher_program.png" alt="Launcher Exe" ></p>
-<p>To customize the name of the launcher, just enter the name in the <strong>Launcher Name</strong> field. If left unspecifed, the name will default to <em>eclipse</em>.</p>
-<p>Customizing the launcher icon varies per platform. The product editor indicates the platform requirements, and flags warnings at the top of the page if the supplied icons do not match the size or depth requirements. </p>
-
-<h2>Launching Arguments</h2>
-<p>To launch an Eclipse product with default program and VM arguments, these arguments are stored in a file named <em>&lt;launcher_name&gt;.ini </em>at the root of the product. PDE creates this file with its content based on the values entered in the <strong>Launching Arguments</strong> section. </p>
-<p><img src="../../../images/product_editor/launcher_arguments.png" alt="launcher arguments" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/licensing.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/licensing.htm
deleted file mode 100755
index eb0df23..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/licensing.htm
+++ /dev/null

@@ -1,16 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Configuration</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Licensing</h1>
-<p>The <strong>Licensing</strong> page allows you to add a URL and license text for your product. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm
deleted file mode 100644
index 1f81299..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Overview</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Overview</h1>
-<p>The <strong>Overview</strong> page defines the product and provides hot links to test and export it. </p>
-
-<h2>Product Definition</h2>
-<p>A product is an <em>org.eclipse.core.runtime.products</em> extension. At minimum, it must have a <strong>name</strong>, an <strong>ID</strong>, a <strong>version</strong> and an <strong>application</strong>. </p>
-<p><img src="../../../images/product_editor/overview_definition.png" alt="Product Definition" > </p>
-<p>The <strong>product name</strong> is a translatable string that appears in the title bar of the application. It is defined as a property in the <em>org.eclipse.core.runtime.products</em> extension.</p>
-<p>The <strong>product identifier</strong> combo box is populated with the identifiers of all product extensions defined in the workspace and the target. You can select one of the defined products, or you can create a new product definition on the fly using the <strong>New...</strong> button.</p>
-<p>The <strong>product version</strong> is a string that is used to version your product file.</p>
-<p>A product must be associated with an <strong>application</strong>, which acts as the main entry point when the product is launched. An application is an <em>org.eclipse.core.runtime.applications</em> extension. The <strong>application</strong> combo box is populated with the identifiers of all application extensions defined in the workspace and the target.</p>
-<p>A product configuration can be <strong>plugin-based</strong> or <strong>feature-based</strong>. A plugin-based configuration is the default because it is simple and does not force you to understand <em>Update Manager</em>-specific concepts like features before building a product. A feature-based configuration is more powerful though, since it enables you to deliver a product that is <strong><em>updatable</em></strong>. That is, you can later publish patches or upgrades to your product on an update site and have your customers use the Eclipse <em>Update Manager</em> to download and install these updates. </p>
-
-<h2>Testing</h2>
-<p>To test your product configuration, just click one of the hot links in the <strong>Testing</strong> section. </p>
-<p><img src="../../../images/product_editor/overview_testing.png" alt="Product Testing" ></p>
-<p>Similar  hot links are also available in the <a href="../manifest_editor/editor.htm">plug-in manifest editor</a>, but there is a noticeable difference in this instance. There is a <strong>Synchronize</strong> step.</p>
-<p>So why is a <strong>Synchronize</strong> needed? Remember that the product configuration is for PDE use only and is   not interpreted nor read by the runtime. Some of the data that enter in this   file (e.g. product ID, application, window images, about image, etc.) must be   copied to the plugin.xml file of your branding plug-in for these changes to take <em><STRONG>real</STRONG></em> effect at runtime. That's what the <strong>synchronize</strong> action   does. It makes sure your <em>plugin.xml</em> contains up-to-date data and in sync with   the product configuration.</p>
-<p>If you use the hot link in this section, PDE does an implicit synchronization of files. If the product is launched via other means, e.g. a context menu launch shortcut, then automatic synchronization does not take place. </p>
-
-<h2>Exporting</h2>
-<p>To export an Eclipse product, you can invoke the <a href="../../export_wizards/export_product.htm">Eclipse Product Export</a> wizard via the hot link in the <strong>Exporting</strong> section. </p>
-<p><img src="../../../images/product_editor/overview_exporting.png" alt="Product Exporting" ></p>
-<p>To export a single product configuration to multiple platforms, you need to have the RCP delta pack installed. It is available for download from the same place as the Eclipse SDK. The RCP delta pack contains all the different platform-specific fragments needed for all supported platforms. </p>
-<p>Once the RCP delta pack is in the target platform, PDE detects the presence of the <em>org.eclipse.equinox.launchers</em> feature and enables the cross-platform export mode.</p>
-<p>Note, to use the RCP delta pack, you have to ensure that the 'Build target platform based on the target's installed plug-ins' option remains unchecked in the <strong>Target Platform</strong> preference page.</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/splash.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/splash.htm
deleted file mode 100644
index f15e7cb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/splash.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Splash</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-
-<h1>Product Splash</h1>
-
-<p>The <strong>Splash</strong> page provides the ability to customize your product with
- a splash screen and a template or a progress bar and message.
-</p>
-
-
-
-<h2>Location</h2>
-<p>The <strong>splash screen</strong> is typically located at the root of the 
- product-defining plug-in and must be called <em><strong>splash.bmp</strong></em>. 
-</p>
-
-<p><img src="../../../images/product_editor/splash_location.png" alt="Splash screen location" ></p>
-
-<p>Alternately, you may choose to place it at the root of any other plug-in in the 
- product (the name restriction stands). 
-</p>
-
-
-
-<h2>Customization</h2>
-
-<p>To customize the startup of a product, you can use either a splash screen 
- template or a progress bar and message.  
-</p>
-
-<p><img src="../../../images/product_editor/splash_custom.png" alt="Splash screen location" ></p>
-
-<p>Splash screen templates contribute custom behavior to the splash screen that
- appears during startup.  The <strong>Template</strong> combo contains three templates
- available for your convenience.  During the export process the selected template's 
- required code will be added and a <em>org.eclipse.ui.splashHandlers</em> extension 
- will be created.  Please be aware that you may only use a splash screen 
- template if your platform is built with 3.3 or higher.  
-</p>
-
-<p>Another option to customize your product is to use the integrated progress bar 
- in the Eclipse splash screen by specifying the co-ordinates of the 
- <strong>progress bar</strong> and <strong>progress message</strong>,
- as well as the text color.  The integrated progress data is specified using properties 
- in the <em>org.eclipse.core.runtime.products</em> extension. 
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/editor.htm
deleted file mode 100644
index 3bf9cb1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/editor.htm
+++ /dev/null

@@ -1,168 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Extension Point Schema Editor</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Extension Point Schema Editor</h2>
-		
-		<h3>About Extension Point Schemas</h3>
-		
-		<p>
-			An extension point schema is an XML schema file that 
-			defines a contract for extension points that extensions 
-			must conform to in order to plug-in and extend the 
-			platform.  
-			
-			More specifically, an extension point schema specifies a formal grammar for an
-			extension point's elements and attributes.  This grammar dictates the		
-			structure, content and semantics of any contributed extension's XML mark-up.
-		</p>
-			
-		<p>
-			Extension point schemas are used during plug-in development to do the following:
-		</p>			
-		
-		<ul>
-			<li>
-				Validate extensions defined in workspace plug-ins.
-			</li>
-			<li>
-				Generate reference extension point documentation.
-			</li>
-			<li>
-				Assist the user in extension creation.
-			</li>			
-		</ul>
-
-		<h3>About This Editor</h3>
-		
-		<p>
-			The <strong>Extension Point Schema Editor</strong> allows you to do the following:
-		</p>
-		
-		<ul>
-			<li>
-				Create and edit an extension point schema's grammar.
-			</li>
-			<li>
-				Include and use the grammar defined by other shared extension point schemas.
-			</li>
-			<li>
-				Document an extension point schema's grammar.
-			</li>
-			<li>
-				Specify schema metadata used by PDE to automate common tasks.
-			</li>		
-			<li>
-				Preview the extension point schema's reference document.
-			</li>					
-		</ul>			
-			
-		<p>
-			This editor abstracts the extension point schema's file mark-up away as an implementation detail that you do 
-			not have to learn to use.
-		</p>
-
-		<h3>Editor Pages</h3>
-		
-		<p>
-			This editor is comprised of the following pages:
-		</p>
-
-		<ul>
-			<li>
-				<a href="page_schema_overview.htm">Schema Overview Page</a>
-			</li>
-			<li>
-				<a href="page_schema_definition.htm">Schema Definition Page</a>
-			</li>
-		</ul>
-
-		<h3>Global Editor Actions</h3>
-		
-		<p>
-			Click the <strong>Preview Reference Document</strong> hyperlink to 
-			preview the reference document pertaining to the saved or unsaved contents of
-			the edited extension point schema.  This action generates an HTML representation of the 
-			schema and opens it in a browser.
-		</p>
-
-		<p>
-			<img src="../../../images/schema_editor/editor_header.png" alt="Schema Header">
-		</p>
-
-		<h3>PDE XML Schema Support</h3>
-
-		<p>
-			Extension point schemas are XML schemas.  As a result, they are
-			written in XML and are able to take advantage of schema annotations 
-			to improve ease of processing and readability.
-			However, extension point schemas only use a small subset 
-			of XML schema features defined by the W3C XML Schema specification.
-		</p>
-		<p>
-			Use of a small XML schema feature subset dramatically simplifies the structure 
-			and syntax of extension	point schemas while still addressing the required needs of the 
-			extension point problem	domain.  
-			It also provides an aesthetic one-to-one mapping of the schema grammar to an 
-			equivalent DTD grammar.
-		</p>
-
-		<p>
-			The main extension point schema limitations are as follows:
-		</p>
-
-		<ul>
-			<li>
-				Only global element declarations are allowed.
-			</li>
-			<li>
-				Only local attribute declarations are allowed.
-			</li>
-			<li>
-				Only sequence and choice compositors are supported.
-			</li>		
-			<li>
-				Only string and boolean attribute types are allowed.
-			</li>
-			<li>
-				Only the enumeration restriction is supported for 
-				attributes of type string.
-			</li>
-			<li>
-				Only local element type declarations are allowed.
-			</li>
-			<li>
-				XML namespaces are not supported.
-			</li>
-			<li>
-				An element can be declared to specify either element
-				content or character content; but, not mixed content
-				(both element and character content).
-			</li>
-		</ul>  
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../../file_wizards/new_schema.htm">New Extension Point Schema Wizard</a>
-			</li>				
-			<li>
-				<a href="http://wiki.eclipse.org/index.php/FAQ_What_is_an_extension_point_schema%3F">
-					What is an extension point schema?
-				</a>
-			</li>
-			<li>
-				<a href="../manifest_editor/editor.htm">Plug-in Manifest Editor</a>
-			</li>	
-		</ul>
-		
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_definition.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_definition.htm
deleted file mode 100644
index 6073c5a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_definition.htm
+++ /dev/null

@@ -1,828 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Schema Definition Page</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Schema Definition Page</h2>
-
-		<h3>About This Page</h3>
-
-		<p>
-			This form page allows you to edit the structure and 
-			properties of schema objects that constitute the edited schema's
-			grammar.
-		</p>
-		
-		<p>
-			The structure of schema objects are edited in 
-			the <strong>Extension Point Elements</strong> section.  
-			This section occupies the upper left-hand portion of the editor area. 
-		</p>
-		<p>
-			The properties of schema objects are edited in the 
-			<strong>&lt;schema-object&gt; Details</strong> sections.
-			These sections are activated in the upper right-hand portion of the editor area depending
-			on the type of schema element selected in the <strong>Extension Point Elements</strong> section. 
-		</p>
-		
-		<h3>Page Sections</h3>
-		
-		<p>
-			This page is comprised of the following sections:
-		</p>		
-		
-		<ul>
-			<li>
-				<a href="#extension-point">Extension Point Elements Section</a>
-			</li>
-			<li>
-				<a href="#description">Description Section</a>
-			</li>
-			<li>
-				<a href="#element">Element Details Section</a>
-			</li>	
-			<li>
-				<a href="#compositor">Compositor Details Section</a>
-			</li>		
-			<li>
-				<a href="#reference">Element Reference Details Section</a>
-			</li>		
-			<li>
-				<a href="#attribute">Attribute Details Section</a>
-			</li>							
-		</ul>
-
-		<a name="extension-point"></a>
-		<h3>Extension Point Elements Section</h3>
-
-		<p>
-			This section allows you to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Visualize and edit the structure of schema objects that 
-				constitute the edited schema's grammar.
-			</li>
-			<li>
-				Activate the corresponding <strong>&lt;schema-object&gt; Details</strong> section 
-				used to edit the properties of a selected schema object.
-			</li>
-		</ul>
-
-		<p>
-			This section is directly accessible through the <strong>Schema Definition</strong> form page.
-		</p>
-
-		<h3>Extension Point Elements Section Fields</h3>
-
-		<p>
-			Use the extension point element viewer field to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Visualize and edit the structure of the 
-				elements, attributes and compositors that 
-				constitute the edited schema's grammar.
-			</li>
-			<li>
-				Activate the corresponding <strong>&lt;schema-object&gt; Details</strong> section 
-				used to edit the properties of a selected element, attribute or 
-				compositor.
-			</li>
-		</ul>
-
-		<p>
-			This viewer contains the following nodes:
-		</p>
-
-		<p>
-			Elements:
-		</p>
-
-		<ul>
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/gel_sc_obj.gif" alt="Element Object">
-				- Select the <em>Element</em> node, to activate the <strong>Element Details</strong> section. 
-			</li>														
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/elref_sc_obj.gif" alt="Element Reference Object">
-				- Select the <em>Element Reference</em> node, to activate the <strong>Element Reference Details</strong> section. 
-			</li>			
-		</ul>
-
-		<p>
-			Compositors:
-		</p>
-
-		<ul>
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/seq_sc_obj.gif" alt="Sequence Object">
-				- Select the <strong>Sequence</strong> <em>Compositor</em> node, 
-				to activate the <strong>Compositor Details</strong> section. 
-			</li>													
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/choice_sc_obj.gif" alt="Choice Object">
-				- Select the <strong>Choice</strong> <em>Compositor</em> node, 
-				to activate the <strong>Compositor Details</strong> section. 
-			</li>		
-		</ul>
-
-		<p>
-			Attributes:
-		</p>
-
-		<ul>
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/att_req_obj.gif" alt="Required Atribute Object">
-				- Select the <em>Required Attribute</em> node, to activate the <strong>Attribute Details</strong> section. 
-			</li>		
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/att_impl_obj.gif" alt="Optional Atribute Object">
-				- Select the <em>Optional Attribute</em> node, to activate the <strong>Attribute Details</strong> section. 
-			</li>		
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/att_class_obj.gif" alt="Attribute Class Object">
-				- Select the <em>Class Attribute</em> node, to activate the <strong>Attribute Details</strong> section. 
-			</li>
-			<li>
-				<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/att_file_obj.gif" alt="Attribute Resource Object">
-				- Select the <em>Resource Attribute</em> node, to activate the <strong>Attribute Details</strong> section. 
-			</li>
-		</ul>
-
-		<p>
-			Example: The <strong>extension</strong> <em>element</em> specifies that a sequence 
-			of one or more <strong>shortcut</strong> <em>elements</em> are allowed as it's legal children.
-			An <em>element reference</em> is used to represent the <strong>shortcut</strong> <em>element</em>.
-			A <strong>Sequence</strong> <em>compositor</em> is used to represent a sequence of <em>elements</em>.
-		</p>
-
-		<p>
-			<img src="../../../images/schema_editor/section_extension-point-elements_2.png" alt="Extension Point Elements Section 2">
-		</p>
-
-		<p>
-			Example:  The <strong>shortcut</strong> <em>element</em> specifies that either a
-			<strong>description</strong> or <strong>category</strong> element is allowed as it's legal
-			child.
-			<em>Element references</em> are used to represent the <strong>description</strong> 
-			and <strong>category</strong> <em>elements</em>.
-			A <strong>Choice</strong> <em>compositor</em> is used to represent a choice of <em>elements</em>.
-			
-		</p>
-
-		<p>
-			<img src="../../../images/schema_editor/section_extension-point-elements_1.png" alt="Extension Point Elements Section 1">
-		</p>
-
-		<h3>Extension Point Elements Section Actions</h3>
-		
-		<p>
-			Click the <strong>Add Element</strong> button to add a new global element declaration 
-			to the extension point schema grammar. 
-			This action is available when any node is selected. 
-			Note:  Element declaration order is not important
-		</p>
-
-		<p>
-			Click the <strong>Add Attribute</strong> button to add a new local attribute
-			declaration to a selected element in the extension point schema grammar.
-			This action is available for all selected <em>element</em> nodes 
-			except for the <strong>extension</strong> <em>element</em> node.
-			The <strong>extension</strong> <em>element</em> node always has 
-			the same attributes:  <strong>id</strong>, <strong>name</strong>, <strong>point</strong>.
-			Note:  Attribute declaration order is not important.
-		</p>
-
-		<p>
-			To delete a schema object from the extension point schema grammar, 
-			right-click on a selected node and select <strong>Delete</strong>.
-			This action is available for all selected nodes except for 
-			the <strong>extension</strong> <em>element</em> node.
-			For non-shared schemas, the <strong>extension</strong> 
-			<em>element</em> node is the special root element used 
-			to define the entry point to the edited schema's grammar.
-			Any extension 
-			defined in the <strong>Plug-in Manifest Editor</strong> must use an
-			<strong>extension</strong> parent element to specify it's XML 
-			related mark-up.
-		</p>
-
-		<p>
-			To specify that an element's children is composed of a sequence or choice of other elements 
-			in the extension point schema grammar, do the following:
-		</p>
-
-		<ol>
-			<li>
-				Select and right-click the <em>element</em> node you wish to designate
-				as the parent element.
-			</li>
-			<li>
-				Select <strong>New &gt; Compositor &gt; Sequence</strong> to define a sequence of elements.
-				Select <strong>New &gt; Compositor &gt; Choice</strong> to define a choice of elements.
-			</li>
-			<li>
-				Select and right-click the new <em>compositor</em> node.
-			</li>
-			<li>
-				Select the element from the <strong>New &gt; Reference</strong>
-				sub-menu that you wish to designate as a child of the parent element.
-				The <strong>Reference</strong> sub-menu is populated with all
-				the elements declared globally in the extension point schema grammar.
-			</li>
-			<li>
-				Repeat steps (3) and (4) to specify additional child elements.
-				If a <strong>Sequence</strong> compositor was specified, this amounts to 
-				specifying additional elements in the sequence.
-				If a <strong>Choice</strong> compositor was specified, this amounts to 
-				specifying additional element choices.
-			</li>
-		</ol>
-
-		<p>
-			Note:  To specify that an element is the child of another element, an intermediate 
-			<strong>Sequence</strong> or <strong>Choice</strong> compositor must always be used
-			by the parent element.  The <em>compositor</em> nodes are connector nodes; whereas,
-			the <em>element reference</em> nodes are leaf nodes.  Therefore, 
-			<em>compositor</em> nodes should always specify at least one child <em>element reference</em> 
-			node.
-		</p>
-
-		<p>
-			Note:  <strong>Sequence</strong> and <strong>Choice</strong> compositors 
-			may be nested any number of times to create more complex grammars.
-		</p>
-
-		<p>
-			Note:  A grammar must not contain self-referent cycles.
-			The most basic form of a prohibited cycle occurs when <em>Element A</em> requires 
-			<em>Element B</em> as a child and <em>Element B</em> requires <em>Element A</em> as a child.
-		</p>
-
-		<p>
-			To specify that an element has no children and allows text to be
-			specified within it's start and end XML tags (character content), 
-			simply leave the element's structure as is by 
-			not adding attributes, compositors and element references to it (element content).
-			Note:  An element cannot specify mixed content
-			(both character content and element content).
-		</p>
-
-		<a name="description"></a>
-		<h3>Description Section</h3>
-
-		<p>
-			This section allows you to provide a brief description for any element, 
-			attribute or compositor within the edited schema's grammar.
-		</p>
-
-		<p>
-			This section is directly accessible through the <strong>Schema Definition</strong> form page.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_description.png" alt="Description Section">
-		</p>
-
-
-		<h3>Description Section Fields</h3>
-		
-		<p>
-			Edit the description text field to provide a brief description for 
-			the current <em>element</em>, <em>attribute</em> or <em>compositor</em> 
-			node selected in the <strong>Extension Point Elements</strong> section.
-			Valid HTML mark-up may be used within this field as needed.
-		</p>
-
-		<p>
-			Note:  Updating an element reference description also updates the description 
-			of the global element declaration it refers to and vice versa.
-		</p>
-
-		<a name="element"></a>
-		<h3>Element Details Section</h3>
-
-		<p>
-			This section allows you to edit the properties of an element.
-			There are two kinds of elements: extension element, non-extension element. 
-			An extension element is the special root element declaration used 
-			to define the entry point to the edited schema's grammar.
-			A non-extension element is a global element declaration used as a basic
-			structural building block within the edited schema's grammar.
-		</p>
-
-		<p>
-			This section is activated by selecting either a <strong>extension</strong> 
-			<em>element</em> node or non-extension <em>element</em> node in the 
-			<strong>Extension Point Elements</strong> section.
-		</p>
-		
-		<p>
-			The <strong>Element Details</strong> section for an <strong>extension</strong> 
-			element.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_element-details_1.png" alt="Element Details Section 1">
-		</p>		
-
-		<p>
-			The <strong>Element Details</strong> section for a non-extension element.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_element-details_2.png" alt="Element Details Section 2">
-		</p>
-
-		<h3>Element Details Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Name</strong> field to specify the element name.
-		</p>
-		
-		<p>
-			Click either the <strong>true</strong> button or <strong>false</strong> button
-			within the <strong>Internal</strong> field to indicate whether the element
-			is internal or not.  The <strong>Plug-in Manifest Editor</strong> will flag
-			any extension XML mark-up that is internal with a warning (by default).
-			This field is analogous to <em>x-internal</em> attribute on exported packages.
-		</p>
-
-		<p>
-			Click either the <strong>true</strong> button or <strong>false</strong> button
-			within the <strong>Deprecated</strong> field to indicate whether the element
-			is deprecated or not.  The <strong>Plug-in Manifest Editor</strong> will flag
-			any extension XML mark-up that is deprecated with a warning (by default).
-			This field is analogous to Java's <em>Javadoc</em> <em>@deprecated</em> tag.
-		</p>
-
-		<p>
-			If an extension element is marked as deprecated, edit the 
-			<strong>Replacement</strong> field to specify the non-deprecated
-			extension point the user should use in it's place to achieve
-			the same functionality.
-		</p>
-
-		<p>
-			Select one of the element's defined attributes from the 
-			<strong>Label Property</strong> field to specify the attribute value to
-			use as the element's label in the <strong>Plug-in Manifest Editor</strong>.
-			For instance, if a value is selected, the element's node label in the 
-			<strong>All Extensions</strong> section of the 
-			<strong>Extensions</strong> page in the <strong>Plug-in Manifest Editor</strong> will
-			be as follows:  <em>selected-attribute-value</em> (<em>element-name</em>).
-			Otherwise, if no value is selected, the element's node label will be as follows: 
-			(<em>element-name</em>).
-		</p>
-
-		<p>
-			Select one of the element's defined resource type attributes 
-			from the <strong>Icon</strong> field to specify the 
-			icon resource to use to represent the element's node in the 
-			<strong>Plug-in Manifest Editor</strong>.  
-			In order for the element's node icon to show up correctly in the 
-			<strong>All Extensions</strong> section of the 
-			<strong>Extensions</strong> page in the 
-			<strong>Plug-in Manifest Editor</strong>, the following conditions
-			must be met:
-		</p>
-		
-		<ul>
-			<li>
-				The element must define a resource type attribute.
-			</li>
-			<li>
-				That attribute must be selected as the value of this field.
-			</li>			
-			<li>
-				The contributed XML mark-up supplying the attribute value 
-				must point to a valid icon resource file.
-			</li>
-		</ul>
-
-		<p>
-			Click either the <strong>true</strong> button or <strong>false</strong> button
-			within the <strong>Translatable</strong> field to indicate whether the element's
-			character content is translatable or not.  This field is only applicable for
-			elements that have no specified children (element content) or attributes and 
-			allow text to be specified within it's start and end XML tags (character content).
-			If an element's character content is marked as translatable, then PDE tools 
-			can be used on contributed extension XML mark-up to externalize the content 
-			into a properties file for multi-language support.
-		</p>
-
-		<p>
-			Use the read-only <strong>DTD approximation</strong> field to view 
-			an approximate one-to-one mapping of the element schema grammar to the equivalent 
-			element DTD grammar.  A DTD (Document Type Definition) is
-			an easier to read, less-powerful alternative to XML Schema for 
-			specifying an XML document's formal grammar.
-			The following notation is used to specify the DTD approximation:
-		</p>
-
-		<ul>
-			<li>
-				<em>element-name</em> - Represents an element in the defined grammar.
-			</li>
-			<li>
-				<strong>EMPTY</strong> - Indicates that no element content or character 
-				content is allowed (only attribute declarations).
-			</li>
-			<li>
-				<strong>#PCDATA</strong> - Indicates that only character content is 
-				allowed (Parsed Character Data).
-			</li>		
-					
-			<li>
-				<strong>()</strong> - Used to group an element's defined sequence and choice compositors.
-			</li>	
-			<li>
-				<strong>|</strong> - Used to delimit element choices.  Represents a logical <em>or</em> disjunction.
-			</li>	
-			<li>
-				<strong>,</strong> - Used to delimit element sequences.  Represents a logical <em>and</em> conjunction.
-			</li>
-			<li>
-				<strong>+</strong> - A qualifier used to indicate one or more instances are allowed.
-			</li>	
-			<li>
-				<strong>*</strong> - A qualifier used to indicate zero or more instances are allowed.
-			</li>																
-		</ul>
-
-		<a name="compositor"></a>
-		<h3>Compositor Details Section</h3>
-
-		<p>
-			This section allows you to edit the properties of a compositor.
-			There are two types of compositors: sequence compositor, choice compositor. 
-			A sequence compositor allows you specify that an element's children is composed of a 
-			sequence of other elements in the edited schema's grammar.
-			A choice compositor allows you specify a that an element's children is composed of a 
-			choice of other elements in the edited schema's grammar.			
-		</p>
-
-		<p>
-			This section is activated by selecting either a <strong>Sequence</strong> or
-			<strong>Choice</strong> node in the <strong>Extension Point Elements</strong> section.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_compositor-details.png" alt="Compositor Details Section">
-		</p>
-
-		<h3>Compositor Details Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Min Occurrences</strong> field to specify the minimum number
-			of occurrences this compositor of other elements and / or compositors is allowed 
-			to appear in the contributed extension XML mark-up.  This field's value is used
-			by PDE to validate multiplicity constraints within the 
-			<strong>Plug-in Manifest Editor</strong>.
-			If <em>Element A</em> requires exactly one <em>Element B</em> or <em>Element C</em> as it's child and it uses
-			a <strong>Choice</strong> compositor specifying 2 minimum occurrences, then any 
-			2 instances of <em>Element B</em> in combination with <em>Element C</em> must be defined in the contributed
-			extension XML mark-up in order to be valid.
-		</p>
-
-		<p>
-			Edit the <strong>Max Occurrences</strong> field to specify the maximum number
-			of occurrences this compositor of other elements and / or compositors is allowed 
-			to appear in the contributed extension XML mark-up.  This field's value is used
-			by PDE to validate multiplicity constraints within the 
-			<strong>Plug-in Manifest Editor</strong>.
-			If <em>Element A</em> requires exactly one <em>Element B</em> or <em>Element C</em> as it's child and it uses
-			a <strong>Choice</strong> compositor specifying 2 maximum occurrences, then no more than 
-			2 instances of <em>Element B</em> in combination with <em>Element C</em> can be defined in the contributed
-			extension XML mark-up to remain valid.
-		</p>
-
-		<p>
-			Check the <strong>Unbounded</strong> field to specify that 
-			there is no constraint on the maximum number of allowed occurrences this 
-			compositor may appear within the contributed extension XML mark-up.
-		</p>
-		
-		<p>
-			Select a value from the <strong>Type</strong> field to specify whether this compositor is a 
-			<strong>sequence</strong> or <strong>choice</strong>. 
-		</p>
-
-		<p>
-			Use the read-only <strong>DTD approximation</strong> field to view 
-			an approximate one-to-one mapping of the compositor schema grammar to the equivalent 
-			compositor DTD grammar.  The notation used to specify the DTD approximation
-			is described under the <strong>Element Details Section Fields</strong> heading in 
-			this document.
-		</p>
-
-		<a name="reference"></a>
-		<h3>Element Reference Details Section</h3>
-
-		<p>
-			This section allows you to edit the properties of an element reference.
-			An element reference is a reference to a global element declaration within
-			the edited schema's grammar.  Element references are used by compositors 
-			as atomic building blocks to define the grammar for global element declarations.
-		</p>
-
-		<p>
-			This section is activated by selecting an <em>element reference</em>
-			node in the <strong>Extension Point Elements</strong> section.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_element-reference-details.png" alt="Element Reference Details Section">
-		</p>
-
-		<h3>Element Reference Details Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Min Occurrences</strong> field to specify the minimum number
-			of occurrences this element is allowed 
-			to appear in the contributed extension XML mark-up.  This field's value is used
-			by PDE to validate multiplicity constraints within the 
-			<strong>Plug-in Manifest Editor</strong>.
-			If <em>Element A</em> specifies 2 minimum occurrences, then 
-			2 instances of <em>Element A</em> must be defined in the contributed
-			extension XML mark-up in order to be valid.
-		</p>
-
-		<p>
-			Edit the <strong>Max Occurrences</strong> field to specify the maximum number
-			of occurrences this element is allowed 
-			to appear in the contributed extension XML mark-up.  This field's value is used
-			by PDE to validate multiplicity constraints within the 
-			<strong>Plug-in Manifest Editor</strong>.
-			If <em>Element A</em> specifies 2 maximum occurrences, then no more than 
-			2 instances of <em>Element A</em> can be defined in the contributed
-			extension XML mark-up to remain valid.
-		</p>
-
-		<p>
-			Check the <strong>Unbounded</strong> field to specify that 
-			there is no constraint on the maximum number of allowed occurrences this 
-			element may appear within the contributed extension XML mark-up.
-		</p>
-
-		<p>
-			Use the read-only <strong>DTD approximation</strong> field to view 
-			an approximate one-to-one mapping of the element schema grammar to the equivalent 
-			element DTD grammar.  The notation used to specify the DTD approximation
-			is described under the <strong>Element Details Section Fields</strong> heading in 
-			this document.
-		</p>
-
-		<h3>Element Reference Details Section Actions</h3>
-		
-		<p>
-			Click the <em>element-name</em> hyperlink within the <strong>Reference</strong>
-			field to edit the properties of the global element declaration this local element
-			reference refers to.  When this action is complete, the referenced 
-			<em>element</em> node is selected in the 
-			<strong>Extension Point Elements</strong> section and the corresponding 
-			<strong>Element Details</strong> section is activated.
-		</p>
-
-		<a name="attribute"></a>
-		<h3>Attribute Details Section</h3>
-
-		<p>
-			This section allows you to edit the properties of an attribute.
-			Attributes are used to provide additional information about elements.
-		</p>
-
-		<p>
-			This section is activated by selecting either a <em>required attribute</em>,
-			<em>optional attribute</em>, <em>class attribute</em> or 
-			<em>resource attribute</em> node 
-			in the <strong>Extension Point Elements</strong> section.
-		</p>
-		
-		<p>
-			The <strong>Attribute Details</strong> section for a required attribute of 
-			type <strong>string</strong> that specifies an enumeration restriction.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_attribute-details_1.png" alt="Attribute Details Section 1">
-		</p>
-
-		<p>
-			The <strong>Attribute Details</strong> section for an optional attribute of 
-			type <strong>boolean</strong> that specifies a default value.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_attribute-details_2.png" alt="Attribute Details Section 2">
-		</p>
-
-		<p>
-			The <strong>Attribute Details</strong> section for a class attribute 
-			that indicates that the class represented by the attribute value 
-			must extend the specified class and / or implement the specified interface.		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_attribute-details_3.png" alt="Attribute Details Section 3">
-		</p>
-
-		<p>
-			The <strong>Attribute Details</strong> section for a resource attribute.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_attribute-details_4.png" alt="Attribute Details Section 4">
-		</p>
-
-
-		<h3>Attribute Details Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Name</strong> field to specify the attribute name.
-		</p>
-
-		<p>
-			Click either the <strong>true</strong> button or <strong>false</strong> button
-			within the <strong>Deprecated</strong> field to indicate whether the attribute
-			is deprecated or not.  The <strong>Plug-in Manifest Editor</strong> will flag
-			any extension XML mark-up that is deprecated with a warning (by default).
-			This field is analogous to Java's <em>Javadoc</em> <em>@deprecated</em> tag.
-		</p>
-
-		<p>
-			Select a value from the <strong>Use</strong> field to indicate whether the 
-			attribute must be specified on it's defining element within contributed 
-			extension XML mark-up.
-			The following selections are available:
-		</p>
-
-		<ul>
-			<li>
-				<strong>optional</strong> - The attribute may be optionally specified on it's defining element.
-			</li>
-			<li>
-				<strong>required</strong> - The attribute must be specified on it's defining element.
-			</li>
-			<li>
-				<strong>default</strong> - The attribute may be optionally specified on it's defining element.
-				If the attribute is not specified, then it's value will assume the defined default value.
-			</li>			
-		</ul>
-
-		<p>
-			Edit the <strong>Default Value</strong> field to specify the default value 
-			to use for an attribute when it is not specified on it's defining element within contributed 
-			extension XML mark-up.  This field is only applicable when 
-			the <strong>default</strong> value from the <strong>Use</strong> field is selected.
-		</p>
-
-		<p>
-			Select a value from the <strong>Type</strong> field to specify the attribute value type.
-			The following selections are available:
-		</p>
-
-		<ul>
-			<li>
-				<strong>string</strong> - The attribute value can be any valid string.
-			</li>
-			<li>
-				<strong>boolean</strong> - The attribute value can be either <strong>true</strong>
-				or <strong>false</strong> (case insensitive).
-			</li>
-			<li>
-				<strong>java</strong> -  The attribute value can be any fully-qualified class name 
-				on the target platform's classpath (e.g. java.lang.String).
-			</li>
-			<li>
-				<strong>resource</strong> - The attribute value can be any project relative path to an
-				existing file or folder resource.
-			</li>
-		</ul>
-
-		<p>
-			Click either the <strong>true</strong> button or <strong>false</strong> button
-			within the <strong>Translatable</strong> field to indicate whether the attributes's
-			value is translatable or not.  This field is only applicable when
-			the <strong>string</strong> value from the <strong>Type</strong> field is selected.
-			If an attribute's value is marked as translatable, then PDE tools 
-			can be used on contributed extension XML mark-up to externalize these values 
-			into a properties file for multi-language support.
-		</p>
-
-		<p>
-			Use the <strong>Restrictions</strong> field to view 
-			a list of string values the attribute is restricted to using
-			as it's own value.  If the field contains no values, then there
-			are no restrictions on the attribute value.
-			This field is only applicable when
-			the <strong>string</strong> value from the <strong>Type</strong> field is selected.			
-			Note:  An enumeration restriction on the string base type is used in
-			the edited schema's grammar to accomplish this functionality.
-		</p>
-
-		<p>
-			Edit the <strong>Extends</strong> field to specify a fully-qualified class name 
-			on the target platform's classpath (e.g. org.eclipse.ui.part.EditorPart) that must 
-			be sub-classed by the class specified as the attribute value.  PDE will validate the 
-			class attribute value in the contributed extension XML mark-up to ensure it 
-			extends the super-class.
-			This field is only applicable when
-			the <strong>java</strong> value from the <strong>Type</strong> field is selected.					
-		</p>
-
-		<p>
-			Edit the <strong>Implements</strong> field to specify a fully-qualified interface name 
-			on the target platform's classpath (e.g. org.eclipse.ui.IEditorPart) that must be 
-			implemented by the class specified as the attribute value.  PDE will validate the 
-			class attribute value in the contributed extension XML mark-up to ensure it 
-			implements the interface.
-			This field is only applicable when
-			the <strong>java</strong> value from the <strong>Type</strong> field is selected.					
-		</p>
-
-		<h3>Attribute Details Section Actions</h3>
-		
-		<p>
-			Click the <strong>Add...</strong> button in the <strong>Restrictions</strong>
-			field to open the <strong>New Restriction</strong> dialog in order to add a 
-			new restriction to the attribute value.  Once the dialog is completed, the 
-			new restriction is added to the list of string values the 
-			attribute is restricted to using as it's own value.
-			This action is only available when
-			the <strong>string</strong> value from the <strong>Type</strong> field is selected.	
-		</p>
-
-		<p>
-			Select a string value within the <strong>Restrictions</strong>
-			field and click the <strong>Remove</strong> button 
-			to remove a restriction from the list of string values the 
-			attribute is restricted to using as it's own value.
-			This action is only available when
-			the <strong>string</strong> value from the <strong>Type</strong> field is selected.	
-		</p>
-
-		<p>
-			If the value specified in the <strong>Extends</strong> field refers to
-			a fully-qualified class name on the target platform's classpath, then
-			clicking on the <strong>Extends</strong> hyperlink will open that class in
-			a new Java source editor.  Otherwise, clicking on the <strong>Extends</strong> 
-			hyperlink will open the <strong>New Java Class</strong> wizard allowing you
-			to create the new class.
-			This action is only available when
-			the <strong>java</strong> value from the <strong>Type</strong> field is selected.				
-		</p>
-
-		<p>
-			If the value specified in the <strong>Implements</strong> field refers to
-			a fully-qualified interface name on the target platform's classpath, then
-			clicking on the <strong>Implements</strong> hyperlink will open that interface in
-			a new Java source editor.  Otherwise, clicking on the <strong>Implements</strong> 
-			hyperlink will open the <strong>New Java Class</strong> wizard allowing you
-			to create the new interface.
-			This action is only available when
-			the <strong>java</strong> value from the <strong>Type</strong> field is selected.				
-		</p>
-
-		<p>
-			Click the <strong>Browse...</strong> button to open the 
-			<strong>Select Type</strong> dialog in order to select an existing class on the
-			target platform's classpath to use as the value for the 
-			<strong>Extends</strong> field.
-			This action is only available when
-			the <strong>java</strong> value from the <strong>Type</strong> field is selected.				
-		</p>
-
-		<p>
-			Click the <strong>Browse...</strong> button to open the 
-			<strong>Select Type</strong> dialog in order to select an existing interface on the
-			target platform's classpath to use as the value for the 
-			<strong>Implements</strong> field.
-			This action is only available when
-			the <strong>java</strong> value from the <strong>Type</strong> field is selected.				
-		</p>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="editor.htm">Extension Point Schema Editor</a>
-			</li>		
-			<li>
-				<a href="../../file_wizards/new_schema.htm">New Extension Point Schema Wizard</a>
-			</li>			
-			<li>
-				<a href="../manifest_editor/editor.htm">Plug-in Manifest Editor</a>
-			</li>		
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_overview.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_overview.htm
deleted file mode 100644
index 8d9aca9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/schema_editor/page_schema_overview.htm
+++ /dev/null

@@ -1,232 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Schema Overview Page</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Schema Overview Page</h2>
-
-		<h3>About This Page</h3>
-		
-		<p>
-			This form page allows you to identify and document an extension point schema.
-			It also allows you to include and use grammars defined by other shared extension point schemas.
-		</p>
-		
-		<h3>Page Sections</h3>
-		
-		<p>
-			This page is comprised of the following sections:
-		</p>		
-		
-		<ul>
-			<li>
-				<a href="#information">General Information Section</a>
-			</li>
-			<li>
-				<a href="#inclusions">Schema Inclusions Section</a>
-			</li>
-			<li>
-				<a href="#documentation">Documentation Section</a>
-			</li>	
-		</ul>
-
-		<a name="information"></a>
-		<h3>General Information Section</h3>
-
-		<p>
-			This section uniquely identifies the edited extension point schema. 
-			The format of an extension point schema ID is the same as the
-			fully qualified ID of it's corresponding extension point:  
-			<em>&lt;plugin-id&gt;.&lt;point-id&gt;</em>
-		</p>
-
-		<p>
-			<img src="../../../images/schema_editor/section_general-information.png" alt="General Information Section">
-		</p>
-
-		<h3>General Information Section Fields</h3>
-
-		<p>
-			Edit the <strong>Plug-in ID</strong> field to specify the qualifier portion
-			of the unique extension point schema ID.  This field's value should match the
-			the ID of the plug-in that the schema's corresponding extension point is defined in.
-		</p>
-
-		<p>
-			Edit the <strong>Point ID</strong> field to specify the ID portion of the
-			unique extension point schema ID.  This field's value should match the
-			ID used to define the schema's corresponding extension point.
-		</p>
-		
-		<p>
-			Edit the <strong>Point Name</strong> field to specify a human-readable
-			name for the extension point schema.  This field's value should match
-			the name used to define the schema's corresponding extension point.
-		</p>		
-
-		<a name="inclusions"></a>
-		<h3>Schema Inclusions Section</h3>
-
-		<p>
-			This section allows you to include and use the grammar from other shared 
-			extension point schemas.
-		</p>
-		
-		<p>
-			<img src="../../../images/schema_editor/section_schema-inclusions.png" alt="Schema Inclusions Section">
-		</p>
-
-		<h3>Schema Inclusions Section Fields</h3>
-		
-		<p>
-			The viewer field lists the shared extension point schemas whose 
-			grammars are included and used by the edited extension point schema.
-		</p>
-
-		<p>
-			Shared extension point schemas located in the same plug-in as the
-			edited extension point schema may be included.
-			These schemas are represented in the viewer by a relative path to 
-			their file name:  
-			<em>&lt;relative-path&gt;/&lt;schema-file-name&gt;</em>
-		</p>
-
-		<p>
-			Shared extension point schemas located in the another workspace
-			plug-in may be included.
-			These schemas are represented in the viewer by a special
-			absolute path to their file name:  
-			<em>schema://&lt;defining-plugin-id&gt;/&lt;path&gt;/&lt;schema-file-name&gt;</em>
-		</p>
-
-		<h3>Schema Inclusions Section Actions</h3>
-		
-		<p>
-			Click the <strong>Add...</strong> button, to open the <strong>File Selection</strong>
-			dialog in order to include and use the grammar from an existing shared extension point 
-			schema in the edited schema.
-			The dialog presents a filtered hierarchical view of all workspace extension point 
-			schemas.  If an extension point schema contained in a different plug-in than the
-			edited schema is selected, a special absolute path will be constructed and entered
-			into the viewer field.  If an extension point schema contained in the same plug-in
-			as the edited schema is selected, a relative path from the edited schema to the
-			selected schema is computed and entered into the viewer field.
-		</p>
-
-		<p>
-			Click the <strong>Remove</strong> button, to remove the selected shared extension
-			point schema's grammar from inclusion and use by the edited extension point schema.
-			This action is available only when a schema is selected in the viewer field.
-		</p>
-
-		<p>
-			Double-click an extension point schema in the viewer field to open that schema
-			in a new <strong>Extension Point Schema Editor</strong>.
-		</p>
-
-		<a name="documentation"></a>
-		<h3>Documentation Section</h3>
-
-		<p>
-			This section allows you to document the edited extension point schema.
-			It's contents will be used to compose the edited extension point
-			schema's reference document.  As a result, valid HTML mark-up may be used 
-			in any of the section's fields.
-		</p>
-
-		<p>
-			This section contains the following tabs:
-		</p>
-
-		<ul>
-			<li>
-				Description
-			</li>
-			<li>
-				Since
-			</li>
-			<li>
-				Examples
-			</li>
-			<li>
-				API Information
-			</li>
-			<li>
-				Supplied Implementation
-			</li>
-			<li>
-				Copyright
-			</li>
-		</ul>
-
-		<p>
-			<img src="../../../images/schema_editor/section_documentation.png" alt="Documentation Section">
-		</p>
-
-		<h3>Documentation Section Fields</h3>
-		
-		<p>
-			Edit the <strong>Description</strong> tab's field to specify a detailed 
-			description of the defining extension point for this edited schema.  
-			Typically, this field is used to describe the extension point's
-			purpose, utility and associated concepts.
-		</p>
-
-		<p>
-			Edit the <strong>Since</strong> tab's field to specify the version of
-			Eclipse this edited schema was first added to.  For example,
-			if this edited schema was first added to Eclipse 3.0, 
-			the field's value should be <em>3.0</em>.
-			The assumption is that the edited schema's grammar is API that
-			persists release to release once introduced and is maintained for backwards
-			compatibility.  This field is analogous to Java's <em>Javadoc</em> 
-			<em>@since</em> tag.
-		</p>
-
-		<p>
-			Edit the <strong>Examples</strong> tab's field to specify 
-			a valid XML snippet of the extension that conforms to this edited 
-			schema's grammar.  Try to use an example that illustrates a typical 
-			use case of the extension.
-		</p>
-
-		<p>
-			Edit the <strong>API Information</strong> tab's field to describe
-			the structure, content and semantics of the extension point's elements and attributes. 
-		</p>
-
-		<p>
-			Edit the <strong>Supplied Implementation</strong> tab's field to 
-			specify whether the plug-in that defines the extension point for 
-			this edited schema also contributes extensions for it.  This field
-			points the user to an actual extension implementation that they can
-			use as a template or reference for defining their own extensions.
-		</p>
-
-		<p>
-			Edit the <strong>Copyright</strong> tab's field to outline the exclusive legal 
-			rights to reproduce, publish, sell, or distribute the edited schema.
-		</p>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="editor.htm">Extension Point Schema Editor</a>
-			</li>		
-			<li>
-				<a href="../manifest_editor/editor.htm">Plug-in Manifest Editor</a>
-			</li>		
-			<li>
-				<a href="../../file_wizards/new_schema.htm">New Extension Point Schema Wizard</a>
-			</li>			
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/dialog_command-composer.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/dialog_command-composer.htm
deleted file mode 100644
index c14d1d0..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/dialog_command-composer.htm
+++ /dev/null

@@ -1,86 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Command Composer Dialog</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Command Composer Dialog</h2>
-
-		<h3>About This Dialog</h3>
-		
-		<p>
-			This dialog allows you to browse, test and select new executable workbench 
-			commands to add to a step or sub-step.  The dialog also allows you to edit
-			applicable parameters for selected workbench commands. 
-		</p>
-		<p>
-			This dialog is accessible by clicking the <strong>Browse...</strong> button in the
-			<strong>Command</strong> section.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_command_details.png" alt="Command Definition Section">
-
-		<h3>Dialog Sections</h3>
-		
-		<p>
-			This dialog is comprised of the following sections:
-		</p>		
-		
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Section
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="section_commands.htm">Commands Section</a>
-				</td>
-				<td class="body">
-					This section allows you to browse and filter executable workbench 
-					commands by category.
-				</td>
-			</tr>			
-			<tr>
-				<td class="body">
-					<a href="section_command-details.htm">Command Details Section</a>
-				</td>
-				<td class="body">
-					This section allows you to do the following:
-
-					<ul>
-						<li>
-							Test an executable workbench command
-						</li>
-						<li>
-							Edit an executable workbench command's applicable parameters
-						</li>
-						<li>
-							Copy an executable workbench command's string representation to the clipboard.
-						</li>			
-					</ul>
-				</td>
-			</tr>
-		</table>		
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm">Commands</a>
-			</li>		
-			<li>
-				<a href="section_command.htm">Command Section</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/editor.htm
deleted file mode 100644
index 97b362e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/editor.htm
+++ /dev/null

@@ -1,129 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Simple Cheat Sheet Editor</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Simple Cheat Sheet Editor</h2>
-		
-		<h3>About Cheat Sheets</h3>
-		
-		<p>
-			In general, cheat sheets help guide users through a complex set of instructions. 
-		   	There are two types of cheat sheets: simple and composite. 
-			Simple cheat sheets are used to organize and present logical steps and sub-steps 
-			to achieve a certain task.
-		</p>
-
-		<p>
-			You can view and run cheat sheets using the <strong>Cheat Sheet View</strong>.
-			To open a cheat sheet in this view, click <strong>Help &gt; Cheat Sheets...</strong>
-		</p>
-		
-		<h3>About This Editor</h3>
-		
-		<p>
-			The <strong>Simple Cheat Sheet Editor</strong> allows you to compose simple
-			cheat sheets and preview them in the <strong>Cheat Sheet View</strong>.  
-			This editor also allows you to embed workbench commands and help document 
-			links in your cheat sheets.
-		</p>
-		
-		<h3>Editor Pages</h3>
-		
-		<p>
-			This editor is comprised of the following pages:
-		</p>
-		
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Page
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="page_cheat-sheet.htm">Simple Cheat Sheet Page</a>
-				</td>
-				<td class="body">
-					A form page that allows you to edit the structure, order and properties of cheat sheet elements
-				</td>
-			</tr>
-		</table>
-
-		<h3>Global Editor Actions</h3>
-		
-		<p>
-			This editor provides the following global actions:
-		</p>
-		
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Register this cheat sheet</strong>
-				</td>
-				<td class="body">
-					Hyperlink
-				</td>
-				<td class="body">
-					<a href="wizard_register-cheat-sheet.htm">Register Cheat Sheet Wizard</a>
-				</td>
-				<td class="body">
-					This wizard allows you to register a simple or composite cheat sheet 
-					with the Eclipse workbench to make it accessible through the 
-					<strong>Help</strong> menu.
-				</td>
-			</tr>
-		</table>
-		
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>Cheat sheet example:
-				<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.pde.rcpapp)")'>
-    				<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the plug-in cheat sheet"> Creating an Eclipse Plug-in
-				</a>
-			</li>		
-			<li>
-				Cheat sheet documentation: 
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm">Cheat Sheets</a>
-			</li>
-			<li>
-				<a href="../composite_cs_editor/editor.htm">Composite Cheat Sheet Editor</a>
-			</li>
-			<li>
-				<a href="../../file_wizards/new_cheat_sheet.htm">New Cheat Sheet Wizard</a>
-			</li>
-			<li>
-				<a href="http://www.eclipse.org/pde/pde-ui/articles/cheat_sheet_dev_workflow/index.html">
-				Recommended Work Flow for Cheat Sheet Development</a>
-			</li>
-			<li>
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm">Commands</a>
-			</li>			
-		</ul>
-		
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/page_cheat-sheet.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/page_cheat-sheet.htm
deleted file mode 100644
index dc161ec..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/page_cheat-sheet.htm
+++ /dev/null

@@ -1,329 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Simple Cheat Sheet Page</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Simple Cheat Sheet Page</h2>
-
-		<h3>About This Page</h3>
-		
-		<p>
-			This form page allows you to edit the structure, order and properties of cheat sheet elements.
-		</p>
-		<p>
-			The structure and order of cheat sheet elements are edited in 
-			the <strong>Content</strong> section.  
-			This section occupies the entire left-hand portion of the editor area. 
-		</p>
-		<p>
-			The properties of cheat sheet elements are edited in the <strong>Definition</strong> sections.
-			These sections are activated in the right-hand portion of the editor area depending
-			on the type of cheat sheet element selected in the <strong>Content</strong> section. 
-		</p>
-
-		<h3>Cheat Sheet Elements</h3>
-		
-		<p>
-			A simple cheat sheet is composed of the following elements:
-		</p>
-		
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Element
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Parent(s)
-				</td>
-				<td class="header">
-					Allowed Occurrences
-				</td>								
-			</tr>
-			<tr>
-				<td class="body">
-					Root
-				</td>
-				<td class="body">
-					The cheat sheet itself.
-				</td>
-				<td class="body">
-					None
-				</td>
-				<td class="body">
-					1
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					Title
-				</td>
-				<td class="body">
-					The title of the task being solved by the cheat sheet.
-				</td>
-				<td class="body">
-					Root
-				</td>
-				<td class="body">
-					1
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					Introduction
-				</td>
-				<td class="body">
-					The introduction of the task being solved by the cheat sheet.
-				</td>
-				<td class="body">
-					Root
-				</td>
-				<td class="body">
-					1
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					Step
-				</td>
-				<td class="body">
-					A step in the task being solved by the cheat sheet.
-				</td>
-				<td class="body">
-					Root
-				</td>
-				<td class="body">
-					1 or more
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					Sub-Step
-				</td>
-				<td class="body">
-					A sub-step of a step in the task being solved by the cheat sheet.
-				</td>
-				<td class="body">
-					Step
-				</td>
-				<td class="body">
-					0 or more
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					Command
-				</td>
-				<td class="body">
-					An executable workbench command that automates the work required by a step or sub-step.
-				</td>
-				<td class="body">
-					Step,
-					<br>
-					Sub-Step
-				</td>
-				<td class="body">
-					0 or 1
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					Help Document Link
-				</td>
-				<td class="body">
-					An associated help link added to a step or introduction.
-				</td>
-				<td class="body">
-					Step,
-					<br>
-					Introduction
-				</td>
-				<td class="body">
-					0 or 1
-				</td>				
-			</tr>			
-			<tr>
-				<td class="body">
-					Help Context ID
-				</td>
-				<td class="body">
-					An associated help link added to a step or introduction.
-				</td>
-				<td class="body">
-					Step,
-					<br>
-					Introduction
-				</td>
-				<td class="body">
-					0 or 1
-				</td>				
-			</tr>																
-		</table>			
-		
-		<h3>Page Sections</h3>
-		
-		<p>
-			This page is comprised of the following sections:
-		</p>		
-		
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Section
-				</td>
-				<td class="header">
-					Associated Element(s)
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="section_content.htm">Content Section</a>
-				</td>
-				<td class="body">
-					Title,
-					<br>
-					Introduction,
-					<br>
-					Step,
-					<br>
-					Sub-Step
-				</td>
-				<td class="body">
-					This section allows you to do the following:
-					<ul>
-						<li>
-							Visualize the structure and order of the cheat sheet's 
-							title, introduction, steps and sub-steps
-							as they appear in the <strong>Cheat Sheet</strong> view.
-						</li>
-						<li>
-							Edit the structure and order of the cheat sheet's steps and sub-steps.
-						</li>
-						<li>
-							Activate the corresponding <strong>Definition</strong> section used to edit the 
-							properties of a selected title, introduction, step or sub-step.
-						</li>
-						<li>
-							Preview and test the edited cheat sheet within the 
-							<strong>Cheat Sheet</strong> view.
-						</li>
-					</ul>
-				</td>
-			</tr>			
-			<tr>
-				<td class="body">
-					<a href="section_title.htm">Title Section</a>
-				</td>
-				<td class="body">
-					Title
-				</td>
-				<td class="body">
-					This <strong>Definition</strong> section allows you to edit the title of the cheat sheet.
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="section_introduction.htm">Introduction Section</a>
-				</td>
-				<td class="body">
-					Introduction
-				</td>
-				<td class="body">
-					This <strong>Definition</strong> section allows you to edit the introduction of the cheat sheet.
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="section_step.htm">Step Section</a>
-				</td>
-				<td class="body">
-					Step
-				</td>
-				<td class="body">
-					This <strong>Definition</strong> section allows you to edit the properties of a step.
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="section_sub-step.htm">Sub-Step Section</a>
-				</td>
-				<td class="body">
-					Sub-Step
-				</td>
-				<td class="body">
-					This <strong>Definition</strong> section allows you to edit the properties of a sub-step. 
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="section_command.htm">Command Section</a>
-				</td>
-				<td class="body">
-					Command
-				</td>
-				<td class="body">
-					This section allows you to do the following:
-
-					<ul>
-						<li>
-							Add an executable workbench command to a step or sub-step
-						</li>
-						<li>
-							Remove an executable workbench command from a step or sub-step
-						</li>
-						<li>
-							Edit the properties of an executable workbench command added to a step or sub-step
-						</li>			
-					</ul>
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<a href="section_help.htm">Help Section</a>
-				</td>
-				<td class="body">
-					Help Document Link,
-					<br>
-					Help Context ID
-				</td>
-				<td class="body">
-					This collapsible section allows you to do the following:
-
-					<ul>
-						<li>
-							Add a help link to a step or introduction using either a help document link 
-							or help context ID as input.
-						</li>
-						<li>
-							Remove a help link from a step or introduction.
-						</li>
-						<li>
-							Edit the help document link or help context 
-							ID used as input to add a help link to a step or introduction.
-						</li>
-					</ul>
-				</td>
-			</tr>															
-		</table>		
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="editor.htm">Simple Cheat Sheet Editor</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command-details.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command-details.htm
deleted file mode 100644
index b6d9da2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command-details.htm
+++ /dev/null

@@ -1,193 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Command Details Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Command Details Section</h2>
-		
-		<h3>About This Section</h3>
-		
-		<p>
-			This section allows you to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Test an executable workbench command
-			</li>
-			<li>
-				Edit an executable workbench command's applicable parameters
-			</li>
-			<li>
-				Copy an executable workbench command's string representation to the clipboard.
-			</li>			
-		</ul>		
-
-		<p>
-			This section is activated by selecting a command node in the <strong>Commands</strong> section.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/dialog_composer_master.png" alt="Command Composer Content Section">
-		
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Command ID</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Workbench Command ID
-				</td>
-				<td class="body">
-					This non-editable field shows the workbench command ID.					
-				</td>
-				<td class="body">
-					N/A
-				</td>				
-			</tr>	
-			<tr>
-				<td class="body">
-					Command Parameter (0 or more)
-				</td>
-				<td class="body">
-					Text or Combo Box
-				</td>
-				<td class="body">
-					Command Parameter
-				</td>
-				<td class="body">
-					A workbench command may have 0 or more configurable parameters.
-					One input field is generated for each command parameter.
-					<br>
-					<br>
-					Enter applicable values into these fields to modify 
-					the behavior of the workbench command accordingly.					
-				</td>
-				<td class="body">
-					N/A
-				</td>				
-			</tr>	
-		</table>
-			
-		<p>
-			An executable workbench command with parameters:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/dialog_composer_details_1.png" alt="Command Composer Details Section 1">
-
-		<p>
-			An executable workbench command without parameters:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/dialog_composer_details_3.png" alt="Command Composer Details Section 2">
-		
-		<h3>Section Actions</h3>
-
-		<p>
-			This section provides the following actions:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Execute</strong>
-				</td>
-				<td class="body">
-					Hyperlink
-				</td>
-				<td class="body">
-					Execute Workbench Command
-				</td>
-				<td class="body">
-					Click this link to execute the workbench command from within the
-					<strong>Command Composer Dialog</strong>.	
-					<br>			
-					<br>			
-					Note:  This action is not available for workbench commands that
-					cannot be executed from within a dialog.
-				</td>
-			</tr>	
-			<tr>
-				<td class="body">
-					<strong>Copy To Clipboard</strong>
-				</td>
-				<td class="body">
-					Hyperlink
-				</td>
-				<td class="body">
-					Copy Command String To Clipboard
-				</td>
-				<td class="body">
-					Click this link to copy an executable workbench command's 
-					string representation to the clipboard.
-					<br>			
-					<br>
-					The string representation can be used to directly embed workbench
-					commands into simple cheat sheets and user assistance documentation.							
-				</td>
-			</tr>									
-		</table>
-		
-		<img src="../../../images/simple_cs_editor/dialog_composer_details_2.png" alt="Command Composer Details Section 2">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm">Commands</a>
-			</li>		
-			<li>
-				<a href="dialog_command-composer.htm">Command Composer Dialog</a>
-			</li>
-			<li>
-				<a href="section_commands.htm">Commands Section</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command.htm
deleted file mode 100644
index 6c5f8cb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_command.htm
+++ /dev/null

@@ -1,199 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Command Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Command Section</h2>
-		
-		<h3>About This Section</h3>
-		
-		<p>
-			This section allows you to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Add an executable workbench command to a step or sub-step
-			</li>
-			<li>
-				Remove an executable workbench command from a step or sub-step
-			</li>
-			<li>
-				Edit the properties of an executable workbench command added to a step or sub-step
-			</li>			
-		</ul>
-
-		<p>
-			This section is accessible by selecting a step or sub-step node in the <strong>Content</strong> section.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_step_master_1.png" alt="Step Content Section">
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Command</strong>
-				</td>
-				<td class="body">
-					Combo Box
-				</td>
-				<td class="body">
-					Workbench Command
-				</td>
-				<td class="body">
-					Select a recently added workbench command from this field to add a command to a step or sub-step.
-					Select <strong>&lt;none&gt;</strong> to remove a command from a step or sub-step.
-					<br>
-					<br>
-					Note: A command cannot be added to a step that contains sub-steps.
-					<br>
-					<br>
-					This field is globally populated and synchronized with all commands recently added 
-					to all steps and sub-steps.
-					<br>
-					<br>
-					Use the <strong>Browse...</strong> button to select new workbench commands.					
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>Parameters</strong>
-				</td>
-				<td class="body">
-					Table
-				</td>
-				<td class="body">
-					Workbench Command Parameters
-				</td>
-				<td class="body">
-					This non-editable field shows the applicable parameters for a workbench 
-					command selected in the <strong>Command</strong> combo box.
-					<br>
-					<br>
-					Each row represents one command parameter or key-value pair.  The first 
-					column lists command parameter keys and the second column lists command
-					parameter values.	
-					<br>
-					<br>
-					To edit the parameters of a selected workbench commands, click the 	
-					<strong>Browse...</strong> button.  							
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>									
-		</table>
-		
-		<img src="../../../images/simple_cs_editor/section_command_details.png" alt="Command Definition Section">
-
-		<h3>Section Actions</h3>
-
-		<p>
-			This section provides the following actions:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Browse...</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Browse Workbench Commands
-				</td>
-				<td class="body">
-					Click this button to launch the
-					<a href="dialog_command-composer.htm">Command Composer Dialog</a>.
-					<br>
-					<br>
-					This dialog allows you to browse, test and select new executable workbench 
-					commands to add to a step or sub-step.  The dialog also allows you to edit
-					applicable parameters for selected workbench commands.  					
-				</td>
-			</tr>	
-		</table>
-			
-		<h3>Representation</h3>
-
-		<p>
-			A step with a command is represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_step_view_2.png" alt="Step Cheat Sheet View">
-
-		<p>
-			A sub-step with a command is represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_step_view_1.png" alt="Step Cheat Sheet View">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm">Commands</a>
-			</li>
-			<li>
-				<a href="dialog_command-composer.htm">Command Composer Dialog</a>
-			</li>
-			<li>
-				<a href="section_content.htm">Content Section</a>
-			</li>
-			<li>
-				<a href="section_step.htm">Step Section</a>
-			</li>
-			<li>
-				<a href="section_sub-step.htm">Sub-Step Section</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_commands.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_commands.htm
deleted file mode 100644
index 352a7ef..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_commands.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Command Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Command Section</h2>
-		
-		<h3>About This Section</h3>
-		
-		<p>
-			This section allows you to browse and filter executable workbench 
-			commands by category.  It is accessible through the <strong>Command Composer Dialog</strong>.
-		</p>
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					None
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Workbench Command Filter Field
-				</td>
-				<td class="body">
-					Type a partial string in this field to filter the <strong>Workbench Command Viewer</strong> 
-					categories and commands by matching occurrences of that string in their names.			
-				</td>
-				<td class="body">
-					N/A
-				</td>				
-			</tr>		
-			<tr>
-				<td class="body">
-					None
-				</td>
-				<td class="body">
-					Tree Viewer
-				</td>
-				<td class="body">
-					Workbench Command Viewer
-				</td>
-				<td class="body">
-					Browse this field to select executable workbench commands.	
-					All root nodes represent categories and all child nodes represent workbench commands.
-				</td>
-				<td class="body">
-					N/A
-				</td>				
-			</tr>					
-		</table>
-
-		<img src="../../../images/simple_cs_editor/dialog_composer_master.png" alt="Command Composer Content Section">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm">Commands</a>
-			</li>		
-			<li>
-				<a href="dialog_command-composer.htm">Command Composer Dialog</a>
-			</li>
-			<li>
-				<a href="section_command-details.htm">Command Details Section</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_content.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_content.htm
deleted file mode 100644
index dec5ed1..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_content.htm
+++ /dev/null

@@ -1,340 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Content Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Content Section</h2>
-		
-		<h3>About This Section</h3>
-		
-		<p>
-			This section allows you to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Visualize the structure and order of the cheat sheet's 
-				title, introduction, steps and sub-steps
-				as they appear in the <strong>Cheat Sheet</strong> view.
-			</li>
-			<li>
-				Edit the structure and order of the cheat sheet's steps and sub-steps.
-			</li>
-			<li>
-				Activate the corresponding <strong>Definition</strong> section used to edit the 
-				properties of a selected title, introduction, step or sub-step.
-			</li>
-			<li>
-				Preview and test the edited cheat sheet within the 
-				<strong>Cheat Sheet</strong> view.
-			</li>
-		</ul>
-
-		<p>
-			This section is accessible through the <strong>Cheat Sheet</strong> form page.
-		</p>
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					None
-				</td>
-				<td class="body">
-					Tree Viewer
-				</td>
-				<td class="body">
-					Cheat Sheet Element Viewer
-				</td>
-				<td class="body">
-					Use this field this field to do the following:
-					<ul>
-						<li>
-							Visualize the structure and order of the cheat sheet's 
-							title, introduction, steps and sub-steps
-							as they appear in the <strong>Cheat Sheet</strong> view.
-						</li>
-						<li>
-							Edit the structure and order of the cheat sheet's steps and sub-steps.
-						</li>
-						<li>
-							Activate the corresponding <strong>Definition</strong> section used to edit the 
-							properties of a selected title, introduction, step or sub-step.
-						</li>
-					</ul>
-				</td>
-				<td class="body">
-					N/A
-				</td>				
-			</tr>		
-		</table>		
-
-		<h3>Cheat Sheet Element Viewer</h3>
-
-		<p>
-			This viewer contains the following nodes:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Node
-				</td>
-				<td class="header">
-					Representation
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/cheatsheet_simple_obj.gif" alt="Root Cheat Sheet Node">
-				</td>
-				<td class="body">
-					Root
-				</td>
-				<td class="body">
-					Select this node, to activate the title <strong>Definition</strong> section.
-				</td>
-			</tr>		
-			<tr>
-				<td class="body">
-					<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/cheatsheet_intro_obj.gif" alt="Introduction Node">
-				</td>
-				<td class="body">
-					Introduction
-				</td>
-				<td class="body">
-					Select this node, to activate the introduction <strong>Definition</strong> section.
-				</td>
-			</tr>	
-			<tr>
-				<td class="body">
-					<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/cheatsheet_item_obj.gif" alt="Step Node">
-				</td>
-				<td class="body">
-					Step
-				</td>
-				<td class="body">
-					Select this node, to activate the step <strong>Definition</strong> section.
-				</td>
-			</tr>	
-			<tr>
-				<td class="body">
-					<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/cheatsheet_subitem_obj.gif" alt="Sub-Step Node">
-				</td>
-				<td class="body">
-					Sub-Step
-				</td>
-				<td class="body">
-					Select this node, to activate the sub-step <strong>Definition</strong> section.
-				</td>
-			</tr>	
-		</table>	
-
-		<img src="../../../images/simple_cs_editor/section_step_master_1.png" alt="Content Section">
-
-		<h3>Section Actions</h3>
-
-		<p>
-			This section provides the following actions:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Add Step</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Add Step to Cheat Sheet
-				</td>
-				<td class="body">
-					Click this button to add a new step to the cheat sheet.
-					This action is available when any of following nodes are selected:  
-					root, introduction, step.
-					<br>
-					<br>
-					If a step or introduction node is selected, the new step will be added 
-					after the selected node.  If the root node is selected, the 
-					new step will be added as the last step of the cheat sheet.
-				</td>
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>Add Sub-Step</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Add Sub-Step to Step
-				</td>
-				<td class="body">
-					Click this button to add a new sub-step to a step.
-					This action is available when any of following nodes are selected:  
-					step<span class="reference">*</span>, sub-step.
-					<br>
-					<br>
-					Note<span class="reference">*</span>:  
-					Any step that either is optional or contains a command cannot
-					contain sub-steps.
-					<br>
-					<br>
-					If a sub-step node is selected, the new sub-step will be added after
-					the selected node.  If a step node is selected, the new sub-step will
-					be added as the last sub-step of that step.
-				</td>
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>Remove</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Remove Cheat Sheet Element
-				</td>
-				<td class="body">
-					Click this button to remove a step or sub-step.
-					This action is available when any of following nodes are selected:  
-					step, sub-step.					
-					<br>
-					<br>
-					Note:  In order to maintain cheat sheet validity, the following nodes
-					cannot be removed:  root, introduction, step 
-					(if it is the last remaining step in the cheat sheet).
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Up</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Move Cheat Sheet Element Up
-				</td>
-				<td class="body">
-					Click this button to move a step or sub-step up one position
-					in order above their respective siblings.
-					This action is available when any of following nodes are selected:  
-					step, sub-step.				
-				</td>
-			</tr>	
-			<tr>
-				<td class="body">
-					<strong>Down</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Move Cheat Sheet Element Down
-				</td>
-				<td class="body">
-					Click this button to move a step or sub-step down one position
-					in order below their respective siblings.
-					This action is available when any of following nodes are selected:  
-					step, sub-step.	
-				</td>
-			</tr>												
-			<tr>
-				<td class="body">
-					<strong>Preview</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Preview Cheat Sheet
-				</td>
-				<td class="body">
-					Click this button to preview and test the saved or unsaved
-					contents of the edited cheat sheet in the <strong>Cheat Sheet</strong> view.  
-					<br>
-					<br>					
-					This convenient action allows you to observe how the edited cheat sheet 
-					actually appears and operates within its deployed environment without having to
-					register the cheat sheet and launch another Eclipse runtime instance.
-				</td>
-			</tr>
-		</table>
-
-		<h3>Representation</h3>
-
-		<p>
-			A cheat sheet previewed in the <strong>Cheat Sheet</strong> view:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_sub-step_view.png" alt="Title Cheat Sheet View">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="page_cheat-sheet.htm">Simple Cheat Sheet Page</a>
-			</li>		
-			<li>
-				<a href="section_title.htm">Title Section</a>
-			</li>
-			<li>
-				<a href="section_introduction.htm">Introduction Section</a>
-			</li>
-			<li>
-				<a href="section_step.htm">Step Section</a>
-			</li>
-			<li>
-				<a href="section_sub-step.htm">Sub-Step Section</a>
-			</li>
-		</ul>
-	
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_help.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_help.htm
deleted file mode 100644
index bffd4cd..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_help.htm
+++ /dev/null

@@ -1,194 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Help Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Help Section</h2>
-		
-		<h3>About This Section</h3>
-
-		<p>
-			This collapsible section allows you to do the following:
-		</p>
-
-		<ul>
-			<li>
-				Add a help link to a step or introduction using either a help document link 
-				or help context ID as input.
-			</li>
-			<li>
-				Remove a help link from a step or introduction.
-			</li>
-			<li>
-				Edit the help document link or help context 
-				ID used as input to add a help link to a step or introduction.
-			</li>
-		</ul>
-
-		<p>
-			This section is accessible by selecting a step or introduction node in the <strong>Content</strong> section.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_step_master_1.png" alt="Step Content Section">
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Type</strong>
-				</td>
-				<td class="body">
-					Combo Box
-				</td>
-				<td class="body">
-					Help Link Type
-				</td>
-				<td class="body">
-					Select <strong>&lt;none&gt;</strong> to remove a help
-					link from a step or introduction.  
-					Consequently, the <strong>Value</strong> input field 
-					will no longer be visible.
-					<br>
-					<br>
-					Select <strong>Help Context ID</strong> to make the 
-					<strong>Value</strong> input field visible right under
-					this field and ready to accept a help context ID as input.
-					<br>
-					<br>
-					Select <strong>Help Document Link</strong> to make the 
-					<strong>Value</strong> input field visible right under
-					this field and ready to accept a help document link as input.
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>Value</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Help Document Link Value or Help Context ID Value
-				</td>
-				<td class="body">
-					If <strong>Help Context ID</strong> is selected in the
-					<strong>Type</strong> field, specify a valid help
-					context ID in this field to add a help link to a step
-					or introduction.
-					<br>
-					<br>
-					In the <strong>Cheat Sheet</strong> view, 
-					clicking on a step or introduction's help link created
-					using a help context ID will open that help
-					context ID in the <strong>Help</strong> view.
-					<br>
-					<br>
-					The format of a valid help context ID is the following:
-					<em>&lt;plugin-id&gt;.&lt;help-context-id&gt;</em>
-					<br>
-					<br>
-					If <strong>Help Document Link</strong> is selected in the
-					<strong>Type</strong> field, specify a valid help
-					document link in this field to add a help link to a step
-					or introduction.
-					<br>
-					<br>
-					In the <strong>Cheat Sheet</strong> view, 
-					clicking on a step or introduction's help link created
-					using a help document link will open that help
-					document link in the <strong>Help</strong> Infocenter.
-					<br>
-					<br>
-					The format of a valid help document link is the following:
-					<em>/&lt;plugin-id&gt;/&lt;path&gt;/&lt;html-file&gt;</em>									
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>						
-		</table>
-
-		<p>
-			Example of a help link removed from a step or introduction.
-			Note:  This section is collapsed by default when no help context ID or 
-			help document link is specified.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_help_details_none.png" alt="Definition Section: None">
-
-		<p>
-			Example of a help link added to a step or introduction defined using a help context ID as input.
-			Note:  This section is expanded by default when a help context ID is specified.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_help_details_id.png" alt="Definition Section: Help Context ID">
-
-		<p>
-			Example of a help link added to a step or introduction defined using a help document link as input.
-			Note:  This section is expanded by default when a help document link is specified.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_help_details_link.png" alt="Definition Section: Help Document Link">
-
-		<h3>Representation</h3>
-
-		<p>
-			An introduction with a help link and various steps with help links are 
-			represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_title_view.png" alt="Title Cheat Sheet View">
-
-		<p>
-			Note:  A help link created using a help context ID is 
-			indistinguishable from one created using a help document link
-			in the <strong>Cheat Sheet</strong> view.
-		</p>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="section_content.htm">Content Section</a>
-			</li>
-			<li>
-				<a href="section_step.htm">Step Section</a>
-			</li>
-			<li>
-				<a href="section_introduction.htm">Introduction Section</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_introduction.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_introduction.htm
deleted file mode 100644
index f3b5aec..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_introduction.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Introduction Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Introduction Section</h2>
-		
-		<h3>About This Section</h3>
-		
-		<p>
-			This <strong>Definition</strong> section allows you to edit the introduction of the cheat sheet. 
-			It is activated by selecting the <strong>Introduction</strong> node in 
-			the <strong>Content</strong> section.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_introduction_master.png" alt="Introduction Content Section">
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>				
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Body</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Cheat Sheet Introduction
-				</td>
-				<td class="body">
-					Edit this field to specify the introduction of the cheat sheet.
-					<br>
-					<br>
-					The text may be formatted using bold and break tags:  
-					To bold text, enclose with HTML-style bold tags: &lt;b&gt;&lt;/b&gt;.
-					To break text, use break tags: &lt;br/&gt;.
-				</td>
-				<td class="body">
-					Yes
-				</td>				
-			</tr>		
-		</table>
-
-		<img src="../../../images/simple_cs_editor/section_introduction_details.png" alt="Introduction Definition Section">
-
-		<h3>Representation</h3>
-
-		<p>
-			The introduction is represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_introduction_view.png" alt="Introduction Cheat Sheet View">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="section_content.htm">Content Section</a>
-			</li>
-		</ul>
-		
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_step.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_step.htm
deleted file mode 100644
index 48c5c1b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_step.htm
+++ /dev/null

@@ -1,163 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Step Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Step Section</h2>
-		
-		<h3>About This Section</h3>
-		
-		<p>
-			This <strong>Definition</strong> section allows you to edit the properties of a step. 
-			It is activated by selecting a step node in the <strong>Content</strong> section.
-		</p>
-		
-		<p>
-			Selection of a step without sub-steps:
-		</p>
-				
-		<img src="../../../images/simple_cs_editor/section_step_master_2.png" alt="Step Content Section">
-
-		<p>
-			Selection of a step with sub-steps:
-		</p>
-				
-		<img src="../../../images/simple_cs_editor/section_step_master_1.png" alt="Step Content Section">
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Title</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Step Title
-				</td>
-				<td class="body">
-					Edit this field to specify the title of the step.
-				</td>
-				<td class="body">
-					Yes
-				</td>				
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>Body</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Step Body
-				</td>
-				<td class="body">
-					Edit this field to specify the instructional content of the step.
-					<br>
-					<br>
-					The text may be formatted using bold and break tags:  
-					To bold text, enclose with HTML-style bold tags: &lt;b&gt;&lt;/b&gt;.
-					To break text, use HTML-style break tags: &lt;br/&gt;.
-				</td>
-				<td class="body">
-					Yes
-				</td>				
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>This step is optional</strong>
-				</td>
-				<td class="body">
-					Checkbox
-				</td>
-				<td class="body">
-					Optional Step
-				</td>
-				<td class="body">
-					Check this field to make the completion of this step in the <strong>Cheat Sheet</strong> 
-					view optional.  
-					<br>
-					<br>					
-					A non-optional step includes a 
-					<strong>Click when complete</strong> action in the <strong>Cheat Sheet</strong> 
-					view to complete the step.  An optional step includes a <strong>Click to skip</strong>
-					action in the <strong>Cheat Sheet</strong> view to skip the step.
-					<br>
-					<br>
-					Note:  A step that contains sub-steps cannot be made optional.
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>						
-		</table>
-
-		<p>
-			Properties of a step without sub-steps:
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_step_details_2.png" alt="Step Definition Section">
-
-		<p>
-			Properties of a step with sub-steps:
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_step_details_1.png" alt="Step Definition Section">
-
-		<h3>Representation</h3>
-
-		<p>
-			A step without sub-steps is represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_step_view_2.png" alt="Step Cheat Sheet View">
-
-		<p>
-			A step with sub-steps is represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_step_view_1.png" alt="Step Cheat Sheet View">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="section_content.htm">Content Section</a>
-			</li>
-			<li>
-				<a href="section_sub-step.htm">Sub-Step Section</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_sub-step.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_sub-step.htm
deleted file mode 100644
index f800f61..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_sub-step.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Sub-Step Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Sub-Step Section</h2>
-		
-		<h3>About This Section</h3>
-		
-		<p>
-			This <strong>Definition</strong> section allows you to edit the properties of a sub-step. 
-			It is activated by selecting a sub-step node in the <strong>Content</strong> section.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_sub-step_master.png" alt="Sub-Step Content Section">
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Body</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Sub-Step Body
-				</td>
-				<td class="body">
-					Edit this field to specify the instructional content of the sub-step.
-				</td>
-				<td class="body">
-					Yes
-				</td>				
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>This sub-step is optional</strong>
-				</td>
-				<td class="body">
-					Checkbox
-				</td>
-				<td class="body">
-					Optional Sub-Step
-				</td>
-				<td class="body">
-					Check this field to make the completion of this sub-step in the <strong>Cheat Sheet</strong> 
-					view optional.  
-					<br>
-					<br>					
-					A non-optional sub-step includes a 
-					<strong>Click when complete</strong> action in the <strong>Cheat Sheet</strong> 
-					view to complete the sub-step.  An optional sub-step includes a <strong>Click to skip</strong>
-					action in the <strong>Cheat Sheet</strong> view to skip the sub-step.
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>						
-		</table>
-
-		<img src="../../../images/simple_cs_editor/section_sub-step_details.png" alt="Sub-Step Definition Section">
-
-		<h3>Representation</h3>
-
-		<p>
-			A sub-step is represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_sub-step_view.png" alt="Sub-Step Cheat Sheet View">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="section_content.htm">Content Section</a>
-			</li>
-			<li>
-				<a href="section_step.htm">Step Section</a>
-			</li>
-		</ul>
-	
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_title.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_title.htm
deleted file mode 100644
index 1caa69f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/section_title.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Title Section</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Title Section</h2>
-
-		<h3>About This Section</h3>
-		
-		<p>
-			This <strong>Definition</strong> section allows you to edit the title of the cheat sheet. 
-			It is activated by selecting the root node in the <strong>Content</strong> section.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/section_title_master.png" alt="Title Content Section">
-
-		<h3>Section Fields</h3>
-
-		<p>
-			This section contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Title</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Cheat Sheet Title
-				</td>
-				<td class="body">
-					Edit this field to specify the cheat sheet title.
-				</td>
-				<td class="body">
-					Yes
-				</td>
-			</tr>		
-		</table>
-
-		<img src="../../../images/simple_cs_editor/section_title_details.png" alt="Title Definition Section">
-
-		<h3>Representation</h3>
-
-		<p>
-			The title is represented in the <strong>Cheat Sheet</strong> view as follows:
-		</p>
-		
-		<img src="../../../images/simple_cs_editor/section_title_view.png" alt="Title Cheat Sheet View">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="section_content.htm">Content Section</a>
-			</li>
-		</ul>
-
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm
deleted file mode 100644
index 3bb4ae8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm
+++ /dev/null

@@ -1,233 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Register Cheat Sheet Wizard</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Register Cheat Sheet Wizard</h2>
-		
-		<h3>About This Wizard</h3>
-		
-		<p>
-			This wizard allows you to register a simple or 
-			composite cheat sheet with the Eclipse workbench 
-			to make it accessible through the <strong>Help</strong> menu.
-		</p>
-
-		<p>
-			The underlying operation performed by this wizard involves generating
-			the XML-related mark-up for the <strong>Cheat Sheet Content</strong>
-			extension point (<strong>org.eclipse.ui.cheatsheets.cheatSheetContent</strong>)
-			and adding it to the plugin.xml file belonging to the plug-in project
-			the cheat sheet being registered is contained within.
-		</p>
-
-		<p>
-			A brief description and problem domain category may be 
-			specified for the cheat sheet during registration. 
-			This wizard will only register the cheat sheet once.
-			Subsequent uses of this wizard allow the user to update the
-			cheat sheet description and category values of the original registration.
-		</p>
-
-		<p>
-			To register the current cheat sheet being edited, click the
-			<strong>Register this cheat sheet</strong>
-			hyperlink in the title area of the <em>Simple Cheat Sheet Editor</em> or
-			<em>Composite Cheat Sheet Editor</em>.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/page_cheat-sheet_header.png" alt="Cheat Sheet Page Header">
-
-		<h3>Wizard Fields</h3>
-
-		<p>
-			This wizard contains the following fields:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-				<td class="header">
-					Required
-				</td>					
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>Category</strong>
-				</td>
-				<td class="body">
-					Combo Box
-				</td>
-				<td class="body">
-					Problem Domain Category
-				</td>
-				<td class="body">
-					To categorize the cheat sheet being registered using an
-					existing problem domain category, select a value from this
-					field.
-					<br>					
-					<br>					
-					If an existing problem domain category is selected, the
-					registered cheat sheet will be placed as a node under that category
-					in the <strong>Cheat Sheet Selection</strong> dialog's tree 
-					viewer.
-					<br>					
-					<br>
-					If <strong>&lt;none&gt;</strong> is selected, the 
-					registered cheat sheet will be placed as a node under the
-					<strong>Other</strong> category
-					in the <strong>Cheat Sheet Selection</strong> dialog's tree 
-					viewer.					
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>		
-			<tr>
-				<td class="body">
-					<strong>Description</strong>
-				</td>
-				<td class="body">
-					Text
-				</td>
-				<td class="body">
-					Brief Cheat Sheet Description 
-				</td>
-				<td class="body">
-					Edit this field to specify a brief description for the
-					cheat sheet being registered.	
-					<br>					
-					<br>
-					If a description is specified, it will appear as a label under the
-					<strong>Cheat Sheet Selection</strong> dialog's tree 
-					viewer when the registered cheat sheet node is selected.
-				</td>
-				<td class="body">
-					No
-				</td>				
-			</tr>				
-		</table>
-		
-		<img src="../../../images/simple_cs_editor/wizard_register_cheat-sheet.png" alt="Register Cheat Sheet Wizard Main">
-
-		<h3>Wizard Actions</h3>
-
-		<p>
-			This wizard provides the following actions:
-		</p>
-
-		<table cellspacing="0">
-			<tr>
-				<td class="header">
-					Label
-				</td>
-				<td class="header">
-					Type
-				</td>
-				<td class="header">
-					Name
-				</td>
-				<td class="header">
-					Description
-				</td>
-			</tr>
-			<tr>
-				<td class="body">
-					<strong>New...</strong>
-				</td>
-				<td class="body">
-					Button
-				</td>
-				<td class="body">
-					Create New Category
-				</td>
-				<td class="body">
-					Click this button to create a new problem domain category.
-					<br>
-					<br>
-					In the resulting <strong>Create New Category</strong> dialog,
-					enter a category name in the <strong>Name</strong> field to 
-					specify the problem domain the cheat sheet being registered 
-					belongs to.
-					<br>
-					<br>
-					The new category will be added to the <strong>Category</strong>					
-					combo box.
-				</td>
-			</tr>	
-		</table>
-
-		<img src="../../../images/simple_cs_editor/wizard_register_category.png" alt="Register Cheat Sheet Wizard Category">
-
-		<h3>How To Access A Registered Cheat Sheet</h3>
-
-		<p>
-			To access a registered cheat sheet within the Eclipse workbench,
-			perform the following steps:
-		</p>			
-			
-		<ol>
-			<li>
-				Launch a new runtime Eclipse workbench<span class="reference">*</span>.  
-			</li>
-			<li>
-				In the runtime Eclipse workbench, click 
-				<strong>Help &gt; Cheat Sheets...</strong> to open the
-				<strong>Cheat Sheet Selection</strong> dialog.
-			</li>
-			<li>
-				Within the dialog, select the following option:  
-				<strong>Select a cheat sheet from the list</strong>
-			</li>
-			<li>
-				In the tree viewer, expand the problem domain category used
-				to categorize the registered cheat sheet.  If one was not
-				specified, expand the <strong>Other</strong> category.
-			</li>
-			<li>
-				Select the registered cheat sheet
-			</li>
-			<li>
-				Click <strong>OK</strong> and the cheat sheet will be
-				opened in the <strong>Cheat Sheet</strong> view.
-			</li>
-		</ol>
-
-		<p>
-			Note<span class="reference">*</span>:  A registered cheat sheet is not
-			accessible through the <strong>Help</strong> menu in the (host) Eclipse 
-			workbench being used to edit it.
-		</p>
-
-		<img src="../../../images/simple_cs_editor/wizard_register_selection.png" alt="Cheat Sheet Selection Dialog">
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="editor.htm">Simple Cheat Sheet Editor</a>
-			</li>
-			<li>
-				<a href="../composite_cs_editor/editor.htm">Composite Cheat Sheet Editor</a>
-			</li>
-		</ul>
-			
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/archives.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/archives.htm
deleted file mode 100644
index e0621cf..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/archives.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Site Information</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1><strong>Site Information </strong></h1>
-
-<h2>Site Description </h2>
-<p>A site description may be as simple as a brief text description.  Alternately, you may specify a URL pointing to an HTML file. The URL can be specified as absolute of relative. If relative, the URL is   assumed to be relative to site.xml. </p>
-<p><img src="../../../images/site_editor/archives_description.png" alt="Description"></p>
-
-<h2>Site Mirrors</h2>
-<p>An update site may point to the URL of a file listing update site mirror definitions. This URL can be absolute or relative to   this site.</p>
-<p><img src="../../../images/site_editor/archives_mirrors.png" alt="Mirrors"></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_editor.htm
deleted file mode 100644
index 277dfb4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_editor.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Site Manifest Editor</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1><strong>Site Manifest Editor</strong></h1>
-<p>PDE provides a form-based multi-page site manifest editor that manages the <em>site.xml</em> file and builds an update site for <em>Update Manager</em>. </p>
-<p>For details on the individual editor sections, refer to the following documents:</p>
-<ul>
-  <li><a href="site_map.htm">Site Map</a></li>
-  <li><a href="archives.htm">Site Information </a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_map.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_map.htm
deleted file mode 100644
index f743fa9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/site_editor/site_map.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Site Map</title>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1><strong>Site Map </strong></h1>
-<p>The <strong>Site Map</strong> page of the site manifest editor lists, categorizes and builds the features hosted on the update site. </p>
-
-<h2>Managing the Site </h2>
-<p>Building an update site is a relatively simple task with the </p>
-<p><img src="../../../images/site_editor/map_managing.png" alt="Managing the Site" ></p>
-<p>To publish a feature on the site, you must first add it via the <strong>Add Feature...</strong> button.</p>
-<p>For easier browsing of the site, it is recommended to create categories and organize the features under those categories. A <strong>category</strong> has a name and a translatable label for display. A feature may appear in &gt;= 0 categories. Categorization enables <em>Update Manager</em> to present a hierarchical view of features. </p>
-<p>Features are   built recursively when you press <strong>Build All</strong>. This means that the features   and all the plug-ins and fragments they include will be built in a single batch   operation. The feature JARs end up in the <em>features/ </em>folder and the plug-in JARs are placed in the <em>plugins/</em> folder of the update  site project.</p>
-<p>If you are dealing with features that include other features, only   the root feature needs to be listed, since the child features are automatically built. </p>
-<p>To build a single feature, select the feature and press   the <strong>Build</strong> button.. </p>
-
-<h2>Feature Environments </h2>
-<p>Features that do not carrry such environment constraints are portable and can be installed on all platforms. If a feature has environment constraints that does not match the user's current platform, you can set <em>Update Manager</em> to filter it out. </p>
-<p>For faster filtering, feature environments should be associated with a feature entry in the site.xml. </p>
-<p>To copy feature environments from the <em>feature.xml</em> to the <em>site.xml</em>, press the <strong>Synchronize...</strong> button in the <strong>Managing the Site</strong> section. </p>
-<p><img src="../../../images/site_editor/map_environment.png" alt="Feature Environment" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/content_page.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/content_page.htm
deleted file mode 100755
index a458d4c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/content_page.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Content Page</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Content Page</h1>
-
-<p>The <strong>Content Page</strong> in the <a href="./target_editor.htm">Target Definition Editor</a> is used to view and edit the set of plug-ins to be included in the target definition when set as the active target platform.  The definition must contain one or more locations containing plug-ins and the definition must be <em>resolved</em> to edit the content.  Only the plug-ins that are checked on this page will be included in the target.  There are multiple options available to filter and sort the list to quickly check what you require.</p>
-
-<p>This page edits the same information as the <a href="../../target_shared/edit_target_content_tab.htm">Content Tab</a> on the <a href="../../target_shared/edit_target_wizard.htm">Edit Target Wizard</a></p>
-
-<img src="../../../images/target_editor/content_page.png" alt="Content Page">
-
-<p><strong>Select / Deselect</strong> will check or uncheck the selected plug-ins. </p>
-
-<p><strong>Select All / Deselect All</strong> will check or uncheck all plug-ins in the target definition.</p>
-
-<p><strong>Add Required</strong> takes the set of currently checked plug-ins and determines all plug-ins required by them.  This will also include any <a href="../../target_shared/edit_target_implicit_tab.htm">implicit dependencies</a> set on this target.  The required plug-ins will be checked in the list.</p>
-
-<p>Use the <strong>Show</strong> options along with the filter text box at the top of the list to filter what is shown in the list.  Showing <em>plug-ins</em> will show any non-source plug-ins in the target, while showing <em>source bundles</em> will display any source.  Even if a plug-in is filtered from the list, it may be included in the target.  You can see a count of included plug-ins underneath the list.</p>
-
-<p>The <strong>Group By</strong> option is used to organize the list into different groups.  The options are:</p>
-<ol>
-<li><strong>None</strong> - No grouping, plug-ins sorted by name</li>
-<li><strong>File Path</strong> - Grouped by the directory path the plug-ins are stored in on the local file system</li>
-<li><strong>Location</strong> - Grouped by the locations set on the <a href="../../target_shared/edit_target_locations_tab.htm">locations tab</a></li>
-</ol>
-  
-  
-<p><img src="../../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./target_editor.htm">Target Definition Editor</a><br>
-<a href="./definition_page.htm">Definition Page</a> (Target Definition Editor)<br>
-<a href="./environment_page.htm">Environment Page</a> (Target Definition Editor)<br>
-<a href="../../target_shared/edit_target_wizard.htm">Edit Target Wizard</a>
-</p>
-
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts"></p>
-<p>
-<a href="../../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/definition_page.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/definition_page.htm
deleted file mode 100755
index 482727d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/definition_page.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Definition Page</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Definition Page</h1>
-
-<p>The <strong>Definition Page</strong> in the <a href="./target_editor.htm">Target Definition Editor</a> is used to edit the most important settings in a target definition file.  The <strong>Target Name</strong> is used to display your targets on the <a href="../../preference_pages/target_platform.htm">Target Platform Preference Page</a>.  The <strong>Locations</strong> section is used to add locations that contain plug-ins and works the same as the <a href="../../target_shared/edit_target_locations_tab.htm">Location Tab</a> on the <a href="../../target_shared/edit_target_wizard.htm">Edit Target Wizard</a></p>
-
-<img src="../../../images/target_editor/definition_page.png" alt="Definition Page">
-
-<p>The locations in the target definition will be displayed in the list.  Each type of location will have a different icon and text.  If the target has been <em>resolved</em> the count of plug-ins will be displayed in blue (the number of plug-ins included from the <a href="./content_page.htm">content page</a> and the total number of plug-ins found.  If there are problems resolving the target, they will be displayed underneath the location with the problem. The <strong>Show Plug-in Content</strong> option can be turned on to display the included plug-ins underneath each location.</p>
-
-<p>Pressing <strong >Add</strong> will open the <a href="../../target_shared/location_add_wizard.htm">Add Location Wizard</a>.  It will provide a choice of location types to add.  Selecting a location and pressing <strong>Edit</strong> will open a location type specific wizard to view and modify the location.</p>
-
-<p><img src="../../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./target_editor.htm">Target Definition Editor</a><br>
-<a href="./content_page.htm">Content Page</a> (Target Definition Editor)<br>
-<a href="./environment_page.htm">Environment Page</a> (Target Definition Editor)<br>
-<a href="../../target_shared/edit_target_wizard.htm">Edit Target Wizard</a>
-</p>
-
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts"></p>
-<p>
-<a href="../../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm
deleted file mode 100755
index 0181ca0..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/environment_page.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Environment Page</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Environment Page</h1>
-
-<p>The <strong>Enviroment Page</strong> in the <a href="./target_editor.htm">Target Definition Editor</a> is used to edit many settings  in the definition affecting how the target will be compiled and run.</p>
-
-<img src="../../../images/target_editor/environment_page.png" alt="Environment Page">
-
-<p>The environment settings on this page can also be edited using the <a href="../../target_shared/edit_target_environment_tab.htm">Environment Tab</a>, <a href="../../target_shared/edit_target_arguments_tab.htm">Arguments Tab</a> and <a href="../../target_shared/edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> on the <a href="../../target_shared/edit_target_wizard.htm">Edit Target Wizard</a></p>
-
-<p>The <strong>Environment</strong> section has four settings that describe the system that this target is built for.  If left blank, the settings for your current running environment are used.  Changing these settings will affect how <a href="../../target_shared/location_edit_site_wizard.htm">Software Site Locations</a> resolve as well as how plug-ins are built and exported.</p>
-
-<p>You can specify a JRE or execution environment for this target definition in the <strong>Target JRE</strong> section.  If you specify a specific JRE or EE here, when this target is set as the active target platform, your workspace default JRE will be changed.</p>
-
-<p>The <strong>Arguments</strong> section is used to set the default program and vm arguments for new PDE <a href="../../launchers/eclipse_application_launcher.htm">launch configurations</a>.Pressing <strong>Variables</strong> will open the <strong>Variable Selection Wizard</strong>.  You can browse through all known variables and get descriptions of what each does.  Under the <em>VM</em> tab you can also press <strong>Import</strong>.  This will open the <a href="../../target_shared/import_arguments_dialog.htm">Import Arguments Dialog</a>.  You can use it to import vm arguments used in the configuration data of any installation locations specified on the <a href="./definition_page.htm">definition page</a>.</p> 
-
-<p>The <strong>Implicit Dependencies</strong> section is used to manage the implicit dependencies of the target.  Any plug-in marked as an implicit dependency will always be added as a required plug-in when PDE determines requirements.  Pressing <strong>Add</strong> will open the <a href="../../target_shared/implicit_plugin_selection_dialog.htm">Implicit Dependencies Selection Dialog</a> allowing you to select one or more plug-ins from your target platform to add as implicit dependencies.</p>
- 
-<p><img src="../../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./target_editor.htm">Target Definition Editor</a><br>
-<a href="./definition_page.htm">Definition Page</a> (Target Definition Editor)<br>
-<a href="./content_page.htm">Content Page</a> (Target Definition Editor)<br>
-<a href="../../target_shared/edit_target_wizard.htm">Edit Target Wizard</a>
-</p>
-
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts"></p>
-<p>
-<a href="../../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/target_editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/target_editor.htm
deleted file mode 100755
index dd0b4a2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/target_editor/target_editor.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Target Definition Editor</title>
-<link rel="stylesheet" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Target Definition Editor</h1>
-<p>The <strong>Target Definition Editor</strong> is used to edit target definition files in the workspace, which should end with the extension &quot;.target&quot;.  Target definition files can be created using the <a href="../../file_wizards/new_target_definition.htm">New Target Definition Wizard</a> or by <a href="../../target_shared/move_target_wizard.htm">moving</a> them to the workspace on the <a href="../../preference_pages/target_platform.htm">Target Platform Preference Page</a>.</p>
-
-<p>The editor consists of three pages:</p>
-<ol>
-<li><a href="./definition_page.htm">Definition Page</a> - Give you definition a descriptive name and provide the locations for plug-ins</li>
-<li><a href="./content_page.htm">Content Page</a> - View the plug-ins available in your target and select a subset to include in the target platform</li>
-<li><a href="./environment_page.htm">Environment Page</a> - Modify other settings for your target defiition including target environment, JRE, arguments and implicit dependencies</li>
-</ol>
-
-<p>At the top of each page in the editor there is a link <strong>Set as Target Platform</strong>.  Activating this link will set this target definition as the active target platform.  To see what your active target platform is, use the <a href="../../preference_pages/target_platform.htm">Target Platform Preference Page</a>.</p>
-
-<h2>Resolving Targets</h2>
-
-<p>Before the contents of a target can be edited and before a target definition can be set as the active target platform it must be <em>resolved</em>.  When a target definition is resolved, the definition's locations are searched for plug-ins.  Depending on the type of locations in the target, this can involved searching a directory, reading the metadata for an installation, reading a feature, or downloading from a remote site.  During resolution a background job will be run.  When it completes the editor will be updated with any problems that occurred.</p>
-
-<p>For up to the minute target troubleshooting help see the <a href="http://wiki.eclipse.org/PDE/Target_Definitions">Target Definitions Wiki Page</a>.</p>
-
-<p><img src="../../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./definition_page.htm">Definition Page</a> (Target Definition Editor)<br>
-<a href="./content_page.htm">Content Page</a> (Target Definition Editor)<br>
-<a href="./environment_page.htm">Environment Page</a> (Target Definition Editor)<br>
-<a href="../../target_shared/new_target_wizard.htm">New Target Wizard</a><br>
-<a href="../../target_shared/edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../../target_shared/move_target_wizard.htm">Move Target Wizard</a>
-</p>
-
-<p><img src="../../../../images/ngrelc.png" alt="Related concepts"></p>
-<p>
-<a href="../../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/editor.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/editor.htm
deleted file mode 100644
index fae1aee..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/editor.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Table of Contents Editor</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>Table of Contents Editor</h2>
-		
-		<h3>About Tables of Contents</h3>
-		
-		<p>
-			Tables of contents allow you to organize your Eclipse product's contribution to on-line help.
-			A well-organized table of contents allows users to easily locate necessary documentation while working with an Eclipse product. 
-			Users of Eclipse products can view installed products' contributions to help by clicking <strong>Help &gt; Help Contents</strong>.   
-		</p>
-
-		<h3>About This Editor</h3>
-		
-		<p>
-			The <strong>Table of Contents Editor</strong> allows you to create and
-			organize tables of contents and visualize their structures.  
-			This editor also allows you to create new HTML pages and tables of contents,
-			and to locate existing ones in your workspace.
-		</p>
-
-		<h3>Editor Pages</h3>
-		
-		<p>
-			This editor is comprised of the following pages:
-		</p>
-
-		<ul>
-			<li>
-				<a href="page_toc.htm">Table of Contents Page</a>
-			</li>
-		</ul>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../../../../../org.eclipse.platform.doc.isv/guide/ua_help.htm">Help System Documentation</a>
-			</li>
-			<li>
-				<a href="../../file_wizards/new_toc.htm">New Table of Contents Wizard</a>
-			</li>
-		</ul>
-		
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/page_toc.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/page_toc.htm
deleted file mode 100644
index 5220ddb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/toc_editor/page_toc.htm
+++ /dev/null

@@ -1,348 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>Table of Contents Page</title>
-		<link rel="STYLESHEET" href="../../../../book.css" type="text/css">
-		<link rel="STYLESHEET" href="../../../tweak.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-	<h2>Table of Contents Page</h2>
-	<h3>About This Page</h3>
-		<p>
-			This page allows you to edit the structure and
-			properties of tables of contents.
-		</p>
-		<p>
-			You can modify and visualize the structure and order of 
-			elements in a table of contents using the 
-			<strong>Table of Contents</strong> section. 
-			This section occupies the left-hand portion of the 
-			editor area.
-		</p>
-		<p>
-			You can modify the properties of specific elements in the 
-			Table of Contents by using the corresponding 
-			<strong>Details</strong> sections. 
-			These sections appear in the right-hand portion of the 
-			editor area depending on the type of element selected 
-			in the <strong>Table of Contents</strong> section.
-		</p>
-
-	<h3>Page Sections</h3>
-		<p>
-			This page is comprised of the following sections:
-		</p>
-		<ul>
-			<li><a href="#toc">Table of Contents Section</a></li>
-			<li><a href="#toc_book">Book Details Section</a></li>
-			<li><a href="#toc_topic">Topic Details Section</a></li>
-			<li><a href="#toc_link">Link Details Section</a></li>
-			<li><a href="#toc_anchor">Anchor Details Section</a></li>
-		</ul>
-
-	<h3>Table of Contents Section</h3>
-		<p>
-			This section allows you to do the following:
-		</p>
-		<ul>
-			<li>
-				Visualize and modify the structure of a table of contents 
-				via addition, removal and reorganization of its elements.
-			</li>
-			<li>
-				Activate the corresponding <strong>Details</strong> 
-				section used to edit the properties of a specific element 
-				in the table of contents.
-			</li>
-			<li>
-				Find and open existing documentation pages and tables 
-				of contents linked from this table of contents.
-			</li>
-		</ul>
-		<img src="../../../images/toc_editor/toc_section.png" alt="Table of Contents Section">
-
-	<a name="toc"></a>
-	<h3>Table of Contents Section Fields</h3>
-		<p>
-			The table of contents tree viewer field displays the 
-			structure of the table of contents as it will appear 
-			in the Help system. This tree viewer allows you to 
-			modify the structure of the table of contents by 
-			reorganizing existing elements or adding new ones 
-			to the tree. 
-		</p>
-		<p>
-			This viewer contains the following kinds of elements:
-		</p>
-		<ul>
-			<li>
-			<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/toc_obj.gif" alt="Book Element">
-			The book element is the root element of a table of contents. 
-			Select this element to activate the <strong>Book Details</strong> 
-			section.
-			</li>
-			<li>
-			<img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/toc_topic_obj.gif" alt="Topic Element">
-			Topics serve as links to Help files, as well as containers for 
-			other elements in the table of contents. 
-			Select a topic to activate the <strong>Topic Details</strong> 
-			section.
-			</li>
-			<li><img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/toc_link_obj.gif" alt="Link Element">
-			Links allow you to include elements from other tables of 
-			contents in your table of contents. 
-			Select a link to activate the <strong>Link Details</strong> 
-			section.</li>
-			<li><img src="PLUGINS_ROOT/org.eclipse.pde.ui/icons/obj16/toc_anchor_obj.gif" alt="Anchor Element">
-			Anchors allow other tables of contents to specify that their 
-			elements will appear in your table of contents. 
-			Select an anchor to activate the <strong>Anchor Details</strong> 
-			section.</li>
-		</ul>
-
-	<h3>Table of Contents Section Actions</h3>
-		<p>
-			Click on the <strong>Add Topic</strong>, 
-			<strong>Add Link</strong> or <strong>Add Anchor</strong> 
-			buttons in order to add a new topic, link or anchor to the 
-			table of contents. 
-			These actions are available when any element is selected. 
-			If the selected element is a book or topic element, 
-			the new element will appear as the last child of the 
-			selected element. 
-			Otherwise, the element will appear immediately after the 
-			selected element.
-		</p>
-		<p>
-			You can also create topic elements by dragging HTML files 
-			and dropping them on the desired location within your table 
-			of contents. The newly added topic directs the user to the 
-			dropped page.
-		</p>
-		<p>
-			Similarly, you can create link elements by dragging XML files 
-			representing tables of contents and dropping them on the 
-			desired location within your table of contents. 
-			The newly added link will reference the dropped table of 
-			contents.
-		</p>
-		<p>
-			Click the <strong>Remove</strong> button to remove an element 
-			from the table of contents. 
-			This action is available for all elements except the book 
-			element. 
-			Note that, in order to maintain the validity of a table of 
-			contents, a topic cannot be removed if it is the only direct 
-			child of the book element.
-		</p>
-		<p>
-			Click the <strong>Up</strong> button to move an element up one 
-			position with respect to its siblings. 
-			This action is available for all elements except the book element.
-		</p>
-		<p>
-			Click the <strong>Down</strong> button to move an element down 
-			one position with respect to its siblings. 
-			This action is available for all elements except the book element.
-		</p>
-		<p>
-			You may also move elements within a table of contents by 
-			dragging them and dropping them in the desired locations.
-		</p>
-		<p>
-			To open the documentation file specified by a table of 
-			contents or a topic, simply double-click on it. 
-			To reveal the documentation file in a resource view, simply 
-			right-click the	element and select an option from the 
-			<strong>Show In</strong> submenu.
-		</p>
-		<p>
-			To open the table of contents specified by a link, simply 
-			double-click on the link. 
-			To reveal the table of contents	in a resource view, simply 
-			right-click the link and select an option from the 
-			<strong>Show In</strong> submenu.
-		</p>
-	
-	<a name="toc_book"></a>
-	<h3>Book Details Section</h3>
-		<p>
-			The <strong>Book Details</strong> section allows you to edit 
-			the name, page location and anchor path of this table of 
-			contents.
-		</p>
-		<img src="../../../images/toc_editor/book_details.png" alt="Book Details Section">
-		<h3>Book Details Section Fields</h3>
-		<p>
-			Edit the <strong>Name</strong> field to specify the name 
-			of the book.</p>
-		<p>
-			Edit the <strong>Location</strong> field to specify the 
-			location of a page associated with the book. 
-			This page will appear when the user clicks on the book 
-			element in the <strong>Help Contents</strong> window. 
-			If no page is specified, a default Help page is automatically 
-			generated by the Help system at runtime.
-		</p>
-		<p>
-			The <strong>Anchor</strong> field allows you to specify if this 
-			table of contents will be embedded within another table of 
-			contents. 
-			The anchor field takes the path to a table of contents 
-			and the ID of an anchor contained in that table of contents, 
-			separated by a '#' symbol. 
-			When users view the referenced table of contents in the 
-			<strong>Help Contents</strong> window, the contents of this 
-			table will be displayed at the location of the specified 
-			anchor.
-		</p>
-		<h3>Book Details Section Actions</h3>
-		<p>
-			If the path specified in the <strong>Location</strong> field 
-			refers to an existing HTML page, then clicking on the 
-			<strong>Location</strong> hyperlink will open the page in a 
-			default editor. 
-			If the path refers to a file that does not exist, or if the 
-			path is empty, then clicking on the <strong>Location</strong> 
-			hyperlink opens a <strong>New Page Wizard</strong>, which 
-			allows you to create HTML pages. In the wizard, the 
-			<strong>File name</strong> field is automatically populated 
-			with the file name from the <strong>Location</strong> field 
-			(if specified). If a valid folder path is specified in the 
-			<strong>Location</strong> field, then this path is 
-			automatically selected in the wizard as the location of the 
-			new file.
-		</p>
-		<p>
-			Click the <strong>Browse</strong> button to open the 
-			<strong>Page Selection</strong> dialog, which allows you to 
-			select an existing HTML page. 
-			The dialog presents a hierarchical view of HTML pages 
-			contained within your workspace. 
-			After a selection is made, the relative path from the project 
-			that contains the table of contents to the selected HTML page 
-			is automatically entered into the <strong>Location</strong> 
-			field.
-		</p>
-		
-	<a name="toc_topic"></a>
-	<h3>Topic Details Section</h3>
-		<p>
-			The <strong>Topic Details</strong> section allows you to edit 
-			the name and page location of this topic.
-		</p>
-		<img src="../../../images/toc_editor/topic_details.png" alt="Topic Details Section">
-		<h3>Topic Details Section Fields</h3>
-		<p>
-			Edit the <strong>Name</strong> field to specify the name of 
-			the topic.
-		</p>
-		<p>
-			Edit the <strong>Location</strong> field to specify the 
-			location of a page associated with the topic. 
-			This page will appear when the user clicks on the topic 
-			element in the <strong>Help Contents</strong> window. 
-			If no page is specified, a default Help page is automatically 
-			generated by the Help system at runtime.
-		</p>
-
-	<h3>Topic Details Section Actions</h3>
-		<p>
-			If the path specified in the <strong>Location</strong> field 
-			refers to an existing HTML page, then clicking on the 
-			<strong>Location</strong> hyperlink will open the page in a 
-			default editor. 
-			If the path refers to a file that does not exist, or if the 
-			path is empty, then clicking on the <strong>Location</strong> 
-			hyperlink opens a <strong>New Page Wizard</strong>, which 
-			allows you to create HTML pages. 
-			In the wizard, the <strong>File name</strong> field is 
-			automatically populated with the file name from the 
-			<strong>Location</strong> field (if specified). 
-			If a valid folder path is specified in the 
-			<strong>Location</strong> field, then this path is 
-			automatically selected in the wizard as the location of the 
-			new file.
-		</p>
-		<p>
-			Click the <strong>Browse</strong> button to open the 
-			<strong>Page Selection</strong> dialog, which allows 
-			you to select an existing HTML page. 
-			The dialog presents a hierarchical view of HTML pages 
-			contained within your workspace. 
-			After a selection is made, the relative path from the 
-			project that contains the table of contents to the 
-			selected HTML page is automatically entered into the 
-			<strong>Location</strong> field.
-		</p>
-		
-	<a name="toc_link"></a>
-	<h3>Link Details Section</h3>
-		<p>
-			The <strong>Link Details</strong> section allows you to edit 
-			the location of a linked table of contents file.
-		</p>
-		<img src="../../../images/toc_editor/link_details.png" alt="Link Details Section">
-
-	<h3>Link Details Section Fields</h3>
-		<p>
-			Edit the <strong>Location</strong> field to specify the 
-			location of a table of contents file to link. 
-			The elements in the linked file will replace this link in 
-			the table of contents when the user views the table of 
-			contents in the <strong>Help Contents</strong> window.
-		</p>
-
-	<h3>Link Details Section Actions</h3>
-		<p>
-			If the path specified in the <strong>Location</strong> field 
-			refers to an existing table of contents file, 
-			then clicking on the <strong>Location</strong> hyperlink 
-			will open the page in a default editor. 
-			If the path refers to a file that does not exist, or if the 
-			path is empty, then clicking on the <strong>Location</strong> 
-			hyperlink opens a <strong>New Table of Contents Wizard</strong>, 
-			which allows you to create a new table of contents. 
-			In the wizard, the <strong>File name</strong> field is 
-			automatically populated with the file name from the 
-			<strong>Location</strong> field (if specified). 
-			If a valid folder path is specified in the 
-			<strong>Location</strong> field, then this path is 
-			automatically selected in the wizard as the location of the 
-			new file.
-		</p>
-		<p>
-			Click the <strong>Browse</strong> button to open the 
-			<strong>Table of Contents Selection</strong> dialog, which allows you to 
-			select an existing table of contents. 
-			The dialog presents a hierarchical view of tables of contents 
-			contained within your workspace. 
-			After a selection is made, the relative path from the project 
-			to the selected table of contents is automatically entered 
-			into the <strong>Location</strong> field.
-		</p>
-		
-		<a name="toc_anchor"></a>
-		<h3>Anchor Details Section</h3>
-		<p>
-			The <strong>Anchor Details</strong> section allows you to 
-			edit the identifier of this anchor.
-		</p>
-		<img src="../../../images/toc_editor/anchor_details.png" alt="Anchor Details Section">
-
-	<h3>Anchor Details Section Fields</h3>
-		<p>
-			Edit the <strong>ID</strong> field to specify the identifier 
-			of the anchor.
-		</p>
-
-	<h3>Relevant Links</h3>
-		<ul>
-			<li><a href="editor.htm">Table of Contents Editor</a></li>
-			<li><a href="../../file_wizards/new_toc.htm">New Table of Contents Wizard</a></li>
-		</ul>
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_features.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_features.htm
deleted file mode 100644
index 3335ce2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_features.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Feature Export</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Export</h1>
-<p>PDE provides a <strong>Feature Export</strong> wizard to export features and constituent plug-ins and fragments into a form that is suitable for deployment. The wizard shields you from Ant scripts and does not pollute your workspace with resources generated during the build operation. The wizard is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.pde.ui.featureExportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the feature export wizard">
-<strong>File &gt; Export... &gt; Plug-in Development &gt; Deployable features</strong>
-</a>. </p>
-
-<h2>Feature Selection </h2>
-<p>The wizard displays all the non-binary features found in the workspace. </p>
-<p><img src="../../images/export_wizards/feature_available.png" alt="Feature Selection" ></p>
-<p>Select the features that you want to export. If you find yourself exporting the same set of features over and over, you can press <strong>Working Set...</strong> to define a <em> working set</em>. </p>
-<p>Features are built recursively; therefore, in the case where one feature includes another feature, only the top-level feature needs to be selected in order to export them both.
-</p>
-
-<h2>Destination</h2>
-<p>You can choose to export the features and their constituent plug-ins to a directory or to a ZIP archive. You can also choose to export the features in a runnable format and have them installed into your currently running Eclipse host.</p>
-<p><img src="../../images/export_wizards/destination.png" alt="Destination" ></p>
-<p>If you choose to export to a <strong>Directory</strong> (the default), the features will be placed in a <em>features/</em> subdirectory and the plug-ins will be placed in a <em>plugins/</em> subdirectory of the chosen directory.</p>
-<p>If you choose to export to an <strong>Archive file</strong>, all of the features and plug-ins will be packaged into a single ZIP archive. Also, the root directory structure inside the ZIP  starts with <em>features/</em> and <em>plugins/</em>. </p>
-<p>If you choose to export and <strong>Install</strong> the features will be exported in a runnable format and a p2 repository will be generated.  After the export completes, an installation operation will run to install the features.  You will be prompted to restart Eclipse when the installation completes.  To uninstall your features you must use the <strong>Installation Details</strong> button on the About Dialog (available by going to Help &gt; About Eclipse SDK). For more details see <a href="../../../tasks/ui_export_install_into_host.htm">Exporting and Installing into the Host</a></p>  
-
-<h2>Options</h2>
-<p><img src="../../images/export_wizards/options_features.png" alt="Options" ></p>
-
-<p>The <strong>Export source</strong> option results in the exporting of source code as well as binaries.  There are two ways to package source with your exported feature.  The <em>Generated Source Bundles</em> option will add the ant commands to the export to create separate source bundles for each of the exported plug-ins.  For more information on source bundles see the PDE Build entry on <a href="../../../tasks/pde_individual_source.htm">Individual Source Bundles</a>.  The second option is to <em>Include source in exported plug-ins</em>.  This option will package the source files in a <em>src/</em> folder at the root of the JAR (if exporting in a JAR format). If the plug-in is packaged as a flat directory, the source code will be placed in a source ZIP inside the plug-in directory as a sibling to the library JAR.</p>
-
-<p>The <strong>Package as individual JAR archives</strong> option packages features and their constituent plug-ins as JARs. If the option is not selected, then the features are exported as flat directories, while their constituent plug-ins are packaged as specified in the <em>feature.xml</em> markup. Plug-in entries that are marked with <em><strong>unpack=&quot;false&quot;</strong></em> in the <em>feature.xml</em> are exported as JARs; otherwise, they are exported as directories.</p>
-<p> There are two additional options available when packaging as individual JARs.  The <strong>Generate metadata repository</strong> option allows you to also generate p2 metadata along with your exported feature. This allows the directory or archive you are exporting to, to be used as a repository that p2 can install and update from.  This option must be turned on when exporting and installing into your running host.  The <strong>Categorize repository</strong> allows the generated metadata repository to be organized by category..  A valid category xml file that includes data for the features being exported must be specified for categories to be created succesfully.</p> 
-
-<p>The <strong>Qualifier replacement</strong> option enables you to substitute a value for the qualifier element in a plug-in's version or feature's version.  The version must be in the following format: &lt;<em>major</em>&gt;.&lt;<em>minor</em>&gt;.&lt;<em>micro</em>&gt;.qualifier.  For example: 3.3.0.qualifier. Normally, the qualifier represents a build date or identifier.</p>
-
-<p>The <strong>Save as Ant script</strong> option lets you save the settings of the export operation so that it can be re-executed at a later time without having to go through the wizard again. Like the export operation, the Ant task runs as an asynchronous job; therefore, it may not be suitable to incorporate it as a part of a larger Ant script. </p>
-
-<p> <strong>Allow binary cycles in target platform</strong> is an option that controls how the export operation deals with cycles in the dependency graph for a plug-in.  PDE Build cannot compile if a cycle is detected.  However, if a cycle only contains binary plug-ins from the target platform, turning on this option will allow PDE Build to continue.</p>
-
-<p> If the <strong>Use class files compiled in the workspace</strong> option is turned on, rather than compiling files as part of the export operation, the binary files in the workspace that were compiled by Eclipse are used.  This should improve performance as it skips the compilation phase, but your workspace must have successfully compiled</p>
-
-<h2>JAR Signing </h2>
-<p>The <strong>JAR Signing</strong> tab is only visible when the <strong>Package as individual JAR archives</strong> option is selected on the <strong>Options</strong> tab. </p>
-<p><img src="../../images/export_wizards/jar_signing.png" alt="JAR Signing" ></p>
-<p>To sign the JARs, <em><strong>you must be running Eclipse with a full JDK, rather than just a JRE. </strong></em></p>
-<p>The <strong>Keystore location</strong>,  <strong>Keypass</strong>, <strong>Alias</strong> and <strong>Password</strong> fields are all required for the signing operation.</p>
-
-<h2>Java Web Start</h2>
-<p>The <strong>Java Web Start</strong> tab is only available when the <strong>Directory</strong> option is selected on the <strong>Destination</strong> tab and the <strong>Package as individual JAR archives</strong> option is selected on the <strong>Options</strong> tab. </p>
-<p><img src="../../images/export_wizards/webstart_features.png" alt="Java Web Start" > .</p>
-<p>The <strong>Site URL</strong> and <strong>JRE version</strong> fields are both required.</p>
-
-<br>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="export_wizards.htm">Export Wizards</a><br>
-<a href="export_plugins.htm">Plug-in Export Wizard</a>
-</p>
-<p><img src="../../../images/ngrelt.png" alt="Related tasks" border="0"></p>
-<p>
-<a href="../../../tasks/ui_export_install_into_host.htm">Export and Install into the Running Host</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_plugins.htm
deleted file mode 100644
index 66e2f30..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_plugins.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Export</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Export</h1>
-<p>PDE provides a <strong>Plug-in Export</strong> wizard to export plug-ins and fragments into a form that is suitable for deployment. The wizard shields you from Ant scripts and does not pollute your workspace with resources generated during the build operation. The wizard is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.pde.ui.pluginExportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the plugin export wizard">
-<strong>File &gt; Export... &gt; Plug-in Development &gt; Deployable plug-ins and fragments</strong>
-</a>. </p>
- 
-<h2>Plug-in Selection </h2>
-<p>The wizard displays all the non-binary plug-ins found in the workspace. </p>
-<p><img src="../../images/export_wizards/plugin_available.png" alt="Plug-ins" ></p>
-<p>Select the plug-ins that you want to export. If you find yourself exporting the same set of plug-ins over and over, you can press <strong>Working Set...</strong> to define a <em>plug-in working set</em>. </p>
-
-<h2>Destination</h2>
-<p>You can choose to export the plug-ins to a directory or to a ZIP archive.  You can also choose to export the plug-ins in a runnable format and have them installed into your currently running Eclipse host.</p>
-<p><img src="../../images/export_wizards/destination.png" alt="Destination" ></p>
-<p>If you choose to export to a <strong>Directory</strong> (the default), the plug-ins will be placed in a <em>plugins/</em> subdirectory of the chosen directory.</p>
-<p>If you choose to export to an <strong>Archive File</strong>, all the plug-ins will be packaged in a single ZIP archive. The directory structure inside the ZIP also starts with <em>plugins/</em> at its root. </p>
-<p>If you choose to export and <strong>Install</strong> the plug-ins will be exported in a runnable format and a p2 repository will be generated.  After the export completes, an installation operation will run to install the plug-ins.  You will be prompted to restart Eclipse when the installation completes.  To uninstall your plug-ins you must use the <strong>Installation Details</strong> button on the About Dialog (available by going to Help &gt; About Eclipse SDK). For more details see <a href="../../../tasks/ui_export_install_into_host.htm">Exporting and Installing into the Host</a></p>  
-
-<h2>Options</h2>
-<p><img src="../../images/export_wizards/options_plugins.png" alt="Options" ></p>
-<p>The <strong>Export source</strong> option results in the exporting of source code as well as binaries.  There are two ways to package source with your exported plug-in.  The <em>Generated Source Bundles</em> option will add the ant commands to the export to create separate source bundles for each of the exported plug-ins.  For more information on source bundles see the PDE Build entry on <a href="../../../tasks/pde_individual_source.htm">Individual Source Bundles</a>.  The second option is to <em>Include source in exported plug-ins</em>.  This option will package the source files in a <em>src/</em> folder at the root of the JAR (if exporting in a JAR format). If the plug-in is packaged as a flat directory, the source code will be placed in a source ZIP inside the plug-in directory as a sibling to the library JAR.</p>
-
-<p>The <strong>Package plug-ins as individual JAR archives</strong> option packages each plug-in as a JAR. This option is recommended for plug-ins whose code is stored at the root (i.e. plug-ins that have no <em>MANIFEST.MF</em> <strong>Bundle-ClassPath</strong> header or the header is of the form <strong>Bundle-ClassPath: .</strong>). Nested JARs are strongly discouraged as they hinder performance; since, the runtime will have to extract these JARs at runtime. Therefore, if the plug-in's code is packaged in a JAR, it is recommended to keep the deployed plug-in as a flat directory.</p>
-
-<p>The <strong>Qualifier replacement</strong> option enables you to substitute a value for the qualifier element in a plug-in's version.  The plug-ins version must be in the following format: &lt;<em>major</em>&gt;.&lt;<em>minor</em>&gt;.&lt;<em>micro</em>&gt;.qualifier.  For example: 3.3.0.qualifier. Normally, the qualifier represents a build date or identifier.</p>
-<p>The <strong>Save as Ant script</strong> option lets you save the settings of the export operation so that it can be re-executed at a later time without having to go through the wizard again. Like the export operation, the Ant task runs as an asynchronous job; therefore, it may not be suitable to incorporate it as a part of a larger Ant script. </p>
-
-<p>The <strong>Save as Ant script</strong> option lets you save the settings of the export operation so that it can be re-executed at a later time without having to go through the wizard again. Like the export operation, the Ant task runs as an asynchronous job; therefore, it may not be suitable to incorporate it as a part of a larger Ant script. </p>
-
-<p> <strong>Allow binary cycles in target platform</strong> is an option that controls how the export operation deals with cycles in the dependency graph for a plug-in.  PDE Build cannot compile if a cycle is detected.  However, if a cycle only contains binary plug-ins from the target platform, turning on this option will allow PDE Build to continue.</p>
-
-<p> If the <strong>Use class files compiled in the workspace</strong> option is turned on, rather than compiling files as part of the export operation, the binary files in the workspace that were compiled by Eclipse are used.  This should improve performance as it skips the compilation phase, but your workspace must have successfully compiled</p>
-
-<h2>JAR Signing </h2>
-<p>The <strong>JAR Signing</strong> tab is only available when the <strong>Package as individual JAR archives</strong> option is selected on the <strong>Options</strong> tab. </p>
-<p><img src="../../images/export_wizards/jar_signing.png" alt="JAR Signing" ></p>
-<p>To sign the JARs, <em><strong>you must be running Eclipse with a full JDK, rather than just a JRE. </strong></em></p>
-<p>The <strong>Keystore location</strong>, <strong>Keypass</strong>, <strong>Alias</strong> and <strong>Password</strong> fields are all required  for the signing operation.</p>
-
-<br>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="export_wizards.htm">Export Wizards</a><br>
-<a href="export_features.htm">Feature Export Wizard</a>
-</p>
-<p><img src="../../../images/ngrelt.png" alt="Related tasks" border="0"></p>
-<p>
-<a href="../../../tasks/ui_export_install_into_host.htm">Export and Install into the Running Host</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm
deleted file mode 100644
index 86b136e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Product Export</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Export</h1>
-<p>PDE provides an <strong>Eclipse Product Export</strong> wizard to export an Eclipse product defined in a <em>product configuration</em>. The wizard shields you from Ant scripts and does not pollute your workspace with resources generated during the build operation. The wizard is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.pde.ui.productExportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the product export wizard">
-<strong>File &gt; Export... &gt; Plug-in Development &gt; Eclipse Product</strong>
-</a>.</p>
-<p><img src="../../images/export_wizards/product.png" alt="Product Export" ></p>
-
-<h2>Product Configuration</h2>
-<p>The <em>Eclipse Product</em> export  wizard is centered around the <a href="../file_wizards/new_product_config.htm">product configuration</a>, which encapsulates all the data that the wizard needs to build the plug-ins and features and generate all the configuration files that are necessary to run the product. </p>
-<p>The <strong>Browse...</strong> button lets you browse through all of the available <em>.product</em> files in the workspace and select the <em>product configuration</em> that will define the product's build process. </p>
-<p>The <strong>Root directory</strong> is the name of the top-level directory of the packaged product. It is set to <em>eclipse</em> by default; however, it can be changed to any name - including names with more than one segment. For example, if the root directory is set to <em>rcp/product</em>, then the product executable and the <em>plugins/</em> directory will be placed in a <em>rcp/product</em> directory. </p>
-
-<h2>Synchronization</h2>
-<p>PDE uses the product configuration only to help create and customize the product. In order for certain types of data stored in the product configuration to take effect at runtime (e.g. window images, the <em>About dialog</em> image and text, etc.), corresponding properties must be written to the <em>org.eclipse.core.runtime.products</em> extension in the product's defining plug-in manifest file. </p>
-<p>The <strong>Synchronize before exporting</strong> option ensures that the plug-in manifest files are always up-to-date (the option is <em>on</em> by default).</p>
-
-<h2>Destination</h2>
-<p>The default option is to export a <strong>Directory</strong>. The product's <strong>Root directory</strong> is stored directly in the specified directory. </p>
-<p>When the option to export to an <strong>Archive file</strong> is selected, the product is packaged in a ZIP archive. </p>
-
-<h2>Source Code </h2>
-<p>The <strong>Include source code</strong> option results in the exporting of source code as well as binaries. If a plug-in is packaged as a JAR, the source code will be placed in a <em>src/</em> folder at the root of the JAR. If the plug-in is packaged as a flat directory, the source code will be placed in a source ZIP inside the plug-in directory as a sibling to the library JAR.</p>
-
-<h2>P2 Metadata </h2>
-<p>The <strong>Generate metadata repository</strong> option allows you to also generate p2 metadata along with your exported feature.  This does not create a p2-enabled product, just the metadata which can then be used to install using p2.</p>
-
-<h2>One-Click Cross-Platform Export</h2>
-<p>The <strong>Export for multiple platforms</strong> option is only available when PDE detects that the RCP delta pack is installed in the target platform. When this option is selected, a second wizard page is available and displays a list of available platforms to export to. This list is compiled by navigating the directory structure of the installed <em>org.eclipse.platform.launchers</em> feature to retrieve the different platform combinations. </p>
-<p><img src="../../images/export_wizards/cross_platform.PNG" alt="Cross Platform Export" > </p>
-<p>In a single operation, PDE generates a product for each selected platform and places it in a directory whose name is of the form <em>&lt;os&gt;_&lt;ws&gt;_&lt;arch&gt;</em>.  The <em>os</em> variable represents the selected operating system.  The <em>ws</em> variable represents the selected windowing system.  And, the <em>arch</em> variable represents the selected processor architecture.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_wizards.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_wizards.htm
deleted file mode 100644
index d971ee0..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_wizards.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Export Wizards</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Export Wizards</h1>
-<p>PDE provides wizards that build, package and export plug-ins, fragments, features and products into a deployable format. The PDE export wizards are available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export()")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the file export wizard">
-<strong>File &gt; Export... &gt; Plug-in Development</strong>
-</a> from the top level menu.</p>
-<p><img src="../../images/export_wizards/export_wizard_select.png" alt="Export Wizards" ></p>
-<p>For details on individual export wizards, refer to the following documents:</p>
-<ul>
-  <li><a href="export_plugins.htm">Plug-in Export</a></li>
-  <li><a href="export_features.htm">Feature Export</a></li>
-  <li><a href="export_product.htm">Product Export</a></li>
-</ul>
-<p><img src="../../../images/ngrelt.png" alt="Related tasks" border="0"></p>
-<p>
-<a href="../../../tasks/ui_export_install_into_host.htm">Export and Install into the Running Host</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_category.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_category.htm
deleted file mode 100755
index 6d15602..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_category.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>New Category Definition File</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>New Category Definition File</h1>
-
-<p>This wizard allows you to create a new category file.  These files provide a set of categories and specify features that belong to each category.  When exporting, a category definition file can be provided so that the exported metadata adds the exported features to the correct category.</p>
-
-<p>The <strong>Category Definition</strong> wizard is available under 		
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewCategoryWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the product configuration wizard"><strong>File &gt; New &gt; Other... &gt; Plug-in Development &gt; Category Definition</strong></a> from the top level menu.</p>
-<p><img src="../../images/new_wizards/category_definition.png" alt="Category Definition Wizard" ></p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../editors/category_editor/definition_page.htm">Category Editor</a><br>
-<a href="../export_wizards/export_features.htm">Feature Export</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_cheat_sheet.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_cheat_sheet.htm
deleted file mode 100644
index 41ec33d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_cheat_sheet.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>New Cheat Sheet Wizard</title>
-		<link rel="STYLESHEET" href="../../book.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>New Cheat Sheet Wizard</h2>
-
-		<h3>About Cheat Sheets</h3>
-		
-		<p>
-			In general, cheat sheets help guide users through a complex set of instructions. 
-		   	There are two types of cheat sheets: simple and composite. 
-			Simple cheat sheets are used to organize and present logical steps and sub-steps 
-			to achieve a certain task.  Composite cheat sheets are used to organize and 
-			present tasks represented by simple cheat sheets to achieve a larger goal.
-		</p>
-		
-		<h3>About This Wizard</h3>
-		
-		<p>
-			This wizard allows you to create a new simple or composite cheat sheet.
-			Upon completion of this wizard, a new cheat sheet will be created with basic
-			content and opened in either the <strong>Simple Cheat Sheet Editor</strong> or 
-			<strong>Composite Cheat Sheet Editor</strong>.
-		</p>		
-
-		<p>
-			To start this wizard, click 
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewCheatSheetWizard)")'>
-    			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the user assistance cheat sheet">
-				<strong>File &gt; New &gt; Other... &gt; User Assistance &gt; Cheat Sheet</strong>
-			</a>.	
-		</p>
-
-		<p>
-			<img src="../../images/new_wizards/wizard_new_cheat-sheet.png" alt="New Cheat Sheet Wizard">
-		</p>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../editors/simple_cs_editor/editor.htm">Simple Cheat Sheet Editor</a>
-			</li>
-			<li>
-				<a href="../editors/composite_cs_editor/editor.htm">Composite Cheat Sheet Editor</a>
-			</li>
-		</ul>
-		
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_file_wizards.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_file_wizards.htm
deleted file mode 100644
index 48ef85d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_file_wizards.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>New File Creation Wizards</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>New File Creation Wizards</h1>
-<p>In addition to manifest files, several other types of files are needed in various aspects and at different stages of plug-in development:</p>
-<ul>
-  <li><strong>Extension point schemas</strong> -  specify the grammar of extension points</li>
-  <li><strong>Product configurations</strong> -  manage all the data needed to define, brand and build an Eclipse product</li>
-  <li><strong>Target definitions</strong> - define all aspects of a target platform</li>
-  <li><strong>Cheat sheets</strong> - Create a cheat sheet for an Eclipse product</li>
-  <li><strong>Help Tables of Contents</strong> - Create a Table of Contents for the documentation in an Eclipse product</li>
-  <li><strong>Category Definitions</strong> - specify categories to apply to features during export</li>
-</ul>
-<p>To help you create these files, PDE provides specialized <strong>New File</strong> creation wizards available via 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard()")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new wizard"><strong>File &gt; New &gt; Other... &gt; Plug-in Development</strong></a>
- from the top level menu. </p>
-<p><img src="../../images/new_wizards/other_category.PNG" alt="File Wizards" ></p>
-<p>For details on individual wizards, refer to the following documents:</p>
-<ul>
-  <li><a href="new_product_config.htm">Product Configuration</a></li>
-  <li><a href="new_target_definition.htm">Target Definition</a></li>
-  <li><a href="new_schema.htm">Extension Point Schema</a></li>
-  <li><a href="new_cheat_sheet.htm">Cheat Sheet</a></li>
-  <li><a href="new_toc.htm">Table of Contents</a></li>
-  <li><a href="new_category.htm">Category Definition</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_product_config.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_product_config.htm
deleted file mode 100644
index 38e32fb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_product_config.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Product Configuration</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Product Configuration</h1>
-<p>A product configuration defines and manages all aspects of an Eclipse product. This file is a development-time file supported by PDE only and is neither interpreted nor read by the runtime. </p>
-<p>The <strong>New Product Configuration</strong> wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewProductConfigurationWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the product configuration wizard"><strong>File &gt; New &gt; Other... &gt; Plug-in Development &gt; Product Configuration</strong></a> from the top level menu.</p>
-<p><img src="../../images/new_wizards/product.PNG" alt="Product Wizard" ></p>
-
-<h2>File Name and Location </h2>
-<p>The only restriction is that the product configuration must have a <em>.product</em> file extension. The product configuration can be placed in any project and any folder. The flexibility in naming the file allows you to store multiple product configurations in the same folder.</p>
-
-<h2>Initial File Content</h2>
-<p>A product configuration can be initialized in one of three ways: </p>
-<ol>
-  <li><strong>Create a configuration file with basic settings</strong>: This option should be chosen if you have not yet defined a product extension in your plug-in or if you are a novice who does not even know what a product is. With this option, you get a product configuration with minimal content which you can incrementally start to define.</li>
-  <li><strong>Use an existing product</strong>: This option should be chosen if you have already defined an org.eclipse.core.runtime.products extension in one of your plug-in and you would like to build and package the product. PDE will use all the settings already defined in the product extension (e.g. product ID, application ID, window images, etc.) to pre-populate the product configuration.</li>
-  <li><strong>Use a launch configuration</strong>: This option should be chosen if you already have a launch configuration that contains all the settings you want in your product (e.g. product ID, list of plug-ins, program and VM arguments, etc.). PDE will use all the launch configuration settings to pre-populate the product configuration. </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_schema.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_schema.htm
deleted file mode 100644
index 8dbebd5..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_schema.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Extension Point Schema</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Extension Point Schema</h1>
-<p>An extension point schema is an XML schema that defines a grammar that formally expresses elements, attributes, and types. This information can be used by tools to validate extensions or offer assistance during the creation of extensions.</p>
-<p>The <strong>New Extension Point Schema </strong>wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewSchemaFileWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new schema file wizard"><strong>File &gt; New &gt; Other... &gt; Plug-in Development &gt; Extension Point Schema </strong></a> from the top level menu.</p>
-<p><img src="../../images/new_wizards/schema.PNG" alt="Extension Point Schema wizard" ></p>
-
-<h2>Extension Point </h2>
-<p>When you create the schema, you need to specify the <strong>Extension Point Name</strong> and fully qualified ID  of the extension point that the schema is associated with (i.e. the concatenation of the <strong>Plug-in ID</strong> and <strong>Extension Point ID</strong>). </p>
-
-<h2>Schema</h2>
-<p>The <strong>Container</strong> field refers to an existing location in the workspace where the schema will be created.</p>
-<p>The <strong>Extension Point Schema</strong> field specifies the path to the schema within the specified container. The schema must have a <em>.exsd</em> file extension.</p>
-<p>Some schemas (e.g. a schema for an expression language) may be incorporated in other schemas. These schemas are designated as shared when the <strong>Create shared schema for inclusion</strong> option is selected. </p>
-<p>When checked, the <strong>Edit extension point schema when done</strong> option opens the newly created <em>.exsd</em> file in a specialized PDE schema editor. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_target_definition.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_target_definition.htm
deleted file mode 100644
index 3a611bb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_target_definition.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Target Definition</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Target Definition </h1>
-<p>A target definition specifies all aspects of a target - including its location, constituent plug-ins and environment. </p>
-<p>The <strong>New Target Definition </strong> wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewProfileWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new target definition wizard"><strong>File &gt; New &gt; Other... &gt; Plug-in Development &gt; Target Definition</strong></a>
- from the top level menu.</p>
-<p><img src="../../images/new_wizards/target.PNG" alt="Target Wizard" ></p>
-
-<h2>File Name and Location </h2>
-<p>The only restriction is that the target definition must have a <em>.target</em> file extension. The target definition can be placed in any project and any folder. The flexibility in naming the file allows you to store multiple target definitions in the same folder.</p>
-
-<h2>Initial File Content</h2>
-<p>A target definition can be initialized in one of four ways: </p>
-<ol>
-  <li><strong>Nothing</strong>: This option creates an empty target definition. </li>
-  <li><strong>Default</strong>: This option creates a minimal target definition with default settings for all sections. </li>
-  <li><strong>Current Target</strong>: This option initializes the file with the settings of the current target platform as defined on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.TargetPlatformPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the target platform preference page">
-<strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong></a> preference page. </li>
-  <li><strong>Template</strong>: This option creates a copy of an existing target definition. This option is particularly useful if you are creating a target definition that augments or slightly modifies an existing target. </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_toc.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_toc.htm
deleted file mode 100644
index a594aeb..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/file_wizards/new_toc.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-	<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-		<title>New Table of Contents Wizard</title>
-		<link rel="STYLESHEET" href="../../book.css" type="text/css">
-		<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-	</head>
-	<body>
-		<h2>New Table of Contents Wizard</h2>
-
-		<h3>About Tables of Contents</h3>
-		
-		<p>
-			Tables of contents allow you to organize your Eclipse product's contribution to on-line help.
-			A well-organized table of contents allows users to easily locate necessary documentation while working with an Eclipse product. 
-			Users of Eclipse products can view installed products' contributions to help by clicking <strong>Help &gt; Help Contents</strong>.   
-		</p>
-		
-		<h3>About This Wizard</h3>
-		
-		<p>
-			This wizard allows you to create a new table of contents.
-			Upon completion of this wizard, a new table of contents will be created with basic
-			content and opened in the <strong>Table of Contents Editor</strong>.
-		</p>
-
-		<p>
-			To start this wizard, click 
-			<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewTOCWizard)")'>
-    			<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-				<strong>File &gt; New &gt; Other... &gt; User Assistance &gt; Table of Contents</strong>
-			</a>.	
-		</p>
-
-		<p>
-			<img src="../../images/new_wizards/new_toc_wizard.png" alt="New Table of Contents Wizard">
-		</p>
-
-		<h3>Relevant Links</h3>
-
-		<ul>
-			<li>
-				<a href="../editors/toc_editor/editor.htm">Table of Contents Editor</a>
-			</li>
-		</ul>
-		
-	</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_features.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_features.htm
deleted file mode 100644
index b621429..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_features.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Feature Import</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Import </h1>
-<p>PDE provides a <strong>Feature Import</strong> wizard to import features from the file system into the workspace. The wizard is available  under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.pde.ui.FeatureImportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the feature import wizard"><strong>File &gt; Import... &gt; Plug-in Development &gt; Features</strong></a> from the top level menu.</p>
-<p><img src="../../images/import_wizards/feature_import.png" alt="Feature Import" ></p>
-
-<h2>Import Location </h2>
-<p>By default, the location to import features from is the target platform as specified on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.TargetPlatformPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the target platform preference page">
-<strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong></a> preference page. </p>
-<p>The <strong>Target Platform...</strong> button is a shortcut that opens the <strong>Target Platform</strong> preference page for inspection or modification.</p>
-<p>If you choose to import features from an arbitrary location on the file system and you do not wish to change the location of the target platform in the preferences, uncheck the <strong>Choose from features in the target platform</strong> checkbox.  Then, use the <strong>Browse...</strong> button to navigate and enter the directory of choice.
-Finally, make sure to press the <strong>Reload</strong> button to refresh the dialog.</p>
-
-<h2>Import Format and Destination </h2>
-<p>When features are imported, a project is created in the workspace for each feature. The project name is the concatenation of the feature ID and &quot;<em>-feature</em>&quot;.</p>
-<p>If PDE detects that your workspace is set up for feature-based self-hosting (as detailed in the <a href="../../../tips/pde_tips.htm">Tips and Tricks</a> section), the  features will be imported into a <em>features/</em> directory that is a sibling of the <em>plugins/</em> directory where the workspace is located. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_plugins.htm
deleted file mode 100644
index 4dcb231..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_plugins.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Plug-in Import</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Import </h1>
-<p>PDE provides a <strong>Plug-in Import</strong> wizard to import plug-ins and fragments from the file system into the workspace. The wizard is available  under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.pde.ui.PluginImportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the plug-in import wizard"><strong>File &gt; Import... &gt; Plug-in Development &gt; Plug-ins</strong></a> from the top level menu.</p>
-<p><img src="../../images/import_wizards/plugin_import.png" alt="Plug-in Import" ></p>
-
-<h2>Import Location </h2>
-<p>The plug-ins can be imported from one of three locations. </p>
-<ol>
-  <li><strong>The active target platform (as specified in the Preferences)</strong>:
-By default, the location to import plug-ins from is the active target platform as specified on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.TargetPlatformPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the target platform preference page">
-<strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong></a> preference page. </li>
-
-<li><strong>Target definition</strong>:
-You can select this option to import plug-ins from a different target definition. Use the drop-down box to select the target definition of choice.
-The <strong>Target Definitions...</strong> button is a shortcut that opens the <strong>Target Platform</strong> preference page for inspection or modification. </li>
-<li><strong>Directory</strong>:
-Select this option if you choose to import plug-ins from an arbitrary location on the file system and you do not wish to change the location of the target platform in the preferences. Then, use the <strong>Browse...</strong> button to navigate and enter the directory of choice. </li>
-</ol>
-
-<h2>Plug-ins and Fragments to Import </h2>
-<p>The <strong>Select from all plug-ins and fragments found at the specified location</strong> option takes you to a second wizard page that lets you browse all plug-ins and choose a subset to import. </p>
-<p><img src="../../images/import_wizards/import_from_all.PNG" alt="Import From All" ></p>
-
-<p>The <strong>Import plug-ins and fragments required by existing workspace plug-ins</strong> option is useful when you are importing all pre-requisites for a plug-in that is not part of the target platform. This option takes you to a second wizard page that is simpler; but, provides less overall control over what gets imported.</p>
-<p><img src="../../images/import_wizards/plugin_import_for_existing.PNG" alt="Import For Existing" ></p>
-
-<h2>Import Format </h2>
-<p>When plug-ins are imported, a project is created in the workspace for each plug-in. The project has the same name as the ID of the plug-in being imported. </p>
-<p>As for the content of each project, it varies by import format: </p>
-<ol>
-  <li><strong>Binary projects</strong>: The plug-in content is copied into the project. The binary code remains intact in a JAR; while, the manifest files and other resources are extracted to the project root. The advantage of binary projects is that they allow you to browse the code without the overhead of compiling the source code. </li>
-  <li><strong>Binary projects with linked content</strong>: The plug-in content is not copied into the project. Instead, links are created in the project to map to the actual physical location of the JARs, files and folders on disk. The advantage of this type of import over a regular binary import is that it is faster to import; since, the operation only involves creating links. The disadvantage of this approach is that linked binary projects can become out of sync and have to be re-imported if the absolute path to these linked files are changed in the file system. </li>
-  <li><strong>Projects with source folders</strong>: The source code for the plug-ins being imported gets extracted and placed in source folders. The advantage of this type of import is that you will be able to modify the imported source code. The disadvantage of this approach is that the code gets compiled and results in an overhead whose magnitude is proportional to the number and size of plug-ins imported. </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_wizards.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_wizards.htm
deleted file mode 100644
index b559757..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/import_wizards/import_wizards.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Import Wizards</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Import Wizards</h1>
-<p>PDE provides wizards that import plug-ins, fragments and features from the file system into the workpace. The PDE import wizards are available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import()")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the file import wizard"><strong>File &gt; Import... &gt; Plug-in Development</strong></a> from the top level menu.</p>
-<p><img src="../../images/import_wizards/import_categories.png" alt="Export Wizards" ></p>
-<p>For details on individual import wizards, refer to the following documents:</p>
-<ul>
-  <li><a href="import_plugins.htm">Plug-in Import </a></li>
-  <li><a href="import_features.htm">Feature Import</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/common.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/common.htm
deleted file mode 100644
index 20ac45a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/common.htm
+++ /dev/null

@@ -1,21 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Common Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Common Tab</h1>
-<p>The <strong>Common Tab</strong> is a tab that is available to all PDE and Java launch configurations.  It defines general aspects of the launch configuration including storage location, console encoding, etc. </p>
-<p><img src="../../images/launchers/launcher_eclipse_common.png" alt="Common Tab" ></p>
-
-<h2>Storage Location</h2>
-<p>A launch configuration is saved as an XML <em>.launch</em> file on disk. By default, this file is saved in the <em>${workspace_loc}/.metadata/.plugins/org.eclipse.debug.core/.launches</em> directory, where <em>${workspace_loc}</em> denotes the workspace location. </p>
-<p>If you want to share a launch configuration with team members, you have the option to save it as a <strong>Shared file</strong> in one of your workspace projects (in order to make it visible for version control).</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/configuration.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/configuration.htm
deleted file mode 100644
index ec294b4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/configuration.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Configuration Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Configuration Tab</h1>
-<p>The <strong>Configuration Tab</strong> is an advanced tab that lets you override the default configuration area location and the <em>config.ini</em> file content of the runtime Eclipse application you are testing. </p>
-<h1><img src="../../images/launchers/launcher_eclipse_configuration.png" alt="Configuration tab" > </h1>
-
-<h2>Configuration Area</h2>
-<p>Every Eclipse application instance has a unique configuration area which contains metadata, caches and configuration files read by the runtime and <em>Update Manager</em> upon startup.</p>
-<p>Typically, the location of the configuration is not important; therefore, PDE generates a unique configuration area for every launch in its own metadata area. This configuration area is deleted when the launch configuration is deleted.</p>
-<p>If desired, a user can set the location of the configuration area. Variables in the directory path are supported; thus, allowing launch configurations to be sharable among team members.</p>
-<p>There is also an option to <strong>Clear the configuration area before launching</strong>, which is useful for testing how plug-ins cache data in that area. </p>
-
-<h2>Configuration File</h2>
-<p> Upon startup, the runtime reads a configuration file named <em>config.ini</em> located in a <em>configuration/</em> subdirectory of the configuration area associated with the Eclipse application instance. This file is a standard properties file that can configure many aspects of the runtime. For a full list of the supported properties, refer to the <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse runtime options</a> document.</p>
-<p>The <strong>Generate a config.ini file with default content</strong> is the default option and is recommended unless you have some very specific needs.  When this option is selected, PDE generates a <em>config.ini</em> file with the following properties:</p>
-<ul>
-  <li><strong>osgi.bundles</strong> - lists all the bundles that should be installed and optionally started once the system is up and running. This list is based on the <em>osgi.bundles</em> key found in the <em>${target_home}/configuration/config.ini</em> file.  (Note, the ${target_home} variable is the location of the target platform).</li>
-  <li><strong>osgi.bundles.defaultStartLevel</strong> - denotes the default OSGi start level at which a bundle should start.  The default value is set to <strong>4</strong></li>
-  <li><strong>osgi.configuration.cascaded</strong> - indicates whether this configuration is standalone or has a parent configuration to cascade up to.  The default value is set to false.</li>
-  <li><strong>osgi.framework</strong> - specifies the URL location of the <em>org.eclipse.osgi</em> plug-in</li>
-  <li><strong>osgi.install.area</strong> - specifies the location of the target platform. </li>
-  <li><strong>osgi.splashPath</strong> - specifies one or more locations of the splash screen.</li>
-</ul>
-<p>The <strong>Use an existing <em>config.ini</em> file as a template</strong> option takes an existing <em>config.ini</em> file and makes a copy of it. PDE neither adds nor removes properties from this file. However, PDE modifies the <strong>osgi.bundles</strong> and <strong>osgi.splashPath</strong> keys by substituting their generic bundle URL values with absolute paths that reflect the actual locations of the bundles on disk.</p>
-<br>
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_application_launcher.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_application_launcher.htm
deleted file mode 100644
index 517254d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_application_launcher.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Eclipse Application Launcher</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Eclipse Application Launcher</h1>
-<p>PDE provides an <em>Eclipse Application</em> launcher which allows you to run and debug your plug-in by launching a separate Eclipse application. As with all other launchers in Eclipse (e.g. the <em>Java Application</em> and <em>Java Applet</em> launchers,...), the <em>Eclipse Application</em> launcher can be invoked via a shortcut and its launch configurations are centrally managed in the <strong>Launch Configuration Dialog</strong>. </p>
-
-<h2>Launching via a Shortcut</h2>
-<p>A quick way to test a plug-in is by launching a separate application via <strong>Eclipse Application</strong> launch shortcuts that are available as: </p>
-<ul>
-  <li> hot links in the <a href="../editors/manifest_editor/testing.htm">Testing</a> section of the plug-in manifest editor's <strong>Overview</strong> page</li>
-  <li>actions in the <strong>Run As &gt; </strong>and <strong>Debug As &gt;</strong> context menus of plug-in projects </li>
-</ul>
-<p>Launch shortcuts are context-sensitive. If the selected resource is a plug-in project or plug-in manifest editor that declares an application (an <em>org.eclipse.core.runtime.applications</em> extension) or a product (an <em>org.eclipse.core.runtime.products</em> extension), then PDE launches that application or product. The set of plug-ins PDE launches with is a minimal set made up of the selected plug-in and all its pre-requisites only. If the selected plug-in contains both a product extension and an application extension, the product extension takes precedence. </p>
-<p>If the selected plug-in does not contain either a product extension or an application extension, PDE launches the default product as defined in the <strong>eclipse.product</strong> key of the <em>config.ini</em> file that is located in the <em>${target_home}/configuration</em> directory.  ${target_home} refers to the location of the target platform as specified on the <strong>Windows &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong> preference page. If the default product is launched, the set of plug-ins used in the launch are all the workspace plug-ins and all the plug-ins that are checked on the <strong>Target Platform </strong>preference page. Target plug-ins whose ID conflict with the ID of a workspace plug-in are not included in the launch configuration. </p>
-<p>PDE creates a new <em>Eclipse Application</em> launch configuration and pre-configures it with reasonable defaults.  This is done <em>only when needed</em> - not every time an <em>Eclipse Application</em> launch shortcut is invoked. PDE searches existing <em>Eclipse Application</em> launch configurations first and reuses one that is already associated with the product or application being launched. If there are multiple existing launch configurations associated with the product or application being launched, PDE displays a dialog containing all matching launch configurations and lets the user decide. </p>
-
-<h2>Customizing a Launch Configuration</h2>
-<p>If you require full control over how to launch your Eclipse application, you can create and customize a launch configuration in the <strong>Launch Configuration Dialog</strong>.</p>
-<p>The <strong>Launch Configuration Dialog</strong> can be invoked via <strong>Run &gt; Run...</strong> or <strong>Debug &gt; Debug...</strong> from the top level menu.    A new <em>Eclipse Application</em> launch configuration can be created by double-clicking on the <strong>Eclipse Application</strong> node in the tree viewer to the left. </p>
-<p>An <em>Eclipse Application</em> launch configuration contains seven tabs allowing you to customize all aspects of the test launch. Refer to the following documents for more details: </p>
-<ul>
-  <li><a href="eclipse_main.htm">Main Tab</a></li>
-  <li><a href="eclipse_args.htm">Arguments Tab</a></li>
-  <li><a href="eclipse_plugins.htm">Plug-ins Tab</a></li>
-  <li><a href="configuration.htm">Configuration Tab</a></li>
-  <li><a href="tracing.htm">Tracing Tab</a></li>
-  <li><a href="environment.htm">Environment Tab</a></li>
-  <li><a href="common.htm">Common Tab</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_args.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_args.htm
deleted file mode 100644
index f79c3a7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_args.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Arguments Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Arguments Tab</h1>
-<p>You can easily test your plug-in under different conditions by customizing the launching program and VM arguments on the <strong>Arguments Tab</strong>. </p>
-<p><img src="../../images/launchers/launcher_eclipse_arguments.png" alt="Arguments" > </p>
-
-<h2>Program and VM Arguments</h2>
-<p><strong>Program arguments</strong> are application-specific values that the application code expects and processes. For example, the <em>-debug</em> argument puts the platform in debug mode and enables tracing, while the <em>-nl fr </em>arguments launch the application in a French locale.</p>
-<p><strong>VM arguments</strong> are typically values that change the behaviour of the <em>Java Virtual Machine</em> (JVM). For example, the <em>-Xmx256M</em> argument allows the Java heap to grow to 256MB. </p>
-<p>The Eclipse runtime is also configurable via many system properties which can be passed as VM arguments in the form: <em>-DpropertyName=propertyValue</em>. For example, <em>-Dosgi.clean=true</em> clears all data cached by the OSGi framework and the Eclipse runtime. </p>
-<p>For a list of the program and VM arguments supported by the Eclipse runtime, refer to the following documents: </p>
-<ul>
-  <li><a href="../../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">Running Eclipse</a></li>
-  <li><a href="../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse Runtime Options </a></li>
-</ul>
-<p>If you would like the same set of program and VM arguments to be used for all your launch configurations, it is recommended that you use the <a href="../target_shared/edit_target_arguments_tab.htm">Launching Arguments</a> setting when editing your <a href="../../../concepts/target.htm">Target Platform</a> to create a template that gets propagated into all newly-created launch configurations. </p>
-
-<h2>Working Directory</h2>
-<p>The <strong>Working Directory</strong> specifies the directory in which the runtime Eclipse application executes (e.g. read and write files into the working directory, etc.). By default, the working directory is the root directory of the Eclipse installation; but, it can be configured by the user to be any writable directory they wish. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_main.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_main.htm
deleted file mode 100644
index b7a446a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_main.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Main Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Main Tab</h1>
-<p>The <strong>Main Tab</strong> allows you to customize important settings of the launch configuration, including the location of the runtime workspace, the program to run and the Java runtime environment in which the program will run. </p>
-<p><img src="../../images/launchers/launcher_eclipse_main.png" alt="Main Tab" ></p>
-
-<h2>Workspace Data</h2>
-<p>The<strong> Workspace Data</strong> location is the directory on disk that will contain all the work and metadata (e.g. preferences, etc.) for the runtime Eclipse application. This location must, of course, be different than the location of your host workspace since you should be testing your plug-in in a sandbox. </p>
-<p>By default, the location of the runtime workspace is set by PDE to have a unique name based on the launch configuration name and to be a sibling of the host workspace directory. You can set the location of the runtime workspace to be anywhere you like as long as the location is writable. Variable names can be used in the path to the runtime workspace location, thus allowing launch configuration to be sharable among team members. </p>
-<p>The <strong>Clear</strong> option is useful if you want to test your plug-in in a fresh workspace or with a clean log file. This option is turned off by default, because Eclipse application workspaces typically contain useful data that does not need to be cleared from one launch to the next.</p>
-<p>The <strong>Ask for confirmation before clearing</strong> option prompts the user before deleting the runtime workspace data. This option is turned on by default to prevent accidental loss of data from the test workspace. </p>
-
-<h2>Program To Run</h2>
-<p>The <strong>Program to Run</strong> section is where you specify the product or application to test. </p>
-<p>The product combo box is populated with the IDs of all products (<em>org.eclipse.core.runtime.products</em> extensions) defined in the workspace and target plug-ins. The product ID that is initially selected is the default product as specified by the <strong>eclipse.product</strong> key in the config.ini file that is located in the <em>${target_home}/configuration</em> directory.  The ${target_home} variable refers to the location of the target platform as specified on the <strong>Windows &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong> preference page. In the Eclipse SDK, the default product ID is <em>org.eclipse.sdk.ide</em>.</p>
-<p>The application combo box is populated with the IDs of all applications (<em>org.eclipse.core.runtime.applications</em> extensions) defined in the workspace and target plug-ins. The application ID that is initially selected is the default application as specified by the <strong>eclipse.application</strong> key in the config.ini file that is located in the <em>${target_home}/configuration</em> directory. In the Eclipse SDK, the default application ID is <em>org.eclipse.ui.ide.workbench</em>. </p>
-<p>The <strong>Run a product</strong> option is selected by default, because testing a product (a branded application) makes for a richer experience than testing a plain application. </p>
-
-<h2>Java Executable</h2>
-<p>The <strong>Java Executable</strong> option allows you to specify the executable to run the Eclipse Application with.  For example, on <em>Windows</em> you can override the default executable, <em>javaw.exe</em>, with <em>java.exe</em> if desired.
-</p>
-<h2>Java Runtime Environment</h2>
-<p>You can test your plug-in against the <em>Java Runtime Environment</em> (JRE) of your choice; furthermore, this runtime JRE does not necessarily have to be the same JRE (with associated SDK) utilized to compile the workspace plug-ins. </p>
-<p>The <strong>Runtime JRE</strong> combo box is populated with all the JREs listed on the <strong>Windows &gt; Preferences.... &gt; Java &gt; Installed JREs</strong> preference page. You can dynamically add more JREs to the list of installed JREs by pressing the <strong>Installed JREs...</strong> button, which will open the <strong>Installed JREs</strong> preference page. </p>
-
-<h2>Bootstrap Entries</h2>
-<p>Launching the host Eclipse instance typically involves a native launcher executable, which in turn calls an <em>org.eclipse.equinox.launcher.Main</em> class to start the bootstrapping process. The <em>Main</em> class  is located in the bundle named <em>org.eclipse.equinox.launcher</em>. </p>
-<p>Launching a runtime Eclipse application bypasses the native executable and calls the <em>Main</em> class directly, as you would run any regular Java application. Therefore, PDE computes the location of the Main class and implicitly adds it to the classpath of the launch configuration.</p>
-<p>Certain profilers require some native libraries to be on the classpath of the launch configuration as well. The <strong>Bootstrap Entries</strong> field allows you to specify and append such additional locations to the classpath.</p>
-
-
-<p>For more information on running Eclipse, refer to the following documents:</p>
-<ul>
-  <li><a href="../../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">Running Eclipse</a></li>
-  <li><a href="../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse Runtime Options </a></li>
-</ul>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_plugins.htm
deleted file mode 100644
index ff53d3a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_plugins.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-ins Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-ins Tab</h1>
-<p>When testing your plug-in, you have the ability to manage and select the list of plug-ins that you want to launch with on the  <strong>Plug-ins Tab</strong> of the launch configuration. </p>
-<p><img src="../../images/launchers/launcher_eclipse_plugins.png" alt="Plug-ins tab" ></p>
-
-<h2>Launch Options </h2>
-<p>The <strong>Launch with</strong> combo box allows you to configure the way the Eclipse Application is launched. The options are explained in more detail below.</p>
-<p>The <strong>all workspace and enabled external plug-ins</strong> option is the default setting. With this option, the runtime Eclipse application you are launching will be made up of all the workspace plug-ins and all the plug-ins that are explicitly checked on the <strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong> preference page. This option requires little maintenance because the list of plug-ins is maintained by PDE and updated prior to every launch as plug-ins are created or deleted in the workspace. This option is recommended when the <strong>Program to Run</strong> setting on the <a href="eclipse_main.htm">Main tab</a> of the launch configuration is set to the <strong>default product</strong> or <strong>default application</strong> of your target. </p>
-<p>The <strong>workspace features</strong> is an advanced option that requires a special setup. It should only be used when you want to test feature lifecycles and leave Update Manager in control of your startup sequence. Refer to the <a href="../../../tips/pde_tips.htm">Tips and Tricks</a> section for details on how to set up your workspace for this option.</p>
-<p>The <strong>plug-ins selected below only</strong> option is typically used when you are testing an RCP application that uses a subset of the plug-ins from the workspace and target. This setting requires more maintenance than the other options, since you have to ensure that the list of selected plug-ins is up-to-date when you add or remove a plug-in from the workspace. There are several buttons available to help you select plug-ins, including an <strong>Add Required Plug-ins</strong> button.  The <strong>Add Required Plug-ins</strong> button should be used often to ensure the subset of plug-ins you have selected is complete. </p>
-<p>Please note that if a workspace plug-in has the same ID as a target plug-in, the workspace plug-in is used in place of its target counterpart. This behavior applies to all three plug-in selection options described above; however, you can override this option by choosing the third option, deselecting a workspace plug-in and selecting the target plug-in with the same ID. </p>
-
-<h2>Validate Plug-ins</h2>
-<p>The <strong>Validate Plug-ins</strong> functionality, which can be invoked via the button located at the bottom right corner of the <strong>Plug-ins tab</strong>, analyzes the selected set of plug-ins to find launching startup problems. For instance, missing dependencies, unsatisfied execution environments, incompatible platform filters are a few of the potential problems that may prevent your plug-in from running.</p>
-<p>By checking the <strong>Validate plug-ins automatically prior to launching</strong> option, PDE will run the <strong>Validate Plug-ins</strong> function prior to every launch. If problems are found, an error dialog will appear for you to examine and you can choose to either continue the launch without correcting the problems or cancel the launch to rectify the issues. Otherwise, if no problems are found, the launch proceeds as normal. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/environment.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/environment.htm
deleted file mode 100644
index 4f2bc6e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/environment.htm
+++ /dev/null

@@ -1,17 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Environment Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Environment Tab</h1>
-<p>The <strong>Environment Tab</strong> is a tab that is common to all PDE and Java launch configurations. It defines the environment variable values to use when running an application. By default, the environment is inherited from the Eclipse runtime. You may opt to override the environment or append to it. </p>
-<p><img src="../../images/launchers/launcher_eclipse_environment.png" alt="Environment Tab" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_args.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_args.htm
deleted file mode 100644
index 46417b7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_args.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Arguments Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Arguments Tab</h1>
-<p>You can easily test your bundle under different conditions by customizing the launching program and VM arguments on the <strong>Arguments Tab</strong>. </p>
-<p><img src="../../images/launchers/launcher_equinox_arguments.png" alt="Equinox Arguments Tab" ></p>
-
-<h2>Program and VM Arguments</h2>
-<p><strong>Program arguments</strong> are values that the <em>Equinox OSGi Framework</em> expects and processes. For example, the <em>-console</em> argument enables the <em>OSGi</em> console allowing you to execute many commands such as installing, starting and stopping bundles. The <em>-console</em> argument is added by default to all newly-created <em>Equinox OSGi Framework</em> launch configurations. </p>
-<p><strong>VM arguments</strong> are typically values that change the behaviour of the <em>Java Virtual Machine</em> (JVM). For example, the <em>-Xmx256M</em> argument allows the Java heap to grow to 256MB. </p>
-<p>The <em>Equinox OSGi Framework</em> is also configurable via many system properties which can be passed as VM arguments in the form: <em>-DpropertyName=propertyValue</em>. For example, <em>-Dosgi.clean=true</em> clears all data cached by the OSGi framework.</p>
-<p>For a list of the program and VM arguments supported by the <em>Equinox OSGi Framework</em>, refer to the following documents: </p>
-<ul>
-  <li><a href="../../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">Running Eclipse</a></li>
-  <li><a href="../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse Runtime Options </a></li>
-</ul>
-<p>If you would like the same set of program and VM arguments to be used for all your launch configurations, it is recommended that you use the <a href="../target_shared/edit_target_arguments_tab.htm">Launching Arguments</a> setting when editing your <a href="../../../concepts/target.htm">Target Platform</a> to create a template that gets propagated into all newly-created launch configurations. </p>
-
-<h2>Working Directory</h2>
-<p>The <strong>Working Directory</strong> specifies the directory in which the <em>Equinox OSGi Framework</em> executes (e.g. read and write files into the working directory, etc.). By default, the working directory is the root directory of the Eclipse installation; but, it can be configured by the user to be any writable directory they wish. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_launcher.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_launcher.htm
deleted file mode 100644
index 35d8499..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_launcher.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>OSGi Framework Launcher</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>OSGi Framework Launcher</h1>
-<p>PDE provides an <em>OSGi Framework</em> launcher, which allows you to launch an OSGi framework and test or debug your OSGi bundle. As with all other launchers in Eclipse (e.g. the <em>Java Application</em> and <em>Java Applet</em> launchers,...), the <em>OSGi Framework</em> launcher can be invoked via a shortcut, and its launch configurations are centrally managed in the <strong>Launch Configuration Dialog</strong>. </p>
-<p>Note that in Eclipse, the words <em>plug-in </em>and <em>bundle</em> are used interchangeably. <em>A plug-in is a bundle and a bundle is a plug-in</em>. </p>
-
-<h2>Launching via a Shortcut</h2>
-<p>A quick way to test a bundle is by launching an <em>OSGi Framework</em> via<strong> Run As &gt; OSGi Framework</strong> from the context menu of a plug-in project. To launch in debug mode, choose <strong>Debug As &gt; OSGi Framework</strong> from the context menu of the plug-in project.   </p>
-<p>When a shortcut is used, PDE searches for existing <em>OSGI Framework</em> launch configurations and creates a new launch configuration only if none were found. If a single launch configuration is found, it is used. If multiple configurations are found, PDE presents a selection dialog containing all existing <em>OSGi Framework</em> launch configurations and prompts the user to choose one. If a new <em>OSGi Framework</em> launch configuration is created, PDE will use the default
- <code>OSGi Framework</code> which is specified on the
- <a href="../preference_pages/osgi_frameworks.htm">OSGi Frameworks</a> preference page.
-</p>
-
-<h2>Customizing a Launch Configuration</h2>
-<p>In order to have full control over launching an <em>OSGi Framework</em>, you can create and customize a launch configuration in the <strong>Launch Configuration Dialog</strong>.</p>
-<p>The <strong>Launch Configuration Dialog</strong> can be invoked via <strong>Run &gt; Run...</strong> or <strong>Debug &gt; Debug...</strong> from the top level menu.    A new <em>OSGi Framework</em> launch configuration can be created by double-clicking on the <strong>OSGi Framework</strong> node in the tree viewer to the left. </p>
-<p>An <em>OSGi Framework</em> launch configuration contains six tabs allowing you to customize all aspects of the test launch.  Please refer to the following documents for more details: </p>
-<ul><li><a href="equinox_plugins.htm">Bundles Tab</a></li>
-  <li><a href="equinox_args.htm">Arguments Tab </a></li>
-  <li><a href="equinox_settings.htm">Settings Tab</a></li>
-  <li><a href="tracing.htm">Tracing Tab</a></li>
-  <li><a href="environment.htm">Environment Tab</a></li>
-  <li><a href="common.htm">Common Tab</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_plugins.htm
deleted file mode 100644
index d853e86..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_plugins.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Bundles Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Bundles Tab</h1>
-<p>The <strong>Bundles Tab</strong> allows you to select the bundles and their start level, which consequently allows you to customize the <strong>osgi.bundles</strong> and <strong>osgi.bundles.defaultStartLevel</strong> system properties that the launch configuration will run with. </p>
-<p><img src="../../images/launchers/launcher_equinox_plugins.png" alt="Equinox Bundles" ></p>
-
-<h2>Default Start Level</h2>
-<p>A start level is a positive integer that denotes the default OSGi start level at which a bundle will run. The <strong>default start level</strong>, which is assigned to all selected bundles, is initially set to <strong>4</strong>. This master setting can be changed directly to modify the start level of bundles <em>en masse</em>, or it can be overridden on a per-bundle basis. </p>
-
-<h2>Default Start Status</h2>
-<p>The start status indicates to the framework whether a bundle should be marked as active after it gets installed. If set to true (the default), a bundle will always be started when the framework is launched. The <strong>Default Auto-Start</strong> is a master setting that is applied to all selected bundles <em>en masse</em>, but it can be overridden on a per-bundle basis. </p>
-
-<h2>Bundle Selection</h2>
-<p>Bundles  that are to be installed by the framework upon startup must be explicitly checked on this page. By default, a bundle will be assigned the default start level and the default start status, but these values can be overridden on a per-bundle basis by selecting the bundle and editing the start level and status in-place. </p>
-<p>There are several buttons available to help you select bundles including an <STRONG>Add Required Bundles</STRONG> button.  The <strong>Add Required Bundles</strong> button should be used often to ensure the subset of bundles you have selected is complete. </p>
-<p>Please note that if a workspace bundle has the same ID as a target bundle, the workspace bundle overrides its target counterpart.  This behavior can be overridden by deselecting a workspace bundle and selecting its target counterpart. </p>
-
-<h2>Validate Bundles</h2>
-<p>The <STRONG>Validate Bundles</STRONG> functionality, which can be invoked   via the button located at the bottom right corner of the <STRONG>Bundles   tab</STRONG>, analyzes the selected set of bundles to find launching   startup problems. For instance, missing dependencies, unsatisfied execution environments,   incompatible platform filters are a few of the potential problems that may   prevent your bundle from running.</p>
-<p>By checking the <STRONG>Validate bundles automatically prior to   launching</STRONG> option, PDE will run the <strong>Validate Bundle</strong> function prior to every launch. If problems are found, a dialog showing the error comes up for you to examine and you have the option to continue the launch without correcting the problems or canceling the launch to rectify the issues. Otherwise, if no problems are found, the launch proceeds as normal. </p>
-<br>
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_settings.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_settings.htm
deleted file mode 100644
index 8b981a8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/equinox_settings.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Settings Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Settings Tab</h1>
-<p>The <strong>Setting Tab</strong> allows you to customize the Java Runtime Environment (JRE) and configuration area settings of the launch configuration. </p>
-<h1><img src="../../images/launchers/launcher_equinox_settings.png" alt="Equinox Settings" > </h1>
-
-<h2>Java Executable</h2>
-<p>The <STRONG>Java Executable</STRONG> option allows you to specify the executable to run the <em>Equinox OSGi Framework</em> with. For example, on <em>Windows</em> you can override the default executable, <em>javaw.exe</em>, with <em>java.exe</em> if desired.</p>
-
-<h2>Java Runtime Environment</h2>
-<p>You can test your bundle against the Java Runtime Environment (JRE) of your   choice; furthermore, this runtime JRE does not necessarily have to be the same JRE (with associated SDK) utilized to compile the workspace bundles. </p>
-<p>The <STRONG>Runtime JRE</STRONG> combo box is populated with all the JREs   listed on the <STRONG>Windows &gt; Preferences.... &gt; Java &gt; Installed   JREs</STRONG> preference page. You can dynamically add more JREs to the list of   installed JREs by pressing the <STRONG>Installed JREs...</STRONG> button, which   will open the <STRONG>Installed JREs</STRONG> preference page. </p>
-
-<h2>Bootstrap Entries</h2>
-<p>By default, the only entry on the launch configuration classpath is the <em>${target_home}/plugins/org.eclipse.equinox.launcher</em> JAR.  The <em>${target_home}/plugins/org.eclipse.equinox.launcher</em> JAR file houses the <em>org.eclipse.equinox.launcher.Main</em> class which contains the bootstrap code.  The <em>${target_home}</em> variable refers to the location of the target platform as specified on the <strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong> preference page. </p>
-<p> The <STRONG>Bootstrap Entries</STRONG> field   allows you to specify and append additional locations to the classpath, if required.</p>
-
-<h2>Configuration Area</h2>
-<p>Every <em>Equinox OSGi Framework</em> instance has a unique configuration area which contains metadata, caches and configuration files read by the framework and possibly other bundles. </p>
-<p>Typically, the location of the configuration is not important; therefore, PDE generates a unique configuration area for every launch in its own metadata area. This configuration   area is deleted when the launch configuration is deleted.</p>
-<p>If desired, the user can set the location of the configuration area.   Variables in the directory path are supported in order to facilitate shareable launch configurations among team members.</p>
-<p>You also have the option to <strong>Clear the configuration area before launching</strong>, which is useful for testing how bundles cache data in that area.  </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_configuration.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_configuration.htm
deleted file mode 100644
index c067864..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_configuration.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>JUnit Plug-in Configuration Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Configuration Tab</h1>
-<p>The <strong>Configuration Tab</strong> is an advanced tab that lets you override the default configuration area location and the <em>config.ini</em> file content of the runtime Eclipse application you are testing. </p>
-<h1><img src="../../images/launchers/launcher_junit_configuration.PNG" alt="JUnit Configuration" ></h1>
-
-<h2>Configuration Area</h2>
-<p>Every Eclipse application instance has a unique configuration area which contains metadata, caches and configuration files read by the runtime and <em>Update Manager</em> upon startup.</p>
-<p>Typically, the location of the configuration is not important; therefore, PDE generates a unique configuration area in its own metadata area. </p>
-<p>By default, this area is reused by all <em>JUnit Plug-in Test</em> launch configurations and deleted when the launch configuration is deleted. That is why the option to <strong>Clear the configuration area before launching</strong> is on by default. </p>
-<p>If desired, the user can set the location of the configuration area. Variables in the directory path are supported in order to make launch configurations sharable among team members.</p>
-
-<h2>Configuration File</h2>
-<p> Upon startup, the runtime reads a configuration file named <em>config.ini</em> located in a <em>configuration/</em> subdirectory of the configuration area associated with the Eclipse application instance. This file is a standard properties file that can configure many aspects of the runtime. For a full list of the supported properties, refer to the <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse runtime options</a> document.</p>
-<p>The <strong>Generate a config.ini file with default content</strong> is the default option and is recommended unless you have some very specific needs.  When this option is selected, PDE generates a <em>config.ini</em> file with the following properties:</p>
-<ul>
-    <li><strong>osgi.bundles</strong> - lists all the bundles that should be installed and optionally started once the system is up and running. This list is based on the <em>osgi.bundles</em> key found in the <em>${target_home}/configuration/config.ini</em> file.  (Note, the ${target_home} variable is the location of the target platform).</li>
-  <li><strong>osgi.bundles.defaultStartLevel</strong> - denotes the default OSGi start level at which a bundle should start.  The default value is set to <strong>4</strong></li>
-  <li><strong>osgi.configuration.cascaded</strong> - indicates whether this configuration is standalone or has a parent configuration to cascade up to.  The default value is set to false.</li>
-  <li><strong>osgi.framework</strong> - specifies the URL location of the <em>org.eclipse.osgi</em> plug-in</li>
-  <li><strong>osgi.install.area</strong> - specifies the location of the target platform. </li>
-  <li><strong>osgi.splashPath</strong> - specifies one or more locations of the splash screen.</li>
-</ul>
-<p>The <strong>Use an existing config.ini file as a template</strong> option takes an existing <em>config.ini</em> and makes a copy of it. PDE neither adds nor removes any properties from the file.  However, PDE modifies the <strong>osgi.bundles</strong> and <strong>osgi.splashPath</strong> keys by substituting their generic bundle URL values with absolute paths that reflect the actual locations of bundles on disk.</p>
-<br>
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_launcher.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_launcher.htm
deleted file mode 100644
index 9927984..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_launcher.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>JUnit Plug-in Test Launcher</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>JUnit Plug-in Test Launcher</h1>
-<p>PDE provides JUnit support for testing plug-ins by contributing a <em>JUnit Plug-in Test</em> launcher to the SDK. As with all other launchers in Eclipse (e.g. the <em>Java Application</em> and <em>Java Applet</em> launchers,...), the <em>JUnit Plug-in Test</em> launcher can be invoked via a shortcut and its launch configurations are centrally managed in the <strong>Launch Configuration Dialog</strong>. </p>
-
-<h2>UI Tests vs. Headless Tests </h2>
-<p>When a <em>JUnit Plug-in Test</em> launch configuration is launched, a lightweight PDE application is the main entry point to the runtime Eclipse instance.  If the application being tested by the user requires a user interface, the PDE application spawns the workbench for that application. Once the workbench is up, the test harness runs inside the workbench. After all tests are run, the PDE application closes the workbench and exits; thus, terminating the test run.</p>
-<p>If the tests being run do not require  a user interface (i.e. headless mode), then the lightweight PDE application runs the test without launching a workbench. After all tests are run, the PDE application exits.</p>
-<p>Refer to the <a href="junit_main.htm">Main tab</a> of the <em>JUnit Plug-in Test</em> launch configuration for details on how to run the different types of tests. </p>
-
-<h2>Launching via a Shortcut</h2>
-<p>A quick way to run a JUnit plug-in test is via the <strong>Run As &gt; JUnit Plug-in Test </strong> from the context menu of a plug-in project. To launch in debug mode, choose <strong>Debug As &gt; JUnit Plug-in Test </strong> from the context menu of the plug-in project.   These actions are also available in the context menus of source folders, packages, source files and methods inside a plug-in project. </p>
-<p>When creating a new launch configuration via a shortcut, PDE examines the dependencies of the enclosing plug-in. If the plug-in requires the <em>org.eclipse.swt</em> plug-in directly or indirectly, then the launch configuration that is created is customized to run UI tests; otherwise, the launch configuration is customized to run headless tests. </p>
-
-<h2>Customizing a Launch Configuration</h2>
-<p>In order to have full control over launching a <em>JUnit Plug-in Test</em>, you can create and customize a launch configuration in the <strong>Launch Configuration Dialog</strong>.</p>
-<p>The <strong>Launch Configuration Dialog</strong> can be invoked via <strong>Run &gt; Run...</strong> or <strong>Debug &gt; Debug...</strong> from the top level menu.    A new <em>JUnit Plug-in Test</em> launch configuration can be created by double-clicking on the <strong>JUnit Plug-in Test </strong> node in the tree viewer to the left. </p>
-<p>A <em>JUnit Plug-in Test</em> launch configuration contains eight tabs allowing you to customize all aspects of the test launch. Refer to the following documents for more details: </p>
-<ul>
-  <li><a href="junit_test.htm">Test Tab</a></li>
-  <li><a href="junit_main.htm">Main Tab  </a></li>
-  <li><a href="junit_plugins.htm">Plug-ins Tab</a></li>
-  <li><a href="eclipse_args.htm">Arguments Tab </a></li>
-  <li><a href="junit_configuration.htm">Configuration Tab </a></li>
-  <li><a href="tracing.htm">Tracing Tab</a></li>
-  <li><a href="environment.htm">Environment Tab</a></li>
-  <li><a href="common.htm">Common Tab</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_main.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_main.htm
deleted file mode 100644
index e7e8503..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_main.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Main Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Main Tab</h1>
-<p>The <strong>Main Tab</strong> allows you to customize important settings of the launch configuration, including the location of the runtime workspace, the program to run and the Java Runtime Environment (JRE). </p>
-<p><img src="../../images/launchers/launcher_junit_main.png" alt="JUnit Plug-in Main" ></p>
-
-<h2>Workspace Data</h2>
-<p>The<strong> Workspace Data</strong> location is the directory on disk that will contain all the work and metadata (e.g. preferences, etc.) for the runtime Eclipse application you are testing. This location must, of course, be different than the location of your host workspace, since you should be testing your plug-in in a sandbox. </p>
-<p>By default, the location of the runtime workspace is set by PDE to have a unique name based on the launch configuration name and to be a sibling of the host workspace directory. You can specify any location for the runtime workspace provided that the new location is writable. Variable names can be used in the path to the runtime workspace location in order to make the launch configuration sharable among team members. </p>
-<p>The <strong>Clear</strong> and <strong>Workspace</strong> options are selected by default because it is recommended to do test runs within a fresh workspace. </p>
-<p>The <strong>Ask for confirmation before clearing</strong> option prompts the user before deleting the runtime workspace data. This option is turned off by default, because the workspaces for <em>JUnit Plug-in Test</em> runs are typically not valuable. </p>
-<p>Please note that the defaults for the <strong>Clear</strong> and <strong>Ask for confirmation before clearing</strong> options in this launch configuration are opposite to the defaults on the <a href="eclipse_main.htm">Main tab</a> of a regular Eclipse Application launch configuration. </p>
-
-<h2>Program To Run</h2>
-<p>The <strong>Program to Run</strong> section is where you specify the product or application to test. </p>
-<p>The product combo box is populated with the IDs of all products (<em>org.eclipse.core.runtime.products</em> extensions) defined in the workspace and target plug-ins. The product ID that is initially selected is the default product as specified by the <strong>eclipse.product</strong> key in the <em>config.ini</em> file located in the <em>${target_home}/configuration</em> directory.  The <em>${target_home}</em> variable refers to the location of the target platform as specified on the <strong>Windows &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong> preference page. In the Eclipse SDK, the default product ID is <em>org.eclipse.sdk.ide</em>.</p>
-<p>The application combo box is populated with the IDs of all applications (<em>org.eclipse.core.runtime.applications</em> extensions) defined in the workspace and target plug-ins. The application ID that is initially selected is the default application as specified by the <strong>eclipse.application</strong> key in the <em>config.ini</em> file that is located in the <em>${target_home}/configuration directory</em>. In the Eclipse SDK, the default application ID is <em>org.eclipse.ui.ide.workbench</em>. </p>
-<p>Some tests neither require a user interface nor a workbench and can therefore be run in headless mode. The <em>JUnit Plug-in Test</em> launcher provides such a mode in the application combo box.</p>
-<p><img src="../../images/launchers/launcher_junit_headless.PNG" alt="headless" > </p>
-
-<h2>Java Executable</h2>
-<p>The <strong>Java Executable</strong> option allows you to specify the executable to run the Eclipse Application with. For example, on <em>Windows</em> you can override the default executable, <em>javaw.exe</em>, with <em>java.exe</em> if desired. </p>
-
-<h2>Java Runtime Environment</h2>
-<p>You can test your plug-in against the JRE of your choice; furthermore, this runtime JRE does not necessarily have to be the same JRE (with associated SDK) utilized to compile the workspace plug-ins. </p>
-<p>The <strong>Runtime JRE</strong> combo box is populated with all the JREs listed on the <strong>Windows &gt; Preferences.... &gt; Java &gt; Installed JREs</strong> preference page. You can dynamically add more JREs to the list of installed JREs by pressing the <strong>Installed JREs...</strong> button, which will open the <strong>Installed JREs</strong> preference page. </p>
-
-<h2>Bootstrap Entries</h2>
-<p>Launching the host Eclipse instance typically involves a native launcher executable, which in turn calls an <em>org.eclipse.equinox.launcher.Main</em> class to start the bootstrapping process. The <em>Main</em> class  is located in the bundle named <em>org.eclipse.equinox.launcher</em>. </p>
-<p>Launching a runtime Eclipse application bypasses the native executable and calls the <em>Main</em> class directly, as you would run any regular Java application. Therefore, PDE computes the location of the <em>Main</em> class and implicitly adds it to the classpath of the launch configuration.</p>
-<p>Certain profilers require some native libraries to be on the classpath of the launch configuration as well. The <strong>Bootstrap Entries</strong> field allows you to specify and append such additional locations to the classpath.</p>
-
-
-<p>For more information on running Eclipse, refer to the following documents:</p>
-<ul>
-  <li><a href="../../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">Running Eclipse</a></li>
-  <li><a href="../../../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html">Eclipse Runtime Options </a></li>
-</ul>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_plugins.htm
deleted file mode 100644
index 5f85fd2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_plugins.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>JUnit Plug-ins Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-ins Tab</h1>
-<p>When testing your plug-in, you have the ability to manage and select the list of plug-ins that you want to launch with on the <strong>Plug-ins Tab</strong> of the launch configuration. </p>
-<p><img src="../../images/launchers/launcher_junit_plugins.png" alt="JUnit Plug-ins Tab" ></p>
-
-<h2>Launch Options </h2>
-<p>The <strong>Launch with</strong> combo box allows you to configure the way the JUnit Plug-in Test is launched. The options are explained in more detail below.</p>
-<p>The <strong>all workspace and enabled external plug-ins</strong> option is the default setting. With this option, the runtime Eclipse application you are launching will be made up of all the workspace plug-ins and all the plug-ins that are explicitly checked on the <strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform</strong> preference page. This option requires little maintenance because the list of plug-ins is maintained by PDE and updated prior to every launch as plug-ins are created or deleted in the workspace. This option is recommended when the <strong>Program to Run</strong> setting on the <a href="junit_main.htm">Main tab</a> of the launch configuration is set to the <strong>default product</strong> or <strong>default application</strong> of your target. </p>
-<p>The <strong>plug-ins selected below only</strong> option is typically used when you are in <strong>headless</strong> mode or when you are testing an RCP application that uses a subset of the plug-ins from the workspace and target. This setting requires more maintenance than the other options since, you have to ensure the list of selected plug-ins is up-to-date when you add or remove a plug-in from the workspace. There are several buttons available to help you select plug-ins, including an <strong>Add Required Plug-ins</strong> button.  The <strong>Add Required Plug-ins</strong> button should be used often to ensure the subset of plug-ins you have selected is complete. </p>
-<p>Please note that if a workspace plug-in has the same ID as a target plug-in, the workspace plug-in overrides its target counterpart. This behavior can be overridden when using the second option; since, you can deselect a workspace plug-in and select its target counterpart. </p>
-
-<h2>Validate Plug-ins</h2>
-<p>The <strong>Validate Plug-ins</strong> functionality, which can be invoked via the button located at the bottom right corner of the <strong>Plug-ins tab</strong>, analyzes the selected set of plug-ins to find launching startup problems. For instance, missing dependencies, unsatisfied execution environments, incompatible platform filters are a few of the potential problems that may prevent your plug-in from running.</p>
-<p>By checking the <strong>Validate plug-ins automatically prior to launching</strong> option, PDE will run the <strong>Validate Plug-ins</strong> function prior to every launch. If problems are found, an error dialog will appear for you to examine and you can choose to either continue the launch without correcting the problems or cancel the launch to rectify the issues. Otherwise, if no problems are found, the launch proceeds as normal. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_test.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_test.htm
deleted file mode 100644
index ff37716..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/junit_test.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Test Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Test Tab</h1>
-<p>The <strong>Test Tab</strong> specifies the tests to run and the level of JUnit test runner to use. </p>
-<h1><img src="../../images/launchers/launcher_junit_test.png" alt="JUnit Plug-in Test" ></h1>
-
-<h2>Tests to Run</h2>
-<p>The <em>JUnit Plug-in Test</em> launcher allows you to run single tests or collections of tests <em>en masse</em>. </p>
-<p>If the individual test option is chosen, you have to specify the fully-qualified test class name along with the name of the plug-in project where the class is located. The launcher can give you more granularity for single tests by allowing you to choose to run a single method from within a test class.</p>
-<p>You also have the option to run all tests housed within a container (project, package or a source folder). In addition to the convenience of running an arbitrary number of test cases with a single click, this option gives you the additional flexibility of not having to update the launch configuration every time you add a test class to your suite. The list of tests is dynamically recomputed prior to every launch based on the current contents of the container. </p>
-
-<h2>Test Runner</h2>
-<p>Eclipse provides two JUnit test runners:</p>
-<ul>
-  <li><strong>JUnit 3</strong>: uses <em>JUnit 3.8.1</em>. This is the default test runner. </li>
-  <li><strong>JUnit 4</strong>:   uses <em>JUnit 4.1.0</em> and is available only if you are running Eclipse with a JRE version that is greater than or equal to 1.5.</li>
-</ul>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/tracing.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/tracing.htm
deleted file mode 100644
index 94afb1e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/launchers/tracing.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Tracing Tab</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Tracing Tab</h1>
-<p>The <strong>Tracing Tab</strong> allows you to put the platform in debug mode and enable tracing which results in debug statements printed to the console.</p>
-<p><img src="../../images/launchers/launcher_eclipse_tracing.png" alt="Tracing Tab" ></p>
-
-<h2>Tracing</h2>
-<p>The platform provides a mechanism for tracking the activity of your plug-in at runtime. It allows you to use tracing flags that will cause tracing information to be printed to the console. </p>
-<p>These flags are defined in <em>.options</em> files. These properties files must be located at the root of a plug-in and must have the following syntax:</p>
-<ul>
-  <li class="style4">&lt;plug-in ID&gt;/debug = true/false (master switch)</li>
-  <li class="style4">&lt;plug-in ID&gt;/&lt;tracing flag&gt; = &lt;value&gt; </li>
-</ul>
-<p>For example,  the <em>org.eclipse.ui.ide</em> plug-in selected  above has a <em>.options</em> file that contains three key-value pairs:</p>
-<ul>
-  <li><em>org.eclipse.ui.ide/debug</em> = <em>true</em></li>
-  <li><em>org.eclipse.ui.ide/debug/gc</em> = <em>true</em></li>
-  <li><em>org.eclipse.ui.ide/debug/internalerror/openDialog</em> = <em>true</em>  </li>
-</ul>
-<p>In your code, to check if your plug-in is in debug mode (i.e. state of the master switch), you can check the return value of <span class="style4">&lt;Activator&gt;.isDebugging()</span>, where <span class="style4">&lt;Activator&gt;</span> is the class specified in the  <strong>Bundle-Activator</strong> header of your plug-in's <em>MANIFEST.MF</em> file.</p>
-<p>Values for individual flag names can be obtained by calling <span class="style4">Platform.getDebugOption(optionName)</span>.</p>
-
-<h2>Enable Tracing </h2>
-<p>When the  <strong>Enable tracing for the selected  plug-ins</strong> option is checked, PDE launches with the <em>-debug &lt;filename&gt;</em> program argument.  The <em>&lt;filename&gt;</em> portion of the program argument is a properties file generated by PDE that contains both key-value pairs for the plug-ins you are tracing and the state of each tracing flag.</p>
-<p>Please note that toggling tracing flags on the <strong>Tracing tab</strong> does not result in the modification of the <em>.options</em> file. The tracing flag values are saved as metadata in the launch configuration itself and are copied into the master properties file that is passed to the runtime via the <em>-debug</em> argument.</p>
-<br>
-<br>
-<br>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/convert_projects.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/convert_projects.htm
deleted file mode 100644
index 7e8c31b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/convert_projects.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Converting Java Projects to Plug-in Projects</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Converting Java Projects to Plug-in Projects</h1>
-
-<p>PDE provides a <strong>Converting Java Projects to Plug-in Projects</strong>
- wizard to quickly and easily utilize PDE capabilities from a Java Project. 
- The wizard is available under the <strong>PDE Tools</strong> menu in the
- context menu of any Java Project.
-</p>
-<p>During the conversion process, PDE will add its nature and builders to the project,
- add the Plug-in Dependencies classpath container.  Finally, PDE will create a MANIFEST.MF and 
- build.properties for the project if they do not already exist.
-</p>
-
-<p><img src="../../images/pde_actions/convert_project.png" alt="Project Selection" ></p>
-
-<h3>Project Selection</h3>
-
-<p>You may select any of the open projects in your workspace which are not already
- PDE projects. 
- By default, the projects selected in the workspace are the projects
- selected for conversion by the wizard.
-</p>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/externalize_strings.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/externalize_strings.htm
deleted file mode 100644
index 8809a9c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/externalize_strings.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Externalizing Strings</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Externalizing Strings</h1>
-
-<p>PDE provides an <strong>Externalize Strings</strong> wizard to help
- externalize strings in your Manifest and plugin.xml files. 
- Externalizing manifest files extracts translatable strings and stores 
- them in a properties file for multi-language support.
- The wizard is available under the <strong>PDE Tools</strong> menu in
- the context menu of a PDE project's MANIFEST.MF or plugin.xml files.
-</p>
-
-<h3>File Selections</h3>
-
-<p><img src="../../images/pde_actions/externalize_strings_selection.png" alt="File Selections" ></p>
-
-<p>The <strong>Plug-ins with non-externalized strings</strong> table
- displays all the plug-in related files in the workspace that contain
- non-externalized strings.  The files are grouped by project, and they
- display the number of non-externalized strings in brackets. 
- You can select one or more files to externalize at one time.
-</p>
-
-<p>The text in the <strong>Localization</strong> box will be
- used to define the properties file in which the externalized
- string keys should be stored.  The file's name is created by
- adding ".properties" to the localization value.
-</p>
-
-
-
-<h3>String Substitution</h3>
-
-<p><img src="../../images/pde_actions/externalize_strings_substitution.png" alt="String Substitution" ></p>
-
-<p>After selecting a file in the <strong>Plug-ins with non-externalized strings</strong>
- table, the non-externalized strings will be displayed in the
- <strong>Strings to be externalized</strong> table. 
- Since you may not want to externalize all the strings in the
- file, you may choose which strings you wish to externalize by
- checking or unchecking strings in the table.  Click on the
- <strong>Substitution Key</strong> column to change the key name.
-</p>
-
-<p>To see the current string value in the table, select either the
- <strong>Value</strong> or <strong>Substitution Key</strong> column of a string. 
- The strings location will be highlighted and displayed in the <strong>Source</strong>
- display.
-</p> 
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/organize_manifests.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/organize_manifests.htm
deleted file mode 100644
index a33fe2e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/organize_manifests.htm
+++ /dev/null

@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Organizing Manifest Files</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Organizing Manifest Files</h1>
-
-<p>PDE provides an <strong>Organize Manifests</strong> wizard to help ensure that
- the information in your Manifest is up to date. 
- The wizard is available through the <strong>PDE Tools</strong> menu in the
- context menu of a PDE project's MANIFEST.MF or plugin.xml files.
-</p>
-
-<p><img src="../../images/pde_actions/organize_manifest.png" alt="Organize Manifest" >
-</p>
-
-<h3>Export Package Options</h3>
-<p>The <strong>Ensure that all packages appear in the MANIFEST.MF</strong> option
- will add Export-Package declarations for any package in the project which is not
- already exported.
-</p>
-
-<p>The <strong>Mark as internal all packages that match the following filter</strong>
- option can be used to modify the visibility of any Export-Package declarations in a
- project's Manifest.  The <strong>Package filter</strong> field should contain a
- regular expression used to match the names of packages that should be marked internal. 
- Packages marked as internal will not be available for use by other bundles. 
- Refer to the <a href="../editors/manifest_editor/access_rules.htm">Access Rules</a>
- document for more information on package visibility.
-</p>
-
-<p>The <strong>Remove unresolved packages</strong> option will remove any Export-Package
- entries which cannot be resolved.  There are a variety of reasons why an exported package
- cannot be resolved, but the most common reason is because it does not exist in the
- project.
-</p>
-
-<p>The <strong>Calculate 'uses' directive for public packages</strong> option will
- handle the complicated computations for the 'uses' directive for any packages that
- other bundles have access to.  Since the computations are complex and require code
- introspection, this operation may take more time than other organization operations. 
- This operation has been marked as a long-running operation.
-</p>
-
-<h3>Dependency Options</h3>
-
-<p>The <strong>Handle unresolved dependencies</strong> option allows you to clean up
- your Manifest by removing any unresolved dependencies. 
- A dependency may be unresolved for a variety of reasons, such as an optional plug-in
- being missing from the current configuration.  For this reason, you may elect to handle
- unresolved dependencies by either <strong>removing them</strong> from the Manifest or
- <strong>marking them as optional</strong>.
-</p>
-
-<p>The <strong>Remove unused dependencies</strong> option can help you identify and
- remove any unused dependencies currently defined in the Manifest. 
- Unused dependencies may require additional unnecessary bundles to be installed in a
- runtime.  This operation analyzes your project's code to check for references and
- may take more time than other organization operations.  This operation has been
- marked as a long-running operation.
-</p>
-
-<p>The <strong>Add required dependencies</strong> option inspects the project's
- code to try to add additional dependencies which are not currently included in
- the manifest. 
- This operation will only find new dependencies for bundles listed in the
- <strong>Automated Management of Dependencies</strong> section of the
- <a href="../editors/manifest_editor/dependencies.htm">Dependencies page</a> in
- the <a href="../editors/manifest_editor/editor.htm">Manifest Editor</a>. 
- This examination may take more time than other organization operations and has
- been marked as a long-running operation.
-</p>    
-
-<h3>Miscellaneous Options</h3>
-
-<p>The <strong>Remove unnecessary lazy activation headers</strong> option will
- remove lazy activation headers if a Bundle-Activator is not defined. 
- If a bundle has nothing to contribute when it is started, a lazy activation
- header is not necessary.
-</p>
-
-<p>The <strong>Delete unnecessary plug-in manifest files</strong> option will
- remove plugin.xml files if a plug-in doesn't contribute any extension or 
- extension points.
-</p>
-
-<h3>Internationalization Options</h3>
-
-<p>The <strong>Prefix icon paths in plug-in extensions with a $nl$ segment</strong>
- option will modify icon paths to allow fragments to contribute unique icons for
- different locales.
-</p>
-
-<p>The <strong>Remove unused keys from the plug-in's properties file</strong>
- option will help find and remove unused keys in the plug-in's properties file.
-</p>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/task_wizards.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/task_wizards.htm
deleted file mode 100644
index f64b57a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/task_wizards.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Task Wizards</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Task Wizards</h1>
-
-<p>PDE provides wizards that will help save you time configuring your workspace
- and developing plug-ins.  The PDE task wizards are available by selecting the
- <strong>PDE Tools</strong> submenu in the context menu.
-</p>
-
-<p><img src="../../images/pde_actions/actions_select.png" alt="Task Wizards" ></p>
-
-<p>For details on individual task wizards, please refer to the following documents:</p>
-<ul>
-  <li><a href="convert_projects.htm">Converting Java Projects to Plug-in Projects</a></li>
-  <li><a href="externalize_strings.htm">Externalizing Strings</a></li>
-  <li><a href="organize_manifests.htm">Organizing Manifest Files</a></li>
-  <li><a href="update_classpaths.htm">Updating Classpaths</a></li>
-</ul>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/update_classpaths.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/update_classpaths.htm
deleted file mode 100644
index 0a08e11..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/pde_actions/update_classpaths.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Updating Classpaths</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Updating Classpaths</h1>
-
-<p>PDE provides an <strong>Update Classpath</strong> wizard that quickly
- updates the classpaths of multiple projects.  The update will change the
- JRE and compiler settings to best match the first execution environment
- specified in each project's Manifest. 
- The wizard is available under the PDE Tools menu in the context menu of a
- Plug-in Project.
-</p>
-
-<p><img src="../../images/pde_actions/update_classpath.png" alt="Project Selection" ></p>
-
-
-
-<h3>Project Selection</h3>
-
-<p>When updating classpaths, you may select any plug-in or fragment project
- in your workspace. 
- All selected projects in your workspace will be selected in the
- <strong>Update Classpath</strong> wizard by default.
-</p>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/compilers.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/compilers.htm
deleted file mode 100644
index 1c6a19d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/compilers.htm
+++ /dev/null

@@ -1,23 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Compilers Preferences</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Compilers Preferences</h1>
-<p>PDE validates and flags potential problems on plug-in, feature and update site manifest files, as well as extension point schemas.</p>
-<p>Syntactic problems are flagged as errors, while the severity level for each potential semantic problem is customizable and can be set to <em>Error</em>, <em>Warning</em> or <em>Ignore</em>.</p>
-<p>For more information, refer to the following documents: </p>
-<ul>
-  <li><a href="plugin_compiler.htm">Plug-in Compiler Preferences</a></li>
-  <li><a href="schema_compiler.htm">Extension Point Schema Compiler Preferences</a></li>
-  <li><a href="feature_compiler.htm">Feature and Update Site Compiler Preferences  </a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm
deleted file mode 100644
index f974b11..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/editors.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Editors Preferences</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-<script type="text/javascript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-
-</head>
-
-<body>
-<h1>Editors Preferences</h1>
-<p>Syntax coloring for the source pages that are embedded in PDE editors can be customized on the 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.EditorPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the editors preference page">
-<strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Editors</strong></a>
- preference page. A <strong>Preview</strong> pane is available to show the changes made before they are applied. Changes take effect on editors only after you press <strong>Apply</strong> or <strong>OK</strong>. </p>
-
-<h2>XML Highlighting Preference </h2>
-<p>The XML Highlighting tab allows you to set the color and font for comments, constant strings, processing instructions, tags and text.</p>
-<p>To customize the font and color for each element, select the element in the the left viewer and make changes using the buttons located on the right. The Preview pane automatically updates to reflect the changes you make. </p>
-<p>This preference affects all plug-in development and user assistance editor source pages. </p>
-<p><img src="../../images/preferences/editors_xml.png" alt="XML Syntax Highlighting" ></p>
-
-<h2>MANIFEST.MF Highlighting Preference </h2>
-<p>The Manifest Highlighting tab allows you to specify the color and font for the assignment operators, attributes, directives, headers, reserved OSGi headers and attribute values.</p>
-<p>To customize the font and color for each element, select the element in the left viewer and make changes using the buttons located on the right. The Preview pane automatically updates to reflect the changes you make.</p>
-<p>The <em>MANIFEST.MF</em> source page of the plug-in editor is controlled by this preference. </p>
-<p><img src="../../images/preferences/editors_manifest.png" alt="MANIFEST.MF Syntax Highlighting" >  </p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/feature_compiler.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/feature_compiler.htm
deleted file mode 100644
index 6470d31..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/feature_compiler.htm
+++ /dev/null

@@ -1,17 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Feature and Update Site Compiler Preferences</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature and Update Site Compiler Preferences</h1>
-<p>Syntactic errors in <em>feature.xml</em> and <em>site.xml</em> files are flagged as errors by the PDE manifest compiler.</p>
-<p>Semantic problems such as references to a non-existent plug-in  or feature are flagged with a <em>Warning</em> by default. The severity level of this problem can be raised to <em>Error</em> or lowered to <em>Ignore</em>. </p>
-<h1><img src="../../images/preferences/compilers_features.png" alt="Features Compiler Options" > </h1>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/osgi_frameworks.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/osgi_frameworks.htm
deleted file mode 100644
index 1b06cfd..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/osgi_frameworks.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>OSGi Frameworks Preferences</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-<script type="text/javascript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-
-</head>
-
-<body>
-<h1>OSGi Frameworks Preferences</h1>
-
-<p>You can configure the default OSGi Framework for new
- <a href="../launchers/equinox_launcher.htm">OSGi Framework</a> launchers 
- using the
- <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.OSGiFrameworksPreferencePage)")'>
- <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the OSGi frameworks preference page">
- <strong>Window &gt; Preferences... &gt; Plug-in Development &gt; OSGi Frameworks</strong></a> preference page.
-</p>
-
-
-
-<h2>OSGi Framework Selection</h2>
-
-<p>All available OSGi Frameworks are listed in the <strong>Installed OSGi Frameworks</strong>
- table.  To contribute an OSGi Framework, the plug-in containing the framework
- implementation must contain an
- <code>org.eclipse.pde.ui.osgiFrameworks</code>
- extension.  
-</p>
-
-<p><img src="../../images/preferences/osgi_frameworks.png" alt="OSGi Framework Selection" ></p>
-
-<p>To set a framework as the default for new 
- <a href="../launchers/equinox_launcher.htm">OSGi Framework</a> launch 
- configurations, select the framework entry in the table and 
- click the <strong>Set as Default</strong> button.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plug_in_development.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plug_in_development.htm
deleted file mode 100644
index 441a2d0..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plug_in_development.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>General Plug-in Development Preferences</title>
-</head>
-
-<body>
-<h1>General Plug-in Development Preferences</h1>
-<p>The  Plug-in Development preference page provides global settings that control:</p>
-<ul>
-  <li>The presentation of plug-in and feature labels in all PDE views, editors and dialogs </li>
-  <li>The Automated Management of Dependencies workflow </li>
-</ul>
-
-<p><img src="../../images/preferences/plugin_development.png" alt="Main Preference Page" ></p>
-
-<h2>Presentation Label Preference </h2>
-<p>By default, whenever a plug-in or a feature is presented in the UI (i.e. in the outline view, Plug-ins view, editors, etc.), the label shows the plug-in or feature ID followed by the plug-in or feature version. </p>
-<p>The <strong>Presentation Label</strong> preference is a global setting that allows you to show an alternate label for plug-ins and features composed of the (translated) name of the plug-in or feature followed by the plug-in or feature version.</p>
-
-<h2>Automated Management of Dependencies Preference </h2>
-<p>With the<a href="../editors/manifest_editor/automated_management.htm"> Automated Management of Dependencies</a> workflow, it is the user's responsibility to explicitly invoke the function that analyzes the plug-in code and generates the correct dependencies for the plug-in <em>MANIFEST.MF</em> file. Neglecting to update the manifests may result in class loading errors when testing the plug-in. </p>
-<p>With the <strong>Automated Management of Dependencies</strong> preference selected, PDE checks all the manifest files in your workspace and makes necessary updates to the manifests prior to launching. This option is a great convenience, but it is off by default because it presents an overhead in the time to launch. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plugin_compiler.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plugin_compiler.htm
deleted file mode 100644
index 7bfd3c8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/plugin_compiler.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Compiler Preferences</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-<script type="text/javascript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-
-<body>
-<h1>Plug-in Compiler Preferences</h1>
-<p>Syntactic errors in <em>plugin.xml</em>, <em>fragment.xml</em> and <em>MANIFEST.MF</em> are all flagged as errors by the plug-in manifest compiler. As for semantic problems in the plug-in manifests, the severity for each problem category can be set to <em>Error</em>, <em>Warning</em> or <em>Ignore</em>. </p>
-
-<h2>Workspace vs. Project Settings </h2>
-<p>The plug-in compiler preferences are set at a workspace level on the 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.CompilersPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the compilers preference page">
-<strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Compilers</strong></a>
-preference page and take effect on all plug-in projects in the workspace. </p>
-<p>It is also possible to override the workspace-scope settings by having compiler settings at the plug-in project level. To do so, select <strong>Properties</strong> from the context menu of a plug-in project. In the <strong>Properties</strong> dialog, project-level manifest compiler settings can be customized on the <strong>Plug-in Development &gt; Plug-in Manifest Compiler</strong> preference page.</p>
-<h2>Semantic Problems </h2>
-<p>PDE validates <em>plugin.xml</em>, <em>fragment.xml</em>, <em>MANIFEST.MF</em> and <em>build.properties</em> files to flag a variety of potential problems that may prevent the plug-in from running properly. </p>
-<p>Note that some problems such as a missing plug-in ID, plug-in version, or plug-in name render a plug-in invalid. Therefore, these problems are flagged with a non-negotiable error marker and are not available for configuration on this preference page. </p>
-<p><img src="../../images/preferences/compilers_plugin.png" alt="Plug-in Compiler Options" ></p>
-<p>The following is a brief explanation for some of the non-obvious potential problems that are flagged by PDE: </p>
-<ul>
-  <li><div class="style3">Unresolved Dependencies:</div> An unresolved dependency is a dependency on a plug-in (in the <strong>Require-Bundle</strong> <em>MANIFEST.MF</em> header) or on a package (in the <strong>Import-Package</strong> <em>MANIFEST.MF</em> header) where the plug-in or package in question does not exist.</li>
-  <li><div class="style3">Incompatible Environment:</div> A plug-in or fragment has an incompatible environment if it has an <strong>Eclipse-PlatformFilter</strong> <em>MANIFEST.MF</em> header whose value is not compatible with the current Target Environment settings as they appear on the <strong>Plug-in Development &gt; Target Platform &gt; Environment</strong> preference page.</li>
-  <li><div class="style3">Unresolved Extension Points:</div> An unresolved extension point is an extension point that does not exist or whose contributing plug-in is unchecked on the <strong>Plug-in Development &gt; Target Platform</strong> preference page. Extensions contributing to such an extension point are flagged. </li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/preferences.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/preferences.htm
deleted file mode 100644
index 177fed2..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/preferences.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>PDE Preferences</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-<script type="text/javascript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-
-<body>
-<h1>Preferences</h1>
-<p>PDE provides preference pages to allow the user to control many aspects of plug-in development including the target platform, editors and manifest compiler settings.</p>
-<p>The Plug-in Development preferences can be accessed via 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.MainPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the main PDE preference page">
-<strong>Window &gt; Preferences... &gt; Plug-in Development</strong></a> from the top level menu. </p>
-<p><img src="../../images/preferences/outline.png" alt="Preferences Outline" > </p>
-<p>For details on plug-in development preferences, refer to the following documents:</p>
-<ul>
-  <li><a href="plug_in_development.htm">General Plug-in Development Preferences</a></li>
-  <li><a href="../../../reference/api-tooling/preferences/ref-baselines.htm">API Baselines</a></li>
-  <li><a href="../../../reference/api-tooling/preferences/ref-errorswarnings.htm">API Errors/Warnings</a></li>
-  <li><a href="compilers.htm">Compiler Preferences</a></li>
-  <li><a href="editors.htm">Editors Preferences</a></li>
-  <li><a href="osgi_frameworks.htm">OSGi Frameworks Preferences</a></li>
-  <li><a href="target_platform.htm">Target Platform Preferences</a></li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/schema_compiler.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/schema_compiler.htm
deleted file mode 100644
index beddc9d..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/schema_compiler.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Extension Point Schema Compiler Preferences</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Extension Point Schema Compiler Preferences</h1>
-<p>PDE validates extension point schemas and flags syntactic problems as errors. Optional features of the PDE schema builder include the real-time generation of reference documentation for schemas and the flagging of unmatched tags in the schema documentation. </p>
-
-<p><img src="../../images/preferences/compilers_schemas.png" alt="Schema Compiler Options" ></p>
-
-<h2>HTML Document Generation Preference</h2>
-<p>The <strong>HTML Document Generation</strong> preference gives the option to generate reference HTML documents from extension point  schemas as soon as the schema is modified and saved. The location where the HTML documents are to be generated is customizable with the default location being a folder named <em>doc</em> at the root of the plug-in project. </p>
-
-<h2>Unmatched Tags Preference </h2>
-<p>The documentation portions of extension point schemas allow HTML tags. Missing closing tags for those HTML tags that require it may result in badly formatted HTML documentation. The PDE builder validates the documentation sections of extension schemas and flag unmatched tags with a <em>Warning</em> by default. The severity level of this problem can be raised to <em>Error</em> or lowered to <em>Ignore</em>.</p>
-
-<p></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm
deleted file mode 100644
index d0ead67..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Target Platform Preferences</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Target Platform Preferences</h1>
-<p>The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.TargetPlatformPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the target platform preference page">
-<strong>Window &gt; Preferences... &gt; Plug-in Development &gt; Target Platform </strong></a> preference page allows you to manage a set of target definitions and select one as the active target platform.  A target definition consists of a set of plug-ins and environment settings.  The active target platform is used to build and launch your workspace plug-ins.</p>
-
-<p>The preference page will list all known target definitions.  Some target definitions will be saved with Eclipse preferences, but this page will also display target definitions found in the workspace and external definition files that have been opened in the workspace.  Definitions in the workspace will have their workspace location displayed in brown next to the name.  The target definition that is currently being used as the active target platform will be checked, marked &quot;Active&quot; and be bolded.  Change the active target platform by checking a different target definition.  Any changes made on this page, including editing of target definitions, will not be saved until <strong>OK</strong> or <strong>Apply</strong> is pressed.</p>
-
-<p><img src="../../images/preferences/target_preferences.png" alt="Target Platform Preference Page"></p>
-
-<p>The default target platform points to the Eclipse application you are currently running.  It is marked with a special Eclipse icon.  You can restore the default target platform at any time by pressing the <strong>Restore Defaults</strong> button.</p>  
-
-<p><strong>Reload</strong> can only be pressed if the active target platform is currently selected and hasn't been changed while the preference page is open.  Pressing it will force the target definition to resolve, refreshing the contents of any directory locations and downloading any out of date plug-ins in site locations.  It is helpful to reload if you have changed something in your target platform outside of Eclipse.  Any problems with the target will be displayed in a dialog.</p>
-
-<p>Press <strong>Add</strong> to create a new target definition.  The <a href="../target_shared/new_target_wizard.htm">New Target Wizard</a> will provide multiple options to create a new target.</p>
-
-<p>Press <strong>Edit</strong> to edit the selected target definition.  This will open the <a href="../target_shared/edit_target_wizard.htm">Edit Target Wizard</a> allowing you to edit all settings in the definition.  You can also double click a target definition to edit it.</p>
-
-<p>Pressing <strong>Remove</strong> will delete the selected target definitions when <strong>OK</strong> or <strong>Apply</strong> is pressed.  If you remove a target definition that is stored in your workspace, it will be deleted.</p>
-
-<p><strong>Move</strong> allows you to move a target definition stored in the Eclipse preferences to the workspace.  The <a href="../target_shared/move_target_wizard.htm">Move Target Wizard</a> will have you choose a location in your workspace and a file name ending in &quot;.target&quot;.  The new location will be displayed in grey beside the target name and will be applied when <strong>OK</strong> or <strong>Apply</strong> is pressed.</p>
-
-<p><img src="../../images/preferences/target_locations_group.png" alt="Target Locations Group"></p>
-
-<p>At the bottom of the page there is a <em>Locations</em> group.  This table will display information about the currently selected target definition.  It provides a quick way to see the contents of a target.</p>
-
-<p>For up to the minute target troubleshooting help see the <a href="http://wiki.eclipse.org/PDE/Target_Definitions">Target Definitions Wiki Page</a>.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./preferences.htm">PDE Preferences</a><br>
-<a href="../target_shared/new_target_wizard.htm">New Target Wizard</a><br>
-<a href="../target_shared/edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../target_shared/move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_content.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_content.htm
deleted file mode 100644
index 26afdf4..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_content.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Fragment Content</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Fragment Content</h1>
-<p>The <strong>Fragment Content</strong> wizard page allows you to customize the fragment properties and specify the fragment host. </p>
-<p><img src="../../images/new_wizards/fragment2.png" alt="Fragment Content" ></p>
-
-<h2>Plug-in Properties </h2>
-<p>A <strong>Fragment ID</strong> is mandatory and must comply with the   <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">plugin.dtd</a>. It is recommended - but not mandatory - for the fragment ID to match the project name.</p>
-<p>A <strong>Fragment Version</strong> is mandatory and must be of the form <em>major.minor.micro.qualifier</em> (e.g. 1.3.0).</p>
-<p>A <strong>Fragment Name</strong> is the translatable presentation name of the fragment. This field is required. </p>
-<p>A <strong>Fragment Provider</strong> is the translatable name of the fragment provider. This field is optional. </p>
-<p><strong>Execution Environment</strong> refers to the required <a href="http://wiki.eclipse.org/EE">execution environment</a> (symbolic representation of a JRE) of your plug-in. This field is optional but recommended to be set.</p>
-
-<h2>Host Plug-in</h2>
-<p>A fragment must specify a host plug-in that it will add functionality to and the host version range that it requires. </p>
-<p>The host <strong>Plug-in ID</strong>  must refer to the ID of a plug-in that already exists in the workspace or the target. </p>
-<p>The host <strong>Minimum Version</strong> and <strong>Maximum Version</strong> are of the form <em>major.minor.micro.qualifier</em>.</p>
-<br>
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_structure.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_structure.htm
deleted file mode 100644
index 0b79642..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/fragment_structure.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Fragment Project Structure</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Fragment Project Structure</h1>
-<p>The <strong>Project Structure</strong> wizard page allows you to specify the project name, location,  settings and target. </p>
-<p><img src="../../images/new_wizards/fragment1.png" alt="Fragment Structure" ></p>
-
-<h2>Project Name </h2>
-<p>When choosing a name for the fragment project, the reverse naming domain convention (e.g. com.example.abc) is recommended - but not enforced by PDE.</p>
-
-<h2>Project Location </h2>
-<p>The default location for the fragment project is a  subdirectory nested inside the workspace location. To change the location, uncheck the <strong>Use default location</strong> checkbox and enter the location of your choice.</p>
-
-<h2>Project Settings </h2>
-<p>Whether or not a fragment project should be created as a Java project depends on whether the fragment will contribute code. Fragment projects that contribute code are housed inside a Java project. Other plug-ins, such as documentation plug-ins do not contribute code and can therefore be contained in simple projects.</p>
-
-<h2>Eclipse vs. OSGi Framework </h2>
-<p>The <strong>Eclipse</strong> vs. <strong>OSGi framework</strong> choice acts as pre-filter to determine what initial pages will be visible in the plug-in manifest editor when it opens.</p>
-<p>Since the extension registry is Eclipse-specific content, the <strong>Extensions</strong> and <strong>Extension Points</strong> pages of the manifest editor are visible only when the <strong>Eclipse version</strong> option is chosen. </p>
-
-<h2>Equinox vs. Standard</h2>
-<p>When targeting an OSGi framework, you have a choice between the <strong>Equinox</strong> and <strong>standard</strong> frameworks. The Equinox OSGi framework augments the <em>MANIFEST.MF</em> content with Eclipse-specific headers (e.g. <strong>Eclipse-LazyStart</strong>) and directives (e.g. <strong>x-friends</strong>). If you do not wish to use these Eclipse-specific headers and attributes, then choose the <strong>standard</strong> option. </p>
-
-<h2>Working Sets</h2>
-<p>For convenience, plug-in projects can easily be associated with working sets which are defined in the workbench. </p>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_patch.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_patch.htm
deleted file mode 100644
index 7d417d8..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_patch.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Feature Patch</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Patch</h1>
-<p>The<strong> New Feature Patch</strong> creation  wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewFeaturePatchWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new feature patch wizard"><strong>File &gt; New &gt; Project... &gt; Plug-in Development &gt; Feature Patch</strong></a>
- from the top level menu. </p>
-<p><img src="../../images/new_wizards/feature_patch.PNG" alt="Feature Patch" ></p>
-
-<h3>Project Settings </h3>
-<p>It is recommended to use the reverse domain naming convention (e.g. com.example.patch) for the <strong>Project name</strong>. </p>
-<p>The project <strong>Location</strong> field specifies the default location as a subdirectory nested inside the workspace location. The project location can be changed to any writable location by unchecking the <strong>Use default location</strong> checkbox and entering the location of choice.</p>
-
-<h3>Feature Patch Properties </h3>
-<p>A feature <strong>Patch ID</strong> is mandatory and must comply with the <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">plugin.dtd</a>.</p>
-<p>A feature <strong>Patch Name</strong> is the translatable presentation name of the plug-in. This field is required. </p>
-<p>A feature <strong>Patch Provider</strong> is the translatable name of the feature provider. This field is optional. </p>
-<p>An <strong>Install Handler Library</strong> may be optionally associated with a feature patch if the patch needs to do specific or additional setup upon installation. Specifying an install handler library in the wizard results in the generation of a Java project; otherwise, the feature project is a simple project by default.</p>
-
-<h3>Properties of Patched Feature</h3>
-<p>The <strong>Feature ID</strong>, <strong>Feature Name</strong> and <strong>Feature Version</strong> of the feature being patched must be specified. These attributes must match those of a feature found in either the workspace or the target. </p>
-
-<h3>Feature Patch Project Structure</h3>
-<p>A feature patch has a standard feature project structure and can be edited using the PDE feature manifest editor. </p>
-<p><img src="../../images/new_wizards/feature_explorer.PNG" alt="Feature Explorer" > </p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_project.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_project.htm
deleted file mode 100644
index 85e0982..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_project.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Feature Project</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Feature Project</h1>
-<p>The<strong> New Feature Project</strong> creation  wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewFeatureProjectWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new feature project wizard"><strong>File &gt; New &gt; Project... &gt; Plug-in Development &gt; Feature Project</strong></a>
- from the top level menu. </p>
-<p>The creation of a feature project is a two-step process:</p>
-<ol>
-  <li>Define the feature properties </li>
-  <li>Select the plug-ins that make up the feature </li>
-</ol>
-
-<h3>Feature Properties </h3>
-<p>The <strong>Feature Properties</strong> wizard page allows you to specify the feature project name, location and main properties.</p>
-<p><img src="../../images/new_wizards/feature1.png" alt="Feature Properties" ></p>
-<p>It is recommended to use the reverse domain naming convention (e.g. com.example.feature) for the <strong>project name</strong>. </p>
-<p>The project <strong>Location</strong> field specifies the default location as a subdirectory nested inside the workspace location. The project location can be changed to any writable location by unchecking the <strong>Use default location</strong> checkbox and entering the location of choice.</p>
-<p>A <strong>Feature ID</strong> is mandatory and must comply with the <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">plugin.dtd</a>.</p>
-<p>A <strong>Feature Version</strong> is mandatory and must be of the form <em>major.minor.</em><em>micro.qualifier</em> (e.g. 1.3.0). </p>
-<p>A <strong>Feature Name</strong> is the translatable presentation name of the feature. This field is required. </p>
-<p>A <strong>Feature Provider</strong> is the translatable name of the feature provider. This field is optional. </p>
-<p>An <strong>Install Handler Library</strong> may be optionally associated with a feature if the feature needs to do specific or additional setup upon installation. Specifying an install handler library in the wizard results in the generation of a Java project; otherwise, the feature project is a simple project by default.</p>
-
-<h3>Plug-in Selection</h3>
-<p>The <strong>Plug-in Selection</strong> wizard page lets you select the plug-ins and fragments that make up the feature content.</p>
-<p><img src="../../images/new_wizards/feature2.PNG" alt="Plug-in Selection" >  </p>
-
-<h3>Feature Project Structure</h3>
-<p>When a feature project is created, its manifest file will open in the PDE feature manifest editor and it will have the following structure:</p>
-<p><img src="../../images/new_wizards/feature_explorer.PNG" alt="Feature Explorer" > </p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_fragment_project.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_fragment_project.htm
deleted file mode 100644
index 7386b34..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_fragment_project.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Fragment Project</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Fragment Project</h1>
-<p>The <strong>New Fragment Project</strong> creation wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewFragmentWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new fragment wizard"><strong>File &gt; New &gt; Project... &gt; Plug-in Development &gt; Fragment Project</strong></a>
- from the top level menu.</p>
-<p>The creation of a fragment project is a two-step process:</p>
-<ol>
-  <li><a href="fragment_structure.htm">Define the fragment project structure</a></li>
-  <li><a href="fragment_content.htm">Specify the fragment content</a></li>
-</ol>
-
-<p>When a new fragment project is created, its manifest file will open in the PDE plug-in manifest editor and the project structure will be similar to the following:</p>
-<p><img src="../../images/new_wizards/fragment_explorer.PNG" alt="Fragment Explorer" > </p>
-<p>If the fragment contributes extensions or extension points, the fragment project will have a <em>fragment.xml</em> file at its root.</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_plugin_project.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_plugin_project.htm
deleted file mode 100644
index d5a0792..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_plugin_project.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Plug-in Project</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Project</h1>
-<p>The <strong>New Plug-in Project</strong> creation wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewProjectWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new plug-in project wizard"><strong>File &gt; New &gt; Project... &gt; Plug-in Project</strong></a> from the top level menu. </p>
-<p>The creation of a plug-in project is a three-step process: </p>
-<ol>
-  <li><a href="plugin_structure.htm">Define the plug-in project structure</a></li>
-  <li><a href="plugin_content.htm">Specify the plug-in content</a> </li>
-  <li><a href="plugin_templates.htm">Add template extensions (optional)</a></li>
-</ol>
-
-<p>When the plug-in project is created, its manifest file will open in the PDE plug-in manifest editor and the project structure will be similar to the following:</p>
-<p><img src="../../images/new_wizards/plugin_explorer.PNG" alt="Plug-in Explorer" ></p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_project_wizards.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_project_wizards.htm
deleted file mode 100644
index aa659d7..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_project_wizards.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>New Project Creation Wizards</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>New Project Creation Wizards</h1>
-<p>During development, every plug-in, fragment, feature and update site is represented in the workspace by a single project. Each type of project is configured with special natures and builders to allow PDE to validate their manifest file(s). </p>
-<p>To help you create these projects, PDE provides new project creation wizards.  These wizards are accessible via 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard()")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the new wizard"><strong>File &gt; New &gt; Project... &gt; Plug-in Development</strong></a> from the top level menu.</p>
-<p><img src="../../images/new_wizards/new_wizards_projects.png" alt="List"></p>
-
-<p>For details on individual wizards, refer to the following documents: </p>
-<ul>
-  <li><a href="new_plugin_project.htm">Plug-in Project</a></li>
-  <li><a href="plugin_from_archives.htm">Plug-in from existing JAR archives</a></li>
-  <li><a href="new_fragment_project.htm">Fragment Project</a></li>
-  <li><a href="new_feature_project.htm">Feature Project</a></li>
-  <li><a href="new_feature_patch.htm">Feature Patch</a></li>
-  <li><a href="new_update_site_project.htm">Update Site Project</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_update_site_project.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_update_site_project.htm
deleted file mode 100644
index ce29f91..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_update_site_project.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Update Site Project</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Update Site Project </h1>
-<p>The<strong> New Update Site Project </strong> creation  wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewSiteProjectWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the New Site Project wziard"><strong>File &gt; New &gt; Project... &gt; Plug-in Development &gt; Update Site Project </strong></a>
- from the top level menu. </p>
-<p><img src="../../images/new_wizards/site.PNG" alt="Update Site Project" ></p>
-
-<h3>Project Settings </h3>
-<p>The <strong>Project Name</strong> for the update site project can be any valid directory name. </p>
-<p>The project <strong>Location</strong> field specifies the default location as a subdirectory nested inside the workspace location. The project location can be changed to any writable location by unchecking the <strong>Use default location</strong> checkbox and entering the location of choice.</p>
-
-<h3>Web Resources</h3>
-<p>The <strong>Generate a web page listing all available features within the site</strong> option generates several web files that can provide an HTML index preview of the update site contents. </p>
-<p>The default location for the <strong>Web resources location</strong> is a <em>web/ </em>folder; but, this location can be overridden by the user. </p>
-
-<h3>Update Site  Project Structure</h3>
-<p>When an update site project is created, its manifest file will open in the PDE site manifest editor. An Update site project has a <em>site.xml</em> file located at its root. If the option to create a web page is chosen in the wizard, the project will also contain a <em>web/</em> folder and an <em>index.html</em> file located at its root. </p>
-<p><img src="../../images/new_wizards/site_explorer.PNG" alt="Site Explorer" ></p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_content.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_content.htm
deleted file mode 100644
index 17e829f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_content.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Plug-in Content</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Content</h1>
-<p>The <strong>Plug-in Content</strong> wizard page allows you to customize the plug-in data. </p>
-<p><img src="../../images/new_wizards/plugin_content.PNG" alt="Plug-in Content" ></p>
-
-<h2>Plug-in Properties </h2>
-<p>A <strong>Plug-in ID</strong> is mandatory and must comply with the   <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">plugin.dtd</a>. It is recommended - but not mandatory - for the plug-in ID to match the plug-in project name.</p>
-<p>A <strong>Plug-in Version</strong> is mandatory and must be of the form <em>major.minor.micro.qualifier</em> (e.g. 1.3.0).</p>
-<p>A <strong>Plug-in Name</strong> is the translatable presentation name of the plug-in. This field is required. </p>
-<p>A <strong>Plug-in Provider</strong> is the translatable name of the plug-in provider. This field is optional. </p>
-<p><strong>Execution Environment</strong> refers to the required <a href="http://wiki.eclipse.org/EE">execution environment</a> (symbolic representation of a JRE) of your plug-in. This field is optional but recommended to be set.</p>
-
-<h2>Plug-in Options </h2>
-<p>An <strong>activator</strong> is a Java class that controls the plug-in's life cycle. It is only needed if you require to do work upon the startup or shutdown of your plug-in. </p>
-<p>The choice of whether the plug-in will make contributions to the UI affects the code generated for the activator:</p>
-<ul>
-  <li> If the plug-in is a UI plug-in, the activator class extends the <em>org.eclipse.ui.plugin.AbstractUIPlugin</em> class. </li>
-  <li>If the plug-in is headless (i.e. non-UI), the activator extends the <em>org.eclipse.core.runtime.Plugin </em>class. </li>
-  <li>If the plug-in is targeted for an OSGi framework, the activator implements the <em>org.osgi.framework.BundleActivator</em> interface. </li>
-</ul>
-<p>The choice of a UI vs. headless plug-in also controls what templates are available on the <a href="plugin_templates.htm">next wizard page</a>. </p>
-<p>Adding <strong>API Analysis</strong> to the project will enable static analysis of API usage from the new project.</p>
-
-<h2>Rich Client Application</h2>
-<p>At a minimum, a rich client application requires a plug-in with an <em>org.eclipse.core.runtime.applications</em> extension. If branding is desired, an <em>org.eclipse.core.runtime.products</em> extension is required. By answering <strong>Yes</strong> to the question in the <strong>Rich Client Application</strong> section, you will be required to go to the <a href="plugin_templates.htm">Templates</a> page where you can choose an RCP template that will generate all the required extensions.</p>
-<br>
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_from_archives.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_from_archives.htm
deleted file mode 100644
index 798243e..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_from_archives.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Plug-in From JAR Archives</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in From Existing JAR Archives</h1>
-<p>The <strong>Plug-in from existing JAR archives</strong> wizard is available under 		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewLibraryPluginProjectWizard)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Library Plug-in Project wizard"><strong>File &gt; New &gt; Project... &gt; Plug-in Development &gt; Plug-in from existing JAR archive</strong></a>
- from the top level menu. </p>
-<p>The creation of a plug-in project from existing JAR archives is a two-step process:</p>
-<ol>
-  <li>Select the JAR archives</li>
-  <li>Specify the plug-in properties</li>
-</ol>
-
-<h2>JAR Selection</h2>
-<p>The <strong>JAR Selection</strong> wizard page lists the JAR archives to be included in the plug-in. </p>
-<p><img src="../../images/new_wizards/bundlizer1.PNG" alt="JAR selection" ></p>
-<p>The <strong>Add...</strong> button opens a dialog that lets you browse the workspace for JAR archives.</p>
-<p>The <strong>Add External...</strong> button opens a file dialog that lets you browse the file system for JAR archives.</p>
-
-<h2>Plug-in Properties </h2>
-<p>The <strong>Plug-in Properties</strong> wizard page allows you to specify the plug-in project settings, plug-in properties and target platform. </p>
-<p><img src="../../images/new_wizards/bundlizer2.PNG" alt="Plug-in Content" > </p>
-<p>It is recommended to use the reverse domain naming convention (e.g. com.example.bundle) for the <strong>project name</strong>. </p>
-<p>The <strong>Location</strong> field specifies the default project location as a subdirectory nested inside the workspace location. The project location can be changed to any writable location by unchecking the <strong>Use default location</strong> checkbox and entering the location of choice.</p>
-<p>A <strong>Plug-in ID</strong> is mandatory and must comply with the <a href="../../../../org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html">plugin.dtd</a>. It is recommended - but not mandatory - for the plug-in ID to match the project name.</p>
-<p>A <strong>Plug-in Version</strong> is mandatory and must be of the form <em>major.minor.service</em> (e.g. 1.3.0).</p>
-<p>A <strong>Plug-in Name</strong> is the translatable presentation name of the plug-in. This field is required. </p>
-<p>A <strong>Plug-in Provider</strong> is the translatable name of the plug-in provider. This field is optional. </p>
-<p>You can optionally use PDE to <strong>Analyze library contents and add dependencies</strong>. 
- PDE analyzes the contents of the libraries specified on the
- <strong>Jar Selection</strong> page, looking for dependencies that may be
- required by the plug-in project.  These dependencies are then automatically
- added to the Manifest.
-</p>
-
-<h2>Target Platform </h2>
-<p>The Target Platform options are intended as a pre-filter that determines which pages of the manifest editor should be visible when the new plug-in project is created.</p>
-<p>For instance, the <strong>Extensions</strong> and <strong>Extension Points</strong> pages will be visible if the <strong>Eclipse version</strong> option is chosen but hidden if the <strong>an OSGi framework</strong> option is chosen.</p>
-<p>Also, the <strong>Package Visibility</strong> section in the <strong>Runtime</strong> page of the manifest editor will be hidden if the <strong>standard</strong> OSGi framework option is selected; since, this section offers Equinox-specific tooling.</p>
-
-<h2>Unzipping JARs</h2>
-<p>Whether the JARs should be zipped or unzipped depends on how you want to package the plug-in. If the plug-in is to be shipped as a single JAR - which is the recommended format as of Eclipse 3.1 - the individual JAR archives should be unzipped. If the plug-in is to be shipped as a flat directory, then the individual JAR archives should be left intact.</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_structure.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_structure.htm
deleted file mode 100644
index 7d6e6df..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_structure.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Plug-in Project Structure</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Project Structure</h1>
-<p>The <strong>Project Structure</strong> wizard page allows you to specify the project name, location,  settings and target. </p>
-<p><img src="../../images/new_wizards/plugin_structure.PNG" alt="Plug-in Project Structure" ></p>
-
-<h2>Project Name </h2>
-<p>When choosing a name for the plug-in project, the reverse naming domain convention (e.g. com.example.abc) is recommended - but not enforced by PDE.</p>
-
-<h2>Project Location </h2>
-<p>The default location for the plug-in project is a  subdirectory nested inside the workspace location. To change the location, uncheck the <strong>Use default location</strong> checkbox and enter the location of your choice.</p>
-
-<h2>Project Settings </h2>
-<p>Whether or not a plug-in project should be created as a Java project depends on whether the plug-in will contribute code. Most plug-ins do contribute code and should therefore be housed inside a Java project. Other plug-ins, such as documentation plug-ins do not contribute code and can therefore be contained in simple projects.</p>
-
-<h2>Eclipse vs. OSGi Framework </h2>
-<p>The <strong>Eclipse</strong> vs. <strong>OSGi framework</strong> choice controls the code generation options available on the <a href="plugin_content.htm">Plug-in Content</a> page as well as the list of <a href="plugin_templates.htm">templates</a> available. </p>
-<p>Eclipse plug-ins are OSGi bundles that use the Eclipse extension registry. Most Eclipse plug-ins use this registry; since, it is available in the runtime layer.  As a result, the <strong>Eclipse</strong> target is selected by default. </p>
-<p>If you do not intend to use the Eclipse extension registry, then you should use the <strong>OSGi framework</strong> option. If you select the <strong>OSGi framework</strong> option, you will not end up with dependencies on the runtime layer.  Moreover, PDE will restrict the available templates and the code generated for you to the OSGi layer. </p>
-
-<h2>Equinox vs. Standard</h2>
-<p>When targeting an OSGi framework, you have a choice between the <strong>Equinox</strong> and <strong>standard</strong> frameworks. The Equinox OSGi framework augments the <em>MANIFEST.MF</em> content with Eclipse-specific headers (e.g. <strong>Eclipse-LazyStart</strong>, <strong>Eclipse-PlatformFilter</strong>) and directives (e.g. <strong>x-friends</strong>). If you do not wish to use these Eclipse-specific headers and attributes, then choose the <strong>standard</strong> option. </p>
-
-<h2>Working Sets</h2>
-<p>For convenience, plug-in projects can easily be associated with working sets which are defined in the workbench. </p>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_templates.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_templates.htm
deleted file mode 100644
index e59e2ea..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/project_wizards/plugin_templates.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Templates</title>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Templates</h1>
-<p>PDE provides templates ranging in complexity and function for the platform's more popular extension points. Each template results in the generation of a fully-functional plug-in.</p>
-<p>The list of templates that you see on this wizard page varies depending on the choices you made on the <a href="plugin_structure.htm">Plug-in Structure</a> and <a href="plugin_content.htm">Plug-in Content</a> wizard pages:</p>
-<ol>
-  <li>Java vs. simple project</li>
-  <li>UI vs. headless</li>
-  <li>Rich client application vs. regular plug-in</li>
-</ol>
-<p><img src="../../images/new_wizards/plugin_templates.PNG" alt="Plug-in Templates" ></p>
-<p>Templates are customizable. For instance, the Plug-in with an editor template allows you to customize the XML editor name, class name, etc. </p>
-<p><img src="../../images/new_wizards/plugin_customize.PNG" alt="Customize Template" ></p>
-
-<h2>Contributing Templates</h2>
-<p>To contribute templates to the <strong>New Plug-in Project</strong> creation wizard, refer to the <em>org.eclipse.pde.ui.pluginContent</em> extension point. </p>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_arguments_tab.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_arguments_tab.htm
deleted file mode 100755
index 1c06cb9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_arguments_tab.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Arguments Tab</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Arguments Tab</h1>
-
-<p>The <strong>Arguments Tab</strong> in the <a href="./edit_target_wizard.htm">Edit Target Wizard</a> is used to set the default program and vm arguments for new PDE <a href="../launchers/eclipse_application_launcher.htm">launch configurations</a>.  Arguments can also be edited on the <a href="../editors/target_editor/environment_page.htm">Environment Page</a> of the <a href="../editors/target_editor/target_editor.htm">Target Editor</a>.</p>
-
-<img src="../../images/target_shared/edit_target_arguments_tab.png" alt="Arguments Tab">
-
-<p>Pressing <strong>Variables</strong> will open the <strong>Variable Selection Wizard</strong>.  You can browse through all known variables and get descriptions of what each does.  Under the <em>VM Arguments</em> group you can also press <strong>Import</strong>.  This will open the <a href="./import_arguments_dialog.htm">Import Arguments Dialog</a>.  You can use it to import vm arguments used in the configuration data of any <a href="./edit_target_locations_tab.htm">installation locations</a> you have added to your target definition.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="./edit_target_content_tab.htm">Content Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_environment_tab.htm">Environment Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_arguments_tab.htm">Arguments Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> (Edit Target Wizard)<br>
-<a href="./implicit_plugin_selection_dialog.htm">Import Variables Dialog</a><br>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="./new_target_wizard.htm">New Target Wizard</a><br>
-<a href="./move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_content_tab.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_content_tab.htm
deleted file mode 100755
index b8cc39a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_content_tab.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Content Tab</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Content Tab</h1>
-
-<p>The <strong>Content Tab</strong> in the <a href="./edit_target_wizard.htm">Edit Target Wizard</a> is used to set a subset of plug-ins to include in the target platform.  The tab displays a list of all plug-ins available in the target definition's <a href="./edit_target_locations_tab.htm">locations</a>.  Only the plug-ins checked on this tab will be included.  There are multiple ways to organize and filter the list.  The target content can also be edited on the <a href="../editors/target_editor/content_page.htm">Content Page</a> of the <a href="../editors/target_editor/target_editor.htm">Target Editor</a>.</p>
-
-<img src="../../images/target_shared/edit_target_content_tab.png" alt="Location Tab">
-
-<p><strong>Select / Deselect</strong> will check or uncheck the selected plug-ins. </p>
-
-<p><strong>Select All / Deselect All</strong> will check or uncheck all plug-ins in the target definition.</p>
-
-<p><strong>Add Required</strong> takes the set of currently checked plug-ins and determines all plug-ins required by them.  This will also include any <a href="./edit_target_implicit_tab.htm">implicit dependencies</a> set on this target.  The required plug-ins will be checked in the list.</p>
-
-<p>Use the <strong>Show</strong> options along with the filter text box at the top of the list to filter what is shown in the list.  Showing <em>plug-ins</em> will show any non-source plug-ins in the target, while showing <em>source bundles</em> will display any source.  Even if a plug-in is filtered from the list, it may be included in the target.  You can see a count of included plug-ins underneath the list.</p>
-
-<p>The <strong>Group By</strong> option is used to organize the list into different groups.  The options are:</p>
-<ol>
-<li><strong>None</strong> - No grouping, plug-ins sorted by name</li>
-<li><strong>File Path</strong> - Grouped by the directory path the plug-ins are stored in on the local file system</li>
-<li><strong>Location</strong> - Grouped by the locations set on the <a href="edit_target_locations_tab.htm">locations tab</a></li>
-</ol>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="./edit_target_locations_tab.htm">Locations Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_environment_tab.htm">Environment Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_arguments_tab.htm">Arguments Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> (Edit Target Wizard)<br>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="./new_target_wizard.htm">New Target Wizard</a><br>
-<a href="./move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_environment_tab.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_environment_tab.htm
deleted file mode 100755
index bd6e1b3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_environment_tab.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Environment Tab</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Environment Tab</h1>
-
-<p>The <strong>Environment Tab</strong> in the <a href="./edit_target_wizard.htm">Edit Target Wizard</a> is used to set environment settings that affect how a target is compiled and run.  The environment settings can also be edited on the <a href="../editors/target_editor/environment_page.htm">Environment Page</a> of the <a href="../editors/target_editor/target_editor.htm">Target Editor</a>.</p>
-
-<img src="../../images/target_shared/edit_target_environment_tab.png" alt="Environment Tab">
-
-<p>The <strong>Target Environment</strong> section has four settings that describe the system that this target is built for.  If left blank, the settings for your current running environment are used.  Changing these settings will affect how <a href="./location_edit_site_wizard.htm">Software Site Locations</a> resolve as well as how plug-ins are built and exported.</p>
-
-<p>You can specify a JRE or execution environment for this target definition in the <strong>Java Runtime Environment</strong> section.  If you specify a specific JRE or EE here, when this target is set as the active target platform, your workspace default JRE will be changed.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="./edit_target_locations_tab.htm">Locations Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_content_tab.htm">Content Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_arguments_tab.htm">Arguments Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> (Edit Target Wizard)<br>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="./new_target_wizard.htm">New Target Wizard</a><br>
-<a href="./move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_implicit_tab.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_implicit_tab.htm
deleted file mode 100755
index bb3c2ac..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_implicit_tab.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Implicit Tab</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Implicit Tab</h1>
-
-<p>The <strong>Implicit Tab</strong> in the <a href="./edit_target_wizard.htm">Edit Target Wizard</a> is used to set the implicit dependencies of the target.  Any plug-in marked as an implicit dependency will always be added as a required plug-in when PDE determines requirements.  Implicit dependencies can also be edited on the <a href="../editors/target_editor/environment_page.htm">Environment Page</a> of the <a href="../editors/target_editor/target_editor.htm">Target Editor</a>.</p>
-
-<img src="../../images/target_shared/edit_target_implicit_tab.png" alt="Location Tab">
-
-<p>Pressing <strong>Add</strong> will open the <a href="./implicit_plugin_selection_dialog.htm">Implicit Dependencies Selection Dialog</a> allowing you to select one or more plug-ins from your target platform to add as implicit dependencies.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="./edit_target_locations_tab.htm">Locations Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_content_tab.htm">Content Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_environment_tab.htm">Environment Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_arguments_tab.htm">Arguments Tab</a> (Edit Target Wizard)<br>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="./new_target_wizard.htm">New Target Wizard</a><br>
-<a href="./move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_locations_tab.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_locations_tab.htm
deleted file mode 100755
index 826b2b0..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_locations_tab.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Locations Tab</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Locations Tab</h1>
-
-<p>The <strong>Location Tab</strong> in the <a href="./edit_target_wizard.htm">Edit Target Wizard</a> is used to set the locations that provide the plug-ins included in the target definition.  There are several types of locations, allowing for definitions to be constructed in different styles.  Locations can also be edited on the <a href="../editors/target_editor/definition_page.htm">Definition Page</a> of the <a href="../editors/target_editor/target_editor.htm">Target Editor</a>.</p>
-
-<img src="../../images/target_shared/edit_target_locations_tab.png" alt="Locations Tab">
-
-<p>The locations in the target definition will be displayed in the list.  Each type of location will have a different icon and text.  If the target has been <em>resolved</em> the count of plug-ins will be displayed in blue (the number of plug-ins included from the <a href="./edit_target_content_tab.htm">Content Tab</a> and the total number of plug-ins found.  If there are problems resolving the target, they will be displayed underneath the location with the problem. The <strong>Show Plug-in Content</strong> option can be turned on to display the included plug-ins underneath each location.</p>
-
-<p>Pressing <strong >Add</strong> will open the <a href="./location_add_wizard.htm">Add Location Wizard</a>.  It will provide a choice of location types to add.  Selecting a location and pressing <strong>Edit</strong> will open a location type specific wizard to view and modify the location.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="./edit_target_content_tab.htm">Content Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_environment_tab.htm">Environment Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_arguments_tab.htm">Arguments Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> (Edit Target Wizard)<br>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_add_wizard.htm">Add Location</a><br>
-<a href="./location_edit_directory_wizard.htm">Directory Location</a><br>
-<a href="./location_edit_installation_wizard.htm">Installation Location</a><br>
-<a href="./location_add_features_wizard.htm">Add Feature Locations</a><br>
-<a href="./location_edit_feature_wizard.htm">Edit Feature Location</a><br>
-<a href="./location_edit_site_wizard.htm">Software Site Location</a><br>
-<a href="./new_target_wizard.htm">New Target Wizard</a><br>
-<a href="./move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_wizard.htm
deleted file mode 100755
index 0092d7c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/edit_target_wizard.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Edit Target Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Edit Target Wizard</h1>
-
-<p>This wizard is used to edit <a href="../../../concepts/target.htm">Target Definitions</a>.  It is opened when a target definition on the <a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a> is edited or a new definition is created.  This wizard provides the same functionality as the <a href="../editors/target_editor/target_editor.htm">Target Editor</a>.</p>
-
-<img src="../../images/target_shared/edit_target_wizard.png" alt="Edit Target Wizard">
-
-<p>The target definition can be given a name which will be used when displaying it on the <a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a>.  The other target settings are separated into tabs:</p>
-<ol>
-<li><a href="./edit_target_locations_tab.htm">Locations</a> - Provides the directories, installations and sites that will provide the plug-ins to include in the target</li>
-<li><a href="./edit_target_content_tab.htm">Content</a> - Allows a subset of the plug-ins found in the locations to be included in the target.  Numerous filtering options are provided for quick editing of the contents</li>
-<li><a href="./edit_target_environment_tab.htm">Environment</a> - Operating system, windowing system, execution environment and other environment settings that affect how your plug-ins are built and run</li>
-<li><a href="./edit_target_arguments_tab.htm">Arguments</a> - Specify the default program and vm arguments to use when launching with this target</li>
-<li><a href="./edit_target_implicit_tab.htm">Implicit Dependencies</a> - Add one or more plug-ins as implicit dependencies.  In PDE, when there is an option to add required plug-ins (such as on the Content tab of this wizard), any plug-ins marked as implicit dependencies will always be treated as required</li>
-</ol>
-<p>Pressing <strong>Finish</strong> will save the changes to the target definition and close the wizard.</p>
-
-<h2>Resolving Targets</h2>
-
-<p>Before the contents of a target can be edited and before a target definition can be set as the active target platform it must be <em>resolved</em>.  When a target definition is resolved, the definition's locations are searched for plug-ins.  Depending on the type of locations in the target, this can involved searching a directory, reading the metadata for an installation, reading a feature, or downloading from a remote site.  During resolution the Edit Target Wizard will become disabled and progress will be displayed.  You can cancel the work, however you will not be able to edit the content of the target.</p>
-
-<p>For up to the minute target troubleshooting help see the <a href="http://wiki.eclipse.org/PDE/Target_Definitions">Target Definitions Wiki Page</a>.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_locations_tab.htm">Locations Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_content_tab.htm">Content Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_environment_tab.htm">Environment Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_arguments_tab.htm">Arguments Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> (Edit Target Wizard)<br>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="./new_target_wizard.htm">New Target Wizard</a><br>
-<a href="./move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/implicit_plugin_selection_dialog.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/implicit_plugin_selection_dialog.htm
deleted file mode 100755
index 005bc31..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/implicit_plugin_selection_dialog.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Implicit Dependencies Selection Dialog</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Implicit Dependencies Selection Dialog</h1>
-
-<p>The <strong>Implicit Dependencies Selection Dialog</strong> allows you to browse through the plug-ins in your target and add one or more of them as implicit dependencies.  This dialog is opened from the <a href="./edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> or the <a href="../editors/target_editor/environment_page.htm">Environment Page</a>.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_implicit_tab.htm">Implicit Dependencies Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/environment_page.htm">Environment Page</a> (Target Editor)<br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/import_arguments_dialog.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/import_arguments_dialog.htm
deleted file mode 100755
index 8657fb3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/import_arguments_dialog.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Import Arguments</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Import Arguments</h1>
-
-<p>The <strong>Import Arguments</strong> dialog is used to copy the arguments used in installations in your target.  Often, if you have an Eclipse installation in your target that requires certain vm arguments to launch, you will require the same arguments to launch.  This dialog is accessed using the <a href="./edit_target_arguments_tab.htm">Arguments Tab</a> or the <a href="../editors/target_editor/environment_page.htm">Environment Page</a>.</p>
-
-<img src="../../images/target_shared/import_arguments_dialog.png" alt="Import Arguments">
-
-<p>To have any arguments available for import, you must have at least one installation in your <a href="./edit_target_locations_tab.htm">Locations</a> that uses vm arguments in its configuration.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="./edit_target_arguments_tab.htm">Arguments Tab</a> (Edit Target Wizard)<br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/environment_page.htm">Environment Page</a> (Target Editor)<br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_features_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_features_wizard.htm
deleted file mode 100755
index deb8ea6..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_features_wizard.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Add Feature Locations Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Add Feature Locations Wizard</h1>
-
-<p>The <strong>Add Feature Locations Wizard</strong> is opened from the <a href="./location_add_wizard.htm">Add Location Wizard</a>.  Select a folder containing features (it can also contain a folder called &quot;features&quot;).  All features found in the directory will be adde to the list.  Check the features you want to add to your target.  When <strong>Finish</strong> is pressed locations will be added to your target for each selected feature.  The plug-ins in the features will be added to your target.</p>
-
-<img src="../../images/target_shared/location_add_features.png" alt="Add Feature Locations Wizard">
-
-<p>When selecting a directory you can use the drop-down to see folders you have used previously.  You can also use variables in the path such as <em>$eclipse_home</em> to make it easier to share your target definition.</p>
-
-<p>The option underneath the list to <strong>Use specific version of the features</strong> allows for more flexibility in the versions.  When checked, the exact feature version as selected in the list will be added to the target and must always be available for the target to <em>resolve</em> correctly.  By turning this option off, the target will use the most recent version of your feature that is found in the directory.  If you change the contents of the directory the target can still <em>resolve</em> correctly as long as some version of the feature can be found.</p>
-
-<p>Once a feature has been added to the target, editing it will open the <a href="./location_edit_feature_wizard.htm">Edit Feature Location Wizard</a></p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/definition_page.htm">Definition Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_add_wizard.htm">Add Location</a><br>
-<a href="./location_edit_directory_wizard.htm">Directory Location</a><br>
-<a href="./location_edit_installation_wizard.htm">Installation Location</a><br>
-<a href="./location_edit_feature_wizard.htm">Edit Feature Location</a><br>
-<a href="./location_edit_site_wizard.htm">Software Site Location</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_wizard.htm
deleted file mode 100755
index c210a96..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_add_wizard.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Add Location Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Add Location Wizard</h1>
-
-<p>The <strong>Add Location Wizard</strong> is opened from the <a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a> or the <a href="../editors/target_editor/definition_page.htm">Definition Page</a>.  It is used to add a new location to a target definition.  On the first page you must select a type of location to add.  Click once on a location type to select it and a description of that location type will be visible at the bottom of the wizard.</p>
-
-<img src="../../images/target_shared/location_selection.png" alt="Add Location Wizard">
-
-<p>By default four types of locations are available:</p>
-<ul>
-<li><a href="./location_edit_directory_wizard.htm">Directory</a> - Select a directory and all plug-ins found inside of it will be added.</li>
-<li><a href="./location_edit_installation_wizard.htm">Installation</a> - Select the directory of an Eclipse installation or Eclipse based product.  All plug-ins installed into the application will be added.</li>
-<li><a href="./location_add_features_wizard.htm">Features</a> - Select one or more features from a directory and the plug-ins in those features will be added.</li>
-<li><a href="./location_edit_site_wizard.htm">Software Site</a> - Select software from an update site or p2 repository to add to the target.</li>
-</ul>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/definition_page.htm">Definition Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_edit_directory_wizard.htm">Directory Location</a><br>
-<a href="./location_edit_installation_wizard.htm">Installation Location</a><br>
-<a href="./location_add_features_wizard.htm">Add Feature Locations</a><br>
-<a href="./location_edit_feature_wizard.htm">Edit Feature Location</a><br>
-<a href="./location_edit_site_wizard.htm">Software Site Location</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_directory_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_directory_wizard.htm
deleted file mode 100755
index a86aa8f..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_directory_wizard.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Directory Location Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Directory Location Wizard</h1>
-
-<p>The <strong>Directory Location Wizard</strong> is used to create and edit directory locations in target definitions.  To create a new directory location use the <a href="./location_add_wizard.htm">Add Location Wizard</a> available from the <a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a> or the <a href="../editors/target_editor/definition_page.htm">Definition Page</a>.</p>
-
-<p>Select a folder containing plug-ins (it can also contain a folder called &quot;plugins&quot;).  All plug-ins found in the directory will be added to the target.  When selecting a directory you can use the drop-down to see folders you have used previously.  You can also use variables in the path such as <em>$eclipse_home</em> to make it easier to share your target definition.</p>
-
-<img src="../../images/target_shared/location_add_directory.png" alt="Directory Location Wizard">
-
-<p>After selecting a directory, you can press <strong>Finish</strong> to add the location to your target or you can press <strong>Next</strong> to <a href="./location_preview.htm">preview</a> the location contents.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/definition_page.htm">Definition Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_add_wizard.htm">Add Location</a><br>
-<a href="./location_edit_installation_wizard.htm">Installation Location</a><br>
-<a href="./location_add_features_wizard.htm">Add Feature Locations</a><br>
-<a href="./location_edit_feature_wizard.htm">Edit Feature Location</a><br>
-<a href="./location_edit_site_wizard.htm">Software Site Location</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_feature_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_feature_wizard.htm
deleted file mode 100755
index 00b596b..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_feature_wizard.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Edit Feature Location Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Edit Feature Location Wizard</h1>
-
-<p>The <strong>Edit Feature Location Wizard</strong> allows you to view the details of a feature location in your target definition.  This wizard is opened from the <a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a> or the <a href="../editors/target_editor/definition_page.htm">Definition Page</a>.</p>
-
-<p><strong>Feature ID</strong> is the identifying name of the feature.</p>
-
-<p><strong>Feature Version</strong> is the version of the feature that is used.  It may be unspecified, in which case the most recent version of the feature found in the directory is used.</p>
-
-<p><strong>Location</strong> is the directory where the feature is found.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/definition_page.htm">Definition Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_add_wizard.htm">Add Location</a><br>
-<a href="./location_edit_directory_wizard.htm">Directory Location</a><br>
-<a href="./location_edit_installation_wizard.htm">Installation Location</a><br>
-<a href="./location_add_features_wizard.htm">Add Feature Locations</a><br>
-<a href="./location_edit_site_wizard.htm">Software Site Location</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_installation_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_installation_wizard.htm
deleted file mode 100755
index 07ece22..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_installation_wizard.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Installation Location Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Installation Location Wizard</h1>
-
-<p>The <strong>Installation Location Wizard</strong> is used to create and edit installation locations in target definitions.  To create a new installation location use the <a href="./location_add_wizard.htm">Add Location Wizard</a> available from the <a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a> or the <a href="../editors/target_editor/definition_page.htm">Definition Page</a>.</p>
-
-<p>Select a folder containing an Eclipse installation or an Eclipse based products.  If the installation uses a special configuration directory you can enter a specific location rather than use the default.  When selecting a directory you can use the drop-down to see folders you have used previously.  You can also use variables in the path such as <em>$eclipse_home</em> to make it easier to share your target definition.</p>
-
-<img src="../../images/target_shared/location_add_application.png" alt="Installation Location Wizard">
-
-<p>After selecting an installation directory, you can press <strong>Finish</strong> to add the location to your target or you can press <strong>Next</strong> to <a href="./location_preview.htm">preview</a> the location contents.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/definition_page.htm">Definition Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_add_wizard.htm">Add Location</a><br>
-<a href="./location_edit_directory_wizard.htm">Directory Location</a><br>
-<a href="./location_add_features_wizard.htm">Add Feature Locations</a><br>
-<a href="./location_edit_feature_wizard.htm">Edit Feature Location</a><br>
-<a href="./location_edit_site_wizard.htm">Software Site Location</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_site_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_site_wizard.htm
deleted file mode 100755
index 02c3b27..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_edit_site_wizard.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Software Site Location Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Software Site Location Wizard</h1>
-
-<p>The <strong>Software Site Location Wizard</strong> is used to create and edit software site locations in target definitions.  To create a new software site location use the <a href="./location_add_wizard.htm">Add Location Wizard</a> available from the <a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a> or the <a href="../editors/target_editor/definition_page.htm">Definition Page</a>.</p>
-
-<img src="../../images/target_shared/location_add_site.png" alt="Software Site Location Wizard">
-
-<p>Software Site Locations can point to software in a repository or update site.  The site can be a remote url allowing for easy sharing.  To start searching for software you must select a site.  Use the drop-down to select a specific site or try using <em>All Available Sites</em>.  You can also press <strong>Add</strong> or click the link to modify the available sites.</p>
-
-<p>If a single site is selected software will only be downloaded from that site.  In addition, the site url will be stored in the target definition so it is available to others who open it.</p>
-
-<p>Once a site has been selected the software available from that site will be displayed in the list.  Check one or more items to include in the target.  To help you quickly find the software you are looking for, you can filter the list by typing in the filter text box, or change the options to <strong>Group by Category</strong> and <strong>Show Only the Latest Version</strong>.  If you select an entry in the list, the details section will display more information about the software.  Pressing <strong>Properties</strong> will display all information available about the selection.</p>
-
-<p>The <strong>Included Software</strong> options at the bottom of the wizard affect how the set of plug-ins to add to your target is determined.  By default, all required software is included.  This means that we find all plug-ins that are required by the software you selected.  All of those plug-ins must be available at the site or sites you have selected.  If any piece is missing, the target will fail to <em>resolve</em> and display an error explaining what requirement is missing.  This is the recommended setting for most users because it will ensure that you get the complete set of plug-ins in your target.  The environment settings of your target definition will be used when determining required plug-ins so that platform specific fragments will be included.</p>
-
-<p>Some users may want to build targets that do not contain all required software.  In addition, some sites and repositories may be missing some required plug-ins.  In these cases you can turn off the <strong>Include Required Software</strong> setting.  With this option off, all required plug-ins that are available in the selected site will be added to the target.  If a requirement is missing, it will be ignored.  If the option to include required software is turned off, the <strong>Include All Environments</strong> option will be available.  Turning it on will result in all available environment specific plug-ins to be added to the target, rather than just the plug-ins that apply to your target's environment settings.</p>
-
-<p>For up to the minute target troubleshooting help see the <a href="http://wiki.eclipse.org/PDE/Target_Definitions">Target Definitions Wiki Page</a>.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/definition_page.htm">Definition Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_add_wizard.htm">Add Location</a><br>
-<a href="./location_edit_directory_wizard.htm">Directory Location</a><br>
-<a href="./location_edit_installation_wizard.htm">Installation Location</a><br>
-<a href="./location_add_features_wizard.htm">Add Feature Locations</a><br>
-<a href="./location_edit_feature_wizard.htm">Edit Feature Location</a><br>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_preview.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_preview.htm
deleted file mode 100755
index dab4129..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/location_preview.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Directory Location Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Directory Location Wizard</h1>
-
-<p>The <strong>Directory Location Wizard</strong> is used to create and edit directory locations in target definitions.  To create a new directory location use the <a href="./location_add_wizard.htm">Add Location Wizard</a> available from the <a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a> or the <a href="../editors/target_editor/definition_page.htm">Definition Page</a>.</p>
-
-<p>Select a folder containing plug-ins (it can also contain a folder called &quot;plugins&quot;).  All plug-ins found in the directory will be added to the target.  When selecting a directory you can use the drop-down to see folders you have used previously.  You can also use variables in the path such as <em>$eclipse_home</em> to make it easier to share your target definition.</p>
-
-<img src="../../images/target_shared/location_add_directory.png" alt="Directory Location Wizard">
-
-<p>After selecting a directory, you can press <strong>Finish</strong> to add the location to your target or you can press <strong>Next</strong> to <a href="./location_preview.htm">preview</a> the location contents.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../../images/target_shared/edit_target_locations_tab.png">Location Tab</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="../editors/target_editor/definition_page.htm">Definition Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a><br>
-<a href="./location_add_wizard.htm">Add Location</a><br>
-<a href="./location_edit_directory_wizard.htm">Directory Location</a><br>
-<a href="./location_edit_installation_wizard.htm">Installation Location</a><br>
-<a href="./location_add_features_wizard.htm">Add Feature Locations</a><br>
-<a href="./location_edit_feature_wizard.htm">Edit Feature Location</a><br>
-<a href="./location_edit_site_wizard.htm">Software Site Location</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/move_target_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/move_target_wizard.htm
deleted file mode 100755
index 262d643..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/move_target_wizard.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Move Target Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>Move Target Wizard</h1>
-
-<p>This wizard moves a <a href="../../../concepts/target.htm">target definition</a> stored in the Eclipse preferences to a file in the workspace.  This wizard is accessed by pressing <strong>Move</strong> on the <a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a>.  You must choose a project or directory to create the file in and a filename.  Target definition files must end in the file extension &quot;.target&quot;.</p>
-
-<img src="../../images/target_shared/move_target_wizard.png" alt="Edit Target Wizard">
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="./new_target_wizard.htm">New Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/new_target_wizard.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/new_target_wizard.htm
deleted file mode 100755
index 52b00f9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/target_shared/new_target_wizard.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>New Target Wizard</title>
-<link rel="stylesheet" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-
-<body>
-<h1>New Target Wizard</h1>
-
-<p>This wizard creates a new <a href="../../../concepts/target.htm">target definition</a> that will be added to the <a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a>.  There are several options to initialize your target definition with data.  The new target definition will be saved in the Eclipse preferences, to create a target definition in your workspace use the <a href="../file_wizards/new_target_definition.htm">New Target Definition File Wizard</a>.</p>
-
-<img src="../../images/target_shared/new_target_wizard.png" alt="New Target Wizard">
-
-<p>Four options are available to initialize your new target definition:</p>
-<ul>
-<li><strong>Nothing</strong>  - Creates a target definition with no locations or other information set.</li>
-<li><strong>Default</strong> - Creates a target definition with the default settings.  The default target uses the plug-ins, environment, and vm arguments of your currently running Eclipse application.</li>
-<li><strong>Current Target</strong> - Creates a target definition with all the same settings as your active target platform.</li>
-<li><strong>Template</strong> - Creates a target definition and copies settings from a contributed template via extension point.  By default, two templates are available providing the basic setup for an RCP application.<p><img src="../../images/target_shared/new_target_wizard_template.png" alt="New Target Template Choice"></p></li>
-</ul>
-
-<p>After choosing an option press <strong>Next</strong> to open the <a href="./edit_target_wizard.htm">Edit Target Wizard</a> and finish creating the target definition.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="./edit_target_wizard.htm">Edit Target Wizard</a><br>
-<a href="./move_target_wizard.htm">Move Target Wizard</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related concepts"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/views/error_log.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/views/error_log.htm
deleted file mode 100644
index 0987a97..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/views/error_log.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Error Log</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Error Log</h1>
-<p>The <strong>Error Log</strong> view captures all the warnings and errors logged by plug-ins. The underlying log file is a <em>.log</em> file stored in the <em>.metadata</em> subdirectory of the workspace. The <strong>Error Log</strong> view is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.pde.runtime.LogView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Log view">
-<strong>Window &gt; Show View &gt; Error Log</strong>
-</a>. </p>
-<p><img src="../../images/views/error_log.png" alt="Error Log" ></p>
-
-<h2>Event Sorting</h2>
-<p>Events in the log view can be sorted by <strong>Message</strong>, <strong>Plug-in ID</strong> or <strong>Date</strong> in ascending or descending order. Simply click on the column header that you want the sorting to be based on. The down arrow in the column header indicates descending order; while, the up arrow indicates an ascending order.</p>
-
-<h2>Event Grouping</h2>
-<p>Events in the log view can be grouped by <strong>Session</strong> or <strong>Plug-in ID</strong>. Simply click on the chevron from the view's toolbar and select <strong>Group By</strong>. </p>
-
-<h2>Event Filtering</h2>
-<p>You can filter the view to show events of a particular type or session. Also, you can limit the number of entries in the view. Filtering options are available under <strong>Filters...</strong> from the view's toolbar drop down menu. </p>
-
-<h2>Import and Export Logs</h2>
-<p>To <strong>import</strong> an arbitrary <em>.log</em> file into the view, press the <strong>Import Log</strong> toolbar button or select <strong>Import Log...</strong> from the context menu.  Then, choose a <em>.log</em> file from the file system. </p>
-<p>To <strong>export</strong> the current log view content into a file, press the <strong>Export Log</strong> toolbar button or select <strong>Export Log...</strong> from the context menu. Then, enter a file name. </p>
-
-<h2>Clear and Delete Logs</h2>
-<p>To <strong>clear</strong> the view log content without deleting the underlying <em>.log</em> file, press the <strong>Clear Log</strong> toolbar button or select <strong>Clear Log Viewer</strong> from the context menu. </p>
-<p>To permanently <strong>delete</strong> the underlying <em>.log</em> file, press the <strong>Delete Log</strong> toolbar button or select <strong>Delete Log</strong> from the context menu. </p>
-
-<h2>Event Details</h2>
-<p>Full details about a particular event can be viewed in the <strong>Event Details</strong> dialog by double-clicking on a particular entry or selecting <strong>Event Details</strong> from the context menu of that entry. You can view the <strong>Date</strong>, <strong>Severity</strong>, <strong>Message</strong>, <strong>Exception Stack Trace</strong> (if available) and <strong>Session Data</strong> of each event. </p>
-<p><img src="../../images/views/error_log_details.png" alt="Error Log Details" ></p>
-<p>You can  navigate from one entry to the next via the <strong>Up</strong> and <strong>Down</strong> arrow buttons. </p>
-<p>To copy the error to the clipboard, press the button with the clipboard image. </p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_dependencies.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_dependencies.htm
deleted file mode 100644
index 0c02ecd..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_dependencies.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Dependencies</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Dependencies</h1>
-<p>The <strong>Plug-in Dependencies</strong> view generates and displays caller and callee relationships from within the plug-in ecosystem defined. The view is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.pde.ui.DependenciesView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Dependencies view">
-<strong>Window &gt; Show View &gt; Other... &gt; PDE &gt; Plug-in Dependencies</strong>
-</a>. </p>
-
-<h2>Callers</h2>
-<p>The <strong>callers</strong> visualization shows all the plug-ins that require a certain plug-in. The visualization is available in both hierarchical and flat-table modes. </p>
-<p><img src="../../images/views/plugin_dependencies_hierarchical_callers.png" alt="Hierarchical Callers" ></p>
-
-<h2>Callees</h2>
-<p>The <strong>callees</strong> visualization shows all the plug-ins required by a certain plug-in. The visualization is available in both hierarchical and flat-table modes. </p>
-<p><img src="../../images/views/plugin_dependencies_flat_callees.png" alt="Flat Callees" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_registry.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_registry.htm
deleted file mode 100644
index 496466a..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugin_registry.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-in Registry</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-in Registry</h1>
-<p>The <strong>Plug-in Registry</strong> view shows the state of all plug-ins in the running instance of Eclipse. The<strong> </strong>view is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.pde.runtime.RegistryBrowser)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Registry Browser">
-<strong>Window &gt; Show View &gt; Other... &gt; Plug-in Development &gt; Plug-in Registry</strong>
-</a>. </p>
-<p><img src="../../images/views/plugin_registry.png" alt="Plug-in Registry" ></p>
-
-<h2>State of the Plug-in</h2>
-<p>For each plug-in in the running system, the view shows:</p>
-<ul>
-  <li>the plug-in ID and version</li>
-  <li>the plug-in state (e.g. <em>active</em> or <em>inactive</em> - Note: the active state is indicated by a green overlay icon)</li>
-  <li>the plug-in location</li>
-  <li>the plug-in runtime libraries </li>
-  <li>the plug-in dependencies</li>
-  <li>the plug-in extensions</li>
-  <li>the plug-in extension points it contributes</li>
-  <li>the plug-in services it consumes</li>
-  <li>the plug-in services it contributes</li>
-</ul>
-
-<h2>Plug-in Filtering</h2>
-<p>The <strong>Show Active Plug-ins Only</strong> menu item is a filter that removes all inactive plug-ins from the view. To re-add them, press the menu item again. This filtering action is also available from the view's toolbar drop down menu.</p>
-
-<p>The <strong>Show Extension Content Only</strong> menu item is a filter that only shows extension or extension points in the view. To show everything again, press the menu item again. This filtering action is also available from the view's toolbar drop down menu.</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugins.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugins.htm
deleted file mode 100644
index df64d2c..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/views/plugins.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Plug-ins</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Plug-ins  </h1>
-<p>The <strong>Plug-ins View</strong> shows a unified view of all the plug-ins you are developing in the workspace and the plug-ins that make up your target platform. The view <strong></strong> is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.pde.ui.PluginsView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Plug-ins view">
-<strong>Window &gt; Show View &gt; Other... &gt; Plug-in Development &gt; Plug-ins</strong>
-</a>. </p>
-<p><img src="../../images/views/plugin_1.png" alt="Plug-ins View" ></p>
-
-<h2>Workspace Plug-ins</h2>
-<p>A workspace plug-in is shown in the view with a yellow and blue project folder icon. Its contents are not shown because the view is not intended to duplicate the behaviour of the <em>Navigator</em> and <em>Package Explorer</em> views. Double-click on the plug-in to open its manifest file in the PDE plug-in manifest editor. </p>
-
-<h2>Target Plug-ins</h2>
-<p>A target plug-in is shown in the view with the regular blue and yellow plug-in icon (or purple and yellow, in the case of a fragment). If the plug-in is stored as a JAR, it is not expandable. Flat plug-ins, on the other hand, are expandable and you can browse their structure and content. Double-click on a plug-in JAR or one of the flat plug-in manifest files to open its manifest file in the PDE plug-in manifest editor. </p>
-
-<h2>Actions</h2>
-<p>Several useful actions are available from the context menu of selected plug-ins within the Plug-ins view:</p>
-<ul>
-  <li><strong>Open Dependencies</strong>: opens the <a href="plugin_dependencies.htm">Plug-in Dependencies</a> view to show hierarchical and tabular renderings of the selected plug-in's relationship to other plug-ins</li>
-  <li><strong>Find References</strong>: finds all references to the selected plug-in by other plug-ins in the workspace and target platform and displayed the results in the <em>Search</em> view.</li>
-  <li><strong>Importing</strong>: provides a quick way to import the selected plug-in into the workspace.</li>
-  <li><strong>Add to Java Search</strong>: adds the code found in the selected plug-in to the scope of the Java search engine without the need to import the plug-in.</li>
-</ul>
-
-<h2>Filtering</h2>
-<p>Several filters are available in the view's toolbar drop down menu to show and hide workspace and disabled target plug-ins.</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/views/target_platform_state.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/views/target_platform_state.htm
deleted file mode 100755
index e7ff3f9..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/views/target_platform_state.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Target Platform State</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Target Platform State</h1>
-<p>The <strong>Target Platform State View</strong> shows the current status of the resolver state in PDE.</p>
-
-<p>The view is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.pde.ui.TargetPlatformStateView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Target Platform State view">
-<strong>Window &gt; Show View &gt; Other... &gt; Plug-in Development &gt; Target Platform State</strong>
-</a>.</p>
-<p>Any plug-ins displayed with a red X are currently unresolved.  
-Expand an unresolved plug-in to reveal the unsatisfied constraints which result in the unresolved status.</p>
-<p>When you open the children of a resolved plug-in, you will see its dependencies separated into imported packages and required bundles.  
-The child of each dependency is the plug-in which satisfies the particular dependency.</p>
-<p><img src="../../images/views/plugin_dependencies_state_status.png" alt="State Status" ></p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../preference_pages/target_platform.htm">Target Platform Preference Page</a><br>
-<a href="../editors/target_editor/target_editor.htm">Target Editor</a>
-</p>
-
-<p><img src="../../../images/ngrelc.png" alt="Related reference"></p>
-<p>
-<a href="../../../concepts/target.htm">Target Definitions</a>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/views/views.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/views/views.htm
deleted file mode 100644
index 318cb44..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/views/views.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Views</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Views</h1>
-<p>PDE provides four views that help plug-in developers inspect different aspects of their development environment. These views can be opened via <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView()")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the Show View dialod">
-<strong>Window &gt; Show View &gt; Other... &gt; Plug-in Development</strong>
-</a>.</p>
-<p><img src="../../images/views/all_views.PNG" alt="PDE View Categories"> </p>
-
-<p>For detailed information on individual PDE views, refer to the following documents:</p>
-<ul>
-  <li><a href="error_log.htm">Error Log</a></li>
-  <li><a href="plugin_registry.htm">Plug-in Registry</a></li>
-  <li><a href="plugins.htm">Plug-ins</a></li>
-  <li><a href="plugin_dependencies.htm">Plug-in Dependencies</a></li>
-  <li><a href="target_platform_state.htm">Target Platform State</a></li>
-</ul>
-
-<h2>Plug-in Development Perspective</h2>
-<p>The <strong>Plug-in Development</strong> perspective is designed to support efficient development and integration of plug-in projects. Its also adds the <strong>Plug-ins</strong> and <strong>Error Log</strong> views which are particularly useful. </p>
-<p>The perspective can be opened via <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.pde.ui.PDEPerspective)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the PDE perspective">
-<strong>Window &gt; Open Perspective &gt; Other... &gt; Plug-in Development</strong>
-</a>.</p>
-<p><img src="../../images/views/perspective.PNG" alt="PDE Perspective"></p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/guide/tweak.css b/bundles/org.eclipse.pde.doc.user/guide/tweak.css
deleted file mode 100644
index f701de3..0000000
--- a/bundles/org.eclipse.pde.doc.user/guide/tweak.css
+++ /dev/null

@@ -1,47 +0,0 @@
-body {
-	margin-bottom: 100px;
-}
-hr {
-	border: none;
-	border-top: 1px dotted #C6E2FF;
-	margin-left: 10pt;
-	margin-bottom: 5px;
-	margin-top: 5px;
-	height: 1px;
-	width: 95%;	
-	text-align: left;
-}
-img {
-	margin-left: 20pt;
-	border: none;
-}
-table { 
-	border: 1px #666699 solid;
-	border-collapse: collapse;
-	border-spacing: 0px;
-	margin-top: 20px;
-	margin-bottom: 20px;	
-	margin-left: 20pt;	
-	width: 95%;
-}
-td.header { 
-	border-bottom: 2px solid #CCCCCC;
-	background-color: #F5F5F5;
-	color: #666699;
-}
-td.body { 
-	border-bottom: 1px dotted #666699;
-	background-color: white;
-	text-align: left;
-	padding-left: 3px;
-	padding-right: 3px;
-	padding-top: 3px;
-	padding-bottom: 3px;
-	border-left: 1px dotted #666699;
-}
-.reference {
-	color:#FF0000;
-}
-
-
-

diff --git a/bundles/org.eclipse.pde.doc.user/images/ngrelc.png b/bundles/org.eclipse.pde.doc.user/images/ngrelc.png
deleted file mode 100644
index 161e3aa..0000000
--- a/bundles/org.eclipse.pde.doc.user/images/ngrelc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/images/ngrelr.png b/bundles/org.eclipse.pde.doc.user/images/ngrelr.png
deleted file mode 100644
index 4726f8c..0000000
--- a/bundles/org.eclipse.pde.doc.user/images/ngrelr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/images/ngrelt.png b/bundles/org.eclipse.pde.doc.user/images/ngrelt.png
deleted file mode 100644
index 74bee2b..0000000
--- a/bundles/org.eclipse.pde.doc.user/images/ngrelt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/notices.html b/bundles/org.eclipse.pde.doc.user/notices.html
deleted file mode 100644
index b81cc5e..0000000
--- a/bundles/org.eclipse.pde.doc.user/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-   <link rel="STYLESHEET" href="book.css" type="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a name="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2009.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/pdeOptions.txt b/bundles/org.eclipse.pde.doc.user/pdeOptions.txt
deleted file mode 100644
index 1b6867e..0000000
--- a/bundles/org.eclipse.pde.doc.user/pdeOptions.txt
+++ /dev/null

@@ -1,80 +0,0 @@
--quiet
--charset "iso-8859-1"
--sourcepath "../org.eclipse.pde.core/src
-;../org.eclipse.pde.ui/src
-;../org.eclipse.pde.build/src
-;../org.eclipse.pde.launching/src"
--d reference/api
--classpath @rt@
-;../org.eclipse.compare/@dot
-;../org.eclipse.compare.core/@dot
-;../org.eclipse.core.boot/@dot
-;../org.eclipse.core.contenttype/@dot
-;../org.eclipse.core.jobs/@dot
-;../org.eclipse.core.resources/@dot
-;../org.eclipse.core.runtime/@dot
-;../org.eclipse.core.runtime.content/@dot
-;../org.eclipse.core.runtime.jobs/@dot
-;../org.eclipse.core.runtime.preferences/@dot
-;../org.eclipse.core.variables/@dot
-;../org.eclipse.debug.core/@dot
-;../org.eclipse.debug.ui/@dot
-;../org.eclipse.equinox.common/@dot
-;../org.eclipse.equinox.preferences/@dot
-;../org.eclipse.equinox.registry/@dot
-;../org.eclipse.equinox.supplement/@dot
-;../org.eclipse.help/@dot
-;../org.eclipse.help.ui/@dot
-;../org.eclipse.jdt.core/@dot
-;../org.eclipse.jdt.debug/jdi.jar
-;../org.eclipse.jdt.debug.ui/@dot
-;../org.eclipse.jdt.junit/@dot
-;../org.eclipse.jdt.junit/junitsupport.jar
-;../org.eclipse.jdt.junit.core/@dot
-;../org.eclipse.jdt.launching/@dot
-;../org.eclipse.jdt.ui/@dot
-;../org.eclipse.jface/@dot
-;../org.eclipse.jface.text/@dot
-;../org.eclipse.osgi/@dot
-;../org.eclipse.osgi.services/@dot
-;../org.eclipse.osgi.util/@dot
-;../org.eclipse.pde.core/@dot
-;../org.eclipse.pde.ui/@dot
-;../org.eclipse.pde.build/@dot
-;../org.eclipse.pde.launching/@dot
-;../org.eclipse.search/@dot
-;../org.eclipse.swt.win32.win32.x86/@dot
-;../org.eclipse.text/@dot
-;../org.eclipse.ui/@dot
-;../org.eclipse.ui.editors/@dot
-;../org.eclipse.ui.ide/@dot
-;../org.eclipse.ui.views/@dot
-;../org.eclipse.ui.workbench/@dot
-;../org.eclipse.ui.workbench.texteditor/@dot
-;../org.eclipse.update.configurator/@dot
--breakiterator
--use
--splitIndex
-
--windowtitle "Eclipse PDE API Specification"
--doctitle "Eclipse PDE API Specification"
--header "<b>Eclipse PDE</b><br>Release 3.6"
--bottom "Copyright (c) IBM Corp. and others 2000, 2009.  All Rights Reserved."
--link http://java.sun.com/j2se/1.4/docs/api
--linkoffline ./../../../org.eclipse.platform.doc.isv/reference/api ../org.eclipse.platform.doc.isv/reference/api
--linkoffline ./../../../org.eclipse.jdt.doc.isv/reference/api ../org.eclipse.jdt.doc.isv/reference/api
--link http://bundles.osgi.org/javadoc/r4
--tag 'noimplement:a:Restriction:'
--tag 'noextend:a:Restriction:'
--tag 'noreference:a:Restriction:'
--tag 'noinstantiate:a:Restriction:'
--tag 'nooverride:a:Restriction:'
-
-org.eclipse.pde.build
-org.eclipse.pde.core
-org.eclipse.pde.core.build
-org.eclipse.pde.core.plugin
-org.eclipse.pde.ui
-org.eclipse.pde.ui.launcher
-org.eclipse.pde.ui.templates
-org.eclipse.pde.launching

diff --git a/bundles/org.eclipse.pde.doc.user/plugin.properties b/bundles/org.eclipse.pde.doc.user/plugin.properties
deleted file mode 100644
index 2e3a3d6..0000000
--- a/bundles/org.eclipse.pde.doc.user/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-#  Copyright (c) 2000, 2007 IBM Corporation and others.
-#  All rights reserved. This program and the accompanying materials
-#  are made available under the terms of the Eclipse Public License v1.0
-#  which accompanies this distribution, and is available at
-#  http://www.eclipse.org/legal/epl-v10.html
-# 
-#  Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName=PDE User Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.pde.doc.user/plugin.xml b/bundles/org.eclipse.pde.doc.user/plugin.xml
deleted file mode 100644
index 37f623c..0000000
--- a/bundles/org.eclipse.pde.doc.user/plugin.xml
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/actions/ref-pdetools.htm b/bundles/org.eclipse.pde.doc.user/reference/actions/ref-pdetools.htm
deleted file mode 100644
index e197946..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/actions/ref-pdetools.htm
+++ /dev/null

@@ -1,29 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../book.css" type="text/css">
-<title>PDE Tools</title>
-</head>
-<body>
-<h1>PDE Tools </h1>
-<p>Select the <strong>PDE Tools</strong> command to access helpful tools from the resulting fly-out menu.</p>
-<p> The menu can be found on:</p>
-	<ul>
-		<li>Java Projects</li>
-		<li>Plug-in Projects</li>
-		<li>build.properties files</li>
-		<li>plugin.xml files</li>
-		<li>MANIFEST.MF files</li>
-	</ul>
-<p>An example fly-out menu for the <strong>PDE Tools</strong> command. 
- </p>
-<p><img src="../images/pde-tools-flyout.PNG" alt="PDE Tools Fly-Out menu"></p>
-<p><img src="../../images/ngrelr.png" alt="Related Reference"></p>
-<p>
-<a href="../api-tooling/actions/ref-apitooling-setup-action.htm">API Tooling Setup</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-apitooling-setup-action.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-apitooling-setup-action.htm
deleted file mode 100644
index af6bc7a..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-apitooling-setup-action.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <title>API Tooling Setup</title>
-</head>
-<body>
-<h1>API Tooling Setup</h1>
-<p>Select the <strong>API Tooling Setup</strong> command [ <img src="PLUGINS_ROOT/org.eclipse.pde.api.tools.ui/icons/full/obj16/category_menu.gif" alt="API Tooling Setup"> ] to start the API Setup wizard.</p>
-<br>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../wizards/ref-api-setup-wizard.htm">API Tooling Setup Wizard</a><br>
-<a href="../../actions/ref-pdetools.htm">PDE Tools Context Menu</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-compare-action.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-compare-action.htm
deleted file mode 100644
index 0b315f4..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/actions/ref-compare-action.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <title>API Compare</title>
-</head>
-<body>
-<h1>API Compare</h1>
-<p>Select the <strong>Compare With &gt; API Baseline...</strong> command to start the API Compare wizard.</p>
-<br>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../../actions/ref-pdetools.htm">PDE Tools Context Menu</a><br>
-<a href="../wizards/ref-api-compare-wizard.htm">API Compare Wizard</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-ant-task.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-ant-task.htm
deleted file mode 100644
index 2dcc2ed..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-ant-task.htm
+++ /dev/null

@@ -1,189 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../apache_style.css" type="text/css">
-<title>API Tools Analysis Ant Task</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Analysis Ant Task </h1>
-<h2>Purpose</h2>
-<p>This task runs a complete API analysis of an API profile relative to a baseline - including API use, binary compatibility, and bundle version number validation. The profile is the current state of a product under development. The profile is compared to an API baseline for binary compatibility (usually the previous release of a product). </p>
-<p>The analysis does not include  @since tag validation as all verification is performed on binary class files (source is not analyzed). </p>
-
-<h2>Usage</h2>
-<h3>Description</h3>
-<p>The name of the ant task is: <code>apitooling.analysis</code>. To be used, the jar file <code>apitooling-ant.jar</code> has to be on the ant
-classpath.</p>
-<div style="text-align: left;">
-<pre style="margin-left: 40px">
-<b><font color="#0000ff">&lt;apitooling.analysis
-	baseline=<font color="#008000">"..."</font>
-	profile=<font color="#008000">"..."</font>
-	report=<font color="#008000">"..."</font>
-	filters=<font color="#008000">"..."</font>
-	excludelist=<font color="#008000">"..."</font>
-	preferences=<font color="#008000">"..."</font>
-	debug=<font color="#008000">"..."</font>
-	eefile=<font color="#008000">"..."</font>
-/&gt;</font></b>
-</pre>
-</div>
-<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
-  <tr>
-    <td valign="top"><b>Attribute</b></td>
-    <td valign="top"><b>Description</b></td>
-    <td align="center" valign="top"><b>Required</b></td>
-  </tr>
-<tr>
-<td valign="top">baseline</td>
-<td valign="top">This attribute specifies the location of the reference baseline.
-<br><br>It can be a .zip, .jar, .tgz, .tar.gz file, or a directory that corresponds to the Eclipse installation folder. This is the 
-directory is which you can find the Eclipse executable.
-<br><br>The location is specified using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">profile</td>
-<td valign="top">This attribute specifies the location of the current product or profile that you want to compare against the reference baseline.
-<br><br>
-It can be a .zip, .jar, .tgz, .tar.gz file, or a directory that corresponds to the Eclipse installation folder. This is the 
-directory is which you can find the Eclipse executable.
-<br><br>The location is specified using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">report</td>
-<td valign="top">Set the output location where the reports will be generated.
-<br><br>
-Once the task is completed, reports are available in this directory using a structure similar to the filter root. A sub-folder is created
-for each component that has problems to be reported. Each sub-folder contains a file called "report.xml".
-<br><br>A special folder called "allNonApiBundles" is also created in this folder which also contains a file called "report.xml".
-This file lists all the bundles that are not using the API Tooling nature.
-<br><br>The location is specified using an absolute path. 
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">filters</td>
-<td valign="top">Set the root directory of API filters to use during the analysis.
-<br><br>
-The argument is the root directory of the .api_filters files that should be used to filter potential problems created by 
-the api tooling analysis.
-<br>The root is specified using an absolute path. 
-<br>The root needs to contain the following structure:
-<pre>
- root
-  |
-  +-- component name (i.e. org.eclipse.jface)
-         |
-         +--- .api_filters
-</pre>
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">excludelist</td>
-<td valign="top">Set the exclude list location. 
-<br><br>The exclude list is used to know what bundles should excluded from the xml report generated by the task execution.
-The lines that start with '#' are ignored from the excluded elements.
-<br>The location is specified using an absolute path.
-<br>The format of the exclude list file looks like this:
-<pre>
- # DOC BUNDLES
- org.eclipse.jdt.doc.isv
- org.eclipse.jdt.doc.user
- org.eclipse.pde.doc.user
- org.eclipse.platform.doc.isv
- org.eclipse.platform.doc.user
- # NON-ECLIPSE BUNDLES
- com.ibm.icu
- com.jcraft.jsch
- javax.servlet
- javax.servlet.jsp
- ...
-</pre>
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">preferences</td>
-<td valign="top">Set the preferences for the task. 
-<br><br>
-The preferences are used to configure problem severities. Problem severities have three possible values: Ignore, Warning, or Error. The set of problems detected is defined by corresponding problem preference keys in API tools.
-<br>The location is specified using an absolute path. If the given location doesn't exist, the preferences won't be set.
-<br>
-Lines starting with '#' are ignored. The format of the preferences file looks like this:
-<pre>
- #Thu Nov 20 17:35:06 EST 2008
- ANNOTATION_ELEMENT_TYPE_ADDED_METHOD_WITHOUT_DEFAULT_VALUE=Ignore
- ANNOTATION_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Ignore
- ANNOTATION_ELEMENT_TYPE_REMOVED_FIELD=Ignore
- ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD=Ignore
- ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Warning
- API_COMPONENT_ELEMENT_TYPE_REMOVED_API_TYPE=Ignore
- API_COMPONENT_ELEMENT_TYPE_REMOVED_TYPE=Ignore
- CLASS_ELEMENT_TYPE_ADDED_METHOD=Error
- CLASS_ELEMENT_TYPE_ADDED_RESTRICTIONS=Ignore
- CLASS_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Ignore
- CLASS_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Ignore
- ...
-</pre>
-The keys can be found in org.eclipse.pde.api.tools.internal.provisional.problems.IApiProblemTypes.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">debug</td>
-<td valign="top">Set the debug value.
-<br><br>The possible values are: <code>true</code>, <code>false</code>
-<br>Default is <code>false</code>.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">eefile</td>
-<td valign="top">Set the execution environment file to use. 
-<br><br>By default, an execution environment file corresponding to a JavaSE-1.6 execution environment is used.
-<br><br>The format of the file is described in this <a href="http://wiki.eclipse.org/index.php/Execution_Environment_Descriptions" target="blank">wiki page</a>.
-<br><br>The file is specified using an absolute path.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-</table>
-
-<h3>Examples</h3>
-
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.analysis
-		baseline=<font color="#008000">"D:\eclipse\3.4.1\eclipse"</font>
-		profile=<font color="#008000">"D:\eclipse-SDK-I20081118-0800-linux-gtk.tar.gz"</font>
-		report=<font color="#008000">"D:\reports\xml"</font>
-		filters=<font color="#008000">"D:\filters"</font>
-		excludelist=<font color="#008000">"D:\exclude_list_external.txt"</font>
-		preferences=<font color="#008000">"D:\tests_api\org.eclipse.pde.api.tools.prefs"</font>
-		debug=<font color="#008000">"true"</font>
-	/&gt;</font></b>
-</pre>
-<p>This will run the task creating <code>report.xml</code> files inside the folder <code>D:\reports\xml</code>.
-It will use the exclude list and the <code>.api_filter</code> files located in <code>D:\exclude_list_external.txt</code> and 
-<code>D:\filters</code> to reduce the number of problems to report.</p>
-<p>Problem severities will be generated as specified by <code>D:\tests_api\org.eclipse.pde.api.tools.prefs</code>.</p>
-<p>Since debug is enabled, some debug tracing will show up in the ant console.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="apifreeze-ant-task.htm">API Tools API Freeze Ant Task</a>
-<br><a href="filegeneration-ant-task.htm">API Tools File Generation Ant Task</a>
-<br><a href="apiuse-ant-task.htm">API Tools API Use Ant Task</a>
-<br><a href="analysis-reportconversion-ant-task.htm">API Tools Analysis Report Conversion Ant Task</a>
-<br><a href="apifreeze-reportconversion-ant-task.htm">API Tools API Freeze Report Conversion Ant Task</a>
-<br><a href="apiuse-reportconversion-ant-task.htm">API Tools API Use Report Conversion Ant Task</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-reportconversion-ant-task.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-reportconversion-ant-task.htm
deleted file mode 100644
index 90e3f37..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/analysis-reportconversion-ant-task.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../apache_style.css" type="text/css">
-<title>API Tools Analysis Report Conversion Ant Task</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Tools Analysis Report Conversion Ant Task </h1>
-<h2>Purpose</h2>
-<p>This task converts  XML reports created by the <code>apitooling.analysis</code> ant task into HTML files.
-</p>
-<h2>Usage</h2>
-<h3>Description</h3>
-<p>The name of the ant task is: <code>apitooling.analysis_reportconversion</code>. To be used, the jar file <code>apitooling-ant.jar</code> has to be on the ant
-classpath.</p>
-<div style="text-align: left;">
-<pre style="margin-left: 40px">
-<b><font color="#0000ff">&lt;apitooling.analysis_reportconversion
-	xmlfiles=<font color="#008000">"..."</font>
-	htmlfiles=<font color="#008000">"..."</font>
-	debug=<font color="#008000">"..."</font>
-/&gt;</font></b>
-</pre>
-</div>
-<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
-  <tr>
-    <td valign="top"><b>Attribute</b></td>
-    <td valign="top"><b>Description</b></td>
-    <td align="center" valign="top"><b>Required</b></td>
-  </tr>
-<tr>
-<td valign="top">xmlfiles</td>
-<td valign="top">Set the location where the xml reports are retrieved.
-<br><br>The location is set using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">htmlfiles</td>
-<td valign="top">Set the location where the html reports are generated.
-<br><br>If not set, the html files are created in the same folder as the xml files.
-<br><br>The location is set using an absolute path.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">debug</td>
-<td valign="top">Set the debug value.
-<br><br>The possible values are: <code>true</code>, <code>false</code>
-<br>Default is <code>false</code>.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-</table>
-
-<h3>Examples</h3>
-
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.analysis_reportconversion
-		xmlfiles=<font color="#008000">"D:\reports\xml"</font>
-		htmlfiles=<font color="#008000">"D:\reports\html"</font>
-		debug=<font color="#008000">"true"</font>
-	/&gt;</font></b>
-</pre>
-<p>This will create an <code>index.html</code> inside the folder <code>D:\reports\html</code>. A report for each
-bundle will be created inside a sub-folder of <code>D:\reports\html</code>. Each sub-folder will contain a 
-<code>report.html</code>.</p>
-<p>Since debug is enabled, some debug tracing will show up in the ant console.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="analysis-ant-task.htm">API Tools Analysis Ant Task</a>
-<br><a href="filegeneration-ant-task.htm">API Tools File Generation Ant Task</a>
-<br><a href="apiuse-ant-task.htm">API Tools API Use Ant Task</a>
-<br><a href="apifreeze-ant-task.htm">API Tools API Freeze Ant Task</a>
-<br><a href="apifreeze-reportconversion-ant-task.htm">API Tools API Freeze Report Conversion Ant Task</a>
-<br><a href="apiuse-reportconversion-ant-task.htm">API Tools API Use Report Conversion Ant Task</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-ant-task.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-ant-task.htm
deleted file mode 100644
index 01083a6..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-ant-task.htm
+++ /dev/null

@@ -1,125 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../apache_style.css" type="text/css">
-<title>API Tools API Freeze Ant Task</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Freeze Ant Task </h1>
-<h2>Purpose</h2>
-<p>This task identifies APIs that have been added, modified, or removed relative to an API baseline.
-This task is intended to validate no API changes occur after an API freeze. </p>
-<h2>Usage</h2>
-<h3>Description</h3>
-<p>The name of the ant task is: <code>apitooling.apifreeze</code>. To be used, the jar file <code>apitooling-ant.jar</code> has to be on the ant
-classpath.</p>
-<div style="text-align: left;">
-<pre style="margin-left: 40px">
-<b><font color="#0000ff">&lt;apitooling.apifreeze
-	baseline=<font color="#008000">"..."</font>
-	profile=<font color="#008000">"..."</font>
-	report=<font color="#008000">"..."</font>
-	excludelist=<font color="#008000">"..."</font>
-	debug=<font color="#008000">"..."</font>
-	eefile=<font color="#008000">"..."</font>
-/&gt;</font></b>
-</pre>
-</div>
-<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
-  <tr>
-    <td valign="top"><b>Attribute</b></td>
-    <td valign="top"><b>Description</b></td>
-    <td align="center" valign="top"><b>Required</b></td>
-  </tr>
-<tr>
-<td valign="top">baseline</td>
-<td valign="top">This attribute specifies the location of the reference baseline.
-<br><br>It can be a .zip, .jar, .tgz, .tar.gz file, or a directory that corresponds to the Eclipse installation folder. This is the 
-directory is which you can find the Eclipse executable.
-<br><br>The location is specified using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">profile</td>
-<td valign="top">This attribute specifies the location of the current product or profile that you want to compare against the reference baseline.
-<br><br>
-It can be a .zip, .jar, .tgz, .tar.gz file, or a directory that corresponds to the Eclipse installation folder. This is the 
-directory is which you can find the Eclipse executable.
-<br><br>The location is specified using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">report</td>
-<td valign="top">Set the name of the report file to be generated.
-<br><br>It should be specified using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">excludelist</td>
-<td valign="top">Set the exclude list location.
-<br><br>
-The exclude list is used to know what bundles should excluded from the xml report
-generated by the task execution.
-<br>The location is specified using an absolute path.
-<br>Lines starting with '#' are ignored from the excluded element.
-<br>The format of the exclude file looks like this:
-<pre># 207144
-org.eclipse.ui.workbench_3.4.0:org.eclipse.ui.ISharedImages#IMG_DEC_FIELD_ERROR
-org.eclipse.ui.workbench_3.4.0:org.eclipse.ui.ISharedImages#IMG_DEC_FIELD_WARNING
-org.eclipse.ui.workbench_3.4.0:org.eclipse.ui.ISharedImages#IMG_ELCL_COLLAPSEALL
-...
-</pre>
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">debug</td>
-<td valign="top">Set the debug value.
-<br><br>The possible values are: <code>true</code>, <code>false</code>
-<br>Default is <code>false</code>.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">eefile</td>
-<td valign="top">Set the execution environment file to use. 
-<br><br>By default, an execution environment file corresponding to a JavaSE-1.6 execution environment is used.
-<br><br>The format of the file is described in this <a href="http://wiki.eclipse.org/index.php/Execution_Environment_Descriptions" target="blank">wiki page</a>.
-<br><br>The file is specified using an absolute path.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-</table>
-
-<h3>Examples</h3>
-
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.apifreeze
-		baseline=<font color="#008000">"D:\eclipse\3.4.1\eclipse"</font>
-		profile=<font color="#008000">"D:\eclipse-SDK-I20081118-0800-linux-gtk.tar.gz"</font>
-		report=<font color="#008000">"D:\report\report.xml"</font>
-		excludelist=<font color="#008000">"D:\exclude_list.txt"</font>
-		debug=<font color="#008000">"true"</font>
-	/&gt;</font></b>
-</pre>
-<p>This will run the task creating <code>report.xml</code> inside the folder <code>D:\report</code>.
-It will use the exclude list <code>D:\exclude_list_external.txt</code> to reduce the number of problems to report.</p>
-<p>Since debug is enabled, some debug tracing will show up in the ant console.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="analysis-ant-task.htm">API Tools Analysis Ant Task</a>
-<br><a href="filegeneration-ant-task.htm">API Tools File Generation Ant Task</a>
-<br><a href="apiuse-ant-task.htm">API Tools API Use Ant Task</a>
-<br><a href="analysis-reportconversion-ant-task.htm">API Tools Analysis Report Conversion Ant Task</a>
-<br><a href="apifreeze-reportconversion-ant-task.htm">API Tools API Freeze Report Conversion Ant Task</a>
-<br><a href="apiuse-reportconversion-ant-task.htm">API Tools API Use Report Conversion Ant Task</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-reportconversion-ant-task.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-reportconversion-ant-task.htm
deleted file mode 100644
index 101548e..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apifreeze-reportconversion-ant-task.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../apache_style.css" type="text/css">
-<title>API Tools API Freeze Report Conversion Ant Task</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Tools API Freeze Report Conversion Ant Task </h1>
-<h2>Purpose</h2>
-<p>This task converts the XML report created by the <code>apitooling.apifreeze</code> ant task into an HTML file.</p>
-<h2>Usage</h2>
-<h3>Description</h3>
-<p>The name of the ant task is: <code>apitooling.apifreeze_reportconversion</code>. To be used, the jar file <code>apitooling-ant.jar</code> has to be on the ant
-classpath.</p>
-<div style="text-align: left;">
-<pre style="margin-left: 40px">
-<b><font color="#0000ff">&lt;apitooling.apifreeze_reportconversion
-	xmlfile=<font color="#008000">"..."</font>
-	htmlfile=<font color="#008000">"..."</font>
-	debug=<font color="#008000">"..."</font>
-/&gt;</font></b>
-</pre>
-</div>
-<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
-  <tr>
-    <td valign="top"><b>Attribute</b></td>
-    <td valign="top"><b>Description</b></td>
-    <td align="center" valign="top"><b>Required</b></td>
-  </tr>
-<tr>
-<td valign="top">xmlfile</td>
-<td valign="top">This attribute specifies the location of the xml file to convert.
-<br><br>The location is specified using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">htmlfile</td>
-<td valign="top">This attribute specifies the location of the html file to generate.
-<br><br>If not set, the html file name is retrieved from the xml file name by replacing ".xml" in ".html".
-<br><br>The location is specified using an absolute path.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">debug</td>
-<td valign="top">Set the debug value.
-<br><br>The possible values are: <code>true</code>, <code>false</code>
-<br>Default is <code>false</code>.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-</table>
-
-<h3>Examples</h3>
-
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.apifreeze_reportconversion
-		xmlfile==<font color="#008000">"D:\report\report.xml"</font>
-		debug=<font color="#008000">"true"</font>
-	/&gt;</font></b>
-</pre>
-<p>This will run the task creating <code>report.html</code> inside the folder <code>D:\report</code> as the
-htmlfile attribute is not set.</p>
-<p>Since debug is enabled, some debug tracing will show up in the ant console.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="analysis-ant-task.htm">API Tools Analysis Ant Task</a>
-<br><a href="filegeneration-ant-task.htm">API Tools File Generation Ant Task</a>
-<br><a href="apiuse-ant-task.htm">API Tools API Use Ant Task</a>
-<br><a href="apifreeze-ant-task.htm">API Tools API Freeze Ant Task</a>
-<br><a href="analysis-reportconversion-ant-task.htm">API Tools Analysis Report Conversion Ant Task</a>
-<br><a href="apiuse-reportconversion-ant-task.htm">API Tools API Use Report Conversion Ant Task</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-ant-task.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-ant-task.htm
deleted file mode 100644
index f722aff..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-ant-task.htm
+++ /dev/null

@@ -1,164 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../apache_style.css" type="text/css">
-<title>API Use Ant Task</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Use Ant Task </h1>
-<h2>Purpose</h2>
-<p>This task runs a complete search of a given baseline to determine a producer-centric report of API usage.</p>
-<p>The analysis does not include  bundles that are not API Tools enabled.</p>
-
-<h2>Usage</h2>
-<h3>Description</h3>
-<p>The name of the ant task is: <code>apitooling.apiuse</code>. To be used, the jar file <code>apitooling-ant.jar</code> has to be on the ant
-classpath.</p>
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.apiuse
-		location=<font color="#008000">"..."</font>
-		scopepattern=<font color="#008000">"..."</font>
-		referencepattern=<font color="#008000">"..."</font>
-		report=<font color="#008000">"..."</font>
-		considerinternal=<font color="#008000">"..."</font>
-		considerapi=<font color="#008000">"..."</font>
-		apipatterns=<font color="#008000">"..."</font>
-		internalpatterns=<font color="#008000">"..."</font>
-		debug=<font color="#008000">"..."</font>
-	/&gt;</font></b>
-</pre>
-<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
-  <tr>
-    <td valign="top"><b>Attribute</b></td>
-    <td valign="top"><b>Description</b></td>
-    <td align="center" valign="top"><b>Required</b></td>
-  </tr>
-<tr>
-	<td valign="top">location</td>
-	<td valign="top">
-		This attribute specifies the location of the current product you want to search for API usage.
-		<br><br>
-		It can be a .zip, .jar, .tgz, .tar.gz file, or a directory that corresponds to a collection of bundles.
-		<br><br>
-		The location is specified using an absolute path.</td>
-	<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-	<td valign="top">scopepattern</td>
-	<td valign="top">
-		This attribute specifies the regular expression pattern used to build the scope of elements to search for 
-	 	references from in the product location.
-	 	<br><br>
-	 	The pattern must be a well-formatted regular expression as
-	 	defined <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html">here</a>.
-	</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-	<td valign="top">referencepattern</td>
-	<td valign="top">
-		Set the regular expression pattern used to build the scope of elements to search for 
-	 	references to in the product location.
-	 	<br><br>
-	 	The pattern must be a well-formatted regular expression as
-	 	defined <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html">here</a>.
-	 	</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-	<td valign="top">report</td>
-	<td valign="top">Set the output location where the reports will be generated.
-		<br><br>
-		Once the task is completed, reports are available in this directory using a hierarchical structure. A sub-folder is created
-		for each component that has another bundle that references it. Each sub-folder contains a file called "[bundlename].xml". Within
-		this folder is another sub-folder (named "[referencing bundle name].xml") for each bundle that references the bundle of the containing folder. 
-		Inside the referencing bundle folder is one of three sub-folders (API, PRIVATE or OTHER) which contain type, method or field references of that kind.
-		<br><br>
-		Two other special files are written into the report directory, which are "not_searched.xml" and "no_apidescription.xml" and they contain
-		information about bundles from the baseline that were not search for usage information and those that did not have an .api_description files in them, respectively.
-		<br><br>
-		The location is specified using an absolute path.
-		<br><br>
-		For example:
-<pre>
-  root
-   |
-   +-- "not_searched.xml"
-   +-- "no_apidescription.xml"
-   +-- bundle name with usage
-   		|
-   		+--referencing bundle name
-   			|
-   			+-- [API or PRIVATE or OTHER]
-   				|
-   				+--[type_ or method_ or field_]references.xml
-</pre>
-		</td>
-	<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-	<td valign="top">considerinternal</td>
-	<td valign="top">If internal references should be considered during the search.
-		<br><br>Default is <code>false</code>.</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-	<td valign="top">considerapi</td>
-	<td valign="top">If API references should be considered during the search.
-		<br><br>Default is <code>false</code>.</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-	<td valign="top">apipatterns</td>
-	<td valign="top">A comma separated list of package name patterns (regular expressions) to consider as API packages.
-		<br><br>By default API descriptions are used in the scanned bundles, but this can be used to
-		override or add API packages.</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-	<td valign="top">internalpatterns</td>
-	<td valign="top">A comma separated list of package name patterns (regular expressions) to consider as private packages.
-		<br><br>By default API descriptions are used in the scanned bundles, but this can be used to
-		override or add private packages.</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-	<td valign="top">debug</td>
-	<td valign="top">Set the debug value.
-		<br><br>The possible values are: <code>true</code>, <code>false</code>
-		<br>Default is <code>false</code>.</td>
-	<td align="center" valign="top">No</td>
-</tr>
-</table>
-
-<h3>Examples</h3>
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.apiuse
-		location=<font color="#008000">"/eclipse/eclipse.tar.gz"</font>
-		scopepattern=<font color="#008000">".*"</font>
-		referencepattern=<font color="#008000">"org\.eclipse.*"</font>
-		report=<font color="#008000">"/eclipse/apiuse-both/XML"</font>
-		considerinternal=<font color="#008000">"true"</font>
-		considerapi=<font color="#008000">"true"</font>
-		debug=<font color="#008000">"true"</font>
-	/&gt;</font></b>
-</pre>
-<p>This will run the task creating <code>*.xml</code> files inside the folder <code>/eclipse/apiuse-both/XML</code>.
-The task will search all bundles in the product location - defined by the regular expression <code>.*</code> - searching 
-for all references to any bundles whose identifier begins with org.eclipse (defined by the <code>org\.eclipse.*</code> regular expression).
-<p>If debug is enabled, some debug tracing will show up in the ant console.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="apifreeze-ant-task.htm">API Tools API Freeze Ant Task</a>
-<br><a href="filegeneration-ant-task.htm">API Tools File Generation Ant Task</a>
-<br><a href="analysis-reportconversion-ant-task.htm">API Tools Analysis Report Conversion Ant Task</a>
-<br><a href="apifreeze-reportconversion-ant-task.htm">API Tools API Freeze Report Conversion Ant Task</a>
-<br><a href="apiuse-reportconversion-ant-task.htm">API Tools API Use Report Conversion Ant Task</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-reportconversion-ant-task.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-reportconversion-ant-task.htm
deleted file mode 100644
index 438cfc1..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/apiuse-reportconversion-ant-task.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../apache_style.css" type="text/css">
-<title>API Use Report Conversion Ant Task</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Use Report Conversion Ant Task </h1>
-<h2>Purpose</h2>
-<p>This task converts the XML report created by the <code>apitooling.apiuse</code> ant task into HTML files.</p>
-<h2>Usage</h2>
-<h3>Description</h3>
-<p>The name of the ant task is: <code>apitooling.apiuse_reportconversion</code>. To be used, the jar file <code>apitooling-ant.jar</code> has to be on the ant
-classpath.</p>
-<div style="text-align: left;">
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.apiuse_reportconversion
-		xmlfiles=<font color="#008000">"..."</font>
-		htmlfiles=<font color="#008000">"..."</font>
-		xsltfile=<font color="#008000">"..."</font>
-		debug=<font color="#008000">"..."</font>
-	/&gt;</font></b>
-</pre>
-</div>
-<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
-  <tr>
-    <td valign="top"><b>Attribute</b></td>
-    <td valign="top"><b>Description</b></td>
-    <td align="center" valign="top"><b>Required</b></td>
-  </tr>
-<tr>
-	<td valign="top">xmlfiles</td>
-	<td valign="top">This attribute specifies the location of the xml files to convert.
-	<br><br>
-	The location is specified using an absolute path.
-	</td>
-	<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-	<td valign="top">htmlfiles</td>
-	<td valign="top">This attribute specifies the location of the html files to generate.
-	<br><br>
-	The location is specified using an absolute path.
-	</td>
-	<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-	<td valign="top">xsltfile</td>
-	<td valign="top">This attribute specifies the location of an XSLT file to be used to generate the reference details pages in a desired ordering.
-	<br><br>
-	A default XSLT file is available in the <code>apitooling-ant.jar</code> JAR file.
-	<br><br>
-	The location is specified using an absolute path.
-	</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-	<td valign="top">debug</td>
-	<td valign="top">Set the debug value.
-	<br><br>The possible values are: <code>true</code>, <code>false</code>
-	<br>Default is <code>false</code>.
-	</td>
-	<td align="center" valign="top">No</td>
-</tr>
-</table>
-
-<h3>Examples</h3>
-
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.apiuse_reportconversion
-		xmlfiles=<font color="#008000">"/eclipse/apiuse-both/XML"</font>
-		htmlfiles=<font color="#008000">"/eclipse/apiuse-both/HTML"</font>
-		xsltfile=<font color="#008000">"/eclipse/references.xsl"</font>
-		debug=<font color="#008000">"true"</font>
-	/&gt;</font></b>
-</pre>
-<p>This will run the task creating <code>*.html</code> files inside the folder <code>/eclipse/apiuse-both/HTML</code> corresponding 
-to the folder structure of the XML file location</p>
-<p>If debug is enabled, some debug tracing will show up in the ant console.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="analysis-ant-task.htm">API Tools Analysis Ant Task</a>
-<br><a href="filegeneration-ant-task.htm">API Tools File Generation Ant Task</a>
-<br><a href="apiuse-ant-task.htm">API Tools API Use Ant Task</a>
-<br><a href="apifreeze-ant-task.htm">API Tools API Freeze Ant Task</a>
-<br><a href="analysis-reportconversion-ant-task.htm">API Tools Analysis Report Conversion Ant Task</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/filegeneration-ant-task.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/filegeneration-ant-task.htm
deleted file mode 100644
index 5a0564c..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/ant-tasks/filegeneration-ant-task.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../apache_style.css" type="text/css">
-<title>API Tools File Generation Ant Task</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Tools File Generation Ant Task </h1>
-<h2>Purpose</h2>
-<p>This task runs to generate all files required by Api Tooling inside a binary bundle. This task is run
-during the Eclipse builds or during the bundle export for all projects
-that have an Api Tooling nature.
-</p>
-<p>Right now, only the file called <code>.api_description</code> is created.</p>
-<h2>Usage</h2>
-<h3>Description</h3>
-<p>The name of the ant task is: <code>apitooling.apigeneration</code>. To be used, the jar file <code>apitooling-ant.jar</code> has to be on the ant
-classpath.</p>
-<div style="text-align: left;">
-<pre style="margin-left: 40px">
-<b><font color="#0000ff">&lt;apitooling.apigeneration
-	projectname=<font color="#008000">"..."</font>
-	project=<font color="#008000">"..."</font>
-	binary=<font color="#008000">"..."</font>
-	target=<font color="#008000">"..."</font>
-	debug=<font color="#008000">"..."</font>
-/&gt;</font></b>
-</pre>
-</div>
-<h3>Parameters</h3>
-<table border="1" cellpadding="2" cellspacing="0">
-  <tr>
-    <td valign="top"><b>Attribute</b></td>
-    <td valign="top"><b>Description</b></td>
-    <td align="center" valign="top"><b>Required</b></td>
-  </tr>
-<tr>
-<td valign="top">projectname</td>
-<td valign="top">Set the project name
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">project</td>
-<td valign="top">Set the project location.
-<br><br>This is the folder that contains all the source files for the given project.
-<br><br>The location is set using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">binary</td>
-<td valign="top">Set the binary locations.
-<br><br>This is a list of folders or jar files that contain all the .class files for the given project.
-They are separated by the platform path separator. Each entry must exist.
-<br><br>They should be specified using absolute paths.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-<td valign="top">target</td>
-<td valign="top">Set the target location.
-<br><br>This is the folder in which the generated files are generated.
-<br><br>The location is set using an absolute path.
-</td>
-<td align="center" valign="top">Yes</td>
-</tr>
-<tr>
-	<td valign="top">debug</td>
-	<td valign="top">Set the debug value.
-		<br><br>The possible values are: <code>true</code>, <code>false</code>
-		<br>Default is <code>false</code>.</td>
-	<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">extraManifests</td>
-<td valign="top">Set the extra manifest files' locations.
-<br><br>This is a list of extra MANIFEST.MF files' locations that can be set to provide more api
- packages to scan. They are separated by the platform path separator. Each entry must exist.
-<br><br>They should be specified using absolute paths.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-<tr>
-<td valign="top">extraSourceLocations</td>
-<td valign="top">Set the extra source locations.
-<br><br>This is a list of locations for source files that will be scanned.
-They are separated by the platform path separator. Each entry must exist.
-<br><br>They should be specified using absolute paths.
-</td>
-<td align="center" valign="top">No</td>
-</tr>
-</table>
-
-<h3>Examples</h3>
-
-<pre>
-	<b><font color="#0000ff">&lt;apitooling.apigeneration
-		projectname=<font color="#008000">"org.eclipse.jdt.core_3.5.0.v_927"</font>
-		project=<font color="#008000">"d:\eclipse\org.eclipse.jdt.core"</font>
-		binary=<font color="#008000">"d:\eclipse\org.eclipse.jdt.core\bin;d:\eclipse\org.eclipse.jdt.core\antbin"</font>
-		target=<font color="#008000">"d:\plugins\org.eclipse.jdt.core"</font>
-		debug=<font color="#008000">"true"</font>
-	/&gt;</font></b>
-</pre>
-<p>This will create a file called <code>.api_description</code> inside the folder <code>d:\plugins\org.eclipse.jdt.core</code> based
-on the source contained in <code>d:\eclipse\org.eclipse.jdt.core</code> and the .class files contained in
-<code>d:\eclipse\org.eclipse.jdt.core\bin</code>.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="analysis-ant-task.htm">API Tools Analysis Ant Task</a>
-<br><a href="apifreeze-ant-task.htm">API Tools API Freeze Ant Task</a>
-<br><a href="apiuse-ant-task.htm">API Tools API Use Ant Task</a>
-<br><a href="analysis-reportconversion-ant-task.htm">API Tools Analysis Report Conversion Ant Task</a>
-<br><a href="apifreeze-reportconversion-ant-task.htm">API Tools API Freeze Report Conversion Ant Task</a>
-<br><a href="apiuse-reportconversion-ant-task.htm">API Tools API Use Report Conversion Ant Task</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_javadoc_tags.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_javadoc_tags.htm
deleted file mode 100644
index 4f6f00d..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_javadoc_tags.htm
+++ /dev/null

@@ -1,108 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../book.css" type="text/css">
-  <title>API Tooling Javadoc Tags</title>
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h1>Defining API Restrictions </h1>
-<p>API tooling provides Javadoc tags to explicitly document and restrict the use of API. The following tables summarizes the Javadoc tags supported by each  member and the semantics of each tag.</p>
-<p>A <em>client</em> refers to a plug-in or bundle that requires the bundle where the associated API is defined. Restrictions are not applied in the same bundle where API is defined. For example, a bundle that defines an interface as @noimplement is also allowed to provide an implementation of that interface.</p>
-<h4>Supported Restriction Tags </h4>
-<table width="100%" border="1" cellspacing="0" cellpadding="2">
-  <tr>
-    <th scope="col">&nbsp;</th>
-    <th scope="col">Class</th>
-    <th scope="col">Interface</th>
-    <th scope="col">Method</th>
-    <th scope="col">Constructor</th>
-    <th scope="col"><p>Final Field </p>    </th>
-    <th scope="col">Non-Final Field </th>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@noimplement</div></th>
-    <td><div align="center">-</div></td>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@noextend</div></th>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@noinstantiate</div></th>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@nooverride</div></th>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@noreference</div></th>
-    <td><div align="center">-</div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-    <td><div align="center">-</div></td>
-    <td><div align="center"><img src="images/ok.gif" alt="Supported" width="16" height="16"></div></td>
-  </tr>
-</table>
-<h4>Restriction Semantics</h4>
-<table width="100%" border="1" cellspacing="0" cellpadding="2">
-  <tr>
-    <th scope="row"><div align="left">@noimplement</div></th>
-    <td><p>Indicates that clients must not implement this interface. Any class using the <em>implements</em> keyword for the associated interface or parent of the associated interface where there is no implementing superclass will be flagged with problem. </p>    </td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@noextend</div></th>
-    <td><div align="left">Indicates that clients must not extend this class or interface. Any class or interface using the <em>extends</em> keyword for the associated type will be flagged with a problem.</div></td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@noinstantiate</div></th>
-    <td><div align="left">Indicates that clients must not instantiate this class. Any code that instantiates the associated class with any constructor will be flagged with a problem.</div></td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@nooverride</div></th>
-    <td><div align="left">Indicates that clients must not redeclare this method. Any subclass that defines a method that overrides the associated method will be flagged with a problem.</div></td>
-  </tr>
-  <tr>
-    <th scope="row"><div align="left">@noreference</div></th>
-    <td> Indicates that clients must not reference this method, constructor, or non-final field. Any code that directly invokes the associated method or constructor or references the associated non-final field will be flagged with a problem.</td>
-  </tr>
-</table>
-<br>
-<p> <img border="0" src="../../images/ngrelt.png" alt="Related tasks"> </p>
-<p> 
-<a href="../../tasks/api_tooling_baseline.htm">Setting up a baseline</a>
-</p>
-<p><img src="../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="api_since_tags.htm">Javadoc @since tag Management</a><br>
-<a href="preferences/ref-baselines.htm">API Baselines Preferences</a><br>
-<a href="preferences/ref-errorswarnings.htm">API Errors and Warnings Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_since_tags.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_since_tags.htm
deleted file mode 100644
index b8f9923..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/api_since_tags.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../book.css" type="text/css">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  <title>Javadoc @since Tag Management</title>
-</head>
-<body>
-<h1> Javadoc @since Tag Management</h1>
-<p>API tooling provides support for management of <code>@since</code> Javadoc tags on new elements that have been added to API (types, methods, fields, etc). 
-New API elements could be a new type added to an API package, a new type added to an API type, a new method added to an API type or a new field added to an API type.
-Method addition is a special case, where a method addition could be adding a method to a type, overriding a parent class method, implementing a parent interface method 
-or changing an existing methods' signature.
-</p>
-<p>
-Note: <code>@since</code> tag information is not propagated via implementation or sub-classing. Each element that is added to API is expected to have 
-its' own <code>@since</code> tag and version information.
-</p>
-<p>
-The tooling provides the following validation for <code>@since</code> tags:
-</p>
-<ul>
-	<li><a href="#missing">Missing <code>@since</code> tags</a></li>
-	<li><a href="#malformed">Malformed <code>@since</code> tags</a></li>
-	<li><a href="#invalid">Invalid <code>@since</code> tag versions</a></li>
-</ul>
-<p>The preferences for <code>@since</code> tag management can be changed on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apitools.errorwarnings.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page"> <b>Plug-in Development &gt; API Errors/Warnings</b></a> preference page.</p>
-<a id="missing"></a>
-<h2>Missing @since tags</h2>
-<p>
-Every new API element detected will be checked by the tooling to ensure it has an <code>@since</code> tag. 
-If the new element does not have an <code>@since</code> tag, it will be flagged as needing one, and a version for the tag will be proposed.
-The proposed version for the new tag will be the current version of the bundle - except in the case of a breaking API change where the bundle
-version also needs to be updated. If the bundle version also needs to be updated, the proposed version for the missing <code>@since</code> tag will be that of the proposed
-bundle version.  
-</p>
-<p>
-Consider the following example: we have a bundle A with version 1.0.0 and we have a class C that was added in version 1.1.0 of A which contains method m1().
-</p>
-<ul>
-<li>If we add a new method to C, say m2(), the tooling will report a missing <code>@since</code> tag problem on m2() and suggest
-that a new tag of <code>@since 1.1</code> be placed on m2().</li>
-<li>If we add a new method to C, say m2() again and we change m1() - introduce a breaking API change - the tooling will report a 
-missing <code>@since</code> tag problem on m2() and suggest that a new tag of <code>@since 2.0</code> be place on m2(). Where <code>2.0.0</code>
-is the new proposed bundle version.</li>
-</ul>
-<a id="malformed"></a>
-<h2>Malformed @since tags</h2>
-<p>
-New elements can have their <code>@since</code> tags checked for consistency to ensure they are properly formulated. API tools 
-checks that all <code>@since</code> tags follow the general format of: <br><br>
-<code>[@since] [pre-amble] [2 part version] [post-amble]</code>
-</p>
-<p>
-Consider the following <code>@since</code> tag examples:
-</p>
-<ul>
-<li><code>@since A 1 added m2()</code>: would be flagged as malformed because the version is missing the second segment</li>
-<li><code>@since</code>: would flagged as malformed since there is no version information</li>
-<li><code>@since A</code>: would be flagged since there is no version information</li>
-<li><code>@since 1.0.0</code>: would be flagged since the version has too many segments</li>
-<li><code>@since A 1.0 added m2()</code>: would not be flagged</li>
-</ul>
-<a id="invalid"></a>
-<h2>Invalid @since tag versions</h2>
-<p>
-New elements can also have their <code>@since</code> tags checked for validity. An <code>@since</code> tag is considered to be valid
-if the version information in the tag matches the version of the bundle.
-</p>
-<p>
-Consider the following example where we have added a new method m2() to an API class in bundle A whose version is 1.0.0:
-</p>
-<ul>
-<li><code>@since A 1.0 added method m2()</code>: is considered valid</li>
-<li><code>@since A 2.0 added method m2()</code>: is invalid since the version of bundle A is 1.0.0</li>
-<li><code>@since A 0.1 added method m2()</code>: is invalid since the version of bundle A is 1.0.0</li>
-</ul>
-<p> 
-	<img border="0" src="../../images/ngrelt.png" alt="Related tasks"><br>
-	<a href="../../tasks/api_tooling_baseline.htm">Setting up a baseline</a>
-</p>
-<p>
-	<img src="../../images/ngrelr.png" alt="Related reference" border="0"><br>
-	<a href="preferences/ref-baselines.htm">API Baselines Preferences</a><br>
-	<a href="preferences/ref-errorswarnings.htm">API Errors and Warnings Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-compare-wizard.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-compare-wizard.png
deleted file mode 100644
index 93b51c7..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-compare-wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-problem-filter-prop.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-problem-filter-prop.png
deleted file mode 100644
index 92eaa31..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-problem-filter-prop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard-preview.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard-preview.png
deleted file mode 100644
index cded0e7..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard-preview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard.png
deleted file mode 100644
index 349cb14..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api-setup-wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_analysis.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_analysis.png
deleted file mode 100644
index b08c305..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_analysis.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_compatibility.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_compatibility.png
deleted file mode 100644
index eea48b3..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_compatibility.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_usage.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_usage.png
deleted file mode 100644
index f7c151c..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_usage.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_version.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_version.png
deleted file mode 100644
index c83f90e..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_options_version.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_tooling.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_tooling.png
deleted file mode 100644
index 5ee7e81..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/api_tooling.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-pref-page.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-pref-page.png
deleted file mode 100644
index 3a0c0e8..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-pref-page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf-dialog.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf-dialog.png
deleted file mode 100644
index c8e7c79..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf-dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf.png
deleted file mode 100644
index da70e58..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/baseline-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/error_ovr.gif b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/error_ovr.gif
deleted file mode 100644
index c112416..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/error_ovr.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/errorwarning-prop-page.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/errorwarning-prop-page.png
deleted file mode 100644
index 96f3fbf..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/errorwarning-prop-page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-dialog-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-dialog-qf.png
deleted file mode 100644
index 0070f73..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-dialog-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-qf.png
deleted file mode 100644
index a85aec7..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/filter-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/ok.gif b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/ok.gif
deleted file mode 100644
index 689e523..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/ok.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-dialog-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-dialog-qf.png
deleted file mode 100644
index c1174e8..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-dialog-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-editor-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-editor-qf.png
deleted file mode 100644
index a720aa6..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-editor-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-qf.png
deleted file mode 100644
index 3823181..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/remove-filter-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-dialog-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-dialog-qf.png
deleted file mode 100644
index 9c429b6..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-dialog-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-editor-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-editor-qf.png
deleted file mode 100644
index 1520f4a..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-editor-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-qf.png
deleted file mode 100644
index b2f292a..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/sincetag-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/success_ovr.gif b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/success_ovr.gif
deleted file mode 100644
index 20fc2f2..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/success_ovr.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-dialog-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-dialog-qf.png
deleted file mode 100644
index cc47b98..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-dialog-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-editor-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-editor-qf.png
deleted file mode 100644
index 4fa0701..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-editor-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-qf.png b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-qf.png
deleted file mode 100644
index 889b0c8..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/images/version-qf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-baselines.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-baselines.htm
deleted file mode 100644
index fb421dc..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-baselines.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" type="text/css">
-<title>API Baselines Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Baselines Preferences </h1>
-<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apiprofiles.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the API Baselines preference page"> <b>Plug-in Development &gt; API Baselines</b></a> preference page. </p>
-<p>An API baseline defines the state you want to compare your development workspace bundles against for the purposes of binary compatibility, bundle version numbers, and @since tags. For example, if you are developing bundles for Eclipse 3.4, you could use Eclipse 3.3 as your baseline.</p>
-<p>
-	<img src="../images/baseline-pref-page.png" alt="API baseline preference page">
-</p>
-<br>
-<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1" width="5%"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">Add Baseline...</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">Allows you to add a new API baseline.</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Edit...</td>
-      <td colspan="1" valign="top" align="left">Allows you to edit a selected API baseline.</td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Remove</td>
-      <td colspan="1" valign="top" align="left">Allows you to remove the selected API baseline(s).</td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Missing API baseline</td>
-      <td colspan="1" valign="top" align="left">This preference is used to notify you when the API builder is going to run and you do not have a default API baseline set.</td>
-      <td colspan="1" valign="top" align="left">Warning</td>
-    </tr>
-  </tbody>
-</table>
-<br>
-<p><img src="../../../images/ngrelt.png" alt="Related tasks"></p>
-<p> <a href="../../../tasks/api_tooling_baseline.htm">Setting up an API  baseline</a> </p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p><a href="ref-errorswarnings.htm">API Errors and Warnings Preferences</a><br>
-  <a href="../quickfixes/ref-api-missing-baseline-qf.htm">Missing API Baseline Quickfix</a><br>
-  <a href="../wizards/ref-api-baseline-wizard.htm">API Baseline Wizard</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-errorswarnings.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-errorswarnings.htm
deleted file mode 100644
index ae21aff..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/preferences/ref-errorswarnings.htm
+++ /dev/null

@@ -1,681 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" type="text/css">
-<title>API Errors and Warnings Preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Errors and Warnings Preferences </h1>
-	<p> The following preferences can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apitools.errorwarnings.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page"> <b>Plug-in Development &gt; API Errors/Warnings</b></a> preference page.  
-	</p>
-	<p>
-		API problems are created during project builds (auto and full builds), the tooling breaks down the types of problems reported into one of three categories:</p>
-<ol>
-   <li><strong><a href="#usage">Usage Problems</a></strong> - restricted code is being called by unauthorized plug-ins</li>
-		   <li><strong><a href="#compat">API Incompatibilities</a></strong> - changes between versions are not compatible</li>
-		   <li><strong><a href="#version">Version Problems</a></strong> - plug-in versions or code versions (@since tags) not correct</li>
-		   <li><strong><a href="#analysis">Analysis Options</a></strong> - general options</li>
-</ol>
-	    <p>You can also configure the problem severities on a per project basis as well, 
-		by using the <a href="../propertypages/ref-errorswarnings-prop.htm"><strong>API Errors/Warnings</strong></a> property page for a project<br>
-</p>
-	
-	<h2><a name="usage"></a>API Use</h2>
-	<p>
-	<img src="../images/api_options_usage.png" alt="API Usage option preference page">
-	</p>
-	<h3>General</h3>
-		<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" width="5%" align="center"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Unsupported use of API Javadoc Tags</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check for API Javadoc tags used incorrectly.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Ignore</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Invalid references to system libraries</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check for references to system libraries that might
-			  be illegal according to the execution environment specified for the bundle.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Ignore</p></td>
-			</tr>
-		  </tbody>
-		</table>
-	<h3>Restrictions</h3>
-		<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"><p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  <tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Implementing an interface marked as '@noimplement'</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check for illegal implementation of marked interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Extending a type marked '@noextend'</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check for classes that extend marked types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Referencing a field or method marked '@noreference'</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check for field and method references to tagged members.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Instantiating a class tagged '@noinstantiate'</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check that tagged classes are not instantiated.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Overriding a method marked as '@nooverride'</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check that tagged methods in parent classes are not overridden in any child class either by extending (re-implement with a call to the overridden parent) or re-implementing (with no call to the overridden parent).</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h3>Leaks</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  <tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Extends a non-API class</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API classes extend non-API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Implements a non-API interface</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API classes implement a non-API interface</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Field with non-API type</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API types have public or protected fields with non-API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Method with a non-API return type</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API types have public or protected methods with non-API return types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Method with non-API parameter type</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API types have public or protected methods with non-API parameter types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h2><a name="compat"></a>API Compatibility</h2>
-	<p>
-	<img src="../images/api_options_compatibility.png" alt="API Compatibility option preference page">
-	</p>
-	<p>
-	</p>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  <tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Report API breakage even if authorized by major version increment</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will report problems for API breakages even if the major version of the bundle has already been incremented.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Disabled</p></td>
-			</tr>
-		  </tbody>
-	</table>
-	<h3>Bundle</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  <tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>An API  type has become non-API</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API types in the current bundle have been changed to non-API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-		</tr>
-		<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API types have been removed from the API scope in the given bundle.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  <tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>An API re-exported type has become non-API</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API re-exported types in the current bundle have been changed to non-API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-		</tr>
-		<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A re-exported type has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API re-exported types have been removed from the API scope in the given bundle.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h3>Class</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  	<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A method (that needs to be implemented) has been added:</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected methods that need to be implemented have been added to any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Restrictions have been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if API restrictions have been added for any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any type parameters have been added to any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The superinterfaces hierarchy has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any parent interfaces have been removed from any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'abstract' has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the 'abstract' keyword has been added to any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'final' has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the 'final' keyword has been added to any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Converted to annotation, enum, or interface</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API classes have been changed to annotations, enums, or interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The visibility has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public API classes have been made private or default scope.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A field has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected fields have been removed from any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A method has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected methods have been removed from any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A constructor has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected constructors have been removed from any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The superclass hierarchy has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any superclasses have been removed from the hierarchy.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>			
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A member type has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any member types have been removed from any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any type parameters have been removed from any API classes.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h3>Interface</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  	<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A field (interface not tagged as '@noimplement') has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public fields have been added to any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A method (interface not tagged as '@noimplement') has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public methods have been added to any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Restrictions have been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if API restrictions have added for any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any type parameters have been added to any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Converted to class, enum, or annotation</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API interfaces have been changed to classes, enums, or interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The superinterfaces hierarchy has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any parent interfaces have been removed for any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any type parameters have been removed from any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A field has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public fields have been removed from any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A method has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public methods have been removed from any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A member type has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if nay member types have been removed from any API interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h3>Enum</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  <tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The superinterfaces hierarchy has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any parent interfaces have been removed from any API enums.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Converted to annotation, class, or interface</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API enums have been changed to annotations, classes, or interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A field has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public fields have been removed from any API enums.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>An enum constant has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any enum constants have been removed from any API enums.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A method has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public methods have been removed from any API enums.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A member type has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any member types have been removed from any API enums.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h3>Annotation</h3>
-		<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A method without a default value has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a method without a default value has been added to API annotations.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Converted to class, enum, or interface</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any API annotations have been converted to classes, enums or interfaces.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A field has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public fields have been removed from any API annotations.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A method has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public methods have been removed from any API annotations.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A member type has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public member types have been removed from any API annotations.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-		</table>
-	<h3>Field</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  <tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A constant value has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a constant value has been added to any previously un-initialized public or protected field constants for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The type has been modified</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the type of any public or protected fields has been changed for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The constant value has been modified</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the value of any public or protected field constants has been changed in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The visibility has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected fields have been made private in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'final' has been removed for static constant</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected fields have had the final keyword removed in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'final' has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the final keyword has been added to any public or protected fields in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'static' has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the static keyword has been removed from any public or protected fields in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'static' has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the static keyword has been added to any public or protected fields in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The constant value has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the value of a constant field has been removed for any public or protected field constants in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type argument has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a type argument has been removed from any public or protected fields in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h3>Method</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The @nooverride restriction has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the restrictions of any public or protected methods have been changed in any API types by adding the @nooverride tag.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a type parameter has been added to any public or protected methods for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Converted variable argument to array type</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a varargs argument has been expanded to an object array for any public or protected methods for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The visibility has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected methods have been made private for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'abstract' has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected methods have been made abstract in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'static' has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected methods have been made static in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'static' has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected methods have been made non-static in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The keyword 'final' has been added (type tagged '@noextend')</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public or protected methods have been made final in any API types that have been tagged @noextend.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The annotation default value has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the default value associated with any API annotation method has been removed.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a type parameter has been removed from any public or protected methods for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h3>Constructor</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a type parameter has been added to any public constructors for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Converted variable argument to array type</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any varargs parameters have been expanded to object arrays for any public constructors for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>The visibility has been reduced</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any public constructors have been made non-public in any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A type parameter has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a type parameter has been removed from any public constructors for any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>	
-	<h3>Type Parameter</h3>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-		  	<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A class bound has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if a class bound has been added to any type parameter of any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>An interface bound has been added</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any interface bounds have been added to any type parameter of any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A class bound has been modified</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any class bounds have been changed on any type parameter of any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>An interface bound has been modified</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any interface bounds have been changed on any type parameter of any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>A class bound has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any class bounds have been removed from any type parameter of any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>An interface bound has been removed</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any interface bounds have been removed from any type parameter of any API types.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-		  </tbody>
-</table>
-	<h2><a name="version" id="version"></a>Version Management</h2>
-	<p>
-	<img src="../images/api_options_version.png" alt="API Version Management option preference page">
-	</p>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Report missing '@since' tags</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if @since tags are missing for types or members added since the version of the API baseline in use.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Report malformed '@since' tags</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any @since tags currently in use are malformed (incorrect syntax).</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Report invalid '@since' tag version</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if any @since tags currently in use have the wrong version.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Report incompatible bundle version</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will check if the bundle version for the plug-in is incorrect, based on any API changes and the current API baseline in use.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Ignore minor version increment without API changes</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>If reporting for incompatible version numbers is enabled, this option can be used to tell the API analysis builder to ignore minor version changes if there has not been an API change compared to the current API baseline.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>On</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Ignore major version increment without API changes</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>If reporting for incompatible version numbers is enabled, this option can be used to tell the API analysis builder to ignore major version changes if there has not been an API change compared to the current API baseline.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>On</p></td>
-			</tr>
-		  </tbody>
-		</table>
-	<h2><a name="analysis" id="analysis"></a>Analysis Options</h2>
-	<p>
-	<img src="../images/api_options_analysis.png" alt="Analysis options preference page">
-	</p>
-	<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-		  <thead>
-			<tr>
-			  <th rowspan="1" colspan="1" width="30%"> <p> Option </p></th>
-			  <th rowspan="1" colspan="1"> <p> Description </p></th>
-			  <th rowspan="1" colspan="1" align="center" width="5%"> <p> Default </p></th>
-			</tr>
-		  </thead>
-		  <tbody>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Bundle missing required constraint/prerequisite</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will report any missing required constraint or prerequisite that prevents the builder from performing a complete analysis. Regardless of the value of this option
-			  the analysis is skipped for the corresponding bundle.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Error</p></td>
-			</tr>
-			<tr>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>Unused API problem filters</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="left"><p>When enabled the API analysis builder will report any API problem filters that are no longer being used.</p></td>
-			  <td rowspan="1" colspan="1" valign="top" align="center"><p>Warning</p></td>
-			</tr>
-		  </tbody>
-		</table>
-<br>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../propertypages/ref-errorswarnings-prop.htm">API Errors and Warnings Property Page</a><br>
-<a href="ref-baselines.htm">API Baselines Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-errorswarnings-prop.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-errorswarnings-prop.htm
deleted file mode 100644
index 715f0ba..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-errorswarnings-prop.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" type="text/css">
-<title>API Errors and Warnings Property Page</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Errors and Warnings Property Page </h1>
-	<p>API problems are created during project builds (auto and full builds), the tooling breaks down the types of problems reported into one of three categories:</p>
-   <ol>
-	   <li><strong>Usage Problems</strong> - restricted code is being called by unauthorized plug-ins.</li>
-	   <li><strong>Binary Incompatibilities</strong> - changes between versions are not binary compatible.</li>
-	   <li><strong>Version Problems</strong> - plug-in versions or code versions (@since tags) not correct.</li>
-   </ol>
-   <p><img src="../images/errorwarning-prop-page.png" alt="API Error and Warnings property page"></p>
-   <p> You can also configure the problem severities for the entire workspace as well using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apitools.errorwarnings.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the API Errors and Warnings preference page"> <b>Plug-in Development &gt; API Errors/Warnings</b></a> preference page.  </p>
-<p>For a complete listing of the preferences and their descriptions, please refer to the API Errors/Warnings preference page.</p>
-
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../preferences/ref-errorswarnings.htm">API Errors and Warnings Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-filters-prop.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-filters-prop.htm
deleted file mode 100644
index 00c9d49..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/propertypages/ref-filters-prop.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="stylesheet" href="../../../book.css" type="text/css">
-<title>API Problem Filters Property Page</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1> API Problem Filters Property Page </h1>
-	<p>API problems are created during project builds (auto and full builds), but sometimes there are problems reported that are <em>known</em> or <em>expected</em> which cannot be readily fixed. These problems <strong><a href="../../../tasks/api_tooling_create_filters.htm">can be filtered</a></strong>.	</p>
-	<p>
-	 Once a problem filter has been created, it can be viewed or removed using the API Problem Filters property page. </p>
-	<p>To locate this property page:</p>
-		<ol>
-			<li>Open the context menu for any API tooling enabled project and select <strong>Properties</strong>.</li>
-			<li>Navigate to <strong>Plug-in Development &gt; API Problem Filters</strong>.</li>
-		</ol>
-<img src="../images/api-problem-filter-prop.png" alt="API Problem Filters property page">
-<p><img src="../../../images/ngrelt.png" alt="Related tasks"></p>
-<p>
-<a href="../../../tasks/api_tooling_create_filters.htm">Creating filters</a><br>
-<a href="../../../tasks/api_tooling_remove_filters.htm">Removing filters</a>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="ref-errorswarnings-prop.htm">API Errors and Warnings Property Page</a><br>
-<a href="../preferences/ref-errorswarnings.htm">API Errors and Warnings Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm
deleted file mode 100644
index 5b86b31..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <title>Add API Problem Filter Quickfix</title>
-</head>
-<body>
-<h1>Add API Problem Filter Quickfix</h1>
-<p>This quickfix can be used to quickly create an API problem filter for a known or expected API problem that cannot be easily corrected.</p>
-<p>This quick fix is available in one of two places:</p>
-<ol>
-  <li><a href="#problems"><strong>The Problems view</strong></a>.</li>
-  <li><strong><a href="#editing">Editing the resource</a></strong> the problem exists in.
-</li>
-</ol>
-<h3><a name="problems" id="problems"></a>The Problems view</h3>
-<ul>
-  <li>Open the <b>Problem</b> view.</li>
-  <li>Select an API Tooling problem.
-  <p><img src="../images/filter-qf.png" alt="API problem selected in problems view"></p>
-  </li>
-  <li>Use <b>Ctrl + 1</b> to trigger the quickfix from the problem view (or use the context menu as shown above).
-  <p><img src="../images/filter-dialog-qf.png" alt="Filter API problem quickfix dialog"></p>
-  </li>
-</ul>
-<h3><a name="editing" id="editing"></a>Editing the resource</h3>
-<ul>
-  <li>Open the resource the API problem exists in.</li>
-  <li>Use <b>Ctrl + 1</b> on the corresponding problem.
-  	<p><img src="../images/version-editor-qf.png" alt="Filter quickfix in an editor"></p>
-  </li>
-</ul>
-<br>
-<p>Once the problem filter has been created the corresponding resource is rebuilt and the problem is removed from the Problems view and any open editors.</p>
-<br>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> 
-<a href="../../../tasks/api_tooling_create_filters.htm">Creating API Problem Filters</a><br>
-<a href="../../../tasks/api_tooling_remove_filters.htm">Removing filters</a><br>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../propertypages/ref-filters-prop.htm">API Problem Filters Property Page</a><br>
-<a href="ref-api-missing-baseline-qf.htm">Missing API Baseline Quickfix</a><br>
-<a href="ref-api-version-qf.htm">Version Numbering Quickfix</a><br>
-<a href="ref-api-sincetag-qf.htm">Since Tag Quickfix</a><br>
-<a href="ref-api-remove-api-filter-qf.htm">Remove Unused Problem Filter Quickfix</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-missing-baseline-qf.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-missing-baseline-qf.htm
deleted file mode 100644
index fc95e1a..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-missing-baseline-qf.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-  <title>Missing API Baseline Quickfix</title>
-</head>
-<body>
-<h1>Missing API Baseline Quickfix</h1>
-<p>This quickfix can be used to quickly help resolve missing API baseline problems.</p>
-<p>This quickfix is available in the Problems view.</p>
-<h3>The Problems view</h3>
-<ul>
-  <li>Open the <b>Problem</b> view.</li>
-  <li>Select the missing API baseline problem.
-    <p><img src="../images/baseline-qf.png" alt="Missing API baseline problem"></p>
-  </li>
-  <li>Use <b>Ctrl + 1</b> to trigger the quickfix from the problem view (or use the context menu as shown above).
-  <p><img src="../images/baseline-qf-dialog.png" alt="Missing API baseline quickfix dialog"></p>
-  </li>
-</ul>
-<p>Completing the quickfix will open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apiprofiles.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the API Baselines preference page"> <b>Plug-in Development &gt; API Baselines</b></a> preference page, allowing you to create a new baseline using the <a href="../wizards/ref-api-baseline-wizard.htm"><strong>API baseline wizard</strong></a>.</p>
-<br>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> 
-<a href="../../../tasks/api_tooling_baseline.htm">Setting up an API  baseline</a><br>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../preferences/ref-baselines.htm">API Baselines Preferences</a><br>
-<a href="ref-api-api-filter-qf.htm">Add API Problem Filter Quickfix</a><br>
-<a href="ref-api-version-qf.htm">Version Numbering Quickfix</a><br>
-<a href="ref-api-sincetag-qf.htm">Since Tag Quickfix</a><br>
-<a href="ref-api-remove-api-filter-qf.htm">Remove Unused Problem Filter Quickfix</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-remove-api-filter-qf.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-remove-api-filter-qf.htm
deleted file mode 100644
index ba80834..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-remove-api-filter-qf.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <title>Remove API Problem Filter Quickfix</title>
-</head>
-<body>
-<h1>Remove API Problem Filter Quickfix</h1>
-<p>This quickfix can be used to quickly remove an API problem filter for an unsupported API problem filter problem.</p>
-<p>This quick fix is available in one of two places:</p>
-<ol>
-  <li><a href="#problems"><strong>The Problems view</strong></a>.</li>
-  <li><strong><a href="#editing">Editing the resource</a></strong> the problem exists in.
-</li>
-</ol>
-<h3><a name="problems" id="problems"></a>The Problems view</h3>
-<ul>
-  <li>Open the <b>Problem</b> view.</li>
-  <li>Select an API Tooling problem.
-  <p><img src="../images/remove-filter-qf.png" alt="API problem selected in problems view"></p>
-  </li>
-  <li>Use <b>Ctrl + 1</b> to trigger the quickfix from the problem view (or use the context menu as shown above).
-  <p><img src="../images/remove-filter-dialog-qf.png" alt="Remove unused filter API problem quickfix dialog"></p>
-  </li>
-</ul>
-<h3><a name="editing" id="editing"></a>Editing the resource</h3>
-<ul>
-  <li>Open the resource the API problem exists in.</li>
-  <li>Use <b>Ctrl + 1</b> on the corresponding problem.
-  	<p><img src="../images/remove-filter-editor-qf.png" alt="Filter quickfix in an editor"></p>
-  </li>
-</ul>
-<br>
-<p>Once the problem filter has been removed the corresponding resource is rebuilt and the unused filter problem is removed from the Problems view and any open editors.</p>
-<br>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" ></p>
-<p> 
-<a href="../../../tasks/api_tooling_create_filters.htm">Creating API Problem Filters</a><br>
-<a href="../../../tasks/api_tooling_remove_filters.htm">Removing filters</a><br>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../propertypages/ref-filters-prop.htm">API Problem Filters Property Page</a><br>
-<a href="ref-api-missing-baseline-qf.htm">Missing API Baseline Quickfix</a><br>
-<a href="ref-api-version-qf.htm">Version Numbering Quickfix</a><br>
-<a href="ref-api-sincetag-qf.htm">Since Tag Quickfix</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-sincetag-qf.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-sincetag-qf.htm
deleted file mode 100644
index 7cdc51c..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-sincetag-qf.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <title>Since Tag Quickfix</title>
-</head>
-<body>
-<h1>Since Tag Quickfix</h1>
-<p>This quickfix can be used to quickly add since tags or help correct problems with existing since tags.</p>
-<p>This quick fix is available in one of two places:</p>
-<ol>
-  <li><a href="#problems"><strong>The Problems view</strong></a>.</li>
-  <li><strong><a href="#editing">Editing the resource</a></strong> the problem exists in.
-</li>
-</ol>
-<h3><a name="problems" id="problems"></a>The Problems view</h3>
-<ul>
-  <li>Open the <b>Problem</b> view.</li>
-  <li>Select a since tag problem.
-  <p><img src="../images/sincetag-qf.png" alt="Since tag problem quickfix"></p>
-  </li>
-  <li>Use <b>Ctrl + 1</b> to trigger the quickfix from the problem view (or use the context menu as shown above).
-  <p><img src="../images/sincetag-dialog-qf.png" alt="Since tag quickfix dialog"></p>
-  </li>
-</ul>
-<h3><a name="editing" id="editing"></a>Editing the resource</h3>
-<ul>
-  <li>Open the resource the API problem exists in.</li>
-  <li>Use <b>Ctrl + 1</b> on the corresponding problem.
-  	<p><img src="../images/sincetag-editor-qf.png" alt="Since tag problem editor quickfix"></p>
-  </li>
-</ul>
-<br>
-<p>Once the since tag problem has been corrected the corresponding resource is rebuilt and the problem is removed from the Problems view and any open editors.</p>
-<br>
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="ref-api-missing-baseline-qf.htm">Missing API Baseline Quickfix</a><br>
-<a href="ref-api-api-filter-qf.htm">Add API Problem Filter Quickfix</a><br>
-<a href="ref-api-version-qf.htm">Version Numbering Quickfix</a><br>
-<a href="ref-api-remove-api-filter-qf.htm">Remove Unused Problem Filter Quickfix</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-version-qf.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-version-qf.htm
deleted file mode 100644
index 93cbc33..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/quickfixes/ref-api-version-qf.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <title>Version Numbering Quickfix</title>
-</head>
-<body>
-<h1>Version Numbering Quickfix</h1>
-<p>This quickfix is used to quickly and easily correct version numbering problems for your plug-in.</p>
-<p>This quickfix is available in one of two places:</p>
-
-<ol>
-  <li><a href="#problems"><strong>The Problems view</strong></a>.</li>
-  <li><strong><a href="#manifest">The manifest editor</a></strong> for the corresponding manifest file.
-  </li>
-</ol>
-<h3><a name="problems" id="problems"></a>The Problems view</h3>
-<ul>
-  <li>Open the <b>Problem</b> view.</li>
-  <li>Select a version numbering problem.
- 	 <p><img src="../images/version-qf.png" alt="Version numbering problem in the problems view"></p>
-  </li>
-  <li>Use <b>Ctrl + 1</b> to trigger the quickfix from the problem view (or use the context menu as shown above).
-  	<p><img src="../images/version-dialog-qf.png" alt="Version numbering quickfix dialog"></p>
-  </li>
-</ul>
-
-<h3><a name="manifest" id="manifest">The manifest editor</a></h3>
-<ul>
-  <li>Open the <b>manifest editor</b> on the manifest with the version problems.</li>
-  <li>Navigate to the MANIFEST.MF tab.</li>
-  <li>Use <b>Ctrl + 1</b> on the corresponding version problem.
-  	<p><img src="../images/version-editor-qf.png" alt="Version problem editor quickfix"></p>
-  </li>
-</ul>
-<br>
-<p><img src="../../../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="ref-api-missing-baseline-qf.htm">Missing API Baseline Quickfix</a><br>
-<a href="ref-api-api-filter-qf.htm">Add API Problem Filter Quickfix</a><br>
-<a href="ref-api-sincetag-qf.htm">Since Tag Quickfix</a><br>
-<a href="ref-api-remove-api-filter-qf.htm">Remove Unused Problem Filter Quickfix</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/views/ref-api-tooling-view.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/views/ref-api-tooling-view.htm
deleted file mode 100644
index 4bcf9a3..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/views/ref-api-tooling-view.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Api Tooling View</title>
-<script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link href="../../../book.css" rel="stylesheet" type="text/css">
-</head>
-
-<body>
-<h1>Api Tooling View</h1>
-<p>The <strong>Api Tooling</strong> view shows all deltas found between a set of selected elements (project, source folders,
-package fragments, or compilation units) and a reference baseline. The<strong>API Tooling </strong>view is available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.pde.api.tools.ui.views.apitooling.views.apitoolingview)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open API Tooling View">
-<strong>Window &gt; Show View &gt; Other... &gt; API Tooling &gt; API Tooling</strong>
-</a>. </p>
-<p><img src="../images/api_tooling.png" alt="API Tooling" ></p>
-
-<h2>Delta details</h2>
-<p>The view itself is showing only the delta's localized message with an overlay image that tells whether the corresponding delta
-is seen as a compatible (<img src="../images/success_ovr.gif" alt="compatible" >) or an incompatible 
-(<img src="../images/error_ovr.gif" alt="breaking" >) delta.
-<br>
-A double-click on a delta shows additional information inside the property view.</p>
-<p>The additional information are:</p>
-<ul>
-  <li>the component on which the delta is reported,</li>
-  <li>the element type,</li>
-  <li>the flags,</li>
-  <li>the key,</li>
-  <li>the kind,</li>
-  <li>the new modifiers,</li>
-  <li>the old modifiers,</li>
-  <li>the restrictions,</li>
-  <li>the type name,</li>
-  <li>the localized message.</li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-baseline-wizard.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-baseline-wizard.htm
deleted file mode 100644
index 3208d9a..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-baseline-wizard.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-  <title>API Baseline Wizard</title>
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>API Baseline Wizard</h1>
-<p>The API baseline wizard can be used to:</p>
-<ul>
-<li>Add new API baselines to your workspace.</li>
-<li>Edit an existing API baseline.</li>
-</ul>
-<p>The wizard can be used from the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apiprofiles.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the API Baselines preference page"> <b>Plug-in Development &gt; API Baselines</b></a> preference page preference page, by selecting either the <strong>Add Baseline... </strong>button (to add a new baseline) or the <strong>Edit...</strong> button (to edit an existing baseline).</p>
-<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1" width="10%"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1" width="5%"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">Name</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">You can choose any name you want for a baseline with the exception that it cannot contain system restricted characters. For example on Windows, you cannot use '/' in file names.</td>
-      <td rowspan="1" colspan="1" valign="top" align="center">Empty</td>
-    </tr>
-	<tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">Location</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">The location for an API baseline is the path to an Eclipse SDK install, typically a path to the '<em>plugins</em>' folder for the install. </td>
-      <td rowspan="1" colspan="1" valign="top" align="center">Empty</td>
-    </tr>
-	<tr>
-	  <td colspan="1" valign="top" align="left">Browse...</td>
-	  <td colspan="1" valign="top" align="left">Selecting the Browse button will allow you to browse for the location of an Eclipse SDK installation.</td>
-	  <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-	<tr>
-	  <td colspan="1" valign="top" align="left">Reset</td>
-	  <td colspan="1" valign="top" align="left">Selecting the Reset button will re-scan the specified location and recreate the API baseline.</td>
-	  <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<br>
-<p>The API Baseline wizard, showing an example Eclipse 3.3.2 baseline being created.</p>
-<img src="../../../guide/images/tasks/baseline_dialog.png" alt="API Baseline Wizard" border="0">
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks"></p>
-<p> 
-<a href="../../../tasks/api_tooling_baseline.htm">Setting up a baseline</a>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../preferences/ref-baselines.htm">API Baselines Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-compare-wizard.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-compare-wizard.htm
deleted file mode 100644
index 660943f..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-compare-wizard.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" charset="ISO-8859-1" type="text/css">
-  <title>API Compare Wizard</title>
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-</head>
-<body>
-<h1>API Compare Wizard</h1>
-<p>The API compare wizard can be used to compare a selected set of selected elements (projects, source folders, package fragments, or compilation units) to a selected API baseline and show those
-results in the <b><a href="../views/ref-api-tooling-view.htm">API Tooling View</a></b></p>
-<br>
-<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1" width="10%"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1" width="5%"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">Baseline</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">You can choose any API baseline from the combo box to compare to.</td>
-      <td rowspan="1" colspan="1" valign="top" align="center">Default baseline or empty</td>
-    </tr>
-	<tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">Add New Baseline</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">Opens the <b><a href="../preferences/ref-baselines.htm">API Baselines</a></b> preference page so that a new baseline can be added for use. </td>
-      <td rowspan="1" colspan="1" valign="top" align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<br>
-<p>The API Compare wizard, showing an example Eclipse 3.4.1 baseline being compared to.</p>
-<img src="../images/api-compare-wizard.png" alt="API Compare Wizard" border="0">
-<br>
-<p><img border="0" src="../../../images/ngrelt.png" alt="Related tasks"></p>
-<p> 
-<a href="../../../tasks/api_tooling_compare_to_baseline.htm">Comparing to an API baseline</a><br>
-<a href="../../../tasks/api_tooling_baseline.htm">Setting up a baseline</a>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../preferences/ref-baselines.htm">API Baselines Preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-setup-wizard.htm b/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-setup-wizard.htm
deleted file mode 100644
index 8f2bccb..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/api-tooling/wizards/ref-api-setup-wizard.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../../book.css" type="text/css">
-  <title>API Tooling Setup Wizard</title>
-</head>
-<body>
-<h1>API Tooling Setup Wizard</h1>
-<p>Before any plug-in project can make use of API Tooling it must first be set up to use the tooling, which can be done using the API Tooling setup wizard.</p> 
-<p>
-To activate the wizard use the following steps:</p>
-<ol>
-<li>Open the context menu on a plug-in project and select <strong><a href="../../actions/ref-pdetools.htm">PDE Tools</a></strong></li>
-<li>On the resulting fly-out menu select <strong><a href="../actions/ref-apitooling-setup-action.htm">API Tooling Setup...</a></strong></li>
-</ol>
-<table border="1" cellspacing="0" cellpadding= "5" width="100%">
-  <thead>
-    <tr>
-      <th rowspan="1" colspan="1" width="20%"> <p> Option </p></th>
-      <th rowspan="1" colspan="1"> <p> Description </p></th>
-      <th rowspan="1" colspan="1" width="5%"> <p> Default </p></th>
-    </tr>
-  </thead>
-  <tbody>
-  	<tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">Choose a project</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">This text field allows you to filter the current list of projects by their name. Where '*' matches anything and '?' matches any character</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">Empty</td>
-    </tr>
-    <tr>
-      <td rowspan="1" colspan="1" valign="top" align="left">Projects</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">This list contains all of the projects in the current workspace that can be set up to use API Tooling. To be available to be converted a project must be a Java plug-in project.</td>
-      <td rowspan="1" colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Select All</td>
-      <td colspan="1" valign="top" align="left">Selects all of the projects in the list.</td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Deselect All</td>
-      <td colspan="1" valign="top" align="left">Deselect all of the projects in the list.</td>
-      <td colspan="1" valign="top" align="left">&nbsp;</td>
-    </tr>
-    <tr>
-      <td colspan="1" valign="top" align="left">Delete component.xml after update is complete</td>
-      <td colspan="1" valign="top" align="left"><p>This option will remove the component.xml file from your plug-in project when the setup is complete. A component.xml file was used prior to API Tooling to describe the API of your plug-in.</p>
-      <p>If a component.xml file is found it will be used by the setup wizard to add <a href="../api_javadoc_tags.htm"><strong>API restrictions</strong></a> (Javadoc tags) to the corresponding source files in your plug-in. All proposed changes can be viewed on the preview page for the wizard.</p></td>
-      <td colspan="1" valign="top" align="center">On</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-The first page of the wizard allows you to select projects and set additional options.
-</p>
-<p>
-<img src="../images/api-setup-wizard.png" alt="API Tooling setup wizard page 1">
-</p>
-<p>
-On the preview page you can see all of the changes that will be made to the project and any source files.
-</p>
-<p>
-<img src="../images/api-setup-wizard-preview.png" alt="API Tooling setup preview page">
-</p>
-<br>
-<p> <img border="0" src="../../../images/ngrelt.png" alt="Related tasks" > </p>
-<p> 
-<a href="../../../tasks/api_tooling_setup.htm">Setting up API Tooling</a>
-</p>
-<p><img src="../../../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../actions/ref-apitooling-setup-action.htm">API Tooling Setup Action</a><br>
-<a href="../../actions/ref-pdetools.htm">PDE Tools Menu</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html b/bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html
deleted file mode 100644
index eb51187..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/extension-points/index.html
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>PDE Extension Points</title>
-<link rel="stylesheet" type="text/css" HREF="../../book.css">
-</head>
-<body>
-<h1> PDE Extension Points </h1>
-<p>The following extension points can be used to extend the capabilities of the 
-  PDE infrastructure: </p>
-<ul>
-  <li><a href="org_eclipse_pde_build_fetchFactories.html">org.eclipse.pde.build.fetchFactories</a></li>
-  <li><a href="org_eclipse_pde_core_javadoc.html">org.eclipse.pde.core.javadoc</a></li>
-  <li><a href="org_eclipse_pde_core_source.html">org.eclipse.pde.core.source</a></li>
-  <li><a href="org_eclipse_pde_core_targets.html">org.eclipse.pde.core.targets</a></li>
-  <li><a href="org_eclipse_pde_ui_launchShortcuts.html">org.eclipse.pde.ui.launchShortcuts</a></li>
-  <li><a href="org_eclipse_pde_ui_newExtension.html">org.eclipse.pde.ui.newExtension</a></li>
-  <li><a href="org_eclipse_pde_ui_osgiFrameworks.html">org.eclipse.pde.ui.osgiFrameworks</a></li>
-  <li><a href="org_eclipse_pde_ui_pluginContent.html">org.eclipse.pde.ui.pluginContent</a></li>
-  <li><a href="org_eclipse_pde_ui_samples.html">org.eclipse.pde.ui.samples</a></li>
-  <li><a href="org_eclipse_pde_ui_targetProvisioners.html">org.eclipse.pde.ui.targetProvisioners</a></li>
-  <li><a href="org_eclipse_pde_ui_templates.html">org.eclipse.pde.ui.templates</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/images/pde-tools-flyout.PNG b/bundles/org.eclipse.pde.doc.user/reference/images/pde-tools-flyout.PNG
deleted file mode 100644
index 75c346b..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/images/pde-tools-flyout.PNG
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/reference/misc/index.html b/bundles/org.eclipse.pde.doc.user/reference/misc/index.html
deleted file mode 100644
index 62ae8f1..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/misc/index.html
+++ /dev/null

@@ -1,20 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="IBM">
-<link rel="STYLESHEET" href="../../book.css" type="text/css">
-<title>PDE - Other Reference Information</title>
-</head>
-<body>
-<h1> Other Reference Information</h1>
-<p>The following specifications, white papers, and design notes describe various 
-  aspects of the PDE. </p>
-<ul>
-  <li><a href="overview-pde.html">Map of PDE Plug-ins</a> 
-  </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html b/bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html
deleted file mode 100644
index ffc1c43..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/misc/overview-pde.html
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta name="Author" content="IBM">
-<title>PDE Overview</title>
-<link rel="STYLESHEET" href="../../book.css" type="text/css">
-</head>
-<body>
-<h1>Map of PDE Plug-ins</h1>
-<p>The PDE provides a comprehensive plug-in development 
-  environment. </p>
-<p>PDE itself is divided up into a number of separate 
-  plug-ins. The following table shows which API packages are found in which plug-ins 
-  (the most commonly referenced API packages are highlighted). This table is useful 
-  for determining which plug-ins a given plug-in should include as prerequisites. 
-</p>
-<table border="1" width="80%" align="center">
-  <tbody> 
-  <tr> 
-    <td><b>API Package</b></td>
-    <td><b>Plug-in id</b></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.pde.core[.*]</tt></td>
-    <td><tt>org.eclipse.pde.core</tt></td>
-  </tr>
-  <tr> 
-    <td><tt>org.eclipse.pde.ui[.*]</tt></td>
-    <td><tt>org.eclipse.pde.ui</tt></td>
-  </tr>
-  </tbody> 
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/pde_builder_config.htm b/bundles/org.eclipse.pde.doc.user/reference/pde_builder_config.htm
deleted file mode 100644
index ceef898..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/pde_builder_config.htm
+++ /dev/null

@@ -1,557 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" type="text/css">
-  <title>Builder Configuration</title>
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h3>Builder Configuration Properties<br>
-</h3>
-<p>The overall build mechanism is driven by a builder configuration
-which includes a build.properties file.<br>
-</p>
-<ul>
-  <li>Basic Settings<br>
-    <table style="width: 100%; text-align: left;" border="1"
- cellpadding="2" cellspacing="0">
-      <tbody>
-      	<tr>
-          <td style="vertical-align: top;">topLevelElementId</td>
-          <td style="vertical-align: top;">The id of the feature being built.<br>This property is new in 3.4 and depends on the use of the 3.4 allElements.xml file.  Build configurations using older style customTargets.xml and/or allElements.xml files should not use this property.</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">buildDirectory<br>
-          </td>
-          <td style="vertical-align: top;">The directory where the
-build will take place.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">configs<br>
-          </td>
-          <td style="vertical-align: top;">A list of configurations to
-build.&nbsp; A configuration is an ampersand separated list of comma
-separated operating system, windowing system and architecture.&nbsp; If
-no config is specified, the platform independent config will be
-built.&nbsp; Example:
-          <div style="text-align: center;">
-          <pre style="margin-left: 40px;">configs = win32, win32, x86 &amp; linux, gtk, ppc</pre>
-          </div>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-  </li>
-</ul>
-<ul>
-<li>p2 Integration<br>
-See the p2 Integration documentation for properties controlling <a href="../tasks/pde_p2_featurebuilds.htm">feature builds</a>, and <a href="../tasks/pde_p2_featurebuilds.htm">product builds</a>.</li>
-</ul>
-<ul>
-  <li>Base Control:&nbsp; The base is a target eclipse install
-containing plug-ins and features that you require but are not building
-yourself.<br>
-    <table style="width: 100%; text-align: left;" border="1"
- cellpadding="2" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;">baseLocation<br>
-          </td>
-          <td style="vertical-align: top;">The location of the target
-eclipse install. In the default template, the value of this is
-${base}/eclipse.&nbsp; (See the base property below).&nbsp; This
-directory is expected to contain <tt>plugins/</tt> and <tt>features/</tt>
-subdirectories
-which contain the binary plug-ins and features respectively.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">baseos<br>
-          </td>
-          <td style="vertical-align: top;">The operating system of the
-eclipse specified by baseLocation<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">basews<br>
-          </td>
-          <td style="vertical-align: top;">The windowing system of the
-eclipse specified by baseLocation<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">basearch<br>
-          </td>
-          <td style="vertical-align: top;">The architecture of the
-eclipse specified by baseLocation<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">pluginPath<br>
-          </td>
-          <td style="vertical-align: top;">A platform path-separator
-separated list of locations to find additional plug-ins and features.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">skipBase<br>
-          </td>
-          <td style="vertical-align: top;">If set, automatically
-download a base eclipse to use as a target<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">base<br>
-          </td>
-          <td style="vertical-align: top;">The location the base
-eclipse will be downloaded to.&nbsp; This should be the parent of
-baseLocation, such that <tt>baseLocation = ${base}/eclipse</tt>.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">eclipseURL<br>
-          </td>
-          <td style="vertical-align: top;">The URL for the eclipse
-download site<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">eclipseBuildId<br>
-          </td>
-          <td style="vertical-align: top;">The build ID of the eclipse
-to download<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">eclipseBaseURL<br>
-          </td>
-          <td style="vertical-align: top;">The actual URL of the zip to
-download.&nbsp; In the default template, the value is:
-          <div style="text-align: center;">
-          <pre>eclipseBaseURL = ${eclipseURL}/eclipse-platform-${eclipseBuildId}-win32.zip</pre>
-          </div>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">filteredDependencyCheck<br>
-          </td>
-          <td style="vertical-align: top;">Constraint the set of plug-ins and features
-          to be considered during the build to the one reachable from the features / plugins being built when set to true<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">resolver.devMode<br>
-          </td>
-          <td style="vertical-align: top;">When set to true, the validation done on the set of plug-ins being built will be
-          less strict. For example it will allow multiple versions of a singleton bundle to be resolved.<br>
-          </td>
-        </tr>
-        
-      </tbody>
-    </table>
-  </li>
-</ul>
-<ul>
-  <li>Output
-Control:&nbsp; The following properties affect the shape
-of the build results.<br>
-    <table style="width: 100%; text-align: left;" border="1"
- cellpadding="2" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;">runPackager<br>
-          </td>
-          <td style="vertical-align: top;">Set if the packager needs to
-be run.&nbsp; Set this if your build results need to contain binary
-features and plug-ins that come from the baseLocation.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">product<br>
-          </td>
-          <td style="vertical-align: top;">The product configuration
-file.&nbsp; Set this if you are building a product.&nbsp; It controls
-branding of your build results.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">archiveNamePrefix<br>
-          </td>
-          <td style="vertical-align: top;">The prefix of the name of
-the final archive files.&nbsp; This is used in allElements.xml when
-setting the archive name on a per config basis.&nbsp; By default, the
-value will be ${buildId}<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">archivePrefix<br>
-          </td>
-          <td style="vertical-align: top;">The name of the archive root
-folder, this is "eclipse" for eclipse builds.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">buildType </td>
-          <td style="vertical-align: top;">Type of build, normally
-something like I, N, M, etc. </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">buildLabel </td>
-          <td style="vertical-align: top;">The label for the build. In
-the default template, the value is <tt>${buildType}.${buildId}</tt> </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">collectingFolder<br>
-          </td>
-          <td style="vertical-align: top;">The folder where the build
-output will be collected.&nbsp;&nbsp; In the default template, the
-value is <tt>${archivePrefix}</tt>.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">groupConfigurations<br>
-          </td>
-          <td style="vertical-align: top;">Whether or not to group all
-configuration into one archive file.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">archivesFormat<br>
-          </td>
-          <td style="vertical-align: top;">The archive format for the
-different configs being built.&nbsp; This is an ampersand separated
-list of configs and their archive format.&nbsp; The format is separated
-by a dash (-).&nbsp; Example:<br>
-          <div style="text-align: center;">
-          <pre>archivesFormat =&nbsp; win32, win32, x86 - antzip &amp; linux, gtk, ppc - tar</pre>
-          </div>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">outputUpdateJars<br>
-          </td>
-          <td style="vertical-align: top;">When set, generates plug-ins
-and features in JAR format for an update site.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">zipArgs<br>
-          </td>
-          <td style="vertical-align: top;">Arguments to be sent to the
-zip executable when the archive format is zip.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">tarArgs<br>
-          </td>
-          <td style="vertical-align: top;">Arguments to be sent to the
-tar executable when the archive format is tar.<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-  </li>
-</ul>
-<ul>
-  <li>Signing and Jnlp control:<br>
-    <table style="width: 100%; text-align: left;" border="1"
- cellpadding="2" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;">generateJnlp<br>
-          </td>
-          <td style="vertical-align: top;">Set to true to generate JNLP
-manifests for the JAR archives<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">jnlp.codebase<br>
-          </td>
-          <td style="vertical-align: top;">The site URL.&nbsp; This
-should be a URL that will be used as the root of all relative URLs in
-the output.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">jnlp.j2se<br>
-          </td>
-          <td style="vertical-align: top;">The J2SE version required to run the JNLP app being exported<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">jnlp.locale<br>
-          </td>
-          <td style="vertical-align: top;">The locale in which the generated jnlp files should be generated.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">jnlp.generateOfflineAllowed<br>
-          </td>
-          <td style="vertical-align: top;">Generate the  &lt;offlineAllowed/&gt; in the generated files when set to true.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">jnlp.configs<br>
-          </td>
-          <td style="vertical-align: top;">Filter the content of the generated jnlp files based on the configuration being built. The configurations need to be listed.<br>
-          </td>
-        </tr>                
-        <tr>        
-          <td style="vertical-align: top;">signJars<br>
-          </td>
-          <td style="vertical-align: top;">Set to true to sign
-jars&nbsp; for features and plug-ins.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">sign.alias<br>
-          </td>
-          <td style="vertical-align: top;">The alias passed to the ant
-signJar task.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">sign.keystore<br>
-          </td>
-          <td style="vertical-align: top;">The keystore passed to the
-ant signJar task.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">sign.storepass<br>
-          </td>
-          <td style="vertical-align: top;">The storepass passed to the
-ant signJar task.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">sign.keypass<br>
-          </td>
-          <td style="vertical-align: top;">The keypass passed to the
-ant signJar task.<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-  </li>
-</ul>
-<ul>
-  <li>Version Control.&nbsp; (See also <a
- href="../tasks/pde_version_qualifiers.htm">Version Qualifiers</a>)<br>
-    <table style="width: 100%; text-align: left;" border="1"
- cellpadding="2" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;">forceContextQualifier<br>
-          </td>
-          <td style="vertical-align: top;">The value of this property
-is used when replacing qualifiers in plug-in and feature
-versions.&nbsp; If set it is used instead of the tags from the map
-files
-or the timestamp.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">generateFeatureVersionSuffix<br>
-          </td>
-          <td style="vertical-align: top;">Set to true to generate
-feature version suffixes<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">generateVersionsLists<br>
-          </td>
-          <td style="vertical-align: top;">Set to true to generate
-properties files listing the final version numbers of features and
-plug-ins being built.&nbsp; This will create
-finalFeaturesVersions.properties
-and finalPluginsVersions.properties files in the builder directory.<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-  </li>
-  <li><a name="fetchControl">Fetch phase Control</a> (See also <a href="../tasks/pde_fetch_phase.htm">Fetching
-from Repositories</a>)<br>
-    <table style="width: 100%; text-align: left;" border="1"
- cellpadding="2" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;">skipMaps<br>
-          </td>
-          <td style="vertical-align: top;">If set, do not attempt to
-fetch map files from CVS<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">mapsRepo<br>
-          </td>
-          <td style="vertical-align: top;">The CVS repository to fetch
-map files from.&nbsp; Example:<br>
-          <div style="text-align: center;">
-          <pre>:pserver:anonymous@example.com/path/to/repo</pre>
-          </div>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">mapsRoot<br>
-          </td>
-          <td style="vertical-align: top;">The path in the CVS
-repository to the directory containing the map files<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">mapsCheckoutTag<br>
-          </td>
-          <td style="vertical-align: top;">The CVS tag to use to
-checkout the map files<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">tagMaps<br>
-          </td>
-          <td style="vertical-align: top;">Set to true to tag the map
-files after fetching them.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">mapsTagTag<br>
-          </td>
-          <td style="vertical-align: top;">The tag with which to tag
-the map files after fetching them.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">skipFetch<br>
-          </td>
-          <td style="vertical-align: top;">Set to true to skip the
-entire fetch phase.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">fetchTag<br>
-          </td>
-          <td style="vertical-align: top;">The tag to use when fetching
-features and plug-ins from CVS.&nbsp; This property overrides the
-values in the map files.<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-  </li>
-</ul>
-<ul>
-  <li>Compilation Control (See also <a href="../tasks/pde_compilation_env.htm">Controlling
-Compilation Environment</a>)<br>
-    <table style="width: 100%; text-align: left;" border="1"
- cellpadding="2" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;">logExtension<br>
-          </td>
-          <td style="vertical-align: top;">The extension of the
-generated log file.&nbsp; This only applies when using the default JDT
-compiler.&nbsp; Default value is ".log".<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">javacDebugInfo<br>
-          </td>
-          <td style="vertical-align: top;">Whether or not to include
-debug info in the output jars.&nbsp; This is passed to the ant javac
-task. If not set, default value is on.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">javacFailOnError<br>
-          </td>
-          <td style="vertical-align: top;">Whether or not to fail the
-build if there are compilation errors.&nbsp; This is passed to the ant
-javac task.&nbsp; If not set, default value is true.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">javacVerbose<br>
-          </td>
-          <td style="vertical-align: top;">Whether or not to enable the
-verbose mode of the compiler.&nbsp; This is passed to the ant javac
-task.&nbsp; If not set, default value is false.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">compilerArg<br>
-          </td>
-          <td style="vertical-align: top;">Set specific arguments to
-pass directly to the compiler.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">javacSource<br>
-          </td>
-          <td style="vertical-align: top;">The java source
-compatibility level to use if a plug-in does not specify any
-settings.&nbsp; If not set, 1.3 is the default value.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">javacTarget<br>
-          </td>
-          <td style="vertical-align: top;">The target .class
-compatibility level to use if a plug-in does not specify any
-settings.&nbsp; If not set, 1.2 is the default value.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">flattenDependencies<br>
-          </td>
-          <td style="vertical-align: top;">Sort bundle dependencies across feature boundaries.  (See also <a href="../tasks/pde_compilation_order.htm">Compilation Order and Parallelization</a>)<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">parallelCompilation<br>
-          </td>
-          <td style="vertical-align: top;">Set to true to enable parallel compilation.  (Requires flattenDependencies=true)</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">parallelThreadCount<br>
-          </td>
-          <td style="vertical-align: top;">The maximum number of threads to use.  Corresponds to <i>threadCount</i> on the ant parallel task.</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">parallelThreadsPerProcessor<br>
-          </td>
-          <td style="vertical-align: top;">The maximum number of threads to use per available processor.  Corresponds to <i>threadsPerProcessor</i> on the ant parallel task.</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">bootclasspath<br>
-          </td>
-          <td style="vertical-align: top;">The bootclasspath to use if
-the plug-in does not specify any settings itself.&nbsp; This is a
-platform path separator separated list of jars.&nbsp; If not set, the
-file set matching ${java.home}/jre/lib/*.jar will be used.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;">&lt;Execution Environment&gt;<br>
-          </td>
-          <td style="vertical-align: top;">Set properties for each JRE
-that can be used to build.&nbsp; These properties will match up against
-Execution Environments specified by individual bundles.&nbsp; The
-values should specify the jars to compile against when using that
-environment.&nbsp; See&nbsp; <a href="../tasks/pde_compilation_env.htm">Controlling
-Compilation Environment</a>.</td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-  </li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/reference/pde_feature_generating_build.htm b/bundles/org.eclipse.pde.doc.user/reference/pde_feature_generating_build.htm
deleted file mode 100644
index 4a1ee74..0000000
--- a/bundles/org.eclipse.pde.doc.user/reference/pde_feature_generating_build.htm
+++ /dev/null

@@ -1,208 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" type="text/css">
-  <title>Feature build configuration</title>
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h3>Feature and Plug-in Build Configuration Properties<br>
-</h3>
-<p>The build mechanism is driven by a build configuration.&nbsp; The
-build configuration for an individual plug-in, fragment, or feature is
-found
-in a <b> build.properties</b> file for the corresponding element.</p>
-<p>PDE project creation wizards generate the <b> build.properties</b>
-file when
-plug-in projects are created. The file contains information on how to
-compile source folders into
-JARs. This information can be indirectly updated in the Runtime page of
-the
-manifest editor. It can also be directly modified using the appropriate
-editor.</p>
-<p>PDE provides a simple editor for the <b> build.properties</b> that
-has form and source views.
-The file itself follows the Java properties format. You need to provide
-a number of
-keys and their corresponding values. Multiple values are separated
-using a comma
-as the delimiter. </p>
-<h4>Common properties</h4>
-<ul>
-  <li><b>bin.includes</b> - lists files that will included in the
-binary version of the plug-in being built;</li>
-  <li><b>bin.excludes</b> - lists files to exclude from the binary
-build;</li>
-</ul>
-<ul>
-  <li><b>qualifier</b> - when the element version number ends with <b>.qualifier</b>
-this indicates by which value ".qualifier" must be replaced. The value
-of the property can either be <b>context</b>, <b>&lt;value&gt;</b> or
-    <b>none</b>. Context will generate a date according to the system
-date, or use the CVS tags when the built is automated. Value is an
-actual value. None will remove ".qualifier". If the property is
-omitted, context is used. (See <a href="../tasks/pde_version_qualifiers.htm">Version Qualifiers</a>.)</li>
-</ul>
-<ul>
-  <li><b>custom=true</b> - indicates that the build script is
-hand-crafted as opposed to automatically generated. Therefore no other
-value is consulted.</li> 	
-</ul>
-<ul>
-  <li><span style="font-weight: bold;">customBuildCallbacks</span> -
-indicates an xml file containing custom targets to use when using this
-feature/plug-in.&nbsp; (See <a href="../tasks/pde_custom_callbacks.htm">Feature
-and Plug-in Custom Build Steps</a>)<br>
-  </li>
-      <li><span style="font-weight: bold;">customBuildCallbacks.failonerror</span> - 
-      sets the subant task's failonerror parameter.  The default is "false".<br>
-  </li>
-    <li><span style="font-weight: bold;">customBuildCallbacks.buildpath</span> -
-     sets the subant task's buildpath parameter.  Use when the location of the custom callbacks file is not
-     relative to the root of the plug-in.<br>
-  </li>
-    <li><span style="font-weight: bold;">customBuildCallbacks.inheritall</span> - sets the subant task's inheritall parameter.  Ant's default is false.<br>
-  </li>
-</ul>
-<h4>Plug-in specific properties</h4>
-<ul>
-  <li><b>source.&lt;library&gt;</b> - lists source folders that will be
-compiled (e.g. <b>source.xyz.jar=src/, src-ant/</b>). If the library
-is specified in your plug-in.xml or manifest.mf, the value should match
-it;</li>
-  <li><b>output.&lt;library&gt;</b> - lists the output folder receiving
-the result of the compilation;</li>
-  <li><b>exclude.&lt;library&gt;</b> - lists the files that should not
-be copied into the library by the compiler;</li>
-  <li> <b>extra.&lt;library&gt;</b> - extra classpaths used to perform
-automated build. Classpath can either be relative paths, or platform
-urls referring to plug-ins and fragments of your development
-environment (e.g. <b>../someplugin/xyz.jar</b>, <b>platform:/plugins/org.apache.ant/ant.jar</b>).
-Platform urls are recommended over relative paths;</li>
-  <li><b>manifest.&lt;library&gt;</b> - indicate the file that will be
-used as a manifest for the library. The file must be located in one of
-the source folder being used as input of the jar.</li>
-</ul>
-<ul>
-  <li><b>src.includes</b> - lists files to include in the source build;</li>
-  <li> <b>src.excludes</b> - lists files to exclude from the source
-build;</li>
-</ul>
-<ul>
-  <li> <b>jars.extra.classpath</b> - <b>(deprecated)</b> same effect
-than extra.&lt;library&gt; except that the entries are applied to all
-libraries;</li>
-  <li> <b>jars.compile.order</b> - defines the order in which jars
-should be compiled (in case there are multiple libraries).</li>
-</ul>
-<ul>
-  <li><span style="font-weight: bold;">jre.compilation.profile</span> -
-set the Environment used to compile this bundle.&nbsp; (See <a
- href="../tasks/pde_compilation_env.htm">Controlling the Compilation Environment</a>)<br>
-  </li>
-  <li><span style="font-weight: bold;">javacSource</span> - set the
-source compatibility level for compiling this bundle.&nbsp; Overrides
-jre.compilation.profile.<br>
-  </li>
-  <li><span style="font-weight: bold;">javacTarget</span> - set the
-target .class compatibility level for compiling this bundle.&nbsp;
-Overrides jre.compilation.profile.</li>
-  <li><span style="font-weight: bold;">bootClasspath</span> - set the
-boot classpath to compile this bundle against, Overrides
-jre.compilation.profile.<br>
-  </li>
-</ul>
-<ul>
-  <li><span style="font-weight: bold;">javacWarnings.&lt;library&gt;</span>
-- set the warning options to pass to the compiler.&nbsp; (See the -warn
-option in <a
- href="../../org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm">Compiling
-Java Code</a> from the JDT Plug-in Developer Guide).<br>
-    <span style="font-weight: bold;"></span></li>
-  <li><span style="font-weight: bold;">javacDefaultEncoding.&lt;library&gt;</span>
-- sets default encoding to use when compiling the given library.</li>
-  <li><span style="font-weight: bold;">javacCustomEncodings.&lt;library&gt;</span>
-- a comma separated list of
-paths and encodings to use when compiling the given library.&nbsp;
-Example: <br>
-    <div style="text-align: center;">
-    <pre>javacCustomEncodings.library.jar = src/org/foo[US-ASCII], src/org/foo/bar.java[ISO-8859-1]</pre>
-    </div>
-  </li>
-</ul>
-<p> The values
-defined for these keys ending with "includes" or "excludes" are
-expressed as Ant "patterns". Standard formats give the expected
-results.&nbsp; For example, "*<b>.jar</b>" indicates all jar files in
-the top level directory. The patterns are not deep by default.&nbsp; If
-you want to
-describe all Java files for example, you should use the pattern "<b>**/*.java</b>".&nbsp;&nbsp;
-The pattern "<b>**</b>" matches any number of directory levels.&nbsp;
-Similarly, to describe whole sub-trees, use "<b>xyz/</b>". </p>
-<h4><a name="Feature_specific_properties"></a>Feature specific
-properties</h4>
-<ul>
-	<li><b>root</b> - List the files and folders that must be included in
-the root of the product. See the <a href="../tasks/pde_rootfiles.htm">Rootfiles help page</a> for more detail, incuding the following additional properties:
-    <ul>
-      <li>root.&lt;config&gt;: per configuration rootfiles.</li>
-      <li>root.folder : rootfiles placed in subfolders.</li>
-      <li>root.permissions : perform chmods on rootfiles.</li>
-      <li>root.link : generate softlinks for rootfiles.</li>
-    </ul>
-  </li>
-  <li><b>root.&lt;config&gt;</b> - list the files and folders that must
-be included in the root of the product when it is built for the
-specified configuration. config is composed of the three (3) segments
-of a configuration separated with a dot;</li>
-</ul>
-<ul>
-  <li><b>root.permissions.&lt;permissionValue&gt;</b> - list the files
-and folders to chmod to the given value. Reference to folders must ends
-with a '/';</li>
-  <li><b>root.permissions.&lt;config&gt;.&lt;permissionValue&gt;</b> -
-list the files and folders to chmod to the given value for a specific
-configuration. Reference to folders must ends with '/';</li>
-</ul>
-<ul>
-  <li><b>root.link</b> - list by pairs (separated by a comma) the files
-and folders that need to be symbolicly linked. The first entry indicate
-the source (target in the unix terminology) and the second entry the
-link name;</li>
-  <li><b>root.link.&lt;config&gt;</b> - a comma separated list of pairs
-of files and folders that need to be symbolicly linked for a specific
-configuration. The first entry indicate the source (target in the unix
-terminology) and the second entry the link name;</li>
-</ul>
-<ul>
-  <li><b>generate.feature@&lt;featureId&gt;</b> - indicates that the
-source feature <b>featureId</b> will be the source feature for the
-feature indicated as value of this property. The values listed after
-the first comma indicates elements to be fetched from the
-repository;&nbsp; (See <a href="../tasks/pde_source_generation.htm">Source
-Plugin and Feature Generation</a>)<br>
-  </li>
-  <li><b>generate.plugin@&lt;pluginId&gt;</b> - indicates that the
-source plug-in <b>pluginId</b> will be the source plug-in for the
-indicated as value of this property.</li>
-</ul>
-<ul>
-  <li><span style="font-weight: bold;">significantVersionDigits</span>
-- The number of significant digits used when generating feature version
-suffixes&nbsp; (See <a href="../tasks/pde_version_qualifiers.htm">Version
-Qualifiers</a>)<br>
-  </li>
-  <li><span style="font-weight: bold;">generatedVersionLength</span> -
-The length of the generated feature version suffix.<br>
-  </li>
-</ul>
-The following example has been extracted from the build.properties of
-the org.eclipse.platform feature.
-<pre style="margin-left: 40px;">bin.includes=epl-v10.html,eclipse_update_120.jpg,feature.xml,feature.properties,license.html<br><br>root=rootfiles,configuration/<br>root.permissions.755=eclipse<br><br>root.linux.motif.x86=../../plugins/platform-launcher/bin/linux/motif,linux.motif<br>root.linux.motif.x86.link=libXm.so.2.1,libXm.so.2,libXm.so.2.1,libXm.so<br>root.linux.motif.x86.permissions.755=*.so*<br></pre>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/schema.css b/bundles/org.eclipse.pde.doc.user/schema.css
deleted file mode 100644
index a03ed6a..0000000
--- a/bundles/org.eclipse.pde.doc.user/schema.css
+++ /dev/null

@@ -1,71 +0,0 @@
-/*******************************************************************************
- * Copyright (c) 2004, 2009 IBM Corporation and others.
- * All rights reserved. This program and the accompanying materials 
- * are made available under the terms of the Eclipse Public License v1.0
- * which accompanies this distribution, and is available at
- * http://www.eclipse.org/legal/epl-v10.html
- * 
- * Contributors:
- *     IBM Corporation - initial API and implementation
- *******************************************************************************/
-
-H6.SchemaHeader {
-	font-size:16px; 
-	display:inline
-}
-
-P.SchemaCopyright {
-	font-size: smaller; 
-	font-style: normal;
-	color: #336699; 
-	display:inline;
-	margin-top: 3.000000pt;
-	margin-bottom: 11.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 0.000000pt;
-}
-
-P.SchemaDtd {
-	color: #800000; 
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 10.000000pt;
-}
-
-P.SchemaDtdAttlist {
-	color: #800000; 
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 20.000000pt;
-}
-
-span.SchemaTag {
-	color: #000080;
-}
-
-span.SchemaCstring {
-	color: #008000;
-}
-
-pre.Example {
-	margin-top: 0.000000pt;
-}
-
-.ConfigMarkupElementDesc {
-	color: black;
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 10.000000pt;
-}
-
-.ConfigMarkupAttlistDesc {
-	color: black;
-	margin-top: 0.000000pt;
-	margin-bottom: 0.000000pt;
-	margin-right: 0.000000pt;
-	margin-left: 32.000000pt;
-}
-

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_baseline.htm b/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_baseline.htm
deleted file mode 100644
index f887d8a..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_baseline.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Setting up an API  baseline</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Setting up an API baseline</h1>
-<p>Once your plug-in is converted to use API tooling, you need to set up a baseline in order to get the
-compatibility analysis performed for your plug-in.</p>
-<p>To create an API baseline do the following:</p>
-<ol>
-<li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apiprofiles.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the API Baselines preference page"> <b>Plug-in Development &gt; API Baselines</b></a> preference page.</li>
-<li>Select the <strong>Add Baseline...</strong> button to open the <a href="../reference/api-tooling/wizards/ref-api-baseline-wizard.htm"><strong>API baseline wizard</strong></a>.
-  <ul>
-    <li>Give a meaningful name for your baseline</li>
-    <li>Click <b>Browse...</b> and select the root folder of the Eclipse SDK you want to choose as your baseline</li>
-    <li>Click <b>OK</b> in the folder dialog</li>
-    <li>Once the baseline is initialized, click <b>Finish</b></li>
-    </ul>
-</li>
-<li>Click <b>OK</b> and you are all set. If your workspace contains some existing projects, you will be prompted for
-    a rebuild.</li>
-</ol>
-
-<br>
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../reference/api-tooling/preferences/ref-baselines.htm">API Baselines Preferences</a><br>
-<a href="../reference/api-tooling/wizards/ref-api-baseline-wizard.htm">API Baseline Wizard</a><br>
-<a href="../reference/api-tooling/quickfixes/ref-api-missing-baseline-qf.htm">Missing API Baseline Quickfix</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_compare_to_baseline.htm b/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_compare_to_baseline.htm
deleted file mode 100644
index 60467e0..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_compare_to_baseline.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Comparing to an API  baseline</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Comparing to an API baseline</h1>
-<p>Any API tooling enabled project in your workspace can be compared to any one of the API baselines set up in your workspace. In addition to
-selecting projects to compare to a baseline you can also select (or multi-select) any of the following within an API tools enabled project:
-</p> 
-<ul>
-<li>source folders</li>
-<li>package fragments</li>
-<li>compilation units</li>
-</ul>
-<p>NOTE: all selections must be made from 
-the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/ref-view-package-explorer.htm">Package Explorer</a></b> because the compare wizard
-works only for Java elements.</p>
-<br>
-<p>To compare to an API baseline do the following:</p>
-<ol>
-<li>Select the elements to compare using the criteria mentioned above.</li>
-<li>Select the API baseline to compare to in the <b><a href="../reference/api-tooling/wizards/ref-api-compare-wizard.htm">Compare Wizard</a></b></li>
-<li>Click <b>Finish</b> and you are all set. Any results from the compare will be shown in the <b><a href="../reference/api-tooling/views/ref-api-tooling-view.htm">API Tooling</a></b> view.</li>
-</ol>
-<br>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"></p>
-<a href="api_tooling_baseline.htm">Setting up a baseline</a>
-
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../reference/api-tooling/preferences/ref-baselines.htm">API Baselines Preferences</a><br>
-<a href="../reference/api-tooling/wizards/ref-api-baseline-wizard.htm">API Baseline Wizard</a><br>
-<a href="../reference/api-tooling/quickfixes/ref-api-missing-baseline-qf.htm">Missing API Baseline Quickfix</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_create_filters.htm b/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_create_filters.htm
deleted file mode 100644
index 7d90934..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_create_filters.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Creating API Problem Filters</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Creating API Problem Filters</h1>
-<p>Filters can be used to remove <em>known</em> or <em>expected</em> API problems that cannot be readily corrected. Problem filters can be created easily using the <strong><a href="../reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm">Create API Problem Filter</a></strong> quickfix. </p>
-<p>Using the quickfix let's see how we can add a new filter.</p>
-<h3>The Problems view</h3>
-<ul>
-<li>Open the <b>Problem</b> view.</li>
-<li>Select an API Tooling problem.</li>
-<li>Use <b>Ctrl + 1</b> to trigger the quickfix from the problem view.</li>
-<li>Select Finish to create the new filter.</li>
-</ul>
-<h3>Editing the resource</h3>
-<ul>
- <li>Open the resource the API problem exists in.</li>
- <li>Use <b>Ctrl + 1</b> on the corresponding problem.</li>
- <li>One of the quickfix proposals will be the creation of a problem filter for the corresponding problem.</li>
- <li>Select it and the problem filter is added for you.</li>
-</ul>
-<p>Once the problem filter has been created the corresponding resource is rebuilt and the problem is removed from the Problems view and any open editors.</p>
-<p><img src="../images/ngrelt.png" alt="Related tasks"></p>
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../reference/api-tooling/propertypages/ref-filters-prop.htm">API Problem Filters Property Page</a><br>
-<a href="../reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm">Add API Problem Filter Quickfix</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_options.htm b/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_options.htm
deleted file mode 100644
index 8624ca5..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_options.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Changing API Tooling options</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Changing API Tooling options</h1>
-<p>The options can be changed per project or per workspace.</p>
-<ol>
-<li>First you need to open the preference page. Do one of the following according to the desired scope:
-<ul>
-<li>for the project scope, right-click a project and select <b>Properties</b>. Then
-	go to <b><a href="../reference/api-tooling/propertypages/ref-errorswarnings-prop.htm">Plug-in
-	Development &gt; API Errors/Warnings</a></b></li>
-<li>for the workspace scope, go to the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.api.tools.ui.apitools.errorwarnings.prefpage)")'> <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the Console preference page"> <b>Plug-in Development &gt; API Errors/Warnings</b></a> preference page.</li>
-</ul>
-</li>
-<li>Select the tab for which you want to modify an option:
-<ul>
-<li><a href="../reference/api-tooling/preferences/ref-errorswarnings.htm#usage"><strong>API Use</strong></a>: for options related to API usage (unsupported tags, API restrictions, API leaks)</li>
-<li><a href="../reference/api-tooling/preferences/ref-errorswarnings.htm#compat"><strong>API Compatibility</strong></a>: for options related to compatibility issues. They are sorted per type of element</li>
-<li><a href="../reference/api-tooling/preferences/ref-errorswarnings.htm#version"><strong>Version Management</strong></a>: for options related to invalid, missing, malformed @since tags or incorrect plug-in versions)</li>
-<li><a href="../reference/api-tooling/preferences/ref-errorswarnings.htm#analysis"><strong>Analysis Options</strong></a> - for general options</li>
-</ul>
-</li>
-<li>All options of a page can be reset to the default values by clicking on <b>Restore Defaults</b>.</li>
-<li>Use the buttons insider the <b>Set All As</b> group to modify all options of the page to a specific value.</li>
-</ol>
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../reference/api-tooling/preferences/ref-errorswarnings.htm">API Errors and Warnings Preferences</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_remove_filters.htm b/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_remove_filters.htm
deleted file mode 100644
index bdb7879..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_remove_filters.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Removing filters</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Removing filters</h1>
-<p>If you want to remove an existing API filter, do the following steps:</p>
-<ul>
-<li>Select the project that has an existing API filter.</li>
-<li>Right-click on the project and select <b>Properties</b>.</li>
-<li>Go to <b><a href="../reference/api-tooling/propertypages/ref-filters-prop.htm">Plug-in Development &gt; API Problem Filters</a></b>
-<p>
-<img src="../guide/images/tasks/api_filter_properties.png" alt="API Filter Properties">
-</p></li>
-<li>From the list of existing filters, select the one you want to remove</li>
-<li>Select <b>Remove</b>.</li>
-<li>Select <b>OK</b> or <b>Apply</b>.</li>
-</ul>
-<p><img src="../images/ngrelt.png" alt="Related tasks"></p>
-<p>
-<a href="api_tooling_create_filters.htm">Creating filters</a><br>
-</p>
-<p><img src="../images/ngrelr.png" alt="Related reference"></p>
-<p>
-<a href="../reference/api-tooling/propertypages/ref-filters-prop.htm">API Problem Filters Property Page</a><br>
-<a href="../reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm">Add API Problem Filter Quickfix</a><br>
-<a href="../reference/api-tooling/quickfixes/ref-api-remove-api-filter-qf.htm">Remove Unused API Problem Filter Quickfix</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_setup.htm b/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_setup.htm
deleted file mode 100644
index 287304e..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/api_tooling_setup.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Setting up API Tooling</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Setting up API Tooling</h1>
-<h2>Configure existing plug-ins</h2>
-<p>This section explains how to enable your existing plug-ins for API analysis.</p>
-<ol>
-<li>Select the project you want to convert.</li>
-<li>Right-click and select <b><a href="../reference/actions/ref-pdetools.htm">PDE Tools</a> &gt; <a href="../reference/api-tooling/actions/ref-apitooling-setup-action.htm">API Tooling Setup...</a></b></li>
-<li>Once the <a href="../reference/api-tooling/wizards/ref-api-setup-wizard.htm"><strong>API Tooling Setup</strong></a> wizard is open, check that the project is selected.</li>
-<li>If your project contains a file <code>component.xml</code>, you can uncheck the checkbox to preserve it after conversion.</li>
-<li>Click <b>Next</b> if you want to preview the changes, or <b>Finish</b> otherwise.</li>
-<li>Your plug-in is now converted to use API tooling.</li>
-</ol>
-
-<h2>Configure a new plug-in</h2>
-
-<p>This section explains how to enable a new plug-ins for API analysis.</p>
-<ol>
-<li>Click on <b>File&gt;New&gt;Project...</b></li>
-<li>Select <b>Plug-in Development&gt;Plug-in Project</b> and click <b>Next</b>.</li>
-<li>Fill the first page as you would do for any other plug-in and click <b>Next</b>.</li>
-<li>Check the option <code>Enable API Analysis</code>.
-<p>
-<img src="../guide/images/tasks/plugin_creation_wizard.png" alt="Plug-in Creation Wizard" border="0"></p>
-</li><li>Complete your Plug-in setup</li>
-<li>Click <b>Finish</b>.</li>
-</ol>
-<p><img src="../images/ngrelt.png" alt="Related tasks" border="0"></p>
-	<p>
-   	 	<a href="api_tooling_baseline.htm">Setting up a baseline</a><br>
-	</p>
-	<p><img src="../images/ngrelr.png"  alt="Related reference" border="0"></p>
-	<p>
-		<a href="../reference/api-tooling/wizards/ref-api-setup-wizard.htm">API Tooling Setup Wizard</a><br>
-		<a href="../reference/actions/ref-pdetools.htm">PDE Tools Menu</a><br>
-		<a href="../reference/api-tooling/actions/ref-apitooling-setup-action.htm">API Tooling Setup Command</a><br>
-		<a href="../reference/api-tooling/api_javadoc_tags.htm">Defining API Restrictions</a>
-	</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_env.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_env.htm
deleted file mode 100644
index b7996fc..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_env.htm
+++ /dev/null

@@ -1,235 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Setting the compilation environment</title>
-</head>
-<body>
-<h1>Setting the Compilation Environment</h1>
-<p>By default, your bundles will be compiled with whichever JRE is
-being used to run the build and with source and target levels set to
-1.3 and 1.2.<br>
-</p>
-<p>PDE build is capable of configuring the JRE used during compilation
-on a per bundle basis.&nbsp; To take advantage of this, the first thing
-to do is to tell PDE build which JREs you have available.&nbsp; In your
-build configuration build.properties file, set properties to point to
-each of your installed JREs.&nbsp; The template build.properties
-provided in org.eclipse.pde.build/templates/headless-build has a list
-of environments commented out.&nbsp; Simply uncomment the properties
-for which you have JREs and set the value to be the set of jars that
-belong on the boot classpath.&nbsp; For example, setting the property:<br>
-</p>
-<div style="text-align: center;"><tt>J2SE-1.5=C:/Java/1.5/jre/lib/rt.jar;C:/Java/1.5/jre/lib/jsse.jar</tt><br>
-</div>
-<p style="text-align: left;">will compile bundles requiring java 1.5
-against rt.jar and jsse.jar.&nbsp; The names of the properties should
-match the names of the environments that PDE Build knows
-about.&nbsp;&nbsp;
-PDE Build will automatically set the source and target levels for each
-environment.&nbsp; The environments that PDE builds knows and their
-associated source/target levels are as follows:<br>
-</p>
-<table
- style="width: 60%; height: 54px; text-align: left; margin-left: auto; margin-right: auto;"
- border="1" cellpadding="1" cellspacing="1">
-  <tbody>
-    <tr>
-      <td style="vertical-align: top; text-align: center;">Environment<br>
-      </td>
-      <td style="vertical-align: top;">Source<br>
-      </td>
-      <td style="vertical-align: top;">Target<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">CDC-1.0/Foundation-1.0<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">CDC-1.1/Foundation-1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.2<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">OSGi/Minimum-1.0<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">OSGi/Minimum-1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.2<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">JRE-1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">J2SE-1.2<br>
-      </td>
-      <td style="vertical-align: top;">1.2<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">J2SE-1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">J2SE-1.4<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.2<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">J2SE-1.5<br>
-      </td>
-      <td style="vertical-align: top;">1.5<br>
-      </td>
-      <td style="vertical-align: top;">1.5<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">JavaSE-1.6<br>
-      </td>
-      <td style="vertical-align: top;">1.6<br>
-      </td>
-      <td style="vertical-align: top;">1.6<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">PersonalJava-1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">PersonalJava-1.2<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">CDC-1.0/PersonalBasis-1.0<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">CDC-1.0/PersonalJava-1.0<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.1<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">CDC-1.1/PersonalBasis-1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.2<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">CDC-1.1/PersonalJava-1.1<br>
-      </td>
-      <td style="vertical-align: top;">1.3<br>
-      </td>
-      <td style="vertical-align: top;">1.2<br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h2>Choosing the Environment for your Bundle</h2>
-There are two settings that affect the environment used to compile your
-bundle.&nbsp; One is the manifest header <span
- style="font-weight: bold;">Bundle-RequiredExecutionEnvironment</span>.&nbsp;
-This header is a list of environments on which your bundle is able to
-run.&nbsp; Your bundle should only use methods that are in the proper
-subset of all the environments listed.&nbsp; It is desirable to have
-your compilation environment match your runtime environment as closely
-as possible.<br>
-<br>
-The second setting is the property <span style="font-weight: bold;">jre.compilation.profile</span>
-from your bundle's build.properties file.&nbsp; The value of this
-property should be the prefered environment for compiling this bundle
-if the Bundle-RequiredExecutionEnvironment list is not adequate.<br>
-<br>
-These two settings together form a list of environments,
-jre.compilation.profile first, then the environments from
-Bundle-RequiredExecutionEnvironment.&nbsp; The first
-environment on this list that is available in your build configuration
-(see above section) will be used to compile your bundle.<br>
-<br>
-Example:<br>
-<pre style="margin-left: 40px;">&lt;buildDirectory&gt;/plugins/bundleA/<br>	META-INF/manifest.mf: Bundle-RequiredExecutionEnvironment: CDC-1.0/Foundation-1.0, J2SE-1.3<br>	build.properties:&nbsp;    jre.compilation.profile=J2SE-1.4<br><br><span
- style="font-weight: bold;"></span>&lt;buildConfiguration&gt;/<br>	build.properties:&nbsp; J2SE-1.3=C:/Java1.3/jre/lib/rt.jar;C:/Java1.3/jre/lib/i18n.jar<br>			   J2SE-1.4=C:/Java1.4/jre/lib/rt.jar;C:/Java1.4/jre/lib/jsse.jar<br></pre>
-<p style="margin-left: 40px;">In the above setup, the list of
-environments considered (in order) is: J2SE-1.4,&nbsp;
-CDC-1.0/Foundation-1.0, J2SE-1.3.&nbsp; The bundle can run on
-CDC/Foundation and J2SE-1.3, but for some reason,&nbsp; it should be
-compiled with J2SE-1.4.&nbsp; In this case, J2SE-1.4 is set in the
-build configuration, and comes first in the list of environments, so it
-is used to compile the bundle.&nbsp; The source and target levels used
-in this case are 1.3 and 1.2.&nbsp; If instead, the build configuration
-defined only J2SE-1.3 and not J2SE-1.4, then J2SE-1.3 would be the only
-environment on the list for which a JRE is available, so it would be
-used to compile the bundle.&nbsp; In that case, the source and target
-levels would be 1.3 and 1.1.<br>
-</p>
-<h2>Explicitly Setting Compilation values</h2>
-If, for some reason, using the enviroments as outlined above does not
-result in the desired setup, then it is possible for a bundle to
-explicitly list the settings it requires.&nbsp; For example, if you
-have a bundle that uses J2SE-1.4 with asserts, then the source and
-target levels would need to be 1.4, instead of the default 1.3 and 1.2.<br>
-<br>
-To explicitly set the java source and target levels, the bundle should
-set the properties <tt style="font-weight: bold;">javacSource</tt> and
-<tt style="font-weight: bold;">javacTarget</tt> in it's
-build.properties
-file.&nbsp; These properties will override the values derived from the
-environment settings.<br>
-<br>
-Similarily, setting the property <tt>bootClasspath</tt> in the
-bundle's build.properties file will override the set of
-jars the bundle is compiled against.<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_order.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_order.htm
deleted file mode 100644
index afc5d8d..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_compilation_order.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Compilation Order and Parallelization</title>
-</head>
-<body>
-<h1>Compilation Order and Parallelization</h1>
-<p>By default, PDE/Build compiles plug-ins by delegating through the feature structure.  Features are visited depth first, the plug-ins within each feature are compiled in dependency-order (as determined by the OSGi resolver).</p>
-<p>This means that all dependencies of a given bundle must contained in the same feature, or in a feature that appears earlier in the depth-first traversal of the feature inclusion hierarchy.  This can make it difficult to organize your
-features.</p>
-
-<h3>Flattening Dependencies</h3>
-<p>New in 3.5 is a builder property <b><tt>flattenDependencies</tt></b>.  Setting this property to true will cause PDE/Build to instead sort all plug-ins regardless accross feature boundaries.  PDE/Build will then generate a new build script
-<i>compile.&lt;feature&gt;.xml</i> which lists all plug-ins in order sorted by their dependencies.  This allows you to partition your bundles into different features according to their functionality without worrying about their inter-dependencies.</p>
-
-<h3>Parallel Compilation</h3>
-<p>If <tt>flattenDependencies</tt> is specified, then PDE/Build is then able to compile bundles in parallel.  It does this by partitioning the sorted list of bundles into groups where each group contains bundles that depend only on bundles in earlier groups.</p>
-<p>Each group is then wrapped in an Ant <tt>&lt;parallel&gt;</tt> task.  The following properties control the parallelization behaviour:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>parallelCompilation</tt></td><td>Set to <b><tt>true</tt></b> to enable parallel compilation. (Requires <tt>flattenDependencies=true</tt>)</td></tr>
-			<tr><td><tt>parallelThreadCount</tt></td><td>The maximum number of threads to use.  Default is 3.  Corresponds to <i>threadCount</i> on the ant parallel task.</td></tr>
-			<tr><td><tt>parallelThreadsPerProcessor</tt></td><td>The maximum number of threads to use per available processor.  Corresponds to <i>threadsPerProcessor</i> on the ant parallel task.</td></tr>
-		</table>
-		
-<p>The resulting compile script that gets generated then looks something like this:</p>
-<pre>
-  &lt;project name="Compile master" default="main"&gt;
-     &lt;target name="main"&gt;
-        &lt;parallel threadsPerProcessor='3'&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.osgi" target="build.jars"/&gt;
-        &lt;/parallel&gt;
-        &lt;parallel threadsPerProcessor='3'&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.equinox.common" target="build.jars"/&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.equinox.p2.jarprocessor" target="build.jars"/&gt;
-        &lt;/parallel&gt;
-        &lt;parallel threadsPerProcessor='3'&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.update.configurator" target="build.jars"/&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.equinox.simpleconfigurator" target="build.jars"/&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.equinox.frameworkadmin" target="build.jars"/&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.core.jobs" target="build.jars"/&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.core.databinding.observable" target="build.jars"/&gt;
-             &lt;ant antfile="build.xml" dir="plugins/org.eclipse.swt" target="build.jars"/&gt;
-             ...
-
-</pre>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_controlling_output.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_controlling_output.htm
deleted file mode 100644
index dfb4af4..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_controlling_output.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Controlling the output format of the build</title>
-</head>
-<body>
-<h1>Controlling the output format of the build</h1>
-<p>
-This section describes how to control the output of a feature or
-product build.</p>
-<h3>Controlling the output format</h3>
-<p>
-The archivesFormat property allows specifying the output format (zip,
-tar, and folder) of the build on a configuration basis. The format of
-the property is &lt;configuration&gt; - &lt;format&gt;, where
-configuration is the same value than the one specified in the <tt>configs</tt>
-property and format is one of the following. </p>
-<ul>
-  <li><tt>folder</tt> - the output will be stored in a folder located
-in <tt>${buildDirectory}/tmp/${archivePrefix}</tt>. The targets
-specified in the <tt>allElements.xml</tt> are not used in this case.
-Due to current restrictions, only one configuration can be build at a
-time when using folder as output format.</li>
-  <li><tt>zip</tt> - the output will be stored in a zip file. The zip
-file will be created by the zip.exe found on the machine running the
-build. This is useful if you have non jar'ed plug-ins that contains
-files requiring specific permissions (mostly on UNIX based systems).
-The property <tt>zipargs</tt> allows passing additional options to the
-zip command.</li>
-  <li><tt>antZip</tt> - the output will be stored in a zip file. The
-zip file will be created by the zip implementation of Ant. This is the
-default value when nothing is specified.</li>
-  <li><tt>tar</tt> - the output will be stored in a gzip'ed tar file.
-The OS implementation of tar and gzip will be used. The property <tt>tarargs</tt>
-allows passing additional options to the tar command.</li>
-</ul>
-Note that changing the format of the output will not change the name of
-the created file. It needs to be changed in the allElements.xml file.
-<h3>Generating JNLP manifests</h3>
-<p>
-To enable the generation of JNLP manifests at build time, set <tt>generateJnlp</tt>
-to <tt>true</tt> and set <tt>jnlp.codebase</tt> to be the value where
-the
-jnlp file will be served from (see codebase attribute in jnlp tag) and <tt>jnlp.j2se</tt>.
-Note that this will not package your plug-ins and features for an
-update site, see the "preparing the output for an update site or jnlp
-site".
-Due to current restrictions, the creation of the jnlp manifest only
-works when producing folders as an output format.
-</p>
-<h3>Preparing the output for an update site or jnlp site</h3>
-<p>
-When put on an update site or a java web start site, plug-ins and
-features need to be packaged properly. To do this, simply set the <tt>outputUpdateJars</tt>
-property to true. Note that this will not generate the site.xml for the
-eclipse update site and it will not generate jnlp files (see generating
-jnlp files).
-</p>
-<h3>Grouping multiple configurations in one build</h3>
-In order to produce an output that contains the plug-ins and features
-of multiple configurations, set <tt>groupConfigurations</tt> to true.
-This will create an archive that contains all the plug-ins and features
-that match the configurations listed in the <tt>configs</tt> property.
-When using this, don't forget to add a target named <tt>&lt;feature.id&gt;.group.group.group</tt>
-in the <tt>allElements.xml</tt> file.
-Due to current restrictions, the usage of this option will cause the
-value specified in archivesFormat to be ignored and <tt>antZip</tt>
-will be used by default.
-<h3>Signing jars</h3>
-<p>
-In order to sign jars during the build, set the property <tt>signJars</tt>
-to true and set values for the properties <tt>sign.alias</tt>, <tt>sign.keystore</tt>,
-and <tt>sign.storepass</tt>.
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_custom_callbacks.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_custom_callbacks.htm
deleted file mode 100644
index 8a51cff..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_custom_callbacks.htm
+++ /dev/null

@@ -1,183 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Customizing feature and plug-in builds</title>
-</head>
-<body>
-<h1>Feature and Plug-in custom build steps</h1>
-<p>New in 3.2 is the ability for a feature or plug-in to contribute
-custom custom steps to its own build.&nbsp; These custom steps can be
-used for things like instrumenting byte-code after compilation,
-indexing help files for documentation, or copying extra files into the
-bundle.&nbsp;</p>
-<p>To use custom targets, a feature or plug-in must define the property
-<tt>customBuildCallbacks</tt> in its build.properties file; the value
-of this
-property is the location of an xml file, relative to the root of the
-feature/plug-in, containing the custom targets.  If the xml file is located elsewhere, use the property
-customBuildCallbacks.buildpath to set the directory to use. </p>
-<p>Templates named
-<span style="font-style: italic;">customBuildCallbacks.xml</span>
-containing the supported custom targets are
-provided in org.eclipse.pde.build/templates/plugins and&nbsp;
-org.eclipse.pde.build/templates/features respectively.&nbsp; These
-templates can be copied into your feature/plug-in and modified as
-needed. </p>
- <p>
- The custom targets will be invoked using the subant task; by default, <span style="font-style: italic;">failonerror</span> is set to false.  To change this
-set the property <tt>customBuildCallbacks.failonerror</tt> to true.  Similarly, the <span style="font-style: italic;">inheritall</span> parameter defaults to false.  Set the 
-property <tt>customBuildCallbacks.inheritall</tt> to change this. 
-</p>
-<h2>Plug-ins</h2>
-<p>The generated build.xml that builds a plug-in contains several
-targets that perform specific tasks.&nbsp; PDE Build allows the plug-in
-to provide custom pre and post targets that will be called before and
-after specific tasks.&nbsp; In addition to any ant properties that may
-already be defined, each custom target may also be passed a couple of
-specific properties.&nbsp; The following targets support custom
-callbacks:<br>
-</p>
-<ul>
-  <li><span style="font-weight: bold;">build.jars</span>:&nbsp; The
-build.jars target will invoke in turn each of the compilation targets
-that will be built for this bundle.&nbsp; It supports <span
- style="font-weight: bold;">pre.build.jars</span> and <span
- style="font-weight: bold;">post.build.jars</span> targets which are
-called before and after all the compilation targets are called.&nbsp;
-Both the pre and post targets are provided with the property <tt>build.result.folder</tt>
-which is the folder to which the
-results of the
-build will be copied.<br>
-    <span style="font-weight: bold;"></span></li>
-  <li><span style="font-weight: bold;">Compilation Targets</span>:&nbsp;
-The build.xml defines a compilation target for each jar being built (eg
-@dot for the bundle itself, or library.jar).&nbsp; Each compilation
-target supports 3 custom callbacks:
-  <ul>
-    <li><span style="font-weight: bold;">pre.&lt;compilation target&gt;</span>:&nbsp;
-Called before source files are compiled.&nbsp; It is provided with the
-following properties:
-    <ul>
-      <li><tt>target.folder</tt>:&nbsp; The folder where the compiled
-class
-files will be placed</li>
-      <li><tt>source.folder&lt;N&gt;</tt>:&nbsp; The source folder(s)
-containing
-the source to be compiled.&nbsp; (eg <tt>source.folder1</tt>, <tt>source.folder2</tt>,
-etc).</li>
-      <li><tt>&lt;compilation target&gt;.classpath</tt>:&nbsp; A
-reference to
-the ant path structure containing the classpath that will be used in
-the compilation.&nbsp; (eg <tt>@dot.classpath</tt>, <tt>library.jar.classpath</tt>).  The reference to the classpath should be used with a <tt>refid</tt>. 
-<br><b>Example:</b>
-<pre>
-&lt;classpath refid="library.jar.classpath"/&gt;
-&lt;property name="mypath" refid="library.jar.classpath" /&gt;
-</pre>
-</li>
-    </ul>
-    </li>
-    <li><span style="font-weight: bold;">post.compile.&lt;compilation
-target&gt;</span>:&nbsp; Called after the source is compiled, but
-before the class files are jared or copied into the build result
-folder.&nbsp;
-It is provided with the same properties as the pre.&lt;compilation
-target&gt; target.</li>
-    <li><span style="font-weight: bold;">post.&lt;compilation target&gt;</span>:&nbsp;
-Called at the end of the compilation target after the results are
-copied to the build result folder.&nbsp; It is provided with the
-following properties:
-    <ul>
-      <li>jar.Location:&nbsp; The jar or folder containing the
-compilation results.</li>
-      <li>&lt;compilation target&gt;.classpath:&nbsp; A reference to
-the ant path structure containing the classpath that was used in the
-compilation.</li>
-    </ul>
-    </li>
-  </ul>
-  </li>
-  <li><span style="font-weight: bold;">build.sources</span>:&nbsp; This
-target builds the source zips for each of the compilation
-targets.&nbsp; It supports <span style="font-weight: bold;">pre.build.sources</span>
-and <span style="font-weight: bold;">post.build.sources</span>
-targets.&nbsp; Both of these targets are provided with the property
-build.result.folder which is the folder to which the source zip files
-will be copied.</li>
-  <li><span style="font-weight: bold;">gather.bin.parts</span>:&nbsp;
-This target copies the build results (ie the jars and any other files
-being included in the bundle) to the final destination directory.&nbsp;
-It is also the target where the version qualifiers are replaced in the
-manifest file (see&nbsp;<a href="pde_version_qualifiers.htm">Version
-Qualifiers</a>). It supports <span style="font-weight: bold;">pre.gather.bin.parts</span>
-and <span style="font-weight: bold;">post.gather.bin.parts</span>
-targets.&nbsp; Two properties are provided to the pre and post targets:
-  <ul>
-    <li><tt>build.result.folder</tt>:&nbsp; the folder containing the
-results of
-the build</li>
-    <li><tt>target.folder</tt>:&nbsp; the destination folder to which
-the build
-results and bundle contents are being copied.</li>
-  </ul>
-  </li>
-  <li><span style="font-weight: bold;">gather.sources</span>: This
-target gathers the source zips for the bundle.&nbsp; It supports <span
- style="font-weight: bold;">pre.gather.sources </span>and <span
- style="font-weight: bold;">post.gather.sources</span> targets.&nbsp;
-Both the pre
-and post targets are provided with the target.folder property which is
-the folder that the sources are being copied to.<br>
-  </li>
-  <li><span style="font-weight: bold;">gather.logs</span>:&nbsp; This
-target collects the log files from the build.&nbsp; It supports <span
- style="font-weight: bold;">pre.gather.logs</span> and <span
- style="font-weight: bold;">post.gather.logs</span>.&nbsp; Both the pre
-and post
-targets are provided with the destination.temp.folder which is the
-temporary folder that the logs files are being copied to.<br>
-  </li>
-  <li><span style="font-weight: bold;">clean</span>:&nbsp; This target
-performs a clean, it supports <span style="font-weight: bold;">pre.clean</span>
-and <span style="font-weight: bold;">post.clean</span> targets.&nbsp;
-The pre and post targets have the following properties:
-  <ul>
-    <li><tt>plugin.destination</tt>:&nbsp; The folder that the final
-bundle was
-copied to.<br>
-    </li>
-    <li><tt>build.result.folder</tt>:&nbsp; The folder that the results
-of the
-build were copied to</li>
-    <li><tt>temp.folder</tt>:&nbsp; The temporary folder where results
-were staged before being copied to the final desination.<br>
-    </li>
-  </ul>
-  </li>
-</ul>
-<h2>Features</h2>
-<p>
-The generated build.xml for features only supports custom build
-callbacks for the gather.bin.parts target.&nbsp; This target will
-invoke that gather.bin.parts target of all the included features and
-plug-ins.&nbsp; It supports pre.gather.bin.parts and
-post.gather.bin.parts.&nbsp; Both of these targets are provided with
-the following properties:
-</p>
-<ul>
-  <li><tt>destination.temp.folder</tt>:&nbsp; The directory to which
-the plugins
-will be copied.</li>
-  <li><tt>feature.directory</tt>:&nbsp; The directory to which the
-files for
-this feature will be copied.<br>
-  </li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_customization.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_customization.htm
deleted file mode 100644
index caa17ea..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_customization.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Customizing a Headless Build</title>
-</head>
-<body>
-<h1>Customizing a Headless Build</h1>
-<p>There are multiple methods for customizing a headless build:</p>
-<ul>
-<li>Using a customTargets.xml file</li>
-<li>Using an allElements.xml file</li>
-<li>Using a customAssembly.xml file</li>
-<li>Using feature or plug-in custom callbacks.  (See <a href="pde_custom_callbacks.htm">Customizing feature and plug-in builds</a>)</li>
-</ul>
-<p>The exact format of the contents of these files all depend on each other.  Therefore, when using customTargets, allElements or customAssembly customizations, it is recommended to ensure that the templates used for these files all come from the same version of PDE/Build.  New versions of PDE/Build are backward compatible with old versions of these customization scripts.</p>
-<p>Template versions of these scripts are available in the <tt>org.eclipse.pde.build</tt> plug-in under the <tt>templates/headless-build</tt> folder.  To use the customization, simply copy the template into your build configuration directory and edit the appropriate targets.</p>
-
-<h2><a name="custom_targets">customTargets.xml</a></h2>
-<p>The customTargets.xml script is for top level customization of the build process.  It provides ant targets that are called between the major phases of the build.  There are pre and post targets available around each of the following build steps:</p>
-<ul>
-<li>Process p2 repositories</li>
-<li>Get Map files</li>
-<li>Fetch source</li>
-<li>Generate build scripts</li>
-<li>Process and run the build scripts</li>
-<li>Assemble the compiled plug-ins and features</li>
-<li>Package pre-compiled binary plug-ins and features</li>
-</ul>
-<p>To use the customTargets.xml script, simply copy it from the PDE/Build templates directory into your build configuration directory and edit the appropriate ant targets.  The script will be automatically detected and used by the headless build.</p>
-<p>The customTargets.xml script also provides delegation to the allElements.xml script for each of the build phases.</p>
-
-<h2>allElements.xml</h2>
-<p>The allElements.xml script is a kind of delegation script that is used to run the various build steps on a given element (usually a feature).  As with the customTargets.xml, to use these customization steps, copy the template from PDE/Build into your build configuration directory.  In Eclipse 3.4, the target element that will be built can be specified in the top level build configuration build.properties file using the properties <tt>topLevelElementType</tt> and <tt>topLevelElementId</tt>.  The elementType should be set to <tt>feature</tt> and the elementId should be set to the feature-id you wish to build.</p>
-<pre>
- 	&lt;target name="allElementsDelegator"&gt;
- 		&lt;ant antfile="${genericTargets}" target="${target}"&gt;
-	 		&lt;property name="type" value="${topLevelElementType}" /&gt;
-	 		&lt;property name="id" value="${topLevelElementId}" /&gt;
- 		&lt;/ant&gt;
- 	&lt;/target&gt;
-</pre>
-<p>The allElements.xml also provides targets used during the assembly and packaging phase of the build.  The <tt>defaultAssemble</tt> target will be called to assemble the archives for all platforms.  If desired, custom targets can be defined for individual platforms.</p>
-<p>To use a custom target for a given platform, define a property "<tt>assemble.&lt;element-id&gt;[.&lt;config&gt;]</tt> and a corresponding target.  The property tells PDE/Build to use this custom target instead of the default target.  This custom target can then be used to give the archive a custom name or perform pre or post processing on the archive.</p>
-<p><b>Example:</b></p>
-<pre>
-	&lt;property name="assemble.org.foo.feature.id.linux.gtk.x86" value="true" /&gt;
- 	&lt;target name="assemble.org.foo.feature.id.linux.gtk.x86"&gt;
- 		&lt;property name="archiveName" value="acme-RCP-${buildId}-linux.gtk.x86.tar.gz" /&gt;
- 		&lt;-- custom pre assemble steps for linux.gtk.x86--&gt;
- 		&lt;ant antfile="${assembleScriptName}" dir="${buildDirectory}"/&gt;
- 		&lt;-- custom post assemble steps for linux.gtk.x86--&gt;
- 	&lt;/target&gt;
-</pre>
-
-<h2>customAssembly.xml</h2>
-<p>The customAssembly.xml script is new in 3.4.  It provides customization points that will be called during the assembly and packaging phases of the build.  As with customTargets.xml and allElements.xml, to use these customization, copy the template from PDE/Build into your build configuration directory.</p>
-<p>The assemble and packaging scripts generated by PDE/Build perform the following actions:</p>
-<ul>
-<li>Call the gather.bin.parts target in the generated build.xml for all features and plug-ins being built.</li>
-<li>Jar up (and optionally sign) any plug-ins and features that are not shipped as folders</li>
-<li>Copy the final results into a staging area and create the final archive</li>
-</ul>
-<p>The assemble scripts deal with collecting the features and plug-ins that were compiled during the build and the package scripts deal with collecting any pre-compiled binary features and plug-ins.  The customAssembly.xml script provides the following targets before or after each of the above steps:</p>
-<ul>
-<li>gather.bin.parts: Called after each invocation of the gather.bin.parts target on the individual plug-ins and features.</li>
-<li>post.gather.bin.parts: Called after invoking the gather.bin.parts targets for all plug-ins and features. Results exist as folders and have not yet been jarred.</li>
-<li>pre.jarsigning: Called just prior to signing a jar.</li>
-<li>post.jarup: Called after all plug-ins and features have been jarred (and potentially signed). </li>
-<li>pre.archive: Called just before the archive file is built</li>
-</ul>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_build.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_build.htm
deleted file mode 100644
index a312772..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_build.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Building features</title>
-</head>
-<body>
-<h1>Building features</h1>
-<p>
-PDE Build comes with infrastructure to automate the build of features.
-Most of the setup necessary
-for such a build can be done through a few modifications to the
-template build.properties provided
-in PDE build. The following section focuses on setting up a simple
-build assuming that all plug-ins
-and features (both to-build and pre-built) referenced from the feature
-being built are already
-locally available on disk.
-</p>
-<h2>Basic Setup</h2>
-<h3>The Build Configuration Directory</h3>
-<p>The first step in setting up a build is to create the build configuration directory.  This is the directory in which the files that control and customize the headless build are kept.</p>
-<p>The main file for controlling the build is the top level build configuration build.properties file.  When setting up a new build, copy the template file from the org.eclipse.pde.build bundle in your eclipse install that you will be using to run your build.  The template file is located under org.eclipse.pde.build/templates/headless-build/build.properties.</p>
-<p>This directory is refered to by the <tt>builder</tt> properties which is normally set on the ant command line.</p>
-<h3>The buildDirectory</h3>
-<p>The <tt>buildDirectory</tt> property specifies the directory in which PDE/Build will generate scripts and perform the actual build.  Plug-ins and features that are being built should placed in <tt>${buildDirectory}/plugins</tt> and <tt>${buildDirectory}/features</tt> sub-directories.
-   If bundles and features are being fetch from a repository (See <a href="pde_fetch_phase.htm">Fetching From Repositories</a>), then they will be placed here as well.</p>
-<p>This directory may be the same as the build configuration directory, or it may be a different directory.  It may be desirable to use a separate directory, especially if the build configuration is kept in CVS and you don't want to pollute it with generated build artifacts.</p>
-<h3>Initial Properties</h3>
-<p>To set up a basic feature build, you need to edit the build configuration build.properties file and set the following properties:</p>
-<ul>
-  <li><span style="font-weight: bold;">topLevelElementId</span>: Set to the id of the feature you wish to build.</li>
-  <li><span style="font-weight: bold;">baseLocation</span>: the location of an eclipse install containing pre-built features and plug-ins in <tt>features/</tt> and <tt>plugins/</tt> subdirectories.  These are the binaries against which you will be compiling.  If you have no pre-requisite binaries and are building everything from scratch, this property can be left un-set.</li>
-  <li><span style="font-weight: bold;">buildDirectory</span>:&nbsp;the directory the build will take place in.</li>
-  <li><span style="font-weight: bold;">configs</span>: list the configurations for which you want your feature to be built. You can uncomment the configuration(s) provided (be careful of the line continuations). If the feature you are building is platform independent, this property does not need to be set or can be set to <tt>*,*,*</tt>.</li>
-  <li><span style="font-weight: bold;">archivePrefix</span>: the name of the directory in which your feature will be unzipped on disk.</li>
-</ul>
-<p>Previous version of PDE/Build also required an allElements.xml file, this is no longer necessary in 3.4.  The allElements.xml can still be used, but is only required if you wish to customize certain aspects of your build.  See <a href="pde_customization.htm">Customizing a Headless Build</a>.</p>
-
-<h2>Running the build</h2>
-<p>To run the build you will use the org.elipse.ant.core.antRunner application. When invoking eclipse with this application to perform a build you need to set two arguments on the command line:</p>
-<ul>
-  <li><code>-buildfile=&lt;/path/to/build.xml&gt;</code>:&nbsp; This is the path to the build.xml provided by pde build.&nbsp; It is located in the org.eclipse.pde.build/scripts directory.&nbsp; This is the build script that drives the whole build process.</li>
-  <li><code>-Dbuilder=&lt;/path/to/configuration folder&gt;</code>:&nbsp;This is the path to the build configuration folder.</li>
-</ul>
-<p>Run the antRunner application using the following command:</p>
-<br>
-<div style="margin-left: 40px;"><code>java -jar
-&lt;eclipseInstall&gt;/plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar
--application org.eclipse.ant.core.antRunner -buildfile
-&lt;&lt;eclipseInstall&gt;/plugins/org.eclipse.pde.build_&lt;version&gt;/scripts/build.xml&gt;
--Dbuilder=&lt;path to the build configuration folder&gt;</code><br>
-</div>
-<p>Once the build is complete, you can get the result in the build directory in the folder named I.TestBuild (this name can be configured by setting the buildLabel property).</p>
-<h2>Advanced scenarios</h2>
-<p>If you require more customization of the build, ie fetching from a repository, see the Advanced PDE Build topics for more information.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_ant.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_ant.htm
deleted file mode 100644
index 3db03ff..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_ant.htm
+++ /dev/null

@@ -1,116 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Generating ANT scripts</title>
-</head>
-
-<body>
-
-<h1>Generating Ant scripts</h1>
-
-<p> <b> Ant</b> is a simple open-source scripting engine that is capable of running
-scripts written in XML format. Ant is ideal for executing tasks usually found in
-automated builds.&nbsp;</p>
-
-<p>The variables set in the plug-in, fragment or feature <b>build.properties
-</b> will be used to generate scripts for
-Ant.&nbsp; PDE generates Ant scripts for creating
-individual plug-in and fragment build files and one overall script for building
-the feature JAR. This &quot;main&quot; script is also responsible for running individual
-script files in the right order (defined by the plug-in dependency chain). Each
-build file has the same name (<b>build.xml</b>) and is created as a sibling of the manifest
-files in the corresponding projects.</p>
-
-<p>Since Ant scripts use the replacement variables in <b>build.properties</b>, you can typically use them &quot;as is&quot;, without
-modifying the generated scripts. If you do modify them, you must not recreate the
-scripts every time you want to rebuild the component. </p>
-
-<p>To create scripts, you can simply select <b>Create Ant Build File</b> while a 
-suitable manifest file (plugin.xml, fragment.xml or feature.xml) is selected in 
-the Navigator or Package Explorer views. The command will generate
-the build script. After selecting <b>Run Ant...</b> from the pop-up menu while 
-the newly generated script file is selected, the following wizard will open:</p>
-
-<p>
-<img src="../guide/images/tasks/feature-jar.png" alt="Ant execution wizard showing available targets" border="0"></p>
-
-<p>The standard Ant wizard allows customization in two ways: by
-providing the execution arguments and by selecting one or more build targets.</p>
-
-<h4>Properties</h4>
-<p>Ant arguments are typically used to provide property values that
-override default values and control the build process. Arguments are set using
-&quot;-Dproperty=value&quot;. The following properties are recognized:</p>
-
-<ul>
-  <li>
-    <p><b>bootclasspath</b> - if set, it replaces the default boot
-    classpath. Used when compiling cross-platform plug-ins (e.g. building a UI
-    plug-in for Windows using Linux)</p></li>
-  <li><b>build.result.folder</b> - where
-    the temporary files for the update JAR creation should be placed.
-    These files are usually the plug-in library JARs.</li>
-  <li><b>plugin.destination</b> - where
-    plug-in and fragment update JARs should be put. These JARs represent
-    entire plug-ins and fragments in a format suitable for publishing on an
-    Install/Update server and referencing by a feature. The typical layout of an
-    Update site is to have all the plug-in and fragment JARs in one place and
-    all the features in another. This argument is useful for placing plug-ins and
-    fragment directly into the desired directory (or the staging place on the
-    local machine before pushing the features onto the remote server).</li>
-  <li><b>feature.destination</b> - where
-    feature update JARs should be put.</li>
-</ul>
-<p>To adapt the behavior of the compiler, the following properties are recognized:</p>
-<ul>
-	<li><b>javacFailOnError</b> - stop the build when an error occurs when set to true. Default is false.</li>
-	<li><b>javacDebugInfo</b> - compile source with debug information when set to true. Default is true.</li>
-	<li><b>javacVerbose</b> - produce verbose output when set to true. Default is true.</li>
-	<li><b>javacSource</b> - value of the -source command-line switch.</li>
-	<li><b>javacTarget</b> - generate class files for specific VM version.</li>
-	<li><b>compilerArg</b> - additional command line arguments for the compiler.</li>
-</ul>
-
-<h4>Targets</h4>
-
-<p>When executing feature build scripts, the
-following targets are used to call individual targets of plug-ins or fragments.
-In order to specify what target to execute, the property <b>target</b> should be
-set (e.g. -Dtarget=refresh). One of the <b>all.*</b> targets serves as an iterator, whereas
-the actual target to execute is specified via the property <b>target</b>.</p>
-<ul>
-  <li><b>all.plugins</b> - for all listed plug-ins</li>
-  <li><b>all.fragments</b> - for all listed fragments</li>
-  <li><b>all.children</b> - for all listed plug-ins and fragments</li>
-  <li><b>build.jars</b> - build JARs for all feature children;</li>
-  <li><b>build.sources</b> - build source for all feature children;</li>
-  <li><b>build.update.jar</b> - generate a feature JAR in the format used by the install/update mechanism.
-	The above mentioned property <b>feature.destination</b> can be used to define
-	where to put the JAR;</li>
-  <li><b>zip.distribution</b> - creates a zip
-file with the feature and its plug-ins and fragments in an SDK-like structure
-but does not include source code;</li>
-  <li><b>zip.sources</b> - creates a zip file with the feature and its plug-ins and fragments in an SDK-like structure which only includes the source;</li>
-  <li><b>clean</b> - delete everything produced by running any of the target;</li>
-  <li><b>refresh</b> - performs a &quot;Refresh&quot; action in the current project, thus making the
-newly generated resources visible in the Navigator or Package Explorer.</li>
-  <li><b>zip.plugin</b> - creates a zip file with the binary and source contents of a plug-in with the following structure:
-  <blockquote>
-  id_version/<br>
-  &nbsp;&nbsp;&nbsp; contents
-</blockquote>where 'id' is the plug-in unique identifier
-and 'version' is the plug-in version. This zip file can be directly unzipped
-into the Eclipse installation directory as a form of a quick manual deployment.</li>
-</ul>
-
-
-
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm
deleted file mode 100644
index 0b42a5a..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_feature_generating_antcommandline.htm
+++ /dev/null

@@ -1,468 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Command line Ant script generation</title>
-</head>
-<body>
-<h1>Generating Ant scripts from the command line</h1>
-<p>Ant scripts are typically generated using the Plug-in Development
-Environment (PDE), but it is also possible to generate
-them by hand or from other scripts.&nbsp;<br>
-Indeed PDE exposes Ant tasks to generate the various build scripts.
-Build script generation facilities
-reside in the following tasks.&nbsp; Arguments are also listed for each
-task.
-</p>
-<ul>
-  <li><b><a name="eclipseFetch">eclipse.fetch</a></b>: generates an Ant script that fetches
-content from a CVS repository. The eclipse fetch is driven by a file
-whose format is described below (see <a href="#directoryFileFormat">Directory
-file format</a>).
-    <table style="text-align: left; margin-left: 40px; width: 90%;"
- border="1" cellpadding="1" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top; text-align: left;"><span
- style="font-style: italic;">elements</span>:<br>
-          </td>
-          <td style="vertical-align: top;">the entry that will be
-fetched. The format
-expected is of the form type@id[,version] as specified in the directory file
-format;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">buildDirectory</span>:<br>
-          </td>
-          <td style="vertical-align: top;">the directory into which
-fetch scripts will be generated and into which features and plug-in projects will be
-checked out;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">directory</span>:<br>
-          </td>
-          <td style="vertical-align: top;">the path to a directory file;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">children</span>:<br>
-          </td>
-          <td style="vertical-align: top;">optional, specifies whether
-the script generation for contained plug-ins and fragments should be invoked.
-Default is set to true;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">cvspassfile</span>:<br>
-          </td>
-          <td style="vertical-align: top;">optional, the name of a CVS
-password file;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">fetchTag</span>:<br>
-          </td>
-          <td style="vertical-align: top;">optional, overrides the tag
-provided in
-directory file by the given value;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">configInfo</span>:<br>
-          </td>
-          <td style="vertical-align: top;">optional, an ampersand
-separated list of
-configuration indicating the targeted configuration. The default is set
-to be platform independent;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">recursiveGeneration</span>:&nbsp;&nbsp; <br>
-          </td>
-          <td style="vertical-align: top;">optional, specify whether or
-not fetch scripts should be generated for nested features. The default is
-set to true.</td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-  </li>
-</ul>
-<ul>
-  <li><b>eclipse.buildScript</b>: generates a build.xml file for the
-given elements as well as additional scripts used by the pde build infrastructure.
-    <table style="width: 90%; text-align: left; margin-left: 40px;"
- border="1" cellpadding="1" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">elements</span> : <br>
-          </td>
-          <td style="vertical-align: top;">the entry to be built.
-Entry is expected to be of the form type@id[,version] as specified in the
-directory file format;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">buildDirectory :</span><br>
-          </td>
-          <td style="vertical-align: top;">the directory where the
-features and plug-ins to build are located. Plug-ins and features must
-respectively be located in <tt>plugins</tt> and <tt>features</tt> folders;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">children</span> :<br>
-          </td>
-          <td style="vertical-align: top;">optional, specifies whether
-the script generation for contained plug-ins and fragments should be invoked.
-Default is set to true;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">recursiveGeneration</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, specified whether
-the
-script generation for contained features should be invoked. Default is
-set to true;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">devEntries</span> :<br>
-          </td>
-          <td style="vertical-align: top;">optional, a comma separated
-list of
-directories to be given to the compile classpath;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">buildingOSGi</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, indicates if the
-target is 3.x.
-or 2.1.&nbsp; Default is true;<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">baseLocation</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, indicates a folder
-which
-containing a target eclipse install with <tt>features/</tt> and <tt>plugins/</tt>
-subdirectories;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">configInfo</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, an ampersand
-separated list of
-configuration indicates the targeted configuration. The default is set
-to be platform independent;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">pluginPath</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, a platform file
-separator separated list of locations from which to find additional
-plug-ins;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">archivesFormat</span> :<br>
-          </td>
-          <td style="vertical-align: top;">optional, an ampersand
-separated list of
-configs and the expected output format for each of those. The format is
-separated by a dash (-) from the configuration. The values supported
-are: folder, tar, zip, antZip, respectively meaning don't archive, use
-tar to create the archive, use the version of info zip available on the
-platform, use ant zip . The default value is antZip;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">product</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, '/' separated path
-to the location of
-an RCP product being built. The first segment of the path must refer to
-the plug-in id of a plug-in containing the .product file;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">signJars</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, indicates if the
-scripts generated
-must sign jars for features and plug-ins. The default value is false.
-The parameters to the sign task are controlled by the following ant
-properties: sign.alias, sign.keystore and sign.storepass respectively
-being passed to the alias, keystore and storepass parameters from the
-ant <a href="http://ant.apache.org/manual/CoreTasks/signjar.html">signJar
-task</a>. The default value is false;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">generateJnlp</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, indicates if a
-jnlp file should
-be generated for all the features being built;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">outputUpdateJars</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, generates plug-ins
-and
-features in the update site format when set. The default value is
-false. Note that the site.xml is not generated nor updated;</td>
-        </tr>
-
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;"></span> <span style="font-style: italic;">groupConfiguration</span>
-: <br>
-          </td>
-          <td style="vertical-align: top;">optional, whether or not to
-group all configurations being built into a single archive;<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">generateVersionsLists</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, whether or not to
-generate properties files listing the versions of features and plug-ins
-that were built;<br>
-          </td>
-        </tr>
-
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">filteredDependencyCheck</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, constrain the set of plug-ins and features
-          to be considered during the build to those reachable from the features;<br>
-          </td>
-        </tr>
-        
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">filterP2Base</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, constrain the set of plug-ins and features
-          to be considered from the baseLocation to those considered to be installed by p2;<br>
-          </td>
-        </tr>
-        
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">generateFeatureVersionSuffix:&nbsp;</span>
-          </td>
-          <td style="vertical-align: top;">optional, whether or not to
-generate the feature version suffix. See also <a
- href="pde_version_qualifiers.htm">Version Qualifiers</a>;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">generatedVersionLength</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, the length of the generated feature version suffix. By default it is set to 28. See also <a
- href="pde_version_qualifiers.htm">Version Qualifiers</a>;<br>
-          </td>
-        </tr>
-        
-       <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">significantVersionDigits</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, the number of significant digits used when generating feature version suffixes.
-          See also <a href="pde_version_qualifiers.htm">Version Qualifiers</a>;<br>
-          </td>
-        </tr>
-        
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">forceContextQualifier</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, uses the given
-value to replace the .qualifier being by plug-ins and features. See also <a
- href="pde_version_qualifiers.htm">Version Qualifiers</a>;<br>
-          </td>
-        </tr>
-                
-      </tbody>
-    </table>
-  </li>
-</ul>
-<ul>
-  <li><a name="eclipseGenerateFeature"><span style="font-weight: bold;">eclipse.generateFeature</span></a>:
-generates a feature that will contain the provided elements.&nbsp; This
-task is used to <a href="pde_product_build.htm">build an RCP
-application from a product configuration file</a>.<br>
-    <table style="width: 90%; text-align: left; margin-left: 40px;"
- border="1" cellpadding="1" cellspacing="0">
-      <tbody>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">featureId</span> : <br>
-          </td>
-          <td style="vertical-align: top;">The id to give to the
-generated Feature.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">buildDirectory</span>:&nbsp;&nbsp;&nbsp; <br>
-          </td>
-          <td style="vertical-align: top;">the directory where the
-features and plug-ins (in <tt>/features</tt> and <tt>/plugins</tt> subdirectories) to
-include are located.&nbsp; The generated feature will be placed in the
-/features subdirectory.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">baseLocation</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, indicates a folder
-which contains installed features and plug-ins<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">productFile</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, a product file on
-which to base the generated feature.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">verify</span> : <br>
-          </td>
-          <td style="vertical-align: top;">Whether or not to use the
-resolver to verify that the provided plug-ins and features are
-available.&nbsp; This also determines whether or not the the feature
-will be able to correctly handle platform specific fragments and
-plug-ins that will be JARed.&nbsp; If all the elements to be included
-in the feature are available locally, then verify should be set to
-True.&nbsp; If the elements need to be fetched from a repository, set
-verify to False, use the resulting feature to fetch the required
-plug-ins and features, then regenerate the container feature using
-verify = True.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">pluginPath</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, a platform file
-separator separated list of locations from which to find additional
-plug-ins</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">configInfo</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, an ampersand
-separated list of
-configuration indicates the targeted configuration. The default is set
-to be platform independent;</td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">pluginList</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, a comma separated
-list of plug-in ids to include in the generated feature.  (Supports attributes, see below)<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">featureList</span> : <br>
-          </td>
-          <td style="vertical-align: top;">optional, a comma separated
-list of feature ids to include in the generated feature. (Supports attributes, see below)<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">fragmentList</span> :<br>
-          </td>
-          <td style="vertical-align: top;">optional, a comma separated
-list of fragment ids to include in the generated feature. (Supports attributes, see below)<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">buildPropertiesFile</span> :<br>
-          </td>
-          <td style="vertical-align: top;">optional, the location of a properties file whose contents should be used as the generated feature's build.properties.<br>
-          </td>
-        </tr>
-        <tr>
-          <td style="vertical-align: top;"><span
- style="font-style: italic;">includeLaunchers</span> :<br>
-          </td>
-          <td style="vertical-align: top;">optional, whether or not to include the equinox launchers, default value is "true".<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-    <p>The <tt>pluginList</tt>, <tt>featureList</tt>, and <tt>fragmentList</tt> arguments of the eclipse.generateFeature task all support attributes.  These arguments all take the form:</p>
-    <pre style="text-align: center;">List = &lt;element-id&gt;[;&lt;attribute&gt;=&lt;value&gt;]* [,&lt;element-id&gt;[;&lt;attribute&gt;=&lt;value&gt;]*]*</pre>
-    <p>Each attribute=value pair will be inserted into the generated xml corresponding to the given element.  <b>Example:</b></p>
-    <pre>
-    	featureList = org.eclipse.feature;optional=true
-    	pluginList = org.eclipse.plugin.A;unpack=true
-    	fragmentList=org.eclipse.fragment.a;os=win32,org.eclipse.fragment.b;os=linux;ws=gtk;arch=x86
-    	
-    	&lt;feature ...&gt;
-    	     ...
-    	     &lt;includes id="org.eclipse.feature" version="0.0.0" optional="true" /&gt;
-    	     ...
-    	     &lt;plugin id="org.eclipse.plugin.A" version="0.0.0" unpack="true" /&gt;
-    	     &lt;plugin id="org.eclipse.fragment.a" version="0.0.0" os="win32" fragment="true" /&gt;
-    	     &lt;plugin id="org.eclipse.fragment.b" version="0.0.0" os="linux" ws="gtk" arch="x86" fragment="true" /&gt;
-    	     ...
-    	&lt;/feature&gt;
-    </pre>
-  </li>
-</ul>
-<h4>Examples</h4>
-<pre>&lt;eclipse.fetch elements="bundle@org.eclipse.osgi"<br>		buildDirectory="c:\toBuild"<br>		directory="directory.txt"<br>		configInfo="win32,win32,x86 &amp; linux, motif, x86"<br>		/&gt;<br>		<br>&lt;eclipse.buildScript elements="bundle@org.eclipse.osgi" <br>		buildDirectory="c:\toBuild"<br>		archivesFormat="macosx, carbon, ppc - tar"/&gt;<br></pre>
-<h3><a name="directoryFileFormat">Directory file format</a></h3>
-Directory files are used to indicate where the plug-ins and features
-can be obtained, as well as their versions. It is a Java property file whose keys are always of the form 
-<tt>type@id[,version]</tt> but where the value is open ended. When using
-map files to fetch your elements, the directory file is a concatenation
-of all the map files, for more details on map files see <a
- href="pde_fetch_phase.htm">Fetching From
-Repositories</a>.
-
-<h3>Using the targets</h3>
-<p>The tasks previously described only work if Eclipse is running. In
-the particular scenario of executing Ant scripts using Eclipse
-tasks,the scripts must be run using the Eclipse Ant Runner application.
-The command line for this particular
-case is the following:
-</p>
-<pre>  java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar -application org.eclipse.ant.core.antRunner -buildfile build.xml<br> </pre>
-<p>Note that the parameters appearing after the application are the
-parameters that are passed to Ant.
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_fetch_phase.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_fetch_phase.htm
deleted file mode 100644
index 6737a08..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_fetch_phase.htm
+++ /dev/null

@@ -1,188 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Fetching from Repositories</title>
-</head>
-<body>
-<h1>Fetching from Repositories</h1>
-<p>
-The infrastructure offered by PDE Build provides steps to fetch the
-source code and pre-built plug-ins from a repository as part of the build process (see the <a href="pde_feature_generating_antcommandline.htm#eclipseFetch">eclipse.fetch</a> task 
-and the <a href="../reference/pde_builder_config.htm#fetchControl">properties to control fetching</a>).
-Two possibilities are available: let PDE build automatically fetch the
-source, or fetch the source code manually.</p>
-
-<h3>First step to automation, the map file</h3>
-<p>
-Given the identifier of a feature or a plug-in that needs to be built, the build
-infrastructure is able to fetch from a repository all the included features and
-plug-ins.</p>
-<p>
-In order to know where to get things from, PDE uses map files. A map
-file is a java property file which maps feature and plug-in ids to a
-location and a tag in a repository. The format of map files is open and but  
-the <b>key</b> part is fixed by PDE Build:</p>
-<div style="text-align: center;">
-<pre>&lt;elementType&gt;@&lt;elementID&gt;[,&lt;elementVersion&gt;] = &lt;repo specific content&gt;</pre>
-</div>
-<p>where <tt>elementType</tt> is one of <tt>bundle</tt>, <tt>feature</tt>,
-<tt>plugin</tt> or <tt>fragment</tt>, and <tt>elementId</tt> and <tt>elementVersion</tt> give the specifics of the element.</p>
-
-<h4>Map file entry for CVS</h4>
-The format of a map file entry to fetch content from CVS is the following:
-<div style="text-align: center;">
-	<pre>&lt;key&gt; = CVS, [,args]</pre>
-</div>
-where <tt>args</tt> is a comma-separated list of key/value pairs described below:
-<ul>
-	<li><tt>tag</tt>, the CVS tag to check out;</li>
-	<li><tt>cvsRoot</tt>, a CVS connection string;</li>
-	<li><tt>path</tt>, an optional CVS module and path where to get the folder containing the element. By default the element name is used as module name;</li>
-	<li><tt>prebuilt</tt>, an optional boolean indicating if the element downloaded is prebuilt. By default this is false;</li>
-	<li><tt>cvsPassFile</tt>, an option path to a cvs pass file;</li>
-	<li><tt>password</tt>, an optional password to use to connect to CVS;</li>
-</ul>
-	
-Example:
-<div style="text-align: center;">
-<pre>plugin@com.ibm.icu,3.6.1=CVS,tag=v200704191630,cvsRoot=:pserver:anonymous@dev.eclipse.org:/cvsroot/tools,path=org.eclipse.orbit/com.ibm.icu/bin,prebuilt=true</pre>
-</div>
-<br>
-<table style="border: solid 1px">
-<tr><td><b>Old style Map Entries</b></td></tr>
-<tr><td>
-In Eclipse 3.2 and earlier, the map file format for CVS was:
-<div style="text-align: center;">
-<pre>&lt;elementType&gt;@&lt;elementID&gt; = CVS, &lt;TAG&gt;, &lt;CVSROOT&gt;[,&lt;PASSWORD&gt;[,&lt;PATH&gt;[,&lt;CVSPASSFILE&gt;]]]</pre>
-</div>
-If any of the optional arguments aren't specified, then the commas are still required to delimit any following arguments.  This format should be considered deprecated and the key/value format is prefered.
-</td>
-</tr>
-</table>
-<h4>Map file entry for Ant GET</h4>
-<p>
-The format of a map file entry to fetch content from any URL supported by <a href="http://ant.apache.org/manual/CoreTasks/get.html">Ant GET</a> is the following:</p>
-<div style="text-align: center;">
-<pre>&lt;key&gt; = GET, &lt;url&gt; [,args]</pre>
-</div>
-where <tt>url</tt> is the url to retrieve the data from and <tt>args</tt> is an optional comma-separated list of key/value pairs described below:  
-<ul>
-	<li><tt>unpack</tt>, set to true the indicate that the downloaded element should be unzipped;</li> 
-	<li><tt>verbose</tt>, set to true to show verbose progress information when downloading. The default value is false;</li>
-	<li><tt>ignoreerrors</tt>, set to true to log errors during the transport. The default value is false;</li>
-	<li><tt>usetimestamp</tt>, conditionally download a file based on the timestamp of the local copy (for http URLs only) when set to true. The default value is false;</li>
-	<li><tt>username</tt>, the username for "BASIC" http authentication;</li>
-	<li><tt>password</tt>, the password to perform the download.</li>
-</ul>
-
-Example:
-<div style="text-align: center;">
-   <pre>plugin@com.ibm.icu,3.4.5=GET,http://download.eclipse.org/tools/orbit/downloads/drops/S200705301823/bundles/com.ibm.icu_3.4.5.jar, unpack=true</pre>
-</div>
-
-<h4><a name="p2_fetch">Map file entry for a p2 fetch</a></h4>
-<p>A new extension has been added to PDE/Build that enables users to fetch artifacts from p2 repositories. You can now add an 
-entry to your map file for build input and PDE/Build will retrieve the artifact and include it in the build. The map file entry needs to include the 
-id and version of the installable unit (IU), and the URI of the repository where the IU can be found. The metadata and artifact repositories are 
-assumed to be co-located. 
-</p>
-
-<p><i>Note:</i> In the Galileo release this only works for bundles/plug-ins and not features.</p>
-
-<p>
-The format of a map file entry to fetch content via p2 is as follows:
-</p>
-<div style="text-align: center;">
-<pre>&lt;elementType&gt;@&lt;elementID&gt; = p2IU, &lt;id&gt;, &lt;version&gt;, &lt;repository&gt;</pre>
-</div>
-<ul>
-<li><tt>id</tt>, the identifier of the Installable Unit;</li>
-<li><tt>version</tt>, the version of the Installable Unit;</li>
-<li><tt>repository</tt>, the location (URI) of the repository where the IU will be found.</li>
-</ul>
-
-Example:
-<div style="text-align: center;">
-   <pre>plugin@my.bundle.id,1.0.0=p2IU,id=my.bundle.id,version=1.0.0,repository=http:/example.eclipse.org/repo</pre>
-</div>
-
-
-
-
-<h4>Map file entry for other repositories</h4>
-<p>PDE Build provides an extension point
-where fetch script generators for different repositories can be plugged in. When your eclipse
-install contains a bundle that provides a script generator extension
-for a different type of repository, you can use that repository by
-specifying it in your map file entries and adhering to the format specified by the extension provider.</p>
-
-<h3>Setting up for CVS source fetching</h3>
-To set up fetching your source from CVS, you should do the following:<br>
-<ul>
-  <li>Make sure you have a cvs.exe on your system search path.&nbsp;
-(Download CVS from <a href="http://www.nongnu.org/cvs/">here</a>).<br>
-  </li>
-  <li>Create a folder called maps in the build directory.</li>
-  <li>Create a file with extension .map in the maps folder.</li>
-  <li>Fill in this map file with all the elements that need to be
-fetched from a repository.</li>
-  <li>Edit the build.properties file from the configuration folder and
-comment out the line <tt>skipFetch=true</tt>.&nbsp; If that property
-is set, then PDE build will skip the entire fetch phase.&nbsp; If you
-want the tag specified in the map files to be ignored you can set the
-property <tt>fetchTag</tt> to a specific value. This is useful when
-doing a nightly build from HEAD instead of from the tagged versions. </li>
-</ul>
-<h4>Getting the map files from CVS</h4>
-Map files are usually stored in a repository. PDE Build offers default
-infrastructure to get those map files from a CVS repository.
-To enable this function change the following properties in your
-configuration's build.properties from your configuration directory:
-<ul>
-  <li><span style="font-weight: bold;">skipMaps</span>:&nbsp; Comment
-out this property.&nbsp; If this property is set, then PDE build will
-not fetch the map files.<br>
-  </li>
-  <li><span style="font-weight: bold;">mapsRepo</span> =
-:pserver:anonymous@example.com/path/to/repo.&nbsp; The CVS repository
-from which to get the map files.<br>
-  </li>
-  <li><span style="font-weight: bold;">mapsRoot</span> =
-/path/to/maps.&nbsp; The path in the CVS repository to the directory
-containing the map files.<br>
-  </li>
-  <li><span style="font-weight: bold;">mapsCheckoutTag</span> =
-HEAD.&nbsp; The CVS tag to use to checkout the map files.</li>
-</ul>
-Fetching the map files from CVS occurs during the Pre-Build phase of
-the build.&nbsp; Scripts to
-fetch all the features and plug-ins included in the feature you are
-building will be generated and
-run during the fetch phase of the build.&nbsp;
-
-<h3>Automatic fetching from other repositories</h3>
-<p>If&nbsp; you are automatically fetching your map files from the
-repository, you will need to copy the customTarget.xml file from
-org.eclipse.pde.build/templates/headless-build into your configuration
-directory.&nbsp; The target&nbsp; getMapFiles is used to fetch the map
-files, this should be modified to fetch from your repository.</p>
-<h3>Getting source code manually</h3>
-You can write custom fetch targets to retrieve your plug-ins and
-features which can be invoked from
-the preSetup or postSetup targets in the customTargets.xml file.&nbsp;
-Features and plug-ins should
-be fetched to
-<tt>${buildDirectory}/features</tt>
-and
-<tt>${buildDirectory}/plugins</tt>
-respectively.&nbsp;
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_individual_source.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_individual_source.htm
deleted file mode 100644
index 44843b2..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_individual_source.htm
+++ /dev/null

@@ -1,116 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" charset="ISO-8859-1" type="text/css">
-  <title>Individual Source Bundles</title>
-</head>
-<body>
-<h1>Individual Source Bundles</h1>
-The traditional format of source bundles in Eclipse was a folder containing src.zip's for all the plug-ins included in a given feature.  Starting in 3.4, Eclipse now ships with individual source bundles.  For each bundle there is a corresponding source bundle which is a jar containing the source for that bundle.  This allows for more flexible delivery of source, and it also alleviates some path length issues that may be experienced on some platforms.
-
-<h2>Eclipse-SourceBundle</h2>
-<p>A source bundle is identified by the presence of the <b><tt>Eclipse-SourceBundle</tt></b> header in its manifest.  The format of this header is:</p>
-<pre style="text-align: center;">Eclipse-SourceBundle: &lt;bundle-id&gt;;version=&lt;version&gt;;roots:="root1, root2"</pre>
-<p>The bundle-id and version indicate the bundle that the included source code corresponds to.  The roots directive indicates the folders within the source bundle that actually contain source code.  If no roots directive is specified, then a value of &quot;.&quot; is assumed.</p>
-<p>Class file libraries are mapped to source locations in a predictable manner. The root of the plug-in maps to the root of the source bundle. This is the main case for most jarred plug-ins. If the plug-in contains additional libraries "foo/lib.jar", the source is expected to be in corresponding "foo/libsrc/" folders in the source bundles.</p>
-<ul>
-<li><b>Example 1</b> : The org.eclipse.pde.core bundle has class files in the root of the jar, plus a nested jar "ant_tasks/pde-ant.jar".  Therefore, the source bundle should have java files in the root and java files in a "ant_tasks/pde-antsrc" folder.
-The roots directive lists both the root of the source bundle "." and the "ant_tasks/pde-antsrc" folder.
-<pre>
-org.eclipse.pde.core.jar		org.eclipse.pde.core.source.jar
-  - org/**/*.class			  - org/**/*.java
-  - ant_tasks/pde-ant.jar		  - ant_tasks/pde-antsrc/org/**/*.java
-<br>
-Eclipse-SourceBundle: org.eclipse.pde.core;version="3.4.0.N20071128-0010";roots:="ant_tasks/pde-antsrc,."
-</pre>
-</li>
-<li><b>Example 2</b> : The org.eclipse.pde.build bundle is a folder on disk.  It contains a pdebuild.jar and a lib/pdebuild-ant.jar.  The source bundle will be a jar that contains a "pdebuildsrc" folder and a "lib/pdebuild-antsrc" folder. 
-<pre>
-org.eclipse.pde.build/			org.eclipse.pde.build.source.jar
-  - pdebuild.jar			  - pdebuildsrc/org/**/*.java
-  - lib/pdebuild-ant.jar		  - lib/pdebuild-antsrc/org/**/*.java
-<br>
-Eclipse-SourceBundle: org.eclipse.pde.build;version="3.4.0.N20071128-0010";roots:="pdebuildsrc,lib/pdebuild-antsrc"
-</pre>
-</li>
-</ul>
-<h2>Generating Individual Source Bundles</h2>
-<p>PDE/Build can automatically generate individual source bundles, but only in a headless build.  Individual soure bundle geneation can be turned on by specifying:</p>
-<pre style="text-align: center;">individualSourceBundles=true</pre>
-<p>This must be specified in the build configuration's top level build.properties file and it controls all source generation for that build.  See <a href="pde_source_generation.htm">Generating Source Features and Plug-ins</a> for details on generating traditional source plug-ins and features, the remainder of this page assumes familiarity with traditional source generation.</p>
-  
-<h3> generate.feature</h3>
-In a feature's build.properties file, the generate.feature property tells pde.build to generate a source feature.
-<pre style="text-align: center;">generate.feature@&lt;source feature id&gt; = &lt;feature id&gt; [, feature@&lt;feature id&gt;]* [, plugin@&lt;plugin id&gt;]* [, exclude@&lt;plugin id&gt;]*</pre>
-<p>When generating individual source bundles, this property remains as before and supports the same attributes (eg version, unpack, optional, etc), the difference will be noticed in the resulting source feature. Before, the source feature would have included 1 source plug-in + a source fragment for each platform being built. In the new format, the source feature will include a source bundle for each plug-in/fragment listed in the original feature.</p>
-<p>Plug-ins that were included in the source feature via the plugin@ syntax will not get corresponding source bundles. This is useful for adding doc plug-ins to the source feature.</p>
-<p>The <tt>exclude@</tt> entry is new for individual source generation.  Some plug-ins that were included in the originating feature (ie doc plug-ins or fragments that contain only native code) may not have source and should be excluded from the generated source feature. The <tt>exclude@</tt> entry supports a <tt>version</tt> attribute.</p> 
-Example:
-<pre style="text-align: center;">generate.feature@org.eclipse.jdt.source=org.eclipse.jdt, plugin@org.eclipse.jdt.doc.isv;unpack="false",exclude@org.eclipse.jdt.doc.user</pre>
-
-<h3>generate.plugin</h3>
-<p>In the old format, the generate.plugin property generates a source plug-in based on the contents of a given feature. When generating individual source bundles, this changes to be based on a given plug-in:</p>
-<pre style="text-align: center;">generate.plugin@&lt;source plug-in id&gt;=&lt;plug-in id&gt;</pre>
-<p>The generate.plugin property was used by features to include source without having a source feature (even though behind the scenes an entire source feature was generated). When generating individual source bundle, features will need to include a *.source bundle for each plug-in along with a corresponding generate.plugin property for each one.</p>
-<p><b>Example</b>: The sdk.examples feature used to look like this:</p>
-<pre>
-   	&lt;feature id="org.eclipse.sdk.examples"  ... &gt; 
-		....
-		&lt;plugin id="org.eclipse.sdk.examples.source"  version="0.0.0"/&gt;
-		&lt;plugin id="org.eclipse.sdk.examples.source.win32.win32.x86" version="0.0.0"/&gt;
-	&lt;/feature&gt;
-<br>	generate.plugin@org.eclipse.sdk.examples.source=org.eclipse.sdk.examples
-</pre>
-<p>This changes to:</p>
-<pre>
-	&lt;feature id="org.eclipse.sdk.examples" ...&gt;
-		...
-		&lt;plugin id="org.eclipse.compare.examples.source"  version="0.0.0"/&gt;
-		&lt;plugin id="org.eclipse.debug.examples.core.source" version="0.0.0"/&gt;
-		&lt;plugin id="org.eclipse.swt.examples.source" version="0.0.0"/&gt;
-	&lt;/feature&gt;
-<br>
-	generate.plugin@org.eclipse.compare.examples.source=org.eclipse.compare.examples
-	generate.plugin@org.eclipse.debug.examples.core.source=org.eclipse.debug.examples.core
-	generate.plugin@org.eclipse.swt.examples.source=org.eclipse.swt.examples
-</pre>
-
-<h3>generateSourceBundle</h3>
-<p>Specific plug-ins may not require source bundles because they don't actually contain source. This may occur with platform specific fragments that only contain a native library. In this case, the bundles may be excluded by the feature as outlined above in generate.feature.</p>
-<p>Or, bundles can explicitly specify in their own build.properties file that no source bundle should be generated for them:</p> 
-<pre style="text-align: center;">generateSourceBundle=false</pre>
-
-<h3>Custom Content</h3>
-<p>Custom content can always be added to generated source bundles using the <tt>post.gather.source</tt> custom callback in the originating bundle.  (See <a href="pde_custom_callbacks.htm">Feature and Plug-in custom build steps</a>).</p>
-<p>When doing this, set the property "src.additionalRoots" in the plugin's build.properties file so that the generate source bundle has the correct roots directive on the Eclipse-SourceBundle header.</p>
-<p>Example:</p>
-<pre>
-org.junit4 :
-   build.properties
-      src.includes = about.html,junitsrc.zip
-      src.additionalRoots=junitsrc
-      customBuildCallbacks=customBuildCallbacks.xml
-
-   customBuildCallbacks.xml
-    	&lt;target name="post.gather.sources" &gt;
-		&lt;mkdir dir="${target.folder}/junitsrc"/&gt;
-		&lt;unzip src="${target.folder}/junitsrc.zip" dest="${target.folder}/junitsrc" overwrite="false"/&gt;
-		&lt;delete file="${destination.temp.folder}/junitsrc.zip" /&gt;		
-	&lt;/target&gt;
-</pre>
-
-<h3>Branding the Source Feature</h3>
-<p>Previously, the generated source plug-in served as a branding plug-in for the generated source feature. Branding files (about.properties, eclipse32.gif, etc) were provided using the sourceTemplatePlugin directory in the original feature.</p>
-<p>When generating individual source bundles, the branding plug-in for the source feature will be the source bundle corresponding to the original branding plug-in. This means that branding files for the source feature's branding plug-in can be contributed using the <tt>src.includes</tt> property in the original branding plug-in.</p>
-<p>The <tt>sourceTemplatePlugin</tt> folder of the feature for which we are generating source also contributes files to the branding plug-in.</p>
-
-<h3>sourceTemplatePlugin vs sourceTemplateBundle</h3>
-<p>Previously, the contents of the <tt>sourceTemplatePlugin</tt> directory of the original feature was copied into the source plug-in. When generating individual source bundles, this remains true only for the branding source bundle (see above).</p>
-<p>For all the other source bundles, the contents of a <tt>sourceTemplateBundle</tt> directory will be copied over.</p>  
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_builds.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_builds.htm
deleted file mode 100644
index b33e8d2..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_builds.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Building p2 Repositories and Products</title>
-</head>
-<body>
-<h1>Building p2 Repositories and Products</h1>
-<p>PDE/Build has built in support for publishing p2 metadata using the new <a href="../../org.eclipse.platform.doc.isv/guide/p2_publisher.html">p2 Publisher</a>.  3.4-style <a href="pde_p2_integration.htm">integration</a> with the old metadata generator still works, but does not support newer features like the <a href="../../org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html">customization of metadata</a>.
-</p>
-<p>The new publisher integration gathers your features and bundles from source and publishes them directly to a p2 repository. To use the new functionality, the builder should define the property:</p>
-<div align="center"><tt><b>p2.gathering = true</b></tt></div>
-<br>
-<p>Setting this property will change the build in significant manner:</p>
-<ul>
-<li><a href="pde_p2_featurebuilds.htm">Feature builds</a> produce a single p2 repository that is a group of all the configurations being built.</li>
-<li><a href="pde_p2_productbuilds.htm">Product builds</a> produce a properly installed fully enabled p2 product.  (And optionally the corresponding repository.)</li>
-</ul>
-<p>See the separate feature and product build help pages for more detail on those types of builds.</p>
-
-
-<h2><a name="gathering_overview">Overview of the changes</a></h2>
-<h3>The build's local repository</h3>
-<p>During the build, all metadata and artifacts will be published into a build repository defined by the property <tt><b>p2.build.repo</b></tt>.  The default location for this repository is <tt>${buildDirectory}/buildRepo</tt>.</p>
-<p>Once all the metadata and artifacts are published into this repository, the final assemble and packaging scripts will mirror and/or install from this repository into the locations that will become the archives produced by the build.  This final
-mirroring and installation can be skipped using <tt><b>skipMirroring</b></tt> and <tt><b>skipDirector</b></tt> properties, in which case the build results would all just be in the build repository.</p>
-
-<h3>Generated build.xml : gathering vs publishing</h3>
-<p>In the generated build.xml for features and plugins there is a target <tt>gather.bin.parts</tt> which was responsible for gathering the contents of the feature/plug-in and copying them to a final directory to be jared (or not) and included in the build results.
-When using <tt>p2.gathering=true</tt>, we instead publish the feature/plug-in directly into a p2 repository.  That is, we are using p2 to gather the binary artifacts directly from the source (this is where the name of the property comes from).</p>
-<p>This is done using a new target named <tt>publish.bin.parts</tt> which uses a new <a href="pde_p2_buildtasks.htm">ant tasks</a> contributed by PDE/Build.  In old style builds, calling <tt>gather.bin.parts</tt> was done by delegating through the feature structure.  Calling <tt>publish.bin.parts</tt> is instead
-done directly from a new assemble p2 script that is generated.</p>
-<h3>Rootfiles contributed by features</h3>
-<p>Old style integrations grouped all the rootfiles contributed by all the features in the build into a single root file installable unit and artifact (which may have been named for a product). With the new publishing support, root files are instead 
-associated with the feature that contributed them.  See the <a href="pde_p2_featuremetadata.htm">feature metadata layout</a> page for more details.</p>
-<h3>The assemble scripts</h3>
-<p>Old style integration was done by calling the metadata generator on the binary results during the assembly and packaging process.  When using <tt>p2.gathering=true</tt> there is a new <tt>assemble.&lt;feature&gt;.p2.xml</tt> script.</p>  
-<p>This script will invoke the publish.bin.parts for all features and bundles being built.  It will also publish metadata for all pre-existing binary features and plug-ins, as well as publishing metadata for products.</p>
-<p>At the end of the p2 assemble script, before the remaining assemble and package scripts are called, we have a complete repository with the full results of the build.  The remaining assemble and package scripts are simply
-slicing up the repository and/or performing installs using the <a href="../../org.eclipse.platform.doc.isv/guide/p2_director.html">p2 director</a> to create the final archives which are the results of the build.</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_buildtasks.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_buildtasks.htm
deleted file mode 100644
index 141a53b..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_buildtasks.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>PDE Build Extensions to the p2 Publisher</title>
-</head>
-<body>
-<h1>PDE Build Extensions to the p2 Publisher</h1>
-<p>PDE Build contributes several ant tasks that extend the <a href="../../org.eclipse.platform.doc.isv/guide/p2_publisher.html">p2 publisher</a>.  These tasks allow PDE Build to publish metadata and artifacts directly into a p2 repository.</p>
-<p>The generated build scripts use these tasks in the context of a full build where things like compiling class files and replacing versions are done.  However, some of the 
-tasks may be usefull in special cases to publish metadata directly without running a full build. </p>
-
-<table cellspacing="1" cellpadding="2">
-	<tr><td><b><tt>eclipse.publish.featuresAndBundles</tt></b></td></tr>
-	<tr><td><p>This task is very similar to the <tt>p2.publish.featuresAndBundles</tt> task contributed by the p2 publisher. 
-	This task will publish metadata for pre-existing binary features and plug-ins which are not being built from source.  The task will also publish categories based on a provided site.xml or category.xml file.
-	</p></td></tr>
-	<tr><td><p>This task supports the following attributes:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>metadataRepository</tt></td><td>A URL specifying the metadata repository to publish to.</td></tr>
-			<tr><td><tt>artifactRepository</tt></td><td>A URL specifying the artifact repository to publish to.</td></tr>
-			<tr><td><tt>repository</tt></td><td>Sets both metadataRepository and artifactRepository.</td></tr>
-			<tr><td><tt>site</tt></td><td>A URL to a site.xml specifying category information.</td></tr>
-			<tr><td><tt>category</tt></td><td>A URL to a category.xml specifyiny category information.</td></tr>
-			<tr><td><tt>siteQualifier</tt></td><td>A qualifier used to ensure resulting category IUs have unique names.</td></tr>
-			<tr><td><tt>&lt;features&gt;</tt></td><td>A nested fileset element specifying the locations of binary features to publish.</td></tr>
-			<tr><td><tt>&lt;bundles&gt;</tt></td><td>A nested fileset element specifying the locations of binary plug-ins to publish.</td></tr>
-		</table>
-	</td></tr>
-</table>
-Example:
-<div  style="border:1px inset">
-<pre>
- &lt;eclipse.publish.featuresAndBundles repository="file:C:/build/repository" category="file:C:/build/category.xml" &gt;
-     &lt;features dir="C:\eclipse\features\" includes="org.eclipse.cvs_1.1.100.v20090514-7E79FEc9BJ99r9XGQ3CICF"	/&gt;
-     &lt;bundles dir="C:\eclipse\plugins" includes="org.eclipse.cvs_1.0.300.v20090520.jar"	/&gt;
-     &lt;bundles dir="C:\eclipse\plugins" includes="org.eclipse.team.cvs.core_3.3.200.I20090430-0408.jar"	/&gt;
-     &lt;bundles dir="C:\eclipse\plugins" includes="org.eclipse.team.cvs.ssh_3.2.100.I20090508-2000.jar"	/&gt;
-     &lt;bundles dir="C:\eclipse\plugins" includes="org.eclipse.team.cvs.ssh2_3.2.200.I20090508-2000.jar"	/&gt;
-     &lt;bundles dir="C:\eclipse\plugins" includes="org.eclipse.team.cvs.ui_3.3.200.I20090521-1750.jar"	/&gt;
- &lt;/eclipse.publish.featuresAndBundles&gt;
-</pre>
-</div>
-<br>
-<table cellspacing="1" cellpadding="2">
-	<tr><td><b><tt>eclipse.gatherBundle</tt></b></td></tr>
-	<tr><td><p>Publish a plug-in directly from source.  Once the .class files for a bundle are compiled, this task will gather up all the files that make up the binary result and publish them as a p2 artifact with metadata.  
-	This task is used in the <tt>publish.bin.parts</tt> task in the plug-in's generated build.xml, this task replaces the <tt>gather.bin.parts</tt> task when you are building with the p2 publisher.</p>
-	</td></tr>
-	<tr><td><p>This task supports the following attributes:</p>
-	<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-		<tr><td><tt>metadataRepository</tt></td><td>The metadata repository to publish to.</td></tr>
-		<tr><td><tt>artifactRepository</tt></td><td>The artifact repository to publish to.</td></tr>
-		<tr><td><tt>buildResultFolder</tt></td><td>Folder containing built .class files, the Manifest and potentially .api_description files.</td></tr>
-		<tr><td><tt>targetFolder</tt></td><td>Content when running with customBuildCallbacks.</td></tr>
-		<tr><td><tt>baseDirectory</tt></td><td>Project location to gather content from when not using customBuildCallbacks</td></tr>
-		<tr><td><tt>unpack</tt></td><td>Whether or not the plug-in should be unpacked into folder form when installed.</td></tr>
-		<tr><td><tt>gatheredSource</tt></td><td>For source bundles, the location of the gather source.</td></tr>
-		<tr><td><tt>&lt;outputFolder&gt;</tt></td><td>Nested elements specifying alternate locations to get .class files from, used when reusing .class files from the workspace.  
-													  This is an ant FileSet with an additional "<tt>library</tt>" attribute specifying which library the class files belong to</td></tr>
-	</table>
-	</td></tr>
-</table>
-Example:
-<div style="border:1px inset">
-<pre>
- &lt;eclipse.gatherBundle metadataRepository="file:/build/repo" artifactRepository="file:/build/repo"
-                       buildResultFolder="${basedir}" baseDirectory="${basedir}" unpack="true" &gt;
-     &lt;outputFolder library="lib/pdebuild-ant.jar" dir="${basedir}" includes="bin_ant/**" /&gt;
-     &lt;outputFolder library="pdebuild.jar" dir="${basedir}" includes="bin/**" /&gt;
- &lt;/eclipse.gatherBundle&gt;
-</pre>
-</div>
-<br>			
-<table cellspacing="1" cellpadding="2">
-	<tr><td><b><tt>eclipse.gatherFeature</tt></b></td></tr>
-	<tr><td><p>Publish a feature directly from source.  This task will gather up all the files that make up the feature jar and publish them as a p2 artifact with metadata.  
-	This task will also publish artifacts containing any <a href="pde_rootfiles.htm">root files</a> that are contributed by this feature.
-	If the feature does not specify a <tt>bin.includes</tt> property, then the feature jar will not be generated, but there will still be root file artifacts and feature group metadata.
-	</p>
-	</td></tr>
-	<tr><td><p>This task supports the following attributes:</p>
-	<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-		<tr><td><tt>metadataRepository</tt></td><td>The metadata repository to publish to.</td></tr>
-		<tr><td><tt>artifactRepository</tt></td><td>The artifact repository to publish to.</td></tr>
-		<tr><td><tt>buildResultFolder</tt></td><td>Folder containing a modified feature.xml with versions replaced.</td></tr>
-		<tr><td><tt>targetFolder</tt></td><td>Content when running with customBuildCallbacks.</td></tr>
-		<tr><td><tt>baseDirectory</tt></td><td>The feature project location</td></tr>
-	</table>
-	</td></tr>
-</table>
-Example:
-<div style="border:1px inset">
-<pre> &lt;eclipse.gatherFeature
-     metadataRepository="file:/build/repo"
-     artifactRepository="file:/build/repo"
-     buildResultFolder="${basedir}"
-     baseDirectory="${basedir}"
- /&gt;
-</pre>
-</div>
-<br>			
-<table cellspacing="1" cellpadding="2">
-	<tr><td><b><a name="brand_p2_artifacts"><tt>eclipse.brand.p2.artifacts</tt></a></b></td></tr>
-	<tr><td><p>Brand launcher artifacts for a product and republish them with a new name for inclusion in the given product.</p></td></tr>
-	<tr><td><p>This task supports the following attributes:</p>
-	<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-		<tr><td><tt>metadataRepository</tt></td><td>The metadata repository to publish to.</td></tr>
-		<tr><td><tt>artifactRepository</tt></td><td>The artifact repository to publish to.</td></tr>
-		<tr><td><tt>config</tt></td><td>The configuration for which the launchers will be used. (eg "gtk.linux.x86")</td></tr>
-		<tr><td><tt>iconsList</tt></td><td>Locations to find the icons to brand the executable with.</td></tr>
-		<tr><td><tt>tempDirectory</tt></td><td>The location of a temporary directory that can be be used.</td></tr>
-		<tr><td><tt>productId</tt></td><td>The id of the product we are publishing for.</td></tr>
-		<tr><td><tt>productVersion</tt></td><td>The version of the product we are publishing for.</td></tr>
-		<tr><td><tt>launcherName</tt></td><td>The name to give the new launcher.</td></tr>
-		<tr><td><tt>launcherProvider</tt></td><td>The name of the IU which is providing the original launcher artifacts.  By default this is "org.eclipse.equinox.executable",  
-		the task will be looking for artifacts named <tt>&lt;launcherProvider&gt;_root.&lt;config&gt;</tt></td></tr>
-	</table>
-	</td></tr>
-</table>			
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm
deleted file mode 100644
index 6178a9a..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Configuring p2 Products</title>
-</head>
-<body>
-<h1>Configuring p2 Products</h1>
-<p>By default, PDE/Build will automatically generate start levels and other configuration information for you.  It does this by generating properties into the <a href="../../org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html">p2.inf</a> file.
-If your product provides its own p2.inf file, then PDE/Build will append to a copy of that file.  It is possible to suppress this behaviour by defining some properties in your p2.inf:</p>
-<table border="5" cellspacing="0" cellpadding="2" align="center">
-	<tr><td><tt>org.eclipse.pde.build.append</tt></td><td>Set to <b><tt>false</tt></b> to disable appending any defaults to the p2.inf file.</td></tr>
-	<tr><td><tt>org.eclipse.pde.build.append.startlevels</tt></td><td>Set to <b><tt>false</tt></b> to disable appending start level information to the p2.inf file.</td></tr>
-	<tr><td><tt>org.eclipse.pde.build.append.launchers</tt></td><td>Set to <b><tt>false</tt></b> to disable including launchers in the p2.inf file.</td></tr>
-</table>
-
-<h3>Start Levels</h3>
-<p>Start level information can be set manually on the configuration tab of the product editor.  <b>If any start level information is set in the .product file, then PDE/Build will not generate any defaults.</b>
-This means that if you decide to set any custom start levels, then you must set start levels for all bundles that will require them.  The default start levels generated by PDE/Build for p2 products are:</p>
-<table border="5" cellspacing="0" cellpadding="2" align="center">
-<tr><td align="center">Bundle</td><td>Start Level</td><td align="center">Auto-Start</td></tr>
-<tr><td>org.eclipse.equinox.simpleconfigurator</td><td align="center">1</td><td align="center">true</td></tr>
-<tr><td>org.eclipse.equinox.common</td><td align="center">2</td><td align="center">true</td></tr>
-<tr><td>org.eclipse.update.configurator</td><td align="center">4 (default)</td><td align="center">true</td></tr>
-<tr><td>org.eclipse.core.runtime</td><td align="center">4 (default)</td><td align="center">true</td></tr>
-<tr><td>org.eclipse.equinox.ds</td><td align="center">1</td><td align="center">true</td></tr>
-</table>
-<p>When setting the start level for org.eclipse.update.configurator, PDE/Build will also automatically set In addition to these properties, <b><tt>org.eclipse.update.reconcile=false</tt></b>.</p>
-<h3>Config.ini properties</h3>
-<p>The <a href="../../org.eclipse.platform.doc.isv/guide/p2_publisher.html">p2 product publisher</a> used by PDE/Build will automatically set a number of config.ini properties based on settings in your .product file:</p>
-<table border="5" cellspacing="0" cellpadding="2" align="center">
-	<tr><td>Property</td><td>Based On</td></tr>
-	<tr><td><tt>eclipse.product</tt></td><td>The product set on the overview tab of the product editor.</td></tr>
-	<tr><td><tt>eclipse.application</tt></td><td>The application set on the overview tab of the product editor.</td></tr>
-	<tr><td><tt>osgi.splashPath</tt></td><td>The plug-in set on the Splash tab of the product editor.</td></tr>
-</table>
-<p>It is also possibly to add arbitrary config.ini properties to your .product file, however there is no tab the editor for this, so it must be done manually by editing the .product file as xml.</p>
-<p>An example of setting properties this way would look like this:</p>
-<pre>
-	...
-	&lt;configurations&gt;
-	   <i>&lt;-- The product editor will generate start level information like this:
-	   &lt;plugin id="org.eclipse.core.runtime" autoStart="true" startLevel="4" /&gt;
-	   --&gt;</i>                                     
-	   &lt;property name="osgi.bundles.defaultStartLevel" value="4" /&gt;   
-	   &lt;property name="osgi.requiredJavaVersion" value="1.5.0"/&gt;    
-	&lt;/configurations&gt;
-	...
-</pre>
-<h3>Launchers</h3>
-<p>PDE/Build will automatically <a href="pde_p2_buildtasks.htm#brand_p2_artifacts">brand launchers</a> (which it gets from the org.eclipse.equinox.executable feature in the delta pack).  These launchers will be automatically included in the
-product along with generated metadata that will set the appropriate <a href="../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html"><i>-startup</i> and <i>--launcher.library</i></a> arguments in the product ini file.</p>
-<p>Because of changes to the structure of <a href="pde_p2_featuremetadata.htm">feature metadata</a> with respect to root files, the org.eclipse.equinox.executable feature should not be included directly in your product.</p> 
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featurebuilds.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featurebuilds.htm
deleted file mode 100644
index a7ee4f2..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featurebuilds.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Feature Builds with p2</title>
-</head>
-<body>
-<h1>Feature Builds with p2</h1>
-<p>Defining the new property:</p>
-<div align="center"><tt><b>p2.gathering = true</b></tt></div>
-<p>will cause a <a href="pde_p2_builds.htm#gathering_overview">few changes</a> for feature builds.  See also the page for <a href="pde_p2_featuremetadata.htm">feature metadata layout</a>.</p>
-<p>In particular, instead of producing per-platform archives, the build will produce a single p2 repository which is a group of all the platforms.  Effectively this is forcing an implicit <tt><b>groupConfigurations=true</b></tt>.</p>
-<p>The following is a list of related properties (old and new):</p>
-<table border="5" cellspacing="0" cellpadding="2">
-	<tr><td><tt><b>p2.gathering</b></tt></td><td>Set to <tt><b>true</b></tt> to turn on p2 publisher based builds.</td></tr>
-	<tr><td><tt>p2.build.repo</tt></td><td>The local build time p2 repository, default is <tt>${buildDirectory}/buildRepo</tt>.  Results will be mirrored from here to the final archive location.</td></tr>
-	<tr><td><tt>groupConfigurations</tt></td><td><tt>p2.gathering=true</tt> has the implicit effect of setting <tt>groupConfigurations=true</tt>.  To control the <a href="pde_controlling_output.htm">output format</a> of the archive use the <tt>group.group.group</tt> configuration.</td></tr>
-	<tr><td><tt>generate.p2.metadata</tt></td><td>This is property for the old <a href="pde_p2_integration.htm">metadata generator integration</a>.  It has no affect when <tt>p2.gathering=true</tt>.</td></tr>
-	<tr><td><tt>p2.metadata.repo<br>p2.artifact.repo</tt></td>
-		<td>These properties were associated with <tt>generate.p2.metadata</tt> and have no affect on feature builds when <tt>p2.gathering=true</tt> because the default behaviour in this case is to create a p2 repository.  (However, these properties do affect <a href="pde_p2_productbuilds.htm">product builds</a>).</td>
-	</tr>
-	<tr><td><tt>p2.metadata.repo.name<br>p2.artifact.repo.name</tt></td><td>Optional, these properties will be used to name the final feature repository.</td></tr>
-	<tr><td><tt>p2.compress</tt></td><td>Set to <tt>true</tt> to compress the final feature repository xml into a jar.</td></tr>
-	<tr><td><tt>p2.flavor</tt></td><td>No affect for feature builds, but does affect <a href="pde_p2_productbuilds.htm">product builds</a>.</td></tr>
-	<tr><td><tt>p2.publish.artifacts</tt></td><td>No affect when <tt>p2.gathering=true</tt> (Old property)</td></tr>
-	<tr><td><tt>p2.root.name<br>p2.root.version</tt></td><td>No affect when <tt>p2.gathering=true</tt> (Old property)</td></tr>
-	<tr><td><tt>p2.context.repos</tt></td><td>Define context repositories.  See <a href="pde_p2_reusingmetadata.htm">reusing metadata</a>.</td></tr>
-	<tr><td><tt>repoBaseLocation</tt></td><td>A folder containing repositories to transform using <tt><a href="../../org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm#p2_repo2runnable">&lt;p2.repo2runnable&gt;</a></tt>.  See also <a href="pde_p2_reusingmetadata.htm">reusing metadata</a>.</td></tr>
-	<tr><td><tt>transformedRepoLocation</tt></td><td>The folder containing the output of <tt><a href="../../org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm#p2_repo2runnable">&lt;p2.repo2runnable&gt;</a></tt>.  See also <a href="pde_p2_reusingmetadata.htm">reusing metadata</a>.</td></tr>
-	<tr><td><tt>p2.category.site</tt></td><td>A URL to a site.xml file used to define categories.</td></tr>
-	<tr><td><tt>p2.category.definition</tt></td><td>A URL to a category.xml file used to define categories.</td></tr>
-	<tr><td><tt>p2.category.prefix</tt></td><td>Define a prefix to ensure unique ids for category IUs generated from site/category files that don't use unique names.</td></tr>
-	<tr><td><tt>skipMirroring</tt></td><td>Skip the mirroring step, no final archive is created.  Build results are found in <tt>${p2.build.repo}</tt>.</td></tr>
-</table>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featuremetadata.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featuremetadata.htm
deleted file mode 100644
index 4e9b1b4..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_featuremetadata.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Layout of Feature Metadata</title>
-</head>
-<body>
-<h1>Layout of Feature Metadata</h1>
-<p>PDE Build has always used features as a kind of grouping mechanism specifying what exactly should be built.  With p2, this idea of a feature as a group has been extended, resulting a more than a single installable unit (IU) being generated per feature.</p>
-From build's perspective, a feature contributes three things:
-<ul>
-<li>A grouping of nested features and plug-ins.</li>
-<li>The (optional) feature jar itself that contains the feature.xml, license files, etc.</li>
-<li>A mechanism to <a href="pde_rootfiles.htm">contribute root files</a> to the install.</li>
-</ul>
-
-<p>When using the <a href="pde_p2_integration.htm">metadata generator</a> introduced in 3.4, we end up with the following structure for feature "<tt>org.example.platform</tt>":</p>
-	<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-		<tr>
-			<td width="320"><tt>org.example.platform.feature.group</tt></td>
-			<td>This is the top level grouping IU for the feature, it will have requirements on all the features and plug-ins that were included and required by the feature.xml.  It also includes a requirement on the 
-			nested <tt>org.example.platform.feature.jar</tt></td>
-		</tr>
-		<tr><th colspan="2">
-		<table  border="1" cellspacing="0" align="right" style="width:98%">
-		<tr><td width="300"><tt>org.example.platform.feature.jar</tt></td>
-			<td>This is the IU representing the feature jar itself.  It has an LDAP filter <div align="center">"<tt>(org.eclipse.update.install.features=true)</tt>"</div>which causes the feature jar to only be installed if the profile defines that property.
-				This IU also has a requirement on the actual <tt>org.example.platform_1.0.0.jar</tt> artifact.
-				<p>If the feature does not define "<tt>bin.includes</tt>" in its build.properties file, then this feature jar IU will not be generated.</p></td></tr>
-		</table>
-		</th></tr>
-	</table>
-	
-<p>Notice this IU structure does not include anything for the root files contributed by the feature.  Instead a build using the metadata generation placed all rootfiles together into a single IU and artifact.</p>
-<p>New in 3.5 is the <a href="pde_p2_builds.htm">p2 publisher</a>.  If we use PDE Build's <a href="pde_p2_buildtasks.htm"><tt>eclipse.gatherFeature</tt></a> task to publish the feature from source, we instead get root file IUs corresponding to the feature that contributed them.  In this case, we end up with metadata as follows:</p>
-<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-		<tr>
-			<td width="370"><tt>org.example.platform.feature.group</tt></td><td>The top level grouping IU for the feature</td>
-		</tr>
-		<tr><th colspan="2">
-		<table  border="1" cellspacing="0" align="right" style="width:98%">
-		<tr><td width="350"><tt>org.example.platform.feature.jar</tt></td><td>The feature jar IU.</td></tr>
-		<tr><td><tt>org.example.platform_root</tt><br>
-		       <tt>org.example.platform_root.&lt;ws&gt;.&lt;os&gt;.&lt;arch&gt;</tt></td>
-		    <td>These are the root file IUs.  The feature.group will include a root IU per platform for which the feature contributes files.  The root IU itself has a requirement on the actual binary artifact from a p2 artifact repository (eg <tt>binary/org.example.platform_root.gtk.linux.x86_1.0.0</tt>) that contains the files.</td></tr>
-		</table>
-		</th></tr>
-	</table>
-
-<p>The use of the new p2 publisher instead of the old metadata generator allows for much finer grain control over how root files are delivered for products.</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_integration.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_integration.htm
deleted file mode 100644
index d93156b..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_integration.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>PDE Build Integration with p2</title>
-</head>
-<body>
-<h1>PDE Build Integration with p2</h1>
-<p>See the <a href="../../org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html">Generating p2 metadata</a> page in the Platform Plugin-in Developer Guide for details on p2 metadata generation.  Generating metadata by itself it not sufficient to create a p2-enabled product.  To do this you must perform an actual p2 install from the generated metadata.  See the <a href="../../org.eclipse.platform.doc.isv/guide/p2_director.html">p2 director</a> documentation for details on how to perform this install from a headless script.</p>
-<p>It is possible to generate p2 metadata with manual calls to the p2 metadata generator in any of PDE/Build's custom tasks (see <a href="pde_customization.htm">Customizing a Headless Build</a>).
-However, PDE/Build does provide integration with p2 via the following properties:</p>
-
-	<table border="5" cellspacing="0" cellpadding="1">
-		<tr>
-			<td><pre>generate.p2.metadata</pre></td>
-			<td>Set to true to turn on p2 metadata generation.  The ant scripts are based on the existence of this property and not the value.  To turn off metadata generation, the property must be removed and not just set to false.<br>
-			In the build scripts, calls to p2 targets are generated when the p2 bundle <tt>org.eclipse.equinox.p2.metadata.generator</tt> and its dependencies are present in the Eclipse that is running the build.
-			These p2 targets are conditional on the <tt>generate.p2.metadata</tt> property.
-			</td>
-		</tr>
-		<tr>
-			<td><pre>p2.metadata.repo<br>p2.artifact.repo</pre></td>
-			<td>Specify a <b>file:</b> URL giving the location of the p2 metadata and artifact repositories to publish to.  It is common, but not necessary for the artifact repository to use the same location as the metadata repository.<br>
-			Example:<br>
-			<pre>
-			p2.metadata.repo=file:${buildDirectory}/repository
-			p2.artifact.repo=file:${buildDirectory}/repository
-			</pre>
-			</td>
-		</tr>
-		<tr>
-			<td><pre>p2.metadata.repo.name<br>p2.artifact.repo.name</pre></td>
-			<td>Optional. Specify a names for the generator p2 repositories.<br>When using a repository that already exists, the existing name of the repository will not be changed.  
-			If not specified, p2 will name the repositories according to their location.
-			</td>
-		</tr>
-		<tr>
-			<td><pre>p2.flavor</pre></td>
-			<td>Set the flavor for the p2 metadata.  When metadata is generated for the Eclipse SDK, a flavor of "tooling" is used. </td>
-		</tr>
-		<tr>
-			<td><pre>p2.publish.artifacts</pre></td>
-			<td>Set to true to publish jars into the artifact repository.  If set to false, then artifact metadata is generated but the jars are not copied to the artifact repository.  WARNING: when set to true, make sure that the p2.artifact.repo is not the same location as the assembly directories used by PDE/Build, otherwise jars might end up deleted!</td>
-		</tr>
-		<tr>
-			<td><pre>p2.root.name<br>p2.root.version</pre></td>
-			<td>Specify the name and version for the root IU that will contain everything that was built.<br>
-			If a <b>.product</b> file is specified in the build, then these properties will be <b>ignored</b>.  Instead, when a .product file is available the root name and version will be the product id and version from the .product file.  See below for more information.
-			</td>
-		</tr>
-	</table>
-	
-<h2>Metadata Generation for Products</h2>
-<p>When running a build with a product file set in the top level build configuration build.properties file (both in builds using the productBuild.xml and the normal build.xml), then PDE/Build will automatically generate metadata for that product.</p>
-<p>In addition to creating Installable Units for all the features and bundles, this will also create the following product Installable Units:</p>
-<ul>
-<li>A top level Product IU using the product-id and the product version.  If no version is set in the .product file, "1.0.0" is used.</li>
-<li>Configuration Units that set start level information for individual bundles as specified in the config.ini used for the product.</li>
-<li>Configuration Units that set program and vm arguments for the product's launcher .ini file.</li>
-<li>Configuration Units that add entries to the config.ini based on the config.ini used for the product.</li>
-<li>Installable Units to deliver the branded launcher as well as any root files.</li>
-<li>Configuration Units that set arguments in the launcher .ini file specifying <tt>-startup</tt> and <tt>--launcher.library</tt> to enable installing the product with a bundle pool.</li>
-</ul>
-<p>With all of these generated Installable Units, it is possible to use p2 to install the complete product out of the repository.</p>
-
-<h2>The Details</h2>
-<p>PDE/Build is essentially calling the metadata generation task provided by p2 at certain points during the build.  It is likely that during a build there is never a single point in time where all build artifacts exist on disk at the same place.  Therefore, it would be necessary to either call the p2 metadata generater on the final archives or, as an optimization, call it multiple times throughout the build.</p>
-<p>Metadata generation will occur throughout the assemble and packaging phases.  This is true for both normal builds and <a href="pde_packager.htm">packager</a> builds.  To illustrate, for a product build using productBuild.xml, the following scripts will be generated (assuming <tt>configs=win32,win32,x86 &amp; linux,gtk,ppc</tt>):</p>
-<ul>
-<li>assemble.org.eclipse.pde.build.container.feature.all.xml</li>
-<li>assemble.org.eclipse.pde.build.container.feature.win32.win32.x86.xml</li>
-<li>assemble.org.eclipse.pde.build.container.feature.linux.gtk.ppc.xml</li>
-<li>package.org.eclipse.pde.build.container.feature.all.xml</li>
-<li>package.org.eclipse.pde.build.container.feature.win32.win32.x86.xml</li>
-<li>package.org.eclipse.pde.build.container.feature.linux.gtk.ppc.xml</li>
-</ul>
-<p>Assemble scripts collect features and plug-ins that were built along with associated root files.  Package scripts collect pre built binary features and plug-ins.  The platform specific scripts collect the pieces for those particular configurations and the "all" scripts delegate to each of the platform specific scripts.</p>
-<p>p2 generation calls will occur as follows:</p>
-<ol>
-<li>assemble win32.win32.x86 : Generate metadata for collected features and plug-ins for windows.</li>
-<li>assemble win32.win32.x86 : Second call to generated metadata for collected root files for windows.</li>
-<li>assemble linux.gtk.ppc : Generate metadata for collected features and plug-ins for linux.</li>
-<li>assemble linux.gtk.ppc : Second call to generated metadata for collected root files for linux.</li>
-<li>assemble all : If not running the packager: Generate metadata for a root installable unit that includes everything above.</li>
-<li>package win32.win32.x86 : Generate metadata for packaged features and plug-ins for windows.</li>
-<li>package win32.win32.x86 : Second call to generated metadata on rootfiles from packaging windows.</li>
-<li>package linux.gtk.ppc : Generate metadata for packaged features and plug-ins for linux.</li>
-<li>package linux.gtk.ppc : Second call to generated metadata on rootfiles from packaging for linux.</li>
-<li>package all : Generate metadata for a root installable unit that includes everything above.</li>
-</ol>
-<p>The p2 metadata generator task supports incremental generation, each call to the p2 metadata generated is done with <tt>mode=incremental</tt>, the final call to generate the root installable unit will run with <tt>mode="final"</tt></p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_productbuilds.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_productbuilds.htm
deleted file mode 100644
index 842081b..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_productbuilds.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Product Builds with p2</title>
-</head>
-<body>
-<h1>Product Builds with p2</h1>
-<p>Defining the new property:</p>
-<div align="center"><tt><b>p2.gathering = true</b></tt></div>
-<p>will cause a <a href="pde_p2_builds.htm#gathering_overview">few changes</a> for product builds.  In particular, the build will produce properly installed fully p2 enabled products.</p>
-<p>The following is a list of related properties (old and new):</p>
-<table border="5" cellspacing="0" cellpadding="2">
-	<tr><td><tt><b>p2.gathering</b></tt></td><td>Set to <tt><b>true</b></tt> to turn on p2 publisher based builds.</td></tr>
-	<tr><td><tt>p2.build.repo</tt></td><td>The local build time p2 repository, default is <tt>${buildDirectory}/buildRepo</tt>.  Results will be mirrored from here to the final archive location.</td></tr>
-	<tr><td><tt>generate.p2.metadata</tt></td><td>This is property for the old <a href="pde_p2_integration.htm">metadata generator integration</a>.  It has no affect when <tt>p2.gathering=true</tt>.</td></tr>
-	<tr><td><tt>p2.metadata.repo<br>p2.artifact.repo</tt></td>
-		<td>By default for product builds, the final archives are the installed products and metadata and artifacts are left in the <tt>${p2.build.repo}</tt>.  If <tt>p2.metadata.repo</tt> and <tt>p2.artifact.repo</tt> are defined, then 
-		the artifacts and metadata for the product will be mirrored from the build repository.</td>
-	</tr>
-	<tr><td><tt>p2.metadata.repo.name<br>p2.artifact.repo.name</tt></td><td>Optional, these properties will be used to name the final repository when <tt>p2.metadata.repo</tt> and <tt>p2.artifact.repo</tt> are used.</td></tr>
-	<tr><td><tt>p2.compress</tt></td><td>Set to <tt>true</tt> to compress the final repository xml into a jar.</td></tr>
-	<tr><td><tt>p2.flavor</tt></td><td>The flavor of the product, used as a qualifier on the configuration metadata for the product.  See <a href="#product_flavors">below</a>.</td></tr>
-	<tr><td><tt>p2.product.qualifier</tt></td><td>The qualifier to use when replacing "1.0.0.<i>qualifier</i>" in a product's version.  If not set, the qualifier will be based on <tt>forceContextQualifier</tt> or the timestamp.</td></tr>
-	<tr><td><tt>p2.publish.artifacts</tt></td><td>No affect when <tt>p2.gathering=true</tt> (Old property)</td></tr>
-	<tr><td><tt>p2.root.name<br>p2.root.version</tt></td><td>No affect when <tt>p2.gathering=true</tt> (Old property)</td></tr>
-	<tr><td><tt>p2.context.repos</tt></td><td>Define context repositories.  See <a href="pde_p2_reusingmetadata.htm">reusing metadata</a>.</td></tr>
-	<tr><td><tt>repoBaseLocation</tt></td><td>A folder containing repositories to transform using <tt><a href="../../org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm#p2_repo2runnable">&lt;p2.repo2runnable&gt;</a></tt>.  See also <a href="pde_p2_reusingmetadata.htm">reusing metadata</a>.</td></tr>
-	<tr><td><tt>transformedRepoLocation</tt></td><td>The folder containing the output of <tt><a href="../../org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm#p2_repo2runnable">&lt;p2.repo2runnable&gt;</a></tt>.  See also <a href="pde_p2_reusingmetadata.htm">reusing metadata</a>.</td></tr>	
-	<tr><td><tt>p2.category.site</tt></td><td>A URL to a site.xml file used to define categories.</td></tr>
-	<tr><td><tt>p2.category.definition</tt></td><td>A URL to a category.xml file used to define categories.</td></tr>
-	<tr><td><tt>p2.category.prefix</tt></td><td>Define a prefix to ensure unique ids for category IUs generated from site/category files that don't use unique names.</td></tr>
-	<tr><td><tt>skipMirroring</tt></td><td>Skip the final mirroring from <tt>${p2.build.repo}</tt> to <tt>${p2.metadata.repo}</tt>.</td></tr>
-	<tr><td><tt>skipDirector</tt></td><td>Skip the call to the director.  No installed products will be produced.  If <tt>p2.metadata.repo</tt> and <tt>p2.artifact.repo</tt> are defined, those repositories will contain the product metadata and artifacts, otherwise <tt>${p2.build.repo}</tt> will contain the results.</td></tr>
-	<tr><td><tt>p2.director.log</tt></td><td>Location of a log file to log the results of the director call.</td></tr>
-	<tr><td><tt>p2.director.profile</tt></td><td>The name to use for the p2 profile created by the director.  Generally it is a good idea to name this something related to your product. Default is "profile".</td></tr>
-	<tr><td><tt>p2.director.extraArgs</tt></td><td>Extra arguments to pass to the directory.  Default is "<tt>-profileProperties org.eclipse.update.install.features=true</tt>".</td></tr>
-</table>
-
-
-<h3><a name="product_flavors">Product Flavor</a></h3>
-<p>As part of a product build, PDE/Build automatically generates default configuration metadata to set start levels and config.ini property.  This metadata is commonly referred to as Configuration Units (CUs).  In particular, start levels are set
-using CU fragments on the IU for the bundle being started.  The flavor is used as a qualifier when generating the CU's name based on the IU.</p>
-<p>For example, with "<tt>p2.flavor = tooling</tt>", <tt>'<b>tooling</b><i>win32.win32.x86</i>org.eclipse.core.runtime'</tt> will be the name of the CU that configures the org.eclipse.core.runtime bundle on windows.
-It may be a good idea to use a flavor based on your product id to avoid conflicts with other metadata, particularly if your product has particular needs with respect to start levels.
-</p>
-<p>See also the <a href="pde_p2_configuringproducts.htm">configuring products</a> page.</p>
-<h3>The director call</h3>
-PDE/Build includes a <tt>runDirector</tt> target that is called to perform installs during a product build.  Currently, this is a fork of the <a href="../../org.eclipse.platform.doc.isv/guide/p2_director.html">director application</a> in a new process.
-In more advanced releng scenarios, it is possible to reuse this task to perform additional installs.  The task requires that the location of the equinox launcher for the builder is defined.  An example call would look something like this:
-<pre>
-	&lt;property name="equinoxLauncherJar" value="/builder/eclipse/plugins/org.eclipse.equinox.launcher_1.0.200.v20090520.jar"/&gt;
-	&lt;ant antfile="${eclipse.pdebuild.scripts}/genericTargets.xml" target="runDirector" inheritAll="true"&gt;
-		&lt;property name="ws" value="gtk"/&gt;
-		&lt;property name="os" value="linux"/&gt;
-		&lt;property name="arch" value="x86"/&gt;
-		&lt;property name="p2.director.installPath" value="${installFolder}"/&gt;
-		&lt;property name="p2.repo" value="${p2.build.repo}"/&gt;
-		&lt;property name="p2.director.iu" value="my.rcp.product"/&gt;
-		&lt;property name="p2.director.version" value="1.0.0"/&gt;
-	&lt;/ant&gt;
-</pre> 
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_reusingmetadata.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_reusingmetadata.htm
deleted file mode 100644
index 645077b..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_reusingmetadata.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Reusing Metadata</title>
-</head>
-<body>
-<h1>Reusing p2 Metadata</h1>
-<p>Metadata for a given feature or bundle can be different depending on how it was generated.  Particularily when <a href="../../org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html">customizing metadata</a>, or when features contribute <a href="pde_p2_featuremetadata.htm">root files</a>. </p>
-<p>Because of this, it is always a good idea to reuse metadata when possible instead of regenerating it based on binary features and bundles that you may not own.</p>
-
-<h3>The repo2runnable task</h3>
-<p>There is an Ant task <a href="../../org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm#p2_repo2runnable"><tt>&lt;p2.repo2runnable&gt;</tt></a> which will transform feature and bundle artifacts into their installed form.  Generally speaking, this is the shape we need the plug-ins to be in if we want
-to be able to compile against them.  This task allows us to easily reconsume repositories from other projects in our own build.  PDE/Build has built-in integration with this task through the following properties:</p>
-<table border="5" cellspacing="0" cellpadding="2">
-	<tr><td><tt>repoBaseLocation</tt></td><td>A folder containing repositories to transform.  This folder can contain zipped repositories as well as sub-folders which are repositories.</td></tr>
-	<tr><td><tt>transformedRepoLocation</tt></td><td>The folder where the tranformed artifacts will be placed.  This folder will then become a p2 repository itself.</td></tr>
-</table>
-<br>
-New in 3.5 are <a href="pde_customization.htm#custom_targets">custom targets</a> <tt>preProcessRepos</tt> and <tt>postProcessRepos</tt> which occur before and after PDE/Build's call to <tt>&lt;p2.repo2runnable&gt;</tt>.  This allows for automatically mirroring or download zipped repositories:
-<pre>
-<b>build.properties:</b>
-	repoBaseLocation=${buildDirectory}/inputRepositories
-	transformedRepoLocation=${buildDirectory}/transformedRepo
-	
-<b>customTargets.xml:</b>
-&lt;target name="preProcessRepos"&gt;
-   &lt;p2.mirror source="http://download.eclipse.org/releases/galileo" destination="file:${repoBaseLocation}/mirrored"&gt;
-      &lt;iu id="org.eclipse.equinox.p2.user.ui.feature.group" /&gt;
-      &lt;iu id="org.eclipse.cdt.feature.group"/&gt;
-   &lt;/p2.mirror&gt;
-   &lt;property name="RCP.Repo-3.5RC3" value="http://download.eclipse.org/eclipse/downloads/drops/S-3.5RC3-200905282000/org.eclipse.rcp-p2repo-3.5RC3.zip" /&gt;
-   &lt;property name="Equinox.Repo-3.5RC3" value="http://download.eclipse.org/equinox/drops/S-3.5RC3-200905282000/equinox-SDK-3.5RC3.zip" /&gt;
-   &lt;get src="${RCP.Repo-3.5RC3" dest="${repoBaseLocation}/org.eclipse.rcp-p2repo-3.5RC3.zip" /&gt;
-   &lt;get src="${Equinox.Repo-3.5RC3" dest=""${repoBaseLocation}/eclipse-equinox-3.5RC3.zip" /&gt;
-&lt;/target&gt;
-</pre>
-<i>(At the time of of this writing, the location of the 3.5 final zips was not yet known, the URLs here serve as an example only and may not exist at any later date.)</i>
-<p>PDE/Build will first call the <tt>preProcessRepos</tt> custom target, then it will call the repo2runnable ant task to transform those downloaded repositories into a form that can be reused by the build.</p>
-<p>The <tt>transformedRepoLocation</tt> property which defines the location for the output of this transformation also serves as a <b>context repository</b>.</p>
-
-<h3>Context repositories</h3>
-<p>The property <tt><b>p2.context.repos</b></tt> is a comma separated list of repositories that serve as <i>context</i> to the build.</p>
-<p>When generating metadata, build will first consult the context repositories to see if there is already existing metadata for the feature or plug-in.  
-If metadata already exists, then it will be copied into the build local repository (<tt>${p2.build.repo}</tt>) instead of new metadata being generated.
-</p>
-<p>As well, if features, bundles, or products have <a href="../../org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html">customized</a> their metadata to depend on something that wasn't included in the build, then PDE/Build will
-perform a <a href="../../org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm#p2_mirror">mirror</a> out of the context repositories.  This mirror operation will include any IUs that were added to feature or plug-in metadata.</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_packager.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_packager.htm
deleted file mode 100644
index b4994e6..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_packager.htm
+++ /dev/null

@@ -1,316 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Repackaging Eclipse Components</title>
-</head>
-<body>
-<h1>Packaging Eclipse Components<br>
-</h1>
-<p>Eclipse components are delivered as archive files. Each archive
-contains a collection of features and plug-ins. Typically the archives
-contain all the functions that a particular component has to offer. It
-is
-often the case that consumers either need more than one component
-and/or only need parts of some components. Without assistance,
-consumers would have to manually fetch the archives containing the
-superset
-of the function they need and then manually extract the required
-features and plug-ins. This can be a laborious and error prone process.</p>
-<p>Fortunately, PDE contains a batch oriented mechanism, the <em>packager</em>
-which can help. In short, the packager takes as input a list of
-archives containing features and a list of interesting features. It
-then fetches
-the zips, extracts the features (and their plug-ins) and repackages
-them into an output zip.</p>
-<h2>Quick Start<br>
-</h2>
-<p>Below is a set of basic steps to get started with the
-packager.&nbsp; It is suggested that you build *nix packages on a *nix
-machine to ensure that file permissions are preserved.<br>
-</p>
-<ol>
-  <li>Create a packaging configuration directory and copy the template
-files (packager.properties, packaging.properties, and
-customTargets.xml) from org.eclipse.pde.build/templates/packager here.</li>
-  <li>Edit the copied packager.properties files and set the following
-properties:
-  <ul>
-    <li><span style="font-weight: bold;">baseDirectory </span>: the
-directory in which the actual packaging work will take place.
-&nbsp;&nbsp;&nbsp; <br>
-    </li>
-    <li><span style="font-weight: bold;">featureList </span>: a comma
-separated list of feature ids that you wish to include in your archive.<br>
-    </li>
-    <li><span style="font-weight: bold;">componentFilter </span>:&nbsp;
-A comma separated list of components from which your features can be
-found.&nbsp; Specifying this will avoid unnecessary downloads.&nbsp;
-Use * if you don't know the components.&nbsp; (See the componentName in
-the <a href="pde_packager.htm#Packager_Map_File_Format">Packager Map
-File Format</a>
-below).<br>
-      <span style="font-weight: bold;"></span></li>
-    <li><span style="font-weight: bold;">contentFilter</span> : A comma
-separated list of content type you are interested in.&nbsp; Common
-content types are <tt>runtime</tt> or <tt>sdk</tt>.&nbsp; This is
-used to optimize the
-downloading of the archives.&nbsp;&nbsp; Leave this blank to not filter
-on content type.&nbsp; (See the contentDescription in the <a
- href="#Packager_Map_File_Format">Packager Map File Format</a>
-below).</li>
-    <li><span style="font-weight: bold;">config </span>:&nbsp; The
-configurations to package. This is an "&amp;" separated list of comma
-separated triples of operating system,
-windowing system and architecture (eg <tt>win32,win32,x86 &amp; linux,
-gtk, ppc</tt>)</li>
-  </ul>
-  </li>
-  <li>Get packager map files.&nbsp; The following properties control
-downdloading the map files:<br>
-    <ul>
-      <li><span style="font-weight: bold;">localMaps</span> : Set this
-property if you have map files locally,
-put
-the map files in <tt>${downloadDirectory}</tt> (by default this is <tt>${baseDirectory}/toPackage</tt>).&nbsp;
-Comment out this property to automatically download the map file.</li>
-      <li><span style="font-weight: bold;">packagerMapURL</span> : The
-URL from which to download the map file.</li>
-    </ul>
-The packager script will concatenate all *.map files found in <tt>${downloadDirectory}</tt>.
-To download more than one map file, or to fetch them from CVS edit the
-customTargets.xml file and change the getMapFiles target. </li>
-  <li>Run the packager using the following command:
-  <pre>java -jar &lt;eclipse install&gt;/plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar -application org.eclipse.ant.core.antRunner <br>    -buildfile &lt;&lt;eclipse install&gt;/plugins/org.eclipse.pde.build_&lt;version&gt;/scripts/package.xml&gt; <br>    -DpackagingInfo=&lt;path to your packaging configuration directory&gt;<br></pre>
-  </li>
-</ol>
-<h2><a name="Packager_Map_File_Format"></a>Packager Map File Format</h2>
-The packager map files are used to describe the various archives, their
-content and where they can be downloaded from.&nbsp; They are similar
-to the map files used in the build process to fetch bundles from
-repositories.&nbsp; The format of a packager map file entry is as
-follows:<br>
-<div style="text-align: center;"><tt>archiveName
-= <span style="font-weight: bold;">url</span> | [<span
- style="font-weight: bold;">configList</span>] |
-[<span style="font-weight: bold;">directory</span>] | <span
- style="font-weight: bold;">contentDescription</span> | <span
- style="font-weight: bold;">componentName</span></tt><br>
-</div>
-<ul>
-  <li><span style="font-weight: bold;">archiveName </span>: This is
-the name of the archive<br>
-    <span style="font-weight: bold;"></span></li>
-  <li><span style="font-weight: bold;">url</span> : This is the url
-where the archive can be found.&nbsp; The concatenation of url and
-archiveName should point to the archive to download.</li>
-  <li><span style="font-weight: bold;">configList</span> : This is an
-"&amp;" separated list of configs that this archive contains.&nbsp;
-(eg: <tt>win32, win32, x86 &amp; linux, gtk, x86</tt>).&nbsp; If no
-value is given the archive is considered to be platform independant.</li>
-  <li><span style="font-weight: bold;">directory</span> : The directory
-where the content of the archive should be extracted relative to a
-standard eclipse installation.&nbsp; When no value is specified it
-means that the archive contains an eclipse installation directory at
-its
-root.<br>
-    <span style="font-weight: bold;"></span></li>
-  <li><span style="font-weight: bold;">contentDescription</span> : The
-content flags indicating the type of content in this archive.&nbsp;
-Normally this is something like <tt>runtime</tt>, <tt>sdk</tt>, <tt>source</tt>,
-    <tt>doc</tt>, etc.</li>
-  <li><span style="font-weight: bold;">componentName</span> : The
-canonical name of the component this archive is for.&nbsp; For example
-eclipse, jdt, cdt, gef, emf, etc.<br>
-  </li>
-</ul>
-<br>
-Note that configList and directory are optional, it is important that
-the appropriate number "|" separators are still used.<br>
-Examples:<br>
-<pre>eclipse-SDK-3.1-win32.zip=http://download.eclipse.org/downloads/drops/R-3.1-200506271435/ | win32,win32,x86 | | sdk | eclipse<br>eclipse-PDE-3.1.zip=http://download.eclipse.org/downloads/drops/R-3.1-200506271435/ | | | runtime | pde<br></pre>
-<h2>Packager Configuration Properties</h2>
-The following properties can be set in the packager configuration
-packager.properties file:<br>
-<table style="width: 90%; text-align: left; margin-left: 40px;"
- border="1" cellpadding="2" cellspacing="0">
-  <tbody>
-    <tr>
-      <td style="vertical-align: top;">baseDirectory<br>
-      </td>
-      <td style="vertical-align: top;">The directory in which all the
-packaging will take place<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">workingDirectory<br>
-      </td>
-      <td style="vertical-align: top;">The directory in which the
-scripts will be generated.&nbsp; The value in the template is <tt>${baseDirectory}/workingPlace</tt><br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">downloadDirectory<br>
-      </td>
-      <td style="vertical-align: top;">The folder to which the archives
-will be downloaded.&nbsp; The value in the template is <tt>${baseDirectory}/toPackage</tt><br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">tempDirectory<br>
-      </td>
-      <td style="vertical-align: top;">The folder that the archives
-will be extracted to.&nbsp; The value in the template is <tt>${baseDirectory}/temp</tt><br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">featurePaths<br>
-      </td>
-      <td style="vertical-align: top;">The name of the root of the
-archives downloaded.&nbsp; The value in the template is <tt>eclipse</tt>.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">featureList<br>
-      </td>
-      <td style="vertical-align: top;">A comma separated list of
-feature ids that you wish to repackage.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">componentFilter<br>
-      </td>
-      <td style="vertical-align: top;">A comma separated list of the
-components from which the features in featureList can be found.&nbsp;
-This filters the available archives and allows the packager to optimize
-the set of files downloaded.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">contentFilter<br>
-      </td>
-      <td style="vertical-align: top;">A comma separated list of
-content types to fetch.&nbsp; This filters the set of available
-archives and allows the packager to optimize the set of files
-downloaded.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">config<br>
-      </td>
-      <td style="vertical-align: top;">An "&amp;" seperated list of
-configs (comma separated triples of operating system, windowing system,
-architecture) to repackage.&nbsp; (eg: <tt>win32, win32, x86 &amp;
-linux, gtk, x86</tt>) </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">archivesFormat<br>
-      </td>
-      <td style="vertical-align: top;">The formats of the
-archives.&nbsp; An "&amp;" separated list of config - format.&nbsp;
-(eg: <tt>win32, win32, x86 - antZip &amp; linux, gtk, ppc - tar</tt>).&nbsp;
-If
-no archive format is specified for a given config, the default format
-is antZip.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">zipargs<br>
-      </td>
-      <td style="vertical-align: top;">Extra arguments to be passed to
-zip<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">unzipargs<br>
-      </td>
-      <td style="vertical-align: top;">Extra arguments to be passed to
-unzip<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">archivePrefix<br>
-      </td>
-      <td style="vertical-align: top;">The prefix of the resulting
-archive(s)<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">collectingFolder<br>
-      </td>
-      <td style="vertical-align: top;">The name of the root folder of
-the resulting archive.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">buildId<br>
-      </td>
-      <td style="vertical-align: top;">Controls the build id in the
-default name of the archive.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">buildType<br>
-      </td>
-      <td style="vertical-align: top;">Type of the build, used in
-naming the build output.&nbsp; Typically one of I, N, M, S, ...<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">buildLabel<br>
-      </td>
-      <td style="vertical-align: top;">Label for the build.&nbsp; The
-template value is <tt>${buildType}.${buildId}</tt><br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">archiveNamePrefix<br>
-      </td>
-      <td style="vertical-align: top;">Control the name of the
-resulting archive.&nbsp; The default value of this is <tt>${buildId}</tt><br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">packagingProperties<br>
-      </td>
-      <td style="vertical-align: top;">A relative path to the file
-containing the properties packaging root files..&nbsp; By default
-this points to packaging.properties.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">deltaPack<br>
-      </td>
-      <td style="vertical-align: top;">Whether or not to generate a
-delta pack.&nbsp; This will exclude platform independant pieces and
-will group all configs into one archive.<br>
-      </td>
-    </tr>
-    <tr>
-      <td style="vertical-align: top;">unzipOrder<br>
-      </td>
-      <td style="vertical-align: top;">a comma separated list of archive name prefixes setting
-      the order in which archives should be extracted.<br>
-      </td>
-    </tr>    
-  </tbody>
-</table>
-<br>
-<h2>Packaging Root Files</h2>
-In the packager configuration packager.properties file, the property
-packagingProperties points to a property file which specifies the root
-files that need to be packaged.&nbsp; By default this is the file
-packaging.properties.<br>
-<br>
-This property file should contain the properties specifying the
-required root files.&nbsp; See the <a
- href="../reference/pde_feature_generating_build.htm#Feature_specific_properties">Feature
-specific properties</a> page for details on the root properties.<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_plugins_build.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_plugins_build.htm
deleted file mode 100644
index 45bcae8..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_plugins_build.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Building plug-ins / bundles</title>
-</head>
-<body>
-<h1>Building plug-ins / bundles</h1>
-<p>
-In order to build plug-ins, bundles or fragments, PDE build requires that you create a feature listing all the elements to be built. 
-In this case the feature is only used to drive the build and will not be present in the final archive nor will it force you to use update sites.
-</p>
-<p>
-A feature used to drive a plug-in build is a standard feature. What makes it different is that its build.properties file does not contain the property <tt>bin.includes</tt>.  It is possible to automatically generate a feature containing the plug-ins you wish to build.  This lets you build your plug-ins without requiring you to maintain a feature.
-See the <a href="pde_feature_generating_antcommandline.htm#eclipseGenerateFeature">eclipse.generateFeature</a> task and the <a href="pde_customization.htm">Customizing a Headless Build</a> page.<br>
-Example:
-</p>
-<pre>
-build.properties:  topLevelElementId = acme.build.feature
-customTargets.xml : 
-	&lt;target name="preSetup"&gt;
-		&lt;eclipse.generateFeature
-			featureId="acme.build.feature"
-			buildDirectory="${buildDirectory}"
-			baseLocation="${baseLocation}"
-			productFile="${product}"
-			verify="false"
-			pluginPath="${pluginPath}"
-			configInfo="${configs}"
-			pluginList="acme.plugin.A,acme.plugin.B"
-			featureList="${featureList}"
-			includeLaunchers="false"
-		/&gt;
-	&lt;/target&gt;
-</pre>
-<p>
-Once you have created the feature to drive the build, follow the instructions on <a href="pde_feature_build.htm">building features</a>.
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm
deleted file mode 100644
index 3268214..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Building an RCP application from a product configuration file</title>
-</head>
-<body>
-<h1>Building an RCP application from a product configuration file</h1>
-<p>PDE Build comes with infrastructure to build a complete RCP
-application from a product configuration file. Most of the setup
-necessary for such a build can be done through a few modifications to
-the template build.properties provided in PDE build. The
-following section focuses on setting up a simple product build assuming
-that all plug-ins and features (both to build and pre-built) referenced
-by the product file are
-already locally available on disk.<br>
-</p>
-<h2>Basic setup</h2>
-<p>
-The first step in setting up a build is to create the directory in
-which the build will take place.
-This directory will be referred to as the <i>build directory</i> and
-will contain the plug-ins and features
-to build as well as all the generated artifacts. Next, copy your
-plug-ins and
-features respectively into "plugins" and "features" subdirectories.
-Your
-product configuration file is expected to be in one of these
-plugins/features.
-</p>
-The second step in setting up a build is to copy the template
-build.properties file from
-org.eclipse.pde.build/templates/headless-build to a new directory which
-will be the build configuration directory (also referred to as the <i>configuration
-directory</i>).
-Edit the copied build.properties file and set the following properties:<br>
-<ul>
-  <li><span style="font-weight: bold;">product</span>: the location of
-your product configuration file in the form "<code>/&lt;plugin or
-feature id&gt;/path/to/.product</code>"</li>
-  <li><span style="font-weight: bold;">baseLocation</span>:&nbsp; the
-location of an eclipse install containing all the pre-built features
-and plug-ins
-that your product requires in features/ and plugins/
-subdirectories.&nbsp; The RCP delta pack (it is available
-from the eclipse download page) is mandatory as it includes the
-org.eclipse.platform.launchers feature which
-contains the launchers and root files necessary for a product.</li>
-  <li><span style="font-weight: bold;">buildDirectory</span>:&nbsp; the
-directory the build will take place in.&nbsp; Set this to the full path
-of the build directory created
-previously.</li>
-  <li><span style="font-weight: bold;">configs</span>: list the
-configurations for which you want your product to be built. You can
-uncomment the configuration(s) provided (be careful of the line
-continuations).</li>
-  <li><span style="font-weight: bold;">archivePrefix</span>: the name
-of the directory of your product once installed on disk.</li>
-</ul>
-<h3>Overview of the directory structure</h3>
-<pre>&lt;buildDirectory&gt;/<br>	plugins/<br>		pluginToBuildA<br>		pluginToBuildB<br>			myProduct.product<br>		...<br>	features/<br>		featureToBuild<br>		...<br><br>&lt;buildConfiguration&gt;/<br>	build.properties<br><br>&lt;baseLocation&gt;<br>	plugins/<br>		org.eclipse.core.runtime<br>		org.eclipse.ui<br>		...<br>	features/<br>		org.eclipse.rcp<br>		org.eclipse.platform.launchers<br>		...<br>		<br></pre>
-<h2>Running the build</h2>
-To run the build you will use the org.elipse.ant.core.antRunner
-application. When invoking eclipse with this application to
-perform a build you need to set two arguments on the command line:<br>
-<ul>
-  <li><code>-buildfile &lt;/path/to/productBuild.xml&gt;</code>:&nbsp;
-This is
-the path to
-the productBuild.xml provided by pde build.&nbsp; It is located in the
-org.eclipse.pde.build/scripts/productBuild directory.&nbsp; This is the
-build file
-that drives the whole product build process.</li>
-  <li><code>-Dbuilder=&lt;/path/to/configuration folder&gt;</code>:&nbsp;
-This is
-the path to the build configuration folder.</li>
-</ul>
-Run the antRunner application using the following command:<br>
-<div style="text-align: center;">
-<div style="text-align: left;">
-<div style="margin-left: 40px;"><code>java -jar
-&lt;eclipseInstall&gt;/plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar -application
-org.eclipse.ant.core.antRunner -buildfile
-&lt;&lt;eclipseInstall&gt;/plugins/org.eclipse.pde.build_&lt;version&gt;/scripts/productBuild/productBuild.xml&gt;
--Dbuilder=&lt;path to the build configuration folder&gt;</code><br>
-</div>
-<code></code></div>
-</div>
-<ul>
-</ul>
-<h2>Advanced scenarios</h2>
-<p>Behind the scenes this setup will generate a feature containing the
-plugins or features specified in your product configuration file.&nbsp;
-This generated feature is then used to drive a normal feature based
-headless build. If you require more customization of the build,
-ie fetching from a repository, see the Advanced
-PDE Build topics for
-more information.
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_rootfiles.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_rootfiles.htm
deleted file mode 100644
index 31727ee..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_rootfiles.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
- <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-
-<title>Adding Files to the Root of a Build</title>
-</head>
-<body>
-
-	<h1>Adding Files to the Root of a Build</h1>
-	<p>
-	Root files are files that must be packaged with an Eclipse install but are not features or plug-ins.  Common examples are the eclipse executable and ini files as well as licensing files.<br>Root files are contributed to a build by features containing the appropriate root properties.</p>
-	
-	<h2>Root file Properties</h2>
-	<table border="5" cellspacing="0" cellpadding="1">
-		<tr>
-			<td><pre>root</pre></td>
-			<td>Specify a list comma separated list of files or folders to be included in all configurations being built.  <br>Relative paths are relative to the containing feature.  Use &quot;file:&quot; to specify a file and &quot;absolute:&quot; to use an absolute path.<br>
-			Examples:
-				<ul>	
-					<li><b><tt>root=rootfiles</tt></b>: A relative path to a folder, the contents of the folder are included</li>
-					<li><tt><b>root=file:license.html,licenses</b></tt>: A relative path to a "license.html" file, and a relative path to a "licenses" folder</li>
-					<li><tt><b>root=absolute:/eclipse/rootfiles</b></tt>: An absolute path to a folder, the contents of the folder are included</li>
-					<li><tt><b>root=absolute:file:/eclipse/about.html,file:lib/*.so*</b></tt>: An absolute path to include &quot;about.html&quot;, as well as a relative path to include all the *.so* files under the lib folder.</li>
-				</ul>
-			<p>Each comma separated entry becomes an ant fileset.  If the entry refers to a folder, then that folder is the "dir" parameter of the fileset and a "**" is used as the "includes" parameter.  If the entry is a file, then the containing directory of the file becomes the "dir" parameter and the file is specified in the "includes" parameter.</p>
-			<p>For all relative files, the property <tt>${baseDir}</tt> will be used in the directory.  This <tt>${baseDir}</tt> property will be feature's root directory where the generated build.xml file will be located.</p>
-			
-			</td>
-		</tr>
-		<tr>
-			<td><pre>root.&lt;config&gt;</pre></td>
-			<td>Specify a list of files or folders to be included for the given configuration.  Configurations specified here should correspond to configurations in the <tt>configs</tt> property for the build.
-			   Relative paths are relative to the containing feature.  The same "file:" and "absolute:" prefixes used in the "root" property also apply here.<br>
-			Examples:
-				<ul>	
-					<li><tt><b>root.win32.win32.x86=rootfiles</b></tt>: A relative path to a folder, the contents of the folder are included in the win32.win32.x86 configuration</li>
-					<li><tt><b>root.linux.gtk.x86=absolute:file:about.html</b></tt>: An absolute path to a file to include in the linux.gtk.x86 configuration.</li>
-				</ul>
-			</td>
-		</tr>
-		<tr>
-			<td><pre>root.folder.&lt;subfolder&gt;</pre><br><pre>root.&lt;config&gt;.folder.&lt;subfolder&gt;</pre></td>
-			<td>Similar to the &quot;<tt>root</tt>&quot; and &quot;<tt>root.&lt;config&gt;</tt>&quot; properties, except that instead of being copied into the root of the eclipse install, files and folders are instea copied into the given subfolder.
-			<br>  Relative paths are relative to the containing feature.  The same "<tt>file:</tt>" and "<tt>absolute:</tt>" prefixes used in the "<tt>root</tt>" property also apply here.<br>
-			Examples:
-				<ul>	
-					<li><tt><b>root.folder.docs/html=html_files</b></tt>: The contents of the feature's &quot;html_files&quot; folder are copied into the docs/html folder in the eclipse install.</li>
-					<li><tt><b>root.linux.gtk.x86.folder.jre=absolute:/build/jres/linux</b></tt>: An absolute path,  the contents of the /build/jres/linux folder are copied into the jre folder of the eclipse install.</li>
-				</ul>
-				
-				These properties are used by PDE/UI when a JRE is specified in a .product file for export.  PDE/Build does not currently support including a JRE using the .product file, and these properties would need to be specified in a feature in to include a JRE in a headless product build.
-			</td>
-		</tr>
-		<tr>
-			<td><pre>root.permissions.<tt>&lt;rights&gt;</tt></pre><br><pre>root.&lt;config&gt;.permissions.&lt;rights&gt;</pre></td>
-			<td>Specify a list of files to on which to run the ant chmod task.  The value of this property will be passed to the ant chmod task as the &quot;includes&quot; parameter.  This means that ant wildcard patterns can be used.<br>
-			Examples:
-				<ul>	
-					<li><tt><b>root.permissions.755=eclipse</b></tt>: Set the 'eclipse' file to have executable permissions.</li>
-					<li><tt><b>root.linux.gtk.x86.permissions.755=lib/**</b></tt>: Set all files under the lib directory to be executable</li>
-				</ul>
-				<br>The 
-			<tt>&lt;rights&gt;</tt> portion of the property is actually passed to the ant chmod task as the &quot;perm&quot; parameter.  If the final archive format for the configuration is antTar, then the <tt>&lt;rights&gt;</tt> format is also passed to an  ant tarfileset as the &quot;filemode&quot; parameter.   Similarly, for antZip and  zipfileset.  While the ant chmod task supports permissions such as &quot;og-rwx&quot; (make non-owners unable to touch the file), the tar  and zip filesets only support 3 digit octal strings.</td>
-		</tr>
-		<tr>
-			<td><pre>root.link</pre><br><pre>root.&lt;config&gt;.link</pre></td>
-			<td>List by pairs (separated by comma) the files and folders that need to be symbolically linked.  The first entry of the pair is the target and the second entry is the link name..<br>
-			Example:
-				<ul>	
-					<li><tt><b>root.macosx.carbon.ppc.link=Eclipse.app/Contents/MacOS/eclipse,eclipse</b></tt>:  In the macosx.carbon.ppc configuration create a softlink in the root named &quot;eclipse&quot; that points to the &quot;Eclipse.app/Contents/MacOS/eclipse&quot; file.</li>
-				</ul>
-				<br>This results in an ant exec task that executes an &quot;<tt>ln -sf</tt>&quot; command.  Given a value of  &quot;targetA, nameA, targetB, nameB, targetC, nameC&quot;, a set of &quot;ln&quot; commands will be executed in the folder where the eclipse rootfiles are collected:
-				<pre>		ln -sf targetA nameA
-ln -sf targetB nameB
-ln -sf targetC nameC</pre>
-			</td>
-		</tr>
-	</table>
-	<h1>Including Root Files in a Product Build</h1>	
-	<p>
-	When using a .product file based on features, then rootfiles can be added to the product simply by specifying the above rootfile properties in any of the included features.  
-</p><p>
-It is possible to include a feature solely for the purpose of contributing rootfiles.  If this "rootfile" feature does not specify a "bin.includes" property in its build.properties file, then it will not be included in the final build results, but its contributed rootfiles will be.
- </p> 
- 
- <p>When a .product file is based on plug-ins instead of features, rootfiles can still be added to the build.  In a product build, PDE/Build automatically generates a container feature which includes all the plug-ins specified in the .product file (See the <a
- href="pde_feature_generating_antcommandline.htm">eclipse.generateFeature</a> task).  There are two ways to add rootfiles to this product build:</p>
- <ul>
- <li>Create a feature that contributes rootfiles, but does not specify a bin.includes property.  Add this feature to the automatically generated container feature by setting the <tt>featureList</tt> property:
- <pre>
-     ${buildDirectory}/features/org.foo.rootfile.feature/rootfiles/*
-                                                        /build.properties    : root = rootfiles
-     ${buildDirectory}/build.properties: featureList = org.foo.rootfile.feature
- </pre>
- </li>
- <li> Add a build.properties file containing absolute root properties to the automatically generated container feature:
- <pre>
-     ${buildDirectory}/build.properties:  generatedBuildProperties = ${buildDirectory}/root.properties
-     ${buildDirectory/root.properties:    root = absolute:${buildDirectory}/rootfiles
-     ${buildDirectory}/rootfiles/*
- </pre>
- </li>
-</ul>
- 
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_source_generation.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_source_generation.htm
deleted file mode 100644
index 2fd44cc..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_source_generation.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Generating Source Features and Plug-ins</title>
-</head>
-<body>
-<h1>Generating Source Features and Plug-ins</h1>
-<p>
-PDE Build can generate a source feature or plug-in. Consider the
-following SDK feature:</p><br>
-<div style="text-align: left; margin-left: 40px;">
-<pre>features/<br>    org.foo.sdk/<br>	feature.xml: &lt;includes id="org.foo.rcp" /&gt;<br>		     &lt;includes id="org.foo.rcp.source" /&gt;<br>	build.properties: generate.feature@org.foo.rcp.source = org.foo.rcp<br>    org.foo.rcp/<br>	feature.xml: &lt;plugin id="org.foo.BundleA" /&gt;<br>		     &lt;plugin id="org.foo.BundleB" /&gt;<br>		     &lt;plugin id="org.foo.BundleB.win32" fragment="true" os="win32" /&gt;<br></pre>
-</div>
-
-<p>
-The idea of the SDK is that it includes a feature as well as
-the source for that feature.&nbsp; Notice
-the <tt>generate.feature</tt> property in the feature's
-build.properties
-file.&nbsp; This property tells PDE Build to generate a feature named
-"<tt>org.foo.rcp.source</tt>" based on the contents of the feature
-"<tt>org.foo.rcp</tt>".&nbsp; PDE build will generate an
-org.foo.rcp.source feature, a plugin that
-will contain the source code, and fragments containing the source of
-any platform specific bundles that were included in the feature:</p><br>
-<div style="text-align: left; margin-left: 40px;">
-<pre>features/<br>    org.foo.rcp.source/<br>	feature.xml:  &lt;plugin id="org.foo.rcp.source"/&gt;<br>		      &lt;plugin id="org.foo.rcp.source.win32" fragment="true" os="win32" /&gt;<br>plugins/<br>    org.foo.rcp.source/src/<br>		org.foo.BundleA/src.zip<br>		org.foo.BundleB/src.zip<br>    org.foo.rcp.source.win32/src/<br>		org.foo.BundleB.win32/src.zip<br> <br></pre>
-</div>
-<h2>Customizing the Generated Source Feature</h2>
-<p>
-The generate.feature property has the following form:</p>
-<pre style="text-align: left;">generate.feature@&lt;source feature id&gt; = &lt;feature id&gt; [, feature@&lt;feature id&gt;[;attribute=value]*]* [, plugin@&lt;plugin id&gt;[;attribute=value]*]*</pre>
-<ul>
-  <li><span style="font-weight: bold;">&lt;source feature id&gt;:</span>&nbsp;
-This is the id of the source feature and plug-in to be generated.&nbsp;
-Normally it is something like &lt;feature id&gt;.source</li>
-  <li><span style="font-weight: bold;">&lt;feature id&gt;</span>:&nbsp;
-The feature on which to base the source feature, the source for all
-contained plug-ins will be collected into the &lt;source feature id&gt;
-plugin.</li>
-  <li><span style="font-weight: bold;">feature@&lt;feature id&gt;</span>:&nbsp;
-This will include the named feature in the generated source feature.</li>
-  <li><span style="font-weight: bold;">plugin@&lt;plug-in id&gt;</span>:&nbsp;
-This will include the named plug-in in the generated source feature.
-If the plug-in is JARed specify <span style="font-weight: bold;">unpack="false"</span>. If multiple versions
-of the plug-in are available, specify the requested version using <span style="font-weight: bold;">version=&lt;pluginVersion&gt;</span> followed by <tt>qualifier</tt>.</li>
-<li>
-<b><i>attribute</i>=<i>value</i></b> : Both feature@ and plugin@ entries can be qualified with additional attributes that should be added in the generated source feature.<br>
-Possible attributes (with example values) for <tt>feaure@</tt> entries are:
-<ul>
-<li>version = 1.0.0 : specify the version of the feature to include</li>
-<li>optional = true : set the included feature as optional</li>
-<li>ws=gtk : set the window system for the included feature</li>
-<li>os=linux : set the operating system for the included feature</li>
-<li>arch=x86 : set the architecture for the included feature</li>
-</ul>
-Possible attributes for <tt>plugin@</tt> entries are:
-<ul>
-<li>version = 1.0.0 : specify the version of the plug-in to include</li>
-<li>unpack = true : set the included plug-in to be unpacked (ie the plug-in should be installed as a folder).</li>
-<li>ws=gtk : set the window system for the included plug-in</li>
-<li>os=linux : set the operating system for the included plug-in</li>
-<li>arch=x86 : set the architecture for the included plug-in</li>
-</ul>
-</li>
-</ul>
-<p>
-Use plugin@ to add additional plug-ins that weren't part of the
-original feature to the generated source feature.&nbsp; This is useful
-for documentation plug-ins.&nbsp; The feature@ together with a source
-template can be used to nest source features (see below).
-</p>
-
-<h3>Source Templates</h3>
-<p>
-The feature from which the source feature is being generated can
-provide template files to be included in the generated source feature:</p><br>
-<div style="text-align: left; margin-left: 40px;">
-<pre>features/<br>    org.foo.rcp/<br> 	sourceTemplateFeature/&lt;files to be included in generated source feature&gt;<br>	sourceTemplatePlugin/&lt;files to be included in generated source plugin&gt;<br>	sourceTemplateFragment/&lt;files to be included in generated platform specific fragments&gt;</pre>
-</div>
-<p>Any files located in these sourceTemplate folder will be included in
-the appropriate generated feature/plug-in/fragment.&nbsp; Specifically,
-files from these directories will replace files generated by PDE
-build.&nbsp; This can be used to provide a custom feature.xml if there
-are requirements for your source feature that PDE build does not
-support.
-</p>
-<h4>Nesting Generated Source Features</h4>
-<p>You can nest source features by providing a
-sourceTemplateFeature/build.properties file for your generated source
-feature that contains a generate.feature property for the nested source
-feature.&nbsp; You will also need to ensure that your top source
-feature.xml includes the nested source feature, do this either by using
-feature@ or by providing a template feature.xml:<br>
-</p>
-<div style="text-align: left; margin-left: 40px;">
-<pre>features/<br>    org.foo.sdk/<br>	sourceTemplateFeature/<br>		build.properties:  generate.feature@org.foo.nested.source = org.foo.nested<br><br>	feature.xml: &lt;includes id="org.foo.rcp" /&gt;<br>		     &lt;includes id="org.foo.rcp.source" /&gt;<br><br>	build.properties: generate.feature@org.foo.rcp.source = org.foo.rcp, feature@org.foo.nested.source<br><br>    org.foo.rcp/...<br>    org.foo.nested/...<br></pre>
-</div>
-In the above example,&nbsp; org.foo.sdk contains a generated source
-feature named org.foo.rcp.source.&nbsp; This generated source feature
-will get the template sourceTemplateFeature/build.properties
-file.&nbsp; It will also include org.foo.nested.source in its
-feature.xml.&nbsp; So when PDE build is processing the generated
-org.foo.rcp.source, it sees the inclusion of the org.foo.nested.source
-feature and the generate.feature property and then generates the
-org.foo.nested.source.
-
-<h2>Generating a Source Plug-in</h2>
-<p>It is also possible to generate a single source plug-in based on a
-feature instead of generating an entire source feature.&nbsp; The
-property to do this is:</p>
-<p style="text-align: center;"><tt>generate.plugin@&lt;source plug-in
-id&gt;=&lt;feature-in id&gt;</tt></p>
-Example:
-<div style="text-align: left; margin-left: 40px;">
-<pre>features/<br>    org.foo.sdk/<br>	feature.xml: &lt;plugin id="org.foo.rcp" /&gt;<br> 		    &lt;plugin id="org.foo.sdk.source" /&gt;<br> <br>	build.properties: generate.plugin@org.foo.sdk.source = org.foo.sdk<br></pre>
-</div>
-<br>
-<br>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_version_qualifiers.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_version_qualifiers.htm
deleted file mode 100644
index 505c7c5..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_version_qualifiers.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-  <title>Using version qualifiers</title>
-</head>
-<body>
-<h1>Using Version Qualifiers</h1>
-<p>Eclipse bundles and features have version numbers of the form <span
- style="font-style: italic;">major</span>.<span
- style="font-style: italic;">minor</span>.<span
- style="font-style: italic;">micro</span>.<span
- style="font-style: italic;">qualifier</span>.&nbsp; The qualifier
-segment of the version is often used to indicated a specific
-build.&nbsp; If you set your feature or plug-in version qualifier to
-"<tt style="font-weight: bold;">qualifier</tt>" (i.e. a version of <tt>1.0.0.qualifier</tt>),
-then PDE build
-will
-automatically replace the word "qualifier" with a generated qualifier.<br>
-</p>
-<h2>Controlling the Generated Qualifier</h2>
-<p>A feature or plug-in can control its qualifier by setting the property "<tt><b>qualifier</b></tt>" in its build.properties file.  There are are a couple of different cases for the value of this property:</p>
-<table style="border: solid;" border="1" cellspacing="0" cellpadding="1" width="95%" align="center">
-	<tr><td><tt>qualifier = none</tt></td><td>Sets the qualifier to be empty.  (i.e. "1.2.3.qualifier" becomes "1.2.3")</td></tr>
-	<tr><td><tt>qualifier = context</tt></td><td>Sets the qualifier to be the <i>context</i> qualifier.  See below for the value of the context qualifier.</td></tr>
-	<tr><td><i>not set</i></td><td>If the "<tt>qualifier</tt>" property is not set, this is equivalent to setting <tt>qualifier = context</tt>.</td></tr>
-	<tr><td><tt>qualifier = v12345</tt></td><td>Any other value sets the qualifier to be that value.</td></tr>
-</table>
-<h3>The Context Qualifier</h3>
-The value of the generated context qualifier is determined by the first of the
-following items that apply:<br>
-<ol>
-  <li>If the property <tt style="font-weight: bold;">forceContextQualifier</tt> is set in your builder's
-configuration build.properties file,&nbsp; then the value of this
-property is used as the qualifier.&nbsp; This property can also be set
-on the command line with -D when invoking ant.<br>
-<ul>
-<li>When exporting from the UI, <tt>forceContextQualifier</tt> is set according to the "Qualifier replacement" value on the options tab of the "Deployable plug-ins and fragments" export wizard.</li>
-</ul>
-  </li>
-  <li>If you are using map files to fetch your bundles from a
-repository,
-then the tag that was used to fetch the bundle will be used as the
-qualifier.</li>
-  <li>If neither forceContextQualifier nor map files are used, then the
-qualifier will be a time stamp in the form YYYYMMDDHHMM (i.e.
-200605121600)<br>
-  </li>
-</ol>
-<h2>Feature Version Suffixes</h2>
-You can turn on the generation of qualifier suffixes for features by
-setting the property <tt style="font-weight: bold;">generateFeatureVersionSuffix=true
-</tt>in the build configuration build.properties file.<br>
-<br>
-The idea of a version is that it should increment each time something
-changes, the version qualifier increments and captures changes from
-build to build.&nbsp; Features rarely change, however, they do contain
-plug-ins which may change often.&nbsp; When version suffixes are turned
-on, a feature version will have the form <span
- style="font-style: italic;">major.minor.micro.qualifier-suffix</span>.&nbsp;&nbsp;
-The suffix is in effect the sum of the version qualifiers of all the
-features and plug-ins included by the feature.&nbsp; This means that
-when one of the included plug-ins increments its version, then the
-version of the feature will automatically increment as well.&nbsp; This
-is particularly useful when the feature is deployed via an update site.<br>
-<br>
-<h2><a name="final_versions"></a>Final Versions</h2>
-<p>
-Occasionally there may be custom build steps that may require the
-actual final version used in the build.&nbsp; When the property <b><tt>generateVersionsLists</tt></b> is set, PDE Build will generate
-properties files containing the versions of the features and plug-ins
-that were built.&nbsp; These properties files can be loaded using the ant property task.</p>
-<p>
-The files are named:
-finalPluginsVersions.properties,
-finalPluginsVersions.&lt;config&gt;.properties,
-finalFeaturesVersions.properties, and&nbsp;
-finalFeaturesVersions.&lt;config&gt;.properties.&nbsp;
-finalPluginsVersions.properties and finalFeaturesVersions.properties
-contain the versions for all of the plug-ins and features that were
-built.&nbsp; The &lt;config&gt; properties files contain the versions
-of plug-ins and features for specific build configurations.</p>
-<p>
-The properties in these files have the form:<br>
-</p><pre>&nbsp;&nbsp;&nbsp; &lt;bundleSymbolicName&gt; = &lt;version&gt;<br>&nbsp;&nbsp;&nbsp; &lt;bundleSymbolicName&gt;_&lt;first 3 segments of version&gt; = &lt;version&gt;</pre>
-If more than one versions of a plug-in or feature exists, then
-<tt>&lt;bundleSymbolicName&gt;=&lt;version&gt;</tt> refers to the plug-in or
-feature with the highest version.
-<p></p>
-Example:<br>
-<pre>&nbsp;&nbsp;&nbsp; org.eclipse.pde.build = 3.3.0.v20070524<br>&nbsp;&nbsp;&nbsp; org.eclipse.pde.build_3.3.0=3.3.0.v20070524<br>&nbsp;&nbsp;&nbsp; org.eclipse.pde.build_3.2.1=3.2.1.r321_v20060823</pre>
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.pde.doc.user/tasks/ui_export_install_into_host.htm b/bundles/org.eclipse.pde.doc.user/tasks/ui_export_install_into_host.htm
deleted file mode 100644
index a7f76f2..0000000
--- a/bundles/org.eclipse.pde.doc.user/tasks/ui_export_install_into_host.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../guide/book.css" type="text/css">
-<title>Export and Install into the Running Host</title>
-<script type="text/javaScript" language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body>
-<h1>Export and Install into the Running Host</h1>
-<p>PDE provides several tools for launching plug-ins and features in your workspace.  The Eclipse Application Launcher can be used to create a second running instance of Eclipse that runs the code you have in your workspace.  This is commonly referred to as <em>self-hosting</em>.  Self-hosting is a powerful debugging and testing tool.  However it is sometimes necessary for code to be tested in your host, your currently running Eclipse instance.  To test code in the host, you need to export and install into the running Eclipse instance.</p>
-
-<p>To export plug-ins and features and install them into the host Eclipse do the following:</p>
-<ol>
-<li>Develop your plug-ins and features in the workspace</li>
-<li>Open the export wizard, either <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.pde.ui.pluginExportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the plugin export wizard">
-<strong>File &gt; Export... &gt; Plug-in Development &gt; Deployable plug-ins and fragments</strong>
-</a> or <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.pde.ui.featureExportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the feature export wizard">
-<strong>File &gt; Export... &gt; Plug-in Development &gt; Deployable features</strong>
-</a></li>
-<li>Select your plug-ins or features to export and install</li>
-<li>Select the last option on the <em>Destination</em> tab <strong>Install into host. Repository</strong>.  Then choose a directory to create the repository in</li>
-<li>Hit <strong>Finish</strong>.  The export operation will run followed by the installation operation.</li>
-<li>If the operations completed succesfully, you will be prompted to restart.  Choose to restart now</li>
-<li>Your plug-ins will be installed and running after the restart.  You can see what has been installed using the <strong>Installation Details</strong> button on the About Dialog (available by going to Help &gt; About Eclipse SDK)</li>
-</ol>
-
-<br>
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0"></p>
-<p>
-<a href="../guide/tools/launchers/eclipse_application_launcher.htm">Eclipse Application Launcher</a><br>
-<a href="../guide/tools/export_wizards/export_wizards.htm">Export Wizards</a><br>
-<a href="../guide/tools/export_wizards/export_plugins.htm">Plug-in Export Wizard</a><br>
-<a href="../guide/tools/export_wizards/export_features.htm">Feature Export Wizard</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png b/bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png
deleted file mode 100644
index e6e9949..0000000
--- a/bundles/org.eclipse.pde.doc.user/tips/images/package-prefix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm b/bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm
deleted file mode 100644
index 862df43..0000000
--- a/bundles/org.eclipse.pde.doc.user/tips/pde_tips.htm
+++ /dev/null

@@ -1,161 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
-<meta name="ProgId" content="FrontPage.Editor.Document">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"></script>
-<title>PDE Tips and Tricks</title>
-</head>
-
-<body>
-
-<h2>Tips and Tricks</h2>
-
-
-<table border="1" cellpadding="10" cellspacing="0" width="600">
-  <tr>
-    <td valign="top" align="left" width="20%">
-    	<b>Creating a Rich Client Application</b>
-    </td>
-    <td valign="top" align="left" width="80%">
-		The 
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.pde.rcpapp)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the RCP cheat sheet"><strong>Creating a Rich Client Application</strong></a>
-		cheat sheet will guide you through the individual steps to create a plug-in, 
-		define a plug-in based product, customize a product, export a Rich Client Platform (RCP) 
-		application and define a feature-based product using the Plug-in Development Environment (PDE).
-    </td>
-  </tr>
-  <tr>
-    <td valign="top" align="left" width="20%">
-    	<b>Creating an Eclipse Plug-in</b>
-    </td>
-    <td valign="top" align="left" width="80%">
-		The 
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.pde.helloworld)")'>
-    		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Open the hello world cheat sheet"><strong>Creating an Eclipse Plug-in</strong></a>
-		cheat sheet will guide you through the individual steps to create a plug-in, a plug-in extension, 
-		a feature and an update site using the Plug-in Development Environment (PDE). 
-		It will also demonstrate how to install and uninstall a feature using Install/Update.
-    </td>
-  </tr>  
-  <tr>
-    <td valign="top" align="left" width="20%" height="345"><b>Feature-based 
-    self-hosting</b></td>
-    <td valign="top" align="left" width="80%" height="345">The current method of self-hosting in Eclipse
-      is plug-in-based. PDE launches a second run-time workbench instance by
-      passing an array of plug-ins that it should load. A regular Eclipse
-      product is feature-based: during startup, it checks all the features that
-      should be active, computes plug-ins that belong to those features, and
-      passes the result for loading.
-      <p>This difference in behavior makes it complicated to self-host in
-      scenarios where a full startup that involves features is required. PDE now
-      supports this scenario if care is taken with the setup:</p>
-      <ol>
-        <li>The workspace needs to be &lt;work-area&gt;/plugins.</li>
-        <li>Features must be imported into the workspace using the new 'Feature
-          Import' wizard (they will be created in &lt;work-area&gt;/features).</li>
-        <li>All plug-ins must be in the workspace (either in source or imported
-          as binary projects WITHOUT linking).</li>
-        <li>When launching, Run-time Workbench launcher must be configured to
-          use features (in Plug-ins and Fragments tab).</li>
-      </ol>
-      <p>If all these conditions are met, the runtime Eclipse instance will be
-      launched in a way that is the closest possible approximation of a normal
-      Eclipse startup. This facilitates testing About dialogs and other aspects
-      that may depend on the set of installed features.</p></td>
-  </tr>
-  <tr>
-    <td valign="top" align="left" width="20%"><b>To clean or not to clean</b></td>
-    <td valign="top" align="left" width="80%">When you create a new runtime 
-    workbench launch configuration, PDE presets the Program Arguments on the 
-    launch configuration to include a -clean argument.&nbsp;
-    <p>This -clean argument clears all runtime-cached data in your runtime 
-    workbench from one invocation to the next to ensure that all the changes 
-    made in your host workbench, e.g. new Java packages were added to a plug-in 
-    project, etc., are picked up when you launch a runtime workbench.</p>
-    <p>This clearing of the cache may hinder performance if your target platform 
-    contains a large number of plug-ins.&nbsp; </p>
-    <p>Therefore, if you're in a situation where your target platform has a 
-    large number of plug-ins and you're at a stage where you are not actively 
-    adding/removing packages from your plug-in projects, you could remove the 
-    -clean argument from the launch configuration to improve startup time.</p></td>
-  </tr>
-  <tr>
-    <td valign="top" align="left" width="20%"><b>Importing with linking</b></td>
-    <td valign="top" align="left" width="80%">Importing external plug-ins and 
-    fragments can be time consuming and may result in large workspaces, 
-    depending on the content of the plug-ins being imported.&nbsp; Therefore, 
-    the 'Import External Plug-ins and Fragments' wizard gives you the option to 
-    import with linking.&nbsp; This means that the import operation will not 
-    copy the resources being imported into your workspace.&nbsp; It will simply 
-    create links to the files being imported.&nbsp; You will be able to browse 
-    these linked resources, as if they had been copied into your workspace.&nbsp; 
-    However, they are physically not there on your file system, so you will not 
-    be able to modify them.&nbsp; Beware of operations that depend on files 
-    being physically in your workspace, as they will not work on linked 
-    resources.</td>
-  </tr>
-  <tr>
-    <td valign="top" align="left" width="20%" height="112"><b>Templates</b></td>
-    <td valign="top" align="left" width="80%" height="112">For a quick start, PDE provides 
-    several template plug-ins that will generate a plug-in with one or more 
-    fully-working extensions.&nbsp; In addition, if at any point, you would like 
-    to add a new extension from the template list (without having to generate a 
-    plug-in), you could access these extension templates directly from the 
-    manifest editor.&nbsp; From the 'Extensions' page of the editor, click 
-    'Add...'.&nbsp; In the wizard that comes up, select Extension Templates in 
-    the left pane and choose the template of choice in the right pane.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left" height="280"><b>Plug-in dependency extent</b></td>
-    <td width="80%" valign="top" align="left" height="280">If you have ever looked at the 
-    list of plug-ins that your plug-in depends on and wondered why your plug-in 
-    needs a particular plug-in X, now you can easily find out why.&nbsp; 
-    <p>The <b>Compute Dependency Extent </b>operation
-      found on the context menu in several contexts (including manifest file
-      Dependencies page and Plug-in Dependencies view) performs a combined Java and
-      plug-in search to find all Java types and extension points provided by 
-    plug-in X which are referenced
-      by your plug-in. The results will be displayed in the Search view.&nbsp; When a type is selected in the Search results view, the <b>References
-      in <i>MyPlugIn</i></b> action in the context menu searches for the places
-      in the plug-in where the selected type is referenced.&nbsp;</p>
-    <p>If the 
-    search returns 0 results, you should definitely remove plug-in X from your 
-    list of dependencies, as it is not being used at all, and it would just slow 
-    class loading.</p>
-    <p>The <b>Compute Dependency Extent</b> is also useful to check if you are 
-    using internal (non-API) classes from plug-in X, which might not be 
-    desirable.</p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left" height="112"><b>Finding unused dependencies</b></td>
-    <td width="80%" valign="top" align="left" height="112">Minimizing a plug-in's number of 
-    dependencies is certain to improve performance.&nbsp; As your plug-in 
-    evolves, its list of dependencies might become stale, as it might be still 
-    containing references to plug-ins that it no longer needs.&nbsp; A quick way 
-    to check that all dependencies listed by your plug-in are actually used by 
-    the plug-in is to run the 'Find Unused Dependencies' utility, which is 
-    available through the context menu of the 'Dependencies' page of PDE's 
-    manifest editor.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left" height="80"><b>Extending the Java 
-    search scope</b></td>
-    <td width="80%" valign="top" align="left" height="80">Java Search is limited to projects 
-    in your workspace and external jars that these projects reference.&nbsp; If 
-    you would like to add more libraries from external plug-ins into the search: 
-    open the Plug-ins View, select a plug-in and choose <b>Add to Java Search</b> 
-    from the context menu. This is handy for remaining
-      aware of other plug-ins that depend on ones you're working on.</td>
-  </tr>
-  </table>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.pde.doc.user/toc.xml b/bundles/org.eclipse.pde.doc.user/toc.xml
deleted file mode 100644
index ae0929d..0000000
--- a/bundles/org.eclipse.pde.doc.user/toc.xml
+++ /dev/null

@@ -1,59 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!--
-     Copyright (c) 2005, 2009 IBM Corporation and others.
-     All rights reserved. This program and the accompanying materials
-     are made available under the terms of the Eclipse Public License v1.0
-     which accompanies this distribution, and is available at
-     http://www.eclipse.org/legal/epl-v10.html
-    
-     Contributors:
-         IBM Corporation - initial API and implementation
- -->
-
-<toc label="Plug-in Development Environment Guide">
-
-	<!-- Overview -->
-	<topic href="guide/intro/pde_overview.htm" label="PDE Overview">
-	</topic>
- <topic label="Concepts">
-    <topic href="concepts/extension.htm" label="Extensions and Extension Points">
-    </topic>
-    <topic href="concepts/feature.htm" label="Feature">
-    </topic>
-    <topic href="concepts/fragment.htm" label="Fragment">
-    </topic>
-    <topic href="concepts/plugin.htm" label="Plug-in">
-    </topic>
-    <topic href="concepts/product.htm" label="Product">
-    </topic>
-    <topic href="concepts/target.htm" label="Target Platform">
-    </topic>
-    <topic href="concepts/update_site.htm" label="Update Site">
-    </topic>
- </topic>
-	
-	<!-- Tasks -->
-	<topic label="Tasks">
- 		<link toc="topics_Tasks.xml"/>
-	</topic>
-	
-	<!-- Reference -->
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	
-	<!-- Tips and Tricks -->
-	<topic label="Tips and Tricks" href="tips/pde_tips.htm"/>
-	
-	<!-- What's New -->
-	<topic label="What's New" href="whatsNew/pde_whatsnew.htm"/>
-	
-	<!-- Legal Notices -->
-	<topic label="Legal" href="notices.html"/>
-	
-	<!-- Enablement -->
-	<enablement>
-		<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.pde.ui"/>
-	</enablement>
-</toc>

diff --git a/bundles/org.eclipse.pde.doc.user/topics_Reference.xml b/bundles/org.eclipse.pde.doc.user/topics_Reference.xml
deleted file mode 100644
index baf9dea..0000000
--- a/bundles/org.eclipse.pde.doc.user/topics_Reference.xml
+++ /dev/null

@@ -1,316 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!--
-     Copyright (c) 2005, 2009 IBM Corporation and others.
-     All rights reserved. This program and the accompanying materials
-     are made available under the terms of the Eclipse Public License v1.0
-     which accompanies this distribution, and is available at
-     http://www.eclipse.org/legal/epl-v10.html
-    
-     Contributors:
-         IBM Corporation - initial API and implementation
- -->
-
-<!-- ============================================================================= -->
-<!-- Define topics for the references                                              -->
-<!-- ============================================================================= -->
-<toc label="Reference">
-   <topic label="API Tools Ant Tasks">
-      <topic href="reference/api-tooling/ant-tasks/analysis-ant-task.htm" label="API Tools Analysis Ant Task">
-      </topic>
-      <topic href="reference/api-tooling/ant-tasks/analysis-reportconversion-ant-task.htm" label="API Tools Analysis Report Conversion Ant Task">
-      </topic>
-      <topic href="reference/api-tooling/ant-tasks/apifreeze-ant-task.htm" label="API Tools API Freeze Ant Task">
-      </topic>
-      <topic href="reference/api-tooling/ant-tasks/apifreeze-reportconversion-ant-task.htm" label="API Tools API Freeze Report Conversion Ant Task">
-      </topic>
-      <topic href="reference/api-tooling/ant-tasks/filegeneration-ant-task.htm" label="API Tools File Generation Ant Task">
-      </topic>
-      <topic href="reference/api-tooling/ant-tasks/apiuse-ant-task.htm" label="API Tools API Use Ant Task">
-      </topic>
-      <topic href="reference/api-tooling/ant-tasks/apiuse-reportconversion-ant-task.htm" label="API Tools API Use Report Conversion Task">
-      </topic>
-   </topic>
-   <topic label="Build Configuration">
-		<topic label="Builder Configuration properties" href="reference/pde_builder_config.htm" />
-  		<topic label="Feature and Plug-in Build configuration" href="reference/pde_feature_generating_build.htm"/>
-   </topic>
- <topic label="Editors">
-	<topic label="Plug-in Manifest Editor" href="guide/tools/editors/manifest_editor/editor.htm">
-		<topic label="Plug-in Overview" href="guide/tools/editors/manifest_editor/overview.htm"/>
-		<topic label="Plug-in Dependencies" href="guide/tools/editors/manifest_editor/dependencies.htm"/>
-		<topic label="Plug-in Runtime" href="guide/tools/editors/manifest_editor/runtime.htm">
-			<topic label="Access Rules" href="guide/tools/editors/manifest_editor/access_rules.htm"/>
-		</topic>
-		<topic label="Plug-in Extensions" href="guide/tools/editors/manifest_editor/extensions.htm"/>
-		<topic label="Plug-in Extension Points" href="guide/tools/editors/manifest_editor/extension_points.htm"/>
-		<topic label="Plug-in Build" href="guide/tools/editors/manifest_editor/build.htm"/>
-	</topic>
-	<topic label="Feature Manifest Editor" href="guide/tools/editors/feature_editor/feature_editor.htm">
-		<topic label="Feature Overview" href="guide/tools/editors/feature_editor/overview.htm"/>
-		<topic label="Feature Information" href="guide/tools/editors/feature_editor/information.htm"/>
-		<topic label="Included Plug-ins" href="guide/tools/editors/feature_editor/plugins.htm"/>
-		<topic label="Included Features" href="guide/tools/editors/feature_editor/included_features.htm"/>
-		<topic label="Feature Dependencies" href="guide/tools/editors/feature_editor/dependencies.htm"/>
-		<topic label="Feature Installation" href="guide/tools/editors/feature_editor/installation.htm"/>
-	</topic>
-	<topic label="Site Manifest Editor" href="guide/tools/editors/site_editor/site_editor.htm">
-		<topic label="Site Map" href="guide/tools/editors/site_editor/site_map.htm"/>
-		<topic label="Site Information" href="guide/tools/editors/site_editor/archives.htm"/>
-	</topic>
-	
-	<!-- Extension Point Schema Editor-->
-	
-	<topic label="Extension Point Schema Editor" href="guide/tools/editors/schema_editor/editor.htm">
-		<topic label="Schema Overview Page" href="guide/tools/editors/schema_editor/page_schema_overview.htm"/>
-		<topic label="Schema Definition Page" href="guide/tools/editors/schema_editor/page_schema_definition.htm"/>
-	</topic>
-	
-	<topic label="Product Configuration Editor" href="guide/tools/editors/product_editor/editor.htm">
-		<topic label="Product Overview" href="guide/tools/editors/product_editor/overview.htm"/>
-  <topic href="guide/tools/editors/product_editor/dependencies.htm" label="Product Dependencies">
-  </topic>
-		<topic label="Product Configuration" href="guide/tools/editors/product_editor/configuration.htm"/>
-		<topic label="Product Launching" href="guide/tools/editors/product_editor/launching.htm"/>
-		<topic label="Product Splash" href="guide/tools/editors/product_editor/splash.htm"/>
-		<topic label="Product Branding" href="guide/tools/editors/product_editor/branding.htm"/>
-  <topic href="guide/tools/editors/product_editor/licensing.htm" label="Product Licensing">
-  </topic>
-	</topic>
-	<topic label="Target Definition Editor" href="guide/tools/editors/target_editor/target_editor.htm">
-		<topic label="Target Definition" href="guide/tools/editors/target_editor/definition_page.htm"/>
-		<topic label="Target Content" href="guide/tools/editors/target_editor/content_page.htm"/>
-		<topic label="Target Environment" href="guide/tools/editors/target_editor/environment_page.htm"/>
-	</topic>
-	
-	<!-- Simple Cheat Sheet Editor-->
-	
-	<topic label="Simple Cheat Sheet Editor" href="guide/tools/editors/simple_cs_editor/editor.htm">
-		<topic label="Simple Cheat Sheet Page" href="guide/tools/editors/simple_cs_editor/page_cheat-sheet.htm">
-			<topic label="Content Section" href="guide/tools/editors/simple_cs_editor/section_content.htm"/>
-			<topic label="Title Section" href="guide/tools/editors/simple_cs_editor/section_title.htm"/>
-			<topic label="Introduction Section" href="guide/tools/editors/simple_cs_editor/section_introduction.htm"/>
-			<topic label="Step Section" href="guide/tools/editors/simple_cs_editor/section_step.htm"/>
-			<topic label="Sub-Step Section" href="guide/tools/editors/simple_cs_editor/section_sub-step.htm"/>
-			<topic label="Command Section" href="guide/tools/editors/simple_cs_editor/section_command.htm">
-				<topic label="Command Composer Dialog" href="guide/tools/editors/simple_cs_editor/dialog_command-composer.htm">
-					<topic label="Commands Section" href="guide/tools/editors/simple_cs_editor/section_commands.htm"/>
-					<topic label="Command Details" href="guide/tools/editors/simple_cs_editor/section_command-details.htm"/>
-				</topic>
-			</topic>
-			<topic label="Help Section" href="guide/tools/editors/simple_cs_editor/section_help.htm"/>
-		</topic>
-		<topic label="Register Cheat Sheet Wizard" href="guide/tools/editors/simple_cs_editor/wizard_register-cheat-sheet.htm"/>
-	</topic>
-
-	<!-- Composite Cheat Sheet Editor-->
-
-	<topic label="Composite Cheat Sheet Editor" href="guide/tools/editors/composite_cs_editor/editor.htm">
-		<topic label="Composite Cheat Sheet Page" href="guide/tools/editors/composite_cs_editor/page_cheat-sheet.htm"/>
-	</topic>
-
-	<!-- Table of Contents Editor -->
-
-	<topic label="Table of Contents Editor" href="guide/tools/editors/toc_editor/editor.htm">
-		<topic label="Table of Contents Page" href="guide/tools/editors/toc_editor/page_toc.htm"/>
-    </topic>
-  <topic href="guide/tools/editors/ctx_help_editor/ctx_help_editor.htm" label="Context Help Editor">
-  </topic>
-  <topic href="guide/tools/editors/category_editor/definition_page.htm" label="Category Definition Editor">
-  </topic>
-</topic>
-<topic label="Launchers">
-	<topic label="Eclipse Application Launcher" href="guide/tools/launchers/eclipse_application_launcher.htm">
-		<topic label="Main Tab" href="guide/tools/launchers/eclipse_main.htm"/>
-		<topic label="Arguments Tab" href="guide/tools/launchers/eclipse_args.htm"/>
-		<topic label="Plug-ins Tab" href="guide/tools/launchers/eclipse_plugins.htm"/>
-		<topic label="Configuration Tab" href="guide/tools/launchers/configuration.htm"/>
-		<topic label="Tracing Tab" href="guide/tools/launchers/tracing.htm"/>
-		<topic label="Environment Tab" href="guide/tools/launchers/environment.htm"/>
-		<topic label="Common Tab" href="guide/tools/launchers/common.htm"/>
-	</topic>
-	<topic label="OSGi Framework Launcher" href="guide/tools/launchers/equinox_launcher.htm">
-		<topic label="Bundles Tab" href="guide/tools/launchers/equinox_plugins.htm"/>
-		<topic label="Arguments Tab" href="guide/tools/launchers/equinox_args.htm"/>
-		<topic label="Settings Tab" href="guide/tools/launchers/equinox_settings.htm"/>
-		<topic label="Tracing Tab" href="guide/tools/launchers/tracing.htm"/>
-		<topic label="Environment Tab" href="guide/tools/launchers/environment.htm"/>
-		<topic label="Common Tab" href="guide/tools/launchers/common.htm"/>
-	</topic>
-	<topic label="JUnit Plug-in Test Launcher" href="guide/tools/launchers/junit_launcher.htm">
-		<topic label="Test Tab" href="guide/tools/launchers/junit_test.htm"/>
-		<topic label="Main Tab" href="guide/tools/launchers/junit_main.htm"/>
-		<topic label="Arguments Tab" href="guide/tools/launchers/eclipse_args.htm"/>
-		<topic label="Plug-ins Tab" href="guide/tools/launchers/junit_plugins.htm"/>
-		<topic label="Configuration Tab" href="guide/tools/launchers/junit_configuration.htm"/>
-		<topic label="Tracing Tab" href="guide/tools/launchers/tracing.htm"/>
-		<topic label="Environment Tab" href="guide/tools/launchers/environment.htm"/>
-		<topic label="Common Tab" href="guide/tools/launchers/common.htm"/>
-	</topic>
-</topic>
- <topic label="Menus and Actions">
-    <topic href="reference/api-tooling/actions/ref-apitooling-setup-action.htm" label="API Tooling Setup">
-    </topic>
-    <topic href="reference/api-tooling/actions/ref-compare-action.htm" label="Compare with API baseline">
-    </topic>
- </topic>
- <topic href="guide/tools/preference_pages/preferences.htm" label="Preferences">
-	<topic label="Compilers Preferences" href="guide/tools/preference_pages/compilers.htm">
-		<topic label="Plug-in Compiler Preferences" href="guide/tools/preference_pages/plugin_compiler.htm"/>
-		<topic label="Extension Point Schema Compiler Preferences" href="guide/tools/preference_pages/schema_compiler.htm"/>
-		<topic label="Feature and Update Site Compiler Preferences" href="guide/tools/preference_pages/feature_compiler.htm"/>
-	</topic>
-	<topic label="Editors Preferences" href="guide/tools/preference_pages/editors.htm"/>
-	<topic label="OSGi Frameworks Preferences" href="guide/tools/preference_pages/osgi_frameworks.htm"/>
-	<topic label="Target Platform Preferences" href="guide/tools/preference_pages/target_platform.htm">
-	</topic>
-    <topic href="reference/api-tooling/preferences/ref-errorswarnings.htm" label="API Errors and Warnings">
-    </topic>
-    <topic label="General Plug-in Development Preferences" href="guide/tools/preference_pages/plug_in_development.htm"/>
-    <topic href="reference/api-tooling/preferences/ref-baselines.htm" label="API Baselines">
-    </topic>
- </topic>
- <topic label="Property Pages">
-    <topic href="reference/api-tooling/propertypages/ref-errorswarnings-prop.htm" label="API Errors and Warnings">
-    </topic>
-    <topic href="reference/api-tooling/propertypages/ref-filters-prop.htm" label="API Problem Filters">
-    </topic>
- </topic>
- <topic label="Quickfixes">
-    <topic href="reference/api-tooling/quickfixes/ref-api-api-filter-qf.htm" label="Create API Problem Filter">
-    </topic>
-    <topic href="reference/api-tooling/quickfixes/ref-api-missing-baseline-qf.htm" label="Missing API Baseline">
-    </topic>
-    <topic href="reference/api-tooling/quickfixes/ref-api-sincetag-qf.htm" label="Since Tags">
-    </topic>
-    <topic href="reference/api-tooling/quickfixes/ref-api-version-qf.htm" label="Version Numbering">
-    </topic>
-    <topic href="reference/api-tooling/quickfixes/ref-api-remove-api-filter-qf.htm" label="Remove Unused API Problem Filters">
-    </topic>
- </topic>
-<topic label="Views" href="guide/tools/views/views.htm">
-	<topic label="Error Log" href="guide/tools/views/error_log.htm"/>
-	<topic label="Plug-in Registry" href="guide/tools/views/plugin_registry.htm"/>
-	<topic label="Plug-ins" href="guide/tools/views/plugins.htm"/>
-	<topic label="Plug-in Dependencies" href="guide/tools/views/plugin_dependencies.htm"/>
- 	<topic href="guide/tools/views/target_platform_state.htm" label="Target Platform State">
- 	</topic>
-</topic>
- <topic label="Wizards and Dialogs">
- 	<topic label="New Project Creation Wizards" href="guide/tools/project_wizards/new_project_wizards.htm">
-		<topic label="Plug-in Project" href="guide/tools/project_wizards/new_plugin_project.htm">
-			<topic label="Plug-in Project Structure" href="guide/tools/project_wizards/plugin_structure.htm"/>
-			<topic label="Plug-in Content" href="guide/tools/project_wizards/plugin_content.htm"/>
-			<topic label="Templates" href="guide/tools/project_wizards/plugin_templates.htm"/>
-		</topic>
-		<topic label="Plug-in from existing JAR archives" href="guide/tools/project_wizards/plugin_from_archives.htm"/>
-		<topic label="Fragment Project" href="guide/tools/project_wizards/new_fragment_project.htm">
-			<topic label="Fragment Project Structure" href="guide/tools/project_wizards/fragment_structure.htm"/>
-			<topic label="Fragment Content" href="guide/tools/project_wizards/fragment_content.htm"/>
-		</topic>
-		<topic label="Feature Project" href="guide/tools/project_wizards/new_feature_project.htm"/>
-		<topic label="Feature Patch" href="guide/tools/project_wizards/new_feature_patch.htm"/>
-		<topic label="Update Site Project" href="guide/tools/project_wizards/new_update_site_project.htm"/>
-	</topic>
-	<topic label="New File Creation Wizards" href="guide/tools/file_wizards/new_file_wizards.htm">
-		<topic label="Product Configuration" href="guide/tools/file_wizards/new_product_config.htm"/>
-		<topic label="Target Definition" href="guide/tools/file_wizards/new_target_definition.htm"/>
-		<topic label="Extension Point Schema" href="guide/tools/file_wizards/new_schema.htm"/>
-		<topic label="Cheat Sheet" href="guide/tools/file_wizards/new_cheat_sheet.htm"/>
-		<topic label="Table of Contents" href="guide/tools/file_wizards/new_toc.htm"/>
-  <topic href="guide/tools/file_wizards/new_category.htm" label="Category Definition">
-  </topic>
-	</topic>
-	<topic label="Import Wizards" href="guide/tools/import_wizards/import_wizards.htm">
-		<topic label="Plug-in Import" href="guide/tools/import_wizards/import_plugins.htm"/>
-		<topic label="Feature Import" href="guide/tools/import_wizards/import_features.htm"/>
-	</topic>
-	<topic label="Export Wizards" href="guide/tools/export_wizards/export_wizards.htm">
-		<topic label="Plug-in Export" href="guide/tools/export_wizards/export_plugins.htm"/>
-		<topic label="Feature Export" href="guide/tools/export_wizards/export_features.htm"/>
-		<topic label="Product Export" href="guide/tools/export_wizards/export_product.htm"/>
-	</topic>
-	<topic label="Task Wizards" href="guide/tools/pde_actions/task_wizards.htm">
-		<topic label="Converting Java Projects to Plug-in Projects" href="guide/tools/pde_actions/convert_projects.htm" />
-		<topic label="Externalizing Strings" href="guide/tools/pde_actions/externalize_strings.htm" />
-		<topic label="Organizing Manifest Files" href="guide/tools/pde_actions/organize_manifests.htm" />
-		<topic label="Updating Classpaths" href="guide/tools/pde_actions/update_classpaths.htm" />
-	</topic>
-    <topic label="API Tooling">
-	    <topic href="reference/api-tooling/wizards/ref-api-setup-wizard.htm" label="API Tooling Setup Wizard">
-	    </topic>
-	    <topic href="reference/api-tooling/wizards/ref-api-baseline-wizard.htm" label="API Baseline Wizard">
-	    </topic>
-	    <topic href="reference/api-tooling/wizards/ref-api-compare-wizard.htm" label="API Compare Wizard">
-	    </topic>
-    </topic>
-    <topic label="Target Wizards">
-       <topic href="guide/tools/target_shared/new_target_wizard.htm" label="New Target Wizard">
-       </topic>
-       <topic href="guide/tools/target_shared/edit_target_wizard.htm" label="Edit Target Wizard">
-       		<topic href="guide/tools/target_shared/edit_target_locations_tab.htm" label="Locations Tab">
-       		</topic>
-        	<topic href="guide/tools/target_shared/edit_target_content_tab.htm" label="Content Tab">
-	       </topic>
-	        <topic href="guide/tools/target_shared/edit_target_environment_tab.htm" label="Environment Tab">
-	       </topic>
-	        <topic href="guide/tools/target_shared/edit_target_arguments_tab.htm" label="Arguments Tab">
-            <topic href="guide/tools/target_shared/import_arguments_dialog.htm" label="Import Arguments Dialog">
-            </topic>
-	       </topic>
-	        <topic href="guide/tools/target_shared/edit_target_implicit_tab.htm" label="Implicit Dependencies Tab">
-            <topic href="guide/tools/target_shared/implicit_plugin_selection_dialog.htm" label="Implicit Dependencies Selection Dialog">
-            </topic>
-	       </topic>
-	       </topic>
-	       <topic href="guide/tools/target_shared/move_target_wizard.htm" label="Move Target Wizard">
-	       </topic>
-    </topic>
- </topic>
- <topic href="reference/api/overview-summary.html" label="API Reference">
-   <topic href="reference/api/org/eclipse/pde/build/package-summary.html" label="org.eclipse.pde.build">
-   </topic>
-   <topic href="reference/api/org/eclipse/pde/core/package-summary.html" label="org.eclipse.pde.core">
-   </topic>
-   <topic href="reference/api/org/eclipse/pde/core/build/package-summary.html" label="org.eclipse.pde.core.build">
-   </topic>
-   <topic href="reference/api/org/eclipse/pde/core/plugin/package-summary.html" label="org.eclipse.pde.core.plugin">
-   </topic>
-   <topic href="reference/api/org/eclipse/pde/ui/package-summary.html" label="org.eclipse.pde.ui">
-   </topic>
-   <topic href="reference/api/org/eclipse/pde/ui/launcher/package-summary.html" label="org.eclipse.pde.ui.launcher">
-   </topic>
-   <topic href="reference/api/org/eclipse/pde/ui/templates/package-summary.html" label="org.eclipse.pde.ui.templates">
-   </topic>
- </topic>
-	<topic label="Extension Points Reference" href="reference/extension-points/index.html">
-    <topic href="reference/extension-points/org_eclipse_pde_build_fetchFactories.html" label="org.eclipse.pde.build.fetchFactories">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_core_javadoc.html" label="org.eclipse.pde.core.javadoc">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_core_source.html" label="org.eclipse.pde.core.source">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_core_targets.html" label="org.eclipse.pde.core.targets">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_ui_launchShortcuts.html" label="org.eclipse.pde.ui.launchShortcuts">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_ui_newExtension.html" label="org.eclipse.pde.ui.newExtension">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_ui_osgiFrameworks.html" label="org.eclipse.pde.ui.osgiFrameworks">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_ui_pluginContent.html" label="org.eclipse.pde.ui.pluginContent">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_ui_samples.html" label="org.eclipse.pde.ui.samples">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_ui_targetProvisioners.html" label="org.eclipse.pde.ui.targetProvisioners">
-    </topic>
-    <topic href="reference/extension-points/org_eclipse_pde_ui_templates.html" label="org.eclipse.pde.ui.templates">
-    </topic>
-	</topic>
-	<topic label="Other Reference Information" href="reference/misc/index.html">
-	</topic>
- <topic href="reference/api-tooling/api_javadoc_tags.htm" label="Defining API Restrictions">
- </topic>
- <topic href="reference/api-tooling/api_since_tags.htm" label="Javadoc @since Tag Management">
- </topic>
-</toc>

diff --git a/bundles/org.eclipse.pde.doc.user/topics_Tasks.xml b/bundles/org.eclipse.pde.doc.user/topics_Tasks.xml
deleted file mode 100644
index 8e61fb2..0000000
--- a/bundles/org.eclipse.pde.doc.user/topics_Tasks.xml
+++ /dev/null

@@ -1,89 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!--
-     Copyright (c) 2005, 2008 IBM Corporation and others.
-     All rights reserved. This program and the accompanying materials
-     are made available under the terms of the Eclipse Public License v1.0
-     which accompanies this distribution, and is available at
-     http://www.eclipse.org/legal/epl-v10.html
-    
-     Contributors:
-         IBM Corporation - initial API and implementation
- -->
-
-<toc label="Tasks">
-   <topic label="PDE Build">
-	  <topic href="tasks/pde_product_build.htm" label="Automated Building of RCP applications from a product configuration file">
-	  </topic>
-	  <topic href="tasks/pde_feature_build.htm" label="Automated Building of Features">
-	  </topic>
-	  <topic href="tasks/pde_plugins_build.htm" label="Automated Building of Plug-ins">
-	  </topic>
-	  <topic href="tasks/pde_feature_generating_ant.htm" label="Generating Ant scripts from PDE">
-	  </topic>
-	  <topic href="tasks/pde_feature_generating_antcommandline.htm" label="Generating Ant scripts from scripts">
-	  </topic>
-   </topic>
-   <topic label="PDE Build Advanced Topics">
-      <topic href="tasks/pde_customization.htm" label="Customizing a Headless Build">
-      </topic>
-      <topic href="tasks/pde_custom_callbacks.htm" label="Feature and Plug-in Custom Build Steps">
-      </topic>
-      <topic href="tasks/pde_fetch_phase.htm" label="Fetching from Repositories">
-      </topic>
-      <topic href="tasks/pde_controlling_output.htm" label="Controlling the output format of the build">
-      </topic>
-      <topic href="tasks/pde_compilation_order.htm" label="Compilation Order and Parallelization">
-      </topic>
-      <topic href="tasks/pde_version_qualifiers.htm" label="Version Qualifiers">
-      </topic>
-      <topic href="tasks/pde_compilation_env.htm" label="Controlling compilation environment">
-      </topic>
-      <topic href="tasks/pde_source_generation.htm" label="Source Plug-in and Feature generation">
-      </topic>
-      <topic href="tasks/pde_individual_source.htm" label="Individual Source Bundles">
-      </topic>
-      <topic href="tasks/pde_packager.htm" label="Repackaging Eclipse Components">
-      </topic>
-      <topic href="tasks/pde_rootfiles.htm" label="Adding Files to the Root of a Build">
-      </topic>
-      <topic label="Topic">
-      </topic>
-   </topic>
-  <topic label="PDE Build Integration with p2">
-  	<topic href="tasks/pde_p2_builds.htm" label="Building p2 Repositories and products">
-  	</topic>
-  	<topic href="tasks/pde_p2_featurebuilds.htm" label="Feature builds with p2">
-  	</topic>
-  	<topic href="tasks/pde_p2_productbuilds.htm" label="Product builds with p2">
-  	</topic>
-     <topic href="tasks/pde_p2_buildtasks.htm" label="PDE/Build extensions to p2">
-     </topic>
-     <topic href="tasks/pde_p2_integration.htm" label="Integration with the 3.4 metadata generator">
-     </topic>
-     <topic href="tasks/pde_p2_featuremetadata.htm" label="Feature Metadata Layout">
-     </topic>
-     <topic href="tasks/pde_p2_reusingmetadata.htm" label="Reusing Metadata">
-     </topic>
-     <topic href="tasks/pde_p2_configuringproducts.htm" label="Configuring Products">
-     </topic>
-  </topic>
-   <topic label="PDE API Tooling">
-      <topic href="tasks/api_tooling_setup.htm" label="Setting up API Tooling">
-      </topic>
-      <topic href="tasks/api_tooling_baseline.htm" label="Setting up a baseline">
-      </topic>
-      <topic href="tasks/api_tooling_create_filters.htm" label="Creating filters">
-      </topic>
-      <topic href="tasks/api_tooling_remove_filters.htm" label="Remove filters">
-      </topic>
-      <topic href="tasks/api_tooling_options.htm" label="Changing API Tooling options">
-      </topic>
-      <topic href="tasks/api_tooling_compare_to_baseline.htm" label="Comparing to an API baseline">
-      </topic>
-   </topic>
-   <topic label="PDE UI">
-      <topic href="tasks/ui_export_install_into_host.htm" label="Export and Install Into Running Host">
-      </topic>
-   </topic>
-</toc>

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/default_style.css b/bundles/org.eclipse.pde.doc.user/whatsNew/default_style.css
deleted file mode 100644
index e485725..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/default_style.css
+++ /dev/null

@@ -1,15 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/apichanges.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/apichanges.png
deleted file mode 100644
index 8e66bec..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/apichanges.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/categorydef.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/categorydef.png
deleted file mode 100644
index e37acda..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/categorydef.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/categoryexport.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/categoryexport.png
deleted file mode 100644
index 5dcbda1..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/categoryexport.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/click-install.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/click-install.png
deleted file mode 100644
index 06032c9..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/click-install.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/dstemplate.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/dstemplate.png
deleted file mode 100644
index 140aab9..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/dstemplate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation-pref.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation-pref.png
deleted file mode 100644
index 8fed896..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation-pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation.png
deleted file mode 100644
index 6374953..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/ee-validation.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/err-warn.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/err-warn.png
deleted file mode 100644
index 1d77633..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/err-warn.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/export-options.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/export-options.png
deleted file mode 100644
index 3734dda..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/export-options.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/filter-quick-fix.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/filter-quick-fix.png
deleted file mode 100644
index c3a5ca1..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/filter-quick-fix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/installcategory.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/installcategory.png
deleted file mode 100644
index 4e14cb8..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/installcategory.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/installed.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/installed.png
deleted file mode 100644
index 24b7031..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/installed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/keypass.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/keypass.png
deleted file mode 100644
index efa73d0..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/keypass.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/menuspy.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/menuspy.png
deleted file mode 100644
index b379427..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/menuspy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/nl-fragments.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/nl-fragments.png
deleted file mode 100644
index bea68ec..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/nl-fragments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/non-ui-thread.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/non-ui-thread.png
deleted file mode 100644
index ccd962d..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/non-ui-thread.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/options-editor.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/options-editor.png
deleted file mode 100644
index fc3e61b..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/options-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-binarycycles.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-binarycycles.png
deleted file mode 100644
index 1116175..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-binarycycles.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-ds.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-ds.png
deleted file mode 100644
index 4be8af4..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-ds.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-jumpconsole.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-jumpconsole.png
deleted file mode 100644
index e8eaba4..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-jumpconsole.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-registryview.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-registryview.png
deleted file mode 100644
index d579b21..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-registryview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-versioning.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-versioning.png
deleted file mode 100644
index 6724948..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/pde-versioning.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/registryfragments.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/registryfragments.png
deleted file mode 100644
index 7e55553..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/registryfragments.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/start-levels.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/start-levels.png
deleted file mode 100644
index 78ec47b..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/start-levels.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/target-editor.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/target-editor.png
deleted file mode 100644
index 3b61fea..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/target-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/target-platform.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/target-platform.png
deleted file mode 100644
index a46f94c..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/target-platform.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/images/targetstateview.png b/bundles/org.eclipse.pde.doc.user/whatsNew/images/targetstateview.png
deleted file mode 100644
index 9a8c377..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/images/targetstateview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm b/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm
deleted file mode 100644
index ec6faa7..0000000
--- a/bundles/org.eclipse.pde.doc.user/whatsNew/pde_whatsnew.htm
+++ /dev/null

@@ -1,337 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>PDE - What's New in 3.5</title>
-<link rel="stylesheet" href="../book.css" type="text/css">
-<style type="text/css">
-td {border-top: solid thin black;}
-img[alt] {background-color:#ffdddd;}
-tr {vertical-align: top;}
-</style>
-</head>
-<body>
-<h2>What's New in 3.5 (PDE) </h2>
-<p>Here are descriptions of some of the more interesting or significant changes made to the Plug-in Development Environment (PDE) for the 3.5 release of Eclipse, grouped into:</p>
-<ul>
-  <li><a href="#ViewsAndEditors">Views and Editors</a></li>
-  <li><a href="#Export">Export</a></li>
-  <li><a href="#APITooling">API Tooling</a> </li>
-  <li><a href="#Build">Build</a></li>
-  <li><a href="#TargetPlatform">Target Platform </a></li>
-</ul>
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table cellpadding="10" cellspacing="0" width="600">
-  <tr>
-    <td colspan="2"><h2><a name="ViewsAndEditors">Views and Editors </a></h2></td>
-  </tr>
-  <tr id="pde-ds">
-    <td align="left" valign="top"><b>Declarative services editor</b></td>
-    <td valign="top">PDE has added declarative services tooling to help author service component definitions.
-      <p><img src="images/pde-ds.png" alt="Declarative Services Editor"></p></td>
-  </tr>
-  <tr id="pde.ds">
-    <td valign="top" align="left"><b>DS Tooling enhancements</b></td>
-    <td valign="top"><p>The OSGi Declarative Services (DS) tooling has been
-      enhanced to support the latest version of the DS specification. Specifically, a new <b>modified</b> attribute has been added to the component element.
-      </p>
-        <p>A new template based on a simple dictionary service has been added to 
-          showcase Declarative Services tooling. </p>
-      <p><img src="images/dstemplate.png" alt="DS Template"></p></td>
-  </tr>
-  <tr id="pde-logview">
-    <td align="left" valign="top"><b>Jump to Console from stack trace</b></td>
-    <td valign="top">The error log view has been enhanced to allow posting stack trace dumps to the <b>Console</b> view from log messages.
-      <p><img src="images/pde-jumpconsole.png" alt="Jump to Console"></p></td>
-  </tr>
-  <tr id="pde-versioning">
-    <td align="left" valign="top"><b>Versioning options</b></td>
-    <td valign="top">To help developers follow versioning best practices, PDE has expanded its compiler options
-      to include version constraint checks on imported packages, exported packages and required bundle statements.
-      <p><img src="images/pde-versioning.png" alt="Preferences &gt; Plug-in Development &gt; Compilers"></p></td>
-  </tr>
-  <tr id="pde.options.editor">
-    <td valign="top" align="left"><b>Properties editor for .options </b></td>
-    <td valign="top"><p>The standard properties file editor is now used for <code>.options</code> files in the workspace.</p>
-        <p><img src="images/options-editor.png" alt="Property file editor"></p></td>
-  </tr>
-  <tr id="pde.product.editor">
-    <td valign="top" align="left"><strong>Product editor enhancements </strong></td>
-    <td valign="top">The product editor has been enhanced to support   bundle start levels and product license information. </td>
-  </tr>
-  <tr id="pde.productosgi">
-    <td valign="top" align="left"><b>Product definition enhancements</b></td>
-    <td valign="top"><p>You can now initialize product definitions from OSGi launch configurations.</p></td>
-  </tr>
-  <tr id="pde.nl.fragments">
-    <td valign="top" align="left"><b>NL fragment generation </b></td>
-    <td valign="top"><p>A new wizard (<strong>PDE Tools -&amp; Internationalize...</strong>) supports the generation of NL fragments for plug-ins in the workspace. A project is generated for each selected plug-in containing skeleton properties files for each selected locale. The generated properties files contain the keys from each of the associated plug-in's properties files.</p>
-        <p><img src="images/nl-fragments.png" alt="Wizard to generate NL fragments" ></p></td>
-  </tr>
-  <tr id="pde.menuspy">
-    <td valign="top" align="left"><b>Plug-in Spy and menus</b></td>
-    <td valign="top"><p>View information about menus by invoking Plug-in Spy 
-      in menu introspection mode (<b>Alt+Shift+F2</b>) and selecting a menu item.
-      </p>
-        <p><img src="images/menuspy.png" alt="Menu Spy"></p></td>
-  </tr>
-  <tr id="registryview">
-    <td align="left" valign="top"><b>Plug-in Registry view enhancements </b></td>
-    <td valign="top">The <b>Plug-in Registry</b> view now supports 
-      browsing for OSGi services.
-      <p><img src="images/pde-registryview.png" alt="Browse for OSGi services using the registry view" ></p></td>
-  </tr>
-  <tr id="launch-config-startLevels">
-    <td valign="top" align="left"><b>Start levels</b></td>
-    <td valign="top">Eclipse Application launch configurations now support start 
-      levels and auto-start settings. You can specify default start levels and auto-start 
-      settings for all plug-ins in the configuration, and provide specific settings for others 
-      by selecting the plug-in in the list.
-      <p><img src="images/start-levels.png" alt="Use the Plug-ins tab to specify start levels" ></p></td>
-  </tr>
-  <tr id="junit-nonUIThread">
-    <td valign="top" align="left"><b>JUnit plug-in tests in non-UI thread</b></td>
-    <td valign="top">You can now launch JUnit Plug-in tests in a non-UI thread. A 
-      check box has been added to the Test tab to specify whether tests should run in the UI thread.
-      <p><img src="images/non-ui-thread.png" alt="Check box for non-UI thread"></p></td>
-  </tr>
-  <tr id="pde.fragments">
-    <td valign="top" align="left"><b>Fragments in the Plug-in Registry view</b></td>
-    <td valign="top"><p>The Plug-in Registry view now includes fragments. Simply expand a plug-in, and expand
-      the <b>Fragments</b> element in the tree to see all available fragments of that plug-in.
-      </p>
-        <p><img src="images/registryfragments.png" alt="Fragments"></p></td>
-  </tr>
-  <tr>
-    <td colspan="2"><h2><a name="Export">Export </a></h2></td>
-  </tr>
-  <tr id="exportInstall">
-    <td valign="top" align="left"><b> Install  into running platform</b></td>
-    <td valign="top"><p>It's simple to run and test your latest code by exporting and install plug-ins and features directly into the running workbench. Choose <strong>Install into host</strong> when exporting and 
-      specify a path in the local file system where exported artifacts can be stored (repository). You will be prompted to restart your 
-      workspace after export and install is complete. </p>
-        <p><img src="images/click-install.png" alt="Export Wizard"></p>
-      <p>Patched plug-ins will appear in the installed software list and can also be uninstalled.</p>
-      <p><img src="images/installed.png" alt="Installation Details Dialog"></p>    </td>
-  </tr>
-  <tr id="pde-binary-cycles">
-    <td valign="top" align="left"><b>Source bundles, binary cycles, and  workspace class files </b></td>
-    <td valign="top"><p>Export options have been enhanced:</p>
-      <ul>
-        <li>Generate source bundles. Select the <b>Export source</b> option and choose <b>Generate 
-        source bundles</b> from the drop down menu. A source bundle will be exported for each 
-      plug-in being exported. </li>
-        <li>Export features, plug-ins, and products with binary cycles. 
-          Binary cycles are cycles that exist in your target platform, not your workspace. This option is on by default.</li>
-        <li>Export existing class files from the workspace. When this option is checked, PDE will re-use existing class files in the workspace rather than compiling class files from source during export.</li>
-      </ul>
-    <p><img src="images/export-options.png" alt="Export Wizard Options Tab"></p></td>
-  </tr>
-  <tr id="pde.feature.categories">
-    <td valign="top" align="left"><strong>Publish feature categories</strong></td>
-    <td valign="top"><p>The new <strong>Category Definition</strong> editor can be 
-      used to assign categories to features when exporting. The category names and 
-      descriptions will then appear in software selection dialogs. First, create a category 
-      definition file via <strong>File &gt; New &gt; Other...</strong> and select<strong> Plug-in Development &gt; Category Definition.</strong> Define categories with 
-      symbolic identifiers, names, and descriptions, and then add features to each category.
-      </p>
-        <p><img src="images/categorydef.png" alt="Category Definition editor" ></p>
-      <p>When exporting your feature, specify the category file to apply when exporting 
-        via the <strong>Options</strong> tab. </p>
-      <p><img src="images/categoryexport.png" alt="Specify category file on export" ></p>
-      <p>The categories can then be seen when browsing the repository from the Install Software dialog.</p>
-      <p><img src="images/installcategory.png" alt="Install new software dialog displays exported categories"></p></td>
-  </tr>
-  <tr id="pde.keypass">
-    <td valign="top" align="left"><b>Keypass support</b></td>
-    <td valign="top"><p>The JAR signing support in PDE has been expanded to include support for keypasses.
-      </p>
-        <p><img src="images/keypass.png" alt="Keypass support"></p></td>
-  </tr>
-  <tr>
-    <td colspan="2"><h2><a name="APITooling">API Tooling </a></h2></td>
-  </tr>
-  <tr id="apiOptions">
-    <td valign="top" align="left"><b>Compatibility options </b></td>
-    <td valign="top"><p>API compatibility options have been reorganized and descriptions have been improved. The number of options has been reduced by combining related problems. For example, problems related to type parameters 
-      are now in their own group rather than being listed separately in the settings for classes, interfaces, and methods. </p>
-      <p>As well, you can be alerted to breaking API changes even if you have incremented the major version of your plug-in. The first time you change a plug-in's API in an incompatible way, problems inform you to increment the major version of your plug-in. Once you increment the major version of your plug-in, API tooling allows additional breaking API changes without warning. Use the new preference <strong>Report API breakage even if authorized by major version increment</strong> to enable this feature (on the <strong>Plug-in Development &gt; API Errors/Warnings</strong> preference page, on the <strong>API Compatibility</strong> tab). When this preference is enabled you must use API problem filters to selectively permit incompatible API changes.</p>
-      <p><img src="images/err-warn.png" alt="Preferences &gt; Plug-in Development &gt; API Errors/Warnings" ></p></td>
-  </tr>
-  <tr id="api.noextend">
-    <td valign="top" align="left"><b>@noextend restriction supported on interfaces</b></td>
-    <td valign="top"><p>API tooling now supports two restrictions on interfaces: <code>@noimplement</code> and <code>@noextend</code>. This allows an interface to be 
-      extended when it is not intended to be implemented directly. For example, a client may 
-      be permitted to subclass an existing implementation of a <code>@noimplement</code> interface and extend the base interface with extra function.</p>
-        <p>Component owners should decide where to add <code>@noextend</code> tags on existing interfaces, as this was previously implicit. To maintain the API contracts 
-          specified in 3.4, <code>@noextend</code> tags can be added to all interfaces 
-          specified as <code>@noimplement</code>. In some cases the <code>@noextend</code> restriction can be omitted, as clients that extend and implement a <code>@noimplement</code> interface will still be flagged with errors. However, if you would like to reserve the 
-          right to add constants to an API interface in the future, you must add the <code>@noextend</code> tag. This is because adding a field to an interface is binary 
-          incompatible if clients can extend or implement an interface (see <a href="http://wiki.eclipse.org/Evolving_Java-based_APIs_2#Evolving_API_Interfaces">Evolving API Interfaces</a>).<br>
-      </p></td>
-  </tr>
-  <tr id="systemLibrary">
-    <td valign="top" align="left"><b>System library validation</b></td>
-    <td valign="top">API tools can now analyze use of system libraries and create 
-      problems when code accesses members that may not be present at runtime. 
-      For example, when a plug-in specifies a required execution environment of J2SE 1.3, 
-      but the only JRE installed in the workspace for building is J2SE 1.5, it is possible to 
-      access methods that exist in J2SE 1.5, but not in J2SE 1.3. In order for the validation to work, 
-      you must install relevant execution environment descriptions from an update site.
-      <p><img src="images/ee-validation-pref.png" alt="API Errors/Warnings preference page"></p>
-      <p>The <strong>API Use</strong> tab of the <strong>API Errors/Warnings</strong> preference page displays installed execution environments. 
-        Use the &quot;install them now&quot; hyperlink to install additional environments 
-        via the software updates dialog.</p>
-      <p><img src="images/ee-validation.png" alt="Illegal access warning"></p></td>
-  </tr>
-  <tr id="api.stale.filters">
-    <td valign="top" align="left"><b>Stale  problem filters </b></td>
-    <td valign="top"><p>API tooling creates warnings for problem filters that are no longer needed. API problem filters often become stale because they are used to filter known incompatibilities between two specific releases. A quick fix is available to remove stale filters. </p>
-        <p><img src="images/filter-quick-fix.png" alt="Quick fix to remove stale filters"></p></td>
-  </tr>
-  <tr id="api.ant.tasks">
-    <td valign="top" align="left"><b>Ant tasks </b></td>
-    <td valign="top"><p>Ant tasks to perform API analysis and generate simple HTML reports are now available. These are the same Ant tasks used in the Eclipse SDK build. Documentation for each task is available in the <strong>Reference</strong> section of the <strong>Plug-in Development Environment Guide</strong>.</p>        </td>
-  </tr>
-  <tr id="pde.api.compare">
-    <td valign="top" align="left"><b>Compare APIs</b></td>
-    <td valign="top"><p>You can now view API changes relative to an API baseline. Select a project or 
-      package in the Package Explorer and choose <strong>Compare With &gt; API Baseline</strong>. 
-      Specify the API baseline you wish to compare against and press <strong>OK</strong>. 
-      The API Tooling view will summarize the API changes.
-      </p>
-          <p><img src="images/apichanges.png" alt="API Tooling view"></p></td>
-  </tr>
-  <colgroup>
-  <col width="30%">
-  <col width="70%">
-  </colgroup>
-  <tbody>
-  <tr>
-    <td colspan="2"><h2><a name="Build">Build </a></h2></td>
-  </tr>
-
-  <tr id="flattenDependencies">
-    <td width="30%" valign="top" align="left"><b>Sort plug-ins across feature boundaries</b></td>
-    <td width="70%" valign="top"><p>PDE/Build determines <a href="../tasks/pde_compilation_order.htm">compilation order</a> by sorting 
-    	plug-ins according to their dependencies. Previously, this sorting was only done within 
-    	a single feature and features were compiled depth first in the order they were included.</p>
-        Set the property:
-        <div align="center"><pre>flattenDependencies=true</pre></div>
-        in your build's configuration, and PDE/Build will instead sort plug-ins across feature boundaries.  
-        This allows you to structure your features according to the best logical groupings 
-        without restrictions imposed by compilation requirements. 	</td>
-  </tr>
-
-  <tr id="parallelCompilation">
-    <td width="30%" valign="top" align="left"><b>Parallel compilation</b></td>
-    <td width="70%" valign="top"><p>If plug-ins are sorted across feature boundaries (see above), 
-    PDE/Build can also group plug-ins allowing for parallel compilation.</p>
-    Set the property:
-    <div align="center"><pre>parallelCompilation=true</pre></div>
-    in your build's configuration, and PDE/Build will group plug-ins for parallel compilation 
-    using Ant's <tt>&lt;parallel&gt;</tt> task.  Setting the properties <tt>parallelThreadCount</tt> 
-    and <tt>parallelThreadsPerProcessor</tt> will control the corresponding attributes on the parallel task.    </td>
-  </tr>
-  <tr id="publish_p2">
-    <td valign="top" align="left"><b>Build integration with p2</b></td>
-    <td valign="top">PDE/Build has updated <a href="../tasks/pde_p2_builds.htm">integration with p2</a>.  It is now
-      able to publish metadata directly from your source instead of generating it based 
-      on binary jars.  For an existing feature or product build, set the property:
-      <pre>
-           p2.gathering = true
-     </pre>
-        <p>Setting this property will use the p2 publisher to gather up your bundle and publish it into a 
-          build specific repository.</p>
-      <p>For product builds, this will automatically perform a director install to create the final product archives.  
-        If you also set the <tt>p2.metadata.repo</tt> and <tt>p2.artifact.repo</tt> properties then build will mirror the 
-        resulting product metadata into those repositories.</p>
-      <p>For Feature builds, this will create a p2 repository for the final archive.  This also has the effect of setting <tt>groupConfigurations=true</tt> and <tt>outputUpdateJars=true</tt>.</p></td>
-  </tr>
-  <tr id="rootfile_artifacts">
-    <td valign="top" align="left"><b>Feature rootfile artifacts</b></td>
-    <td valign="top">When publishing metadata directly from source using the <tt>p2.gathering=true</tt> property, 
-      root files contributed by features will be published into the artifact repository and <a href="../tasks/pde_p2_featuremetadata.htm">associated metadata</a> will be created.
-      The result is that installing your feature will also cause the feature's root files to be installed.</td>
-  </tr>
-  <tr id="product_qualifiers">
-    <td valign="top" align="left"><b>Qualifier replacement on .product files</b></td>
-    <td valign="top"><p>When building products using <a href="../tasks/pde_p2_productbuilds.htm"><tt>p2.gathering=true</tt></a>, PDE/Build will now replace the ".qualifier" on the version specified in a .product file used
-      in a product build.  Set the property <b><tt>p2.product.qualifier</tt></b> to be the qualifier you wish to use.
-      </p>
-        <p>If no value is specified, the default will be either the value of <tt>forceContextQualifier</tt> or the default timestamp.</p>    </td>
-  </tr>
-
-  <tr id="pde-build-fetch">
-    <td width="30%" valign="top" align="left"><b>Fetch artifacts for your build using p2</b></td>
-    <td width="70%" valign="top">
-      A new extension has been added to PDE/Build that enables users to <a href="../tasks/pde_fetch_phase.htm#p2_fetch">fetch
-    	artifacts</a> from p2 repositories. You can now add an entry to your map
-    	file for build input and PDE/Build will retrieve the artifact and include it in the build.
-    	<p>
-    	The map file entry needs to include the id and version of the installable unit (IU), and
-    	the URI of the repository where the IU can be found. The metadata and 
-    	artifact repositories are assumed to be co-located. An example (needs to be on one line) is:</p>
-    	<p>
-    	<code>
-    		plugin@my.bundle.id,1.0.0=p2IU,id=my.bundle.id,version=
-    		&nbsp;&nbsp;&nbsp;1.0.0,repository=http://example.com/repo</code></p></td>
-  </tr>
-
-  <tr id="repo2runnable">
-    <td width="30%" valign="top" align="left"><b>p2 repositories as a target for PDE Build</b></td>
-    <td width="70%" valign="top"><p>
-    	You can now specify a location that contains <a href="../tasks/pde_p2_reusingmetadata.htm">local p2 repositories</a> in nested folders or zip files.
-    	The build will automatically transform the repositories into a form that PDE/Build can 
-    	compile against.</p>
-    	<p>
-    	There is a new <tt>processRepos</tt> phase in the main build script with corresponding
-    	<tt>pre</tt> and <tt>post</tt> targets in the <tt>customTargets.xml</tt> file.</p>
-    	<p>
-    	You must set these properties in the <tt>build.properties</tt> for your builder. The
-    	<tt>repoBaseLocation</tt> is the location of the folder containing the local p2 
-    	repositories. The <tt>transformedRepoLocation</tt> is the location where the transformed
-    	artifacts will be placed after being processed.</p>
-    	<p>
-    	<code>
-    	repoBaseLocation=${base}/repos<br>
-		transformedRepoLocation=${base}/transformedRepos		</code>		</p>	</td>
-	</tr>
-  <tr>
-    <td colspan="2"><h2><a name="TargetPlatform">Target Platform </a></h2></td>
-  </tr>
-
-  <tr id="pde.target.platform">
-    <td width="30%" valign="top" align="left"><strong>Target platform and target definitions </strong></td>
-    <td width="70%" valign="top"><p>The target platform preference page (<strong>Preferences
-     &gt; Plug-in Development &gt; Target Platform</strong>) has been redesigned. The page allows the user to select the active target platform from all target 
-     definitions in the workspace. 
-     Target definitions can be created and edited from this page using a wizard or with the target definition editor. You can quickly switch 
-     between targets using the checkboxes. Targets can be composed of plug-ins originating from installations, directories, features, and software sites. See <a href="../concepts/target.htm">target definition concepts</a> for more details on crafting targets. </p>
-      <p><img src="images/target-platform.png" alt="Target platform preference page"></p></td>
-  </tr>
-  <tr id="targetEditor">
-    <td valign="top" align="left"><b>Target editor enhancements</b></td>
-    <td valign="top">The target editor has been enhanced to support new features 
-      in target definitions. Targets now support installation-based locations in addition to 
-      directories and features. As well, the editor support retrieval of plug-ins from update 
-      sites. The wizards used to add content to a target definition are the same as 
-      described in the new target platform preference page (above).
-      <p><img src="images/target-editor.png" alt="Target Definition Editor"></p>
-      <p>To support new features, the underlying target file format has been enhanced. 
-        The new editor continues to read old target files, but only writes files in the new format.</p></td>
-  </tr>
-
-  <tr id="pde.target.state">
-    <td width="30%" valign="top" align="left"><b>Target platform state</b></td>
-    <td width="70%" valign="top"><p>The new <strong>Target Platform State</strong> 
-    view displays all the bundles used to build, run and debug plug-ins with. The state is 
-    built from the active target definition.</p>
-    <p><img src="images/targetstateview.png" alt="Target Platform State view" ></p></td>
-  </tr>
-  </tbody>
-</table>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/.cvsignore b/bundles/org.eclipse.platform.doc.isv/.cvsignore
deleted file mode 100644
index 4a2cb51..0000000
--- a/bundles/org.eclipse.platform.doc.isv/.cvsignore
+++ /dev/null

@@ -1,2 +0,0 @@
-bin
-platformOptions.tmp.txt

diff --git a/bundles/org.eclipse.platform.doc.isv/.project b/bundles/org.eclipse.platform.doc.isv/.project
deleted file mode 100644
index 310af89..0000000
--- a/bundles/org.eclipse.platform.doc.isv/.project
+++ /dev/null

@@ -1,22 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.platform.doc.isv</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-		<buildCommand>
-			<name>org.eclipse.pde.SchemaBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.PluginNature</nature>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs b/bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs
deleted file mode 100644
index c0d0c86..0000000
--- a/bundles/org.eclipse.platform.doc.isv/.settings/org.eclipse.pde.prefs
+++ /dev/null

@@ -1,12 +0,0 @@
-#Tue May 03 09:52:47 EDT 2005
-compilers.p.deprecated=1
-compilers.p.no-required-att=0
-compilers.p.not-externalized-att=1
-compilers.p.unknown-attribute=0
-compilers.p.unknown-class=0
-compilers.p.unknown-element=1
-compilers.p.unknown-resource=1
-compilers.p.unresolved-ex-points=0
-compilers.p.unresolved-import=0
-compilers.use-project=true
-eclipse.preferences.version=1

diff --git a/bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF b/bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF
deleted file mode 100644
index 9b8a2dc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,8 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.platform.doc.isv; singleton:=true
-Bundle-Version: 3.6.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Require-Bundle: org.eclipse.help;bundle-version="[3.2.0,4.0.0)"

diff --git a/bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt b/bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt
deleted file mode 100644
index b404738..0000000
--- a/bundles/org.eclipse.platform.doc.isv/aaa-how-to-add-things.txt
+++ /dev/null

@@ -1,3 +0,0 @@
-The information that was here has been moved to:
-
-http://wiki.eclipse.org/index.php/How_to_add_things_to_the_Eclipse_doc
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/about.html b/bundles/org.eclipse.platform.doc.isv/about.html
deleted file mode 100644
index 7501377..0000000
--- a/bundles/org.eclipse.platform.doc.isv/about.html
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"  xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>June 2, 2006</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise 
-indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available 
-at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is 
-being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was 
-provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/book.css b/bundles/org.eclipse.platform.doc.isv/book.css
deleted file mode 100644
index c65a811..0000000
--- a/bundles/org.eclipse.platform.doc.isv/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/build.properties b/bundles/org.eclipse.platform.doc.isv/build.properties
deleted file mode 100644
index 4ffe955..0000000
--- a/bundles/org.eclipse.platform.doc.isv/build.properties
+++ /dev/null

@@ -1,33 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2008 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-customBuildCallbacks=customBuildCallbacks.xml
-
-bin.includes = META-INF/,\
-               about.html,\
-               book.css,\
-               guide/,\
-               notices.html,\
-               plugin.properties,\
-               plugin.xml,\
-               porting/,\
-               questions/,\
-               reference/,\
-               samples/,\
-               schema.css,\
-               toc.xml,\
-               topics_Guide.xml,\
-               topics_Porting.xml,\
-               topics_Questions.xml,\
-               topics_Reference.xml,\
-               topics_Samples.xml,\
-               workbench.png,\
-               whatsNew/,\
-               index*/

diff --git a/bundles/org.eclipse.platform.doc.isv/buildDoc.xml b/bundles/org.eclipse.platform.doc.isv/buildDoc.xml
deleted file mode 100644
index 3706821..0000000
--- a/bundles/org.eclipse.platform.doc.isv/buildDoc.xml
+++ /dev/null

@@ -1,136 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<project name="Platform Doc Isv Build" default="all"  basedir="." >
-
-	<target name="init">
-		<available file="${basedir}/index" property="index.present"/>
-	</target>
-
-	<target name="all" depends="init" unless="index.present">
-		<antcall target="convertSchemaToHtml" />
-		<antcall target="examplesDocCopy" />
-		<antcall target="generateJavadoc" />
-		<antcall target="build.index" />
-		<!--antcall target="createDocZip" /-->
-	</target>
-
-
-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.jdt.doc.isv" if="eclipse.running">
-		<help.buildHelpIndex manifest="${basedir}/plugin.xml" destination="${basedir}"/>
-	</target>
-
-	<target name="convertSchemaToHtml" if="eclipse.running">
-		<property name="dest" value="reference/extension-points" />
-
-		<record name="${basedir}/platformconvert.txt" action="start"/>
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ant.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ant.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.compare/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.contenttype/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.expressions/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.filebuffers/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.filesystem/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.resources/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.runtime/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.core.variables/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.debug.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.debug.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.equinox.preferences/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.equinox.app/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.equinox.http.registry/plugin.xml" destination="${dest}" />
-        <pde.convertSchemaToHTML manifest="../org.eclipse.equinox.registry/plugin.xml" destination="${dest}" /> 
-        <pde.convertSchemaToHTML manifest="../org.eclipse.equinox.security/plugin.xml" destination="${dest}" /> 
-		<pde.convertSchemaToHTML manifest="../org.eclipse.help/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.help.base/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.help.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.help.webapp/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ltk.core.refactoring/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ltk.ui.refactoring/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.search/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.team.core/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.team.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.browser/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.cheatsheets/plugin.xml" destination="${dest}" />
-		<!--copy extra files linked to by generated extension point doc-->
-		<copy file="../org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.html" todir="${dest}"/>
-		<copy file="../org.eclipse.ui.cheatsheets/schema/cheatSheetContentFileSpec.exsd" todir="${dest}"/>
-		<copy file="../org.eclipse.ui.cheatsheets/schema/compositeContentFile.html" todir="${dest}"/>
-		<copy file="../org.eclipse.ui.cheatsheets/schema/compositeContentFile.exsd" todir="${dest}"/>
-		
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.console/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.editors/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.externaltools/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.ide/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.intro/plugin.xml" destination="${dest}" />
-		<!--copy extra HTML file linked to by generated extension point doc-->
-		<copy file="../org.eclipse.ui.intro/schema/introContentFileSpec.html" todir="${dest}"/>
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.navigator/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.views.properties.tabbed/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.ui.workbench.texteditor/plugin.xml" destination="${dest}" />
-		<pde.convertSchemaToHTML manifest="../org.eclipse.update.core/plugin.xml" destination="${dest}" />
-		<record name="${basedir}/platformconvert.txt" action="stop"/>
-	</target>
-
-	<target name="examplesDocCopy" >
-		<copy todir="samples">
-			<fileset dir="..">
-				<include name="org.eclipse.compare.examples/doc-html/"/>
-				<include name="org.eclipse.compare.examples.xml/doc-html/"/>				
-				<include name="org.eclipse.swt.examples/doc-html/"/>
-				<include name="org.eclipse.swt.examples.browser/doc-html/"/>
-				<include name="org.eclipse.swt.examples.controls/doc-html/"/>
-				<include name="org.eclipse.swt.examples.launcher/doc-html/"/>
-				<include name="org.eclipse.swt.examples.layouts/doc-html/"/>
-				<include name="org.eclipse.swt.examples.ole.win32/doc-html/"/>
-				<include name="org.eclipse.swt.examples.paint/doc-html/"/>
-				<include name="org.eclipse.ui.examples.fieldassist/doc-html/"/>
-				<include name="org.eclipse.ui.examples.javaeditor/doc-html/"/>
-				<include name="org.eclipse.ui.examples.multipageeditor/doc-html/"/>
-				<include name="org.eclipse.ui.examples.propertysheet/doc-html/"/>
-				<include name="org.eclipse.ui.examples.readmetool/doc-html/"/>
-				<include name="org.eclipse.ui.examples.undo/doc-html/"/>
-				<include name="org.eclipse.team.examples.filesystem/doc-html/"/>
-			</fileset>
-		</copy>
-	</target>
-
-	<target name="getJavadocPath">
-		<available file="${java.home}/../bin/javadoc.exe" property="javadoc" value="${java.home}/../bin/javadoc.exe"/>
-		<available file="${java.home}/../bin/javadoc" property="javadoc" value="${java.home}/../bin/javadoc" />
-	</target>
-
-	<target name="generateJavadoc" depends="getJavadocPath" if="javadoc">
-
-		<property name="optionsFile" value="platformOptions.tmp.txt" />
-		<copy file="platformOptions.txt" tofile="${optionsFile}" overwrite="true" />
-		
-		<condition property="argsListDelimiter" value=":">
-			<os family="unix" />
-		</condition>
-		<condition property="argsListDelimiter" value=";">
-			<os family="windows" />
-		</condition>
-		
-		<replaceregexp file="${basedir}/${optionsFile}" flags="g" match="(\r\n?|\n);" replace="${argsListDelimiter}" />
-		<replace file="${basedir}/${optionsFile}" token="@rt@" value="${bootclasspath}" />
-
-		<!--scrub isv plugin directories of any preexisting api doc content-->
-		<delete dir="reference/api"/>
-		<mkdir dir="reference/api"/>
-
-		<exec dir="." executable="${javadoc}" output="doc.bin.log">
-			<arg line="@${basedir}/${optionsFile} -J-Xmx1000M" />
-		</exec>
-		
-		<!--workaround for bug 101048-->
-		<replace dir="reference/api" token="=&quot;/../misc/api-usage-rules.html" value="=&quot;./../misc/api-usage-rules.html">
-			<include name="*htm*" />
-		</replace>
-
-	</target>
-
-	<target name="createDocZip">
-		<zip zipfile="${basedir}/doc.zip" basedir="${basedir}" includes="book.css, notices.html, about.html, concepts/**, gettingStarted/**, images/**, reference/**, porting/**, tasks/**,samples/**,guide/**,questions/**" />
-	</target>
-</project>
-

diff --git a/bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml b/bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml
deleted file mode 100644
index 4974688..0000000
--- a/bundles/org.eclipse.platform.doc.isv/customBuildCallbacks.xml
+++ /dev/null

@@ -1,151 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- ===================================================================== -->
-<!-- Custom targets called from a project's generated build.xml            -->
-<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.-->
-<!-- ===================================================================== -->
-<project name="Build specific targets and properties" default="noDefault">
-
-	<!-- ===================================================================== -->
-	<!-- Default target                                                        -->
-	<!-- ===================================================================== -->
-	<target name="noDefault">
-		<echo message="This file must be called with explicit targets" />
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.jars                              -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.jars">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.jars                               -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.jars">
-		<ant antfile="buildDoc.xml" />
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.sources                            -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the compilation target <name>                      -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   source.foldern : n = 1 ... N, the source folders                    -->
-	<!--   target.folder  : where the results of the compilation go            -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="pre.activeHelpSample.jar">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after compilation but before jaring					   -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   source.foldern : n = 1 ... N, the source folders                    -->
-	<!--   target.folder  : where the results of the compilation go            -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="post.compile.activeHelpSample.jar">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the compilation target <name>                       -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   jar.location - the location of the compilation results              -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="post.activeHelpSample.jar">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.bin.parts                        -->
-	<!-- Available parameters :                                                -->
-	<!--  destination.temp.folder - the directory plugins will be collected to -->
-	<!--  feature.directory - the directory containing the resulting feature   -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.bin.parts">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.bin.parts                         -->
-	<!-- Available parameters :                                                -->
-	<!--   base.dir - root of the project                                      -->
-	<!--   build.result.folder - folder containing the build results           -->
-	<!--   target.folder - destination folder                                  -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.bin.parts">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.sources                          -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.logs                             -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.logs">        
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.logs                              -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.logs">       
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target clean                                   -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.clean">              
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target clean                                    -->
-	<!-- Available parameters :                                                -->
-	<!--   plugin.destination - final destination of the build                 -->
-	<!--   build.result.folder - results of the compilation                    -->
-	<!--   temp.folder - temporary folder                                      -->
-	<!-- ===================================================================== -->
-	<target name="post.clean">             
-	</target>
-</project>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant.htm
deleted file mode 100644
index 026af8f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Platform Ant support
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Platform Ant support</h1>
-<p>Ant is a Java-based build tool that uses XML-based configuration files to
-describe build tasks.&nbsp; The Eclipse platform allows you to run Ant buildfiles
-from your plug-in and contribute new Ant <a href="../reference/extension-points/org_eclipse_ant_core_antTasks.html">tasks</a>, 
-<a href="../reference/extension-points/org_eclipse_ant_core_antTypes.html">types</a> and
-<a href="../reference/extension-points/org_eclipse_ant_core_antProperties.html">properties</a>
-using extension points.&nbsp; The rest of this discussion assumes that you have a basic
-understanding of Ant.</p>
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm
deleted file mode 100644
index c72579a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_contributing_task.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing tasks and types
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Contributing tasks and types</h2>
-<p>When your plug-in contributes Ant tasks and types, the tasks and types have access to all
-of the classes inside the contributing plug-in. For example, the <b>eclipse.refreshLocal</b> task 
-contributed by <b>org.eclipse.core.resources</b> plug-in is 
-a wrapper for the
-<a href="../reference/api/org/eclipse/core/resources/IResource.html#refreshLocal(int, org.eclipse.core.runtime.IProgressMonitor)">
-<b>
-IResource.refreshLocal()</b></a> method.</p>
-
-
-<p>Tasks and types contributed by plug-ins must not be placed in any of the 
-plug-in libraries. They have to be in a separate JAR. This means that the
-plug-in classes do not have access to the tasks and types provided by the 
-plug-in.&nbsp; (See 
-<a href="#jar">Why a separate JAR for tasks and types</a>?
-for more information.)</p>
-
-
-<p> The <b><a href="../reference/extension-points/org_eclipse_ant_core_antTasks.html">org.eclipse.ant.core.antTasks</a></b> extension point provides an example of how to specify
-a new task 
-in the <b>plugin.xml</b> file.</p>
-
-
-<A NAME="monitor"></A><h3>
-Progress Monitors</h3>
-<P >
-The Eclipse Ant support provides access to an <a href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">
-<b>
-IProgressMonitor</b></a> if one is passed when invoking the AntRunner. One of the advantages of having access to a progress
-monitor is that a long-running task can check to see if the user has requested its cancellation. The progress
-monitor object is obtained from the Ant project's references.&nbsp; Note that a monitor is only made available if
-the method <a href="../reference/api/org/eclipse/ant/core/AntRunner.html#run(org.eclipse.core.runtime.IProgressMonitor)">
-<b>
-AntRunner.run(IProgressMonitor)</b></a> was called with a valid progress monitor. The following code snippet
-shows how to obtain a progress monitor from the task's project:
-</P>
-<pre>import org.apache.tools.ant.BuildException;
-import org.apache.tools.ant.Task;
-import org.eclipse.ant.core.AntCorePlugin;
-import org.eclipse.core.runtime.IProgressMonitor;
-
-public class CoolTask extends Task {
-
-public void execute() throws BuildException {
-<b>	IProgressMonitor monitor = 
-		(IProgressMonitor) getProject().getReferences().get(AntCorePlugin.ECLIPSE_PROGRESS_MONITOR);
-</b>	if (monitor == null) {
-		...
-	} else {
-		...
-	}
-}
-}
-</pre>
-
-
-<h3 >
-Important rules when contributing tasks and types</h3>
-
-
-<p>
-The following should work as a checklist for plug-in developers:</p>
-<ul>
-  <li>The JAR containing the tasks must not be a plug-in library (declared in 
-  &lt;library&gt;&lt;/library&gt;).</li>
-  <li>The task or type can reference any class available for the plug-in but 
-  plug-in classes must not access the tasks or types.</li>
-  <li>Native libraries should be loaded by the plug-in library classes and not tasks or types.</li>
-</ul>
-
-
-<A NAME="jar"></A>
-<h3>Why a separate JAR for tasks and types?</h3>
-<p>
-There are basically two requirements for running Ant in Eclipse that do not fit
-the plug-in model very well:</p>
-<ul>
-  <li>Change the Ant classpath at runtime</li>
-  <li>Change the Ant version at runtime</li>
-</ul>
-<p>
-During runtime plug-in classloaders cannot have their classpaths expanded and
-plug-ins cannot change their dependencies. At the same time having separate
-JARs for the tasks and types is a good isolation from the plug-in classloading
-mechanism. Having these extra JARs declared by a plug-in permits adding the
-contributing plug-in to the Ant classpath as well.
-</p>
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm
deleted file mode 100644
index 71e4115..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_developing.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Developing tasks and types
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Developing Ant tasks and types within Eclipse</h2>
-<p>
-  Ant tasks and types must be loaded by an Ant classloader instead of a plug-in
-  classloader. This can cause problems when developing and testing new tasks and types
-  to be run in the same VM as Eclipse. To avoid these issues, it is necessary
-  to store the tasks and types in a location that is not visible to any plug-in
-  classloader.</p>
-<p>
-  The following guidelines should be followed when developing and 
-  debugging new tasks and types to be run within the same VM as Eclipse.</p>
-<ul>
-  <li> Contributed Ant tasks or types should be defined in their own source folder 
-    within a plug-in (i.e. separate from the source folders containing regular 
-    plug-in classes)</li>
-  <li>Each source folder containing the Ant tasks and types should have its own 
-    output location that does not overlap with the output location of the regular 
-    plug-in classes.</li>
-  <li>When testing/debugging the new Ant tasks or types using PDE Launch,
-  additional configuration is required:
-  <ul>
-  <li>the project contributing
-    the Ant tasks or types must be configured to <b>exclude</b> the output folders 
-    containing the Ant tasks and types. Use the <b>Properties</b> dialog for the project to
-    correctly configure the <b>Plug-in Development &gt; Runtime Classpath</b> by removing the Ant output 
-    directories from the plug-ins classpath.</li>
-  <li>The JAR file containing the Ant tasks and types and specified
-  in the org.eclipse.ant.core.extraClasspathEntries extension,
-  must be built manually, or using an external tool builder.
-  </li>
-  </ul>
-  </li>
-</ul>
-<p>
-  The <code>org.eclipse.ant.core</code> plugin can be used as an example of how to set up a plugin that contributes tasks within Eclipse. 
- For development and testing of this plugin within Eclipse, an external tool builder
- explictly generates the tasks JAR when triggered on specific resource changes.
-</p>  
-
-<p>Also see <a href="ant_contributing_task.htm">Contributing tasks and types</a>.</p>
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm
deleted file mode 100644
index cf5059c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_eclipse_tasks.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Ant tasks provided by the platform
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Ant tasks provided by the platform</h2>
-<p>The platform provides some useful Ant tasks and properties that 
-interact with the workspace. They can be used with buildfiles that are set to build within the same JRE as the workspace.</p>
-
-
-<A NAME="monitor"></A><h3>
-eclipse.refreshLocal</h3>
-<p>
-This task is a wrapper to the <a href="../reference/api/org/eclipse/core/resources/IResource.html#refreshLocal(int, org.eclipse.core.runtime.IProgressMonitor)">
-<b>
-IResource.refreshLocal()</b></a> method. Example:</p>
-<pre>&lt;eclipse.refreshLocal resource=&quot;MyProject/MyFolder&quot; depth=&quot;infinite&quot;/&gt;</pre>
-<ul>
-  <li> <b>resource</b> is a resource path relative to the workspace&nbsp;</li>
-  <li> 
-<b>depth</b> can be one of the following: <b>zero</b>, <b> one</b> or <b>infinite</b></li>
-</ul>
-<h3 >
-eclipse.incrementalBuild</h3>
-
-<p>
-When the <b>project</b> attribute is supplied, this task is a wrapper to<b>
-<a href="../reference/api/org/eclipse/core/resources/IProject.html#build(int, org.eclipse.core.runtime.IProgressMonitor)">
-IProject.build()</a></b>.  Otherwise, this task is a wrapper to the method:<b>
-<a href="../reference/api/org/eclipse/core/resources/IWorkspace.html#build(int, org.eclipse.core.runtime.IProgressMonitor)">
-IWorkspace.build()</a></b>.
-</p>
-<p>
-Examples:
-</p>
-<pre>&lt;eclipse.incrementalBuild/&gt;</pre>
-
-<pre>
-&lt;eclipse.incrementalBuild project=&quot;MyProject&quot; kind=&quot;incremental&quot;/&gt;
-</pre>
-
-<ul>
-  <li> <b>project</b> the name of the project to be built</li>
-  <li> <b>kind</b> the kind of build to perform. Possible values include:
-  <ul>
-  	<li><b>"incremental"</b> to perform an incremental build</li>
-  	<li><b>"full"</b> to discard existing builder state and rebuild everything from scratch</li>
-  	<li><b>"clean"</b> to discard existing builder state but not rebuild</li>
-  </ul>
-  </li>
-  <li> <b>builder</b> the name of the builder to run; If this value is not specified
-	  all builders are run</li>
-</ul>
-
-<h3>eclipse.convertPath</h3>
-
-<p>
-Converts a file system path to a resource path or vice-versa. The resulting value is
-assigned to the given property. The <b>property</b> attribute must be specified, as well as
-either the <b>fileSystemPath</b> or <b>resourcePath</b> attribute.  When 
-a file system path is supplied, this task is a wrapper to
-<b>
-<a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html#getContainerForLocation(org.eclipse.core.runtime.IPath)">
-IWorkspaceRoot.getContainerForLocation(IPath)</a></b>.  When a resource path
-is supplied, this task is a wrapper to
-<b>
-<a href="../reference/api/org/eclipse/core/resources/IResource.html#getLocation()">IResource.getLocation()</a></b>.
-</p>
-<p>
-Examples:</p>
-
-<pre>&lt;eclipse.convertPath fileSystemPath=&quot;${basedir}&quot; property=&quot;myPath&quot;/&gt;</pre>
-
-<pre>&lt;eclipse.convertPath resourcePath=&quot;MyProject/MyFile&quot; property=&quot;myPath&quot;/&gt;</pre>
-
-<br>
-
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm
deleted file mode 100644
index a241393..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_expanding_classpath.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Expanding the Ant classpath
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Expanding the Ant classpath</h2>
-<p>Plug-ins can contribute 
-<a href="../reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html">extra JAR files</a> 
-to the Ant classpath. The plug-in contributing the JARs is added to the Ant classpath, and as a result,
-classes inside the contributed JAR files will have access to all classes available to the plug-in. However, the 
-reverse is not true. Since the contributed JAR files must be separate JARs, and not plug-in libraries,
-the plug-in classes do not have access to the classes provided by the contributed JARs. The
-<a href="../reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html">
-<b>org.eclipse.ant.core.extraClasspathEntries</b></a> extension point provides an example of how to specify the extra JARs 
-in the plugin.xml file.</p>
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm b/bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm
deleted file mode 100644
index 160944e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ant_running_buildfiles_programmatically.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Running Ant buildfiles programmatically
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Running Ant buildfiles programmatically</h2>
-<p>
-The Ant support built into Eclipse allows plug-ins to programmatically run Ant buildfiles.
-This is done via the <a href="../reference/api/org/eclipse/ant/core/AntRunner.html"><b>AntRunner</b></a> 
-class included in the <b> org.eclipse.ant.core</b> plug-in.
-</p>
-
-<p>The following code snippet shows an example of how to use the <a href="../reference/api/org/eclipse/ant/core/AntRunner.html"><b>AntRunner</b></a> from within code of another plug-in:</p>
-
-<pre>import org.eclipse.ant.core.AntRunner;
-import org.eclipse.core.runtime.IProgressMonitor;
-
-...
-
-public void runBuild() {
-	IProgressMonitor monitor = ...
-	AntRunner runner = new AntRunner();
-	runner.setBuildFileLocation(&quot;c:/buildfiles/build.xml&quot;);
-	runner.setArguments(&quot;-Dmessage=Building -verbose&quot;);
-	runner.run(monitor);
-}</pre>
-
-<p>If a progress monitor is used, it is made available for the running tasks.
-See <a href="./ant_contributing_task.htm#monitor">Progress Monitors</a> for more details.
-</p><p>Note that only one Ant build can occur at any given time if the builds do not occur in separate VMs. See <a href="../reference/api/org/eclipse/ant/core/AntRunner.html#isBuildRunning()">
-AntRunner.isBuildRunning()</a>;
-</p>
-
-<h3>
-Special care for native libraries if build occurs within the same JRE as the workspace</h3>
-<P >
-Every time an Ant buildfile runs in Eclipse a new classloader is created. Since a library can only be
-loaded by one classloader in Java, tasks making use of native libraries could run into problems during
-multiple buildfile runs. If the previous classloader has not been garbage collected at the time the new
-classloader tries to load the native library, an exception is thrown indicating the problem and the
-build fails. One way of avoiding this problem is having the library load be handled by
-a class inside a plug-in library. The task can make use of that class for accessing native
-methods. This way, the library is loaded by the plug-in classloader and it does not run into the
-load library conflict.
-</P>
-
-
-<P >
-&nbsp;</P>
-
-
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/arch.htm b/bundles/org.eclipse.platform.doc.isv/guide/arch.htm
deleted file mode 100644
index 881a6ea..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/arch.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Platform architecture 
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Platform architecture </h1>
-
-<p>The Eclipse platform is structured around the concept of <b>plug-ins</b>.  Plug-ins are
-structured bundles of code and/or data that contribute function to the system.  Function can be
-contributed in the form of code libraries (Java classes with public API), platform <b>extensions</b>,
-or even documentation.  Plug-ins can define <b>extension points</b>, well-defined places 
-where other plug-ins can add functionality.</p>
-
-<p>Each subsystem in the platform is itself structured as a set of plug-ins that implement
-some key function.  Some plug-ins add visible features to the platform using the extension model.
-Others supply class libraries that can be used to implement system extensions.</p>
-
-<p>The Eclipse SDK includes the basic platform plus two major tools that are
-useful for plug-in development.&nbsp; The Java development tools (JDT)
-implement a full featured Java development environment.&nbsp; The Plug-in
-Developer Environment (PDE) adds specialized tools that streamline the
-development of plug-ins and extensions.</p>
-
-<p>These tools not only serve a useful purpose, but also provide a great example of
-how new tools can be added to the platform by building plug-ins that extend the
-system.</p>
-
-<p><img border="0" src="images/sdk-arch.jpg"  alt="line drawing of the architecture of the sdk"></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm b/bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm
deleted file mode 100644
index 5973848..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/arch_struct.htm
+++ /dev/null

@@ -1,125 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Platform SDK roadmap</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Platform SDK roadmap</H2>
-
-<H3>Runtime core</H3>
-
-<P >
-The platform runtime core implements the runtime engine that starts the platform base and dynamically discovers and runs plug-ins. A
-<b> plug-in</b> is a structured component that describes itself to the system using
-an OSGi manifest (<b>MANIFEST.MF</b>) file and a plug-in manifest
-(<b>plugin.xml</b>) file. The platform maintains a registry of installed plug-ins and the function they provide.</P>
-
-<P >
-A general goal of the runtime is that the end user should not pay a memory or performance penalty for plug-ins that are installed, but not used. A plug-in can be installed and added to the registry, but the plug-in will not be activated unless
-a function provided by the plug-in has been requested according to the user's activity.</P>
-<P>The platform runtime is implemented using the OSGi services model. While implementation details of the runtime may not be 
-important to many application developers, those already familiar with OSGi will recognize that an Eclipse plug-in is, in effect,
-an OSGi bundle.</P>
-<P >
-The best way to get a feel for the runtime system is to build a plug-in. See
-<a HREF="firstplugin.htm" CLASS="XRef"> Plug it in: Hello World meets the workbench</a> to get started
-building a plug-in.  To understand the nuts and bolts of the runtime system, see 
-<a HREF="runtime.htm">Runtime overview</a>.</P>
-
-<H3>
-Resource management</H3>
-<P >
-The resource management plug-in defines a common resource model for managing the
-artifacts of tool plug-ins. Plug-ins can create and modify <b>projects</b>, <b>folders</b>, and 
-<b>files</b> for organizing and storing development artifacts on disk.</p>
-<P >
-<a HREF="resInt.htm" CLASS="XRef">Resources overview</a> provides an overview of the resource management system.</P>
-
-
-<H3>
-Workbench UI</H3>
-<P >
-The workbench UI plug-in implements the workbench UI and defines a number of extension points that allow 
-other plug-ins to contribute menu and toolbar actions, drag and drop operations, dialogs, wizards, 
-and custom views and editors.</P>
-<P >
-<a HREF="workbench.htm" CLASS="XRef">Plugging into the workbench</a> introduces the workbench
-UI extension points and API.</P>
-<P >
-Additional UI plug-ins define frameworks that are generally useful for user
-interface development.&nbsp; These frameworks were used to develop the workbench
-itself.&nbsp; Using the frameworks not only eases the development of a plug-in's
-user interface, but ensures that plug-ins have a common look and feel and a consistent 
-level of workbench integration.
-</P>
-
-<P >
-The Standard Widget Toolkit (SWT) is a low-level, operating system independent toolkit that supports platform integration and portable API.
-It is described in
-<a HREF="swt.htm" CLASS="XRef">Standard Widget Toolkit</a>.</P>
-<P >
-The JFace UI framework provides higher-level application constructs for supporting dialogs, wizards, actions, user preferences, and widget management.&nbsp;
-The functionality in JFace is described in
-<a HREF="dialogs.htm" CLASS="XRef"> Dialogs and wizards</a> and
-<a HREF="jface.htm" CLASS="XRef">JFace: UI framework for plug-ins</a>.</P>
-
-<H3>Team support</H3>
-<p>
-The Team plug-ins allow other plug-ins to define and register implementations
-for team programming, repository access, and versioning.&nbsp; The Eclipse SDK
-includes a CVS plug-in that uses the team support to provide CVS client support
-in the SDK.&nbsp;&nbsp;</p>
-
-<p>Team support is described in <a href="team.htm">Team support</a>.</p>
-
-<H3>Debug support</H3>
-<p>
-The Debug plug-ins allow other plug-ins to implement language specific program
-launchers and debuggers.&nbsp;</p>
-
-<p>Debug support is described in <a href="debug.htm">Program debug and launching
-support</a>.</p>
-
-<h3 >
-Help System</h3>
-<P >The Help plug-in implements a platform optimized help web server and
-document integration facility.&nbsp; It defines extension points that plug-ins
-can use to contribute help or other plug-in documentation as browsable
-books.&nbsp; The documentation web server includes special facilities to allow
-plug-ins to reference files by using logical, plug-in based URLs instead of file
-system URLs.</P>
-
-<P >Additional features are provided for integrating help topics in product
-level documentation configurations.</P>
-<P >The help facility is described in <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/concepts/help.htm">Plugging in help</a>.</P>
-
-<H3>
-Java development tools (JDT)</H3>
-<P >
-The Java development tools (JDT) plug-ins extend the platform workbench by
-providing specialized features for editing, viewing, compiling, debugging, and
-running Java code.</P>
-<P >The JDT is installed as a set of plug-ins that are included in the SDK.&nbsp;
-The Java development user guide describes how to use the Java tools.&nbsp; The JDT Plug-in
-Developer Guide describes the structure and API of the JDT.</P>
-
-<H3>
-Plug-in Development Environment (PDE)</H3>
-<P >The Plug-in Development Environment (PDE) supplies tools that automate the
-creation, manipulation, debugging, and deploying of plug-ins.&nbsp; </P>
-<P >The PDE is installed as a set of plug-ins that are included in the
-SDK.&nbsp; The PDE Guide describes how to use the environment.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/bundle_security.html b/bundles/org.eclipse.platform.doc.isv/guide/bundle_security.html
deleted file mode 100644
index fe4d97d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/bundle_security.html
+++ /dev/null

@@ -1,117 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Security: Protecting against malicious code</title>
-</head>
-<BODY BGCOLOR="#ffffff">
-
-<h1>Signed bundles and protecting against malicious code</h1>
-
-<h2>Overview</h2>
-
-<p>The Eclipse platform faces a problem common to any program that can be extended by executable code: the potential that the extension code
- may be malicious. To address this concern, Eclipse embraces and extends the facilities built into the Java runtime in order to do two things:</p>
-
-<ol>
-<li>Authenticate the source of executable code in bundles</li>
-<li>Authorize the installation and runtime behaviour of code</li>
-</ol>
-
-<h2>Authenticating code packaged in a bundle</h2>
-
-<p>The first step towards protecting the platform from malicious code is 'authentication', or proving the identity of the person who is distributing the code in a bundle. This is facilitated by the use of a Public Key Infrastructure (PKI), where users are issued public certificates and private keys that uniquely identify them. Another common and well know use of certificates is the SSL protocol by which secured web sites are accessed.</p>
-
-<p>The mechanism by which the authentication step is enabled is through the use of 'digital signatures' created by the code distributor, using a private key and a process called 'signing'. When consuming code and validating the identity of the code signer, the digital signatures are input - along with the signers public key - to an inverse process called 'verifying'.</p>
-
-<p>In the Java platform, digital signatures are built into the Jar packaging format. A signed jar contains additional files alongside the META-INF\MANIFEST.MF that contain the information required to verify the signature, specifically a signature file (&lt;SIGNERNAME&gt;.SF) containing cryptographic digests of the resources contained in the Jar, and a block file (&lt;SIGNERNAME&gt;.RSA or &lt;SIGNERNAME&gt;.DSA) containing the signature data and associated certificates.</p>
-
-<p>Using this information, one can verify that specific resources in a Jar file have not been tampered with and also establish the identity of the signer. The runtime then determines the 'trustedness' of the signer, the default behaviour being to check for the presence of the signer certificate (or one of its ancestor certificates) in the JRE's 'cacerts' file.</p>
-
-<p>For more general information on PKI, Certificates, Digests, and Signatures:</p>
-<ul>
-<li><a href="http://en.wikipedia.org/wiki/Public_key">http://en.wikipedia.org/wiki/Public_key</a></li>
-<li><a href="http://en.wikipedia.org/wiki/Digital_signature">http://en.wikipedia.org/wiki/Digital_signature</a></li>
-<li><a href="http://en.wikipedia.org/wiki/Hash_algorithm">http://en.wikipedia.org/wiki/Hash_algorithm</a></li>
-</ul>
-
-<p>For more specific information on signing in the Java platform:</p>
-<ul>
-<li><a href="http://java.sun.com/docs/books/tutorial/deployment/jar/signindex.html">http://java.sun.com/docs/books/tutorial/deployment/jar/signindex.html</a></li>
-<li><a href="http://www.ibm.com/developerworks/library/j-jar/index.html">http://www.ibm.com/developerworks/library/j-jar/index.html</a></li>
-<li><a href="http://www.onjava.com/pub/a/onjava/2001/04/12/signing_jar.html?page=1">http://www.onjava.com/pub/a/onjava/2001/04/12/signing_jar.html?page=1</a></li>
-</ul>
-
-<h2>Signing code packaged in a bundle</h2>
- 
-<p>In order to sign a bundle, an Eclipse developer has a handful of options:</p>
-
-<ol>
-<li>The Java command line tool, 'jarsigner'
-
-<p>Jarsigner is a tool that ships with the Java SDK, and can be used to generate signatures on Jar files. For more information see the SDK documentation at:</p>
-<p>
-<a href="http://java.sun.com/j2se/1.3/docs/tooldocs/win32/jarsigner.html">http://java.sun.com/j2se/1.3/docs/tooldocs/win32/jarsigner.html</a></p>
-</li>
-<li>A custom ant task, &lt;signjar&gt;
-
-<p>The 'Ant' build tool has a built-in task for automating the signing of code. For more information, see the related Ant documentation at:</p>
-<p>
-<a href="http://ant.apache.org/manual/CoreTasks/signjar.html">http://ant.apache.org/manual/CoreTasks/signjar.html</a></p>
-</li><li>The Eclipse 'export deployable plug-ins and fragments' functionality
-
-<p>Eclipse ships with the ability to export Eclipse plug-ins  and sign them at the same time. When exporting deployable plug-ins and fragments, there is a JAR Signing tab available. In the tab, the exporter can specify a KeyStore (a password-protected key storage) containing a private key to use for the signing.</p>
-</li>
-</ol>
-
-<h2>Verifying signed code packaged in a bundle</h2>
- 
-<p>As with generation of signed bundles, verification of signed code can be done by an Eclipse developer in several ways:</p>
-
-<ol>
-<li>The command line, 'jarsigner'
-
-<p>The Jarsigner tool is also capable of verifying signatures when passed a -verify option. For more information, consult the Java SDK documentation.</p>
-
-</li>
-<li>Programmatically via the core Java APIs.
-
-<p>There are several APIs in the Java API which allow interaction with signed Jars. For example, the java.util.JarFile API can be passed a parameter which enables verification of signatures. Several consumers of this API, including the URLClassLoader, pass this parameter to cause verification to occur. Unfortunately, little detail beyond the success or failure of verification is available through the core APIs.</p>
-</li>
-<li>Programmatically via the Equinox 'signedcontent' APIs
-
-<p>In 3.4, several interfaces for inspecting the signer details of a bundle have been introduced into the Equinox bundle (org.eclipse.osgi). Starting with the SignedContentFactory, a developer can programmatically inspect the entries in a bundle to see signers, timestamps and whether a code signer is trusted or not. For more information see the javadoc for the org.eclipse.osgi.signedcontent package of the org.eclipse.osgi bundle.</p>
-</li>
-</ol>
-
-<h1>Authorization of signed code</h1>
-
-<p>Once the signer(s) of code packaged in a bundle is established via authentication, the next step to perform is 'authorization'. Authorization is the process by which the system decides whether a piece of code should be able to perform a specified action. Although the Java runtime supports a fine grained runtime permission model, Eclipse also supports two additional enforcement points with respect to signed code packaged in bundles. This gives Eclipse platform deployers a range of security solutions that allow tradeoffs to be made between flexibility and complexity versus manageability and performance. In Eclipse 3.4 or later, authorization based on signatures can be performed:</p>
- 
-<ol>
-<li>When code is installed by the provisioning system
-
-<p>For several previous releases and in the new P2 provisioning framework, Eclipse has the ability to check signatures as bundles are provisioned into the system. As the provisioning system encounters bundles, it automatically performs authentication of the code signer and will prompt if a signer is not trusted according to the system configuration. The end user will be presented with a list of untrusted signers, and choosing to trust will allow the bundles to be installed into the platform.</p>
-</li>
-<li>When code is loaded by the runtime
-
-<p>Since 3.4, the Equinox runtime has had the ability to check the signature of code as it is loaded. The benefit to this feature beyond checking signatures during provisioning is the ability to dynamically remove trust and disable code should an exploit be exposed in deployed code. In order to enable signature-based authorization at load time, the following VM argument must be passed:</p>
-<pre>
-	-Dosgi.signedcontent.support=authority
-</pre>
-<p>See the runtime options page for more information about the osgi.signedcontent.support runtime variable.</p>
-</li>
-</ol>
-
-<p>For more information on security topics related to Eclipse and Equinox, see the site:</p>
-
-<ul>
-<li><a href="http://www.eclipse.org/equinox/security">http://www.eclipse.org/equinox/security</a></li>
-</ul>
-
-
-
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf.htm
deleted file mode 100644
index 38bc7ad..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf.htm
+++ /dev/null

@@ -1,230 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Oakland Software and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Common Navigator Framework</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>Common Navigator Framework</H1>
-
-<p>A JFace Viewer provides the user with a view of objects using a single
-content provider, label provider, sorter and filter. The Common
-Navigator Framework (CNF) extends this idea by allowing a single view to
-dynamically use multiple and unrelated sets of content providers, label
-providers, sorters and filters. These can be activated in the view
-depending on declarative expressions or using API calls. The CNF
-implemented by the <b><a
-	href="../reference/api/org/eclipse/ui/navigator/package-summary.html">
-org.eclipse.ui.navigator</a></b> plugin.</p>
-
-<p>The CNF uses the idea of <i>Navigator Content Extensions</i>
-(NCE) which can refer to a content provider, label provider, sorter, or
-drag adaptor (note that filters are configured separately). An NCE has
-associated expressions that tell it when it is active. NCEs are also
-presented to the user in the view context menu so that user can turn
-them on or off in order to show the view in different ways. Examples of
-NCEs are a resource content extension that controls how resources are
-presented and Java content extension that shows Java projects. In the
-IDE's Project Explorer, you can turn off the Java content extension
-getting a pure resource view of the workspace.</p>
-
-<p>By using the NCEs it's possible to include different <i>model
-objects</i> directly in the view. These model objects might be related in a
-cascading fashion. For example a resource object (an <code>IFile</code>)
-might refer to a Java class object. This Java class object can be
-presented directly in the view by defining an NCE. The Java class object
-can have children (representing methods, fields, etc) all of which
-appear in the view. You can then add another NCE to display model
-objects related to the Java (or resource object) that display content
-related to a Java Server Page object. This can all be done without the
-"lower level" NCEs (resources, Java) being aware of the existence of the
-"outer" NCEs (JSP). Further, it's possible for outer NCEs to override by
-suppressing processing associated with lower level NCEs according to
-their requirements. And even further, it's possible (using the
-pipelining mechanism) for even level in this cascaded set of NCEs to
-arrange the presentation of the objects according to their
-specifications, moving, adding, or suppressing objects as necessary.</p>
-
-<p>The CNF has depends only on <code>org.eclipse.ui</code> and is
-therefore suitable for use both within the IDE and in an RCP
-application.</p>
-
-<p>The CNF is highly configurable and many of its components can be
-used separately (though this is not the typical case). For example, it's
-possible use the service that manages content extensions with a viewer
-other than the standard <code>CommonViewer</code>.</p>
-
-<p>The CNF documentation has the following sections:</p>
-<ul>
-	<li><a href="cnf_config.htm">Configuration Overview</a> - A high
-	level discussion of the configuration.</li>
-	<li><a href="cnf_operation.htm">Operational Topics</a> - A detailed discussion of various topics in the
-	operation of the CNF</li>
-	<li><a href="cnf_steps.htm">Step-by-step Instructions</a>
-	- Provides configuration instructions for various scenarios.</li>
-	
-	<!--
-	<li><a href="cnf_examples.htm">Examples</a> - Describes the
-	example projects for the CNF.</li>
-	-->
-
-	<li><a href="cnf_troubleshooting.htm">Troubleshooting</a> - Some suggestions for troubleshooting.</li>
-</ul>
-
-<h2>Major Components of the Common Navigator Framework</h2>
-
-<p>The CNF has the following major parts:</p>
-<ol>
-	<li><b>View Part</b> - <b><a
-		href="../reference/api/org/eclipse/ui/navigator/CommonNavigator.html">CommonNavigator
-	</a></b>.</li>
-
-	<li><b>Viewer</b> -<b><a
-		href="../reference/api/org/eclipse/ui/navigator/CommonViewer.html">CommonViewer
-	</a></b> the implementation of a viewer that is contained in the above view
-	part. You can also use the CNF with your own viewer that can be
-	displayed anywhere.</li>
-
-	<li><b>Navigator Content Extensions</b> - <b><a
-		href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent</a></b>
-	This extension point is where you configure the collections of content
-	you want to make visible.</li>
-
-	<li><b>Navigator Viewer</b> - <b><a
-		href="../reference/extension-points/org_eclipse_ui_navigator_viewer.html">org.eclipse.ui.navigator.navigatorContent</a></b>
-	This extension point is used to declare the relationship between the
-	NCEs and a particular viewer. Regular expressions may be used here to
-	allow a viewer to dynamically detect NCEs that it does not know about
-	beforehand. visible.</li>
-
-	<li><b>Resource Support</b> - <b><a href="../guide/resInt.htm">Resources
-	</a></b> are one of the main types of objects managed by the CNF. To support
-	this the <b><a
-		href="../reference/api/org/eclipse/ui/navigator/resources/package-summary.html">
-	org.eclipse.ui.navigator.resources</a></b> plug-in provides all of the
-	necessary definitions. The Project Explorer is configured using these
-	definitions.</li>
-
-</ol>
-
-<h2>Navigators - Where the CNF Fits</h2>
-
-<p>There are currently 3 major navigators in the Eclipse IDE.</p>
-<ol>
-	<li><b>Project Explorer</b> - This is an instance of the
-	CommonNavigator that is provided by the <b><a
-		href="../reference/api/org/eclipse/ui/navigator/resources/package-summary.html">
-	org.eclipse.ui.navigator.resources</a></b> plugin. It provides a view of the
-	workspace and has a large number of NCEs contributed for resources,
-	Java, C, Web Tools, Data Tools, PHP, etc.</li>
-	<li><b>Package Explorer</b> - Provided by the Java Development
-	Tools (JDT) UI project, this provides a view of Java classes for the
-	workspace. Generally speaking, the presentation of the Package Explorer
-	and Project Explorer for Java objects is substantially similar. The JDT
-	is not used for projects beyond Java.</li>
-	<li><b>Navigator</b> - This view is an implementation of the now
-	deprecated (as of 3.5) <b><a
-		href="../reference/api/org/eclipse/ui/views/navigator/package-summary.html">org.eclipse.ui.views.navigator
-	</a>ResourceNavigator </b> class provided in the <code>org.eclipse.ui.ide</code>
-	plugin. It shows only the workspace resources and does not support
-	extensibility to show other content. In a future release, the Navigator
-	view will be provided by an implementation of the CommonNavigator.
-	<p>
-	We also provide <a href="cnf_steps_rn_migration.htm">instructions</a> for migration from the ResourceNavigator to the CNF.
-	</p>
-	</li>
-</ol>
-
-<p>The only navigator intended for general purpose client use if the
-CNF, which can be used either by adding NCEs visable in the Project
-Explorer (if developing an IDE plugin), or using a separate instance of
-the CommonNavigator as a view.</p>
-
-<h2>Navigator Content Extensions (NCE)</h2>
-
-<p>The CNF allows you to include not only resources but any type of
-object. One typical use case is that of a resource (consider a Java file
-for example) which has several subordinate objects presented as tree
-nodes representing aspects of the class like imports, methods, etc. The
-CommonViewer (portion of the Common Navigator) will include the
-IResource object representing the Java file, and then as its children an
-object for each import, method, etc. The mechanism for defining this is
-a <b><a href="cnf_config.htm#contentExtension">navigator content
-extension</a></b>.</p>
-
-<p>Each content extension also provides a means of associating
-objects with appropriate icons, labels and menu items.</p>
-
-<p>Content extensions are invoked based on an enablement expression
-which is defined using core expressions in the extension point.
-Enablement expressions are commonly defined by sensing the class of an
-object.</p>
-
-<p></p>
-
-<p>A priority may be associated with a content extension which helps
-to determine the order of invocation of the NCEs. It's possible that
-more than one content extension may be enabled for a given object and
-situation. Priorities are defined with words like "high" or "normal". A
-high priority would be associated with an extension that defines the
-primary UI for frequently manipulating an object. A low priority would
-be given to relatively infrequent utility sorts of UI.</p>
-
-<p>Content extensions may be activated and deactivated for a given
-view part in the UI using the <b>Customize View</b> menu item in the
-header menu associated with the view part. Common filters are also may
-also be activated and deactivated the same way.</p>
-
-<h2>Common Filters</h2>
-
-<p>Filters allow the user to specify which resources or objects to
-exclude. Like content extensions, filters may be specified centrally and
-shared.  
-</p>
-
-<h2>Common Wizards</h2>
-
-<p>References to wizards for new/import/export may be defined. These
-are included in the appropriate popup menu based on the enablement.</p>
-
-<h2>Action Providers</h2>
-
-<p>Though the CNF provides a mechanism to work with actions, it is
-recommended that you instead use the <b><a
-	href="../guide/workbench_cmd.htm">Workbench Commands </a></b> instead of actions.
-</p>
-
-<p>Action providers provide a means to configure the retargetable
-actions and programmatically configure the popup menu in a CNF viewer.
-These are useful for when you must perform a computation to determine
-which items are added to the menu, or to adjust the retargetable actions
-to ensure that the user keystrokes are handled properly (like for
-Cut/Copy/Paste).</p>
-
-<h2>Drag and Drop Support</h2>
-
-<p>A drop assistant may be associated with a content extension to
-provide handling of additional (non-standard) transfer types or
-validation in the event of a drop.</p>
-
-<h2>Link with Editor Support</h2>
-
-<p>The link helper extension point provides a flexible mechanism of
-determining the appropriate selection in the navigator when an editor is
-activated. Conversely, it also provides the appropriate editor to be
-activated when the selection changes.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_config.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_config.htm
deleted file mode 100644
index d1faecd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_config.htm
+++ /dev/null

@@ -1,225 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Oakland Software and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Configuring the Common Navigator</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h1>Configuring the Common Navigator</h1>
-
-<p>This section defines the configuration at a conceptual level;
-some level of detail is omitted for clarity and conciseness. For the
-complete details see the extension point documentation or the <a
-	href="cnf_operation.htm">Operational Topics</a>
-section.
-<ul>
-	<li><b><a
-		href="../reference/extension-points/org_eclipse_ui_navigator_viewer.html">org.eclipse.ui.navigator.viewer</a></b></li>
-	<li><b><a
-		href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent</a></b></li>
-	<li><b><a
-		href="../reference/extension-points/org_eclipse_ui_navigator_linkHelper.html">org.eclipse.ui.navigator.linkHelper</a></b></li>
-</ul>
-</p>
-
-<h2>Viewer Configuration</h2>
-
-<p>As the CommonNavigator is a View, it is added using the <b><a
-	href="../reference/extension-points/org_eclipse_ui_views.html">org.eclipse.ui.views</a></b>
-extension point. The CNF configuration aspects of the view instance are
-specified with a corresponding <b><a
-	href="../reference/extension-points/org_eclipse_ui_navigator_viewer.html">org.eclipse.ui.navigator.viewer</a></b>
-extension point.</p>
-
-<p>It is possible to use the CNF facilities for an arbitrary
-TreeViewer (??? could this be any StructuredViewer). In this case you
-still need to use this extension point, but it is used only to bind the
-CNF view information with the NCEs. You then programmatically (??? how)
-bind your Viewer with the NavigatorContentService.</p>
-<p>The view may be associated with <b><a
-	href="#contentExtension">Navigator Content Extensions</a></b> that define
-how its content is found and rendered. The entries here are used to look
-up NCEs, common filters and common wizards.</p>
-
-<p>The view may also be associated with <b><a
-	href="#actionProviders">Action Providers</a></b> that define code for
-programmatic updating and provision of actions or retargetable actions.
-The entries here are used to look up action providers.</p>
-
-<p>The view may also be associated with <b><a
-	href="#linkHelpers">Link Helpers</a></b> that define the relationship
-between the selection in the view and the active editor.</p>
-
-<p>Content extensions, common wizards, common filters, action
-providers and link helpers are bound to the view using an
-include/exclude mechanism and with the capability of pattern matching.
-This allows the actual content extensions (defined below) to be
-specified in a granular fashion such that views can select only those
-they actually need. The point of the exclude part of the mechanism is to
-exclude undesired items that were specified in the include statement.
-For example, the include statement could specify
-"com.mycompany.content.*" and exclude could remove the test content
-extensions by saying "com.mycompany.content.test.*".</p>
-
-<p>A view is always associated with a popup menu. One important part
-of the popup menu configuration at this level is the insertion points,
-which are the locations where menu items can be added depending on when
-and where the menu is shown. By default, a standard set of insertion
-points is provided (described in the extension point documentation).
-However, you can can define your insertion points directly using <b>popupMenus</b>.
-</p>
-
-<p>You can also direct the view to use a specific popup menu by id
-using <b>popupMenuId</b>, and you can indicate whether to ignore
-platform action contributions to the menu.</p>
-
-<p>In the startup case, it is necessary to call some content
-extensions on the root node of the tree of the view in order to get the
-initial set of children. This set of content extensions is specified by
-setting the isRoot() property on the viewerContentBinding.</p>
-
-
-<p>This defines:</p>
-<ol>
-	<li><b>viewerContentBinding</b> - bind a Content Extension or
-	Common Filter specified with the <b><a
-		href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/navigatorContent</a></b>
-	extension point;</li>
-	<li><b>viewerActionBinding</b> - bind action providers specified
-	with the <b><a
-		href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/actionProvider</a></b>
-	extension point;</li>
-	<li><b>popupMenus</b> - defines the insertion points (standard
-	places where menu items can be added) for the popup menu associated
-	with the viewer. Mutually exclusive with popupMenuId.</li>
-	<li><b>popupMenuId</b> - causes the view to use the menu defined
-	by the <b><a
-		href="../reference/extension-points/org_eclipse_ui_popupMenus.html">org.eclipse.ui.popupMenus</a></b>
-	extension point. Mutually exclusive with popupMenus.</li>
-	<li><b>dragAssistent</b> - points to code that may provide extra
-	transfer types to be used when starting a drag from the viewer.</li>
-	<li><b>options</b> - specifies options used to control the
-	presentation of the view. For example these allow hiding of menus and
-	buttons shown at the top of the view. Theses options are defined by <b><a
-		href="../reference/api/org/eclipse/ui/navigator/INavigatorViewerDescriptor.html">INavigatorViewerDescriptor
-	</a> </b></li>
-</ol>
-
-<a name="contentExtension"></a>
-<h2>Navigator Content Extension (NCE)</h2>
-
-<p>A navigator content extension, specified with <b><a
-	href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/navigatorContent</a></b>
-defines a named collection of attributes (content provider class, label
-provider class, icon, etc) to be enabled under certain conditions
-(typically in response to selection in the navigator). An example of a
-content extension is that for a resource. Content extensions are useful
-to describe other model objects that might be included in the view.</p>
-
-<p>The definition of content extensions is separated from their
-association with a particular view instance allowing them to be shared
-and reused. Each content extension has an id, which is used to bind it
-with a view, and a display name which is presented to the user to allow
-the content extensions to be activated or deactivated by the user
-interface associated with the each view.</p>
-
-<p>Content extensions may be active or not. This can be controlled
-by the user using the Customize View menu item of the navigator.
-Inactive content extensions are not considered when processing the view.</p>
-
-<p>The content extension defines the following:</p>
-<ol>
-	<li><b>triggerPoints</b> - specifies the conditions when this
-	content extension is enabled based on a given object. You can specify
-	tests with core expressions on the object for which the content
-	extension should be enabled.</li>
-	<li><b>possibleChildren</b> - like triggerPoints, but used for the
-	case where the parent of the desired content extension is known, like
-	in the drop case where we need to determine which content extension is
-	required to handle the drop based on the drop target which is the
-	parent of the eventual object that will be added to the tree.</li>
-	<li><b>enablement</b> - specifies an enablement that is both a <b>triggerPoints</b>
-	and <b>possibleChildren</b>.</li>
-	<li><b>labelProvider</b> - an <b><a
-		href="../reference/api/org/eclipse/jface/viewers/ILabelProvider.html">ILabelProvider</a></b>
-	provides the text to be shown in the view.</li>
-	<li><b>contentProvider</b> - an<b><a
-		href="../reference/api/org/eclipse/jface/viewers/ITreeContentProvider.html">ITreeContentProvider</a></b>
-	provides the means of getting the parent and child objects for the
-	viewer. Other interfaces are possible, see the extension point
-	documentation for these.</li>
-	<li><b>descriptionProvider</b> - <b><a
-		href="../reference/api/org/eclipse/ui/navigator/IDescriptionProvider.html">IDescriptionProvider</a></b>
-	provides a description that is shown in the status bar.</li>
-	<li><b>activeByDefault</b> - indicates this content extension
-	should be made active in the default configuration of the workbench
-	(e.g. a new workspace).</li>
-	<li><b>priority</b> - used to determine which content extension to
-	use in the event that multiple extensions are enabled (based on their
-	enablement conditions).</li>
-	<li><b>icon</b> - used to associate the object with a specific
-	icon.</li>
-	<li><b>providesSavables</b> - indicates the content provider
-	provides saveables. If true the content provider must adapt to
-	SavablesProvider.</li>
-</ol>
-
-<h3>Common Filter</h3>
-
-<p>A common filter, specified with <b><a
-	href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/commonFilter</a></b>
-defines a filter that is controllable by the user in the view. The
-filter definition contains an id, a description that describes the
-filter, a description that describes what is filtered out, and the
-conditions (using core expressions) that identify objects the filter
-suppresses.</p>
-<p>The common filter is bound to the view using the <b>viewerContentBinding</b>
-element of the viewer configuration.</p>
-
-<h3>Common Wizard</h3>
-
-<p>A common filter, specified with <b><a
-	href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/commonWizard</a></b>
-defines wizard that is to be shown in the new, import, or export menu.</p>
-<p>The common wizard is bound to the view using the <b>viewerContentBinding</b>
-element of the viewer configuration.</p>
-
-<h3>Action Providers</h3>
-<a name="actionProviders"></a>
-
-<p>An action provider, specified with <b><a
-	href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/actionProvider</a></b>
-allows you to specify a class, subclassing <b><a
-	href="../reference/api/org/eclipse/ui/navigator/CommonActionProvider.html">org.eclipse.ui.navigator.CommonActionProvider</a></b>
-that is invoked at right-click and selection time to allow you to
-contribute to the popup menu or to the action bars.</p>
-
-<p>Action providers may be defined at the top level of the extension
-point, not associated with any content extension. These action providers
-are named and then bound to the CommonViewer using the <b>org.eclipse.ui.navigator.viewer/viewerActionBinding</b>.</p>
-
-<p>Action providers may also be associated with a content extension,
-in which case they are active with the content extension. This is done
-by including the action provider inside of the <b>org.eclipse.ui.navigator.navigatorContent/navigatorContent</b>
-extension point.</p>
-
-<h3>Link Helpers</h3>
-<a name="linkHelpers"></a>
-
-<p>A link helper, specified with <b><a
-	href="../reference/extension-points/org_eclipse_ui_navigator_linkHelper.html">org.eclipse.ui.navigator.linkHelper</a></b>
-allows you to control how the &quot;Link with Editor&quot; matches the
-selection in the navigator with an editor and matches an active editor
-with the selection in the navigator.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_operation.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_operation.htm
deleted file mode 100644
index dba5b57..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_operation.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Oakland Software and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Operational Topics</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h1>Operational Topics</h1>
-<p>This section covers the operation of the CNF in detail.</p>
-
-<h2>Content Provider selection</h2>
-<p>Selecting the content provider is done by finding one or more
-NCEs associated with an object. The CNF is registered as a content
-provider a viewer and thus gets called at the content provider APIs in
-response to actions by the user on the viewer. In general, if the user
-is navigating by expanding in the viewer, the <code>getElements()</code>
-or <code>getChildren()</code> methods are called. However if the user
-has selected some object (like in an editor) and wishes to show it in
-the viewer, the <code>getParent()</code> method is used because the
-viewer needs to be able to figure out the part of the tree between the
-object and the content currently visible in the viewer.</p>
-
-<p>When selecting an NCE in reaction to the <code>getElements()</code>
-or <code>getChildren()</code> call on the viewer, the <b>triggerPoints</b>
-(or <b>enablement</b> if specified) expression is evaluated against the
-object. The content provider associated with that NCE is invoked. If
-there are multiple content providers enabled by their <b>triggerPoints</b>
-(or <b>enablement</b>) expressions, they are all invoked in order
-according to priority and their results are concatenated.</p>
-
-<p>When selecting an NCE in reaction to the <code>getParent()</code>
-call on the viewer, the <b>possibleChildren</b> (or <b>enablement</b> if
-specified) expression is evaluated against the object. The content
-provider associated with that NCE is invoked. If there are multiple
-content providers enabled by their <b>possibleChildren</b> (or <b>enablement</b>)
-expressions, the content providers are invoked in priority order. The
-first non-null parent returned by the content provider is used.</p>
-
-<p>The <b>overrides</b> element allows an NCE to be overridden by
-another. In this case the content provider associated with the
-suppressed NCE will not be invoked to contribute.</p>
-
-<p>During the initialization of the viewer, the it gets the initial
-input by invocation of the <a
-	href="../reference/api/org/eclipse/ui/navigator/CommonNavigator.html#getInitialInput"><code>CommonNavigator.getInitialInput()</code></a>.
-The default implementation of this method is to return the input of the
-current page. Thus, the initial input becomes the first object that is
-evaluated for the selection of NCEs.</p>
-
-<!--
-
-<h2>Label Provider selection</h2>
-
-<p>TBS - talk about the association of the object with the NCE that
-is associated with the object's content provider.</p>
-
-<p>More ???TBS</p>
-
-<h2>Pipelining</h2>
-
-<p>Pipelining works with the override mechanism to allow reshaping
-the tree of objects. To use pipelining service, your content provider
-must implement the <b>IPipedlinedTreeContentProvider</b> interface.</p>
-<p>??? More TBS</p>
-
--->
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_rcp.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_rcp.htm
deleted file mode 100644
index dbdcb08..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_rcp.htm
+++ /dev/null

@@ -1,137 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Oakland Software and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Common Navigator in an RCP Application</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Using the Common Navigator in an RCP Application</h1>
-
-<p>
-To add the Common Navigator to an RCP application and have it manipulate the
-workspace resources, do the following:
-</p>
-
-<ol>
-<li>
-Add the following as dependent plug-ins:
-<ol type="a">
-<li>org.eclipse.ui.navigator</li>
-<li>org.eclipse.ui.navigator.resources</li>
-<li>org.eclipse.ui.ide</li>
-<li>org.eclipse.core.resources</li>
-</ol>
-</li>
-<li>Add a View extension (org.eclipse.ui.views) which uses the class org.eclipse.ui.navigator.CommonNavigator.
-<pre>
-   &lt;extension
-         point="org.eclipse.ui.views"&gt;
-      &lt;view
-            name="View"
-            class="org.eclipse.ui.navigator.CommonNavigator"
-            id="example.view"&gt;
-      &lt;/view&gt;
-   &lt;/extension&gt;
-</pre>
-</li>
-<li>Update your perspective factory (IPerspectiveFactory) code to show the new View (this is necessary when adding any View):
-
-<pre>
-	public void createInitialLayout(IPageLayout layout) {
-		String editorArea = layout.getEditorArea();
-		layout.setEditorAreaVisible(false);
-		layout.setFixed(true);
-		
-		layout.addStandaloneView("example.view",  true /* show title */, IPageLayout.LEFT, 1.0f, editorArea);
-	}
-</pre>
-
-<p>
-Note that for the moment you need to specify "true" to show title, otherwise the viewer will not render correctly
-(<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=235171">bug 235171</a>).</p>
-</li>
-<li>
-Add a org.eclipse.ui.navigator.viewer extension that has:
-<ul>
-<li>viewerActionBinding, point this to your View Id above (example.view)
-<ul>
-<li>includes of org.eclipse.ui.navigator.resources</li>
-</ul>
-</li>
-<li>viewerContentBinding, point this to your View Id above (example.view)
-<ul>
-<li>includes of:
-<ul>
-<li>org.eclipse.ui.navigator.resources</li>
-<li>org.eclipse.ui.navigator.resourceContent</li>
-<li>org.eclipse.ui.navigator.resources.filters</li>
-<li>org.eclipse.ui.navigator.resources.linkHelper</li>
-<li>org.eclipse.ui.navigator.resources.workingSets</li>
-</ul>
-</li>
-</ul>
-</li>
-</ul>
-
-<pre>
-
-   &lt;extension
-         point="org.eclipse.ui.navigator.viewer"&gt;
-       &lt;viewerActionBinding
-            viewerId="example.view"&gt;
-         &lt;includes&gt;
-             &lt;actionExtension pattern="org.eclipse.ui.navigator.resources.*" /&gt;
-         &lt;/includes&gt;
-       &lt;/viewerActionBinding&gt;
-       &lt;viewerContentBinding 
-            viewerId="example.view"&gt;
-          &lt;includes&gt;
-       	     &lt;contentExtension pattern="org.eclipse.ui.navigator.resourceContent" /&gt;		       	      
-	     &lt;contentExtension pattern="org.eclipse.ui.navigator.resources.filters.*"/&gt;
-             &lt;contentExtension pattern="org.eclipse.ui.navigator.resources.linkHelper"/&gt;
-             &lt;contentExtension pattern="org.eclipse.ui.navigator.resources.workingSets"/&gt;
-          &lt;/includes&gt;
-       &lt;/viewerContentBinding&gt;
-   &lt;/extension&gt;
-</pre>
-</li>
-<li>Add the following to your WorkbenchAdvisor
-<ol type="a">
-<li>To get the resource workspace as input, override this method:
-
-<pre>
-	public IAdaptable getDefaultPageInput() {
-		IWorkspace workspace = ResourcesPlugin.getWorkspace();
-		return workspace.getRoot();
-	}
-</pre>
-</li>
-<li>To get the correct adapters hooked up add this code to the initialize() method:
-
-<pre>
-	public void initialize(IWorkbenchConfigurer configurer) {
-		WorkbenchAdapterBuilder.registerAdapters();
-	}
-</pre>
-
-<blockquote><i>
-<b>Warning:</b> the WorkbenchAdapterBuilder.registerAdapters() is an internal method and not part 
-of the Eclipse API and is therefore subject to change in a subsequent release.  There is an open work 
-item to replace this with similar capability that is part of the API.
-</i></blockquote>
-</li>
-</ol>
-</li>
-</ol>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps.htm
deleted file mode 100644
index 550b6a2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Oakland Software and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Procedures and Examples Using the CNF</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h1>Procedures and Examples for Using the CNF</h1>
-
-<p>The sections below define the set of steps for using the CNF 
-in various scenarios. Some of the sets of below have a plugin in the UI examples
-that shows the end result.
-</p>
-<p>
-<ul>
-<li><a href="cnf_steps_general.htm">Creation of a Common Navigator View</a></li>
-<li><a href="cnf_steps_content.htm">Content and Action Binding</a></li>
-<li><a href="cnf_steps_rn_migration.htm">Migrating from the ResourceNavigator</a></li>
-</ul>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_content.htm
deleted file mode 100644
index cab7c10..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_content.htm
+++ /dev/null

@@ -1,176 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Simon Zambrovski and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Content and Action Binding</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h1>Content and Action Binding</h1>
-<p>The sections below define the set of steps for <a
-	href="#resource">usage of resource content</a> and <a
-	href="#definition">definition of own content</a> for the CNF-based
-viewer. Finally, the steps needed for <a href="#action">Action
-Binding</a> are described. As described <a href="cnf_config.htm">previously</a>,
-in order to render content the viewer selects the corresponding NCEs
-based on the evaluation of the expressions on the selected objects.</p>
-
-<h2><a name="resource">Usage of Resource Content</a></h2>
-<p>One of the use cases of usage of the Common Navigator is the
-manipulation of the workspace resources. The resources-related content
-is defined by the <code>org.eclipse.ui.navigator.resources</code>
-plugin. The example of the resource usage of CNF can be found in <code>org.eclipse.ui.examples.navigator.resources</code>.
-</p>
-<ol>
-	<li>Perform the general steps described in <a
-		href="cnf_steps_general.htm">Creation of Common Navigator Viewer</a></li>
-	<li>Add the following as dependent plug-ins:
-	<ul>
-		<li><code>org.eclipse.ui.navigator.resources</code></li>
-	</ul>
-	</li>
-	<li>Add a <code>org.eclipse.ui.navigator.viewer</code> extension
-	that has:
-	<ul>
-		<li><code>viewerContentBinding</code>, point this to Id of your
-		view (example.view)</li>
-		<li>includes of:
-		<ul>
-			<li>org.eclipse.ui.navigator.resourceContent</li>
-			<li>org.eclipse.ui.navigator.resources.*</li>
-		</ul>
-		</li>
-	</ul>
-	<pre>
-   &lt;extension
-         point="org.eclipse.ui.navigator.viewer"&gt;
-       &lt;viewerContentBinding 
-            viewerId="example.view"&gt;
-          &lt;includes&gt;
-       	     &lt;contentExtension pattern="org.eclipse.ui.navigator.resourceContent" /&gt;		       	      
-	     &lt;contentExtension pattern="org.eclipse.ui.navigator.resources.filters.*"/&gt;
-          &lt;/includes&gt;
-       &lt;/viewerContentBinding&gt;
-   &lt;/extension&gt;
-   </pre></li>
-</ol>
-<p>Please note, that using CNF inside of your own RCP requires three
-additional steps.</p>
-<ol>
-	<li>Add the <code>org.eclipse.ui.ide</code> as dependent plug-in</li>
-	<li>To get the resource workspace root (<code>IWorkspaceRoot</code>)
-	as default page input, override the <a
-		href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html#getDefaultPageInput"><code>WorkbenchAdvisor.getDefaultPageInput()</code></a>
-	method in your WorkbenchAdvisor: <pre>
-	public IAdaptable getDefaultPageInput() 
-	{
-		return ResourcesPlugin.getWorkspace().getRoot();
-	}
-</pre></li>
-	<li>Hook the workbench adapters correctly before they are used, so
-	add this code to the <a
-		href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html#initialize"><code>WorkbenchAdvisor.initialize(IWorkbenchConfigurer)</code></a>
-	method: <pre>
-	public void initialize(IWorkbenchConfigurer configurer) 
-	{
-		IDE.registerAdapters();
-	}
-</pre></li>
-</ol>
-<h2><a name="definition">Own Content Definition</a></h2>
-<p>Along with resource content provided by the <code>org.eclipse.ui.navigator.resources</code>
-plugin, application-specific content can be defined and presented in the
-CNF-based viewer. In order to define and use application specific you
-need to:</p>
-<ol>
-	<li>Use extension <code>org.eclipse.ui.navigator.navigatorContent</code>
-	and declare the NCE, with it providers and trigger conditions for the
-	content: <pre>
-  &lt;extension
-         point="org.eclipse.ui.navigator.navigatorContent"&gt;
-      &lt;navigatorContent 
-            id="org.eclipse.ui.examples.navigator.propertiesContent" 
-            name="Properties File Contents"
-            contentProvider="org.eclipse.ui.examples.navigator.PropertiesContentProvider"
-            labelProvider="org.eclipse.ui.examples.navigator.PropertiesLabelProvider" 
-            activeByDefault="true"
-            icon="icons/prop_ps.gif"
-            priority="normal" &gt;
-         &lt;triggerPoints&gt;
-         	&lt;or&gt;
-	            &lt;and&gt;
-	               &lt;instanceof value="org.eclipse.core.resources.IResource"/&gt;
-	               &lt;test
-	                     forcePluginActivation="true"
-	                     property="org.eclipse.core.resources.extension"
-	                     value="properties"/&gt;
-	            &lt;/and&gt;
-				&lt;instanceof value="org.eclipse.ui.examples.navigator.PropertiesTreeData"/&gt;
-			&lt;/or&gt;
-         &lt;/triggerPoints&gt;
-         &lt;possibleChildren&gt;
-            &lt;or&gt;
-               &lt;instanceof value="org.eclipse.ui.examples.navigator.PropertiesTreeData"/&gt; 
-            &lt;/or&gt;
-         &lt;/possibleChildren&gt;
-      &lt;/navigatorContent&gt;
-   &lt;/extension&gt;
-</pre> For more details, please consult the <a href="cnf_config.htm">CNF
-	Configuration</a> and <a href="cnf_operation.htm">Operational Topics</a>.</li>
-	<li>Bind the content to the viewer using the <code>org.eclipse.ui.navigator.viewer</code>
-	extension. <pre>
-   &lt;extension
-         point="org.eclipse.ui.navigator.viewer"&gt;
-      &lt;viewerContentBinding viewerId="example.view"&gt;
-         &lt;includes&gt;
-            &lt;contentExtension pattern="org.eclipse.ui.examples.navigator.propertiesContent"/&gt;
-         &lt;/includes&gt;
-      &lt;/viewerContentBinding&gt;
-   &lt;/extension&gt;
-</pre> Note, that instead of using the exact Id of the content, the usage of
-	the regular expression is allowed in the <code>pattern</code>
-	attribute, so <code>org.eclipse.ui.examples.navigator.*</code> would
-	also work.</li>
-</ol>
-<h2><a name="action">Action Binding</a></h2>
-<p>The usage of actions in the viewer follows the same pattern as the content binding. For usage of existing 
-actions on resources defined in the <code>org.eclipse.ui.navigator.resources</code> plugin:</p>
-<ol>
-	<li>Add the following as dependent plug-ins:
-	<ul>
-		<li><code>org.eclipse.ui.navigator.resources</code></li>
-	</ul>
-	</li>
-	<li>Add a <code>org.eclipse.ui.navigator.viewer</code> extension
-	that has:
-	<ul>
-		<li><code>actionContentBinding</code>, point this to Id of your
-		view (example.view)</li>
-		<li>includes of:
-		<ul>
-			<li>org.eclipse.ui.navigator.resources.*</li>
-		</ul>
-		</li>
-	</ul>
-	<pre>
-   &lt;extension
-         point="org.eclipse.ui.navigator.viewer"&gt;
-       &lt;viewerActionBinding 
-            viewerId="example.view"&gt;
-          &lt;includes&gt;
-       	     &lt;actionExtension pattern="org.eclipse.ui.navigator.resources.*" /&gt;		       	      
-          &lt;/includes&gt;
-       &lt;/viewerContentBinding&gt;
-   &lt;/extension&gt;
-   </pre></li>
-</ol>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_general.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_general.htm
deleted file mode 100644
index 37e7301..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_general.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-<meta name="copyright"
-	content="Copyright (c) Simon Zambrovski and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Creation of Common Navigator View</TITLE>
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Creation of Common Navigator View</h1>
-<p>
-In order to use the CNF-based view in the application several steps are required which are discussed below. The created view can be 
-configured by binding specific content and actions to it, which is discussed in the <a href="cnf_steps_content.htm">Content and Action Binding</a>. 
-</p>
-
-<p>The example plugin <code>org.eclipse.ui.examples.navigators.resources</code> shows this.</p>
-
-<ol>
-<li>
-Add the following as dependent plug-ins:
-<ul>
-<li><code>org.eclipse.ui</code></li>
-<li><code>org.eclipse.ui.navigator</code></li>
-</ul>
-</li>
-<li>Add a View extension (<code>org.eclipse.ui.views</code>) and provide <code>org.eclipse.ui.navigator.CommonNavigator</code> 
-as the value of <code>class</code> attribute. Please note, that the <code>id</code> of the view will be required in later steps 
-for the content and action bindings.
-<pre>
-   &lt;extension
-         point="org.eclipse.ui.views"&gt;
-      &lt;view
-            name="View"
-            class="org.eclipse.ui.navigator.CommonNavigator"
-            id="example.view"&gt;
-      &lt;/view&gt;
-   &lt;/extension&gt;
-</pre>
-</li>
-</ol>
-<p>
-Please note, that if you are 
-<a href="rcp_perspective.htm">defining your own perspective</a> in which the Common 
-Navigator is used, the <code>showTitle</code> parameter must be set to <code>true</code> 
-in order the viewer renders correctly (see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=235171">bug 235171</a>).
-</p>
-<pre>
-	public void createInitialLayout(IPageLayout layout) {
-		String editorArea = layout.getEditorArea();
-		layout.setEditorAreaVisible(false);
-		layout.setFixed(true);
-		
-		layout.addStandaloneView("example.view",  true /* show title */, IPageLayout.LEFT, 1.0f, editorArea);
-	}
-</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_rn_migration.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_rn_migration.htm
deleted file mode 100644
index 95d6d6c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_steps_rn_migration.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Oakland Software and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Migrating from the ResourceNavigator</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Migrating from the ResourceNavigator</h1>
-
-<p>
-First follow the steps to <a href="cnf_steps_general.htm">add the Common Navigator</a> and check that the 
-steps required for usage of <a href="cnf_steps_content.htm">resource content</a> are applied.
-</p>
-
-<p>The following steps discuss the migration component for each part of the ResourceNavigator</p>
-
-<ol>
-<li>
-<code>org.eclipse.ui.ide.resourceFilters</code>
-<p>
-Add the corresponding 
-<b><a href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/commonFilter</a></b>
-extensions.
-</p>
-</li>
-
-<li>
-<code>FrameList</code> support <code>get/setFrameList()</code>
-<p>
-The FrameList support is used for the Go Into functionality.  Support for this 
-is included in the ProjectExplorer subclass of CommonNavigator.  You should subclass ProjectExplorer
-instead of CommonNavigator. 
-</p>
-</li>
-
-
-<li>
-
-<code>ResourcePatternFilter</code> support <code>get/setPatternFilter()</code>
-<p>
-Configure the ResourcePatternFilter using the 
-<b><a href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent/commonFilter</a></b>
-extension.  Then you can access the instance of the filter using the following code (where <code>yourViewer</code> is the instance
-of the CommonViewer and <code>yourFilterId</code> is the string of the Id of your common filter configured above):
-<pre>
-INavigatorContentService contentService = yourViewer.getNavigatorContentService();
-INavigatorFilterService filterService = contentService.getFilterService();
-ICommonFilterDescriptor[] fds = filterService.getVisibleFilterDescriptors();
-for (int i = i; i &lt; fds.length; i++) {
-	if (fds[i].getId().equals(yourFilterId))
-		return filterService.getViewerFilter(filterDescriptor);
-}
-</pre>
-</p>
-</li>
-
-<li>
-<code>IWorkingSet</code> support <code>get/setWorkingSet()</code>
-<p>
-Working sets are not directly supported by the Common Navigator.  The Project Explorer however does support
-working sets.  There is however no current API in the Project Explorer to manipulate working sets.  The
-Project Explorer provides a UI to work with working sets.  If this sort of API is required, please file
-an enhancement request explaining the requirement.
-</p>
-</li>
-
-<li>
-<code>ResourceSorter</code> support <code>get/setResourceSorter()</code>
-<p>
-Use the sorting facility in the Common Navigator.
-</p>
-</li>
-
-<li>
-<code>ResourceComparator</code> support <code>get/setResourceComparator()</code>
-<p>
-Use ResourceSorter instead for now as the Common Navigator does not directly support
-ResourceComparators.
-</p>
-</li>
-
-</ol>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/cnf_troubleshooting.htm b/bundles/org.eclipse.platform.doc.isv/guide/cnf_troubleshooting.htm
deleted file mode 100644
index 7fca77e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/cnf_troubleshooting.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) Oakland Software and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Troubleshooting</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Troubleshooting</h1>
-
-<h2>Check Your Ids</h2>
-
-<p>This is the most common problem in configuring the CNF. Make sure
-the Ids match exactly what you expect them to. </p>
-<h2>Is it a Wildcard or Regular Expression?</h2>
-
-<p>Be sure that the <code>includes</code> and <code>excludes</code>
-Ids for the navigator content extensions or filters are actually <b>regular
-expressions</b> and not wild cards. So if you are looking for <code>com.mycompany.myplugin*</code>
-(this is a wildcard), make sure you use <code>com.mycompany.myplugin.*</code>
-(which is a matching regular expression). The former will find things
-like <code>com.mycompany.mypluginnnnn</code>, but won't find <code>com.mycompany.myplugin.function1</code>.
-</p>
-
-<h2>Tracing</h2>
-
-<p>The CNF provides tracing that can be helpful to resolve problems.
-To enable the tracing go to the <b>Tracing</b> tab in the <b>Launch
-Configuration Dialog</b> and select <b>Enable Tracing</b>. Then check the <code>org.eclipse.ui.navigator</code>
-plugin, and on the right check <b>debug</b> and <i>also</i> one of the
-following:</p>
-<ul>
-	<li><b>debug/setup</b> - Shows the processing of the
-	configuration.</li>
-	<li><b>debug/dnd</b> - Shows all aspects of drag and drop
-	processing.</li>
-	<li><b>debug/resolution</b> - Shows the resolution of an object to
-	its navigator content extension.</li>
-	<li><b>debug/viewermap</b> - Shows the low-level map that associates
-	the Navigator Content Extensions with active elements in the viewer.</li>
-</ul>
-
-<p>
-If you require support, include the tracing when you report your problem.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare.htm
deleted file mode 100644
index d4218cb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Compare support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Compare support</H1>
-
-
-<p>
-If your plug-in defines and manipulates its own resource types, you may have
-special requirements for comparing resources.&nbsp; Resources are often compared
-when working with local history or with files from a repository.&nbsp; The <b>compare</b>
-plug-in supports merging of multiple content streams and the implementation of advanced compare views.
-Services provided by this plug-in include:</p>
-
-
-<ul>
-  <li>Interfaces for merging multiple text streams into a single output stream</li>
-  <li>Two and three-way compare and merge components for hierarchical structures
-    inferred from text</li>
-  <li>Differencing engines for hierarchical structures and character ranges in
-    text</li>
-</ul>
-<p>These services are used in the platform to assist with user tasks such as
-integrating patch files and comparing/merging the workspace with local history.</p>
-<h2>Compare viewers</h2>
-<p>
-All compare viewers are standard <a href="jface_viewers.htm"> JFace viewers</a> that expect an input object implementing the
-<b><a href="../reference/api/org/eclipse/compare/structuremergeviewer/ICompareInput.html">ICompareInput</a></b>
-interface.</p>
-<p>
-Compare viewers are said to be
-<a href="compare_contentviewer.htm">content-oriented</a>  if they compare flat
-inputs such as text or images and
-<a href="compare_structureviewer.htm">structure-oriented</a>  if they compare
-hierarchically structured input elements.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm
deleted file mode 100644
index be2dadf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_beyond.htm
+++ /dev/null

@@ -1,129 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Advanced compare techniques</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Advanced compare techniques</H2>
-
-<p>
-This section provides additional information about advanced API in the compare
-plug-in.</p>
-
-<h3>Writing compare operations</h3>
-
-<p>A compare operation must be implemented as a subclass of
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>.&nbsp;
-A
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>
-runs a (potentially lengthy) compare operation
-under progress monitor control, creates a UI for drilling-down into the
-compare results, tracks the dirty state of the result in case of merge,
-and saves any changes that occurred during a merge.</p>
-
-<p>
-
-<a href="../reference/api/org/eclipse/compare/CompareUI.html"><b>CompareUI</b></a>
-defines the entry point to initiate a configurable
-compare operation on arbitrary resources. The result of the compare is
-opened into a compare editor where the details can be browsed and edited
-in dynamically selected structure and content viewers.</p>
-<p>
-
-<a href="../reference/api/org/eclipse/compare/NavigationAction.html"><b>NavigationAction</b></a>
-is used to navigate (step) through the individual
-differences of a 
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>.</p>
-<p>
-
-<a href="../reference/api/org/eclipse/compare/CompareConfiguration.html"><b>CompareConfiguration</b></a>
-configures various UI aspects
-of compare/merge viewers like title labels and images, or whether a side
-of a merge viewer is editable. It is passed to the
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>
-on creation.</p>
-<p>
-
-When implementing a hierarchical compare operation as a subclass of
-<a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a>,
-clients must provide a tree of objects where each
-node implements the interface
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>.
-This interface is used by the hierarchical differencing engine
-(<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a>) to walk the tree.
-<br>
-In addition every leaf of the tree must implement the
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
-interface in order to give the differencing engine access to its stream content.</p>
-<p>
-
-<a href="../reference/api/org/eclipse/compare/BufferedContent.html"><b>BufferedContent</b></a>
-provides a default implementation
-for the
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/IContentChangeNotifier.html"><b>IContentChangeNotifier</b></a>
-interfaces.
-Its subclass
-<a href="../reference/api/org/eclipse/compare/ResourceNode.html"><b>ResourceNode</b></a>
-adds an implementation for the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/ITypedElement.html"><b>ITypedElement</b></a>
-interfaces
-based on platform workbench resources
-(<a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>). 
-It can be used without modification as the input to the differencing engine.</p>
-
-
-<h3>Compare functionality outside of compare editors</h3>
-
-
-<p>If you want to use compare functionality outside of the standard compare editor 
-(for example, in a dialog or wizard) the compare plug-in provides additional helper
-classes.</p>
-
-<p>
-
-<a href="../reference/api/org/eclipse/compare/CompareViewerPane.html"><b>CompareViewerPane</b></a>
-is a convenience class which provides
-a label and local toolbar for a compare viewer (or any other subclass of a <a href="jface_viewers.htm"> JFace
-viewer</a>).&nbsp; Its abstract subclass
-<a href="../reference/api/org/eclipse/compare/CompareViewerSwitchingPane.html"><b>CompareViewerSwitchingPane</b></a>
-supports <b>dynamic viewer switching</b>, that is the viewer installed in the pane is dynamically 
-determined by the pane's input object.</p>
-
-<h3><a name="Single">Comparing a single file in an editor</a></h3>
-
-<p>The <a href="../reference/api/org/eclipse/compare/CompareEditorInput.html"><b>CompareEditorInput</b></a> supports
-the comparison of an arbitrary file/folder structure which can be displayed in an editor, dialog or view. 
-However, the specific case of comparing a single file in an editor warrants special handling because, in that case, the
-desired behavior should be close to that of editing the file. So, for this purpose a subclass of CompareEditorInput
-has been provided. The <a href="../reference/api/org/eclipse/team/ui/synchronize/SaveableCompareEditorInput.html">
-<b>SaveableCompareEditorInput</b></a> class provides this capability and has the following features:</p>
-<ul>
-<li>provides a static method <code>createFileElement</code> for creating a type element that represents a file.</li>
-<li>supports the use of shared documents (i.e. file buffers).</li>
-<li>supports the workbench Saveables API.</li>
-<li>auto-closes when changes are resolved.</li>
-<li>initializes asynchronously.</li>
-</ul>
-
-<h3><a name="Patch">Working with patches</a></h3>
-
-<p>The <a href="../reference/api/org/eclipse/compare/patch/ApplyPatchOperation.html"><b>ApplyPatchOperation</b></a> provides
-the ability to launch the Apply Patch wizard programmatically. The pages shown by the wizard are determined using the inputs to the operation.
-The class also contains the static method <code>parsePatch</code> which can be used by clients to deal with patches in a custom manner.
-
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm
deleted file mode 100644
index 9718638..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_contentviewer.htm
+++ /dev/null

@@ -1,190 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Implementing a Content Viewer</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Implementing a content viewer</H2>
-
-
-<p>
-The compare plug-in allows you to supply specialized viewers for viewing and
-merging content differences between unstructured elements.</p>
-
-
-<h3>
-Simple content viewers</h3>
-
-
-<p>
-A <b>content viewer</b> is used in places where only a single input is available and therefore
-no compare is necessary.&nbsp; A typical example for this is the &quot;<b>Restore from Local
-History</b>&quot; function.&nbsp; The <a href="../reference/extension-points/org_eclipse_compare_contentViewers.html"><b>org.eclipse.compare.contentViewers</b></a>
-extension point allows you to define a specialized content viewer that does not
-compare its inputs. </p>
-<pre>&lt;extension
-	point="org.eclipse.compare.contentViewers"&gt;
-	&lt;viewer
-		extensions="java,java2"
-		class="org.eclipse.jdt.internal.ui.compare.JavaTextViewerCreator"
-		id="org.eclipse.jdt.internal.ui.compare.JavaTextViewerCreator"&gt;
-	&lt;/viewer&gt;
-	&lt;contentTypeBinding
-		contentTypeId="org.eclipse.jdt.core.javaSource"
-		contentViewerId="org.eclipse.jdt.internal.ui.compare.JavaTextViewerCreator"&gt;
-	&lt;/contentTypeBinding&gt;
-&lt;/extension&gt;
-</pre>
-<p>Specialized viewers contributed by your plug-in are designated in the
-<b>viewer</b> element.  You must specify the <b>id </b>of the viewer and the <b>class</b> that
-creates it.  You may also specify any file <b>extensions</b> for which the content viewer should be used.&nbsp;&nbsp;</p>
-<p>You may also use the <b>contentTypeBinding</b> element to associate a <a href="runtime_content.htm">content type</a> 
-with a content viewer.  
-</p>
-<h3>Content merge viewers</h3>
-<p>	A <b> content merge viewer </b> performs a two-way or three-way compare of its inputs
-and presents the result side-by-side or in any other suitable way.&nbsp; The viewer lets the user 
-merge between the inputs.  Content merge viewers are common for text or images.</p>
-<p>If the standard merge viewers are not appropriate for your plug-in's
-function, you may choose to implement your own content merge viewer.&nbsp; Your
-content merge viewer should be registered with the platform using the
-<a href="../reference/extension-points/org_eclipse_compare_contentMergeViewers.html"><b>org.eclipse.compare.contentMergeViewers</b></a>
-extension point.&nbsp; The following markup shows
-the definition of specialized content merge viewers for viewing Java files and
-properties files in the Java IDE:
-</p>
-<pre>&lt;extension
-      point="org.eclipse.compare.contentMergeViewers"&gt;
-      &lt;viewer
-            extensions="java,java2"
-            class="org.eclipse.jdt.internal.ui.compare.JavaContentViewerCreator"
-            id="org.eclipse.jdt.internal.ui.compare.JavaContentViewerCreator"&gt;
-      &lt;/viewer&gt;
-      &lt;contentTypeBinding
-            contentTypeId="org.eclipse.jdt.core.javaSource"
-            contentMergeViewerId="org.eclipse.jdt.internal.ui.compare.JavaContentViewerCreator"&gt;
-	  &lt;/contentTypeBinding&gt;
-&lt;/extension&gt;
-&lt;extension
-      point="org.eclipse.compare.contentMergeViewers"&gt;
-      &lt;viewer
-            extensions="properties,properties2"
-            class="org.eclipse.jdt.internal.ui.compare.PropertiesFileMergeViewerCreator"
-            id="org.eclipse.jdt.internal.ui.compare.PropertiesFileMergeViewerCreator"&gt;
-      &lt;/viewer&gt;
-      &lt;contentTypeBinding
-            contentTypeId="org.eclipse.jdt.core.javaProperties"
-            contentMergeViewerId="org.eclipse.jdt.internal.ui.compare.PropertiesFileMergeViewerCreator"&gt;
-	  &lt;/contentTypeBinding&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-Similar to content viewers, specialized merge viewers contributed by your plug-in are designated in the
-<b>viewer</b> element.  You must specify the <b>id </b>of the viewer and the <b>class</b> that
-creates it.  You may also specify any file <b>extensions</b> for which the content merge viewer should be used.
-</p>
-<p>Also similar to content viewers, you can use <b>contentTypeBinding</b> to associate a <a href="runtime_content.htm">content type</a> 
-with a merge viewer.  The JDT plug-in binds content merge viewers to two different content types:  Java source and Java properties files.
-</p>
-
-
-<p> <a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a>
-is an abstract compare and merge viewer
-with two side-by-side content areas and an optional content area for a
-common ancestor (for three-way compare).&nbsp; Because the implementation makes
-no assumptions about the content type, the subclass is responsible for dealing
-with the specific content type.&nbsp;&nbsp;</p>
-
-
-<p> <b>ImageMergeViewer</b> in <b> org.eclipse.compare.internal</b> shows how to
-implement a simple merge viewer for images using a <a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a>.&nbsp;
-A <a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a> 
-accesses its model by means of a content
-provider which must implement the
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/IMergeViewerContentProvider.html"><b>IMergeViewerContentProvider</b></a> interface.</p>
-
-
-<h4><a name="Text">Text merging</a></h4>
-
-
-<p> If your viewer uses text, additional classes that&nbsp; compare
-and merge text content can be used.</p>
-<p>
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>
-is the concrete subclass of
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/ContentMergeViewer.html"><b>ContentMergeViewer</b></a>
- used for comparing and merging text content.&nbsp; A text merge viewer uses the
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifferencer.html"><b>RangeDifferencer</b></a>
-to perform a textual, line-by-line comparison of two (or three) input documents.</p>
-<p>
-For text lines that differ, the
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>
-uses an
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/ITokenComparator.html"><b>ITokenComparator</b></a>
-to find the longest sequences of matching and non-matching tokens.
-The 
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>'s
-default token compare works on characters separated by white space. If a
-different strategy is needed (for example, Java tokens in a Java-aware
-merge viewer), clients can create their own token comparators by implementing
-the
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/ITokenComparator.html"><b>ITokenComparator</b></a>
-interface.</p>
-<p>
- <a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a>
- works on whole documents and on sub ranges of documents. For partial documents,
-the viewer's input must adapt to an
-<a href="../reference/api/org/eclipse/compare/contentmergeviewer/IDocumentRange.html"><b>IDocumentRange</b></a>
-instead of an
-<a href="../reference/api/org/eclipse/jface/text/IDocument.html"><b>IDocument</b></a>.</p>
-
-<p>The <a href="../reference/api/org/eclipse/compare/contentmergeviewer/TextMergeViewer.html"><b>TextMergeViewer</b></a> also
-supports the use of a shared document (i.e. document's that are shared by multiple open editors) when the input adapts to an 
-<a href="../reference/api/org/eclipse/compare/ISharedDocumentAdapter.html"><b>ISharedDocumentAdapter</b></a>. Subclasses of
-TextMergeViewer that provide syntax highlighting must implement both the <code>getDocumentPartitioner()</code> and
-<code>getDocumentPartitioning()</code> methods to support shared documents.	</p>
-
-<h4>Range differencing</h4>
-<p> 
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifferencer.html"><b>RangeDifferencer</b></a>
- finds the longest sequences of matching and
-non-matching comparable entities in text content. Its implementation is based on
-an objectified version of the algorithm by Eugene W. Myers found <a href="http://citeseer.ist.psu.edu/myers86ond.html">here</a>.
- Clients must supply
-an input to the differencer that implements the
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b></a>
-interface.
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b></a>
-breaks the input data into a sequence
-of entities and provides a method for comparing
-one entity with the entity in another
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b></a>.
-</p><p>
-For example, to compare two text documents and find the longest common
-sequences of matching and non-matching lines,
-the implementation of
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/IRangeComparator.html"><b>IRangeComparator</b> </a>
-must break the document into lines and provide a method for testing
-whether two lines are considered equal.
-See <b>org.eclipse.compare.internal.DocLineComparator</b> for an example of how this can be done.</p>
-<p>The differencer returns the differences among these sequences as an
-array of
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifference.html"><b>RangeDifference</b></a>
-objects.
-Every single
-<a href="../reference/api/org/eclipse/compare/rangedifferencer/RangeDifference.html"><b>RangeDifference</b></a>
-describes the kind of difference
-(no change, change, addition, deletion) and the corresponding ranges
-of the underlying comparable entities in the two or three inputs.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm
deleted file mode 100644
index 006685f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_streammerger.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Merging multiple files</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Merging multiple files</H2>
-<p>
-In some cases, the ability to merge files without the assist of a user
-is desirable.  The extension point
-<a href="../reference/extension-points/org_eclipse_team_core_storageMergers.html"><b>org.eclipse.team.core.storageMergers</b></a>
-allows you to contribute a class that merges three different files (or storage units) into a single output stream. Storage mergers
-can be associated with file extensions or bound to a particular content type.  The Platform defines a storage
-merger for merging three files of plain text:</p>
-<pre>&lt;extension
-	point="org.eclipse.team.core.storageMergers"&gt;
-	&lt;storageMerger
-		extensions="txt"
-		class="org.eclipse.team.internal.ui.mapping.TextStorageMerger"
-		id="org.eclipse.team.ui.textStorageMerger"&gt;
-	&lt;/storageMerger&gt;
-	&lt;contentTypeBinding
-		contentTypeId="org.eclipse.core.runtime.text"
-		streamMergerId="org.eclipse.team.ui.textStorageMerger"&gt;
-	&lt;/contentTypeBinding&gt;
-&lt;/extension&gt;
-</pre>
-<p>The storage merger itself is described in the <b>storageMerger</b> element.  You must specify the <b>id </b>of the 
-merger and the <b>class</b> that implements it.  You may also specify any file <b>extensions</b> for which the 
-the storage merger should be used.</p>
-<p>You may also use the <b>contentTypeBinding</b> element to associate a <a href="runtime_content.htm">content type</a> 
-with a storage merger.
-</p>
-<p>
-Storage mergers must implement 
-<a href="../reference/api/org/eclipse/team/core/mapping/IStorageMerger.html"><b>IStorageMerger</b></a>.
-This simple interface merges the contents from three different storage units into a single output stream.
-The not-so-simple implementation depends upon your plug-in and its content types.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm b/bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm
deleted file mode 100644
index f86a3f7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/compare_structureviewer.htm
+++ /dev/null

@@ -1,170 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Implementing a structure viewer</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Implementing a structure viewer</H2>
-<p>
-A structure merge viewer performs a two-way or three-way compare of its inputs, presents the result
-in a hierarchical view, and lets the user merge between the inputs.&nbsp;
-Structure merge viewers are common for workspace resources or the members of
-an archive file.</p>
-<h3>Tree-like structure viewers</h3>
-<p>Because the implementation of many structure compare viewers is based
-on a tree, the compare plug-in provides a generic tree-based
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>.
-Your plug-in is responsible for supplying a <b>structure creator</b>  that breaks a single input object into a hierarchical structure.
-The <a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>
-performs the compare on the resulting structure and displays the result as a tree.</p>
-<p>You designate a structure creator for your plug-in using the <a href="../reference/extension-points/org_eclipse_compare_structureCreators.html"><b>org.eclipse.compare.structureCreators</b></a>
-extension.  Much like content viewers, a structure creator can be specified for a set of file <b>extensions</b>, or
-a <b>contentTypeBinding</b> can be used to associate a <a href="runtime_content.htm">content type</a> with a particular
-structure creator.  We won't review the markup here since it's so similar to content viewers.
-The JDT plug-in defines several contributions for 
-<a href="../reference/extension-points/org_eclipse_compare_structureCreators.html"><b>org.eclipse.compare.structureCreators</b></a>.</p>
-
-<h3>Other hierarchical structure viewers</h3>
-<p>In some cases, the tree-based <a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>
-may not be appropriate for your plug-in.&nbsp; The <a href="../reference/extension-points/org_eclipse_compare_structureMergeViewers.html"><b>org.eclipse.compare.structureMergeViewers</b></a>
-extension point allows you to define your own implementation for a structure
-merge viewer.  A structure merge viewer can be specified for file <b>extensions</b>, or
-a <b>contentTypeBinding</b> can be used to associate a <a href="runtime_content.htm">content type</a> with a particular
-structure merge viewer.  See the JDT plug-in for examples of
-<a href="../reference/extension-points/org_eclipse_compare_structureMergeViewers.html"><b>org.eclipse.compare.structureMergeViewers</b></a>
-contributions.</p>
-
-<h4>
-Differencer&nbsp;</h4>
-
-
-<p>
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a>
-is a differencing engine for hierarchically
-structured data. It takes two or three inputs and performs a two-way or
-three-way compare on them.</p>
-
-
-<p>
-
-If the input elements to the differencing engine implement the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-interface, the engine recursively applies itself to the children of
-the input element. Leaf elements must implement the
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
-interface so that the differencer can perform a byte wise comparison on their contents.</p><p>There
-are several good examples of differencers included in the platform
-implementation:</p>
-<ul>
-  <li>
-<a href="../reference/api/org/eclipse/compare/ResourceNode.html"><b>ResourceNode</b></a>
- implements both interfaces
-(and more) for platform workspace resources
-(<a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>org.eclipse.core.resources.IResource</b></a>).</li>
-  <li>
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DocumentRangeNode.html"><b>DocumentRangeNode</b></a>
-    is used to compare hierarchical structures
-that are superimposed on a document.&nbsp; Nodes and leaves correspond to ranges in a document
-(<a href="../reference/api/org/eclipse/compare/contentmergeviewer/IDocumentRange.html"><b>IDocumentRange</b></a>).&nbsp;
-    Typically, <a href="../reference/api/org/eclipse/compare/structuremergeviewer/DocumentRangeNode.html"><b>DocumentRangeNode</b></a>s
-are created while parsing a document and they represent
-the semantic entities of the document (e.g. a Java class, method or field).
-The two subclasses <b>JavaNode</b> (in <b>org.eclipse.jdt.internal.ui.compare</b>)
-and <b>PropertyNode</b> (in <b>org.eclipse.jdt.internal.ui.compare</b>) are good examples for this.</li>
-</ul>
-<p>
-
-By default the differencing engine returns the result of the compare operation
-as a tree of
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffNode.html"><b>DiffNode</b></a>
-objects.&nbsp; A
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffNode.html"><b>DiffNode</b></a>
-describes the changes among two or three inputs.&nbsp; The type of result nodes
-can be changed by overriding
-a single method of the engine.</p>
-<h4>Difference Viewers</h4>
-<p>
-
-A tree of
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffNode.html"><b>DiffNode</b></a>s
-can be displayed in a 
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a>.
-The
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a>
-requires that inner nodes of the tree implement
-the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IDiffContainer.html"><b>IDiffContainer</b></a>
-interface and leaves implement the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IDiffElement.html"><b>IDiffElement</b></a>
-interface.</p>
-<p>
-
-The typical steps to compare hierarchically structured data and to display
-the differences are as follows:</p>
-<ol>
-<li>
-Map the input data into a tree of objects implementing both the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
- interfaces</li>
-
-<li>
-Perform the compare operation by means of the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a></li>
-
-<li>
-Feed the differencing result into the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a></li>
-
-</ol>
-<p>
-The
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureDiffViewer.html"><b>StructureDiffViewer</b></a>
-is a specialized
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/DiffTreeViewer.html"><b>DiffTreeViewer</b></a>
-that automates the three steps from above. It takes a single input object
-of type
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/ICompareInput.html"><b>ICompareInput</b></a>
-from which it retrieves the two or three
-input elements to compare.&nbsp; It uses an
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureCreator.html"><b>IStructureCreator</b></a>
-to extract a tree containing <a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>
-and
-<a href="../reference/api/org/eclipse/compare/IStreamContentAccessor.html"><b>IStreamContentAccessor</b></a>
- objects from them.&nbsp; These trees are then compared with the differencing engine and
-the result is displayed in the tree viewer.
-</p>
-<p>
-The
-<a href="../reference/api/org/eclipse/compare/ZipFileStructureCreator.html"><b>ZipFileStructureCreator</b></a>
-is an implementation of the
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureCreator.html"><b>IStructureCreator</b></a>
-interface and makes the contents of a zip archive available as a
-hierarchical structure of
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/IStructureComparator.html"><b>IStructureComparator</b></a>s
-which can be easily compared
-by the differencing engine
-(<a href="../reference/api/org/eclipse/compare/structuremergeviewer/Differencer.html"><b>Differencer</b></a>).
-It is a good example for how to make structured files available to the hierarchical 
-compare functionality of the compare plug-in.</p>
-
-<a name="Text"></a>
-<p>
-For text based inputs, clients should subclass the <a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureCreator.html"><b>StructureCreator</b></a>
-class. This will enable the use of a shared document between multiple editors open on the same file. 
-Subclasses of
-StructureCreator that provide syntax highlighting must implement both the <code>getDocumentPartitioner()</code> and
-<code>getDocumentPartitioning90</code> methods to support shared documents.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug.htm
deleted file mode 100644
index c5112cd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Program debug and launch support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Program debug and launch support</H1>
-<p>The resources plug-in in the Eclipse platform allows you to manage a set of
-source files for a program and compile them using an incremental project
-builder.&nbsp; Plug-ins can define new builders that handle special resource
-types, such as source files for a particular programming language.&nbsp; Once an
-executable program is built with your plug-in's builder, how can you make sure
-that it gets invoked correctly?</p>
-<p>The <b><a href="../reference/api/org/eclipse/debug/core/package-summary.html"> org.eclipse.debug.core</a>
-</b> plug-in provides the API that allows a program to define a configuration
-for launching a program.&nbsp; The program can be launched in different modes.  For
-example, it could be launched for regular execution, for debugging, for profiling,
-or any other mode defined by your plug-in.&nbsp; The
-Eclipse Java development tooling (JDT) uses the platform debug support to launch
-Java VM's and the Java debugger.&nbsp;&nbsp;</p>
-<p>The <b><a href="../reference/api/org/eclipse/debug/ui/package-summary.html"> org.eclipse.debug.ui</a></b> plug-in includes support for user configuration of
-launch parameters and utility classes that ease the implementation of powerful debuggers.</p>
-<p>There are some shared concepts in launching and debugging programs that are
-implemented in the platform debug support.&nbsp; However, the best way to
-understand how to use the platform debug support is to study a robust concrete
-implementation of launching and debugging, such as the JDT launching and debug
-tools.&nbsp; We'll review the major concepts of the platform debug support in the context
-of the JDT concrete implementation.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm
deleted file mode 100644
index ec69461..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_breakpoints.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Breakpoints</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Breakpoints </h3>
-<p>Breakpoints allow users to suspend the execution of a program at a particular
-location. Breakpoints are typically shown in the UI along with the source
-code. When a breakpoint is encountered during execution of a program, the program suspends
-and triggers a <b>SUSPEND</b> debug event with <b>BREAKPOINT</b> as the
-reason.</p>
-<p>If your plug-in needs to show breakpoints in its UI, you can add an 
-<a href="../reference/api/org/eclipse/debug/core/IBreakpointListener.html"><b>IBreakpointListener</b></a>
-to the <a href="../reference/api/org/eclipse/debug/core/IBreakpointManager.html"><b>IBreakpointManager</b></a>.
-The <a href="../reference/api/org/eclipse/debug/core/IBreakpointManager.html"><b>IBreakpointManager</b></a> is the
-central authority over all breakpoints.  Breakpoints are added and removed using the breakpoint manager, which in
-turn informs any listeners about breakpoint activity.  The operation of breakpoints can be enabled or disabled
-using the breakpoint manager.  The breakpoint manager can be obtained from the 
-<a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>:</p>
-<pre>
-IBreakpointManager mgr = DebugPlugin.getDefault().getBreakpointManager();
-</pre>
-<p>Plug-ins that define their own debug models and launch configurations often
-need to define their own breakpoint types. You can implement breakpoints
-for your particular debug model by defining a class that implements 
-<a href="../reference/api/org/eclipse/debug/core/model/IBreakpoint.html"><b>IBreakpoint</b></a>.</p>
-<p>Breakpoints are implemented using <a href="resAdv_markers.htm">resource markers</a>.
-Recall that resource markers allow you to associate meta information about a 
-resource in the form of named attributes. By implementing a breakpoint 
-using markers, the debug model can make use of all the existing marker function 
-such as persistence, searching, adding, deleting, and displaying in editors.</p>
-<p>Why is it important to know about markers when using breakpoints?&nbsp; When
-you create a breakpoint type, you must also specify an associated marker
-type. Every extension of <a href="../reference/extension-points/org_eclipse_debug_core_breakpoints.html"><b>org.eclipse.debug.core.breakpoints</b></a>
-should be accompanied by an extension of <a href="../reference/extension-points/org_eclipse_core_resources_markers.html"><b>org.eclipse.core.resources.markers</b></a>.&nbsp;
-This is best demonstrated by looking at the extensions defined by the Java
-tooling for Java breakpoints.</p>
-<pre>&lt;extension id=&quot;javaBreakpointMarker&quot; point=&quot;org.eclipse.core.resources.markers&quot;&gt;
-	&lt;super type=&quot;<b>org.eclipse.debug.core.breakpointMarker</b>&quot;/&gt;
-&lt;/extension&gt;
-
-&lt;extension id=&quot;<b>javaExceptionBreakpointMarker</b>&quot; point=&quot;org.eclipse.core.resources.markers&quot;&gt;
-	&lt;super type=&quot;org.eclipse.jdt.debug.javaBreakpointMarker&quot;/&gt;
-	&lt;persistent value=&quot;true&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.jdt.debug.core.caught&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.jdt.debug.core.uncaught&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.jdt.debug.core.checked&quot;/&gt;
-&lt;/extension&gt;</pre>
-<pre>&lt;extension point=&quot;org.eclipse.debug.core.breakpoints&quot;&gt;
-	&lt;breakpoint
-		id=&quot;javaExceptionBreakpoint&quot;
-		markerType=&quot;<b>org.eclipse.jdt.debug.javaExceptionBreakpointMarker</b>&quot;
-		class=&quot;org.eclipse.jdt.internal.debug.core.breakpoints.JavaExceptionBreakpoint&quot;&gt;
-	&lt;/breakpoint&gt;
-&lt;/extension&gt;</pre>
-<p>The debug plug-in defines a special type of marker, <b>org.eclipse.debug.core.breakpointMarker</b>.
-When you define a breakpoint marker for your debugger, you should declare it using this marker as a super 
-type. This allows the debug model to find all possible breakpoints within 
-a source file by searching for subtypes of its marker. In the example 
-above, the <b>javaExceptionBreakpointMarker</b> has a super type, <b>javaBreakpointMarker</b>, 
-whose super type is the <b>breakpointMarker</b>. The <b>javaExceptionBreakpoint</b> 
-(defined in the breakpoint extension) designates the <b>javaExceptionBreakpointMarker</b> 
-as its marker.</p>
-<p>What does all of this mean? When the debug code obtains
-a source code file, it can search for all markers whose super type is 
-<b>org.eclipse.debug.core.breakpointMarker</b>. Having found all of the markers, it can then 
-use the extension registry to map the markers to their associated breakpoint classes.
-In this way, the platform debug code can generically find all breakpoint types that have been set on a
-particular source file. </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm
deleted file mode 100644
index 54460c0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_debug.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Debugging a program</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Debugging a program</h2>
-<p>When you define a <a href="debug_launch.htm">launch configuration</a> for
-running a program, you can specify which modes (run, debug, profile, etc.) are supported
-by your program.  If you support debug mode, then you need to implement a debug
-model and UI that allow users to interact with your programs while they are under debug.
-The core platform debug plug-in provides support for:</p>
-<ul>
-  <li> a generic debug model</li>
-  <li>debug events and listeners</li>
-  <li>breakpoint management</li>
-  <li>expression management</li>
-</ul>
-<p>The debug UI plug-in provides a framework for showing your debug model in the UI.  It also includes
-utility classes for implementing common UI tasks.</p>
-<p>Since it's difficult to discuss generic debugging in any meaningful detail,
-we'll review the platform debug model and UI classes from the perspective of the
-Java debugger.</p>
-<p><a href="http://www.eclipse.org/articles/Article-Debugger/how-to.html">How to Write an Eclipse Debugger</a> 
-provides a start to finish example for building a debugger using a simple push down automata (PDA)
-assembly language as an example.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm
deleted file mode 100644
index 3993e9e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_expressions.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Expressions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Expressions</h3>
-<p>An <b>expression</b> is a snippet of code that can be evaluated to produce a
-value. The context for an expression depends on the particular debug
-model. Some expressions may need to be evaluated at a specific location in
-the program so that its variables can be referenced.
-<a href="../reference/api/org/eclipse/debug/core/model/IExpression.html"><b>IExpression</b></a>
-defines a general interface for debug expressions.</p>
-<p>An expression manager (<a href="../reference/api/org/eclipse/debug/core/IExpressionManager.html"><b>IExpressionManager</b></a>)
-keeps track of all of the expressions in the workspace. It will also fire
-events to interested listeners as expressions are added, removed, or changed.</p>
-<p>Expressions can be used to implement &quot;inspectors,&quot; or &quot;scrapbooks&quot; that let users evaluate
-code snippets. The Java tooling uses expressions to implement the
-expression generated when the user inspects the source code.</p>
-<p>A <b>watch expression</b> is an expression that is repeatedly evaluated as the program executes.
-<a href="../reference/api/org/eclipse/debug/core/model/IWatchExpression.html"><b>IWatchExpression</b></a>
-defines a specialized kind of <a href="../reference/api/org/eclipse/debug/core/model/IExpression.html"><b>IExpression</b></a>
-that updates the value of the expression when supplied with a new debug context.  Watch expressions are used to implement
-&quot;watch lists,&quot; which show changes in the value of an expression as the program executes.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm
deleted file mode 100644
index 7684722..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launching a program</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Launching a program</h2>
-<p>The platform debug plug-ins allow your plug-in to extend the platform so that your
-partiticular type of program can be launched from the workbench, obtaining input from the user if
-necessary.  A unique type of program that can be launched in the platform is called a
-<b>launch configuration type</b>. The class 
-<a href="../reference/api/org/eclipse/debug/core/ILaunchConfiguration.html"><b>ILaunchConfiguration</b></a>
-is used to describe a type of configuration.  A launch
-configuration keeps a set of named attributes that can be used to store data
-specific for a particular kind of launcher.</p>
-<p>For each launch configuration type, there are different <b>modes</b> in which the 
-configuration can be launched.  The platform defines modes for running, debugging, 
-or profiling a program defined by a particular configuration.  Plug-ins are free to implement 
-any or all of these launch modes for their 
-particular launch configuration, or define new launch modes for any launch
-configuration.</p>
-<p>Plug-ins that contribute additional types of launchers do so by providing an 
-<a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate.html"><b>ILaunchConfigurationDelegate</b></a>
-(or <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate2.html"><b>ILaunchConfigurationDelegate2</b></a>)
-that knows how to launch a program given the expected type and mode for launch configuration.&nbsp; Once the program
-is launched, an <a href="../reference/api/org/eclipse/debug/core/ILaunch.html"><b>ILaunch</b>
-</a>object is used to represent the launched session.&nbsp; This object can be
-queried for information such as running processes, debug session information,
-and source code location.&nbsp; A launch knows the configuration that was used to create
-it.&nbsp; </p>
-<p><img alt="" border="0" src="images/launch.jpg" > </p>
-<p>Users interact with a launch
-configuration dialog to set up the parameters for different types of
-launches. These configurations can be
-stored in a file to be shared with other users or stored locally in the workspace.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm
deleted file mode 100644
index 8f0baa9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_adding.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Adding launchers to the platform</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Adding launchers to the platform</h3>
-<p>Your plug-in can add launch configuration types to the platform using the <a href="../reference/extension-points/org_eclipse_debug_core_launchConfigurationTypes.html"><b>org.eclipse.debug.core.launchConfigurationTypes</b></a>
-extension point.&nbsp; This extension point allows you to declare a
-configuration type using a unique id.&nbsp; You must provide a corresponding
-implementation of <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate.html"><b>ILaunchConfigurationDelegate</b></a>.
-The delegate is responsible for launching its launch configuration in a specified mode.  
-Optionally, you can implement <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate2.html"><b>ILaunchConfigurationDelegate2</b></a>,
-which enhances the delegate interface to allow your delegate to abort a launch, build relevant projects in the workspace
-before a launch, and control the creation of the launch object that is used in a launch.
-</p>
-<p>
-In addition to defining the delegate, you can specify which launch modes are supported
-by your delegate, and a name that should be used when showing launchers
-of this type to the user.</p>
-<p>The following markup shows how the Java tools declare a Java launch
-configuration for launching local Java programs:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.launchConfigurationTypes&quot;&gt;
-   &lt;launchConfigurationType
-   	   id=&quot;org.eclipse.jdt.launching.localJavaApplication&quot;
-	   <b>name=&quot;%localJavaApplication&quot;
-	   delegate=&quot;org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunchConfigurationDelegate&quot;
-	   modes= &quot;run, debug&quot;</b>
-	   sourceLocatorId=&quot;org.eclipse.jdt.launching.sourceLocator.JavaSourceLookupDirector&quot;
-       sourcePathComputerId=&quot;org.eclipse.jdt.launching.sourceLookup.javaSourcePathComputer&quot;&gt;
-   &lt;/launchConfigurationType&gt;
-&lt;/extension&gt;</pre>
-<p>This extension defines a launch configuration delegate that can be used to run or debug programs that
-are launched using the local Java launch configuration.</p>
-<h4>Defining new launch modes</h4>
-<p>We mentioned previously that the platform defines launch modes for running, debugging, or profiling
-a program.  These modes are defined using the <a href="../reference/extension-points/org_eclipse_debug_core_launchModes.html"><b>org.eclipse.debug.core.launchModes</b></a>
-extension point. This extension point allows you to declare a launch mode by defining its string mode
-name and the label that should be shown to the user to describe the mode.  The following markup shows 
-the definition of the platform's three standard launch modes:</p>
-<pre>
-&lt;extension point="org.eclipse.debug.core.launchModes"&gt;
-	&lt;launchMode
-		label="%run"
-		mode="run"&gt;
-	&lt;/launchMode&gt;
-	&lt;launchMode
-		label="%debug"
-		mode="debug"&gt;
-	&lt;/launchMode&gt;
-	&lt;launchMode
-		label="%profile"
-		mode="profile"&gt;
-	&lt;/launchMode&gt;
-&lt;/extension&gt;
-</pre>
-<p>Note that the mode is not associated with any particular launch configuration type.  As shown earlier, that association
-occurs when a launch delegate is specified for a configuration type.  </p>
-<h4>Defining launch delegates</h4>
-<p>Since launch modes can be specified independently of launch configuration types, it's possible that new modes
-are defined that are not implemented by the original delegate for a launch configuration.  In this case, a plug-in
-may define a launch delegate that implements a particular mode for a particular launch configuration type.
-This can be done using the <a href="../reference/extension-points/org_eclipse_debug_core_launchDelegates.html"><b>org.eclipse.debug.core.launchDelegates</b></a>
-extension point. This extension point allows you to define a launch delegate that implements the specified modes
-for a given configuration type.  The following markup shows how you could define a delegate for profiling
-a local Java application:</p>
-<pre>
-&lt;extension point="org.eclipse.debug.core.launchDelegates"&gt;
-  &lt;launchDelegate
-   id=&quot;com.example.MyJavaProfileDelegate&quot;
-   delegate=&quot;com.example.MyJavaProfileDelegate&quot;
-   type=&quot;org.eclipse.jdt.launching.localJavaApplication&quot;
-   modes=&quot;profile&quot;&gt;
-  &lt;/launchDelegate&gt;
- &lt;/extension&gt;
-</pre>
-<p>The specification of the delegate is similar to the way it is done when defining a launch configuration
-type, except that in this case the type of launch configuration is specified along with the supported
-modes.  As seen previously, the delegate must implement <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate.html"><b>ILaunchConfigurationDelegate</b></a>,
-and can optionally implement <a href="../reference/api/org/eclipse/debug/core/model/ILaunchConfigurationDelegate2.html"><b>ILaunchConfigurationDelegate2</b></a> for
-more control over the launch sequence.</p>
-<h4>Other references</h4>
-<p><a href="http://www.eclipse.org/articles/Article-Launch-Framework/launch.html">We Have Lift-off: The Launching Framework in Eclipse</a> 
-provides a start to finish example for defining your own launch type.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm
deleted file mode 100644
index 91689dd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_comparators.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Comparing launch configurations</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h4>Comparing launch configurations</h4>
-<p>We've seen how a plug-in can use named attributes and values to store important data with a
-launch configuration. Since the interpretation of a plug-in's attributes are not known by the platform, 
-an extension point is provided that allows you to supply a comparator for a specific attribute.
-This comparator is used to determine whether attributes of the specified name are
-equal. In many cases, the simple string compare provided by
-java.lang.Object.equals(Object) is suitable for comparing attributes. This
-technique will be used if no comparator has been provided. However, some attribute values
-may require special handling, such as stripping white space values from text
-before comparing for equality. </p>
-<p>Comparators are contributed using the <a href="../reference/extension-points/org_eclipse_debug_core_launchConfigurationComparators.html"><b>org.eclipse.debug.core.launchConfigurationComparators</b></a>
-extension point.&nbsp; </p>
-<p>The Java tools supply launch configuration comparators for comparing program
-source paths and class paths.</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.launchConfigurationComparators&quot;&gt;
-	&lt;launchConfigurationComparator
-		id = &quot;org.eclipse.jdt.launching.classpathComparator&quot;
-		class = &quot;org.eclipse.jdt.internal.launching.RuntimeClasspathEntryListComparator&quot;
-		attribute = &quot;org.eclipse.jdt.launching.CLASSPATH&quot;/&gt;
-	&lt;launchConfigurationComparator
-		id = &quot;org.eclipse.jdt.launching.sourcepathComparator&quot;
-		class = &quot;org.eclipse.jdt.internal.launching.RuntimeClasspathEntryListComparator&quot;
-		attribute = &quot;org.eclipse.jdt.launching.SOURCE_PATH&quot;/&gt;		
-&lt;/extension&gt;</pre>
-<p>Comparators must implement the interface <b>java.util.Comparator</b>.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm
deleted file mode 100644
index 2469c77..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_java.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launching Java applications</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Launching Java applications</h4>
-<p>
-In <a href="debug_launch_processfactories.htm">Process factories</a>, we saw how a system process is used to invoke
-a program and how wrapping it with an <a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>
-allows clients to access launch-related information about the process.  These techniques are general and can be used to launch
-any external program from the platform.
-</p>
-<p>Additional classes provided in the <b>org.eclipse.jdt.debug</b> plug-in provide support for launching a specific JRE with a specified
-classpath, arguments, VM arguments, and a main type.  See the following references for more specific information about launching
-a Java application:</p>
-<ul>
-<li><a href="http://www.eclipse.org/articles/Article-Java-launch/launching-java.html">Launching Java Applications Programmatically</a> </li>
-<li><a href="http://www.eclipse.org/articles/Article-Launch-Framework/launch.html">We Have Lift-off: The Launching Framework in Eclipse</a></li>
-</ul>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm
deleted file mode 100644
index 1260051..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_processfactories.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Process factories</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Process factories</h4>
-<p>When a launch configuration launches its program, it is responsible for invoking the executable
-program in the requested mode.  The implementation for a launch will depend on the specifics of
-each launch configuration, but most plug-ins will build a command line and call a runtime exec to start
-the program.  The <a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>
-class implements a convenience method for invoking a runtime exec and handling the possible exceptions.
-Clients can specify the command line and working directory for the exec.
-</p>
-<pre>
-Process p = DebugPlugin.exec(cmdLine, workingDirectory);
-</pre>
-<p>Once the <b>java.lang.Process</b> for the executing program has been created, it needs to be managed by the
-debug plug-in.  For starters, the process needs to be associated with the
-<a href="../reference/api/org/eclipse/debug/core/ILaunch.html"><b>ILaunch</b></a>
-that represents the launched program.  The debug plug-in defines a wrapper for a system process,
-<a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>,
-that allows clients to access the associated <a href="../reference/api/org/eclipse/debug/core/ILaunch.html"><b>ILaunch</b></a>
-and assign their own named attributes to the process.  In addition, 
-<a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>,
-defines a label for the process and associates an <a href="../reference/api/org/eclipse/debug/core/model/IStreamsProxy.html"><b>IStreamsProxy</b></a>
-with the process that gives clients access to the input, output, and error streams of the system process.  This process wrapper
-can also be created using a utility method in
-<a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>.
-</p>
-<pre>
-IProcess process= DebugPlugin.newProcess(launch, p, "My Process);
-</pre>
-<p>
-A map of named attributes can also be supplied.
-</p>
-<p>
-Many plug-ins can simply rely on the utility methods in <a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>
-for launching the system process and wrapping it in an <a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a>.
-For those plug-ins that need more control in the creation of the wrapper, a <b>process factory</b> can be associated with a launch
-configuration.  The process factory is used to create an <a href="../reference/api/org/eclipse/debug/core/model/IProcess.html"><b>IProcess</b></a> 
-that meets the special needs of the plug-in.   The process factory is referenced by id, and should be stored in the
-<b>DebugPlugin.ATTR_PROCESS_FACTORY_ID</b> attribute of the launch configuration.</p>
-<p>The association between the process factory id and the class that implements it is made using the
-<a href="../reference/extension-points/org_eclipse_debug_core_processFactories.html"><b>org.eclipse.debug.core.processFactories</b></a>
-extension point.</p>
-<p>The following example shows how the Ant plug-in sets up a process factory for its launches:</p>
-<pre>
-&lt;extension point=&quot;org.eclipse.debug.core.processFactories&quot;&gt;
-	&lt;processFactory
-		class=&quot;org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntProcessFactory&quot;
-		id=&quot;org.eclipse.ant.ui.remoteAntProcessFactory&quot;&gt;
-	&lt;/processFactory&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-It is the responsibility of the registering plug-in to store the process factory id in the proper launch configuration attribute.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm
deleted file mode 100644
index cee4714..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_sourcelocators.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Obtaining a program's source code</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h4>Obtaining a program's source code</h4>
-<p>For certain kinds of launch modes, it may be important to obtain the source code that corresponds
-with the current execution point in the code.  This is typically important when debugging or profiling
-a program.  Several different extension points are provided by the debug plug-in that allow plug-ins to
-register classes that can assist with locating source code.</p>
-<h5>Source locators</h5>
-<p>
-<a href="../reference/api/org/eclipse/debug/core/model/ISourceLocator.html"><b>ISourceLocator</b></a>
-and <a href="../reference/api/org/eclipse/debug/core/model/IPersistableSourceLocator.html"><b>IPersistableSourceLocator</b></a>
-define interfaces for mapping from an executing program back to the source
-code. </p>
-<p>Source locators are typically implemented to work with a corresponding launch
-configuration and launch configuration delegate.  A source locator id may be specified when a launch configuration
-type is defined, or it may be associated programmatically with a launch configuration using the 
-<b>ILaunchConfiguration.ATTR_SOURCE_LOCATOR_ID</b> attribute.  In either case, at some point the id
-of a source locator for a configuration must be resolved to the class that actually implements 
-<a href="../reference/api/org/eclipse/debug/core/model/IPersistableSourceLocator.html"><b>IPersistableSourceLocator</b></a>.
-The association between a source locator id and its class is established using the 
-<a href="../reference/extension-points/org_eclipse_debug_core_sourceLocators.html"><b>org.eclipse.debug.core.sourceLocators</b></a>
-extension point.</p>
-<p>The following markup is from the Java tooling:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.sourceLocators&quot;&gt;
-	&lt;sourceLocator
-		id = &quot;org.eclipse.jdt.debug.ui.javaSourceLocator&quot;
-	   	class=&quot;org.eclipse.jdt.debug.ui.JavaUISourceLocator&quot;
-	   	name=&quot;%javaSourceLocator&quot;/&gt;
-&lt;/extension&gt;</pre>
-<p>Since launch configurations can be persisted, source locator ids may will be stored
-with the launch configuration.  When it's time to instantiate a source locator, the
-debug plug-in looks up the source locator id attribute and instantiates the class associated with
-that id.</p>
-<p>The implementation for source lookup necessarily depends on the type of program being launched.  However, the platform
-defines an abstract implementation for a source locator that looks up source files on a given path that includes
-directories, zip files, jar files, and the like.  To take advantage of this implementation, your plug-in can extend
-<a href="../reference/api/org/eclipse/debug/core/sourcelookup/AbstractSourceLookupDirector.html"><b>AbstractSourceLookupDirector</b></a>.
-All that is needed from the specific implementation is the ability to provide an appropriate
-<a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceLookupParticipant.html"><b>ISourceLookupParticipant</b></a>, which can
-map a stack frame to a file name. See the extenders of <a href="../reference/api/org/eclipse/debug/core/sourcelookup/AbstractSourceLookupDirector.html"><b>AbstractSourceLookupDirector</b></a>.
-for examples.</p>
-<h5>Source path computers</h5>
-<p>The <a href="../reference/api/org/eclipse/debug/core/sourcelookup/AbstractSourceLookupDirector.html"><b>AbstractSourceLookupDirector</b></a>
-searches for source files according to a particular source code lookup path.  This path is expressed as an array of
-<a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceContainer.html"><b>ISourceContainer</b></a>.  The source containers
-that should be searched for source are typically computed according to the particulars of the source configuration that is being
-launched.  <a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourcePathComputer.html"><b>ISourcePathComputer</b></a>
-defines the interface for an object that computes the appropriate source path for a launch configuration.  A source path computer,
-much like a source locator, is specified by id, and can be specified in the extension definition for a launch configuration type, or 
-associated programmatically by setting the <b>ISourceLocator.ATTR_SOURCE_PATH_COMPUTER_ID</b> attribute for the launch configuration.
-The id for a source path computer is associated with its implementing class in the
-<a href="../reference/extension-points/org_eclipse_debug_core_sourcePathComputers.html"><b>org.eclipse.debug.core.sourcePathComputers</b></a>
-extension point.  The following markup shows the definition used by JDT for its Java source path computer:
-</p>
-<pre>
-&lt;extension point=&quot;org.eclipse.debug.core.sourcePathComputers&quot;&gt;
-	&lt;sourcePathComputer
-		id=&quot;org.eclipse.jdt.launching.sourceLookup.javaSourcePathComputer&quot;
-		class=&quot;org.eclipse.jdt.launching.sourcelookup.containers.JavaSourcePathComputer&quot;&gt;
- 	&lt;/sourcePathComputer&gt;
- 	...
-</pre>
-<p>
-The source path computer is responsible for computing an array of <a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceContainer.html"><b>ISourceContainer</b></a>
-that represents the source lookup path.  For example, the Java source path computer considers the classpath when building the
-path. 
-</p>
-<h5>Source container types</h5>
-<p>The containers specified as part of a source lookup path must implement <a href="../reference/api/org/eclipse/debug/core/sourcelookup/ISourceContainer.html"><b>ISourceContainer</b></a>,
-which can search the container represented for a named source element.  Different kinds of source containers may be needed to represent the
-different kinds of places source code is stored.  For example, the JDT defines source containers that represent source in a Java project,
-source on the classpath, and source in a package fragment.  The source containers used for a launch configuration may be stored by id in
-the launch configuration.  Since launch configurations can be persisted, there must be a way to associate the id of a source container
-with its implementation class.  This is done using the 
-<a href="../reference/extension-points/org_eclipse_debug_core_sourceContainerTypes.html"><b>org.eclipse.debug.core.sourceContainerTypes</b></a>
-extension point. The following example comes from the JDT:
-</p>
-<pre>
-&lt;extension point=&quot;org.eclipse.debug.core.sourceContainerTypes&quot;&gt;
-	&lt;sourceContainerType
-		id=&quot;org.eclipse.jdt.launching.sourceContainer.javaProject&quot;
-		name=&quot;%javaProjectSourceContainerType.name&quot;
-		description=&quot;%javaProjectSourceContainerType.description&quot;
-		class=&quot;org.eclipse.jdt.internal.launching.JavaProjectSourceContainerTypeDelegate&quot;&gt;
-	&lt;/sourceContainerType&gt; 
-	...
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm
deleted file mode 100644
index f766eae..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_status.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Handling errors from a launched program</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Handling errors from a launched program</h3>
-<p>If you have defined your own type of launch configuration, it's likely that
-you will want to handle errors or other status information that arises during the
-running of the program. For example, you may want to prompt or alert the
-user when certain types of errors occur during a launch, or provide information
-messages for certain status changes in the program. Since it's good
-practice to separate UI handling from core function, you do not want to have
-direct references from your launch delegate to status handling classes.</p>
-<p>This problem is addressed by the 
-<a href="../reference/extension-points/org_eclipse_debug_core_statusHandlers.html"><b>org.eclipse.debug.core.statusHandlers</b></a>
-extension point. It allows you to associate a status handler with a
-specific status code. Using this extension point, you can define all of
-the possible status and error codes in your launch delegate and core classes,
-while registering unique handlers for the different status codes from another
-plug-in.</p>
-<p>The extension point does not designate any association between a status
-handler and a launch configuration. It is up to the implementation of the
-launch delegate to detect errors, find the appropriate status handler, and
-invoke it. The extension merely provides a registry so that the status
-handlers can be found for particular status codes. 
-<a href="../reference/api/org/eclipse/debug/core/DebugPlugin.html"><b>DebugPlugin</b></a>
-provides a utility method for obtaining a specific status handler.</p>
-<pre>
-IStatusHandler handler = DebugPlugin.getDefault().getStatusHandler(status);</pre>
-<p>Status handlers should implement <a href="../reference/api/org/eclipse/debug/core/IStatusHandler.html"><b>IStatusHandler</b></a>.
-The status handling class is specified in the extension definition, along with
-its associated status code and the plug-in that is expected to generate the
-status codes.</p>
-<p>The following markup shows how the Java tools declare status handlers:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.core.statusHandlers&quot;&gt;
-	&lt;statusHandler
-		id=&quot;org.eclipse.jdt.debug.ui.statusHandler.vmConnectTimeout&quot;
-		class=&quot;org.eclipse.jdt.internal.debug.ui.launcher.VMConnectTimeoutStatusHandler&quot;
-		plugin =&quot;org.eclipse.jdt.launching&quot;
-		code=&quot;117&quot;&gt;
-	&lt;/statusHandler&gt;	
-	...
-&lt;/extension&gt;</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm
deleted file mode 100644
index d46ba27..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_ui.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launch configuration dialog</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Launch configuration dialog</h3>
-<p>Launch configurations can most easily be visualized by looking at their
-corresponding UI. Users interact with a launch configuration dialog to
-create instances of the different types of launch configurations that have been
-contributed by plug-ins. Each type of launch configuration defines a group
-of tabs that collect and display information about the configuration. The
-tab group for running a local Java application is shown below.</p>
-<p><img src="images/lcd.png" alt="Launch configuration dialog with contributed tab groups" border="0"></p>
-<p>The tabs are contributed using the <a href="../reference/extension-points/org_eclipse_debug_ui_launchConfigurationTabGroups.html"><b>org.eclipse.debug.ui.launchConfigurationTabGroups</b></a>
-extension point. In this extension, the id of a configuration type (defined using
-<a href="../reference/extension-points/org_eclipse_debug_core_launchConfigurationTypes.html"><b>org.eclipse.debug.core.launchConfigurationTypes</b></a>)
-is associated with the class that implements <a href="../reference/api/org/eclipse/debug/ui/ILaunchConfigurationTabGroup.html"><b>ILaunchConfigurationTabGroup</b></a>.</p>
-<p>It's possible that a some tab groups are only appropriate when launching the configuration in a particular mode.  If this is the case, then
-one or more <b>mode</b> elements can be specified along with the class.  For each mode, the tab group can be given a unique description. 
-If no mode is specified, then the tab group will be shown on all modes that
-do not have a mode-specific tab group contribution.  The Java application tab group is defined for run and debug modes:</p>
-<pre>
-   &lt;extension
-         point="org.eclipse.debug.ui.launchConfigurationTabGroups"&gt;
-      &lt;launchConfigurationTabGroup
-            type="org.eclipse.jdt.launching.localJavaApplication"
-            helpContextId="org.eclipse.jdt.debug.ui.launchConfigHelpContext.local_java_application"
-            class="org.eclipse.jdt.internal.debug.ui.launcher.LocalJavaApplicationTabGroup"
-            id="org.eclipse.jdt.debug.ui.launchConfigurationTabGroup.localJavaApplication"
-            bannerImage="icons/full/wizban/java_app_wiz.png"&gt;
-            &lt;launchMode 
-                  mode="debug"
-                  perspective="org.eclipse.debug.ui.DebugPerspective"
-                  description="%localJavaApplicationTabGroupDescription.debug"&gt;
-            &lt;/launchMode&gt;
-            &lt;launchMode
-                  mode="run"
-                  description="%localJavaApplicationTabGroupDescription.run"&gt;
-            &lt;/launchMode&gt;
-      &lt;/launchConfigurationTabGroup&gt;
-      ...
-</pre>
-<p>Note that a perspective may also be specified with a mode.  This will cause the platform to switch to the specified perspective when
-the program is launched in that mode.</p>
-<p>Your tab group class is responsible for creating the necessary tabs and
-displaying and saving the relevant data from the launch configuration
-attributes. A tab that is common to all configurations, <a href="../reference/api/org/eclipse/debug/ui/CommonTab.html"><b>CommonTab</b></a>,
-is already implemented and can be created by any configuration. This tab
-manages the saving of the launch configuration as well as collecting common
-preferences.</p>
-<p><img src="images/common_tab.png" alt="Launch configuration tabs" border="0"></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm
deleted file mode 100644
index 99c69d2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uiimages.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launch configuration type images</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Launch configuration type images</h3>
-<p>The image that is shown for a launch configuration type in the launch dialog
-is contributed using the <a href="../reference/extension-points/org_eclipse_debug_ui_launchConfigurationTypeImages.html"><b>org.eclipse.debug.ui.launchConfigurationTypeImages</b></a>
-extension point.&nbsp; This extension associates an image file with the id of a
-configuration type.</p>
-<p><img src="images/launchImage.png" alt="Launch configuration images" border="0"></p>
-<p>The markup for the Java application image is as follows:</p>
-<pre>
-&lt;extension
-	point="org.eclipse.debug.ui.launchConfigurationTypeImages"&gt;
- 		&lt;launchConfigurationTypeImage
-			icon="icons/full/etool16/java_app.png"
-			configTypeID="org.eclipse.jdt.launching.localJavaApplication"
-			id="org.eclipse.jdt.debug.ui.launchConfigurationTypeImage.localJavaApplication"&gt;
-		&lt;/launchConfigurationTypeImage&gt;
-		...
-</pre>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm
deleted file mode 100644
index c63b41f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_launch_uishortcuts.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Launch shortcuts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Launch shortcuts</h3>
-<p>Once a launch configuration has been defined using the dialog, it can be
-shown directly in the appropriate menu, rather than having to open the launch configuration
-dialog again.  When a launch configuration is shown directly in a menu, we refer to it as a
-<b>launch shortcut</b>.  The <a href="../reference/extension-points/org_eclipse_debug_ui_launchShortcuts.html"><b>org.eclipse.debug.ui.launchShortcuts</b></a>
-extension point is used to register these shortcuts.  In the extension
-definition, you can specify in which modes the shortcuts are shown. For each shortcut, you must specify
-an implementation of <a href="../reference/api/org/eclipse/debug/ui/ILaunchShortcut.html"><b>ILaunchShortcut</b></a>.
-This class is used to launch a program given a particular selection in a view or
-editor.</p>
-<p>
-You may also specify when the shortcut should be shown.  The <b>contexttualLaunch</b> element allows you to describe
-applicable modes and enabling conditions for the shortcut.  This is best demonstrated by example.  The following
-markup registers shortcuts for launching a Java application:</p>
-<pre>
-  &lt;extension
-         point="org.eclipse.debug.ui.launchShortcuts"&gt;
-      &lt;shortcut
-            label="%JavaApplicationShortcut.label"
-            icon="icons/full/etool16/java_app.png"
-            helpContextId="org.eclipse.jdt.debug.ui.shortcut_local_java_application"
-            modes="run, debug"
-            class="org.eclipse.jdt.internal.debug.ui.launcher.JavaApplicationLaunchShortcut"
-            id="org.eclipse.jdt.debug.ui.localJavaShortcut"&gt;
-         &lt;contextualLaunch&gt;
-           &lt;enablement&gt;
-             &lt;with variable="selection"&gt;
-               &lt;count value="1"/&gt;
-               &lt;iterate&gt;
-                 &lt;or&gt;
-                   &lt;test property="org.eclipse.debug.ui.matchesPattern" value="*.java"/&gt;
-                   &lt;test property="org.eclipse.debug.ui.matchesPattern" value="*.class"/&gt;
-                   &lt;instanceof value="org.eclipse.jdt.core.IJavaElement"/&gt;
-                 &lt;/or&gt;
-                 &lt;test property="org.eclipse.jdt.debug.ui.hasMainType"/&gt;
-               &lt;/iterate&gt;
-             &lt;/with&gt;
-           &lt;/enablement&gt;
-  		 &lt;/contextualLaunch&gt;
-         ...
-      &lt;/shortcut&gt;
-      ...
-</pre>
-<p>See <a href="workbench_actionfilters.htm">Boolean expressions and action filters</a> for an explanation of the XML syntax for 
-enabling conditions.  The complete syntax is described in the documentation for 
-<a href="../reference/extension-points/org_eclipse_debug_ui_launchShortcuts.html"><b>org.eclipse.debug.ui.launchShortcuts</b></a>.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm
deleted file mode 100644
index 1615eeb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_model.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Platform debug model</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Platform debug model</h3>
-<p>The platform debug model defines generic debug interfaces that are intended 
-  to be implemented and extended in concrete, language-specific implementations.</p>
-<h4>Artifacts</h4>
-<p>The model includes classes that represent different artifacts in a program
-under debug.&nbsp; All of the artifacts implement <a href="../reference/api/org/eclipse/debug/core/model/IDebugElement.html"><b>IDebugElement</b></a>
-in addition to their own interfaces.&nbsp; The model includes definitions for
-the following artifacts:</p>
-<ul>
-  <li>Debug targets (<a href="../reference/api/org/eclipse/debug/core/model/IDebugTarget.html"><b>IDebugTarget</b></a>)
-    - a debuggable execution context, such as a process or virtual machine</li>
-  <li>Expressions (<a href="../reference/api/org/eclipse/debug/core/model/IExpression.html"><b>IExpression</b></a>)
-    - a snippet of code that can be evaluated to produce a value</li>
-  <li>Memory blocks (<a href="../reference/api/org/eclipse/debug/core/model/IMemoryBlock.html"><b>IMemoryBlock</b></a>)
-    - a contiguous segment of memory in an execution context</li>
-  <li>Registers (<a href="../reference/api/org/eclipse/debug/core/model/IRegister.html"><b>IRegister</b></a>)
-    - a named variable in a register group</li>
-  <li>Register groups (<a href="../reference/api/org/eclipse/debug/core/model/IRegisterGroup.html"><b>IRegisterGroup</b></a>)
-    - a group of registers assigned to a stack frame</li>
-  <li>Stack frames (<a href="../reference/api/org/eclipse/debug/core/model/IStackFrame.html"><b>IStackFrame</b></a>)
-    - an execution context in a suspended thread containing local variables and
-    arguments</li>
-  <li>Threads (<a href="../reference/api/org/eclipse/debug/core/model/IThread.html"><b>IThread</b></a>)
-    - a sequential flow of execution in a debug target containing stack frames</li>
-  <li>Values (<a href="../reference/api/org/eclipse/debug/core/model/IValue.html"><b>IValue</b></a>)
-    - the value of a variable</li>
-  <li>Variables (<a href="../reference/api/org/eclipse/debug/core/model/IVariable.html"><b>IVariable</b></a>)
-    - a visible data structure in a stack frame or value</li>
-  <li>Watch expressions (<a href="../reference/api/org/eclipse/debug/core/model/IWatchExpression.html"><b>IWatchExpression</b></a>)
-    - an expression that updates its value when provided with a particular context</li>
-</ul>
-<p>Plug-ins that implement language-specific debuggers typically extend these
-interfaces to include language-specific behavior.&nbsp; All debug elements can
-return the id of the plug-in that originated them.&nbsp; This is important for
-registering other classes that are associated with a debug model, such as UI
-classes.</p>
-<h4>Actions</h4>
-<p>The model also includes interfaces that define a set of debug actions that
-are common behaviors among debug artifacts.&nbsp; These interfaces are
-implemented by debug elements where appropriate.&nbsp; They include the
-following actions:</p>
-<ul>
-  <li>Disconnect (<a href="../reference/api/org/eclipse/debug/core/model/IDisconnect.html"><b>IDisconnect</b></a>) 
-    - the ability to end a debug session with a target program and allow the target 
-    to continue running</li>
-  <li>Step (<a href="../reference/api/org/eclipse/debug/core/model/IStep.html"><b>IStep</b></a>) 
-    - the ability to step into, over, and return from the current execution point</li>
-  <li>Step filters (<a href="../reference/api/org/eclipse/debug/core/model/IStepFilters.html"><b>IStepFilters</b></a>) 
-    - the ability to enable or disable filtering of step operations so that a debug target can apply filters to
-    steps when appropriate</li>
-  <li>Suspend and resume (<a href="../reference/api/org/eclipse/debug/core/model/ISuspendResume.html"><b>ISuspendResume</b></a>) 
-    - the ability to suspend and resume execution</li>
-  <li>Terminate (<a href="../reference/api/org/eclipse/debug/core/model/ITerminate.html"><b>ITerminate</b></a>) 
-    - the ability to terminate an execution context</li>
-  <li>Modify a value (<a href="../reference/api/org/eclipse/debug/core/model/IValueModification.html"><b>IValueModification</b></a>) 
-    - the ability to modify the value of a variable</li>
-</ul>
-<p>If you look at the definitions for the platform debug elements, you will see
-that different elements implement different debug actions.&nbsp; Standard
-interfaces for the elements and their behaviors allow the platform to provide
-abstract implementations of utility classes and UI support that can be extended
-for concrete implementations of debuggers.</p>
-<h4>Events</h4>
-<p>Debug events (<a href="../reference/api/org/eclipse/debug/core/DebugEvent.html"><b>DebugEvent</b></a>)
-are used to describe events that occur as a program is being debugged.&nbsp;
-Debug events include the debug element that is associated with the event.&nbsp;
-Each kind of debug element has a specific set of events that it supports as
-documented in <a href="../reference/api/org/eclipse/debug/core/DebugEvent.html"><b>DebugEvent</b></a>.
-Debugger implementations can add application specific debug events using a designation of
-<b>DebugEvent.MODEL_SPECIFIC</b> as the kind of event.  A client data field can be used in this case
-to add model-specific information about the event.</p>
-<p>Debugger UI classes typically listen to specific events for elements in order
-display information about changes that occur in the elements.&nbsp; Debug events
-arrive in groups called <b>debug event sets</b>.&nbsp; Events that occur at the
-same point of execution in a program arrive in the same set.&nbsp; Clients
-should implement an <a href="../reference/api/org/eclipse/debug/core/IDebugEventSetListener.html"><b>IDebugEventSetListener</b></a>
-and register the listener with the <a href="../reference/api/org/eclipse/debug/core/package-summary.html"><b>org.eclipse.debug.core</b></a>
-plug-in in order to receive debug events.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm
deleted file mode 100644
index c13a49f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_presentation.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Debug model presentation</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Debug model presentation</h3>
-<p>Since there is a generic, uniform model for debug elements in the platform,
-it's possible to provide a starting point for implementing a debugger UI.
-The heart of the debugger UI support is the <b>debug model
-presentation</b> (<a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a>).
-The debug model presentation is responsible for providing labels, images, and
-editors associated with specific debug elements.</p>
-<p>Plug-ins that define their own debug model typically provide a debug model
-presentation for displaying debug elements in the model. This is
-accomplished using the 
-<a href="../reference/extension-points/org_eclipse_debug_ui_debugModelPresentations.html"><b>org.eclipse.debug.ui.debugModelPresentations</b></a>
-extension point. This extension point allows an implementation of <a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a>
-to be associated with the identifier of a particular debug model.</p>
-<p>Recall that <a href="debug_model.htm">debug model elements</a> know the id of
-their originating debug model. This means that given any debug element,
-the debug platform can obtain the id of the debug model and then query the
-extension registry for any corresponding debug model presentations.</p>
-<p>The markup for adding a debug model presentation looks like this:</p>
-<pre>&lt;extension point = &quot;org.eclipse.debug.ui.debugModelPresentations&quot;&gt; 
-         &lt;debugModelPresentation
-             class = &quot;org.eclipse.jdt.internal.debug.ui.JDIModelPresentation&quot;
-             id = &quot;org.eclipse.jdt.debug&quot;
-             detailsViewerConfiguration = &quot;org.eclipse.jdt.internal.debug.ui.display.DetailsViewerConfiguration&quot;&gt;
-          &lt;/debugModelPresentation&gt; 
-&lt;/extension&gt;</pre>
-<p>An optional <b>detailsViewerConfiguration</b> can be specified in addition to
-the debug model presentation. The details viewer must extend the JFace 
-<a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html"><b>SourceViewerConfiguration</b></a>
-class. The meaning of &quot;details&quot; is interpreted by the debug
-model. The details are computed by the debug model presentation and passed
-to the details viewer. For example, the Java debugger uses the details
-viewer to show code assist in the variables view when expressions are evaluated.</p>
-<p>Implementors of <a href="../reference/api/org/eclipse/debug/ui/IDebugModelPresentation.html"><b>IDebugModelPresentation</b></a> may
-also implement <a href="../reference/api/org/eclipse/debug/ui/IDebugEditorPresentation.html"><b>IDebugEditorPresentation</b></a> when
-more control is needed over the editor that is displaying source code for a stack frame.  Implementors may control the
-editor's position or the annotations in the source.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm b/bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm
deleted file mode 100644
index b452c98..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/debug_ui.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Debug UI utility classes</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Debug UI utility classes</h3>
-<p>In addition to defining a general framework for showing a debug UI, the debug UI plug-in 
-includes classes that implement useful utility methods for implementing a debugger UI.</p>
-<p><a href="../reference/api/org/eclipse/debug/ui/DebugUITools.html"><b>DebugUITools</b></a>
-groups many of these utilities and includes methods for the following:</p>
-<ul>
-  <li>Saving and/or building the workspace before launching a particular launch configuration</li>
-  <li>Storage and retrieval of images on behalf of debug UI clients</li>
-  <li>Lookup of the debug model presentation associated with a given debug model</li>
-  <li>Retrieval of the debug plug-in preference store</li>
-  <li>Information about the current program under debug, such as the current context, process, or console</li>
-  <li>Opening the launch configuration dialog with various defaults</li>
-  <li>Enabling or disabling the use of step filters</li>
-</ul>
-<p><a href="../reference/api/org/eclipse/debug/ui/IDebugView.html"><b>IDebugView</b></a>
-provides common function for debug views. It provides access to an
-underlying viewer and its debug model presentation. Typically, clients
-should extend <a href="../reference/api/org/eclipse/debug/ui/AbstractDebugView.html"><b>AbstractDebugView</b></a>
-rather than implement the interface from scratch. <a href="../reference/api/org/eclipse/debug/ui/AbstractDebugView.html"><b>AbstractDebugView</b></a>
-provides many useful functions:</p>
-<ul>
-  <li>Storage of actions in an action registry</li>
-  <li>Generic handling of the underlying viewer's context menu</li>
-  <li>General implementations of delete key and double click function </li>
-  <li>Mechanism for displaying an error message in the view</li>
-</ul>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm
deleted file mode 100644
index 6f0e7fc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Dialogs and wizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Dialogs and wizards</h1>
-<p>
-We've seen how to extend the workbench UI by adding views, editors, and 
-actions to the workbench.  We've contributed a preference page for controlling
-the behavior of our plug-in.  Now we can tie it all together by launching our 
-own dialogs in response to these actions.</p>
-<p>
-The JFace UI framework provides several standard dialogs and a framework for
-building your own dialogs and wizards.  We'll look at the different kinds of dialogs and wizards and how to build
-them.</p>
-<p>
-We'll also cover some simple workbench extensions for contributing wizards.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog.htm
deleted file mode 100644
index 86c14d7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<TITLE>Filtered item selection dialog</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Filtered item selection dialog</h2>
-<p><a
-	href="../reference/api/org/eclipse/ui/dialogs/FilteredItemsSelectionDialog.html">
-<b>FilteredItemsSelectionDialog</b></a> is a powerful dialog for displaying a set
-of items to be selected by the user.  This dialog is used as the basis of the "Open Resource"
-and "Open Type" dialogs in the Eclipse SDK. You can create your own subclass of this
-dialog to quickly implement a similar dialog for your domain objects. Some of the
-dialog's key features include:
-</p>
-<ul>
-	<li>Support for multiple selections</li>
-	<li>Details field that shows information about the selected element</li>
-	<li>Uses JFace viewers, content and label providers</li>
-	<li>Background population, filtering, sorting, and refreshing of the item list</li>
-	<li>History of previously selected elements persisted across invocations</li>
-	<li>Supports for regular expression pattern matching and camel-case matching.
-	Filtering is implemented using <a
-		href="../reference/api/org/eclipse/ui/dialogs/SearchPattern.html"><b>SearchPattern</b></a></li>
-</ul>
-
-For examples illustrating how to create you own custom implementations of this dialog,
-see the following:
-<ul>
-<li><a href="dialogs_FilteredItemsSelectionDialog_example.htm"> <b>Creating a custom filtered item selection dialog</b></a></li>
-<li><a href="dialogs_FilteredItemsSelectionDialog_example_advanced.htm"><b>Advanced use of the filtered item selection dialog</b></a></li>
-</ul>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example.htm
deleted file mode 100644
index 52d6d0b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example.htm
+++ /dev/null

@@ -1,172 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
-	type="text/css">
-<script language="JavaScript"
-	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Creating a custom filtered item selection dialog</title>
-</head>
-<body>
-
-<h2>Creating a custom filtered items selection dialog</h2>
-<p>In this example, we will contribute a basic search dialog to illustrate the steps 
-needed to create a custom subclass of  <a href="../reference/api/org/eclipse/ui/dialogs/FilteredItemsSelectionDialog.html">
-<b> FilteredItemsSelectionDialog</b></a>.</p>
-
-<ol>
-	<li>
-	Create a new Plug-in Project using Hello, world template. 
-	</li>
-	<li>
-	Create a class extending <em>org.eclipse.ui.dialogs.FilteredItemsSelectionDialog</em>.
-	Let's name it <em>FilteredResourcesSelectionDialogExample</em>.
-	</li>
-	<li>
-	Choose a source of  the resources that will be used during filtering. In our 
-	example we will generate our own set of random strings as follows:
-	<pre>
-   private static ArrayList resources = new ArrayList();
-   
-   static {
-      generateRescourcesTestCases('A', 'C', 8, ""); //$NON-NLS-1$
-      generateRescourcesTestCases('a', 'c', 4, ""); //$NON-NLS-1$
-   }
-
-   private static void generateRescourcesTestCases(char startChar, char endChar, int length, String resource){
-      for (char ch = startChar; ch &lt;= endChar; ch++) {
-         String res = resource + String.valueOf(ch);
-         if (length == res.length()) 
-            resources.add(res);
-         else if ((res.trim().length() % 2) == 0)
-            generateRescourcesTestCases(Character.toUpperCase((char)(startChar + 1)), Character.toUpperCase((char)(endChar + 1)), length, res);
-         else 
-            generateRescourcesTestCases(Character.toLowerCase((char)(startChar + 1)), Character.toLowerCase((char)(endChar + 1)), length, res);
-      }
-   }
-</pre></li>
-	<li>
-	Now, let's implement abstract methods from the <em>FilteredItemsSelectionDialog</em>
-	class.
-	<ul>
-		<li><em>createExtendedContentArea(Composite)</em>: This method
-		creates an extra content area located above the details. For now,
-		we will just return null because we don't need any extra fields for this simple
-		example: 
-		<pre>
-   protected Control createExtendedContentArea(Composite parent) {
-      return null;
-   }</pre></li>
-		<li><em>createFilter()</em>: Creates a new instance of a filter.
-		In the simplest implementation you should also extend <em>
-		FilteredItemsSelectionDialog.ItemsFilter </em> and implement the abstract
-		methods. Eg.: <pre>
-   protected ItemsFilter createFilter() {
-      return new ItemsFilter() {
-         public boolean matchItem(Object item) {
-            return matches(item.toString());
-         }
-         public boolean isConsistentItem(Object item) {
-            return true;
-         }
-      };
-   }</pre></li>
-		<li><em>
-		fillContentProvider(FilteredItemsSelectionDialog.AbstractContentProvider,
-		FilteredItemsSelectionDialog.ItemsFilter,
-		org.eclipse.core.runtime.IProgressMonitor)</em>: Fills the content provider
-		with matching items. Eg.: <pre>
-   protected void fillContentProvider(AbstractContentProvider contentProvider,
-      ItemsFilter itemsFilter, IProgressMonitor progressMonitor)
-         throws CoreException {
-      progressMonitor.beginTask("Searching", resources.size()); //$NON-NLS-1$
-      for (Iterator iter = resources.iterator(); iter.hasNext();) {
-         contentProvider.add(iter.next(), itemsFilter);
-         progressMonitor.worked(1);
-      }
-      progressMonitor.done();
-   }</pre></li>
-
-		<li><em>getDialogSettings()</em>: Returns the settings object that stores
-		information about how the dialog information is persisted. This method can't
-		return null, so we'll just return a simple settings object: 
-		<pre>
-   private static final String DIALOG_SETTINGS = "FilteredResourcesSelectionDialogExampleSettings";	
-		
-   protected IDialogSettings getDialogSettings() {
-      	IDialogSettings settings = Activator.getDefault().getDialogSettings()
-				.getSection(DIALOG_SETTINGS);
-		if (settings == null) {
-			settings = Activator.getDefault().getDialogSettings()
-					.addNewSection(DIALOG_SETTINGS);
-		}
-		return settings;
-   }</pre></li>
-
-		<li><em>getElementName(Object)</em>: Returns a name for the given
-		object. This is used to check duplicates. <pre>
-   public String getElementName(Object item) {
-      return item.toString();
-   }</pre></li>
-		
-		<li><em>getItemsComparator()</em>: Returns a comparator used to
-		sort items. In our example we will just use standard string comparison:<pre>
-   protected Comparator getItemsComparator() {
-      return new Comparator() {
-         public int compare(Object arg0, Object arg1) {
-            return arg0.toString().compareTo(arg1.toString());
-         }
-      };
-   }</pre></li>
-
-		<li><em>validateItem(Object)</em>: Validates that the item is a valid
-		selection.  In our example we just return an OK status, because all items
-		are valid:<pre>
-   protected IStatus validateItem(Object item) {
-      return Status.OK_STATUS;
-   }</pre></li>
-
-	</ul>
-	</li>
-	<li>
-	Add title of dialog and set simple implementation of <em>SelectionHistory</em> on dialog:<pre>
-	public FilteredResourcesSelectionDialogExample(Shell shell, boolean multi) {
-	   super(shell, multi);
-	   setTitle("Filtered Resources Selection Dialog Example");
-	   setSelectionHistory(new ResourceSelectionHistory());
-	}
-	
-	private class ResourceSelectionHistory extends SelectionHistory {
-	   protected Object restoreItemFromMemento(IMemento element) {
-		  return null; 
-	   }
-	   protected void storeItemToMemento(Object item, IMemento element) {
-	   }
-	}</pre></li>
-	<li>
-	Change <em>run(IAction)</em> method from <em>SimpleAction</em> to:<pre>
-	public void run(IAction action) {
-	   Shell shell = new Shell();
-	   FilteredItemsSelectionDialog dialog = new FilteredResourcesSelectionDialogExample(shell, true);
-	   dialog.setInitialPattern("a");
-	   dialog.open();
-	}</pre></li>	
-	<li>
-	Change tooltip of SimpleAction from <em>"Hello, Eclipse world"</em> to <em>"Filtered Items Selection Dialog Example"</em>.
-	</li>
-	<li>
-	Run Eclipse with created plug-in.
-	</li>
-	<li>
-	The resulting dialog looks as follows:
-	<p><img
-		src="images/filteredResourcesSelectionDialogExample.png" border="0"
-		alt="Screen shot of a simple search dialog"></p>
-	</li>
-</ol>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example_advanced.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example_advanced.htm
deleted file mode 100644
index 54e1d69..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_FilteredItemsSelectionDialog_example_advanced.htm
+++ /dev/null

@@ -1,207 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
-	type="text/css">
-<script language="JavaScript"
-	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Advanced use of the filtered item selection dialog</title>
-</head>
-<body>
-
-<h2>Advanced use of the filtered items selection dialog</h2>
-
-In the <a href="dialogs_FilteredItemsSelectionDialog_example.htm">previous example</a>, 
-we saw how to create a simple subclass of FilteredItemsSelectionDialog. Now let's 
-explore some of the advanced capabilities provided by this dialog:
-<ul>
-<li><a href="#history">Adding selected items history</a></li>
-<li><a href="#filter">Adding custom filters</a></li>
-<li><a href="#checkbox">Adding an extra check-box to the dialog</a></li>
-</ul>
-
-<h3><a name="history">Adding selected items</a> history</h3>
-The dialog can be configured to save and restore the history of items that have
-been selected.
-<ol>
-	<li>In the <a href="dialogs_FilteredItemsSelectionDialog_example.htm">previous part</a> we created a subclass of <em>FilteredItemsSelectionDialog.SelectionHistory</em> but it do nothing.
-	Now, we should fill out methods responsible for saving and loading objects:
-	<pre>
-   private class ResourceSelectionHistory extends SelectionHistory {
-      /*
-       * @see org.eclipse.ui.dialogs.FilteredItemsSelectionDialog.SelectionHistory#restoreItemFromMemento(org.eclipse.ui.IMemento)
-       */
-      protected Object restoreItemFromMemento(IMemento element) {
-         return element.getString("resource"); //$NON-NLS-1$
-      }
-      /*
-       * @see org.eclipse.ui.dialogs.FilteredItemsSelectionDialog.SelectionHistory#storeItemToMemento(java.lang.Object,
-       *      org.eclipse.ui.IMemento)
-       */
-      protected void storeItemToMemento(Object item, IMemento element) {
-         element.putString("resource", item.toString()); //$NON-NLS-1$
-      }
-   }</pre>
-	</li>
-
-    <li>Open the dialog.
-    </li>
-    <li>Select listed elements and click OK:
-    	<ul>
-    		<li>
-    			<em>AbCdEfGh</em>
-    		</li>
-    		<li>
-    			<em>AbCdEfGi</em>
-    		</li>
-    		<li>
-    			<em>AbCdEfGj</em>
-    		</li>
-    		<li>
-    			<em>AbCdEfHh</em>
-    		</li>
-    		<li>
-    			<em>AbCdEfHi</em>
-    		</li>
-    		<li>
-    			<em>AbCdEfHj</em>
-    		</li>
-    		<li>
-    			<em>abCd</em>
-    		</li>
-    		<li>
-    			<em>abCe</em>
-    		</li>
-    		<li>
-    			<em>abCf</em>
-    		</li>
-    		<li>
-    			<em>abDd</em>
-    		</li>
-    		<li>
-    			<em>abDe</em>
-    		</li>
-    	</ul>
-    </li>
-	<li>Our example dialog now looks like this:
-	<p><img
-		src="images/filteredResourcesSelectionDialogExampleAdvance1.png"
-		border="0" alt="Image of a simple search dialog"></p>
-	</li>
-</ol>
-
-<h3><a name="filter">Adding custom filters</a></h3>
-Next we will expand the filter to hide all strings that start with a lower case character.
-<ol>
-	<li>Create a subclass of <em>FilteredItemsSelectionDialog.ItemsFilter</em>, 
-	implement the necessary abstract methods and override <em>equalsFilter(ItemsFilter)</em>
-	and <em>isSubFilter(ItemsFilter)</em>. These two methods are used to optimize
-	filtering of the view.  If a new filter is added that is equal to the existing filter,
-	no further filtering is required.  If the new filter is a sub-filter of the existing filter, then
-	filtering is only done on the items that matched the existing filter.
-   <pre>
-   private boolean onlyLowerCase = true;
-  	
-   private class ResourceFilter extends ItemsFilter {
-   public final boolean onlyLowerCase = FilteredResourcesSelectionDialogExample.this.onlyLowerCase;
-
-      public boolean matchItem(Object item) {
-         String resource = item.toString();
-         if (onlyLowerCase &amp;&amp; Character.isUpperCase(resource.charAt(0)))
-            return false;
-         return matches(resource);
-      }
-      public boolean equalsFilter(ItemsFilter filter) {
-         ResourceFilter resourceFilter = (ResourceFilter) filter;
-         if (onlyLowerCase != resourceFilter.onlyLowerCase)
-            return false;
-         return super.equalsFilter(filter);
-      }
-      public boolean isSubFilter(ItemsFilter filter) {
-         ResourceFilter resourceFilter = (ResourceFilter) filter;
-         if (onlyLowerCase != resourceFilter.onlyLowerCase)
-            return false;
-         return super.isSubFilter(filter);
-      }
-      public boolean isConsistentItem(Object item) {
-         return true;
-      }
-   }</pre></li>
-	<li>On your subclass of FilteredItemsSelectionDialog, override the <i>createFilter()</i> method: 
-	<pre>
-   protected ItemsFilter createFilter() {
-      return new ResourceFilter();
-   }</pre></li>
-	<li>Now the dialog will only display strings that start with a lower case letter. 
-	<p><img src="images/filteredResourcesSelectionDialogExampleAdvance2.png"
-		border="0" alt="Image of a simple search dialog"></p>
-	</li>
-</ol>
-
-<h3><a name="checkbox">Adding an extra check-box to the dialog</a></h3>
-<p>We will use a check-box and a menu action to indicate whether
-to filter strings that start with a lower case character.</p>
-<ol>
-	<li>Extend the dialog's content area by implementing <em>createExtendedContentArea(Composite)</em>
-	method: <pre>
-   private Button checkButton;
-  	
-   protected Control createExtendedContentArea(Composite parent) {
-      checkButton = new Button(parent, SWT.CHECK);
-      checkButton.setText("Only Lower Case Strings"); //$NON-NLS-1$
-      checkButton.addSelectionListener(new SelectionListener() {
-         public void widgetDefaultSelected(SelectionEvent e) {
-         }
-         public void widgetSelected(SelectionEvent e) {
-            if (onlyLowerCase != ((Button) e.widget).getSelection()) {
-               onlyLowerCase = ((Button) e.widget).getSelection();
-               applyFilter();
-            }
-         }
-      });
-      return checkButton;
-   }</pre></li>
-	<li>Next, create a new action and add it to the menu by overriding <em>fillViewMenu(IMenuManager)</em>.
-	Eg.: <pre>
-   private Action showOnlyLowerCaseStringsAction = new ShowOnlyLowerCaseStringsAction();
-   
-   private class ShowOnlyLowerCaseStringsAction extends Action {
-      /**
-       * Creates a new instance of the action.
-       */
-      public ShowOnlyLowerCaseStringsAction() {
-         super("Only Lower Case String", //$NON-NLS-1$
-            IAction.AS_CHECK_BOX);
-      }
-      public void run() {
-         if (onlyLowerCase != isChecked()) {
-            onlyLowerCase = isChecked();
-            applyFilter();
-         }
-      }
-   }
-   
-   protected void fillViewMenu(IMenuManager menuManager) {
-      super.fillViewMenu(menuManager);
-      menuManager.add(showOnlyLowerCaseStringsAction);
-   }
-  </pre></li>
-  <li>At the end override <em>applyFilter()</em> as follows:<pre>
-   protected void applyFilter() {
-      super.applyFilter();
-      checkButton.setSelection(onlyLowerCase);
-      showOnlyLowerCaseStringsAction.setChecked(onlyLowerCase);
-   }</pre>
-  </li>
-
-	<li>Now open the dialog: 
-	<p><img src="images/filteredResourcesSelectionDialogExampleAdvance3.png"
-		border="0" alt="Image of a simple search dialog"></p>
-	</li>
-</ol>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm
deleted file mode 100644
index 153fd03..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_applications.htm
+++ /dev/null

@@ -1,137 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<TITLE>
-Application dialogs
-</TITLE>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Application dialogs</h2>
-<P >
-When a standard dialog is too simple for your plug-in, you can build your own dialog using the
-<a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b> Dialog</b></a> class. Earlier, we saw how the readme tool contributed an &quot;Open Readme Browser&quot;
-action in an action set.&nbsp; This action set is shown in the workbench tool bar
-and <b>Window-&gt;Readme File Editor</b> menu.&nbsp;&nbsp;</P>
-
-<P >
-Now we are ready to look at the implementation of this action in the readme
-tool's <b>WindowActionDelegate</b>.</P>
-
-<pre>
-   public void run(IAction action) {
-      SectionsDialog dialog = new SectionsDialog(window.getShell(),
-         ReadmeModelFactory.getInstance().getSections(selection));
-      dialog.open();
-   }
-</pre>
-
-<P >
-The window action delegate for the action set uses the current selection in the resource navigator view (the
-<b> .readme</b> file) to get a list of sections in the readme file. This list and the
-workbench window's shell are passed to the
-<b>SectionsDialog</b>.&nbsp;</P>
-
-<P >
-When the user selects the action, the <b>SectionsDialog</b>
-is opened.</P>
-
-<img src="images/readmedialog.png" alt="" border="0" >
-
-
-<P >
- The <b> SectionsDialog</b> is implemented in the readme tool plug-in by subclassing the
-<b><a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"> Dialog</a>
-</b> class in the <b><a href="../reference/api/org/eclipse/jface/dialogs/package-summary.html"> org.eclipse.jface.dialogs</a>
-package.</b></P>
-<P >
-The <a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b> Dialog</b></a> class provides basic support for building a dialog shell window, creating the common dialog buttons, and launching the dialog. The subclasses are responsible for handling the content of the dialog itself:</P>
-<ul>
-  <li><b>createDialogArea</b> creates the SWT controls that represent the dialog contents. This is similar to creating the controls for a view or
-    editor.
-<P>
-The <b> SectionsDialog</b> creates an SWT list to display the list of sections. It uses a JFace viewer to populate the list. (We'll look at JFace viewers in
-<a HREF="jface_viewers.htm" CLASS="XRef"> Viewers</a>.) Note that our dialog does not have to create any of the buttons for the dialog since this is done by our
-superclass.</P>
-<pre>
-   protected Control createDialogArea(Composite parent) {
-      Composite composite = (Composite)super.createDialogArea(parent);
-      List list = new List(composite, SWT.BORDER);
-      ...
-      ListViewer viewer = new ListViewer(list);
-      ...
-      return composite;
-   }
-</pre>
-<br>
-  </li>
-  <li><b>configureShell</b> is overridden to set an appropriate title for the shell window.
-<pre>
-   protected void configureShell(Shell newShell) {
-      super.configureShell(newShell);
-      newShell.setText(MessageUtil.getString(&quot;Readme Sections&quot;));
-      ...
-   }
-</pre>
-<br>
-  </li>
-  <li>
-<b>
-okButtonPressed</b> is overridden to perform whatever action is necessary when the user presses the OK button. (You can also override
-<b> cancelButtonPressed</b> or <b> buttonPressed(int)</b> depending on the design of your dialog.)&nbsp;&nbsp;
-  </li>
-</ul>
-<b>SectionsDialog</b> does not implement an <b> okButtonPressed</b> method. It inherits the &quot;do-nothing&quot; implementation from
-<a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b>Dialog</b></a>. This is not typical. Your dialog usually performs some processing in response to one of the dialog buttons being pressed.
-<P >
-Dialogs can be as simple or as complicated as necessary. When you implement a dialog, most of your dialog code is concerned with creating the SWT controls that represent its content area and handling any events necessary while the dialog is up. Once a button is pressed by the user, the dialog can query the state of the various controls (or viewers) that make up the dialog to determine what to do.</P>
-
-<h3> Popup dialogs</h3>
-<p>
-In some cases, you might want to show information about something in a dialog, but in a way that is more &quot;lightweight&quot; than
-launching a regular dialog.  For example, a dialog may be intended to provide transient information that can be easily dismissed, without taking the
-focus away from the user's work.  If this is the case, you can use the
-<a href="../reference/api/org/eclipse/jface/dialogs/PopupDialog.html"><b>PopupDialog</b></a> class to implement the dialog.  The look and feel of
-a <a href="../reference/api/org/eclipse/jface/dialogs/PopupDialog.html"><b>PopupDialog</b></a> is different than a regular 
-<a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b>Dialog</b></a> in several ways.  It does not have any buttons across the bottom,
-it does not have the standard window title bar, and its borders, spacing, and fonts are smaller and more compact.  
-</p>
-<p>
-Although a <a href="../reference/api/org/eclipse/jface/dialogs/PopupDialog.html"><b>PopupDialog</b></a> looks very different than
-a regular dialog, the code in your plug-in's subclass that defines the dialog content is almost the same.  You still implement the <b>createDialogArea</b> method
-to create the SWT controls for the dialog.  The main difference in the application code is that the constructor that creates the dialog has many
-more parameters than the regular <a href="../reference/api/org/eclipse/jface/dialogs/Dialog.html"><b>Dialog</b></a> class.  For example, the <b>SectionsDialog</b>
-could be turned into a <a href="../reference/api/org/eclipse/jface/dialogs/PopupDialog.html"><b>PopupDialog</b></a> by simply changing the superclass
-of the dialog and configuring the dialog in the constructor:
-</p>
-<pre>
-   public class SectionsDialog extends <b>PopupDialog</b> {
-      protected IAdaptable input;
-
-      /**
-      * Creates a new SectionsDialog.
-      */
-      public SectionsDialog(Shell parentShell, IAdaptable input) {
-        <b>super(parentShell, SWT.DEFAULT, false, // do not take focus when opened
-        	false, // do not persist the bounds
-        	false, // do not show a resize menu
-        	false, // do not show a menu item for persisting bounds
-        	null, //  no title
-        	null); // no info text</b>
-        this.input = input;
-      }
-      ...
-</pre>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm
deleted file mode 100644
index 154fc21..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_settings.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<TITLE>Dialog settings</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<h2>
-Dialog settings</h2>
-<p>
-The <a href="../reference/api/org/eclipse/jface/dialogs/package-summary.html"> <b> org.eclipse.jface.dialogs</b></a> 
-package provides a utility class,
-<a href="../reference/api/org/eclipse/jface/dialogs/DialogSettings.html"><b>DialogSettings</b></a>, 
-for storing and retrieving keyed values. You can use this class to save and retrieve primitive data types 
-and string values that you associate with key names. The settings are loaded and saved using an XML file.</p>
-<p><a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a> provides support for plug-in wide dialog settings stored in an XML file in your plug-in's directory. If a dialog settings file is not found in your plug-in directory, an empty
-<a href="../reference/api/org/eclipse/jface/dialogs/DialogSettings.html"> <b> DialogSettings</b></a> will be created for you. When the plug-in is shut down, any settings that were added to it will be saved in an XML file and retrieved the next time the plug-in is started up.</p>
-<p>
-You can access your dialog settings anywhere in your plug-in code. The following snippet shows how you could obtain the dialog settings for the readme tool.</p>
-<pre>
-   IDialogSettings settings = ReadmePlugin.getDefault().getDialogSettings();
-</pre>
-<p>
-Values are stored and retrieved using get and put methods. The get methods are named after the type of primitive that is being accessed. You can store and retrieve
-boolean, long, double, float, int, array, and string values. The following snippet shows how we could use dialog settings to initialize control values in a dialog.</p>
-<pre>
-   protected Control createDialogArea(Composite parent) {
-      IDialogSettings settings = ReadmePlugin.getDefault().getDialogSettings();
-      checkbox = new Button(parent,SWT.CHECK);
-      checkbox.setText(&quot;Generate sample section titles&quot;);
-      // initialize the checkbox according to the dialog settings
-<b>      checkbox.setSelection(settings.getBoolean(&quot;GenSections&quot;));
-</b>   }
-</pre>
-<p>
-The value of the setting can be stored later when the ok button is pressed.</p>
-<pre>
-   protected void okPressed() {
-      IDialogSettings settings = ReadmePlugin.getDefault().getDialogSettings();
-      // store the value of the generate sections checkbox
-<b>      settings.put(&quot;GenSections&quot;, checkbox.getSelection());
-</b>      super.okPressed();
-   }
-</pre>
-<h3>Dialog bounds settings</h3>
-<p>
-In general, the definition and interpretation of dialog settings are the responsibility of your plug-in.  However, there are some specific dialog
-settings keys defined inside the JFace dialog framework that are used to remember the last size and position of a dialog, so that the dialog
-can be opened to that size and position on its next invocation.  The framework will do the work to query and store the dialog's size
-and position, but you must implement a method that supplies the 
-<a href="../reference/api/org/eclipse/jface/dialogs/IDialogSettings.html"> <b>IDialogSettings</b></a> instance that should be used
-to store the dialog bounds information.  The following snippet shows how the <b>SectionsDialog</b>
-could take advantage of this feature.
-</p>
-<pre>
-   protected IDialogSettings getDialogBoundsSettings() {
-	   return ReadmePlugin.getDefault().getDialogSettings();
-   }
-</pre>
-<p>
-By implementing this method, the size and position of the <b>SectionsDialog</b> will be stored in predefined keys within the
-plug-in's dialog settings, causing the dialog to open at its previous location.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm
deleted file mode 100644
index c8bb816..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_standard.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<TITLE>
-Standard dialogs
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Standard dialogs</h2>
-<P >
-The package <a href="../reference/api/org/eclipse/jface/dialogs/package-summary.html"> <b> org.eclipse.jface.dialogs</b></a> defines the basic support for dialogs. This package provides standard dialogs for displaying user messages and obtaining simple input from the user.</P>
-<ul>
-  <li>
-<a href="../reference/api/org/eclipse/jface/dialogs/MessageDialog.html">
-<b>
-MessageDialog</b></a> displays a message to the user. You can set the dialog title, image, button text, and message in the constructor for this dialog.</li>
-  <li><a href="../reference/api/org/eclipse/jface/dialogs/ErrorDialog.html"><b>ErrorDialog</b></a> displays information about an error. You can set the dialog title and message for the dialog. You can also supply an IStatus object which the dialog will use to obtain an error message.</li>
-  <li>
-<a href="../reference/api/org/eclipse/jface/dialogs/InputDialog.html"><b>
-InputDialog</b></a> allows the user to enter text. You can set the dialog title, default text value, and supply an object that will validate the text input.</li>
-  <li>
-<a href="../reference/api/org/eclipse/jface/dialogs/ProgressMonitorDialog.html"><b>
-ProgressMonitorDialog</b></a> shows progress to the user during the running of
-a long operation.</li>
-</ul>
-<P >
-The standard dialogs are designed so that you can completely specify the dialog in its constructor. We saw a
-<b><a href="../reference/api/org/eclipse/jface/dialogs/MessageDialog.html"> MessageDialog</a>
-</b> in action in the readme tool's view action:</P>
-<pre>
-   MessageDialog.openInformation(
-      view.getSite().getShell(),&quot;Readme Editor&quot;,&quot;View Action executed&quot;);</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm
deleted file mode 100644
index de642ec..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Wizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Wizards</H2>
-<P >
-Wizards are used to guide the user through a sequenced set of tasks. Your plug-in can contribute wizards at predefined extension points in the workbench. It can also create and launch its own wizards.</P>
-<P >
-When you contribute to a workbench wizard extension point, the actions that launch the wizard are already set up by the workbench. You need only supply the wizard that will be used.&nbsp;</P>
-
-<P >
-If you need to launch other wizards that are not already defined in workbench
-wizard extension points, you must launch them yourself.&nbsp; You can launch your own wizards by adding an action to a view, editor, popup,
-or an action set.&nbsp;</P>
-
-<P >
-A wizard is composed of several different underlying parts.&nbsp;</P>
-
-<img alt="" border="0" src="images/wiz_arch.jpg" >
-
-
-<p>
-&nbsp;</p>
-
-
-<h3>
-Wizard dialog</h3>
-<P >
-The wizard dialog (<b><a href="../reference/api/org/eclipse/jface/wizard/WizardDialog.html">WizardDialog</a></b>)
-is the top level dialog in a wizard. It defines the standard wizard buttons and manages a set of pages that are provided to it.</P>
-<P >
-When you contribute to a workbench wizard extension, you do not have to create a wizard dialog. One is created on your behalf by the workbench, and your wizard is set into it.</P>
-
-
-<P >
-The wizard dialog performs the enabling and disabling of the <b>Next</b>, <b>Back</b>, and <b> Finish</b> 
-buttons based on information it obtains from the wizard and the current wizard
-page.</P>
-
-
-<h3>
-Wizard</h3>
-<P >
-The wizard (<a href="../reference/api/org/eclipse/jface/wizard/IWizard.html"><b>IWizard</b></a>)
-controls the overall appearance and behavior of the wizard, such as title bar text, image, and the availability of a help button.
-Wizards often use a corresponding <a href="../reference/api/org/eclipse/jface/dialogs/DialogSettings.html"><b>DialogSettings</b></a>
-to obtain (and store) the default values for the settings of controls on the wizard pages.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> Wizard</a></b> class
-implements many of the details for standard wizard behavior.&nbsp; You typically
-extend this class to implement behavior specific to your wizard. The primary responsibilities of your wizard
-will include:</P>
-<ul>
-  <li>
-    
-Creating and adding your pages to your wizard</li>
-  <li>
-    
-Implementing the behavior that should occur when the user presses the <b> Finish</b> button.
-  </li>
-</ul>
-
-
-<h3>
-Wizard page</h3>
-<P >
-The wizard page (<a href="../reference/api/org/eclipse/jface/wizard/IWizardPage.html"><b>IWizardPage</b></a>) defines the controls that are used to show the content of the wizard page. It responds to events in its content areas and determines when the page is completed.</P>
-<P >
-Your wizard page typically extends the <a href="../reference/api/org/eclipse/jface/wizard/WizardPage.html"><b> WizardPage</b></a> class.&nbsp;
-The primary responsibilities of your wizard page will include:</P>
-<ul>
-  <li>
-    
-creating the SWT controls that represent the page</li>
-  <li>
-    
-determing when the user has supplied enough information to complete the page (that is, when the user can move to the next page.)
-  </li>
-</ul>
-
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm
deleted file mode 100644
index 6b90def..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_exportWizards.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-org.eclipse.ui.exportWizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<H3>
-org.eclipse.ui.exportWizards</H3>
-<P >
-You can add a wizard to the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>File &gt; Export</b></a>
-  
-menu option in the workbench using the
-<a href="../reference/extension-points/org_eclipse_ui_exportWizards.html"><b> org.eclipse.ui.exportWizards</b></a> extension point. The process for defining the extension and implementing the wizard is similar to&nbsp;
-<b><a href="../reference/extension-points/org_eclipse_ui_newWizards.html">org.eclipse.ui.newWizards</a></b>.&nbsp;
-The primary difference in the markup is that export wizards do not define or
-assign categories for the wizards themselves.&nbsp; The wizards appear
-uncategorized in a wizard dialog. </P>
-<P >
-<img src="images/exportwizard.png" alt="" border="0"> </P>
-<P >
-The wizard supplied in the class parameter of the markup must implement <a href="../reference/api/org/eclipse/ui/IExportWizard.html"><b>IExportWizard</b></a>.
-Its pages are typically extended from
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardExportPage.html"><b> WizardExportPage</b></a>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm
deleted file mode 100644
index 0259712..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_extensions.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Workbench wizard extension points</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<h2>
-Workbench wizard extension points</h2>
-<P >
-The workbench defines extension points for wizards that create new resources, import resources, or export resources.&nbsp;</P>
-<P >
- When you make selections in the new, import, or export menu, the workbench uses
-various wizard
-selection dialogs to display all the wizards that have been contributed for that particular extension point.&nbsp;
-The
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>import wizard</b></a>
-
-dialog is shown below.</P>
-<P >
-<img src="images/importwizard.png" alt="Import wizard dialog with selection list" border="0"></P>
-<P >
-Your wizard takes control once it is selected in the list and the <b> Next</b> button is pressed. This is when your first page becomes visible.&nbsp;</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm
deleted file mode 100644
index 20af9cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_importWizards.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>org.eclipse.ui.importWizards</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H3>
-org.eclipse.ui.importWizards</H3>
-<P >
-You can add a wizard to the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>File &gt; Import</b></a>
-
-menu option in the workbench using the
-<a href="../reference/extension-points/org_eclipse_ui_importWizards.html"> <b> org.eclipse.ui.importWizards</b></a> extension point. The process for defining the extension and implementing the wizard is similar to
-<b><a href="../reference/extension-points/org_eclipse_ui_newWizards.html">org.eclipse.ui.newWizards</a></b>.&nbsp;
-The primary difference in the markup is that import wizards do not define or
-assign categories for the wizards themselves.&nbsp; The wizards appear
-uncategorized in a wizard dialog. </P>
-<P >
-<img src="images/importwizard.png" alt="" border="0"> </P>
-<P >
-The wizard supplied in the class parameter of the markup must implement <a href="../reference/api/org/eclipse/ui/IImportWizard.html"><b>IImportWizard</b></a>.
-Its pages are typically extended from
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardImportPage.html"> <b> WizardImportPage</b></a>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm
deleted file mode 100644
index 29d0a531..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_multipage.htm
+++ /dev/null

@@ -1,111 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Multi-page wizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Multi-page wizards</h2>
-<P >
-If your wizard implements a complex task, you may want to use more than one page to obtain information from the user.</P>
-<P >
-In general, the implementation pattern is the same as for a single page wizard.</P>
-<ul>
-  <li>
-    
-Create a <a href="../reference/api/org/eclipse/jface/wizard/WizardPage.html"> <b> WizardPage</b></a> subclass for each page in your wizard. Each wizard page should use
-<b>setPageComplete(true)</b> when it has enough information.</li>
-  <li>
-    
-Create a <a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> <b> Wizard</b></a> subclass which adds each page to the wizard.</li>
-  <li>
-    
-Implement a <b> performFinish</b> method to perform the finish logic.</li>
-</ul>
-<P >
-When you design a wizard, it's good practice to put all the required information on the first page if possible. This way, the user does not have to traverse the entire set of pages in order to finish the task.&nbsp;
-Optional information can go on subsequent pages. </P>
-<P >
-When a page requires input from the user before it can be considered complete, use
-<b>setPageComplete(false)</b> to signify that it is not complete. As the page receives events from its controls, it rechecks to see if the page is complete. Once the required input is provided,
-<b>setPageComplete(true)</b> signals completion.</P>
-<P >
-The <a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> <b> Wizard</b></a> class handles the
-logic required to enable and disable the <b> Finish</b>  button according to the
-completion state of the pages.&nbsp; The
-<b> Finish</b> button is only enabled for a wizard when each of its pages have set its completion state to true.</P>
-
-<h3>
-Validation and page control</h3>
-<P >
-The classes <a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html"> <b> WizardNewFileCreationPage</b></a> and
-<b> CreateReadme1</b> show a common pattern for implementing page validation.</P>
-<P >
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html">
-<b>
-WizardNewFileCreationPage</b></a> defines a common event handler for all SWT events which validates the page. This means the page will be validated whenever an event is received from a widget to which the page added a listener.</P>
-<pre>
-   public void handleEvent(Event event) {
-      setPageComplete(validatePage());
-   }
-</pre>
-<P >
-Once the <b>ReadmeCreationPage</b> creates its controls, it sets the state of the page using
-<b>validatePage</b>.</P>
-<pre>
-   public void createControl(Composite parent) {
-      super.createControl(parent);
-      // create controls, add listeners, and layout the page
-      ...
-      // sample section generation checkboxes
-      sectionCheckbox = new Button(group,SWT.CHECK);
-      sectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_section_titles&quot;));
-      sectionCheckbox.setSelection(true);
-      sectionCheckbox.<b>addListener</b>(SWT.Selection,this);
-
-      subsectionCheckbox = new Button(group,SWT.CHECK);
-      subsectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_subsection_titles&quot;));
-      subsectionCheckbox.setSelection(true);
-      subsectionCheckbox.<b>addListener</b>(SWT.Selection,this);
-      ...
-      <b>setPageComplete(validatePage());</b>
-   }
-</pre>
-<P >
-Using this pattern, a wizard page can put all of its page validation code in one method,
-<b>validatePage()</b>. This method determines the initial state of the page and recalculates the state any time it receives an event from a widget on its page.</P>
-<P >
-Since we added a listener to the section checkbox, we will recompute the valid state of the page whenever that checkbox receives a selection event.
-Note that the page's
-<b> handleEvent</b> method must call super to ensure that the
-inherited page validation behavior occurs in addition to any specific event handling for this
-page.</P>
-<pre>
-   public void handleEvent(Event e) {
-      Widget source = e.widget;
-      if (source == sectionCheckbox) {
-         if (!sectionCheckbox.getSelection())
-            subsectionCheckbox.setSelection(false);
-         subsectionCheckbox.setEnabled(sectionCheckbox.getSelection());
-      }
-      super.handleEvent(e);
-   }
-</pre>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm
deleted file mode 100644
index 4469d3e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_newWizards.htm
+++ /dev/null

@@ -1,210 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-org.eclipse.ui.newWizards
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<H3>
-org.eclipse.ui.newWizards</H3>
-<P >
-You can add a wizard to the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>File &gt; New</b></a>
-
-menu options in the workbench using the
-<a href="../reference/extension-points/org_eclipse_ui_newWizards.html"><b> org.eclipse.ui.newWizards</b></a> extension point. The readme
-tool example uses this extension point definition to add the Readme File wizard:</P>
-<pre>
-&lt;extension
-      point = &quot;org.eclipse.ui.newWizards&quot;&gt;
-	&lt;category
-	   id = &quot;org.eclipse.ui.examples.readmetool.new&quot;
-	   parentCategory=&quot;org.eclipse.ui.Examples&quot;
-	   name=&quot;%NewWizard.category&quot;&gt;
-	&lt;/category&gt;
- 	&lt;wizard
-	   id = &quot;org.eclipse.ui.examples.readmetool.wizards.new.file&quot;
-      	   name = &quot;%NewWizard.name&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeCreationWizard&quot;
-	   category=&quot;org.eclipse.ui.Examples/org.eclipse.ui.examples.readmetool.new&quot;
-	   icon=&quot;icons/obj16/newreadme_wiz.png&quot;&gt;
-    	   &lt;description&gt;%NewWizard.desc&lt;/description&gt;
-	   &lt;selection class=&quot;org.eclipse.core.resources.IResource&quot;/&gt;
-	&lt;/wizard&gt;
-&lt;/extension&gt;
-</pre>
-<P >The <b>category</b> describes the grouping for the wizard.&nbsp; An optional
-<b>parentCategory</b>  establishes the new category as a child of an existing
-category.</p>
-<P > Top level categories will appear in the <b> File &gt; New </b>menu.&nbsp;
-In this example, the <b>parentCategory</b> is set to an &quot;Examples&quot;
-category.&nbsp; Where did the parent category come from?&nbsp; The <b>org.eclipse.ui</b>
-plug-in defines a standard examples category in its markup:</p>
-<pre>&lt;extension
-        point=&quot;org.eclipse.ui.newWizards&quot;&gt;
-    &lt;category
-          name=&quot;%NewWizards.Category.Examples&quot;
-          id=&quot;org.eclipse.ui.Examples&quot;&gt;
-    &lt;/category&gt;
-    ...</pre>
-<P >This category appears in the <b> File &gt; New </b> menu.</P>
-<P >
-<img src="images/newwizardmenu.png" alt="New menu with Examples category" border="0"></P>
-<P >
-&nbsp;</P>
-<P >
-The readme tool's category <b>name</b> 
- defines the label that is used for the next layer of grouping underneath the
-parent category.&nbsp; These categories are shown as the second level in the tree
-shown in the <b>New Example</b> wizard.&nbsp; The wizard's <b>name</b> and <b>icon</b> are shown
-underneath when you expand the category.&nbsp; The <b>description</b> 
-of the selected wizard is shown at the top of the wizard when you select it.</P>
-<P >
-<img src="images/newwizardlist.png" alt="New example wizard with readme entries" border="0"></P>
-<P >
-This information about the wizard appears solely because of the markup in the <b>plugin.xml
-</b>file.&nbsp; None of the plug-in code runs
-until the user chooses the <b>Next</b> button.&nbsp; Once this happens, the
-workbench will instantiate the wizard <b>class</b>
-specified in the markup and pass it an expected selection <b>class</b>.</P>
-<P >
-The class identified in this extension (<b>ReadmeCreationWizard</b>) must
-implement the
-<a href="../reference/api/org/eclipse/ui/INewWizard.html"> <b> INewWizard</b></a> interface.&nbsp;
-Most wizards do so by extending the platform
-<a href="../reference/api/org/eclipse/jface/wizard/Wizard.html"> <b> Wizard</b></a> class
-although this is an implementation mechanism and not required by the extension
-point.</P>
-<P >
-The wizard itself does little but create the pages inside of it. Let's look at the implementation of the page first, and then come back to the wizard.</P>
-
-<H4>
-Pages</H4>
-<P >
-The workbench provides base wizard page classes that support the type of processing performed for each wizard extension point. You can use these pages, or extend them to add additional processing.</P>
-<P >
-The goal of the <b> ReadmeCreationWizard</b> is to create a new file, add the required content to the file, and as an option, open an editor on the file. Our page needs to define the controls that let the user specify what content goes in the file and whether an editor should be launched.</P>
-<P >
-We create the wizard page, <b>ReadmeCreationPage</b>, by extending
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html"><b>WizardNewFileCreationPage</b></a>. The controls for a wizard page are defined in a fashion
-similar to the definition of the controls for a view or an editor. The page implements a
-<b> createControl</b> method, creating the necessary SWT widgets as children of the supplied
-<a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><b>Composite</b></a>. Since the superclass already adds widgets that support new file processing, we need only extend the
-<b> createControl</b> method in our wizard page to add the additional checkboxes that control generation of sections and opening of the editor.</P>
-<pre>
-   public void createControl(Composite parent) {
-      // inherit default container and name specification widgets
-      super.createControl(parent);
-      Composite composite = (Composite)getControl();
-      ...
-      // sample section generation group
-      Group group = new Group(composite,SWT.NONE);
-      group.setLayout(new GridLayout());
-      group.setText(MessageUtil.getString(&quot;Automatic_sample_section_generation&quot;));
-      group.setLayoutData(new GridData(GridData.GRAB_HORIZONTAL |
-         GridData.HORIZONTAL_ALIGN_FILL));
-      ...
-      // sample section generation checkboxes
-      sectionCheckbox = new Button(group,SWT.CHECK);
-      sectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_section_titles&quot;));
-      sectionCheckbox.setSelection(true);
-      sectionCheckbox.addListener(SWT.Selection,this);
-
-      subsectionCheckbox = new Button(group,SWT.CHECK);
-      subsectionCheckbox.setText(MessageUtil.getString(&quot;Generate_sample_subsection_titles&quot;));
-      subsectionCheckbox.setSelection(true);
-      subsectionCheckbox.addListener(SWT.Selection,this);
-      ...
-      // open file for editing checkbox
-      openFileCheckbox = new Button(composite,SWT.CHECK);
-      openFileCheckbox.setText(MessageUtil.getString(&quot;Open_file_for_editing_when_done&quot;));
-      openFileCheckbox.setSelection(true);
-      ...
-   }
-</pre>
-<P >
-You should be able to follow this code if you understand the concepts in
-<a HREF="swt.htm" CLASS="XRef">Standard Widget Toolkit</a>.</P>
-<P >
-The basic patterns for implementing a page include:</P>
-<ul>
-  <li>
-    
-Add listeners to any controls that affect dynamic behavior of the page. For example, if selecting an item in a list or checking a box affects the state of other controls of the page, add a listener so you can change the state of the page.</li>
-  <li>
-    
-Populate the controls with data based on the current selection when the wizard was launched. Some of the data may depend on the values in other controls. Some of the controls may use dialog settings to initialize their
-values.&nbsp;&nbsp;</li>
-  <li>
-    
-Use <b>setPageComplete(true)</b> when enough information is provided by the user to exit the page (and move to the next page or finish the wizard.)</li>
-</ul>
-<P >
-The <b>ReadmeCreationPage</b> class inherits a lot of this behavior from the
-<a href="../reference/api/org/eclipse/ui/dialogs/WizardNewFileCreationPage.html"><b>WizardNewFileCreationPage</b></a>.&nbsp;
-Browse the implementation of these classes for further information.</P>
-<P >
-Now that we understand what a page does, let's look again at the wizard.</P>
-
-
-<H4>
-Wizard</H4>
-<P >
-The wizard is responsible for creating the pages and providing the &quot;finish&quot; logic.</P>
-<P >
-The basic patterns for implementing a wizard include:</P>
-<ul>
-  <li>
-Implement the <b>init</b> method to set up local variables for context information such as the workbench and the current selection.<br>
-<pre>
-   public void init(IWorkbench workbench,IStructuredSelection selection) {
-      this.workbench = workbench;
-      this.selection = selection;
-      setWindowTitle(MessageUtil.getString(&quot;New_Readme_File&quot;));
-      setDefaultPageImageDescriptor(ReadmeImages.README_WIZARD_BANNER);
-   }
-</pre></li>
-
-  <li>
-Implement <b> addPages</b> by creating instances of the pages.<br>
-<pre>
-   public void addPages() {
-      mainPage = new ReadmeCreationPage(workbench, selection);
-      addPage(mainPage);
-   }
-</pre></li>
-
-  <li>
-Implement <b> performFinish</b> to finish the task.<br>
-
-  Multi-page wizards typically handle the finish logic in the wizard itself, since each page will contribute information that determines how the task is implemented. Single page wizards can implement the logic in the wizard or ask the page to finish the job.
-The approach you take largely depends on where your important state is kept.&nbsp;
-In the case of the readme wizard, we are going to ask our page to handle the finish processing.&nbsp;
-<pre>
-   public boolean performFinish() {
-      return mainPage.finish();
-   }
-</pre></li>
-</ul>
-<P >
-The completed wizard looks like this:</P>
-<P >
-<img src="images/readmewizard.png" alt="Readme file creation wizard page" border="0"></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm b/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm
deleted file mode 100644
index 8b277fa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/dialogs_wizards_wizarddialogs.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Wizard dialogs
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Wizard dialogs</h2>
-<P >
-The previous example supplied a wizard for a specified extension point. Another, perhaps more common,
-case is that you want to launch your own plug-in's wizard from some action that you have defined. (In
-<a HREF="workbench_menus.htm" CLASS="XRef"> Workbench menu contributions</a>, we discuss the ways you can contribute actions to the workbench.) </P>
-<P >Wizards are displayed in the UI by placing them in a containing
-dialog.&nbsp; This detail is handled for you when you contribute to a wizard
-extension.&nbsp; When you are launching your own wizard, you must display it
-yourself by wrapping it in a <a href="../reference/api/org/eclipse/jface/wizard/WizardDialog.html"><b>WizardDialog</b></a>.</P>
-<P >
-For example, the <b> ReadmeCreationWizard</b> could be launched independently by creating a wizard dialog and associating it with the
-<b>ReadmeCreationWizard</b>. The following code snippet shows how this could be done from some action delegate. (The method assumes that we know the workbench and the selection.)</P>
-<pre>
-   public void run(IAction action) {
-      // Create the wizard
-      ReadmeCreationWizard wizard = new ReadmeCreationWizard();
-      wizard.init(getWorkbench(), selection);
-
-      // Create the wizard dialog
-      WizardDialog dialog = new WizardDialog
-         (getWorkbench().getActiveWorkbenchWindow().getShell(),wizard);
-      // Open the wizard dialog
-      dialog.open();
-   }</pre>
-   <p>If you need to embed a wizard anywhere else in your plug-in's user
-   interface, the interface <a href="../reference/api/org/eclipse/jface/wizard/IWizardContainer.html"><b>IWizardContainer</b></a>
-   defines the necessary protocol for hosting a wizard.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors.htm
deleted file mode 100644
index bd970b1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Editors
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Editors</h1>
-<P >
-We have seen how plug-ins can contribute an editor to the workbench, but we
-haven't yet looked at the implementation of an editor.</P>
-<P >There is no &quot;typical&quot; implementation pattern for an editor, because editors usually provide application-specific semantics.&nbsp;
-A tool that edits and manages a particular content type will
-provide customized behavior for manipulating the data represented by the resource.</P>
-<P >Editors can come in all shapes and sizes.&nbsp; If a plug-in's editor is text-based, then the editor can either use the existing default text editor, or create a customized text editor
-by using the facilities provided in the platform.&nbsp; The latter approach is used by the
-Java example editor.</P>
-    <p >
-<img src="images/javaeditor.png" alt="Java text editor" border="0" > </p>
-    <p >
-If a plug-in's editor is not text based, then a custom editor must be implemented by the plug-in. There are several approaches for building
-custom editors, all of which depend on the look and behavior of the editor.</p>
-<ul>
-  <li>
-    
-Form-based editors can layout controls in a fashion similar to a dialog or wizard.&nbsp;
-    The Plug-in Development Environment (PDE) uses this approach in building its
-    manifest editors.&nbsp;&nbsp;</li>
-  <li>
-    
-Graphics intensive editors can be written using SWT level code.&nbsp; For
-example, an editor could create its own SWT window for displaying the
-information, or it could use a custom SWT control that is optimized for the
-application.</li>
-  <li>
-    
-List-oriented editors can use JFace list, tree, and table viewers to manipulate
-their data.</li>
-</ul>
-<P >
-Once the implementation model for the editor has been determined, implementing the editor is much like programming a stand-alone JFace or SWT application.&nbsp;
-Platform extensions are used to add actions, preferences, and wizards needed to
-support the editor.&nbsp; But the internals of the editor are largely dependent
-on your application design principles and internal model.
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm
deleted file mode 100644
index 4825ae5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_actions.htm
+++ /dev/null

@@ -1,163 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Registering editor actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Registering editor actions</H2>
-<p>The text editor framework provides many utility classes that aid in presenting
-and updating text and source code.&nbsp; Now we will turn our attention to the workbench in
-which the editor is but one part.&nbsp; How does the editor interact with other
-workbench features such as context menus, menu bars, and tool bars?</p>
-
-<h3>Editor menu bar actions</h3>
-
-<p>To understand how editors register themselves with the workbench and provide
-actions for the workbench menu bar, see the section discussing <a href="workbench_basicext_editors.htm">org.eclipse.ui.editors</a>.&nbsp;
-We won't rehash that information here.&nbsp;&nbsp;We'll just take a quick look
-at the markup where the Java example editor registers its editor.</p>
-
-<pre>&lt;extension
-      point=&quot;org.eclipse.ui.editors&quot;&gt;
-   &lt;editor
-         name=&quot;%javaEditorName&quot;
-         icon=&quot;icons/obj16/java.png&quot;
-         extensions=&quot;jav&quot;
-         <b>contributorClass=&quot;org.eclipse.ui.examples.javaeditor.JavaActionContributor&quot;</b>
-         class=&quot;org.eclipse.ui.examples.javaeditor.JavaEditor&quot;
-         id=&quot;org.eclipse.ui.JavaEditor&quot;&gt;
-   &lt;/editor&gt;
-&lt;/extension&gt;</pre>
-
-<p>Workbench menu bar actions are contributed by the <b>JavaActionContributor</b>.&nbsp; 
-  It implements actions that are placed in the workbench <b>Edit</b> menu and 
-  the workbench tool bar.</p>
-
-<pre>public JavaActionContributor() {
-	super();
-	fContentAssistProposal= <b>new RetargetTextEditorAction</b>(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistProposal.&quot;); //$NON-NLS-1$
-	...
-	fContentAssistTip= new RetargetTextEditorAction(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistTip.&quot;); //$NON-NLS-1$
-	...
-	fTogglePresentation= new PresentationAction();
-}</pre>
-<p>The first two actions are defined as retargetable text editor actions. The 
-  principle is similar to the <a href="wrkAdv_retarget.htm">retargetable actions</a> 
-  provided by the workbench. Retargetable text editor actions represent menu entries 
-  which the action contributor dynamically binds to corresponding actions provided 
-  by the active editor. When the active editor changes, the action to which a 
-  retargetable text editor action is bound changes as well. The following snippet 
-  shows that the editor action contributor finds the corresponding action by asking 
-  the editor for an action of a given id:</p>
-<pre>protected final IAction getAction(ITextEditor editor, String actionId) {<br>	return (editor == null ? null : editor.getAction(actionId));<br>}
-
-public void setActiveEditor(IEditorPart part) {<br>	super.setActiveEditor(part);<br>	ITextEditor editor= null;<br>	if (part instanceof ITextEditor)<br>		editor= (ITextEditor) part;<br>	fContentAssistProposal.setAction(getAction(editor, &quot;ContentAssistProposal&quot;));<br>	fContentAssistTip.setAction(getAction(editor, &quot;ContentAssistTip&quot;));<br>	fTogglePresentation.setEditor(editor);<br>	fTogglePresentation.update();<br>}</pre>
-<p>The id must be the same under which the action is registered with the editor 
-  as given here for the <b>JavaTextEditor</b>. (See also next section.):<br>
-</p>
-<pre>protected void createActions() {
-	super.createActions();
-		
-	IAction a= new TextOperationAction(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistProposal.&quot;, this, ISourceViewer.CONTENTASSIST_PROPOSALS); //$NON-NLS-1$
-	<b>a.setActionDefinitionId(ITextEditorActionDefinitionIds.CONTENT_ASSIST_PROPOSALS);</b>
-	setAction(&quot;ContentAssistProposal&quot;, a); 
-		
-	a= new TextOperationAction(JavaEditorMessages.getResourceBundle(), &quot;ContentAssistTip.&quot;, this, ISourceViewer.CONTENTASSIST_CONTEXT_INFORMATION);  //$NON-NLS-1$
-	a.setActionDefinitionId(ITextEditorActionDefinitionIds.CONTENT_ASSIST_CONTEXT_INFORMATION);
-	setAction(&quot;ContentAssistTip&quot;, a); 
-}</pre>
-
-<p>The third action in the contributor is a concrete action added to the workbench 
-  tool bar.&nbsp; It toggles the state of the editor between showing the highlighted 
-  range (as dictated by the Java example's content outliner) and showing the entire 
-  file.&nbsp; This action only appears in the tool bar.</p>
-
-<h3>Editor context menus</h3>
-
-The editor context menus are created and managed in the <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
- and <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a><b>
- </b>framework.
-<p>The method <b>createActions</b> is used to register actions with the editor.&nbsp; 
-  This includes actions appropriate for the editor context menus or any actions 
-  contributed in extension definitions.&nbsp; In the Java example editor, only 
-  the actions that get bound to the retargetable actions are created.&nbsp; However, 
-  the Java example editor also inherits the actions created by <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a> 
-  and its superclasses.&nbsp; These actions can be used in the editor context 
-  menus.</p>
-<p>The <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-method <b>editorContextMenuAboutToShow</b> is used in the framework to allow
-editors to add actions to the context menu for the editing area.&nbsp; You can
-use a menu path to decide exactly where your action should appear.&nbsp; Valid
-menu paths inside the editor context menu are defined in the implementation of
-this method in <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.</p>
-<p>There are several ways to add an action to this menu.&nbsp; The first way is 
-  by adding an action using only the id under which it is registered with the 
-  editor.&nbsp; For example, the <b>JavaTextEditor</b> adds its actions for content 
-  assistance to the menu when this method is called.&nbsp; Actions will not appear 
-  in the menu when no action is registered under the used id.</p>
-<pre>public void editorContextMenuAboutToShow(MenuManager menu) {
-	super.editorContextMenuAboutToShow(menu);
-	addAction(menu, &quot;ContentAssistProposal&quot;); 
-	addAction(menu, &quot;ContentAssistTip&quot;); 
-}</pre>
-<p>The superclass <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a> 
-  adds actions a second way - by specifying a menu group in the context menu 
-  for placing the action.&nbsp; In this case the actions (<b>Shift Left</b>, <b>Shift 
-  Right</b>) do appear in the context menu in the group defined by <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.</p>
-<pre>protected void editorContextMenuAboutToShow(IMenuManager menu) {
-	super.editorContextMenuAboutToShow(menu);
-	addAction(menu, ITextEditorActionConstants.GROUP_EDIT, ITextEditorActionConstants.SHIFT_RIGHT);
-	addAction(menu, ITextEditorActionConstants.GROUP_EDIT, ITextEditorActionConstants.SHIFT_LEFT);
-}</pre>
-<p><img src="images/javaeditorcontextmenu.png" alt="Editor context menu" border="0"> </p>
-<p>The method <b>rulerContextMenuAboutToShow</b>  is used in the same way before
-the ruler's context menu is shown.&nbsp; The implementation of this method in <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
-defines the groups in which items can be added to the menu. </p>
-<h3>Menu ids </h3>
-<p>The editor context and ruler context menus can be assigned ids so that other
-plug-ins can contribute to these menus in their extensions.&nbsp; The scheme for
-establishing menu ids is more flexible since the original version of the
-platform.&nbsp; However, the framework can run in a compatibility mode in order
-to remain compatible with plug-ins developed for the original version.&nbsp; You
-can use <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html#setCompatibilityMode()"><b>AbstractTextEditor.setCompatibilityMode()</b></a>
-to control this behavior.&nbsp; The default setting is true. </p>
-
-<h4>1.0 compatible menu ids </h4>
-<p>When the compatibility mode is true, the ids of the editor and ruler context 
-  menus can be set using <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a> 
-  protocol.&nbsp; The methods <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html#setEditorContextMenuId(java.lang.String)"><b>setEditorContextMenuId</b></a> 
-  and <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html#setRulerContextMenuId(java.lang.String)"><b>setRulerContextMenuId</b></a> 
-  can be used for this purpose.&nbsp; Resetting the ids can be useful if you want 
-  to prevent inheriting menus that were contributed to superclass menus.&nbsp; 
-  For example, the <b>JavaTextEditor</b> in the example resets its context menu 
-  ids to be Java specific in order to prevent inheriting any generic text contributions 
-  from other plug-ins. </p>
-<pre>protected void initializeEditor() {
-	super.initializeEditor();
-	JavaEditorEnvironment.connect(this);
-	setSourceViewerConfiguration(new JavaSourceViewerConfiguration());
-	<b>setEditorContextMenuId(&quot;#JavaEditorContext&quot;); 
-	setRulerContextMenuId(&quot;#JavaRulerContext&quot;); </b>
-}</pre>
-<p>If no id is set anywhere in the 
-  concrete hierarchy, the default ids defined by <b><a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html">AbstractTextEditor</a></b> 
-  will be used. </p>
-<h4>1.0 non-compatible menu ids </h4>
-<p>The editor context menu id is always <code>&lt;editor id&gt;.EditorContext</code>, 
-  where <code>&lt;editor id&gt;</code> is the id of the editor . The id of an 
-  editor is defined in the xml declaration of the editor. The ruler context menu 
-  id is always <code>&lt;editor id&gt;.RulerContext</code>.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm
deleted file mode 100644
index 991c307..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_annotations.htm
+++ /dev/null

@@ -1,218 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Source viewers and annotations
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Source viewers and annotations</H2>
-<p>The editor and its corresponding text viewer are largely responsible for the
-implementation of the document's presentation and the configuration of any needed
-helper classes.&nbsp; (See <a href="jface_viewers.htm">Viewers</a> if you are not familiar with the
-concept of a viewer.)&nbsp;&nbsp;</p>
-<p>A <b><a href="../reference/api/org/eclipse/jface/text/TextViewer.html">TextViewer</a></b>
-handles all of the low level details of mapping the document model and its
-partitions into the colored and formatted text that a user sees.&nbsp; For source code style editors, a <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-is provided.&nbsp; A source viewer introduces the notion of source code
-annotations.&nbsp; These annotations can be shown in a vertical ruler on the left side of
-the text, an overview ruler on the right side of the text,&nbsp;or as colored
-squigglies underneath text.</p>
-<p><b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-and its helper classes are used
-throughout the <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
-hierarchy.&nbsp; The package <b><a href="../reference/api/org/eclipse/jface/text/source/package-summary.html">org.eclipse.jface.text.source</a></b>
-defines this viewer and the other classes supporting annotation presentation.</p>
-<h3>Annotations and rulers</h3>
-<p>Annotations, like partitions, are largely dependent on the kind of document being edited.
-The <a href="../reference/api/org/eclipse/jface/text/source/IAnnotationModel.html"><b>IAnnotationModel</b></a>
-for a document is what holds the annotations, enumerates them on request, and listens for text
-changes in order to keep the annotations up to date with the text.  Annotation models are registered
-in the <b><a href="../reference/extension-points/org_eclipse_core_filebuffers_annotationModelCreation.html">org.eclipse.core.filebuffers.annotationModelCreation</a></b> 
-extension.  This extension point allows plug-ins to register a class that will create an annotation model
-appropriate for a given file extension.  The Java Editor example does not use this extension point, so it
-inherits the annotation model defined by the platform.</p>
-<pre>&lt;extension
-	point="org.eclipse.core.filebuffers.annotationModelCreation"&gt;
-	&lt;factory
-		extensions="*"
-		<b>class="org.eclipse.ui.texteditor.ResourceMarkerAnnotationModelFactory"</b>&gt;
-	&lt;/factory&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-The supplied factory class will create a
-<b><a href="../reference/api/org/eclipse/ui/texteditor/ResourceMarkerAnnotationModel.html">ResourceMarkerAnnotationModel</a></b>
-for files with any extension.  This class displays annotations that represent a marker on a resource in the
-workspace.&nbsp; (See <a href="resAdv_markers.htm">Resource markers</a> for more
-information on markers.)&nbsp; It assigns an image and description to each marker and monitors its resource for changes in the markers.</p>
-<p>To see how an annotation model is displayed in a text editor, we'll examine
-the platform text editor and its use of rulers and annotations.&nbsp; The
-specifics of how different annotations are shown in the rulers and text can be
-controlled by the user in the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Annotations)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Editors &gt; Text Editors &gt; Annotations</b></a>
-
-preferences.</p>
-<h4>Vertical ruler</h4>
-<p>A vertical ruler to the left of the editing area is used by platform text
-editors to show text ranges and line-based annotations adjacent to their text line.</p>
-
-<p><img src="images/javaeditorverticalruler.png" alt="Vertical ruler" border="0"></p>
-
-<p>These annotations are described in the supplied <b><a href="../reference/api/org/eclipse/ui/texteditor/ResourceMarkerAnnotationModel.html">ResourceMarkerAnnotationModel</a></b>.&nbsp; 
-  This model is set into the <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b> 
-  when the source viewer is initialized by the editor.&nbsp; The following snippet 
-  from <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a> 
-  <b> </b>shows how the document and the annotation model are associated with 
-  the viewer.</p>
-
-<pre>private void initializeSourceViewer(IEditorInput input) {
-		
-	IAnnotationModel model= getDocumentProvider().getAnnotationModel(input);
-	IDocument document= getDocumentProvider().getDocument(input);
-		
-	if (document != null) {
-		<b>fSourceViewer.setDocument(document, model)</b>;
-		...</pre>
-<p>Once the source viewer is configured with the proper document and annotation
-model, it has enough information to present the document and ensure the correct
-annotations are shown in the vertical ruler to the left.&nbsp; The model is
-associated with the ruler when the document is set.&nbsp; The following snippet
-shows what happens when a document is set into the source viewer.&nbsp; It has
-been simplified from the actual code in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-for clarity:</p>
-
-<pre>public void setDocument(IDocument document, IAnnotationModel annotationModel) {
-	...
-	// create visual annotation model from the supplied model and store 
-	// in fVisualAnnotationModel
-	...
-	if (fVerticalRuler != null)
-		<b>fVerticalRuler.setModel(fVisualAnnotationModel)</b>;
-</pre>
-
-<p>In this way, the ruler is associated with the appropriate annotation
-model.&nbsp;&nbsp;</p>
-
-<p>Let's look at the ruler itself.&nbsp; It is created by the text editor and 
-  then connected with the editor's viewer.&nbsp; Since the Java editor example 
-  does not define any special behavior for rulers, it inherits the ruler as defined 
-  in <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.</p>
-
-<pre>protected IVerticalRuler createVerticalRuler() {
-	CompositeRuler ruler= new CompositeRuler();
-	ruler.addDecorator(0, new AnnotationRulerColumn(VERTICAL_RULER_WIDTH));
-	if (isLineNumberRulerVisible())
-		ruler.addDecorator(1, createLineNumberRulerColumn());
-	return ruler;
-}</pre>
-<p>The text editor uses a CompositeRuler. This ruler does not have a visual presentation 
-  of its own.&nbsp; The presentation is provided by a list of decorators that 
-  show columns (<b><a href="../reference/api/org/eclipse/jface/text/source/IVerticalRulerColumn.html">IVerticalRulerColumn</a></b>) 
-  in the ruler.&nbsp; In this example, a ruler column that shows annotations (<b><a href="../reference/api/org/eclipse/jface/text/source/AnnotationRulerColumn.html">AnnotationRulerColumn</a></b>) 
-  is always added, and a line number ruler column is added based on user preferences. 
-  The annotation ruler column handles the particulars of displaying the annotation 
-  images in the proper locations.</p>
-<p>Despite all the classes involved in showing a ruler, note that the example
-editor needed only to subclass framework classes to get ruler
-behavior.&nbsp;&nbsp; <b>JavaDocumentProvider</b>&nbsp;inherits an appropriate
-marker annotation model from <b><a href="../reference/api/org/eclipse/ui/editors/text/FileDocumentProvider.html">FileDocumentProvider</a></b>.&nbsp;
-The JavaTextEditor inherits the ruler presentation from <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.</p>
-<h4>Overview ruler</h4>
-<p>An overview ruler on the right hand side of the editing area is used to show 
-  annotations concerning the entire document.&nbsp; These annotations are shown 
-  relative to their position in the document and do not move as the user scrolls 
-  the document.&nbsp;&nbsp;There usually is a corresponding annotation on the 
-  vertical ruler when that portion of the document is visible.&nbsp;&nbsp;</p>
-<p>The vertical ruler below shows that there are two tasks in the document and
-one bookmark.&nbsp; Since the bookmarked text is visible, its annotation is also
-shown on the left.</p>
-<p><img src="images/javaeditoroverviewruler.png" alt="Vertical overview ruler in Java Editor" border="0" ></p>
-<p>The user can navigate to the location of the annotation in the code by
-clicking on the annotation itself.</p>
-<p>The types of annotations shown in the overview ruler are determined by adding 
-  annotation types to the ruler.&nbsp; In the following snippet from <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>, 
-  annotation types are dynamically added to the ruler. (See next section for more 
-  information about <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>.)</p>
-
-<pre>private void showAnnotationOverview(Object annotationType) {<br>	if (fOverviewRuler != null) {
-		Color c= getAnnotationTypeColor(annotationType);<br>		fOverviewRuler.setAnnotationTypeColor(annotationType, c);
-		int l= getAnnotationTypeLayer(annotationType);<br>		fOverviewRuler.setAnnotationTypeLayer(annotationType, l);<br>		fOverviewRuler.addAnnotationType(annotationType);<br>		fOverviewRuler.update();<br>	}
-}</pre>
-<p>The overview ruler is also supplied with an <b><a href="../reference/api/org/eclipse/jface/text/source/IAnnotationAccess.html">IAnnotationAccess</a></b>
-that is used to provide information about a particular annotation, such as its
-type and how it is to be displayed.&nbsp; The <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-uses a <a href="../reference/api/org/eclipse/ui/texteditor/DefaultMarkerAnnotationAccess.html"><b>DefaultMarkerAnnotationAccess</b></a>
-which interprets annotations according to their marker types and consults the
-user preferences to see which marker types should be shown in the overview
-ruler. </p>
-
-<pre>protected IAnnotationAccess createAnnotationAccess() {
-	return new DefaultMarkerAnnotationAccess(fAnnotationPreferences);
-}</pre>
-<p>Consult the implementation of <a href="../reference/api/org/eclipse/ui/texteditor/DefaultMarkerAnnotationAccess.html"><b>DefaultMarkerAnnotationAccess</b></a>
-and <a href="../reference/api/org/eclipse/ui/texteditor/MarkerAnnotation.html"><b>MarkerAnnotation</b></a>
-for more detail about presenting markers in the overview ruler. </p>
-<h4>Text annotations </h4>
-<p>In addition to showing annotations in the rulers, a source viewer can show
-annotations as colored squiggly marks in the text.&nbsp;&nbsp;</p>
-<p><img src="images/javaeditorsquiggly.png" alt="Squiggly mark in Java Editor" border="0"></p>
-<p>We'll look again at the creation of the source viewer in <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.</p>
-
-<pre>protected ISourceViewer createSourceViewer(Composite parent, IVerticalRuler ruler, int styles) {
-		
-	... 
-	ISourceViewer sourceViewer= new SourceViewer(parent, ruler, fOverviewRuler, isOverviewRulerVisible(), styles);
-	<b>fSourceViewerDecorationSupport= new SourceViewerDecorationSupport(sourceViewer, fOverviewRuler, fAnnotationAccess, sharedColors);
-	configureSourceViewerDecorationSupport();</b>
-		
-	return sourceViewer;
-}</pre>
-<p>The class <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>
-handles many of the decorations shown in a source viewer, including text
-annotations, colored margins, colored cursor lines, and the like.&nbsp; It is
-configured with the user preferences so that it can respond to dynamic updates
-of user preference changes.&nbsp; Most editors need not be concerned with the
-details of how these decorations are painted.&nbsp; (See <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>
-and related classes such as <a href="../reference/api/org/eclipse/jface/text/source/AnnotationPainter.html"><b>AnnotationPainter</b></a>
-if you must!).&nbsp; The important thing to know is what decorations are
-available so that the <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
-and its supporting <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a>
-are configured correctly.</p>
-<h4>Configuring a SourceViewerDecorationSupport</h4>
-<p>Let's look at the configuration used by <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-for the decoration support.</p>
-
-<pre>protected void configureSourceViewerDecorationSupport() {
-
-	<b>Iterator e= fAnnotationPreferences.getAnnotationPreferences().iterator();
-	while (e.hasNext())
-		fSourceViewerDecorationSupport.setAnnotationPreference((AnnotationPreference) e.next());</b>
-	fSourceViewerDecorationSupport.setAnnotationPainterPreferenceKeys(DefaultMarkerAnnotationAccess.UNKNOWN, UNKNOWN_INDICATION_COLOR, UNKNOWN_INDICATION, UNKNOWN_INDICATION_IN_OVERVIEW_RULER, 0);
-		
-	fSourceViewerDecorationSupport.setCursorLinePainterPreferenceKeys(CURRENT_LINE, CURRENT_LINE_COLOR);
-	fSourceViewerDecorationSupport.setMarginPainterPreferenceKeys(PRINT_MARGIN, PRINT_MARGIN_COLOR, PRINT_MARGIN_COLUMN);
-	fSourceViewerDecorationSupport.setSymbolicFontName(getFontPropertyPreferenceKey());
-}</pre>
-<p>Note that the annotation preferences are used to define annotation types for 
-  all of the annotations shown in the user preferences.&nbsp; This includes annotations 
-  contributed by any plug-in and is not limited to the workbench-supplied annotations.&nbsp; 
-  If you do not wish to show all available annotations in your editor, you should 
-  override this method and set up the <a href="../reference/api/org/eclipse/ui/texteditor/SourceViewerDecorationSupport.html"><b>SourceViewerDecorationSupport</b></a><b> 
-  </b>with only those types you want to show.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm
deleted file mode 100644
index fe96181..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_contentassist.htm
+++ /dev/null

@@ -1,154 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Content assist
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Content assist</H2>
-<p>Content assist allows you to provide context sensitive content completion upon 
-  user request.&nbsp; This functionality is implemented by the platform text framework 
-  in <b><a href="../reference/api/org/eclipse/jface/text/contentassist/package-summary.html">org.eclipse.jface.text.contentassist</a></b>.&nbsp; 
-  Popup windows (infopops) are used to propose possible text choices to complete 
-  a phrase.&nbsp; The user can select these choices for insertion in the text.&nbsp; 
-  Content assist also supports contextual infopops for providing the user with 
-  information that is related to the current position in the document.&nbsp;</p>
-<p>Implementing content assist is
-optional.&nbsp; By default, <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>does not install a content assistant since it does not know the
-document model used for a particular editor, and has no generic behavior for
-content assist.&nbsp;</p>
-<p>In order to implement content assist, your editor's source
-viewer configuration must be <a href="editors_sourceviewers.htm">configured</a>
-to define a content assistant.&nbsp; This is done in the Java editor example
-inside the <b>JavaSourceViewerConfiguration</b>.</p>
-
-<pre>public IContentAssistant getContentAssistant(ISourceViewer sourceViewer) {
-
-	ContentAssistant assistant= new ContentAssistant();
-<b>	assistant.setContentAssistProcessor(new JavaCompletionProcessor(), IDocument.DEFAULT_CONTENT_TYPE);
-	assistant.setContentAssistProcessor(new JavaDocCompletionProcessor(), JavaPartitionScanner.JAVA_DOC);
-</b>
-	...
-	return assistant;
-}</pre>
-<p>Content assist behavior is defined in the interface <a href="../reference/api/org/eclipse/jface/text/contentassist/IContentAssistant.html"><b>IContentAssistant</b></a>.&nbsp;
-Setting up a content assistant is somewhat similar to setting up syntax
-highlighting.&nbsp; The assistant should be configured with different phrase completion strategies for different
-document content types.&nbsp; The completion strategies are implemented
-using&nbsp; <a href="../reference/api/org/eclipse/jface/text/contentassist/IContentAssistProcessor.html"><b>IContentAssistProcessor</b></a>.&nbsp;
-A processor proposes completions and computes context information for an offset
-within particular content type.</p>
-<h3>Content assist processors</h3>
-<p>Not all content types need to have content assistance.&nbsp; In the Java example 
-  editor, content assist processors are provided for the default content type 
-  and javadoc, but not for multi-line comments.&nbsp; Let's look at each of these 
-  processors.</p>
-<p>The <b>JavaCompletionProcessor</b> is quite simple.&nbsp; It can only propose
-keywords as completion candidates.&nbsp; The keywords are defined in a field,
-<code>fgProposals</code>, and these keywords are always proposed as the
-candidates:</p>
-
-<pre>public ICompletionProposal[] computeCompletionProposals(ITextViewer viewer, int documentOffset) {
-	ICompletionProposal[] result= new ICompletionProposal[fgProposals.length];
-	for (int i= 0; i &lt; fgProposals.length; i++) {
-		IContextInformation info= new ContextInformation(fgProposals[i], MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.Proposal.ContextInfo.pattern&quot;), new Object[] { fgProposals[i] })); //$NON-NLS-1$
-		result[i]= new CompletionProposal(fgProposals[i], documentOffset, 0, fgProposals[i].length(), null, fgProposals[i], info, MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.Proposal.hoverinfo.pattern&quot;), new Object[] { fgProposals[i]})); //$NON-NLS-1$
-	}
-	return result;
-}</pre>
-<p><img src="images/javacontentassist.png" alt="Keyword content assist" border="0"></p>
-
-<p>Completion can be triggered by user request or can be automatically triggered
-when the &quot;(&quot; or &quot;.&quot; character is typed:</p>
-
-<pre>public char[] getCompletionProposalAutoActivationCharacters() {
-	return new char[] { '.', '(' };
-}</pre>
-<p>In addition to proposing completions, the <b>JavaCompletionProcessor</b> 
-defines context information that can be requested by the user.&nbsp; Context
-information includes a description of the pieces of information available in a
-given context and the detailed information message.&nbsp;&nbsp;</p>
-<p>In the Java editor example, the information is not really contextual.&nbsp; 
-  An array containing five similar context information objects is computed for the 
-  current offset when the user requests context info.&nbsp;All of these context 
-  information objects define a context that contains the five characters in front 
-  of the offset and the five after the offset. If any one of these five proposals is 
-  selected, the detailed information will appear near the cursor and will stay 
-  as long as the cursor is within the context of the five characters around the offset. 
-</p>
-
-<pre>public IContextInformation[] computeContextInformation(ITextViewer viewer, int documentOffset) {
-	IContextInformation[] result= new IContextInformation[5];
-	for (int i= 0; i &lt; result.length; i++)
-		result[i]= new ContextInformation(
-			MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.ContextInfo.display.pattern&quot;), new Object[] { new Integer(i), new Integer(documentOffset) }),
-			MessageFormat.format(JavaEditorMessages.getString(&quot;CompletionProcessor.ContextInfo.value.pattern&quot;), new Object[] { new Integer(i), new Integer(documentOffset - 5), new Integer(documentOffset + 5)}));
-	return result;
-}</pre>
-<p><img src="images/javacontextassist.png" alt="Java context assist" border="0"></p>
-<p>&nbsp;</p>
-<p>This context information is shown automatically when the &quot;#&quot; character 
-  is typed:</p>
-<pre>public char[] getContextInformationAutoActivationCharacters() {
-	return new char[] { '#' };
-}</pre>
-<h3>Content assist configuration</h3>
-<p>The appearance and behavior of content assist can be configured using <a href="../reference/api/org/eclipse/jface/text/contentassist/IContentAssistant.html"><b>IContentAssistant</b></a>.&nbsp;
-For example, you can configure the auto activation time out, and the orientation
-and color of information popups.</p>
-
-<pre>public IContentAssistant getContentAssistant(ISourceViewer sourceViewer) {
-
-	ContentAssistant assistant= new ContentAssistant();
-	...
-	assistant.enableAutoActivation(true);
-	assistant.setAutoActivationDelay(500);
-	assistant.setProposalPopupOrientation(IContentAssistant.PROPOSAL_OVERLAY);
-	assistant.setContextInformationPopupOrientation(IContentAssistant.CONTEXT_INFO_ABOVE);
-	assistant.setContextInformationPopupBackground(JavaEditorEnvironment.getJavaColorProvider().getColor(new RGB(150, 150, 0)));
-
-	return assistant;
-}</pre>
-
-<h3>Show the content assist action in the menu</h3>
-<p>
-If the content assistant is correctly supplied as mentioned above then the key binding (<strong>Ctrl+Space</strong> per default) will work out of the box.
-To make the action appear in the main menu the editor action bar contributor has to be extended:</p>
-<pre>
-...
-private RetargetTextEditorAction fContentAssist;
-
-public MyEditorActionContributor() {
-	fContentAssist= new RetargetTextEditorAction();
-	String commandId= ITextEditorActionDefinitionIds.CONTENT_ASSIST_PROPOSALS;
-	fContentAssist.setActionDefinitionId(commandId);
-}
-
-public void contributeToMenu(IMenuManager menu) {
-	IMenuManager editMenu= menu.findMenuUsingPath(M_EDIT);
-	editMenu.appendToGroup(MB_ADDITIONS, fContentAssist);
-}
-
-public void setActiveEditor(IEditorPart part) {
-	IAction editorAction= getAction(part, ITextEditorActionConstants.CONTENT_ASSIST);
-	fContentAssist.setAction(editorAction);
-}
-...
-</pre>
-
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm
deleted file mode 100644
index 9df8900..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_documents.htm
+++ /dev/null

@@ -1,150 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Documents and partitions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Documents and partitions</H2>
-<p>The platform text framework defines a document model for text and provides 
-  a viewer that displays text using this model.&nbsp;We will start by looking 
-  at the Java editor example and how it uses this model.&nbsp; We will not focus 
-  on the basic mechanics of registering an editor extension, since we've already 
-  seen this in the section discussing <a href="workbench_basicext_editors.htm"><b>org.eclipse.ui.editors</b></a>.&nbsp; 
-  Instead, we'll look at the specifics of how the editor class is implemented 
-  in the example.</p>
-<h3>Document providers and documents</h3>
-<p>In the workbench, an editor is typically opened when the user selects a domain 
-  element (such as a file or an element stored inside an archive file) and opens 
-  it.&nbsp; When the editor is created, it is associated with an editor input 
-  (<a href="../reference/api/org/eclipse/ui/IEditorInput.html"><b>IEditorInput</b></a>), 
-  which describes the object being edited.</p>
-<p>The Java editor example opens when the user opens a file with the &quot;*.jav&quot; 
-  extension.&nbsp; In this case, the input to the editor is an <a href="../reference/api/org/eclipse/ui/IFileEditorInput.html"><b>IFileEditorInput</b></a>.&nbsp; 
-  The platform text framework assumes little about the editor input itself.&nbsp; 
-  It works with a presentation model, called an <a href="../reference/api/org/eclipse/jface/text/IDocument.html"><b>IDocument</b></a>, 
-  for the input, so that it can effectively display and manipulate text.</p>
-<p>This means that there must be a way to map from an expected domain model (the 
-  editor input) to the presentation model.&nbsp; This mapping is defined in an 
-  <a href="../reference/api/org/eclipse/ui/texteditor/IDocumentProvider.html"><b>IDocumentProvider</b></a>.&nbsp; 
-  Given an editor input, the document provider returns an appropriate <a href="../reference/api/org/eclipse/jface/text/IDocument.html"><b>IDocument</b></a>.</p>
-<p>The Java editor example inherits the <b>TextFileDocumentProvider</b> defined by 
-  the plug-in <b>org.eclipse.ui.editors</b>. The extension
-  <b><a href="../reference/extension-points/org_eclipse_ui_editors_documentProviders.html">org.eclipse.ui.editors.documentProviders</a></b> 
-  is used to define mappings between editor input types (or file extensions)
-  and document providers. The editors plug-in defines its document provider as follows:</p>
-<pre>
-   &lt;extension
-         point="org.eclipse.ui.editors.documentProviders"&gt;
-      &lt;provider
-            class="org.eclipse.ui.editors.text.TextFileDocumentProvider"
-            inputTypes="org.eclipse.ui.IStorageEditorInput"
-            id="org.eclipse.ui.editors.text.StorageDocumentProvider"&gt;
-      &lt;/provider&gt;
-   &lt;/extension&gt;
-</pre>
-<p>This extension point allows plug-ins to register document providers and associate them
-  with either a file extension or an editor input class.  Since the Java editor example does
-  not define its own document provider extension, it inherits the generic document provider
-  specified for all input types that are <a href="../reference/api/org/eclipse/ui/IStorageEditorInput.html"><b>IStorageEditorInput</b></a>.
-  When the user opens a file for editing, the platform manages the details of creating the
-  proper document provider instance.  If a specific document provider is registered for the file extension, that one
-  will be used.  If there is no specific document provider for the file extension, then the editor input type
-  will be used to find the appropriate provider.</p>
-<p>By using the generic platform document provider, the Java editor example can take advantage of all of the
-features of the document provider, such as file buffering and other optimizations.</p>
-<h4>Document setup</h4>
-<p>Since the Java editor uses the platform text document provider, how can it supply any specialized behavior
-for handling Java files?</p>
-<p>
-The extension <b><a href="../reference/extension-points/org_eclipse_core_filebuffers_documentSetup.html">org.eclipse.core.filebuffers.documentSetup</a></b> 
-is used to define mappings between file extensions and an <a href="../reference/api/org/eclipse/core/filebuffers/IDocumentSetupParticipant.html"><b>IDocumentSetupParticipant</b></a>.
-The setup participant will set up the document with any special features once it has been provided to the editor.</p>
-<pre>&lt;extension
-	id="ExampleJavaDocumentSetupParticipant"
-	name="%documentSetupParticipantName"
-	point="org.eclipse.core.filebuffers.documentSetup"&gt;
-	&lt;participant
-		extensions="jav"
-		<b>class="org.eclipse.ui.examples.javaeditor.JavaDocumentSetupParticipant"</b>&gt;
-	&lt;/participant&gt;
-&lt;/extension&gt;
-</pre>
-<p>This extension definition is what gives the example a chance to setup the document for Java specific
-tasks.  So what does <b>JavaDocumentSetupParticipant</b> do?  We'll look at a simplified version of the
-<b>setup</b> method.</p>
-<pre> 	public void setup(IDocument document) {
-		...
-		IDocumentPartitioner partitioner= new FastPartitioner(JavaEditorExamplePlugin.getDefault().getJavaPartitionScanner(), JavaPartitionScanner.JAVA_PARTITION_TYPES);
-		partitioner.connect(document);
-		...
-	}
-</pre>
-<p>The setup code configures an object called a <b>partitioner</b>.</p>
-<h4>Partitions</h4>
-<p>The partitioner (<a href="../reference/api/org/eclipse/jface/text/IDocumentPartitioner.html"><b>IDocumentPartitioner</b></a>)
-is responsible for dividing the document into non-overlapping 
-  regions called partitions.&nbsp; Partitions (represented by <a href="../reference/api/org/eclipse/jface/text/ITypedRegion.html"><b>ITypedRegion</b></a>) 
-  are useful for treating different sections of the document differently with 
-  respect to features like syntax highlighting or formatting.</p>
-<p> In the case of the Java editor
-example, the document is divided into partitions that represent the javadoc
-comments, multi line comments, and everything else.&nbsp; Each region is assigned a
-content type and its position in the document.&nbsp; Positions are updated as the user edits text.</p>
-<h4>Rule based document partitioning</h4>
-<p>It is up to each editor to determine the appropriate implementation for a
-document partitioner.&nbsp; Support is provided in <b><a href="../reference/api/org/eclipse/jface/text/rules/package-summary.html">org.eclipse.jface.text.rules</a></b>
- for rule-based document scanning.&nbsp; Using a rule-based scanner allows an editor to use
-the <a href="../reference/api/org/eclipse/jface/text/rules/FastPartitioner.html"><b>FastPartitioner</b></a>
-provided by the framework.</p>
-<pre>IDocumentPartitioner partitioner= new FastPartitioner(JavaEditorExamplePlugin.getDefault().getJavaPartitionScanner(), JavaPartitionScanner.JAVA_PARTITION_TYPES);
-</pre>
-<p><a href="../reference/api/org/eclipse/jface/text/rules/RuleBasedPartitionScanner.html"><b>RuleBasedPartitionScanner</b></a>
-is the superclass for rule based scanners.&nbsp; Subclasses are responsible
-for enumerating and implementing the rules that should be used to distinguish
-tokens such as line delimiters, white space, and generic
-    patterns when scanning a document.&nbsp; The example's <b>JavaPartitionScanner</b>
-defines rules for distinguishing single line comments, character constants, javadoc, multi
-line comments, and&nbsp;words.&nbsp; This is done in the scanner's constructor:</p>
-<pre>public JavaPartitionScanner() {
-	super();
-	IToken javaDoc= new Token(JAVA_DOC);
-	IToken comment= new Token(JAVA_MULTILINE_COMMENT);
-
-	List rules= new ArrayList();
-	// Add rule for single line comments.
-	rules.add(new EndOfLineRule(&quot;//&quot;, Token.UNDEFINED)); 
-
-	// Add rule for strings and character constants.
-	rules.add(new SingleLineRule(&quot;\&quot;&quot;, &quot;\&quot;&quot;, Token.UNDEFINED, '\\')); 
-	rules.add(new SingleLineRule(&quot;'&quot;, &quot;'&quot;, Token.UNDEFINED, '\\')); 
-
-	// Add special case word rule.
-	rules.add(new WordPredicateRule(comment));
-
-	// Add rules for multi-line comments and javadoc.
-	rules.add(new MultiLineRule(&quot;/**&quot;, &quot;*/&quot;, javaDoc, (char) 0, true)); 
-	rules.add(new MultiLineRule(&quot;/*&quot;, &quot;*/&quot;, comment, (char) 0, true)); 
-
-	IPredicateRule[] result= new IPredicateRule[rules.size()];
-	rules.toArray(result);
-	setPredicateRules(result);
-}</pre>
-<p>See the classes in <b><a href="../reference/api/org/eclipse/jface/text/rules/package-summary.html">org.eclipse.jface.text.rules</a></b>
- for more details about defining rules and the types of rules availables.&nbsp;
-We'll look at the scanners again when we look at <a href="editors_highlighting.htm">syntax
-coloring</a>.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm
deleted file mode 100644
index fc74766..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_highlighting.htm
+++ /dev/null

@@ -1,130 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Syntax coloring
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Syntax coloring</H2>
-<p>Syntax coloring is provided in the platform text framework using a model of damage, repair, and reconciling.&nbsp;
-For
-    each change applied to a document, a presentation reconciler determines
-    which region of the visual presentation should be invalidated and how to
-    repair it.&nbsp; Different strategies can be used for different content
-types in the document.</p>
-<p>Implementing syntax coloring (and doing so with a presentation reconciler) is
-optional.&nbsp; By default, <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>does not install a presentation reconciler since it does not know the
-document model used for a particular editor, and has no generic behavior for
-syntax highlighting.&nbsp;&nbsp;</p>
-<p>In order to use the reconciling classes to implement syntax highlighting, your editor's source
-viewer configuration must be <a href="editors_sourceviewers.htm">configured</a>
-to define a presentation reconciler.&nbsp; Once again, we start with <b>JavaSourceViewerConfiguration</b>
- to see how a presentation reconciler is defined for our editor.</p>
-
-<pre>public IPresentationReconciler getPresentationReconciler(ISourceViewer sourceViewer) {
-
-	PresentationReconciler reconciler= new PresentationReconciler();
-	...
-	return reconciler;
-}</pre>
-<p>To understand what a presentation reconciler does, we must first look at the
-concepts of damage, repair, and reconciling.</p>
-<h3>Damage, repair, and reconciling</h3>
-<p>As the user modifies text in an editor, parts of the editor must be
-redisplayed to show the changes.&nbsp; Computing the text that must be
-redisplayed is known as computing <b>damage</b>.&nbsp; When syntax coloring is
-involved, the amount of damage caused by an editing operation becomes more
-extensive, since the presence or absence of a single character could change the
-coloring of the text around it.&nbsp;&nbsp;</p>
-<p>Damagers (<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationDamager.html">IPresentationDamager</a></b>)
-  determine the region of a document's presentation which must be rebuilt because 
-  of a document change. A presentation damager is assumed to be specific to a 
-  particular document content type (or region). It must be able to return a damage 
-  region that is valid input for a presentation repairer (<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationRepairer.html">IPresentationRepairer</a></b>).&nbsp; 
-  A repairer must be able to derive all of the information 
-  it needs from a damage region in order to successfully describe the <b>repairs</b> 
-  that are needed for a particular content type.</p>
-<p><b>Reconciling</b> describes the overall process of
-maintaining the presentation of a document as changes are made in the
-editor.&nbsp; A presentation reconciler (<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationReconciler.html">IPresentationReconciler</a></b>)
-monitors changes to the text through its associated viewer.&nbsp; It uses the
-document's regions to determine the content types affected by the change and
-notifies a damager that is appropriate for the affected content type.&nbsp; Once
-the damage is computed, it is passed to the appropriate repairer which will
-construct repair descriptions that are applied to the viewer to put it back in
-sync with the underlying content.&nbsp;</p>
-<p>The classes in <b><a href="../reference/api/org/eclipse/jface/text/reconciler/package-summary.html">org.eclipse.jface.text.reconciler</a></b>
- define additional support classes for synchronizing a document model with
-external manipulation of the document.</p>
-<p>Presentation reconcilers should be provided with a repairer and
-damager pair for each content type to be found in the document.&nbsp; It is up to each editor to determine the appropriate implementation for a
-presentation reconciler.&nbsp; However, the platform provides support in <b><a href="../reference/api/org/eclipse/jface/text/rules/package-summary.html">org.eclipse.jface.text.rules</a></b>
- for using rule-based document scanners to compute and repair damage.&nbsp;
-Default damagers and repairers are defined in this package.&nbsp; They can be
-used along with the standard reconcilers in <b><a href="../reference/api/org/eclipse/jface/text/presentation/package-summary.html">org.eclipse.jface.text.presentation</a></b>
-to implement syntax coloring by defining scanning rules for the document.</p>
-<h4>Rule based reconciling</h4>
-<p>Now we have enough background to look in detail at the creation of the
-example presentation
-reconciler.&nbsp; Recall that the Java editor example implements a <b>JavaPartitionScanner</b>
- which partitions the document into content types representing javadoc, multi
-line comments, and everything else.&nbsp;</p>
-<p>For each of these content types, a damager/repairer pair must be
-specified.&nbsp; This is done below using the <b><a href="../reference/api/org/eclipse/jface/text/presentation/PresentationReconciler.html">PresentationReconciler</a></b>
-and the <b><a href="../reference/api/org/eclipse/jface/text/rules/DefaultDamagerRepairer.html">DefaultDamagerRepairer</a></b>.</p>
-<pre>
-	JavaColorProvider provider= JavaEditorEnvironment.getJavaColorProvider();
-	PresentationReconciler reconciler= new PresentationReconciler();
-		
-	DefaultDamagerRepairer dr= new DefaultDamagerRepairer(JavaEditorEnvironment.getJavaCodeScanner());
-	reconciler.setDamager(dr, IDocument.DEFAULT_CONTENT_TYPE);
-	reconciler.setRepairer(dr, IDocument.DEFAULT_CONTENT_TYPE);
-
-	dr= new DefaultDamagerRepairer(new SingleTokenScanner(new TextAttribute(provider.getColor(JavaColorProvider.JAVADOC_DEFAULT))));
-	reconciler.setDamager(dr, JavaPartitionScanner.JAVA_DOC);
-	reconciler.setRepairer(dr, JavaPartitionScanner.JAVA_DOC);
-
-	dr= new DefaultDamagerRepairer(new SingleTokenScanner(new TextAttribute(provider.getColor(JavaColorProvider.MULTI_LINE_COMMENT))));
-	reconciler.setDamager(dr, JavaPartitionScanner.JAVA_MULTILINE_COMMENT);
-	reconciler.setRepairer(dr, JavaPartitionScanner.JAVA_MULTILINE_COMMENT);
-
-	return reconciler;
-</pre>
-<p> Note that the example provide scanners for each content type.&nbsp;&nbsp;</p>
-<p>The default content type is set up with a <b>JavaCodeScanner</b> so that
-keywords can be detected and colored.&nbsp; The <b>JavaCodeScanner</b> builds
-rules for detecting different kinds of tokens, such as single line comments,
-white space, and words.&nbsp; It describes the colors that should be used for
-words of different token types.&nbsp;&nbsp;&nbsp;</p>
-<p>The other content types are set up with a <b>SingleTokenScanner</b> and given
-a color to be used for tokens in these content types.</p>
-<p>All of the details for damaging and repairing the proper parts of the
-documents according to the scanning rules are handled by <b><a href="../reference/api/org/eclipse/jface/text/rules/DefaultDamagerRepairer.html">DefaultDamagerRepairer</a></b>.&nbsp;
-These details typically don't need to be understood by plug-in code.&nbsp; Your
-plug-in should focus on building a set of rules that are appropriate for
-partitioning and scanning its editor content.</p>
-<h4>Dynamically installing a reconciler</h4>
-<p>The Java editor example provides a subclass of <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b> for installing the presentation reconciler as seen earlier.&nbsp; A
-presentation reconciler can also be installed dynamically on a text viewer using
-<b><a href="../reference/api/org/eclipse/jface/text/presentation/IPresentationRepairer.html">IPresentationReconciler</a></b>
-protocol.&nbsp; There is no
-particular runtime benefit to doing it either way, but putting all of the
-pluggable behavior overrides in a subclass of <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>provides the advantage of consolidating all of the behavioral overrides in one place.&nbsp;
-The dynamic protocol may be useful when different presentation reconcilers are
-attached to a viewer throughout the life of an editor.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm
deleted file mode 100644
index d34768d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_hover.htm
+++ /dev/null

@@ -1,118 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Text and ruler hover
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Text and ruler hover</H2>
-<p>Hover support is provided in the platform text framework, allowing you to implement 
-  informational hovers (or infopops) over the text and the rulers shown in your 
-  editor.</p>
-<p>Hover support is optional.&nbsp; By default, <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>does not install hover behavior since there is no useful general information
-to show.&nbsp; In order to provide text or ruler hover, your editor's source
-viewer configuration must be <a href="editors_sourceviewers.htm">configured</a>
-to define a pluggable hover object.</p>
-<p>Let's look again at <b>JavaSourceViewerConfiguration</b>
- to see which methods define the hover behavior:</p>
-
-<pre>public ITextHover getTextHover(ISourceViewer sourceViewer, String contentType) {
-	return new JavaTextHover();
-}
-public IAnnotationHover getAnnotationHover(ISourceViewer sourceViewer) {
-	return new JavaAnnotationHover();
-}
-</pre>
-<p>Hover helper classes can also be installed dynamically using <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
- protocol (<b>setTextHover</b> and <b>setAnnotationHover</b>).&nbsp; There is no
-particular runtime benefit to doing it either way, but putting all of the
-pluggable behavior overrides in a subclass of <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>provides the advantage of consolidating all of the definitions in one place.</p>
-<p>Let's look at the specifics of providing both kinds of hover.</p>
-<h3>Text hover</h3>
-<p>Text hover allows you to provide informational text about text shown in the 
-  editor.&nbsp; This is done using the <b><a href="../reference/api/org/eclipse/jface/text/ITextHover.html">ITextHover</a></b> 
-  interface.&nbsp; A text hover is responsible for computing the region that should 
-  be used as the source of hover information, given an offset into the document.&nbsp; 
-  It is also responsible for providing the informational text about a specific 
-  region.&nbsp; <b>JavaTextHover</b> is pretty simple.&nbsp; It checks to see 
-  if the supplied offset for hover is contained inside the text selection.&nbsp;&nbsp;&nbsp; 
-  If so, it supplies the selection range as hover region.&nbsp;</p>
-
-<pre>public class JavaTextHover implements ITextHover {
-
-	...
-	
-	public IRegion getHoverRegion(ITextViewer textViewer, int offset) {
-		Point selection= textViewer.getSelectedRange();
-		if (selection.x &lt;= offset &amp;&amp; offset &lt; selection.x + selection.y)
-			return new Region(selection.x, selection.y);
-		return new Region(offset, 0);
-	}
-}</pre>
-<p>Given its own computed hover region, it obtains the selected text from its
-document and returns that as the hover info.</p>
-
-<pre>public class JavaTextHover implements ITextHover {
-
-	public String getHoverInfo(ITextViewer textViewer, IRegion hoverRegion) {
-		if (hoverRegion != null) {
-			try {
-				if (hoverRegion.getLength() &gt; -1)
-					return textViewer.getDocument().get(hoverRegion.getOffset(), hoverRegion.getLength());
-			} catch (BadLocationException x) {
-			}
-		}
-		return JavaEditorMessages.getString(&quot;JavaTextHover.emptySelection&quot;); 
-	}
-	...
-}</pre>
-<p>Sure enough, we can see that if we hover over a selection in the editor, the
-hover text shows the selection.</p>
-<p><img src="images/javatexthover.png" alt="Hover information on selected region" border="0"></p>
-<p>More complicated contextual information can be used to compute useful hover
-information.&nbsp; Examples of this can be found in the <b>JavaTextHover</b>
-implemented with the JDT editor.</p>
-<h3>Ruler hover</h3>
-<p>Hover on the vertical ruler is useful for showing show line-oriented information.&nbsp;
-The hover class is configured as described above.&nbsp; <b><a href="../reference/api/org/eclipse/jface/text/source/IAnnotationHover.html">IAnnotationHover</a></b>
-is the interface for ruler hover objects.&nbsp; Although the name implies that
-the hover is designed for annotations in the ruler, it is really up to an
-individual editor to detemine what is appropriate.&nbsp; A ruler hover is responsible for returning the info string associated with a
-particular line number, regardless of the presence of markers on that line.&nbsp;&nbsp;&nbsp;</p>
-<p>The Java example editor's <b>JavaAnnotationHover</b>  implements hover for
-all lines.&nbsp; It uses the line number to
-obtain all of the text on the hover line and returning it as the info string.</p>
-
-<pre>public String getHoverInfo(ISourceViewer sourceViewer, int lineNumber) {
-	IDocument document= sourceViewer.getDocument();
-
-	try {
-		IRegion info= document.getLineInformation(lineNumber);
-		return document.get(info.getOffset(), info.getLength());
-	} catch (BadLocationException x) {
-	}
-	return null;
-}</pre>
-<p><img src="images/javarulerhover.png" alt="Hover information on ruler" border="0"></p>
-<p>Since the hover has access to the document and the
-source viewer, it has all the context needed to make more complicated contextual
-decisions about the info that should be shown.&nbsp; For example, the annotation
-model could be retrieved from the source viewer in order to provide hover info
-for any annotations shown in the vertical ruler.&nbsp; The <b>JavaAnnotationHover</b>
-provided by the JDT editor provides this capability.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm
deleted file mode 100644
index 860a088..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_jface.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Text editors and platform text
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2 CLASS="Heading2">Text editors and platform text</H2>
-<p>The platform text facility is used to implement the default text editor for
-the workbench.&nbsp; The interface for text editing is defined in <a href="../reference/api/org/eclipse/ui/texteditor/ITextEditor.html"><b>ITextEditor</b></a>
- as a text specific extension of <a href="../reference/api/org/eclipse/ui/IEditorPart.html"><b>IEditorPart</b></a>.&nbsp;&nbsp;</p>
-<p>The implementation of <a href="../reference/api/org/eclipse/ui/texteditor/ITextEditor.html"><b>ITextEditor</b></a>
-in the platform is structured in layers.&nbsp; <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>
-is the core class of the framework for extending the editor to support source code style
-editing of text.&nbsp; This framework is defined in <a href="../reference/api/org/eclipse/ui/texteditor/package-summary.html"><b>org.eclipse.ui.texteditor</b></a>.</p>
-<p>The concrete implementation class <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>
-defines the behavior for the standard platform text editor.&nbsp; It is
-defined in the package <b><a href="../reference/api/org/eclipse/ui/editors/text/package-summary.html">org.eclipse.ui.editors.text</a></b>.</p>
-<p>The text editor framework provides a model-independent editor that
-supports the following features:</p>
-<ul>
-  <li>presentation and user modification of text</li>
-  <li>standard text editing operations such as cut/copy/paste, find/replace</li>
-  <li>support for context and pulldown menus</li>
-  <li>visual presentation of text annotations in rulers or as squigglies in the
-    text</li>
-  <li>automatic update of annotations as the user edits text</li>
-  <li>presentation of additional information such as line numbers</li>
-  <li>syntax highlighting</li>
-  <li>content assist</li>
-  <li>text outlining pages that show the hierarchical structure of the text</li>
-  <li>context sensitive behavior</li>
-  <li>hover support over rulers and text</li>
-  <li>key binding contexts</li>
-  <li>preference handling</li>
-</ul>
-<p>We will explore how these features can be implemented in an editor by
-studying the <b>org.eclipse.ui.examples.javaeditor</b>
- example.&nbsp; This example shows how complex features like text coloring, hover help, and
-automatic indenting can be implemented.&nbsp; </p>
-<p>In discussing these features we will be moving between the abstract
-framework, the platform editor <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>,
-and the example's subclass, <b>JavaEditor</b>.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm
deleted file mode 100644
index 1b63721..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_sourceviewers.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Configuring a source viewer
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Configuring a source viewer</H2>
-<p>So far we've looked at <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b>
- in the context of managing source code annotations.</p>
-<p>The <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b> 
-  is also the central hub for configuring your editor with pluggable behavior 
-  such as text hovering and syntax highlighting.&nbsp; &nbsp;For these features, the editor 
-  supplies a <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a> 
-  </b>that is used to configure the <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewer.html">SourceViewer</a></b> 
-  when it is created.&nbsp; The Java example editor need only to supply a <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a> 
-  </b>appropriate for its needs.&nbsp; The following snippet shows how the <b>JavaTextEditor</b> 
-  creates its configuration:</p>
-<pre>
-protected void initializeEditor() {
-	super.initializeEditor();
-	<b>setSourceViewerConfiguration(new JavaSourceViewerConfiguration());</b>
-	...
-</pre>
-<p>What does the <b>JavaSourceViewerConfiguration</b> do?&nbsp; Much of its
-behavior is inherited from <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>,
-which defines default strategies for pluggable editor behaviors such as auto
-indenting, undo behavior, double-click behavior, text hover, syntax
-highlighting, and formatting.&nbsp; Public methods in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a>
-</b>provide the helper objects that implement these behaviors.
- </p>
-<p>If the default behavior defined in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>
-does not suit your editor, you should override <b>initializeEditor() </b>as
-shown above and set your own source viewer configuration into the editor.&nbsp;
-Your configuration can override methods in <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>
-to supply customized helper objects that implement behavior for your
-editor.&nbsp; The following snippet shows two of the ways the <b>JavaSourceViewerConfiguration</b>
-supplies customized helper objects for the Java editor example:
- </p>
-
-<pre>public IAnnotationHover getAnnotationHover(ISourceViewer sourceViewer) {
-	return new JavaAnnotationHover();
-}
-	
-public IAutoIndentStrategy getAutoIndentStrategy(ISourceViewer sourceViewer, String contentType) {
-	return (IDocument.DEFAULT_CONTENT_TYPE.equals(contentType) ? new JavaAutoIndentStrategy() : new DefaultAutoIndentStrategy());
-}</pre>
-<p>In the first method, a customized helper class is provided for implementing 
-  annotation hovering.&nbsp; In the second method, the default content type of 
-  the document is queried to determine whether a customized auto-indent strategy 
-  or the default strategy should be used. </p>
-<p>See the API reference for <b><a href="../reference/api/org/eclipse/jface/text/source/SourceViewerConfiguration.html">SourceViewerConfiguration</a></b>
-for all the ways you can configure a source viewer by overriding methods.
- </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm
deleted file mode 100644
index ce55822..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_utilities.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Other text editor responsibilities
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Other text editor responsibilities</H2>
-<p>The Java example editor inherits a lot of useful default behavior from <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.&nbsp;
-The text editing framework handles several other responsibilities that you can
-customize by overriding methods in <a href="../reference/api/org/eclipse/ui/texteditor/AbstractTextEditor.html"><b>AbstractTextEditor</b></a>.&nbsp;
-Browse the implementation of this class and its subclasses to see how behavior
-is customized in the framework.</p>
-<p>The following are some of the useful framework features that can be
-configured.</p>
-<h3>Preference handling</h3>
-<p>Text editors typically contribute user preferences that control the
-presentation and behavior of the editor.&nbsp; In the text framework, each text
-editor instance has an associated preference store that is used for accessing
-user preferences.&nbsp; This preference store can be set up by your editor, or
-you can inherit from preference stores already used in the framework.</p>
-<p>In the case of the Java example editor, it inherits the preference store
-initialized by <a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b>TextEditor</b></a>.&nbsp;
-This is the preference store defined by the workbench editors
-plug-in.&nbsp;&nbsp;</p>
-
-<pre>protected void initializeEditor() {
-	...
-	setPreferenceStore(EditorsPlugin.getDefault().getPreferenceStore());
-}</pre>
-
-The editors plug-in preferences can be manipulated in the 
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Editors</b></a>
-
-and
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.GeneralTextEditor)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Editors &gt; Text Editors</b></a>
-
-preference pages.
-<p>If you do not want to use the standard workbench text preferences for your 
-  editor, you can set a different preference store.&nbsp; This is typically done 
-  by overriding <b>initializeEditor</b> and setting your own preference store.&nbsp; 
-  If you do use your own preference store, you will also need to override the 
-  method <b>handlePreferenceStoreChanged()</b> which is triggered whenever a preference 
-  is updated.</p>
-<h3>Key bindings</h3>
-<p><a href="wrkAdv_keyBindings_contexts.htm">Key binding contexts</a> are useful
-for establishing a lookup order for key bindings. Having contextual key bindings
-reduces the chances of different plug-ins contributing conflicting key
-sequences.  By default, the workbench operates in a generic context for working with 
-windows or dialogs.  When a text editor becomes active, it is responsible
-for resetting the context to the text editing context, so that editor specific key
-bindings will be active.</p>
-
-<p>In the platform text framework, each text editor instance has an associated array of
-key binding scopes. It is responsible for setting the correct scopes when it becomes 
-  active. <a href="../reference/api/org/eclipse/ui/texteditor/AbstractDecoratedTextEditor.html"><b>AbstractDecoratedTextEditor</b></a> 
-  defines this scope and takes care of making it active. The scope is assigned 
-  in a method that is called from the constructor:</p>
-
-<pre>protected void initializeKeyBindingScopes() {
-	setKeyBindingScopes(new String[] { &quot;org.eclipse.ui.textEditorScope&quot; });  
-}</pre>
-
-<p>The argument to the method is an array of ids that have been defined for contexts.
-If you want your editor to define its own key binding context, then you can
-override this method in your editor class, or set the scope dynamically using <b>setKeybindingScopes</b>.</p>
-<p>The context itself must be defined with the corresponding id in the <b><a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></b>
-extension point. The following is the definition for the text editing context.</p>
-<pre>
-&lt;extension
-	point=&quot;org.eclipse.ui.contexts&quot;&gt;
-	&lt;context
-		name=&quot;%context.editingText.name&quot;
-		description=&quot;%context.editingText.description&quot;
-		id=&quot;org.eclipse.ui.textEditorScope&quot;
-		parentId=&quot;org.eclipse.ui.contexts.window&quot;&gt;
-	&lt;/context&gt;
-	...
-</pre>
-<p>(Note:&nbsp; We use the terms <b>scope</b> and <b>context</b> interchangeably in this
-discussion.  The method names in the text classes still refer to key binding contexts
-as scopes.  These method names reflect the original implementation of contexts as scopes 
-and use outdated terminology.)</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm
deleted file mode 100644
index 38aa5e8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench editors
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workbench editors</H2>
-<P >
-Although the implementation of a workbench editor will be specific to your plug-in and the 
-content that you want to edit, the workbench provides a general structure for building an 
-editor.  The following concepts apply to all workbench editors.</P>
-
-<h3 >
-Editor parts and their inputs</h3>
-
-<P >
-An editor must implement <a href="../reference/api/org/eclipse/ui/IEditorPart.html"><b>IEditorPart</b></a>
-and is often built by extending the <a href="../reference/api/org/eclipse/ui/part/EditorPart.html"><b>EditorPart</b></a>
-class.&nbsp; An editor implements its user interface in the <b>createPartControl</b>
-method.&nbsp; This method is used to assemble the SWT widgets or JFace viewers
-that present the editor contents.&nbsp;</P>
-
-<P >
-An <b> editor input</b> is a description of something to be edited. You can think of
-an editor input as a file name, though it is more general.
-<a href="../reference/api/org/eclipse/ui/IEditorInput.html"> <b> IEditorInput</b></a> defines the protocol for an editor input, including the name of the input and the image that should be used to represent it in
-the labels at the top of the editor.</P>
-
-<P >
-<img src="images/editorInputLabel.png" alt="Editor input label" border="0"></P>
-<P >
-Three generic editor inputs are provided in the platform. <a href="../reference/api/org/eclipse/ui/IFileEditorInput.html"><b> IFileEditorInput</b></a> represents an input
-that is a file in the file system, and <a href="../reference/api/org/eclipse/ui/IURIEditorInput.html"><b> IURIEditorInput</b></a> represents an input based on a URI.&nbsp;
-<a href="../reference/api/org/eclipse/ui/IStorageEditorInput.html"><b>IStorageEditorInput</b></a> represents an input
-that is a stream of bytes. These bytes may come from sources other than the file system.</P>
-
-
-<h3 >
-Resetting the editor input</h3>
-
-
-<P >If your editor can support the replacement of the
-editor's input object on the fly, you should implement&nbsp; <a href="../reference/api/org/eclipse/ui/IReusableEditor.html"><b>IReusableEditor</b></a>.
-Implementing this interface allows the workbench to &quot;recycle&quot; your
-editor.&nbsp; Workbench user preferences allow the user to dictate that editors
-should be reused after a certain number of them are open.</P>
-
-
-<h3 >
-Navigating the editor input&nbsp;</h3>
-
-
-<p>If you want to implement a navigation history in your editor, you should
-implement <a href="../reference/api/org/eclipse/ui/INavigationLocationProvider.html"><b>INavigationLocationProvider</b></a>.&nbsp;
-This provides a mechanism for the workbench to request a current navigation
-location (<a href="../reference/api/org/eclipse/ui/INavigationLocation.html"><b>INavigationLocation</b></a>)
-as needed to keep a navigation history.&nbsp; The workbench handles the
-mechanics of the navigation user interface.&nbsp; Your <a href="../reference/api/org/eclipse/ui/INavigationLocation.html"><b>INavigationLocation</b></a>
-will be notified when it needs to restore the editor to the location that it represents.</p>
-
-
-<P >The rest of your editor's implementation depends on the content that you are
-trying to present.&nbsp; We'll look next at the most common type of editor - the
-text editor.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm b/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm
deleted file mode 100644
index 8e55895..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/editors_workbench_outliner.htm
+++ /dev/null

@@ -1,140 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Content outliners</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<h2>
-Content outliners</h2>
-<P >
-Editors often have corresponding <b>content outliners</b> that provide a
-structured view of the editor contents and assist the user in navigating through
-the contents of the editor.</P>
-<P >
-The workbench provides a standard <b>Outline</b> view for this purpose.&nbsp;
-The workbench user controls when this view is visible using the <b>Window &gt; Show
-View</b> menu.</P>
-<P >Since the generic
-<a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"><b> TextEditor</b></a> 
-doesn't know anything about the structure of its text, it cannot provide
-behavior for an interesting outline view.&nbsp; Therefore, the default <b>Outline</b> view,
-shown below, doesn't
-do much.</P>
-<P ><img src="images/genericoutliner.png" alt="Default content outliner" border="0"></P>
-<P >&nbsp;</P>
-<P >Editors in the text framework can supply their own content outliner page to the
-outline view.&nbsp; The outliner for an editor is specified when the workbench requests an
-adapter of type <b><a href="../reference/api/org/eclipse/ui/views/contentoutline/IContentOutlinePage.html">IContentOutlinePage</a></b>.</P>
-<pre>
-public Object getAdapter(Class required) {
-	if (IContentOutlinePage.class.equals(required)) {
-		if (fOutlinePage == null) {
-			fOutlinePage= new <b>JavaContentOutlinePage</b>(getDocumentProvider(), this);
-			if (getEditorInput() != null)
-				fOutlinePage.setInput(getEditorInput());
-		}
-		return fOutlinePage;
-	}
-	return super.getAdapter(required);
-}
-</pre>
-
-
-<P >A content outliner page must implement <b><a href="../reference/api/org/eclipse/ui/views/contentoutline/IContentOutlinePage.html">IContentOutlinePage</a></b>.&nbsp;
-This interface combines the ability to notify selection change listeners (<a href="../reference/api/org/eclipse/jface/viewers/ISelectionProvider.html"><b>ISelectionProvider</b></a>)
-with the behavior of being a page in a view (<a href="../reference/api/org/eclipse/ui/part/IPage.html"><b>IPage</b></a>).&nbsp;
-Content outliners are typically implemented using JFace viewers.&nbsp; The
-default implementation of a content outliner (<b><a href="../reference/api/org/eclipse/ui/views/contentoutline/ContentOutlinePage.html">ContentOutlinePage</a></b>)
-uses a JFace tree viewer to display a hierarchical representation of the
-outline.&nbsp; This representation is suitable for many structured outliners, including
-<b>JavaContentOutlinePage</b>.</P>
-
-
-<P >Let's take a look at the implementation of the page. When the outline page 
-  is created by the editor in the snippet above, its input element is set to the 
-  editor's input element.&nbsp; This input can often be passed directly to the 
-  outline page's viewer, as is done below.</P>
-
-
-<pre>
-public void createControl(Composite parent) {
-
-	super.createControl(parent);
-
-	TreeViewer viewer= getTreeViewer();
-	viewer.setContentProvider(new ContentProvider());
-	viewer.setLabelProvider(new LabelProvider());
-	viewer.addSelectionChangedListener(this);
-
-	if (fInput != null)
-		viewer.setInput(fInput);
-}
-</pre>
-
-
-<P >The tree viewer creation is inherited from <b><a href="../reference/api/org/eclipse/ui/views/contentoutline/ContentOutlinePage.html">ContentOutlinePage</a></b>.&nbsp; 
-  The standard label provider is used.  The content provider is provided inside
-   <b>JavaContentOutlinePage</b> and is responsible for parsing the editor input into
-   individual segments whenever it changes.</P>
-
-
-<pre>
-		public void inputChanged(Viewer viewer, Object oldInput, Object newInput) {
-			...
-			if (newInput != null) {
-				IDocument document= fDocumentProvider.getDocument(newInput);
-				if (document != null) {
-					document.addPositionCategory(SEGMENTS);
-					document.addPositionUpdater(fPositionUpdater);
-					parse(document);
-				}
-			}
-		}
-</pre>
-
-
-<P >The text is parsed into ranges, called segments, within the document.&nbsp;
-These segments are displayed by name in the outline view.</P>
-
-
-<P ><img src="images/javacontentoutline.png" alt="Java example outliner" border="0"></P>
-
-
-<P >When the selection changes, the selected segment is 
-  retrieved.&nbsp; Its offsets are used to set the highlight range in the editor.</P>
-
-
-<pre>
-public void selectionChanged(SelectionChangedEvent event) {
-
-	super.selectionChanged(event);
-
-	ISelection selection= event.getSelection();
-	if (selection.isEmpty())
-		fTextEditor.resetHighlightRange();
-	else {
-		Segment segment= (Segment) ((IStructuredSelection) selection).getFirstElement();
-		int start= segment.position.getOffset();
-		int length= segment.position.getLength();
-		try {
-			fTextEditor.setHighlightRange(start, length, true);
-		} catch (IllegalArgumentException x) {
-			fTextEditor.resetHighlightRange();
-		}
-	}
-}
-</pre>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm
deleted file mode 100644
index 80c5423..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Simple plug-in example</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Plug it in: Hello World meets the workbench</H1>
-<P >
-The Eclipse platform is structured as a core runtime engine and a set of additional features that are installed as platform
-<b>plug-ins</b>. Plug-ins contribute functionality to the platform by contributing to pre-defined
-<b> extension points</b>. The workbench UI is contributed by one such plug-in. When you start up the workbench, you are not starting up a single Java program. You are activating a platform runtime which can dynamically discover registered plug-ins and start them as needed.</P>
-<P >
-When you want to provide code that extends the platform, you do this by defining
-system extensions in your plug-in. The platform has a well-defined set of extension
-points - places where you can hook into the platform and contribute system behavior. From the platform's perspective, your plug-in is no different
-than basic plug-ins like the resource management system or the workbench itself.</P>
-<P >
-So how does your code become a plug-in?&nbsp;</P>
-<ul>
-  <li>Decide how your plug-in will be integrated with the platform.</li>
-  <li>Identify the extension points that you need to contribute in order to
-    integrate your plug-in.</li>
-  <li>Implement these extensions according to the specification for the
-    extension points.</li>
-  <li>Provide a manifest file (manifest.mf) that describes the packaging and
-  prerequisites for your code, and a plug-in manifest (plugin.xml) that
-  describes the extensions you are defining.</li>
-</ul>
-<P >
-The process for creating a plug-in is best demonstrated by implementing an old classic, 
-&quot;Hello World,&quot; as a plug-in.  The intention of this example is to give you a flavor
-of how plug-in development is different from Java application development.  We'll gloss over a 
-lot of details in order to get the plug-in built and running.  Then we'll look at extension
-points in more detail, see where they are defined, and learn how plug-ins describe their implementation of an extension.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm
deleted file mode 100644
index 56d0bdc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_btb.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Beyond the basics
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Beyond the basics</H2>
-<P >
-Hopefully you've gotten a flavor of how you can contribute code in the form of an extension, and package
-that functionality into a plug-in.  From here, you can start diving into more detail:</P>
-<ul>
-  <li><a href="workbench_basicext.htm">Basic workbench extension points</a></li>
-  <li><a href="workbench_menus.htm">Workbench menu contributions</a></li>
-  <li><a href="wrkAdv.htm">Advanced workbench concepts</a></li>
-  <li><a href="dialogs_wizards_extensions.htm">Workbench wizard extension points</a></li>
-</ul>
-<P >
-A complete list of extension points can be found in the <a href="../reference/extension-points/index.html">Platform
-Extension Point Reference</a>.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm
deleted file mode 100644
index f39100a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_create.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Creating the plug-in project
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Creating the plug-in project</H2>
-
-<P >You can use any Java IDE you wish to build Eclipse plug-ins, but of course the
-  Eclipse SDK provides tooling specific for plug-in development.  We'll walk 
-  through the steps for building our plug-in with the Eclipse SDK, since this is the 
-  typical case. If you are not already familiar with the Eclipse workbench and the Java IDE, 
-  consult the Java development user guide or PDE guide for further explanations of the steps 
-  we are taking. For now we are focusing on the code, not the tool; 
-  however, there are some IDE logistics for getting started.</P>
-<h3>Creating your plug-in project</h3>
-<p>You will need to create a project that contains your work.  We'll take advantage of some of the
-code-generation facilities of the Plug-in Development Environment (PDE) to give us a template to
-start from.  This will set up the project for writing Java code and generate the default plug-in 
-manifest files (explained in a moment) and a class to hold our view.
-</p>
-<ol>
-  <li>Open the <b>New Project...</b> wizard
-  
-  (<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>File &gt; New &gt; Project...</b></a>)
-  
-    and choose <b>Plug-in Project </b>from the <b>Plug-in Development</b> category
-    and click <strong>Next</strong>.</li>
-  <li>On the <strong>Plug-in Project </strong> page, use <b>com.example.helloworld</b> 
-    as the name for your project and check the box for <strong>Create a Java project</strong> 
-    (this should be the default).  Leave the other settings on the page with their default
-    settings and then click <strong>Next</strong> to accept the default plug-in project structure.</li>
-  <li>On the <strong>Plug-in Content</strong> page, look at the default settings.  The wizard sets <strong>com.example.helloworld</strong> 
-    as the id of the plug-in.&nbsp; The wizard will also generate a plug-in class for your plug-in and allow you to supply additional information about
-    contributing to the UI.  These defaults are acceptable, so click <strong>Next</strong>.  </li>
-  <li>On the <strong>Templates</strong> page, check the box for <strong>Create a plug-in using one of the templates</strong>.  Then
-    select the <strong>Plug-in with a view</strong> template.  Click <strong>Next</strong>.  </li>
-  <li>We want to create a minimal plug-in, so at this point we need to change the default settings to keep things as
-    simple as possible.  On the <strong>Main View Settings</strong> page, change the suggested defaults as follows:
-    <img border="0" src="images/firstpluginpde.png" alt="Plug-in view settings" >
-    <ul>
-    <li>Change the <strong>Java Package Name</strong> from <strong>com.example.helloworld.views</strong> to <strong>com.example.helloworld</strong>
-    (we don't need a separate package for our view).</li>
-    <li>Change the <strong>View Class Name</strong> to <strong>HelloWorldView</strong>.</li>
-    <li>Change the <strong>View Name</strong> to <strong>Hello View</strong>.</li>
-    <li>Leave the default <strong>View Category Id</strong> as <strong>com.example.helloworld</strong>.</li>
-    <li>Change the <strong>View Category Name</strong> to <strong>Hello Category</strong>.</li>
-    <li>Leave the default viewer type as <strong>Table viewer</strong> (we will change this in the code to make it even simpler).</li>
-    <li>Uncheck the box for <strong>Add the view to the resource perspective</strong>.</li>
-    <li>Click <strong>Next</strong> to proceed to the next page.</li>
-    </ul></li>
-  <li>On the <strong>View Features</strong> page, uncheck all of the boxes so that no extra
-    features are generated for the plug-in.  Click <strong>Finish</strong> to create the project and the plug-in skeleton.  </li>
-  <li>When asked if you would like to switch to the Plug-in Development perspective, 
-    answer <strong>Yes</strong>.</li>
-  <li>Navigate to your new project and examine its contents.</li>
-</ol>
-<p>The skeleton project structure includes several folders, files, and a Java package.  The important files at this stage are the
-<strong>plugin.xml</strong> and <strong>MANIFEST.MF</strong> (manifest) files and the Java source code for your plug-in.  
-We'll start by looking at the implementation for a view and then
-examine the manifest files.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm
deleted file mode 100644
index ebf0f43..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_manifest.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The Hello World manifests
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>The Hello World manifests</H2>
-
-<p>Before we run the new view, let's take a look at the manifest files that were 
-generated for us. First, double-click the plugin.xml file to open the plug-in
-editor and select the <strong>plugin.xml</strong> tab.</p>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;?eclipse version=&quot;3.2&quot;?&gt;
-&lt;plugin&gt;
-	&lt;extension point=&quot;org.eclipse.ui.views&quot;&gt;
-		&lt;category
-			name=&quot;Hello Category&quot;
-			id=&quot;com.example.helloworld&quot;&gt;
-		&lt;/category&gt;
-		&lt;view
-			name=&quot;Hello View&quot;
-			icon=&quot;icons/sample.gif&quot;
-			category=&quot;com.example.helloworld&quot;
-			class=&quot;com.example.helloworld.views.HelloWorldView&quot;
-			id=&quot;com.example.helloworld.views.HelloWorldView&quot;&gt;
-		&lt;/view&gt;
-	&lt;/extension&gt;
-&lt;/plugin&gt;
-</pre>
-<p>
-The information about the view that we provided when we created the plug-in project was used to generate
-an entry in the plugin.xml file that defines our view extension.  In the extension definition,
-we define a <b>category</b> for the view, including its <b>name</b> and <b>id</b>.  We then define the view 
-itself, including its <b>name</b> and <b>id</b>, and we associate it with the <b>category</b> using the id we
-defined for our category.  We also specify the <b>class</b> that implements our view, <b>HelloWorldView</b>. 
-</p>
-<p>
-As you can see, the plug-in manifest file wraps up all the information about our extension and how to run it into
-a nice, neat package.
-</p>
-<p>The other manifest file that is generated by the PDE is the OSGi manifest, MANIFEST.MF.  This file is created
-in the META-INF directory of the plug-in project, but is most easily viewed by clicking on the
-<strong>MANIFEST.MF</strong> tab of the plug-in editor.  The OSGi manifest describes lower-level information
-about the packaging of the plug-in, using the OSGi bundle terminology.  It contains information such as
-the name of the plug-in (bundle) and the bundles that it requires.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm
deleted file mode 100644
index a5503a3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_minimal.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-A minimal plug-in
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-A minimal plug-in</H2>
-<P >
-We all know what &quot;Hello World&quot; looks like in plain old Java without using any user interface frameworks or
-other specialized libraries.</P>
-<pre>
-   public class HelloWorld {
-      public static void main(String[] args) {
-         System.out.println(&quot;Hello World&quot;);
-      }
-   }
-</pre>
-<P >
-What happens to this old standard in the context of the Eclipse platform?  Instead of thinking of Hello World as a self-contained program, we recast it as an extension of the platform. Since we want to say hello to the world, we need to figure out how to extend the workbench to include our greeting.</P>
-<P >
-When we get deeper into the platform user interface components, we'll do an exhaustive review of the ways that you can extend and customize the workbench
-UI. For now, let's start with one of the simplest workbench extensions - a view.&nbsp;</P>
-
-<p>You can think of the workbench window as a frame that presents various visual
-parts. These parts fall into two major categories: views and editors.&nbsp; We
-will look at editors later.&nbsp; <b>Views</b>
-provide information about some object that the user is working with in the
-workbench. Views often change their content as the user selects different
-objects in the workbench.</p>
-
-<H3>
-Hello world view</H3>
-<P >
-For our hello world plug-in, we will implement our own view to greet the user with &quot;Hello World.&quot;</P>
-<P >
-The plug-in <b>org.eclipse.ui.workbench</b> defines most of the public interfaces that make up the workbench
-API. These interfaces can be found in the package <b><a href="../reference/api/org/eclipse/ui/package-summary.html"> org.eclipse.ui</a></b>
-and its sub packages.  Many of these interfaces have
-default implementation classes that you can extend to provide simple modifications to the system. In our hello world example, we will extend a workbench view to provide a label that says hello.</P>
-<P >
-The interface of interest is <b><a href="../reference/api/org/eclipse/ui/IViewPart.html">IViewPart</a></b>, which defines the methods that must be implemented to contribute a view to the workbench. The class
-<b><a href="../reference/api/org/eclipse/ui/part/ViewPart.html">ViewPart</a></b> provides a default implementation of this interface. In a nutshell, a view part is responsible for creating the widgets needed to show the view.</P>
-<P > The standard views in the workbench often display some information about 
-  an object that the user has selected or is navigating. Views update their contents 
-  based on actions that occur in the workbench. In our case, we are just saying 
-  hello, so our view implementation will be quite simple.</P>
-<p>
-Before jumping into the code, we need to make sure our environment is set up for plug-in development...
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm
deleted file mode 100644
index 1e36ffe..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_run.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Running the plug-in
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Running the plug-in</H2>
-<P > We have all the pieces needed to run our new plug-in. Now we need to build 
-  the plug-in. If your Eclipse workbench is set up to build automatically, then 
-  your new view class should have compiled as soon as you saved the new content. 
-  If not, then select your new project and choose 
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.ui.project.buildProject)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Project &gt; Build Project</b></a>.
-  
-  The class should compile without error.</p>
-<p>There are two ways to run a plug-in once it has been built.</p>
-<ol>
-<li>The plug-in's manifest files and jar file can be installed in the <strong>eclipse/plugins</strong> directory.  When
-the workbench is restarted, it will find the new plug-in.</li>
-<li>The PDE tool can be used to run another workbench from within your current workbench.  This
-<strong>runtime workbench</strong> is handy for testing new plug-ins immediately as you develop them
-from your workbench.  (For more information about how a runtime workbench works, check the PDE guide.)</li>
-</ol>
-<p>
-For simplicity, we'll run the new plug-in from within the Eclipse workbench. </p>
-<h3>Launching the workbench</h3>
-<p>To launch a runtime workbench, choose
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenRunConfigurations")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Run &gt; Run...</b></a>.
-
-  This dialog will show you all the different kinds of ways you can launch a program. 
-  Choose <strong>Eclipse Application</strong>, click <strong>New</strong> and accept all of the default settings. 
-  This will cause another instance of the Eclipse workbench, the runtime workbench, 
-  to start. </p>
-<h3>Running Hello World</h3>
-<P > So where is our new view? We can see all of the views that have been contributed 
-  by plug-ins using the <b>Window &gt; Show View</b> menu.</P>
-
-<img src="images/perspectivemenu.png" alt="" border="0">
-<P >
-This menu shows us what views are available for the current perspective. You can see all of the views that are contributed to the platform (regardless of perspective) by selecting
-<b>Other...</b>. This will display a list of view categories and the views available under each category. </P>
-<P >
-The workbench creates the full list of views by using the extension registry to
-find all the plug-ins that have provided extensions for the
-<a href="../reference/extension-points/org_eclipse_ui_views.html"><b> org.eclipse.ui.views</b></a> extension point. </P>
-
-<img src="images/showview.png" alt="Show View dialog with Hello entry" border="0">
-<P >
-There we are! The view called &quot;Hello View&quot; has been added to the <b> Show View</b> window underneath our category &quot;Hello Category.&quot; The labels for our category and view were obtained from the extension point configuration markup in the
-<b>plugin.xml</b>. </P>
-<P ><i><b>
-Up to this point, we still have not run our plug-in code!&nbsp; </b></i>The
-declarations we made in the <b>plugin.xml</b> (which can be seen by other plug-ins using the extension registry)
-are enough for the workbench to find out that there is a
-view called &quot;Hello View&quot; available in the &quot;Hello&quot; category. It even knows what class 
-implements the view. But none of our code will be run until we decide to
-show the view.</P>
-<P >
-If we choose the &quot;Hello View&quot; view from the <b> Show View</b> list, the
-workbench will activate our plug-in, instantiate and initialize our view class, and show the
-new view in the workbench along with all of the other views. Now our code is running.&nbsp;</P>
-
-<img src="images/workbenchwithhello.png" alt="Workbench with Hello World view" border="0">
-<P >
-There it is, our first plug-in! We'll cover more specifics about UI classes and extension points later on.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm b/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm
deleted file mode 100644
index 4502c00..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/firstplugin_view.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The Hello World view
-</TITLE>
-
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The Hello World view</H2>
-
-<P >Now that we've created a project, package, and view class for our plug-in, we're ready to study some code.&nbsp; Here is everything you need in
-your <b>HelloWorldView</b>.&nbsp; Copy the contents below into the
-class you created, replacing the auto-generated content.&nbsp;</P>
-<pre>
-   package com.example.helloworld.views;
-
-   import org.eclipse.swt.widgets.Composite;
-   import org.eclipse.swt.widgets.Label;
-   import org.eclipse.swt.SWT;
-   import org.eclipse.ui.part.ViewPart;
-
-   public class HelloWorldView extends ViewPart {
-      Label label;
-      public HelloWorldView() {
-      }
-      public void createPartControl(Composite parent) {
-         label = new Label(parent, SWT.WRAP);
-         label.setText(&quot;Hello World&quot;);
-      }
-      public void setFocus() {
-         // set focus to my widget.  For a label, this doesn't
-         // make much sense, but for more complex sets of widgets
-         // you would decide which one gets the focus.
-      }
-   }
-</pre>
-<P >
-The view part creates the widgets that will represent it in the <b> createPartControl</b> method. In this example, we create an SWT label and set the &quot;Hello World&quot; text into it.  This
-is about the simplest view that can be created.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms.htm
deleted file mode 100644
index 8ec4e7a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-UI Forms
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-UI Forms</H1>
-<p>UI Forms is an optional Rich Client plug-in based on SWT and JFace that 
-provides the support for creating portable web-style user interfaces across all 
-Eclipse UI categories. It provides a few carefully chosen custom widgets, 
-layouts and support classes required to achieve the desired Web look. Being 
-based on SWT, they are inherently portable across all the platforms where SWT is 
-supported.</p>
-<p>UI Forms break the established expectations on which classes of widgets can 
-be expected in Eclipse workbench UI categories (editors, views, wizards, 
-dialogs). An Eclipse form can appear in any and all of them, expanding the 
-possibilities of the UI developers to use the most appropriate concept for the 
-task regardless where they are.</p>
-<p>Eclipse Forms add the following to make web-style user interfaces possible:</p>
-<ul>
-	<li>A concept of a 'form' that is suitable for inclusion in the content 
-	areas such as views and editors 
-	</li>
-	<li>A toolkit that manages colors, hyperlink groups and other aspects of a 
-	form, as well as serve as a factory for a number of SWT controls 
-	</li>
-	<li>A new layout manager that lays out controls similar to HTML table layout 
-	algorithm 
-	</li>
-	<li>A set of custom control designed to fit in the form (hyperlink, image 
-	hyperlink, scrollable composite, section) 
-	</li>
-	<li>A multi-page editor where each page is a form (e.g. PDE manifest 
-	editors)</li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm
deleted file mode 100644
index 7b2dca8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_colors.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Color and font management
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Color and font management</H1>
-<p align="left">When using forms in a non-trivial way, it is important to share 
-as much as possible to conserve resources. For this reason, color management 
-should be separated from the toolkit when there are more than one form to 
-handle.</p>
-<p align="left">Of course, it is possible to create one toolkit per form, but 
-that is too wasteful if there are many forms. Instead:</p>
-<ul>
-	<li>
-	<p align="left">Create one toolkit for all the forms that have the same life 
-	cycle. For example, if creating a multi-page editor, create one toolkit per 
-	editor and dispose it when editor is disposed. All the pages in the editor 
-	should share this toolkit.</p></li>
-	<li>
-	<p align="left">Create one color manager (<code>FormColors</code>) per 
-	plug-in. When creating the toolkit, pass the color manager to the toolkit. 
-	The toolkit will know that the colors are shared and will not dispose them.</p>
-	</li>
-	<li>
-	<p align="left">Use platform support for fonts and if possible, use <code>
-	JFaceResources</code> predefined fonts. Between default, 'banner' and 
-	'header' fonts, you can accomplish a lot. Using many fonts is very confusing 
-	for the user, and if you do manage your own, you must ensure alternatives 
-	across platforms. The JFace fonts are guaranteed to work on all the 
-	platforms Eclipse ships on.</p></li>
-	<li>
-	<p align="left">Dispose the color manager on plug-in shutdown (don't assume 
-	that plug-in shutdown also means platform shutdown - Eclipse runtime can 
-	uninstall your plug-in dynamically while the platform is still running).</p></li>
-	<li>
-	<p align="left">Use form color manager to allocate all the colors needed by 
-	the forms.</p></li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm
deleted file mode 100644
index e904fec..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls.htm
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-UI Forms controls
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-UI Forms controls</H1>
-<p>UI Forms are based on SWT and JFace. Consequently, standard SWT controls are 
-routinely used. However, a few custom controls have been added in order to 
-deliver a rich web-style user interface when combined with the standard SWT 
-control set:</p>
-<ul>
-	<li><a href="forms_controls_form.htm">Form</a></li>
-	<li><a href="forms_controls_link.htm">Hyperlink</a></li>
-	<li>
-	<a href="forms_controls_section.htm">ExpandableComposite and Section</a></li>
-	<li><a href="forms_controls_text.htm">FormText</a></li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm
deleted file mode 100644
index 037f3d8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_form.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Form control
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Form control</H1>
-<p><b>Form</b> is a basic control used to host UI Forms. It provides for setting 
-a title and scrolling the content similar to a Web browser. What makes forms 
-appealing is the fact that the content is an SWT composite that can be used as 
-you would use it in other contexts. For example, consider the following code 
-snippet:</p>
-<blockquote>
-	<pre>public class FormView extends ViewPart {
-	private FormToolkit toolkit;
-	private ScrolledForm form;
-	/**
-	 * The constructor.
-	 */
-	public FormView() {
-	}
-	/**
-	 * This is a callback that will allow us to create the viewer and
-	 * initialize it.
-	 */
-	public void createPartControl(Composite parent) {
-		toolkit = new FormToolkit(parent.getDisplay());
-		form = toolkit.createScrolledForm(parent);
-		form.setText(&quot;Hello, Eclipse Forms&quot;);
-	}
-	/**
-	 * Passing the focus request to the form.
-	 */
-	public void setFocus() {
-		form.setFocus();
-	}
-	/**
-	 * Disposes the toolkit
-	 */
-	public void dispose() {
-		toolkit.dispose();
-		super.dispose();
-	}
-}</pre>
-</blockquote>
-<p>UI Forms manipulate SWT widgets in a number of ways in order to achieve the 
-desired effect. For that reason, controls are typically created using the <code>
-FormToolkit</code>. Normally an instance of a <code>ScrolledForm</code> is 
-created in order to get scrolling. When forms need to be nested, a <code>Form</code> 
-instance provides everything except for scrolling of the form content.</p>
-<p>Form content is rendered below the title. SWT widgets are created in the form 
-using <code>Form.getBody()</code> as a parent.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm
deleted file mode 100644
index 9ca3d0e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_link.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Hyperlink control
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Hyperlink control</H1>
-<p>Hyperlink is a custom widget created to complement the standard SWT widget 
-set when used in the context of UI Forms. Hyperlink is a selectable text control 
-that acts like a Web browser hyperlink:</p>
-<pre>	Hyperlink link = toolkit.createHyperlink(form.getBody(), &quot;Click here.&quot;,
-				SWT.WRAP);
-		link.addHyperlinkListener(new HyperlinkAdapter() {
-			public void linkActivated(HyperlinkEvent e) {
-				System.out.println(&quot;Link activated!&quot;);
-			}
-		});
-		link.setText(&quot;A sample link&quot;);</pre>
-<p>Hyperlinks fire <code>HyperlinkEvent</code> objects when users interact with 
-them. By adding a <code>HyperlinkListener</code>, clients can capture when the 
-mouse enters and exits the link, as well as activates it (either by mouse click 
-or by 'Enter' key).</p>
-<p>Hyperlinks created by the form toolkit are automatically inserted into a <b>
-hyperlink group</b>. <code>HyperlinkGroup</code> manages common hyperlink 
-properties like normal and hover foreground color, underline style etc. for all 
-the links that belong to the group.</p>
-<p>Since many hyperlinks are combined with a small image, UI Forms provide a 
-subclass called <code>ImageHyperlink</code> that add the ability to combine text 
-and image in one clickable control. This class can also be used when a hyperlink 
-image (without text) is needed. If image is not set, <code>ImageHyperlink</code> 
-behaves identically to <code>Hyperlink</code>.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm
deleted file mode 100644
index 93ed252..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_section.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Expandable composite and Section controls
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Expandable composite and Section controls</H1>
-<p><code>ExpandableComposite</code> acts similar to <code>Group</code> control 
-with the ability to collapse a portion of a page a toggle control:</p>
-<div align="left">
-	<pre>	ExpandableComposite ec = toolkit.createExpandableComposite(form.getBody(), 
-					ExpandableComposite.TREE_NODE|
-					ExpandableComposite.CLIENT_INDENT);
-	ec.setText(&quot;Expandable Composite title&quot;);
-	String ctext = &quot;We will now create a somewhat long text so that &quot;+
-	&quot;we can use it as content for the expandable composite. &quot;+
-	&quot;Expandable composite is used to hide or show the text using the &quot;+
-	&quot;toggle control&quot;;
-	Label client = toolkit.createLabel(ec, ctext, SWT.WRAP);
-	ec.setClient(client);
-	ec.addExpansionListener(new ExpansionAdapter() {
-		public void expansionStateChanged(ExpansionEvent e) {
-			form.reflow(true);
-		}
-	});</pre>
-</div>
-<p>The <code>ExpandableComposite</code> control accepts a number of styles that 
-affect its appearance and behavior. Style <code>TREE_NODE</code> will create the 
-toggle control used in a tree widget for expanding and collapsing nodes, while
-<code>TWISTIE</code> will create a triangle-style toggle. Using <code>EXPANDED</code> 
-will create the control in the initial expanded state. If style <code>COMPACT</code> 
-is used, control will report width in the collapsed state enough to fit in the 
-title line only (i.e. when collapsed, it will be as compact horizontally as 
-possible). Finally, <code>CLIENT_INDENT</code> will indent the client to align 
-with the title (otherwise, client will be aligned with the toggle control).</p>
-<p>Expandable composite itself is responsible for rendering the toggle control 
-and the title. The control to expand or collapse is set as a client. Note the 
-requirement that the client is a direct child of the expandable composite.</p>
-<p>Expandable composite fires <code>ExpansionEvent</code> objects when expansion 
-state changes. Adding an expansion listener to the control is needed in order to 
-reflow the form on state change. This is because expansion causes changes in 
-expandable composite size, but the change will not take effect until the next 
-time the parent is laid out (hence we need to force it).</p>
-<p><code>Section</code> is a subclass of the expandable composite that adds 
-additional capabilities. It is typically used to partition a form into a number 
-of sections, each with its own title and optional description. When <code>
-Section.TITLE_BAR</code> or <code>Section.SHORT_TITLE_BAR</code> styles are 
-used, decoration around the title area further enhances the grouping.</p>
-<p>Unlike <code>ExpandableComposite</code>, <code>Section</code> automatically 
-handles reflows on expansion state change. Other interesting uses of the 
-expansion state notification are lazy creation of the Section content that is 
-delayed until the section is expaned.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm
deleted file mode 100644
index 214b2d5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-FormText control
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-FormText control</H1>
-<p align="left">It is possible to achieve highly polished results using images, 
-hyperlinks and text snippets mixed together in a form. However, when the mix of 
-these elements is needed as part of one integral text, it is very hard to do. To 
-remedy the problem, UI Forms offer a rudimentary text control that can do the 
-following:</p>
-<ul>
-	<li>
-	<p align="left">Render plain wrapped text</p></li>
-	<li>
-	<p align="left">Render plain text but convert any segment that starts with
-	<b>http://</b> into a hyperlink on the flyv</p></li>
-	<li>
-	<p align="left">Render text with XML tags</p></li>
-</ul>
-<p align="left">In all the modes, <code>FormText</code> control is capable of 
-rendering either a string or an input stream.</p>
-<h2 align="left">Rendering normal text (label mode)</h2>
-<div align="left">
-	<pre>	FormText rtext = toolkit.createFormText(form.getBody(), true);
-	String data = &quot;Here is some plain text for the text to render.&quot;;
-	rtext.setText(data, false, false);</pre>
-</div>
-<div align="left">
-	<p align="left">Second argument set to <code>false</code> means that we will 
-	treat input text as-is, and the third that we will not try to expand URLs if 
-	found.</p></div>
-<div align="left">
-	<h2>Automatic conversion of URLs into hyperlinks</h2>
-	<p>It is possible to still handle the text as normal but automatically 
-	convert segments with http:// protocol into hyperlinks:</p>
-	<pre>	FormText rtext = toolkit.createFormText(form.getBody(), true);
-	String data = &quot;Here is some plain text for the text to render; &quot;+
-                       &quot;this text is at http://www.eclipse.org web site.&quot;;
-	rtext.setText(data, false, <b>true</b>);</pre>
-	<p align="left">Similar to the <code>Hyperlink</code> control, <code>
-	FormText</code> accepts listeners that implement <code>HyperlinkListener</code>. 
-	These listeners will be notified about events related to the hyperlink 
-	segments within the control.</p></div>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm
deleted file mode 100644
index d6d3244..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_controls_text_markup.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Parsing formatting markup
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Parsing formatting markup</H1>
-<p align="left">The most powerful use of the <code>FormText</code> control is 
-when formatting tags are added to the text. The expected root tag is <code>form</code>. 
-It can have one or more children that can either be <code>&lt;p&gt;</code> or <code>&lt;li&gt;</code>. 
-Either of these can have normal text, text between <code>&lt;b&gt;</code> or <code>
-&lt;span&gt;</code> tags, images, links and <code>SWT</code> controls. Images are 
-declared using <code>&lt;img href=&quot;<i>image key</i>&quot;/&gt;</code> (no content), while 
-links are expressed using <code>&lt;a href=&quot;<i>href</i>&quot;&gt;text&lt;/a&gt;</code>.</p>
-<p align="left">Some of the tags mentioned above have additional attributes. Tag
-<code>&lt;a&gt;</code> can accept <code>nowrap=&quot;true&quot;</code> to block the link from 
-being wrapped into the new line. Tag <code>&lt;p&gt;</code> can have attribute <code>
-vspace=&quot;false&quot;</code> (<code>true</code> by default) that adds additional space 
-between paragraphs. Tag <code>&lt;li&gt;</code> has more attributes:</p>
-<ul>
-	<li>
-	<p align="left"><b>style</b> - can be <code>text</code>, <code>bullet</code> 
-	and <code>image</code> (default is <code>bullet</code>)</p></li>
-	<li>
-	<p align="left"><b>value</b> - not used for <code>bullet</code>; if style is
-	<code>text</code>, the value will be rendered instead in place of a bullet; 
-	if style is <code>image</code>, value represents a key in the image table of 
-	an image to be rendered in place of a bullet</p></li>
-	<li>
-	<p align="left"><b>vspace</b> - the same as for the '<code>p</code>' tag.</p>
-	</li>
-	<li>
-	<p align="left"><b>indent</b> - the number of pixels to indent text</p></li>
-	<li>
-	<p align="left"><b>bindent</b> - the number of pixels to indent the bullet 
-	(this number is independent from 'indent' - be careful not to overlap them)</p>
-	</li>
-</ul>
-<p>Tags that affect appearance of the normal text are <code>&lt;b&gt;</code> (works as 
-expected), and <code>&lt;span&gt;</code>. The later allows you to change font and/or 
-color of the text within the tag. Soft line breaks can be added using
-<code>&lt;br/&gt;</code> tag. The text is parsed as XML, this means that there 
-must be an end tag for each element so you cannot use open <code>&lt;br&gt;</code> 
-as in HTML). The XML entity &amp;amp; is recognized and replaced with &amp;, and it is required that ampersand (&amp;)
-characters which are not part of an entity declaration be represented as &amp;amp;. 
-Numeric entities may also be used in formatted text.</p>
-<p>Since release 3.1, <code>FormText</code> can be used to mix SWT widgets 
-inside text, hyperlinks and images. SWT controls are created as children of
-<code>FormText</code>, which makes <code>FormText</code> a layout manager of a 
-sort, with instruction on where to place the control relative to text embedded 
-directly in the XML.</p>
-<p>One common theme that can be observed is that <code>FormText</code> is not 
-responsible for loading images, fonts, resolving links or colors. This is not a 
-browser and it is much better to separate concerns and simply assign images and 
-colors managed elsewhere. Both links and images simply have '<code>href</code>' 
-attribute to reference them. For links, the value of this attribute will be 
-provided in the hyperlink event when listeners are notified. Images need to be 
-registered with the text control using the matching 'href' key. This way, the 
-control does not need to worry about loading the images - it has them in the 
-hash table and can render them immediately.</p>
-<p>Similar approach has been used for colors and fonts. Colors are already 
-handled by the toolkit, so you can allocate as many as you want using a unique 
-key and RGB values by calling <code>toolkit.getColors().createColor()</code>. 
-What is left is to set all the colors referenced in the '<code>span</code>' tag 
-so that the control will be able to use them during rendering.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm
deleted file mode 100644
index 8c5b490..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_editors.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Multi-page form editors
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Multi-page form editors</H1>
-<p align="left">UI Forms provide a basic support for multi-page editors you can 
-build on.</p>
-<p align="left">You should start building a UI Forms multi-page editor by 
-extending <code>FormEditor</code>:</p>
-<blockquote>
-	<pre>public class SimpleFormEditor extends FormEditor {
-
-	public SimpleFormEditor() {
-	}
-
-	protected FormToolkit createToolkit(Display display) {
-		// Create a toolkit that shares colors between editors.
-		return new FormToolkit(ExamplesPlugin.getDefault().getFormColors(
-				display));
-	}
-
-	protected void addPages() {
-		try {
-		addPage(new FreeFormPage(this));
-		addPage(new SecondPage(this));
-		addPage(new ThirdPage(this));
-		addPage(new MasterDetailsPage(this));
-		addPage(new PageWithSubPages(this));
-		}
-		catch (PartInitException e) {
-			//
-		}
-	}
-
-	public void doSave(IProgressMonitor monitor) {
-	}
-
-	public void doSaveAs() {
-	}
-
-	public boolean isSaveAsAllowed() {
-		return false;
-	}</pre>
-</blockquote>
-<p>A very simple way to get started is to create pages and add them as above. 
-Each page need to implement <code>FormPage</code> and override <code>
-createFormContent(IManagedForm managedForm)</code> method. Obviously there is a 
-managed form already created in the page, and you should create contents in the 
-enclosed form, and also register any form part that needs to be part of the 
-managed life cycle.</p>
-<p>In addition to form pages, you can add one or more text editors as a raw 
-source alternative to the GUI pages. For this, you should call '<code>addPage(IEditorPart, 
-IEditorInput input)</code>' method in the superclass.</p>
-<h2 align="left">Recommended practices for Eclipse Forms multi-page editors</h2>
-<p align="left">There are many ways you can go about writing a form-based 
-multi-page editor. It mostly depends on the type of content you are editing and 
-proficiency of your users. There are two ways you can approach it:</p>
-<ol>
-	<li>
-	<p align="left">If the typical users are using the editor infrequently, raw 
-	source is hard to edit by hand or complex, your users are not very technical 
-	etc., you should make COMPLETE pages that are fully capable of editing every 
-	aspect of the content without the need to turn to the raw source. In this 
-	approach, source page is there only for occasional validation, rather than 
-	for regular work. In that respect, you can get away with a basic text 
-	editor. PDE extension point schema editor falls into this group.</p></li>
-	<li>
-	<p align="left">If your users are more technical, have no problem editing 
-	the file by hand but would appreciate some help from time to time, consider 
-	providing a mixed experience - make a good source editor with all the 
-	add-ons like incremental outline, context assist, syntax highlighting etc. 
-	In turn, add complex value-add functionality in the form pages that are hard 
-	to achieve from source. We have learned from experience that it is very hard 
-	to convince seasoned users to switch from source editing if the value-add is 
-	marginal or debatable. However, function that was only available in GUI 
-	pages and was very high-quality was used readily.</p></li>
-</ol>
-<p align="left">Creating a high quality multi-page editor with mixed GUI and 
-source pages has its challenges. Accepting that users will switch pages 
-frequently requires a good model of the underlying content. The model should be 
-directly tied to the underlying document(s) so that it is in sync both when 
-users type in the text directly and when they change it structurally through the 
-GUI pages (don't forget the indirect changes caused by other workbench actions 
-while the editor is still up).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm
deleted file mode 100644
index 1fca0e0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-UI Forms Layouts
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-UI Forms Layouts</H1>
-<p align="left">UI Forms offer two new layouts over those provided by SWT. These 
-layouts implement the common interface and can be used on any UI SWT composite, 
-but are typically used in conjunction with UI Forms. The purpose of these 
-layouts is to manage form layout in a way that is similar to Web browsers. 
-Controls are laid out with respect to the form width. The goal is to respect 
-form width as much as possible and compensate by growing the form vertically 
-(and employing scroll bars where needed).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm
deleted file mode 100644
index 3455902..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_column.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-ColumnLayout
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-ColumnLayout</H1>
-<p>Another custom layout in UI Forms is a variation of the <code>RowLayout</code>. 
-If we configure <code>RowLayout</code> to place children vertically (in 
-columns), and to make all controls the same with within the column, we would get 
-several columns (depending on the width of controls), but the last column would 
-typically not be completely filled (depending on the number of controls). Again, 
-if placed in a form, we would get all the controls in one column because <code>
-RowLayout</code> cannot do 'vertical' wrapping. If we use <code>GridLayout</code>, 
-we must choose the number of columns up front and live with the choice.</p>
-<p>There are situations in more complex forms where we want the number of 
-columns to be adaptive. In other words, we would like the number to change 
-depending on the width of the form - use more when possible, drop the number 
-down as the width decreases. We would also like to fill the form area more-less 
-equally (with all the columns roughly the same height). All this can be achieved 
-with <code>ColumnLayout</code>.</p>
-<p>Compared to <code>TableWrapLayout</code>, <code>ColumnLayout</code> is much 
-simpler. Hardly any configuration is needed. The only choice you need to make is 
-the range of columns you want to have (default is 1 to 3).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm
deleted file mode 100644
index 4541ac1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_layouts_table.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-TableWrapLayout
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-TableWrapLayout</H1>
-<p align="left">TableWrapLayout is a grid-based layout very similar to SWT's versatile 
- GridLayout. It differs from GridLayout in that it uses a layout algorithm that 
-works more like HTML tables. It tries to respect the provided client area width 
-and grows vertically to compensate. </p>
-<p align="left">There are many similarities between GridLayout and 
-TableWrapLayout. Both organize children in grids. Both have layout data that 
-instructs the layout how to treat each control. Both can accept hints on which 
-control should grab excess space, etc.</p>
-<p align="left">However, they fundamentally differ in the approach to the 
-layout. <code>TableWrapLayout</code> starts with columns. It computes minimal, 
-preferred and maximum widths of each column and uses this information to assign 
-excess space. It also tries to be fair when dividing space across columns so 
-that there is no excess wrapping of some controls.</p>
-<p align="left">It is possible to mix <code>GridLayout</code> and <code>
-TableWrapLayout</code> but the branch where <code>GridLayout</code> is used is 
-the one where wrapping stops. This is quite acceptable if you don't want it to 
-wrap (if the composite contains controls that cannot wrap anyway, like text, 
-buttons, trees etc.). However, you should have an unbroken path of TableWrapLayouts 
-from the form body to each text control that needs to wrap.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm
deleted file mode 100644
index 020c244..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_managed.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Managed forms
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Managed forms</H1>
-<p align="left">Managed forms are wrappers that add life cycle management and 
-notification to form members. Managed form is not a form by itself. It <i>has</i> 
-a form and accepts registration of <code>IFormPart</code> element. For each
-<code>IFormPart</code>, it manages events like dirty state, saving, commit, 
-focus, selection changes etc. In order to reach to the wrapped form widget, call 
-the '<code>getForm()'</code> method.</p>
-<p align="left">There is a similarity between managed forms and JFace viewers - 
-the relationship between a form and a managed form is similar to the one between 
-a <code>Table</code> widget and <code>TableViewer</code> in JFace, for example.</p>
-<p align="left">Not every control on the form needs to be a form part. It is 
-better to group a number of controls and implement <code>IFormPart</code> 
-interface for the group. Section is a natural group and Eclipse Form provides
-<code>SectionPart</code> implementation. It implements the interface and 
-contains a <code>Section</code> instance (either created outside and passed into 
-the constructor, or created in the part itself).</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm b/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm
deleted file mode 100644
index e8cf4d5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/forms_master_details.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Master/Details block
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>
-Master/Details block</H1>
-<p align="left">Master/Details is a pattern used throughout the UI world. It 
-consists of a list or a tree ('master') and a set of properties ('details') 
-driven by the selection in the master. Eclipse Forms provide the implementation 
-of the pattern as a useful building block with the following properties:</p>
-<ul>
-	<li>
-	<p align="left">While details part is created, master part factory method is 
-	abstract and must be implemented by the subclass</p></li>
-	<li>
-	<p align="left">Master and details parts are children of the sash form and 
-	the ratio of the form space allocated for each can be changed by moving the 
-	sash.</p></li>
-	<li>
-	<p align="left">Through the nature of the sash form, master and details 
-	parts can be organized horizontally or vertically in the form.</p></li>
-</ul>
-<p align="left">The idea of master/details block is to create a tree or a table 
-section that fires the selection notification via the managed form. If the 
-details part can handle the selected object, it should switch to the page for it 
-and display properties. When building on top of the provided master/details 
-block, subclasses should:</p>
-<ul>
-	<li>
-	<p align="left">Create the master part (the one that drives the details)</p>
-	</li>
-	<li>
-	<p align="left">Contribute actions to the form tool bar (consumes 
-	upper-right portion of the form in the title area)</p></li>
-	<li>
-	<p align="left">Register details pages, one for each distinct input that can 
-	arrive from the master part</p></li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm b/bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm
deleted file mode 100644
index 7cd44fa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/httpservice.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Http Service and JSP support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Http Service and JSP support</H1>
-<p>
-Equinox provides support for building and running OSGi based web applications both inside RCP and application server environments. In an OSGi web application use
-of the <a href="http://www.osgi.org/javadoc/r4v42/org/osgi/service/http/HttpService.html">OSGi Http Service</a> replaces the use of web.xml deployment file. The Http Service provides a means to register servlets and resources in a manner
-more consistent with the dynamic environment in Eclipse where bundles can come and go. 
-</p>
-<p>
-The platform SDK comes packaged with <b>org.eclipse.equinox.http.jetty</b>, an implementation of the OSGi Http Service that uses Jetty as its underlying servlet container. This implementation allows customization and 
-<a href="../reference/api/org/eclipse/equinox/http/jetty/JettyConfigurator.html">configuration</a> of many of the server settings important for integration.
-</p>
-<p>
-Java Server Pages play a central role in many java server environments, allowing the presentation of dynamic content. On-the-fly compilation of JSPs
-is provided by <b>org.eclipse.equinox.jsp.jasper</b>'s <a href="../reference/api/org/eclipse/equinox/jsp/jasper/JspServlet.html">JSPServlet</a>.
-</p>
-
-<h2>Http Service Extension Points</h2>
-<p>
-In many cases it's easier to use the more declarative style of interaction provided by the extension registry. To support this usage style 
-<b>org.eclipse.equinox.http.registry</b> provides extension points for 
-<a href="../reference/extension-points/org_eclipse_equinox_http_registry_httpcontexts.html">httpcontexts</a>, 
-<a href="../reference/extension-points/org_eclipse_equinox_http_registry_servlets.html">servlets</a>, and 
-<a href="../reference/extension-points/org_eclipse_equinox_http_registry_resources.html">resources</a> that allow the equivalent 
-registration of web resources in the Http Service.
-</p>
-<p>
-A <a href="../reference/api/org/eclipse/equinox/jsp/jasper/registry/JSPFactory.html">JSP Extension Factory</a> class in <b>org.eclipse.equinox.jsp.jasper.registry</b> provides JSP support for use in conjunction with the 
-<a href="../reference/extension-points/org_eclipse_equinox_http_registry_servlets.html">servlets</a> extension point.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/about.png b/bundles/org.eclipse.platform.doc.isv/guide/images/about.png
deleted file mode 100644
index 9394e1e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/about.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png
deleted file mode 100644
index f7cd314..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/actionseteditorretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png
deleted file mode 100644
index 807adf5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsetoutlineretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png
deleted file mode 100644
index dba718b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/actionsets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg
deleted file mode 100644
index 99e4170..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/arch-npi.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png b/bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png
deleted file mode 100644
index c58bfba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/basicIntro.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png b/bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png
deleted file mode 100644
index 10f186c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/browserexample.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png
deleted file mode 100644
index 1213868..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/cheatsheets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png b/bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png
deleted file mode 100644
index 0d03354..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/common_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_global.png b/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_global.png
deleted file mode 100644
index 22a0c06..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_global.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_popup.png b/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_popup.png
deleted file mode 100644
index c4dcba2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_popup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_view_dropdown.png b/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_view_dropdown.png
deleted file mode 100644
index 0f33109..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_view_dropdown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_window.png b/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_window.png
deleted file mode 100644
index 3c63933..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/contributions_window.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png b/bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png
deleted file mode 100644
index 286c5dc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/cvsdecorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png
deleted file mode 100644
index 6861c5d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editorAction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png
deleted file mode 100644
index 3a7203e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editorInputLabel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png
deleted file mode 100644
index a158e8e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editormenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png
deleted file mode 100644
index 1aa96ac..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editoroutlineretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png
deleted file mode 100644
index 617e2d4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editorretargets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png b/bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png
deleted file mode 100644
index 8fb9419..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/editortoolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/efs-newProject.png b/bundles/org.eclipse.platform.doc.isv/guide/images/efs-newProject.png
deleted file mode 100644
index 9741cb6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/efs-newProject.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png b/bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png
deleted file mode 100644
index cd35bc7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/emptyworkbench.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_data.png b/bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_data.png
deleted file mode 100644
index 3fc4d89..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_data.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_prov.png b/bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_prov.png
deleted file mode 100644
index c153f14..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/equinox_secure_storage_prov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png b/bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png
deleted file mode 100644
index 7cbb3cb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/exportwizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png
deleted file mode 100644
index cb42002..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filetypes.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExample.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExample.png
deleted file mode 100644
index a8763ce..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExample.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance1.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance1.png
deleted file mode 100644
index 49e890e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance2.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance2.png
deleted file mode 100644
index 4529844..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance3.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance3.png
deleted file mode 100644
index b49c6cf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filteredResourcesSelectionDialogExampleAdvance3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png
deleted file mode 100644
index 121725f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png b/bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png
deleted file mode 100644
index 55b824c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/filtersselection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png b/bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png
deleted file mode 100644
index 0d56f49..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/firstpluginpde.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png b/bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png
deleted file mode 100644
index c8a0499..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/genericoutliner.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png b/bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png
deleted file mode 100644
index 240c81d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/help_contents.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png b/bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png
deleted file mode 100644
index 3fdc382..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/ignore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png b/bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png
deleted file mode 100644
index 0f2ad15..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/importwizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png b/bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png
deleted file mode 100644
index 0ffe226..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/infopops.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png
deleted file mode 100644
index 96dd532..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacheatsheet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png
deleted file mode 100644
index 1f26da5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentassist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png
deleted file mode 100644
index 1b15289..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontentoutline.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png
deleted file mode 100644
index 36c5eab..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javacontextassist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png
deleted file mode 100644
index 8bf34fa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png
deleted file mode 100644
index ba63198..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorcontextmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png
deleted file mode 100644
index 8a2f8b1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditoroverviewruler.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png
deleted file mode 100644
index 52f78e3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorsquiggly.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png
deleted file mode 100644
index 4939e96..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javaeditorverticalruler.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png
deleted file mode 100644
index 55e7edd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javarulerhover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png b/bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png
deleted file mode 100644
index 158a199..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/javatexthover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png b/bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png
deleted file mode 100644
index d39f662..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/keybindings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg
deleted file mode 100644
index 9b5e2e3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/launch.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png b/bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png
deleted file mode 100644
index 509c2ca..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/launchImage.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png b/bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png
deleted file mode 100644
index 345c706..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/lcd.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png
deleted file mode 100644
index d9854ba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/markerquickfixmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png b/bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png
deleted file mode 100644
index c8d66ac..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/markerresolution.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png b/bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png
deleted file mode 100644
index 9cbe316..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/navigator.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png b/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png
deleted file mode 100644
index e7ab955..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardlist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png
deleted file mode 100644
index e640a9e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/newwizardmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/no_category.png b/bundles/org.eclipse.platform.doc.isv/guide/images/no_category.png
deleted file mode 100644
index 75547cf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/no_category.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png
deleted file mode 100644
index 0321c43..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/perspectivemenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png b/bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png
deleted file mode 100644
index 2d2fb82..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_filters.png b/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_filters.png
deleted file mode 100644
index 9b826ab..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_filters.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_groupByType.png b/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_groupByType.png
deleted file mode 100644
index 425bbeb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_groupByType.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_markerTypeCat.png b/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_markerTypeCat.png
deleted file mode 100644
index e4abb9e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/problems_view_markerTypeCat.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/problemsview_groups.png b/bundles/org.eclipse.platform.doc.isv/guide/images/problemsview_groups.png
deleted file mode 100644
index ae03059..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/problemsview_groups.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png b/bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png
deleted file mode 100644
index abb2883..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/projectset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/quickfix.png b/bundles/org.eclipse.platform.doc.isv/guide/images/quickfix.png
deleted file mode 100644
index c6563ca..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png
deleted file mode 100644
index 633836c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png
deleted file mode 100644
index b21f379..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsetmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png
deleted file mode 100644
index c1dc995..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeactionsettoolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png
deleted file mode 100644
index 97201d3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmedialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png
deleted file mode 100644
index 37ff8b8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkerhelp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png
deleted file mode 100644
index de4baae..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmemarkermenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png
deleted file mode 100644
index 5c66a24..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutliner.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png
deleted file mode 100644
index 8e066b1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoutlinerpopup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png
deleted file mode 100644
index d0202ca..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeoverview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png
deleted file mode 100644
index f0db52d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepopupmenu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png
deleted file mode 100644
index 8251cfa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmepreferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png
deleted file mode 100644
index 91a9773..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeproperties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmetrim.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmetrim.png
deleted file mode 100644
index 0989268..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmetrim.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmetrimxml.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmetrimxml.png
deleted file mode 100644
index c4b3968..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmetrimxml.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png
deleted file mode 100644
index abeb1aa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png
deleted file mode 100644
index cef3257..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewaction.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewcommand.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewcommand.png
deleted file mode 100755
index cef3257..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmeviewcommand.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png b/bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png
deleted file mode 100644
index 61a3b80..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/readmewizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/sample.gif b/bundles/org.eclipse.platform.doc.isv/guide/images/sample.gif
deleted file mode 100644
index 34fb3c9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/sample.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg
deleted file mode 100644
index eb19cab..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/sdk-arch.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/showview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/showview.png
deleted file mode 100644
index 3ccad19..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/showview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png b/bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png
deleted file mode 100644
index 61057ba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/singleclick.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png b/bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png
deleted file mode 100644
index ed401bd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/team-version_controlled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png b/bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png
deleted file mode 100644
index fb9848a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/team_synchronize_example_localhistory_overview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png b/bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png
deleted file mode 100644
index aacf35c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/teamdecorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png b/bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png
deleted file mode 100644
index a27e0e4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/teamintegration.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png b/bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png
deleted file mode 100644
index 38340cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/teamprefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png b/bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png
deleted file mode 100644
index e4f0f3c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/texteditor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png b/bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png
deleted file mode 100644
index bd56b79..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/textencoding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg b/bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg
deleted file mode 100644
index 2af1d89..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/wiz_arch.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png
deleted file mode 100644
index a13d62f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png
deleted file mode 100644
index 55db76f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbench_decomposed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png
deleted file mode 100644
index 88d58f5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchdecorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png
deleted file mode 100644
index 3b20cce..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workbenchwithhello.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png
deleted file mode 100644
index 1a4f7b9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workingSetTypes.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png b/bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png
deleted file mode 100644
index 3a10a0b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/images/workingset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int.htm b/bundles/org.eclipse.platform.doc.isv/guide/int.htm
deleted file mode 100644
index f736d76..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Welcome to Eclipse
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Welcome to Eclipse</H1>
-<p>Welcome to the Eclipse platform!&nbsp;</p>
-<p>The following sections discuss the issues and problems with building
-integrated tool suites, and how the Eclipse tooling platform can help solve
-these problems.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm b/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm
deleted file mode 100644
index fad7457..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int_eclipse.htm
+++ /dev/null

@@ -1,163 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-What is Eclipse?
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-What is Eclipse?</H2>
-<P >
- Eclipse is a platform that has been designed from the ground up for building integrated web and application development tooling. By design, the platform does not provide a great deal of
-end user functionality by itself. The value of the platform is what it encourages: rapid development of integrated features based on a
-<b> plug-in</b> model.</P>
-<P >
-Eclipse provides a common user interface (UI) model for working with tools.&nbsp; It is designed
-to run on multiple operating systems while providing robust integration with
-each underlying OS.&nbsp; Plug-ins can program to the Eclipse portable APIs and
-run unchanged on any of the supported operating systems.&nbsp;</P>
-<P >
-At the core of Eclipse is an architecture for dynamic discovery, loading, and running of plug-ins. The
-platform handles the logistics of finding and running the right code.  The platform UI provides a standard
-user navigation model.&nbsp; Each plug-in can then focus on doing a small number of tasks well. What
-kinds of tasks? Defining, testing, animating, publishing, compiling, debugging,
-diagramming...the
-only limit is your imagination.</P>
-
-<H3>
-Open architecture</H3>
-<P >
-The Eclipse platform defines an open architecture so that each plug-in development team can focus on their 
-area of expertise. Let the repository experts build the back ends and the usability experts build the end 
-user tools. If the platform is designed well, significant new features and levels of integration can be 
-added without impact to other tools.</P>
-<P >
-The Eclipse platform uses the model of a common workbench to integrate the tools from the end user's point of view. Tools that you develop can
-plug into the workbench using well defined hooks called <b>extension points</b>.</P>
-<P >
-The platform itself is built in layers of plug-ins, each one defining extensions to the extension points of 
-lower-level plug-ins, and in turn defining their own extension points for further customization.  This extension 
-model allows plug-in developers to add a variety of function to the basic tooling platform. The artifacts for each 
-tool, such as files and other data, are coordinated by a common platform resource model.</P>
-<P >
-The platform gives the users a common way to work with the tools, and provides integrated management o
-f the resources they create with plug-ins. </P>
-<P >Plug-in developers also gain from this architecture.&nbsp; The platform
-manages the complexity of different runtime environments, such as different
-operating systems or workgroup server environments.&nbsp; Plug-in
-developers can focus on their specific task instead of worrying about these
-integration issues.</P>
-
-
-
-<H3>
-Platform structure</H3>
-<P >
-The Eclipse platform itself is structured as subsystems which are implemented in
-one or more plug-ins.&nbsp; The subsystems are built on top of a small runtime engine.
-The figure below depicts a simplified view.   </P>
-
-<P >
-<img src="images/arch-npi.jpg" alt="Platform runtime base with groups of plug-ins adding function" border="0" > </P>
-
-<P >
-The plug-ins that make up a subsystem define extension points for adding behavior to the
-platform.&nbsp; The following table describes the major runtime components of the platform that
-are implemented as one or more plug-ins. </P>
-
-<table border="1" width="100%">
-  <tr>
-    <td width="29%">
-
-<H4>
-Platform runtime</H4>
-    </td>
-    <td width="71%">Defines the extension point and plug-in model. It dynamically 
-      discovers plug-ins and maintains information about the plug-ins and their extension points 
-      in a platform registry.
-      Plug-ins are started up when required according to user operation of the
-      platform.  The runtime is implemented using the OSGi framework.</td>
-  </tr>
-  <tr>
-    <td width="29%">
-<H4>Resource management (workspace)</H4>
-    </td>
-    <td width="71%">Defines API for creating and managing resources (projects,
-      files, and folders) that are produced by tools and kept in the file system.</td>
-  </tr>
-  <tr>
-    <td width="29%">
-<H4>
-Workbench UI</H4>
-    </td>
-    <td width="71%">Implements the user cockpit for navigating the platform. It defines extension points for adding UI components such as views or menu actions.&nbsp;
-      It supplies additional toolkits (JFace and SWT) for building user
-      interfaces. The UI services are structured so that a subset of the UI plug-ins can be used to build rich client applications that are
-      independent of the resource management and workspace model.  IDE-centric plug-ins define additional function for 
-      navigating and manipulating resources.</td>
-  </tr>
-  <tr>
-    <td width="29%">
-
-
-<H4>
-Help system</H4>
-    </td>
-    <td width="71%">Defines extension points for plug-ins to provide help or
-      other documentation as browsable books.</td>
-  </tr>
-  <tr>
-    <td width="40%">
-
-
-<H4>Team support</H4>
-    </td>
-    <td width="60%">Defines a team programming model for managing and versioning resources.&nbsp;</td>
-  </tr>
-  <tr>
-    <td width="40%">
-
-
-<h4>Debug support</h4>
-    </td>
-    <td width="60%">Defines a language independent debug model and UI classes
-      for building debuggers and launchers.</td>
-  </tr>
-  <tr>
-    <td width="40%">
-  
-<h4>Other utilities</h4>
-    </td>
-    <td width="60%">Other utility plug-ins supply function such as searching and comparing resources, performing builds using XML configuration files,
-    and dynamically updating the platform from a server.</td>
-  </tr>
-</table>
-
-
-
-<H3>
-Out of the box</H3>
-<P >
-Out of the box - or off the web - the basic platform is an integrated development environment (IDE) for anything (and nothing in particular). </P>
-<P >
-<img src="images/emptyworkbench.png" alt="Workbench window" border="0"></P>
-<P >
-It's the plug-ins that determine the ultimate functionality of the platform.&nbsp;
-That's why the Eclipse SDK ships with additional plug-ins to enhance the
-functionality of the SDK.</P>
-<P >
-Your plug-ins can provide support for editing and manipulating additional types of
-resources such as Java files, C programs, Word documents, HTML pages, and JSP files.</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm b/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm
deleted file mode 100644
index cd7d1dd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int_goal.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The holy grail
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The challenge</H2>
-<P >
-What we all want is a level of integration that magically blends separately developed tools into a
-well designed suite.&nbsp; And it should be simple enough that existing tools can be moved to the platform without using a shoehorn or
-a crowbar.</P>
-<P >
-The platform should be open, so that users can select tools from the best source and know that their supplier has a voice in the development of the underlying platform. </P>
-<P >
-It should be simple to understand, yet robust enough to support integration without a lot of extra glue.</P>
-<P >
-It should provide tools that help automate mundane tasks.&nbsp; It should be stable enough
-so that industrial strength tools can build on top of it. And it should be useful enough that the platform developers can use it to build itself.</P>
-<P >
-These are all goals of Eclipse.&nbsp; The remainder of this programming guide
-will help you determine how close Eclipse has come to delivering on these
-ideals.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm b/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm
deleted file mode 100644
index 089bee6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/int_who.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Who needs a platform?</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Who needs a platform?</H2>
-<P >
-On any given day, you can probably find an announcement about a strategic alliance,
-an open architecture, or a commercial API that promises to integrate all your tools, seamlessly move your data among applications, and simplify your programming life.</P>
-<P >
-Down in the trenches, you're trying to apply enough import/export duct tape to let marketing say &quot;suite&quot; with a straight face.</P>
-<P >
-Where is all this integration pressure coming from? Why is everyone trying to integrate their products into suites or build platforms to support open integration? Who needs these platforms?</P>
-
-<H3>
-End users</H3>
-<P >
-Let's face it. End users do not call the support line to say, &quot;What I really need is an open tools platform.&quot;</P>
-<P >
-But they do ask why your product doesn't integrate with their other tools. They ask for features outside of the scope of your application because they can't get their data to a tool that would do the job better. They run into problems importing and exporting between different programs. They wonder why their programs have completely different user interfaces for doing similar tasks. Doesn't it seem obvious that their web site design tool should be integrated with their scripting program?</P>
-<P >
-Your users want the freedom to pick the best tool for the task. They don't want to be constrained because
-your software only integrates with a few other programs. They have a job to do, and it's not managing the flow of files and data between their tools. They're busy solving their own problems. It's your job to make the tools
-work, and even better if you can make them work together.</P>
-
-
-<H3>
-Software developers</H3>
-<P >
-Meanwhile, you are slaving on your tool implementing the next round of critical features, fixing bugs, and shipping releases. The last thing you need is another emergency import feature added to your list.</P>
-<P >
-Wouldn't it be nice if you could just publish enough hooks to make integrating with your tool everyone else's problem?
-Unfortunately, unless you work for one of the giants, you just don't have enough clout to get away with that.
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm b/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm
deleted file mode 100644
index b0979d7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/java_web_start.htm
+++ /dev/null

@@ -1,184 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Deploying eclipse based application with Java Web Start
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Deploying eclipse based application with Java Web Start</h2>
-<p>
-Applications built on Eclipse can be deployed using Java Web Start.</p><p>
-Java Web Start "is an application-deployment technology that gives you the power to launch full-featured 
-applications with a single click from your web browser".</p>
- <p>
-The prerequisites to start eclipse from Java Web Start are:</p>
-<ul>
-<li> The deployed application must be based on Eclipse 3.1 or later; </li>
-<li> All deployed plug-ins must be jar'ed;</li>
-<li> All plug-ins must be signed since the application needs full permission from the client.</li>
-</ul> 
-The following steps describe how to setup a Java Web Start site serving up a feature based RCP application. 
-These steps are for applications based on eclipse 3.3. Instructions on how to achieve the same for eclipse
-3.1 and 3.2 can respectively be found in the 3.1 and 3.2 SDKs.
-
-<h3>Step 1, creating a wrapper feature</h3>
-<ul>
-<li> Create a feature including all the features that are listed in your product definition;</li>
-<li> Ensure that the <tt>org.eclipse.equinox.launcher</tt> plug-in is in the feature or in one of the included feature;</li>
-</ul>
-
-<h3> Step 2, exporting the wrapper feature</h3>
-Note. Before proceeding with this step make sure to have a key store available. Eclipse does not provide any
-facility to create key stores. You can use the <tt>keytool</tt> application that
-comes with the JDK. In addition, ensure that the eclipse you are developing 
-with is running on a Java SDK instead of a JRE. If this constraint is not satisfied, the jar signing will fail.
-
-<ul>
-<li> Select the wrapper feature and do
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.pde.ui.featureExportWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>File &gt; Export &gt; Plug-in Development &gt; Deployable Features</b></a>.
-
-In the wizard, select the wrapper feature, 
-choose the "directory" option to export your JNLP application to, and check the option "package features and 
-plug-ins as individual JAR archives". On the next page of the wizard, fill in the information relative to your key store 
-in the "Signing JAR Archives" section. Then in the "JNLP section", enter the name of the server that will serve up your 
-application and the level of JRE required to start your application. That last value will be used to in the generated JNLP 
-files to fill in the value of <code>&lt;j2se version="1.4+" /&gt; </code>. Click finish.</li>
- 
-<li> Once the export is done you should have the following structure on disk
-<pre>
-site/   <i>(The root of your jnlp site)</i>
-  features/
-    WrapperingFeature_1.0.0.jar
-    WrapperingFeature_1.0.0.jnlp
-    com.xyz.abc_1.0.0.jar
-    com.xyz.abc_1.0.0.jnlp
-    ...
-  plugins/
-    org.eclipse.core.runtime_3.1.0.jar
-    com.foo.baz_1.0.0.jnlp
-    org.eclipse.equinox.launcher_&lt;version&gt;.jar
-    ...
-</pre>
-</li>
-</ul>
-
-<h3>Step 3, creating the main JNLP file</h3>
-<p>A Java Web Start application is described by JNLP files. They replace the <tt>eclipse.exe</tt> and the <tt>config.ini</tt>
-files by some equivalent mechanism. For example, JNLP has its own mechanism to control splash screen, ways
-to pass parameters and define what constitutes the application.</p>
-<p>
-When you did the export, all the simple JNLP files have been created, so you are left with writing
-the main file that will control the application. Because the majority of the main file is common to all 
-applications, it is recommended to start from the following self documented template.</p>
-<p>
-On the site serving up your application, the file must be located at the root.
-Once you will be done editing this file, your application will be ready.</p>
-<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;jnlp 
-    spec="1.0+" 
-    codebase="http://myCompany.org/jnlpServer" 
-    href="mail.jnlp"&gt; &lt;!-- URL to the site containing the jnlp application. It should match the value used on  export. Href, the name of this file --&gt;
-  &lt;information&gt;
-    &lt;!-- user readable name of the application --&gt;
-    &lt;title&gt; Mail Application &lt;/title&gt;  
-    &lt;!-- vendor name --&gt;
-    &lt;vendor&gt;My company&lt;/vendor&gt;
-    &lt;!-- vendor homepage --&gt; 
-    &lt;homepage href="My company website" /&gt; 
-    &lt;!-- product description --&gt;
-    &lt;description&gt;This is a mail client&lt;/description&gt; 
-    &lt;icon kind="splash" href="splash.gif"/&gt;
-  &lt;/information&gt;
- 
-  &lt;!--request all permissions from the application. This does not change--&gt;
-  &lt;security&gt;
-    &lt;all-permissions/&gt;
-  &lt;/security&gt;
- 
-  &lt;!-- The name of the main class to execute. This does not change--&gt;
-  &lt;application-desc main-class="org.eclipse.equinox.launcher.WebStartMain"&gt;
-    &lt;argument&gt;-nosplash&lt;/argument&gt;
-  &lt;/application-desc&gt;
- 
-  &lt;resources&gt;
-    &lt;!-- Reference to the launcher jar. The version segment must be updated to the version being used--&gt;
-    &lt;jar href="plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar"/&gt;
- 
-    &lt;!-- Reference to all the plugins and features constituting the application --&gt;
-    &lt;!-- Here we are referring to the wrapper feature since it transitively refers to all the other plug-ins  necessary --&gt;
-    &lt;extension 
-        name="Wrapper feature"
-        href="features/Wrappering_1.0.0.jnlp"/&gt;
- 
-    &lt;!-- Information usually specified in the config.ini --&gt;
-    &lt;property 
-        name="osgi.instance.area" 
-        value="@user.home/Application Data/mail"/&gt;
-    &lt;property 
-        name="osgi.configuration.area" 
-        value="@user.home/Application Data/mail"/&gt;
-        
-    &lt;!-- The id of the product to run, like found in the overview page of the product editor --&gt;
-    &lt;property 
-        name="eclipse.product" 
-        value="mail.product"/&gt;
-  &lt;/resources&gt;
-
-  &lt;!-- Indicate on a platform basis which JRE to use --&gt; 
-  &lt;resources os="Mac"&gt;
-    &lt;j2se version="1.5+" java-vm-args="-XstartOnFirstThread"/&gt;
-  &lt;/resources&gt;
-  &lt;resources os="Windows"&gt;
-    &lt;j2se version="1.4+"/&gt;
-  &lt;/resources&gt;
-  &lt;resources os="Linux"&gt;
-    &lt;j2se version="1.4+"/&gt;
-  &lt;/resources&gt;
-&lt;/jnlp&gt;
-</pre>
-<p>Tip: once you have created this file, you can store it in the wrapper feature in a folder such that on every export you will get the complete structure.
-This folder needs to be referenced from the <tt>root</tt> property of the build.properties (e.g: <tt>root=&lt;folderContainingMainJNLPFile&gt;/</tt>).
-</p>
-
-<h3>Plug-ins based application</h3>
-<p>Even though your RCP application does not use features, Java Web Start-ing it is possible.</p><p>
-To do so, it is recommended to create a wrapper feature in order to facilitate the creation of the 
-main jnlp file and ease the deployment. This wrapper feature will list all the plug-ins of your application. Once the feature has been updated
-copy the generated JNLP file and modify it to become your main JNLP file.</p>
-
-<h3>Miscellaneous</h3>
-<h4>Java Web Start on linux</h4>
-<p>
-When an eclipse application is started with Web Start on Linux the default windowing system is motif. 
-If you want to run GTK, you need to set the property osgi.ws to &quot;gtk&quot; in the main jnlp file.
-For example you can add:
-</p>
-<pre>
-  &lt;resources os="Linux"&gt;
-        &lt;property name="osgi.ws" value="gtk"/&gt;
-  &lt;/resources&gt;
-</pre>
-<h3>Known limitations</h3>
-<ul>
-<li>Eclipse Update and Java Web Start<br>
-Those two deployment technologies can work together under the following restrictions:
-plug-ins installed by Java Web Start can not be updated by Update and vice-versa. Features and plug-ins installed
-by Java Web Start can't be referred in the prerequisites of features that needs to be installed by Update;</li>
-<li> Request to exit the application with a restart code are ignored;</li>
-<li>On the Mac, you can only use Web Start with Java 1.5 or later.</li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface.htm
deleted file mode 100644
index fbc4e90..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>The JFace UI framework</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>The JFace UI framework</H1>
-<P >
-We've seen that the workbench defines extension points for plug-ins to contribute UI function to the platform. Many of these extension points,
-particularly wizard extensions, are implemented using classes in the
-<b>
-org.eclipse.jface.*</b> packages. What's the distinction? </P>
-<P >
-JFace is a UI toolkit that provides helper classes for developing UI features
-that can be tedious to implement. JFace operates above the level of a raw widget system. It includes classes for handling common 
-UI programming tasks:</P>
-<ul>
-  <li>
-<b><a href="jface_viewers.htm">
-Viewers</a></b> handle the drudgery of populating, sorting, filtering, and updating widgets.</li>
-  <li>
-<b><a href="jface_actions.htm">
-Actions and contributions</a></b> introduce semantics for defining user actions and specifying where to make them available.</li>
-  <li>
-<b><a href="jface_resources.htm">
-Image and font registries</a></b> provide common patterns for handling UI resources.</li>
-  <li>
-<b><a href="dialogs.htm">
-Dialogs and wizards</a></b> define a framework for building complex interactions with the
-user.</li>
-  <li>
-<b><a href="jface_fieldassist.htm">
-Field assist</a></b> provides classes that help guide the user in choosing appropriate content
-for fields in dialogs, wizards, or forms.</li>
-</ul>
-<P >
-JFace frees you up to focus on the implementation of your specific
-plug-in's function, rather than focusing on the underlying widget system or solving problems that are common in almost any UI application. </P>
-
-<h2>
-JFace and the workbench</h2>
-<P >
-Where does JFace end and the workbench begin? Sometimes the lines aren't so obvious. In general, the JFace APIs (from the packages
-<b>org.eclipse.jface.*</b>) are independent of the workbench extension points and APIs. Conceivably, a JFace program could be written without using any workbench code at all.</P>
-<P >
-The workbench makes use of JFace but attempts to reduce dependencies where possible. For example, the workbench part model
-(<a href="../reference/api/org/eclipse/ui/IWorkbenchPart.html"><b>IWorkbenchPart</b></a>)
-is designed to be independent of
-JFace. We saw earlier that views and editors can be implemented using SWT widgets directly without using any JFace classes. The workbench attempts to remain &quot;JFace neutral&quot; wherever possible, allowing programmers to use the parts of JFace they find useful. In practice, the workbench uses JFace for much of its implementation and there are references to JFace types in API definitions. (For example, the JFace interfaces for
-<b><a href="../reference/api/org/eclipse/jface/action/IMenuManager.html">IMenuManager</a></b>,
-<b><a href="../reference/api/org/eclipse/jface/action/IToolBarManager.html">IToolBarManager</a></b>, and
-<b><a href="../reference/api/org/eclipse/jface/action/IStatusLineManager.html"> IStatusLineManager</a></b> show up as types in the workbench
-<b><a href="../reference/api/org/eclipse/ui/IActionBars.html">IActionBar</a></b>
-methods.)</P>
-<p>When using JFace API, it's a good idea to keep in mind the rules of engagement for
-using background threads.  See <a href="swt_threading.htm#workbench_threads">The workbench and threads</a> for more information.
-</p>
-
-<h2>JFace and SWT</h2>
-<P >
-The lines between SWT and JFace are much cleaner. SWT does not depend on any JFace or platform code at all. Many of the SWT examples show how you can build a standalone application. </P>
-<P >
-JFace is designed to provide common application UI function on top of the SWT
-library. JFace does not try to &quot;hide&quot; SWT or replace its function. It provides classes and interfaces that handle many of the common tasks associated with programming a dynamic UI using
-SWT.</P>
-<P >
-The relationship between JFace and SWT is most clearly demonstrated by looking at viewers and their relationship to SWT widgets.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm
deleted file mode 100644
index 22456cf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_actions.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Actions and contributions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Actions and contributions</H2>
-<P >
-The action classes allow you to define user commands independently from their presentation in the UI. This gives you the flexibility to change the presentation of an action in your plug-in without changing the code that actually performs the command once it has been chosen. The contribution classes are used to manage the actual UI items representing the commands. You don't program to the contribution classes, but you will see them in some of the workbench and JFace API.</P>
-
-<H3>
-Actions</H3>
-<P >
-An action (<a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>) represents a command
-that can be triggered by the end user. Actions are typically associated with buttons, menu items, and items in tool bars. </P>
-<P >
-Although actions do not place themselves in the UI, they do have UI oriented properties, such as tool tip text, label text,
-and an image. This allows other classes to construct widgets for the presentation of the action.</P>
-<P >
-When the user triggers the action in the UI, the action's run method is invoked to do the actual work. A common pattern in the run method is to query the workbench selections and manipulate the objects that are selected. Another common pattern is to launch a wizard or dialog when an action is chosen. </P>
-<P >
-You should not directly implement the <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b> IAction</b></a> interface. Instead, you should subclass the
-<b><a href="../reference/api/org/eclipse/jface/action/Action.html"> Action</a></b> class. Browse the subclasses of this class to see many of the common patterns for actions. The code below implements the &quot;About&quot; action. It is one of the simpler actions in the workbench.</P>
-<pre>
-   public void run() {
-      new AboutDialog(workbenchWindow.getShell()).open();
-   }
-</pre>
-<P >
-Earlier we saw the workbench interfaces <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html"> IViewActionDelegate</a></b> and
-<b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>. These interfaces are used when contributing view actions or editor actions to the workbench. The workbench action delegates are initialized with a reference to their associated view or editor. With this knowledge, they can navigate to the workbench page or window, accessing selections or any other information needed to perform the action. </P>
-<P >
-You will implement your own action classes whenever you want to define a command in your plug-in. If you are contributing actions to other views and editors, you will implement action delegates.</P>
-
-
-<H3>
-Contribution items</H3>
-<P >
-A contribution item (<a href="../reference/api/org/eclipse/jface/action/IContributionItem.html"><b>IContributionItem</b></a>) represents the UI portion of an action. More specifically, it represents an item that is contributed to a shared UI resource such as a menu or tool bar.</P>
-<P >
-Contribution items know how to fill a specific SWT widget with the appropriate SWT item that represents the contribution.</P>
-<P >
-You don't have to worry about creating a contribution item when you are
-contributing actions to the workbench UI. This is done on your behalf when the workbench creates UI items for the actions that you have defined.</P>
-
-
-<H3>
-Contribution managers</H3>
-<P >
-A contribution manager (<b><a href="../reference/api/org/eclipse/jface/action/IContributionManager.html">IContributionManager</a></b>) represents a collection of contribution items that will be
-presented in the UI. You can add and insert contribution items using named contribution ids to place the items in the appropriate order. You can also find items by id and remove individual items.</P>
-<P >
-Each implementation of <a href="../reference/api/org/eclipse/jface/action/IContributionManager.html"><b> IContributionManager</b></a> knows how to fill a specific SWT widget with its items. JFace provides contribution managers for
-menus (<b><a href="../reference/api/org/eclipse/jface/action/IMenuManager.html">IMenuManager</a></b>),
-tool bars (<b><a href="../reference/api/org/eclipse/jface/action/IToolBarManager.html">IToolBarManager</a></b>), and status
-lines (<b><a href="../reference/api/org/eclipse/jface/action/IStatusLineManager.html">IStatusLineManager</a></b>).</P>
-<P >
-As a plug-in developer, you do not need to implement these interfaces, but you will see references to some of these managers in API methods.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm
deleted file mode 100644
index 0c31aaa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_fieldassist.htm
+++ /dev/null

@@ -1,249 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Field assist
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Field assist</H2>
-<P >
-Often, a user is expected to provide textual information
-in a simple field such as a text field or combo box.  Although the application
-code that populates these fields is generally much simpler than code that populates a complex
-widget such as a table or tree, these &quot;simple&quot; fields usually place more
-burden on the user.  The user must identify which fields require content, whether a
-field contains valid content, and what choices are expected.  The JFace <b>field assist</b> 
-support provides classes that help guide the user through input tasks.</P>
-<P >The <b><a href="../reference/api/org/eclipse/jface/fieldassist/package-summary.html">org.eclipse.jface.fieldassist</a></b> package 
-provides assistance in two ways.  <b>Control decorations</b> allow you to place
-image decorations adjacent to a control in order to cue the user about the status of a 
-particular field.  <b>Content proposal</b> support allows you to provide a content assist popup that 
-provides content choices for the user.</P>
-<h3>Control decorations</h3>
-<p>A control decoration is a rendered image that can be placed adjacent to a field
-in a window or dialog.  Decorations may be placed adjacent to a control in one of
-six positions (top, center, or bottom to the left or right of the control).  One or 
-more control decorations may be defined for a control.  The
-API for <b><a href="../reference/api/org/eclipse/jface/fieldassist/ControlDecoration.html">
-ControlDecoration</a></b> allows you to hide and show the decoration, assign descriptive
-text to the decoration, and listen to events associated with the decoration.
-</p>
-<h4>Creating a control decoration</h4>
-<p>Creating a control decoration is straightforward.  Clients simply specify the control to
-be decorated and SWT constants describing the position of the decoration relative to the
-control.  Consider this snippet, in
-which an application creates a text control inside one of its dialogs:</p>
-<pre>
-...
-// Create a text field
-Text text = new Text(parent, SWT.BORDER);
-text.setText("some text"); 
-...
-</pre>
-<p>
-A decoration can then be created for the control.
-</p>
-<pre>
-...
-// Create a control decoration for the control.
-ControlDecoration dec = new ControlDecoration(text, SWT.TOP | SWT.LEFT);
-...
-</pre>
-<p>Once the decoration is created, its image and text can be specified.
-</p>
-<pre>
-...
-// Specify the decoration image and description
-Image image = JFaceResources.getImage("myplugin.specialimage");
-dec.setImage(image);
-dec.setDescriptionText("This field is special");
-</pre>
-<p>
-Clients can use the <b>setShowOnlyOnFocus</b> method to specify whether the decoration 
-should be shown only when the control has focus, or whether it should be shown at all times.  
-The <b>setShowHover</b> method allows clients to configure whether the description text is
-shown in a hover when the mouse hovers over the decoration.
-</p>
-<h4>Laying out decorated controls</h4>
-<p>
-When adding decorations to controls that appear inside a dialog or window, you should 
-make sure there is enough space adjacent to the control to render the decoration without
-overlapping other controls.  For example, when using a grid layout in a dialog, there should
-be enough margin space between the cells in the grid so that a decoration can be shown adjacent to
-controls in the cells. 
-</p>
-<pre>
-...
-// Set the layout data to ensure there is enough space for the decoration
-GridData data = new GridData(IDialogConstants.ENTRY_FIELD_WIDTH, SWT.DEFAULT);
-<b>data.horizontalIndent = image.getBounds().width;</b>
-text.setLayoutData(data);
-...
-</pre>
-<p>
-The width of a decoration is simply the width of its image.  However,
-layout can get more complicated if you are using decorations with different widths.
-If this is the case, you can simplify things by first creating field decorations to represent
-all of your control decorations.</p>  
-<h4>Field decorations</h4>
-<p>A <b><a href="../reference/api/org/eclipse/jface/fieldassist/FieldDecoration.html">
-FieldDecoration</a></b> is simply a data object that combines the image and text used to
-show a decoration.  Once created, these field decorations can be registered in the
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/FieldDecorationRegistry.html">
-FieldDecorationRegistry</a></b>.  
-</p>
-<h4>Field decoration registry</h4>
-<p>The field decoration registry allows you to register and access field decorations 
-using a string id.  This provides a convenient way for you to refer to decorations used throughout your
-application.  You may choose to define API that exposes your decoration ids if you wish to
-make them available to other plug-ins.  Note that registering a decoration does not manage
-the life-cycle of the images inside those decorations.  Your application can decide how to manage
-these images.  For example, the JFace image registry may be used to register and manage the
-image's life-cycle.  Alternatively, your application may wish to create the image on demand
-and dispose of it when it is no longer needed.  The javadoc for the registration methods in
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/FieldDecorationRegistry.html">
-FieldDecorationRegistry</a></b> explains the different ways that images can be specified when
-registering a decoration. To determine the margin width needed for decorations, you can use 
-the <b><a href="../reference/api/org/eclipse/jface/fieldassist/FieldDecorationRegistry.html">
-FieldDecorationRegistry</a></b> protocol to access the width of the largest decoration and create
-the necessary indent.
-</p>
-<pre>
-...
-// Set the layout data
-GridData data = new GridData(IDialogConstants.ENTRY_FIELD_WIDTH, SWT.DEFAULT);
-<b>data.horizontalIndent = FieldDecorationRegistry.getDefault().getMaximumDecorationWidth();</b> 
-text.setLayoutData(data);
-...
-</pre>
-<p>Although the field assist support does not dictate how decorations should be used,
-the registry does define standard decorations that can be used by applications to show certain
-states for a field.  For example, the following snippet uses a standard
-decoration for indicating an error in a field:</p>
-<pre>
-...
-// Create a control decoration to indicate an error.
-ControlDecoration dec = new ControlDecoration(text, SWT.TOP | SWT.LEFT);
-FieldDecoration errorFieldIndicator = FieldDecorationRegistry.getDefault().
-   getFieldDecoration(FieldDecorationRegistry.DEC_ERROR);
-dec.setImage(errorFieldIndicator.getImage());
-dec.setDescriptionText(errorFieldIndicator.getDescription());
-...
-</pre>
-<h3>Content proposals</h3>
-<p>In addition to annotating fields with decorations, applications may provide a 
-content proposal assistant that activates a proposal popup for a field.  You may install a
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/ContentProposalAdapter.html">
-ContentProposalAdapter</a></b> on an arbitrary control in order to provide this behavior.
-The following snippet installs a content proposal adapter on a text control.  Note that
-this text control could be a control created directly by the application or one obtained
-from a decorated field.
-</p>
-<pre>
-...
-autoActivationCharacters = new char[] { '#', '(' };
-keyStroke = KeyStroke.getInstance("Ctrl+Space");
-// assume that myTextControl has already been created in some way
-ContentProposalAdapter adapter = new ContentProposalAdapter(
-	myTextControl, new TextContentAdapter(), 
-	new SimpleContentProposalProvider(new String [] {"ProposalOne", "ProposalTwo", "ProposalThree"}),
-	keyStroke, autoActivationCharacters);
-</pre>
-<p>In order to get and set the content of the control when the user chooses a proposal
-in the popup, the adapter must be supplied with an instance of
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/IControlContentAdapter.html">
-IControlContentAdapter</a></b>, which can retrieve and set the contents of a particular
-kind of control.  For text fields, you can use the class
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/TextContentAdapter.html">
-TextContentAdapter</a></b>.  However, you have the flexibility
-to implement <b><a href="../reference/api/org/eclipse/jface/fieldassist/IControlContentAdapter.html">
-IControlContentAdapter</a></b> to use the content proposal adapter with any other kind of control.</p>
-<p>When creating a content proposal adapter, you must also specify an instance of
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/IContentProposalProvider.html">
-IContentProposalProvider</a></b>, from which the proposals themselves are retrieved.
-This provider is responsible for returning an array of content proposals.  The proposals
-themselves are specified as instances of <b><a href="../reference/api/org/eclipse/jface/fieldassist/IContentProposal.html">
-IContentProposal</a></b>, from which the label and content of the proposal can be obtained, in addition
-to other information, such as a detailed description of the proposal.
-</p>
-<p>
-In the example above, the <b><a href="../reference/api/org/eclipse/jface/fieldassist/SimpleContentProposalProvider.html">
-SimpleContentProposalProvider</a></b> is used.  This provider is defined by specifying a simple array of Strings as the
-content proposals.  The simple provider implements the necessary protocol to map each string into
-the expected <b><a href="../reference/api/org/eclipse/jface/fieldassist/IContentProposal.html">
-IContentProposal</a></b>.  The flexibility of <b><a href="../reference/api/org/eclipse/jface/fieldassist/IContentProposalProvider.html">
-IContentProposalProvider</a></b> allows you to implement a proposal provider with advanced features, such as filtering
-the proposals based on the control's content, providing explanatory labels in the popup instead of the actual
-content that will be inserted, and specifying the expected cursor position after a proposal is inserted.
-See the <b>Field Assist Example</b> and search for implementors of 
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/IContentProposalProvider.html">
-IContentProposalProvider</a></b> for advanced usage.
-</p>
-<h4>Configuring a content proposal adapter</h4>
-<p>We've seen that the basic definition for a content proposal adapter includes the control for which the proposals
-are provided, the content adapter used to alter the content of the control, and the proposal provider that defines
-the list of proposals in the popup.  In addition to these basics, there are many ways that the content proposal
-adapter can be configured: </p>
-<ul>
-<li><b>setAutoActivationCharacters</b> allows you to specify an array of characters that
-will automatically trigger the content proposal popup when typed into the control.</li>
-<li><b>setAutoActivationDelay</b> defines the delay in milliseconds
-between the time the user types an autoactivation character and the popup is opened.</li>
-<li><b>setFilterStyle</b> allows you to control whether any automatic filtering of proposals
-is done, based on the keystrokes typed while the popup is active.</li>
-<li><b>setLabelProvider</b> allows you to specify a label provider which will provide an
-image and string for each proposal.</li>
-<li><b>setPopupSize</b> allows you to specify the desired size of the proposal popup
-when it is activated.</li>
-<li><b>setPropagateKeys</b> controls whether keys typed into an open proposal popup
-should also be propagated back to the control.</li>
-<li><b>setProposalAcceptanceStyle</b> allows you to control how an accepted proposal
-affects the content of the control (insertion, replacement, custom implementation).</li>
-<li>the <b>keyStroke</b> parameter in the constructor can be used to activate the
-content proposal popup using an explicit key sequence that does not affect the content of the control.</li>
-</ul>
-<p>The <b>Field Assist Example</b> allows you to configure these various options in the example preferences
-and try out the different combinations.  For example, the adapter can be configured so that
-it is invoked explicitly with a keystroke and inserts the proposal content into the
-control, causing it to behave much like the text editor content assist.  
-See the javadoc for more specifics about each of these methods and how they interact with each other.
-</p>
-<h4>Auto complete fields</h4>
-<p>The content proposal adapter methods can be used to configure an adapter so that it behaves
-more like the type-ahead field completion used in web browser URL or search fields.  
-<b><a href="../reference/api/org/eclipse/jface/fieldassist/AutoCompleteField.html">
-AutoCompleteField</a></b> can be used when this style of interaction is desired.  Clients need
-only specify the list of completions when defining an auto complete field.  Configuration
-of the content proposal adapter and proposal provider will be handled internally.</p>
-<h3>Workbench field assist</h3>
-<p>Field assist support at the JFace level gives your application a lot of flexibility in determining
-how to decorate fields and show proposals for field content.  This is desirable for stand-alone
-JFace applications or stand-alone rich client applications.  However, if your application is intended to integrate
-with other plug-ins, such as the Eclipse SDK or third-party plug-ins, you will probably want to
-use the field assist support in a way that is consistent with other plug-ins.  The workbench 
-defines utility classes that use field assist for specific kinds of interactions.  </p>
-<p>For example,
-the class <b><a href="../reference/api/org/eclipse/ui/fieldassist/ContentAssistCommandAdapter.html">
-ContentAssistCommandAdapter</a></b> configures a content proposal adapter for
-content-assist style insertion.  It provides a handler for the workbench-level content assist
-command, so that the content proposal popup is opened when the user invokes the keystroke or 
-trigger sequence that has been specified in the workbench key bindings.  It can optionally
-provide a control decoration with the content assist light bulb image.  See the 
-<b><a href="../reference/api/org/eclipse/ui/fieldassist/package-summary.html">org.eclipse.ui.fieldassist</a></b> package 
-for more detail about workbench-level field assist.
-</p>
-<p>This package is expected to evolve as the workbench expands its use of field assist and
-standardizes the use of decorations for certain field states.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm
deleted file mode 100644
index 677f3ba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_operations.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Long-running operations</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="#ffffff">
-<h2>
-Long-running operations</h2>
-<p>
-The <b><a
- href="../reference/api/org/eclipse/jface/operation/package-summary.html">
-org.eclipse.jface.operations</a></b> package defines interfaces for
-long-running operations that require progress indicators or allow user
-cancellation of the operation.  These interfaces are used in the implementation
-of the workbench progress dialogs and views.</p>
-<p>In general, plug-ins should use the workbench support provided in 
-<a href="../reference/api/org/eclipse/ui/progress/IProgressService.html"><b>IProgressService</b></a>
-for running long operations, so that all plug-ins will have a consistent presentation
-of progress.  See <a href="workbench_jobs.htm">Workbench Concurrency Support</a> for
-a complete discussion of the available support for progress dialogs and views.  The remainder
-of this discussion highlights the details of the JFace operations infrastructure which is
-used by the workbench.</p>
-<h3>Runnables and progress</h3>
-<p>
-The platform runtime defines a common interface, <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>,
-which is used to report progress to the user while long running
-operations are in progress. The client can provide a monitor as a
-parameter in many platform API methods when it is important to show
-progress to the user.</p>
-<p>JFace defines more specific interfaces for objects that implement
-the user interface for a progress monitor.&nbsp;</p>
-<p>
-<b><a
- href="../reference/api/org/eclipse/jface/operation/IRunnableWithProgress.html">
-IRunnableWithProgress</a></b> is the interface for a long-running
-operation.&nbsp; The <b>run</b>
-method for this interface has an <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a>
-</b>parameter that is used to report progress and check for user
-cancelation.</p>
-<p><a
- href="../reference/api/org/eclipse/jface/operation/IRunnableContext.html"><b>IRunnableContext</b></a>
-is the interface for the different places in the UI where progress can
-be
-reported.&nbsp; Classes that implement this interface may choose to use
-different techniques for showing progress and running the
-operation.&nbsp;
-For example, <b><a
- href="../reference/api/org/eclipse/jface/dialogs/ProgressMonitorDialog.html">ProgressMonitorDialog</a></b>
-implements this interface by showing a progress dialog.&nbsp; <b><a
- href="../reference/api/org/eclipse/ui/IWorkbenchWindow.html">IWorkbenchWindow</a></b>
-implements this interface by showing progress in the workbench window's
-status
-line.&nbsp; <a
- href="../reference/api/org/eclipse/jface/wizard/WizardDialog.html"><b>WizardDialog</b></a>
-implements this interface to show long running operations inside the wizard status line.</p>
-
-<blockquote><i>Note:&nbsp; The workbench UI provides additional support for operations in <b><a
-href="../reference/api/org/eclipse/ui/actions/WorkspaceModifyOperation.html">WorkspaceModifyOperation</a></b>.
-This class simplifies the implementation of long-running operations that modify the workspace. It maps between <a
-href="../reference/api/org/eclipse/jface/operation/IRunnableWithProgress.html"><b>IRunnableWithProgress</b></a>
-and <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html"><b>IWorkspaceRunnable</b></a>.&nbsp;
-See the javadoc for further detail.</i></blockquote>
-
-<h3>Modal operations</h3>
-<p>
-The <b><a
- href="../reference/api/org/eclipse/jface/operation/ModalContext.html">
-ModalContext</a></b> class is provided to run an operation that is
-modal from the client code's perspective.
-It is used inside the different implementations of <a
- href="../reference/api/org/eclipse/jface/operation/IRunnableContext.html"><b>IRunnableContext</b></a>.&nbsp;
-If your plug-in needs to wait on the completion of a long-running
-operation before continuing
-execution, <b><a
- href="../reference/api/org/eclipse/jface/operation/ModalContext.html">ModalContext</a></b>
-can be used to accomplish this while still keeping the user interface
-responsive.</p>
-<p>
-When you run an operation in a modal context, you can choose to fork
-the operation in a different thread. If
-<b>fork</b> is false, the operation will be run in the
-calling thread.&nbsp; If <b>fork</b> is true,&nbsp; the
-operation will be run in a new thread, the calling thread will be
-blocked, and
-the UI event loop will be run until the operation
-terminates.&nbsp;&nbsp;</p>
-<p>
-For more information on the UI event loop, see <a class="XRef"
- href="swt_threading.htm"> Threading issues for clients</a>.<br>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm
deleted file mode 100644
index ffca695..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_resources.htm
+++ /dev/null

@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-User interface resources
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-User interface resources</H2>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/resource/package-summary.html"> org.eclipse.jface.resource</a></b> package defines classes that help plug-ins manage UI resources such as fonts and icons.</P>
-<P >
-Many of the workbench extension points allow plug-ins to supply icons that can be used to show their contributions in the workbench. Since GUI operating systems support a limited number of images or fonts in memory at once, a plug-in's UI resources must be carefully managed and sometimes shared between widgets.</P>
-<P >
-We've already seen several references to icons in the readme tool plug-in. Some of its icons are specified in the
-<b> plugin.xml</b> markup.</P>
-<pre>&lt;extension
-   point=&quot;org.eclipse.ui.views&quot;&gt;
-	&lt;category
-	   id=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   name=&quot;%Views.category&quot;&gt;
-	&lt;/category&gt;
-	&lt;view
-	   id=&quot;org.eclipse.ui.examples.readmetool.views.SectionsView&quot;
-	   name=&quot;%Views.ReadmeSections&quot;
-	   <b>icon</b>=&quot;icons/view16/sections.png&quot;
-	   category=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeSectionsView&quot;&gt;
-	&lt;/view&gt;
-&lt;/extension&gt;</pre>
-<P >
-We've also seen code that describes images on the fly. The following is from the readme tool's
-<b>ReadmeEditorActionBarContributor</b>.</P>
-<pre>public ReadmeEditorActionBarContributor() {
-      	...
-	action1 = new EditorAction(MessageUtil.getString(&quot;Editor_Action1&quot;));
-	action1.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action1&quot;));
-<b>	action1.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_DISABLE);
-	action1.setImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_ENABLE);
-</b>	...
-</pre>
-<P >JFace provides the basic support classes that allow plug-ins to manage their icons and fonts without worrying about when the corresponding platform graphics objects
-are created and destroyed. These support classes are used directly by plug-ins as shown above, or indirectly when the workbench uses these classes to obtain images that are described in extension point markup.</P>
-
-<H3>
-Image descriptors and the registry</H3>
-<P >
-The SWT <b><a href="../reference/api/org/eclipse/swt/graphics/Image.html">Image</a></b> class represents an image from the operating system's perspective. Because most GUI operating systems have a limit on the number of images that can be open at once, plug-ins should be very careful when creating them,
-and ensure that they also dispose of them properly when finished using them. By using the JFace
-<b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptor</a></b> and
-<b><a href="../reference/api/org/eclipse/jface/resource/ImageRegistry.html"> ImageRegistry</a></b> classes instead of the SWT image, plug-ins can generally avoid creating, managing, and disposing these images directly.</P>
-
-<H4>
-Image descriptor</H4>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptor</a></b> class can be used as a lightweight description of an image. It specifies everything that is needed to create an image, such as the
-URL or filename where the image can be obtained.
-<b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptors</a></b> do not allocate an actual platform image unless specifically requested using the
-<b> createImage()</b> method. </P>
-<P >
-Image descriptors are the best strategy when your code is structured such that it defines all the icons in one place and allocates them as they are needed. Image descriptors can be created at any time without concern for OS resources, making it convenient to create them all in initialization code. </P>
-
-
-<H4>
-Image registry</H4>
-<P >
-The <a href="../reference/api/org/eclipse/jface/resource/ImageRegistry.html"><b> ImageRegistry</b></a> class is used to keep a list of named images. Clients can add image descriptors or SWT images directly to the list. When an image is requested by name from the registry, the registry will return the image if it has been created, or create one from the descriptor. This allows clients of the registry to share images.</P>
-<P >
-Images that are added to or retrieved from the registry must not be disposed by any client. The registry is responsible for disposing of the image since the images are shared by multiple clients. The registry will dispose of the images when the platform GUI system shuts down.</P>
-
-
-
-<H3>
-<a name="jface_resources_patterns">
-Plug-in patterns for using images</a></H3>
-
-<H4>
-Specifying the image in the plugin.xml</H4>
-<P >
-Where possible, specify the icon for your plug-in's UI objects in the <b> plugin.xml</b> file. Many of the workbench extension points include configuration parameters for an icon file. By defining your icons in your extension contribution in the plugin.xml, you leave the image management strategy up the platform. Since the icons are typically kept in your plug-in's directory, this allows you to specify the icons and manage the files all in one place.</P>
-<P >
-The other patterns should only be considered when you can't specify the icon as part of your extension contribution.</P>
-
-
-<H4>
-Explicit creation</H4>
-<P >
-Explicitly creating an image is the best strategy when the image is infrequently used and not shared. The image can be created directly in SWT and disposed after it is used.</P>
-<P >
-Images can also be created explicitly using an <b><a href="../reference/api/org/eclipse/jface/resource/ImageDescriptor.html"> ImageDescriptor</a></b> and invoking the
-<b> createImage()</b> method. As in the first case, the dispose() method for the image must be invoked after the image is
-no longer needed.&nbsp; For example, if a dialog creates an image when it is
-opened, it should dispose the image when it is closed.</P>
-
-
-<H4>
-Image registry</H4>
-<P >
-When an image is used frequently in a plug-in and shared across many different objects in the UI, it is useful to register the image descriptor with an
-<a href="../reference/api/org/eclipse/jface/resource/ImageRegistry.html"><b>ImageRegistry</b></a>. The images in the registry will be shared with any object that queries an image by the same name. You must not dispose any images in the registry since they are shared by other objects.</P>
-<P >
-Adding an image to the image registry is the best strategy when the image is used frequently, perhaps through the lifetime of the plug-in, and is shared by many objects. The disadvantage of using the registry is that images in the registry are not disposed until the
-GUI system shuts down. Since there is a limit on the number of platform (SWT) images that can be open at one time, plug-ins should be careful not to register too many icons in a registry.</P>
-<P >
-The class <b><a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"> AbstractUIPlugin</a></b> includes protocol for creating a plug-in wide image registry.</P>
-
-
-<H4>
-Label providers</H4>
-<P >
-When an icon is used frequently to display items in a particular viewer, it can be shared among similar items in the viewer using a label provider. Since a label provider is responsible for returning an image for any
-object in a viewer, it can control the creation of the image and any sharing of images across objects in the viewer. </P>
-<P >
-The label provider can use any of the previously discussed techniques to produce an image. If you browse the various implementations of
-<b> getImage()</b> in the <b><a href="../reference/api/org/eclipse/jface/viewers/LabelProvider.html"> LabelProvider</a></b> subclasses, you will see a variety of approaches including caching a single icon for objects and maintaining a table of images by type.&nbsp;
-Images created by a label provider must be disposed in the provider's <b>dispose()
-</b>method, which is called when the viewer is disposed.</P>
-<P >
-Using a label provider is a good compromise between explicit creation and the image registry. It promotes sharing of icons like the image registry, yet still maintains control over the creation and disposal of the actual image.</P>
-
-
-<H4>
-Plug-in wide image class</H4>
-<P >
-When fine-tuning a plug-in, it is common to experiment with all of these different image creation patterns. It
-can be useful to isolate the decision making regarding image creation in a separate class and instruct all clients to use the class to obtain all images. This way, the creation sequence can be tuned to reflect the actual performance characteristics of the plug-in.&nbsp;</P>
-
-<H3> ResourceManager</H3>
-<P > The <a href="../reference/api/org/eclipse/jface/resource/ResourceManager.html"><b> 
-  ResourceManager</b></a> class is used to keep a mapping of ImageDescriptors 
-  to Images so that an Image can be reused be referring to it via it's descriptor.When 
-  an image is requested by descriptor from the registry, the registry will return 
-  the image if it has been created, or create one from the descriptor. This allows 
-  clients of the registry to share images. </P>
-<P >The top level ResourceManager is a <a href="../reference/api/org/eclipse/jface/resource/DeviceResourceManager.html"><strong>DeviceResourceManager</strong></a> 
-  which is created on a Display. The ResourceManager defined by <strong><a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html">JFaceResources</a></strong>.<strong>getResources() 
-  </strong>is a DeviceResourceManager and can be used as the top level ResourceManager. 
-  If you need a ResourceManager with a shorter lifecycle than the DeviceResourceManager 
-  you can create a <strong><a href="../reference/api/org/eclipse/jface/resource/LocalResourceManager.html">LocalResourceManager</a></strong> 
-  as a child and dispose of it when you are done with it.</P>
-<P >A DeviceResourceManager will be disposed when the Display used to create it 
-  is disposed so no special management code is required.</P>
-<P > Images that are added to or retrieved from the manager must not be disposed 
-  by any client. The manager is responsible for disposing of the image since the 
-  images are shared by multiple clients. The registry will dispose of the images 
-  when the ResourceManager that holds onto them is disposed.</P>
-<H3> Font registry</H3>
-<P >
-Fonts are another limited resource in platform operating systems. The creation and disposal issues are the same for fonts as
-for images, requiring similar speed/space tradeoffs. In general, fonts are allocated in SWT by requesting a font with a platform dependent font name.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/resource/FontRegistry.html"> FontRegistry</a></b> class keeps a table of fonts by their name. It manages the allocation and disposal of the font.</P>
-<P >
-In general, plug-ins should avoid allocating any fonts or describing fonts with platform specific names. Although the font registry is used internally in JFace, it is typically not used by plug-ins. The
-<b><a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"> JFaceResources</a></b> class should be used to access common fonts.</P>
-<P >It is very common to allow users to specify their preferences for the
-application's fonts in a preference page.&nbsp; In these cases, the
-<b><a href="../reference/api/org/eclipse/jface/preference/FontFieldEditor.html"> FontFieldEditor</a></b> should be used to obtain the font name from the user, and a
-<b><a href="../reference/api/org/eclipse/jface/resource/FontRegistry.html"> FontRegistry</a></b> may be used to keep the font.&nbsp;
-The
-<b><a href="../reference/api/org/eclipse/jface/preference/FontFieldEditor.html"> FontFieldEditor</a></b>
-is only used in preference pages.</P>
-
-
-<H3>
-JFaceResources</H3>
-<P >
-The class <a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"><b> JFaceResources</b></a> controls access to common platform fonts and images. It maintains an internal font and image registry so that clients can share named fonts and images.</P>
-<P >
-There are many techniques used in the workbench and other plug-ins to share images where required. The
-<a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"><b> JFaceResources</b></a> image registry is not widely used across the workbench and plug-in code.</P>
-<P >
-Use of fonts is much simpler. The workbench and most plug-ins use the <a href="../reference/api/org/eclipse/jface/resource/JFaceResources.html"><b> JFaceResources</b></a> class to request fonts by logical name. Methods such as
-<b> getDialogFont() </b> and <b> getDefaultFont()</b> are provided so that plug-ins can use the expected fonts in their UI.</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm b/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm
deleted file mode 100644
index 4f81295..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/jface_viewers.htm
+++ /dev/null

@@ -1,219 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Viewers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Viewers</H2>
-<P >
-Why would you ever want to use a viewer when we have already seen that workbench
-UI contributions like views, editors, wizards, and dialogs can be implemented
-directly with SWT widgets?&nbsp;&nbsp;</P>
-<P >Viewers allow you to create widgets while still using your model
-objects.&nbsp; If you use an SWT widget directly, you have to convert your
-objects into the strings and images expected by SWT.&nbsp; Viewers act as
-adapters on SWT widgets, handling the common code for handling widget events
-that you would otherwise have to implement yourself.&nbsp;</P>
-<P > We first saw a viewer in the readme tool's view contribution, inside the
-<b>ReadmeSectionsView</b>.</P>
-<pre>
-   public void createPartControl(Composite parent) {
-      viewer = new ListViewer(parent);
-      ...
-   }
-</pre>
-<blockquote><i>
-Note:&nbsp; Viewers can be used to provide the implementation for both workbench views and editors. The term viewer does not imply that they are only useful for implementing views. For example, the
-<b> TextViewer</b> is used in the implementation in many of the workbench and plug-in editors.</i></blockquote>
-
-<H3>
-Standard viewers</H3>
-<P >JFace provides viewers for most of the non-trivial widgets in SWT. Viewers are most commonly used for
-list, tree, table, and text widgets.&nbsp;</P>
-<P >
-Each viewer has an associated SWT widget. This widget can be created implicitly by supplying the parent
-<b> Composite</b> in a convenience viewer constructor, or explicitly by creating it first and supplying it to the viewer in its constructor.</P>
-<h4 ><a name="listviewer">List-oriented viewers</a></h4>
-<P > Lists, trees, and tables share many common capabilities from a user's point of view, such as population with objects, selection, sorting, and filtering.&nbsp;</P>
-<P >These viewers keep
-a list of domain objects (called <b>elements</b>) and display them in their
-corresponding SWT widget. A list viewer knows how to get a text label from any
-element in the list.&nbsp; It obtains the label from an <a href="../reference/api/org/eclipse/jface/viewers/ILabelProvider.html"><b>ILabelProvider</b></a>
-which can be set on the viewer.&nbsp; List viewers know how to map from the widget callbacks back into the
-world of elements known by the viewer client.</P>
-<P >
-Clients that use a plain SWT widget have to operate
-at the SWT level - where items are strings and events often relate to an index within the list of strings. Viewers provide higher level semantics. Clients are notified of selections and changes to the list
-using the elements they provided to the viewer. The viewer handles all the grunt work for mapping indexes back to
-elements, adjusting for a filtered view of the objects, and re-sorting when necessary.</P>
-<P >
-Filtering and sorting capability is handled by designating a viewer sorter (<a href="../reference/api/org/eclipse/jface/viewers/ViewerSorter.html"><b>ViewerSorter</b></a>)
-and/or viewer filter (<a href="../reference/api/org/eclipse/jface/viewers/ViewerFilter.html"><b>ViewerFilter</b></a>)
-for the viewer. (These can be specified for tree and table viewers in addition to
-list viewers.) The client need only provide a class that can compare or filter the objects in the list. The viewer handles the details of populating the list according to the specified order and
-filter, and maintaining the order and filter as elements are added and removed.</P>
-
-
-<P >
-Viewers are not intended to be extended by clients.&nbsp; To customize a viewer,
-you can configure it with your own content and label providers.</P>
-
-
-<P >A <b><a href="../reference/api/org/eclipse/jface/viewers/ListViewer.html">ListViewer</a></b>
-maps elements in a list to an SWT <b><a href="../reference/api/org/eclipse/swt/widgets/List.html">List</a></b>
-control.</P>
-
-<P >
-A <a href="../reference/api/org/eclipse/jface/viewers/TreeViewer.html"><b> TreeViewer</b></a> displays hierarchical objects in an SWT
-<a href="../reference/api/org/eclipse/swt/widgets/Tree.html"><b> Tree</b></a> widget. It handles the
-details for expanding and collapsing items. There are several different kinds of tree viewers for different SWT tree controls (plain tree, table tree, checkbox tree).</P>
-<P >A <a href="../reference/api/org/eclipse/jface/viewers/TableViewer.html"><b>TableViewer</b></a> 
-  is very similar to a list viewer, but adds the ability to view multiple columns 
-  of information for each element in the table.&nbsp; Table viewers significantly 
-  extend the function of the SWT table widget by introducing the concept of editing 
-  a cell. Special cell editors can be used to allow the user to edit a table cell 
-  using a combo box, dialog, or text widget. The table viewer handles the creation 
-  and placement of these widgets when needed for user editing.&nbsp; This is done 
-  using the <b><a href="../reference/api/org/eclipse/jface/viewers/CellEditor.html">CellEditor</a></b> 
-  classes, such as <b><a href="../reference/api/org/eclipse/jface/viewers/TextCellEditor.html">TextCellEditor</a></b> 
-  and <b><a href="../reference/api/org/eclipse/jface/viewers/CheckboxCellEditor.html">CheckboxCellEditor</a></b>. 
-  A virtual table, only populated when viewed, the table viewer only runs a designated 
-  number of results regardless of what is actually created. The database &quot;lazily&quot; 
-  requests JIT and will only query a predetermined number at a time.</P>
-
-
-<H4>
-Text viewer</H4>
-<P >
- Text widgets have many common semantics such as double click behavior, undo, coloring, and navigating by index or line.&nbsp;
-A <b><a href="../reference/api/org/eclipse/jface/text/TextViewer.html">TextViewer</a></b>
-is an adapter for an SWT <a href="../reference/api/org/eclipse/swt/custom/StyledText.html"><b>StyledText</b></a>
-widget. Text viewers provide a document model to the client and manage the conversion of the document to the styled text information provided by the text widget.</P>
-<P >
-Text viewers are covered in more detail in <a HREF="editors.htm" CLASS="XRef">Workbench
-Editors</a>.</P>
-
-
-
-<H3>
-Viewer architecture</H3>
-<P >
-To understand a viewer, you must become familiar with the relationship between a viewer's input element, its contents, its selection, and the information actually displayed in the widget that it is manipulating.</P>
-
-<H4>
-Input elements</H4>
-<P >
-An <b> input element</b> is the main object that the viewer is displaying (or editing). From the viewer's point of view, an input element can be any object at all. It does not assume any particular interface is implemented by the input element. (We'll see why in a moment when we look at content providers.)</P>
-<P >
-A viewer must be able to handle a change of input element. If a new input element is set into a viewer, it must repopulate its widget according to the new element, and disassociate itself from the previous input element. The semantics
-for registering as a listener on an input element and populating the widget
-based on the element are different for each kind of viewer.</P>
-
-
-<H4>
-Content viewers</H4>
-<P >
-A <b> content viewer</b> is a viewer that has a well defined protocol for obtaining information from its input element. Content viewers use two specialized helper classes, the
-<b><a href="../reference/api/org/eclipse/jface/viewers/IContentProvider.html">IContentProvider</a></b> and
-<b><a href="../reference/api/org/eclipse/jface/viewers/ILabelProvider.html">ILabelProvider</a></b>, to populate their widget and display information about the input element.</P>
-<P >
-<b><a href="../reference/api/org/eclipse/jface/viewers/IContentProvider.html">
-IContentProvider</a></b> provides basic lifecycle protocol for associating a content provider with an input element and handling a change of input element. More specialized content providers are implemented for different kinds of viewers. The most common content provider is
-<b><a href="../reference/api/org/eclipse/jface/viewers/IStructuredContentProvider.html">IStructuredContentProvider</a></b>, which can provide a list of objects given an input element. It is used in list-like viewers, such as lists, tables, or trees. In general, the content provider knows how to map between the input element and the expected viewer content.</P>
-<P >
-<b><a href="../reference/api/org/eclipse/jface/viewers/ILabelProvider.html">
-ILabelProvider</a></b> goes a step further. Given the content of a viewer (derived from the input element and content provider), it can produce the specific UI elements, such as names and icons, that are needed to display the content in the viewer. Label providers can aid in saving icon resources since they can ensure the same instance of the icon is used for all like types in a viewer.</P>
-<blockquote><i>
-Note:&nbsp; Instances of particular content and label providers are not intended to be shared across multiple viewers. Even if all your viewers use the same type of content or label provider, each viewer should be initialized with
-its own instance of the provider class. The provider life cycle protocol is
-designed for a 1-to-1 relationship between a provider and its
-viewer.</i></blockquote>
-<P > Input elements, content providers, and label providers allow viewers to hide 
-  most of the implementation details for populating widgets. Clients of a viewer 
-  need only worry about populating a viewer with the right kind of input and content 
-  provider. The label provider must know how to derive the UI information from 
-  the viewer content.</P>
-<P >A label provider can show more than just text and an image. JFace provides 
-  several classes and interfaces to support extra functionality. 
-  The following classes are supported by the TableViewer, AbstractTreeViewer and 
-  TableTreeViewer. </P>
-<ul>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IColorProvider.html">
-IColorProvider</a></b>. Make your label provider implement this interface
-to set a different foreground or background color for an item.   Unless system colors 
-are used, these colors should be cached to minimize the amount of system resources used.
-Be sure to dispose of any colors you create when your label provider is disposed.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IFontProvider.html">
-IFontProvider</a></b> . Implement this interface in your label provider to set the font of 
-items in the view.  Fonts should also be cached, and disposed when your label provider
-is disposed. <b>Control.getFont()</b> should be called as little as possible because
-it will create a new instance of <b>Font</b> whenever it is called.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/ILabelDecorator.html">
-ILabelDecorator</a></b>  An ILabelDecorator is an object that can take an image or 
-    text and add adornments to it.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/DecoratingLabelProvider.html">
-DecoratingLabelProvider</a></b>  The DecoratingLabelProvider is a compound object 
-    that takes both a label provider and an ILabelDecorator. This allows a label 
-    provider to hook into a decorator mechanism such as the one provided in the 
-    Workbench.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IViewerLabelProvider.html">
-IViewerLabelProvider</a></b>  The IViewerLabelProvider is a label provider that allows 
-    for building of labels by an external object such as a decorator. The DecoratingLabelProvider 
-    is an IViewerLabelProvider.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IDelayedLabelDecorator.html">
-IDelayedLabelDecorator</a></b>  The IDelayedLabelDecorator is an ILabelDecorator 
-    that supports decoration that is delayed (such as an IDecoratorManager that 
-    decorates in a Thread). IDecoratorManagers are IDelayedLabelDecorators. You 
-    can get the Workbench <b><a href="../reference/api/org/eclipse/ui/IDecoratorManager.html">
-IDecoratorManager</a></b> by calling <b><a href="../reference/api/org/eclipse/ui/IWorkbench.html">
-IWorkbench</a>.getDecoratorManager()</b>.</li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IColorDecorator.html">
-IColorDecorator</a></b>  An IColorDecorator is an object that can support decorating 
-    foreground and background colors. </li>
-  <li><b><a href="../reference/api/org/eclipse/jface/viewers/IFontDecorator.html">
-IFontDecorator</a></b>  An IFontDecorator is an object that can support decorating 
-    fonts.</li>
-</ul>
-<P >It is possible to affect the color of items in a view either from within the
-view's label provider, or via a decorator. Generally it is better to use the color and 
-font support in label providers, since decorators affect every view that shows a 
-particular type. If you do use a color or font decorator make sure its values can be 
-set in the Colors and Fonts preference page.</P>
-
-<H3>
-Viewers and the workbench</H3>
-<P >
-The flexibility provided by viewers, content providers, and label providers can be demonstrated by looking at how the workbench uses them.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/ui/model/WorkbenchContentProvider.html"> WorkbenchContentProvider</a></b> is a structured content provider that obtains contents from an input element by asking for its children. The concept of adapters is used again in order to implement generic function. When asked for the list of elements from its input element, the
-<b><a href="../reference/api/org/eclipse/ui/model/WorkbenchContentProvider.html"> WorkbenchContentProvider</a></b> obtains an
-<b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b> for the input element. If an
-<b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b> has been registered for the input element, then the content provider can safely assume that the element can be queried for its
-children.&nbsp; <b><a href="../reference/api/org/eclipse/ui/model/WorkbenchContentProvider.html">WorkbenchContentProvider</a>
-</b>also does the work needed to keep its viewer up to date when the
-workspace changes.&nbsp;</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/ui/model/WorkbenchLabelProvider.html">WorkbenchLabelProvider</a></b>
-is a label provider that obtains an <b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b> from an object in order to find its text and image. The concept of a label provider is particularly helpful for workbench objects because it allows a single label provider to cache images that are commonly used in a viewer. For example, once the
-<b><a href="../reference/api/org/eclipse/ui/model/WorkbenchLabelProvider.html">WorkbenchLabelProvider</a></b> obtains an image to use for an
-<b><a href="../reference/api/org/eclipse/core/resources/IProject.html">IProject</a></b>, it can cache that image and use it for all
-<b><a href="../reference/api/org/eclipse/core/resources/IProject.html"> IProject</a></b> objects shown in the viewer.</P>
-<P > By defining a common adapter, <b><a href="../reference/api/org/eclipse/ui/model/IWorkbenchAdapter.html">IWorkbenchAdapter</a></b>, 
-  and registering it for many of the platform types, we make it possible for these 
-  types to be represented correctly in many of the common viewers and the workbench 
-  views that contain them. </P>
-<P >&nbsp;</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/login_extensions.html b/bundles/org.eclipse.platform.doc.isv/guide/login_extensions.html
deleted file mode 100644
index d0c8979..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/login_extensions.html
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Security: Login based on JAAS</title>
-</head>
-<BODY BGCOLOR="#ffffff">
-
-<h1>Login based on JAAS</h1>
-
-<h2>Overview</h2>
-
-<p>The Java Authentication and Authorization Service (or JAAS) is a login framework available in the Java runtime since version 1.4. It allows developers to write security-agnostic code that allows for pluggable backends for authentication (consider LDAP vs Smartcard vs Operating system, etc). There are several implementations of login backends that ship with the various JREs.</p>
-<p>For more information on JAAS:</p>
-<ul>
-<li><a href="http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/JAASRefGuide.html">http://java.sun.com/j2se/1.4.2/docs/guide/security/jaas/JAASRefGuide.html</a></li>
-</ul>
-
-<h2>Extension-point based contribution</h2>
-<p>JAAS has specific expectations of where the classes that are used to build a LoginContext should be found - typically the extension classloader. In order to get around these limitations and bridge into the Eclipse environment, there are several extension points available for bundles to contribute JAAS artifacts into the system. Specifically, the following artifacts have corresponding extension points in the org.eclipse.equinox.security bundle:</p>
-<ul>
-<li>javax.security.auth.Configuration</li>
-<li>javax.security.auth.spi.LoginModule</li>
-<li>javax.security.auth.callback.CallbackHandler</li>
-</ul>  
-<p>In order to evolve the API but still embrace the model, there is an org.eclipse.equinox.security.auth.ILoginContext interface which maps to the LoginContext class in JAAS. Additional features are available on this interface, but most functionality still speaks in terms of core JAAS artifacts (Subjects, Principals, etc).</p>
-
-<h2>Declarative wiring via LoginContextFactory</h2>
-<p>Another limitation of the JAAS framework is that there is a strong coupling between the backend login Configuration and the CallbackHandler (UI) which will service the login execution. There is an extension to create the mapping from a configuration name to a specific CallbackHandler, and a factory (org.eclipse.equinox.security.auth.LoginContextFactory) which can generate an ILoginContext without knowledge required of specific CallbackHandlers.</p>
-
-<h2>Notifications through ILoginContextListener</h2>
-<p>Another use case which is implemented is the ability to monitor the execution of an applications login lifecycle via an event listener model. This functionality is available through the org.eclipse.equinox.security.auth.ILoginContextListener interface.</p>
-
-<h2>Future work</h2>
-<p><i>Feedback surrounding this functionality is greatly appreciated.</i> Potential future direction involves integrating login into the RCP lifecycle, Jobs framework, etc and using the user context to affect the behaviour of the runtime system (filter, etc).</p> 
-</BODY></HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/network.htm b/bundles/org.eclipse.platform.doc.isv/guide/network.htm
deleted file mode 100644
index 86720c6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/network.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Network support
-</TITLE>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>Network support</H1>
-<p>The networking support provided as part of the Platform includes:</p>
-
-<ul>
-<li>Proxy support provided by the 
-<a href="../reference/api/org/eclipse/core/net/proxy/package-summary.html">org.eclipse.core.net.proxy</a> 
-package of the <em>org.eclipse.core.net</em> plug-in.</li>
-<li>SSH2 support provided by the <em>com.jcraft.jsch</em> plug-in. Clients should make use
-of the API in the <a href="../reference/api/org/eclipse/jsch/core/package-summary.html">org.eclipse.jsch.core</a>
-package to ensure that the settings specified in the preference page are respected.</li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_category_generation.htm b/bundles/org.eclipse.platform.doc.isv/guide/p2_category_generation.htm
deleted file mode 100644
index aebe4d0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_category_generation.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-  <title>Content categorization</title>
-</head>
-<body>
-<h1>Content categorization</h1>
-<p>
-By default, the p2 Install Software Dialog groups all the installable units by category.  If an installable unit is not
-categorized, it will not be displayed in the user interface. 
-</p>
-
-<img src="images/no_category.png">
-
-<p>
-There are currently two supported methods for categorizing content.
-</p>
-<ol>
-<li><a href="#category_def">A category definition file</a></li>
-<li><a href="#p2_inf">A p2.inf file</a></li>
-</ol>
-
-<h2><a name="category_def">Category Definition File</a></h2>
-<p>
-A category definition file is an XML file that describes which categories a feature should be listed in.  
-The category definition file can be edited using the 
-<a href="../../org.eclipse.pde.doc.user/guide/tools/editors/category_editor/definition_page.htm">Category Definition Editor</a>. 
-The category definition can be specified when 
-<a href="../../org.eclipse.pde.doc.user/guide/tools/export_wizards/export_features.htm">exporting a feature</a>, 
-<a href="../../org.eclipse.pde.doc.user/tasks/pde_p2_builds.htm">building using PDE Build</a>, 
-or injected into a repository using the 
-<a href="p2_publisher.html#category_publisher">category publisher</a>.
-</p>
-
-<h2><a name="p2_inf">The p2.inf File</a></h2>
-<p>
-The p2.inf file is a properties file that can be used to customize capabilites, properties, and instructions. Information
-about this provisional file is available in the section 
-<a href="p2_category_generation.htm">Customizing p2 metadata</a>.
-
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_composite_repositories.htm b/bundles/org.eclipse.platform.doc.isv/guide/p2_composite_repositories.htm
deleted file mode 100644
index e2df0f2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_composite_repositories.htm
+++ /dev/null

@@ -1,109 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Composite repositories</title>
-</head>
-<body>
-
-<h1>Composite repositories</h1>
-<p>
-As repositories continually grow in size they become harder to manage. The goal of composite repositories is to make this task easier 
-by allowing site maintainers to have a parent repository which refers to multiple child repositories. Users are then able to reference the parent repository
-and the content of all the child repositories will be transparently available to them. 
-</p>
-
-<h2>How it works</h2>
-<p>
-With the built-in repository types defined by p2, when a user connects to a server, p2 checks to see if there are any files that are recognized. 
-In particular for metadata repositories it searches for a <code>content.xml</code> file or a <code>content.jar</code> and in the case of 
-artifact repositories it looks for an <code>artifacts.xml</code> or <code>artifacts.jar</code> file.
-</p>
-<p>
-So in order to create a composite repository, all one needs to do is create a new &quot;index&quot; file for the metadata and/or artifact
-repository and p2 will recognize that a composite repository has been defined and it will load it and its children. Composite repositories use
-a different index file name to help p2 recognize them as composite repositories.
-</p>
-
-<h2>Sample composite metadata repository</h2>
-
-<p>
-File: <code>compositeContent.xml</code>
-<pre>
-&lt;?xml version='1.0' encoding='UTF-8'?&gt;
-&lt;?compositeMetadataRepository version='1.0.0'?&gt;
-&lt;repository name='&quot;Eclipse Project Test Site&quot;'
-    type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository'
-    version='1.0.0'&gt;
-  &lt;properties size='1'&gt;
-    &lt;property name='p2.timestamp' value='1243822502499'/&gt;
-  &lt;/properties&gt;
-  &lt;children size='2'&gt;
-    &lt;child location='http://example.eclipse.org/childOne'/&gt;
-    &lt;child location='http://example.eclipse.org/childTwo'/&gt;
-  &lt;/children&gt;
-&lt;/repository&gt;
-</pre>
-</p>
-
-<h2>Sample composite artifact repository</h2>
-
-<p>
-File: <code>compositeArtifacts.xml</code>
-
-<pre>
-&lt;?xml version='1.0' encoding='UTF-8'?&gt;
-&lt;?compositeArtifactRepository version='1.0.0'?&gt;
-&lt;repository name='&quot;Eclipse Project Test Site&quot;'
-    type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' 
-    version='1.0.0'&gt;
-  &lt;properties size='1'&gt;
-    &lt;property name='p2.timestamp' value='1243822502440'/&gt;
-  &lt;/properties&gt;
-  &lt;children size='2'&gt;
-    &lt;child location='http://example.eclipse.org/childOne'/&gt;
-    &lt;child location='http://example.eclipse.org/childTwo'/&gt;
-  &lt;/children&gt;
-&lt;/repository&gt;
-</pre>
-</p>
-
-<h2>Composite repositories as part of the build</h2>
-
-<p>
-In order to automate composite repository actions in release engineering builds, Ant tasks have been provided which can be called to create and 
-modify composite repositories. The tasks are defined in the <code>org.eclipse.equinox.p2.repository.tools</code> bundle.
-</p>
-
-<h3>p2.composite.repository</h3>
-<h4>Attributes</h4>
-<ul>
-<li><code>failOnExists</code> - Whether it should fail if the repository already exists. (Default is <i>false</i>)</li>
-<li><code>validate</code> - A comparator-id. Child repositories claiming to contain the same artifact are compared using the given 
-comparator. These are extensions to the <code>org.eclipse.equinox.p2.artifact.repository.artifactComparators</code> extension 
-point. Comparators provided by p2 are:
-<ul>
-      <li><code>org.eclipse.equinox.p2.repository.tools.jar.comparator</code>: Compare jars. Class files are disassembled and compared for equivalence, 
-      properties and manifest files are compared as such, all other files are compared byte-for-byte.</li>
-      <li><code>org.eclipse.equinox.artifact.md5.comparator</code>: Compare the MD5 sums as recorded in the artifact repositories.</li>
-</ul>
-</li> 
-</ul>
-
-<h4>Sub-elements</h4>
-<ul>
-<li><code>add</code> - A nested element containing a list of repositories to add to the composite.</li>
-<li><code>remove</code> - A nested element containing a list repositories to remove from the composite.</li> 
-</ul>
-
-<h4>Examples</h4>
-
-Some example Ant tasks for composite repositories and further explanation can be found on the <a href="p2_repositorytasks.htm">p2 Ant tasks</a> page.
-
-</body>
-</html>
-

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html b/bundles/org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html
deleted file mode 100644
index b64e2a1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_customizing_metadata.html
+++ /dev/null

@@ -1,277 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-  <title>Customizing p2 metadata</title>
-</head>
-<body>
-<h1>Customizing p2 metadata</h1>
-<p>
-<i> Disclaimer: Authoring p2 metadata is new in 3.5 and something we expect to support with better tooling in a future release.
-The support for customizing metadata with a p2.inf file is provisional although we expect to maintain a basic level
-of compatibility for common tasks.</i>
-</p>
-<p>
-On occasion the metadata that is automatically generated by p2 for bundles, features and products 
-does not provide everything required to successfully provision an installable unit.
-For those cases in the 3.5 release p2 supports the use of an advice file (a p2.inf file) that can be used to augment the metadata for an installable unit.
-In this release the p2.inf file will allow an author to customize capabilities, properties, and instructions. 
-In addition support is provided for defining additional installable units that are related to the container IU.
-</p> 
-
-The touchpoint advice file is a <b>java properties</b> file and can be placed: 
-<ul>
-<li>In bundles (META-INF/p2.inf): The instructions are added to the installable unit for the bundle.</li> 
-<li>In features (a p2.inf file co-located with the feature.xml): The instructions are added to the installable unit for the feature group.</li> 
-<li>In products (a p2.inf file co-located with the .product file): The instructions are added to the root installable unit for that product.</li>
-</ul>
-
-<p>
-Version substitution is a common practice and two special version parameters are supported: 
-</p> 
-<ul>
-<li><b>$version$</b> - returns the string form of the containing IU's version</li>
-<li><b>$qualifier$</b> - returns just the string form of the qualifier of the containing IU's version</li> 
-</ul>
-
-<p>One common use for advice files is to allow more fine grained control of the 
-<a href="#categoryGen">generation of categories</a> used by the UI to group installable features</p> 
-
-<hr>
-<h3>Capability Advice</h3>
-<p>Note: Capability advice will "replace" an existing capability of the same type on the IU if the name and namespace match.</p>
-<p>There are three different type of capability advice:</p> 
-<ol>
-<li><b>provides</b> - these are capabilities that an IU will offer to satisfy the needs of other IUs.</li> 
-<li><b>requires</b> - these are the capabilities that an IU requires from other IUs in order to resolve correctly.</li> 
-<li><b>metaRequirements</b> - these are capabilities that the IU puts on the profile that must already be installed before this IU can be installed.</li> 
-</ol>
-
-<pre>
- provides.{#}.namespace = {namespace}
- provides.{#}.name = {name}
- provides.{#}.version = {version} (optional / default: 1.0.0)
- 
- requires.{#}.namespace = {namespace}
- requires.{#}.name = {name}
- requires.{#}.range = {range} (optional / default: 0.0.0)]
- requires.{#}.greedy = {true|false} (optional / default: true)
- requires.{#}.optional = {true|false} (optional / default: false)
- requires.{#}.multiple = {true|false}  (optional / default: false)
- 
- metaRequirements.{#}.namespace = {namespace}
- metaRequirements.{#}.name = {name}
- metaRequirements.{#}.range = {range} (optional / default: 0.0.0)
- metaRequirements.{#}.greedy = {true|false} (optional / default: true)
- metaRequirements.{#}.optional = {true|false} (optional / default: false)
- metaRequirements.{#}.multiple = {true|false}  (optional / default: false)
- </pre>
- 
-Where {#} is an index for the property, {namespace}, and {name} are the associated named strings, {version} and {range} are version and version range strings respectively. 
-<br>
-For example: 
-<pre>
- provides.0.namespace = testNamespace1
- provides.0.name = testName1
- provides.0.version = 1.2.3.$qualifier$
- provides.1.namespace = testNamespace2
- provides.1.name = testName2
- provides.1.version = $version$
- 
- requires.0.namespace = testNamespace1
- requires.0.name = testName1
- requires.0.range = [1.2.3.$qualifier$, 2)
- requires.0.greedy = true
- requires.0.optional = true
- requires.0.multiple = true
- requires.1.namespace = testNamespace2
- requires.1.name = testName2
- requires.1.range = [$version$, $version$]
- requires.1.greedy = false
- 
- metaRequirements.0.namespace = testNamespace1
- metaRequirements.0.name = testName1
- metaRequirements.0.range = [1.2.3, 2)
- metaRequirements.0.greedy = true
- metaRequirements.0.optional = true
- metaRequirements.0.multiple = true
- metaRequirements.1.namespace = testNamespace2
- metaRequirements.1.name = testName2
- metaRequirements.1.range = $version$
- metaRequirements.1.greedy = false
-</pre>
-<hr>
-<h3>Property Advice</h3>
-<pre> 
- properties.{#}.name = {propertyName}
- properties.{#}.value = {propertyValue}
- </pre>
-<p>Where {#} is an index for the property, {propertyName}, and {propertyValue} hold the name and value strings for the property. 
-<br>For example: 
-</p>
-<pre>
- properties.0.name = testName1
- properties.0.value = testValue1
- properties.1.name = testName2
- properties.1.value = testValue2
-</pre>
-<hr>
-<h3>Touchpoint Instruction Advice</h3>
-<pre> 
- instructions.{phase} = {raw actions}
- instructions.{phase}.import = {qualified action name} [,{qualified action name}]* (optional)
-</pre>
-Where {phase} is a p2 installation phase (collect, configure, install, uninstall, unconfigure, etc). 
-
-Note:
-<ul> 
-<li>The {raw actions} will be "appended" to the end of any instructions already being generated.</li> 
-<li>The qualified action names for the IU's touchpoint type are implicitly imported. All other actions need to be imported.</li>
-</ul>
- 
-For example: 
-<pre>
- instructions.install = \
-    ln(targetDir:@artifact,linkTarget:foo/lib.1.so,linkName:lib.so);\
-    chmod(targetDir:@artifact,targetFile:lib/lib.so,permissions:755);
- instructions.install.import= \
-    org.eclipse.equinox.p2.touchpoint.natives.ln,\
-    org.eclipse.equinox.p2.touchpoint.natives.chmod
-</pre>
-Additional information on touchpoint instructions and action syntax can be found <a href="http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instructions_35">here.</a>
-<hr>
-<h3>Additional Installable Unit Advice</h3> 
-<p>In addition to customizing attributes of the containing IU one can also author additional installable units that work 
-with the container IU. Typically this mechanism is used to author an IU fragment that customizes the containing IU or one of its dependencies.</p> 
-
-<pre>
- iu.{#}.id = {identifier} 
- iu.{#}.version = {version} (optional)
- </pre>
-<p>Where {#} is an index for the installable unit, so multiple installable units can be declared. A full range of IU customizations are supported including:</p> 
-
-<pre>
- id
- version
- singleton
- copyright
- licenses
- filter
- touchpoint
- update
- artifacts
- properties
- provides
- requires
- metaRequirements
- hostRequirements
- instructions
- </pre>
-<p>To illustrate all the various settings for these customizations here's a more complete example of: (unit.0) a minimal IU and (unit.1) a full featured IU:</p> 
-
-<pre>
- units.0.id = testid0
- units.0.version = 1.2.3
- units.1.id = testid1
- units.1.version = 1.2.4
- units.1.singleton = true
- units.1.copyright = testCopyright
- units.1.copyright.location = http://localhost/test
- units.1.filter = test=testFilter
- units.1.touchpoint.id = testTouchpointId
- units.1.touchpoint.version = 1.2.5
- units.1.update.id = testid1
- units.1.update.range = (1,2)
- units.1.update.severity = 2
- units.1.update.description = some description
- units.1.artifacts.0.id = testArtifact1
- units.1.artifacts.0.version = 1.2.6
- units.1.artifacts.0.classifier = testClassifier1
- units.1.artifacts.1.id = testArtifact2
- units.1.artifacts.1.version = 1.2.7
- units.1.artifacts.1.classifier = testClassifier2
- units.1.licenses.0 = testLicense
- units.1.licenses.0.location = http://localhost/license
- units.1.properties.0.name = testName1
- units.1.properties.0.value = testValue1
- units.1.properties.1.name = testName2
- units.1.properties.1.value = testValue2
- units.1.requires.0.namespace = testNamespace1
- units.1.requires.0.name = testName1
- units.1.requires.0.range = [1.2.3.$qualifier$, 2)
- units.1.requires.0.greedy = true
- units.1.requires.0.optional = true
- units.1.requires.0.multiple = true
- units.1.requires.1.namespace = testNamespace2
- units.1.requires.1.name = testName2
- units.1.requires.1.range = $version$
- units.1.requires.1.greedy = false
- units.1.requires.1.optional = false
- units.1.metaRequirements.0.namespace = testNamespace1
- units.1.metaRequirements.0.name = testName1
- units.1.metaRequirements.0.range = [1.2.3.$qualifier$, 2)
- units.1.metaRequirements.0.greedy = true
- units.1.metaRequirements.0.optional = true
- units.1.metaRequirements.0.multiple = true
- units.1.metaRequirements.1.namespace = testNamespace2
- units.1.metaRequirements.1.name = testName2
- units.1.metaRequirements.1.range = $version$
- units.1.metaRequirements.1.greedy = false
- units.1.metaRequirements.1.optional = false
- units.1.provides.0.namespace = testNamespace1
- units.1.provides.0.name = testName1
- units.1.provides.0.version = 1.2.3.$qualifier$
- units.1.provides.1.namespace = testNamespace2
- units.1.provides.1.name = testName2
- units.1.provides.1.version = $version$
- units.1.instructions.configure = addProgramArg(programArg:-startup); addProgramArg(programArg:@artifact);
- units.1.instructions.unconfigure = removeProgramArg(programArg:-startup); removeProgramArg(programArg:@artifact);)
- units.1.instructions.unconfigure.import = some.removeProgramArg
- units.1.hostRequirements.0.namespace = testNamespace1
- units.1.hostRequirements.0.name = testName1
- units.1.hostRequirements.0.range = [1.2.3.$qualifier$, 2)
- units.1.hostRequirements.0.greedy = true
- units.1.hostRequirements.0.optional = true
- units.1.hostRequirements.0.multiple = true
-</pre>
-
-<hr>
-
-<a name="categoryGen"></a>
-<h2>Category Generation Using p2.inf</h2>
-
-<p>The p2 UI allows for hierarchical organization of installable units based on the concept of "categories" where the children
-of categories are what's installable. On occasion we might want to take finer grained control of the contents of a category and
-what it contains. For example we might want to support further categorization of a feature's contents to allow individual plug-ins
-to be installed instead of the more typical features.</p>
-
-<p>To support this we can tag a feature as a category as follows:</p>
-<pre>
-  properties.1.name=org.eclipse.equinox.p2.type.category
-  properties.1.value=true
-</pre>
-
-<p>Another possibility is to use "additional IU advice" to create a specialized category IU like this:</p>
-<pre>
-  units.1.id=my.product.category
-  units.1.version=1.0.0
-  units.1.provides.1.namespace=org.eclipse.equinox.p2.iu
-  units.1.provides.1.name=my.product.category
-  units.1.provides.1.version=1.0.0
-  units.1.properties.1.name=org.eclipse.equinox.p2.type.category
-  units.1.properties.1.value=true
-  units.1.properties.2.name=org.eclipse.equinox.p2.name
-  units.1.properties.2.value=My Category Name
-  requires.1.namespace=org.eclipse.equinox.p2.iu
-  requires.1.name=my.product
-  requires.1.range=[1.0.0,1.0.0]
-  requires.1.greedy=true
-</pre>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_director.html b/bundles/org.eclipse.platform.doc.isv/guide/p2_director.html
deleted file mode 100644
index 04f773e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_director.html
+++ /dev/null

@@ -1,171 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-
-<title>Installing software using the p2 director application</title>
-</head>
-<body>
-
-<h1>Installing software using the p2 director application</h1>
-In addition to the "Software Updates" dialog, you can also perform
-provisioning operations from a command line or script. 
-This is achieved using a tool called the director application. The director application 
-is a command line tool for installing additional software or uninstalling
-software from an Eclipse-based product. This application is capable of provisioning a
-complete installation from scratch or simply extending your application.
-Depending on your needs, this application can be executed both inside and
-outside of the target product being provisioned.
-
-<h2>Terminology</h2>
-<ul>
-	<li><b>Director application:</b> the application performing p2
-	operations such as install or uninstall. This application is provided
-	by the org.eclipse.equinox.p2.director.app bundle.</li>
-	<li><b>Provisioning operation:</b> an operation installing,
-	uninstalling features.</li>
-	<li><b>Target product:</b> the installation targeted by the
-	provisioning operation.</li>
-	<li><b>Builder:</b> an eclipse based application containing the
-	director application bundle and its depents.</li>
-</ul>
-<br>
-
-<h2>Running inside the target application</h2>
-<p>In this mode, the provisioning operation happens from within the
-targeted product that you are provisioning. It is equivalent to starting
-up the targeted product and using the p2 UI to perform the equivalent
-operation.</p>
-<p>This means that the target application has to be in a runnable
-state and has to contain the director application bundle. Also, since the
-target product will have run, cache files will have been created in the
-configuration folder (e.g. configuration/org.eclipse.osgi).</p>
-<p>The following example shows the command line used to install CDT
-into the SDK.</p>
-<pre>
-<code>
-  &lt;targetProductFolder&gt;/eclipsec.exe 
-   -application org.eclipse.equinox.p2.director 
-   -repository http://download.eclipse.org/releases/galileo/
-   -installIU org.eclipse.cdt.feature.group/&lt;version&gt;
-</code>
-</pre>
-
-<h2>Provisioning without running the target application</h2>
-<p>In this case the provisioning operation happens "outside" of
-the targeted product. The "targeted product" is *not* started. This
-allows one to both modify an existing installation and create a complete
-installation from scratch given proper metadata.</p>
-
-<p>This also has the advantage that since the targeted product does
-not need to be started, the provisioning operation can be performed on
-any platform for any other platform (e.g. on my linux machine, one can
-add plug-ins to a windows-based target application).</p>
-
-<h3>Installing / uninstalling IUs into a target product</h3>
-<p>To install or uninstall something into an existing target product
-a few extra arguments than for the "inside" mode need to be set. These
-mostly consist in providing the provisioning operation the ID of the
-profile it needs to operate on, and where it is located on disk.</p>
-
-<p>For example, if from a directory called "d:\builder" containing
-the builder, you want to install CDT into an existing SDK located into
-"d:\eclipse", you would use the following command line.</p>
-<pre>
-<code>
-   d:\builder\eclipsec.exe
-   -application org.eclipse.equinox.p2.director
-   -repository http://download.eclipse.org/releases/galileo/
-   -installIU org.eclipse.cdt.feature.group
-   -destination d:/eclipse/
-   -profile SDKProfile</code>
-</pre>
-<p>Note that there is no need to describe the os/ws/arch of the
-platform being targeted because all this information is already 
-available in the profile of the application in which we are
-provisioning.</p>
-
-<h3>Installing a complete product</h3>
-<p>The creation of a complete product using the director application
-only needs a few extra arguments compared to the previous example. Most of these
-consist of values used to initialize the profile in which the
-application will be provisioned.</p>
-
-<p>The following example demonstrates how to create a linux/gtk
-installation of the Eclipse SDK provisioned into a folder called "d:\eclipse" using
-a director application located in "d:\builder".</p>
-
-<pre>
-<code>
-   d:\builder\eclipsec.exe
-   -application org.eclipse.equinox.p2.director
-   -repository http://download.eclipse.org/eclipse/updates/3.5
-   -installIU org.eclipse.sdk.ide
-   -destination d:/eclipse/
-   -profile SDKProfile
-   -profileProperties org.eclipse.update.install.features=true
-   -bundlepool d:/eclipse/
-   -p2.os linux
-   -p2.ws gtk
-   -p2.arch x86
-   -roaming
- </code>
-</pre>
-<p>The -p2.* arguments describe the os/ws/arch that the provisioned
-product is targeting.</p>
-
-<h2>Arguments Description</h2>
-<ul>
-<li><b>-application
-org.eclipse.equinox.p2.director</b>: the application ID.</li>
-<li><b>-metadataRepository</b>: a comma separated list of
-metadata repository URLs where the software to be installed can be
-found.</li>
-<li><b>-artifactRepository</b>: a comma separated list of
-artifact repository URLs where the software artifacts can be found.</li>
-<li><b>-repository</b>: a comma separated list of repository URL where 
-  each entry denotes colocated meta-data and artifact repositories.</li>
-<li><b>-installIU</b>: a comma separated list of IUs to install. Each entry in the list is in the form &lt;id&gt; [ '/' &lt;version&gt; ].
-If you are looking to install a feature, the identifier of
-the feature has to be suffixed with ".feature.group".</li>
-<li><b>-uninstallIU</b>: a comma separated list of IUs to uninstall. Each entry in the list is in the form &lt;id&gt; [ '/' &lt;version&gt; ].</li>
-<li><b>-revert</b>: Revert the installation to a previous state [ the number representing the previous state of the profile  as found in p2/org.eclipse.equinox.p2.engine/&lt;profileId&gt;/ ].</li>
-<li><b>-destination</b>: the path of a folder in which the targeted
-product is located.</li>
-<li><b>-list</b>: lists all IU's found in the given repositories in a property like format. IUs can optionally be listed. Each entry in the list is in the form &lt;id&gt; [ '/' &lt;version&gt; ].</li>
-<li><b>-profile</b>: the profile id containing the
-description of the targeted product. This ID is is defined by the 
-<tt>eclipse.p2.profile</tt> property contained in the config.ini of the targeted
-product. For the Eclipse SDK the ID is "SDKProfile"</li>
-<li><b>-profileProperties</b>: a comma separated list of &lt;key&gt;=&lt;value&gt;
-pair. The property org.eclipse.update.install.features=true will cause
-the update manager features to be installed.</li>
-<li><b>-bundlepool</b>: the location of where the plug-ins and features will be stored. This value is
-only taken into account when a new profile is created. For an
-application where all the bundles are located into the plugins/ folder
-of the destination, set it to &lt;destination&gt;.</li>
-<li><b>-p2.os</b>: the OS to use when the profile is created.
-This will be used to filter which OS specific installable units need to
-be installed.</li>
-<li><b>-p2.ws</b>: the windowing system to use when the
-profile is created. This will be used to filter which WS specific
-installable units need to be installed.</li>
-<li><b>-p2.arch</b>: the architecture to use when the profile
-is created. This will be used to filter which architecture specific
-installable units need to be installed.</li>
-<li><b>-roaming</b>: indicates that the product resulting
-from the installation can be moved. This property only makes sense when
-the destination, bundle pool are in the same location and
-eclipse.p2.data.area is set to destination/p2. This value is only taken
-into account when the profile is created.</li>
-<li><b>-shared</b>: use a shared location for the install. The path defaults to ${user.home}/.p2.</li>
-<li><b>-verifyOnly</b>: only verify that the actions can be performed. Don't actually install or remove anything.</li>
-</ul>
-While doing these operations, you can disable the automatic mirror selection mechanism by setting the VM argument eclipse.p2.mirrors to false.
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_metadata.html b/bundles/org.eclipse.platform.doc.isv/guide/p2_metadata.html
deleted file mode 100644
index 469ab68..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_metadata.html
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-  <title>Metadata management</title>
-</head>
-<body>
-<h1>Metadata management</h1>
-<p>
-As described in the <a href="p2_overview.htm">overview</a>, p2 provides
-facilities for software dependency management, and for performing all of the necessary
-steps to get an application physically installed and configured into an end user's system.
-The information that describes the dependencies between application components, and the steps
-required to properly configure a running system is called the <em>p2 metadata</em>.</p>
-<p>In many cases this metadata can be computed directly from the information in your plug-in
-and feature manifests, and an extra step is simply required to <em>publish</em> this
-data into a format suitable for consumption by p2. In other cases, a plug-in or
-application developer may need to author or customize the p2 metadata for their
-software. The following sections describe in more detail how to author and publish
-p2 metadata for your application or plug-in.
-<ul>
-<li><a href="p2_publisher.html">Publishing metadata</a></li>
-<li><a href="p2_customizing_metadata.html">Customizing metadata</a></li>
-<li><a href="p2_publishingtasks.htm">Ant Tasks for publishing metadata</a></li>
-</ul>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html b/bundles/org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html
deleted file mode 100644
index cdfad80..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_metadata_generator.html
+++ /dev/null

@@ -1,213 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-  <title>Generating p2 metadata</title>
-</head>
-<body>
-<h1>Generating p2 metadata</h1>
-<p>
-<b>As of Eclipse 3.5 the metadata generator is deprecated.  The <a href="p2_publisher.html">publisher</a> should be used instead.</b>
-</p>
-
-<p>
-With the "classic" Update Manager, all metadata for features and bundles is self-contained in the features and 
-bundles themselves. In p2 the metadata contains more information and is stored 
-separately in what are called Installable Units (IUs) and Configuration Units (CUs).
-</p>
-
-<p>
-In order to be backwards-compatible, p2 is able to install things from old-style update sites and extension locations
-by generating metadata for these things on-the-fly, but this of course is not the optimal situation. Ideally plug-in
-developers should create p2 metadata when they produce their bundles, features, and products. 
-</p>
-
-<p>
-This document describes how to generate p2 metadata for your software.
-</p>
-
-<h2>The Metadata Generator Application</h2>
-<p>
-Since Eclipse 3.4, p2 ships with a metadata generator application that plug-in developers can run. The generator application is contained in the
-bundle <code>org.eclipse.equinox.p2.metadata.generator</code>. This bundle is part of the Eclipse SDK, 
-and is also available in the p2 Admin UI. The generator can be invoked using the generic Eclipse launcher format as follows:
-</p>
-
-<p>
-<code>eclipse -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator &lt;generatorArgs&gt;</code>
-</p>
-
-<p>
-The generator application has three primary modes of operation:
-</p>
-<ol>
-	<li>Generating metadata for a folder containing bundles and features (<code>-source</code> argument)</li>
-	<li>Generating metadata for a traditional Eclipse update site (<code>-updateSite</code> argument)</li>
-	<li>Generating metadata for an existing Eclipse application that does not contain p2 metadata (<code>-config</code> argument)</li>
-</ol>
-
-<p>
-Note that you can also generate metadata for your features, bundles, and products through the PDE
-UI and in headless PDE builds. See the <a href="../../org.eclipse.pde.doc.user/guide/tools/export_wizards/export_wizards.htm">Export Wizards</a> section in the Plug-in Development Environment Guide as well as <a href="../../org.eclipse.pde.doc.user/tasks/pde_p2_integration.htm">PDE Build integration with p2</a> for details.
-</p>
-
-<p>
-Once you run the generator, you will see the generated artifact repository index file in <code>artifacts.xml</code> and 
-the generated metadata repository index file in the <code>content.xml</code> (or <code>artifacts.jar</code> and
-<code>content.jar</code> if you used the -compress option). There is nothing forcing you to have the metadata and
-artifact repositories co-located, but you can do this if you wish to.
-</p>
-
-<h3>1. Bundles and Features</h3>
-<p>
-If you have a directory with bundles and features and you want to create p2 metadata for them, you can use the p2
-metadata generator. Here is an example of using the generator in this scenerio. In this case the features and bundles
-are located under the <code>D:/myData/</code> directory and the artifact and metadata repositories are co-located
-and produced to <code>D:/repository/</code>. In this case the bundles and features are copied (published) to the
-artifact repository folder (<code>D:/repository/</code>). This repository folder can be published to a server without
-any further modification.
-</p>
-
-<pre>
-eclipse
-   -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator
-   -source D:/myData/
-   -metadataRepository file:D:/repository/
-   -metadataRepositoryName "My Update Site"
-   -artifactRepository file:D:/repository/
-   -artifactRepositoryName "My Artifacts"
-   -publishArtifacts
-   -publishArtifactRepository
-   -compress
-   -noDefaultIUs
-   -vmargs -Xmx256m
-</pre>
-
-<h3>2. Update Manager Site</h3>
-<p>
-If you have an update manager site (site index file along with features and plug-ins) and you would like to generate
-p2 metadata, you can use the metadata generator application. The following example shows how to generate metadata 
-from an pre-existing update site located in <code>D:\ganymedeM5</code>. The output files from the operation will
-also be placed in the <code>D:\ganymedeM5</code> folder so clients will be able to point to the same location,
-regardless of which UI they are using.
-</p>
-<pre>
-eclipse
-   -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator
-   -updateSite D:/ganymedeM5/
-   -site file:D:/ganymedeM5/site.xml
-   -metadataRepository file:D:/ganymedeM5/
-   -metadataRepositoryName "Ganymede Update Site"
-   -artifactRepository file:D:/ganymedeM5/
-   -artifactRepositoryName "Ganymede Artifacts"
-   -compress
-   -reusePack200Files
-   -noDefaultIUs
-   -vmargs -Xmx256m
-</pre>
-
-<h3>3. Existing Non-p2 Eclipse Application</h3>
-<p>
-If you have an existing Eclipse application with plug-ins, features, root files and a configuration, then you can 
-use the <code>-config</code> mode to run the generator.
-</p>
-<pre>
-eclipse
-   -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator
-   -config D:/application/
-   -metadataRepository file:D:/repository/
-   -metadataRepositoryName "My Update Site"
-   -artifactRepository file:D:/repository/
-   -artifactRepositoryName "My Artifacts"
-   -publishArtifacts
-   -publishArtifactRepository
-   -root my.application
-   -rootVersion 1.0.0
-   -compress
-   -noDefaultIUs
-   -vmargs -Xmx256m
-</pre>
-
-<h2>Input Arguments</h2>
-
-<p>You can invoke the p2 metadata generator in one of these modes:</p>
-<dl>
-<dt><code>-source &lt;path&gt;</code></dt>
-	<dd>the path to a folder containing <code>plugins</code> and <code>features</code> folders</dd>
-<dt><code>-updateSite &lt;path&gt;</code></dt>
-	<dd>the path to a traditional update site</dd>
-<dt><code>-config &lt;path&gt;</code></dt>
-	<dd>the path of an Eclipse application that is not p2-enabled</dd>
-</dl>
-<p>Here are other command-line options:</p>	 
-<dl>
-<dt><code>-exe &lt;path&gt;</code></dt>
-	<dd>the location of the application launcher executable</dd>
-<dt><code>-launcherConfig &lt;path&gt;</code></dt>
-	<dd>the path of the launcher configuration file (e.g. <code>eclipse.ini</code>)</dd>
-<dt><code>-features &lt;path&gt;</code></dt>
-	<dd>the location of the features folder</dd>
-<dt><code>-bundles &lt;path&gt;</code></dt>
-	<dd>the location of bundles folder</dd> 
-<dt><code>-base &lt;path&gt;</code></dt>
-	<dd>a base location containing a <code>plugins</code> and <code>features</code> directory</dd> 
-<dt><code>-p2.os &lt;os&gt;</code></dt>
-	<dd>the target operating system for the application</dd> 
-<dt><code>-site &lt;path&gt;</code></dt>
-	<dd>the URL of a <code>site.xml</code> file used to generate categories</dd> 
-</dl>    
-<h2>Output Arguments</h2>
-<p>And some more command-line arguments related to the output:</p>
-<dl>
-<dt><code>-metadataRepository &lt;url&gt;</code></dt>
-	<dd>the URL to a writable metadata repository that will contain the produced metadata</dd> 
-<dt><code>-metadataRepositoryName &lt;name&gt;</code></dt>
-	<dd>a user-friendly name for the metadata repository</dd> 
-<dt><code>-artifactRepository &lt;url&gt;</code></dt>
-	<dd>the URL to a writable artifact repository that will contain the produced artifacts</dd>
-<dt><code>-artifactRepositoryName &lt;name&gt;</code></dt>
-	<dd>a user-friendly name for the artifact repository</dd> 
-<dt><code>-publishArtifacts</code></dt>
-	<dd>flag indicating that the artifacts should be published (copied) to the repository. When this flag is not set, the actual bytes 
-	underlying the artifact will not be copied, but the repository index will be created. When this option is not 
-	specified, it is recommended to set the artifactRepository to be in the same location as the source (<code>-source</code>).</dd>
-<dt><code>-publishArtifactRepository</code></dt>
-	<dd>flag indicating to write out the artifact repository index file</dd> 
-<dt><code>-append</code></dt>
-	<dd>flag indicating that repositories will be appended to as opposed to over-written</dd> 
-<dt><code>-root &lt;name&gt;</code></dt>
-	<dd>When you run the generator application, it will create a <b>root IU</b> which will contain everything that has
-	been generated during this run. This argument is used for setting the name of the root IU.</dd> 
-<dt><code>-rootVersion &lt;version&gt;</code></dt>
-	<dd>The version of the root installable unit</dd> 
-<dt><code>-inplace</code></dt>
-	<dd>causes the metadata and artifact repositories to be written into the source location</dd> 
-<dt><code>-noDefaultIUs</code></dt>
-	<dd>flag to indicate the default configuration units should not be created</dd> 
-<dt><code>-compress</code></dt>
-	<dd>cause the repositories to store their index files in compressed form</dd> 
-<dt><code>-reusePack200Files</code></dt>
-	<dd>Specifying -reusePack200 does not require you to have pack200 files on the server, nor does it cause pack200 
-	files to be created. When this option is specified, the generator looks for pack.gz files and if available it creates an 
-	entry for them in the artifact repository index.</dd>
-</dl>	 
-
-<h2>Generator Ant Task</h2>
-<p>
-The metadata generator is also available as an Ant task. It is called <code>p2.generator</code> and it is available in the 
-<code>org.eclipse.equinox.p2.metadata.generator</code> bundle. The arguments passed to the task are the same as
-listed above.
-</p>
-
-<h2>Updated Documentation</h2>
-<p>
-Up-to-date information on the p2 metadata generator application can be found on the 
-<a href="http://wiki.eclipse.org/Equinox_p2_Metadata_Generator">Eclipse p2 wiki</a>.
-</p>   
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_mirror.html b/bundles/org.eclipse.platform.doc.isv/guide/p2_mirror.html
deleted file mode 100644
index 61a9887..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_mirror.html
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Mirroring repositories with p2</title>
-</head>
-<body>
-<h1>Mirroring repositories with p2</h1>
-<p>p2 provides two applications that support copying (mirroring) the content of remote repositories to a local repository.  
-There is also a <a href="p2_repositorytasks.htm#p2_mirror">p2.mirror ant task.</a></p>
-
-<h2>Mirroring an artifact repository</h2>
-<p>The artifact mirroring application supports duplicating a complete artifact repository into a target repository. 
-To perform this operation you simply need an eclipse installation that contains the <tt>org.eclipse.equinox.p2.artifact.repository</tt> bundle.
-The following command will copy the complete contents of a source repository into the destination repository. If the destination
-repository does not already exist, the mirroring application will create a new repository with the same properties as the source.</p> 
-<pre>
-<code>
-   &lt;eclipseInstall&gt;\eclipse.exe
-   -application org.eclipse.equinox.p2.artifact.repository.mirrorApplication
-   -source http://download.eclipse.org/releases/ganymede
-   -destination file:d:/artifactLocalRepository/
-</code>
-</pre>
-
-<h3>Arguments description</h3>
-<ul>
-<li><b>-application org.eclipse.equinox.p2.artifact.repository.mirrorApplication:</b> the application ID.</li>
-<li><b>-source &lt;source location&gt;</b>: the artifact repository to mirror from.</li>
-<li><b>-destination &lt;destination location&gt;</b>: the artifact repository to mirror to.</li>
-</ul>
- 
-<h3>Additional arguments</h3>
-<ul>
-<li><b>-writeMode clean</b>: removes all artifacts from the destination repository before performing the mirroring process.</li>
-<li><b>-verbose</b>: enables error messages and error logging.</li>
-<li><b>-ignoreErrors</b>: ensures the mirroring application continues to run in the event of an error during the mirroring process.</li>
-<li><b>-raw</b>: instructs the mirroring application to copy the exact artifact descriptors from source into the destination instead of 
-	initializing new artifact descriptors with properties from the source descriptors.</li>
-<li><b>-compare</b>: instructs the mirroring application to perform a comparison when a duplicate artifact descriptor is found.</li>
-<li><b>-comparator &lt;comparator ID&gt;</b>: specifies which comparator the mirroring application should use to compare 
-	artifact descriptors. Uses the "MD5 Comparator" if no comparator is defined which compares the MD5 hash property of the artifact descriptors.</li>
-<li><b>-compareAgainst &lt;baseline location&gt;</b>: specifies the location of a known good repository. 
-  When specified the mirror application will compare all artifacts from the source to the baseline with precedence given to artifacts found in the baseline.</li>
-<li><b>-destinationName &lt;destination name&gt;</b>: specifies what the destination repository should be named. 
-  If no name is specified, the source repository's name will be used as the destination's name if no repository exists at the destination.</li>
-</ul>
- 
-<h2>Mirroring a metadata repository</h2>
-<p>The metadata mirroring application supports copying a complete metadata repository into a target repository.
-To perform this operation you simply need an eclipse installation that contains the <tt>org.eclipse.equinox.p2.metadata.repository</tt> bundle.
-The following command will copy the complete source repository into the destination repository. If the destination
-repository does not already exist, the mirroring application will create a new repository with the same properties as the source.</p> 
-<pre>
-<code>
-    &lt;eclipseInstall&gt;\eclipse.exe
-   -application org.eclipse.equinox.p2.metadata.repository.mirrorApplication
-   -source http://download.eclipse.org/releases/ganymede
-   -destination file:d:/metadataLocalRepository/
-</code>
-</pre>
- 
-<h3>Arguments description</h3>
-<ul>
-<li><b>-application
-org.eclipse.equinox.p2.metadata.repository.mirrorApplication:</b> the application ID.</li>
-<li><b>-source &lt;source location&gt;</b>: the metadata repository to mirror from.</li>
-<li><b>-destination &lt;destination location&gt;</b>: the metadata repository to mirror to.</li>
-</ul>
-
-<h3>Additional arguments</h3>
-<ul>
-<li><b>-writeMode clean:</b> removes all installable units from the destination repository before performing the mirroring process.</li>
-<li><b>-destinationName &lt;destination name&gt;</b>: specifies what the destination repository should be named. 
-	If no name is specified, the source repository's name will be used as the destination's name if no repository exists at the destination.</li>
-<!-- Uncomment when this becomes useful <li><b>-roots: &lt;specified installable units&gt;</b> instructs mirroring application to only 
-	mirror specified installable units. The installable units must be defined as Name/Version or Name/(Version Range) and separated by commas.</li> -->
-<!-- Uncomment when transitive is implemented <li><b>-transitive:</b> ensures all installable unit's dependencies are satisfied. Adds 
-	dependent installable units when necessary. Combined with "-roots" this argument can be used to perform repository slicing.</li> -->
-</ul>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_overview.htm b/bundles/org.eclipse.platform.doc.isv/guide/p2_overview.htm
deleted file mode 100644
index 23fe20a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_overview.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Provisioning platform (p2)</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Provisioning platform (p2)</H2>
-<p>
-Installation and updates are managed in Eclipse using a provisioning
-platform called p2. Fundamentally, p2 is a technology for provisioning and
-managing Eclipse- and Equinox-based applications. You can use p2 to install
-or manage any aspect of your application, from the physical plug-ins and native
-code, to the configuration of the installed software - file permissions, command line arguments, etc. 
-Installation with p2 does not consist simply in adding or removing files in the 
-file system, but more generally the sequence of events that must occur to lay
-down and configure a system that is ready to run. Core aspects of p2 include:
-<ul>
-<li>Automatic resolution of dependencies between software components. With p2,
-you state the root set of items you want installed or uninstalled, and p2 computes
-the complete set of required system changes automatically.</li>
-<li>Transport of software components and configuration data from remote 
-repositories to the system being installed. p2 includes sophisticated algorithms for
-performing multi-threaded transfers, including support for mirrors and automatic
-re-balancing of transfers based on network state (availability, throughput). </li>
-<li>An extensible mechanism for "teaching" p2 how to install and configure various
-kinds of software. By default p2 knows how to install and configure Eclipse plug-ins,
-and basic native integration such as adding/removing files, setting permissions,
-and creating symbolic links.</li>
-<li>A graphical user interface integrated into the Eclipse platform, to allow 
-end users to examine and manage the application.</li>
-<li>A suite of command line tools and Ant tasks, to allow developers and release
-engineers to build and configure p2-enabled applications.</li>
-</ul>
-</p>
-<p>
-The following documentation sections describe how to use p2 to build and deliver
-your own Eclipse-based applications and extensions.
-<ul>
-<li><a href="p2_metadata.html">Metadata management</a></li>
-<li><a href="p2_director.html">Installation management</a></li>
-<li>Repository management</li>
-</ul>
-</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_publisher.html b/bundles/org.eclipse.platform.doc.isv/guide/p2_publisher.html
deleted file mode 100644
index 03ea110..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_publisher.html
+++ /dev/null

@@ -1,243 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) EclipseSource and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-  <title>Publishing p2 metadata</title>
-</head>
-<body>
-<h1>Publishing p2 metadata</h1>
-<p>
-The p2 metadata contains useful information about the elements that can be installed.  These elements 
-are called Installable Units (IUs).  Among other things, the IUs describe dependencies, 
-properties and configuration information.
-</p>
-
-<p>
-There are three different ways p2 repositories can be created.  1) By using the export wizard, 2) using PDE Build, and 3)
-using the publisher.  The Plug-in Development Environment Guide explains how the  
-<a href="../../org.eclipse.pde.doc.user/guide/tools/export_wizards/export_features.htm">feature export wizard</a>, 
-<a href="../../org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm">product export wizard</a> and 
-<a href="../../org.eclipse.pde.doc.user/tasks/pde_p2_builds.htm">PDE Build</a>
-can be used to generate metadata.  The remainder of this document explains how the publisher can be used.
-</p>
-
-<p>
-The <em>publisher</em> is the means by which deployable entities get added to repositories. For example, 
-the publisher can be used to create an IU from an OSGi Bundle or Eclipse Feature.  The publisher consists
-of an extensible set of publishing actions, applications and Ant tasks that allow users to generate 
-p2 repositories from a number of different sources.  The publisher replaces the 
-<a href="p2_metadata_generator.html">Metadata Generator</a>.
-</p>
-
-<p>
-In order to be backwards-compatible, p2 is able to install things from old-style update sites and extension locations
-by generating metadata for these things on-the-fly, but this of course is not the optimal situation. Ideally, plug-in
-developers should create p2 metadata when they produce their bundles, features, and products. 
-</p>
-
-<p>
-This document describes how to publish p2 metadata for your software using <b>the publisher</b>.
-</p>
-
-<p>
-The publisher can be used in two ways:
-</p>
-<ol>
-<li><a href="#headless_applications">Command line applications</a></li>
-<li><a href="p2_publishingtasks.htm">Ant Tasks</a></li>
-</ol>
-
-<h2><a name="headless_applications">Command Line Applications</a></h2>
-<p>
-Since Eclipse 3.5, p2 ships with four command line publisher applications that plug-in developers can run. The applications are contained
-in <code>org.eclipse.equinox.p2.publisher</code> and <code>org.eclipse.equinox.p2.updatesite</code>.  These bundles are
-part of the Eclipse SDK. The four applications are:
-</p>
-
-<ol>
-<li><a href="#updatesite_publisher">UpdateSite Publisher</a></li>
-<li><a href="#features_and_bundles_publisher">Features And Bundles Publisher</a></li>
-<li><a href="#product_publisher">Product Publisher</a></li>
-<li><a href="#category_publisher">Category Publisher</a></li>
-</ol>
-
-<h3><a name="updatesite_publisher">UpdateSite Publisher</a></h3>
-
-<p>
-The updatesite publisher application (<code>org.eclipse.equinox.p2.publisher.UpdateSitePublisher</code>) is a command line application 
-that is capable of generating metadata (p2 repositories) from an update site containing a site.xml, bundles and features.  The 
-updatesite publisher can be invoked using the generic Eclipse launcher format as follows:
-</p>
-
-<p>
-<code>eclipse -application org.eclipse.equinox.p2.publisher.UpdateSitePublisher &lt;publisherArgs&gt;</code>
-</p>
-
-<p>Here are the supported command-line options:</p>	 
-
-<dl>
-<dt><code>-metadataRepository &lt;URI&gt;</code></dt>
-	<dd>the URI to the metadata repository where the installable units should be published</dd>
-<dt><code>-artifactRepository &lt;URI&gt;</code></dt>
-	<dd>the URI to the artifact repository where the artifacts should be published</dd>
-<dt><code>-source &lt;path&gt;</code></dt>
-	<dd>the location of the update site</dd>
-<dt><code>-compress</code></dt>
-	<dd>a flag indicating that the repository should be compressed</dd> 
-<dt><code>-append</code></dt>
-	<dd>flag indicating that repositories will be appended to as opposed to over-written</dd> 
-<dt><code>-publishArtifacts</code></dt>
-	<dd>flag indicating that the artifacts should be published (copied) to the repository. When this flag is not set, the actual bytes 
-	underlying the artifact will not be copied, but the repository index will be created. When this option is not 
-	specified, it is recommended to set the artifactRepository to be in the same location as the source (<code>-source</code>).</dd>
-</dl>    
-
-<p>Here is an example of how the updatesite publisher can be used to create a compressed p2 repository from an update site: </p>
-<pre>
-eclipse -application org.eclipse.equinox.p2.publisher.UpdateSitePublisher
- -metadataRepository file:/&lt;some location&gt;/repository
- -artifactRepository file:/&lt;some location&gt;/repository
- -source /&lt;location with a site.xml&gt;
- -configs gtk.linux.x86
- -compress
- -publishArtifacts
-</pre>
-
-<p>
-Once you run the publisher, you will see the generated artifact repository index file in <code>artifacts.xml</code> and 
-the generated metadata repository index file in the <code>content.xml</code> (or <code>artifacts.jar</code> and
-<code>content.jar</code> if you used the -compress option). There is nothing forcing you to have the metadata and
-artifact repositories co-located, but you can do this if you wish to.
-</p>
-
-<h3><a name="features_and_bundles_publisher">Features And Bundles Publisher</a></h3>
-
-<p>
-The features and bundles publisher application (org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher) 
-is a command line application that is capable of generating metadata (p2 repositories) 
-from pre-built Eclipse bundles and features. The features and bundle publisher can be invoked using the 
-generic Eclipse launcher format as follows:
-</p>
-
-<p>
-<code>eclipse -application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher &lt;publisherArgs&gt;</code>
-</p>
-
-<p>Here are command-line options:</p>	 
-<dl>
-<dt><code>-metadataRepository &lt;URI&gt;</code></dt>
-	<dd>the URI to the metadata repository where the installable units should be published</dd>
-<dt><code>-artifactRepository &lt;URI&gt;</code></dt>
-	<dd>the URI to the artifact repository where the artifacts should be published</dd>
-<dt><code>-source &lt;path&gt;</code></dt>
-	<dd>the location of the update site</dd>
-<dt><code>-bundles &lt;path&gt;</code></dt>
-	<dd>the location of the bundles</dd>
-<dt><code>-features &lt;path&gt;</code></dt>
-	<dd>the location of the features</dd>	
-<dt><code>-compress</code></dt>
-	<dd>a flag indicating that the repository should be compressed</dd> 
-<dt><code>-append</code></dt>
-	<dd>flag indicating that repositories will be appended to as opposed to over-written</dd> 	
-<dt><code>-publishArtifacts</code></dt>
-	<dd>flag indicating that the artifacts should be published (copied) to the repository. When this flag is not set, the actual bytes 
-	underlying the artifact will not be copied, but the repository index will be created. When this option is not 
-	specified, it is recommended to set the artifactRepository to be in the same location as the source (<code>-source</code>).</dd>
-</dl>   
-
-<p>
-The features and bundles publisher application can be invoked using the <code>-source</code> option by pointing 
-at a directory that contains two sub-directories (features and plug-ins).  The publisher can also be invoked 
-by pointing at the bundles and features separately and using the <code>-bundles</code> and <code>-features</code> options.
-</p>
-
-<p>Here is an example of how the features and bundles publisher can be used to create a compressed p2 repository from a collection
-of bundles and features: </p>
-<pre>
-eclipse -application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher
-   -metadataRepository file:/&lt;some location&gt;/repository
-   -artifactRepository file:/&lt;some location&gt;/repository
-   -source /&lt;location with a plugin and feature directory&gt;
-   -configs gtk.linux.x86
-   -compress
-   -publishArtifacts
-</pre>
-
-<h3><a name="product_publisher">Product Publisher</a></h3>
-<p>
-The product publisher application (<code>org.eclipse.equinox.p2.publisher.ProductPublisher</code>) is a command line application 
-that is capable of generating metadata (p2 repositories) from a .product file.  The product publisher does not generate metadata
-for the bundles and features that make up the product.  The product publisher can be invoked using the 
-generic Eclipse launcher format as follows:
-</p>
-
-<p>
-<code>eclipse -application org.eclipse.equinox.p2.publisher.ProductPublisher &lt;publisherArgs&gt;</code>
-</p>
-
-<p>Here are the supported command-line options:</p>	 
-<dl>
-<dt><code>-metadataRepository &lt;URI&gt;</code></dt>
-	<dd>the URI to the metadata repository where the installable units should be published</dd>
-<dt><code>-artifactRepository &lt;URI&gt;</code></dt>
-	<dd>the URI to the artifact repository where the artifacts should be published</dd>
-<dt><code>-productFile &lt;path&gt;</code></dt>
-	<dd>the location of the product file</dd>
-<dt><code>-executables &lt;path&gt;</code></dt>
-	<dd>the location of the executables feature</dd>
-<dt><code>-flavor &lt;String&gt;</code></dt>
-	<dd>the flavor used for the configuration units (if unsure, using tooling)</dd>	
-<dt><code>-compress</code></dt>
-	<dd>a flag indicating that the repository should be compressed</dd> 
-<dt><code>-append</code></dt>
-	<dd>flag indicating that repositories will be appended to as opposed to over-written</dd> 
-</dl>  
-
-<p>Here is an example of how the product publisher can be used to create a p2 repository from a .product file:</p>
-
-<pre>
-eclipse -application org.eclipse.equinox.p2.publisher.ProductPublisher
-   -metadataRepository file:/&lt;some location&gt;/repository
-   -artifactRepository file:/&lt;some location&gt;/repository
-   -productFile /&lt;location&gt;/&lt;filename&gt;.product
-   -append
-   -executables /&lt;deltapack parent&gt;/delta/eclipse/features/org.eclipse.equinox.executable_3.3.200.v20090426-1530-7M-Fm-FI3UouOdcoUJz-7oc
-   -flavor tooling
-   -configs gtk.linux.x86
-</pre>
-
-<h3><a name="category_publisher">Category Publisher</a></h3>
-<p>
-The category publisher application (org.eclipse.equinox.p2.publisher.CategoryPublisher) is a command line application that is capable of 
-categorizing a set of Installable Units in a given repository. The categorization is driven from a category file. The category publisher 
-can be invoked using the generic Eclipse launcher format as follows:
-</p>
-
-<p>
-<code>eclipse -application org.eclipse.equinox.p2.publisher.CategoryPublisher &lt;publisherArgs&gt;</code>
-</p>
-
-<p>Here is an example of how the product publisher can be used to categorize a p2 repository from a category.xml file: </p>
-
-<pre>
-eclipse -application -application org.eclipse.equinox.p2.publisher.CategoryPublisher
-   -metadataRepository file:/&lt;some location&gt;/repository
-   -categoryDefinition file:/&lt;some location&gt;/category.xml
-   -compress
-</pre>
-<p>
-Categories are always appended to a repository.  
-</p>
-
-<h2>Updated Documentation</h2>
-<p>
-Up-to-date information on the p2 publisher can be found on the 
-<a href="http://wiki.eclipse.org/Equinox/p2/Publisher">Eclipse p2 wiki</a>.
-</p>   
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_publishingtasks.htm b/bundles/org.eclipse.platform.doc.isv/guide/p2_publishingtasks.htm
deleted file mode 100644
index 65f7533..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_publishingtasks.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Ant tasks for publishing p2 metadata</title>
-</head>
-<body>
-<h1>Ant tasks for publishing p2 metadata</h1>
-<p>Since Eclipse 3.5, p2 ships with two publisher ant tasks. The ant tasks are contained
-in <code>org.eclipse.equinox.p2.publisher</code>.  This bundles is
-part of the Eclipse SDK.</p>
-
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><tt>Default Attributes</tt></b></td></tr>
-	<tr><td><p>The <tt>p2.publish.*</tt> ant tasks outlined below all support the following attributes:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>metadataRepository</tt></td><td>A URL specifying the metadata repository to publish to.</td></tr>
-			<tr><td><tt>artifactRepository</tt></td><td>A URL specifying the artifact repository to publish to.</td></tr>
-			<tr><td><tt>repository</tt></td><td>Sets both metadataRepository and artifactRepository.</td></tr>
-			<tr><td><tt>metadataRepositoryName</tt></td><td>When creating a new metadata repository, sets the name.</td></tr>
-			<tr><td><tt>artifactRepositoryName</tt></td><td>When creating a new artifact repository, sets the name.</td></tr>
-			<tr><td><tt>repositoryName</tt></td><td>Sets both metadataRepositoryName and artifactRepositoryName.</td></tr>
-			<tr><td><tt>append</tt></td><td>Whether to append to the repository.  (Default is "true")</td></tr>
-			<tr><td><tt>compress</tt></td><td>When creating a new repository, whether or not to compress the metadata. (Default is "false")</td></tr>
-			<tr><td><tt>publishArtifacts</tt></td><td>Whether or not to publish the artifacts. (Default is "true")</td></tr>
-			<tr><td><tt>reusePackedFiles</tt></td><td>Whether or not to include discovered Pack200 files in the repository. (Default is "false")</td></tr>
-			<tr><td><tt>&lt;contextRepository&gt;</tt></td>
-			<td>Nested elements specifying context repositories, supports the following attributes:
-				<table cellspacing="0" cellpadding="2" border="1" width="100%">
-				<tr><td><tt>location</tt></td><td>A URL specifying the location of the repository.</td></tr>
-				<tr><td><tt>artifact</tt></td><td>"true" or "false": whether or not there is an artifact repository at this location.</td></tr>
-				<tr><td><tt>metadata</tt></td><td>"true" or "false": whether or not there is a metadata repository at this location.</td></tr>
-				</table>
-				<p>If a given context repository contains metadata for one of the features or bundles that are being published, then that metadata
-				will be re-used instead of generating new metadata.</p>
-			</td></tr>
-		</table>
-	</td></tr>
-</table>
-<br>
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><tt>p2.publish.featuresAndBundles</tt></b></td></tr>
-	<tr><td><p>This task will publish metadata for pre-existing binary features and plug-ins.</p></td></tr>
-	<tr><td><p>This task supports the following attributes and elements:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>source</tt></td><td>A folder containing plugins and features subfolders to publish.</td></tr>
-			<tr><td><tt>&lt;features&gt;</tt></td><td>A nested fileset element specifying the locations of binary features to publish.</td></tr>
-			<tr><td><tt>&lt;bundles&gt;</tt></td><td>A nested fileset element specifying the locations of binary plug-ins to publish.</td></tr>
-		</table>
-	</td></tr>
-</table>
-<br>
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><tt>p2.publish.product</tt></b></td></tr>
-	<tr><td><p>Publish a .product file. This task assumes everything included in the product already exists in the repository. (That is, all features and bundles have been previously published.)</p>
-	</td></tr>
-	<tr><td><p>This task supports the following attributes:</p>
-	<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-		<tr><td><tt>flavor</tt></td><td>Set the flavor for the p2 metadata, default is "tooling".  Products should consider using a unique flavor if they have special requirements for bundle start levels.</td></tr>
-		<tr><td><tt>productFile</tt></td><td>The location of the .product file describing the product.</td></tr>
-		<tr><td><tt>executables</tt></td><td>The location of the executables feature.  This is the feature that is used for branding and publishing the executables.</td></tr>
-		<tr><td><tt>&lt;config&gt;</tt></td><td>Nested elements specifying configurations supported by this product. Config elements specify ws, os and arch:
-												<div align="center"><tt>&lt;config ws="gtk" os="linux" arch="x86" /&gt;</tt></div>
-		</td></tr>
-		<tr><td><tt>&lt;advice&gt;</tt></td><td>Nested elements specifying specifying additional advice to use when creating the product.  Currently the accepted kinds of advice are "featureVersions" and "pluginVersions".
-		<div align="center"><tt>&lt;advice kind="featureVersions" file="finalFeaturesVersions.properties" /&gt;<br>&lt;advice kind="pluginVersions" file="finalPluginsVersions.properties" /&gt;</tt></div>
-		PDE/Build will generate these version properties files when the builder sets the property <a href="../../org.eclipse.pde.doc.user/tasks/pde_version_qualifiers.htm#final_versions"><tt>generateVersionsLists</tt>"</a>.
-		</td></tr>
-	</table>
-	</td></tr>
-</table>
-<br>			
-
-<p>
-   In addition to the publisher tasks, metadata can be generated as 
-   <a href="../../org.eclipse.pde.doc.user/tasks/pde_p2_buildtasks.htm">part of PDE Build</a>.
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm b/bundles/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm
deleted file mode 100644
index 7f72937..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/p2_repositorytasks.htm
+++ /dev/null

@@ -1,255 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>Ant tasks for managing repositories</title>
-</head>
-<body>
-<h1>Ant tasks for managing repositories</h1>
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><a name="source_repositories"><b>Specifying source repositories</b></a></td></tr>
-	<tr><td><p>Several p2 tasks accept "source" repositories.  Source repositories can be specified in several different ways:</p>
-	<ul>
-	<li>A <b><tt>source</tt></b> attribute directly on the ant task.  The value is a URL to a location that contains both a metadata and artifact repository.  For example:
-	<div align="center"><tt>&lt;p2.mirror source="http://download.eclipse.org/releases/galileo" .... /&gt;</tt></div>
-	</li>
-	<li>A <b><tt>&lt;source&gt;</tt></b> element nested in the ant task.  This element is an ant fileset, with additional <i>location</i> and <i>kind</i> attributes.
-	<ul>
-		<li><i>location</i> : A URL specifying the location of a repository.  If this attribute is set, all fileset based attributes are ignored.</li>
-		<li><i>kind</i>: Either "<tt>metadata</tt>" or "<tt>artifact</tt>".  If not set, the repository is both metadata and artifacts.</li>
-	</ul> 
-	If no <i>location</i> attribute is set, all directories matched by the fileset are added as repositories and all *.zip files are treated as zipped repositories 
-	(accessed using a jar: URL). For example:
-<pre>&lt;source kind="metatata" dir="/build/input" includes="*.zip" /&gt;
-&lt;source location="http://download.eclipse.org/releases/galileo" /&gt;
-</pre>
-	</li>
-	<li>A <b><tt>&lt;source&gt;</tt></b> element containing a list of repositories.  Each nested element is again a fileset with an additional <i>kind</i> attribute.  For example:
-<pre>&lt;source&gt;
-   &lt;repository location="http://download.eclipse.org/releases/galileo" /&gt;
-   &lt;repository kind="metadata" file="/build/repos/cdt-master-6.0.0-I200903161435.zip" /&gt;
-   &lt;repository kind="artifact" dir="/build/repos" includes="*repo" /&gt;
-&lt;/source&gt;
-</pre>
-	</li>
-	</ul></td></tr>
-	<tr><td><a name="destination_repositories"><b>Specifying destination repositories</b></a></td></tr>
-	<tr><td><p>Several p2 tasks accept "destination" repositories.  Destination repositories can be specified in several different ways:</p>
-	<ul>
-	<li>A <b><tt>destination</tt></b> attribute directly on the ant task.  The value is a URL to a location for both a metadata and artifact repository.</li>
-	<li>A <b><tt>&lt;repository&gt;</tt></b> element nested in the ant task.  (<b><tt>&lt;destination&gt;</tt></b> may also be used.) 
-	  This element supports the following attributes:
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>location</tt></td><td>A URL to the location of the repository</td></tr>
-			<tr><td><tt>kind</tt></td><td>Either "<tt>metadata</tt>" or "<tt>artifact</tt>".  Default is both if not specified.</td></tr>
-			<tr><td><tt>name</tt></td><td>A name to give the repository if the repository does not already exist.</td></tr>
-			<tr><td><tt>append</tt></td><td>Append to a repository that is already there.  (Default is "true")</td></tr>
-			<tr><td><tt>compressed</tt></td><td>Whether to compress the content/artifact xml into a jar (Default is "true")</td></tr>
-			<tr><td><tt>format</tt></td><td>A URL to another repository from which to copy the repository name and other properties.</td></tr>
-		</table>
-	</li>
-	</ul></td></tr>
-	<tr><td><a name="installable_units"><b>Specifying Installable Units</b></a></td></tr>
-	<tr><td>Some p2 tasks allow specifying installable units to work with.  This is done with nested <tt>&lt;iu&gt;</tt> elements which support the following attributes:
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>id</tt></td><td>The id of the IU to match.</td></tr>
-			<tr><td><tt>version</tt></td><td>The version of the IU to match.  If not specified, the highest versioned IU is returned.  (requires <i>id</i> to be set)</td></tr>
-			<tr><td><tt>query</tt></td><td>Matches all IUs satisfying the query.  Currently only "property" queries are supported. 
-			  The format of the query attribute is intended to be "xpath-like". Eg:
-			<div align="center"><tt>&lt;iu query="property[@name='org.eclipse.equinox.p2.type.category']" /&gt;</tt></div>
-			<div align="center"><tt>&lt;iu query="property[@name='my.property.name' @value='specialValue']" /&gt;</tt></div>			
-			</td></tr>
-		</table>
-	</td></tr>
-</table>
-<h2>Ant Tasks</h2>
-<br>
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><a name="p2_mirror"><tt>p2.mirror</tt></a></b></td></tr>
-	<tr><td><p>This task mirrors artifacts and metadata from the given source repositories to the destination.  
-	  This task will traverse the source repository and recursively include all IUs that match the requirements of IUs being mirrored (this is called <em>slicing</em> the repository).</p>
-	  </td>
-	</tr>
-	<tr><td><p>This task supports the following attributes and elements:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>source</tt></td><td>Source repositories, as outlined <a href="#source_repositories">above</a></td></tr>
-			<tr><td><tt>desination</tt></td><td>Destination repositories, as outlined <a href="#destination_repositories">above</a></td></tr>
-			<tr><td><tt>&lt;iu&gt;</tt></td><td>Nested IU elements, as outlined <a href="#installable_units">above</a>.  
-			  The installable units to mirror.  If none are specified, all IUs contained in the source repositories are mirrored.</td></tr>
-			<tr><td><tt>log</tt></td><td>A file to use for logging the results.</td></tr>
-			<tr><td><tt>ignoreErrors</tt></td><td>Whether or not to ignore errors. (Default is false)</td></tr>
-			<tr><td><tt>raw</tt></td><td>Copy the exact artifact descriptors from source into the destination instead of 
-			  initializing new artifact descriptors with properties from the source descriptors. (Default is true)</td></tr>
-			<tr><td><tt>verbose</tt></td><td>Turn on verbose logging.</td></tr>
-			<tr><td><tt>validate</tt></td><td>Validate that all all source descriptors are present in the 
-			  destination after mirroring is complete. (Default is false)</td></tr>
-			<tr><td><tt>&lt;comparator&gt;</tt></td><td>A nested comparator element for comparing against a baseline repository.  
-			  If IUs from the source repository already exist in the baseline, then the artifacts will be mirrored from 
-			  the baseline instead of the source.  This element supports the following attributes:
-			<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-				<tr><td><tt>&lt;baseline&gt;</tt></td><td>A nested element specifying the baseline repository.  
-				  See <a href="#destination_repositories"><i>destination repositories</i></a> above.</td></tr>
-				<tr><td><tt>comparator</tt></td><td>Id of a comparator to use if the baseline artifacts should be compared 
-				  against the source artifacts.  These are extensions to the <i>org.eclipse.equinox.p2.artifact.repository.artifactComparators</i> extension point.  
-				  Comparators provided by p2 are:
-				<ul>
-				<li><i>org.eclipse.equinox.p2.repository.tools.jar.comparator</i>: Compare jars.  
-				  Class files are disassembled and compared for equivalence, properties and manifest files are compared as such, all other files are compared byte-for-byte.</li>
-				<li><i>org.eclipse.equinox.artifact.md5.comparator</i>: Compare the MD5 sums as recorded in the artifact repositories.</li>
-				</ul>
-				
-				</td></tr>
-				<tr><td><tt>comparatorLog</tt></td><td>A log file for the results of the comparison.</td></tr>
-			</table>
-			</td></tr>
-			<tr><td><tt>&lt;slicingOptions&gt;</tt></td><td>A nested element for specifying how to slice the 
-			  repositories to bring in additional IUs.  This element supports the following attributes:
-			<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-				<tr><td><tt>followStrict</tt></td><td>Set to true if only strict dependencies should be followed.  
-				  A strict dependency is defined by a version range only including one version (e.g. [1.0.0.v2009, 1.0.0.v2009]). (Default is false)</td></tr>
-				<tr><td><tt>includeOptional</tt></td><td>Whether or not to follow optional requirements. (Default is true).</td></tr>
-				<tr><td><tt>includeNonGreedy</tt></td><td>Whether or not to follow non-greedy requirements. (Default is true).</td></tr>
-				<tr><td><tt>includeFeatures</tt></td><td>Whether or not to include features. (Default is true).</td></tr>
-				<tr><td><tt>platformFilter</tt></td><td>An "os,ws,arch" triplet to set as the platform against which IU LDAP filters will be matched.  
-				  IUs not matching the filter will not be mirrored.</td></tr>
-				<tr><td><tt>filter</tt></td><td>Set additional filter properties.  Format is a comma separated list of "key=value" pairs.</td></tr>
-				<tr><td><tt>followOnlyFilteredRequirements</tt></td><td>Invert the filters, include only the IUs that <b>don't</b> match.</td></tr>
-				<tr><td><tt>latestVersionOnly</tt></td><td>Set to "true" to filter the resulting set of IUs to only included the latest version of each Installable Unit.
-				By default, all versions satisfying dependencies are included.</td></tr>
-			</table>
-			</td></tr>
-		</table>
-	</td></tr>
-</table>
-<br>
-Examples:
-<p>Creating a delta pack repository based on the contents of the platform, rcp, jdt and equinox.executable features:</p>
-<pre>
-	&lt;p2.mirror source="file://${buildRepo}"&gt;
-	   &lt;destination kind="metadata" location="file://${deltaTemp}" name="RCP Delta Pack Repo"  /&gt;
-	   &lt;destination kind="artifact" location="file://${deltaTemp}" name="RCP Delta Pack Repo"  /&gt;
-	   &lt;iu id="org.eclipse.platform.feature.group" version="" /&gt;
-	   &lt;iu id="org.eclipse.rcp.feature.group" version="" /&gt;
-	   &lt;iu id="org.eclipse.jdt.feature.group" version="" /&gt;
-	   &lt;iu id="org.eclipse.equinox.executable" version="" /&gt;
-	   &lt;slicingOptions includeOptional="false" includeNonGreedy="false" followStrict="true" followOnlyFilteredRequirements="true" /&gt;
-	&lt;/p2.mirror&gt;
-</pre>
-<p>Mirror the org.eclipse.equinox.p2.user.ui feature and other required bundles locally (perhaps in preparation for a build).</p>
-<pre>
-	&lt;p2.mirror source="http://download.eclipse.org/releases/galileo" destination="${p2Repo}"&gt;
-	   &lt;slicingOptions followStrict="true" /&gt;
-	   &lt;iu id="org.eclipse.equinox.p2.user.ui.feature.group" /&gt;
-	   &lt;iu id="org.eclipse.ecf"/&gt;
-	   &lt;iu id="org.eclipse.ecf.filetransfer"/&gt;
-	   &lt;iu id="org.eclipse.ecf.identity"/&gt;
-	   &lt;iu id="org.eclipse.ecf.provider.filetransfer"/&gt;
-	   &lt;iu id="org.eclipse.ecf.provider.filetransfer.httpclient"/&gt;
-	   &lt;iu id="org.eclipse.ecf.provider.filetransfer.httpclient.ssl" /&gt;
-	   &lt;iu id="org.eclipse.ecf.provider.filetransfer.ssl"/&gt;
-	   &lt;iu id="org.eclipse.ecf.ssl" /&gt;
-	   &lt;iu id="org.apache.commons.codec"/&gt;
-	   &lt;iu id="org.apache.commons.httpclient"/&gt;
-	   &lt;iu id="org.apache.ant"/&gt;
-	   &lt;iu id="org.eclipse.core.runtime.compatibility.registry"/&gt;
-	&lt;/p2.mirror&gt;
-</pre>
-<p>Mirror the results of a build into a public location, and compare against the existing update site to ensure that artifacts 
-  haven't changed if their versions haven't been updated.</p>
-<pre>
-	&lt;p2.mirror source="file:${buildRepo}" ignoreErrors="true" log="${buildlogs}/mirrorlog.txt"&gt;
-	   &lt;destination compressed="true" name="${p2.repo.name}" location="file:${updateRepo}" append="true" /&gt;
-	   &lt;comparator comparator="org.eclipse.equinox.p2.repository.tools.jar.comparator" comparatorLog="${buildlogs}/comparatorlog.txt"&gt;
-	      &lt;repository location="file:${updateSite}" /&gt;
-	   &lt;/comparator&gt;
-	&lt;/p2.mirror&gt;
-</pre>
-
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><a name="p2_repo2runnable"><tt>p2.repo2runnable</tt></a></b></td></tr>
-	<tr><td><p>Transform IUs into their installed form and add them to the destination repository.  This allows compiling against folder 
-	  shaped bundles that contain nested jars.  This task is the main mechanism by which headless PDE/Builds can reuse metadata.</p>
-	</td></tr>
-	<tr><td><p>This task supports the following attributes and elements:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>source</tt></td><td>Source repositories, as outlined <a href="#source_repositories">above</a></td></tr>
-			<tr><td><tt>desination</tt></td><td>Destination repositories, as outlined <a href="#destination_repositories">above</a></td></tr>
-			<tr><td><tt>failOnError</tt></td><td>Default is true.  Set to "false" to ignore errors and complete the operation.</td></tr>
-			<tr><td><tt>&lt;iu&gt;</tt></td><td>Nested IU elements, as outlined <a href="#installable_units">above</a>.  
-			  The installable units to transform.  If none are specified, all IUs contained in the source repositories are transformed.</td></tr>
-		</table>
-	</td></tr>
-</table>
-<br>
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><tt>p2.process.artifacts</tt></b></td></tr>
-	<tr><td><p>Process a local, file-based artifact repository.  This task will (optionally) sign and pack artifacts, 
-	  as well as update the MD5 sums in the repository to match the actual artifacts on disk (since signing/conditioning will change the MD5 sums).
-	This task will use the jarProcessor, which in turn uses ant's SignJar task which requires the <i>jarsigner</i> command line tool.</p></td></tr>
-	<tr><td><p>This task supports the following attributes and elements:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>repositoryPath</tt></td><td>A URL to an artifact repository to process.  This must be a local, file-based repository.</td></tr>
-			<tr><td><tt>pack</tt></td><td>Whether or not to create pack.gz artifacts.  (Default is false)</td></tr>
-			<tr><td><tt>normalize</tt></td><td>Whether or not to do pack200(pack + unpack) conditioning on the artifacts.  
-			  (Default is false, however sign + pack will imply a normalize.)</td></tr>
-			<tr><td><tt>repositoryPath</tt></td><td>A URL to an artifact repository to process.  This must be a local, file-based repository.</td></tr>
-			<tr><td><tt>&lt;sign&gt;</tt></td><td>A nested element to enable signing.  This element supports the following attributes:
-			<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-				<tr><td><tt>alias</tt></td><td>The alias to sign with</td></tr>
-				<tr><td><tt>keystore</tt></td><td>The location of the keystore.</td></tr>
-				<tr><td><tt>keypass</tt></td><td>Password for the private key (if different).</td></tr>
-				<tr><td><tt>storepass</tt></td><td>Password for the key store.</td></tr>
-				<tr><td><tt>unsign</tt></td><td>Whether or not to strip any existing signatures before signing.  (Default is false)</td></tr>
-			</table>
-			</td></tr>
-			<tr><td><tt>&lt;feature&gt;</tt></td><td>Nested elements specifying features IUs to process 
-			  (see <a href="#installable_units">above</a>,  the <i>query</i> attribute is not supported here).  
-			  If no features or plug-ins are specified, the entire repository is processed.</td></tr>
-			<tr><td><tt>&lt;plugin&gt;</tt></td><td>Nested elements specifying plugins IUs to process 
-			  (see <a href="#installable_units">above</a>, the <i>query</i> attribute is not supported here).  
-			  If no features or plug-ins are specified, the entire repository is processed.</td></tr>
-		</table>
-	</td></tr>
-</table>		
-<br>
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><tt>p2.remove.iu</tt></b></td></tr>
-	<tr><td><p>Remove Installable Units from the given metadata and artifact repositories.  The provided repositories must be modifiable.</p></td></tr>
-	<tr><td><p>This task supports the following attributes and elements:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>&lt;repository&gt;</tt></td><td>Nested elements specifying metadata and artifact repositories to remove Installable Units from.  See <a href="#destination_repositories">destination repositories</a> above.  
-			A metadata repository is required, the artifact repository is optional.</td></tr>
-			<tr><td><tt>&lt;iu&gt;</tt></td><td>Nested IU elements, as outlined <a href="#installable_units">above</a>.  
-			  The installable units to remove.  Matching IUs are removed from the metadata repository, and all associated artifacts are removed from the artifact repository (if provided).</td></tr>
-		</table>
-	</td></tr>
-</table>		
-<br>
-<table cellspacing="1" cellpadding="2" width="95%" align="center">
-	<tr><td><b><tt>p2.composite.repository</tt></b></td></tr>
-	<tr><td><p>Create a composite repository</p></td></tr>
-	<tr><td><p>This task supports the following attributes and elements:</p>
-		<table border="5" cellspacing="0" cellpadding="1" width="95%" align="center">
-			<tr><td><tt>failOnExists</tt></td><td>Whether we should fail if the repository already exists.  (Default is false)</td></tr>
-			<tr><td><tt>validate</tt></td><td>A comparator-id.  Child repositories claiming to contain the same artifact are 
-			  compared using the given comparator.  These are extensions to the <i>org.eclipse.equinox.p2.artifact.repository.artifactComparators</i> 
-			  extension point.  Comparators provided by p2 are:
-				<ul>
-				<li><i>org.eclipse.equinox.p2.repository.tools.jar.comparator</i>: Compare jars.  Class files are disassembled and 
-				  compared for equivalence, properties and manifest files are compared as such, all other files are compared byte-for-byte.</li>
-				<li><i>org.eclipse.equinox.artifact.md5.comparator</i>: Compare the MD5 sums as recorded in the artifact repositories.</li>
-				</ul>
-			</td></tr>
-			<tr><td><tt>&lt;add&gt;</tt></td><td>A nested element containing a list of repositories to add to the composite. 
-			  See <a href="#source_repositories">source repositories</a> above.</td></tr>
-			<tr><td><tt>&lt;remove&gt;</tt></td><td>A nested element containing a list repositories to remove 
-			  from the composite. See <a href="#source_repositories">source repositories</a> above.</td></tr>
-		</table>
-	</td></tr>
-</table>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm
deleted file mode 100644
index d1a857a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Preference pages
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Preference pages</h2>
-<p>
-Once a plug-in has contributed extensions to the workbench user interface, it is common for
-the plug-in to allow the user to control some of the behavior of the plug-in through
-user preferences.
-</p>
-<p>
-The platform UI provides support for storing plug-in preferences and showing them to the user
-on pages in the workbench <b>Preferences</b> dialog. Plug-in preferences are key/value pairs, where the 
-key describes the name of the preference, and the value is one of several different types.  (See
-<a href="runtime_preferences.htm">Runtime preferences</a> for a detailed description of 
-the runtime preferences infrastructure.)</p>
-<p>How does a plug-in contribute a page for showing its preferences?  We will use the readme 
-tool example to see how it contributes a preference page to the
-workbench and then look at some of the underlying support for building preference pages.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm
deleted file mode 100644
index cbd20c0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_contribute.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Contributing a preference page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contributing a preference page</h3>
-<P > The <b><a href="../reference/extension-points/org_eclipse_ui_preferencePages.html"> 
-  org.eclipse.ui.preferencePages</a></b> extension point allows you to contribute 
-  pages to the general preferences
-  
-  (<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Preferences</b></a>)
-  
-  dialog. The preferences dialog presents a hierarchical list of user preference
-  entries. Each entry displays a corresponding preference page when selected.</P>
-<P >
-The readme tool uses this extension point to add the Readme Example preferences page.</P>
-<pre>   &lt;extension
-      point = &quot;org.eclipse.ui.preferencePages&quot;&gt;
-       &lt;page id=&quot;org.eclipse.ui.examples.readmetool.Page1&quot;
-	    class=&quot;org.eclipse.ui.examples.readmetool.ReadmePreferencePage&quot;
-            name=&quot;%PreferencePage.name&quot;&gt;
-       &lt;/page&gt;
-   &lt;/extension&gt;</pre>
-<P >
-This markup defines a preference page named &quot;Readme Example&quot; which is implemented by the class
-<b>ReadmePreferencePage</b>. The class must implement the
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchPreferencePage.html"> IWorkbenchPreferencePage</a></b> interface.</P>
-<P > The workbench uses the core runtime's preference mechanisms to access all nodes in the preference tree 
-and their corresponding pages. This list can be initialized from information in the preferences service
-without running any plug-in code.</P>
-<P >
-<img src="images/preferences.png" alt="Workbench preferences page" border="0"></P>
-<P >
-The &quot;Readme Example&quot; preference is added to the top level of the
-preference tree on the left.&nbsp; Why? Because a preference page contribution will be added as a root of the tree unless a
-<b> category</b> attribute is specified. (The name <b> category</b> is somewhat misleading.
-Perhaps a better name is
-<b>path</b>.) The <b> category</b> attribute
-specifies the id (or a sequence of ids from the root) of the parent page. For example, the following markup would create a second readme tool preference page, &quot;Readme Example Child Page,&quot; as a child of the original page.</P>
-<pre>
-   &lt;extension
-      point = &quot;org.eclipse.ui.preferencePages&quot;&gt;
-      &lt;page
-         id=&quot;org.eclipse.ui.examples.readmetool.Page1&quot;
-         class=&quot;org.eclipse.ui.examples.readmetool.ReadmePreferencePage&quot;
-         name=&quot;%PreferencePage.name&quot;&gt;
-      &lt;/page&gt;
-      &lt;page
-         id=&quot;org.eclipse.ui.examples.readmetool.Page2&quot;
-         class=&quot;org.eclipse.ui.examples.readmetool.ReadmePreferencePage2&quot;
-         name=&quot;Readme Example Child Page&quot;
-         category=&quot;org.eclipse.ui.examples.readmetool.Page1&gt;
-      &lt;/page&gt;
-   &lt;/extension&gt;
-</pre>
-
-
-<P >
-Once the user selects the entry for a preference page in the tree on the left,
-the workbench will create and display a preference page using the <b> class</b> specified in the
-extension definition.&nbsp; This action is what activates the plug-in (if it
-wasn't already activated due to another user operation).</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm
deleted file mode 100644
index 43ed308..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_fieldeditors.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Field editors
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>
-Field editors</H3>
-<P >
-The implementation of a preference page is primarily SWT code.&nbsp; SWT code is
-used to create the preference page controls, set the values of the controls, and
-retrieve the values of the controls. The
-<b><a href="../reference/api/org/eclipse/jface/preference/package-summary.html">org.eclipse.jface.preference</a></b> 
-package provides helper classes, called <b> field editors</b>, that create the widgets and implement the value setting 
-and retrieval code for the most common preference types. The platform provides field editors for displaying and updating 
-many value types, including booleans, colors, strings, integers, fonts, and file names.</P>
-<P >
- <b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html"> FieldEditorPreferencePage</a></b> implements a
-page that uses these field editors to display and store the preference values on the page.&nbsp;
- Instead of creating SWT controls to fill its contents, a <b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html"> FieldEditorPreferencePage</a></b> 
-subclass creates field editors to display the contents.&nbsp; All of the fields
- on the page must be implemented as field editors.&nbsp; The following is a
-snippet from the debug UI preferences page:</P>
-<pre>protected void createFieldEditors() {
-	addField(new BooleanFieldEditor(IDebugUIConstants.PREF_BUILD_BEFORE_LAUNCH, 
-		DebugPreferencesMessages.getString(&quot;DebugPreferencePage.auto_build_before_launch&quot;), 
-		SWT.NONE, getFieldEditorParent())); 
-	...	
-	String[][] perspectiveNamesAndIds = getPerspectiveNamesAndIds();
-	addField(new ComboFieldEditor(IDebugUIConstants.PREF_SHOW_DEBUG_PERSPECTIVE_DEFAULT,
-		DebugPreferencesMessages.getString(&quot;DebugPreferencePage.Default_perspective_for_Debug_2&quot;), //$NON-NLS-1$
-		perspectiveNamesAndIds,
-		getFieldEditorParent()));
-	...
-}</pre>
-<P >
-Each field editor is assigned the name of its corresponding preference key and the text label for the SWT
-control that it will create. The kind of control created depends on the type of field editor. For example, a boolean field editor creates a checkbox.</P>
-<P >
-Since the preference page is associated with a preference store (specified in the
-<b> doGetPreferenceStore</b> method), the code for storing the current values,
-for initializing the control values from the preference store, and for restoring the controls to
-their default values can all be implemented in the
-<b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html">FieldEditorPreferencePage</a></b>.</P>
-<P >
-The <b><a href="../reference/api/org/eclipse/jface/preference/FieldEditorPreferencePage.html"> FieldEditorPreferencePage</a></b> 
-will use a grid layout with one column as the default layout for field editor
-widgets.&nbsp; For special layout requirements, you can override the <b>createContents</b> method.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm
deleted file mode 100644
index ca1bd4b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prefs_implement.htm
+++ /dev/null

@@ -1,166 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Implementing a preference page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Implementing a preference page</h3>
-
-<h4>
-Defining the page</h4>
-<p>
-The JFace plug-in provides a framework for implementing wizards, preference pages, 
-and dialogs.  The implementation for these dialogs follows a common pattern.
-The contents of a page or dialog is defined by implementing a <b>createContents</b> 
-method that creates the SWT controls representing the page content.  This method
-should also add listeners for any events of interest. The page is responsible for 
-creating and returning the composite that will parent all of the controls in the page.
-The following snippet shows the highlights:</p>
-<pre>
-protected Control createContents(Composite parent)
-{
-	...
-	//composite_textField &lt;&lt; parent
-	Composite composite_textField = createComposite(parent, 2);
-	Label label_textField = createLabel(composite_textField, MessageUtil.getString(&quot;Text_Field&quot;));	 
-	textField = createTextField(composite_textField);
-	pushButton_textField = createPushButton(composite_textField, MessageUtil.getString(&quot;Change&quot;)); 
-
-	//composite_tab &lt;&lt; parent
-	Composite composite_tab = createComposite(parent, 2);
-	Label label1 = createLabel(composite_tab, MessageUtil.getString(&quot;Radio_Button_Options&quot;)); 
-
-	//
-	tabForward(composite_tab);
-	//radio button composite &lt;&lt; tab composite
-	Composite composite_radioButton = createComposite(composite_tab, 1);
-	radioButton1 = createRadioButton(composite_radioButton, MessageUtil.getString(&quot;Radio_button_1&quot;)); 
-	radioButton2 = createRadioButton(composite_radioButton, MessageUtil.getString(&quot;Radio_button_2&quot;)); 
-	radioButton3 = createRadioButton(composite_radioButton, MessageUtil.getString(&quot;Radio_button_3&quot;)); 
-
-
-	//composite_tab2 &lt;&lt; parent
-	Composite composite_tab2 = createComposite(parent, 2);
-	Label label2 = createLabel(composite_tab2, MessageUtil.getString(&quot;Check_Box_Options&quot;)); //$NON-NLS-1$
-
-	//
-	tabForward(composite_tab2);
-	//composite_checkBox &lt;&lt; composite_tab2
-	Composite composite_checkBox = createComposite(composite_tab2, 1);
-	checkBox1 = createCheckBox(composite_checkBox, MessageUtil.getString(&quot;Check_box_1&quot;)); 
-	checkBox2 = createCheckBox(composite_checkBox, MessageUtil.getString(&quot;Check_box_2&quot;)); 
-	checkBox3 = createCheckBox(composite_checkBox, MessageUtil.getString(&quot;Check_box_3&quot;)); 
-
-	initializeValues();
-
-	return new Composite(parent, SWT.NULL);
-}</pre>
-<p>
-Most of the code in this method is concerned with creating and laying out the controls, so we won't dissect it here.&nbsp;
-Here is what the corresponding page looks like:</p>
-<p>
-<img src="images/readmepreferences.png" alt="Readme tool preferences page" border="0"></p>
-<p>
-The other primary responsibility of a preference page is to react to the <b> performOk</b> message. Typically, this 
-method updates and stores the user preferences and, if necessary, updates any other plug-in objects to reflect the 
-change in preferences.  The <b>performDefaults</b> method is used to restore preferences to their
-default state when the user presses the <b>Restore Defaults</b>
-button.&nbsp;&nbsp;</p>
-<p>
-You may override <b>performApply</b> if you have additional processing when the
-user selects <b>Apply</b>.&nbsp; The default implementation is to call <b>performOk</b>.&nbsp;&nbsp;</p>
-<p>
-Preference pages should override the <b> doGetPreferenceStore()</b> method to return a preference store for 
-storing their values. </p>
-
-
-<h4>
-Plug-in preference store</h4>
-<p>Preference stores are a convenience mechanism for accessing and storing preference values in a
-plug-in class.  They provide plug-in level access to preferences that are actually stored using 
-the runtime preferences service.  <a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a> 
-defines a plug-in wide preference store that is maintained during the lifetime of the plug-in.  Your plug-in
-can add entries to this preference store and update the values as the user changes the settings in your preferences page.   
-Since preference stores use the platform preferences service, they will take care of saving preference values at the 
-appropriate scope and location, and initializing the preference store using the appropriate mechanisms.</p>
-<p>
-The following code in the <b> ReadmePreferencePage</b> obtains the preference store for the
-<b>ReadmePlugin</b>.</p>
-<pre>
-   protected IPreferenceStore doGetPreferenceStore() {
-      return ReadmePlugin.getDefault().getPreferenceStore();
-   }
-</pre>
-<p>
-Because <b> ReadmePlugin</b> extends the <b><a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"> AbstractUIPlugin</a></b> class, it automatically inherits a preference store. 
-This preference store is initialized using the platform preferences service. The only thing the <b>ReadmePlugin</b> has 
-to do is implement a method that initializes the preference controls to their default values. These values are used the 
-first time the preference page is shown or when the user presses the <b>Defaults</b> button in the preferences page.</p>
-<pre>
-protected void initializeDefaultPreferences(IPreferenceStore store) {
-	// These settings will show up when Preference dialog
-	// opens up for the first time.
-	store.setDefault(IReadmeConstants.PRE_CHECK1, true);
-	store.setDefault(IReadmeConstants.PRE_CHECK2, true);
-	store.setDefault(IReadmeConstants.PRE_CHECK3, false);
-	store.setDefault(IReadmeConstants.PRE_RADIO_CHOICE, 2);
-	store.setDefault(IReadmeConstants.PRE_TEXT, MessageUtil.getString(&quot;Default_text&quot;)); //$NON-NLS-1$
-}</pre>
-
-<blockquote><i>
-Note:&nbsp; If there are no preferences saved anywhere for a plug-in, the plug-in will get an empty preference
-store.</i></blockquote>
-<h4>
-Retrieving and saving preferences</h4>
-<p>
-Once you've associated your plug-in's preference store with your preference page, you can implement the logic for retrieving and saving the preferences.</p>
-<p>
-Preference pages are responsible for initializing the values of their controls using the preferences settings from the preference store. This
-process is similar to initializing dialog control values from dialog settings. The
-<b> ReadmePreferencePage</b> initializes all of its controls in a single method,
-<b>initializeValues</b>, which is called from its <b> createContents</b> method.</p>
-<pre>private void initializeValues() {
-	IPreferenceStore store = getPreferenceStore();
-	checkBox1.setSelection(store.getBoolean(IReadmeConstants.PRE_CHECK1));
-	checkBox2.setSelection(store.getBoolean(IReadmeConstants.PRE_CHECK2));
-	checkBox3.setSelection(store.getBoolean(IReadmeConstants.PRE_CHECK3));
-	...
-}</pre>
-<p>
-When the <b>OK</b> (or <b>Apply</b>) button is pressed, the current values of the controls on the preference page should be stored back into the
-preference store. The
-<b> ReadmePreferencePage</b> implements this logic in a separate method,
-<b>storeValues</b>.</p>
-<pre>
-private void storeValues() {
-	IPreferenceStore store = getPreferenceStore();
-	store.setValue(IReadmeConstants.PRE_CHECK1, checkBox1.getSelection());
-	store.setValue(IReadmeConstants.PRE_CHECK2, checkBox2.getSelection());
-	store.setValue(IReadmeConstants.PRE_CHECK3, checkBox3.getSelection());
-	...
-}</pre>
-<p>
-When the user presses the <b>Defaults</b> button, the platform will restore all preference store values to the default values specified in the plug-in class. However, your preference page is responsible for reflecting these default values
-in the controls on the preference page. The
-<b> ReadmePreferencePage</b> implements this in <b>initializeDefaults</b>.</p>
-<pre>
-   private void initializeDefaults() {
-      IPreferenceStore store = getPreferenceStore();
-      checkBox1.setSelection(store.getDefaultBoolean(IReadmeConstants.PRE_CHECK1));
-      checkBox2.setSelection(store.getDefaultBoolean(IReadmeConstants.PRE_CHECK2));
-      checkBox3.setSelection(store.getDefaultBoolean(IReadmeConstants.PRE_CHECK3));
-      ...
-   }</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm
deleted file mode 100644
index 1d88022..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_contribute.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing a property page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contributing a property page</h3>
-<P >
-You can contribute a property page for an object by using the
-<a href="../reference/extension-points/org_eclipse_ui_propertyPages.html"> <b> org.eclipse.ui.propertyPages</b></a> extension point.
-An object's property page is invoked using the <b>Properties </b>menu in any
-view that shows objects, such as the resource navigator view.&nbsp; This menu is available when a single
-object is
-selected.&nbsp;</P>
-<P >The readme tool contributes two property pages.</P>
-<pre>
-&lt;extension
-     point = &quot;org.eclipse.ui.propertyPages&quot;&gt;
-        &lt;page
-           id=&quot;org.eclipse.ui.examples.readmetool.FilePage&quot;
-           name=&quot;%PropertiesPage.filePage&quot;
-	   objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeFilePropertyPage&quot;
-           nameFilter=&quot;*.readme&quot;&gt;
-        &lt;/page&gt;
-         &lt;page
-            id=&quot;org.eclipse.ui.examples.readmetool.FilePage2&quot;
-            name=&quot;%PropertiesPage.filePage2&quot;
- 	   objectClass=&quot;org.eclipse.core.resources.IFile&quot;
- 	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeFilePropertyPage2&quot;
-            nameFilter=&quot;*.readme&quot;&gt;
-         &lt;/page&gt;
-  &lt;/extension&gt;
-</pre>
-<P >When you define a property page, you specify the <b>objectClass</b> for
-which this page is valid.&nbsp; Objects of this class will include your page
-when the properties are shown.&nbsp; You may optionally supply a <b>nameFilter</b>
-that further refines the class.&nbsp; In the readme tool example, both pages are contributed for objects of type <b><a href="../reference/api/org/eclipse/core/resources/IFile.html"> IFile</a></b> with a
-<b>.readme</b> file extension. </P>
-<P >Property pages are not limited to workbench resources.&nbsp; All objects
-showing up in the workbench (even domain-specific objects created by other
-plug-ins) may have property pages.&nbsp; Any plug-in may register property pages
-for any object type. </P>
-<P >
-Property pages look a lot like preference pages, except there is no hierarchy or categorization of property pages. In the dialog below, both readme property pages appear in the main list of pages.</P>
-<P >
-<img src="images/readmeproperties.png" alt="Properties dialog with readme entries" border="0" ></P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm b/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm
deleted file mode 100644
index 0cca916..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/preferences_prop_implement.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Implementing a property page
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Implementing a property page</h3>
-<P >
-When the workbench creates and launches a properties page, it sets the selected resource into the page. The page can use the
-<b> getElement()</b> method to obtain its element, an <b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html">IAdaptable</a></b>. </P>
-<P >
-The pattern for creating property pages is similar to that of preference pages, so we will only focus on what is different. Property pages show information about their element. This information can be obtained
-by accessing the element in order to query or compute the relevant
-information.&nbsp; The information can also be stored and retrieved from the
-resource's properties.</P>
-<P >
-The <b> ReadmeFilePropertyPage</b> computes most of its information using its element. The following snippet shows how the number of sections is computed and displayed in a label.</P>
-<pre>
-   ...
-   IResource resource = (IResource) getElement();
-   ...
-   IAdaptable sections = getSections(resource);
-   if (sections instanceof AdaptableList) {
-      AdaptableList list = (AdaptableList)sections;
-      label = createLabel(panel, String.valueOf(list.size()));
-   ...
-</pre>
-<P >
-When a property is computed, there is no need for corresponding logic to save the value, since the user cannot update this value.</P>
-<P >
-Properties pages are commonly used for viewing and for setting the
-application-specific&nbsp; properties of a resource.
-(See <a HREF="resInt_properties.htm" CLASS="XRef">Resource properties</a>  for a
-discussion of session and persistent properties.)&nbsp;
-Since the property page knows its resource, the resources API can be used in the page to initialize control values or
-to set new property values based on user selections in the properties page.</P>
-<P >
-The following snippet shows a checkbox value being initialized from a property on a property page's element.</P>
-<pre>
-   private void initializeValues() {
-      ...
-      IResource resource = (IResource) getElement();
-      label.setText(resource.getPersistentProperty(&quot;MyProperty&quot;));
-      ...
-   }
-</pre>
-<P >
-The corresponding code for saving the checkbox value back into the property looks like this:</P>
-<pre>
-   private void storeValues() {
-      ...
-      IResource resource = (IResource) getElement();
-      resource.setPersistentProperty(&quot;MyProperty&quot;, label.getText());
-      ...
-   }
-</pre>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product.htm b/bundles/org.eclipse.platform.doc.isv/guide/product.htm
deleted file mode 100644
index dafdd92..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Packaging and delivering Eclipse based products</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Packaging and delivering Eclipse based products</H1>
-<p>
-  The Eclipse platform is designed so you can add plug-ins that provide function
-  for the software development tools community.&nbsp; Commercial software
-  vendors can build, brand, and package products using the platform as a base
-  technology.&nbsp; These products can be sold and supported commercially.&nbsp;
-</p>
-<p>
-  The Eclipse SDK can be downloaded and used as a Java IDE and Eclipse plug-in
-  development tool, but it is not marketed as a commercial product.&nbsp; The
-  platform provides the raw ingredients for a product without a box, label, or
-  price tag.&nbsp; It defines a file and directory structure that lets you
-  easily customize the platform's about dialog and splash screen to brand your
-  product.</p>
-<p>
-  The license governing the Eclipse platform gives you a lot of freedom over how
-  to build and configure a product.&nbsp; However, Eclipse based products will
-  coexist more easily on a user's system if the products use similar standards
-  for packaging, configuring, and installing their products.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm
deleted file mode 100644
index 8a22f4c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_config_install.htm
+++ /dev/null

@@ -1,137 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Product installation guidelines</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Product installation guidelines</h2>
-<p>The platform provides standard tools for updating and extending
-products.&nbsp; In order to participate in the platform mechanisms for updating
-and extending products, your packaged product should follow the following
-guidelines.&nbsp; This will allow your product to peacefully
-coexist with, or even enhance, other Eclipse based products.</p>
-<p>Consider again the sample directory structure for the acmeweb product:</p>
-<pre>acmeweb/
-	acmeweb.exe
-	eclipse/	
-		.eclipseproduct
-		artifacts.xml	
-		eclipse.exe	
-		install.ini	
-		.config/	
-			platform.cfg
-		jre/
-		dropins/
-		features/	
-			com.example.acme.acmefeature_1.0.0/
-				feature.xml
-			...
-		plugins/
-			com.example.acme.acmefeature_1.0.0/
-				plugin.xml
-				about.ini
-				about.html
-				about.mappings
-				about.properties
-				acme.png
-				plugin_customization.ini
-				splash.bmp
-				welcome.xml
-			com.example.acme.acmewebsupport_1.0.0/
-			...
-		links/
-			...
-		p2/
-			...</pre>			
-
-<p>Where did these files come from?&nbsp; Let's look at the product content from
-the perspective of the development team.&nbsp; The installed files can be
-grouped into five main categories:</p>
-<ul>
-  <li>top-level product files (such as the acmeweb.exe)</li>
-  <li>product features and plug-ins</li>
-  <li>the Eclipse platform itself (this includes the contents of the p2 and configuration folder)</li>
-  <li>the Java runtime environment (JRE)</li>
-  <li>files generated by the installation process itself</li>
-</ul>
-<p>A proper installation script will produce the appropriate directory structure
-by doing the following:</p>
-<ul>
-  <li>allow the user to specify the top level directory of the install (such as <b>c:\acmeweb.&nbsp;
-    </b>We will refer to it as <b>acmeweb</b> for the remaining steps.)</li>
-  <li>ensure that a product is not already installed in the location</li>
-  <li>copy the files as follows:
-    <ul>
-      <li>Top-level product files are copied to <b>acmeweb</b></li>
-      <li>Eclipse files are copied to <b>acmeweb/eclipse </b>using the expected
-        feature and plugin directory structures</li>
-      <li>JRE files are copied to <b>acmeweb/eclipse/jre</b>.&nbsp; If a JRE is
-        already located elsewhere, then the application shortcut should be setup
-        to invoke eclipse with the <b>-vm</b> command line argument so that the
-        location of the JRE is known by the platform</li>
-      <li>Product features and plug-ins are copied to <b>acmeweb/eclipse/features</b>
-        and <b>acmeweb/eclipse/plugins</b></li>
-      <li>Platform configuration information is copied to <b>acmeweb/eclipse/configuration</b></li>
-      <li>Platform update support information is copied to <b>acmeweb/eclipse/p2</b></li>      
-    </ul>
-  </li>
-  <li>create a marker file, <b>.eclipseproduct</b>, in <b>acmeweb/eclipse</b>.&nbsp;
-    The marker file is a <b>java.io.Properties</b> format file that indicates
-    the name, id, and version of the product.</li>
-  <li>store any necessary install info (user, license, date) that is to be shown
-    in the about dialog in <b>acmeweb/eclipse/plugins/com.example.acmefeature_1.0.0/about.mappings</b></li>
-  <li>if the primary feature mechanism (pre R3.0) is used to define the product, replace the 
-  <b>acmeweb/eclipse/install.ini</b> with one that sets the property <b>feature.default.id
-    </b>to the product's primary feature</li>
-  <li>invoke the product executable using the <b>-initialize</b> option.&nbsp;
-    This causes the platform to quietly perform all time-consuming first-time
-    processing and cache the results, so that when the user starts the product
-    it comes up promptly in an open-for-business state.</li>
-</ul>
-<h3>Multi-user issues</h3>
-<p>When a product is installed with the intention of sharing the installation among multiple users,
-care must be taken to separate individual user's data (such as the <b>workspace</b>
-directory) from the shared product install directory.</p>
-<h3>Uninstall issues</h3>
-<p>When a product is uninstalled, the following concepts are important.</p>
-<ul>
-  <li><b>all</b> files in the <b>eclipse/features</b> and <b>eclipse/plugins</b>
-    directories should be removed, even if they weren't originally installed by
-    the installation program.&nbsp; This ensures that files added by the
-    platform update manager are removed when the product is
-    removed.</li>
-  <li>except for the point above, <b>only</b> those files installed by the
-    installation program in other directories should be removed.&nbsp; It is
-    important to preserve any important data, such as the <b> workspace</b>
-    directory, so
-    that reinstalling the product after an uninstall will produce expected
-    results.</li>
-</ul>
-<h3>Reinstalling the product</h3>
-<p>When the product is already installed, the installer should allow a service
-update or upgrade if one is available.&nbsp; The existence of the product can be
-confirmed by looking for <b>acmeweb/eclipse/.eclipseproduct</b>.&nbsp; The
-information in this marker file can be used to confirm with the user that the
-correct product is being updated.&nbsp; The availability of updates can be
-confirmed with pattern matches against feature names.&nbsp; For example, the
-presence of <b>acmeweb/eclipse/plugins/com.example.acmefeature_1.0.1 </b>would
-indicate that the 1.0.1 version update had already been applied to the product.</p>
-<p>Once the validity of the reinstall is established, the install program should
-copy or replace files as needed.&nbsp; If the version of the underlying Eclipse
-platform has not changed, there is a good chance that complete directories can
-be ignored.&nbsp; The version numbers appended to the platform features and
-plugins can be used to determine whether any changes underneath a plug-in or
-feature's directory are necessary.&nbsp; </p>
-<p>Additional information on installing products can be found in <a href="../reference/misc/eclipse-install.html">How
-to write an Eclipse installer</a>.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm
deleted file mode 100644
index b59f081..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_configproduct.htm
+++ /dev/null

@@ -1,116 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Customizing a product</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Customizing a product</h3>
-<p>There are many customizable aspects of a product, such as its splash screen,
-  about dialog text,  window icons, etc. Most of these customizations are defined
-  in the contribution to the <a href="../reference/extension-points/org_eclipse_core_runtime_products.html"><b>org.eclipse.core.runtime.products</b></a>
-extension point.</p>
-<p>
-Let's look at how some of the more common customizable elements are defined.</p>
-<h3>About dialogs</h3>
-<p>The platform &quot;about&quot; dialog is shown whenever the user selects
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help &gt; About</b></a>
-
-in the workbench menu.&nbsp;&nbsp;</p>
-<p><img src="images/about.png" alt="About dialog" border="0" ></p>
-<p>The upper part of the about dialog shows product level information while the
-  lower part details the features (if any) and plug-ins installed.&nbsp; The
-  feature details (branding if you will) are supplied using<b> about.ini</b>, <b>about.properties</b> and <b>about.html</b>
-files in the plug-in associated with the feature.&nbsp; This
-information is displayed when the user requests feature details and selects a
-particular feature.</p>
-<p>The product branding (top half of the dialog) is specify by extension properties
-that describe the text and images that are shown in this dialog.
-For example, the following extract from the Eclipse Platform product declaration.</p>
-<pre>	&lt;property
-		name="aboutText"
-		value="%aboutText"/&gt;
-	&lt;property
-		name="aboutImage"
-		value="icons/eclipse_lg.png"/&gt;
-	&lt;/product&gt;</pre>
-<ul>
-  <li><b>aboutText</b> specifies the text to show in the about dialog</li>
-  <li><b>aboutImage</b> specifies an image that should be used in the about dialog.  Large
-  images will be shown by themselves, and smaller images will be shown along with the about
-  text.</li>
-</ul>
-<p>See <b><a href="../reference/api/org/eclipse/ui/branding/IProductConstants.html">IProductConstants</a></b>
-for more information about these properties.
-</p>
-<h3>Window images</h3>
-<p>A 16x16 pixel color image can be used to brand windows created by the
-product.&nbsp; It will appear in the upper left hand corner of product
-windows.&nbsp; It is specified in the <b>windowImage</b> attribute in the 
-products extension definition.  Alternatively, the <b>windowImages</b> attribute
-can be used to describe an array of images of different sizes that should be used in the
-upper left hand corner.</p>
-<pre>	&lt;property
-		name="windowImages"
-		value="icons/eclipse.png,icons/eclipse32.png"/&gt;</pre>
-<p>The <b>windowImages</b> property supercedes the <b>windowImage</b> property if
-both are specified.</p>
-<h3>Welcome page</h3>
-<p>Products using the Eclipse 2.1 welcome page mechanism can specify the name and location
-of their welcome page file in the <b>welcomePage</b> property.</p>
-<pre>	&lt;property
-		name="welcomePage"
-		value="$nl$/welcome.xml"/&gt;</pre>
-<p>Use of this property is 
-now discouraged in favor of the <b><a href="../reference/extension-points/org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></b>
-extension point.  See <a href="ua_intro.htm">Welcome/Intro support</a> for more
-detail about the new welcome/intro mechanisms.</p>
-<h3><a name="preferences"></a>Preferences defaults</h3>
-
-<p>The <b>preferenceCustomization</b> property can be used to specify a file containing
-default preference values for the product.</p>
-<pre>	&lt;property
-		name="preferenceCustomization"
-		value="plugin_customization.ini"/&gt;</pre>
-<p>This file is a <b>java.io.Properties</b> format file.
-  Typically this file is used to set the values for preferences that are published
-  as part of a plug-in's public API.&nbsp; That is, you are taking a risk if you
-  refer to preferences that are used by plug-ins but not defined formally in the
-  API.&nbsp;&nbsp;</p>
-<h3>Splash screens</h3>
-<p>The product splash screen is specified in the <tt>config.ini</tt> which is
-  located underneath the product's <tt>configuration</tt> directory. The <b>osgi.splashPath</b> property
-  in this file describes places to search for a file called <b>splash.bmp</b>.
-  The <strong>osgi.splashLocation </strong>property identifes a complete and
-  exact path to the splash screen file to use. Specifying a splash path allows
-  for locale specific splash screens to be used as the given search path can
-  indicate several plug-ins or fragments to search as well as <code>$nl$</code> style paths.
-  See the
-  platform
-  SDK's <tt>config.ini</tt> file
-  for a complete description of properties that can be configured in this file.
-  The image should be supplied in 24-bit color BMP format (RGB format) and should
-  be approximately 500x330 pixels in size.</p>
-  <p>The location, size, and color of the progress bar and progress message shown
-  in the splash screen during startup can be configured using the properties
-  <b>startupProgressRect</b>, <b>startupMessageRect</b>, and
-  <b>startupForegroundColor</b>. See
-  <b><a href="../reference/api/org/eclipse/ui/branding/IProductConstants.html">IProductConstants</a></b>
-  for more information about these properties.  Note that by default, no progress
-  will be reported at startup.  To enable startup progress reporting, set the following
-  preference to <b>true</b>, for example in the preference customization file:
-  <b><a href="../reference/api/org/eclipse/ui/IWorkbenchPreferenceConstants.html#SHOW_PROGRESS_ON_STARTUP">IWorkbenchPreferenceConstants.SHOW_PROGRESS_ON_STARTUP</a></b></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def.htm
deleted file mode 100644
index ba7fd07..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Products and features</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Products and features</h2>
-<p>An Eclipse based <b>product</b> is a stand-alone program built with the
-Eclipse platform.  A product may optionally be packaged and delivered as one or more
-<b>features</b>, which are simply groupings of plug-ins that are managed as a single entity by
-the Eclipse update mechanisms.</p>
-<p>Products include all the code and plug-ins needed to run them.&nbsp; This
-includes a Java runtime environment (JRE) and the Eclipse platform code.&nbsp;
-The plug-in code, JRE, and Eclipse platform are typically installed with a
-product-specific installation program.&nbsp; Product providers are free to use
-any installation tool or program that is appropriate for their needs.&nbsp; </p>
-<p>Once installed, the user launches the product and is presented with an
-Eclipse workbench configured specifically for the purpose supported by the
-product, such as web development, C++ program development, or any other
-purpose.&nbsp; The platform makes it easy to configure labels, about dialogs,
-graphics, and splash screens, so that the user has no concept of a platform
-workbench, but instead views the workbench as the main window of the product
-itself.</p>
-<p>The top level directory structure of such a product looks something like this
-for a hypothetical product called &quot;AcmeWeb&quot; that has been installed on
-a Windows platform:</p>
-<pre>acmeweb/
-	acmeweb.exe		<i>(product executable)</i>
-	eclipse/		<i>(directory for installed Eclipse files)</i>
-		.eclipseproduct	<i>(marker file)</i>
-		artifacts.xml (bundle pool contents)
-		eclipse.exe
-		eclipse.ini	
-		configuration/	
-			config.ini
-		dropins/
-		jre/
-		features/	<i>(installed features if any)</i>
-			com.example.acme.acmefeature_1.0.0/
-				feature.xml
-			...
-		plugins/
-			org.eclipse.equinox.launcher_1.0.0.v20070530.jar
-			org.eclipse.equinox.launcher.win32.win32.x86/
-			com.example.acme.acmefeature_1.0.0/
-				plugin.xml
-				about.ini
-				about.html
-				about.mappings
-				about.properties
-				acme.png
-				splash.jpg
-			com.example.acme.acmewebsupport_1.0.0/
-			...
-		links/
-			...
-		p2/
-			...</pre>
-<p>There are actually two ways of defining a product in Eclipse.  The preferred
-  mechanism is to
-use the <a href="product_def_extpt.htm">products extension point</a>. 
-This extension point allows you to define your product and customize
-branding such as splash screens, window icons, and
-the like.</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm
deleted file mode 100644
index 6ee6810..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_extpt.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Products extension point</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Products extension point</h3>
-<p>The preferred mechanism for defining a product based on the Eclipse platform
-  is to contribute to the
-<a href="../reference/extension-points/org_eclipse_core_runtime_products.html"><b>org.eclipse.core.runtime.products</b></a>
-extension point.  To do this, a plug-in simply declares the name and id of its
-product,
-as
-well as the id of the application extension that should be run when the product
-is
-invoked. This is the technique used by the Eclipse
-platform itself in defining the Eclipse product.  Here is the extension definition
-found in <b>org.eclipse.platform</b>:</p>
-<pre>&lt;extension id="ide" point="org.eclipse.core.runtime.products"&gt; 
-	&lt;<b>product name="%productName" application="org.eclipse.ui.ide.workbench" description="%productBlurb"</b>&gt; 
-		&lt;property name="windowImages" value="eclipse.png,eclipse32.png"/&gt; 
-		&lt;property name="aboutImage" value="eclipse_lg.png"/&gt; 
-		&lt;property name="aboutText" value="%productBlurb"/&gt; 
-		&lt;property name="appName" value="Eclipse"/&gt; 
-		&lt;property name="preferenceCustomization" value="plugin_customization.ini"/&gt; 
-	&lt;/product&gt; 
-&lt;/extension&gt; </pre>
-A product extension is defined whose <b>application</b> id is "org.eclipse.ui.ide.workbench".
-This is the application id defined by the plug-in <b>org.eclipse.ui.ide</b> in
-its
-contribution to the <a href="../reference/extension-points/org_eclipse_core_runtime_applications.html"><b>org.eclipse.core.runtime.applications</b></a>
-extension point.
-
-<pre>
-&lt;extension
-	<b>id="workbench"</b>
-	point="org.eclipse.core.runtime.applications"&gt;
-	&lt;application&gt;
-		&lt;run
-			class="org.eclipse.ui.internal.ide.IDEApplication"&gt;
-		&lt;/run&gt;
-	&lt;/application&gt;
-&lt;/extension&gt; 
-</pre>
-<p>
-This extension is defined with the same id that is referenced in the <b>application</b> property
-of the product extension. (The fully qualified name, with plug-in prefix, is
-used when referring to the
-application id from the other plug-in.)  Using this mechanism, a separate plug-in
-can define all of the product-specific branding, and then refer to an existing
-plug-in's application as the application that
-is actually run when the product is started.
-</p>
-<p>
-In addition to the application, the <a href="../reference/extension-points/org_eclipse_core_runtime_products.html"><b>org.eclipse.core.runtime.products</b></a>
-extension describes product customization properties that are used to configure the product's branding information.
-This information is described as named properties.  Let's look again at that portion of the markup for the 
-platform plug-in.</p>
-<pre>	&lt;property name="windowImages" value="eclipse.png,eclipse32.png"/&gt; 
-	&lt;property name="aboutImage" value="eclipse_lg.png"/&gt; 
-	&lt;property name="aboutText" value="%productBlurb"/&gt; 
-	&lt;property name="appName" value="Eclipse"/&gt; 
-	&lt;property name="preferenceCustomization" value="plugin_customization.ini"/&gt; </pre>
-The possible property names that are honored by the platform for product customization are defined in
-<b><a href="../reference/api/org/eclipse/ui/branding/IProductConstants.html">IProductConstants</a></b>.
-See the javadoc for a complete description of these properties and their values.  We'll look at these
-further in <a href="product_configproduct.htm">Customizing a product</a>.
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm
deleted file mode 100644
index 538d9fd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_feature.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Features</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Features</h3>
-<p>A <b>feature</b> is a way of grouping and describing different functionality
-that makes up a product. Grouping plug-ins into features allows the product to be
-installed and updated using the Eclipse update server and related support.</p>  
-<p>Features do not contain any code.&nbsp; They merely describe a set of
-plug-ins that provide the function for the feature and information about how to
-update it. Features are packaged in a <a href="../reference/misc/feature_archive.html">feature
-archive</a> file and described using a <a href="../reference/misc/feature_manifest.html">feature
-manifest file</a>, feature.xml. The following is the first part of the manifest for
-the platform feature:</p>
-<pre>
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;feature
-      id="org.eclipse.platform"
-      label="%featureName"
-      version="3.3.0"
-      provider-name="%providerName"
-      image="eclipse_update_120.jpg"&gt;
-
-   &lt;description&gt;
-      %description
-   &lt;/description&gt;
-
-   &lt;license url="%licenseURL"&gt;
-      %license
-   &lt;/license&gt;
-
-   &lt;url&gt;
-      &lt;update label="%updateSiteName" url="http://update.eclipse.org/updates/3.3"/&gt;
-      &lt;discovery label="%updateSiteName" url="http://update.eclipse.org/updates/3.3/"&gt;
-   &lt;/url&gt;
-
-   &lt;plugin
-         id="org.apache.ant"
-         download-size="0"
-         install-size="0"
-         version="1.6.1"/&gt;
-
-   &lt;plugin
-         id="com.jcraft.jsch"
-         download-size="0"
-         install-size="0"
-         version="0.1.31"
-         unpack="false"/&gt;
-	...
-&lt;/feature&gt;
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm
deleted file mode 100644
index 5ad9bcf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_nl.htm
+++ /dev/null

@@ -1,128 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Locale specific files</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Locale specific files</h2>
-<p>Fragments are a convenient way to package national language
-translations.&nbsp; Let's look more closely at the directory structure used for
-installing locale-specific translation files.&nbsp; This directory structure is
-used regardless of whether the translated files are packaged in a fragment or
-delivered in the original plug-in.</p>
-<p>There are three mechanisms for locating locale specific files in a
-plug-in.&nbsp;&nbsp;</p>
-<ul>
-  <li><b>Platform core mechanism</b> (the platform's runtime locale-specific
-    sub-directory search)</li>
-  <li><b>Java resource bundles</b> (java.util.ResourceBundle)</li>
-  <li><b>The plugin.properties mechanism</b> (Translating values from the plugin.xml files)</li>
-</ul>
-<p>It is important to understand which mechanism is used to access any given
-file that must be translated so that you'll know what to name the file and where
-to put it in the file system relative to the plug-in.</p>
-<h4><a name="platform">Platform core mechanism</a></h4>
-<p>The platform core defines a directory structure that uses locale-specific
-subdirectories for files that differ by locale.&nbsp; Translated files are
-placed in a directory called <b>nl</b> under the plug-in.&nbsp; For example, the
-following install tree shows a trivial (no code) plug-in with locale-specific
-translations of its <b>about.properties</b> file.&nbsp; The various translations
-are shown as coming from a plug-in fragment rather than the plug-in
-itself.&nbsp; This is typical for shipping translations separately from the
-base, but you could also place the <b>nl</b> sub-directory under the plug-in
-itself.</p>
-<pre>acmeweb/
-  eclipse/
-    plugins/
-      com.example.acme.acmewebsupport_1.0.0/
-        plugin.xml
-        about.properties    <i>(default locale)</i>
-      com.example.acme.fragmentofacmewebsupport_1.0.0/
-        fragment.xml   <i>(a fragment of com.example.acme.acmewebsupport 1.0.0)</i>
-        nl/
-          fr/
-            about.properties  <i>(French locale)</i>
-            CA/
-              about.properties  <i>(French Canadian locale)</i>
-            FR/
-              EURO/
-                about.properties <i>(French France Euros)</i>
-          en/
-            about.properties  <i>(English locale)</i>
-            CA/
-              about.properties  <i>(English Canadian locale)</i>
-            US/
-              about.properties <i>(English US locale)</i>
-         de/
-            about.properties <i>(German locale)</i> </pre>
-<p>The files to be translated are not contained in JAR files.&nbsp; Each file
-should have exactly the same file name, but be located in subdirectories
-underneath the <b>nl</b> sub-directory in the fragment's (or plug-in's) root.</p>
-<p>Only the most specific file is accessed at runtime.&nbsp; The file paths are
-searched as part of the <a href="../reference/api/org/eclipse/core/runtime/Platform.html"><b>Platform.find</b></a>, <a href="../reference/api/org/eclipse/core/runtime/IPluginDescriptor.html"><b>IPluginDescriptor.find</b></a>
-and <b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin.find</a></b>
-mechanism.&nbsp; For example, suppose the default locale is <b>en_CA</b>,
-and a plug-in searches for the <b>about.properties</b> as follows:</p>
-<pre>somePlugin.find(&quot;$nl$/about.properties&quot;);</pre>
-<p>The method will return a URL corresponding to the first place <b>about.properties</b> is found according to the following
-order:</p>
-<pre>com.example.acme.acmewebsupport_1.0.0/nl/en/CA/about.properties
-com.example.acme.fragmentofacmewebsupport_1.0.0/nl/en/CA/about.properties
- ...  		&lt;any other fragments&gt;
-com.example.acme.acmewebsupport_1.0.0/nl/en/about.properties
-com.example.acme.fragmentofacmewebsupport_1.0.0/nl/en/about.properties
- ...
-com.example.acme.acmewebsupport_1.0.0/about.properties
-com.example.acme.fragmentofacmewebsupport_1.0.0/about.properties</pre>
-<p>This mechanism is used by plug-ins to search for well known file names inside
-other plug-ins.&nbsp; This includes the following well known file names:</p>
-<ul>
-  <li><b>preferences.properties</b>&nbsp; (externalized strings for plug-in
-    -specific preference default overrides)</li>
-  <li><b>about.properties</b>&nbsp; (externalized strings for feature
-    &quot;about&quot; information)</li>
-  <li><b>plugin_customization.properties</b>&nbsp; (externalized strings for
-    product-specific preference default overrides)</li>
-  <li><b>splash.bmp</b>&nbsp; (product-specific splash screens)</li>
-</ul>
-<blockquote>
-  <p><i>(Note:&nbsp; The <b>plugin.properties</b> and <b>fragment.properties </b>are
-  conspicuously absent from this list. They are treated in a sightly different way described below.)</i></p>
-</blockquote>
-<h4>Java resource bundles</h4>
-<p>The standard Java handling of property resource bundles is used for other
-files.&nbsp; Translated files are contained in a JAR file, with each properties
-file having a locale-specific name, such as &quot;<b>message_en_CA.properties</b>&quot;.&nbsp;
-The files are in package-specific subdirectories and may appear in the plug-in
-itself or one of its fragments.&nbsp; Each translated properties file may be
-partial since lookup of keys accesses a well-defined chain of properties files.</p>
-
-<h4>The plugin.properties mechanism</h4>
-The mechanism used to translate plugin.properties files uses the Java resource bundles naming convention. However the files must be located in the root 
-of the plug-in or in the root of a fragment of this plug-in. 
-The same rules apply to the translation of MANIFEST.MF.
-
-<h3>Defining NL fragments</h3>
-<p>The shape of NL fragments has evolved slightly since 2.1. 
-Previously all translation files (including the plugin.properties) were provided in a jar. 
-This was inconsistent since the plugin.properties file was provided at the root of the plug-in.
-<br>
-To adapt your NL fragment to the new model, remove the plugin.properties translation files from the jar and put them at the root of the fragment as siblings of fragment.xml.
-For example, the new shape of the NL fragment for org.eclipse.ui.workbench is the following:</p>
-<pre>  org.eclipse.ui.workbench.nl/
-     fragment.xml
-     plugin_fr.properties
-     plugin_pt_BR.properties
-     ...
-     nl1.jar</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm
deleted file mode 100644
index dc89d2f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_def_plugins.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Plug-ins</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Plug-ins and fragments</h2>
-<p>Features are described in terms of the plug-ins that comprise them.&nbsp;
-This means that plug-ins are the fundamental unit for packaging
-function.&nbsp;&nbsp;</p>
-<p>While features are organized for the purposes of distributing and updating
-products, plug-ins are organized to facilitate the development of the product
-function among the product team.&nbsp; The development team determines when to
-carve up program function into a separate plug-in.&nbsp;&nbsp;</p>
-<p>Plug-ins are packaged in a <a href="../reference/misc/plugin_archive.html">plug-in
-archive</a> file and described using a <a href="../reference/misc/plugin_manifest.html">plug-in
-manifest file</a>, <b>plugin.xml</b>.&nbsp;&nbsp;</p>
-<p>Plug-in <b>fragments</b> are separately packaged files whose contents are
-treated as if they were in the original plug-in archive file.&nbsp; They are
-useful for adding plug-in functionality, such as additional national language
-translations, to an existing plug-in after it has been installed.&nbsp;
-Fragments are ideal for shipping function that may trail the initial product
-release, since they can be used to add function without repackaging or
-reinstalling the original plug-in.&nbsp; When a fragment is detected by the
-platform, its contents are merged with the function in the original
-plug-in.&nbsp; In other words, if you query the platform plug-in registry, you
-would see the extensions and other function provided in the fragment as if it
-was in the original plug-in.</p>
-<p>Fragments are described using a fragment manifest file, <b>fragment.xml.</b>&nbsp;
-It is similar to the plug-in manifest file.&nbsp; Since a fragment shares many
-properties with its plug-in, some attributes in the plug-in manifest are not
-valid, such as the plug-in class and plug-in imports.</p>
-<p><a href="../reference/misc/plugin_archive.html">Plug-in
-archive</a> files can contain plug-ins or fragments.&nbsp; </p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm
deleted file mode 100644
index 921dc56..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_extension.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Product extensions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Product extensions</h2>
-<p>An <b>extension</b> is a set of Eclipse features and plug-ins that are
-designed to extend the functionality of already-installed Eclipse based
-products.&nbsp; Extensions are installed separately, but used only in
-conjunction with other Eclipse based products.&nbsp; This means that an extension does not
-need to install a JRE, the Eclipse platform, or a primary feature.&nbsp; The
-recommended directory structure for extensions allows a single installation to be
-used with multiple Eclipse based products.</p>
-<p>The following directory structure shows how an extension for a hypothetical
-product, <b>betterwebs</b>, could be used to extend the function of the <b>acmeweb</b>
-product.</p>
-<pre>betterwebs/
-	eclipse/			<i>(directory for installed Eclipse files)</i>
-		.eclipseextension	(marker file)
-		features/		<i>(installed features)</i>
-			com.example.betterwebs.betterfeature_1.0.0/
-				feature.xml
-		plugins/
-			com.example.betterwebs.betterfeature_1.0.0/
-				plugin.xml
-				about.html
-			com.example.betterwebs.betterwebsupport_1.0.0/
-</pre>
-
-<p>The relationship between an extension and the product that it is designed to
-enhance is set up in the <b>links</b> directory of the original product.&nbsp;
-Recall the following directory in the acmeweb product:</p>
-<pre>acmeweb/
-	...
-	eclipse/		<i>(directory for installed Eclipse files)</i>
-		...
-		jre/
-		features/	<i>(installed features)</i>
-			...
-		plugins/
-			...
-<b>		links/
-</b>			com.example.betterwebs.betterfeature.link</pre>
-
-<p>When an extension is installed, it creates a link file in the <b>links</b>
-directory of any product that it is intending to extend.&nbsp; This link file
-makes the original product aware of the existence of the extension.</p>
-
-<h3>Installing and uninstalling extensions</h3>
-
-<p>The install process for extensions is similar to that for products except for
-the following differences:</p>
-
-<ul>
-  <li>Determine which already-installed product is to be extended (by asking the
-    user or searching the computer for the appropriate marker file)</li>
-  <li>Create an <b>.eclipseextension</b> marker file (instead of an <b>.eclipseproduct</b>
-    marker file).&nbsp; The format and content are similar to the product
-    markers.</li>
-  <li>Create a link file for the extension and write it into the <b>links</b>
-    directory of the associated product.&nbsp; The link file has the same name
-    as the extension's feature directory without the version suffix.&nbsp; The
-    link file is a <b>java.io.Properties </b>format file which defines the path
-    to the installed extension.</li>
-</ul>
-<p>The uninstall process for extensions is similar to that for products except
-that the uninstall must remove the link file from any products where it added
-one. </p>
-<p>Additional information on installing extensions can be found in <a href="../reference/misc/eclipse-install.html">How
-to write an Eclipse installer</a>.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/product_update.htm b/bundles/org.eclipse.platform.doc.isv/guide/product_update.htm
deleted file mode 100644
index fcd2381..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/product_update.htm
+++ /dev/null

@@ -1,85 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Updating a product or extension</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Updating a product or extension</h2>
-<p>By following the prescribed procedures for packaging and installing products,
-we can take advantage of <b>platform provisioning support,</b> which treats
-products and extensions in a uniform way and allows users to discover and
-install updated versions of products and extensions.</p>
-<p>Before looking at the implementation of such a server, it's important to
-revisit some important concepts:</p>
-<ul>
-  <li>The platform provides a framework for defining <b>features</b> and software <b>sites</b>.&nbsp;
-    The platform itself defines a concrete implementation of features and
-    sites.&nbsp; This concrete implementation is what allows the platform
-    to upgrade and install additional features.</li>
-  <li>The platform <b>software site</b> can be used to <b>update</b> products by
-    installing new versions of features.&nbsp; It can also be used to <b>install</b>
-    or <b>update</b> extensions by adding or upgrading features.&nbsp;&nbsp;
-    This is only possible for products and extensions that conform to the
-    platform's concrete implementation of features and sites and conform to the
-    appropriate install guidelines.</li>
-  <li>Developers are free to use native installers and uninstallers to upgrade
-    their own products and extensions without regard to sites and the
-    platform update support.</li>
-</ul>
-<p>That said, what do we do if we want to fully participate in the platform
-implementation of product updating and use its update server?</p>
-<h3>Feature and plug-in packaging</h3>
-<p>The previous example product and extension directory structures show how
-features and plug-ins are laid out once they are installed.&nbsp; In order to
-install features using the software site, the features must be packaged in a
-feature archive file.&nbsp; This is described in <a href="../reference/misc/feature_archive.html"> Feature
-Archive Files</a>. </p>
-<p>Plug-ins and fragments must be packaged according to the format described in <a href="../reference/misc/plugin_archive.html"> Plug-in
-Archive Files</a>.</p>
-<h3>Software site layout</h3>
-<p>The software site must be a URL-accessible server with a fixed layout.&nbsp;
-The list of available features and plug-ins provided by the server is described
-in a site map file, <b>content.xml</b>.&nbsp; The server URL can be
-specified as a full URL to the site map file, or a URL of a directory path
-containing the site map.&nbsp; Prefer using the directory path as this will allow
-for future changes to the software site format.
-&nbsp; The site map file contains a list of all the
-available features and the location of the feature archives on the server.&nbsp;
-It also describes the locations of the plug-in archives that are referenced in
-the feature manifest.</p>
-<p>A simple site layout for our example web product and extension could look something like this:</p>
-<pre>&lt;site root&gt;/
-	artifacts.jar <i>(compressed p2 artifact repository - present in p2 optimized site)</i>
-	content.jar <i>(compressed p2 metadata repository - present in p2 optimized site)</i>
-	features/	<i>(contains feature archive files)</i>
-		com.example.acme.acmefeature_1.0.1.jar
-		com.example.betterwebs.betterfeature_1.0.1.jar
-		...
-	plugins/	<i>(contains plug-in archive files)</i>
-		com.example.acme.acmefeature_1.0.1.jar
-		com.example.acme.acmewebsupport_1.0.3.jar
-		com.example.betterwebs.betterfeature_1.0.1.jar
-		com.example.betterwebs.betterwebsupport_1.0.1.jar
-		...</pre>
-<h3>Update servers</h3>
-<p>An Eclipse project software site is provided for updating the platform
-itself.  In addition, the platform update UI allows users to maintain a list of software sites that
-can be searched for new features.  Any site that conforms to the specified update server
-layout may be added to the list. Users can choose to manually or automatically search for
-additional features or upgrades to their installed features.  </p>
-<p>
-Software sites can be created and manipulated by creating an "update site"
-project in PDE, or by using the <a href="p2_publisher.html">publishing</a>
-and <a href="p2_repositorytasks.htm">repository manipulation</a> command
-line tools and Ant tasks.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp.htm
deleted file mode 100644
index f5a34ef..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Building a Rich Client Platform application
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Building a Rich Client Platform application</h1>
-<P>
-While the Eclipse platform is designed to serve as an open tools platform, it is architected so that its components could be 
-used to build just about any client application.  The minimal set of plug-ins needed to build a rich client application is collectively
-known as the <b>Rich Client Platform</b>.  
-</P>
-<p>
-Applications that don't require a common resource model can be built using a subset of the platform.  These rich applications
-are still based on a dynamic plug-in model, and the UI is built using the same toolkits and extension points.  The layout and
-function of the workbench is under fine-grained control of the plug-in developer in this case.  Up until now, we've been adding
-all of our visible function to the platform SDK workbench.  In a rich client application, we are responsible for defining the
-application and its workbench.
-</P>
-<p>
-When we say that the Rich Client Platform is the minimal set of plug-ins needed to build a platform application with
-a UI, we mean that your application need only require two plug-ins, <b>org.eclipse.ui</b> and <b>org.eclipse.core runtime</b>.  
-However, rich client applications are free to use any API deemed necessary 
-for their feature set, and can require any plug-ins above the bare minimum.  The 
-<a href="../reference/misc/overview-platform.html">Map of platform plug-ins</a> is a useful 
-reference when determing what plug-ins should be required when using various platform
-API.</P>
-<p>The main thing that differentiates a rich client application from the platform workbench is that the application
-is responsible for defining which class should be run as the main application.  We'll look at how this is done in
-the context of an example.
-</p>
-
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm
deleted file mode 100644
index 31018b2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_actions.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Defining the actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Defining the actions</H3>
-<P>
-The primary customization provided by the <b>BrowserAdvisor</b> in the browser example is the
-designation of the action bar content for the workbench window:</p>
-<pre>	public void fillActionBars(IWorkbenchWindow window, IActionBarConfigurer configurer, int flags) {
-		...
-		BrowserActionBuilder builder = new BrowserActionBuilder(window);
-		getWorkbenchConfigurer().getWindowConfigurer(window).setData(BUILDER_KEY, builder); 
-		builder.fillActionBars(configurer, flags);
-	}
-</pre> 
-<p>Let's take a closer look at how these actions are defined in the <b>BrowserActionBuilder</b>.  In particular,
-let's look at the actions that are handled by the browser view.</p>
-<pre>private void makeActions() {
-		...				
-		backAction = new RetargetAction("back", "&amp;Back");  
-		backAction.setToolTipText("Back");
-		backAction.setImageDescriptor(images.getImageDescriptor(ISharedImages.IMG_TOOL_BACK));
-		window.getPartService().addPartListener(backAction);
-		
-		forwardAction = new RetargetAction("forward", "&amp;Forward");  
-		forwardAction.setToolTipText("Forward");
-		forwardAction.setImageDescriptor(images.getImageDescriptor(ISharedImages.IMG_TOOL_FORWARD));
-		window.getPartService().addPartListener(forwardAction);
-		
-		stopAction = new RetargetAction("stop", "Sto&amp;p"); 
-		stopAction.setToolTipText("Stop");
-		window.getPartService().addPartListener(stopAction);
-		
-		refreshAction = new RetargetAction("refresh", "&amp;Refresh");  
-		refreshAction.setToolTipText("Refresh");
-		window.getPartService().addPartListener(refreshAction);
-		...
-	}
-</pre> 
-<p>The actions are defined as retargetable actions so that individual views can implement the handler actions.
-The <b>BrowserView</b> associates its handler actions with the window's retargetable actions when it creates 
-the controls for the view:</p>
-<pre>	private Browser createBrowser(Composite parent, final IActionBars actionBars) {
-		
-		...
-		actionBars.setGlobalActionHandler("back", backAction); 
-		actionBars.setGlobalActionHandler("forward", forwardAction); 
-		actionBars.setGlobalActionHandler("stop", stopAction); 
-		actionBars.setGlobalActionHandler("refresh", refreshAction); 
-		...
-	}
-</pre>
-<p>These actions are created when the view is first created.</p>
-<pre>	private Action backAction = new Action("Back") {
-		public void run() {
-			browser.back();
-		}
-	};
-</pre>
-<p>
-See <a href="wrkAdv_retarget.htm">Retargetable actions</a> for a complete discussion of retargetable actions and how they
-are defined and implemented.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm
deleted file mode 100644
index b78165b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_advisor.htm
+++ /dev/null

@@ -1,124 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Customizing the workbench
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Customizing the workbench</H2>
-<p>The "entry point" for supplying custom workbench behavior is the designation of a
-<b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>
-for configuring the workbench.  Your rich client plug-in should extend this abstract class to provide
-the application-specific configuration for the workbench.  The browser example does this using the 
-<b>BrowserAdvisor</b> class.</p>
-<pre>
-	...
-	int code = PlatformUI.createAndRunWorkbench(display,
-			<b>new BrowserAdvisor()</b>);
-	...
-</pre>
-<p>A workbench advisor is responsible for overriding methods to configure the workbench with its desired layout and
-features, such as the action bar items or intro page.  
-</p>
-<h3>The workbench life-cycle</h3>
-<p>Life-cycle methods provided by the workbench advisor allow
-your application to hook into the creation of the workbench at any point in time and influence the behavior.
-The following list of advisor life-cycle methods that can be overridden
-comes from the javadoc for <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>.</p>
-<ul>
-<li><code>initialize</code> - called first; before any windows; use to
-register things</li>
-<li><code>preStartup</code> - called second; after initialize but
-before first window is opened; use to temporarily disable things during
-startup or restore</li>
-<li><code>postStartup</code> - called third; after first window is
-opened; use to reenable things temporarily disabled in previous step</li>
-<li><code>postRestore</code> - called after the workbench and its windows
-have been recreated from a previously saved state; use to adjust the
-restored workbench</li>
-<li><code>preWindowOpen</code> - called as each window is being opened; 
-use to configure aspects of the window other than action bars </li>
-<li><code>fillActionBars</code> - called after <code>preWindowOpen</code> to
-configure a window's action bars</li>
-<li><code>postWindowRestore</code> - called after a window has been
-recreated from a previously saved state; use to adjust the restored
-window</li>
-<li><code>postWindowCreate</code> -  called after a window has been created,
-either from an initial state or from a restored state;  used to adjust the
-window</li>
-<li><code>openIntro</code> - called immediately before a window is opened in
-order to create the introduction component, if any.</li>
-<li><code>postWindowOpen</code> - called after a window has been
-opened; use to hook window listeners, etc.</li>
-<li><code>preWindowShellClose</code> - called when a window's shell
-is closed by the user; use to pre-screen window closings</li>
-<li><code>eventLoopException</code> - called to handle the case where the
-event loop has crashed; use to inform the user that things are not well</li>
-<li><code>eventLoopIdle</code> - called when there are currently no more
-events to be processed; use to perform other work or to yield until new
-events enter the queue</li>
-<li><code>preShutdown</code> - called just after event loop has terminated
-but before any windows have been closed; allows the application to veto
-the shutdown</li>
-<li><code>postShutdown</code> - called last; after event loop has terminated
-and all windows have been closed; use to deregister things registered during
-initialize</li>
-</ul> 
-<p>
-As you can see, a rich client application has a lot of control over how the workbench is configured
-and implemented.  In the browser example, the primary function of the <b>BrowserAdvisor</b> is to configure the action bars with
-menu items appropriate for a browser.  This is done in the <b>fillActionBars</b> method:</p>
-<pre>
-	public void fillActionBars(IWorkbenchWindow window, IActionBarConfigurer configurer, int flags) {
-		...
-		BrowserActionBuilder builder = new BrowserActionBuilder(window);
-		getWorkbenchConfigurer().getWindowConfigurer(window).setData(BUILDER_KEY, builder); 
-		builder.fillActionBars(configurer, flags);
-	}
-</pre> 
-<p>In this method, the workbench is configured with a specialized action builder.  This action builder
-is used to fill the action bars of the workbench.  We'll look at the details for how the actions are specified
-in <a href="rcp_actions.htm">Defining the actions</a>.  For now, we are focusing on how we configure
-the workbench.</p>
-<p>Note the use of the <b>getWorkbenchConfigurer()</b> method above.  The 
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchConfigurer.html">IWorkbenchConfigurer</a></b> and
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchWindowConfigurer.html">IWorkbenchWindowConfigurer</a></b> are
-used in conjunction with the <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>
-to customize the window.  These classes allow you to override many aspects of workbench creation at different levels.
-For example, the <b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchWindowConfigurer.html">IWorkbenchWindowConfigurer</a></b> defines
-protocol that assumes a particular configuration of controls in the workbench window, such an action bar, status line, perspective bar,
-cool bar, etc.  Its protocol allows you customize and populate these items.  The 
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchConfigurer.html">IWorkbenchConfigurer</a></b> 
-operates at a higher level, allowing you to store application-specific data with the workbench.  The
-<b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b> provides
-access to these configurers in the life-cycle methods noted above.  Lower level methods inside 
-<b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b> may be overridden
-to completely replace default behavior.  For example, your workbench advisor could
-override the method that creates the SWT controls in the window in order to provide a completely
-different implementation for the main window.</p>
-<p>
-In other words, there are many ways to customize the workbench and several different levels at which these
-techniques can be used.
-The javadoc for <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>,
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchConfigurer.html">IWorkbenchConfigurer</a></b>, and
-<b><a href="../reference/api/org/eclipse/ui/application/IWorkbenchWindowConfigurer.html">IWorkbenchWindowConfigurer</a></b>
-includes a complete description of the available protocol.  See also the complete implementation of
-<b>BrowserAdvisor</b> for comments on alternate implementations. 
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm
deleted file mode 100644
index 1095d7d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_browser.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-The browser example
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The browser example</H2>
-<P>
-
-We will look at how to build a Rich Client Platform application by going through a simple
-web browser example.  This example is not included in the R3.0 SDK, but can be downloaded from the project
-<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ui.examples.rcp.browser/">org.eclipse.ui.examples.rcp.browser</a>.
-If you are working in Eclipse, you may simply check out the project from the Eclipse CVS repository (see the
-<a href="http://dev.eclipse.org/cvshowto.html">Eclipse CVS How-To</a> if you are not familiar with the procedure for
-checking out projects from CVS).
-</p>
-<p>
-To run the RCP Browser example from within the Eclipse SDK: </p>
-<ol>
-<li>Load the project <tt>org.eclipse.ui.examples.rcp.browser</tt> from the Eclipse CVS repository. </li>
-<li>Choose
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.debug.ui.commands.OpenRunConfigurations")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Run &gt; Run...</b></a>
-
-from the workbench menu bar and create a new "Run-time workbench" 
-configuration named "Browser Example". </li>
-<li>On the <b>Arguments</b> tab, select <b>Run a product</b> and select "org.eclipse.ui.examples.rcp.browser.product" from the drop-down. </li>
-<li>On the <b>Plug-ins</b> tab, select <b>Choose plug-ins and fragments to launch from the list</b> so that you can select which
-plug-ins are needed. </li>
-<li>Press <b>Deselect All</b> to start with a clean slate. </li>
-<li>Check "org.eclipse.ui.examples.rcp.browser" </li>
-<li>Press <b>Add Required Plug-ins</b>. </li>
-<li>Check "org.eclipse.update.configurator" </li>
-<li>Run or debug the new run configuration. </li>
-</ol>
-<img border="0" src="images/browserexample.png" alt="Browser Example Window">
-<p>
-As you can see, it's hard to tell that this application has anything at all to do with Eclipse (apart from the default
-web site that it browses!).  There is no resource navigator, no mention of the Eclipse Platform, and none of the familiar
-menu bar items from the platform workbench.  (The few Eclipse-related features, such as the window icon, could
-also be reconfigured if desired.)
-</p>
-<p>
-Hopefully this example helps clarify what's exciting about the Rich Client Platform.  Let's take a look under the covers so we
-can learn what's involved in building one.  We'll assume that you are familiar with the basic workbench extensions discussed in
-<a href="workbench.htm">Plugging into the workbench</a>.  
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm
deleted file mode 100644
index 6052636..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_define.htm
+++ /dev/null

@@ -1,108 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Defining a rich client application
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Defining a rich client application</H2>
-<p>
-The definition of a rich client application plug-in starts out similarly to the other plug-ins we've been
-studying.  The only difference in the <tt>MANIFEST.MF</tt> file is that the list of 
-required plug-ins is much smaller than we've been used to!
-</p>
-
-<pre>
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.ui.examples.rcp.browser; singleton:=true
-Bundle-Version: 3.3.0.qualifier
-Bundle-ClassPath: browser.jar
-Bundle-Activator: org.eclipse.ui.examples.rcp.browser.BrowserPlugin
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Require-Bundle: org.eclipse.core.runtime,
- org.eclipse.ui
-Eclipse-LazyStart: true
-</pre>
-
-<p>
-Up to now, we've contributed function to the platform workbench by declaring extensions that
-add elements to the workbench.  In all of the <tt>plugin.xml</tt> content that we've reviewed so far,
-we've only looked at individual contributions to a workbench that is assumed to be there.  On the rich
-client platform, there is no application already defined.  Your rich client plug-in is the one
-responsible for specifying the class that should be executed when the platform is started.  This 
-is done in the <a href="../reference/extension-points/org_eclipse_core_runtime_applications.html"><b>org.eclipse.core.runtime.applications</b></a>
-extension.</p>
-<pre>   &lt;extension
-         point="org.eclipse.core.runtime.applications"
-         id="app"
-         name="%appName"&gt;
-      &lt;application&gt;
-         &lt;run
-            class="org.eclipse.ui.examples.rcp.browser.BrowserApp"&gt;
-         &lt;/run&gt;
-      &lt;/application&gt;
-   &lt;/extension&gt;
-</pre> 
-<p>In this extension, we specify the class that should be run when the platform is first started.
-This class must implement <b><a href="../reference/api/org/eclipse/equinox/app/IApplication.html">IApplication</a></b>,
-which simply means that it must implement a <b>start</b> and <b>stop</b> method.  The start method is responsible for creating the SWT display and
-starting up a workbench.  The class <b><a href="../reference/api/org/eclipse/ui/PlatformUI.html">PlatformUI</a></b>
-implements convenience methods for performing these tasks.</p>
-<pre>
-	public Object start(IApplicationContext context) throws Exception {
-		Display display = PlatformUI.createDisplay();
-		try {
-			int code = PlatformUI.createAndRunWorkbench(display,
-					new BrowserAdvisor());
-			// exit the application with an appropriate return code
-			return code == PlatformUI.RETURN_RESTART
-					? EXIT_RESTART
-					: EXIT_OK;
-		} finally {
-			if (display != null)
-				display.dispose();
-		}
-	}
-</pre>
-<p>The call to <b>createAndRunWorkbench</b> will not return until the workbench is closed.  The SWT event loop and other
-low-level logistics are handled inside this method.  At this stage, it's not so important
-that you understand the underlying mechanics in running an SWT application.</p>
-<p>
-The stop method is used to force the application to shutdown.  In the browser example the workbench is closed to 
-force the application to shutdown.</p>
-<pre>
-	public void stop() {
-		final IWorkbench workbench = PlatformUI.getWorkbench();
-		if (workbench == null)
-			return;
-		final Display display = workbench.getDisplay();
-		display.syncExec(new Runnable() {
-			public void run() {
-				if (!display.isDisposed())
-					workbench.close();
-			}
-		});
-	}
-</pre>
-<p>The call to <b>syncExec</b> will not return until the workbench is closed.  This will force the application to exit 
-and the call to <b>createAndRunWorkbench</b> to return.
-</p>
-<p>
-This code can be copied to your rich client
-application with minimal changes.  In fact, the hook for you to add your own functionality is the <b>WorkbenchAdvisor</b>
-that is passed as an argument when the workbench is created.  Let's take a closer look.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm
deleted file mode 100644
index e7fca58..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_extensions.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Making UI contributions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Making UI contributions</H2>
-<P>
-So far, we've seen that the main difference between a rich client platform plug-in and an 
-Eclipse SDK plug-in is that the rich client plug-in is responsible for specifying the  
-class that should be run when the platform is started.  This class creates and runs a
-workbench window that is configured appropriately.  What else is different about a rich
-client application?  Not much, actually.
-</p>
-<p>Once the infrastructure for the application workbench is in place, the techniques for 
-adding function to the workbench are the same as those we used when we were extending the
-platform SDK workbench.  The workbench UI extension points are used to add views, editors,
-menus, and all of the other contributions we know and love.  In the case of the browser example,
-we'll be adding extensions for a perspective and a couple of views. </p>
-<p>
-We were introduced to these extensions in <a href="workbench.htm">Plugging into the workbench</a>.
-For completeness, we'll take a look at how the browser example uses these extensions, but we'll
-assume that we already have a working knowledge of these concepts.
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm
deleted file mode 100644
index f76ea61..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_perspective.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Adding the perspective
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Adding the perspective</H3>
-<P>
-When a rich client application uses the <b><a href="../reference/api/org/eclipse/ui/application/WorkbenchAdvisor.html">WorkbenchAdvisor</a></b>
-as the primary means for customizing the workbench, it must supply a perspective that is shown in the workbench window.
-This perspective must be identified in the application's workbench advisor class.  The following is specified in the
-<b>BrowserAdvisor</b> class:</p>
-<pre>	public String getInitialWindowPerspectiveId() {
-		return BrowserApp.BROWSER_PERSPECTIVE_ID; 
-	}
-</pre> 
-<p>While <b>BrowserApp</b> defines:</p>
-<pre>	public static final String PLUGIN_ID = "org.eclipse.ui.examples.rcp.browser";
-	public static final String BROWSER_PERSPECTIVE_ID = PLUGIN_ID + ".browserPerspective";
-</pre> 
-<p>The corresponding perspective is defined in the browser plug-in's manifest:</p>
-<pre>   &lt;extension
-         point="org.eclipse.ui.perspectives"&gt;
-      &lt;perspective
-            id="org.eclipse.ui.examples.rcp.browser.browserPerspective"
-            name="%perspectives.browser.name"
-            class="<b>org.eclipse.ui.examples.rcp.browser.BrowserPerspectiveFactory</b>"
-            fixed="true"/&gt;
-   &lt;/extension&gt;
-</pre> 
-<p>The <b>BrowserPerspectiveFactory</b> is responsible for laying out the views appropriately.</p>
-<pre>	public void createInitialLayout(IPageLayout layout) {
-		layout.addView(BrowserApp.BROWSER_VIEW_ID, IPageLayout.RIGHT, .25f, IPageLayout.ID_EDITOR_AREA);
-		layout.addPlaceholder(BrowserApp.HISTORY_VIEW_ID, IPageLayout.LEFT, .3f, IPageLayout.ID_EDITOR_AREA); 
-		IViewLayout historyLayout = layout.getViewLayout(BrowserApp.HISTORY_VIEW_ID);
-		historyLayout.setCloseable(true);
-		layout.setEditorAreaVisible(false);
-	}
-</pre>
-<p>The browser perspective defines two views (one visible, with a placeholder for the other), and makes the
-editor area invisible.  For a complete discussion of perspectives and their corresponding layout, see <a href="workbench_perspectives.htm">Perspectives</a>.
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm b/bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm
deleted file mode 100644
index a1567f7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/rcp_view.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Adding views
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Adding views</H3>
-<P>
-The browser example defines two views in its workbench.  One view shows the browser content and the other
-displays the history of visited links.  We first saw these views when they were added to the browser's perspective:</p> 
-<pre>	public void createInitialLayout(IPageLayout layout) {
-		<b>layout.addView(BrowserApp.BROWSER_VIEW_ID, IPageLayout.RIGHT, .25f, IPageLayout.ID_EDITOR_AREA);
-		layout.addPlaceholder(BrowserApp.HISTORY_VIEW_ID, IPageLayout.LEFT, .3f, IPageLayout.ID_EDITOR_AREA); </b>
-		IViewLayout historyLayout = layout.getViewLayout(BrowserApp.HISTORY_VIEW_ID);
-		historyLayout.setCloseable(true);
-		layout.setEditorAreaVisible(false);
-	}
-</pre>
-<p> The corresponding views are also defined in the browser plug-in's manifest:</p> 
-<pre>   &lt;extension
-         point="org.eclipse.ui.views"&gt;
-      &lt;category
-            id="org.eclipse.ui.examples.rcp.browser"
-            name="%views.category.name"/&gt;
-      &lt;view
-            id="org.eclipse.ui.examples.rcp.browser.browserView"
-            name="%views.browser.name"
-            icon="icons/eclipse.png"
-            <b>class="org.eclipse.ui.examples.rcp.browser.BrowserView"</b>
-            category="org.eclipse.ui.examples.rcp.browser"
-            allowMultiple="true"/&gt;
-      &lt;view
-            id="org.eclipse.ui.examples.rcp.browser.historyView"
-            name="%views.history.name"
-            icon="icons/eclipse.png"
-            <b>class="org.eclipse.ui.examples.rcp.browser.HistoryView"</b>
-            category="org.eclipse.ui.examples.rcp.browser"/&gt;
-   &lt;/extension&gt;
-</pre>
-<p>The <b>BrowserView</b> and <b>HistoryView</b> create the necessary SWT controls for showing the browser content
-and history.  The implementation of these views is no different for rich client plug-ins, so we won't
-review them here.  See the example classes and <a href="workbench_basicext_views.htm">
-org.eclipse.ui.views</a> for more information.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv.htm
deleted file mode 100644
index b767f13..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Advanced resource concepts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Advanced resource concepts</H1>
-<p>In <a href="resInt.htm">Resources overview</a> we took a look at the 
-basic services and APIs provided by the <tt>org.eclipse.core.resources</tt>
-plug-in.  This and other related plug-ins also contain many advanced features that are useful
-for plug-ins that require a deeper level of integration.  For details on these advanced
-features, take a gander at some of these topics:
-</p>
-<ul>
-  <li><a href="resAdv_natures.htm">Project natures</a></li>
-  <li><a href="resAdv_builders.htm">Incremental project builders</a></li>
-  <li><a href="resAdv_derived.htm">Derived resources</a></li>
-  <li><a href="resAdv_saving.htm">Workspace save participation</a></li>
-  <li><a href="resAdv_hooks.htm">Resource modification hooks</a></li>
-  <li><a href="resAdv_refresh.htm">Refresh providers</a></li>
-  <li><a href="resAdv_efs_intro.htm">Alternate file systems</a> 
-    <ul>
-      <li><a href="resAdv_efs_api.htm">Using the file system API</a></li>
-      <li><a href="resAdv_efs_resources.htm">Working with resources in other file systems</a></li>
-      <li><a href="resAdv_efs_providers.htm">File system providers</a></li>
-       <li><a href="wrkAdv_efs_resources.htm">User interface support for alternative file systems</a></li>
-    </ul>
-  </li>
-</ul>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm
deleted file mode 100644
index 0495b30..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_batching.htm
+++ /dev/null

@@ -1,144 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Batching resource changes
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Batching resource changes</H3>
-<p>When you need to modify resources in the workspace, it is important to keep in mind that other plug-ins might be
-working with the same resources.  The resources API provides robust mechanisms for keeping plug-ins informed about
-changes in the workspace, and for making sure that multiple plug-ins do not modify the same resource at the same time.
-Where possible, your plug-in's modifications to the workspace should be batched in units of work inside a <b>workspace runnable</b>.
-These runnables help to reduce the amount of change notifications generated by changes.  They also allow you to declare
-which part of the workspace is to be modified, so that other plug-ins can be locked out of changing the same part of the
-workspace.
-</p>
-<p>The protocol for <b><a href="../reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html">IWorkspaceRunnable</a></b> 
-is fairly simple.  A workspace runnable looks just like a long-running operation or platform job.  The actual work is done inside
-a <b>run</b> method, with progress reported to the supplied 
-<b><a href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>.  Code that
-manipulates the workspace is performed inside the <b>run</b> method.
-</p>
-<pre>IWorkspaceRunnable myRunnable = 
-	new IWorkspaceRunnable() {
-		<b>public void run(IProgressMonitor monitor) throws CoreException {</b>
-			//do the actual work in here
-			...
-		}
-}
-</pre>
-<p>When it is time to the run the code, your plug-in tells the workspace to run the code on its behalf.  This way, the
-workspace can generate any necessary change events and ensure that no two plug-ins are modifying the same resource
-at the same time.  (Even if your plug-in is not using background jobs and the concurrency framework to modify the
-workspace, other plug-ins may be doing so.)
-</p>
-<h4>Scheduling rules and locking</h4>
-<p><b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a></b> protocol is used to
-run a workspace runnable.  The preferred technique is using the long form of the <b>run</b> method which supplies 
-a scheduling rule and specifies how resource change events are broadcast.
-</p>
-<p>Specifying a scheduling rule when running a workspace runnable allows the workspace to determine whether
-the resource changes will conflict with workspace changes happening in other threads.  (See 
-<a href="runtime_jobs_rules.htm">Scheduling rules</a> for an overview of scheduling rules and 
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/ISchedulingRule.html">ISchedulingRule</a></b> protocol.)
-Fortunately, <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b> 
-protocol includes the protocol for <b><a href="../reference/api/org/eclipse/core/runtime/jobs/ISchedulingRule.html">ISchedulingRule</a></b>,
-which means that a resource can often be used as a scheduling rule for itself.
-</p>
-<p>Confused?  Code can help to clarify this point.  Suppose your plug-in is getting ready to modify a bunch of
-resources in a particular project.  It can use the project itself as the scheduling rule for making the changes.
-The following snippet runs the workspace runnable that we created earlier:
-</p>
-<pre>IWorkspace workspace = ResourcesPlugin.getWorkspace();
-workspace.run(myRunnable, <b>myProject</b>, <b>IWorkspace.AVOID_UPDATE</b>, null);
-</pre>
-<p>The runnable is passed to the workspace, followed by the project that the 
-code is manipulating.  This tells the workspace that all of the changes in the 
-runnable are confined to <tt>myProject</tt>.  Any requests by other threads
-to change <tt>myProject</tt> will be blocked until this runnable completes.  
-Likewise, this call will block if some other thread is already modifying 
-<tt>myProject</tt>.  By specifying which part of the resource tree will be 
-modified by the runnable, you are allowing other threads to continue modifying 
-other portions of the workspace.  It is important to be sure that your resource rule 
-matches the work being done inside the runnable.  When a non-null scheduling 
-rule is used, any attempt to access a resource outside the scope of the scheduling 
-rule will trigger an exception.
-</p>
-<p>
-There are two special scheduling rules that are important to consider.  First,
-if you use an instance of <tt>IWorkspaceRoot</tt> as the scheduling rule,
-it means your thread is blocking access to <b>all</b> resources in the tree.
-While a thread holds the root rule, no other thread is allowed to modify the
-workspace.  Conversely, a rule of <tt>null</tt> indicates that the thread
-will block access to <b>no</b> resources in the tree.  While a thread with the
-null rule is free to modify the workspace itself, other threads will not be prevented
-from performing their own modifications.  The <tt>IWorkspaceRoot</tt> and
-<tt>null</tt> scheduling rules occupy opposite ends of the concurrency spectrum.  
-With <tt>IWorkspaceRoot</tt> there is no concurrency
-and only one thread is modifying the workspace at a time.  With a <tt>null</tt> rule,
-there is maximum concurrency as all threads can modify the workspace concurrently.
-</p>
-<p>The third parameter to the <b>run</b> method specifies whether any periodic resource change events should
-be broadcast during the scope of this call.  Using <tt>IWorkspace.AVOID_UPDATE</tt> tells the platform to suppress any
-resource change events while the runnable is running and to broadcast one event at the end of the changes.
-During this call, any other runnables created in the runnable will be considered part of the parent batch
-operation.  Resource changes made in those runnables will appear in the parent's resource change notification.
-</p>
-<h4>Resource rule factory</h4>
-<p>In the example above, we assumed that the code inside our runnable only modified resources in a particular project.
-This made it very easy to specify a scheduling rule for the runnable.  In practice, it can be more difficult
-to compute what parts of the workspace are affected by a particular change.  For example, moving a resource from one
-project to another affects both projects.  <b><a href="../reference/api/org/eclipse/core/resources/IResourceRuleFactory.html">IResourceRuleFactory</a></b> 
-can be used to help compute an appropriate resource rule for certain kinds of resource changes.  You can get
-a resource rule factory from the workspace itself.
-</p>
-<pre>IWorkspace workspace = ResourcesPlugin.getWorkspace();
-IResourceRuleFactory ruleFactory = <b>workspace.getRuleFactory()</b>;
-</pre>
-<p>The factory can supply rules appropriate for many kinds of operations.  If your runnable is moving a resource
-from one location to another, it can obtain a rule appropriate for this operation:
-</p>
-<pre>ISchedulingRule movingRule = ruleFactory.moveResource(sourceResource, destinationResource);
-workspace.run(myRunnable, <b>movingRule</b>, IWorkspace.AVOID_UPDATE, null);
-</pre>
-<p>See the javadoc for <b><a href="../reference/api/org/eclipse/core/resources/IResourceRuleFactory.html">IResourceRuleFactory</a></b> 
-for the list of available rules.  The resources plug-in uses these rules itself to implement most resource operations.
-Browsing the code that references these rule methods will help demonstrate how they are used in practice.
-</p>
-<p>Multiple rules can be combined using 
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/MultiRule.html">MultiRule</a></b>.
-</p>
-<pre>ISchedulingRule movingRule = ruleFactory.moveResource(sourceResource, destinationResource);
-ISchedulingRule modifyRule = ruleFactory.modifyResource(destinationResource);
-workspace.run(myRunnable, <b>MultiRule.combine(movingRule, modifyRule)</b>, IWorkspace.AVOID_UPDATE, null);
-</pre>
-<h4>Ignoring the rules</h4>
-<p>The short form of the <b>run</b> method in
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a></b>
-is also available.  It is retained for backward compatibility.  The short form does not include a rule or an update
-flag.
-</p>
-<pre>workspace.run(myRunnable, null);
-</pre>
-<p>is effectively the same as calling
-</p>
-<pre>workspace.run(myRunnable, workspace.getRoot(), IWorkspace.AVOID_UPDATE, null);
-</pre>
-<p>Specifying the workspace root as the scheduling rule will put a lock on the entire workspace until the runnable
-is finished.  This is the most conservative way to perform a workspace update, but it is not very friendly to
-other concurrency-minded plug-ins.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm
deleted file mode 100644
index f145887..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_builders.htm
+++ /dev/null

@@ -1,254 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Incremental project builders</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Incremental project builders</H2>
-<P >
-An <b>incremental project builder</b> is an object that manipulates the resources in a project in
-a particular way.  Incremental project builders are often used to apply a
-transformation on a resource to produce a resource or artifact of another kind.
-Resources created by a builder are typically marked as <a href="resAdv_derived.htm">derived resources</a>.
-</P>
-<p>Plug-ins contribute incremental project builders to the platform in order to implement specialized resource 
-transformations. For example, the Java development tools (JDT)define an incremental project builder that compiles
-a Java source file into a class file any time a file is added or modified in a Java project.  It also
-keeps track of dependent files and recompiles them when necessary.
-</p>
-<p>From an API point of view, the platform defines two basic types of builds:
-</p>
-<ul>
-<li>A <b> full build </b> performs a build from scratch. It treats all resources in a project
-as if they have never been seen by the builder.</li>
-<li>An <b> incremental build</b> uses a &quot;last build state,&quot; maintained internally by the builder,
-to do an optimized build based on the changes in the project since the last build.</li>
-</ul>
-<p>Incremental builds are seeded with a resource change delta. The delta reflects the net effect of all resource 
-changes since the builder last built the project.  This delta is similar to the one used inside resource change events.
-</p>
-<p>Projects can be periodically <b>cleaned</b> by the user in order to force a rebuild of a complete project
-the next time an incremental build is performed on that project.  Cleaning a project removes build information
-such as problem markers and class files.
-</p>
-<p>Builders are best understood by example. The JDT Java compiler is driven by a Java incremental project builder 
-which recompiles the files in a project that are affected by changes. When a full build is triggered, (or an incremental
-build after a clean), all of the <b> .java</b> files in the project are compiled. Any compile problems encountered 
-are added as problem markers on the affected <b> .java</b> files. When an incremental build is triggered, the builder 
-selectively recompiles the added, changed, or otherwise affected <b>.java</b> files that are described in the 
-resource delta and updates the problem markers as necessary. Any <b>.class</b> files or markers that are no 
-longer appropriate are removed.
-</p>
-<p>Incremental building has obvious performance benefits for projects with hundreds or thousands of resources, 
-most of which are unchanging at any given point in time.
-</p>
-<P >
-The technical challenge for incremental building is to determine exactly what needs to be rebuilt. For example, the
-internal state maintained by the Java builder includes things like a dependency
-graph and a list of compilation problems reported.  This information is used during an incremental build to 
-identify which classes need to be recompiled in response to a change in a Java resource. </P>
-<P >
-Although the basic structure for building is defined in the platform, the real work is done in the builder
-code.  Patterns for implementing complex incremental builders are beyond the scope of this discussion, since the 
-implementation is dependent on the specific builder design. </P>
-
-<H3>Invoking a build</H3>
-<p>A builder can be invoked explicitly in one of the following ways:
-</p>
-<ul>
-<li><b>IProject.build()</b> runs the build processing on the receiving project according to the build
-method's arguments.</li>
-<li><b>IWorkspace.build()</b> runs the build processing on all open projects in the workspace.</li>
-</ul>
-<P >
-In practice, the workbench user triggers a build by selecting corresponding commands in the resource 
-navigator menu.</P>
-<P >
-Incremental project builders are also invoked implicitly by the platform during an auto-build.
-If enabled, auto-builds run whenever the workspace is changed.</P>
-<H3>
-Defining an incremental project builder</H3>
-<P >
-The <a href="../reference/extension-points/org_eclipse_core_resources_builders.html"> <b> org.eclipse.core.resources.builders</b></a> extension point is used to contribute an
-incremental project builder to the platform. The following markup shows how the hypothetical plug-in
-<b> com.example.builders</b> could contribute an incremental project builder.</P>
-<pre>
-   &lt;extension
-      id=&quot;mybuilder&quot; name=&quot;My Sample Builder&quot; point=&quot;org.eclipse.core.resources.builders&quot;&gt;
-      &lt;builder
-         &lt;run 
-            <b>class=&quot;com.example.builders.BuilderExample&quot;</b>&gt;
-            &lt;parameter name=&quot;optimize&quot; value=&quot;true&quot; /&gt;
-            &lt;parameter name=&quot;comment&quot; value=&quot;Builder comment&quot; /&gt;
-         &lt;/run&gt;
-      &lt;/builder&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-The <b> class</b> identified in the extension point must extend the platform class 
-<b><a href="../reference/api/org/eclipse/core/resources/IncrementalProjectBuilder.html">IncrementalProjectBuilder</a></b>. </P>
-<pre>
-   public class BuilderExample extends IncrementalProjectBuilder {
-      IProject[] build(int kind, Map args, IProgressMonitor monitor)
-            throws CoreException {
-         // add your build logic here
-         return null;
-      }
-      protected void startupOnInitialize() {
-         // add builder init logic here
-      }
-      protected void clean(IProgressMonitor monitor) {
-         // add builder clean logic here
-      }
-   }
-</pre>
-<P >
-Build processing begins with the <b> build()</b> method, which includes information about the kind of build that 
-has been requested.  The build is one of the following values:</p>
-<ul>
-<li><b>FULL_BUILD</b> indicates that all resources in the project should be built.</li>
-<li><b>INCREMENTAL_BUILD</b> indicates that the build is incremental.</li>
-<li><b>AUTO_BUILD</b> indicates that an incremental build is being triggered automatically because a
-resource has changed and the autobuild feature is on.</li>
-</ul>
-<p>If an incremental build has been requested, a resource delta is provided to describe the changes in the 
-resources since the last build. The following snippet further refines the
-<b> build() </b> method.
-</P>
-<pre>   protected IProject[] build(int kind, Map args, IProgressMonitor monitor
-         throws CoreException {
-      if (kind == IncrementalProjectBuilder.FULL_BUILD) {
-         fullBuild(monitor);
-      } else {
-         IResourceDelta delta = getDelta(getProject());
-         if (delta == null) {
-            fullBuild(monitor);
-         } else {
-            incrementalBuild(delta, monitor);
-         }
-      }
-      return null;
-   }
-</pre>
-
-<P>It sometimes happens that when building project &quot;X,&quot; a builder
-needs information about changes in some other project &quot;Y.&quot;&nbsp; (For
-example, if a Java class in X implements an interface provided in Y.)&nbsp;
-While building X, a delta for Y is available by calling <b>getDelta(Y)</b>.&nbsp;
-To ensure that the platform can provide such deltas, X's builder must have
-declared the dependency between X and Y by returning an array containing Y from
-a previous <b>build()</b> call.&nbsp; If a builder has no dependencies, it can simply return null.
-See <b><a href="../reference/api/org/eclipse/core/resources/IncrementalProjectBuilder.html">IncrementalProjectBuilder</a></b>
-for further information.</P>
-
-<H4>
-Full build</H4>
-<P >
-The logic required to process a full build request is specific to the plug-in. It may involve visiting every 
-resource in the project or even examining other projects if there are dependencies between projects.
-The following snippet suggests how a full build might be implemented.</P>
-<pre>
-   protected void fullBuild(final IProgressMonitor monitor) throws CoreException {
-      try {
-         getProject().accept(new MyBuildVisitor());
-      } catch (CoreException e) { }
-   }
-</pre>
-<P >
-The build visitor would perform the build for the specific resource (and answer true to continue visiting all 
-child resources).</P>
-<pre>
-   class MyBuildVisitor implements IResourceVisitor {
-      public boolean visit(IResource res) {
-         //build the specified resource.
-         //return true to continue visiting children.
-         return true;
-      }
-   }
-</pre>
-<P >
-The visit process continues until the full resource tree has been traveled.</P>
-
-<H4>
-Incremental build</H4>
-<P >
-When performing an incremental build, the builder works with a resource change delta instead of a complete
-resource tree.</P>
-<pre>
-   protected void incrementalBuild(IResourceDelta delta, 
-         IProgressMonitor monitor) throws CoreException {
-      // the visitor does the work.
-      delta.accept(new MyBuildDeltaVisitor());
-   }
-</pre>
-<P >
-The visit process continues until the complete resource delta tree has been traveled. The specific nature of changes
-is similar to that described in
-<a HREF="resAdv_events.htm#resAdv_events_listener" CLASS="XRef">Implementing a resource change listener</a>.&nbsp;
-One important difference is that with incremental project builders, you are working with a resource delta based 
-on a particular project, not the entire workspace.</P>
-
-<H4>
-Cleaning before a build</H4>
-<P>
-The workbench allows users to <b>clean</b> a project or set of projects before initiating a build.  This feature
-allows the user to force a rebuild from scratch on only certain projects.  Builders should implement 
-this method to clean up any problem markers and <a href="resAdv_derived.htm">derived resources</a> in the project.
-</P>
-
-<H3>
-Associating an incremental project builder with a project</H3>
-<P >
-To make a builder available for a given project, it must be included in the build spec for the project. 
-A project's build spec is a list of commands to run, in sequence, when the project is built. Each command 
-names a single incremental project builder. </P>
-<P>
-<b>NOTE:</b> The builder name in a build command is the fully qualified id
-of the builder extension. The fully qualified id of an extension is created by combining
-the plug-in id with the simple extension id in the plugin.xml file. For example, a builder with simple extension
-id &quot;mybuilder&quot; in the plug-in &quot;com.example.builders&quot; would have the
-name &quot;com.example.builders.mybuilder&quot;</p>
-<P >
-The following snippet adds a new builder as the first builder in the existing list of builders.</P>
-<pre>
-   final String BUILDER_ID = "com.example.builders.mybuilder";
-   IProjectDescription desc = project.getDescription();
-   ICommand[] commands = desc.getBuildSpec();
-   boolean found = false;
-
-   for (int i = 0; i &lt; commands.length; ++i) {
-      if (commands[i].getBuilderName().equals(BUILDER_ID)) {
-         found = true;
-         break;
-      }
-   }
-   if (!found) { 
-      //add builder to project
-      ICommand command = desc.newCommand();
-      command.setBuilderName(BUILDER_ID);
-      ICommand[] newCommands = new ICommand[commands.length + 1];
-
-      // Add it before other builders.
-      System.arraycopy(commands, 0, newCommands, 1, commands.length);
-      newCommands[0] = command;
-      desc.setBuildSpec(newCommands);
-      project.setDescription(desc, null);
-   }
-</pre>
-<P >
-Configuring a project's builder is done just once, usually as the project is being created.
-A common way to associate a builder with a project is by configuring a <a href="resAdv_natures.htm">project nature</a>.
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm
deleted file mode 100644
index 2ec5793..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_concurrency.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Concurrency and the workspace
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Concurrency and the workspace</h3>
-
-<p>We've already seen that workspace code must be aware of concurrency even if it is not using the 
-concurrency framework.  Batching of workspace changes and use of scheduling rules helps in sharing 
-the workspace with other plug-ins (and their threads) that are modifying the workspace.  Once your plug-in
-is using batching and rules (see <a href="resAdv_batching.htm">Batching resource changes</a>), it is
-easy to perform the same work using the platform concurrency mechanisms.
-</p>
-
-<h4>Workspace jobs</h4>
-<p>A <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> is a basic unit of 
-asynchronous work running concurrently with other jobs.  The resources plug-in defines 
-<b><a href="../reference/api/org/eclipse/core/resources/WorkspaceJob.html">WorkspaceJob</a></b>
-as a convenient mechanism for defining asynchronous resource modifications.  Code that would
-normally be batched in an <b><a href="../reference/api/org/eclipse/core/resources/IWorkspaceRunnable.html">IWorkspaceRunnable</a></b> 
-is instead put in the <b>runInWorkspace</b> method of a workspace job subtype.  Instead of running the code using 
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a></b> protocol,
-the job is scheduled just like any other job.  The appropriate scheduling rules must be added on the job before 
-it is scheduled.
-</p>
-<p>Let's look at an example workspace runnable and what we should do to make it a job:
-</p>
-<pre>IWorkspaceRunnable myRunnable = 
-	new IWorkspaceRunnable() {
-		public void run(IProgressMonitor monitor) throws CoreException {
-			//do the actual work in here
-			doSomeWork();
-			...
-		}
-}
-</pre>
-<p>The work is moved to the appropriate method of our
-<b><a href="../reference/api/org/eclipse/core/resources/WorkspaceJob.html">WorkspaceJob</a></b>
-subtype.
-</p>
-<pre>class MyWorkspaceJob extends WorkspaceJob {
-	public MyWorkspaceJob() {
-		super("My Workspace Job");
-	}
-	public IStatus runInWorkspace(IProgressMonitor monitor) {
-		//do the actual work in here
-		doSomeWork();
-		return Status.OK_STATUS;
-	}
-}
-</pre>
-<p>Our runnable had to be invoked specifically:
-</p>
-<pre>IWorkspace workspace = ResourcesPlugin.getWorkspace();
-workspace.run(myRunnable, myProject, IWorkspace.AVOID_UPDATE, null);
-</pre>
-<p>Our job is scheduled like any other job.  The platform job manager will run it according to its
-priority, other jobs in the queue, and the scheduling rules.  Note that we must attach the 
-scheduling rule to the job in order to prevent simultaneous modification of <tt>myProject</tt>.
-</p>
-<pre>MyWorkspaceJob job = new MyWorkspaceJob();
-<b>job.setRule(myProject);</b>
-job.schedule();
-</pre>
-<p>Now that the operation has been structured as a job, all of the scheduling mechanisms (priority, delay, rescheduling) can
-be used.  Resource change events will be batched until the job is finished running.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm
deleted file mode 100644
index d42f8f8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_derived.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Derived resources
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Derived resources</h2>
-
-<p>Many resources get created in the course of translating, compiling, copying,
-or otherwise processing files that the user creates and edits.&nbsp; <b>Derived
-resources</b> are resources that are not original data, and can be recreated
-from their source files.&nbsp; It is common for derived files to be excluded
-from certain kinds of processing.&nbsp;&nbsp;</p>
-<p>For example, derived resources are typically not kept in a team repository,
-since they clutter the repository, change regularly, and can be recreated from
-their source files.&nbsp; It is not practical for team providers to make
-decisions about which files are derived.&nbsp; The resource API provides a
-common mechanism for plug-ins to indicate the resources they create that are
-derived.</p>
-<p>Plug-ins may use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>setDerived(boolean)
-</b>to indicate that a resource is derived from other resources. Newly created resources are not
-derived by default, so this
-method must be used to explicitly mark the resource as derived.&nbsp; A
-common use is to mark a subfolder of the project as derived when an
-&quot;output&quot; folder (such as the &quot;bin&quot; folder in Java projects)
-is created by the plug-in.</p>
-<p>Other plug-ins, usually team providers, can use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>isDerived
-</b>to determine whether a particular resource should be managed by the
-repository.&nbsp; Attempts to mark projects or the workspace root as derived will be
-ignored.</p>
-<blockquote>
-<p><i>Note:&nbsp; The concept of derived resources is provided for other
-(non-team) plug-ins to indicate which resources are inappropriate for repository
-management.&nbsp; Special files created by team implementations to manage their
-data should not be marked as derived resources.&nbsp; See <a href="team_resources_private.htm">Team
-private resources</a> for a technique for marking team-related implementation
-resources hidden.</i></p>
-</blockquote>
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_api.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_api.htm
deleted file mode 100644
index 0c319be..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_api.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Using the file system API
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Using the file system API</h3>
-<p>
-The <tt>org.eclipse.core.filesystem</tt> plug-in provides a generic API for 
-interacting with an arbitrary file system.  This API is similar to <tt>java.io.File</tt>,
-with a few key differences:
-</p>
-<ul>
-<li>Plug-ins can install providers for different types of file systems.</li>
-<li>All methods integrate support for reporting progress and responding to cancelation,
-making it easier to integrate into a graphical user interface.</li>
-<li>There is support for some additional functionality not available in <tt>java.io.File</tt>,
-such as getting and setting file permissions.</li>
-<li>There are more convenience methods, such as copy, move, and recursive deletion.</li>
-</ul>
-<p>
-In the file system API, the path for any given file is represented as a hierarchical
-<tt>java.net.URI</tt>.  The URI scheme represents the kind of file system,
-and the URI path component represents the location of the file within the file
-system tree.  Thus any given hierarchical URI represents a potential file or
-directory in some arbitrary file system.
-</p>
-<p>
-The API for working with files and file systems is found in the 
-<b><a href="../reference/api/org/eclipse/core/filesystem/package-summary.html">org.eclipse.core.filesystem</a></b>)
-package. The central API type is 
-<b><a href="../reference/api/org/eclipse/core/filesystem/IFileStore.html">IFileStore</a></b>
-Each instance of <tt>IFileStore</tt> represents
-a single file in the file system.  As with <tt>IResource</tt>, the existence of
-an <tt>IFileStore</tt> instance does not mean that such a file exists on disk. You
-can use an <tt>IFileStore</tt> instance to create, delete, copy, move, or open
-streams on files.  For a given <tt>URI</tt>, you can get your hands on an <tt>IFileStore</tt>
-instance using the static method <tt>EFS.getStore(URI)</tt>
-</p>
-<p>
-The <b><a href="../reference/api/org/eclipse/core/filesystem/IFileSystem.html">IFileSystem</a></b>
-interface can be used to find out things about the file system as a whole.  Each
-<tt>IFileSystem</tt> instance represents a single URI scheme, such as "file:",
-"ftp:", etc.  You can use this type to ask questions such as what file attributes
-are supported, or whether the file system is case-sensitive.  You can also use
-this type to obtain an <tt>IFileStore</tt> for a given <tt>URI</tt>.
-</p>
-<p>
-Most methods on <tt>IFileStore</tt> have a flag parameter that allows
-extra options to be supplied. The flag values can be found
-in the <b><a href="../reference/api/org/eclipse/core/filesystem/EFS.html">EFS</a></b>
-class.  For example, to open an output stream for appending to a file, use:
-</p>
-<pre>
-	IFileStore store = ...//some file store
-	store.openOutputStream(EFS.APPEND, null);
-</pre>
-<p>
-If you want the default behaviour for a method, use <b>EFS.NONE</b>.
-</p>
-<p>
-The <b><a href="../reference/api/org/eclipse/core/filesystem/IFileInfo.html">IFileInfo</a></b>
-interface represents the state of a file at a particular moment in time. In particular,
-you can find out if the file exists, whether it is a directory, what its attributes are,
-and so on.  This information can be modified and then set back into the file.  For
-example, here is a snippet that sets the read only attribute on a directory:
-</p>
-<pre>
-	IFileStore store = ...//some file store
-	IFileInfo info = store.fetchInfo();
-	if (info.exists() &amp;&amp; info.isDirectory()) {
-		info.setAttribute(EFS.ATTRIBUTE_READ_ONLY, true);
-		store.putInfo(info, EFS.SET_ATTRIBUTES, null);
-	}
-</pre>
-<p>
-This style of API allows you to obtain and change file information with
-a single call to the file system. In the above example, there is only
-one file system call to fetch the info, and then you can perform as many
-operations as you want on the <tt>IFileInfo</tt> object without hitting
-the disk again.
-</p>
-<p>
-The <b><a href="../reference/api/org/eclipse/core/filesystem/EFS.html">EFS</a></b>
-class has static factory methods for obtaining <tt>IFileStore</tt> and <tt>IFileSystem</tt>
-instances, as well as various option constants and error codes.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_intro.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_intro.htm
deleted file mode 100644
index d163805..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_intro.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Alternate file systems
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Alternate file systems</h3>
-
-<p>
-Most of the time, resources in the workspace are stored in a local file system
-that is accessible via <tt>java.io.File</tt>.  However, it is also possible
-to create resources that are stored in other kinds of file systems, such
-as network file systems or a database.
-</p>
-<p>
-The next few sections cover how to contribute alternative file systems, and how 
-to work with resources stored in different file systems.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_providers.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_providers.htm
deleted file mode 100644
index f9f7b15..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_providers.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-File system providers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>File system providers</h3>
-
-<p>
-By default, the <tt>org.eclipse.core.filesystem</tt> plug-in only includes a file system
-implementation for the local file system.  Plug-ins can contribute implementations
-for other file systems using the 
-<b><a href="../reference/extension-points/org_eclipse_core_filesystem_filesystems.html">org.eclipse.core.filesystem.filesystems</a></b> 
-extension point.  File system providers must provide subclasses of 
-<b><a href="../reference/api/org/eclipse/core/filesystem/provider/FileStore.html">FileStore</a></b>
-and
-<b><a href="../reference/api/org/eclipse/core/filesystem/provider/FileSystem.html">FileSystem</a></b>.
-Minimally, all abstract methods must be implemented, but other methods can be
-overridden to provide more efficient implementations of methods such as copy,
-move, delete, etc.  Refer to the javadoc on these classes for more details on
-what the default implementations do, and for advice on how and when to override
-each method.
-</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_resources.htm
deleted file mode 100644
index 2a41e6f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_efs_resources.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Working with resources in other file systems
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Working with resources in other file systems</h3>
-
-<p>
-Most of the API in the <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-hierarchy works the same way
-regardless of what kind of file system the resources are stored in.  However,
-there are some particular APIs that you need to avoid when working with
-resources in other file systems, because they are only designed to work
-with the local file system.
-</p>
-<p>
-In particular, the <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a>.getLocation</b> method is specified to return
-the local file system path of the resource.  If the resource is in some other file
-system, then this method is not applicable and will return <tt>null</tt>.
-It is better to use the method <b>getLocationURI</b> instead,
-which works regardless of what kind of file system the resource is stored in.
-</p>
-<p>
-Similarly, the method 
-<b><a href="../reference/api/org/eclipse/core/resources/IProjectDescription.html">IProjectDescription</a> getLocation</b>
-and <b>setLocation</b> methods should be avoided because they are
-only effective in the local file system. The URI-based location methods should
-be used instead.
-</p>
-<h4>Local caching</h4>
-<p>
-Say you are working with resources that are not in the local file system, but you
-really need a local file.  For example, you may be using a library that has a 
-dependency on <tt>java.io.File</tt>). In this case you can use the 
-<tt>IFileStore.toLocalFile</tt> method to obtain a local copy of the file. Note that
-this will only cause one file or directory to be cached locally, rather than an entire
-directory tree.  Here is an example of using local caching to open a zip file on
-an IFileStore:
-</p>
-<pre>
-   IFileStore store = ...;//some file store
-   java.io.File file = store.toLocalFile(EFS.NONE, null);
-   if (file == null) {
-      //we are not a local file store, so we need to cache a local copy
-      file = store.toLocalFile(EFS.CACHE, null);
-   }
-   java.util.zip.ZipFile zip = new java.util.ZipFile(file);
-</pre>
-<h4>Linking to other file systems</h4>
-<p>
-You can use linked resources to create projects that draw together resources
-from multiple file systems.  Simply use the method 
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a>.createLink(URI, int, IProgressMonitor)</b> or
-<b><a href="../reference/api/org/eclipse/core/resources/IFolder.html">IFolder</a>.createLink(URI, int, IProgressMonitor)</b>
-to create a resource in an existing project whose contents are stored in another location in
-an arbitrary file system.  You can even create links below other linked resources to
-create arbitrary resource trees drawing from many different file systems.  Here
-is a simple example that creates a sibling linked file that shares the same file
-system location as the source:
-</p>
-<pre>
-   IFile source = ...;//some source file
-   IFile link = source.getParent().getFile(new Path(source.getName() + ".link"));
-   link.createLink(source.getLocationURI(), IResource.NONE, null);
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm
deleted file mode 100644
index 904a5a9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_events.htm
+++ /dev/null

@@ -1,295 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Tracking resource changes
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Tracking resource changes</H3>
-<p>We've just seen how to batch resource changes in a runnable (<a href="resAdv_batching.htm">Batching resource changes</a>).
-Let's look at the other side of the coin.  What if you want to keep track of all of the changes to the workspace that happen
-while your plug-in is running?  You can register an
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceChangeListener.html"> IResourceChangeListener</a></b> 
-with the workspace. Your listener will be notified of the changes via an
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceChangeEvent.html"> IResourceChangeEvent</a></b> 
-object, which describes the changes.
-</p>
-<h4>Registering a listener</h4>
-
-<p>First, you must register a resource change listener with the workspace.
-</p>
-<pre>   IResourceChangeListener listener = new MyResourceChangeReporter();
-   ResourcesPlugin.getWorkspace().addResourceChangeListener(
-      listener, IResourceChangeEvent.POST_CHANGE);
-</pre>
-
-<p>Your listener will be notified after modifications to the workspace resources
-have been made. Resource API methods that modify resources trigger these events as part of their documented 
-behavior. The method comment for a resource API method explicitly states whether or not it triggers a resource 
-change event. For example, the following is included in the <b> IFile.setContents()</b> comment:
-</p>
-<pre>   This method changes resources; these changes will be reported in a subsequent
-   resource change event, including an indication that this file's content have
-   been changed.
-</pre>
-
-<p>Methods that create, delete, or change a resource typically trigger these events. Methods that read, but 
-do not write, resources typically do not trigger these events.
-</p>
-<h4>Resource change events</h4>
-
-<p>The resource change event describes the specifics of the change (or set of changes) that have occurred in the 
-workspace. The event contains a <b> resource delta</b> that describes the <i> net</i> effect of the changes. 
-For example, if you add a resource and later delete it during one batch of changes, the resource will not appear 
-in the delta.
-</p>
-<p>The resource delta is structured as a tree rooted at the workspace root. The resource delta tree describes 
-these types of changes:
-</p>
-<ul>
-  <li>
-Resources that have been created, deleted, or changed. If you have deleted (or added) a folder, 
-the resource delta will include the folder and all files contained in the folder.</li>
-  <li>
-Resources that have been moved or renamed using the <b> IResource.move()</b> API.</li>
-  <li>
-Markers that have been added, removed, or changed. Marker modification is considered to be a 
-workspace modification operation.</li>
-  <li>
-Files that have been modified. Changed files are identified in the resource delta, but you do not 
-have access to the previous content of the file in the resource delta.</li>
-</ul>
-<p>To traverse a resource delta tree, you may implement the 
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceDeltaVisitor.html"> IResourceDeltaVisitor</a></b> 
-interface or traverse the tree explicitly using <b>IResource.getAffectedChildren</b>. Resource delta visitors 
-implement a <b> visit</b> method that is called by the resource delta as it enumerates each change in the tree.
-</p>
-<blockquote><i>
-Note:&nbsp; Changes made to resource session properties or resource persistent properties are not identified 
-in the resource delta.</i></blockquote>
-<p>Resource change events are sent whenever a change (or batched set of changes) is made to the workspace. In 
-addition, resource change events are sent for certain specific workspace operations. The table below summarizes 
-the types of resource change events and when they are reported.
-</p>
-<TABLE BORDER="1">
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="CellHeading">
-Event type</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="CellHeading">
-Description</P>
-</TH>
-</TR>
-<TR>
-<TD>
-<P CLASS="CellBody">
-<b>
-PRE_CLOSE</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners that a project is about to be closed. This event can be used to extract and save necessary information from the in-memory representation
-(e.g., session properties) of a project before it is closed. (When a project is closed, the in-memory representation is disposed). The workspace is locked (no resources can be updated) during this event.
-The event contains the project that is being closed.</P>
-</TD>
-</TR>
-<TR>
-<TD>
-<P CLASS="CellBody">
-<b>
-PRE_DELETE</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners that a project is about to deleted. This event can be used to
-perform clean-up operations, such as removing any saved state that is related to
-the project from your plug-in's directory.&nbsp; The workspace is locked (no resources can be updated) during this event. The event contains the project that is being deleted.</P>
-</TD>
-</TR>
-<TR>
-<TD>
-<P CLASS="CellBody"><b>PRE_BUILD</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners before any building occurs.&nbsp; This event is
-broadcast when an explicit build is requested, or when the platform detects a 
-build needs to occur, regardless of whether auto-building is actually enabled. 
-The workspace is <b> not</b> locked during this event (resources can be updated). 
-The event contains a resource delta describing the changes that have occurred since the end of the last
-<b>POST_BUILD</b> event.</P>
-</TD>
-</TR>
-<tr>
-<TD>
-<P CLASS="CellBody">
-<b>
-POST_BUILD</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Notifies listeners after any building occurs.&nbsp; This event is
-broadcast after an explicit build is requested, or when the platform detects a 
-build needs to occur, regardless of whether auto-building is actually enabled. 
-The workspace is <b> not</b> locked during this event (resources can be updated). 
-The event contains a resource delta describing the changes that have occurred since the end of the last
-<b>POST_BUILD</b> event.</P>
-</TD>
-</tr>
-<tr>
-<TD>
-<P CLASS="CellBody">
-<b>
-POST_CHANGE</b></P>
-</TD>
-<TD>
-<P CLASS="CellBody">
-Describes a set of changes that have occurred to the workspace since the last 
-<b> POST_CHANGE</b> event was reported. Triggered after a resource change
-API is used individually or in a batched set of workspace changes. Also triggered 
-before any <b>PRE_BUILD</b> and after any <b>POST_BUILD</b>
-notification is complete. The event contains a resource delta describing the net changes since the last
-<b> POST_CHANGE</b> event.&nbsp; The workspace is
-locked (no resources can be updated) during this event.</P>
-</TD>
-</tr>
-</TABLE>
-
-<h4><a name="resAdv_events_listener">Implementing a resource change listener</a></h4>
-
-<p>The following example implements a console-based resource change listener. A resource change listener 
-is registered for specific types of events and information about these events is printed to the console:
-</p>
-<pre>   IResourceChangeListener listener = new MyResourceChangeReporter();
-   ResourcesPlugin.getWorkspace().addResourceChangeListener(listener,
-      IResourceChangeEvent.PRE_CLOSE
-      | IResourceChangeEvent.PRE_DELETE
-      | IResourceChangeEvent.PRE_BUILD
-      | IResourceChangeEvent.POST_BUILD
-      | IResourceChangeEvent.POST_CHANGE);
-</pre>
-<p>The listener checks for each event type and reports information about the 
-resource that was changed and the kinds of changes that occurred.&nbsp;
-Although this example is designed to show a general listener that handles all
-the types of resource events, a typical listener would register for just one
-type of event.
-</p>
-<p>The implementation for <b> POST_CHANGE </b> uses another class that can 
-be used to visit the changes in the resource delta.
-</p>
-<pre>   import org.eclipse.resources.*;
-   import org.eclipse.runtime.*;
-
-   public class MyResourceChangeReporter implements IResourceChangeListener {
-      public void resourceChanged(IResourceChangeEvent event) {
-         IResource res = event.getResource();
-         switch (event.getType()) {
-            case IResourceChangeEvent.PRE_CLOSE:
-               System.out.print(&quot;Project &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; is about to close.&quot;);
-               break;
-            case IResourceChangeEvent.PRE_DELETE:
-               System.out.print(&quot;Project &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; is about to be deleted.&quot;);
-               break;
-            case IResourceChangeEvent.POST_CHANGE:
-               System.out.println(&quot;Resources have changed.&quot;);
-               event.getDelta().accept(new DeltaPrinter());
-               break;
-            case IResourceChangeEvent.PRE_BUILD:
-               System.out.println(&quot;Build about to run.&quot;);
-               event.getDelta().accept(new DeltaPrinter());
-               break;
-            case IResourceChangeEvent.POST_BUILD:
-               System.out.println(&quot;Build complete.&quot;);
-               event.getDelta().accept(new DeltaPrinter());
-               break;
-         }
-      }
-   }
-</pre>
-<p>The <b> DeltaPrinter</b> class implements the <b><a href="../reference/api/org/eclipse/core/resources/IResourceDeltaVisitor.html">IResourceDeltaVisitor</a></b> interface to interrogate the resource delta. The
-<b> visit()</b> method is called for each resource change in the resource delta. The visitor uses a return value to indicate whether
-deltas for child resources should be visited.
-</p>
-<pre>   class DeltaPrinter implements IResourceDeltaVisitor {
-      public boolean visit(IResourceDelta delta) {
-         IResource res = delta.getResource();
-         switch (delta.getKind()) {
-            case IResourceDelta.ADDED:
-               System.out.print(&quot;Resource &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; was added.&quot;);
-               break;
-            case IResourceDelta.REMOVED:
-               System.out.print(&quot;Resource &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; was removed.&quot;);
-               break;
-            case IResourceDelta.CHANGED:
-               System.out.print(&quot;Resource &quot;);
-               System.out.print(res.getFullPath());
-               System.out.println(&quot; has changed.&quot;);
-               break;
-         }
-         return true; // visit the children
-      }
-   }
-</pre>
-<p>Further information can be obtained from the supplied resource delta. The following snippet shows how
-the <b>IResourceDelta.CHANGED</b> case could be implemented to further describe the resource changes.
-</p>
-<pre>   ...
-   case IResourceDelta.CHANGED:
-      System.out.print(&quot;Resource &quot;);
-      System.out.print(delta.getFullPath());
-      System.out.println(&quot; has changed.&quot;);
-      int flags = delta.getFlags();
-      if ((flags &amp; IResourceDelta.CONTENT) != 0) {
-            System.out.println(&quot;--&gt; Content Change&quot;);
-      }
-      if ((flags &amp; IResourceDelta.REPLACED) != 0) {
-            System.out.println(&quot;--&gt; Content Replaced&quot;);
-      }
-      if ((flags &amp; IResourceDelta.MARKERS) != 0) {
-            System.out.println(&quot;--&gt; Marker Change&quot;);
-            IMarkerDelta[] markers = delta.getMarkerDeltas();
-            // if interested in markers, check these deltas
-      }
-      break;
-   ...
-</pre>
-<p>For a complete description of resource deltas, visitors, and marker deltas, consult the
-API specification for <b><a href="../reference/api/org/eclipse/core/resources/IResourceDelta.html">IResourceDelta</a></b>,
-<b><a href="../reference/api/org/eclipse/core/resources/IResourceDeltaVisitor.html">IResourceDeltaVisitor</a></b>, and
-<b><a href="../reference/api/org/eclipse/core/resources/IMarkerDelta.html">IMarkerDelta</a></b>.</P>
-<blockquote><i>
-Note:&nbsp; Resource change listeners are useful for tracking changes that occur to resources while 
-your plug-in is activated. If your plug-in registers a resource change listener during its startup code, 
-it's possible that many resource change events have been triggered before the activation of your plug-in. 
-The resource delta contained in the first resource change event received by your plug-in will not contain 
-all of the changes made since your plug-in was last activated. If you need to track changes made between 
-activations of your plug-in, you should use the support provided for workspace saving. This is described in
-<a HREF="resAdv_saving.htm" CLASS="XRef"> Workspace save participation</a>.</i></blockquote>
-<blockquote><i>
-Note:&nbsp; Some resource change events are triggered during processing that occurs in a background thread.  Resource
-change listeners should be thread-safe.  See <a href="swt_threading.htm">Threading issues</a> for a discussion about
-thread safety with the UI.
-</i></blockquote>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm
deleted file mode 100644
index 648b50a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_hooks.htm
+++ /dev/null

@@ -1,117 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resource modification hooks
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<body>
-<H2>
-Resource modification hooks</H2>
-<P >So far, we've assumed that resource API is being used to modify resources
-that are located in the user's file system.&nbsp; This is indeed the fundamental
-structure of the workspace, but it's also possible that a plug-in adds
-capabilities for manipulation of resources that are managed somewhere
-else.&nbsp; For example, the platform <a href="team.htm">Team support</a>
-plug-ins add the ability to work with resources that are under the management of
-a versioning repository.</P>
-
-<P > The resource API includes capabilities that have been added specifically 
-  to enable the team support plug-ins and plug-ins that implement repository providers 
-  using the team support.&nbsp; The following discussion covers the generic mechanism 
-  for registering resource hooks.&nbsp; See <a href="team_provider_repository.htm#hooks">Implementing 
-  a repository provider</a> for a discussion of how team uses these hooks.&nbsp;&nbsp;</P>
-
-<h3 >
-Resource move/delete hooks</h3>
-
-<P >
-This hook allows the team plug-in and its providers to control
-    how resource moves and deletes are implemented.&nbsp; The hook includes the ability to prevent
-these operations from
-    happening.&nbsp; Implementors can provide alternate implementations for
-    moving or deleting files, folders, and projects.&nbsp;</P>
-
-<P >
-The team plug-in uses the <a href="../reference/extension-points/org_eclipse_core_resources_moveDeleteHook.html"><b>org.eclipse.core.resources.moveDeleteHook</b></a>
-extension point to register its hook:</P>
-
-<pre >&lt;extension point=&quot;org.eclipse.core.resources.moveDeleteHook&quot; id=&quot;MoveDeleteHook&quot;&gt;
-	&lt;moveDeleteHook class=&quot;org.eclipse.team.internal.core.MoveDeleteManager&quot;/&gt;
-&lt;/extension&gt;
-</pre>
-
-<P >
-The supplied class must implement <a href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>,
-which is called by the platform whenever a resource is moved or deleted.&nbsp;
-The team plug-in installs a move delete hook manager that can determine which
-team provider is managing a resource and invoke its specific hook.</P>
-
-<h3 >
-File modification validators</h3>
-
-<p>It's also possible that team repository providers will need to prevent or
-intervene in the editing or saving of a file. The team plug-in
-accomplishes this by using the extension point <a href="../reference/extension-points/org_eclipse_core_resources_fileModificationValidator.html"><b>org.eclipse.core.resources.fileModificationValidator</b></a>
-to register a validator that is called whenever a resource is to be modified.</p>
-
-<pre >&lt;extension point=&quot;org.eclipse.core.resources.fileModificationValidator&quot; id=&quot;FileValidator&quot;&gt;
-	&lt;fileModificationValidator class=&quot;org.eclipse.team.internal.core.FileModificationValidatorManager&quot;/&gt;
-&lt;/extension&gt;</pre>
-
-<P >The supplied class must implement <a href="../reference/api/org/eclipse/core/resources/team/FileModificationValidator.html"><b>FileModificationValidator</b></a>,
-which is called by the platform whenever a resource is saved or
-opened. The team plug-in installs a file modification manager that
-can determine which team provider is managing a resource and invoke its specific
-validator.</P>
-
-<h3 >General team hook</h3>
-<p>
-Repository providers sometimes need to hook into additional workspace operations
-in order to impose extra restrictions or customize workspace behavior.  The
-<a href="../reference/extension-points/org_eclipse_core_resources_teamHook.html"><b>org.eclipse.core.resources.teamHook</b></a>
-extension point provides some other special functions for team providers.  In particular,
-this hook allows a team provider to decide whether linked folders and files should
-be allowed for a given project.  Some repository systems have strict rules about the
-physical layout of projects on disk, and are not able to handle resources linked to
-arbitrary locations.</p>
-<p>
-The team hook also allows a repository provider to supply a 
-<a href="runtime_jobs_rules.htm">scheduling rule</a>
-factory that will be used by all workspace operations.  Each time an API method is called
-that modifies the workspace in some way, a scheduling rule is obtained by the workspace.
-This scheduling rule prevents other threads from modifying those resources during
-the invocation of the API method.  If a repository provider is performing additional
-work inside a file modification validator or move/delete hook, the provider must
-also tell the workspace what additional scheduling rules it will need. See
-the section on <a href="resAdv_batching.htm">resource batching</a> for more
-details on how the workspace uses scheduling rules.
-</p>
-<P >The supplied class for the team hook must implement <a href="../reference/api/org/eclipse/core/resources/team/TeamHook.html"><b>TeamHook</b></a>.
-The team plug-in installs the single team hook that
-can determine which team provider is managing a resource and invoke its specific
-hook.</P>
-
-<blockquote>
-
-  <P ><i>Note:&nbsp; All three of these team hooks are designed specifically 
-    for use by the team core plug-in.&nbsp; They are not intended for general use.&nbsp; 
-    Team providers should not install hooks using these extension points, but 
-    instead implement their hooks in their Repository Provider class.&nbsp;&nbsp; 
-    See <a href="team_provider_repository.htm#hooks">Team resource modification 
-    hooks</a> for more information about using these hooks.</i></P>
-
-</blockquote>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm
deleted file mode 100644
index 6344d1a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_markers.htm
+++ /dev/null

@@ -1,274 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resource markers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<body>
-<H2>
-Resource markers</H2>
-<P >
-We know that plug-ins can define specialized file extensions and contribute editors that provide
-specialized editing features for these file types.&nbsp; During the course of editing (or building) a resource, a plug-in may need to tag resources to communicate problems or other information to the user. The resource marker mechanism is used to manage this kind of information.</P>
-<P >
-A <b> marker</b> is like a yellow sticky note stuck to a resource.  On the marker you can record information about a
-problem (e.g., location, severity) or a task to be done.&nbsp; Or you can simply
-record a location for a marker as a bookmark.&nbsp;</P>
-<P >
-  Users can quickly jump to the marked location within a resource. The workbench UI supports presentation of
-bookmarks, breakpoints, tasks, and problems along the side of the editor.&nbsp;
-These markers can also be shown as items in views, such as the tasks or bookmarks view.</P>
-<P >
-The platform resources API defines methods for creating markers, setting marker values, and extending the platform with new marker types. While the platform manages markers, it is the plug-ins that control their creation, removal and attribute values. </P>
-<P >
-Markers are intended to be small, lightweight objects.  There could be hundreds, even thousands of markers in a single
-project.&nbsp; For example, the Java compiler uses a marker to flag each problem
-it finds in source code.</P>
-<P >
-The platform will throw away markers attached to resources that are deleted, but plug-ins are responsible for removing
-their stale markers when they no longer apply to a resource that still exists.</P>
-
-<H3>
-Marker operations</H3>
-<P >
-Manipulating a marker is similar to manipulating a resource.&nbsp; Markers are <b>handle</b>
-objects.&nbsp; You can obtain a marker handle from a resource, but you don't
-know if it actually exists until you use <b>exists()</b>
-protocol or otherwise try to manipulate it.&nbsp; Once you've established that a
-marker exists, you can query named attributes that may have been assigned to it.</P>
-
-<P >
-Markers are owned and managed by the platform, which takes care of making
-markers persistent and notifying listeners as markers are added, deleted, or
-changed.&nbsp; Plug-ins are responsible for creating any necessary markers, changing their attributes, and removing them when they are
-no longer needed.</P>
-
-<H4>
-Marker creation</H4>
-<P >
-Markers are not directly created using a constructor. They are created using a factory method
-(<b>IResource.createMarker()</b>) on the associated resource. </P>
-<pre>
-   IMarker marker = file.createMarker(IMarker.TASK);
-</pre>
-<P >
-To create a marker that has global scope (not associated with any specific resource), you can use
-the workspace root
-(<b>IWorkspace.getRoot()</b>) as the resource. </P>
-
-
-<H4>
-Marker deletion</H4>
-<P >
-The code for deleting a marker is straightforward.</P>
-<pre>
-   try {
-      marker.delete();
-   } catch (CoreException e) {
-      // Something went wrong
-   }
-</pre>
-<P >
-When a marker is deleted, its marker object (handle) becomes &quot;stale.&quot; Plug-ins should use the
-<b> IMarker.exists()</b> protocol to make sure a marker object is still valid.</P>
-<P >
-Markers can be deleted in batch by asking a resource to delete its markers. This method is useful when removing
-many markers at once or if individual marker references or ids are not available.</P>
-<pre>
-   int depth = IResource.DEPTH_INFINITE;
-   try {
-      resource.deleteMarkers(IMarker.PROBLEM, true, depth);
-   } catch (CoreException e) {
-      // something went wrong
-   }
-</pre>
-<P >
-When deleting a group of markers, you specify a marker <b> type</b> to delete, such as <b> IMarker.PROBLEM</b>, or
-<b> null</b> to delete all markers. The second argument
-indicates whether you want to delete subtype markers.&nbsp; (We'll look a
-subtypes in a moment when we define new marker types.)&nbsp; The <b> depth</b> argument controls the depth of deletion.&nbsp; </P>
-
-
-<P >
-You can also delete markers using <b>IWorkspace.deleteMarkers(IMarker
-[])</b>. </P>
-
-
-<H4>
-Marker attributes</H4>
-<P >
-Given a marker, you can ask for its associated resource, its id (unique relative to that resource), and its type. You can also access additional information
-via generic attributes. </P>
-<P >
-Each type of marker has a specific set of attributes that are defined by the
-creator of the marker type using naming conventions.&nbsp; The
-<b><a href="../reference/api/org/eclipse/core/resources/IMarker.html"> IMarker</a></b> interface defines a set of constants containing
-the standard attribute names (and some of the expected values) for the platform marker types.  The following method manipulates attributes using the platform constants.</P>
-<pre>
-   IMarker marker = file.createMarker(IMarker.TASK);
-   if (marker.exists()) {
-      try {
-         marker.setAttribute(IMarker.MESSAGE, &quot;A sample marker message&quot;);
-         marker.setAttribute(IMarker.PRIORITY, IMarker.PRIORITY_HIGH);
-      } catch (CoreException e) {
-         // You need to handle the case where the marker no longer exists      }
-   }</pre>
-
-
-<P>
-Attributes are maintained generically as name/value pairs, where the names are strings and a value can be any one of the supported value types
-(boolean, integer, string). The limitation on value types allows the platform to persist the markers quickly and simply.</P>
-
-
-<H4>
-Querying markers</H4>
-<P >
-Resources can be queried for their markers and the markers of their children. For example, querying the workspace root with infinite depth considers all of the markers in the workspace.</P>
-<pre>
-   IMarker[] problems = null;
-   int depth = IResource.DEPTH_INFINITE;
-   try {
-      problems = resource.findMarkers(IMarker.PROBLEM, true, depth);
-   } catch (CoreException e) {
-      // something went wrong
-   }
-</pre>
-<P >
-The result returned by <b>findMarkers</b>  depends on
-the arguments passed.&nbsp; In the snippet above, we are looking for all markers
-of type <b>PROBLEM</b> that appear on the resource and
-all of its direct and indirect descendants.&nbsp; </P>
-
-
-<P >
-If you pass
-<b> null</b>  as the marker type, you will get all the
-marker types associated with the resource. The second argument specifies whether
-you want to look at the resource's children.&nbsp; The
-<b> depth</b> argument controls the depth of the search
-when you are looking at the resource's children. The depth can be <b>DEPTH_ZERO</b>
-(just the given resource), <b>DEPTH_ONE</b> (the resource and all
-of its direct children) or
-<b>DEPTH_INFINITE</b> (the resource and all of its direct and indirect
-descendants). </P>
-
-
-<H4>
-Marker persistence</H4>
-<P >
-The platform standard markers (task, problem, and bookmark) are <b>persistent</b>. This means that their state will be saved across workbench shutdown and startup.
-However, markers of a persistent type may be selectively made transient by setting the reserved attribute <strong>transient</strong> to true.
-</P>
-<P >
-New marker types declared by plug-ins are not persistent unless they are declared as such.</P>
-
-
-
-<H3>
-<a name="resAdv_markers_extending">
-Extending the platform with new marker types</a></H3>
-<P >
-Plug-ins can declare their own marker types using the <b><a href="../reference/extension-points/org_eclipse_core_resources_markers.html"> org.eclipse.core.resources.markers</a></b> 
-extension point. The standard marker types for problems, tasks and bookmarks are declared by the platform in the resources plug-in's markup.</P>
-<pre>
-   &lt;extension
-      id=&quot;problemmarker&quot; 
-      point=&quot;org.eclipse.core.resources.markers&quot; 
-      name=&quot;%problemName&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.marker&quot;/&gt;
-      &lt;persistent value=&quot;true&quot;/&gt;
-      &lt;attribute name=&quot;severity&quot;/&gt;
-      &lt;attribute name=&quot;message&quot;/&gt;
-      &lt;attribute name=&quot;location&quot;/&gt;
-   &lt;/extension&gt;
-   &lt;extension
-      id=&quot;taskmarker&quot; 
-      point=&quot;org.eclipse.core.resources.markers&quot; 
-      name=&quot;%taskName&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.marker&quot;/&gt;
-      &lt;persistent value=&quot;true&quot;/&gt;
-      &lt;attribute name=&quot;priority&quot;/&gt;
-      &lt;attribute name=&quot;message&quot;/&gt;
-      &lt;attribute name=&quot;done&quot;/&gt;
-      &lt;attribute name=&quot;userEditable&quot;/&gt;      
-   &lt;/extension&gt;
-   &lt;extension
-      id=&quot;bookmark&quot; 
-      point=&quot;org.eclipse.core.resources.markers&quot; 
-      name=&quot;%bookmarkName&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.marker&quot;/&gt;
-      &lt;persistent value=&quot;true&quot;/&gt;
-      &lt;attribute name=&quot;message&quot;/&gt;
-      &lt;attribute name=&quot;location&quot;/&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-New marker types are derived from existing ones using multiple inheritance. New marker types inherit all of the attributes from their
-super types and add any new attributes defined as part of the declaration. They also transitively inherit
-attributes from the super types of their super types.  The following markup defines a new kind of marker in a hypothetical
-<b>com.example.markers</b> plug-in.</P>
-<pre>
-   &lt;extension
-      id=&quot;mymarker&quot;
-      point=&quot;org.eclipse.core.resources.markers&quot; /&gt;
-   &lt;extension
-      id=&quot;myproblem&quot;
-      point=&quot;org.eclipse.core.resources.markers&quot;&gt;
-      &lt;super type=&quot;org.eclipse.core.resources.problemmarker&quot;/&gt;
-      &lt;super type=&quot;com.example.markers.mymarker&quot;/&gt;
-      &lt;attribute name=&quot;myAttribute&quot; /&gt;
-      &lt;persistent value=&quot;true&quot; /&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-Note that the type <b> org.eclipse.core.resources.problemmarker</b> is actually one of the pre-defined types (aka
-<b>IMarker.PROBLEM</b>).&nbsp; </P>
-<P >
-  The only aspect of a marker
-super type that is not inherited is its <b> persistence</b> flag.&nbsp;
-  The default value for persistence is false, so any marker type that should be
-  persistent must specify <b>&lt;persistent
-  value=&quot;true&quot;/&gt;</b>. </P>
-<P >
-After declaring the new marker type in your plug-in manifest file, you can create instances of
-<b>com.example.markers.myproblem</b> marker type and freely set or get the
-<b> myAttribute</b> attribute.</P>
-<P >
-Declaring new attributes allows you to associate data with markers that you plan to use elsewhere (in your
-views and editors).  Markers of a particular type do not have to have values for all of the declared attributes.  The attribute declarations are more for solving naming convention problems (so everyone uses &quot;message&quot; to talk about a marker's description) than
-for constraining content. </P>
-<pre>
-   public IMarker createMyMarker(IResource resource) {
-      try {
-         IMarker marker = resource.createMarker(&quot;com.example.markers.myproblem&quot;);
-         marker.setAttribute(&quot;myAttribute&quot;, &quot;MYVALUE&quot;);
-         return marker;
-      } catch (CoreException e) {
-         // You need to handle the cases where attribute value is rejected
-      }
-   }
-</pre>
-<P >
-You can query your own marker types in the same way you query the platform marker
-types.&nbsp; The method below finds all <b>mymarkers</b> associated with the given target resource and all
-of its descendents.  Note that this will also find all
-<b>myproblems</b> since true is passed for the <b>includeSubtypes</b>
-argument.</P>
-<pre>
-   public IMarker[] findMyMarkers(IResource target) {
-      String type = &quot;com.example.markers.mymarker&quot;;
-      IMarker[] markers = target.findMarkers(type, true, IResource.DEPTH_INFINITE);
-   }
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm
deleted file mode 100644
index 706cb74..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_modify.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Modifying the workspace
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Modifying the workspace</h2>
-<p>In the course of performing its function, your plug-in may need to make changes to resources in the workspace.
-The workspace is an important data model for many plug-ins in the system, many of which rely on keeping up with
-the current state of the workspace.  Plug-ins may even be concurrently updating the workspace.  It's important
-for your plug-in to act as a responsible workspace citizen when making changes to resources.  What makes a plug-in 
-a good workspace citizen?
-</p>
-
-<ul>
-<li><b>Batching</b> of changes where possible to avoid flooding the system with unnecessary events or triggering
-unnecessary processing on an interim state.</li>
-<li><b>Listening</b> to resource change events and updating models as the workspace changes.</li>
-<li><b>Fine-grained locking</b> of the workspace when making modifications instead of locking the entire workspace.</li>
-</ul>
-
-<p>The next few sections look at these concepts in more detail. 
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm
deleted file mode 100644
index c646533..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_natures.htm
+++ /dev/null

@@ -1,176 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Project natures
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Project natures</H2>
-<P >
-Project natures allow a plug-in to tag a project as a specific kind of project. For example, the Java development tools (JDT) use a &quot;Java nature&quot; to add
-Java-specific behavior to projects.&nbsp; Project natures are defined by
-plug-ins, and are typically added or removed per-project when the user performs
-some action defined by the plug-in.</P>
-<P >A project can have more than one nature.&nbsp; However, when you define a
-project nature, you can define special constraints for the nature:</P>
-<ul>
-  <li><b>one-of-nature</b> - specifies that the nature is one of a named
-    set.&nbsp; Natures in a set are mutually exclusive; that is, only one nature
-    belonging to the set can exist for a project.</li>
-  <li><b>requires-nature</b> - specifies that the nature depends on another
-    nature and can only be added to a project that already has the required
-    nature.</li>
-</ul>
-<P >
-To implement your own nature, you need to define an extension and supply a class
-which implements <b><a href="../reference/api/org/eclipse/core/resources/IProjectNature.html">IProjectNature</a></b>.</P>
-
-<H3>
-Defining a nature</H3>
-<P >
-The <a href="../reference/extension-points/org_eclipse_core_resources_natures.html"> <b> org.eclipse.core.resources.natures</b></a> extension point is used to add a project nature definition. The following markup adds a nature for the hypothetical
-<b> com.example.natures</b> plug-in.</P>
-<pre>
-   &lt;extension
-      point=&quot;org.eclipse.core.resources.natures&quot;
-      id=&quot;mynature&quot;
-      name=&quot;My Nature&quot;&gt;
-      &lt;runtime&gt;
-         &lt;run class=&quot;com.example.natures.MyNature&quot;&gt;
-         &lt;/run&gt;
-      &lt;/runtime&gt;
-   &lt;/extension&gt;
-</pre>
-<P >
-The class identified in the extension must implement the platform interface
-<b><a href="../reference/api/org/eclipse/core/resources/IProjectNature.html">IProjectNature</a></b>. This class implements plug-in specific behavior for associating nature-specific information with a project when
-the nature is configured.</P>
-<pre>
-   public class MyNature implements IProjectNature {
-
-      private IProject project;
-
-      public void configure() throws CoreException {
-         // Add nature-specific information
-         // for the project, such as adding a builder
-         // to a project's build spec.
-      }
-      public void deconfigure() throws CoreException {
-         // Remove the nature-specific information here.
-      }
-      public IProject getProject() {
-         return project;
-      }
-      public void setProject(IProject value) {
-         project = value;
-      }
-   }
-</pre>
-<P >
-The <b> configure()</b> and <b> deconfigure()</b> methods are sent by the platform
-when natures are added and removed from a project.&nbsp; You can implement the
-<b> configure()</b> method to add a builder to a project as discussed in
-<a HREF="resAdv_builders.htm" CLASS="XRef">Builders</a>.</P>
-
-
-<H3>
-Associating the nature with a project</H3>
-<P >
-Defining the nature is not enough to associate it with a project.&nbsp; You must
-assign a nature to a project by updating the project's description to include
-your nature.&nbsp; This usually happens when the user creates a new project with a specialized new project wizard that assigns the
-nature.&nbsp; The following snippet
-shows how to assign our new nature to a given project.</P>
-<pre>
-   try {
-      IProjectDescription description = project.getDescription();
-      String[] natures = description.getNatureIds();
-      String[] newNatures = new String[natures.length + 1];
-      System.arraycopy(natures, 0, newNatures, 0, natures.length);
-      newNatures[natures.length] = &quot;com.example.natures.mynature&quot;;
-      description.setNatureIds(newNatures);
-      project.setDescription(description, null);
-   } catch (CoreException e) {
-      // Something went wrong
-   }
-</pre>
-<P>
-<b>NOTE:</b> The nature id is the fully qualified id
-of the nature extension. The fully qualified id of an extension is created by combining
-the plug-in id with the simple extension id in the plugin.xml file. For example, a nature with simple extension
-id &quot;mynature&quot; in the plug-in &quot;com.example.natures&quot; would have the
-name &quot;com.example.natures.mynature&quot;
-</p>
-<P>The natures are not actually assigned to (and configured) for the project
-until you set the project description into the project.&nbsp; Also note that the identifier used for the nature is the fully qualified name (plug-in id + extension id) of the nature extension. </P>
-<P>
-If the nature has been defined with constraints, then workspace API can be used
-to validate the new nature.&nbsp; For example, suppose a nature is defined with
-a prerequisite: </P>
-<pre>   &lt;extension
-      point=&quot;org.eclipse.core.resources.natures&quot;
-      <b>id=&quot;myOtherNature&quot;</b>
-      name=&quot;My Other Nature&quot;&gt;
-      &lt;runtime&gt;
-         &lt;run class=&quot;com.example.natures.MyOtherNature&quot;&gt;
-         &lt;/run&gt;
-      &lt;/runtime&gt;
-<b>   &lt;requires-nature id=&quot;com.example.natures.mynature&quot;/&gt;
-</b>   &lt;/extension&gt;
-</pre>
-<P >
-The new nature is not valid unless the first nature exists for the
-project.&nbsp; Depending on the design of your plug-in, you may want to check
-whether the prerequisite nature has been installed, or you may want to add the
-prerequisite nature yourself.&nbsp; Either way, you can check on the validity of
-proposed combinations of project natures using workspace API. </P>
-
-<pre>   try {
-      IProjectDescription description = project.getDescription();
-      String[] natures = description.getNatureIds();
-      String[] newNatures = new String[natures.length + 1];
-      System.arraycopy(natures, 0, newNatures, 0, natures.length);
-<b>      newNatures[natures.length] = &quot;com.example.natures.myOtherNature&quot;;
-</b>      IStatus status = <b>workspace.validateNatureSet(newNatures);
-</b>
-      // check the status and decide what to do
-      if (status.getCode() == IStatus.OK) {
-      	description.setNatureIds(newNatures);
-      	project.setDescription(description, null);
-      } else {
-      	// raise a user error
-	...
-      }
-   } catch (CoreException e) {
-      // Something went wrong
-   }
-</pre>
-
-
-<H3>Nature descriptors</H3>
-<p>In addition to working with natures by their id, you can obtain the
-descriptor (<a href="../reference/api/org/eclipse/core/resources/IProjectNatureDescriptor.html"><b>IProjectNatureDescriptor</b></a>)
-which describes a nature, its constraints, and its label.&nbsp; You can query a
-particular nature for its descriptor, or get descriptors from the
-workspace.&nbsp; The following snippet gets the project nature descriptor for
-our new nature:
-</p>
-<pre>      IProjectNatureDescriptor descriptor = workspace.getNatureDescriptor(&quot;com.example.natures.myOtherNature&quot;);
-</pre>
-<p>You can also get an array of descriptors for all installed natures:
-</p>
-<pre>      IProjectNatureDescriptor[] descriptors = workspace.getNatureDescriptors();
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm
deleted file mode 100644
index 8026c05..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_refresh.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Refresh providers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Refresh providers</H2>
-<P >
-The <a href="../reference/extension-points/org_eclipse_core_resources_refreshProviders.html"><b>org.eclipse.core.resources.refreshProviders</b></a> 
-extension point allows plug-ins to register and implement their own mechanisms for monitoring the external file system
-and refreshing the workspace appropriately.  This extension point is intended for plug-ins that implement
-specialized, often native, schemes for monitoring file system changes.</P>
-<p>
-The plug-in fragment <b>org.eclipse.core.resources.win32</b> implements a native refresh monitor based on
-file system callbacks.  A more naive refresh monitor based on polling is defined for other platforms.
-</p>
-<p>The following snippet shows the definition for this extension in the <b>org.eclipse.core.resources.win32</b>
-fragment.
-</p>
-<pre>   &lt;extension
-         id="win32"
-         point="org.eclipse.core.resources.refreshProviders"&gt;
-      &lt;refreshProvider
-            name="%win32MonitorFactoryName"
-            <b>class="org.eclipse.core.internal.resources.refresh.win32.Win32RefreshProvider"</b>&gt;
-      &lt;/refreshProvider&gt;
-   &lt;/extension&gt;
-</pre>
-<p>The <b>class</b> attribute must be a class that extends 
-<b><a href="../reference/api/org/eclipse/core/resources/refresh/RefreshProvider.html">RefreshProvider</a></b>.
-This class is responsible for installing a monitor on a specific resource and its resource subtree if it is a 
-project or folder.  The monitor must implement 
-<b><a href="../reference/api/org/eclipse/core/resources/refresh/IRefreshMonitor.html">IRefreshMonitor</a></b>.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm b/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm
deleted file mode 100644
index c7d3f1e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resAdv_saving.htm
+++ /dev/null

@@ -1,263 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workspace save participation
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workspace save participation</H2>
-<P >
-Workspace save processing is triggered when the workbench is shut down by the user and at other times
-periodically by the platform.&nbsp; Plug-ins can participate in the workspace save process so that critical
-plug-in data is saved to disk whenever the rest of the workspace's persistent data is saved. </P>
-<P >
-The workspace save process can also be used to track changes that occur between activations of your plug-in.</P>
-
-<H3>
-Implementing a save participant</H3>
-<P >
-To participate in workspace saving, you must add a save participant to the workspace. This is typically done during your plug-in's startup method.&nbsp;
-This is also where you read any state that you might have saved
-when your plug-in was last shut down.</P>
-<P >
-Let's look at a simple plug-in which will demonstrate the save process.</P>
-<pre>
-   package com.example.saveparticipant;
-
-   import org.eclipse.core.runtime.*;
-   import org.eclipse.core.resources.*;
-   import java.io.File;
-   import java.util.*;
-
-   public class MyPlugin extends Plugin {
-      private static MyPlugin plugin;
-
-      public MyPlugin(IPluginDescriptor descriptor) {
-         super(descriptor);
-         plugin = this;
-      }
-
-      public static MyPlugin getDefault() {
-         return plugin;
-      }
-
-      protected void readStateFrom(File target) {
-      }
-
-      public void startup() throws CoreException {
-         super.startup();
-         ISaveParticipant saveParticipant = new MyWorkspaceSaveParticipant();
-         ISavedState lastState =
-            <b>ResourcesPlugin.getWorkspace().addSaveParticipant(this, saveParticipant);</b>
-         if (lastState == null)
-            return;
-         IPath location = lastState.lookup(new Path(&quot;save&quot;));
-         if (location == null)
-            return;
-         // the plugin instance should read any important state from the file.
-         File f = getStateLocation().append(location).toFile();
-         readStateFrom(f);
-      }
-
-      protected void writeImportantState(File target) {
-      }
-   }</pre>
-<P >
-<b><a href="../reference/api/org/eclipse/core/resources/ISaveParticipant.html">
-ISaveParticipant</a></b> defines the protocol for a workspace save participant. Implementors of this
-interface can provide behavior for different stages of the save process.&nbsp;
-Let's look at the stages and how our class <b>WorkspaceSaveParticipant</b>
-implements each of these steps.</P>
-<ul>
-  <li>
-<b>
-prepareToSave</b> notifies the participant that the workspace is about to be saved and that it should suspend normal operation until further notice.&nbsp;
-Our save particpant does nothing here.</li>
-</ul>
-<pre>
-      public void prepareToSave(ISaveContext context) throws CoreException {
-      }
-</pre>
-<ul>
-  <li>
-<b>
-saving</b> tells the participant to save its important state.</li>
-</ul>
-<pre>
-      public void saving(ISaveContext context) throws CoreException {
-         switch (context.getKind()) {
-            case ISaveContext.FULL_SAVE:
-               MyPlugin myPluginInstance = MyPlugin.getDefault();
-               // save the plug-in state
-               <b>int saveNumber = context.getSaveNumber();
-               String saveFileName = &quot;save-&quot; + Integer.toString(saveNumber);
-               File f = myPluginInstance.getStateLocation().append(saveFileName).toFile();
-               </b>// if we fail to write, an exception is thrown and we do not update the path
-               <b>myPluginInstance.writeImportantState(f);
-               context.map(new Path(&quot;save&quot;), new Path(saveFileName));
-               context.needSaveNumber();</b>
-               break;
-            case ISaveContext.PROJECT_SAVE:
-               // get the project related to this save operation
-               IProject project = context.getProject();
-               // save its information, if necessary
-               break;
-            case ISaveContext.SNAPSHOT:
-               // This operation needs to be really fast because
-               // snapshots can be requested frequently by the
-               // workspace.
-               break;
-         }
-      }
-</pre>
-<blockquote>
-  <p>The <a href="../reference/api/org/eclipse/core/resources/ISaveContext.html"><b> ISaveContext</b></a> describes information about the save operation.&nbsp;
-There are three kinds of save operations:&nbsp; <b>FULL_SAVE</b>,
-<b>SNAPSHOT</b>, and <b>PROJECT_SAVE</b>.&nbsp;
-Save participants should be careful to perform the processing appropriate for
-the kind of save event they have received.&nbsp; For example, snapshot events
-may occur quite frequently and are intended to allow plug-ins to save their
-critical state.&nbsp; Taking a long time to save state which can be recomputed
-in the event of a crash will slow down the platform.</p>
-<P >
-A save number is used to create data save files that are named using sequential numbers (<b>save-1</b>,
-<b>save-2</b>, etc.)&nbsp; Each save file is mapped to a logical file name (<b>save</b>) that is independent of the save number. Plug-in data is written to the corresponding file and can be retrieved later without knowing the specific save number of the last successful save operation.&nbsp;
-Recall that we saw this technique in our&nbsp; plug-in's startup code:</P>
-<pre>
-<b>IPath location = lastState.lookup(new Path(&quot;save&quot;));</b>
-</pre>
-<P >
-After we have saved our data and mapped the file name, we call <b>needSaveNumber</b> 
-to indicate that we have actively participated in a workspace save and want to assign a number to the save activity.
-The save numbers can be used to create data files as above.&nbsp;</P>
-
-
-</blockquote>
-<ul>
-  <li>
-<b>
-doneSaving</b> notifies the participant that the workspace has been saved and the participant can continue normal operation.</li>
-</ul>
-<pre>
-      public void doneSaving(ISaveContext context) {
-         MyPlugin myPluginInstance = MyPlugin.getDefault();
-
-         // delete the old saved state since it is not necessary anymore
-         int previousSaveNumber = <b>context.getPreviousSaveNumber()</b>;
-         String oldFileName = &quot;save-&quot; + Integer.toString(previousSaveNumber);
-         File f = myPluginInstance.getStateLocation().append(oldFileName).toFile();
-         f.delete();
-      }
-</pre>
-<blockquote>
-  <p>Here, we clean up the save information from the previous save
-  operation.&nbsp; We use <b>getPreviousSaveNumber</b> 
-  to get the save number that was assigned in the previous save operation (not
-  the one we just completed).&nbsp; We use this number to construct the name of
-  the file that we need to delete.&nbsp; Note that we do not use the save
-  state's logical file map since we've already mapped our current save file
-  number.&nbsp;</p>
-</blockquote>
-<ul>
-  <li>
-<b>
-rollback</b> tells the participant to rollback the important state because the save operation has failed.</li>
-</ul>
-<pre>
-      public void rollback(ISaveContext context) {
-         MyPlugin myPluginInstance = MyPlugin.getDefault();
-
-         // since the save operation has failed, delete the saved state we have just written
-         int saveNumber = context.getSaveNumber();
-         String saveFileName = &quot;save-&quot; + Integer.toString(saveNumber);
-         File f = myPluginInstance.getStateLocation().append(saveFileName).toFile();
-         f.delete();
-      }
-</pre>
-<blockquote>
-  <p>Here, we delete the state that we just saved.&nbsp; Note that we use the
-  current save number to construct the file name of the file we just saved.&nbsp;
-  We don't have to worry about the fact that we mapped this file name into the <a href="../reference/api/org/eclipse/core/resources/ISaveContext.html"><b> ISaveContext</b></a><b>.
-  </b>The platform will discard the context when a save operation fails.</p>
-</blockquote>
-
-
-<p>If your plug-in throws an exception at any time during the save lifecycle, it
-will be removed from the current save operation and will not get any of the
-remaining lifecycle methods.&nbsp; For example, if you fail during your <b>saving</b> 
-method, you will not receive a
-<b>
-rollback</b>  or
-<b>
-doneSaving</b>  message.&nbsp;</p>
-
-
-<H3>
-Using previously saved state</H3>
-<P >
-When you add a save participant to the workspace, it will return an <b><a href="../reference/api/org/eclipse/core/resources/ISavedState.html"> ISavedState</a></b> 
-object, which describes what your plug-in saved during its last save operation (or
-<b> null</b> if your plug-in has not previously saved any state). This
-object can be used to access information from the previous save file (using the save number and file map) or to process changes that have occurred between activations of a plug-in.</P>
-
-<H4>
-Accessing the save files</H4>
-<P >
-If a file map was used to save logically named files according to the save number, this same map can be used to retrieve the data from the last known save state.</P>
-<pre>
-   ISaveParticipant saveParticipant = new MyWorkspaceSaveParticipant();
-   ISavedState lastState =
-      ResourcesPlugin.getWorkspace().addSaveParticipant(myPluginInstance, saveParticipant);
-
-   if (lastState != null) {
-      String saveFileName = lastState.lookup(new Path(&quot;save&quot;)).toString();
-      File f = myPluginInstance.getStateLocation().append(saveFileName).toFile();
-      // the plugin instance should read any important state from the file.
-      myPluginInstance.readStateFrom(f);
-   }
-</pre>
-
-
-<H4>
-Processing resource deltas between activations</H4>
-<P >
-Recall that any number of resource change events could occur in the workspace before your plug-in is ever activated. If you want to know what changes have occurred since your plug-in was
-deactivated, you can use the save mechanism to do so, even if you don't need to save any other data.</P>
-<P >
-The save participant must request that the platform keep a resource delta on its behalf. This is done as part of the save operation.</P>
-<pre>
-   public void saving(ISaveContext context) throws CoreException {
-      // no state to be saved by the plug-in, but request a
-      // resource delta to be used on next activation.
-      context.needDelta();
-   }
-</pre>
-<P >
-During plug-in startup, the previous saved state can be accessed and change events will be created for all changes that have occurred since the last save.</P>
-<pre>
-   ISaveParticipant saveParticipant = new MyWorkspaceSaveParticipant();
-   ISavedState lastState =
-      ResourcesPlugin.getWorkspace().addSaveParticipant(myPluginInstance, saveParticipant);
-   if (lastState != null) {
-      lastState.processResourceChangeEvents(new MyResourceChangeReporter());
-   }
-</pre>
-<P >
-The provided class must implement <a href="../reference/api/org/eclipse/core/resources/IResourceChangeListener.html"><b>IResourceChangeListener</b></a>, as described in
-<a HREF="resAdv_events.htm" CLASS="XRef"> Tracking resource changes</a>.&nbsp; The changes since the last save are reported as part of the <b> POST_AUTO_BUILD</b> resource change event.</P>
-<blockquote><i>
-Note:&nbsp; Marker changes are not reported in the change events stored in an <b> ISavedState</b>. 
-You must assume that any or all markers have changed since your last state was saved.</i></blockquote>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt.htm
deleted file mode 100644
index 3ec9334..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Resources overview</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Resources overview</H1>
-<p> An essential plug-in for Eclipse IDE applications is the resources plug-in 
-  (named <b>org.eclipse.core.resources</b>). The resources plug-in provides services 
-  for accessing the projects, folders, and files that a user is working with. 
-</p>
-<p>For more information on workspace resources, check out some of the following 
-  documents:</p>
-<ul>
-  <li><a href="resInt_workspace.htm">Resources and the workspace</a></li>
-  <li><a href="resInt_filesystem.htm">Resources and the file system</a></li>
-  <li><a href="resInt_properties.htm">Resource properties</a></li>
-  <li><a href="resInt_preferences.htm">Project-scoped preferences</a></li>
-  <li><a href="resInt_content.htm">File encoding and content types</a></li>
-  <li><a href="resInt_linked.htm">Linked resources</a></li>
-  <li><a href="resAdv_markers.htm">Resource markers</a></li>
-  <li><a href="resAdv_modify.htm">Modifying the workspace </a> 
-    <ul>
-      <li><a href="resAdv_batching.htm">Batching resource changes</a></li>
-      <li><a href="resAdv_events.htm">Tracking resource changes</a></li>
-      <li><a href="resAdv_concurrency.htm">Concurrency and the workspace</a></li>
-    </ul>
-  </li>
-</ul>
-<p>
-If you still haven't found what you need, venture on to the <a href="resAdv.htm">
-Advanced resource concepts</a> section.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm
deleted file mode 100644
index 3da3b44..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_content.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-File encoding and content types
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-File encoding and content types</H2>
-<P >
-The platform runtime plug-in defines infrastructure for defining and discovering <b>content types</b> for data
-streams.  (See <a href="runtime_content.htm">Content types</a> for an overview of the content framework.)  
-An important part of the content type system is the ability to specify different encodings (character sets)
-for different kinds of content.  The resources API further allows default character sets to be established for 
-projects, folders, and files.  These default character sets are consulted if the content of the file itself
-does not define a particular encoding inside its data stream.
-</P>
-<h3>
-Setting a character set
-</h3>
-<p>
-We've seen in <a href="runtime_content.htm">Content types</a> that default file encodings can be established
-for content types.  More fine-grained control is provided by the resources API.
-</p>
-<p>
-<b><a href="../reference/api/org/eclipse/core/resources/IContainer.html">IContainer</a></b> 
-defines protocol for setting the default character set for a particular project or folder.  This gives 
-plug-ins (and ultimately the user) more freedom in determining an appropriate character set for a set of files when
-the default character sets from the content type may not be appropriate.</p>
-<p>
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b> defines API for setting
-the default character set for a particular file.  If no encoding is specified inside the file contents,
-then this character set will be used.  The file's default character set takes precedence over any default
-character set specified in the file's folder, project, or content type.
-</p>
-<p>
-Both of these features are available to the end-user in the properties page for a resource.
-</p>
-<h3>Querying the character set</h3>
-
-<p><b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b> also defines API for
-querying the character set of a file.  A boolean flag specifies whether only the character set explicitly 
-defined for the file should be returned, or whether an implied character set should be returned.  For example:
-</p>
-<pre>	String charset = myFile.getCharset(false);
-</pre>
-<p>returns null if no character set was set explicitly on myFile.  However, 
-</p>
-<pre>	String charset = myFile.getCharset(true);
-</pre>
-<p>will first check for a character set that was set explicitly on the file.  If none is found, then the content of the file
-will be checked for a description of the character set.  If none is found, then the file's containing folders and projects 
-will be checked for a default character set.  If none is found, the default character set defined for the content type 
-itself will be checked.  And finally, the platform default character set will be returned if there is no other designation
-of a default character set.  The convenience method <b>getCharset()</b> is the same as using <b>getCharset(true)</b>.
-</p>
-<h3>Content types for files in the workspace</h3>
-<p>For files in the workspace, <a href="../reference/api/org/eclipse/core/resources/IFile.html"><strong>IFile</strong></a> provides API for obtaining 
-  the file content description:</p>
-<pre>IFile file = ...;
-IContentDescription description = file.getDescription();</pre>
-<p>This API should be used even when clients are only interested in determining 
-  the content type - the content type can be easily obtained from the content 
-  description. It is possible to detect the content type or describe files in 
-  the workspace by obtaining the contents and name and using the API described 
-  in <a href="runtime_content_using.htm">Using content types</a>, but that is not recommended. Content type determination 
-  using <strong>IFile.getContentDescription()</strong> takes into account <a href="resAdv_natures.htm">project 
-  natures</a> and project-specific settings. If you go directly to the content 
-  type manager, you are ignoring that. But more importantly, because reading the 
-  contents of files from disk is very expensive. The Resources plug-in maintains 
-  a cache of content descriptions for files in the workspace. This reduces the 
-  cost of content description to an acceptable level.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm
deleted file mode 100644
index 6f91adc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_filesystem.htm
+++ /dev/null

@@ -1,241 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resources and the file system
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Resources and the file system</H2>
-<P >
-When the platform is running and the resources plug-in is active, the workspace is represented by an instance of
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html"> IWorkspace</a></b>, which provides 
-protocol for accessing the resources it contains.  An <b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html"> IWorkspace</a></b> 
-instance represents an associated collection of files and directories in one or more file systems.  You can access the 
-workspace from the resources plug-in class (defined in 
-<b><a href="../reference/api/org/eclipse/core/resources/package-summary.html">org.eclipse.core.resources</a></b>). </P>
-<pre>
-   IWorkspace workspace = ResourcesPlugin.getWorkspace(); 
-</pre>
-<P >
-When the resources plug-in is not running, the workspace exists solely in the file 
-system and is viewed or manipulated by the user via standard file-based tools. 
-Let's look at what a workspace looks like on disk as we explain the
-resources plug-in API. </P>
-
-<H3>
-Our sample tree on disk</H3>
-<P >
-When you started the platform SDK, you were prompted to provide a <b>workspace</b>
-directory.  This is the directory where various plug-ins store interesting metadata
-that is unique to a particular instance of the platform.  By default, the resources
-plug-in stores each project in a sub-directory of the workspace directory. 
-Within these subdirectories are the folders and files that each project contains.  </P>
-<P >
-Let's say your chose the directory <b>c:\MySDK\workspace</b> for your workspace.
-Inside this directory we find subdirectories named after the workspace's projects,
-<b> MyWeb</b> and <b>MyServlet</b>.  These are called the projects' content directories.
-Content directories are created by the platform when the user creates a project.</P>
-<P >
-Inside each directory, we find the files and folders within the project, laid out exactly the same as they are in the 
-workspace's resource tree.  All file names are the same, and the files' contents are the same
-whether accessed from the file system or from the workspace. The only surprise
-is the <b>.project</b> file, explained in a moment.</P>
-<pre>
-   C:\MySDK\workspace  (workspace root)
-      .metadata\ (platform metadata directory
-      MyWeb\ (project content directory for MyWeb)
-	 .project
-         index.html
-         images\
-            logo.png
-      MyServlet\ (project content directory for MyServlet)
-	 .project
-         src\
-            main.java
-         bin\
-            main.class</pre>
-<P >
-The platform has a special <b>.metadata</b> directory for holding platform internal information.  The
-<b>.metadata</b> directory of a workspace is considered to be a &quot;black box.&quot;  Important information about the 
-workspace structure, such as a project's references or a resource's properties,
-is stored in the metadata portion of the workspace and should only be accessed by tools through the
-platform API.&nbsp; These files should never be edited or manipulated using
-generic file system API. </P>
-<P >In addition, each project has its own <b>.project</b> file, where metadata
-about the project is kept.&nbsp; This file is basically an on-disk equivalent of
-the information found in a project's
-<b><a href="../reference/api/org/eclipse/core/resources/IProjectDescription.html">IProjectDescription</a></b>.&nbsp;&nbsp; </P>
-<P >Apart from the <b>.metadata</b>  directory and the <b>.project</b> files, the folders and files in the workspace directory are fair game for other
-tools.&nbsp; The files and folders can be manipulated by non-integrated tools, such as text editors and file system
-utilities.&nbsp; The only issue is that the user must be careful when editing
-these files both in the workbench and externally.&nbsp; (This is no
-different than when a user edits a file using two independent stand-alone
-tools.)&nbsp; The workbench provides refresh operations to reconcile the
-workspace view of resources with the actual state in the file system and 
-there is an option to periodically refresh the workspace based on the state of the file system.</P>
-
-<H3>
-Our sample tree in code</H3>
-<P >
-The resource API allows us to manipulate this resource tree in code.  Here we will look at some code snippets for a quick taste of the resource
-API.  The resource API is defined in a series of interfaces in
-<b><a href="../reference/api/org/eclipse/core/resources/package-summary.html">org.eclipse.core.resources</a></b>.  There are interfaces for all of the resource types, such as
-<b><a href="../reference/api/org/eclipse/core/resources/IProject.html">IProject</a></b>,
-<b><a href="../reference/api/org/eclipse/core/resources/IFolder.html">IFolder</a></b>, and
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b>.  Extensive common protocol is defined in
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>.  We also make use of the
-<b><a href="../reference/api/org/eclipse/core/runtime/package-summary.html">org.eclipse.core.runtime</a></b> interface
-<b><a href="../reference/api/org/eclipse/core/runtime/IPath.html">IPath</a></b>, which represents segmented paths such as resource or file system paths.</P>
-<P >
-Manipulating resources is very similar to manipulating files using <b> java.io.File</b>.&nbsp;
-The API is based on <b>handles</b>.&nbsp; When you use API like <b>getProject</b>
-or <b>getFolder</b>, you are returned a handle to the
-resource.&nbsp;&nbsp; There is no guarantee or requirement that the resource itself exists
-until you try to do something with the handle.&nbsp; If you expect a resource to
-exist, you can use <b>exists</b> method to ensure
-this is the case.&nbsp;&nbsp;  </P>
-<P >
-To navigate the workspace from a plug-in, we must first obtain the <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html"><b>IWorkspaceRoot</b></a>, which represents the top of the resource hierarchy in the workspace.</P>
-<pre>
-   IWorkspaceRoot myWorkspaceRoot = ResourcesPlugin.getWorkspace().getRoot();</pre>
-<P >
-Once we have a workspace root, we can access the projects in the workspace. </P>
-<pre>
-   IProject myWebProject = myWorkspaceRoot.getProject(&quot;MyWeb&quot;);
-   // open if necessary
-   if (myWebProject.exists() &amp;&amp; !myWebProject.isOpen())
-      myWebProject.open(null);
-</pre>
-<P >
-Before we can manipulate a project, we must open it.  Opening the project reads the project's
-structure from disk and creates the in-memory object representation of the project's resource tree.  Opening a project is an explicit operation since each open project consumes memory to represent the resource tree
-internally and open projects participate in various resource lifecycle events
-(such as building) which can be lengthy.&nbsp; In general, closed projects
-cannot be accessed and will appear empty even though the resources are still present in the file system.</P>
-<P >
-You'll notice that many of these resource examples pass a <b> null</b> parameter when manipulating resources.
-Many resource operations are potentially heavyweight enough to warrant progress reporting and
-user cancellation.  If your code has a user interface, you will typically pass an <b><a href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html"> IProgressMonitor</a></b>,
-which allows the
-resources plug-in to report progress as the resource is manipulated and allows the user to cancel the operation if desired.&nbsp;
-For now, we simply pass <b>null</b>, indicating no
-progress monitor.</P>
-<P >
-Once we have an open project, we can access its folders and files, as well as create additional ones.&nbsp;
-In the following example we create a file resource from the contents of a file
-located outside of our workspace.  </P>
-<pre>
-   IFolder imagesFolder = myWebProject.getFolder(&quot;images&quot;);
-   if (imagesFolder.exists()) {
-      // create a new file
-      IFile newLogo = imagesFolder.getFile(&quot;newLogo.png&quot;);
-      FileInputStream fileStream = new FileInputStream(
-         &quot;c:/MyOtherData/newLogo.png&quot;);
-      newLogo.create(fileStream, false, null);
-      // create closes the file stream, so no worries.   
-   }
-</pre>
-<P >
-In the example above, the
-first line obtains a handle to the images folder.&nbsp; We must check that the
-folder <b>exists</b> before we can do anything
-interesting with it.&nbsp; Likewise, when we get the file <b>newLogo</b>,
-the handle does not represent a real file until we create the file in the last
-line.&nbsp; In this example, we create the file by populating it with the
-contents of <b>logo.png</b>.  </P>
-<P >
-The next snippet is similar to the previous one, except that it copies the <b> newLogo</b> file from the original logo rather than create a new
-one from its contents.</P>
-<pre>
-   IFile logo = imagesFolder.getFile(&quot;logo.png&quot;);
-   if (logo.exists()) {
-      IPath newLogoPath = new Path(&quot;newLogo.png&quot;);
-      logo.copy(newLogoPath, false, null);
-      IFile newLogo = imagesFolder.getFile(&quot;newLogo.png&quot;);
-      ...
-   }
-</pre>
-<P >
-Finally, we'll create another images folder and move the newly created file to it.  We rename the file as a side effect of moving it.</P>
-<pre>
-   ...
-   IFolder newImagesFolder = myWebProject.getFolder(&quot;newimages&quot;);
-   newImagesFolder.create(false, true, null);
-   IPath renamedPath = newImagesFolder.getFullPath().append(&quot;renamedLogo.png&quot;);
-   newLogo.move(renamedPath, false, null);
-   IFile renamedLogo = newImagesFolder.getFile(&quot;renamedLogo.png&quot;);
-</pre>
-
-<P>Many of the resource API methods include a <b>force</b>
-boolean flag which specifies whether resources that are out of synch with the
-corresponding files in the file system will be updated anyway.&nbsp; See <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>
-for more information.&nbsp; You can also use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a><b>.isSynchronized
-</b>to determine whether a particular resource is in synch with the file system.</P>
-
-<H3>
-<a name="mapping">
-Mapping resources to disk locations</a></H3>
-<P >
-  In the sample resource tree, we've assumed that all of the project content directories are
-in the <b>workspace</b> directory underneath the platform root
-directory (<b>C:\MySDK\workspace)</b>.  This is the default configuration
-for projects.&nbsp; However, a project's content directory can be mapped to any 
-arbitrary directory in some backing file system, perhaps even on a different machine.</P>
-<P >
-The ability to map the location of a project independent of other projects allows the user to
-store the contents of a project in a place that makes sense for the project and the project team.  
-A project's content directory should be considered &quot;out in the open.&quot;  
-This means that users can create, modify, and delete resources
-by using the workbench and plug-ins, or by directly using file system based tools and editors.</P>
-<P> Resource path names are not complete file system paths.  Resource paths are always
-based on the project's location (usually the <b>workspace</b>
-directory).&nbsp; To obtain the full file system path to a resource, you must query its location using
-<b>
-<a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a>.getLocationURI.&nbsp;
-</b>Howevever, you cannot use
-<b> <a href="../reference/api/org/eclipse/core/resources/IProjectDescription.html">IProjectDescription</a>.setLocation
-</b>to change its location, because that method is just a simple setter for a
-data structure.&nbsp;&nbsp;</P>
-<P>Conversely, if you want to get the corresponding resource object given a file
-system path, you can use <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html"><b>IWorkspaceRoot</b></a>.<b>findFilesForLocationURI</b>
-or <a href="../reference/api/org/eclipse/core/resources/IWorkspaceRoot.html"><b>IWorkspaceRoot</b></a>.<b>findContainersForLocationURI</b>.</P>
-
-<H3>
-Resource API and the file system</H3>
-<P >
-When we use the resources API to modify our workspace's resource tree, the files
-are changed in the file system in addition to updating our resource objects.  What about changes to
-resource files that happen outside of the platform's API?  </P>
-<P >
-External changes to resources will not be reflected in the workspace and resource objects until 
-detected by the resources plug-in.  The resources plug-in also uses a mechanism appropriate for
-each particular native operating system for discovering external changes made in the file system.
-In addition, clients can use resource API to 
-reconcile workspace and resource objects with the local file system quietly and without user intervention.
-The user can also explicitly force a refresh in the resource navigator view of the workbench.  </P>
-<p>Many of the methods in the resource APIs include a force parameter which specifies how resources that
-are out of sync with the file system should be handled.  The API Reference for each method provides specific information 
-about this parameter. Additional methods in the API allow programmatic control of file system refresh, such as
-<b>IResource.refreshLocal(int depth, IProgressMonitor monitor)</b>. See 
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-for information on correct usage and costs.</p>
-<p>
-Plug-ins that wish to supply their own mechanism for periodically refreshing the workspace based on
-the state of the external file system may do so using the
-<a href="../reference/extension-points/org_eclipse_core_resources_refreshProviders.html"><b>org.eclipse.core.resources.refreshProviders</b></a> 
-extension point.  See <a href="resAdv_refresh.htm">Refresh providers</a> for more information. </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm
deleted file mode 100644
index 635a85c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_linked.htm
+++ /dev/null

@@ -1,197 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Linked resources
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>Linked resources</H2>
-<P >Earlier discussions of resources and the file system (<a href="resInt_filesystem.htm#mapping">Mapping
-resources to disk locations)</a> assumed that all resources in a project are
-located in the same place in the file system.&nbsp; This is generally
-true.&nbsp; However, the concept of <b>linked resources</b> in the workbench is
-provided so that files and folders inside a project can be stored in a file system outside of the project's location.&nbsp;
-</P>
-<P >Linked resources can
-be located virtually anywhere in a file system.  They can reside outside the project location,
-or even within another project.  There are only a few restrictions on linked
-resource locations. The method 
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a>.validateLinkLocation</b>
-can be used to ensure that a given location is valid for creating a linked resource.
-</P>
-<P>
-Linked resources are created using the method 
-<b><a href="../reference/api/org/eclipse/core/resources/IFolder.html">IFolder</a>.createLink</b> or
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a>.createLink</b>.  
-To determine programmatically whether a given resource is a linked resource, you
-can use the method
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a>.isLinked</b>.
-Note that this method will only return <code>true</code> for linked resources, not for children 
-of linked resources.
-</P>
-<P>
-Apart from these special methods for creating linked resources and
-finding out if a resource is linked, you can use normal workspace API when manipulating linked
-resources.  In most respects, linked resources act exactly like any other resource in
-the workspace.  However, some restrictions apply when moving, copying, or
-deleting linked resources.&nbsp; See <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-and its sub-classes for information on individual operations and their limitations.
-</P>
-<h3>Path variables</h3>
-<P>
-  Path variables can be used
-when specifying the location of linked resources.&nbsp; A path variable is a simple (String -&gt;
-<b><a href="../reference/api/org/eclipse/core/runtime/IPath.html">IPath</a></b>) 
-or (String -&gt; <b>URI</b>) mapping that 
-defines a shortcut for a location in a file system.&nbsp; Variables can ease
-the management of linked resources by reducing the number of places where
-hard-coded, absolute file system paths are used.</p><P>Path variables
-streamline the management of linked resources for users in several ways:</p>
-<ul>
-<li>Allows a single reference to the absolute path when defining several linked resources under a common
-  root</li>
-<li>Allows the location of several resources to be redefined by changing a
-  single variable</li>
-<li>Allows users to share projects containing linked resources without updating
-  the paths of each resource (since the absolute path can vary from one machine
-  to another.)</li>
-</ul>
-<p>
-The last item in this list deserves a bit of explanation.  When a user creates a
-linked resource in a project, a description of the linked resource is added to the
-project description file (&quot;.project&quot;) in the project's location. By
-using a path variable, users can share a project (by copying the project's
-content or by using a repository), and redefine the variable to suit each
-individual workstation.&nbsp; For example, one user might store external resources under c:\temp on
-one system,
-while another user using Unix might store the same resources in /home/username/tmp.&nbsp;
-Defining a path variable on each workspace (<code>TEMP=c:\temp</code> and <code>TEMP=/home/userb/tmp)</code>
- allows users to work around this difference and share the projects with linked
-resources as is.</p>
-<p><b><a href="../reference/api/org/eclipse/core/resources/IPathVariableManager.html">IPathVariableManager</a></b>
- defines the API for creating, manipulating, and resolving path variables. It also provides methods for validating variable names and values before
-creating them, and for installing a listener to be notified when path variable definitions
-change.  You can obtain an instance of this class using
-<b><a href="../reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a>.getPathVariableManager</b>.
-See the code examples at the end of this section for more detail.</p>
-<p>
-The method 
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a>.getRawLocationURI</b>
-can be used to find out the unresolved location of a linked resource. That is,
-to get the actual path variable name instead of resolving it to its value.&nbsp;
-If a resource location is not defined with a path variable, the <b>getRawLocationURI</b>
-method acts exactly like the <b>getLocationURI</b> method.
-</p>
-<h3>Broken links</h3>
-<p>
-Clients that manipulate resources programmatically need to be aware of the possibility of
-broken links.  Broken links occur when a linked resource's location does not
-exist, or is specified relative to an undefined path variable. The following
-special cases apply when using <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-protocol:</p>
-<ul>
-<li>The <b>copy</b> and <b>move</b> methods will fail when called on broken links.</li>
-<li>Calling <b>refreshLocal</b> on a broken link will not cause the resource to be removed
-from the workspace, as it does for normal resources that are missing from the file system.</li>
-<li>The method <b>getLocation</b> will return <code>null</code> for linked resources
-whose locations are relative to undefined path variables.</li>
-<li>You can still use <b>delete</b> to remove broken links from the workspace.</li>
-</ul>
-<H3>Compatibility with installed plug-ins</H3>
-<p>
-Some plug-ins may not be able to handle linked resources, so there are a number
-of mechanisms available for disabling them.  If you are writing a plug-in that absolutely
-needs all of a project's contents to be located in the project's default location, you 
-can use these mechanisms to prevent users from creating linked resources where
-you don't want them to appear.
-</p>
-<p>
-The first mechanism is called the <i>project nature veto</i>.  If you define your
-own <a href="resAdv_natures.htm">project nature</a>, you can specify in the nature 
-definition that the nature is not compatible with linked resources.  Here is an example 
-of a nature definition that 
-employs the nature veto:</p>
-<pre>&lt;extension
-	id=&quot;myNature&quot;
-	name=&quot;My Nature&quot;
-	point=&quot;org.eclipse.core.resources.natures&quot;&gt;
-	&lt;runtime&gt;
-		&lt;run class=&quot;com.xyz.MyNature&quot;/&gt;
-	&lt;/runtime&gt;
-	&lt;options <b>allowLinking=&quot;false&quot;</b>/&gt;
-&lt;/extension&gt;
-</pre>
-<p>
-The second mechanism for preventing linked resource creation is the <i>team hook</i>.
-If you define your own repository implementation, you can make use of the <b><a href="../reference/extension-points/org_eclipse_core_resources_teamHook.html">org.eclipse.core.resources.teamHook</a></b>
-extension point to prevent the creation of linked
-resources in projects that are shared with your repository type.  By default, 
-repository providers do <em>not</em> allow linked resources in projects
-connected to the repository.&nbsp;
-</p>
-<p>If the repository support is provided by an older plug-in
-that is not aware of linked resources, you will not be able to create linked resources
-in those projects.&nbsp;
-</p>
-<p>
-Finally, there is a preference setting that can be used to disable linked resources
-for the entire workspace.  While the previous two veto mechanisms work
-on a per-project basis, this preference affects all projects in the workspace.  To
-set this preference programatically, use the preference <code>ResourcesPlugin.PREF_DISABLE_LINKING</code>.
-Note that even when set, users or plug-ins can override this by turning the preference
-off.
-</p>
-
-<H3>Linked resources in code</H3>
-<P >
-Let's go into some examples of using linked resources in code. We'll start by 
-defining a path variable:</p>
-<pre>   IWorkspace workspace = ResourcesPlugin.getWorkspace();
-   IPathVariableManager pathMan = workspace.getPathVariableManager();
-   String name = &quot;TEMP&quot;;
-   IPath value = new Path(&quot;c:\\temp&quot;);
-   if (pathMan.validateName(name).isOK() &amp;&amp; pathMan.validateValue(value).isOK()) {
-      pathMan.setValue(name, value);
-   } else {
-      //invalid name or value, throw an exception or warn user
-   }
-</pre>
-<p>Now we can create a linked resource relative to the defined path variable:</p>
-<pre>   IProject project = workspace.getProject(&quot;Project&quot;);//assume this exists
-   IFolder link = project.getFolder(&quot;Link&quot;);
-   IPath location = new Path(&quot;TEMP/folder&quot;);
-   if (workspace.validateLinkLocation(location).isOK()) {
-      link.createLink(location, IResource.NONE, null);
-   } else {
-      //invalid location, throw an exception or warn user
-   }
-</pre>
-<p>That's it!  You now have a linked folder in your workspace called &quot;Link&quot;
-that is located at &quot;c:\temp\folder&quot;.</p>
-<p>
-Let's end with some code snippets on this linked resource to illustrate the behavior other
-methods related to linked resources:</p>
-<pre>
-   link.getFullPath() ==&gt; &quot;/Project/Link&quot;
-   link.getLocation() ==&gt; &quot;c:\temp\folder&quot;
-   link.getRawLocation() ==&gt; &quot;TEMP/folder&quot;
-   link.isLinked() ==&gt; &quot;true&quot;
-   
-   IFile child = link.getFile(&quot;abc.txt&quot;);
-   child.create(...);
-   child.getFullPath() ==&gt; &quot;/Project/Link/abc.txt&quot;
-   child.getLocation() ==&gt; &quot;c:\temp\folder\abc.txt&quot;
-   child.getRawLocation() ==&gt; &quot;c:\temp\folder\abc.txt&quot;
-   child.isLinked() ==&gt; &quot;false&quot;
-</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm
deleted file mode 100644
index c238883..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_preferences.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Project-scoped preferences
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Project-scoped preferences</H2>
-<P >
-In <a href="runtime_preferences.htm">Runtime preferences</a>, we looked at the infrastructure for defining and 
-storing preferences with different scopes.  We also saw that the
-<a href="../reference/extension-points/org_eclipse_core_runtime_preferences.html"><b>org.eclipse.core.runtime.preferences</b></a> 
-extension can be used to define additional scopes for preferences.  The platform resources plug-in defines its own
-preference scope, called &quot;Project,&quot; in order to define project-scoped preferences.  Project-scoped preferences are stored in a file located
-inside the project.  This makes it easy to store a set of preferences and exchange them with other users using 
-resource-oriented mechanisms such as a version control system.
-</p>
-<h3>Specifying the scope</h3>
-
-<p>The definition for new scopes is pretty simple.  The plug-in defines the name of the scope, as well as the class
-that implements it.  The resources plug-in defines the project scope 
-as follows:
-</p>
-<pre>	&lt;extension id="preferences" point="org.eclipse.core.runtime.preferences" name="preferences"&gt;
-		&lt;scope name="project" class="org.eclipse.core.internal.resources.ProjectPreferences"/&gt;
-	&lt;/extension&gt;
-</pre>
-<p>The specified class must implement the 
-<b><a href="../reference/api/org/eclipse/core/runtime/preferences/IScope.html">IScope</a></b> interface, which means
-it must be capable of creating preference nodes for the scope.
-</p>
-
-<h3>Project-scoped preference nodes</h3>
-
-<p>Since the project scope for preferences is not one of the standard runtime scopes, the node representing a project-level
-preference must be obtained specifically.  From the root preference node, you must navigate to the project-scoped
-preference.  This can be achieved using the <b>ProjectScope</b>:
-</p>
-<pre>	IScopeContext projectScope = new ProjectScope(MyProject);
-</pre>
-<p>Once the project scope for a particular is project is found, the preference values can
-be obtained using the same mechanisms seen earlier.  Preferences are named using the string name of the 
-preference.  The names are qualified with another string (often a plug-in id) that qualifies the namespace
-of the preference.  The following snippet gets a preference node from the project scope.  You'll notice that once
-the correct scope is obtained, working with the nodes is no different than with nodes from other scopes.
-</p>
-<pre>	...
-	Preferences projectNode = projectScope.getNode(&quot;com.example.myplugin&quot;);
-	if (projectNode != null) {
-		value = projectNode.getBoolean(&quot;MyPreference&quot;, &quot;true&quot;);
-		//do something with the value.
-	}
-	...
-</pre>
-<p>To save the value to a file in the project, the node is flushed.  The resources plug-in handles the logistics
-for managing the project-level preferences file.
-</p>
-<pre>	projectNode.flush();
-</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm
deleted file mode 100644
index 6d6d717..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_properties.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resource properties
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Resource properties</h2>
-<p>Resources have properties that can be used to store meta-information about the resource.  Your plug-in
-can use these properties to hold information about a resource that is specific to your purpose.
-Resource properties are declared, accessed, and maintained by various plug-ins, and are not interpreted 
-by the platform.  When a resource is deleted from the workspace, its properties are also deleted.
-</p>
-<p>There are two kinds of resource properties:
-</p>
-<ul>
-<li><b>Session properties</b> allow your plug-ins to easily cache information about a resource in key-value pairs.
-The values are arbitrary objects.&nbsp; These properties are maintained in memory and lost when a resource is 
-deleted from the workspace, or when the project or workspace is closed.</li>
-<li><b>Persistent properties</b> are used to store resource-specific information on disk.  The value of a 
-persistent property is an arbitrary string. Your plug-in decides how to interpret the string.  The strings are 
-intended to be short (under 2KB).  Persistent properties are stored on disk with the platform metadata and 
-maintained across platform shutdown and restart.</li>
-</ul>
-<p>If you follow the convention of qualifying property key names with the unique id of your plug-in, you won't 
-have to worry about your property names colliding with those of other plug-ins.
-</p>
-<p>If your plug-in needs to store persistent information about a project that is much larger than 2 KB, then these
-properties should be exposed as resources in their own right, rather than using the persistent properties API.
-</p>
-<p>See <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">
-IResource</a></b> for a description of the API for getting and setting the different kinds
-of resource properties.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm b/bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm
deleted file mode 100644
index 005f0b7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/resInt_workspace.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Resources and the workspace
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Resources and the workspace</H2>
-<P >
-The central hub for your user's data files is called a <b>workspace</b>.  You can think of the platform 
-workbench as a tool that allows the user to navigate and manipulate the workspace.  The resources 
-plug-in provides APIs for creating, navigating, and manipulating resources in a workspace. The workbench 
-uses these APIs to provide this functionality to the user. Your plug-in can also use these APIs.</P>
-<P >
-From the standpoint of a resource-based plug-in, there is exactly one workspace, and it is always open for 
-business as long as the plug-in is running.  The workspace gets opened automatically when the resources 
-plug-in is activated, and closed when the platform is shut down.  If your plug-in requires the resources 
-plug-in, then the resources plug-in will be started before your plug-in, and the workspace will be available to you.</P>
-<P >
-The workspace contains a collection of resources.  From the user's perspective, there are three different types 
-of resources:  <b>projects</b>, <b>folders</b>, and <b>files</b>. A project is a collection of any number of 
-files and folders.  It is a container for organizing other resources that relate to a specific area.  Files and 
-folders are just like files and directories in the file system.  A folder contains other folders or files.  
-A file contains an arbitrary sequence of bytes.  Its content is not interpreted by the platform.</P>
-<P >
-A workspace's resources are organized into a tree structure, with projects at the top, and folders and files 
-underneath. A special resource, the workspace root resource, serves as the root of the resource tree. 
-The workspace root is created internally when a workspace is created and exists as long as the workspace exists.</P>
-<P >
-A workspace can have any number of projects, each of which can be stored in
-a different location in some file system.</P>
-<P>
-The workspace resource namespace is always case-sensitive and  case-preserving. 
-Thus the workspace allows multiple sibling resources to exist with names that 
-differ only in case.  The workspace also doesn't put any restrictions on valid characters 
-in resource names, the length of resource names, or the size of resources on disk.  
-Of course, if you store resources in a file system that is not case-sensitive, or that does
-have restrictions on resource names, then those restrictions will show through
-when you actually try to create and modify resources.
-</P>
-<H3>
-A sample resource tree</H3>
-<P >
-The tree below (represented in the workbench navigator view) illustrates a typical hierarchy of resources in a 
-workspace. The (implied) root of the tree is the workspace root.  The projects are immediate children of the 
-workspace root.  Each node (other than the root) is one of the three kinds of resources, and each has a name that 
-is different from its siblings. </P>
-<P >
-<img src="images/navigator.png" alt="Navigator view with sample workspace" border="0">
-</P>
-
-<P >
-Resource names are arbitrary strings (almost -- they must be legal file names).  
-The platform itself does not dictate resource names, nor does it specify any names with special
-significance.&nbsp; (One exception is that you cannot name a project &quot;<b>.metadata</b>&quot;
-since this name is used internally.) </P>
-<P >
-Projects contain files and folders, but not other projects. Projects and folders
-are like directories in a file system.&nbsp; When you delete a project, you will
-be asked whether you want to delete all of the files and folders that it
-contains.&nbsp; Deleting a folder from a project will delete
-the folder and all of its children.  Deleting a file is analogous to deleting a file in the file system.  </P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime.htm
deleted file mode 100644
index 5d81d69..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Runtime overview</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Runtime overview</H1>
-<p>
-The Eclipse runtime defines the plug-ins (<b>org.eclipse.osgi</b> and <b>org.eclipse.core.runtime</b>) on which all
-other plug-ins depend.  The runtime is responsible for defining a structure for plug-ins and the implementation
-detail (bundles and classloaders) behind them.  The runtime is also responsible for finding and executing the main
-Eclipse application and for maintaining a registry of plug-ins, their extensions, and extension points.
-</p>
-<p>
-The runtime also provides an assortment of utilities, such as logging, debug trace options, 
-adapters, a preference store, and a concurrency infrastructure. Of course, as 
-a minimal kernel, the runtime is only interesting once plug-ins that make use of it and
-perform some kind of task are created.  Like Atlas, the runtime plug-in stoically resides at the bottom
-of the plug-in heap, holding the Eclipse universe aloft on its steady shoulders.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_app_model.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_app_model.htm
deleted file mode 100644
index bfe09d7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_app_model.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Runtime application model</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Runtime application model</H2>
-<p> The platform runtime provides an application container for controlling and executing
-  applications.  The runtime application container implements the Application Admin 
-  service specification included in the OSGi R4 specification.  The application container is 
-  responsible for discovering all available applications and registering an
-  <a href="http://www.osgi.org/javadoc/r4v42/org/osgi/service/application/ApplicationDescriptor.html">
-  ApplicationDescriptor</a> OSGi service for each application that is available.  An ApplicationDescriptor 
-  service can be used to launch an application.  When an application is launched an 
-  <a href="http://www.osgi.org/javadoc/r4v42/org/osgi/service/application/ApplicationHandle.html">
-  ApplicationHandle</a> OSGi service is registered to represent the instance of the running 
-  application.  An ApplicationHandle service can be used to shutdown an application.
-  See the <a href="http://www.osgi.org/javadoc/r4v42/org/osgi/service/application/package-summary.html">org.osgi.service.application</a>
-  package and the <a href="http://www.osgi.org/Download/Release4V41">OSGi R4.1 specification</a> for more
-  information.
-</p>
-<h3>
-The default application
-</h3>
-<p>
-A given Eclipse configuration may contain many products and applications.  An Eclipse configuration 
-specifies a default application which is launched by the application container as soon as the platform 
-runtime is up and running.  The default application can be specified by one of the following 
-configuration options</p>
-<ul>
-<li><a href="../reference/misc/runtime-options.html#eclipseproduct">eclipse.product</a> - 
-identifies the product to launch the platform runtime with. A product supplies branding information 
-(window icons, title bar text etc.) as well as defining the default application to run.</li>
-<li><a href="../reference/misc/runtime-options.html#eclipseapplication">eclipse.application</a> - 
-identifies the application to launch the platform runtime with.  This option overrides default application 
-defined by the product.</li>
-</ul>
-
-<h3>
-Defining an application
-</h3>
-<p>
-Plug-ins may define their own applications using the 
-<a href="../reference/extension-points/org_eclipse_core_runtime_applications.html"><b>org.eclipse.core.runtime.applications</b></a> 
-extension.  In this extension, the plug-in defines the name and ID of the application, as well a class that implements
-the application.  The class which implements the application is used to launch and shutdown application instances.
-</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_components.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_components.htm
deleted file mode 100644
index c198e97..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_components.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Runtime components</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Runtime components</H2>
-<p> The Eclipse runtime itself is factored into several components:
-</p><ul>
-<li><b>org.eclipse.core.contenttype</b> - <a href="runtime_content.htm">Content type mechanism</a></li>
-<li><b>org.eclipse.core.jobs</b> - <a href="runtime_jobs.htm">Concurrency infrastructure</a></li>
-<li><b>org.eclipse.core.net</b> - <a href="network.htm">Network and proxy management infrastructure</a></li>
-<li><b>org.eclipse.equinox.app</b> - <a href="runtime_app_model.htm">Application Model</a></li>
-<li><b>org.eclipse.equinox.common</b> - Common basic functionality</li>
-<li><b>org.eclipse.equinox.preferences</b> - <a href="runtime_preferences.htm">Runtime preferences</a></li>
-<li><b>org.eclipse.equinox.registry</b> - <a href="runtime_registry.htm">Extension registry</a></li>
-<li><b>org.eclipse.equinox.security</b> - <a href="runtime_registry.htm">Security infrastructure</a></li>
-</ul>
-<p> If your plug-in has a dependency on the <b>org.eclipse.core.runtime</b>, then it will continue to 
-run unchanged. However, if you would like to minimize the number of dependencies, then you are able to 
-pick only the runtime bundles that you use.</p>
-<p> If you would like to use Import-Package directive (rather than Require-Bundle) then you should be 
-aware that the <b><a href="../reference/api/org/eclipse/core/runtime/package-summary.html">org.eclipse.core.runtime</a></b> 
-package is split across several bundles. </p>
-<p>To import only the content of this package provided by 
-the <b>org.eclipse.equinox.common</b> bundle, use this line in the manifest file:</p>
-<pre>
-	Import-Package: org.eclipse.core.runtime; common="split" 
-</pre>
-<p> To import the content of the package from the <b>org.eclipse.equinox.registry</b> and 
-<b>org.eclipse.equinox.common</b> bundles, use:</p>
-<pre>
-	Import-Package: org.eclipse.core.runtime; registry="split"
-</pre>
-<p> And to import the complete package, use:</p>
-<pre>
-	Import-Package: org.eclipse.core.runtime
-</pre>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm
deleted file mode 100644
index 55cd517..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Content types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Content types</h2>
-<p>The <b><a href="../reference/api/org/eclipse/core/runtime/content/package-summary.html">org.eclipse.core.runtime.content</a></b> 
-  package provides support for detecting the content type for data streams. Content 
-  types are used by several content-sensitive features of Eclipse, such as automatic 
-  encoding determination, editor selection, and menu contributions. A central 
-  content registry allows plug-ins to request content type detection and to find 
-  out what content types are available and how they related to each other. The 
-  content type registry is extensible so plug-ins can contribute new content type 
-  definitions.</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm
deleted file mode 100644
index be78bf4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_contributing.htm
+++ /dev/null

@@ -1,132 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing content types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Contributing content types</h2>
-<h3>Providing a new content type</h3>
-<p>The platform defines some fundamental content types, such as plain text and 
-  XML. These content types are defined the same way as those contributed by any 
-  other plug-ins. We will look at how the platform defines some of its content 
-  types in order to better understand the content type framework.</p>
-<p>Plug-ins define content types by contributing an extension for the extension 
-  point <b><a href="../reference/extension-points/org_eclipse_core_runtime_contentTypes.html">org.eclipse.core.runtime.contentTypes</a></b>. 
-  In this extension, a plug-in specifies a simple id and name for the content 
-  type (the full id is always the simple id prefixed by the current namespace). 
-  The following snippet shows a trimmed down version of the <code>org.eclipse.core.runtime.text</code> 
-  content type contribution:</p>
-<pre>
-	&lt;extension point="org.eclipse.core.runtime.contentTypes"&gt;
-		&lt;content-type 
-			id="text"
-			name="%textContentTypeName"&gt;
-			file-extensions="txt"&gt;
-			&lt;describer class=&quot;org.eclipse.core.internal.content.TextContentDescriber&quot;/&gt;
-		&lt;/content-type&gt;
-		...</pre>
-<p>The <code>file-extensions</code> attribute defines what file extensions are 
-  associated with the content type (in this example, &quot;.txt&quot;). The <code>file-names</code> 
-  attribute (not used in this case) allows associating full names. Both attributes 
-  are taken into account by the platform when performing content type detection 
-  and description (if the client provides a file name).</p>
-<p>The <code>describer</code> element is used to define a <em>content describer</em> 
-  for the content type.</p>
-<h3>Detecting and describing content</h3>
-<p>A content type should provide a content describer if there are any identifiable 
-  characteristics that allow automatic content type detection, or any interesting 
-  properties in data belonging to the content type. In the case of <code>org.eclipse.core.runtime.text</code>, 
-  it is not possible to figure out the content type by just looking at the contents. 
-  However, text streams might be prepended by a <em>byte order mark</em>, which 
-  is a property clients might be interested in knowing about, so this warrants 
-  a content describer.</p>
-<p>The describer is an implementation of <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentDescriber.html">IContentDescriber</a></b> 
-  or <b><a href="../reference/api/org/eclipse/core/runtime/content/ITextContentDescriber.html">ITextContentDescriber</a></b>. 
-  The latter is a specialization of the former that must be implemented by describers 
-  of text-oriented content types. Regardless the nature of the content type, the 
-  describer has two responsibilities: helping determining whether its content 
-  type is appropriate for a given data stream, and extracting interesting properties 
-  from a data stream that supposedly belongs to its content type.</p>
-<p>The method <b>describe(stream, description)</b> is called whenever the platform 
-  is trying to determine the content type for a particular data stream or describe 
-  its contents. The description is <code>null</code> when only detection is requested. 
-  Otherwise, the describer should try to fill the content description with any 
-  properties that could be found <em>by reading the stream</em>, and only those. 
-  The content type markup should be used to declare any properties that have default 
-  values (for example, <code>org.eclipse.core.runtime.xml</code> declares UTF-8 
-  as the default charset).</p>
-<p>When performing its duty, the content describer is expected to execute as quickly 
-  as possible. The less the data stream has to be read, the better. Also, <em>it 
-  is expected that the content describer implementation be declared in a package 
-  that is exempt from plug-in activation (see the <a href="../reference/misc/bundle_manifest.html">Eclipse-AutoStart</a> 
-  bundle manifest header). Since all describers are instantiated when the content 
-  type framework is initialized, failure in complying with this requirement causes 
-  premature activation, which must be avoided. Future implementations of the platform 
-  might refuse to instantiate describers if doing so would trigger activation 
-  of the corresponding plug-in.</em></p>
-<h3>Extending an existing content type</h3>
-
-<p>Content types are hierarchical in nature. This allows new content types to 
-  leverage the attributes or behavior of more general content types. For example, 
-  a content type for XML data is considered a child of the text content type: 
-</p>
-<pre>&lt;content-type 
-	id=&quot;xml&quot;
-	name=&quot;%xmlContentTypeName&quot;
-	base-type=&quot;org.eclipse.core.runtime.text&quot;
-	file-extensions=&quot;xml&quot;&gt;
-	&lt;describer class=&quot;org.eclipse.core.internal.content.XMLContentDescriber&quot;/&gt;
-	&lt;property name=&quot;charset&quot; default=&quot;UTF-8&quot;/&gt;
-&lt;/content-type&gt;</pre>
-<p>A XML file is deemed a kind of text file, so any features applicable to the 
-  latter should be applicable to the former as well.</p>
-<p>Note that the XML content type overrides several content type attributes originally 
-  defined in the Text content type such as the file associations and the describer 
-  implementation. Also, this content type declares a default property value for 
-  <code>charset</code> property. That means that during content description for 
-  a data stream considered as belonging to the XML content type, if the describer 
-  does not fill in the charset property, the platform will set it to be &quot;UTF-8&quot;.</p>
-<p>As another example, the <code>org.eclipse.ant.core.antBuildFile</code> content 
-  type (for Ant Build Scripts) extends the XML content type:</p>
-<pre>&lt;content-type  <br>	id=&quot;antBuildFile&quot; <br>	name=&quot;%antBuildFileContentType.name&quot; <br>	base-type=&quot;org.eclipse.core.runtime.xml&quot;<br>	file-names=&quot;build.xml&quot;<br>	file-extensions=&quot;macrodef,ent,xml&quot;&gt; <br>	&lt;describer <br>		class=&quot;org.eclipse.ant.internal.core.contentDescriber.AntBuildfileContentDescriber&quot;&gt;<br>	&lt;/describer&gt; <br>&lt;/content-type&gt;</pre>
-<p>Note that the default value for the charset property is inherited. It is possible 
-  to cancel an inherited property or describer by redeclaring them with the empty 
-  string as value.</p>
-<h4>Additional file associations</h4>
-<p>New file associations can be added to existing content types. For instance, 
-  the Resources plug-in associates the <code>org.eclipse.core.runtime.xml</code> 
-  to &quot;.project&quot; files:</p>
-<pre>&lt;extension point="org.eclipse.core.runtime.contentTypes"&gt;
-	&lt;file-association content-type=&quot;org.eclipse.core.runtime.xml&quot; file-names=&quot;.project&quot;/&gt;
-	...
-</pre>
-<h4>Content type aliasing</h4>
-<p>Due to the extensible nature of Eclipse, a content type a plug-in rely on may 
-  not be available in a given product configuration. This can be worked around 
-  by using content type aliasing. A <em>content type alias</em> is a placeholder 
-  for another preferred content type whose availability is not guaranteed. For 
-  instance, the Runtime declares an alias (<code>org.eclipse.core.runtime.properties</code>) 
-  for the Java properties content type provided by the Java development tools (JDT) 
-  (<code>org.eclipse.jdt.core.javaProperties</code>):</p>
-<pre>&lt;!-- a placeholder for setups where JDT's official type is not available --&gt;			<br>&lt;content-type 
-	id=&quot;properties&quot; 
-	name=&quot;%propertiesContentTypeName&quot; <br>	base-type=&quot;org.eclipse.core.runtime.text&quot;<br>	alias-for=&quot;org.eclipse.jdt.core.javaProperties&quot;<br>	file-extensions=&quot;properties&quot;&gt;<br>	&lt;property name=&quot;charset&quot; default=&quot;ISO-8859-1&quot;/&gt;<br>&lt;/content-type&gt;		</pre>
-
-
-
-<p>This provides plug-ins with a placeholder they can refer to regardless the 
-  preferred content type is available or not. If it is, the alias content type 
-  is supressed from the content type catalog and any references to it are interpreted 
-  as references to the target content type. If it is not, the alias will be used 
-  as an ordinary content type.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm
deleted file mode 100644
index ee9603d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_content_using.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Using content types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Using content types</h2>
-<blockquote><i> Note:&nbsp; For this discussion, we specifically avoid the use 
-  of the word <b>file</b> when talking about content. The runtime content engine 
-  does not assume that content is contained in a file in the file system. However, 
-  it does include protocol that allows content types to be associated with file-naming 
-  patterns. In practice, these file names represent files in the file system, 
-  but nothing in the implementation of the content system assumes that the content 
-  is located in the file system. <a HREF="resInt_content.htm">File encoding and 
-  content types</a> discusses the file-oriented content type capabilities contributed 
-  by the platform resources plug-in and is a must-read for developers interested 
-  in using the content type API in that context.</i></blockquote>
-<h3>Finding out about content types</h3>
-<p>Content types are represented by <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html">IContentType</a></b>. 
-  This interface represents a unique content type that knows how to read a data 
-  stream and interpret content type-specific information. Content types are hierarchical 
-  in nature. For example, a content type for XML data is considered a child of 
-  the text content type. This allows new content types to leverage the attributes 
-  or behavior of more general content types. </p>
-<p>The <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b> 
-  is the entry point that gives access to most of the content type related API 
-  provided by the platform runtime. To obtain a reference to the platform <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b>, 
-  clients can use the <b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">Platform</a></b> 
-  API:</p>
-<pre>IContentTypeManager contentTypeManager = Platform.getContentTypeManager();</pre>
-<p> Clients can use the platform <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b> 
-  to find out about the content types in the system. </p>
-<ul>
-  <li><b>getAllContentTypes</b> allows clients to get all of the content types 
-    defined in the platform. </li>
-  <li><b>getContentType</b> allows clients to obtain a content type by its unique 
-    identifier.</li>
-</ul>
-<h3>Detecting the content type for a data stream</h3>
-<p>Given a stream of bytes, it is possible to determine its content type by calling 
-  the <b><a href="../reference/api/org/eclipse/core/runtime/content/IContentTypeManager.html">IContentTypeManager</a></b> 
-  API as follows:</p>
-<pre>
-InputStream stream = ...;
-IContentType contentType = contentTypeManager.findContentTypeFor(stream, &quot;file.xml&quot;);
-stream.close();
-</pre>
-<p>This will return the most appropriate <a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html"><strong>IContentType</strong></a> 
-  given the input provided, or <code>null</code> if none can be found. Multiple 
-  content types might be deemed appropriate for a given data stream. In that case, 
-  the platform uses some heuristics to determine which one should be selected. 
-  The file name is the first criterion by which content types are selected. It 
-  can be omitted, but this has two issues: the results might not be as correct 
-  because many unrelated content types might accept the same input; there is also 
-  a big performance hit, since all content types in the platform have to be given 
-  a chance of analysing the stream. So, unless it is not available, clients should 
-  always provide a file name along with the stream.</p>
-<h3>Describing a data stream</h3>
-<p>Another interesting feature of the content type support in the platform is 
-  the ability of <em>describing the contents</em> of a binary or character stream. 
-  The following code snippet shows how to do that:</p>
-<pre>InputStream stream = ...; 
-IContentDescription description = contentTypeManager.getDescriptionFor(stream, &quot;file.xml&quot;);
-stream.close();</pre>
-<p>The returned <strong><a href="../reference/api/org/eclipse/core/runtime/content/IContentDescription.html">IContentDescription</a></strong> 
-  instance describes the content type and additional relevant information extracted 
-  from the contents provided. The content description stores content-specific 
-  properties in form of key/value pairs. The platform itself is able to describe 
-  properties such as the character set and the byte order of text-based streams, 
-  but others can be defined by content type providers.</p>
-<h3>Providing content-sensitive features</h3>
-<p>New content types are often defined as specialization of existing ones. This 
-  hierarchy establishes a &quot;is a&quot; relationship between a derived content 
-  type and its base type. Plug-in developers must honor this when implementing 
-  content sensitive features. If a given feature is applicable to a given content 
-  type, the feature must be applicable to any derived content types as well. The 
-  <strong>IContentType.isKindOf(IContentType superType) </strong>method allows 
-  determining whether two <a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html"><strong>IContentType</strong></a>s 
-  are related. The method <strong>IContentType.getBaseType()</strong> allows determining 
-  the base type of a given <a href="../reference/api/org/eclipse/core/runtime/content/IContentType.html"><strong>IContentType</strong></a>.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
deleted file mode 100644
index e0719a5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs.htm
+++ /dev/null

@@ -1,222 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Concurrency infrastructure</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Concurrency infrastructure</H2>
-<p>
-One of the major challenges of a complex system is to remain responsive while tasks are being performed.  This
-challenge is even greater in an extensible system, when components that weren't designed to run together are
-sharing the same resources.  The
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/package-summary.html"> org.eclipse.core.runtime.jobs</a></b> 
-package addresses this challenge by providing infrastructure for scheduling, executing, and managing 
-concurrently running operations.   This infrastructure is based on the use of <i>jobs</i> to represent
-a unit of work that can run asynchronously.</p>
-<h3>Jobs</h3>
-The <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> class represents
-a unit of asynchronous work running concurrently with other jobs.  To perform a task, a plug-in creates 
-a job and then <i>schedules</i> it.  Once a job is scheduled, it is added to a job queue managed by the 
-platform.  The platform uses a background scheduling thread to manage all of the pending jobs.  As a running
-job completes, it is removed from the queue and the platform decides which job to run next.  When a job 
-becomes active, the platform invokes its <b>run()</b> method.  Jobs are best demonstrated with a simple example:
-<pre>
-   class TrivialJob extends Job {
-      public TrivialJob() {
-         super("Trivial Job");
-      }
-      public IStatus run(IProgressMonitor monitor) {
-         System.out.println("This is a job");
-         return Status.OK_STATUS;
-      }
-   }
-</pre>
-The job is created and scheduled in the following snippet:
-<pre>
-   TrivialJob job = new TrivialJob();
-   System.out.println("About to schedule a job");
-   job.schedule();
-   System.out.println("Finished scheduling a job");
-</pre>
-The output of this program is timing dependent.  That is, there is no way
-to be sure when the job's <b>run</b> method will execute in relation
-to the thread that created the job and scheduled it.  The output will
-either be:
-<pre>
-   About to schedule a job
-   This is a job
-   Finished scheduling a job
-</pre>
-or:
-<pre>
-   About to schedule a job
-   Finished scheduling a job
-   This is a job
-</pre>
-
-<p>
-If you want to be certain that a job has completed before continuing, you can use
-the <b>join()</b> method.  This method will block the caller until the job has completed, or 
-until the calling thread is interrupted.  Let's rewrite our snippet from above in a more 
-deterministic manner:
-</p>
-<pre>   TrivialJob job = new TrivialJob();
-   System.out.println("About to schedule a job");
-   job.schedule();
-   job.join();
-   if (job.getResult().isOk())
-      System.out.println("Job completed with success");
-   else
-      System.out.println("Job did not complete successfully");
-</pre>
-Assuming the <b>join()</b> call is not interrupted, this method is guaranteed to
-return the following result:
-<pre>
-   About to schedule a job
-   This is a job
-   Job completed with success
-</pre>
-<p>
-Of course, it is generally not useful to join a job immediately after scheduling it,
-since you obtain no concurrency by doing so. In this case you might as well do the work
-from the job's run method directly in the calling thread.  We'll look at some examples later on where 
-the use of join makes more sense.
-</p>
-<p>
-The last snippet also makes use of the job <b>result</b>.  The result
-is the <b><a href="../reference/api/org/eclipse/core/runtime/IStatus.html">IStatus</a></b>
-object that is returned from the job's <b>run()</b> method.  You can use this result
-to pass any necessary objects back from the job's run method.  The result can also be used to
-indicate failure (by returning an <b><a href="../reference/api/org/eclipse/core/runtime/IStatus.html">IStatus</a></b>
-with severity <b>IStatus.ERROR</b>), or cancellation (<b>IStatus.CANCEL</b>).
-</p>
-<h3>Common job operations</h3>
-<p>
-We've seen how to schedule a job and wait for it complete, but there are many other
-interesting things you can to do jobs.  If you
-schedule a job but then decide it is no longer needed, the job can be stopped using
-the <b>cancel()</b> method.  If the job has not yet started running when canceled,
-the job is immediately discarded and will not run.  If, on the other hand, the job 
-has already started running, it is up to the job whether it wants to respond to the cancellation.
-When you are trying to cancel a job, waiting for it using the <b>join()</b> method comes in handy.
-Here is a common idiom for canceling a job, and waiting until the job is finished before
-proceeding:</p>
-<pre>   if (!job.cancel())
-      job.join();
-</pre>
-<p>If the cancellation does not take effect immediately, then <b>cancel()</b> will return 
-false and the caller will use <b>join()</b> to wait for the job to successfully cancel.
-</p>
-<p>
-Slightly less drastic than cancellation is the <b>sleep()</b> method.  Again,
-if the job has not yet started running, this method will cause the
-job to be put on hold indefinitely.  The job will still be remembered by the platform,
-and a <b>wakeUp()</b> call will cause the job to be added to the wait
-queue where it will eventually be executed. 
-</p>
-<h3>Job states</h3>
-<p>
-A job goes through several states during its lifetime.  Not only can it be manipulated through API
-such as <b>cancel()</b> and <b>sleep()</b>, but its state also changes as the platform runs and completes the
-job.  Jobs can move through the following states:</p>
-<ul>
-<li><b>WAITING</b> indicates that the job been scheduled to run, but is not running yet.</li>
-<li><b>RUNNING</b> indicates that the job is running.</li>
-<li><b>SLEEPING</b> indicates that the job is sleeping due to a sleep request or because it was scheduled
-to run after a certain delay.</li>
-<li><b>NONE</b> indicates that the job is not waiting, running, or sleeping.  A job is in this state when
-it has been created but is not yet scheduled.  It is also in this state after it is finished running or when
-it has been canceled.</li>
-</ul>
-<p>A job can only be put to sleep if it is currently <b>WAITING</b>.  Waking up a sleeping job will put it back in the
-<b>WAITING</b> state.  Canceling a job will return it to the <b>NONE</b> state.
-</p>
-<p>
-If your plug-in needs to know the state of a particular job, it can register a <i>job change listener</i> that is
-notified as the job moves through its life-cycle.  This is useful for showing progress or otherwise reporting on
-a job.  
-</p>
-<h3>Job change listeners</h3>
-<p>
-The <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> method
-<b>addJobChangeListener</b> can be used to register a listener on a particular job.  
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobChangeListener.html">IJobChangeListener</a></b>
-defines protocol for responding to the state changes in a job:
-</p>
-<ul>
-<li><b>aboutToRun</b> is sent when the job is about to be run.</li>
-<li><b>awake</b> is sent when a previously sleeping job is now waiting to be run.</li>
-<li><b>done</b> is sent when a job finishes execution.</li>
-<li><b>running</b> is sent when a job starts running.</li>
-<li><b>scheduled</b> is sent when a job is scheduled and waiting in the queue of jobs.</li>
-<li><b>sleeping</b> is sent when a waiting job is put to sleep.</li>
-</ul>
-<p>In all of these cases, the listener is provided with an
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobChangeEvent.html">IJobChangeEvent</a></b>
-that specifies the job undergoing the state change and status on its completion (if it is done).
-</p>
-<blockquote><i>
-Note:  Jobs also define the <b>getState()</b> method for obtaining the (relatively) current
-state of a job.  However, this result is not always reliable since jobs run in a different thread and may
-change state again by the time the call returns.  Job change listeners are the recommended mechanism
-for discovering state changes in a job.
-</i></blockquote>
-<h3>The job manager</h3>
-<p>
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-defines protocol for working with all of the jobs in the system.  Plug-ins that show progress or otherwise
-work with the job infrastructure can use <b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-to perform tasks such as suspending all jobs in the system, finding out which job is running, or receiving progress
-feedback about a particular job.  The platform's job manager can be obtained using 
-<b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">Platform</a></b> API:</p>
-<pre>   IJobManager jobMan = Platform.getJobManager();
-</pre>
-<p>Plug-ins interested in the state of all jobs in the system can register a job change listener on the job manager rather
-than registering listeners on many individual jobs.  
-</p>
-<h3>Job families</h3>
-<p>
-It is sometimes easier for a plug-in to work with a group of related jobs as a single unit.
-This can be accomplished using <i>job families</i>.  A job declares that it belongs to a certain family by 
-overriding the <b>belongsTo</b> method:</p>
-<pre>
-   public static final String MY_FAMILY = "myJobFamily";
-   ...
-   class FamilyJob extends Job {
-      ...
-      public boolean belongsTo(Object family) {
-         return family == MY_FAMILY;
-      }
-   }
-</pre>
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-protocol can be used to cancel, join, sleep, or find all jobs in a family:
-<pre>
-   IJobManager jobMan = Platform.getJobManager();
-   jobMan.cancel(MY_FAMILY);
-   jobMan.join(MY_FAMILY, null);
-</pre>
-<p>Since job families are represented using arbitrary objects, you can store interesting
-state in the job family itself, and jobs can dynamically build family objects as needed.
-It is important to use family objects that are 
-fairly unique, to avoid accidental interaction with the families created by
-other plug-ins. 
-</p>
-<p>
-Families are also a convenient way of locating groups of jobs.  The method <b>IJobManager.find(Object family)</b> can
-be used to locate instances of all running, waiting, and sleeping jobs at any
-given time.
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
deleted file mode 100644
index c304435..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_locks.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Locks</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Locks</H3>
-<p>
-It's possible that multiple jobs in the system need to access and manipulate the same object.
-<b><a href="../reference/api/org/eclipse/core/runtime/jobs/ILock.html">ILock</a></b> defines protocol
-for granting exclusive access to a shared object.  When a job needs access to the shared object, it <i>acquires</i> a lock
-for that object.  When it is finished manipulating the object, it <i>releases</i> the lock. 
-</p>
-<p>A lock is typically created when the shared object is created or first accessed by a plug-in.  That is, code that
-has a reference to the shared object also has a reference to its lock.  We'll start by creating a lock, <b>myLock</b>, that
-will be used to control access to <b>myObject</b>:
-</p>
-<pre>   ...
-   myObject = initializeImportantObject();
-   IJobManager jobMan = Platform.getJobManager();
-   <b>myLock = jobMan.newLock();</b>
-   ...
-</pre>
-<p>A robust implementation of  <b><a href="../reference/api/org/eclipse/core/runtime/jobs/ILock.html">ILock</a></b> 
-is provided by the platform.  The job manager provides instances of this lock for use by clients.  These locks
-are aware of each other and can avoid circular deadlock.(We'll explain more about that statement in a moment.)
-</p>
-<p>Whenever code in a job requires access to <b>myObject</b>, it must first acquire 
-the lock on it.  The following snippet shows a common idiom for working with a lock:
-</p>
-<pre>...
-// I need to manipulate myObject, so I get its lock first.
-try {		
-	<b>myLock.acquire();</b>
-	updateState(myObject);  // manipulate the object
-} finally {
-	<b>lock.release();</b>
-}
-...
-</pre>
-<p>The <b>acquire()</b> method will not return until the calling job can be granted exclusive access to the lock.  
-In other words, if some other job has already acquired the lock, then this code will be blocked until the lock 
-is available.  Note that the code that acquires the lock and manipulates <b>myObject</b> is wrapped in 
-a <tt>try</tt> block, so that the lock can be released if any exceptions occur while working with the object.  
-</p>
-<p>Seems simple enough, right?  Fortunately, locks are pretty straightforward to use.  They are also reentrant, which
-means you don't have to worry about your job acquiring the same lock multiple times.  Each lock keeps a count of the
-number of acquires and releases for a particular thread, and will only release from a job when the number of 
-releases equals the number of acquires.
-</p>
-<h4>Deadlock</h4>
-<p>Earlier we noted that locks provided by the job manager are aware of each other and can avoid circular deadlock. 
-To understand how deadlock occurs, let's look at a simple scenario.  Suppose &quot;Job A&quot; acquires &quot;Lock A&quot; and 
-subsequently tries to acquire &quot;Lock B.&quot; Meanwhile, &quot;Lock B&quot; is held by &quot;Job B&quot; 
-which is now blocked waiting on &quot;Lock A.&quot;  This kind of deadlock indicates an underlying design problem
-with the use of the locks between the jobs.  While this simple case can be avoided easily enough, the chances
-of accidentally introducing deadlock increase as the number of jobs and locks used in your design increase.  
-</p> 
-<p>Fortunately, the platform will help you in identifying deadlocks.  When the job manager detects a deadlock 
-condition, it prints diagnostic information to the log describing the deadlock condition.  Then it breaks the 
-deadlock by temporarily granting access to the locks owned by a blocked job to other jobs that are waiting on them.  
-It is important to carefully test any implementation involving multiple locks and fix any deadlock conditions that
-are reported by the platform.
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
deleted file mode 100644
index 2576c03..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_progress.htm
+++ /dev/null

@@ -1,157 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Reporting progress</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Reporting progress</h3>
-<p>
-Long running jobs (those lasting more than a second) should report
-progress to the
-<b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-that is passed to the job's <b>run</b> method. The workbench progress
-view will
-show all progress messages and units of completed work given to this
-monitor. </p>
-<p>The supplied progress monitor should also be used to check for
-cancellation requests made from the progress view. When a user (or
-plug-in using job API) attempts to cancel a job, the <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-method <b>isCanceled()</b> will return <tt>true</tt>. It is the job's
-responsibility to frequently
-check the cancellation status of a job and respond to a cancellation by
-exiting the <b>run</b> method as soon as possible once it detects a
-cancellation. The following <b>run</b> method reports progress
-and responds to job cancellation:
-</p>
-<pre>   public IStatus run(IProgressMonitor monitor) {
-      final int ticks = 6000;
-      monitor.<b>beginTask</b>("Doing some work", ticks);
-      try {
-         for (int i = 0; i &lt; ticks; i++) {
-            if (monitor.<b>isCanceled</b>())
-               return Status.CANCEL_STATUS;
-            monitor.<b>subTask</b>("Processing tick #" + i);
-            //... do some work ...
-            monitor.<b>worked</b>(1);
-         }
-      } finally {
-         monitor.<b>done</b>();
-      }
-      return Status.OK_STATUS;<br>   }
-</pre>
-<p>The <b>beginTask</b> method is used to name the task in the
-corresponding progress view and to
-establish the total amount of work to be done so that the view can
-compute progress. The
-<b>subTask</b> messages will appear as a child in the progress tree as
-work is done. The progress view will calculate and display a percent
-completion based on the amount of work
-reported in the <b>worked</b> calls.
-</p>
-<h3>Progress monitors and the UI</h3>
-<p>
-As you can see, the <b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-class is designed with corresponding UI support in mind. The platform's
-UI plug-in provides support so that
-the workbench can show progress for jobs that are running. You can set
-up your jobs with this in mind, so that
-you can control how they are presented.<br>
-</p>
-<p>See <a href="workbench_jobs.htm">Workbench Concurrency Support</a>
-for a detailed look at the APIs available for showing progress for jobs.<br>
-</p>
-<h4>System jobs</h4>
-
-<p>What if your job is a low-level implementation detail that you don't
-want to show to users? You can flag your job as a <i>system job</i>. A
-system job is just like any other job, except the corresponding UI
-support will not set up a progress view or show any other UI
-affordances associated with running a job. If your job is not either
-directly initiated by a user, or a periodic task that can be configured
-by a user, then your job should be a system job. The protocol for
-setting a system job is simple:
-</p>
-<pre>   class TrivialJob extends Job {
-      public TrivialJob() {
-         super("Trivial Job");
-         <b>setSystem(true)</b>;
-      }
-      ...
-   }
-</pre>
-<p>The <b>setSystem</b> call must be made before the job is
-scheduled. An exception will be triggered if you attempt this call on a
-job that is currently waiting, sleeping, or running.
-</p>
-<h4>User jobs</h4>
-
-<p>If your job is a long running operation that is initiated by a user,
-then you should flag your job as a <i>user job</i>. A user job will
-appear in a modal progress dialog that provides a button
-for moving the dialog into the background. The workbench defines a user
-preference that controls whether
-these dialogs are ever modal. By defining your job as a user job, your
-progress feedback will
-automatically conform with the user preference for progress viewing.
-The protocol for setting a user job
-is similar:
-</p>
-<pre>   class TrivialJob extends Job {
-      public TrivialJob() {
-         super("Trivial Job");
-         <b>setUser(true)</b>;
-      }
-      ...
-   }
-</pre>
-<p>The <b>setUser</b> call must also be made before the job is scheduled. 
-</p>
-
-<h3>Progress groups</h3>
-
-<p><i>Progress groups</i> are another mechanism that can be used to
-influence the way that a job is shown in the UI. When it is more
-appropriate to show the aggregate progress of several related jobs in
-the UI, a special
-<b><a
- href="../reference/api/org/eclipse/core/runtime/IProgressMonitor.html">IProgressMonitor</a></b>
-that represents
-a group of related jobs can be created. This monitor is created using <b><a
- href="../reference/api/org/eclipse/core/runtime/jobs/IJobManager.html">IJobManager</a></b>
-protocol. The following snippet shows how to create a progress group
-and associate it with a job.
-</p>
-<pre>   ...
-   IJobManager jobMan = Platform.getJobManager();
-   myGroup = jobMan.createProgressGroup();
-   job.setProgressGroup(myGroup, 600);  // specify the units of work the job needs to show.
-   job.schedule()
-   ...
-</pre>
-<p>The group facility allows plug-ins to break tasks into multiple
-jobs if needed, but to report them to the user as if
-they are a single task. The progress group monitor will handle the
-details for computing the percentage completion
-relative to all of the jobs in the group.
-</p>
-<p>A job must be placed into the progress group before it is scheduled.
-After a job finishes running, its reference to the progress group is
-lost. If the job is to be scheduled again, it must be set into the
-group
-once again before it is scheduled.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
deleted file mode 100644
index 56df046..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_rules.htm
+++ /dev/null

@@ -1,228 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Scheduling rules</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Scheduling rules</H3>
-<p>
-Job <i>scheduling rules</i> can be used to control when your jobs run in relation to
-other jobs. In particular, scheduling rules allow you to prevent multiple jobs
-from running concurrently in situations where concurrency can lead to inconsistent
-results. They also allow you to guarantee the execution order of a series of jobs.
-The power of scheduling rules is best illustrated by an example. Let's start by 
-defining two jobs that are used to turn a light switch on and off concurrently:</p>
-<pre>   public class LightSwitch {
-      private boolean isOn = false;
-      public boolean isOn() {
-         return isOn;
-      }
-      public void on() {
-         new LightOn().schedule();
-      }
-      public void off() {
-         new LightOff().schedule();
-      }
-      class LightOn extends Job {
-         public LightOn() {
-            super("Turning on the light");
-         }
-         public IStatus run(IProgressMonitor monitor) {
-            System.out.println("Turning the light on");
-            isOn = true;
-            return Status.OK_STATUS;
-         }
-      }
-      class LightOff extends Job {
-         public LightOff() {
-            super("Turning off the light");
-         }
-         public IStatus run(IProgressMonitor monitor) {
-            System.out.println("Turning the light off");
-            isOn = false;
-            return Status.OK_STATUS;
-         }
-      }
-   }
-</pre>
-<p>Now we create a simple program that creates a light switch and turns it
-on and off again:</p>
-<pre>   LightSwitch light = new LightSwitch();
-   light.on();
-   light.off();
-   System.out.println("The light is on? " + switch.isOn());
-</pre>
-<p>If we run this little program enough times, we will eventually obtain the following output:</p>
-<pre>   Turning the light off
-   Turning the light on
-   The light is on? true
-</pre>
-<p>How can that be?  We told the light to turn on and then off, so its final state
-should be off!  The problem is that there was nothing preventing the
-<tt>LightOff</tt> job from running at the same time as the <tt>LightOn</tt>
-job.  So, even though the &quot;on&quot; job was scheduled first, their
-concurrent execution means that there is no way to predict the exact
-execution order of the two concurrent jobs. If the <tt>LightOff</tt> job ends
-up running before the <tt>LightOn</tt> job, we get this invalid result.
-What we need is a way to prevent the two jobs from running concurrently, and 
-that's where scheduling rules come in.</p>
-<p>
-We can fix this example by creating a simple scheduling rule that acts as a 
-<i>mutex</i> (also known as a <i>binary semaphore</i>):</p>
-<pre>   class Mutex implements ISchedulingRule {
-      public boolean isConflicting(ISchedulingRule rule) {
-         return rule == this;
-      }
-      public boolean contains(ISchedulingRule rule) {
-         return rule == this;
-      }
-   }
-</pre>
-<p>This rule is then added to the two light switch jobs from our previous example:</p>
-<pre>   public class LightSwitch {
-      <b>final MutextRule rule = new MutexRule();</b>
-      ...
-      class LightOn extends Job {
-         public LightOn() {
-            super("Turning on the light");
-            <b>setRule(rule);</b>
-         }
-         ...
-      }
-      class LightOff extends Job {
-         public LightOff() {
-            super("Turning off the light");
-            <b>setRule(rule);</b>
-         }
-         ...
-      }
-   }
-</pre>
-<p>
-Now, when the two light switch jobs are scheduled, the job infrastructure will
-call the <tt>isConflicting</tt> method to compare the scheduling rules of the
-two jobs. It will notice that the two jobs have conflicting scheduling rules, and 
-will make sure that they run in the correct order. It will also make sure they never
-run at the same time. Now, if you run the example program a million times,
-you will always get the same result:</p>
-<pre>   Turning the light on
-   Turning the light off
-   The light is on? false
-</pre>
-<p>
-Rules can also be used independently from jobs as a general locking mechanism.
-The following example acquires a rule within a try/finally block, preventing other
-threads and jobs from running with that rule for the duration between 
-invocations of <tt>beginRule</tt> and <tt>endRule</tt>.</p>
-<pre>   IJobManager manager = Platform.getJobManager();
-   try {
-      manager.beginRule(rule, monitor);
-      ... do some work ...
-   } finally {
-      manager.endRule(rule);
-   }
-</pre>
-<p>You should exercise extreme caution when acquiring and releasing scheduling
-rules using such a coding pattern. If you fail to end a rule for which you
-have called <tt>beginRule</tt>, you will have locked that rule forever.</p>
-<H3>Making your own rules</H3>
-<p>
-Although the job API defines the contract of scheduling rules, it does not actually
-provide any scheduling rule implementations. Essentially, the generic infrastructure
-has no way of knowing what sets of jobs are ok to run concurrently. By default,
-jobs have no scheduling rules, and a scheduled job is executed as fast as a 
-thread can be created to run it.</p> 
-<p>
-When a job does have a scheduling rule,
-the <tt>isConflicting</tt> method is used to determine if the rule conflicts with
-the rules of any jobs that are currently running. Thus, your implementation
-of <tt>isConflicting</tt> can define exactly when it is safe to execute your job.
-In our light switch example, the <tt>isConflicting</tt> implementation simply uses
-an identity comparison with the provided rule. If another job has the identical rule,
-they will not be run concurrently.  When writing your own scheduling rules, be
-sure to read and follow the API contract for <tt>isConflicting</tt> carefully.</p>
-<p>
-If your job has several unrelated constraints, you can compose multiple
-scheduling rules together using a 
-<a href="../reference/api/org/eclipse/core/runtime/jobs/MultiRule.html">MultiRule</a>.
-For example, if your job needs to turn on a light switch, and also write information to
-a network socket, it can have a rule for the light switch and a rule for write access to the socket,
-combined into a single rule using the factory method <tt>MultiRule.combine</tt>.</p>
-<H3>Rule hierarchies</H3>
-<p>
-We have discussed the <tt>isConflicting</tt> method on 
-<a href="../reference/api/org/eclipse/core/runtime/jobs/ISchedulingRule.html">ISchedulingRule</a>,
-but thus far have not mentioned the <tt>contains</tt> method. This method is
-used for a fairly specialized application of scheduling rules that many clients will not require.
-Scheduling rules can be logically composed into hierarchies for controlling access to
-naturally hierarchical resources. The simplest example to illustrate this concept is
-a tree-based file system. If an application wants to acquire an exclusive lock
-on a directory, it typically implies that it also wants exclusive access to the files
-and sub-directories within that directory. The <tt>contains</tt> method is
-used to specify the hierarchical relationship among locks. If you do not need
-to create hierarchies of locks, you can implement the <tt>contains</tt> method
-to simply call <tt>isConflicting</tt>.</p>
-<p>
-Here is an example of a hierarchical lock for controlling write access to <tt>java.io.File</tt> handles.
-</p>
-<pre>   public class FileLock implements ISchedulingRule {
-      private String path;
-      public FileLock(java.io.File file) {
-         this.path = file.getAbsolutePath();
-      }
-      public boolean <b>contains</b>(ISchedulingRule rule) {
-         if (this == rule)
-            return true;
-         if (rule instanceof FileLock)
-            return ((FileLock)rule).path.startsWith(path);
-         if (rule instanceof MultiRule) {
-            MultiRule multi = (MultiRule) rule;
-            ISchedulingRule[] children = multi.getChildren();
-            for (int i = 0; i &lt; children.length; i++)
-               if (!contains(children[i]))
-                  return false;
-            return true;
-         }
-         return false;
-      }
-      public boolean <b>isConflicting</b>(ISchedulingRule rule) {
-         if (!(rule instanceof FileLock))
-            return false;
-         String otherPath = ((FileLock)rule).path;
-         return path.startsWith(otherPath) || otherPath.startsWith(path);
-      }
-   }
-</pre>
-<p>The <tt>contains</tt> method comes into play if a thread tries to acquire
-a second rule when it already owns a rule. To avoid the possibility of deadlock,
-any given thread can only own <em>one</em> scheduling rule at any given time.
-If a thread calls <tt>beginRule</tt> when it already owns a rule, either through 
-a previous call to <tt>beginRule</tt> or by executing a job with a scheduling rule, 
-the <tt>contains</tt> method is consulted to see if the two rules are equivalent.
-If the <tt>contains</tt> method for the rule that is already owned returns <tt>true</tt>,
-the <tt>beginRule</tt> invocation will succeed. If the <tt>contains</tt> method returns
-<tt>false</tt> an error will occur.</p>
-<p>
-To put this in more concrete terms, say a thread owns our example <tt>FileLock</tt>
-rule on the directory at &quot;c:\temp&quot;. While it owns this rule, it is only allowed
-to modify files within that directory subtree. If it tries to modify files in other directories that
-are not under &quot;c:\temp&quot;, it should fail. Thus a scheduling rule is a 
-concrete specification for what a job or thread is allowed or not allowed to do. 
-Violating that specification will result in a runtime exception. In
-concurrency literature, this technique is known as <i>two-phase locking</i>. In a
-two-phase locking scheme, a process much specify in advance all locks it will need for a particular
-task, and is then not allowed to acquire further locks during the operation. Two-phase locking eliminates
-the hold-and-wait condition that is a prerequisite for circular wait deadlock. Therefore, it is impossible
-for a system using only scheduling rules as a locking primitive to enter a deadlock.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm
deleted file mode 100644
index 1ca693c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_jobs_scheduling.htm
+++ /dev/null

@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Job scheduling</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Job scheduling</H3>
-<p>
-Our examples so far have demonstrated simple job creation, scheduling, and progress reporting.  
-The job scheduling mechanism is actually more powerful than we've shown so far.  You can have more
-fine-grained control over the way your job is scheduled by using priorities, delays, and custom
-scheduling conditions.
-</p>
-<h4>
-Job priorities</h4>
-<p>
-A job <i>priority</i> can be used to establish the importance of a job relative to other jobs in the
-system.  Setting the priority of a job won't affect a job that is already running, but it will affect how
-a waiting job is scheduled relative to other jobs.  The priority of a job can be one of several pre-defined
-priority constants:</p>
-<ul>
-<li><b>INTERACTIVE</b> jobs generally have priority over other jobs.  They should be short-running or low
-on processor usage, so that they don't block other INTERACTIVE jobs from running.</li>
-<li><b>SHORT</b> jobs typically complete within a second, but may take a little longer.  They run in the
-background and have priority over all jobs except INTERACTIVE jobs. </li>
-<li><b>LONG</b> jobs are for longer running background jobs.  They run only after INTERACTIVE and
-SHORT jobs have been run. </li>
-<li><b>BUILD</b> jobs are for jobs associated with building tasks.  They are a lower priority than LONG.  BUILD jobs
-only run when all LONG jobs are complete.</li>
-<li><b>DECORATE</b> jobs are the lowest priority in the system.  They are used for tasks that provide information that
-may help supplement the UI, but that the user is not generally waiting for.</li>
-</ul>
-<p>The default priority for a job is LONG.  The following snippet creates the trivial job we used earlier, 
-but sets the priority to DECORATE to indicate that it is the lowest level priority:
-</p>
-<pre>   TrivialJob job = new TrivialJob();
-   <b>job.setPriority(Job.DECORATE);</b>
-   job.schedule();
-</pre>
-
-<h4>Scheduling with a delay</h4>
-
-<p>Another technique for controlling how a job is scheduled is to use a scheduling delay.  A scheduling delay
-can be specified when the job is scheduled.  The job will be delayed for the specified number of milliseconds
-before it is scheduled.
-</p>
-<pre>   TrivialJob job = new TrivialJob();
-   <b>job.schedule(1000);  // wait one second before scheduling</b>
-</pre>
-
-<h4>Rescheduling a job</h4>
-
-<p>Scheduling a job that is already waiting or is sleeping has no effect.  However, scheduling a job that is 
-already running will cause it to be rescheduled after it is finished.  This is a convenient mechanism for
-repetitive jobs such as background polling loops.  If the job is rescheduled multiple 
-times while it is running, it will only be rescheduled once with the most recently supplied delay.  The
-following snippet defines a job that reschedules itself to run 10 seconds after it finishes the
-current iteration.
-</p>
-<pre>   class RepetitiveTrivialJob extends Job {
-      public RepetitiveTrivialJob() {
-         super("Repetitive Trivial Job");
-      }
-      public IStatus run(IProgressMonitor monitor) {
-         System.out.println("Running the job.");
-         // reschedule after 10 seconds
-         <b>schedule(10000);</b>
-         return Status.OK_STATUS;
-      }
-   }
-</pre>
-
-<h4>Custom scheduling conditions</h4>
-
-<p>Additional protocol in the <b><a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html">Job</a></b> class
-allows a job to check for preconditions just before it is scheduled or run.  This is best demonstrated by example:
-</p>
-<pre>class JobWithPreconditions extends Job {
-	...
-	public boolean <b>shouldSchedule()</b> {
-		return super.shouldSchedule() &amp;&amp; checkJobPreconditions();
-	}
-	public boolean <b>shouldRun()</b> {
-		return super.shouldRun() &amp;&amp; checkJobPreconditions();
-	}
-	...
-}
-</pre>
-<p>The <b>shouldSchedule</b> method is called just before the job manager places the job in the queue.  This allows the job
-to cancel itself if basic preconditions for scheduling are not met.  The job should return <tt>false</tt> it
-is inappropriate to schedule it.  Likewise, the <b>shouldRun</b> method is called just before the job manager 
-runs the job.  Any additional conditions that must be met before the job is run must be checked at this time.  
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm
deleted file mode 100644
index 8cd7d9a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>The runtime plug-in model</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The runtime plug-in model</H2>
-<P >
-The platform runtime engine is started when a user starts an application developed with Eclipse.  
-The runtime implements the basic <b>plug-in</b> model and infrastructure used by the platform.  
-It keeps track of all of the installed plug-ins and the function that they provide. 
-</p>
-<p>A plug-in is a structured component that contributes code (or documentation or both) to the system and describes
-it in a structured way. Plug-ins can define <b>extension points</b>, well-defined 
-function points that can be extended by other plug-ins. When a plug-in contributes an implementation for an 
-extension point, we say that it adds an <b>extension</b> to the platform. These extensions and extension points
-are declared in the plug-ins's manifest (<b>plugin.xml</b>) file.
-</p>
-<P >
-Using a common extension model provides a structured way for plug-ins to describe the ways they can be extended, and 
-for client plug-ins to describe the extensions they supply.  Defining an extension point is much like defining 
-any other API.  The only difference is that the extension point is declared using XML instead of a code signature.
-Likewise, a client plug-in uses XML to describe its specific extension to the system.  
-</p>
-<p>A general goal of the runtime is that the end user should not pay a memory 
-  or performance penalty for plug-ins that are installed, but not used. The declarative 
-  nature of the platform extension model allows the runtime engine to determine 
-  what extension points and extensions are supplied by a plug-in without ever 
-  running it. Thus, many plug-ins can be installed, but none will be activated 
-  until a function provided by a plug-in has been requested according to the user's 
-  activity. This is an important feature in providing a scalable, robust platform. 
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm
deleted file mode 100644
index 0c9cf95..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_model_bundles.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Plug-ins and bundles</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Plug-ins and bundles</H3>
-<p>
-The mechanics for supporting plug-ins are implemented using the <a href="http://www.osgi.org">OSGi</a> framework.  From this
-standpoint, a plug-in is the same thing as an OSGi <b>bundle</b>.  The bundle and its associated classes specify and implement
-the process for Java class-loading, prequisite management, and the bundle's life-cycle.  For the rest of this discussion, we use
-the terms <b>plug-in</b> and <b>bundle</b> interchangeably, unless discussing a particular class in the framework.  
-</p>
-<h4>Plugin</h4>
-<p>
-The <b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b> class represents a plug-in that
-is running in the platform.  It is a convenient place to centralize the life-cycle aspects and overall 
-semantics of a plug-in.  A plug-in can implement specialized function for the <b>start</b> and <b>stop</b>
-aspects of its life-cycle.  Each life-cycle method includes a reference to a  
-<b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html">BundleContext</a></b> which can supply
-additional information.</p>
-<p>
-The <b>start</b> portion of the life-cycle is worth particular discussion.  We've seen already that information 
-about a plug-in can be obtained from the plug-in's manifest file without ever running any of the 
-plug-in's code.  Typically, some user action in the workbench causes a chain of events that 
-requires the starting of a plug-in.  From an implementation point of view, a plug-in is
-never started until a class contained in the plug-in needs to be loaded.
-</p>
-<p>
-The <b>start</b> method has been a convenient place to implement initialization and
-registration behavior for a plug-in.  However, it is important to realize that your plug-in
-can be started in many different circumstances.  Something as simple as obtaining an icon to decorate
-an object can cause one of your plug-in's classes to be loaded, thus starting your plug-in.  Over-eager 
-initialization can cause your plug-in's code and data to be loaded long before it is necessary.  Therefore,
-it's important to look closely at your plug-in's initialization tasks and consider alternatives
-to performing initialization at start-up.</p>
-<ul>
-<li><b>Registration</b> activities such as registering listeners or starting background threads are appropriate
-during plug-in start-up if they can be performed quickly.  However, it is advisable to trigger these
-actions as part of accessing the plug-in's data if the registration activities have side-effects such
-as initializing large data structures or performing unrelated operations. </li>
-<li><b>Initialization</b> of data is best done lazily, when the data is first accessed, rather than automatically
-in the start-up code.  This ensures that large data structures are not built until they are truly necessary.</li>
-</ul>
-
-<h4>Bundle Context</h4>
-<p>
-Life-cycle management is where the OSGi &quot;bundle&quot; terminology and the platform's 
-&quot;plug-in&quot; terminology meet.  When your plug-in is started, it is given a reference to a <b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html">
-BundleContext</a></b> from which it can obtain information related to the plug-in.  The
-<b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html">BundleContext</a></b>
-can also be used to find out about other bundles/plug-ins in the system.  
-</p>
-<p>
-<b>BundleContext.getBundles()</b> can be used to obtain an array of all bundles in the system.  Listeners for
-<b>BundleEvent</b> can be registered so that your plug-in is aware when another bundle has a change
-in its life-cycle status.  See the javadoc for 
-<b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html">BundleContext</a></b> and
-<b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleEvent.html">BundleEvent</a></b> for more information.
-</p>
-<blockquote><i>
-Prior to 3.0, a plug-in registry (<b>IPluginRegistry</b>) was provided to supply similar information.  For example,
-it could be queried for the plug-in descriptors of all plug-ins in the system.  This registry is now deprecated and
-<b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleContext.html">BundleContext</a></b> should be
-used for this purpose.  The platform registry is now used exclusively for information about extensions 
-and extension points.
-</i></blockquote>
-<h4>Bundle Activator</h4>
-<p>
-The <b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleActivator.html">BundleActivator</a></b> interface defines
-the start and stop behavior implemented in 
-<b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b>.  Although the
-<b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b> class is a convenient place
-to implement this function, a plug-in developer has complete freedom to implement the interface for
-<b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleActivator.html">BundleActivator</a></b> in any class
-appropriate for the plug-in's design.  In fact, your plug-in need not implement this interface at all if it
-does not have specific life-cycle management needs.  </p>
-<h4>Bundles</h4>
-<p>
-Underneath every plug-in lies an OSGi bundle managed by the framework.
-The <b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/Bundle.html">Bundle</a></b> is the OSGi unit of modularity.  Fundamentally, a 
-bundle is just a collection of files (resources and code) installed in the 
-platform.  Each bundle has its own Java
-class loader, and includes protocol for starting, stopping, and uninstalling itself.  From the Eclipse platform 
-point of view, <b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/Bundle.html">Bundle</a></b> is merely an implementation 
-class.   Plug-in developers do not extend the bundle class, but use <b><a href="../reference/api/org/eclipse/core/runtime/Plugin.html">Plugin</a></b>
-or other <b><a href="http://www.osgi.org/javadoc/r4v42/org/osgi/framework/BundleActivator.html">BundleActivator</a></b> implementations
-to represent the plug-in.</p>
-
-
-</BODY>
-</HTML>
-
-

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm
deleted file mode 100644
index 1f0dad3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_preferences.htm
+++ /dev/null

@@ -1,136 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Runtime preferences</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Runtime preferences</H2>
-<p> The <b><a href="../reference/api/org/eclipse/core/runtime/preferences/package-summary.html">org.eclipse.core.runtime.preferences</a></b> 
-  package provides infrastructure for storing a plug-in's preferences. Preferences 
-  typically map to settings controlled by the user on the <b>Preferences</b> page, 
-  although this is not required by the underlying infrastructure. Plug-in preferences 
-  are key/value pairs, where the key describes the name of the preference, and 
-  the value is one of several different types (boolean, double, float, int, long, 
-  or string). Preferences can be stored and retrieved by the platform from the 
-  file system. The exact location of the saved preferences depends upon the <b>scope</b> 
-  of the preference. </P>
-<h3>
-Preference scopes
-</h3>
-The <b>scope</b> of a preference is closely related to where the preference is stored.  Plug-in
-developers can decide which of the standard scopes apply for their preferences, or can define 
-new scopes that make sense for their plug-in.  Let's look first at the scopes defined by
-the platform runtime:
-<ul>
-<li><b>Instance</b> scoped preferences are stored per workspace, or per running instance of the platform.</li>
-<li><b>Configuration</b> scoped preferences are stored per installation of the platform.  They are shared between
-workspaces.  For example, if a user has a single installation of the platform, but runs several different workspaces, 
-preferences scoped at the configuration level will be shared between the workspaces.</li>
-<li><b>Default</b> scoped preferences represent the default values for preferences.  These are not changed or stored
-by the platform.  However, the values originate from files stored with the plug-in's product
-or primary feature. (See <a href="product_def.htm">What is a product?</a> for an explanation of products and
-primary features, and their related files.)</li>
-</ul>
-<p>
-You can think of the overall preference store as a hierarchy of nodes, where each main branch of the hierarchy
-represents a particular scope.  The children of any particular node depend upon how that scope is defined.
-For the instance and configuration scopes, the child nodes are the preferences for a particular plug-in as specified
-by a preference <b>qualifier</b>, usually the plug-in's <b>id</b>.
-</p>
-<p>
-If all of this sounds confusing, don't worry.  If you don't care about scopes and nodes,
-you need not worry about any particular scope or about which node of the tree actually contains your preference value.
-The preferences API will automatically traverse the nodes in the proper order (instance, configuration, default)
-when you query a preference value and use the supplied qualifier and preference name to find the node that actually
-contains the value.
-</p>
-<p>Preferences are accessed using <b><a href="../reference/api/org/eclipse/core/runtime/preferences/IPreferencesService.html">
-IPreferencesService</a></b> protocol.  The platform's default preference service can be accessed using the
-<b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">Platform</a></b> class.
-</p>
-<pre>
-	...
-	IPreferencesService service = <b>Platform.getPreferencesService()</b>;
-	...
-</pre>
-<p>
-Once the preference service is obtained, preference values can be queried by name using any of
-<b>get...</b> methods provided in <b><a href="../reference/api/org/eclipse/core/runtime/preferences/IPreferencesService.html">IPreferencesService</a></b>.
-For example, the following snippet queries the value of the &quot;MyPreference&quot; preference in the plug-in
-&quot;com.example.myplugin&quot;.
-</p>
-<pre>
-	...
-	IPreferencesService service = Platform.getPreferencesService();
-	boolean value = service.getBoolean(&quot;com.example.myplugin&quot;, &quot;MyPreference&quot;, true, <b>null</b>);
-	//do something with the value.
-	...
-</pre>
-<p>The last parameter in the query method is an array of scope contexts to use when searching for the
-preference node. If the 
-array is <b>null</b>, then the platform assumes that the default scope search order should be used and guesses
-the appropriate preference node.  If an array of scopes contexts is passed, then this determines
-the scope lookup order that should be used to find the preference node.  The default scope lookup order
-is always consulted if no node can be found using the specified scopes.
-</p>
-<h3>
-Using scopes and nodes
-</h3>
-<p>
-If a plug-in needs finer control over the scope search order, classes that represent the scopes can be used
-to access the actual node that represents the preference at a particular scope.  In this way, an array of 
-nodes can be created that specifies the particular search order required.  The following snippet queries the
-preferences service for the same preference used above, but searches the configuration scope for the plug-in, 
-followed by the instance scope for the plug-in. When nodes are specified for the search order, the default
-scoping is not considered.  That is, the platform will only search the exact nodes that have been provided.</p>
-<pre>
-	...
-	IPreferencesService service = Platform.getPreferencesService();
-	Preferences configurationNode = new ConfigurationScope().getNode(&quot;com.example.myplugin&quot;);
-	Preferences instanceNode = new InstanceScope().getNode(&quot;com.example.myplugin&quot;);
-	Preferences[] nodes = new Preferences[] {configurationNode, instanceNode};
-	stringValue = service.get(&quot;MyPreference&quot;, &quot;true&quot;, nodes);
-	//do something with the value.
-	...
-</pre>
-<p>
-A plug-in may also implement its own traversal through the preference tree nodes. The root node of the preference tree
-can be obtained from the preferences service.  The scope classes can be used to further traverse the tree.
-The following snippet traverses to a specific node and retrieves the preference value from the node itself.
-</p>
-<pre>
-	...
-	IPreferencesService service = Platform.getPreferencesService();
-	Preferences root = service.getRootNode();
-	Preferences myInstanceNode = root.node(InstanceScope.SCOPE).node(&quot;com.example.myplugin&quot;);
-	if (myInstanceNode != null) {
-		value = node.getBoolean(&quot;MyPreference&quot;, &quot;true&quot;);
-		//do something with the value.
-	}
-	...
-</pre>
-<h3>
-Extending the scopes
-</h3>
-<p>
-Plug-ins may define their own specialized scopes using the 
-<a href="../reference/extension-points/org_eclipse_core_runtime_preferences.html"><b>org.eclipse.core.runtime.preferences</b></a> 
-extension.  In this extension, the plug-in defines the name of the new scope, as well a class that can create
-preference nodes for the new scope.  Optionally, it can specify the name of a class that initializes the default
-preference values at that scope.  When a plug-in defines a new scope, it is up to that plug-in to implement the 
-traversal order for any new scope relative to the platform traversal order.  We'll look at this capability in more 
-detail using the specific example of <a href="resInt_preferences.htm">Project-scoped preferences</a>.
-</p>
- 
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm b/bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm
deleted file mode 100644
index b4b83ea..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/runtime_registry.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Extension points and the registry</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-Extension points and the registry</H3>
-<p>
-While the "bundle" aspects of a plug-in may be interesting to the runtime plug-in and runtime tools,
-it is much more common that a plug-in is concerned with what extension points have been defined
-by plug-ins and what extensions are contributed by plug-ins.  This information is provided 
-by the platform extension registry, <b><a href="../reference/api/org/eclipse/core/runtime/IExtensionRegistry.html">
-IExtensionRegistry</a></b>.
-</p>
-<p>Why might a plug-in want to know what extensions are present?  A concrete example will help show
-the need for this information and the protocol for getting it.</p>
-<p>Recall the workbench <b>Show View</b> dialog which shows all of the available views that have
-been installed in the platform.</p>
-<img src="images/showview.png" alt="Show View dialog with Hello entry" border="0">
-<p>
-We know that the category names and view names of all contributed views are specified in the
-<b>plugin.xml</b> file for any plug-in that contributes an extension for <b>org.eclipse.ui.views</b>.
-But how does the workbench find out this information?  From the platform extension registry.  The following 
-code is a simplified snippet based on the workbench implementation of the <b>Show View</b> dialog:
-</p>
-<pre>
-	...
-	IExtensionRegistry registry = <b>Platform.getExtensionRegistry()</b>;
-	IExtensionPoint point = <b>registry.getExtensionPoint(&quot;org.eclipse.ui.views&quot;)</b>;
-	if (point == null) return;
-	IExtension[] extensions = <b>point.getExtensions()</b>;
-	for (int i = 0; i &lt; extensions.length; i++)
-		readExtension(extensions[i]);  //get the information about each extension
-	...
-</pre>
-<p>
-We see above that the registry can be obtained from the <b><a href="../reference/api/org/eclipse/core/runtime/Platform.html">
-Platform</a></b> class.  The protocol in <b><a href="../reference/api/org/eclipse/core/runtime/IExtensionRegistry.html">
-IExtensionRegistry</a></b> is used to find the extension point named <b>org.eclipse.ui.views</b>.  Information in the registry
-about particular extension points or extensions can be found using protocol defined in
-<b><a href="../reference/api/org/eclipse/core/runtime/IExtensionRegistry.html">IExtensionRegistry</a></b>,
-<b><a href="../reference/api/org/eclipse/core/runtime/IExtensionPoint.html">IExtensionPoint</a></b>,
-and <b><a href="../reference/api/org/eclipse/core/runtime/IExtension.html">IExtension</a></b>.  
-The javadoc for these classes provides detailed information about the registry protocol.
-</p>
-<p>
-Once the extension definition of interest has been found, protocol in 
-<b><a href="../reference/api/org/eclipse/core/runtime/IConfigurationElement.html">IConfigurationElement</a></b>
-can be used to examine the individual attributes of an extension.
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/search.htm b/bundles/org.eclipse.platform.doc.isv/guide/search.htm
deleted file mode 100644
index 6ee4697..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/search.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Search support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Search support</H1>
-
-
-<p>
-If your plug-in defines and manipulates its own resource types, you may have
-special requirements for searching a resource.&nbsp; For example, the Java IDE
-plug-in implements a search engine specialized for Java files.&nbsp;&nbsp;&nbsp;</p>
-
-
-<p>
-The <b>search</b> plug-in allows you to add a specialized page describing your
-search to the workbench search dialog.&nbsp; This allows you to obtain any
-specialized information needed from the user and perform a search using your
-plug-in's internal model.</p>
-
-
-<p>
-You should also provide a specialized class for displaying the search results.
-Abstract implementations of a search result page are provided to give you a head
-start.</p>
-
-
-<p>
-These services are contributed using search plug-in extension points.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/search_page.htm b/bundles/org.eclipse.platform.doc.isv/guide/search_page.htm
deleted file mode 100644
index 6248b3e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/search_page.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing a search page</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Contributing a search page</H2>
-
-
-<p>When the user selects a resource and chooses the search command, the search
-plug-in launches a dialog containing pages for different kinds of content
-searches.&nbsp; These pages are contributed using the <a href="../reference/extension-points/org_eclipse_search_searchPages.html"><b>org.eclipse.search.searchPages</b></a>
-extension point.</p><p>The markup for contributing a search page is
-straightforward.&nbsp; The following example is the JDT plug-in's contribution
-of the Java search page:</p>
-<pre>&lt;extension point=&quot;org.eclipse.search.searchPages&quot;&gt;
-   &lt;page id=&quot;org.eclipse.jdt.ui.JavaSearchPage&quot;
-		icon=&quot;icons/full/obj16/jsearch_obj.png&quot;
-		label=&quot;%JavaSearchPage.label&quot;
-		sizeHint=&quot;460,160&quot;
-		extensions=&quot;java:90, jav:90&quot;
-		showScopeSection=&quot;true&quot;
-		canSearchEnclosingProjects=&quot;true&quot;
-		<b>class=&quot;org.eclipse.jdt.internal.ui.search.JavaSearchPage&quot;</b>&gt;
-	&lt;/page&gt;
-&lt;/extension&gt;
-</pre>
-<p>The <b>class</b> that implements the
-search page must be specified.&nbsp; This class must implement the <a href="../reference/api/org/eclipse/search/ui/ISearchPage.html"><b>ISearchPage</b></a>
-nterface and typically extends <a href="../reference/api/org/eclipse/jface/dialogs/DialogPage.html"><b>DialogPage</b></a>.&nbsp;
-The <b>label</b> and <b>icon</b> that can be
-used to describe the search in the search dialog are also specified.&nbsp;
-Additional parameters control the size of the page and the location of the page
-within the search dialog.</p>
-<p>The <b>extensions</b> attribute specifies the
-resources on which the search page can operate.&nbsp; It is formatted as a comma
-separated list of file extensions.&nbsp; Each file extension should be followed
-by a numeric weight value, where 0 is the lowest weight, separated by a
-colon.&nbsp; The weight value is a relative value used to allow the search
-infrastructure to find the search page most appropriate for a given resource.</p>
-<p>If a search page can search all possible resources then &quot;*&quot; should be used.</p>
-<h3>Implementing
-the search page</h3>
-<p>The
-protocol for <a href="../reference/api/org/eclipse/search/ui/ISearchPage.html"><b>ISearchPage</b></a>
-is simple.&nbsp; Your search page must implement <code>performAction()</code> which
-is called when the <b>Search</b> button is pressed.&nbsp; Of course, your
-particular search implementation depends on your plug-in's function, but it is
-typical to open a results viewer in this method using
-the <a href="../reference/api/org/eclipse/search/ui/NewSearchUI.html"><b>NewSearchUI</b></a>
-method <tt>activateSearchResultView().</tt>	</p>
-<p>Your plug-in is responsible for
-showing its results in the search result view.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/search_result.htm b/bundles/org.eclipse.platform.doc.isv/guide/search_result.htm
deleted file mode 100644
index 02ba15f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/search_result.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing a search result page</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Contributing a search result page</H2>
-
-<p>You can contribute a customized search results page using
-the <a href="../reference/extension-points/org_eclipse_search_searchResultViewPages.html"><b>org.eclipse.search.searchResultViewPages</b></a>
-extension point.
-</p>
-<p>When contributing a search result view page, you specify the class of search result that the page should
-be used for, and the name of the class that implements the page.  The following example is the JDT plug-in's 
-contribution of the Java search results page:</p>
-<pre>&lt;extension
-	id="JavaSearchResultPage"
-	point="org.eclipse.search.searchResultViewPages"&gt;
-	&lt;viewPage
-		id="org.eclipse.jdt.ui.JavaSearchResultPage"
-		searchResultClass="org.eclipse.jdt.internal.ui.search.JavaSearchResult"
-		class="org.eclipse.jdt.internal.ui.search.JavaSearchResultPage"&gt;
-	&lt;/viewPage&gt;
-&lt;/extension&gt;
-</pre>
-<p>The <b>class</b> must implement the <a href="../reference/api/org/eclipse/search/ui/ISearchResultPage.html"><b>ISearchResultPage</b></a>
-interface and often extends <a href="../reference/api/org/eclipse/search/ui/text/AbstractTextSearchViewPage.html"><b>AbstractTextSearchViewPage</b></a>.
-</p> 
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage.htm b/bundles/org.eclipse.platform.doc.isv/guide/secure_storage.htm
deleted file mode 100644
index 0a12a2a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Secure storage</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Secure storage</H2>
-
-<p>You can use secure storage to persist sensitive data (such as login credentials) in an encrypted form.</p> 
-
-<p>Secure storage takes care of a chicken-and-egg problem of &quot;needing to get a password to encrypt 
-a password&quot; and organizes data in a hierarchical form. It provides a central secure repository 
-for the application.</p> 
-
-<p>Secure storage is intended to store data that is relatively small in size. There is no hard cap limit at this 
-time on the data size, but it is advisable to keep size of an entry under a kilobyte. If you do need to encrypt 
-a large size object, consider creating a random key and using it with Java PBE encryption to encrypt your data. 
-You can then store the key used to encrypt the object in secure storage. Later you can obtain the key from 
-secure storage to decrypt the data.</p>
-
-<p>The secure storage can be extended by supplying custom password provider modules and custom encryption 
-algorithms. Multiple secure storages can be created and maintained at any time using different 
-customizations.</p>
-
-<p>This collection of topics describes how your code can utilize the secure storage. It assumes familiarity 
-with the concepts described in the 
-<a href="../../org.eclipse.platform.doc.user/reference/ref-securestorage-works.htm"><b>user documentation</b></a>.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_architecture.htm b/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_architecture.htm
deleted file mode 100644
index 27e6b5c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_architecture.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Secure Storage Architecture</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Secure Storage Architecture</H2>
-
-
-<p>From a logical perspective secure storage represents a hybrid of OSGi's Preferences 
-and a keyring.</p>
-
-<p>The front end is modeled in a fashion very similar to the 
-<a href="http://www.osgi.org/javadoc/r4v42/org/osgi/service/prefs/Preferences.html" title="Preferences specification in org.osgi.service.prefs"><b>OSGi Preferences Service specification</b></a>. 
-Secure storage is represented as a tree of nodes. Nodes provide context. For instance, a bundle 
-<i>&quot;com.abc&quot;</i> could use the node <i>&quot;abc&quot;</i> under the node <i>&quot;com&quot;</i> under 
-the root node. As in Preference's, the path to such node can be described as <i>&quot;/com/abc&quot;</i>.</p>
-
-<p align=center><img alt="Logical organization of data in secure storage" src="images/equinox_secure_storage_data.png">
-</p>
-<p align=center><b>Picture 1. How the data is organized.</b></p>
-
-<p>The data is stored under the node as a key-value pair. The data can be stored in an encrypted form or as 
-a clear text. The ability to store clear-text data is provided so that logically related information (such as 
-non-encrypted user name and encrypted password) can be stored using the same mechanism.</p>
-
-<p>The code to store a password associated with &quot;com.abc&quot; could look like this:</p>
-<pre>
-	...
-	ISecurePreferences root = SecurePreferencesFactory.getDefault();
-	ISecurePreferences node = root.node(&quot;/com/abc&quot;);
-	node.put(&quot;password&quot;, &quot;12345&quot;, true /*encrypt*/);
-	...
-</pre>
-<p>and then to retrieve the data:</p>
-<pre>
-	...
-	String password = node.get(&quot;password&quot;, null /*default*/);
-	...
-</pre>
-
-<p>If secure storage was modified, it will be saved when the application is closed. Alternatively, a save can be triggered 
-programmatically by calling 
-<a href="../reference/api/org/eclipse/equinox/security/storage/ISecurePreferences.html#flush()">
-<b>ISecurePreferences#flush()</b></a>.</p>
-
-<p>On the back end, secure storage can be thought of as a keyring. Each entry is associated with a password 
-provider; only this password provider can be used in the future to decrypt the entry.</p> 
-
-<p align=center><img alt="Secure storage entries and password providers" src="images/equinox_secure_storage_prov.png">
-</p>
-<p align=center><b>Picture 2. Relationship between entries and password providers.</b></p>
-
-<p>Secure storage has provisions to obtain the master password from various sources described by 
-password providers. Even more importantly for developers, the set of password providers is open and 
-easily customizable.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_dev.htm b/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_dev.htm
deleted file mode 100644
index bd3a5c8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_dev.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Developing with Secure Storage</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Developing with Secure Storage</H2>
-
-<h4>Central Classes and Interfaces</h4>
-
-<p>The functionality of secure storage is exposed via APIs of the <b>org.eclipse.equinox.security</b> bundle. 
-
-The <b><a href="../reference/api/org/eclipse/equinox/security/storage/package-summary.html">
-org.eclipse.equinox.security.storage</a></b> package contains several classes and interfaces that are likely 
-going to serve as a starting point.</p>
-
-<p>The <a href="../reference/api/org/eclipse/equinox/security/storage/SecurePreferencesFactory.html">
-<b>SecurePreferencesFactory</b></a> can be used to obtain the root node of the secure preferences. The 
-<a href="../reference/api/org/eclipse/equinox/security/storage/SecurePreferencesFactory.html#getDefault()">
-<b>SecurePreferencesFactory#getDefault()</b></a> method will return default secure preference root node. 
-If you prefer your secure storage to be isolated from the rest of the application, you can use 
-<a href="../reference/api/org/eclipse/equinox/security/storage/SecurePreferencesFactory.html#open(java.net.URL, java.util.Map)">
-<b>SecurePreferencesFactory#open(URL location, Map options)</b></a> method to open a secure storage corresponding to 
-the location of your choice. This method also takes a map of optional hints that can be used to influence 
-the behavior of this instance of secure storage.</p>
-
-<p>The restrictions put on the node names are similar to the 
-<a href="http://www.osgi.org/javadoc/r4v42/org/osgi/service/prefs/Preferences.html" title="Preferences specification in org.osgi.service.prefs"><b>OSGi Preferences</b></a>: 
-no double forward slashes, no trailing forward slash. In addition, node names can only contain printable ASCII characters. 
-If you need to use a string that does not fit those restrictions, the 
-<a href="../reference/api/org/eclipse/equinox/security/storage/EncodingUtils.html">
-<b>EncodingUtils</b></a> class can be used to convert the string into a compliant form.</p>
-
-<p>The functionality provided by the nodes is described by the 
-<a href="../reference/api/org/eclipse/equinox/security/storage/ISecurePreferences.html">
-<b>ISecurePreferences</b></a> interface. You'll find this interface is very similar to the OSGi Preferences with 
-a few minor differences. One of the differences is that many methods use 
-<a href="../reference/api/org/eclipse/equinox/security/storage/StorageException.html">
-<b>StorageException</b></a> to provide more detailed description of exceptions.</p>
-
-<h4>Debugging</h4>
-
-<p>The contents of the default secure storage can be seen in the 
-   <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.security.ui.storage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Security &gt; Secure Storage</strong></a> 
-preferences page. To enable modifications of the contents of secure storage, enable debug options of 
-the <b>org.eclipse.equinox.security.ui</b> bundle. Enabling debug options will add context menus to the preferences 
-page tree and to the values table. The context menus allow removal and addition of nodes and values to be performed 
-directly from the preferences page.</p>
-
-<p>You'll notice that context menus are disabled for the <i>&quot;org.eclipse.equinox.secure.storage&quot;</i> 
-node. This node and its children are reserved for secure storage use and should not be modified directly.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_providers.htm b/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_providers.htm
deleted file mode 100644
index 648eb31..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/secure_storage_providers.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Creating Password Providers</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Creating Password Providers</H2>
-
-<h4>Extending Password Providers</h4>
-
-<p>When storing information (such as a CVS password) in the secure storage, the information 
-gets encrypted with a master password. The interesting question about this process is how to store 
-the master password?</p> 
-
-<p>The answer is in the password provider implementations. In a logical sense, password provider modules 
-represent a trusted 3rd party, an external black box, which we trust to store our master password. That black 
-box can be an operating system, some piece of hardware, or the user himself.</p>
-
-<p>Several password provider modules are supplied with the SDK. They provide a basic &quot;fallback&quot; support 
-and an improved support for some specific operating systems. For the most part you won't need to create 
-a password provider - unless you'd like to add (or improve) integration with an operating system or add interaction 
-with some specific hardware. In this case the set of password providers can be easily extended.</p>
-
-<h4>Declaring a Password Provider</h4>
-
-<p>The password provider modules have to be described as an extension to the extension point 
-<a href="../reference/extension-points/org_eclipse_equinox_security_secureStorage.html"><b>org.eclipse.equinox.security.secureStorage</b></a>. 
-The extension must specify an ID; the qualified ID of the extension will be used as an ID of the provider  
-module and must not be changed between releases. The optional name and description of the password provider 
-show up in the 
-   <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.security.ui.storage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Security &gt; Secure Storage</strong></a> 
-preferences page and are visible to the end user.</p>
-
-<p>Provider declaration includes the fully qualified class name that implements the provider, the numerical 
-priority value, and a set of hints.</p> 
-
-<p>The priority is used to select a password provider when new data is added to the secure storage. 
-The enabled provider with the highest priority is used by default. (Note that this can be overridden 
-programmatically using 
-<a href="../reference/api/org/eclipse/equinox/security/storage/provider/IProviderHints.html#REQUIRED_MODULE_ID">
-<b>IProviderHints#REQUIRED_MODULE_ID</b></a> or by using the runtime option 
-&quot;-eclipse.password&quot;.)</p>
-
-<p>The priority is an integer number from 0 to 10, with 10 being the highest priority. Consider adding your 
-providers in the mid-range of priorities, 2 to 7, reserving top and bottom values.</p>
-
-<p>An end user can disable a password provider via Secure Storage preferences page. Disabled providers are 
-not considered when new data is added to the secure storage, but can be called on data retrieval if 
-the data was originally encrypted with this provider.</p>
-
-<p>Provider declaration can also specify a set of hints to help optimize interaction between the secure 
-storage framework and the provider. The set of hints is open and can be extended in future. At the time 
-of this writing the only expected hint is <b>&quot;AutomaticPasswordGeneration&quot;</b>. This hint 
-informs the framework that the password provider creates a master password without user interaction.</p>
-
-<h4>Implementing a Password Provider</h4>
-
-<p>The class implementing the password provider must extend the 
-<a href="../reference/api/org/eclipse/equinox/security/storage/provider/PasswordProvider.html">
-<b>PasswordProvider</b></a> class. The central point of that class is the 
-
-<a href="../reference/api/org/eclipse/equinox/security/storage/provider/PasswordProvider.html#getPassword(org.eclipse.equinox.security.storage.provider.IPreferencesContainer, int)">
-<b>getPassword()</b></a> method that returns the master password for the provider for the current user. The method 
-receives hints when a new password is expected to be created (as opposing to retrieving previously generated 
-master password).</p>
-
-<p>If your password provider has user interaction or has alternative paths to obtain the master password, you might 
-consider overriding the 
-<a href="../reference/api/org/eclipse/equinox/security/storage/provider/PasswordProvider.html#retryOnError(java.lang.Exception, org.eclipse.equinox.security.storage.provider.IPreferencesContainer)">
-<b>PasswordProvider#retryOnError()</b></a> method to inform the secure storage that the provider might 
-be able to obtain a &quot;better&quot; password. For example, consider a password provider with the master password 
-entered by the user. If the password entered was invalid, then the 
-<a href="../reference/api/org/eclipse/equinox/security/storage/provider/PasswordProvider.html#retryOnError(java.lang.Exception, org.eclipse.equinox.security.storage.provider.IPreferencesContainer)">
-<b>PasswordProvider#retryOnError()</b></a> method will be consulted to see if the password provider can 
-obtain a correct password.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt.htm
deleted file mode 100644
index 4f94aa8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Standard Widget Toolkit</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H1>The Standard Widget Toolkit</H1>
-
-<P>The Standard Widget Toolkit (SWT) is a widget toolkit for Java developers
-that provides a portable API and tight integration with the underlying native
-OS GUI platform.</P>
-
-<P>Many low level UI programming tasks are handled in higher layers of the
-Eclipse platform.  For example, JFace viewers and actions provide
-implementations for the common interactions between applications and widgets.
-However, knowledge of SWT is important for understanding how the rest of the
-platform works.</P>
-
-
-<h2>Portability and platform integration</h2>
-
-<P>SWT defines a common portable API that is provided on all supported
-platforms, and implements the API on each platform using native widgets
-wherever possible.  This allows the toolkit to immediately reflect any
-changes in the underlying OS GUI look and feel while maintaining a consistent
-programming model on all platforms.</P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm
deleted file mode 100644
index ce15e5e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_error.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Error handling</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Error handling</H2>
-
-<P>SWT can trigger three types of exceptions:
-<strong>IllegalArgumentException</strong>,
-<strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>, and
-<strong><a href="../reference/api/org/eclipse/swt/SWTError.html">SWTError</a></strong>.
-Applications should not have to catch any other kind of exception or error
-when calling SWT.</P>
-
-<blockquote><em>Note: If any other exception besides these three is thrown
-from SWT, it should be considered a bug in the SWT implementation.</em></blockquote>
-
-<P>Where possible, exceptions are triggered consistently across platforms.
-However, some errors are specific to an SWT implementation on a particular
-platform.</P>
-
-
-<H3>IllegalArgumentException</H3>
-
-<P>The arguments passed in SWT API methods are checked for appropriate state
-and range before any other work is done. An <strong>IllegalArgumentException</strong>
-will be thrown when it is determined that an argument is invalid.</P>
-
-<P>Code that causes an <strong>IllegalArgumentException</strong> on one platform 
-will cause the same exception on a different platform.</P>
-
-
-<H3>SWTException</H3>
-
-<P><strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>
-is thrown when a recoverable error occurs internally in SWT. The error code and
-message text provide a further description of the problem.</P>
-
-<P>SWT remains in a known stable state after throwing the exception.
-For example, this exception is thrown when an SWT call is made from a non-UI
-thread.</P>
-
-
-<H3>SWTError</H3>
-
-<P><a href="../reference/api/org/eclipse/swt/SWTError.html"><strong>SWTError</strong></a>
-is thrown when an unrecoverable error occurs inside SWT.</P>
-
-<P>SWT will throw this error when an underlying platform call fails, leaving
-SWT in an unknown state, or when SWT is known to have an unrecoverable error,
-such as running out of platform graphics resources.</P>
-
-<P>Once an SWT error has occurred, there is little that an application can do
-to correct the problem. These errors should not be encountered during normal
-course of operation in an application, but high reliability applications
-should still catch and report the errors.</P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm
deleted file mode 100644
index b5d9cd1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_examples.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>SWT Examples</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>SWT Examples</H2>
-
-<P>This page lists places where you can find SWT examples and more information on SWT.</P>
-
-<H3>Examples Guide</H3>
-
-<P>Within this <strong>Platform Plug-in Developer Guide</strong> is an <em>Examples Guide</em> that describes how to install and run the Eclipse platform examples.
-SWT has contributed many of these examples, some as Eclipse plug-ins, and others as standalone SWT examples.</P>
-
-<H3>SWT Snippets</H3>
-
-<P>A great collection of SWT examples can be found on the SWT Snippets page: <a href="http://www.eclipse.org/swt/snippets/">http://www.eclipse.org/swt/snippets/</a>.
-Here, you will find hundreds of simple stand-alone SWT examples.</P>
-
-<H3>More Information</H3>
-
-<P>For further information on SWT, multi-platform screenshots, FAQ, links to books, articles, and tutorials, and more, please visit:
-<a href="http://www.eclipse.org/swt">http://www.eclipse.org/swt/</a>.</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm
deleted file mode 100644
index fd546cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_graphics.htm
+++ /dev/null

@@ -1,206 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Graphics</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Graphics</H2>
-
-<P>SWT provides a graphics engine for drawing graphics and displaying
-images in widgets. You can get pretty far without ever programming to the
-graphics interface, since widgets handle the painting of icons, text, and other
-data for you. However, if your application displays custom graphics, or if
-you are implementing a custom drawn widget, then you will need to understand
-some basic drawing objects in SWT.</P>
-
-
-<H3>Graphics context</H3>
-
-<P>The graphics context,
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>,
-is the focal point for SWT graphics support. Its API describes all of the
-drawing capabilities in SWT.</P>
-
-<P>A GC can be used for drawing on a control (the most common case), on an image,
-on a display, or to a printer. When drawing on a control, you use the GC
-supplied to you in the control's paint event. When drawing on an image,
-display, or printer, you must create a GC configured for it, and dispose of the
-GC when you are finished using it.</P>
-
-<P>Once you've got a GC, you can set its attributes, such as color, line width, and font, which control
-the appearance of the graphics drawn in the GC.</P>
-
-<P>The API Reference for
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>
-describes the complete set of graphics functions.</P>
-
-
-<H3>Fonts</H3>
-
-<P>The <strong><a href="../reference/api/org/eclipse/swt/graphics/Font.html">Font</a></strong> and
-<strong><a href="../reference/api/org/eclipse/swt/graphics/FontData.html">FontData</a></strong>
-classes are used when manipulating fonts in SWT.</P>
-
-<P>FontData describes the characteristics of a font. You can create a FontData
-by specifying a font name, style, and size.  FontData includes API for querying 
-these attributes. Since FontData does not allocate any OS resources, you do not
-need to dispose of it.</P>
-
-<P>The Font is the actual graphic object representing a font that is used in the
-drawing API. You create a Font for a 
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-by specifying the Display and the FontData of the font that you want. You can 
-also query a Font for its FontData.</P>
-
-<P>You must dispose of an allocated Font when you are finished using it.</P>
-
-
-<H3>Colors</H3>
-
-<P>Colors are similar to fonts. You create a
-<strong><a href="../reference/api/org/eclipse/swt/graphics/Color.html">Color</a></strong>
-for a Display by specifying the RGB values for the desired color. You must dispose of an
-allocated color when you are finished using it.</P>
-
-<P>The Display method <code>getSystemColor(int)</code> allows you to query the predefined
-system colors for the OS platform. You should not free colors obtained using
-this technique.</P>
-
-
-<P >The color model is discussed in detail in the article 
-<a href="http://www.eclipse.org/articles/Article-SWT-Color-Model/swt-color-model.htm">SWT color model</a>.</P>
-
-
-<H3>Images</H3>
-
-<P>The <strong><a href="../reference/api/org/eclipse/swt/graphics/Image.html">Image</a></strong>,
-<strong><a href="../reference/api/org/eclipse/swt/graphics/ImageData.html">ImageData</a></strong>, and
-<strong><a href="../reference/api/org/eclipse/swt/graphics/ImageLoader.html">ImageLoader</a></strong>
-classes are used when manipulating Images in SWT.</P>
-
-<P>ImageData describes the actual pixels in the image, using the
-<a href="../reference/api/org/eclipse/swt/graphics/PaletteData.html"><strong>PaletteData</strong></a>
-class to describe the utilized color values.  ImageData is a device- and 
-platform-independent description of an image.</P>
-
-<P>ImageLoader loads and saves ImageData in different file formats. SWT 
-currently supports loading and saving of image formats including <em>BMP</em> 
-(Windows Bitmap), <em>ICO</em> (Windows Icon), <em>JPEG</em>, <em>GIF</em>, and 
-<em>PNG</em>.</P>
-
-<P>The Image is the actual graphic object representing the image that is used 
-in the drawing API.  You create an image for a particular Display.  Images can 
-be created in several ways:</P>
-
-<ul>
-  <li>use an ImageData to initialize the image's contents</li>
-  <li>copy an existing Image</li>
-  <li>load an Image from a file</li>
-</ul>
-
-<p>Regardless of how you create the Image, you are responsible for disposing
-it.</p>
-
-
-<H3>Graphics object lifecycle</H3>
-
-<P>Most of the graphics objects used for drawing in SWT allocate resources in
-the underlying OS and must be explicitly freed. The same rule discussed earlier
-applies here. If you create it using a constructor, you should free it. If you
-get access to it from somewhere else, do not free it.</P>
-
-
-<H4>Creation</H4>
-
-<P>Graphics objects such as graphics contexts, fonts, colors, and images are
-allocated in the OS as soon as the object is created. How you plan to use your
-graphics objects determines when you should create them.</P>
-
-<P>For graphics objects that are used heavily throughout the application, you
-can create them at the time that you create your widgets. This is commonly
-done for colors and fonts. In other cases, it is more appropriate to create
-your graphics objects on the fly. For example, you might create a graphics
-context in one of your widget event handlers in order to perform some
-calculations.</P>
-
-<P>If you are implementing a custom widget, you typically allocate graphics
-objects in the constructor if you always make use of them. You might allocate
-them on the fly if you do not always use them or if they are dependent upon
-the state of some attribute.</P>
-
-
-<H4>Painting</H4>
-
-<P>Once you have allocated your graphics objects, you are ready to paint.
-<em>You should always do your painting inside of a paint listener.</em>  There
-are rare cases, particularly when implementing custom widgets, when you paint
-while responding to some other event. However this is generally discouraged.
-If you think you need to paint while handling some other event, you should
-first try to use the <strong> redraw()</strong> method, which will generate
-another paint event in the OS.  Drawing outside of the paint method defeats
-platform optimizations and can cause bugs depending upon the number of pending
-paints in the event queue.</P>
-
-<P>When you receive a paint event, you will be supplied with a
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>
-pre-configured for drawing in the widget. <em>Do not free this</em>
-<strong><a href="../reference/api/org/eclipse/swt/graphics/GC.html">GC</a></strong>!
-You did not create it.</P>
-
-<P>Any other graphics objects must be allocated while handling the event (or
-beforehand). Below is a snippet based on the
-<strong>org.eclipse.swt.examples.HelloWorld5</strong> sample. The color red was
-previously allocated when creating the widget, so it can be used here.</P>
-
-<pre>
-   shell.addPaintListener (new PaintListener () {
-      public void paintControl (PaintEvent event) {
-         GC gc = event.gc;
-         gc.setForeground (red);
-         Rectangle rect = event.widget.getClientArea ();
-         gc.drawRectangle (rect.x + 10, rect.y + 10, rect.width - 20, rect.height - 20);
-         gc.drawString (resHello.getString(&quot;Hello_world&quot;), rect.x + 20, rect.y + 20);
-      }
-   });
-</pre>
-
-
-<H4>Disposal</H4>
-
-<P>Every graphics object that you allocate must be freed when you are finished
-using it.</P>
-
-<P>The timing of the disposal depends upon when you created the object. If you
-create a graphics object while creating your widget, you should generally add
-a dispose listener onto the widget and dispose of the graphics when the widget
-is disposed. If you create an object on the fly while painting, you should
-dispose of it when finished painting.</P>
-
-<P>The next code snippet shows a slightly modified version of our paint listener.
-In this example, it allocates and frees the color red while painting.</P>
-
-<pre>
-   shell.addPaintListener (new PaintListener () {
-      public void paintControl (PaintEvent event) {
-         GC gc = event.gc;
-         Color red = new Color (event.widget.getDisplay (), 0xFF, 0, 0);
-         gc.setForeground (red);
-         Rectangle rect = event.widget.getClientArea ();
-         gc.drawRectangle (rect.x + 10, rect.y + 10, rect.width - 20, rect.height - 20);
-         gc.drawString (resHello.getString (&quot;Hello_world&quot;), rect.x + 20, rect.y + 20);
-         red.dispose ();
-      }
-   });
-</pre>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm
deleted file mode 100644
index 8834d38..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Layouts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Layouts</H2>
-
-<P>Often the best way to handle simple widget positioning is in a resize event
-listener.  However, there are common patterns used by applications when placing
-widgets.  These patterns can be structured as configurable layout algorithms
-that can be reused by many different applications.</P>
-
-<P>SWT defines <em>layouts</em> that provide general purpose positioning and
-sizing of child widgets in a composite.  Layouts are subclasses of the abstract
-class <strong><a href="../reference/api/org/eclipse/swt/widgets/Layout.html">Layout</a></strong>.
-The SWT standard layouts can be found in the
-<strong><a href="../reference/api/org/eclipse/swt/layout/package-summary.html">org.eclipse.swt.layout</a></strong>
-package.</P>
-
-<P>There are some general definitions used when resizing and positioning
-widgets:</P>
-
-<ul>
-  <li>The <em>location</em> of a widget is its x,y coordinate location within
-    its parent widget.</li>
-  <li>The <em>preferred size</em> of a widget is the minimum size needed to
-    show its content. This is computed differently for each kind of widget.</li>
-  <li>The <em>clientArea</em> is the area in which a child can be placed without
-    being clipped.</li>
-  <li>The <em>trim</em> is the distance between a widget's client area and its
-    actual border.  Trim is occupied by the widget's borders or extra space
-    at its edge.  The size and appearance of the trim is widget and platform
-    dependent.</li>
-</ul>
-
-<P>These concepts are relevant for applications regardless of whether a layout
-is used. You can think of a layout as a convenient way to package resize
-functionality for reuse.</P>
-
-<P>Some additional concepts are introduced by layouts:</P>
-
-<ul>
-  <li>Some layouts support <em>spacing</em> between widgets in the layout.</li>
-  <li>Some layouts support a <em>margin</em> between the edge of the layout and
-    the widget adjacent to the edge.</li>
-</ul>
-
-<P>See <a href="http://www.eclipse.org/articles/Understanding%20Layouts/Understanding%20Layouts.htm">Understanding
-layouts in SWT</a> for further discussion and pictures demonstrating these concepts.</P>
-
-<P>The following code snippet shows the simple case of an application using a
-resize callback to size a label to the size of its parent shell:</P>
-
-<pre>
-   Display display = new Display ();
-   Shell shell = new Shell (display);
-   Label label = new Label (shell, SWT.CENTER);
-   shell.addControlListener (new ControlAdapter () {
-      public void controlResized (ControlEvent e) {
-         label.setBounds (shell.getClientArea ());
-      }
-   });
-</pre>
-
-<P>The next snippet uses a layout to achieve the same effect:</P>
-
-<pre>
-   Display display = new Display ();
-   Shell shell = new Shell (display);
-   Label label = new Label (shell, SWT.CENTER);
-   shell.setLayout (new FillLayout ());
-</pre>
-
-<P>Even for this simple example, using a layout reduces the application code.
-For more complex layouts, the simplification is much greater.</P>
-
-<p>The following table summarizes the standard layouts provided by SWT.</p>
-
-<table border="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<tr>
-<th><div CLASS="CellHeading">Layout</div></th>
-<th><div CLASS="CellHeading">Purpose</div></th>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/FillLayout.html">FillLayout</a></strong></td>
-<td>Lays out controls in a single row or column, forcing them to be the same
-size.</td>
-</tr>
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/FormLayout.html">FormLayout</a></strong></td>
-<td>Positions the children by using FormAttachments to optionally configure the
-left, top, right and bottom edges of each child.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/GridLayout.html">GridLayout</a></strong></td>
-<td>Positions the children by rows and columns.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/layout/RowLayout.html">RowLayout</a></strong></td>
-<td>Places the children either in horizontal rows or vertical columns.</td>
-
-</tr>
-</table>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm
deleted file mode 100644
index a795ee5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_layouts_custom.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Custom Layouts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>Custom layouts</H3>
-
-<P>Occasionally you may need to write your own custom
-<a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><strong>Layout</strong></a>
-class. This is most appropriate when you have a complex layout that is used
-in many different places in your application.   Note that unless you are
-writing a very generic layout that will be used by several
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Composite.html">Composite</a></strong>
-widgets, it is sometimes simpler and easier to calculate sizes and position
-children in a resize listener.</P>
-
-<P>Layouts are responsible for implementing two methods:</P>
-
-<ul>
-  <li><strong>computeSize(...)</strong> calculates the width and height of a
-      rectangle that encloses all of the composite's children once they have
-      been sized and placed according to the layout algorithm. The hint
-      parameters allow the width and/or height to be constrained.  For example,
-      a layout may choose to grow in one dimension if constrained in another.</li>
-  <li><strong>layout(...)</strong> positions and sizes the composite's children.
-      A layout can choose to cache layout-related information, such as the
-      preferred extent of each of the children. The <strong>flushCache</strong>
-      parameter tells the <a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><strong>Layout</strong></a>
-      to flush cached data, which is necessary when other factors besides the
-      size of the composite have changed, such as the creation or removal of
-      children, or a change in the widget's font.</li>
-</ul>
-
-<p>A third method, <strong>flushCache(...)</strong>, can be optionally
-implemented to clear any cached data associated with a specific control.
-Often, the computeSize() method of a widget can be expensive, and so layouts
-can cache results to improve performance.</p>
-
-<p>Further discussion of custom layouts can be found in
-<a href="http://www.eclipse.org/articles/Understanding%20Layouts/Understanding%20Layouts.htm">Understanding
-layouts in SWT</a>.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm
deleted file mode 100644
index 2ab9313..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_threading.htm
+++ /dev/null

@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Threading issues</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Threading issues</H2>
-
-<p>When working with a widget toolkit, it is important to understand the
-underlying thread model that is used for reading and dispatching platform
-GUI events.  The implementation of the UI thread affects the rules that
-applications must follow when using Java threads in their code.</p>
-
-
-<h3>Native event dispatching</h3>
-
-<p>Underneath any GUI application, regardless of its language or UI toolkit,
-the OS platform detects GUI events and places them in application event queues.
-Although the mechanics are slightly different on different OS platforms, the
-basics are similar. As the user clicks the mouse, types characters, or surfaces
-windows, the OS generates application GUI events, such as mouse clicks,
-keystrokes, or window paint events. It determines which window and application
-should receive each event and places it in the application's event queue.</p>
-
-<p>The underlying structure for any windowed GUI application is an event loop.
-Applications initialize and then start a loop which simply reads the GUI events
-from the queue and reacts accordingly. Any work that is done while handling one
-of these events must happen quickly in order to keep the GUI system responsive
-to the user.</p>
-
-<p>Long operations triggered by UI events should be performed in a separate
-thread in order to allow the event loop thread to return quickly and fetch the
-next event from the application's queue. However, access to the widgets and
-platform API from other threads must be controlled with explicit locking and
-serialization.  An application that fails to follow the rules can cause an OS
-call to fail, or worse, lock up the entire GUI system.</p>
-
-
-<H3>SWT UI thread</H3>
-
-<P>SWT follows the threading model supported directly by the platforms.  The
-application program runs the event loop in its main thread and dispatches
-events directly from this thread.  The UI thread is the thread in which the
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-was created.  All other widgets must be created in the UI thread.</p>
-
-<P>Since all event code is triggered from the application's UI thread,
-application code that handles events can freely access the widgets and
-make graphics calls without any special techniques.  However, the application
-is responsible for forking computational threads when performing long
-operations in response to an event.</P>
-
-<blockquote><em>Note:  SWT will trigger an 
-<strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>
-for any calls made from a non-UI thread that must be made from the UI
-thread.</em></blockquote>
-
-<P>The main thread, including the event loop, for an SWT application has
-the following structure:</p>
-
-<pre>
-   public static void main (String [] args) {
-      Display display = new Display ();
-      Shell shell = new Shell (display);
-      shell.open ();
-      // start the event loop. We stop when the user has done
-      // something to dispose our window.
-      while (!shell.isDisposed ()) {
-         if (!display.readAndDispatch ())
-            display.sleep ();
-      }
-      display.dispose ();
-   }
-</pre>
-
-<P>Once the widgets are created and the shell is opened, the application
-reads and dispatches events from the OS queue until the shell window is
-disposed. If there are no events available for us in the queue, we tell the
-display to sleep to give other applications a chance to run.</P>
-
-<P>SWT provides special access methods for calling widget and graphics code
-from a background thread.</P>
-
-
-<H3><a name="syncExec">Executing code from a non-UI thread</a></H3>
-
-<P>Applications that wish to call UI code from a non-UI thread must provide a
-<strong>Runnable</strong> that calls the UI code. The methods
-<strong>syncExec(Runnable)</strong> and <strong>asyncExec(Runnable)</strong>
-in the <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-class are used to execute these runnables in the UI thread during the event
-loop.</p>
-
-<ul>
-  <li><strong>syncExec(Runnable)</strong> should be used when the application
-      code in the non-UI thread depends on the return value from the UI code
-      or otherwise needs to ensure that the runnable is run to completion
-      before returning to the thread. SWT will block the calling thread until
-      the runnable has been run from the application's UI thread. For example,
-      a background thread that is computing something based on a window's
-      current size would want to synchronously run the code to get the window's
-      size and then continue with its computations.</li>
-  <li><strong>asyncExec(Runnable)</strong> should be used when the application
-      needs to perform some UI operations, but is not dependent upon the
-      operations being completed before continuing. For example, a background
-      thread that updates a progress indicator or redraws a window could
-      request the update asynchronously and continue with its processing.  In
-      this case, there is no guaranteed relationship between the timing of the
-      background thread and the execution of the runnable.</li>
-</ul>
-
-<P>The following code snippet demonstrates the pattern for using these methods:</P>
-
-<pre>
-   // do time-intensive computations
-   ...
-   // now update the UI. We don't depend on the result,
-   // so use async.
-   display.asyncExec (new Runnable () {
-      public void run () {
-         if (!myWindow.isDisposed())
-            myWindow.redraw ();
-      }
-   });
-   // now do more computations
-   ...
-</pre>
-
-<p>It is good practice to check if your widget is disposed from within the runnable
-when using asyncExec.  Since other things can happen in the UI thread between
-the call to <code>asyncExec</code> and the execution of your runnable,
-you can never be sure what state your widgets are in by the time your runnable
-executes.</p>
-
-
-<H3><a name="workbench_threads">The workbench and threads</a></H3>
-
-<p>The threading rules are very clear when you are implementing an SWT
-application from the ground up since you control the creation of the event
-loop and the decision to fork computational threads in your application.</P>
-
-<P>Things get a bit more complicated when you are contributing plug-in code
-to the workbench.  The following rules can be considered "rules of engagement"
-when using platform UI classes, although from release to release there may be
-exceptions to these rules:</P>
-
-<ul>
-  <li>In general, any workbench UI extensions you add to the platform will be
-  executing in the workbench's UI thread, unless they are specifically related
-  to threads or background jobs (such as background job progress indication).</li>
-  <li>If you receive an event from the workbench, it is not guaranteed that it is
-  executing in the UI thread of the workbench.  Consult the javadoc for the particular
-  class that defines the listener or event.  If there is no specific documentation
-  discussing threading, and the class is clearly a UI-related class, you may expect that
-  the event arrives in the UI thread of the workbench.</li>
-  <li>Likewise, a platform UI library should not be considered thread-safe unless it is
-  specifically documented as such.  Note that most platform UI classes dispatch listeners
-  from the calling thread that triggered the event.  Workbench and JFace API calls do not 
-  check that the caller is executing in the UI thread.This means that your plug-in may
-  introduce a problem if you call a method that triggers an event from a non-UI thread.
-  SWT triggers an <strong><a href="../reference/api/org/eclipse/swt/SWTException.html">SWTException</a></strong>
-  for all API calls made from a non-UI thread. In general, avoid calling platform UI code from 
-  another thread unless the javadoc specifically allows it.</li>
-   <li>If your plug-in forks a computational thread or uses a workbench Job, it must use the
-      <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-      <strong>asyncExec(Runnable)</strong> or <strong>syncExec(Runnable)</strong>
-      methods when calling any API for the workbench, JFace, or SWT, unless the API specifically
-      allows call-in from a background thread.</li>
-  <li>If your plug-in uses the JFace
-      <a href="../reference/api/org/eclipse/jface/operation/IRunnableContext.html"><strong>IRunnableContext</strong></a>
-      interface to invoke a progress monitor and run an operation, it supplies
-      an argument to specify whether a computational thread is forked for
-      running the operation.</li>
-</ul>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm
deleted file mode 100644
index 5c06122..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets.htm
+++ /dev/null

@@ -1,180 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Widgets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H2>Widgets</H2>
-
-<P>SWT includes many rich features, but a basic knowledge of the system's core -
-<em>widgets</em>, <em>layouts</em>, and <em>events</em> - is all that is needed
-to implement useful and robust applications.</P>
-
-
-<H3>Widget application structure</H3>
-
-<P>When you are contributing UI elements using platform workbench extensions,
-the mechanics of starting up SWT are handled for you by the workbench.</P>
-
-<P>If you are writing an SWT application from scratch outside of the
-workbench, you must understand more about SWT's application structure.</P>
-
-<P>A typical stand-alone SWT application has the following structure:</P>
-
-<ul>
-  <li>Create a
-      <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-      which represents an SWT session.</li>
-  <li>Create one or more
-      <strong><a href="../reference/api/org/eclipse/swt/widgets/Shell.html"> Shell</a></strong>s
-      which serve as the main window(s) for the application.</li>
-  <li>Create any other widgets that are needed inside the shell.</li>
-  <li>Initialize the sizes and other necessary state for the widgets. Register
-      listeners for widget events that need to be handled.</li>
-  <li>Open the shell window.</li>
-  <li>Run the event dispatching loop until an exit condition occurs, which
-      is typically when the main shell window is closed by the user.</li>
-  <li>Dispose the display.</li>
-</ul>
-
-<P>The following code snippet is adapted from the
-<strong><a href="../samples/org.eclipse.swt.examples/doc-html/swt_helloworld_ex.html">org.eclipse.swt.examples.helloworld.HelloWorld2</a></strong>
-application. Since the application only displays the string &quot;Hello World,&quot;
-it does not need to register for any widget events.</P>
-
-<pre>
-   public static void main (String [] args) {
-      Display display = new Display ();
-      Shell shell = new Shell (display);
-      Label label = new Label (shell, SWT.CENTER);
-      label.setText (&quot;Hello_world&quot;);
-      label.setBounds (shell.getClientArea ());
-      shell.open ();
-      while (!shell.isDisposed ()) {
-         if (!display.readAndDispatch ()) display.sleep ();
-      }
-      display.dispose ();
-   }
-</pre>
-
-
-<H4>Display</H4>
-
-<P>The <strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>
-represents the connection between SWT and the underlying platform's GUI system.
-Displays are primarily used to manage the platform event loop and control
-communication between the UI thread and other threads. (See
-<a HREF="swt_threading.htm" CLASS="XRef">Threading issues for clients</a> for
-a complete discussion of UI threading issues.)</P>
-
-<P>For most applications you can follow the pattern that is used above.  You
-must create a display before creating any windows, and you must dispose of
-the display when your shell is closed. You don't need to think about the
-display much more unless you are designing a multi-threaded application.</P>
-
-
-<H4>Shell</H4>
-
-<P>A <strong><a href="../reference/api/org/eclipse/swt/widgets/Shell.html">Shell</a></strong>
-is a &quot;window&quot; managed by the OS platform window manager. Top level
-shells are those that are created as a child of the display. These windows are
-the windows that users move, resize, minimize, and maximize while using the
-application. Secondary shells are those that are created as a child of another
-shell. These windows are typically used as dialog windows or other transient
-windows that only exist in the context of another window.</P>
-
-
-<H4>Parents and children</H4>
-
-<P>All widgets that are not top level shells must have a parent. Top level
-shells do not have a parent, but they are created in association with a
-particular
-<strong><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display</a></strong>.
-You can access this display using <strong>getDisplay()</strong>.
-All other widgets are created as descendants (direct or indirect) of top level
-shells.</P>
-
-<P><strong><a href="../reference/api/org/eclipse/swt/widgets/Composite.html">Composite</a></strong>
-widgets are widgets that can have children.</P>
-
-<P>When you see an application window, you can think of it as a widget tree, or
-hierarchy, whose root is the shell. Depending on the complexity of the
-application, there may be a single child of the shell, several children, or
-nested layers of composites with children.</P>
-
-
-<H4>Style bits</H4>
-
-<P>Some widget properties must be set at the time a widget is created and
-cannot be subsequently changed. For example, a list may be single or
-multi-selection, and may or may not have scroll bars.</P>
-
-<P>These properties, called <em>styles</em>, are set in the constructor.  All
-widget constructors take an <strong>int</strong> argument that specifies
-the bitwise <strong>OR</strong> of all desired styles. In some cases, a
-particular style is considered a hint, which means that it may not be
-available on all platforms, but will be gracefully ignored on platforms that
-do not support it.</P>
-
-<P>The style constants are located in the
-<strong><a href="../reference/api/org/eclipse/swt/SWT.html">SWT</a></strong>
-class as public static fields. A list of applicable constants for each
-widget class is contained in the API Reference for
-<strong><a href="../reference/api/org/eclipse/swt/SWT.html">SWT</a></strong>.</P>
-
-
-<H4>Resource disposal</H4>
-
-<P>The platforms underneath SWT require explicit allocation and freeing of
-OS resources.  In keeping with the SWT design philosophy of reflecting the
-platform application structure in the widget toolkit, SWT requires that you
-explicitly free any OS resources that you have allocated.  In SWT, the
-<strong>Widget.dispose()</strong> method is used to free resources associated
-with a particular toolkit object.</P>
-
-<P>The rule of thumb is that if you create the object, you must dispose of it.
-Here are some specific ground rules that further explain this philosophy:</P>
-
-<ul>
-  <li>If you create a graphic object or widget using a constructor, you must
-      explicitely dispose of it when you are finished using it.</li>
-  <li>When a
-      <a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>,
-      is disposed, the composite and all of its child widgets are recursively disposed. In this
-      case, you do not need to dispose of the widgets themselves. However, you
-      must free any graphics resources allocated in conjunction with those widgets.</li>
-  <li>If you get a graphic object or widget without using a constructor (e.g. Control.getBackground()),
-      do not dispose of it since you did not allocate it.</li>
-  <li>If you pass a reference to your widget or graphic object to another
-      object, you must take care not to dispose of it while it is still
-      being used.  (Similar to the rule described in
-      <a HREF="jface_resources.htm#jface_resources_patterns" CLASS="XRef">Plug-in
-      patterns for using images</a>.)</li>
-  <li>If you create a graphic object for use during the lifetime of one of your
-      widgets, you must dispose of the graphic object when the widget is
-      disposed. This can be done by registering a dispose listener for your
-      widget and freeing the graphic object when the <strong>dispose</strong>
-      event is received.</li>
-</ul>
-
-<p>There is one exception to these rules.  Simple data objects, such as
-<strong><a href="../reference/api/org/eclipse/swt/graphics/Rectangle.html">Rectangle</a></strong> and
-<strong><a href="../reference/api/org/eclipse/swt/graphics/Point.html">Point</a></strong>,
-do not use operating system resources. They do not have a
-<strong>dispose()</strong> method and you do not have to free them.  If in
-doubt, check the javadoc for a particular class.</p>
-
-<p>See <a href="http://www.eclipse.org/articles/swt-design-2/swt-design-2.html">Managing
-operating resources</a> for further discussion of this topic.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm
deleted file mode 100644
index 1dc142f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_controls.htm
+++ /dev/null

@@ -1,237 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Controls</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>Controls</H3>
-
-<p>A <a href="../reference/api/org/eclipse/swt/widgets/Control.html"><strong>Control</strong></a>
-is a widget that you can create and place anywhere you want in your widget
-parent/child tree.  The <a href="../reference/api/org/eclipse/swt/package-summary.html">SWT
-API reference</a> and examples contains detailed information about the
-different kinds of controls and their usage.  The
-<strong><a href="../reference/api/org/eclipse/swt/widgets/package-summary.html">org.eclipse.swt.widgets</a></strong>
-package defines the core set of widgets in SWT.  The following table summarizes
-the concrete types of controls provided in this package.</p>
- 
-
-<table border="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<tr>
-<th><div CLASS="CellHeading">Widget</div></th>
-<th><div CLASS="CellHeading">Purpose</div></th>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/browser/Browser.html">Browser</a></strong></td>
-<td>Control containing a native HTML renderer.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Button.html">Button</a></strong></td>
-<td>Selectable control that issues notification when pressed and/or
-released.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Canvas.html">Canvas</a></strong></td>
-<td>Composite control that provides a surface for drawing arbitrary graphics.
-Often used to implement custom controls.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Caret.html">Caret</a></strong></td>
-<td>An i-beam that is typically used as the insertion point for text.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Combo.html">Combo</a></strong></td>
-<td>Selectable control that allows the user to choose a string from a list of
-strings, or optionally type a new value into an editable text field.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Composite.html">Composite</a></strong></td>
-<td>Control that is capable of containing other widgets.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/CoolBar.html">CoolBar</a></strong></td>
-<td>Composite control that allows users to dynamically reposition the cool items
-contained in the bar.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/CoolItem.html">CoolItem</a></strong></td>
-<td>Selectable user interface object that represents a dynamically positionable
-area of a cool bar.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/DateTime.html">DateTime</a></strong></td>
-<td>Selectable user interface object that allows the user to enter and modify date or time values.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ExpandBar.html">ExpandBar</a></strong></td>
-<td>Composite control that groups pages that can be shown or hidden by the user with labeled headers.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ExpandItem.html">ExpandItem</a></strong></td>
-<td>Selectable user interface object corresponding to a header for a page in an ExpandBar.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Group.html">Group</a></strong></td>
-<td>Composite control that groups other widgets and surrounds them with an
-etched border and/or label.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Label.html">Label</a></strong></td>
-<td>Non-selectable control that displays a string or an image.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Link.html">Link</a></strong></td>
-<td>Selectable control that displays a text with links.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/List.html">List</a></strong></td>
-<td>Selectable control that allows the user to choose a string or strings from a
-list of strings.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Menu.html">Menu</a></strong></td>
-<td>User interface object that contains menu items.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/MenuItem.html">MenuItem</a></strong></td>
-<td>Selectable user interface object that represents an item in a menu.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ProgressBar.html">ProgressBar</a></strong></td>
-<td>Non-selectable control that displays progress to the user, typically in the
-form of a bar graph.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Sash.html">Sash</a></strong></td>
-<td>Selectable control that allows the user to drag a rubber banded outline of
-the sash within the parent window.  Used to allow users to resize child widgets
-by repositioning their dividing line.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Scale.html">Scale</a></strong></td>
-<td>Selectable control that represents a range of numeric values.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ScrollBar.html">ScrollBar</a></strong></td>
-<td>Selectable control that represents a range of positive numeric values. Used
-in a Composite that has V_SCROLL and/or H_SCROLL styles.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Shell.html">Shell</a></strong></td>
-<td>Window that is managed by the OS window manager. Shells can be parented by
-a Display (top level shells) or by another shell (secondary shells).</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Slider.html">Slider</a></strong></td>
-<td>Selectable control that represents a range of numeric values.  A slider is
-distinguished from a scale by providing a draggable thumb that can adjust the
-current value along the range.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Spinner.html">Spinner</a></strong></td>
-<td>Selectable control that allows the user to enter and modify numeric
-values.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TabFolder.html">TabFolder</a></strong></td>
-<td>Composite control that groups pages that can be selected by the user using
-labeled tabs.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TabItem.html">TabItem</a></strong></td>
-<td>Selectable user interface object corresponding to a tab for a page in a tab
-folder.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Table.html">Table</a></strong></td>
-<td>Selectable control that displays a list of table items that can be selected
-by the user.  Items are presented in rows that display multiple columns
-representing different aspects of the items.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TableColumn.html">TableColumn</a></strong></td>
-<td>Selectable user interface object that represents a column in a table.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TableItem.html">TableItem</a></strong></td>
-<td>Selectable user interface object that represents an item in a table.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Text.html">Text</a></strong></td>
-<td>Editable control that allows the user to type text into it.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ToolBar.html">ToolBar</a></strong></td>
-<td>Composite control that supports the layout of selectable tool bar
-items.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/ToolItem.html">ToolItem</a></strong></td>
-<td>Selectable user interface object that represents an item in a tool bar.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/Tree.html">Tree</a></strong></td>
-<td>Selectable control that displays a hierarchical list of tree items that can
-be selected by the user.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TreeColumn.html">TreeColumn</a></strong></td>
-<td>Selectable user interface object that represents a column in a tree.</td>
-</tr>
-
-<tr>
-<td><strong><a href="../reference/api/org/eclipse/swt/widgets/TreeItem.html">TreeItem</a></strong></td>
-<td>Selectable user interface object that represents a hierarchy of tree items
-in a tree.</td>
-</tr>
-</table>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm
deleted file mode 100644
index 23b2af7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_custom.htm
+++ /dev/null

@@ -1,171 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Custom widgets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Custom widgets</h3>
-
-<P>You may want to extend SWT by implementing your own custom widget. SWT itself provides a package,
-<strong><a href="../reference/api/org/eclipse/swt/custom/package-summary.html">org.eclipse.swt.custom</a></strong>,
-which contains custom controls that are not in the core set of SWT controls but are
-needed to implement the platform workbench.</P>
-
-<table border="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<tr>
-<th><div CLASS="CellHeading">Control</div></th>
-<th><div CLASS="CellHeading">Purpose</div></th>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CBanner.html">CBanner</a></strong></td>
-<td>CBanner is used in the workbench to layout the toolbar area and
-perspective switching toolbar.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CCombo.html">CCombo</a></strong></td>
-<td>Similar to Combo, but is vertically resizable allowing it to fit inside table cells.</td>
-</tr>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CLabel.html">CLabel</a></strong></td>
-<td>Similar to Label, but supports shortening of text with an ellipsis. Also supports
-a gradient effect for the background color as seen in the active workbench view.
-Does not support wrapping.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CTabFolder.html">CTabFolder</a></strong></td>
-<td>Similar to TabFolder, but supports additional configuration of the visual
-appearance of tabs (top or bottom) and borders.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/CTabItem.html">CTabItem</a></strong></td>
-<td>Selectable user interface object corresponding to a tab for a page in a
-CTabFolder.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/SashForm.html">SashForm</a></strong></td>
-<td>Composite control that lays out its children in a row or column arrangement
-and uses a Sash to separate them so that the user can resize them.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/ScrolledComposite.html">ScrolledComposite</a></strong></td>
-<td>Composite control that scrolls its contents and optionally stretches its
-contents to fill the available space.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/StyledText.html">StyledText</a></strong></td>
-<td>Editable control that allows the user to type text.  Ranges of text inside
-the control can have distinct colors and font styles.</td>
-</TR>
-
-<TR>
-<td><strong><a href="../reference/api/org/eclipse/swt/custom/ViewForm.html">ViewForm</a></strong></td>
-<td>ViewForm is used in the workbench to position and size a view's label/toolbar/menu local bar.</td>
-</tr>
-</table>
-
-
-
-<h4>Implementing a custom widget</h4>
-
-<p>Once you've determined that you need a custom widget and have decided which
-platforms must be supported, you can consider several implementation techniques
-for your widget. These techniques can be mixed and matched depending on what
-is available in the underlying OS platform.</p>
-
-
-<h4>Native implementation</h4>
-
-<p>If your application requires a native widget that is not provided by SWT,
-you will need to implement it natively. This may be a platform widget, a third
-party widget, or any other widget in a platform shared library.  A complete
-example of a native custom widget implementation can be found in
-<a href="http://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm">Creating
-Your Own Widgets using SWT</a>.</p>
-
-
-<h4>Combining existing widgets</h4>
-
-<p>Widgets can be combined to form widgets that are more sophisticated.  For
-example, a Combo can be implemented using a text entry widget along with a
-button and a drop-down list.  To implement a combined widget, you create a
-subclass of
-<a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>
-and manage the children internally.</p>
-
-<p>A simple example can be found in
-<a href="../reference/api/org/eclipse/swt/custom/CCombo.html"><strong>CCombo</strong></a>.</p>
-
-<h4>Custom drawn implementation</h4>
-
-<p>In some cases, you don't have any native code or existing widgets that help
-you in the implementation of your new widget. This means you must draw the
-widget yourself in the handler for the Paint event.  Although this technique
-can become quite complicated, it has the advantage of producing a completely
-portable implementation.</p>
-
-<p>Custom drawn controls are implemented by subclassing the
-<a href="../reference/api/org/eclipse/swt/widgets/Canvas.html"><strong>Canvas</strong></a> or
-<a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>.
-Subclass <a href="../reference/api/org/eclipse/swt/widgets/Canvas.html"><strong>Canvas</strong></a>
-if your widget will not contain any child controls.</p>
-
-<P>The internal implementation of a custom drawn widget usually involves these
-major tasks:</P>
-
-<ul>
-  <li>Create any graphics objects needed in your constructor and store them in
-      an instance variable. Register a listener for the <strong>dispose</strong>
-      event on your canvas or composite so that you can free these objects
-      when the widget is destroyed.</li>
-  <li>Add a <strong>paintListener</strong> to your canvas or composite and
-      paint the widget according to your design. For complex widgets, a lot
-      of work goes into optimizing this process by calculating and repainting
-      only what's absolutely necessary.</li>
-  <li>Ensure that any API calls that affect the appearance of your widget
-      trigger a repaint of the widget. In general, you should use
-      <strong>redraw</strong> to damage your widget when you know you must
-      repaint, rather than call your internal painting code directly. This
-      gives the platform a chance to collapse the paint you want to generate
-      with any other pending paints and helps streamline your code by funneling
-      all painting through one place.</li>
-  <li>If your widget defines events in its API, determine what low level
-      <a href="../reference/api/org/eclipse/swt/widgets/Canvas.html"><strong>Canvas</strong></a> or
-      <a href="../reference/api/org/eclipse/swt/widgets/Composite.html"><strong>Composite</strong></a>
-      events will trigger your widget's events. For example, if you have a
-      clicked event, you will want to register a mouse event on your canvas and
-      perform calculations (such as hit testing) to determine whether the mouse
-      event in your canvas should trigger your widget event.</li>
-</ul>
-
-<P>Many of the widgets implemented in the
-<a href="../reference/api/org/eclipse/swt/custom/package-summary.html"><strong>org.eclipse.swt.custom</strong></a>
-use this approach. A simple example can be found in
-<a href="../reference/api/org/eclipse/swt/custom/CLabel.html"><strong>CLabel</strong></a>.</P>
-
-<P>Further information on custom widgets can be found in
-<a href="http://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm">Creating
-your own widgets using SWT.</a></P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm b/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm
deleted file mode 100644
index d71ca9c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/swt_widgets_events.htm
+++ /dev/null

@@ -1,275 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Events</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>Events</H3>
-
-<P>Once we create a display and some widgets, and start up the application's
-message loop, where does the real work happen? It happens every time an event is
-read from the queue and dispatched to a widget. Most of the application logic is
-implemented as responses to user events.</P>
-
-<P>The basic pattern is that you add a listener to some widget that you have
-created, and when the appropriate event occurs the listener code will be
-executed. This simple example is adapted from
-<strong>org.eclipse.swt.examples.helloworld.HelloWorld3</strong>:</P>
-
-<pre>
-   Display display = new Display ();
-   Shell shell = new Shell (display);
-   Label label = new Label (shell, SWT.CENTER);
-   ...
-   shell.addControlListener (new ControlAdapter () {
-      public void controlResized (ControlEvent e) {
-         label.setBounds (shell.getClientArea ());
-      }
-   });
-</pre>
-
-<P>For each type of listener, there is an interface that defines the listener
-(<em>Xyz</em><strong>Listener</strong>), a class that provides event information
-(<em>Xyz</em><strong>Event</strong>), and an API method to add the listener
-(<strong>add</strong><em>Xyz</em><strong>Listener</strong>).  If there is more
-than one method defined in the listener interface then there is an adapter
-(<em>Xyz</em><strong>Adapter</strong>) that implements the listener interface
-and provides empty methods.   All of the events, listeners,
-and adapters are defined in the package
-<strong><a href="../reference/api/org/eclipse/swt/events/package-summary.html">org.eclipse.swt.events</a></strong>.</P>
-
-<P>The following tables summarize the events that are available and the widgets
-that support each event.  Events can be split into two general categories:
-high level events which represent a logical operation on a control, and low
-level events which describe more specific user interactions.  High level events
-may be represented by multiple low level events which may differ per
-platform.  Low level events should generally only be used for custom widget
-implementations.</P>
-
-
-<h4>High level events</h4>
-
-<TABLE BORDER="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<TR>
-<TH><P CLASS="CellHeading">Event Type</P></TH>
-<TH><P CLASS="CellHeading">Description</P></TH>
-</TR>
-
-<tr>
-<td><strong>Activate</strong>, <strong>Deactivate</strong></td>
-<td>Generated when a Control is activated or deactivated.</td>
-</tr>
-
-<TR>
-<td><strong>Arm</strong></td>
-<td>A MenuItem is armed (highlighted and ready to be selected).</td>
-</TR>
-
-<TR>
-<td><strong>Close</strong></td>
-<td>A Shell is about to close as requested by the window manager.</td>
-</TR>
-
-<TR>
-<td><strong>DefaultSelection</strong></td>
-<td>The user selects an item by invoking a default selection action.  For
-example, by hitting Enter or double clicking on a row in a Table.</td>
-</tr>
-
-<TR>
-<td><strong>Dispose</strong></td>
-<td>A widget is about to be disposed, either programmatically or by user.</td>
-</TR>
-
-<tr>
-<td><strong>DragDetect</strong></td>
-<td>The user has initiated a possible drag operation.</td>
-</tr>
-
-<tr>
-<td><strong>EraseItem</strong></td>
-<td>A TableItem or TreeItem is about to have its background drawn.</td>
-</tr>
-
-<TR>
-<td><strong>Expand</strong>, <strong>Collapse</strong></td>
-<td>An item in a Tree is expanded or collapsed.</td>
-</TR>
-
-<TR>
-<td><strong>Help</strong></td>
-<td>The user has requested help for a widget.  For example, this occurs when
-the F1 key is pressed under Windows.</td>
-</TR>
-
-<TR>
-<td><strong>Iconify</strong>, <strong>Deiconify</strong></td>
-<td>A Shell has been minimized, maximized, or restored.</td>
-</TR>
-
-<TR>
-<td><strong>ImeComposition</strong></td>
-<td>Allows custom text editors to implement in-line editing of international text.</td>
-</TR>
-
-<tr>
-<td><strong>MeasureItem</strong></td>
-<td>The size of a custom drawn TableItem or TreeItem is being requested.</td>
-</tr>
-
-<tr>
-<td><strong>MenuDetect</strong></td>
-<td>The user has requested a context menu.</td>
-</tr>
-
-<TR>
-<td><strong>Modify</strong></td>
-<td>The widget's text has been modified.</td>
-</TR>
-
-<TR>
-<td><strong>Move</strong>, <strong>Resize</strong></td>
-<td>A control has changed position or has been resized, either programmatically
-or by user.</td>
-</TR>
-
-<TR>
-<td><strong>Movement</strong></td>
-<td>An updated caret offset is needed in response to a user action in a StyledText.</td>
-</TR>
-
-<tr>
-<td><strong>PaintItem</strong></td>
-<td>A TableItem or TreeItem is about to have its foreground drawn.</td>
-</tr>
-
-<tr>
-<td><strong>Selection</strong></td>
-<td>The user selects an item in the control.  For example, by single clicking
-on a row in a Table or by keyboard navigating through the items.</td>
-</tr>
-
-<tr>
-<td><strong>SetData</strong></td>
-<td>Data needs to be set on a TableItem when using a virtual table.</td>
-</tr>
-
-<tr>
-<td><strong>Settings</strong></td>
-<td>An operating system property, such as a system font or color, has been changed.</td>
-</tr>
-
-<tr>
-<td><strong>Show</strong>, <strong>Hide</strong></td>
-<td>A control's visibility has changed.</td>
-</tr>
-
-<TR>
-<td><strong>Traverse</strong></td>
-<td>The user is trying to traverse out of the control using a keystroke.  For
-example, the escape or tab keys are used for traversal.</td>
-</TR>
-
-<TR>
-<td><strong>Verify</strong></td>
-<td>A widget's text is about to be modified.  This event gives the application
-a chance to alter the text or prevent the modification.</td>
-</TR>
-</TABLE>
-
-
-<h4>Low level events</h4>
-
-<TABLE BORDER="1" width="600">
-<colgroup>
-    <col width="34%">
-    <col width="66%">
-</colgroup>
-<TR>
-<TH><P CLASS="CellHeading">Event Type</P></TH>
-<TH><P CLASS="CellHeading">Description</P></TH>
-</TR>
-
-<TR>
-<td><strong>FocusIn</strong>, <strong>FocusOut</strong></td>
-<td>A control has gained or lost focus.</td>
-</TR>
-
-<TR>
-<td><strong>KeyDown</strong>, <strong>KeyUp</strong></td>
-<td>The user has pressed or released a keyboard key when the control has
-keyboard focus.</td>
-</TR>
-
-<TR>
-<td><strong>MouseDown</strong>, <strong>MouseUp</strong>,
-<strong>MouseDoubleClick</strong></td>
-<td>The user has pressed, released, or double clicked the mouse over the
-control.</td>
-</TR>
-
-<TR>
-<td><strong>MouseMove</strong></td>
-<td>The user has moved the mouse above the control.</td>
-</TR>
-
-<TR>
-<td><strong>MouseEnter</strong>, <strong>MouseExit</strong>,
-<strong>MouseHover</strong></td>
-<td>The mouse has entered, exited, or hovered over the control.</td>
-</TR>
-
-<TR>
-<td><strong>MouseWheel</strong></td>
-<td>The mouse wheel has been rotated.</td>
-</TR>
-
-<TR>
-<td><strong>Paint</strong></td>
-<td>The control has been damaged and requires repainting.</td>
-</TR>
-</table>
-
-
-<H4>Untyped events</H4>
-<P>In addition to the typed event system described above, SWT supports a low level,
-untyped widget event mechanism.  The untyped mechanism relies on a constant to 
-identify the event type and defines a generic listener that is supplied with 
-this constant. This allows the listener to implement a &quot;case style&quot; listener.
-In the following snippet, we define a generic event handler and add several listeners to a shell.</P>
-
-<pre>
-   Shell shell = new Shell ();
-   Listener listener = new Listener () {
-      public void handleEvent (Event e) {
-         switch (e.type) {
-            case SWT.Resize:
-               System.out.println (&quot;Resize received&quot;);
-               break;
-            case SWT.Paint:
-               System.out.println (&quot;Paint received&quot;);
-               break;
-            default:
-               System.out.println (&quot;Unknown event received&quot;);
-         }
-      }
-   };
-   shell.addListener (SWT.Resize, listener);
-   shell.addListener (SWT.Paint, listener);
-</pre>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team.htm b/bundles/org.eclipse.platform.doc.isv/guide/team.htm
deleted file mode 100644
index 84ae798..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-<title>Team support</title>
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Team support</h1>
-<p>The Eclipse Team support defines API that allow plug-ins to
-integrate the function of a versioning and configuration management
-repository. The function provided by a repository fundamentally affects
-the user workflow, since there are additional steps for retrieving
-files, comparing their content with local content, versioning them, and
-returning updated files to the repository. The goal of the team plug-in
-API is to be passive enough to allow repository plug-in providers to
-define their own workflow so that users familiar with their product can
-use the platform in a similar fashion and provide support for workflows
-that we have found are useful for team plug-ins. </p>
-<p>
-This goal is accomplished by supplying several building blocks:
-</p>
-<ul>
-  <li><a href="team_provider_repository.htm">Repository Providers</a>
-    <blockquote> A repository provider allows synchronization of
-workspace resources with a remote location. At a minimum it allows
-pushing resources in the workspace to a remote location and pulling
-resources from a remote location into the workspace. A repository
-provider is associated with a project and controls the resources in the
-project by optionally providing a <a
- href="../reference/api/org/eclipse/core/resources/team/FileModificationValidator.html">FileModificationValidator
-      </a>and <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html">IMoveDeleteHook</a>.
-There is only one repository provider associated with each project. A
-user associates a repository provider with a project by providing a <a
- href="../reference/api/org/eclipse/team/ui/IConfigurationWizard.html">IConfigurationWizard</a>.
-Repository providers can also participate in exporting and importing of
-projects into the workspace via the team project set feature. To
-support this a repository provider should implement a <a
- href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a>.<br>
-    </blockquote>
-  </li>
-  <li><a href="team_resources.htm">Resource Management</a>
-    <blockquote> Allows other plug-ins to indicate special handling of resources 
-      with respect to team operations. The repository provider can mark resources 
-      as team-private which essentially hides the resource from other plug-ins. 
-      This is done via the <a href="../reference/api/org/eclipse/core/resources/IResource.html#setTeamPrivateMember(boolean)">IResource#setTeamPrivateMember</a> 
-      method and is commonly done to hide repository provider specific meta-files 
-      from the user. Also, builders will often mark build output as derived which 
-      is a hint to a repository provider that the resource is transient and could 
-      be ignored by the repository provider. A provider can check this flag on 
-      a resource via the <a href="../reference/api/org/eclipse/core/resources/IResource.html#isDerived()">IResource#isDerived</a> 
-      method.<br>
-      <br>
-      In addition, other plug-ins can add provide hints to the repository provider 
-      about file type information via the <a
- href="../reference/extension-points/org_eclipse_team_core_fileTypes.html">org.eclipse.team.core.fileTypes</a> 
-      extension and about common files that should be ignored by the repository 
-      via the <a
- href="../reference/extension-points/org_eclipse_team_core_ignore.html">org.eclipse.team.core.ignore</a> 
-      extension.<br>
-    </blockquote>
-  </li>
-</ul>
-<ul>
-  <li><a href="team_synchronize.htm">Synchronization Support</a> [<b>new
-in 3.0</b>]
-    <blockquote> Synchronize support provides classes and interfaces
-for managing dynamic collections of synchronization information (<a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo</a>,
-      <a href="../reference/api/org/eclipse/team/core/synchronize/SyncInfoSet.html">SyncInfoSet</a>).
-This support helps you manage information about variants of the
-resources in the workspace. For example, with FTP you could store
-timestamps for the latest remote file and the base for the currently
-loaded resource. Synchronization support provides APIs to help manage
-and persist resource variants and display synchronization state to the
-user.<br>
-    </blockquote>
-  </li>
-    <li><a href="team_model.htm">Support for Logical Model Integration</a> [<b>new
-in 3.2</b>]
-    <blockquote> The logical model integration support defines API that allows 
-      logical models to participate in team operations. In model based views, 
-      model providers can use this support in order to have team decorations and 
-      operations appear on their model elements. In resource based views (e.g. 
-      Resource Navigator), model providers can use this support to validate that 
-      operations performed on resources will not corrupt the model and to ensure 
-      that all the resources that constitute a model element are included in team 
-      operations. For team merge operations, the API allows model providers to 
-      use model semantics during merge operations and to participate in the preview 
-      of merge operation. The description of the support for logical model integration 
-      is divided into a <a href="team_model_repo.htm">Repository Roadmap for Logical 
-      Model Integration</a> and a <a href="team_model_model.htm">Model Roadmap 
-      for Logical Model Integration</a>.<br>
-    </blockquote>
-  </li>
-</ul>
-
-<p>The UI support is also structured passively.&nbsp;Placeholders for
-team provider actions, preferences, and properties are defined by the team
-UI plug-in, but it's up to the team plug-in provider to define these UI
-elements.&nbsp;The team UI plug-in also includes a simple, extendable
-configuration wizard that lets users associate projects with
-repositories.&nbsp;Plug-ins can supply content for this wizard that let
-the user specify repository specific information.
-</p>
-<p>Multiple repository providers can coexist peacefully within the
-platform.&nbsp;In fact, it's even possible to have different client
-implementations for the same repository installed. For example, one
-could install a CVS client designed for experts and a different one for
-novice users.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm
deleted file mode 100644
index 0228a0d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_howto.htm
+++ /dev/null

@@ -1,271 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Rich Team Integration</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body bgcolor="#ffffff">
-<h2>Rich Team Integration</h2>
-<p>
-Integrating your repository's support with the platform starts with
-good solid design.&nbsp;The goal is to integrate the workflow that your
-repository users know with the concepts defined in the workbench.&nbsp;Because 
-there are many ways to extend workbench UI and functionality, you have a lot of
-flexibility in how you achieve integration.&nbsp;So where to start?
-</p>
-<p>Building a team provider is not just a matter of learning Team
-API.&nbsp;(Subsequent sections will focus on the specific support
-introduced by the team plug-in.)&nbsp;It's a matter of understanding <a
- href="workbench.htm">workbench integration</a>.&nbsp;So let's start
-with the big picture.&nbsp;We'll be using the CVS client as a case
-study for integrating a team provider with the platform. Let's look at
-some of the function the CVS provider supplies and what workbench and
-team facilities you can use to achieve similar levels of integration.</p>
-<p>
-<img
- alt="Workbench with CVS menu items, views, tasks, and decorators"
- src="images/teamintegration.png"></p>
-<p>The CVS client integrates seamlessly with the existing workbench
-resource perspective.&nbsp;It allows users to configure a project for
-CVS, adds functionality to a resource's menu, decorates resources with
-team-specific information, provides customized views that show
-team-specific information, adds team-oriented tasks to the task
-list...&nbsp;The list goes on and on.&nbsp;How can your provider
-achieve similar integration?&nbsp;Here are some basic steps to start
-with and links for information (both team-specific and
-workbench-oriented) on these topics.</p>
-<h3>Getting started</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Define a
-       <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>
-      </b> that represents your implementation.</td>
-      <td width="68%">
-      <ul>
-          <li><a href="team_provider_repository.htm#repository_pt">Define your 
-            provider using <b>org.eclipse.team.core.repository</b></a>.</li>
-          <li>Subclass <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a> 
-            </b> and <a href="team_provider_repository.htm#repo_impl">implement 
-            the necessary methods</a>.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Provide a configuration wizard so that users can
-associate your provider with their projects.</td>
-      <td width="68%">
-      <ul>
-          <li><a href="team_provider_repository.htm#ui_conf">Contribute a wizard 
-            using <b>org.eclipse.team.ui.configurationWizards</b></a>.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Add your actions to the Team menu.</td>
-      <td width="68%">
-      <ul>
-        <li><a href="team_ui_actions.htm">Add your actions to the Team
-menu</a>.</li>
-        <li>Use the <a href="workbench_basicext_popupMenus.htm"><b>popupMenus</b></a>
-extension to define the menu items.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Enhancing resource views</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Add provider-specific properties to the
-properties page for a resource.</td>
-      <td width="68%">
-      <ul>
-          <li> <a href="preferences_prop_implement.htm">Implement</a> and <a href="preferences_prop_contribute.htm">contribute</a> 
-            property pages to show team-specific properties for your resource.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Implement specialized decorators to show
-team-related attributes</td>
-      <td width="68%">
-      <ul>
-        <li><a href="team_ui_decorators.htm">Contribute decorators</a>
-to resource views.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Reduce clutter by filtering out any resources
-that are used in implementing team support.&nbsp;</td>
-      <td width="68%">
-      <ul>
-        <li>Use <a href="team_resources_private.htm">team-private
-resources</a> to hide implementation files and folders.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Handling user editing and changes to resources</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Intervene in the saving of resources so you can
-check permissions before a user changes a file.</td>
-      <td width="68%">
-      <ul>
-        <li>Implement the <a href="team_provider_repository.htm#hooks">fileModificationValidator</a>
-hook.</li>
-        <li>Use <a
- href="../reference/api/org/eclipse/core/resources/team/FileModificationValidator.html#validateSave(org.eclipse.core.resources.IFile)"><b>validateSave</b></a>
-to prevent or intervene in saving of files.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Intervene before a user edits a file to see if
-it's allowed.</td>
-      <td width="68%">
-      <ul>
-        <li>Implement the <a href="team_provider_repository.htm#hooks">fileModificationValidator</a>
-hook.</li>
-        <li>Use <a
- href="../reference/api/org/eclipse/core/resources/team/FileModificationValidator.html#validateEdit(org.eclipse.core.resources.IFile[], org.eclipse.core.resources.team.FileModificationValidationContext)"><b>validateEdit</b></a>
-to prevent or intervene in editing of files.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Track changes to resources in the workspace so
-you can allow associated changes in the repository.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="team_provider_repository.htm#hooks">move/delete
-hooks</a> to prevent or enhance moving and deleting of resources.</li>
-        <li>See <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>
-          <b> </b>for more detail about what you can do.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td>Ensure that the proper resource locks are obtained for
-resource operations that invoke the move/delete hook or
-fileModificatonValidator.</td>
-      <td>
-      <ul>
-        <li>Use the <a href="team_provider_repository.htm#hooks">resource
-rule factory </a> to ensure that the proper rules are obtained for
-resource operations.</li>
-        <li>See <a
- href="../reference/api/org/eclipse/core/resources/team/ResourceRuleFactory.html"><b>ResourceRuleFactory</b></a>
-          <b> </b>for more details.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Enable the use of linked resources.</td>
-      <td width="68%">
-      <ul>
-        <li>See <a href="team_resources_linked.htm"><b>Team and linked
-resources</b></a>.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3>Streamlining repository-related tasks</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Provide an easy way to export a description of
-your projects.</td>
-      <td width="68%">
-      <ul>
-        <li>Use <a href="team_resources_projects.htm">project sets</a>
-to export your projects without exporting the content so that users can
-rebuild projects from the repository.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Reduce clutter in the repository by ignoring
-files that can be regenerated.</td>
-      <td width="68%">
-      <ul>
-        <li>Honor the <a href="team_resources_filetypes.htm"><b>ignore</b></a>
-extension when handling files and use ignore for your plug-in's derived
-files.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<h3> Enhancing platform integration</h3>
-<table width="73%" cellspacing="0" cellpadding="0" border="1">
-  <tbody>
-    <tr>
-      <td width="32%">Add provider-specific preferences to the
-preferences page.</td>
-      <td width="68%">
-      <ul>
-        <li><a href="team_ui_prefs.htm">Add your preferences to the
-Team category</a>.</li>
-        <li><a href="preferences_prefs_implement.htm">Build your
-preference page</a> using workbench support.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Implement custom views to show detailed
-information about repositories or their resources.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="workbench_basicext_views.htm"><b>views</b></a>
-extension to contribute a view.</li>
-        <li>See the CVS provider's repository view for an example.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Add your views or actions to existing workbench
-perspectives if appropriate.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="workbench_advext_perspectiveExtension.htm"><b>perspectiveExtensions</b></a>
-extension to add your plug-in's shortcuts or views to existing
-perspectives.</li>
-      </ul>
-      </td>
-    </tr>
-    <tr>
-      <td width="32%">Implement a repository-specific perspective to
-streamline repository administration or browsing.</td>
-      <td width="68%">
-      <ul>
-        <li>Use the <a href="workbench_advext_perspectives.htm"><b>perspectives</b></a>
-extension to define your own perspective, views, short cuts, and page
-layout.</li>
-      </ul>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<p>&nbsp;</p>
-<p>&nbsp; </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_model.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_model.htm
deleted file mode 100644
index bf41f7f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_model.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-<title>Team Support for Logical Model Integration</title>
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Team Support for Logical Model Integration</h1>
-<p>There are two viewpoints of interest when describing the Team support for logical 
-  model integration:</p>
-<ul>
-  <li><em>Repository Provider</em>: A Repository Provider is the connection between 
-    the local workspace and a remote repository. Details of the logical model 
-    support from the standpoint of a Repository Provider can be found in the <a href="team_model_repo.htm">Repository 
-    Roadmap for Logical Model Integration</a>.<br>
-  </li>
-  <li><em>Model Provider</em>: A Model Provider is the tooling that allows the 
-    user to work with the model elements that are stored in the resources in the 
-    local workspace. Details of how Model Providers can leverage this support 
-    is found in <a href="team_model_model.htm">Model Roadmap for Logical Model 
-    Integration</a>.</li>
-</ul>
-<p>The following points summarize the features covered by the Team logical model 
-  support.</p>
-<ul>
-  <li>Maintaining Workspace Consistency: Operations performed directly on resources 
-    may have undesirable side effects on model elements that are persisted in, 
-    or are otherwise associated with, those resources. Clients can use the ResourceChangeValidator 
-    to validate that changes to resources will not have undesirable side effects 
-    on models while models can implement the ModelProvider#validateChange method 
-    to validate a resource change.<br>
-  </li>
-  <li>Team Operations and Decorations: It has always been possible to have team 
-    operations and decorations appear on model elements that have a one-to-one 
-    relationship by adapting the model element to the corresponding IResource. 
-    It is now possible to have operation and decorations appear on model elements 
-    that have more complex relationships to resources by adapting a model element 
-    to a ResourceMapping.<br>
-  </li>
-  <li>Semantic Merges of Model Elements: Model Providers can participate in headless 
-    merges by associating an IStorageMerger with a particular file type, if there 
-    is a one-to-one correspondence between model elements and resources. For more 
-    complex relationships, Model Providers can adapt their ModelProvider to an 
-    IResourceMappingMerger to have access to the full content of the merge operation.<br>
-  </li>
-  <li>Model participation in team viewers: The team views now make use of the Common Navigator
-  framework. By extending a Common Navigator extension point and a Team extension point, and supplying a content
-  provider and a label provider, a Model Provider can appear in the team views. With a few more additional
-  steps, it is also possible to provide Merge Preview support for a model.
-    <br>
-  </li>
-  <li>Remote Discovery: Model Providers can participate in Remote Discovery through the use of
-  the Team ProjectSetCapability class to obtain an URI from project set entries. This URI can then
-  be used with the Eclipse File System API to access remote contents.
-  </li>
-  <li>Model History: Model Providers can access individual File History through the FileHistory API, and present a
-  model history  as they wish in a custom History Page which get displayed in the History View. </li>
-  
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_model_model.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_model_model.htm
deleted file mode 100644
index ae13795..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_model_model.htm
+++ /dev/null

@@ -1,474 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css"
-	rel="STYLESHEET">
-<title>Model Roadmap for Logical Model Integration</title>
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Model Roadmap for Logical Model Integration</h1>
-
-<p>Here is a list of what model providers can do to take advantage
-of the Team logical model support:</p>
-
-<ol>
-	<li>Adapt model elements in model views to <a
-		href="#ResourceMapping">ResourceMapping</a> in order to allow resource
-	based operations to appear on your model elements.</li>
-	<li>Register a <a href="#ModelProvider">ModelProvider</a> to
-	ensure that your model is consulted when operations are performed on
-	the resources related to your model.</li>
-	<li>Use the <a href="#ChangeValidation">ResourceChangeValidator</a>
-	when performing operations on resources in order to ensure that any
-	potential side effects on the model elements related to those resources
-	are made known to the user.</li>
-	<li>Implement an <a href="#AutoMerge">IResourceMappingMerger</a>
-	in order to participate in headless merges that involve the resources
-	related to your model.</li>
-	<li>Register a <a href="#TeamContent">teamContentProvider</a> in
-	order to participate in Team viewers such as merge previews.</li>
-	<li>Provide an <a href="#History">IHistoryPageSource</a> to show
-	logical model history in the Team history view.</li>
-	<li>Use the <a href="#RemoteBrowsing">Eclipse File System</a> API
-	to access the remote state of model projects.</li>
-	<li>Use the <a href="#Decoration">SynchronizationStateTester</a>
-	API to ensure proper decoration of model elements that do not have a
-	one-to-one mapping to resources.</li>
-	<li>Use the <a href="#Saveable">Saveable</a>
-	API to manage the save life cycle of model elements.)</li>
-    <li>Use the <a href="#ElementHistory">ElementLocalHistoryPageSource</a>
-	API to show local history for sub-file model elements (e.g. Java methods)</li>
-	<li>Use the <a href="#ChangeTracker">ChangeTracker</a>
-	API to group related changes together.</li>
-</ol>
-
-<p>The following sections describe each of these points in more
-detail. The <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a> 
-  plug-in contain an example that illustrate several of these points.
-  You can check the project out from the CVS repository and use it as 
-  a reference while you are reading this tutorial. <em>Disclaimer</em>: The source 
-  code in the example plug-ins may change over time. To get a copy that matches 
-  what is used in this example, you can check out the project using the 3.3 version 
-  tag (most likely R3_3) or a date tag of June 30, 2007.
-</p>
-
-<h2><a name="ResourceMapping"></a>Resource Mappings</h2>
-
-<h3>The Basic Resource Mapping API</h3>
-<p>The resource mapping API is purposely simple with logical model
-manipulations omitted. A client can't use this interface to display
-logical models or gain any interesting additional knowledge about it.
-It's purpose is simply to map one or more model elements to workspace
-resources.</p>
-<p>The API consists of the following classes:</p>
-<ul>
-	<li><strong>ResouceMapping</strong>: 
-	<a href="../reference/api/org/eclipse/core/resources/mapping/ResourceMapping.html">ResourceMapping</a>
-	is the Class to which logical model elements adapt to indicate that the
-	model corresponds to a set of resources in the workspace. The methods
-	of interest are:
-	<ul>
-		<li><code>Object getModelObject()</code>: The model object from
-		which the mapping was derived (or adapted).</li>
-		<li><code>ResourceTraversal[]
-		getTraversals(ResourceMappingContext, IProgressMonitor)</code>: The resource
-		traversal that cover the resources that constitute the model object.</li>
-	</ul>
-	</li>
-	<li><strong>ResourceTraversal</strong>: A <a
-		href="../reference/api/org/eclipse/core/resources/mapping/ResourceTraversal.html"><code>ResourceTraversal</code></a>
-	contains a set of resources and a depth flag that indicates the depth
-	to which the resources in the traversal are associated with the
-	originating model object. Resource traversals are provided to a client
-	by a resource mapping in order to describe the contents of a model in
-	such a way that the client (e.g. a repository provider) can perform its
-	operations in as efficient a means as possible. Methods of interest
-	are:
-	<ul>
-		<li><code>getResources()</code></li>
-		<li><code>getDepth()</code></li>
-	</ul>
-	</li>
-	<li><strong>ResourceMappingContext</strong>: A context that is
-	provided to the resource mapping by the client when obtaining
-	traversals. This context allows the logical model to determine what the
-	remote state of the model is so that the proper resources can be
-	covered by the resource traversals returned by the resource mapping.
-	The use of the<code> <a
-		href="../reference/api/org/eclipse/core/resources/mapping/ResourceMappingContext.html">ResourceMappingContext</a></code>
-	and<code> <a
-		href="../reference/api/org/eclipse/core/resources/mapping/RemoteResourceMappingContext.html">RemoteResourceMappingContext</a></code>
-	is a bit more complicated and is described in the <a
-		href="#ResourceMappingContext">Resource Mapping Context</a> section.</li>
-</ul>
-<p>There are two types of plugins that should be interested in
-resource mappings. Those who provide a model that consists of, or is
-persisted in, resources in the workspace and those that want to perform
-operations on resources. The former is covered in the next section while
-the later is covered in the <a href="team_model_repo.htm">Repository
-Roadmap for Logical Model Integration</a>.</p>
-
-<h3>Adapting a Model to a ResourceMapping</h3>
-
-<p>Plug-ins that adapted their model objects to <code>IResource</code>
-in order to get resource specific actions shown in the context menu can
-now adapt to <code>ResourceMapping</code> if a richer description of how
-the object adapts to resources is beneficial. However, they are not
-required to do so if there is no benefit. For instance a Java
-compilation unit (i.e. *.java file shown in a JDT view) that now
-currently adapts to <code>IFile</code> need not adapt to <code>ResourceMapping</code>
-since nothing is gained. However, a Java package should adapt to <code>ResourceMapping</code>
-in order to indicate that the package consists of only the files in the
-corresponding folder and not the subfolders.</p>
-<p>The preferred way to adapt model elements to a resource mapping
-is to use an adapter factory. The following is the XML markup for
-contributing an adapter factory in a plug-in manifest.</p>
-<pre style="background-color: rgb(204, 204, 255);">   &lt;extension<br>         point="org.eclipse.core.runtime.adapters"&gt;<br>      &lt;factory<br>            class="org.eclipse.example.library.logical.AdapterFactory"<br>            adaptableType="org.eclipse.example.library.Book"&gt;<br>         &lt;adapter type="org.eclipse.core.resources.mapping.ResourceMapping"/&gt;<br>      &lt;/factory&gt;<br>      &lt;factory<br>            class="org.eclipse.example.library.logical.AdapterFactory"<br>            adaptableType="org.eclipse.example.library.Library"&gt;<br>         &lt;adapter type="org.eclipse.core.resources.mapping.ResourceMapping"/&gt;<br>      &lt;/factory&gt;<br>      ...<br>   &lt;/extension&gt;</pre>
-<p>The adapter factory implementation would look something like
-this:</p>
-<pre style="background-color: rgb(204, 204, 255);">public class AdapterFactory implements IAdapterFactory {<br>   public Object getAdapter(Object adaptableObject, Class adapterType) {<br>      if((adaptableObject instanceof EObject) &amp;&amp; adapterType == ResourceMapping.class) {<br>         return new EObjectResourceMapping((EObject)adaptableObject);<br>      }<br>      return null;<br>   }<br><br>   public Class[] getAdapterList() {<br>      return new Class[] {ResourceMapping.class};<br>   }<br>}</pre>
-<p>Model objects can implement the <code>IAdaptable</code>
-interface. When they do so, they must ensure that the Platform adapter
-manager is consulted. This can be done by either subclassing <code>PlatformObject</code>
-or by using the following line of code:</p>
-<blockquote>
-<p><code>Platform.getAdapterManager().getAdapter(Object,
-Class)</code></p>
-</blockquote>
-<p>The above is the preferable approach. However, the model object
-can implement the IAdaptable interface and provide a <code>getAdapter(Class)</code>
-implementation that creates returns an instance of <code>ResourceMapping</code>
-explicitly when asked for one. This is a more straightforward approach
-but the least desirable as the model must have explicit knowledge of the
-adaptation to resources.</p>
-<p>In some cases, the provider of a logical model may not want their
-model to adapt to <code>IResource</code> in every context or may want
-the object to adapt differently for object contributions than for other
-contexts. The workbench UI provides a special intermediate adapter API,
-<code>IContributorResourceAdapter</code>, for this purpose. When objects
-are being adapted to <code>IResource</code> in the context of object
-contributions, the workbench first tries to adapt the resource to <code>IContributorResourceAdapter</code>
-before trying to adapt to <code>IResource</code> directly. A new
-sub-interface of this interface, <code>IContributorResourceAdapter2</code>,
-has been added which provides the same capability for <code>ResourceMapping</code>.
-The only difference is that the model provider should register a factory
-for<code> IContributorResourceAdapter</code> since the Workbench does an
-<em>instanceof</em> check to see if the contributed adapter is also an
-instance of <code>IContributorResourceAdapter2</code>.</p>
-<p>The implementation of the <code>ResourceMapping</code> subclass
-for a Java package would look something like this.</p>
-<pre style="background-color: rgb(204, 204, 255);">public class JavaPackageResourceMapping extends ResourceMapping {<br>   IPackageFragment package;<br>   ...<br>   public getModelObject() {<br>      return package;<br>   }<br>   public ResourceTraversals[] getTraversals(<br>             ResourceMappingContext context, <br>             IProgressMonitor monitor) {<br>      return new ResourceTraversal[] { <br>         new ResourceTraversal(<br>            new IResource[] { package.getCorrespondingResource() },<br>            IResource.DEPTH_ONE, IResource.NONE)<br>      }<br>   }<br>}</pre>
-<p>This is a fairly straightforward mapping so the implementation is
-not complex. The complexity of the resource mapping implementation will,
-of course, vary from model to model.</p>
-
-<h3><a name="ResourceMappingContext"></a>Resource Mapping Context</h3>
-<p>One of the advantages of a Resource Mapping API is that it allows
-plug-ins to implement any operations they desire in terms of resource
-mappings (e.g. CVS update, CVS commit, CVS tag, dirty decoration, etc.).
-However, the API that has been introduced so far deals only with the
-local state of the model. When working with a model that may be shared
-between developers, you end up in a situation where the remote state of
-the model (i.e. the state of the model that another user has checked-in
-to the repository) may differ from the state in the workspace. If you
-performed a CVS update, you would want the local state of the model to
-match the remote state even if it meant that additional files needed to
-be included or some files needed to be removed.</p>
-<p>This is not an issue for some logical models. For instance, a
-java package is a container visited to a depth of one, regardless of the
-remote state of the model. Given this, a repository provider can easily
-determine that outgoing deletions should be included when committing or
-that incoming additions should be included when updating. However, the
-resources that constitute some logical models may change over time. For
-instance, the resources that constitute a model element may depend of
-the contents of a manifest file (or some other similar mechanism). In
-order for the resource mapping to return the proper traversal, it must
-access the remote contents of the manifest file (if it differs from the
-local contents) in order to see if there are additional resources that
-need to be included. These additional resources may not exist in the
-workspace but the repository provider would know how to make sure they
-did when the selected action was performed.</p>
-<p>In order to support these more complex models, a <code>RemoteResourceMappingContext</code>
-can be passed to the <code>ResourceMapping#getTraversals</code> method.
-When a context is provided, the mapping can use it to ensure that all
-the necessary resources are included in the traversal. If a context is
-not provided, the mapping can assume that only the local state is of
-interest.</p>
-<h4>When does a ResourceMapping need to worry about the
-RemoteResourceMappingContext?</h4>
-<p>A <code>ResourceMapping</code> need only worry about a context
-supplied to the <code>getTraversals</code> method in cases were the
-resources that make up a model change over time and the relationship
-between the model and resources cannot be described by a simple
-traversal that is guaranteed to encompass those resources (and only
-those resources) that constitute the model. For example, although the
-resources of a Java package may change over time, the package can be
-described as a folder of depth of one so a resource mapping for java
-packages would not need to make use of the resource mapping context.</p>
-<p>As a more complicated example, consider an HTML file that
-contains several images. Let's make the assumption that any images
-references from an HTML file are part of the model of that file. When
-updating the local contents of the HTML file from a repository, the user
-would expect that any new images would be included. The <code>getTraversals</code>
-method for a <code>ResourceMapping</code> for the HTML file model would
-look something like this:</p>
-<pre style="background-color: rgb(204, 204, 255);">public class HTMLResourceMapping extends ResourceMapping {<br>	   private HTMLFile htmlFile;<br>	   public ResourceTraversal[] getTraversals(ResourceMappingContext context, <br>              IProgressMonitor monitor)<br>	      IResource[] resources = htmlFile.getResources();<br>	      if (context instanceof RemoteResourceMappingContext) {<br>	         // Look for any additional resources on the server<br>	         RemoteResourceMappingContext remoteContext = (RemoteResourceMappingContext)context;<br>	         IFile file = htmlFile.getFile();<br>	         if (remoteContext.hasRemoteChange(file, monitor)) {<br>	        	 IStorage storage = remoteContext.fetchRemoteContents(file, monitor);<br>	        	 IResource[] additionalResources = getReferences(storage.getContents());<br>	        	 resources = combine(resources, additionalResources);<br>	         }<br>	         if (remoteContext.isThreeWay() &amp;&amp; remoteContext.hasLocalChange(file, monitor)) {<br>        		 IStorage storage = remoteContext.fetchBaseContents(file, monitor);<br> 	             IResource[] additionalResources = getReferences(storage.getContents());<br>	             resources = combine(resources, additionalResources);<br>	         }<br>	      }<br>	      return new ResourceTraversal[] { <br>            new ResourceTraversal(resources, IResource.DEPTH_ZERO, IResource.NONE)};<br>	   }<br>}</pre>
-<p>Notice that there are two sets of resources included in the
-model: those derived from the local contents of the HTML file in the
-workspace and those obtained from the contents of the remote file and
-base file. In either of these two sets, there may be resources that do
-not exist in the workspace. For instance, the local HTML file may
-contain a relative link to an image that does not exist in the
-workspace. This resource should be included so that it will be fetched
-if it exists remotely. As for the remote file, it may contain a new copy
-that references additional images that should be fetched when the new
-remote contents are downloaded.</p>
-
-
-<h2><a name="ModelProvider"></a>Model Providers</h2>
-
-<p>Model providers are a means to group related resource mappings
-together. Here is a link to the <a
-	href="../reference/api/org/eclipse/core/resources/mapping/ModelProvider.html">ModelProvider</a>
-class. This class serves three main purposes:</p>
-<ol>
-	<li>From a model provider, clients can then obtain additional API
-	pieces for performing operations on a set of resource mappings using
-	the adaptable mechanism. For example, the <code>IResourceMappingMerger</code>
-	for the model is obtained by adapting the model provider.</li>
-	<li>Given a set of file-system resources, clients can query
-	whether a model provider has model elements persisted in those
-	resources and, if it does, obtain the set of resource mappings that
-	describe the relationship.</li>
-	<li>For operations on a set of resources, the resource change
-	validator will query the model providers in order to determine if there
-	are any potential side effects of an operation that users should be
-	made aware of. This is covered in a separate section on <a
-		href="#ChangeValidation">change validation</a>.</li>
-</ol>
-<p>The following is an example of a modelProvider extension
-definition.</p>
-<pre style="background-color: rgb(204, 204, 255);">   &lt;extension<br>         id="modelProvider"<br>         name="Library Example"<br>         point="org.eclipse.core.resources.modelProviders"&gt;<br>      &lt;modelProvider<br>            class="org.eclipse.team.examples.library.adapt.LibraryModelProvider"<br>            name="Library Example"/&gt;<br>      &lt;extends-model id="org.eclipse.core.resources.modelProvider"/&gt;<br>      &lt;enablement&gt;
-         &lt;test property="org.eclipse.core.resources.projectNature" 
-               value="org.eclipse.team.examples.library.view.nature" /&gt;<br>       &lt;/enablement&gt;<br>   &lt;/extension&gt;<br></pre>
-<p>The <code>LibraryModelProvider</code> is a subclass of <code>ModelProvider</code>.
-The enablement rule is used to match resources that the Library model
-persists its model in. In the above example, the model provider will
-match any resource in a project that has the library nature.</p>
-<p>Once the model provider is defined, the <code>ResourceMapping#getModelProviderId()</code>
-method should be overridden to return the id of the model provider.</p>
-<pre style="background-color: rgb(204, 204, 255);">   public String getModelProviderId() {<br>      return "org.eclipse.team.examples.library.adapt.modelProvider";<br>   }<br></pre>
-<p>To get the proper inverse mapping of resources to resource
-mapping for those resources that match your provider's enablement rule,
-you should also override one or both of the <code>getMapping</code>
-methods. The method that you need to override depends on whether your
-model has elements that contain multiple resources or not. If your model
-elements map to a single resource, you can override the method that
-accepts a single<code>IResource</code> argument. Otherwise, you will
-need to override the method that accepts an array of resources. Here's
-an example using the single resource case.</p>
-<p>The following example method wraps a library model file in an
-appropriate resource mapping. It also wraps folders that contain files
-that are of interest to the model provider.<br>
-</p>
-<pre style="background-color: rgb(204, 204, 255);">public class LibraryModelProvider extends ModelProvider {<br>	   public ResourceMapping[] getMappings(IResource resource, <br>              ResourceMappingContext context, IProgressMonitor monitor) {<br>          if (isModelFile(resource)) {<br>              // Return a resource mapping on the file<br>              return new LibraryResourceMapping(resource);<br>          } if (containsModelFiles(resource)) {<br>              // Create a deep resource mapping on the container<br>              return new LibraryContainerResourceMapping(resource);<br>          }<br>          // The resource is not of interest to this model provider<br>          return null;<br>	   }<br>}</pre>
-<p>Clients can then access the model provider to determine whether
-the model providers cares about the resources that are about to be
-operated on. The next section describes API that will be provided to
-team operations that use the model provider API to determine the
-complete set of resource mappings to be operated on when a team
-operation is performed on a set of selected resources or model elements.</p>
-
-
-<h2><a name="ChangeValidation"></a>Resource Change Validation</h2>
-
-<p>Operations performed on resources should be validated first to
-ensure that the user is aware of any potential side effects. Here are the
-steps required to validate a resource change.</p>
-<ol>
-	<li>Build up a description of the change using the <code><a
-		href="../reference/api/org/eclipse/core/resources/mapping/IResourceChangeDescriptionFactory.html">IResourceChangeDescriptionFactory</a></code>.
-	The factory produces an <code>IResourceDelta</code> that mirrors what
-	the resulting resource delta will look like once the operation is
-	performed.</li>
-	<li>Validate the change using the <code><a
-		href="../reference/api/org/eclipse/core/resources/mapping/ResourceChangeValidator.html">ResourceChangeValidator</a></code>.
-	The validator consults all the model providers that have registered an
-	interest in the affected resources. The result is one or more status
-	that contain the id of the originating model and a description of the
-	potential side effect of the operation on the model.</li>
-	<li>Make the user aware of any potential side effects from models
-	that are unknown to the originator of the operation. For instance, if a
-	Java refactoring has received a side effect from the Java model, it can
-	be ignored since the refactoring understands the semantics of the Java
-	model. However, if a side effect from the Library model is returned, it
-	should be made known to the user since Java has no knowledge of the
-	Library model.</li>
-</ol>
-
-<h2><a name="AutoMerge"></a>Model-based Merging</h2>
-
-<p>When a Team provider is attempting a headless merge, it will do
-the following:</p>
-<ol>
-	<li>Obtain the resource mappings from the selected elements</li>
-	<li>Determine the model providers involved using the
-	ResourceMapping#getModelProvider() method.</li>
-	<li>Expand the scope of the operation to include all necessary
-	resource mappings.</li>
-	<li>Build up a description of the synchronization state between
-	the local and remote. This description is provided to the models
-	through the <a
-		href="../reference/api/org/eclipse/team/core/mapping/IMergeContext.html">IMergeContext</a>
-	API.</li>
-	<li>Adapt the model providers to <a
-		href="../reference/api/org/eclipse/team/core/mapping/IResourceMappingMerger.html">IResourceMappingMerger</a>.
-	</li>
-	<li>Invoke the validateMerge method on each merger, passing in the
-	synchronization description, to ensure there is not some condition that
-	should prevent an attempted merge.</li>
-	<li>Delegate the merge to the model mergers to perform the merge.
-	</li>
-	<li>Model providers can delegate the merge of individual files
-	back to the Team provider if they only want to control the order of the
-	merge or may perform the merge themselves and signal to the team
-	provider when they are done.</li>
-</ol>
-
-<h2><a name="TeamContent"></a>Model Content in Team Operation Views</h2>
-
-<p>The display of model elements in the context of a Team operation
-is made possible by the Common Navigator framework.</p>
-<ul>
-	<li>Provide an extension of the <a
-		href="../reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent</a>
-	extension.</li>
-	<li>Provide an extension of the <a
-		href="../reference/extension-points/org_eclipse_team_ui_teamContentProviders.html">org.eclipse.team.ui.teamContentProviders</a>
-	extension point to associate the content provider with a model
-	provider.</li>
-	<li>Implement a content provider and label provider for the
-	navigatorContent extension. It is best to subclass <a
-		href="../reference/api/org/eclipse/team/ui/mapping/SynchronizationContentProvider.html">SynchronizationContentProvider</a>
-	and <a
-		href="../reference/api/org/eclipse/team/ui/mapping/SynchronizationLabelProvider.html">SynchronizationLabelProvider</a>
-	for this. They wrap existing content/label providers and handle
-	interactions with the team provider such as sync state decoration and
-	filtering based on sync state.</li>
-</ul>
-<p>The above steps will allow models to appear in dialogs used by
-team operations. There are additional steps required to integrate into a
-merge preview.</p>
-<ul>
-	<li>Adapt the model provider to <a
-		href="../reference/api/org/eclipse/team/ui/mapping/ISynchronizationCompareAdapter.html">ISynchronizationCompareAdapter</a>.
-	This is done to allow the model to open model specific compare editors
-	on model elements.</li>
-	<li>Implement an acti on provider for the navigatorContent
-	extension as a subclass of <a
-		href="../reference/api/org/eclipse/team/ui/mapping/SynchronizationActionProvider.html">SynchronizationActionProvider</a>.
-	This will allow the model to register merge handlers that will be
-	invoked when users perform merge operations on the model
-	provider's elements in the merge preview.</li>
-</ul>
-
-<h2><a name="History"></a>History View</h2>
-
-<p>The following improvements have been made in the area of file
-history and model element history:</p>
-<ul>
-	<li>The History view has been generalized to display the history of
-	any object that adapts to an <a
-		href="../reference/api/org/eclipse/team/ui/history/IHistoryPageSource.html">IHistoryPageSource</a>.
-	Thus, model providers can render the history for their logical model
-	elements.</li>
-	<li>An <a
-		href="../reference/api/org/eclipse/team/core/history/IFileHistoryProvider.html">IFileHistoryProvider</a>
-	API has been added for obtaining and querying the remote history of
-	workspace files. Logical models can obtain and interpret this history.</li>
-	<li>An <a
-		href="../reference/api/org/eclipse/team/ui/history/IHistoryCompareAdapter.html">IHistoryCompareAdapter</a>
-	is used to hook up the selection in an IHistoryPage to compare editors
-	so that history pages can be reused in the context of compare
-	operations.</li>
-</ul>
-
-<h2><a name="RemoteBrowsing"></a>Remote Browsing</h2>
-
-<p>The following has been provided to support remote browsing:</p>
-<ul>
-	<li>An Eclipse File System API has been introduced in the
-	org.eclipse.core.filesystem plug-in.</li>
-	<li>API has been added to the <a
-		href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a> to obtain
-	the URI from project set entries. These URIs can be used to obtain a
-	FileSystem for the purposes of browsing remote contents.</li>
-	<li>Models that require an IResource base project can use the file
-	system to create a team-private project.</li>
-	<li>Methods have been added to the ProjectSetCapability for
-	loading a URI as a project.</li>
-</ul>
-
-<h2><a name="Decoration"></a>Decorating Model Elements with Team State</h2>
-
-<p>Team providers can decorate model elements by converting their
-lightweight decorators to work for resource mappings in the same way
-object contributions are converted to work for resource mappings.
-However, there is one aspect of logical model element decoration that is
-problematic. If a model element does not have a one-to-one mapping to a
-resource, the model element may not receive a label update when the
-underlying resources change.</p>
-
-<p>To address this issue, the <code><a
-		href="../reference/api/org/eclipse/team/ui/mapping/ITeamStateProvider.html">ITeamStateProvider</a></code> was introduced in order to give model
-providers access to state changes that may affect team decorations. In addition,
-model views can use a <code><a
-		href="../reference/api/org/eclipse/team/ui/mapping/SynchronizationStateTester.html">SynchronizationStateTester</a></code> to determine when the
-labels of logical model elements need to be updated. This API relies on
-the <code>ITeamStateProvider</code> interface to determine when the team state
-of resource has changed and can be passed to a team decorator as part of an <code><a
-		href="../reference/api/org/eclipse/jface/viewers/IDecorationContext.html">IDecorationContext</a></code>.</p>
-
-<h2><a name="Saveable"></a>Using the Saveable API</h2>
-
-<p>
-Logical model providers may use the <code>
-<a href="../reference/api/org/eclipse/ui/Saveable.html">Saveable</a></code> 
-API to manage the Save lifecycle of their model elements. If they do so,
-they should adapt their Saveable instances to a ResourceMapping to ensure that
-repository providers (and other tools) can determine which resources would be affected
-if the saveable was saved. For instance, this is important in the case where a repository
-provider wants to ensure that there are no open dirty editors on a set of resources before a repository
-operation is performed.</p>
-
-<h2><a name="ElementHistory"></a>Showing the history of sub-file elements</h2>
-
-<p>The <code><a href="../reference/api/org/eclipse/team/ui/history/ElementLocalHistoryPageSource.html">ElementLocalHistoryPageSource</a></code>
-class can be used by models to show the local history for a sub-file element such as a Java method. 
-History can be shown in the History view by calling the 
-<code><a href="../reference/api/org/eclipse/team/ui/TeamUI.html">TeamUI</a>#showHistory</code> method with the model element 
-and history page source as arguments. Models that call this also need to provide a subclass of
-<a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureCreator.html"><code>StructureCreator</code></a>
-as described in the <a href="compare_beyond.htm#Patch">Advanced compare techniques</a> section.
-The history can also be shown in a dialog using the 
-<code><a href="../reference/api/org/eclipse/team/ui/history/HistoryPageCompareEditorInput.html">HistoryPageCompareEditorInput</a></code>
-class. Subclasses can control whether the dialog is to be used for comparison purposes or as a dialog that supports
-replacing the current element with an element from the history.
-</p>
-
-<h2><a name="ChangeTracker"></a>Grouping related changes</h2>
-
-Model providers that wish to ensure that changes to sets of resources are committed or checked-in to a repository together
-can subclass the 
-<code><a href="../reference/api/org/eclipse/team/core/mapping/ChangeTracker.html">ChangeTracker</a></code> class. This class
-is used to track local changes and issue requests to the repository provider to group related changes together.
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_model_repo.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_model_repo.htm
deleted file mode 100644
index 34a1360..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_model_repo.htm
+++ /dev/null

@@ -1,594 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css"
-	rel="STYLESHEET">
-<title>Repository Roadmap for Logical Model Integration</title>
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-
-<body bgcolor="#ffffff">
-
-
-<h1>Repository Roadmap for Logical Model Integration</h1>
-
-<p>To provide full support for logical models, a repository provider
-can perform the following steps:</p>
-<ol>
-
-	<li>Contribute the appropriate repository operations to elements
-	that adapt to <a href="#ResourceMapping"><code>ResourceMapping</code></a>.</li>
-
-	<li>Ensure that operations performed on resource mappings include
-	all the appropriate model elements and resources by using an <a
-		href="#SyncScope"><code>ISynchronizationScope</code></a> and
-	supporting API.</li>
-
-	<li>Allow model providers to participate in headless merging
-	through the <a href="#AutoMerge"><code>IMergeContext</code></a>
-	interface and supporting API.</li>
-
-	<li>Allow model providers to participate in merge previews by
-	using the <a href="#TeamContent"><code>teamContentProviders</code></a>
-	for the models involved in the merge. A <code>ModelSynchronizeParticipant</code>
-	class is provided to help manage the relationship between the model
-	content, a merge context and the Compare framework.</li>
-
-	<li>Provide access to the history of workspace files through the <a
-		href="#FileHistory"><code>IFileHistoryProvider</code></a> API</li>
-
-	<li>Provide access to remote configurations using the Eclipse File
-	System API in the <em>org.eclipse.core.filesystem</em> plug-in and link
-	this to workspace projects through the <a href="#EFS"><code>ProjectSetCapability</code></a>
-
-	</li>
-	<li>Support logical model element decoration by providing a
-	workspace <code>Subscriber</code> for use with the <a
-		href="#Decoration"><code>SynchronizationStateTester</code></a> API.</li>
-		
-	<li>Allow models to group related changes by implementing the <a
-		href="#ChangeGrouping"><code>IChangeGroupingRequestor</code></a> API.</li>
-</ol>
-
-<p>The following sections describe each of these points in more
-detail. The <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a> 
-  plug-in contain an example that illustrate several of these points.
-  You can check the project out from the CVS repository and use it as 
-  a reference while you are reading this tutorial. <em>Disclaimer</em>: The source 
-  code in the example plug-ins may change over time. To get a copy that matches 
-  what is used in this example, you can check out the project using the 3.3 version 
-  tag (most likely R3_3) or a date tag of June 30, 2007.
-</p>
-
-
-<h2><a name="ResourceMapping"></a>Contributing Actions to Resource
-Mappings</h2>
-
-<h3>The Basic Resource Mapping API</h3>
-
-<p>The resource mapping API consists of the following classes:</p>
-<ul>
-	<li><a
-		href="../reference/api/org/eclipse/core/resources/mapping/ResourceMapping.html">ResourceMapping</a>:
-	The class to which logical model elements adapt to indicate that the
-	model corresponds to a set of resources in the workspace. The methods
-	of interest are:
-	<ul>
-		<li><code>Object getModelObject()</code>: The model object from
-		which the mapping was derived (or adapted).</li>
-		<li><code>ResourceTraversal[]
-		getTraversals(ResourceMappingContext, IProgressMonitor)</code>: The resource
-		traversal that cover the resources that constitute the model object.</li>
-	</ul>
-	</li>
-	<li><a
-		href="../reference/api/org/eclipse/core/resources/mapping/ResourceTraversal.html">ResourceTraversal</a>:
-	A <code>ResourceTraversal</code> contains a set of resources and a
-	depth flag that indicates the depth to which the resources in the
-	traversal are associated with the originating model object. Resource
-	traversals are provided to a client by a resource mapping in order to
-	describe the contents of a model in such a way that the client (e.g. a
-	repository provider) can perform its operations in as efficient a means
-	as possible. Methods of interest are:
-	<ul>
-		<li><code>getResources()</code></li>
-		<li><code>getDepth()</code></li>
-	</ul>
-	</li>
-	<li><a
-		href="../reference/api/org/eclipse/core/resources/mapping/ResourceMappingContext.html">ResourceMappingContext</a>:
-	a context that is provided to the resource mapping by the client when
-	obtaining traversals. This context allows the logical model to
-	determine what the remote state of the model is so that the proper
-	resources can be covered by the resource traversals returned by the
-	resource mapping. The use of the <code>ResourceMappingContext</code>
-	and <code><a
-		href="../reference/api/org/eclipse/core/resources/mapping/RemoteResourceMappingContext.html">RemoteResourceMappingContext</a></code>
-	is a bit more complicated and is described <a
-		href="#ResourceMappingContext">later</a>.</li>
-</ul>
-<p>There are two types of plugins that should be interested in
-resource mappings. Those who provide a model that consists of, or is
-persisted in, resources in the workspace and those that want to perform
-operations on resources. The former case will be covered in the <a
-	href="team_model_model.htm">model roadmap</a> and the later case is
-covered in the next section.</p>
-
-<h3>Resource Mappings and Object Contributions</h3>
-
-<p>Plug-ins that contribute extensions to adaptable extension points
-will have to make two changes to support the new <code>ResourceMapping</code>
-APIs:</p>
-<ol>
-	<li>Update any <em>objectContributions</em> of the <a
-		href="../reference/extension-points/org_eclipse_ui_popupMenus.html">popupMenus</a>
-	extension point in their plugin.xml file to target <code>ResourceMapping</code>
-	instead of <code>IResource</code> (for those for which this is
-	appropriate).</li>
-	<li>Update their actions to work on <code>ResourceMapping</code>
-	instead of <code>IResource</code> and respect the depth constraints
-	provided in the traversals.</li>
-</ol>
-<p>Plug-ins that add object contributions to <code>IResource</code>
-can now add them to <code>ResourceMapping</code> instead, if the action
-can apply to multiple resources. Here is an XML snippet that contributes
-a menu action to objects that adapt to resource mappings:</p>
-
-<pre style="background-color: rgb(204, 204, 255);">   &lt;extension
-       point="org.eclipse.ui.popupMenus"&gt;
-      &lt;objectContribution
-            objectClass="org.eclipse.core.resources.mapping.ResourceMapping"
-            adaptable="true"
-            id="org.eclipse.team.ccvs.ui.ResourceMapperContributions"&gt;
-         &lt;enablement&gt;<br>           &lt;adapt type="org.eclipse.core.resources.mapping.ResourceMapping"&gt;<br>              &lt;test <br>                 property="org.eclipse.core.resources.projectPersistentProperty" <br>                 args="org.eclipse.team.core.repository,org.eclipse.team.cvs.core.cvsnature" /&gt;<br>           &lt;/adapt&gt;<br>         &lt;/enablement&gt;<br>         &lt;action<br>               label="%UpdateAction.label"<br>               definitionId="org.eclipse.team.cvs.ui.update"<br>               class="org.eclipse.team.internal.ccvs.ui.actions.UpdateAction"<br>               tooltip="%UpdateAction.tooltip"<br>               menubarPath="team.main/group2"<br>               id="org.eclipse.team.cvs.ui.update"&gt;<br>         &lt;/action&gt;<br>         ...<br>      	&lt;/objectContribution&gt;<br>   &lt;/extension&gt;</pre>
-
-<p>Contributions to <code>ResourceMapping</code> will automatically
-apply to objects that adapt to <code>IResource</code>. This transitive
-association is handled by the Workbench. Filtering of the contributions
-to resource mappings can be done using enablement expressions. An
-expression for filtering by project persistent property has been added
-to allow repository providers to have their menus appear on projects
-that are mapped to their repositories.</p>
-
-<p>Actions that have been contributed to the <code>ResourceMapping</code>
-class will be given a selection that contains one or more <code>ResourceMappings</code>.
-It is the actions responsibility to translate the resource mapping into
-a set of resources to be operated on. This can be done by calling <code>getTraversals</code>
-to get the traversals of the mapping. Traversals are used to allow the
-clients of the traversal to optimize their operations based on the depth
-of the resources being traversed. A client may traverse the resource
-manually or may use the resource and the depth as input into an
-operation that the action delegates to do the work. As an example, if
-the user performs a CVS update on a java package and the java package
-resource mapping maps to a folder of depth one, CVS would issue an
-appropriate command ("cvs update -l" for those who are curious) which
-would perform a shallow update on the folder the package represents.</p>
-
-<p>Although it is possible to obtain a set of traversals directly
-from the selected resource mappings, there are model relationships (or
-repository relationships) that may require the inclusion of additional
-resources or model elements in an operation. The next section describes
-how to ensure that all required resources are included in an operation</p>
-
-<h2><a name="SyncScope"></a>Operation Scope</h2>
-
-<p>For team operations, the selected mappings need to be translated
-into the set of mappings to be operated on. This process involves
-consulting all model providers to ensure that they get included in
-operations on resources that match their enablement rules. The term we
-use to describe the complete set of resource mappings to be operated on
-is the operation <em>scope</em>. The following API has been provided for
-this:</p>
-<ul>
-	<li><code><a
-		href="../reference/api/org/eclipse/team/core/mapping/ISynchronizationScope.html">ISynchronizationScope</a></code>:
-	Interface that defines the API for accessing the scope of the
-	operation. It provides access to all the resource mappings being
-	operated on and the traversals for those mappings as they were
-	calculated during the scope building process.</li>
-	<li><code><a
-		href="../reference/api/org/eclipse/team/core/mapping/ISynchronizationScopeManager.html">ISynchronizationScopeManager</a></code>:
-	Interface that defines the API for creating and managing a scope.</li>
-	<li><code><a
-		href="../reference/api/org/eclipse/team/core/mapping/provider/SynchronizationScopeManager.html">SynchronizationScopeManager</a></code>:
-	Extendable class that provides a default implementation of the <code>ISynchronizationScopeManager</code>
-	API.</li>
-	<li><code><a
-		href="../reference/api/org/eclipse/team/ui/synchronize/ModelOperation.html">ModelOperation</a></code>:
-	Extendable operation class that generates a scope using a provided
-	scope manager and prompts if additional resources or mappings have been
-	included in the operation due to model provider relationships.</li>
-</ul>
-<p>The <em>initialize(IProgressMonitor)</em> method of the <code>SynchronizationScopeManager</code>
-class handles the entire process of converting an input set of resource
-mappings into the complete set of mappings that need to be operated on
-as well as the complete set of traversals that cover these mappings. A
-repository provider can tailor the process by:</p>
-<ol>
-	<li>Providing a <code>RemoteResourceMappingContext</code> for use
-	when obtaining resource traversals from resource mappings.</li>
-	<li>Overriding <code>SynchronizationScopeManager</code> to tailor
-	the scope management process as required.</li>
-</ol>
-<p>The next two sections describe these points in more detail.</p>
-
-<h3><a name="ResourceMappingContext"></a>Remote Resource Mapping
-Context</h3>
-
-<p>In order to guarantee that all necessary resources get included
-in a team operation, the model provider may need the ability to glimpse
-at the state of one or more resources in the repository. For some
-models, this may not be required. For instance, a java package is a
-container visited to a depth of one, regardless of the remote state of
-the model. Given this, a repository provider can easily determine that
-outgoing deletions should be included when committing or that incoming
-additions should be included when updating. However, the resources that
-constitute some logical models may change over time. For instance, the
-resources that constitute a model element may depend of the contents of
-a manifest file (or some other similar mechanism). In order for the
-resource mapping to return the proper traversal, it must access the
-remote contents of the manifest file (if it differs from the local
-contents) in order to see if there are additional resources that need to
-be included. These additional resources may not exist in the workspace
-but the repository provider would know how to make sure they did when
-the selected action was performed.</p>
-<p>In order to support these more complex models, a <code>RemoteResourceMappingContext</code>
-can be passed to the <code>ResourceMapping#getTraversals</code> method.
-When a context is provided, the mapping can use it to ensure that all
-the necessary resources are included in the traversal. If a context is
-not provided, the mapping can assume that only the local state is of
-interest.</p>
-
-<p>The remote resource mapping context provides three basic queries:</p>
-<ul>
-	<li>What type of comparison is being performed: two-way or
-	three-way?
-	<ul>
-		<li>For two-way, does the local contents differ from the remote
-		contents?</li>
-		<li>For three-way, are there local changes and are there remote
-		changes?</li>
-	</ul>
-	</li>
-	<li>What are the contents of the remote (and base for three-way)
-	counterparts of the file?</li>
-	<li>What are the remote members of a folder?</li>
-</ul>
-<p>The answer to the first question above depends on the type of
-operation that is being performed. Typically, updates and merges are
-three-way while comparisons and replace operations (at least for CVS)
-are two-way.</p>
-<p>The Eclipse Team API includes a <code>Subscriber</code> class
-that defines an API for providing the synchronization state between the
-local workspace and a remote server. A <code><a
-	href="../reference/api/org/eclipse/team/core/subscribers/SubscriberResourceMappingContext.html">SubscriberResourceMappingContext</a></code>
-is provided that uses a <code><a
-	href="../reference/api/org/eclipse/team/core/subscribers/Subscriber.html">Subscriber</a></code>
-to access the necessary remote state. Clients that have a <code>Subscriber</code>
-do not need to do any additional work to get a resource mapping context.</p>
-
-<h3>Subclassing SynchronizationScopeManager</h3>
-
-<p>The <code>SynchronizationScopeManager</code> class can be
-subclassed to tailor the scope generation and management process. The
-two main reasons for subclassing the scope manager are:</p>
-<ol>
-	<li>The repository provider needs to include additional resources
-	due to some repository level relationship (e.g. change set). This can
-	be accomplished by overriding the <em>adjustInputTraversals(ResourceTraversal[])</em>
-	method.</li>
-	<li>The synchronization has a longer lifecycle (e.g. Synchronize
-	view vs. dialog) and needs the potential to react to scope changes. The
-	<code><a
-		href="../reference/api/org/eclipse/team/core/mapping/ISynchronizationScopeParticipant.html">ISynchronizationScopeParticipant</a></code>
-	interface defines the API that model providers can use to participate
-	in the scope management process. The <code><a
-		href="../reference/api/org/eclipse/team/core/subscribers/SubscriberScopeManager.html">SubscriberScopeManager</a></code>
-	class is a <code>Subscriber</code> based subclass of <code>SynchronizationScopeManager</code>
-	that involves participants in the scope management process. An example
-	of why this type of process is needed is working sets. If a working set
-	is one of the resource mappings in a scope, the set of traversals
-	covered by the scope would increase if resources were added to the
-	working set.</li>
-</ol>
-
-<h2><a name="AutoMerge"></a>Model-based Merging</h2>
-
-<p>The main repository operation type that requires model
-participation is merging. In many cases, models only need to participate
-at the file level. For this, the <code>IStorageMerger</code> API was
-introduced to allow model providers to contribute mergers that should be
-used to merge files of a particular extension or content type. However,
-in some cases, models may need additional context to participate
-properly in a merge. For this purpose, we introduced the <code>IResourceMappingMerger</code>
-and <code>IMergeContext</code> APIs.</p>
-
-<p>Merge operations are still triggered by actions associated with a
-repository provider. However, once a merge type operation is requested
-by the user, the repository provider needs to involve the model
-providers in the merge process to ensure that the merge does not corrupt
-the model in some way.</p>
-
-<p>There are two main pieces of repository provider API related to
-the model-based merging support.</p>
-<ol>
-	<li>API to describe the synchronization state of the resources
-	involved in the merge.</li>
-	<li>API to allow model providers to merge model elements.</li>
-</ol>
-The following sections describe these two pieces.
-
-<h3>API for Synchronization State Description</h3>
-
-<p>An important aspect of model-based merging is the API used to
-communicate the synchronization state of the resources involved to the
-model provider. The following interfaces are used to describe the
-synchronization state:</p>
-<ul>
-	<li><a
-		href="../reference/api/org/eclipse/team/core/mapping/ISynchronizationContext.html">ISynchronzationContext</a>:
-	provides access to the synchronization state of all resources within
-	the scope of the operation. The following API pieces are used to
-	describe the synchronization state of resources.
-	<ul>
-		<li><a
-			href="../reference/api/org/eclipse/team/core/diff/IDiff.html">IDiff</a>:
-		A generic path-based diff that consist of a diff kind (NO_CHANGE, ADD,
-		REMOVE, CHANGE).</li>
-		<li><a
-			href="../reference/api/org/eclipse/team/core/diff/ITwoWayDiff.html">ITwoWayDiff</a>:
-		A diff that provides more details about a change between two states of
-		an element (CONTENT, MOVE_TO, MOVE_FROM, COPY_FROM, REPLACE).</li>
-		<li><a
-			href="../reference/api/org/eclipse/team/core/diff/IThreeWayDiff.html">IThreeWayDiff</a>:
-		A diff that consists of either a local or remote two-way diff or both
-		and provides a direction description for the change (INCOMING,
-		OUTGOING, CONFLICTING) based on the presence of either or both the
-		local and remote change.</li>
-		<li><a
-			href="../reference/api/org/eclipse/team/core/mapping/IResourceDiff.html">IResourceDiff</a>:
-		A two-way diff that applies to resources and provides access to the
-		before state and after state of files through the <a
-			href="../reference/api/org/eclipse/team/core/history/IFileRevision.html">IFileRevision</a>
-		API.</li>
-		<li><a
-			href="../reference/api/org/eclipse/team/core/diff/IDiffTree.html">IDiffTree</a>:
-		A generic path-based data structure for accessing a tree of diffs.</li>
-		<li><a
-			href="../reference/api/org/eclipse/team/core/mapping/IResourceDiffTree.html">IResourceDiffTree</a>:
-		A resource-based data structure that contains the synchronization
-		state for all resources in the operation scope that are out-of-sync.</li>
-	</ul>
-	</li>
-</ul>
-
-<p>Abstract classes are provided for all these interfaces with the
-convention that the class names match the interface names with the "I"
-prefix removed. The only class that repository providers must override
-is the <code>ResourceDiff</code> class so that appropriate before and
-after file revisions can be provided.</p>
-
-<h3>API for Model Merging</h3>
-
-<p>The <a
-	href="../reference/api/org/eclipse/team/core/mapping/IMergeContext.html">IMergeContext</a>
-interface extends synchronization context with additional methods that
-support merging. Callback methods exist for:</p>
-<ul>
-	<li>Merging one or more diffs.</li>
-	<li>Rejecting the remote changes in one or more diffs</li>
-	<li>Indicating that one or more conflicts have been merged by the
-	model</li>
-	<li>Performing a group of operations while holding an appropriate
-	scheduling rule.</li>
-</ul>
-<p>An abstract <a
-	href="../reference/api/org/eclipse/team/core/mapping/provider/MergeContext.html">MergeContext</a>
-class is provided that contains default implementations for much of the
-merging behavior and also uses the <a
-	href="../reference/api/org/eclipse/team/core/mapping/IStorageMerger.html">IStorageMerger</a>
-to perform three-way merges. A <a
-	href="../reference/api/org/eclipse/team/core/subscribers/SubscriberMergeContext.html">SubscriberMergeContext</a>
-class is also provided which handles the population and maintenance of
-the synchronization state description associated with the merge context.</p>
-
-<p>An operation class, <a
-	href="../reference/api/org/eclipse/team/ui/synchronize/ModelMergeOperation.html">ModelMergeOperation</a>
-is provided which uses the <code>IResourceMappingMerger</code> API to
-perform a model-based merge operation. Subclasses need to override the <code>initializeContext(IProgressMonitor)</code>
-method to return a merge context. The operation uses this context to
-attempt a headless model-based merge. If conflicts exist, the preview of
-the merge is left to the subclass. As we'll see in the next section,
-there is a <a
-	href="../reference/api/org/eclipse/team/ui/synchronize/ModelParticipantMergeOperation.html">ModelParticipantMergeOperation</a>
-that provides preview capabilities using a <a
-	href="../reference/api/org/eclipse/team/ui/synchronize/ModelSynchronizeParticipant.html">ModelSynchronizeParticipant</a>.</p>
-
-
-<h2><a name="TeamContent"></a>Model Content in Team Viewers</h2>
-
-<p>Support for the display of logical models in a team operation is
-provided using the Common Navigator framework which was introduced in
-Eclipse 3.2. Logical models can associate a content extension with a
-model provider using the <em><a
-	href="../reference/extension-points/org_eclipse_team_ui_teamContentProviders.html">org.eclipse.team.ui.teamContentProviders</a></em>
-extension point. Team providers access these content providers through
-the <code>ITeamContentProviderManager</code>.</p>
-
-<p>There are several places where a team provider may wish to
-display logical models:</p>
-<ul>
-	<li>When the scope of an operation has been expanded due to model
-	provider relationships. The <code>ModelOperation</code> class provides
-	a prompt that uses the registered team content providers to inform the
-	user of a scope expansion.</li>
-	<li>When a merge preview is required. The <a
-		href="../reference/api/org/eclipse/team/ui/synchronize/ModelSynchronizeParticipant.html">ModelSynchronizeParticipant</a>
-	class makes use of the team content providers and a merge context to
-	display a merge preview. Team providers can extend this class in
-	several ways to tailor the preview.</li>
-</ul>
-<p>The <code>ModelSynchronizeParticipant</code> provides integration
-into the Synchronize view or any container that can display <code>ISynchronizePage</code>s.
-The participant makes use of both the pre-existing synchronization
-participant capabilities and the Common Navigator capabilities to allow
-for team providers and models to tailor the toolbar, context menu and
-other aspects of the merge preview. The <code>ModelSynchronizeParticipant</code>
-provides the following:</p>
-<ul>
-	<li>A synchronize page that defines the link between a scope
-	manager, merge context and team content providers.</li>
-	<li>Toolbar actions for displaying direction modes (Incoming,
-	Outgoing, Both and Conflicting modes).</li>
-	<li>Toolbar action for cycling through models involves (i.e. Show
-	All, Show Resources, Show Java, etc).</li>
-	<li>Refresh and scheduled refresh actions.</li>
-	<li>Action to open elements in a compare editor.</li>
-	<li>Change Navigation actions.</li>
-	<li>Standard Merge actions (Merge, Overwrite and MarkasMerged) for
-	which models can register handlers and team providers can provide
-	appropriate labels (e.g. Update for CVS).</li>
-</ul>
-
-<p>Here's a checklist of steps for tailoring a model synchronize
-participant for a particular Team provider:</p>
-<ul>
-	<li>Define the participant using the 
-	<em><a
-	href="../reference/extension-points/org_eclipse_team_ui_synchronizeParticipants.html">org.eclipse.team.ui.synchronizeParticipants</a></em>
-	extension point. This will require team providers to create a subclass
-	of <code>ModelSynchronizeParticipant</code></li>
-	<li>Define a viewer for the participant using the 
-		<em><a
-	href="../reference/extension-points/org_eclipse_ui_navigator_viewer.html">org.eclipse.ui.navigator.viewer</a></em>
-	extension point. The viewer definition is used to specify what menu
-	groups appear in the context menu.</li>
-	<li>Override the <em>initializeConfiguration</em> method of the
-	participant in order to set the <code>ISynchronizePageConfiguration.P_VIEWER_ID</code>
-	to the id of the viewer specified in the previous step.</li>
-	<li>Override the <em>createMergeActionGroup</em> to provide a
-	custom subclass of <code>MergeActionGroup</code> in order to tailor the
-	appearance of the merge related actions.</li>
-	<li>If the participant is persistable, override the <em>createScopeManager</em>
-	and <em>restoreContext</em> methods to recreate the scope manager and
-	merge context for the participant when it is restored on startup.</li>
-	<li>Implement a subclass of <code>ModelParticipantMergeOperation</code>
-	for handling the transition from a model-based merge to a preview in a
-	dialog or Synchronize view.</li>
-</ul>
-<p>The following XML snipets illustrate how the CVS participant class
-is registered and how it's viewer is defined.</p>
-<pre style="background-color: rgb(204, 204, 255);">   &lt;extension point="org.eclipse.team.ui.synchronizeParticipants"&gt;
-      &lt;participant
-            name="CVS"
-            icon="$nl$/icons/full/eview16/cvs_persp.gif"
-            class="org.eclipse.team.internal.ccvs.ui.mappings.WorkspaceModelParticipant"
-            id="org.eclipse.team.cvs.ui.workspace-participant"&gt;
-      &lt;/participant&gt;
-   &lt;/extension&gt;
-   
-   &lt;extension point="org.eclipse.ui.navigator.viewer"&gt;
-       &lt;viewer viewerId="org.eclipse.team.cvs.ui.workspaceSynchronization"&gt;
-           &lt;popupMenu
-                allowsPlatformContributions="false"
-                id="org.eclipse.team.cvs.ui.workspaceSynchronizationMenu"&gt; 
-             &lt;insertionPoint name="file"/&gt;
-             &lt;insertionPoint name="edit" separator="true"/&gt;       
-             &lt;insertionPoint name="synchronize"/&gt;
-             &lt;insertionPoint name="navigate" separator="true"/&gt;
-             &lt;insertionPoint name="update" separator="true"/&gt;
-             &lt;insertionPoint name="commit" separator="false"/&gt;
-             &lt;insertionPoint name="overrideActions" separator="true"/&gt;
-             &lt;insertionPoint name="otherActions1" separator="true"/&gt;
-             &lt;insertionPoint name="otherActions2" separator="true"/&gt;
-             &lt;insertionPoint name="sort" separator="true"/&gt;
-             &lt;insertionPoint name="additions" separator="true"/&gt;             
-             &lt;insertionPoint name="properties" separator="true"/&gt;
-          &lt;/popupMenu&gt;
-       &lt;/viewer&gt;
-   &lt;/extension&gt;
-</pre>
-
-<h2><a name="FileHistory"></a>File History</h2>
-<p>A file history API has been added to allow models to access the
-history of files. The file history API consists of the following
-interfaces:</p>
-<ul>
-	<li><a
-		href="../reference/api/org/eclipse/team/core/history/IFileHistoryProvider.html">IFileHistoryProvider</a>:
-	Obtained from a RepositoryProvider, the file history provider allows
-	clients to obtain the file history of a particular file.</li>
-	<li><a
-		href="../reference/api/org/eclipse/team/core/history/IFileHistory.html">IFileHistory</a>:
-	A data structure that allows access to the history of a file</li>
-	<li><a
-		href="../reference/api/org/eclipse/team/core/history/IFileRevision.html">IFileRevision</a>:
-	The description of a single revision or state of a file at a particular
-	point in time in its history.</li>
-</ul>
-<p>Along with this API, a generic file History view has been added.
-This will allow Team providers to display their file/resource history in
-a shared view and also allows models to display model element history
-for elements that do not map directly to files. The History view is a
-page-based view which obtains a page for the selected element in the
-following way:</p>
-<ul>
-	<li>A history page for workspace resources is obtained by adapting
-	the <code>RepositoryProvider</code> associated with the project that
-	contains the resource to an <a
-		href="../reference/api/org/eclipse/team/ui/history/IHistoryPageSource.html">IHistoryPageSource</a>.
-	</li>
-	<li>A history page for other objects is obtained by adapting the
-	object itself to an <code>IHistoryPageSource</code>.</li>
-</ul>
-
-
-<h2><a name="EFS"></a>Project Set Capability</h2>
-
-<p>Methods have been added to <code><a
-		href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a></code> to
-support the translation between a reference string used to identify a
-mapping between a project and remote content and URIs that identify a
-file-system scheme registered with the 
-	<em><a
-	href="../reference/extension-points/org_eclipse_core_filesystem_filesystems.html">org.eclipse.core.filesystem.filesystems</a></em>
-extension point. Team providers can optionally provide support for this
-in order to allow logical models to performing remote browsing and
-project loading.</p>
-
-<h2><a name="Decoration"></a>Decorating Model Elements</h2>
-
-<p>Team providers can decorate model elements by converting their
-lightweight decorators to work for resource mappings in the same way
-object contributions are converted to work for resource mappings.
-However, there is one aspect of logical model element decoration that is
-problematic. If a model element does not have a one-to-one mapping to a
-resource, the model element may not receive a label update when the
-underlying resources change.</p>
-
-<p>To address this issue, the <code><a
-		href="../reference/api/org/eclipse/team/ui/mapping/ITeamStateProvider.html">ITeamStateProvider</a></code> was introduced in order to give model
-providers access to state changes that may affect team decorations. In addition,
-model views can use a <code><a
-		href="../reference/api/org/eclipse/team/ui/mapping/SynchronizationStateTester.html">SynchronizationStateTester</a></code> to determine when the
-labels of logical model elements need to be updated. This API relies on
-the <code>ITeamStateProvider</code> interface to determine when the team state
-of resource has changed and can be passed to a team decorator as part of an <code><a
-		href="../reference/api/org/eclipse/jface/viewers/IDecorationContext.html">IDecorationContext</a></code>.</p>
-		
-<h2><a name="ChangeGrouping"></a>Grouping Related Changes</h2>
-
-Some logical models need to ensure that a set of changed files get committed or checked-in to the repository at the same time.
-To facilitate this, repository providers can adapt their 
-<code><a href="../reference/api/org/eclipse/team/core/RepositoryProviderType.html">RepositoryProviderType</a></code>
-to an instance of 
-<code><a href="../reference/api/org/eclipse/team/core/mapping/IChangeGroupingRequestor.html">IChangeGroupingRequestor</a></code>.
-This API allows models to request that a set of files get committed or checked-in as a single unit.
-		
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm
deleted file mode 100644
index 2edf102..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_provider_repository.htm
+++ /dev/null

@@ -1,312 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Implementing a repository provider</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Repository providers</h2>
-<p>
-A repository provider (<b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>)
-is the central class in the implementation of your
-repository.&nbsp;This class is responsible for configuring a project
-for repository management and providing the necessary hooks for resource
-modification.&nbsp;Providers are mapped to a project using <a
- href="resInt_properties.htm">project
-persistent properties</a>.&nbsp; The mechanism for mapping providers to
-a project is not central to the team API, but you'll need to be aware of
-it when filtering out resources in your UI.&nbsp; For the most part, you'll be
-using team API to work with projects and associate them with your provider.
-</p>
-<p>
-To implement a provider, you must define a repository using <a
- href="../reference/extension-points/org_eclipse_team_core_repository.html"><b>org.eclipse.team.core.repository</b></a>
-and supply a class derived from&nbsp;<b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.&nbsp;
-We'll use the CVS client as an example to see how this
-works.</p>
-<h3><a name="repository_pt"></a>Extension point</h3>
-<p>
-The <a
- href="../reference/extension-points/org_eclipse_team_core_repository.html">
-<b> org.eclipse.team.core.repository</b></a> extension point is used to
-add a repository definition.&nbsp; Here is the markup for the CVS client.</p>
-<pre>
-&lt;extension
-	point="org.eclipse.team.core.repository"&gt;	
-	&lt;repository
-		class="org.eclipse.team.internal.ccvs.core.CVSTeamProvider"
-		id="org.eclipse.team.cvs.core.cvsprovider"&gt;	
-	&lt;/repository&gt;
-&lt;/extension&gt;
-</pre>
-<p>This registers your team provider with the team support plug-in and
-assigns
-an id that should be used when your provider is associated with a
-project.&nbsp; The specified <b>class</b> for the repository must extend <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.
-</p>
-<h3><a name="repo_impl"></a>Implementing a RepositoryProvider</h3>
-<p>
-The class identified in the extension must be a subclass of <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.
-Its primary responsibilities are to configure and deconfigure a project
-for
-repository support, and supply any necessary resource modification
-hooks.&nbsp;
-The CVS client serves as a good example.&nbsp; Its repository provider
-is <b>CVSTeamProvider</b>.</p>
-
-<pre>public class CVSTeamProvider extends RepositoryProvider {<br>...<br>	</pre>
-<p> <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>
-</b>&nbsp;defines two abstract methods, <b>configureProject</b> and 
-<b>deconfigure</b>.&nbsp;All providers must implement these methods.</p>
-<p>A project is configured
-when it is first associated with a particular repository
-provider.&nbsp;This
-typically happens when the user selects a project and uses the team
-wizards to
-associate a project with your repository.&nbsp;Regardless of how the
-operation
-is triggered, this is
-the appropriate time to compute or cache any data about the project
-that you'll
-need to provide your repository function.&nbsp;(Assume that mapping
-the project
-to your provider has already happened.&nbsp;You'll be taking care of
-this in
-your configuration wizard.)</p>
-<p>The
-CVS provider simply broadcasts the fact that a project has been
-configured:</p>
-<pre>
-public void configureProject() throws CoreException {
-	CVSProviderPlugin.broadcastProjectConfigured(getProject());
-}
-</pre>
-<p>We won't follow the implementation of the plug-in broadcast
-mechanism.&nbsp;Suffice to say that any parties that need to compute
-or initialize project specific data can do so at this time.</p>
-<p>A project is deconfigured when the user no longer wants to associate a team 
-provider with a project.&nbsp;It is up to your plug-in to implement the user
-action that causes this to happen (and unmapping the project from your team
-provider will happen there).&nbsp;The <b>deconfigure</b> method&nbsp;is the
-appropriate time to delete any project related caches or remove any
-references to the project in the UI.&nbsp;The CVS provider flushes project
-related caches kept in its views and broadcasts the fact that the project is
-deconfigured.</p>
-<pre>
-public void deconfigure() throws CoreException {
-	...	
-	try {
-		EclipseSynchronizer.getInstance().flush(getProject(), true, true /*flush deep*/, null);
-	} catch(CVSException e) {
-		throw new CoreException(e.getStatus());
-	} finally {
-		CVSProviderPlugin.broadcastProjectDeconfigured(getProject());
-	}
-}
-</pre>
-<h3> <a name="ui_conf"></a>Configuring a project </h3>
-<p>Typically, the first step in building a team UI is implementing a
-wizard page that allows users to configure a project for your plug-in's team
-support.&nbsp;This is where your team provider's id will be added to
-the project's properties.&nbsp;You participate in project configuration by
-contributing to the <a
- href="../reference/extension-points/org_eclipse_team_ui_configurationWizards.html"><b>org.eclipse.team.ui.configurationWizards</b></a>
-extension point.&nbsp;This wizard is shown when the user chooses 
-<b>Team&nbsp;&gt;&nbsp;Share Project...</b>.
-</p>
-<p>We'll look at this in the context of the CVS client implementation.&nbsp;
-Here is the CVS UI markup for its configuration wizard:
-</p>
-<pre>
-&lt;extension
-	point="org.eclipse.team.ui.configurationWizards"&gt;
-	&lt;wizard
-		name="%SharingWizard.name"
-		icon="icons/full/wizards/newconnect_wiz.png"	
-		class="org.eclipse.team.internal.ccvs.ui.wizards.SharingWizard"
-		id="org.eclipse.team.ccvs.ui.SharingWizard"&gt;
-	&lt;/wizard&gt;
-&lt;/extension&gt;
-</pre>
-<p>As usual, plug-ins supply a <b>class</b> that implements the
-extension and a
-unique <b>id</b> to identify their extension.&nbsp; The <b>name</b>
-and <b>icon</b>
-are shown in the first page of the project configuration wizard if
-there are
-multiple providers to choose from.
-</p>
-<p>Once the user has selected a provider, the next page shows the
-specific
-configuration information for your provider.&nbsp;(If your provider is
-the only
-team provider plug-in installed, then the wizard skips directly to your
-page.)&nbsp;Your wizard must implement <a href="../reference/api/org/eclipse/team/ui/IConfigurationWizard.html"><b>IConfigurationWizard</b></a>,
-which initializes the wizard for a specified workbench and
-project.&nbsp;The rest of the implementation depends on the design of your wizard.
-You must gather up any information needed to associate the project with your
-team support.
-</p>
-<p> When the wizard is completed, you must map your team provider to
-the project
-using <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html#map(org.eclipse.core.resources.IProject, java.lang.String)">RepositoryProvider.map(IProject,
-String)</a></b>.&nbsp;Mapping handles the assignment of the correct
-project persistent property to your project.
-</p>
-<p> The CVS client does this work in its provider's <b>setSharing</b>
-method, which is called when its wizard is finished:
-</p>
-<pre>
-public void setSharing(IProject project, FolderSyncInfo info, IProgressMonitor monitor) throws TeamException {
-
-	// Ensure provided info matches that of the project
-	...
-	// Ensure that the provided location is managed
-	...
-	// Register the project with Team
-	<b>	RepositoryProvider.map(project, CVSProviderPlugin.getTypeId());</b>
-}
-</pre>
-<h3>Finding a provider</h3>
-<p>Static methods in <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b> 
-  make it easy for clients to map projects to providers and to find the providers 
-  associated with a given project. </p>
-<ul>
-  <li><b>map(IProject, String)</b> - instantiates a provider of the
-specified provider id and maps the specified project to it.&nbsp;This
-call sets the proper project persistent property on the project.</li>
-  <li><b>unmap(IProject, String)</b> - removes the association of the
-specified provider id from the specified project.&nbsp;Leaves the
-project unassociated with any team provider.</li>
-  <li><b>getProvider(IProject)</b> - answers the provider for a given
-project.&nbsp;Can be used to find any team provider for a
-project.</li>
-  <li><b>getProvider(IProject, String) </b>- answers the provider for
-a given project with the specified provider id.&nbsp;Can be used to
-check whether a particular team provider type is associated with a
-given project.&nbsp;It is commonly used by providers to quickly check
-whether a given project is under their care.&nbsp;This call is safer
-for clients since it does not return a provider that does not match the
-client's id.</li>
-</ul>
-<h3>Repository Providers and Capabilities</h3>
-<p>
-If a product chooses to add a Repository plug-in to a capability, it
-should bind the capability to the repository id. Here are the two steps
-to take to enable a RepositoryProvider as a capability:
-</p>
-<ol>
-<li>Bind the capability to the repository provider id. This allows the
-Team plug-in to activate/disable based on repository provider ids.<br>
-<pre>
-&lt;activityPatternBinding
-	activityId="org.eclipse.team.cvs"
-	pattern="org\.eclipse\.team\.cvs\.core/.*cvsnature"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>
-</li>
-<li>Next bind the capability to all UI packages for the provider:<br>
-<pre>
-&lt;activityPatternBinding
-	activityId="org.eclipse.team.cvs"
-	pattern="org\.eclipse\.team\.cvs\.ui/.*"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>
-</li>
-</ol>
-<p>
-There are two capability triggers points defined by the Team plug-ins.
-The first is the <span style="font-weight: bold;">Team &gt; Share
-Project...</span> wizard which allows filtering of repository providers
-based on the enabled/disabled state of workbench capabilities, and the
-other is the Team plug-in auto-enablement trigger.</p>
-<h3>Resource modification hooks<a name="hooks"></a></h3>
-<p>Most of the interesting function associated with a repository
-provider occurs as the user works with resources in the project that is
-configured for the provider.&nbsp; In order to be aware of changes the
-user makes to a resource, the provider can implement <a
- href="resAdv_hooks.htm">resource modification hooks</a>.&nbsp;The
-resources plug-in provides these hooks as extension points.&nbsp;The
-documentation for <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>,
-<a
- href="../reference/api/org/eclipse/core/resources/team/FileModificationValidator.html"><b>FileModificationValidator</b></a>
-and <a
- href="../reference/api/org/eclipse/core/resources/team/ResourceRuleFactory.html"><strong>ResourceRuleFactory</strong></a>
-describe the details for implementing these hooks.</p>
-<p>The team plug-in optimizes and simplifies the association of the
-hook with
-appropriate resources by registering generic hooks with the resources
-plug-in.&nbsp; These generic hooks simply look up the repository
-provider for a
-given resource and obtain its hook.&nbsp; This has the advantage of
-calling only
-one provider hook rather than having each provider implementation
-register a
-hook that must first check whether the resource is managed by the
-provider.</p>
-<p>What this means to your plug-in is that you provide any necessary
-hooks by overriding methods in <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>.&nbsp;
-The default implementation of these methods answers null,
-indicating that no hook is necessary (except for the resource rule
-factory, as described below): </p>
-<ul>
-  <li><b>getMoveDeleteHook</b> - answers an <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>
-appropriate for the provider.&nbsp; This hook allows providers to
-control how moves and deletes occur and includes the ability to prevent
-them from happening.&nbsp; Implementors can provide alternate
-implementations for moving or deleting files, folders, and
-projects.&nbsp; The CVS client uses this hook to monitor folder
-deletions and ensure that any files contained in deleted folders are
-remembered so that they can later be deleted from the repository if
-desired.</li>
-  <li><b>getFileModificationValidator2</b> - answers an <a
- href="../reference/api/org/eclipse/core/resources/team/FileModificationValidator.html"><b>FileModificationValidator</b></a>
-appropriate for the provider.&nbsp; This hook allows providers to
-pre-check any modifications or saves to files.&nbsp; This hook is
-typically needed when a repository provider wants to implement <b>pessimistic
-versioning</b>.&nbsp; In pessimistic versioning, a file must be checked
-out before modifying it, and only one client can check out a file at
-any given time.&nbsp; Pessimistic versioning could be implemented by
-checking out a file (if not already checked out) whenever a file is
-edited, and checking the file back in when it is saved. CVS uses
-this hook when using the watch/edit mode, but by default CVS
-uses an optimistic versioning scheme that does not require this hook.</li>
-  <li><strong>getRuleFactory</strong> - answers a resource rule factory
-appropriate for the provider. Providers should always override this
-method as the default factory locks the workspace for all operations
-for backwards compatibility reasons. Provides should subclass <a
- href="../reference/api/org/eclipse/core/resources/team/ResourceRuleFactory.html"><strong>ResourceRuleFactory</strong></a>
-and override those rules required to ensure that the proper rules are
-obtained for operations that invoke the move/delete hook and file
-modification validator. The rule methods of particular interest to
-repository providers are:
-    <ul>
-      <li><em>deleteRule</em> - move/delete hook</li>
-      <li><em>moveRule</em> -move/delete hook</li>
-      <li><em>validateEditRule</em> - file modification validator
-validateEdit</li>
-      <li><em>modifyRule</em> - file modification validator validateSave</li>
-    </ul>
-  </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm
deleted file mode 100644
index fe760bc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources.htm
+++ /dev/null

@@ -1,239 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Repository resource management</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Repository resource management</h2>
-<p>Once you have created a <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>,
-there are other resource management mechanism that should be understood:<br>
-</p>
-<ul>
-  <li>In order to allow other plug-ins to indicate special handling for
-their projects
-and files the team plug-in defines extension points that other
-providers and other plug-ins can use to register <a href="#filetypes">file
-types</a> and to
-declare files that should be <a href="#ignored">ignored </a>by a
-repository provider.</li>
-  <li>Team providers can also register a class that can be used to
-persist
-a <a href="#projectsets">set a projects</a> so that references to the
-project can be shared across
-a team, with the actual contents coming from the repository.</li>
-  <li>Repository providers should consider how they will handle <a
- href="#linked">linked resources</a>.<br>
-  </li>
-  <li>Finally, team providers can mark resources that should be hidden
-from the user as <a href="#teamprivate">team private</a>.<br>
-  </li>
-</ul>
-<h3><a name="ignored"></a>Ignored files</h3>
-<p>In several cases, it may be unnecessary to keep certain files under
-repository control.&nbsp; For example, resources that are derived from
-existing
-resources can often be omitted from the repository.&nbsp; For example,
-compiled
-source files, (such as Java ".class" files), can be omitted since
-their corresponding source (".java") file is in the repository.&nbsp;
-It also may be inappropriate to version control metadata files that are
-generated by repository providers.&nbsp; The <a
- href="../reference/extension-points/org_eclipse_team_core_ignore.html"><b>org.eclipse.team.core.ignore</b></a>
-extension point allows providers to declare file types that should be
-ignored
-for repository provider operations.&nbsp; For example, the CVS client
-declares
-the following:</p>
-<pre>&lt;extension point="org.eclipse.team.core.ignore"&gt;<br>	&lt;ignore pattern = ".#*" selected = "true"/&gt;<br>&lt;/extension&gt;</pre>
-<p>The markup simply declares a file name <b>pattern</b> that should
-be ignored
-and a <b>selected</b> attribute which declares the default selection
-value of
-the file type in the preferences dialog.&nbsp; It is ultimately up to
-the user
-to decide which files should be ignored.&nbsp; The user may select,
-deselect,
-add or delete file types from the default list of ignored files.</p>
-<p><img src="images/ignore.png" alt="" border="0"></p>
-<h3><a name="filetypes"></a>File Types<br>
-</h3>
-<p>Some repositories implement different handling for text vs. binary
-files.&nbsp; The <a
- href="../reference/extension-points/org_eclipse_team_core_fileTypes.html"><b>org.eclipse.team.core.fileTypes</b></a>
-extension allows plug-ins to declare file types as text or binary
-files.&nbsp;
-For example, the Java tooling declares the following:
-</p>
-<pre>&lt;extension point="org.eclipse.team.core.fileTypes"&gt;<br>  &lt;fileTypes extension="java" type="text"/&gt;<br><br>  &lt;fileTypes extension="classpath" type="text"/&gt;<br>  &lt;fileTypes extension="properties" type="text"/&gt;<br>  &lt;fileTypes extension="class" type="binary"/&gt;<br><br>  &lt;fileTypes extension="jar" type="binary"/&gt;<br>  &lt;fileTypes extension="zip" type="binary"/&gt;<br>&lt;/extension&gt;</pre>
-<p>The markup lets plug-ins define a file type by <b>extension</b> and
-assign a <b>type</b>
-of text or binary.&nbsp; As with ignored files, it is ultimately up to
-the user
-to manage the list of text and binary file types.
-</p>
-<p><img src="images/filetypes.png" alt="" border="0"> 
-</p>
-<h3><a name="linked"></a>Team and linked resources</h3>
-<p>A project may contain resources that are not located within the
-project's directory in the local file system. These resources are
-referred to as <a href="resInt_linked.htm">linked resources</a>. </p>
-<h4>Consequences for Repository Providers</h4>
-<p>Linked resources can pose particular challenges for repository
-providers which operate directly against the file system. This is a
-consequence of the fact that linked resources by design do not exist in
-the immediate project directory tree in the file system. </p>
-<p>Providers which exhibit the following characteristics may be
-affected by linked resources:</p>
-<ol>
-  <li>Those which call out to an external program that then operates
-directly against the file system.</li>
-  <li>Those which are implemented in terms of IResource but assume that
-all the files/folders in a project exist as direct descendents of that
-single rooted directory tree.</li>
-</ol>
-<p>In the first case, lets assume the user picks a linked resource and
-tries to perform a provider operation on it. Since the provider calls a
-command line client, we can assume that the provider does something
-equivalent to first calling <a
- href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.getLocation().toOSString(),
-feeding the resulting file system location as an argument to the
-command line program. If the resource in question is a linked resource,
-this will yield a file/folder outside of the project directory tree.
-Not all command line clients may expect and be able to handle this
-case. In short, if your provider ever gets the file system location of
-a resource, it will likely require extra work to handle linked
-resources. </p>
-<p>The second case is quite similar in that there is an implicit
-assumption that the structure of the project resources is 1:1 with that
-of the file system files/folders. In general, a provider could be in
-trouble if they mix IResource and java.io.File operations. For example,
-for links, the parent of <a
- href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-is not the same as the java.io.File's parent and code which assumes
-these to be the same will fail.
-</p>
-<h4>Backwards Compatibility</h4>
-<p>It was important that the introduction of linked resources did not inadvertently 
-  break existing providers. Specifically, the concern was for providers that reasonably 
-  assumed that the local file system structure mirrored the project structure. 
-  Consequently, by default linked resources can not be added to projects that 
-  are mapped to such a provider. Additionally, projects that contain linked resources 
-  can not by default be shared with that provider.</p>
-<h4>Strategies for Handling Linked Resources</h4>
-<p>In order to be "link friendly", a provider should allow projects
-with linked resources to be version controlled, but can disallow the
-version controlling of linked resources themselves. </p>
-<p>A considerably more complex solution would be to allow the
-versioning of the actual linked resources, but this should be
-discouraged since it brings with it complex scenarios (e.g. the file
-may already be version controlled under a different project tree by
-another provider). Our recommendation therefore is to support version
-controlled projects which contain non-version controlled linked
-resources.</p>
-<h4>Technical Details for Being "Link Friendly"</h4>
-<p>Repository provider implementations can be upgraded to support
-linked resources by overriding the <b><a
- href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>.canHandleLinkedResources()</b>
-method to return <strong>true</strong>. Once this is done, linked
-resources will be allowed to exist in projects shared with that
-repository provider. However, the repository provider must take steps
-to ensure that linked resources are handled properly. As mentioned
-above, it is strongly suggested that repository providers ignore all
-linked resources. This means that linked resources (and their children)
-should be excluded from the actions supported by the repository
-provider. Furthermore, the repository provider should use the default
-move and delete behavior for linked resources if the repository
-provider implementation overrides the default <a
- href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>.</p>
-<p>Team providers can use <a
- href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>isLinked()
-</b>to determine if a resource is a link. However, this method only
-returns true for the root of a link. The following code segment can be
-used to determine if a resource is the child of a link.</p>
-<pre>String linkedParentName = resource.getProjectRelativePath().segment(0);<br>IFolder linkedParent = resource.getProject().getFolder(linkedParentName);<br>boolean isLinked = linkedParent.isLinked();</pre>
-<p>Repository providers should ignore any resource for which the above
-code evaluates to <strong>true</strong>.</p>
-<h3><a name="teamprivate"></a>Team private resources</h3>
-<p>It is common for repository implementations to use extra files and
-folders to
-store information specific about the repository implementation.&nbsp;
-Although
-these files may be needed in the workspace, they are of no interest to
-other
-plug-ins or to the end user.</p>
-<p>Team providers may use <a
- href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>setTeamPrivateMember(boolean)
-</b>to indicate that a resource is private to the implementation of a
-team
-provider. Newly created resources are not private members by default,
-so this
-method must be used to explicitly mark the resource as team
-private.&nbsp; A
-common use is to mark a subfolder of the project as team private when
-the
-project is configured for team and the subfolder is created.</p>
-<p>Other resource API that enumerates resources (such as resource delta
-trees)
-will exclude team private members unless explicitly requested to
-include
-them.&nbsp; This means that most clients will not "see" the team
-private resources and they will not be shown to the user.&nbsp; The
-resource
-navigator does not show team private members by default, but users can
-indicate
-via Preferences that they would like to see team private resources.</p>
-<p>Attempts to mark projects or the workspace root as team private will
-be
-ignored.</p>
-<h3><a name="projectsets"></a>Project sets</h3>
-<p>Since the resources inside a project under version control are kept
-in the
-repository, it is possible to share projects with team members by
-sharing a
-reference to the repository specific information needed to reconstruct
-a project
-in the workspace.&nbsp; This is done using a special type of file
-export for <b>team
-project sets</b>.&nbsp;&nbsp;</p>
-<p><img  border="0" alt=""
- src="images/projectset.png"></p>
-<p>&nbsp;</p>
-<p>In 3.0, API was added to <a
- href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a>
-to allow repository providers to declare a class that implements
-project saving for projects under their control.&nbsp; When the user
-chooses to export project sets, only the projects configured with
-repositories that define project sets are shown as candidates for
-export. This API replaces the old project set serialization API (see
-below). </p>
-<p>The project set capability class for a repository provider is obtained from 
-  the <a
- href="../reference/api/org/eclipse/team/core/RepositoryProviderType.html">RepositoryProviderType</a> 
-  class which is registered in the same extension as the repository provider. 
-  For example:</p>
-<pre>&lt;extension point="org.eclipse.team.core.repository"&gt;<br>    &lt;repository<br>          typeClass="org.eclipse.team.internal.ccvs.core.CVSTeamProviderType"<br><br>          class="org.eclipse.team.internal.ccvs.core.CVSTeamProvider"<br>          id="org.eclipse.team.cvs.core.cvsnature"&gt;<br>    &lt;/repository&gt;<br>&lt;/extension&gt;</pre>
-<p>Prior to 3.0, The <a
- href="../reference/extension-points/org_eclipse_team_core_projectSets.html"><b>org.eclipse.team.core.projectSets</b></a>
-extension point allowed repository providers to declare a class that
-implements project saving for projects under their control.&nbsp; When
-the user chooses to export project sets, only the projects configured
-with repositories that define project sets are shown as candidates for
-export.</p>
-<p>For example, the CVS client declares the following:</p>
-<pre>&lt;extension point="org.eclipse.team.core.projectSets"&gt;<br>	&lt;projectSets id="org.eclipse.team.cvs.core.cvsnature" class="org.eclipse.team.internal.ccvs.ui.CVSProjectSetSerializer"/&gt;<br>&lt;/extension&gt;</pre>
-<p>The specified class must implement <a
- href="../reference/api/org/eclipse/team/core/IProjectSetSerializer.html"><b>IProjectSetSerializer</b></a>.
-Use of this interface is still supported in 3.0 but has been deprecated.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm
deleted file mode 100644
index b86f7f4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_filetypes.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>File types</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>File types</h3>
-<p>The presence of a repository management system may dictate special handling
-needs for files.&nbsp; For example, some files should be omitted from version
-control.&nbsp; Some providers have special handling for text vs. binary
-files.&nbsp; The team plug-in defines extension points that allow other plug-ins
-to provide information about their file types.&nbsp; In all cases, special
-handling is ultimately left up to the user via the team Preferences page.&nbsp;
-These extensions allow plug-ins to seed the preferences with values appropriate
-for the plug-in.</p>
-<h4>Ignored files</h4>
-<p>In several cases, it may be unnecessary to keep certain files under
-repository control.&nbsp; For example, resources that are derived from existing
-resources can often be omitted from the repository.&nbsp; For example, compiled
-source files, (such as Java &quot;.class&quot; files), can be omitted since
-their corresponding source (&quot;.java&quot;) file is in the repository.&nbsp;
-It also may be inappropriate to version control metadata files that are
-generated by repository providers.&nbsp; The <a href="../reference/extension-points/org_eclipse_team_core_ignore.html"><b>org.eclipse.team.core.ignore</b></a>
-extension point allows providers to declare file types that should be ignored
-for repository provider operations.&nbsp; For example, the CVS client declares
-the following:</p>
-<pre>&lt;extension point=&quot;org.eclipse.team.core.ignore&quot;&gt;
-	&lt;ignore pattern = &quot;.#*&quot; selected = &quot;true&quot;/&gt;
-&lt;/extension&gt;</pre>
-<p>The markup simply declares a file name <b>pattern</b> that should be ignored
-and a <b>selected</b> attribute which declares the default selection value of
-the file type in the preferences dialog.&nbsp; It is ultimately up to the user
-to decide which files should be ignored.&nbsp; The user may select, deselect,
-add or delete file types from the default list of ignored files.</p>
-<p><img src="images/ignore.png" alt="" border="0" ></p>
-<h4>Text vs. binary files</h4>
-<p>Some repositories implement different handling for text vs. binary
-files.&nbsp; The <a href="../reference/extension-points/org_eclipse_team_core_fileTypes.html"><b>org.eclipse.team.core.fileTypes</b></a>
-extension allows plug-ins to declare file types as text or binary files.&nbsp;
-For example, the Java tooling declares the following:
-</p>
-
-<pre>&lt;extension point=&quot;org.eclipse.team.core.fileTypes&quot;&gt;
-  &lt;fileTypes extension=&quot;java&quot; type=&quot;text&quot;/&gt;
-  &lt;fileTypes extension=&quot;classpath&quot; type=&quot;text&quot;/&gt;
-  &lt;fileTypes extension=&quot;properties&quot; type=&quot;text&quot;/&gt;
-  &lt;fileTypes extension=&quot;class&quot; type=&quot;binary&quot;/&gt;
-  &lt;fileTypes extension=&quot;jar&quot; type=&quot;binary&quot;/&gt;
-  &lt;fileTypes extension=&quot;zip&quot; type=&quot;binary&quot;/&gt;
-&lt;/extension&gt; </pre>
-
-<p>The markup lets plug-ins define a file type by <b>extension</b> and assign a <b>type</b>
-of text or binary.&nbsp; As with ignored files, it is ultimately up to the user
-to manage the list of text and binary file types.
-</p>
-
-
-
-
-<p><img src="images/filetypes.png" alt="" border="0" >
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm
deleted file mode 100644
index b02f736..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_linked.htm
+++ /dev/null

@@ -1,86 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Team and linked resources</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Team and linked resources</h3>
-<p>A project may contain resources that are not located within the project's directory 
-  in the local file system. These resources are referred to as <a href="resInt_linked.htm">linked 
-  resources</a>. </p>
-<h4>Consequences for Repository Providers</h4>
-<p>Linked resources can pose particular challenges for repository providers which 
-  operate directly against the file system. This is a consequence of the fact 
-  that linked resources by design do not exist in the immediate project directory 
-  tree in the file system. </p>
-<p>Providers which exhibit the following characteristics may be affected by linked 
-  resources:</p>
-<ol>
-  <li>Those which call out to an external program that then operates directly 
-    against the file system.</li>
-  <li>Those which are implemented in terms of IResource but assume that all the 
-    files/folders in a project exist as direct descendents of that single rooted 
-    directory tree.</li>
-</ol>
-<p>In the first case, lets assume the user picks a linked resource and tries to perform
-  a provider operation on it.  Since the provider calls a command line client, we can assume that
-  the provider does something equivalent to first calling
-   <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.getLocation().toOSString(),
-  feeding the resulting file system location as an argument to the command line program.  If the resource in question is
-  a linked resource, this will yield a file/folder outside of the project directory tree.  Not all
-  command line clients may expect and be able to handle this case.
-  In short, if your provider ever gets the file system location of a resource, it will likely require
-  extra work to handle linked resources.  
-</p>
-<p>The second case is quite similar in that there is an implicit assumption that the structure of
-  the project resources is 1:1 with that of the file system files/folders.  In general,
-  a provider could be in trouble if they mix IResource and java.io.File operations. 
-  For example, for links, the parent of 
-  <a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-  is not the same
-  as the java.io.File's parent and code which assumes these to be the same will fail.
-</p>
-<h4>Backwards Compatibility</h4>
-<p>It was important that the introduction of linked resources did not inadvertently 
-  break existing providers. Specifically, the concern was for providers that reasonably 
-  assumed that the local file system structure mirrored the project structure. 
-  Consequently, by default linked resources can not be added to projects that 
-  are mapped to such a provider. Additionally, projects that contain linked resources 
-  can not by default be shared with that provider.</p>
-<h4>Strategies for Handling Linked Resources</h4>
-<p>In order to be &quot;link friendly&quot;, a provider should allow projects 
-  with linked resources to be version controlled, but can disallow the version 
-  controlling of linked resources themselves. </p>
-<p>A considerably more complex solution would be to allow the versioning of the 
-  actual linked resources, but this should be discouraged since it brings with 
-  it complex scenarios (e.g. the file may already be version controlled under 
-  a different project tree by another provider). Our recommendation therefore 
-  is to support version controlled projects which contain non-version controlled 
-  linked resources.</p>
-<h4>Technical Details for Being &quot;Link Friendly&quot;</h4>
-<p>Repository provider implementations can be upgraded to support linked resources 
-  by overriding the <b><a href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a>.canHandleLinkedResourceURI()</b> 
-  method to return <strong>true</strong>. Once this is done, linked resources 
-  will be allowed to exist in projects shared with that repository provider. However, 
-  the repository provider must take steps to ensure that linked resources are 
-  handled properly. As mentioned above, it is strongly suggested that repository 
-  providers ignore all linked resources. This means that linked resources (and 
-  their children) should be excluded from the actions supported by the repository 
-  provider. Furthermore, the repository provider should use the default move and 
-  delete behavior for linked resources if the repository provider implementation 
-  overrides the default <a href="../reference/api/org/eclipse/core/resources/team/IMoveDeleteHook.html"><b>IMoveDeleteHook</b></a>.</p>
-<p>Team providers can use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>isLinked(IResource.CHECK_ANCESTORS) 
-  </b>to determine if a resource is a link or is the descendant of a link.</p>
-<p>Repository providers should ignore any resource for which the above code evaluates 
-  to <strong>true</strong>.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm
deleted file mode 100644
index e9e8d17..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_private.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Team private resources</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Team private resources</h3>
-<p>It is common for repository implementations to use extra files and folders to
-store information specific about the repository implementation.&nbsp; Although
-these files may be needed in the workspace, they are of no interest to other
-plug-ins or to the end user.</p>
-<p>Team providers may use <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>.<b>setTeamPrivateMember(boolean)
-</b>to indicate that a resource is private to the implementation of a team
-provider. Newly created resources are not private members by default, so this
-method must be used to explicitly mark the resource as team private.&nbsp; A
-common use is to mark a subfolder of the project as team private when the
-project is configured for team and the subfolder is created.</p>
-<p>Other resource API that enumerates resources (such as resource delta trees)
-will exclude team private members unless explicitly requested to include
-them.&nbsp; This means that most clients will not &quot;see&quot; the team
-private resources and they will not be shown to the user.&nbsp; The resource
-navigator does not show team private members by default, but users can indicate
-via Preferences that they would like to see team private resources.</p>
-<p>Attempts to mark projects or the workspace root as team private will be
-ignored.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm
deleted file mode 100644
index e5ad5a6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_resources_projects.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Project sets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Project sets</h3>
-<p>Since the resources inside a project under version control are kept in the
-repository, it is possible to share projects with team members by sharing a
-reference to the repository specific information needed to reconstruct a project
-in the workspace.&nbsp; This is done using a special type of file export for <b>team
-project sets</b>.&nbsp;&nbsp;</p>
-<p><img src="images/projectset.png" alt="" border="0" ></p>
-<p>&nbsp;</p>
-<p>In 3.0, API was added to <a href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">ProjectSetCapability</a> 
-  to allow repository providers to declare a class that implements project saving 
-  for projects under their control.&nbsp; When the user chooses to export project 
-  sets, only the projects configured with repositories that define project sets 
-  are shown as candidates for export. This API replaces the old project set serialization 
-  API (see below). </p>
-<p>The project set capability class for a repository provider is obtained from 
-  the <a href="../reference/api/org/eclipse/team/core/ProjectSetCapability.html">RepositoryProviderType</a> 
-  class which is registered in the same extension as the repository provider. 
-  For example:</p>
-<pre>&lt;extension point="org.eclipse.team.core.repository"&gt;
-    &lt;repository
-          typeClass=&quot;org.eclipse.team.internal.ccvs.core.CVSTeamProviderType&quot;
-          class=&quot;org.eclipse.team.internal.ccvs.core.CVSTeamProvider&quot;
-          id=&quot;org.eclipse.team.cvs.core.cvsnature&quot;&gt;
-    &lt;/repository&gt;
-&lt;/extension&gt;</pre>
-<p>Prior to 3.0, The <a href="../reference/extension-points/org_eclipse_team_core_projectSets.html"><b>org.eclipse.team.core.projectSets</b></a> 
-  extension point allowed repository providers to declare a class that implements 
-  project saving for projects under their control.&nbsp; When the user chooses 
-  to export project sets, only the projects configured with repositories that 
-  define project sets are shown as candidates for export.</p>
-<p>For example, the CVS client declares the following:</p>
-<pre>&lt;extension point=&quot;org.eclipse.team.core.projectSets&quot;&gt;
-	&lt;projectSets id=&quot;org.eclipse.team.cvs.core.cvsnature&quot; class=&quot;org.eclipse.team.internal.ccvs.ui.CVSProjectSetSerializer&quot;/&gt;
-&lt;/extension&gt;</pre>
-<p>The specified class must implement <a href="../reference/api/org/eclipse/team/core/IProjectSetSerializer.html"><b>IProjectSetSerializer</b></a>. 
-  Use of this interface is still supported in 3.0 but has been deprecated.</p>
-<p>&nbsp;
-   
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm
deleted file mode 100644
index 011e64f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize.htm
+++ /dev/null

@@ -1,229 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Synchronization Support</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Synchronization Support</h2>
-<p>Eclipse includes APIs for managing and displaying synchronization state 
-  between workspace resources and resources in another location. We refer to a 
-  resource outside of the workspace as a variant. Synchronizing is the act of 
-  displaying the changes between resources in different locations and optionally 
-  allowing the user to affect the synchronization state by performing an action. 
-  The synchronize APIs are orthogonal to the RepositoryProvider APIs and can be 
-  used without a repository provider. The purpose of the synchronization API is 
-  to ease the task of implementing different ways of presenting the synchronization 
-  state of resources. As such, the API requires a means to query the synchronization 
-  state of resources but does not require a means to affect the state. The means 
-  of affecting the state is left to the implementer (although the UI does provide 
-  hooks for adding provider specific menu items to menus).</p>
-<h3>Terminology </h3>
-<p>Before the synchronization API is described, it is helpful to
-present some of the terminology and concepts that apply when discussing
-workspace synchronization.</p>
-<blockquote>
-  <p><em>Resource Variant</em>: A local resource that is mapped to a resource 
-    that exists at another location can be referred to as a variant of that resource. 
-    That is, the resources are usually very similar but may differ slightly (either 
-    due to modifications to the local resource or changes made the remote copy 
-    by other users). We take a local workspace centric view of this, referring 
-    to the local copy as the resource and any remote copy as resource variants.</p>
-  <p><em>Synchronize</em>: We refer to synchronize as the action of displaying 
-    to the user the differences between resource variants. Synchronizing doesn't 
-    affect the state of the variants, but instead provides a view to help the 
-    user understand the differences between different sets of variants. It is 
-    common however to allow users to affect the states of the variants (e.g. allowing 
-    to check-in, or revert) while synchronizing.</p>
-  <p><em>Two-way vs. Three-way Synchronization</em>: There are two basic types 
-    of synchronization state determination: two-way and three-way. A two-way comparison 
-    only considers the local resource and a single resource variant, referred 
-    to as the remote resource variant. This type of comparison can only show the 
-    differences between the two resources but cannot offer hints as to how the 
-    changes interrelate. Most code repository systems support a three-way comparison 
-    for synchronization state determination. This type of comparison involves 
-    the local resource, a remote resource variant and a base resource variant. 
-    The base resource variant represents a common ancestor for the local and remote 
-    resources. This allows for more sophisticated synchronization states that 
-    indicate the direction of the change.<br>
-  </p>
-  <p>Table 1: The synchronization states<br>
-  </p>
-  <table style="text-align: left; width: 90%;" border="1"
- cellspacing="2" cellpadding="2">
-    <tbody>
-      <tr>
-        <td style="vertical-align: top;"><span
- style="font-weight: bold;">Two-Way</span></td>
-        <td style="vertical-align: top;"><span
- style="font-weight: bold;">Three-Way</span></td>
-      </tr>
-      <tr>
-        <td style="vertical-align: top;">Changed<br>
-Deleted<br>
-Added</td>
-        <td style="vertical-align: top;">Outgoing Change<br>
-Incoming Change<br>
-Outgoing Deletion<br>
-Incoming Deletion<br>
-Outgoing Addition<br>
-Incoming Addition<br>
-Conflicting Change<br>
-Conflicting Deletion<br>
-Conflicting Addition</td>
-      </tr>
-    </tbody>
-  </table>
-</blockquote>
-<h3>The Basics - SyncInfo</h3>
-<p>
-The classes in the <a
- href="../reference/api/org/eclipse/team/core/synchronize/package-summary.html">org.eclipse.team.core.synchronize</a>
-are used to describe the synchronization state. The most important
-class is <a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo</a>
-because it is the class that actually defines the synchronization
-state. It can be used as follows:
-</p>
-<pre><span style="color: rgb(68, 68, 204);">SyncInfo info = getSyncInfo(resource); // this is a simulated method of obtaining the sync info for a resource<br>int changekind = info.getKind();<br>if(info.getResourceComparator().isThreeWay()) {<br>  if((changeKind &amp; SyncInfo.DIRECTION_MASK) == SyncInfo.INCOMING) {<br>    // do something<br>  }<br>} else if(changeKind == SyncInfo.CHANGE) {<br>    // do something else<br>}</span></pre>
-<p>
-The SyncInfo class provides both the two-way and three-way comparison algorithms, 
-a client must provide the resources and a class that can compare the resources 
-(<a
- href="../reference/api/org/eclipse/team/core/variants/IResourceVariantComparator.html">IResourceVariantComparator</a>). 
-Here is an example variant comparator:
-</p>
-<pre style="color: rgb(68, 68, 204);">public class TimestampVariantComparator implements IResourceVariantComparator {	<br>  protected boolean compare(IResourceVariant e1, IResourceVariant e2) {<br>    if(e1.isContainer()) {<br>      if(e2.isContainer()) {<br>        return true;<br>      }<br>      return false;<br>    }<br>    if(e1 instanceof MyResourceVariant &amp;&amp; e2 instanceof MyResourceVariant) {<br>      MyResourceVariant myE1 = (MyResourceVariant)e1; <br>      MyResourceVariant myE2 = (MyResourceVariant)e2; <br>      return myE1.getTimestamp().equals(myE2.getTimestamp());<br>    }<br>    return false;<br>  }<br>  protected boolean compare(IResource e1, IResourceVariant e2) {<br>      <br>  }<br>  public boolean isThreeWay() {<br>    return true;<br>  }<br>}<br><br>SyncInfo info = new SyncInfo(resource, variant1, variant2, new TimestampComparator());<br>info.init(); // calculate the sync info</pre>
-<p>This package also contains collections specifically designed to contain
-SyncInfo and filters that can be applied to SyncInfo instances.
-</p>
-<h3>Managing the synchronization state</h3>
-<p>
-As we have seen in the examples above, <a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo
-</a>and
-<a
- href="../reference/api/org/eclipse/team/core/variants/IResourceVariantComparator.html">IResourceVariantComparator</a>
- classes provide access to the
-synchronization state of resources. But what we haven't seen yet is how
-the state is managed. A <a
- href="../reference/api/org/eclipse/team/core/subscribers/Subscriber.html">Subscriber</a>
-provides access to the synchronization state between the resources in
-the local workspace and a set of resource variants for these resources
-using either a two-way or three-way comparison, depending on the nature
-of the subscriber. A subscriber provides the following capabilities:
-</p>
-
-<ul>
-  <li><span style="font-weight: bold;">local workspace traversal</span>: a subscriber 
-    supports the traversal of the local workspace resources that are <em>supervised</em> 
-    by the subscriber. As such, the subscriber has a set of <em>root</em> resources 
-    that define the workspace subtrees under the subscriber's control, as well 
-    as a <em>members</em> method that returns the supervised members of a workspace 
-    resource. This traversal differs from the usual workspace resource traversal 
-    in that the resources being traversed may include resources that do not exist 
-    locally, either because they have been deleted by the user locally or created 
-    by a 3rd party. <br>
-  </li>
-  <li><span style="font-weight: bold;">resource synchronization state determination</span>: 
-    For supervised resources, the subscriber provides access to the synchronization 
-    state of the resource, including access to the variants of the resource. For 
-    each supervised resource, the subscriber provides a <em>SyncInfo</em> object 
-    that contains the synchronization state and the <em>variants</em> used to 
-    determine the state.The subscriber also provides an <em>IResourceVariantComparator</em> 
-    which determines whether two-way or three-way comparison is to be used and 
-    provides the logic used by the SyncInfo to comparing resource variants when 
-    determining the synchronization state. <br>
-  </li>
-  <li><span style="font-weight: bold;">refresh of synchronization state and change 
-    notification</span>: Clients can react to changes that happen to local resources 
-    by listening to the Core resource deltas. When a local resource is changed, 
-    the synchronization state of the resource can then be re-obtained from the 
-    subscriber. However, clients must explicitly query the server to know if there 
-    are changes to the resource variants. For subscribers, this process is broken 
-    up into two parts. A client can explicitly <em>refresh</em> a subscriber. 
-    In response the subscriber will obtain the latest state of the resource variants 
-    from the remote location and fire <em>synchronization state change</em> events 
-    for any resource variants that have changed. The change notification is separate 
-    from the refresh since there may be other operations that contact the remote 
-    location and obtain the latest remote state.&nbsp;</li>
-</ul>
-<p> The APIs do not not define how a Subscriber is created, this is left to the 
-  specific implementations. For example the CVS plug-in creates a Subscriber when 
-  a merge is performed, another for a comparison, and another when synchronizing 
-  the local workspace with the current branch. </p>
-<p>
-So let's revisit our first example of using SyncInfo and see how a
-Subscriber could be used to access SyncInfo.</p>
-
-<pre><span style="color: rgb(68, 68, 204);">// Create a file system subscriber and specify that the<br>// subscriber will synchronize with the provided file system location<br>Subscriber subscriber = new FileSystemSubscriber("c:\temp\repo");<br><br>// Allow the subscriber to refresh its state<br>subscriber.refresh(subscriber.roots(), IResource.DEPTH_INFINITE, monitor);<br><br>// Collect all the synchronization states and print<br>IResource[] children = subscriber.roots();<br>for(int i=0; i &lt; children.length; i++) {<br>  printSyncState(children[i]);<br>}<br><br>...<br><br>void printSyncState(Subscriber subscriber, IResource resource) {<br>  System.out.println(subscriber.getSyncInfo(resource).toString());<br></span><span
- style="color: rgb(68, 68, 204);"><span style="color: rgb(68, 68, 204);">  IResource[] children = subscriber.members(resource);<br>  for(int i=0; i &lt; children.length; i++) {<br>    IResource child = children[i];<br>    if(! child.exists()) {<br>      System.out.println(resource.getFullPath() + " doesn't exist in the workspace");<br>    }<br>    printSyncState(subscriber, children[i]);<br>  }<br>}<br></span></span></pre>
-<p>
-The important point to remember is that the Subscriber knows about
-resources that do not exist in the workspace and non-existing resources
-can be returned from the <a
- href="../reference/api/org/eclipse/team/core/subscribers/Subscriber.html#members(org.eclipse.core.resources.IResource)">Subscriber#members()</a>
-and <a
- href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html#getLocal()">SyncInfo#getLocal()</a>.
- </p>
-<h3>Displaying the synchronizations state in the UI</h3>
-<p>
-We could spend more time explaining how to manage synchronization state
-but instead let's see how to actually get the state shown to the user.
-A <a
- href="../reference/api/org/eclipse/team/ui/synchronize/ISynchronizeParticipant.html">ISynchronizeParticipant
-</a>is the user interface component that displays synchronization state
-and allows the user to affect its state. The Synchronize View displays
-synchronize participants, but it is also possible to show these in
-dialogs and wizards. In order to provide support for users to show any
-type of synchronization state to the user, even those not based on
-SyncInfo and Subscribers, a participant is a very generic component.</p>
-<p>
-There is also an extension point called <a
- href="../reference/extension-points/org_eclipse_team_ui_synchronizeWizards.html">org.eclipse.team.ui.synchronizeWizards</a>
-to add a synchronization creation wizard. This will put your wizard in
-the global synchronize action and in the Synchronize View, so that
-users can easily create a synchronization of your type.
-</p>
-<p>
-However, if you have implemented a Subscriber you can benefit from a
-concrete participant called <a
- href="../reference/api/org/eclipse/team/ui/synchronize/SubscriberParticipant.html">SubscriberParticipant
-</a>which will provide
-the following functionality:
-</p>
-
-<ul>
-  <li>Collects SyncInfo from a Subscriber in the background.</li>
-  <li>Listens to changes in the workspace and those found when a
-Subscriber is refreshed and keeps the synchronization state updated
-dynamically.</li>
-  <li>Provides the user interface that support modes for filtering the
-changes, and layouts.</li>
-  <li>Support scheduling a refresh with the Subscriber so that the
-synchronization states are kept up-to-date.</li>
-  <li>Supports refreshing a Subscriber in the background.</li>
-  <li>Supports navigation of the changes and showing the differences
-between the files.</li>
-  <li>Supports configuration of the actions, toolbars, and decorators
-by subclasses.<br>
-  </li>
-</ul>
-<p>The best way to explain these concepts are to see them used in the context 
-  of a simple example. Go to the <a
- href="team_synchronize_localhistory_example.htm">local history synchronization</a> 
-  example to see how all of these pieces can be used together. Or if you want 
-  pointers on how to use the more advanced APIs, go to <a
- href="team_synchronize_beyond_basics.htm">Beyond The Basics</a>.<br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm
deleted file mode 100644
index 1db8a01..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_beyond_basics.htm
+++ /dev/null

@@ -1,177 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Synchronization Support - Beyond the basics</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Beyond the Basics</h2>
-<p>If you plan on providing synchronization support and don't have an existing 
-  mechanism for managing synchronization state, this section explains how to implementing 
-  a Subscriber from scratch. This means that there is no existing synchronization 
-  infrastructure and illustrates how to use some API that is provided to maintain 
-  the synchronization state.<br>
-</p>
-<p>For the remainder of this example we will make use of a running
-example. The source code can be found in the file system provider
-package of the <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a>
-plug-in. You should check the project out from the CVS repository and
-use as a reference while you are reading this tutorial. </p>
-<h3>Implementing a Subscriber From Scratch</h3>
-<p>This first example assumes that there is no existing infrastructure for maintaining 
-  the synchronization state of the local workspace. When implementing a subscriber 
-  from scratch, you can make use of some additional API provided in the <em>org.eclipse.team.core</em> 
-  plug-in. The <a
- href="../reference/api/org/eclipse/team/core/variants/package-summary.html">org.eclipse.team.core.variants</a> 
-  package contains two subclasses of <a
- href="../reference/api/org/eclipse/team/core/subscribers/Subscriber.html">Subscriber 
-  </a>which can be used to simplify implementation. The first is <a
- href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber 
-  </a>which will be discussed in the second example below. The second is a subclass 
-  of the first: <a
- href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a>. 
-  This subscriber implementation provides several helpful classes for managing 
-  the synchronization state of a local workspace. If you do not have any existing 
-  infrastructure, this is a good place to start. </p>
-<p>Implementing a subscriber from scratch will be illustrated using the file system 
-  example available in the <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a> 
-  plug-in. The code in the following description is kept to a minimum since it 
-  is available from the Eclipse CVS repository. Although not technically a three-way 
-  subscriber, the file system example can still make good use of this infrastructure. 
-  The FTP and WebDAV plug-ins also are built using this infrastructure.</p>
-<h3>ThreeWaySubscriber</h3>
-<p>For the file system example, we already had an implementation of a <a href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider 
-  </a>that associated a local project with a file system location where the local 
-  contents were mirrored. FileSystemSubscriber was created as a subclass of <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a> 
-  in order to make use of a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-  to manage workspace synchronization state. Subclasses of this class must do 
-  the following:</p>
-<ul>
-  <li>create a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-    instance to manage the local workspace synchronization state.</li>
-  <li>create an instance of a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWayRemoteTree.html">ThreeWayRemoteTree</a> 
-    subclass to provide remote tree refresh. 
-  <ul>
-    <li>The class FileSystemRemoteTree was defined for this
-purpose</li>
-  </ul></li>
-  <li>implement a method to create the resource variant handles used to
-calculate the synchronization state.
-    <ul>
-      <li>The class FileSystemResourceVariant (a subclass of <a href="../reference/api/org/eclipse/team/core/variants/CachedResourceVariant.html">CachedResourceVariant</a>) 
-        was defined for this</li>
-    </ul>
-  </li>
-  <li>implement the roots method
-    <ul>
-      <li>The roots for the subscriber are all the projects mapped to
-the FileSystemProvider. Callbacks were added to FileSystemProvider
-in order to allow the FileSystemSubscriber to generate change
-events when projects are mapped and unmapped.</li>
-    </ul>
-  </li>
-</ul>
-<p>In addition to the subscriber implementation, the get and put
-operations for the file system provider were modified to update the
-synchronization state in the ThreeWaySynchronizer. The
-operations are implemented in the class
-org.eclipse.team.examples.filesystem.FileSystemOperations.</p>
-<h3>ThreeWaySynchronizer</h3>
-<p><a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-  manages the synchronization state between the local workspace and a remote location. 
-  It caches and persists the local, base and remote timestamps in order to support 
-  the efficient calculation of the synchronization state of a resource. It also 
-  fires change notifications to any registered listeners. The <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a> 
-  translates these change events into the proper format to be sent to listeners 
-  registered with the subscriber.</p>
-<p>The <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a> 
-  makes use of Core scheduling rules and locks to ensure thread safety and provide 
-  change notification batching.</p>
-<h3>ThreeWayRemoteTree</h3>
-<p>A <a href="../reference/api/org/eclipse/team/core/variants/ThreeWayRemoteTree.html">ThreeWayRemoteTree</a> 
-  is a subclass of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-  that is tailored to the <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a>. 
-  It must be overridden by clients to provide the mechanism for fetching the remote 
-  state from the server. <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-  is discussed in more detail in the next example.</p>
-<h3>CachedResourceVariant</h3>
-<p>A <a href="../reference/api/org/eclipse/team/core/variants/CachedResourceVariant.html">CachedResourceVariant</a> 
-  is a partial implementation of IResourceVariant that caches any fetched contents 
-  for a period of time (currently 1 hour). This is helpful since the contents 
-  may be accessed several times in a short period of time (for example, to determine 
-  the synchronization state and display the contents in a compare editor). Subclasses 
-  must still provide the unique content identifier along with the byte array that 
-  can be persisted in order to recreate the resource variant handle.</p>
-<h3>Building on Top of Existing Workspace Synchronization</h3>
-<p>Many repository providers may already have a mechanism for managing their synchronization 
-  state (e.g. if they have existing plug-ins). The <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber</a> 
-  and its related classes provide the ability to build on top of an existing synchronization 
-  infrastructure. For example, this is the superclass of all of the CVS subscribers.</p>
-<h4>ResourceVariantTreeSubscriber</h4>
-<p>As was mentioned in the previous example, the <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySubscriber.html">ThreeWaySubscriber</a> 
-  is a subclass of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber</a> 
-  that provides local workspace synchronization using a <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a>. 
-  Subclasses of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTreeSubscriber.html">ResourceVariantTreeSubscriber</a> 
-  must provide:</p>
-<ul>
-  <li>
-    <p>Subclasses of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-      (or <a href="../reference/api/org/eclipse/team/core/variants/AbstractResourceVariantTree.html">AbstractResourceVariantTree</a>) 
-      that provide the behavior for traversing and refreshing the remote resource 
-      variants and, for subscribers that support three-way comparisons, the base 
-      resource variants.</p>
-  </li>
-  <li>An implementation of <a href="../reference/api/org/eclipse/team/core/variants/IResourceVariantComparator.html">IResourceVariantComparator</a> 
-    that performs the two-way or three-way comparison for a local resource and 
-    its base and remote resource variants.It is common to also provide a subclass 
-    of <a href="../reference/api/org/eclipse/team/core/synchronize/SyncInfo.html">SyncInfo</a> 
-    in order to customize the synchronization state determination algorithm. </li>
-  <li>An implementation of the roots method for providing the roots of the subscriber 
-    and an implementation of the isSupervised method for determining what resources 
-    are supervised by the subscriber.</li>
-</ul>
-<p>The other capabilities of the subscriber are implemented using these
-facilities.</p>
-<h4>ResourceVariantTree</h4>
-<p><a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantTree.html">ResourceVariantTree</a> 
-  is a concrete implementation of <a href="../reference/api/org/eclipse/team/core/variants/IResourceVariantTree.html">IResourceVariantTree</a> 
-  that provides the following:</p>
-<ul>
-  <li>traversal of the resource variant tree</li>
-  <li>logic to merge the previous resource variant tree state with the
-current fetched state.</li>
-  <li>caching of the resource variant tree using a <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantByteStore.html">ResourceVariantByteStore</a>.</li>
-</ul>
-<p>The following must be implemented by subclasses:</p>
-<ul>
-  <li>creation of resource variant handles from the cached bytes that
-represent a resource variant</li>
-  <li>fetching of the current remote state from the server</li>
-  <li>creation of the byte store instance used to cache the bytes that
-uniquely identify a resource variant</li>
-</ul>
-<p>Concrete implementations of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantByteStore.html">ResourceVariantByteStore</a> 
-  are provided that persist bytes across workbench invocations (<a href="../reference/api/org/eclipse/team/core/variants/PersistantResourceVariantByteStore.html">PersistantResourceVariantByteStore</a>) 
-  or cached the bytes only for the current session (<a href="../reference/api/org/eclipse/team/core/variants/SessionResourceVariantByteStore.html">SessionResourceVariantByteStore</a>). 
-  However, building a subscriber on top of an existing workspace synchronization 
-  infrastructure will typically require the implementation of <a href="../reference/api/org/eclipse/team/core/variants/ResourceVariantByteStore.html">ResourceVariantByteStore</a> 
-  subclasses that interface with the underlying synchronizer. For example the 
-  <a href="../reference/api/org/eclipse/team/core/variants/ThreeWayRemoteTree.html">ThreeWayRemoteTree</a> 
-  makes use of a byte store implementation that stores the remote bytes in the 
-  <a href="../reference/api/org/eclipse/team/core/variants/ThreeWaySynchronizer.html">ThreeWaySynchronizer</a>.</p>
-<p>The creation of resource variant handles for this example does not differ from 
-  the previous example except that the handles are requested from a resource variant 
-  tree instance instead of the subscriber.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm
deleted file mode 100644
index 9f98ffb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_synchronize_localhistory_example.htm
+++ /dev/null

@@ -1,332 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-<meta content="text/css" http-equiv="Content-Style-Type">
-<link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-<title>Synchronization Support - Local History Example</title>
-<link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>Local History Example</h2>
-<p>The best way to understand the Synchronize APIs is to create a simple example 
-  that actually works. In this example we will be creating a page in the Synchronize 
-  View that will display the latest local history state for all files in the workspace. 
-  The local history synchronization will update automatically when changes are 
-  made to the workspace, and a compare editor can open to browse, merge, then 
-  changes. We will also add a custom decorator to show the last timestamp of the 
-  local history element and an action to revert the workspace files to their latest 
-  saved local history state. This is an excellent example because we already have 
-  a store of resource variants available and we don't have to manage it.</p>
-<p>For the remainder of this example we will make use of a running example. Much, 
-  but not all, of the source code will be included on this page. The full source 
-  code can be found in the local history package of the <a
- href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.team.examples.filesystem/">org.eclipse.team.examples.filesystem</a> 
-  plug-in. You can check the project out from the CVS repository and use it as 
-  a reference while you are reading this tutorial. <em>Disclaimer</em>: The source 
-  code in the example plug-ins may change over time. To get a copy that matches 
-  what is used in this example, you can check out the project using the 3.3.2 version 
-  tag (most likely R3_3_2) or a date tag of June 10, 2007.<br>
-  <br>
-  <img src="images/team_synchronize_example_localhistory_overview.png" alt="local history overview"><br>
-  <br>
-  This screen shot shows the local history synchronization in the Synchronize 
-  View. With it you can browse the changes between the local resource and the 
-  latest state in history. It has a custom decorator for displaying the timestamp 
-  associated with the local history entry and a custom action to revert your file 
-  to the contents in the local history. Notice also that the standard Synchronize 
-  View presentation is used which provide problem annotations, compressed folder 
-  layout, and navigation buttons.</p>
-<h3>Defining the variants for local history</h3>
-<p>The first step is to define a variant to represent the elements from local 
-  history. This will allow the synchronize APIs to access the contents from the 
-  local history so it can be compared with the current contents and displayed 
-  to the user.</p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-public class LocalHistoryVariant implements IResourceVariant {
-  private final IFileState state;
-  public LocalHistoryVariant(IFileState state) {
-    this.state = state;
-  }
-  public String getName() {
-    return state.getName();
-  }
-  public boolean isContainer() {
-    return false;
-  }
-  public IStorage getStorage(IProgressMonitor monitor) throws TeamException {
-    return state;
-  }
-  public String getContentIdentifier() {
-    return DateFormat.getDateTimeInstance().format(new Date(state.getModificationTime()));
-  }
-  public byte[] asBytes() {
-    return null;
-  }
-  public IFileState getFileState() {
-    return state;
-  }
-}
-</span></pre>
- 
-<p>Since the IFileState interface already provides access to the contents of the 
-  file from local history (i.e. implements the IStorage interface), this was easy. 
-  Generally, when creating a variant you have to provide a way of accessing the 
-  content, a content identifier that will be displayed to the user to identify 
-  this variant, and a name. The asBytes() method is only required if persisting 
-  the variant between sessions. <br>
-  <br>
-  Next, let's create a variant comparator that allows the SyncInfo calculation 
-  to compare local resources with their variants. Again, this is easy because 
-  the existence of a local history state implies that the content of the local 
-  history state differs from the current contents of the file. This is because 
-  the specification for local history says that it won't create a local history 
-  state if the file hasn't changed. </p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-public class LocalHistoryVariantComparator implements IResourceVariantComparator {
-  public boolean compare(IResource local, IResourceVariant remote) {
-    return false;
-  }
-  public boolean compare(IResourceVariant base, IResourceVariant remote) {
-    return false;
-  }
-  public boolean isThreeWay() {
-    return false;
-  }
-}
-</span></pre>
- 
-<p>Because we know that the existence of the local history state implies that 
-  it is different from the local, we can simply return <strong>false</strong> 
-  when comparing the file to it's local history state. Also, synchronization with 
-  the local history is only two-way because we don't have access to a base resource 
-  so the method for comparing two resource variants is not used.</p>
-<p> Note that the synchronize calculation won't call the compare method of the 
-  comparator if the variant doesn't exist (i.e. is null). It is only called if 
-  both elements exist. In our example, this would occur both for files that don't 
-  have a local history and for all folders (which never have a local history). 
-  To deal with this, we need to define our own subclass of SyncInfo in order to 
-  modify the calculated synchronization state for these cases.</p>
-  
-<pre><span style="color: rgb(68, 68, 204);">
-public class LocalHistorySyncInfo extends SyncInfo {
-  public LocalHistorySyncInfo(IResource local, IResourceVariant remote, IResourceVariantComparator comparator) {
-    super(local, null, remote, comparator);
-  }
-  protected int calculateKind() throws TeamException {
-    if (getRemote() == null)
-      return IN_SYNC;
-    else
-      return super.calculateKind();
-  }
-}
-</span></pre>
-
-<p>We have overridden the constructor to always provide a base that is <em>null</em> 
-  (since we are only using two-way comparison) and we have modified the synchronization 
-  kind calculation to return <em>IN_SYNC</em> if there is no remote (since we 
-  only care about the cases where there is a local file and a file state in the 
-  local history.</p>
-<h3>Creating the Subscriber</h3>
-<p>Now we will create a Subscriber that will provide access to the resource variants 
-  in the local history. Since local history can be saved for any file in the workspace, 
-  the local history Subscriber will supervise every resource and the set of roots 
-  will be all projects in the workspace. Also, there is no need to provide the 
-  ability to refresh the subscriber since the local history changes only when 
-  the contents of a local file changes. Therefore, we can update our state whenever 
-  a resource delta occurs. That leaves only two interesting method on our local 
-  history subscriber: obtaining a SyncInfo and traversing the workspace. </p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-public SyncInfo getSyncInfo(IResource resource) throws TeamException {
-  try {
-    IResourceVariant variant = null;
-    if(resource.getType() == IResource.FILE) {
-      IFile file = (IFile)resource;
-      IFileState[] states = file.getHistory(null);
-      if(states.length &gt; 0) {
-        // last state only
-        variant = new LocalHistoryVariant(states[0]);
-      } 
-    }
-    SyncInfo info = new LocalHistorySyncInfo(resource, variant, comparator);
-    info.init();
-    return info;
-  } catch (CoreException e) {
-    throw TeamException.asTeamException(e);
-  }
-}
-</span></pre>
-
-<p>The Subscriber will return a new SyncInfo instance that will contain the latest 
-  state of the file in local history. The SyncInfo is created with a local history 
-  variant for the remote element. For projects, folders and files with no local 
-  history, no remote resource variant is provided, which will result in the resource 
-  being considered in-sync due to the <em>calculateKind</em> method in our LocalHistorySyncInfo. 
-</p>
-<p>The remaining code in the local history subscriber is the implementation of 
-  the <em>members</em> method:</p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-public IResource[] members(IResource resource) throws TeamException {
-    try {
-      if(resource.getType() == IResource.FILE)
-        return new IResource[0];
-      IContainer container = (IContainer)resource;
-      List existingChildren = new ArrayList(Arrays.asList(container.members()));
-      existingChildren.addAll(Arrays.asList(container.findDeletedMembersWithHistory(IResource.DEPTH_INFINITE, null)));
-      return (IResource[]) existingChildren.toArray(new IResource[existingChildren.size()]);
-    } catch (CoreException e) {
-      throw TeamException.asTeamException(e);
-    }
-}
-</span></pre>
-
-<p>The interesting detail of this method is that it will return non-existing children 
-  if a deleted resource has local history. This will allow our Subscriber to return 
-  SyncInfo for elements that only exist in local history and are no longer in 
-  the workspace.</p>
-<h3>Adding a Local History Synchronize Participant</h3>
-<p>So far we have created the classes which provide access to SyncInfo for elements 
-  in local history. Next, we will create the UI elements that will allow us to 
-  have a page in the Synchronize View to display the last history state for every 
-  element in local history. Since we have a Subscriber, adding this to the Synchronize 
-  View is easy. Let's start by adding an synchronize participant extension point:</p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-&lt;extension
-  point="org.eclipse.team.ui.synchronizeParticipants"&gt;
-  &lt;participant
-      persistent="false"
-      icon="icons/full/wizards/synced.gif"
-      class="org.eclipse.team.examples.localhistory.LocalHistoryParticipant"
-      name="Latest From Local History"
-      id="org.eclipse.team.synchronize.example"/&gt;
-&lt;/extension&gt;
-</span></pre>
- 
-<p>Next we have to implement the LocalHistoryParticipant. It will subclass SubscriberParticipant 
-  which will provide all the default behavior for collecting SyncInfo from the 
-  subscriber and updating sync states when workspace changes occur. In addition, 
-  we will add an action to revert the workspace resources to the latest in local 
-  history.</p>
-<p>First, we will look at how a custom action is added to the participant.</p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-public static final String CONTEXT_MENU_CONTRIBUTION_GROUP = "context_group_1"; //$NON-NLS-1$
-  
-private class LocalHistoryActionContribution extends SynchronizePageActionGroup {
-  public void initialize(ISynchronizePageConfiguration configuration) {
-    super.initialize(configuration);
-    appendToGroup(
-      ISynchronizePageConfiguration.P_CONTEXT_MENU, CONTEXT_MENU_CONTRIBUTION_GROUP, 
-      new SynchronizeModelAction("Revert to latest in local history", configuration) { //$NON-NLS-1$
-        protected SynchronizeModelOperation getSubscriberOperation(ISynchronizePageConfiguration configuration, IDiffElement[] elements) {
-          return new RevertAllOperation(configuration, elements);
-        }
-      });
-  }
-}
-</span></pre>
-
-<p>Here we are adding a specific SynchronizeMoidelAction and operation. The behavior 
-  we get for free here is the ability to run in the background and show busy status 
-  for the nodes that are being worked on. The action reverts all resources in 
-  the workspace to their latest state in local history. The action is added by 
-  adding an action contribution to the participants configuration. The configuration 
-  is used to describe the properties used to build the participant page that will 
-  display the actual synchronize UI. </p>
-<p>The participant will initialize the configuration as follows in order to add 
-  the local history action group to the context menu:</p>
-  
-<pre><span style="color: rgb(68, 68, 204);">
-protected void initializeConfiguration(ISynchronizePageConfiguration configuration) {
-  super.initializeConfiguration(configuration);
-  configuration.addMenuGroup(
-    ISynchronizePageConfiguration.P_CONTEXT_MENU, 
-    CONTEXT_MENU_CONTRIBUTION_GROUP);
-  configuration.addActionContribution(new LocalHistoryActionContribution());
-  configuration.addLabelDecorator(new LocalHistoryDecorator());	
-}
-</span></pre>
- 
-<p>Now lets look at how we can provide a custom decoration. The last line of the 
-  above method registers the following decorator with the page's configuration.</p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-private class LocalHistoryDecorator extends LabelProvider implements ILabelDecorator {
-  public String decorateText(String text, Object element) {
-    if(element instanceof ISynchronizeModelElement) {
-      ISynchronizeModelElement node = (ISynchronizeModelElement)element;
-      if(node instanceof IAdaptable) {
-        SyncInfo info = (SyncInfo)((IAdaptable)node).getAdapter(SyncInfo.class);
-        if(info != null) {
-          LocalHistoryVariant state = (LocalHistoryVariant)info.getRemote();
-          return text+ " ("+ state.getContentIdentifier() + ")";
-        }
-      }
-    }
-    return text;
-  }
-		
-  public Image decorateImage(Image image, Object element) {
-    return null;
-  }
-}
-</span></pre>
-
-<p>The decorator extracts the resource from the model element that appears in 
-  the synchronize view and appends the content identifier of the local history 
-  resource variant to the text label that appears in the view.</p>
-<p>The last and final piece is to provide a wizard that will create the local 
-  history participant. The Team Synchronizing perspective defines a global synchronize 
-  action that allows users to quickly create a synchronization. In addition, the 
-  ability to create synchronizations in available from the Synchronize view toolbar. 
-  To start, create a synchronizeWizards extension point:</p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-&lt;extension
-  point="org.eclipse.team.ui.synchronizeWizards"&gt;
-  &lt;wizard
-    class="org.eclipse.team.examples.localhistory.LocalHistorySynchronizeWizard"
-    icon="icons/full/wizards/synced.gif"
-    description="Synchronize resources with their previous contents in the local history"
-    name="Synchronize with Latest From Local History"
-    id="ExampleSynchronizeSupport.wizard1"/&gt;
-&lt;/extension&gt;
-</span></pre>
- 
-<p>This will add our wizard to the list and in the wizards performFinish() method we 
-  will simply create our participant and add it to the synchronize manager.</p>
-
-<pre><span style="color: rgb(68, 68, 204);">
-LocalHistoryParticipant participant = new LocalHistoryParticipant();
-ISynchronizeManager manager = TeamUI.getSynchronizeManager();
-manager.addSynchronizeParticipants(new ISynchronizeParticipant[] {participant});
-ISynchronizeView view = manager.showSynchronizeViewInActivePage();
-view.display(participant);
-</span></pre>
-
-<h3>Conclusion</h3>
-<p>This is a simple example of using the synchronize APIs and we have glossed 
-  over some of the details in order to make the example easier to understand. 
-  Writing responsive and accurate synchronization support is non-trivial, the 
-  hardest part being the management of synchronization information and the notification 
-  of synchronization state changes. The user interface, if the one associated 
-  with SubscriberParticipants is adequate, is the easy part once the Subscriber 
-  implementation is complete. For more examples please refer to the org.eclipse.team.example.filesystem 
-  plug-in and browse the subclasses in the workspace of Subscriber and ISynchronizeParticipant.<br>
-  <br>
-  The next section describes some class and interfaces that can help you write 
-  a Subscriber from scratch including how to cache synchronization states between 
-  workbench sessions.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm
deleted file mode 100644
index 3cd80dd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_actions.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Adding team actions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-   Adding team actions
-</h3>
-<p>The team UI plug-in defines a popup menu extension in order to consolidate
-all team-related actions in one place.&nbsp; The team menu includes many
-subgroup slots so that team provider plug-ins can contribute actions and have
-some amount of control over the order of items in the menu.&nbsp; The following
-markup is from the team UI's plug-in manifest:</p>
-<pre>&lt;extension
-     point=&quot;org.eclipse.ui.popupMenus&quot;&gt;
-	&lt;objectContribution
-       	   id=&quot;org.eclipse.team.ui.ResourceContributions&quot;
-           objectClass=&quot;org.eclipse.core.resources.IResource&quot; adaptable=&quot;true&quot;&gt;
-		&lt;menu
-			id=&quot;<b>team.main</b>&quot;
-			path=&quot;additions&quot;
-			label=&quot;%TeamGroupMenu.label&quot;&gt;
-			<b>&lt;separator name=&quot;group1&quot;/&gt;
-			&lt;separator name=&quot;group2&quot;/&gt;
-			&lt;separator name=&quot;group3&quot;/&gt;
-			&lt;separator name=&quot;group4&quot;/&gt;
-			&lt;separator name=&quot;group5&quot;/&gt;
-			&lt;separator name=&quot;group6&quot;/&gt;
-			&lt;separator name=&quot;group7&quot;/&gt;
-			&lt;separator name=&quot;group8&quot;/&gt;
-			&lt;separator name=&quot;group9&quot;/&gt;
-			&lt;separator name=&quot;group10&quot;/&gt;</b>
-			&lt;separator name=&quot;targetGroup&quot;/&gt;
-			&lt;separator name=&quot;projectGroup&quot;/&gt;
-		&lt;/menu&gt;
-	... 
-&lt;/extension&gt;</pre>
-<p>A team menu is added to the popup menu of all views that show resources (or
-objects that adapt to resources.)&nbsp; Your plug-in can use the id of this menu
-and the separator groups in order to add your own menu items.&nbsp; There is
-nothing to keep you from defining your own popup menus, action sets, or view and
-editor actions.&nbsp; However, adding your actions to the predefined team menu
-makes it easier for the end user to find your actions.</p>
-<p>Let's look at a CVS action that demonstrates some interesting points:</p>
-<pre>&lt;extension
-    point=&quot;org.eclipse.ui.popupMenus&quot;&gt;
-     &lt;objectContribution
-           objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-           adaptable=&quot;true&quot;
-           id=&quot;org.eclipse.team.ccvs.ui.IFileContributions&quot;&gt;
-        &lt;filter
-              <b>name=&quot;projectPersistentProperty&quot;</b>
-              <b>value=&quot;org.eclipse.team.core.repository=org.eclipse.team.cvs.core.cvsnature&quot;&gt;</b>
-        &lt;/filter&gt;
-        &lt;action
-              label=&quot;%IgnoreAction.label&quot;
-              tooltip=&quot;%IgnoreAction.tooltip&quot;
-              class=&quot;org.eclipse.team.internal.ccvs.ui.actions.IgnoreAction&quot;
-              menubarPath=&quot;<b>team.main/group3</b>&quot;
-              helpContextId=&quot;org.eclipse.team.cvs.ui.team_ignore_action_context&quot;
-              id=&quot;org.eclipse.team.ccvs.ui.ignore&quot;&gt;
-        &lt;/action&gt;
-	...</pre>
-<p>Note that the action is contributed using the <a href="../reference/extension-points/org_eclipse_ui_popupMenus.html"><b>org.eclipse.ui.popupMenus
-</b>
-</a>workbench extension point.&nbsp; Here are some team-specific things
-happening in the markup:</p>
-<ul>
-  <li>the action is filtered by a project persistent property which identifies
-    team providers.&nbsp; The value of the property must be of the format <b>&quot;org.eclipse.team.core.repository=&lt;your
-    repository id&gt;&quot;</b> where <b>&lt;your repository id&gt;</b> is the <b>id</b>
-    provided in the <a href="../reference/extension-points/org_eclipse_team_core_repository.html"> <b> org.eclipse.team.core.repository</b></a> 
-    markup.&nbsp; This filter ensures that the CVS popup menu items only appear for
-    files that appear in projects that have been mapped to the CVS repository
-    id.</li>
-  <li>the action is added to a group in the menu that was specified above in the
-    team UI plug-in</li>
-</ul>
-<p>The implementation of an action is largely dependent on your specific
-provider.</p>
-<p>&nbsp;</p>
-<p>
-   &nbsp;
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm
deleted file mode 100644
index 8e81b50..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_decorators.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Team decorators</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Team decorators </h3>
-<p>Since any view that shows resources can contain projects that are configured 
-  with different team providers, it is helpful for team providers to contribute 
-  <a href="workbench_advext_decorators.htm">decorators</a> that distinguish resources 
-  configured for their repository.&nbsp; The CVS client uses decorators to show 
-  information such as a dirty flag (the &gt; symbol), tags, keywords (e.g. &quot;(ASCII 
-  -kkv)&quot;), and revisions (e.g. &quot;1.15&quot;). Icons can also be decorated 
-  (e.g. the <img src="images/team-version_controlled.png" alt="version control icon"> 
-  symbol indicates that the resource is managed by CVS).</p>
-
-
-
-
-<p><img src="images/teamdecorators.png" alt="Resource navigator with team decorators turned on" border="0" >
-</p>
-
-
-
-
-<p>Some decorators may be expensive to compute, so it's a good idea to allow the
-users some control over the use, or even content, of decorators.&nbsp; The CVS
-client provides a preference page that allows users to control the presentation
-and content of decorators.
-</p>
-
-
-
-
-<p>See <a href="../reference/extension-points/org_eclipse_ui_decorators.html"><b>org.eclipse.ui.decorators</b></a>
-for a complete description of the decorator extension point.&nbsp; The CVS
-decorator markup is as follows:
-</p>
-
-<pre>&lt;extension
-     point=&quot;org.eclipse.ui.decorators&quot;&gt;
-  &lt;decorator
-        objectClass=&quot;org.eclipse.core.resources.IResource&quot;
-        adaptable=&quot;true&quot;
-        label=&quot;%DecoratorStandard.name&quot;
-        state=&quot;false&quot;
-        class=&quot;org.eclipse.team.internal.ccvs.ui.CVSDecorator&quot;
-        id=&quot;org.eclipse.team.cvs.ui.decorator&quot;&gt;
-     &lt;description&gt;
-        %DecoratorStandard.description
-     &lt;/description&gt;
-  &lt;/decorator&gt;
-&lt;/extension&gt;</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_history.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui_history.htm
deleted file mode 100644
index 65e887e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_history.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Adding History support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-   Adding History support
-</h2>
-<p>There are two parts to adding History support to your repository:</p>
-<ul>
-<li>Providing implementations for the core history interfaces; see the
-<b>Providing History</b> section.</li>
-<li>Creating the UI elements for the History Page which gets displayed in the
-History View; see the <b>Showing History</b> section.</li>
-</ul>
-
-<h3>Providing History</h3>
-<p>
-The core history interfaces allow users to access the history of an item by querying the 
-<a href="../reference/api/org/eclipse/team/core/history/IFileHistoryProvider.html">IFileHistoryProvider</a>
-returned by the RepositoryProvider.  To do this, you need to:
-</p>
-<ul>
-<li>Provide an implementation for <a href = "../reference/api/org/eclipse/team/core/history/IFileHistory.html">IFileHistory</a> 
-by extending <a href = "../reference/api/org/eclipse/team/core/history/provider/FileHistory.html">FileHistory</a>.</li>
-<li>Provide an implementation for <a href = "../reference/api/org/eclipse/team/core/history/IFileRevision.html">IFileRevision</a> by extending
-<a href = "../reference/api/org/eclipse/team/core/history/provider/FileRevision.html">FileRevision</a>.</li>
-<li>Provide an implementation for <a href = "../reference/api/org/eclipse/team/core/history/IFileHistoryProvider.html">IFileHistoryProvider</a> by
-extending <a href = "../reference/api/org/eclipse/team/core/history/provider/FileHistoryProvider.html">FileHistoryProvider</a>.</li>
-<li>Provide an implementation for <a HREF="../reference/api/org/eclipse/team/core/RepositoryProvider.html#getFileHistoryProvider()">getFileHistoryProvider</a> to
-allow users to fetch the IFileHistoryProvider from your RepositoryProvider.</li>
-</ul>
-
-<h3>Showing History</h3>
-<p>To display history for items in your repository, you can provide one or more HistoryPages which will be shown
-in the History view. To do this, you need to:</p>
-<ul>
-<li>Provide an implementation for <a href = "../reference/api/org/eclipse/team/ui/history/IHistoryPage.html">IHistoryPage</a> by extending
-<a href = "../reference/api/org/eclipse/team/ui/history/HistoryPage.html">HistoryPage.</a></li>
-<li>Provide an implementation for <a href = "../reference/api/org/eclipse/team/ui/history/IHistoryPageSource.html">IHistoryPageSource</a> by
-extending <a href = "../reference/api/org/eclipse/team/ui/history/HistoryPageSource.html">HistoryPageSource</a>. When a resource is selected to
-be shown in the History view it will try to adapt the FileHistoryProvider it gets from your repository provider to a HistoryPageSource. If 
-it doesn't succeed, it will then try to adapt the repository provider itself. For non-resource objects, the History view will
-try to adapt the object to a HistoryPageSource. The FileSystem History view example registers an adapter factory that adapts a FileHistoryProvider
-to an IHistoryPageSource.
- </li>
-<li>Create a Show History Action, provide an object contribution for the Action. See <a href="../reference/extension-points/org_eclipse_ui_popupMenus.html"><b>org.eclipse.ui.popupMenus</b></a> for more
-info.</li>
-</ul>
-
-<h3>Showing History for Sub-file Elements</h3>
-<p>To display the history of a model element that is contained in a file, you can do the following:</p>
-<ul>
-<li>Implement a <a href="../reference/api/org/eclipse/compare/structuremergeviewer/StructureCreator.html"><b>StructureCreator</b></a>
-for the file.</li>
-<li>Subclass <a href="../reference/api/org/eclipse/team/ui/history/ElementLocalHistoryPageSource.html"><b>ElementLocalHistoryPageSource</b></a>
-and adapt your sub-file element(s) to an instance of the subclass.</li>
-<li>To show the history in the History View, pass your history page source and element to the <code>showHistoryFor</code>
-method of <a href="../reference/api/org/eclipse/team/ui/TeamUI.html"><b>TeamUI</b></a>.</li>
-<li>To show the history in a dialog, provide History actions (show, compare, replace) that make use of a 
-<a href="../reference/api/org/eclipse/team/ui/history/HistoryPageCompareEditorInput.html"><b>HistoryPageCompareEditorInput</b></a>
-to show the history.</li>
-</ul>
-
-<h3>FileSystem History example</h3>
-<p>The FileSystem example illustrates how you can provide history and a history page for repository items.
-Select a resource in a FileSystem managed project and choose <b>Team &gt; Show History</b>. The FileSystem History
-page will be displayed in the History view with all of the local revisions as well as the FileSystem revision
- displayed. You can right click on any revision and select <i>Open</i> from the context menu to open the revision.</p>
- 
-<h3>FileRevisionEditorInput</h3>
-<p>To support the <i>Open</i> functionality, the FileSystem history example had to create its own FileSystemRevisionEditorInput (see 
-org.eclipse.team.examples.filesystem.ui.FileSystemRevisionEditorInput). This class adapts to IFileRevision and to IFileState, which
-can be used to determine whether the editor contains remote contents (IFileRevision) or local history contents (IFileState).</p>
-
-<p>Likewise, the existing FileRevisionEditorInput's that come with the SDK and are used by the CVS History page and Local History page 
-all adapt to IFileRevision which can be used to determine if the revision contained in the editor is that of a remote revision.</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm b/bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm
deleted file mode 100644
index 5b12309..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/team_ui_prefs.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Adding preferences and properties</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Adding preferences and properties</h3>
-<p><a href="preferences_prefs.htm">Preferences</a> and <a href="preferences_prop_contribute.htm">properties</a>
-can be contributed by team UI plug-ins using the standard techniques.&nbsp; The
-only difference for a team plug-in is that preferences should be contributed
-using the team category, so that all team related preferences are grouped
-together.&nbsp; The CVS markup for the main preferences page looks like this:</p>
-<pre>&lt;extension
-      point=&quot;org.eclipse.ui.preferencePages&quot;&gt;
-   &lt;page
-         name=&quot;%PreferencePage.name&quot;
-         <b>category=&quot;org.eclipse.team.ui.TeamPreferences&quot;</b>
-         class=&quot;org.eclipse.team.internal.ccvs.ui.CVSPreferencesPage&quot;
-         id=&quot;org.eclipse.team.cvs.ui.CVSPreferences&quot;&gt;
-   &lt;/page&gt;
-&lt;/extension&gt;</pre>
-<p>The preferences dialog shows the CVS preferences underneath the team
-category.</p>
-<p><img src="images/teamprefs.png" alt="" border="0" ></p>
-<p>&nbsp;</p>
-<p>Properties are added as described by <a href="../reference/extension-points/org_eclipse_ui_propertyPages.html"><b>org.eclipse.ui.propertyPages</b></a>.&nbsp;
-There is no special team category for properties, since a resource can only be
-configured for one repository provider at a time.&nbsp; However, you must set up
-your property page to filter on the team project persistent property (similar to
-the way we filtered resources for popup menu actions.)</p>
-<pre>
-  &lt;extension
-    point=&quot;org.eclipse.ui.propertyPages&quot;&gt;
-     &lt;page
-           objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-           adaptable=&quot;true&quot;
-           name=&quot;%CVS&quot;
-           class=&quot;org.eclipse.team.internal.ccvs.ui.CVSFilePropertiesPage&quot;
-           id=&quot;org.eclipse.team.ccvs.ui.propertyPages.CVSFilePropertiesPage&quot;&gt;
-        &lt;filter
-<b>              name=&quot;projectPersistentProperty&quot;
-              value=&quot;org.eclipse.team.core.repository=org.eclipse.team.cvs.core.cvsnature&quot;&gt;
-</b>        &lt;/filter&gt;
-     &lt;/page&gt;
-     ...</pre>
-<p>
-   &nbsp;
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua.htm
deleted file mode 100644
index d7e2325..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>User assistance support</title>
-</head>
-<body>
-
-<h1>User assistance support</h1>
-
-<h3>What is user assistance?</h3>
-
-<p>
-User assistance is a set of components that together introduce the user
-to the product, guide the user through tasks, and help the user find more
-information about the product. There are four basic components:
-</p>
-
-<ul>
-<li><a href="ua_intro.htm">Welcome</a></li>
-<li><a href="ua_help.htm">Help</a></li>
-<li><a href="ua_cheatsheet.htm">Cheat Sheets</a></li>
-<li><a href="ua_statushandling.htm">Status Handling</a></li>
-</ul>
-
-<h3>Welcome</h3>
-
-<p>
-<a href="ua_intro.htm">Welcome</a> (also called Intro) support is a set of
-extension points and workbench parts that allow plug-ins to define specialized
-pages that introduce a platform product to new users. These extension points
-can be used to create the &quot;Initial User Experience&quot; of the product in
-the form of welcome pages. Welcome pages are intended to guide users into
-discovering a product's functionality. They are typically shown the first time
-a product is started.
-</p>
-
-<h3>Help</h3>
-
-<p>
-The <a href="ua_help.htm">help system</a> provides the raw building blocks to
-structure and contribute documentation to the platform. It does not dictate
-structure or granularity of documentation. You can choose the tools and
-structure for your documentation that suits your needs.&nbsp; The help plug-in
-allows you to describe your documentation structure to the platform using a
-table of contents (toc) file.
-</p>
-
-<p>
-Help also includes context help support, where a user can
-summon help for a particular element in the UI (e.g. by pressing F1 on Windows).
-In addition, help provides the ability to perform a single search that finds
-information from any number of sources (federated information search).
-</p>
-
-<h3>Cheat Sheets</h3>
-
-<p>
-<a href="ua_cheatsheet.htm">Cheat sheets</a> guide users through tasks. The
-task is broken down into steps and presented to the user one step at a time, and
-the user checks off the steps as he/she completes them. Cheat sheets come in two
-forms: simple (one task, several steps), and composite (many sub-tasks, each
-having many steps). Which one you use depends on the size and complexity of the
-task you want to guide the user through.
-</p>
-
-<h3>Status Handling</h3>
-
-<p>
-<a href="ua_statushandling.htm">Status handling</a> is a facility that 
-allows to introduce a custom way of showing problems in the product to users. 
-A part of the facility is an extension point which allows to plug new status handler
-specific for the product. This handler associated to the product is intended
-to present the problem in the useful for users way.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
deleted file mode 100644
index 386a47b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Cheat sheets</title>
-</head>
-<body>
-
-<h2>Cheat sheets</h2>
-
-<h3><b>Guiding the user through tasks</b></h3>
-
-<p>
-Even when the platform UI filters out unneeded functionality, there is still a steep learning
-curve faced by a new user.  The platform UI introduces several mechanisms for helping the user choose what
-task needs to be done and guiding the user through the steps in that task.  These mechanisms are used by
-the workbench itself to help guide Eclipse SDK users through tasks.
-</p>
-<ul>
-<li>Cheat sheets can help guide the user through a series of 
-steps in order to achieve some
-overall goal.  Some steps can be performed by the cheat sheet, and some are described so that the user
-can manually complete the step.</li>
-<li>Composite cheat sheets 
-can guide the user through larger problems by breaking that problem into tasks. 
-Each task is represented by a simple cheat sheet. </li>
-</ul>
-
-<h3>Related links</h3>
-<p>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm">Working with cheat sheets</a><br>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm">Working with composite cheat sheets</a><br>
-<a href="ua_cheatsheet_simple.htm">Simple cheat sheets</a><br>
-<a href="ua_cheatsheet_composite.htm">Composite cheat sheets</a><br>
-<a href="ua_cheatsheet_guidelines.htm">Authoring guidelines</a><br>
-<a href="../reference/extension-points/cheatSheetContentFileSpec.html">Cheat 
-Sheet Content File Format</a><br>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
deleted file mode 100644
index 8176b99..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite.htm
+++ /dev/null

@@ -1,149 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Composite cheat sheets</title>
-</head>
-<body>
-
-<h2>Composite cheat sheets</h2>
-
-<p>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm">
-Composite cheat sheets</a> provide guidance through complex problems by breaking 
-the problem into a set of smaller tasks. Composite cheat sheets are registered 
-using the&nbsp; the <b>
-<a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">
-org.eclipse.ui.cheatsheets.cheatSheetContent</a></b> extension point. </p>
-<h3>Content file format</h3>
-<p>The composite cheat sheet content itself is defined in a separate file which 
-conforms to the&nbsp; <a href="ua_cheatsheet_composite_content.htm">composite cheat sheet 
-content file specification</a>. The content file is&nbsp; an XML file and 
-consists of&nbsp; a set of tasks organized in groups into a tree structure. </p>
-<p>&lt;compositeCheatsheet&gt; is the root element of a composite cheat sheet. It will 
-have a single root task which may be a &lt;task&gt; or &lt;taskGroup&gt;. &lt;taskGroup&gt; 
-elements may have one or more children each of which can be a &lt;task&gt; or &lt;taskGroup&gt;. 
-A &lt;task&gt; does not have child tasks.</p>
-<p>Tasks and task groups may contain &lt;intro&gt; elements which contain the text to 
-be displayed before the task has been started and &lt;onCompletion&gt; elements which 
-contain the text to be displayed once the task is completed. Both the &lt;intro&gt; 
-and &lt;onCompletion&gt; elements may contain form text markup, in the example below 
-the tags &lt;b&gt; and &lt;/b&gt; are used to make text bold.</p>
-<p>Tasks may also contain &lt;param&gt; elements. A cheat sheet task may have any 
-of the following parameters: &quot;id&quot; is the id of a registered cheatsheet, &quot;path&quot; 
-is the relative path or URL of the cheat sheet content file and &quot;skipIntro&quot; is&nbsp; 
-a boolean parameter which if true causes&nbsp; the cheat sheet to start at the 
-first step rather than at the introduction. Either &quot;id&quot; or &quot;path&quot; but not both 
-must be specified.</p>
-<p>A &lt;dependency&gt; node from task &quot;B&quot; to task &quot;A&quot; represents a requirement that 
-task A is completed before task B can be started.</p>
-<h3>Cheat sheet task parameters</h3>
-<p>If a task has kind = &quot;cheatsheet&quot; a cheat sheet will be opened when that task 
-is started, There are three possible parameters to a cheat sheet task.</p>
-<table border="1" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111">
-  <tr>
-    <td width="10%">Parameter name</td>
-    <td width="29%">&nbsp;Description</td>
-  </tr>
-  <tr>
-    <td width="10%">id</td>
-    <td width="29%">The id of a cheat sheet which has been registered using the 
-    extension point org.eclipse.ui.cheatsheets.cheatSheetContent. This 
-    identifies the cheatsheet which will be associated with this task. Either 
-    the id or the path parameter (but not both) should be specified.</td>
-  </tr>
-  <tr>
-    <td width="10%">path</td>
-    <td width="29%">The URL of a cheat sheet content file. This may be an 
-    absolute URL, or relative to the content file for the composite cheat sheet. 
-    If both id and path are specified the path will be used to locate the 
-    content file and the id parameter will be ignored.</td>
-  </tr>
-  <tr>
-    <td width="10%">showIntro</td>
-    <td width="29%">A boolean parameter with default value of true. If &quot;false&quot; 
-    the cheat sheet when started will initially show the first step rather than 
-    the introduction..</td>
-  </tr>
-</table>
-<h3>Example of a composite cheat sheet</h3>
-<p>The file below is an example of how to create a composite cheat sheet from 
-existing cheat sheets. It shows how to create task groups and make tasks skippable.</p>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;compositeCheatsheet name=&quot;Composite cheat sheet example&quot;&gt;
-    &lt;taskGroup name= &quot;Composite cheat sheet example&quot;&gt;
-         &lt;intro&gt; This is an example of a &lt;b&gt;composite cheat sheet&lt;/b&gt; built from existing cheat sheets.
-                 &lt;br/&gt;&lt;br/&gt;You can select a task to work on either by following the hyperlinks or by
-                 selecting a task in the tree. 
-         &lt;/intro&gt;  
-         &lt;onCompletion&gt;Congratulations you have completed all the tasks.&lt;/onCompletion&gt;             
-         &lt;task kind=&quot;cheatsheet&quot; name= &quot;Branching and merging using CVS&quot; skip=&quot;true&quot;&gt;
-              &lt;param name = &quot;id&quot; value = &quot;org.eclipse.platform.cvs_1&quot; /&gt;
-              &lt;intro&gt;This cheat sheet is intended for CVS users. If you are not using CVS or do
-              not intend to branch and merge you may skip this task.
-              &lt;/intro&gt;
-               &lt;onCompletion&gt;Congratulations you now know how to branch and merge.&lt;/onCompletion&gt;                  
-         &lt;/task&gt;
-         &lt;taskGroup name= &quot;Create Java Projects&quot; kind = &quot;sequence&quot;&gt;
-             &lt;intro&gt; First you will learn how to create a simple java project, then you will create 
-             an java project which uses SWT. 
-             &lt;br/&gt;&lt;br/&gt;This task group is a sequence which means that
-             if you click on the subtask &quot;Standalone SWT Application&quot; it will not let that task be started 
-             until &quot;Create a java project&quot; has been completed.
-             &lt;/intro&gt;
-              &lt;onCompletion&gt;Congratulations you have built both Java applications.&lt;/onCompletion&gt;
-             &lt;task kind=&quot;cheatsheet&quot; name= &quot;Create a java project&quot; id = &quot;createJavaProject&quot;&gt;
-                 &lt;param name=&quot;id&quot; value = &quot;org.eclipse.jdt.helloworld&quot;/&gt;
-                 &lt;param name=&quot;showIntro&quot; value = &quot;false&quot;/&gt;
-                 &lt;intro&gt;This cheat sheet walks through the process of creating a simple hello world application. 
-                        The cheat sheet can launch wizards to create a new project and a new class. 
-                 &lt;/intro&gt;
-                 &lt;onCompletion&gt;Congratulations you have succeeded in creating a hello world application&lt;/onCompletion&gt;
-             &lt;/task&gt;
-             &lt;task kind=&quot;cheatsheet&quot; name= &quot;Standalone SWT Application&quot;&gt;
-                 &lt;intro&gt;Eclipse plugins which contribute to the user interface use The Standard Widget Toolkit (SWT). 
-                    This task guide can be used to learn more about SWT. 
-                 &lt;/intro&gt;
-                 &lt;param name = &quot;id&quot; value = &quot;org.eclipse.jdt.helloworld.swt&quot; /&gt;
-                  &lt;onCompletion&gt;Congratulations you have succeeded in creating an SWT application.&lt;/onCompletion&gt;           
-             &lt;/task&gt;      
-         &lt;/taskGroup&gt;
-    &lt;/taskGroup&gt;
-&lt;/compositeCheatsheet&gt;</pre>
-<h3>Composite Cheat Sheet Extensibility - Provisional in Eclipse 3.2</h3>
-<p>Composite cheat sheets are extensible, however in Eclipse 3.2 this 
-extensibility is provisional and the classes could change before they become 
-API. Composite cheat sheet support can be extended by using the extension point 
-org.eclipse.ui.cheatsheets.cheatSheetContent which has two new elements 
-taskEditor and taskExplorer which allow for contribution of task editors and 
-task explorers.</p>
-<p>Contributing a task editor defines a new kind of task which displays in the 
-task detail section. To contribute a task editor implement a concrete subclass 
-of&nbsp; TaskEditor, then&nbsp; add a taskEditor element to plugin.xml.</p>
-<p>The representation of the task explorer is also configurable with an 
-extension point,&nbsp; a tree explorer&nbsp; is included with the Eclipse platform. By 
-default the explorer for a composite cheat sheet when first opened is a tree, an 
-attribute on the &lt;compositeCheatSheet&gt; element will allow that default to be 
-overridden. If more than one explorer is registered the view menu will contain a 
-menu item to switch between explorers. To contribute a task explorer first 
-implement a concrete subclass of&nbsp; TaskExplorer, then&nbsp; add a taskExplorer element 
-to plugin.xml.</p>
-
-<h3>Related links</h3>
-<p>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm">Working with cheat sheets</a><br>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm">Working with composite cheat sheets</a><br>
-<a href="ua_cheatsheet_simple.htm">Creating cheat sheets</a><br>
-<a href="ua_cheatsheet_guidelines.htm">Authoring guidelines</a><br>
-<a href="ua_cheatsheet_composite_content.htm">Composite cheat 
-sheet content file specification</a><br>
-<a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">
-org.eclipse.ui.cheatsheets.cheatSheetContent extension point</a><br>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
deleted file mode 100644
index c6c28a6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_composite_content.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Composite cheat sheet content file XML format</title>
-</head>
-<body>
-
-<h3>Composite cheat sheet content file XML format</h3>
-
-<h6 class=CaptionFigColumn id=header>Identifier: </h6>org.eclipse.ui.cheatsheets.composite_schema<p></p>
-<h6 class=CaptionFigColumn id=header>Since: </h6>3.2
-<p></p>
-
-<h6 class=CaptionFigColumn id=header>Description: </h6><p>The schema definition for a composite cheat sheet content file. A composite cheat sheet consists of a set of tasks organized into task groups. Each task can be a simple cheat sheet or a user contributed task kind.</p>
-<h6 class=CaptionFigColumn id=header>Configuration Markup:</h6>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.compositeCheatsheet">compositeCheatsheet</a> (<a href="#e.taskGroup">taskGroup</a> | <a href="#e.task">task</a>)&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST compositeCheatsheet</p>
-<p class=code id=dtdAttlist>name&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-The root element of a composite cheatsheet</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>name</b> - The name of the composite cheat sheet which will be displayed in large font when the composite cheat sheet is opened.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.taskGroup">taskGroup</a> ((<a href="#e.task">task</a> | <a href="#e.taskGroup">taskGroup</a>) , <a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.dependency">dependency</a>*)&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST taskGroup</p>
-<p class=code id=dtdAttlist>kind&nbsp;CDATA "set"</p><p class=code id=dtdAttlist>name&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>skip&nbsp;(true | false) "false"&gt;</p>
-<p class=ConfigMarkup id=elementDesc>
-A task group represents a collection of related tasks. If the kind is "choice" only one of the child tasks need to be completed. If the kind is "set" or "sequence" all children must be completed.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>kind</b> - The kind of this task group which can be "set", "sequence" or "choice". If the kind is set or sequence this task group is complete when all of its child tasks/task groups have been completed. In addition the subtasks of a sequence must be completed in order. A choice is complete when any of its subtasks has been completed.</li>
-<li><b>name</b> - The name of this task group which will be displayed in the task explorer.</li>
-<li><b>id</b> - An id for this task group which is required if this task group is referenced by a dependency element.</li>
-<li><b>skip</b> - If true this group of tasks may be skipped.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.task">task</a> (<a href="#e.intro">intro</a>? , <a href="#e.onCompletion">onCompletion</a>? , <a href="#e.param">param</a>* , <a href="#e.dependency">dependency</a>*)&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST task</p>
-<p class=code id=dtdAttlist>kind&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>name&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>skip&nbsp;(true | false) "false"&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A leaf task within a composite cheat sheet. A task does not have children, but it does have a task editor which shows in the lower/right hand pane of the cheat sheet view. The task kind determines which task editor will be opened, a task kind of "cheatsheet" represents a simple cheatsheet. Other task kinds may be contributed.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>kind</b> - The task kind. A task kind of "cheatsheet" represents a simple cheatsheet, other task kinds can be contributed using the extension point org.eclipse.ui.cheatsheets.cheatSheetContent.</li>
-<li><b>name</b> - The name of this task which will be displayed in the task explorer.</li>
-<li><b>id</b> - An id for this task group which is required if this task group is referenced by a dependency element.</li>
-<li><b>skip</b> - If true this task may be skipped.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.param">param</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST param</p>
-<p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>value&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A parameter to a task within a composite cheatsheet. Each parameter has a name and value, both of which are strings. A task may have any number of parameters, two parameters for a single task may not share the same name.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>name</b> - The name of this parameter.</li>
-<li><b>value</b> - The value of this parameter.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.intro">intro</a> (#PCDATA)&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Contains the text which will be displayed before this task has been started. May contain form text markup.</p>
-<br><br>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.onCompletion">onCompletion</a> (#PCDATA)&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Contains the text which will be displayed in the completion panel for this task. May contain form text markup.</p>
-<br><br>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.dependency">dependency</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST dependency</p>
-<p class=code id=dtdAttlist>task&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Creates a dependency between two tasks or subtasks.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>task</b> - The id of the task or task group which must be completed before this task can be started.</li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm
deleted file mode 100644
index 472933d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_guidelines.htm
+++ /dev/null

@@ -1,113 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Cheat sheet authoring guidelines</title>
-</head>
-<body>
-
-<h2>Cheat sheet authoring guidelines</h2>
-
-<p>
-Cheat sheets and composite cheat sheets enable a user to achieve a goal by 
-completing a sequence of steps. These guidelines discuss when to use cheat 
-sheets and how to best write a cheat sheet. </p>
-
-<h3>
-When to create cheat sheets</h3>
-
-<p>
-Cheat sheets are well suited to tasks which consist of&nbsp; steps which lead 
-towards a tangible goal, such as building a simple application. The goal must be 
-well defined so that the user can see success when all the steps in cheat sheet 
-have been completed. Tutorials are often good candidates for cheat sheets, in a 
-tutorial the goal is to learn how to perform a specific task. Cheat sheets will 
-usually contain up to 10 steps and can be completed in a half an hour or less. 
-For larger tasks consider using a composite cheat sheet. </p>
-
-<h3>
-When to create composite cheat sheets</h3>
-
-<p>
-Composite cheat sheets are used to for 
-providing guidance through a task which is too large to describe in a single 
-cheat sheet or which has multiple goals. A composite cheat sheet can be used to 
-describe a sequence of tasks each of which builds on its predecessor. </p>
-
-<h3>
-When not to use cheat sheets</h3>
-
-<p>
-Cheat sheets work best when problem can be solved by a sequence of simple steps. Cheat sheets are not a substitute for the help system which allows for 
-creation of HTML pages with rich graphics and random access of information using 
-search and hyperlinks. Cheat sheets are not intended for tasks which require a 
-large amount of text to be input by the user. </p>
-<h3>Guidelines for creating a cheat sheet</h3>
-<ul>
-  <li>Choose a short and meaningful title.</li>
-  <li>Utilize links to the help system in cheat sheet tasks whenever possible to 
-  provide background or more detailed information</li>
-  <li>Consider rewriting as a composite cheat sheet if there are more than 10 
-  steps.</li>
-  <li>Utilize commands where possible to perform simple tedious tasks such as 
-  opening perspectives, opening resources, executing wizards. Be sure to also 
-  provide a description of how to achieve the same effect without using the 
-  command.</li>
-  <li>&nbsp;Ensure commands can be skipped if the user decides to do the steps 
-  manually</li>
-  <li>Specify dialog=&quot;true&quot; for steps which open dialogs. This will cause the 
-  cheat sheet to open in a &quot;tray&quot; to the right of&nbsp; most dialogs.</li>
-  <li>Organize the steps in such a way that the user sees visible signs of 
-  success frequently. A cheat sheet that makes a number of different changes to 
-  java source and then launches an application could be rewritten so that the 
-  application was launched after each source change.</li>
-  <li>Make sure the user understands why they are performing each step.</li>
-  <li>Rather than describing multiple ways to perform&nbsp; a step pick the 
-  simplest way requiring the least amount of description.</li>
-  <li>Use&nbsp; break (&lt;br/&gt;) tags to improve readability.</li>
-  <li>Subitems can be used to break steps down into smaller steps.</li>
-  <li>Not all cheat sheets will require subitems.</li>
-  <li>Start subitem label text using action word such as &quot;Input&quot;, &quot;Expand&quot;, 
-  &quot;Select&quot;, etc</li>
-  <li>For subitem labels, clearly identify interface text using quotes to allow 
-  users to differentiate instruction text from interface text they&nbsp; need to 
-  locate and interact with.</li>
-  <li>Each subitem should be responsible for one atomic task such as inputting 
-  one value.</li>
-  <li>Always add an &lt;onCompletion&gt; element to the last step of a cheat sheet.</li>
-  <li>Test cheat sheets with different sizes for the cheat sheet view.</li>
-  <li>Test cheat sheets with the error log view open so you can see if any 
-  warnings are written to the log.</li>
-</ul>
-<h3>Guidelines for creating a composite cheat sheet</h3>
-<ul>
-  <li>A composite cheat sheet should contain tasks that are related by a common 
-  theme.</li>
-  <li>Each task within a composite cheat sheet should have a well defined goal.</li>
-  <li>Use &lt;onCompletion&gt; elements to recognize success.</li>
-  <li>Task names should&nbsp; be short and concise.</li>
-  <li>Complex problems can be solved by using tasks that build upon their 
-  predecessors.</li>
-  <li>Use skip=&quot;true&quot; if a task is optional.</li>
-  <li>For consistency, make sure the simple cheat sheet introduction and name 
-  match the introduction and name specified in the composite cheat sheet..</li>
-  <li>For task descriptions, clearly identify interface text using bold 
-  formatting.</li>
-  <li>Sequences should be used only when it is important to enforce order in 
-  which tasks can be started.</li>
-</ul>
-
-<h3>Related links</h3>
-<p>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm">Working with cheat sheets</a><br>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm">Working with composite cheat sheets</a><br>
-<a href="ua_cheatsheet_simple.htm">Simple cheat sheets</a><br>
-<a href="ua_cheatsheet_composite.htm">Composite cheat sheets</a><br>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
deleted file mode 100644
index c2a22b4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_cheatsheet_simple.htm
+++ /dev/null

@@ -1,243 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Simple cheat sheets</title>
-</head>
-<body>
-
-<h2>Simple cheat sheets</h2>
-
-<P >
-Cheat sheets guide the user through a series of complex tasks to achieve
-an overall goal.  For example, a cheat sheet could be used to help guide the user through all the steps needed to
-create, compile, and run a simple Java program.  Cheat sheets are launched from the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help &gt; Cheat Sheets...</b></a>
-
-menu item.  Cheat sheets can also be launched from an intro page.  
-</p>
-<p>Cheat sheets are defined using the
-<b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">org.eclipse.ui.cheatsheets.cheatSheetContent</a></b>
-extension point.  The cheat sheet content itself is defined in a separate file so that it can be more easily
-translated into other languages.
-</P>
-<h4>
-Contributing a cheat sheet</h4>
-<p>Contributing a cheat sheet is pretty straightforward.  Let's look at a cheat sheet contributed by the
-JDT for building a simple Java application.
-</p>
-<pre>&lt;extension point="org.eclipse.ui.cheatsheets.cheatSheetContent"&gt;
-	&lt;cheatsheet
-		name="%cheatsheet.helloworld.name"
-		contentFile="$nl$/cheatsheets/HelloWorld.xml"
-		id="org.eclipse.jdt.helloworld"&gt;
-		&lt;description&gt;%cheatsheet.helloworld.desc&lt;/description&gt;
-	&lt;/cheatsheet&gt;
-	...
-</pre>
-Much like other workbench contributions, a name, description, and id can be specified for the cheat
-sheet.  The name and description are shown when the user accesses the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help &gt; Cheat Sheets...</b></a>
-
-list.  A category for the cheat sheet can also be defined if you want 
-to place several cheat sheets into a logical grouping.  If no category is specified, the cheat sheet will
-appear in the <b>Other</b> category.
-<p align="center">
-<img border="0" src="images/cheatsheets.png" alt="Cheat sheet dialog"></p>
-<h4>Cheat sheet items</h4>
-<p>
-The real work for cheat sheets is done in the content file.  The content file is an XML file whose name and location
-are specified in the <b>contentFile</b> attribute.  The path for the file is relative to the plug-in's directory.  (Note
-the use of the <tt>$nl$</tt> variable in the directory name, which means the file will be located in a directory specific
-to the national language of the target environment.)
-</p>
-<p>The file format itself includes overview information about the cheat sheet followed
-by a description of each step (called an <i>item</i>) that
-the user will perform.  At its simplest, an item is just a detailed description of the step that the user should
-take.  However, an item can also specify an action that can be run to perform the step on behalf of the
-user.  Let's look at the first part of the content file (<tt>HelloWorld.xml</tt>) 
-for the Java cheat sheet.
-</p>
-<pre>&lt;?xml version="1.0" encoding="UTF-8" ?&gt; 
-&lt;cheatsheet title="Simple Java Application"&gt;
-	&lt;intro 
-		href="/org.eclipse.ui.cheatsheets.doc/tasks/tcheatst.htm"&gt;
-		&lt;description&gt;
-Welcome to the Hello, World Java tutorial.
-It will help you build the famous "hello world" application and try it out. You will create a java project, and a java class that will print "hello world" in the console when run.
-Let's get started!
-		&lt;/description&gt;
-&lt;/intro&gt;
-	&lt;item
-		href="/org.eclipse.platform.doc.user/concepts/concepts-4.htm"
-		title="Open the Java Perspective"&gt;
-		<b>&lt;action
-			pluginId="org.eclipse.ui.cheatsheets"
-			class="org.eclipse.ui.internal.cheatsheets.actions.OpenPerspective"
-			param1="org.eclipse.jdt.ui.JavaPerspective"/&gt;</b>
-		&lt;description&gt;
-Select Window-&gt;Open Perspective-&gt;Java in the menu bar at the top of the workbench.
-This step changes the perspective to set up the Eclipse workbench for Java development.
-You can click the "Click to Perform" button to have the "Java" perspective opened automatically.
-		&lt;/description&gt;
-&lt;/item&gt;
-...
-</pre>
-<p align="center">
-<img border="0" src="images/javacheatsheet.png" alt="Simple java cheat sheet">
-</p>
-<p>
-The title and intro information are shown at the top of the cheat sheet.  Then, the items are described. 
-The first item for this cheat sheet describes how to open the Java perspective.  Better still, the <b>action</b>
-attribute specifies a class that can be used to run the action on behalf of the user.  The class must
-implement <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>.  This is rather
-convenient, as it allows you to reuse the action classes written for menu or toolbar contributions.
-</p>
-<p>
-The class for the action can optionally implement 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetAction.html"><b>ICheatSheetAction</b></a>
-if the action uses parameters or needs to be aware of the cheat sheet and its state.  In this case, the action
-will be passed an array of parameters and a reference to the 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetManager.html"><b>ICheatSheetManager</b></a>
-so that it can request additional information about the cheat sheet. 
-Any necessary parameters can be passed to the action's run method using the <b>param<i>N</i></b> attributes.
-</p>
-<p>
-It is strongly recommended that actions invoked from cheat sheets report a success/fail outcome if running the
-action might fail.  (For example, the user might cancel the action from its dialog.)  See 
-<b><a href="../reference/api/org/eclipse/jface/action/IAction.html">IAction</a>.notifyResult(boolean)</b> for
-more detail.
-</p>
-<p>
-Items do not have to define actions.  If your item must be performed manually by the user, you need not
-specify an action at all.  Below is the third step of the Java cheat sheet, which merely
-tells the user how to code the simple application.  When no action is specified, the item description
-must instruct the user to press the appropriate button after the task has been completed.
-</p>
-<pre>&lt;item
-	href="/org.eclipse.jdt.doc.user/tasks/tasks-54.htm"
-	title="Add a System.out.println line in your main method"&gt;
-	&lt;description&gt;
-Now that you have your HelloWorld class,
-In the "public static void main" method, add the following statement:  System.out.println("Hello world!"); and save your changes.  Press the "click when done" button below when finished.
-	&lt;/description&gt;
-&lt;/item&gt;
-</pre>
-Additional attributes control whether the item can be skipped completely and what document should be
-launched if the user requests help during the step.  See the 
-<b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">org.eclipse.ui.cheatsheets.cheatSheetContent</a></b>
-extension point documentation for a description of all of the attributes that can be defined inside
-a cheat sheet.
-<h4>Subitems</h4>
-<p>
-Subitems may be defined to further organize the presentation of an item.  Unlike items, subitems do not have to
-be visited in any particular order.  Subitems may also define actions that automatically perform the subtask for
-the user.  Subitem actions are described in the same way as item actions. 
-</p>
-<h4>Conditional expressions and cheat sheet variables</h4>
-<p>
-Conditional expressions can be used to define cheat sheet elements whose content or behavior depends upon a
-particular condition being true.  Conditions are described in the <b>condition</b> element of a subitem
-using arbitrary string values that are matched
-against the <b>when</b> attribute for each choice.  Conditions typically reference cheat sheet
-variables using the form  <tt>${<i>var</i>}</tt>, where <i>var</i> refers to the name of a cheet sheet variable.
-A few simple examples will help demonstrate how conditional expressions work.
-</p>
-<p>
-<b>Conditional subitems</b> can be used to chose one subitem from a list of possible subitems.
-Only the first subitem whose <b>when</b> attribute matches the condition attribute is included in the
-cheat sheet.  For example:
-</p>
-<pre>&lt;item ...&gt;
-	&lt;conditional-subitem condition="${v1}"&gt;
-		&lt;subitem when="a" label="Step for A." /&gt;
-		&lt;subitem when="b" label="Step for B." /&gt;
-	&lt;/conditional-subitem&gt;
-&lt;/item&gt;
-</pre>
-This item specifies two possible subitems that depend on the value of the variable <tt>v1</tt>.
-If the variable value is <tt>a</tt>, then the first subitem will be included.  If the variable value
-is <tt>b</tt>, then the second subitem will be included.  If the variable is neither value, it is considered
-an error.
-<p>
-<b>Conditional actions</b> are similar to conditional subitems.  The <b>perform-when</b> element specifies
-a condition for performing one action among a list of possible actions.  The condition is described the same way,
-using an arbitrary string that often references a variable.  The action whose <b>when</b> attribute
-matches the condition is the one that will be performed.   For example:
-</p>
-<pre>&lt;item ...&gt;
-	&lt;perform-when condition="${v1}"&gt;
-		&lt;action when="a" class="com.example.actionA" pluginId-"com.example" /&gt;
-		&lt;action when="b" class="com.example.actionB" pluginId-"com.example" /&gt;
-	&lt;/perform-when&gt;
-&lt;/item&gt;
-</pre>
-The action to be performed is chosen based on the value of the <tt>v1</tt> variable.  If the variable
-value is neither <tt>a</tt> or <tt>b</tt>, it is considered an error.
-<h4>Repeated subitems</h4>
-<p>Repeated subitems describe a subitem that can can expand into 0, 1, or more similar substeps.  The
-substeps are individualized using the special variable <tt>${this}</tt>.  This variable will be replaced by
-the values specified in the <b>values</b> attribute.  The values attribute is a string of values that are separated
-by commas.  A variable that expands into a list of values may be used in the values attribute.
-For example:
-</p>
-<pre>&lt;item ...&gt;
-	&lt;repeated-subitem values="${v1}"&gt;
-		&lt;subitem label="Step ${this}" /&gt;
-	&lt;/repeated-subitem&gt;
-&lt;/item&gt;
-</pre>
-If the value of the variable is <tt>1,b,three</tt>, then three subitems will appear in the cheat sheet, each
-having a unique label ("Step 1," "Step b," "Step three").  The variable can be used in the label or the
-action paramater value.  It can also be accessed from the 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetManager.html"><b>ICheatSheetManager</b></a>
-while the action is executing.
-<h4>
-Cheat sheet listeners</h4>
-<p>
-In some cases, you may want to change other parts of your UI if a cheat sheet is active.
-For example, you may have an editor that shows special annotations if a cheat sheet is guiding the
-user through an editing task.  In this case, a <b>listener</b> can be specified as an attribute of
-the cheatsheet.  The listener attribute must be the fully qualified name of a Java class that
-subclasses
-<a href="../reference/api/org/eclipse/ui/cheatsheets/CheatSheetListener.html"><b>CheatSheetListener</b></a>.  
-Listeners will receive notifications along with an 
-<a href="../reference/api/org/eclipse/ui/cheatsheets/ICheatSheetEvent.html"><b>ICheatSheetEvent</b></a> when there
-is a change in the cheat sheet's life cycle, such as when it opens, closes, or completes.  
-</p>
-<h4>
-Contributing attributes to an existing cheat sheet</h4>
-<p>
-The <b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html">org.eclipse.ui.cheatsheets.cheatSheetItemExtension</a></b>
-extension can be used to contribute arbitrary attributes to a pre-existing cheat sheet.  
-The purpose of this extension point is to allow a plug-in to add additional buttons that will
-aid the user for a given step.  These additional buttons are displayed beside the help icon.  </p>
-<p>To use this mechanism, you can
-define any arbitrary attribute inside an item definition in the cheat sheet XML file.  The attribute name will be matched against any
-attributes contributed in extensions to <b><a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html">org.eclipse.ui.cheatsheets.cheatSheetItemExtension</a></b>.
-See the extension point documentation for more detail.
-</p>
-
-<h4>Related links</h4>
-<p>
-<a href="../../org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm">Working with cheat sheets</a><br>
-<a href="ua_cheatsheet_composite.htm">Creating composite cheat sheets</a><br>
-<a href="ua_cheatsheet_guidelines.htm">Authoring guidelines</a><br>
-<a href="../reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html">
-org.eclipse.ui.cheatsheets.cheatSheetContent extension point</a><br>
-<a href="../reference/extension-points/cheatSheetContentFileSpec.html">Cheat 
-sheet content file specification</a><br>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
deleted file mode 100644
index 94ed1ea..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic.htm
+++ /dev/null

@@ -1,122 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Dynamic content</title>
-
-<style type="text/css">
-	.highlight {
-		color: blue;
-	}
-</style>
-</head>
-<body>
-
-<h2>Dynamic content</h2>
-
-<h3>What is dynamic content?</h3>
-
-<p>
-Several user assistance components allow you to provide dynamic content. This
-means the content can change depending on the user's environment or context. For
-example, you may want a section of your help document or welcome page to only
-appear if the user has a certain functionality enabled.
-</p>
-
-<p>
-There are two basic ways to create dynamic content. One is to add tags and attributes
-(annotations) to your XML markup instructing the system to filter out sections or
-documents, include sections from other documents, or extend documents by contributing
-into anchors or replacing elements.
-</p>
-
-<p>
-The other method is to write your own content producer by plugging in some
-Java code that will write the content from scratch or process existing static
-documents on-the-fly. Let's examine both approaches.
-</p>
-
-<h3>XML Annotations</h3>
-
-The simplest way to create dynamic content is to use the XML markup annotations.
-You simply add some special attributes and tags to your XML markup and the system
-will process the instructions. You can use this markup to:
-
-<ul>
-<li><a href="ua_dynamic_filters.htm">Filter</a> out documents or parts of documents</li>
-<li><a href="ua_dynamic_includes.htm">Include</a> sections from other documents, and</li>
-<li><a href="ua_dynamic_extensions.htm">Extend</a> documents using anchors, contributions, and
-   replacements.</li>
-</ul>
-
-<p>
-To learn more about each aspect of the markup, follow the links above or find the
-topics in the table of contents.
-</p>
-
-<p>
-This is demonstrated in the XHTML fragment shown below:
-</p>
-
-<hr>
-<pre>
-&lt;p&gt;
-This is a static paragraph.
-&lt;/p&gt;
-
-&lt;!-- This tag will be replaced with the referenced tag --&gt;
-<span class="highlight">&lt;include path="my.plugin.id/path/my_other_document.xhtml/element_id"/&gt;</span>
-
-&lt;ul&gt;
-   &lt;li&gt;
-      This is a static list item.
-   &lt;/li&gt;
-   &lt;li&gt;
-      This only shows when running on Windows and plugin com.myplugin is not installed.
-      <span class="highlight">&lt;enablement&gt;
-         &lt;systemTest property=&quot;osgi.os&quot; value=&quot;win32&quot;/&gt;
-         &lt;not&gt;
-            &lt;with variable=&quot;platform&quot;&gt;
-               &lt;test property=&quot;org.eclipse.core.runtime.isBundleInstalled&quot; args=&quot;com.myplugin&quot;/&gt;
-            &lt;/with&gt;
-         &lt;/not&gt;
-      &lt;/enablement&gt;</span>
-   &lt;/li&gt;
-&lt;/ul&gt;
-
-&lt;!-- An element with an id that can be replaced by another element --&gt;
-<span class="highlight">&lt;p id="my.paragraph"&gt;
-   This paragraph can be replaced because it has an id.
-&lt;/p&gt;</span>
-
-&lt;!-- A place where others can add content --&gt;
-<span class="highlight">&lt;anchor id="my.anchor.id"/&gt;</span>
-</pre>
-<hr>
-
-<h3>Content producers</h3>
-
-<p>
-A content producer is a mechanism for plugging-in Java code to produce the document
-content on-the-fly. Content producers are more powerful than XML annotations, but
-are more complex to use.
-</p>
-
-<p>
-Content producers are supported in the following areas of user assistance:
-</p>
-
-<ul>
-   <li>Welcome XML/XHTML</li>
-   <li>Help topics (any format)</li>
-   <li>Help table of contents</li>
-   <li>Help keyword index</li>
-   <li>Context-sensitive help</li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm
deleted file mode 100644
index 49923d3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_extensions.htm
+++ /dev/null

@@ -1,142 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Content extensions</title>
-</head>
-<body>
-
-<h2>Content extensions</h2>
-
-<p>
-A content extension is either a contribution of content into a known anchor (similar to an
-extension into an extension point), or the replacement of an existing element in a document. 
-</p>
-
-<h3>Contributing into anchors</h3>
-
-<p>
-Anchor elements (e.g. <code>&lt;anchor id=&quot;my_anchor&quot;/&gt;</code>) can be specified
-in any user assistance XML document, and represent places at which other components are allowed
-to extend this document. Specifying an anchor is as simple as adding the element in your markup.
-</p>
-
-<p>
-To contribute content into an anchor, you must write the content to be added in a separate XML
-file and hook it into the platform using one of two extension points. For <a
-href="ua_help.htm">help</a> or <a href="ua_cheatsheet.htm">cheat sheet</a> content, you must
-use the <a href="../reference/extension-points/org_eclipse_help_contentExtension.html"><code>
-org.eclipse.help.contentExtension</code></a> extension point. For <a href="ua_intro.htm">welcome
-(intro)</a> extensions, use
-<a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html"><code>
-org.eclipse.ui.intro.configExtension</code></a>. The table of contents markup also allows the
-special constructs <a href="ua_help_content_nested.htm"><code>link</code></a> and <a
-href="ua_help_content_nested.htm"><code>link_to</code></a> which perform a similar function
-to includes and contributions, but perform the additional operation of merging extra documents
-to index for searching.
-</p>
-
-<p>
-For example, let's say component A's documentation provides a listing of file formats it
-supports. If component B extends A's support to several more formats, you can place an
-anchor in A's list, and extend the list from B. For example:
-</p>
-
-<pre>
-   &lt;p&gt;The following list shows the supported formats:&lt;/p&gt;
-   &lt;ul&gt;
-      &lt;li&gt;Portable Network Graphics (.png)&lt;/li&gt;
-      &lt;li&gt;Joint Photographic Experts Group (.jpeg)&lt;/li&gt;
-      &lt;li&gt;Graphical Interchange Format (.gif)&lt;/li&gt;
-      
-      &lt;!-- Extra formats go here --&gt;
-      <font color="blue">&lt;anchor id="image_format_list"/&gt;</font>
-   &lt;/ul&gt;
-</pre>
-
-<p>
-Then component B can make a contribution to the anchor to add more formats
-to the list by specifying the following extension:
-</p>
-
-<pre>
-   &lt;extension point=&quot;org.eclipse.help.contentExtension&quot;&gt; 
-      &lt;contentExtension
-            file=&quot;path/to/extension.xml&quot;/&gt;
-   &lt;/extension&gt;
-</pre>
-
-<p>
-Where the file <code>path/to/extension.xml</code> might contain:
-</p>
-
-<pre>
-   &lt;contentExtension&gt;
-      &lt;contribution
-            content=&quot;docs/mydoc.xhtml#mycontent&quot;
-            path=&quot;/component_a_plugin/docs/doc_with_anchor.xhtml#anchorId&quot;&gt;
-      &lt;/contribution&gt;
-   &lt;/contentExtension&gt;
-</pre>
-
-<p>
-The element with the <code>id</code> attribute <code>mycontent</code> in document
-<code>docs/mydoc.xhtml</code> would contain the content you wish to contribute
-into the anchor. The result will be that when the user views the document, the extra content
-will appear at the anchor as though it was explicitly added into the original document.
-</p>
-
-<h3>Replacing content</h3>
-
-<p>
-Any XML element in a user assistance document that has an <code>id</code> attribute that is
-unique to that document can be replaced with any other element.
-</p>
-
-<p>
-As with contributions into anchors, to replace an element, you must write the new element to
-replace with in a separate XML file and hook it into the platform using one of two extension
-points. For <a href="ua_help.htm">help</a> or <a href="ua_cheatsheet.htm">cheat sheet</a> content,
-you must use the <a href="../reference/extension-points/org_eclipse_help_contentExtension.html">
-<code>org.eclipse.help.contentExtension</code></a> extension point. For <a href="ua_intro.htm">
-welcome (intro)</a> extensions, use
-<a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html"><code>
-org.eclipse.ui.intro.configExtension</code></a>.
-</p>
-
-<p>
-The only difference with replacements as opposed to contributions into anchors is the name of the
-XML element used in the markup; use the <code>replacement</code> element instead of
-<code>contribution</code> (or <code>replacementContent</code> in the case of welcome). For example:
-</p>
-
-<pre>
-   &lt;contentExtension&gt;
-      &lt;replacement
-            content=&quot;docs/mydoc.xml#myelement&quot;
-            path=&quot;/plugin.id/path/doc.xml#elementId&quot;&gt;
-      &lt;/replacement&gt;
-   &lt;/contentExtension&gt;
-</pre>
-
-<p>
-(Note the markup is different for welcome, as specified in the <a
-href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html"><code>
-org.eclipse.ui.intro.configExtension</code></a> extension point)
-</p>
-
-<h3>Path format</h3>
-
-<p>
-The format of the <code>path</code> attribute is <code>/pluginId/path/file.xml#elementId</code>,
-except welcome where it is <code>pageId/path/to/elementId</code> where the pageId is the welcome
-page id, and all other path segments are ids of container elements like groups, leading to the
-target element.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
deleted file mode 100644
index 3e11e79..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_filters.htm
+++ /dev/null

@@ -1,521 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Filters</title>
-
-<style type="text/css">
-	.deprecated {
-		color: #444444;
-	}
-	.warning {
-		color: red;
-	}
-	.highlight {
-		color: blue;
-	}
-</style>
-</head>
-<body>
-
-<h2>Filters</h2>
-
-<p>
-If some sections of a document (e.g. a list item in a XHTML help topic) should only be displayed
-to the user if certain conditions are met, you can specify an enablement expression declaring the
-criteria that must be met in order to display the element.
-</p>
-
-<p>
-Filters are specified by adding an <code>&lt;enablement&gt;</code> element as a <em>child</em>
-of the element that should conditionally be filtered. The syntax used is
-<a href="../reference/api/org/eclipse/core/expressions/package-summary.html#package_description">
-core expressions</a>, which is the same syntax used to filter menu contributions, etc from the UI.
-</p>
-
-<h3>System tests</h3>
-
-<p>
-Expressions check criteria by performing tests. One type of test is a system test, which tests
-a system property against an expected value. Some common system properties to test by are listed
-below:
-</p>
-
-<table border="1">
-   <tr>
-      <td>
-         <strong>Property</strong>
-      </td>
-      <td>
-         <strong>Meaning</strong>
-      </td>
-      <td>
-         <strong>Possible values</strong>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>osgi.os</code>
-      </td>
-      <td>
-         operating system
-      </td>
-      <td>
-         <code>win32, win32, linux, macosx, aix, solaris, hpux, qnx</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>osgi.ws</code>
-      </td>
-      <td>
-         windowing system
-      </td>
-      <td>
-         <code>win32, motif, gtk, photon, carbon</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>osgi.arch</code>
-      </td>
-      <td>
-         processor architecture
-      </td>
-      <td>
-         <code>x86, x86_64, ia64, ia64_32, ppc, PA_RISC, sparc</code>
-      </td>
-   </tr>
-</table>
-
-<p>
-Here are a few examples of system tests:
-</p>
-<pre>&lt;p&gt;
-   This paragraph should only be displayed on Windows.
-   <span class="highlight">&lt;enablement&gt;
-      &lt;systemTest property=&quot;osgi.os&quot; value=&quot;win32&quot;/&gt;
-   &lt;/enablement&gt;</span>
-&lt;/p&gt;
-
-&lt;p&gt;
-   This paragraph should *not* be displayed on GTK.
-   <span class="highlight">&lt;enablement&gt;
-      &lt;not&gt;
-         &lt;systemTest property=&quot;osgi.ws&quot; value=&quot;gtk&quot;/&gt;
-      &lt;/not&gt;
-   &lt;/enablement&gt;</span>
-&lt;/p&gt;
-
-&lt;p&gt;
-   This paragraph should only be displayed on PowerPC Macs.
-   <span class="highlight">&lt;enablement&gt;
-      &lt;systemTest property=&quot;osgi.os&quot; value=&quot;macosx&quot;/&gt;
-      &lt;systemTest property=&quot;osgi.arch&quot; value=&quot;ppc&quot;/&gt;
-   &lt;/enablement&gt;</span>
-&lt;/p&gt;
-</pre>
-
-
-<p>
-<em>Note: When several sub-expressions are listed with no boolean operator, they are
-by default ANDed together. See the complete
-<a href="../reference/api/org/eclipse/core/expressions/package-summary.html#package_description">
-expressions syntax</a> specification for more details.</em>
-</p>
-
-<h3>Property tests</h3>
-
-<p>
-In addition to system tests, you can test any property of an available object as long as
-there is a <a href="../reference/extension-points/org_eclipse_core_expressions_propertyTesters.html">
-property tester</a> available for it.
-</p>
-
-<p>
-Tests always perform their test on a property of some object, and each object has different
-properties you can test. User assistance provides two variables that are used to select
-the object to test on:
-</p>
-
-<ul>
-   <li><code>platform</code> - The underlying platform you're running on</li>
-   <li><code>workbench</code> - The UI workbench</li>
-</ul>
-
-<p>
-You can perform a test on one of these by using the <code>&lt;with&gt;</code> element,
-as shown below:
-</p>
-
-<pre>&lt;enablement&gt;
-   <span class="highlight">&lt;with variable=&quot;platform&quot;&gt;</span>
-      &lt;test property=&quot;<em>x</em>&quot; value=&quot;<em>y</em>&quot;/&gt;
-   <span class="highlight">&lt;/with&gt;</span>
-&lt;/enablement&gt;
-</pre>
-
-<p>
-Each property has a namespace, which is a prefix such as <code>org.eclipse.ui</code>
-that is used to minimize the chances of duplicate properties being defined by two
-components. The table below shows some common properties you can test by:
-</p>
-
-<table border="1">
-   <tr>
-      <td>
-         <strong>Property</strong>
-      </td>
-      <td>
-         <strong>Object (variable)</strong>
-      </td>
-      <td>
-         <strong>Meaning</strong>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>org.eclipse.core.runtime.product</code>
-      </td>
-      <td>
-         <code>platform</code>
-      </td>
-      <td>
-         tests if the expected value matches the currently active product's unique id
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>org.eclipse.core.runtime.isBundleInstalled</code>
-      </td>
-      <td>
-         <code>platform</code>
-      </td>
-      <td>
-         tests if the bundle with the symbolic name (e.g. <code>org.eclipse.help</code>)
-         specified as a single argument is installed on the platform
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>org.eclipse.ui.isActivityEnabled</code>
-      </td>
-      <td>
-         <code>workbench</code>
-      </td>
-      <td>
-         tests if the activity with the id specified as a single argument exists and
-         is currently enabled in the workbench
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>org.eclipse.ui.isCategoryEnabled</code>
-      </td>
-      <td>
-         <code>workbench</code>
-      </td>
-      <td>
-         tests if the category of activities with the id specified as a single argument
-         exists and is currently enabled in the workbench. A category is enabled if all its
-         activities are enabled
-      </td>
-   </tr>
-</table>
-
-<p>
-Here are a few examples using these properties:
-</p>
-
-<pre>&lt;p&gt;
-   This paragraph should only be displayed when running the Eclipse SDK.
-   <span class="highlight">&lt;enablement&gt;
-      &lt;with variable=&quot;platform&quot;&gt;
-         &lt;test property=&quot;org.eclipse.core.runtime.product&quot; value=&quot;org.eclipse.sdk.ide&quot;/&gt;
-      &lt;/with&gt;
-   &lt;/enablement&gt;</span>
-&lt;/p&gt;
-
-&lt;p&gt;
-   This paragraph should only be displayed when either the <code>com.myactivity.a</code> or
-   <code>com.myactivity.b</code> activity (or both) is enabled in the workbench.
-   <span class="highlight">&lt;enablement&gt;
-      &lt;with variable=&quot;workbench&quot;&gt;
-         &lt;or&gt;
-            &lt;test property=&quot;org.eclipse.ui.isActivityEnabled&quot; args=&quot;com.myactivity.a&quot;/&gt;
-            &lt;test property=&quot;org.eclipse.ui.isActivityEnabled&quot; args=&quot;com.myactivity.b&quot;/&gt;
-         &lt;or&gt;
-      &lt;/with&gt;
-   &lt;/enablement&gt;</span>
-&lt;/p&gt;
-
-&lt;p&gt;
-   This paragraph should only be displayed when the <code>com.mycategory</code> category
-   is enabled and the <code>com.mybundle</code> bundle is not installed.
-   <span class="highlight">&lt;enablement&gt;
-      &lt;with variable=&quot;workbench&quot;&gt;
-         &lt;test property=&quot;org.eclipse.ui.isCategoryEnabled&quot; args=&quot;com.mycategory&quot;/&gt;
-      &lt;/with&gt;
-      &lt;with variable=&quot;platform&quot;&gt;
-         &lt;not&gt;
-            &lt;test property=&quot;org.eclipse.core.runtime.isBundleInstalled&quot; args=&quot;com.mybundle&quot;/&gt;
-         &lt;/not&gt;
-      &lt;/with&gt;
-   &lt;/enablement&gt;</span>
-&lt;/p&gt;
-</pre>
-
-<p>
-<em>Note: Make sure you use the <code>value</code> and <code>args</code> attributes for the appropriate
-tests. In general, string properties like product will use <code>value</code> where boolean
-tests (<code>isSomethingTrue</code>) will use <code>args</code>. See the complete
-<a href="../reference/api/org/eclipse/core/expressions/package-summary.html#package_description">
-expressions syntax</a> specification for more details on how to write expressions.</em>
-</p>
-
-<h3>Defining your own test</h3>
-
-The core expressions framework allows you define your own test that can test
-on any arbitrary property of any object that is accessible through the variables defined for
-the context you're in. You do this by defining a
-<a href="../reference/extension-points/org_eclipse_core_expressions_propertyTesters.html">
-property tester</a>.
-
-<p>
-Note: The variables <code>platform</code> and <code>workbench</code> resolve to the
-<code>org.eclipse.core.runtime.Platform Class</code> object (we use the class object for
-&quot;static&quot; tests) and the singleton <code>org.eclipse.ui.IWorkbench</code> instance,
-respectively. Your property tester must declare one of these two classes for its type.
-</p>
-
-<h3>
-Using Filters in Table of Contents (TOC) Files</h3>
-
-<p>
-Filters can be used in Table of Contents files to filter out content that does 
-not apply to the current installation. The example below is a topic which is 
-only included in the TOC if plugin x.y.z is running.</p>
-
-<pre class="highlight">    &lt;topic href=&quot;html/subtopic.html&quot; label=&quot;This topic is shown only if plugin x,y.z is running&quot;&gt;
-      &lt;enablement&gt;
-      &lt;with variable=&quot;platform&quot;&gt;
-          &lt;test property=&quot;org.eclipse.core.runtime.isBundleInstalled&quot; args=&quot;x.y.z&quot;/&gt;
-      &lt;/with&gt;
-      &lt;/enablement&gt;
-    &lt;/topic&gt;</pre>
-
-<h3>Filter attributes/elements <span class="warning">(deprecated)</span></h3>
-
-<p>
-Prior to the 3.3, filters were specified using <code>filter</code> attributes or elements.
-The use of these filters is now deprecated, and you should use expressions (described
-above) instead.
-</p>
-
-<p>The table below contains a complete list of all the filter properties and
-their possible values for use with filter elements and attributes.</p>
-
-<span class="warning">(deprecated)</span>
-<table class="deprecated" border="1">
-   <tr>
-      <td>
-         <b>Property</b>
-      </td>
-      <td>
-         <b>Meaning</b>
-      </td>
-      <td>
-         <b>Possible Values</b>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>os</code>
-      </td>
-      <td>
-         operating system
-      </td>
-      <td>
-         <code>win32, win32, linux, macosx, aix, solaris, hpux, qnx</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>ws</code>
-      </td>
-      <td>
-         windowing system
-      </td>
-      <td>
-         <code>win32, motif, gtk, photon, carbon</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>arch</code>
-      </td>
-      <td>
-         processor architecture
-      </td>
-      <td>
-         <code>x86, x86_64, ia64, ia64_32, ppc, PA_RISC, sparc</code>
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>product</code>
-      </td>
-      <td>
-         eclipse product identifier
-      </td>
-      <td>
-         Any product identifier (e.g., for SDK, <code>org.eclipse.sdk.ide</code>)
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>plugin</code>
-      </td>
-      <td>
-         plug-in presence
-      </td>
-      <td>
-         Any plug-in identifier (e.g. <code>org.eclipse.help</code>)
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>category</code>
-      </td>
-      <td>
-         category of activities
-      </td>
-      <td>
-         Any activity category identifier (e.g. for Team category,
-         <code>org.eclipse.categories.teamCategory</code>)
-      </td>
-   </tr>
-   <tr>
-      <td>
-         <code>activity</code>
-      </td>
-      <td>
-         activity (capability)
-      </td>
-      <td>
-         Any activity identifier (e.g. for CVS Support activity, 
-         <code>org.eclipse.team.cvs</code>)
-      </td>
-   </tr>
-</table>
-
-<p>If the name does not match any pre-defined property, the help system will
-use the JVM's system property of that name. For example, you can pass in any
-user-defined property at launch, such as <code>-Dlocation=paris,france</code>
-and filter by that property.</p>
-
-<p>There are two ways to specify filters on an element; using attributes, or
-elements.</p>
-
-<h3>Filter Attribute <span class="warning">(deprecated)</span></h3>
-
-<p>The first form is to add a <span class="highlight"><code>filter</code></span> attribute
-to the element. The general form is:</p>
-
-<pre>   &lt;element <span class="highlight">filter="[name][operator][value]"</span>&gt;
-      Some text.
-   &lt;/element&gt;
-</pre>
-
-<p>The <span class="highlight"><code>name</code></span> is the name of the property
-by which to filter, for example, <code>os</code> for operating system. The
-<span class="highlight"><code>operator</code></span> is either <code>=</code> to denote
-a <i>match</i> (exact match, case sensitive), or <code>!=</code> to denote <i>does
-not match</i>. The <span class="highlight"><code>value</code></span> is what the property
-should (or shouldn't) match. For example, for <code>os</code>, one of the possible
-values is <code>win32</code> (Windows). A complete list of filter properties and their
-values is available in a table below.</p>
-
-<p>The example below shows how to display a paragraph of text in an XHTML document
-when running on Linux only.</p>
-
-<pre>   &lt;p filter="os=linux"&gt;
-      This message will only appear when viewed on Linux.
-   &lt;/p&gt;
-</pre>
-
-<p>In this second example, the link will only appear when plugin
-<code>com.my.plugin</code> is not installed:</p>
-
-<pre>   &lt;a href="..." filter="plugin!=com.my.plugin"&gt;
-      Click here to download plugin com.my.plugin.
-   &lt;/a&gt;
-</pre>
-
-<h3>Filter Element <span class="warning">(deprecated)</span></h3>
-
-<p>The second form is to use a <code>filter</code> element as a <i>child</i> of
-the element you wish to filter. This form is slightly longer than the attribute
-form, but it is more powerful because you can specify any number of filters on an
-element. The general form is:</p>
-
-<pre>   &lt;element attribute="value"&gt;
-      <span class="highlight"><code>&lt;filter name="[name]" value="[modifier][value]"/&gt;</code></span>
-   &lt;/element&gt;
-</pre>
-
-<p>The <span class="highlight"><code>name</code></span> and <span class="highlight"><code>
-value</code></span> here are the same as with the attribute. However, since they
-are separated, we need another way to specify whether or not it should match. By
-default, if you do not provide a <span class="highlight"><code>modifier</code></span>,
-match is assumed. If it should <i>not</i> match, set the modifier to "<code>!</code>
-"</p>
-
-<p>Here is the first example shown above in the second form:</p>
-
-<pre>   &lt;p&gt;
-      &lt;filter name="os" value="linux"/&gt;
-      This message will only appear when viewed on Linux.
-   &lt;/p&gt;
-</pre>
-
-<p>And the second example:</p>
-
-<pre>   &lt;a href="..."&gt;
-      &lt;filter name="plugin" value="!com.my.plugin"/&gt;
-      Click here to download plugin com.my.plugin.
-   &lt;/a&gt;
-</pre>
-
-<h3>Infocenter</h3>
-
-<p>
-Filtering support is turned <strong>off</strong> when running help in
-<a href="ua_help_setup_infocenter.htm">infocenter</a> mode, causing all content,
-including filtered content, to be visible. If you intend to host your
-documentation in both workbench and infocenter modes, you should use filters in
-a way that makes sense even if filtering is turned off.
-</p>
-
-<h3>Where can I use filters?</h3>
-
-<p>
-Filtering can be used in any XML-based user assistance document, such as help XHTML topics,
-help table of contents, welcome pages, cheat sheets, etc. You cannot use filtering in
-HTML documents.
-</p>
-
-<p>
-In any case, you <b>must not</b> place filters on any element where removing that
-element would result in <i>invalid</i> XML. For example, you should not place a
-filter on the <code>html</code> element in XHTML, because without that element it
-is no longer valid
-XHTML.
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
deleted file mode 100644
index 04327a8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_dynamic_includes.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Includes</title>
-</head>
-<body>
-
-<h2>Includes</h2>
-
-<p>
-Includes are used include parts of other documents into your document. The
-markup specifies the document and element to include, and before the document is
-shown to the user, the include element will be <i>replaced</i> with the element
-referred to.
-</p>
-
-<p>
-For example, you may wish to show a copyright at the end of each help document
-you provide. You could copy and paste it in each document, but if the copyright
-changes (e.g. the copyright year), you have to modify <i>every</i> one of your
-documents.
-</p>
-
-<p>
-Instead, you can place the copyright in a separate XHTML file called <code>
-copyright.xhtml</code> and assign it a unique identifier, like this:
-</p>
-
-<pre>
-   &lt;p <font color="blue">id="copyright"</font>&gt;
-      Copyright 2006 My Company. All rights reserved.
-   &lt;/p&gt;
-</pre>
-
-<p>
-Then for each document, simply include the copyright paragraph:
-</p>
-
-<pre>
-   &lt;p&gt;
-      This is my document. It should have a copyright at the end.
-   &lt;/p&gt;
-   <font color="blue">&lt;include path="my.plugin.id/path/copyright.xhtml/copyright"/&gt;</font>
-</pre>
-
-<p>
-Before the document is sent to the browser to be displayed, the <code>include</code>
-element will be <i>replaced</i> by the copyright paragraph.
-</p>
-
-<h3>Where can I use includes?</h3>
-
-<p>
-See below for a list of the document types in which includes can be used. The
-format of the <code>path</code> element of the include <i>depends on the type of
-document you're including from</i>. As you can see in the example above,
-the format for XHTML help documents is <code>
-"&lt;plugin_id&gt;/&lt;path_to_file&gt;/&lt;element_id&gt;"</code>. Refer to the links
-below for the format for your document type.
-</p>
-
-<ul>
-   <li><a href="ua_intro_xhtml.htm">Welcome/Intro XML/XHTML format</a></li>
-   <li><a href="ua_help_content_xhtml.htm#include_format">Help XHTML format</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm
deleted file mode 100644
index 20ae8be..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Help</title>
-</head>
-<body>
-
-<h2>Help</h2>
-
-<P >
-The Eclipse platform's help facilities provide you with the raw building blocks to structure and contribute
-documentation to the platform. It does not dictate structure or granularity of documentation.
-You can choose the tools and structure for your documentation that suits your
-needs.&nbsp; The help plug-in allows you to describe your documentation
-structure to the platform using a table of contents (toc) file.</P>
-<P >Your plug-in's online help is contributed using the <a href="../reference/extension-points/org_eclipse_help_toc.html"> <b> org.eclipse.help.toc</b></a> extension point. You can either contribute the online help as part of your code plug-in or provide it separately in its own documentation plug-in.</P>
-<P >
-Separating the documentation into a separate plug-in is beneficial in those situations where the code and documentation teams are different groups or where you want to reduce the coupling between the documentation and code. </P>
-<P >
-Advanced features of the help system include context-sensitive help with
-reference links and the ability to invoke platform
-code from the documentation.&nbsp;A help browser lets you view, print, and 
-search your documentation. Since 3.1, the new Help view adds dynamic help and 
-federated information search capability.</P>
-<P >
-The best way to demonstrate the contribution of help is to create a
-documentation plug-in.</P>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
deleted file mode 100644
index 01c4541..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Help content</title>
-</head>
-<body>
-
-<h2>Help content</h2>
-
-<p><b>Building a help plug-in</b></p>
-
-<P >
-In this example, we assume that a documentation author has already supplied you with the raw documentation in the form of HTML files. The granularity
-and structure of these files is completely up to the documentation team. Once the documentation is delivered, setting up the plug-in and topics can be done independently.</P>
-
-<P >
-We start by assuming that the documentation has already been provided in the following tree.</P>
-<pre>
-   html/
-      concepts/
-         concept1.html
-         concept1_1.html
-         concept1_2.html
-      tasks/
-         task1.html
-         task2.html
-         task3_1.html
-         task3_2.html
-      ref/
-         ref1.html
-         ref2.html
-</pre>
-<P >
-We will assume that the plug-in name is <b>com.example.helpexample</b>.</P>
-<P >
-The first step is to create a plug-in directory, <b>com.example.helpexample</b> underneath the platform
-<b>plugins</b> directory. The <b>doc\</b>
-sub tree shown above should be copied into the directory. </P>
-<P >
-Documentation plug-ins need a manifest just like code plug-ins. The following markup defines the documentation plug-in.</P>
-
-<pre>
-   &lt;?xml version=&quot;1.0&quot; ?&gt;
-   &lt;plugin name=&quot;Online Help Sample&quot;
-      id=&quot;com.example.helpexample&quot;
-      version=&quot;1.0&quot;
-      provider-name=&quot;MyExample&quot; /&gt;
-</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
deleted file mode 100644
index b40c80c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Active help</title>
-</head>
-<body>
-
-<h2>Active help</h2>
-
-<p>Active help is the ability to invoke Eclipse code from on-line
-documentation.&nbsp;It is implemented by including some JavaScript in your
-documentation that describes a class that should be run inside the Eclipse
-platform. </p>
-
-<p>For example, instead of writing, &quot;Go to the Window Menu and open the
-message dialog,&quot; your on-line help can include a link that will open your
-application's message dialog for the user.&nbsp; Active help links look like hyperlinks in
-the on-line help.</p>
-
-<p>Below is an active help link that opens the cheatsheet "Check out a CVS project".&nbsp;
-We will take a look at how to create and reference your own actions.</p>
-
-<p><a href='javascript:liveAction(
-	"org.eclipse.ui.cheatsheets", 
-	"org.eclipse.ui.cheatsheets.OpenCheatSheetFromHelpAction",
-	"org.eclipse.platform.cvs.checkout")'>Open a cheatsheet.</a></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
deleted file mode 100644
index a6aa5b7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_action.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Writing the help action</title>
-</head>
-<body>
-
-<h3>Writing the help action</h3>
-
-<p>The interface <a href="../reference/api/org/eclipse/help/ILiveHelpAction.html"><b>ILiveHelpAction</b></a>
-is used to build an active help action.</p>
-
-
-<p>It is straightforward to implement an <a href="../reference/api/org/eclipse/help/ILiveHelpAction.html"><b>ILiveHelpAction</b></a><b>.</b>&nbsp;
-You must implement two methods.</p>
-
-
-<ul>
-  <li><b>run()</b> - This method is called to run the live help action.&nbsp;
-    This method will be called by the help system from a non-UI thread, so UI
-    access must be wrapped in a <b><a href="../reference/api/org/eclipse/swt/widgets/Display.html">Display.syncExec()</a></b>
-    method.&nbsp;&nbsp;</li>
-  <li><b>setInitializationString(String)</b> - This method is called to
-    initialize your action with a String data parameter you can specify in the
-    HTML which runs the JavaScript <b>liveAction</b>.&nbsp;&nbsp;
-If you don't need initialization data, you can just implement
-this method to do nothing.&nbsp; This method is called before <b>run()</b>.</li>
-</ul>
-
-
-<p>Here is a simple implementation of a live help action that opens a message
-dialog. We don't need any information from the JavaScript, so the
-initialization data is ignored.</p>
-
-
-<pre>package org.eclipse.platform.doc.isv.activeHelp;
-
-import org.eclipse.help.ILiveHelpAction;
-import org.eclipse.jface.dialogs.MessageDialog;
-import org.eclipse.swt.widgets.*;
-import org.eclipse.ui.*;
-/**
- * Sample Active Help action.
- */
-public class ActiveHelpOpenDialogAction implements ILiveHelpAction {
-
-     public void setInitializationString(String data) {
-          // ignore the data.  We do not use any javascript parameters.
-     }
-
-     public void run() {
-          // Active help does not run on the UI thread, so we must use syncExec
-          Display.getDefault().syncExec(new Runnable() {
-               public void run() {
-                    IWorkbenchWindow window =
-                         PlatformUI.getWorkbench().getActiveWorkbenchWindow();
-                    if (window != null) {
-                         // Bring the Workbench window to the top of other windows;
-                         // On some Windows systems, it will only flash the Workbench
-                         // icon on the task bar
-                         Shell shell = window.getShell();
-                         shell.setMinimized(false);
-                         shell.forceActive();
-                         // Open a message dialog
-                         MessageDialog.openInformation(
-                              window.getShell(),
-                              &quot;Hello World.&quot;,
-                              &quot;Hello World.&quot;);
-                    }
-               }
-          });
-     }
-}</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
deleted file mode 100644
index efbef57..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_debug.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Tips for debugging active help</title>
-</head>
-<body>
-
-<h2>Tips for debugging active help</h2>
-
-
-<p>The code and markup that triggered our active help link looks pretty
-straightforward.&nbsp; But what do you do if your active help link doesn't seem
-to work?</p>
-
-
-<h4>Test your action ahead of time</h4>
-
-
-<p>If your action implementation is fairly involved, you should invoke the
-action yourself with some test code inside Eclipse.&nbsp; This way, you'll know
-that the action is error-free before invoking it from the JavaScript.&nbsp; </p>
-
-
-<h4>Ensure the JavaScript is running</h4>
-
-
-<p>You can modify &quot;<b>liveHelp.js</b>&quot; (make a copy of this from the plugins/org.eclipse.help
-plugin and change your <code>script</code> statement to refer to your local copy)
-to include a call to the <b>alert</b> function as the first statement in the <b>liveAction</b>
-function:</p>
-
-
-<pre>function liveAction(pluginId, className, argument)
-{
-<b>	alert(&quot;liveAction called&quot;);
-	...</b></pre>
-
-
-<p>The <b>alert</b> function opens a warning dialog in the browser and can be
-used to verify that the <b>liveAction</b> was properly invoked in your
-HTML.&nbsp; If you don't see a warning dialog when you click on your help link,
-then you have a problem in the HTML markup.</p>
-
-
-<h4>Debug the active help action</h4>
-
-
-<p>Once you know that the JavaScript is running, you can debug your action from
-inside Eclipse.&nbsp; To do this, you can set a breakpoint in your help action
-class and start up a self-hosted Eclipse instance.&nbsp; You must test your
-active help with the Help browser from the newly launched Eclipse instance, not
-from your host instance, since the JavaScript from your help HTML calls a
-servlet on the Eclipse help server that launched the browser.</p>
-
-
-<p>If nothing happens after you've set up the breakpoint and clicked on the
-active help link, it's likely that your plug-in and active help class were not
-correctly specified in the JavaScript.&nbsp; </p>
-
-
-<p>Once you've managed to stop at the breakpoint in your action, you can debug
-the action as you would any other Java code.</p>
-
-
-<h4>Make sure your UI code is wrapped in Display.syncExec</h4>
-
-
-<p>A common runtime problem is improperly accessing UI code from the thread that
-invokes the active help.&nbsp; If your live help action came from code that ran
-originally in a UI thread, it will need to be modified to handle the fact that
-it is running from a non-UI thread.&nbsp; </p>
-
-
-<pre>public void run() {
-		// Active help does not run on the UI thread, so we must use syncExec
-		Display.getDefault().syncExec(new Runnable() {
-							public void run() {
-								//do the UI work in here;
-							}
-		});		
-	}
-
-</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
deleted file mode 100644
index 3b33e5b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_active_invoke.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Invoking the action from HTML</title>
-</head>
-<body>
-
-<h2>Invoking the action from HTML</h2>
-
-<P>
-To include active help links in your documentation, you must first declare the
-use of the supporting JavaScript code. The live help JavaScript is located in the <b>org.eclipse.help</b>
-plug-in.&nbsp; You refer to it using the help system's <a href="ua_help_content_files.htm#help_plugin_files_xref">cross
-plug-in referencing</a> technique. This script reference should be placed in the <b>HEAD</b> section of your HTML:
-</P>
-
-<pre >&lt;script language=&quot;JavaScript&quot; src=&quot;PLUGINS_ROOT/org.eclipse.help/livehelp.js&quot;&gt; &lt;/script&gt;</pre>
-
-<P >
- In the body of your documentation, you invoke the liveAction script.&nbsp;&nbsp; </P>
-
-
-<pre >&lt;a href='javascript:liveAction(
-	&quot;org.eclipse.platform.doc.isv&quot;, 
-	&quot;org.eclipse.platform.doc.isv.activeHelp.ActiveHelpOpenDialogAction&quot;,
-	&quot;&quot;)'&gt;Click here for a Message.&lt;/a&gt;</pre>
-
-
-<P >The parameters for <b>liveAction </b> are&nbsp; </P>
-
-
-<ul>
-  <li> the ID of the plug-in that
-contains the action</li>
-  <li>the name of the class that implements the action</li>
-  <li>the String that will be passed to the live help action using <b>setInitializationString</b>.&nbsp;
-    We don't need to pass any information from the HTML page, so we just
-    pass an empty string.</li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_child_links.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_child_links.htm
deleted file mode 100644
index bc3584d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_child_links.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adding Child Links to Help Pages</title>
-</head>
-<body>
-
-<h2>Adding Child Links to Help Pages</h2>
-
-<p>
-The Eclipse Help System recognizes two special comments in the source code which can be used to 
-cause child links to appear in help topics. This is useful in the case of a help topic which is
-the parent of an anchor. 
-</p>
-<p>
-If the sequence <pre>&lt;!--INSERT_CHILD_LINKS--&gt;</pre> appears in the source code it will be replaced
-with html containing hyperlinks to all child topics.
-<p>
-<p>
-If the sequence <pre>&lt;!--INSERT_CHILD_LINK_STYLE--&gt;</pre> appears in the source code it will be replaced
-by either <code>"has_child_topics"</code> or <code>"no_child_topics"</code> depending on whether or not
-the topic has children. This can be used to assign a style to a section of html so that it will only be
-shown if the topic has children.
-<p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
deleted file mode 100644
index 742a4b7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command.htm
+++ /dev/null

@@ -1,130 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Embedding commands in help</title>
-</head>
-<body>
-
-<h2>Embedding commands in help</h2>
-
-<p>It is possible to create links to workbench commands in help content.  When
-the user clicks the link, the command will be executed.  This feature is similar
-to <a href="ua_help_content_active.htm">Active Help</a> in that it uses JavaScript to bridge between the documentation
-HTML and the Eclipse Java runtime.  Also like Active Help, the command framework is extensible;
-so you can contribute new commands with interesting behaviors.
-However, unlike Active Help, there are a large number of useful commands already defined
-in the workbench and more are being added all the time.  This should be appealing to
-documentation authors because linking to an existing command does not require
-writing any Java code.
-</p>
-<p>
-Command links can be used to:
-</p>
-<ul>
-<li>
-Open a specific preference page, such as
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Appearance</b></a>.
-
-</li>
-<li>
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-Select a new perspective</a>
-
-or switch to a pre-determined perspective like the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaBrowsingPerspective)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Java Browsing</b></a>.
-
-perspective
-</li>
-<li>
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-Select a view to open</a>
-
-or open a pre-determined view like the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Bookmarks</b></a>.
-
-view
-</li>
-<li>
-Open wizards like the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.pde.ui.NewProjectWizard)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>New Plug-in Project</b></a>
-
-wizard and the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.ui.wizards.export.Preferences)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Export Preferences</b></a>.
-
-wizard
-</li>
-<li>
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.jdt.helloworld)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-Open a Cheat Sheet</a>.
-
-</li>
-<li>
-Open a
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.dialogs.openMessageDialog(imageType=3,buttonLabel2=Maybe,title=Opinion Poll,message=Do you like command links?,buttonLabel0=Yes,defaultIndex=0,buttonLabel1=No)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-message dialog</a>.
-
-</li>
-<li>
-Open the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>About Eclipse SDK</b></a>
-
-dialog.
-</li>
-<li>
-And much more!
-</li>
-</ul>
-
-<p>
-To get an idea of the range of commands available, look at the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Keys</b></a>
-
-preference page. This page is used to bind key sequences to commands
-so it shows the list of available commands.  <i>Note that not every command will do something useful from
-help content.  Many commands are designed to work within a somewhat narrow context (like a particular view,
-or expecting a certain type of selection).</i>
-</p>
-
-<p>
-If you want to define your own commands, refer to the documentation for the
-<a href="../reference/api/org/eclipse/core/commands/package-summary.html"><tt>org.eclipse.core.commands</tt></a> API package
-and the <a href="../reference/extension-points/org_eclipse_ui_commands.html"><tt>org.eclipse.ui.commands</tt></a> and
-<a href="../reference/extension-points/org_eclipse_ui_handlers.html"><tt>org.eclipse.ui.handlers</tt></a> extension-points.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
deleted file mode 100644
index 6320ce0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_command_authoring.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Authoring a command link</title>
-</head>
-<body>
-
-<h2>Authoring a command link</h2>
-
-<P>
-To include command links in your documentation, you must first declare the
-use of the supporting JavaScript code. The live help JavaScript is located in the <b>org.eclipse.help</b>
-plug-in.&nbsp; You refer to it using the help system's <a href="ua_help_content_files.htm#help_plugin_files_xref">cross
-plug-in referencing</a> technique. This script reference should be placed in the <b>HEAD</b> section of your HTML:
-</P>
-
-<pre >&lt;script type=&quot;text/javascript&quot; src=&quot;PLUGINS_ROOT/org.eclipse.help/livehelp.js&quot;&gt;
-&lt;/script&gt;</pre>
-
-<P>
-Now in the body of your documentation you may invoke the <b>executeCommand</b> function.
-Here is an example:
-</P>
-
-<pre>&lt;a href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'&gt;
-Open the About dialog&lt;/a&gt;</pre>
-
-<P>
-The parameter for the <b>executeCommand</b> function is a serialized
-<a href="../reference/api/org/eclipse/core/commands/ParameterizedCommand.html">
-<b>ParameterizedCommand</b></a>.
-See the
-<a href="../reference/api/org/eclipse/core/commands/ParameterizedCommand.html#serialize()">
-<b>ParameterizedCommand.serialize()</b></a> method for full details on this format.
-</P>
-
-<P>
-The example above shows the bare minimum required to embed a command in an HTML link.
-The Eclipse documentation supplements this with two extra pieces of information.
-First a <tt>class</tt> attribute is specified to allow for tuning the look of the link
-via CSS.  Second, an image tag is included before the link text.  The image serves
-to distinguish command links from ordinary links to other HTML pages.  Supplementing
-our initial example with these two extra features will look like this:
-</P>
-
-<pre>&lt;a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'&gt;
-&lt;img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"&gt;
-Open the About dialog&lt;/a&gt;</pre>
-
-<P>
-In the examples above, the About dialog command does not require any parameters, so the
-serialization is merely its command id: <tt>org.eclipse.ui.help.aboutAction</tt>.
-Below is another example showing a command with a parameter.  Note the command id is
-followed by the parameter id and value in parentheses:
-</P>
-
-<pre>&lt;a href='javascript:executeCommand(
-	"org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'&gt;
-	Show a preference page&lt;/a&gt;</pre>
-
-<P>
-Another example demonstrates that multiple parameters are possible.  They are comma
-separated and the order of the parameters is not important.
-</P>
-
-<pre>&lt;a href='javascript:executeCommand(
-	"org.eclipse.ui.dialogs.openMessageDialog(imageType=3,buttonLabel2=Maybe,title=Opinion Poll,message=Do you like command links?,buttonLabel0=Yes,defaultIndex=0,buttonLabel1=No)")'&gt;
-	Open a message dialog&lt;/a&gt;</pre>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
deleted file mode 100644
index ca25e96..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_files.htm
+++ /dev/null

@@ -1,133 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Help server and file locations</title>
-</head>
-<body>
-
-<h2>Help server and file locations</h2>
-
-<P >
-The platform utilizes its own documentation server to provide the actual web pages
-for your plug-in's documentation.&nbsp; A custom server allows the platform to handle HTML content
-in a browser independent manner and to provide plug-in aware support.&nbsp; The
-main difference to you as a plug-in developer is that you have a little more
-flexibility in the way you structure your files and specify your links. </P>
-<P >
-A documentation plug-in can run from a jar file or unpacked into plug-in directory
-during installation. A plug-in archive jar is not
- expanded into a plug-in directory when value of <code>unpack</code> attribute
- of the <code>plugin</code> element is specified as true in the <a href="../reference/misc/feature_manifest.html">feature
- manifest</a>. In such plug-in, the documentation is compressed in the plug-in's
-jar, together with other plug-in files. </P>
-<P >In plug-ins that run unpacked, the documentation can be delivered
-  in a zip file, avoiding problems that may result
-  when a large number of files
-  are
-  present
-  in a plug-in
-  directory.
-  In
-  our example
-plug-in, we created a sub-directory called <b>html</b>.&nbsp;
-Alternatively, we could have placed our html files into a zip file called
-<b>doc.zip</b>.&nbsp; This zip file must mimic the file
-structure underneath the plug-in directory.&nbsp; In our case, it must contain
-the sub-directory <b>html</b> and all the contents
-underneath <b>html</b>.</P>
-<P >Note that for plug-ins running from a jar, there is no need for documentation
-  to be additionally contained in doc.zip, and such set-up of doc.zip in an unexploded
-   plug-in jar
-is not supported by help system</P>
-<P >When resolving file names in a plug-in that runs unpacked, the help server
-  looks in the <b>doc.zip</b>
-file for documents before it looks in the plug-in directory itself.&nbsp; When
-used as a link, the argument in an
-<b> href</b> is assumed to be relative to the current plug-in.&nbsp; Consider
-the following link: </P>
-
-
-<pre>   &lt;topic label=&quot;Ref1&quot; href=&quot;html/ref/ref1.html&quot;/&gt;</pre>
-
-
-<P>The help plug-in will look for this file as follows: </P>
-
-
-<ul>
-  <li>look in <b> doc.zip</b> for the file <b>/html/ref/ref1.html</b></li>
-  <li>look for the file <b>ref1.html</b> in the <b>/html/ref </b>sub-directory structure underneath the plug-in
-    directory.</li>
-</ul>
-<P >A fully qualified link can be used to refer to any content on the web.&nbsp; </P>
-
-
-<pre >   &lt;topic label=&quot;Ref1&quot; href=&quot;http://www.example.com/myReference.html&quot;/&gt;</pre>
-
-
-<h4 >National language and translated documentation</h4>
-
-
-<p >The platform help system uses the same national language directory lookup
-scheme used by the rest of the platform for finding translated files.&nbsp; (See
-<a href="product_def_nl.htm#platform">Locale specific files</a> for an
-explanation of this directory structure.)&nbsp; If you are using a <b>doc.zip</b>
-file, you should produce a <b>doc.zip</b> file for <b>each</b> locale and place
-it inside the correct locale directory.&nbsp; (You should not replicate the <b>nl</b>
-locale directory structure inside the doc.zip file.)</p>
-<p >In addition to locale specific directories, help system checks windowing
-  system and operating system directories when locating help resources. Look-up
-  is performed in the following order: <strong>ws</strong>, <strong>os</strong>, <strong>nl</strong> subdirectories, then
-  the root of the plug-in, until the resource is located. Documents, and other
-  resource, like images which differ between system, should be placed under ws
-  or os directories for specific platform.</p>
-  
-<h4 ><a name="help_plugin_files_xref">Cross plug-in referencing</a></h4>
-
-<P >The <b>href</b> argument can also refer to content from another
-plug-in.&nbsp; This is done by using a special cross plug-in referencing
-notation that is resolved by the help server: </P>
-
-<pre >   &lt;topic label=&quot;Ref1&quot; href=&quot;<b>PLUGINS_ROOT/another_plugin_id</b>/ref/ref1.html&quot;/&gt;</pre>
-
-<p>
-Here <code><b>PLUGINS_ROOT</b></code> will be resolved at runtime and replaced with
-the root directory for the plugins. You can specify your own plug-in id for
-<code><b>another_plugin_id</b></code>. For example, you could link to this chapter
-of the programmer's guide using the following topic:
-</p>
-
-<pre >   &lt;topic label=&quot;Help Chapter in Platform Doc&quot; href=&quot;<b>PLUGINS_ROOT/org.eclipse.platform.doc.isv/guide/help.html</b>&quot;/&gt;</pre>
-
-<p>
-Prior to 3.2, references to documents in other plug-ins were made by using '..'
-to go up to the plug-in level, then referencing the plug-in Id followed by the
-HREF to the topic inside the plug-in. The recommended way to do this now is
-to use <code>PLUGINS_ROOT</code> instead of '..'. Using this variable avoids
-avoids these up/down trips in references, and can be used for all the resource
-URLs in the help documents (images, links, CSS files, java script files etc.)
-</p>
-
-<p class="Note">Note:&nbsp; When referencing content from another plug-in, be
-sure to use the plug-in's <b>id</b>, as declared in its <b>plugin.xml </b>file,
-not its directory name.&nbsp; While these are often the same in practice, it's
-important to check that you are using the id and not the directory name.</p>
-
-<h4 >Referencing the Product Plug-in.</h4>
-
-<p>Branding information is often placed in a plug-in defining a
-  product as explained in <a href="product_def.htm">Defining a Product</a>. Help
-  resources in the product plug-in can be referenced from the table of contents
-  or topics using special identifier <code><b>PRODUCT_PLUGIN</b></code> for the
-  plug-in ID. For example,</p>
-<pre >   href=&quot;PLUGINS_ROOT/<b>PRODUCT_PLUGIN</b>/book.css&quot;</pre>
-<p>refers to a style sheet residing in the plug-in for the currently running
-product.
-  </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
deleted file mode 100644
index 8e6ec56..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_manifest.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Completing the plug-in manifest</title>
-</head>
-<body>
-
-<h2>Completing the plug-in manifest</h2>
-
-<P >
-We started this example by creating our plug-in and document files. Next we created
-toc files to describe the organization of our content.
-The remaining piece of work is to pull everything together into a master toc and
-update our <b> plugin.xml</b> to actually contribute the master toc.&nbsp; </P>
-
-<P >
- We start by creating a <b>toc.xml</b> to contribute the three tocs we created
- initially.&nbsp; Instead of providing an <b>href</b> for each topic, we use the
- <b>link</b> attribute to refer to our existing toc files. </P>
-
-<pre>&lt;toc label=&quot;Online Help Sample&quot; topic=&quot;html/book.html&quot;&gt;
-	&lt;topic label=&quot;Concepts&quot;&gt;
-		&lt;link toc=&quot;toc_Concepts.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Tasks&quot;&gt;
-		&lt;link toc=&quot;toc_Tasks.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Reference&quot;&gt;
-		&lt;link toc=&quot;toc_Ref.xml&quot; /&gt;
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-
-<P >
- Then we update the <b>plugin.xml</b> to contribute our master toc: </P>
-<pre>
-   &lt;extension point=&quot;org.eclipse.help.toc&quot;&gt;
-      &lt;toc file=&quot;toc.xml&quot; <b>primary</b>=&quot;true&quot; /&gt;
-   &lt;/extension&gt;</pre>
-<P >Note the use of the <b>primary</b> attribute.&nbsp; Setting this attribute
-to true indicates that the toc should always appear in the navigation, even if
-it is not referenced by any other toc.&nbsp; This way, our &quot;master&quot;
-toc is always guaranteed to show up in the topics list.&nbsp; It appears at the
-top level list of books since no other toc references it.&nbsp;<I><BR>
-Note</I>: 
-If more files were associated with this toc but not present in the navigation, but just linked from other topics, then to have those topics available to the search engine we would have to use the <B>extradir</B> attribute in the toc.</P>
-<P >Finally, we contribute our individual toc files. </P>
-<pre>   &lt;extension point=&quot;org.eclipse.help.toc&quot;&gt;
-       &lt;toc file=&quot;toc_Concepts.xml&quot; /&gt;
-       &lt;toc file=&quot;toc_Tasks.xml&quot; /&gt;
-       &lt;toc file=&quot;toc_Reference.xml&quot; /&gt;
-   &lt;/extension&gt;</pre>
-<P >These toc files will not appear in the top level list of books because we
-did not set the <b>primary</b> attribute.&nbsp; Toc files that are not
-designated as primary will only appear in the documentation web if they are
-referred to from some toc that is a primary toc or is linked in by a primary
-toc. </P>
-
-<P >That's it. If you copy your plug-in directory to the platform's <b> plugins</b> directory, start the platform, and choose
-<b> Help-&gt;Help Contents</b>, you should see your example appear in the list
-of books. If you click on the "Online Help Sample", you'll see your toc structure:</P>
-
-<p><img src="images/help_contents.png" alt="On-line help browser with sample book structure" border="0" ></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
deleted file mode 100644
index c1f5064..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_nested.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Building nested documentation structures</title>
-</head>
-<body>
-
-<h2>Building nested documentation structures</h2>
-
-<p>As plug-ins contribute function to the platform, it's common to add
-documentation that describes the new function.&nbsp; How can this documentation
-be structured so that the user sees a cohesive and complete set of documentation
-instead of many individual contributions?&nbsp; The table of contents definition
-provides mechanisms for building documentation in both a top-down and bottom-up
-fashion.</p>
-
-<h4>Top-down nesting</h4>
-
-<p>Top-down nesting refers to the technique of defining a master table of
-contents which refers to all other included tocs.&nbsp; Top-down nesting is a
-convenient method for breaking up known content into smaller pieces.&nbsp; With
-top-down nesting, the <b>link</b> attribute is used in the table of contents
-definition to refer to linked tocs rather than providing an <b>href</b>.&nbsp; </p>
-
-<pre>&lt;toc label=&quot;Online Help Sample&quot; topic=&quot;html/book.html&quot;&gt;
-	&lt;topic label=&quot;Concepts&quot;&gt;
-		&lt;link toc=&quot;toc_Concepts.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Tasks&quot;&gt;
-		&lt;link toc=&quot;toc_Tasks.xml&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Reference&quot;&gt;
-		&lt;link toc=&quot;toc_Ref.xml&quot; /&gt;
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-
-
-<p>The basic structure stays the same (Concepts, Tasks, Reference), but the
-individual tocs are free to evolve.&nbsp; They in turn might link to other sub-tocs.
-</p>
-
-<h4>Bottom-up composition</h4>
-
-<p>Bottom-up composition is more flexible in that it lets new plug-ins decide
-where the documentation should exist in the toc structure.&nbsp; Bottom-up
-composition is accomplished using <b>anchor</b> attributes.&nbsp; A toc defines
-named anchor points where other plug-ins can contribute documentation.&nbsp; In
-our example, we could add anchors so that plug-ins can contribute additional
-material between the concepts, tasks, and reference sections.</p>
-
-<pre>&lt;toc label=&quot;Online Help Sample&quot; topic=&quot;html/book.html&quot;&gt;
-	&lt;topic label=&quot;Concepts&quot;&gt;
-		&lt;link toc=&quot;toc_Concepts.xml&quot; /&gt;
-		&lt;<b>anchor</b> id=&quot;postConcepts&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Tasks&quot;&gt;
-		&lt;link toc=&quot;toc_Tasks.xml&quot; /&gt;
-		&lt;<b>anchor</b> id=&quot;postTasks&quot; /&gt;
-	&lt;/topic&gt;
-	&lt;topic label=&quot;Reference&quot;&gt;
-		&lt;link toc=&quot;toc_Ref.xml&quot; /&gt;		
-		&lt;<b>anchor</b> id=&quot;postReference&quot; /&gt;
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-<p>Other plug-ins can then contribute to the anchor from their plug-in.&nbsp;
-This is done using the <b>link_to</b> attribute when defining a toc.</p>
-<pre>&lt;toc <b>link_to=&quot;../com.example.helpexample/toc.xml#postConcepts&quot;</b> label=&quot;Late breaking info about concepts&quot;&gt;
-	&lt;topic&gt;
-		...
-	&lt;/topic&gt;
-&lt;/toc&gt;</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_process.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_process.htm
deleted file mode 100644
index d38cf2f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_process.htm
+++ /dev/null

@@ -1,25 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Processing Help Content</title>
-</head>
-<body>
-
-<h2>Processing Help Content</h2>
-
-<p>
-The Eclipse help system performs preprocessing on html and xhtml pages to add breadcrumbs 
-and JavaScript. The processing is performed by output filter which operate on the output stream. Since Eclipse 3.5 
-Eclipse has had an extension point to allow user defined filters to be added. This can be used for example to inject javascript 
-into every help page. See the extension point <a href = 
-"../reference/extension-points/org_eclipse_help_webapp_contentFilter.html"> org.eclipse.help.webapp.contentFilter</a> 
-for more information.
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_remote.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_remote.htm
deleted file mode 100644
index 1f0b8d1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_remote.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Remote Help</title>
-</head>
-<body>
-
-<h2>Remote Help</h2>
-
-<p><b>What is remote help?</b></p>
-
-<p>
-The help system provides the ability to retrieve content, not only from plug-ins
-installed in the local instance of Eclipse, but also from one or more remote servers running
-help in <a href="ua_help_setup_infocenter.htm">infocenter</a> mode. This allows
-products to ship without help content and provide it from a server to reduce their
-download and install size. It also allows user the ability to include help content
-from plug-ins not installed in their environment.
-</p>
-
-<p><b>How does remote help work?</b></p>
-
-<p>
-Content from the remote help servers is merged seamlessly with the local content. There
-will be no difference perceptible to the user other than potential network delays. This
-is done by adding a second implementation of <code>AbstractTocProvider</code> called
-<code>RemoteTocProvider</code> that supplies the content from the remote help server
-alongside the local <code>TocFileProvider</code>. For performance reasons, where both
-are available, local content will be supplied rather than remote content.
-</p>
-
-<p><b>How do I setup a remote help server?</b></p>
-
-<p>
-All you have to do to setup a remote help server is run the help system (version 3.3
-or later) in <a href="ua_help_setup_infocenter.htm">infocenter</a> mode.
-</p>
-
-<p><b>How do I access a remote help server?</b></p>
-
-<p>
-A remote help server can be specified in two ways as follows:</p>
-<ul>
-<li><a href="ua_help_setup_preferences.htm#remoteHelp">Product customization</a>: There are 
-6 options that can be included in the <code>plugin_customization.ini</code> file to
-setup remote help defaults. They are <code>remoteHelpOn</code>, <code>remoteHelpHost</code>,
-<code>remoteHelpPath</code>,
-<code>remoteHelpPort, remoteHelpName, remoteHelpICEnabled.</code>.
-</li>
-<li><a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/reference/help_preferences_content.htm">
-Help Content preferences</a>: There is a preference page that allows users to
-configure remote help server settings manually.</li>
-</ul>
-
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
deleted file mode 100644
index e10462e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_toc.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Table of contents (toc) files</title>
-</head>
-<body>
-
-<h2>Table of contents (toc) files</h2>
-
-<P >
-Now that we have our sample content files we can create a table of contents (<b>toc</b>)
-file. A toc file defines the key entry points into the HTML content files by mapping a topic
-label to a reference in one of the HTML files.&nbsp; </P>
-<P >
-Applications that are being migrated to the platform can reuse existing documentation by
-using the toc file to define entry points into that documentation. </P>
-<P >
-A plug-in can have one or more toc files. Our example documentation is organized into three main categories: concepts, tasks and reference. How do we make
-toc files that represent this structure?</P>
-<P >
-We could make one large toc file, or we could create a separate toc file for each main category of content. This decision should be made according to the way your documentation teams work together.
-If a different author owns each category, it might be preferable to keep
-separate toc files for each category.&nbsp; It is not dictated by the platform architecture. </P>
-<P >
-In this example, we will create a toc file for each major content category. For such a small number of files,
-having separate toc files for each category may not be necessary.&nbsp; We
-will build this example as if we had many more files or had separate authors who
-own each content category.</P>
-<P >
-Our files look like this:</P>
-
-<H4>toc_Concepts.xml</H4>
-<pre>
-   &lt;toc label=&quot;Concepts&quot;&gt;
-      &lt;topic label=&quot;Concept1&quot; href=&quot;html/concepts/concept1.html&quot;&gt;
-         &lt;topic label=&quot;Concept1_1&quot; href=&quot;html/concepts/concept1_1.html&quot;/&gt;
-         &lt;topic label=&quot;Concept1_2&quot; href=&quot;html/concepts/concept1_2.html&quot;/&gt;
-      &lt;/topic&gt; 
-   &lt;/toc&gt;
-</pre>
-
-<H4>
-toc_Tasks.xml</H4>
-<pre>
-   &lt;toc label=&quot;Tasks&quot;&gt;
-      &lt;topic id=&quot;plainTasks&quot; label=&quot;Plain Stuff&quot;&gt;
-         &lt;topic label=&quot;Task1&quot; href=&quot;html/tasks/task1.html&quot;/&gt;
-         &lt;topic label=&quot;Task2&quot; href=&quot;html/tasks/task2.html&quot;/&gt;
-      &lt;/topic&gt;
-      &lt;topic id=&quot;funTasks&quot; label=&quot;Fun Stuff&quot; &gt;
-         &lt;topic label=&quot;Task3_1&quot; href=&quot;html/tasks/task3_1.html&quot;/&gt;
-         &lt;topic label=&quot;Task3_2&quot; href=&quot;html/tasks/task3_2.html&quot;/&gt;
-      &lt;/topic&gt;
-   &lt;/toc&gt;
-</pre>
-
-<H4>
-toc_Ref.xml</H4>
-<pre>
-   &lt;toc label=&quot;Reference&quot;&gt;
-      &lt;topic label=&quot;Ref1&quot; href=&quot;html/ref/ref1.html&quot;/&gt;
-      &lt;topic label=&quot;Ref2&quot; href=&quot;html/ref/ref2.html&quot;/&gt;
-   &lt;/toc&gt;
-</pre>
-<P >
- A topic can be a simple link to content.&nbsp;
-For example, &quot;Task1&quot; provides a <b>label</b>
-and an <b>href</b> linking to the content.&nbsp; A
-topic can also be a hierarchical grouping of sub topics with no content of its
-own.&nbsp; For example, &quot;Fun Stuff&quot; has only a <b>label</b>
-and sub topics, but no <b>href</b> .&nbsp; Topics can
-do both, too.&nbsp; &quot;Concept1&quot; has an <b>href</b>
-and sub topics. </P>
-
-<p><b>Dynamic content</b></p>
-
-<p>
-Dynamic content is available for the table of contents in the form of
-<a href="ua_dynamic_filters.htm">filters</a> and <a href="ua_dynamic_extensions.htm">
-extensions</a>. For example, you may want a topic to show up in the table of contents
-only when running on a specific operating system.
-</p>
-
-<p>
-<a href="ua_dynamic_includes.htm">Includes</a> are not supported here because they
-are not needed; use <a href="ua_help_content_nested.htm">links</a> instead.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
deleted file mode 100644
index 4f6bff6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_content_xhtml.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Contributing XHTML help documents</title>
-</head>
-<body>
-
-<h2>Contributing XHTML help documents</h2>
-
-<p><b>Why use XHTML?</b></p>
-
-<p>
-The help system provides the ability to produce <a href="ua_dynamic.htm">dynamic help
-content</a> by annotating your XHTML markup with special tags to
-<a href="ua_dynamic_filters.htm">filter</a>,
-<a href="ua_dynamic_includes.htm">include</a>, and
-<a href="ua_dynamic_extensions.htm">extend</a> documents. These features are not
-available when using HTML.
-</p>
-
-<p><b>How to contribute XHTML</b></p>
-
-<p>
-XHTML help documents are contributed in exactly the same way as HTML documents by referencing them from a table of contents (TOC) file.
-Since Eclipse 3.4 it is no longer necessary to bind the "org.eclipse.help.base.xhtml&quot; search participant to your
-         doc plugin.</p> 
-</ul>
-
-<p><a name="include_format"><b>XHTML include format</b></a></p>
-
-<p>
-If you wish to use <a href="ua_dynamic_includes.htm">includes</a> in your XHTML,
-the format of the <code>path</code> attribute is as follow: (explained below)
-</p>
-
-<pre>   &lt;plugin_id&gt;/&lt;path_to_xhtml_file&gt;/&lt;filename_xhtml&gt;/&lt;element_id&gt;
-</pre>
-
-<p>
-Where the fields are:
-</p>
-
-<ul>
-   <li>
-      <b>plugin_id</b>: The id of the plug-in containing the content to include
-      (e.g. <code>org.eclipse.help</code>)
-   </li>
-   <li>
-      <b>path_to_xhtml_file</b>: The plug-in relative path to the file (e.g. <code>
-      /my_folder/my_sub_folder/</code>)
-   </li>
-   <li>
-      <b>filename_xhtml</b>: The name of the XHTML file, including extension (e.g.
-      <code>my_file.xhtml</code>)
-   </li>
-   <li>
-      <b>element_id</b>: The unique identifier for the element you wish to include. This
-      is set by adding an <code>id</code> attribute to that element (e.g. <code>
-      my.element.id</code>)
-   </li>
-</ul>
-
-<p>
-For example, if you wish to include the paragraph (<code>&lt;p&gt;</code> element)
-with the id <code>my_copyright</code> from the file <code>/copyrights/copyright.xhtml
-</code> in plugin <code>my.product.plugin</code>, you would specify the following:
-</p>
-
-<pre>   my.product.plugin/copyrights/copyright.xhtml/my_copyright
-</pre>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
deleted file mode 100644
index 13c9ec3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Context-sensitive help</title>
-</head>
-<body>
-
-<h2>Context-sensitive help</h2>
-
-<p>A focused set of help topics that is related to the current context can be 
-shown to users on demand using <b>context-sensitive help</b>. This form of user 
-assistance is delivered to users when a platform-specific trigger is activated 
-(e.g. F1 key on Windows, Ctrl+F1 on GTK, Help key on Carbon). Until Eclipse 3.1, 
-context-sensitive help was presented in infopop windows. Since 3.1, a new Help 
-view is the preferred way to deliver context-sensitive information to the user.</p>
-<p>Context-sensitive help can be associated with widgets statically using 
-context IDs, or dynamically using context providers. The new help view also adds 
-dynamic help capability by searching help for topics relevant for the current 
-context.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
deleted file mode 100644
index ec23931..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_dynamic.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Dynamic context help</title>
-</head>
-<body>
-
-<h2>Dynamic context help</h2>
-
-<p>
-In addition to statically associating widgets and context Ids, it is possible to 
-provide this information dynamically for a more dynamic context-sensitive help 
-capability. Help system uses context Ids to locate the matching
-<a href="../reference/api/org/eclipse/help/IContext.html">
-org.eclipse.help.IContext</a> object. The new Help view tracks activation of the 
-workbench parts (views and editors) and checks if they adapt to
-<a href="../reference/api/org/eclipse/help/IContextProvider.html">
-org.eclipse.help.IContextProvider</a> interface. If they do, the view will use 
-the context provider to locate the <code>IContext</code> object and get the 
-required information from it. This object can be cached or created on the fly.</p>
-<p>
-Workbench parts that want to create the context object dynamically should adapt 
-to the <code>IContextProvider.class</code> object as a key:</p>
-<blockquote>
-	<pre>public Object getAdapter(Class key) {
-	if (key.equals(IContextProvider.class)) {
-		return new MyContextProvider();
-	}
-	return super.getAdapter(key);
-}</pre>
-</blockquote>
-<p>The context provider interface requires implementation of three methods:</p>
-<blockquote>
-	<pre>public class MyContextProvider implements IContextProvider {
-	int getContextChangeMask() {
-		return NONE;
-	}
-	IContext getContext(Object target) {
-		return myContext;
-	}
-	String getSearchExpression(Object target) {
-		return null;
-	}
-}</pre>
-</blockquote>
-<p>If context change mask returns <code>NONE</code>, context object will need to 
-be provided when the workbench part is activated. If <code>SELECTION</code> is 
-returned, you will need to provide context object that is sensitive to the 
-current selection in the part. Each time part selection provider fires a 
-selection change event, the context provider will be asked to provide context 
-object.</p>
-<p>Optionally, search expression for the dynamic help can be provided. 
-Otherwise, a combination of the part name and perspective name will be used with 
-good results in most cases.
-</p>
-
-<p>
-<b>Note:</b> In addition to using context providers (or alternatively), you can use
-XML annotations to <a href="ua_dynamic_filters.htm">filter</a> topics in context
-help.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
deleted file mode 100644
index c594128..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_id.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Declaring a context id</title>
-</head>
-<body>
-
-<h2>Declaring a context id</h2>
-
-<p>
-The <b>setHelp</b> method in
-<b><a href="../reference/api/org/eclipse/ui/help/IWorkbenchHelpSystem.html">org.eclipse.ui.help.IWorkbenchHelpSystem</a></b>
-is used to associate a context id with a <code>Control</code>, <code>IAction</code>,
-<code>Menu</code>, or <code>MenuItem</code>. The context id should be fully
-qualified with the plug-in id. For example, the following snippet associates
-the id &quot;com.example.helpexample.panic_button&quot; with a button in the
-application.
-</p>
-
-<pre>PlatformUI.getWorkbench().getHelpSystem().setHelp(myButton, com.example.helpexample.panic_button);</pre>
-
-<p>
-The following UI controls cannot have context ids (and therefore cannot have
-context-sensitive help):
-</p>
-
-<ul>
-  <li>Toolbar buttons (ToolItem)</li>
-  <li>CTabItem</li>
-  <li>TabItem</li>
-  <li>TableColumn</li>
-  <li>TableItem</li>
-  <li>TableTreeItem</li>
-  <li>TreeItem</li>
-</ul>
-
-<p>
-Widgets that do not get focus should not be assigned context ids, since they
-will never trigger a context-sensitive help.
-</p>
-
-<p>
-<em>
-Note: The default implementation of help will display the help dialog tray only if
-the dialog is either large enough to accomodate it, or is resizable. Otherwise,
-an infopop will be shown.
-</em>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm
deleted file mode 100644
index a3b3457..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_infopops.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Infopops</title>
-</head>
-<body>
-
-<h2>Infopops</h2>
-
-<p>An infopop is a small window associated with a
-particular SWT widget in a plug-in's user interface.&nbsp; It displays
-context-sensitive help and links to related help topics for the widget.&nbsp;It
-is activated when the user puts focus on the widget and presses the <code>F1</code>
-key (<code>Ctrl+F1</code> on GTK, and <code>Help</code> key on Carbon).</p>
-<p>Since Eclipse 3.1, the preferred way to show the context help is in the help 
-window. However, it is still possible to configure context help presentation to 
-use infopops in the Help preferences. For example, here is an infopop that has been defined on 
-the General/Search page: </p>
-<p align="center">
-<img border="0" src="images/infopops.png" alt="Image showing an infopop">
-</p>
-
-<p>Since Eclipse 3.1, infopops have a link to show the currently displayed 
-context help in the new Help view.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
deleted file mode 100644
index e5b6d79..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_context_xml.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Describing and packaging context-sensitive help content</title>
-</head>
-<body>
-
-<h2>Describing and packaging context-sensitive help content</h2>
-
-<p>
-Context-sensitive help is described by associating the context id declared in
-the UI code with a description and list of links to related topics or commands
-in the online help. These associations are made inside an XML file located
-within the plug-in that contains the topics in question. You can create any number
-of XML files containing context help associations for each plug-in. The
-description and links for each context id is made inside
-<strong>&lt;context&gt;</strong> elements in the XML file. Each context element
-can have an optional <strong>&lt;description&gt;</strong> element which is used
-to describe the UI object and any number of <strong>&lt;topic&gt;</strong>
-elements which link to the on-line documentation, as well as command links
-to perform any operation for the user, e.g. open a cheat sheet.
-</p>
-
-<p>
-Since 3.1, context elements can optionally override the default title used to 
-present the context help information in the Help view.
-</p>
-
-<pre>&lt;contexts&gt;
-	&lt;context id=&quot;panic_button&quot; title=&quot;Panic Button Title&quot;&gt;
-		&lt;description&gt;This is the panic button.&lt;/description&gt;
-		&lt;command serialization=&quot;org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=org.eclipse.panic.button.cheatsheet)quot; label=&quot;Pushing the panic button&quot;/&gt;
-		&lt;topic href=&quot;reference/panic_button.htm&quot; label=&quot;Panic Button Reference&quot;/&gt;
-	&lt;/context&gt;
-	...
-&lt;/contexts&gt;
-</pre>
-
-<p>
-Once the contexts have been described in the XML file (or files), you are ready
-to refer to the context files in your plug-in manifest. Note that the context id
-is not qualified. 
-</p>
-
-<p>A plug-in containing context files contributes them using the <b><a href="../reference/extension-points/org_eclipse_help_contexts.html">org.eclipse.help.contexts</a></b>
-extension point.&nbsp;&nbsp;
-</p>
-
-<pre>   &lt;extension point=&quot;org.eclipse.help.contexts&quot;&gt;
-      &lt;contexts file=&quot;myContextHelp.xml&quot;  /&gt;
-   &lt;/extension&gt;
-</pre>
-
-<p>You can reference context files from other plug-ins by including the <b>plugin</b>
-attribute.&nbsp; This allows you to group all of your documentation, including
-content-sensitive help, in one plug-in, and refer to it from the UI code plug-in or some other
-related plug-in.</p>
-
-<pre>   &lt;extension point=&quot;org.eclipse.help.contexts&quot;&gt;
-      &lt;contexts file=&quot;myContextHelp.xml&quot; <b>plugin</b>=&quot;com.example.helpExample&quot;  /&gt;
-   &lt;/extension&gt;</pre>
-   
-<p>When a context id is declared in an extension point the Eclipse help system will create a fully qualified
-context id of the form <code>&lt;plug-in name&gt;.&lt;context id&gt;</code> and use this when matching against the context
-ids used in the Java source. &lt;plug-in name&gt; is the value of the "plugin" attribute, or if not specified the
-name of the plug-in in which the org.eclipse.help.contexts extension is declared.</p>
-
-<h4>
-Context-sensitive help from multiple plug-ins</h4>
-
-
-<p>Another level of flexibility is the ability to contribute context-sensitive 
-help for the
-same context id from different plug-ins.&nbsp; This is useful, for example, if
-there are different sets of documentation plug-ins that may or may not be
-installed in a user's configuration.&nbsp; This allows each documentation
-plug-in to declare its contexts independently.&nbsp; The end user will see the
-merged context-sensitive help content for all plug-ins that contributed contexts for the
-widget's id.</p>
-
-<p>Note that the plugin attribute must be used in the extensions if multiple plugins will 
-contribute to the same context.&nbsp; When multiple plug-ins contribute 
-context-sensitive help for
-the same context ID, the content defined in the plug-in that declared the
-context (the UI plug-in) is shown first.&nbsp; Additional descriptions and links
-are appended in no guaranteed order.</p>
-
-<h4>Dynamic content</h4>
-
-<p>
-Dynamic content is available for the context help in the form of
-<a href="ua_dynamic_filters.htm">filters</a> on context help topic links. For
-example, you may want a topic link to show up in the context help only when running
-on a specific operating system.
-</p>
-
-<h4>
-Adding Context Help to your Java Code</h4>
-
-<p>
-See <a href="ua_help_context_id.htm">declaring a context Id</a> for more 
-information.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm
deleted file mode 100644
index c05922d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_infocenter_preferences.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Infocenter customization</title>
-
-</head>
-<body>
-
-<h2>Infocenter customization</h2>
-
-<p>All of the customizations which can apply to the Eclipse help system can also be applied to an Eclipse infocenter including
-product specific branding, style sheets, banner and ordering of books. The easiest way to do this is to 
-create a plug-in which implements
-the org.eclipse.core.runtime.products extension point and place all the customization in that plugin.
-</p>
-<p>The Help system itself is divided up into a number of separate
-plug-ins.
-These tables shows available preferences, and which plug-in
-defines them.
-</p>
-
-<h3>Creating a product plug-in</h3>
-<p>A product plugin can be created using the menu item File/New/Project and selecting Plug-in Project. 
-Uncheck the check box titled "Create Java Project", give the project a name, hit "next" and "finish" to 
-exit the wizard. In the extensions tab of the plug-in manifest editor add the extension 
-"org.eclipse.core.runtime.products" and give it a name. Create a product element beneath that and give it a name. 
-Beneath the product element add a property element and 
-set "preferenceCustomization" to "plugin_customization.ini".  plugin.xml will now contain entries similar to 
-the following.
-<pre>
- &lt;extension
-         id="custom"
-         point="org.eclipse.core.runtime.products"&gt;
-      &lt;product
-            application="org.eclipse.ui.ide.workbench"
-            description="This is my custom product"
-            name="Custom Product"&gt;
-         &lt;property
-               name="preferenceCustomization"
-               value="plugin_customization.ini"&gt;
-         &lt;/property&gt;
-      &lt;/product&gt;
-   &lt;/extension&gt;
-</pre>
-</p>
-
-<h3>Installing the product plug-in</h3>
-<p>
-    Export the product plug-in as a deployable plug-in. Copy the jar file for the exported plug-in 
-    to the "dropins" folder in the eclipse installation which will be used to start the infocenter.
-    Start the infocenter with an additional argument to specify the product. For example if the 
-    product plugin is called help.product and it's product id is "custom" add the argument 
-    "-product help.product.custom". Open the infocenter, the title will now show the customized product name.
-</p>
-<h3>Additional customization</h3>
-<p>
-Modify plugin_customization.ini in the product plugin to add more customizations, see <a href = "ua_help_setup_preferences.htm">
-Help system customization</a>, re-export and replace the plug-in in the dropins folder. To modify the banner
-a line like this could be added to plugin_custiomization.ini.
-<pre>
-org.eclipse.help.base/banner=/org.eclipse.help.webapp/advanced/banner.html
-</pre>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_menu.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_menu.htm
deleted file mode 100644
index dcd25cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_menu.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Help content</title>
-</head>
-<body>
-
-<h2>The Help Menu</h2>
-
-<p>The Eclipse Platform and SDK contain menu items for Help Contents, Search and 
-Dynamic Help. A menu item to show the keyword index can be added to the help 
-menu in an Eclipse based product by adding the following extension point to the 
-plugin.xml file of the product plugin. The same approach will work equally well 
-for a Rich Client application.</p>
-<p><br>
-&lt;extension point=&quot;org.eclipse.ui.menus&quot;&gt;<br>
-&nbsp;&nbsp;&nbsp; &lt;menuContribution locationURI=&quot;menu:help?before=group.assist&quot;&gt;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;command commandId=&quot;org.eclipse.help.ui.indexcommand&quot;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-mnemonic=&quot;I&quot;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-style=&quot;push&quot;&gt;<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/command&gt;<br>
-&nbsp;&nbsp;&nbsp; &lt;/menuContribution&gt;<br>
-&lt;/extension&gt;</p>
-
-<pre>
-</pre>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
deleted file mode 100644
index f08f084..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Help search</title>
-</head>
-<body>
-
-<h2>Help search</h2>
-
-<p>Since Eclipse 3.1, search in the workbench has been partitioned into two 
-major categories: development artifact search and information search. The former 
-is handled by the search dialog opened from the Search menu. The later is 
-available from Help&gt;Search menu item which opens the new Help view into the 
-Search page.</p>
-<p>The new information search facility uses multiple search engines run in 
-parallel using the same search expression. Eclipse provides a number of 
-preconfigured search engines. New engines can be added programmatically or by 
-the user. All the results are collated in the Search page directly.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
deleted file mode 100644
index 834d5a2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_search_types.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Plugging in search engines</title>
-</head>
-<body>
-
-<h2>Plugging in search engines</h2>
-
-<p>
-The new federated information search in Help system uses the notion of <b>search 
-engine types</b> and <b>search engines</b>. An engine type is a meta-engine from 
-which a number of concrete search engines can be created by parameterization.</p>
-<p>New engine types are contributed through the
-<a href="../reference/extension-points/org_eclipse_help_ui_searchEngine.html">
-org.eclipse.help.ui.searchEngine</a>:</p>
-<blockquote>
-	<pre>&lt;extension point=&quot;org.eclipse.help.ui.searchEngine&quot;&gt;
-	&lt;engineType
-		scopeFactory=&quot;com.example.xyz.XYZScopeFactory&quot;
-		label=&quot;XYZ Search&quot;
-		class=&quot;com.example.xyz.search.XYZSearch&quot;
-		icon=&quot;icons/etool16/xyzsearch.gif&quot;
-		pageClass=&quot;com.example.xyz.search.XYZSearchPage&quot;
-		id=&quot;com.example.xyz.XYZSearch&quot;&gt;
-		&lt;description&gt;
-			Instances of XYZ Search search the XYZ site.
-		&lt;/description&gt;
-	&lt;/engineType&gt;</pre>
-</blockquote>
-This extension point is used to plug in search participants in the information 
-search. Each search engine can be configured individually. When search is 
-initiated, each search engine is executed as a background job, and the results 
-are collated in the help view immediately under the query. 
-<p>Search engines defined here will not automatically show up as federated 
-search participants until engine product binding is established, unless <code>
-productId</code> attribute is left undefined. For engines that define it, only 
-those bound to a particular product will show up when that product is running.
-</p>
-<p>Search engines can simply compose a URL and provide only one hit containing 
-that URL as <code>href</code>. Popular search engines for which API support 
-requires license can be plugged in like this. On the other end of the spectrum, 
-search engines can communicate with the server and receive individual hits with 
-information like label, href, short description, score etc. Local help engine 
-can produce hits this way.</p>
-<p>Regardless of the search mechanism, engines can provide various search scope 
-settings using JFace preference pages. These pages are shown when 'Advanced 
-Settings' link is followed from the Help view. In addition to root preference 
-pages defined with the engine, additional preference sub-pages can be plugged in 
-for more advanced settings. </p>
-<p>Scope settings are loaded and stored using <code>IPreferenceStore</code> 
-objects. Scope settings for all engines are grouped together under a named <b>
-scope set</b>. When first opened, default scope set ('Default') is created, but 
-users can define more scope sets and flip between them. </p>
-<p>Since federated search support is part of <code>org.eclipse.help.base</code> 
-plug-in, a factory is needed to create search scope objects from the data in the 
-preference store. Clients that plug in scope preference pages are required to 
-plug in scope factories as well. </p>
-<p>Engines defined in this extension point do not show up in the UI by default. 
-What is shown there is a concrete <b>instance</b> of a search engine that can be 
-individually modified. Products can pre-configure the help system with a number 
-of instances of the registered engine types, possibly parameterized to perform 
-in a desired way. In addition, users can add their own instances of the 
-registered engines and configure them to their liking:</p>
-<blockquote>
-	<pre>
-&lt;engine
-	enabled=&quot;true&quot;
-	engineTypeId=&quot;com.example.xyz.search.XYZSearch&quot;
-	id=&quot;com.example.xyz.XYZSearch&quot;
-	label=&quot;XYZ Search&quot;&gt;
-&lt;/engine&gt;
-&lt;engine
-	enabled=&quot;true&quot;
-	engineTypeId=&quot;org.eclipse.help.ui.web&quot;
-	id=&quot;org.eclipse.sdk.Eclipse&quot;
-	label=&quot;%search.Eclipse.label&quot;&gt;
-	&lt;description&gt;
-		%search.Eclipse.desc
-	&lt;/description&gt;
-	&lt;param 
-		name=&quot;url&quot; 
-		value=&quot;http://eclipse.org/search/search.cgi?q={expression}&amp;amp;ul=&amp;amp;ps=20&amp;amp;m=all&quot;&gt;
-	&lt;/param&gt;
-&lt;/engine&gt;</pre>
-</blockquote>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm
deleted file mode 100644
index 9960fe0..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Configuration/setup</title>
-</head>
-<body>
-
-<h2>Configuration/setup</h2>
-
-<p>
-This section contains topics related to installing, configuring, and customizing
-the help system to work in different environments and products.
-</p>
-
-<h3>Help modes</h3>
-
-<p>
-The help system can run in three modes: workbench (normal),
-<a href="ua_help_setup_infocenter.htm">infocenter</a>, and
-<a href="ua_help_setup_standalone.htm">standalone</a>. Workbench mode is used
-for serving help integrated with the product, usually via a Help menu. This mode
-also offers context help and the help view, which are not available in the two other
-modes. <strong>Standalone</strong> mode has the same goal as workbench mode, but is
-for products that are not eclipse-based (the help will be less integrated).
-<strong>Infocenter</strong> mode is used to serve help content to the masses
-over the Web. Consult the links above for details.
-</p>
-
-<h3>Rich Client Platform (RCP) support</h3>
-
-<p>
-The Help system is an <em>optional</em> Rich Client Platform (RCP) component. That
-is, it is not part of the minimal RCP, but <a href="ua_help_setup_rcp.htm">can be
-added</a> to it to provide help in your RCP application.
-</p>
-
-<h3>Product customization</h3>
-
-<p>
-Help provides <a href="ua_help_setup_preferences.htm">preferences</a> that products
-can use to <strong>customize</strong> the help system to their needs. These include
-ways to customize branding, appearance, turn on/off functionality, etc.
-</p>
-
-<h3>Pre-indexing</h3>
-
-<p>
-For products that offer a large number of help documents, the initial indexing
-phase that occurs when searching for the first time can be lengthy. To avoid this
-delay, you can <a href="ua_help_setup_preindex.htm">pre-index</a> your help contents
-and ship the pre-built index along with your documentation. This is a trade-off
-between performance (avoiding the indexing phase) and space (to store the index).
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm
deleted file mode 100644
index 9494ba3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_about.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Using about.html to debug infocenters</title>
-<link rel="stylesheet" href="../book.css" charset="utf-8" type="text/css">
-</head>
-<body>
-
-<h1>Using about.html to debug infocenters</h1>
-
-<p>
-When developing an infocenter sometimes not all of the books show as expected or 
-customizations do not have the desired effect. The about.html page can be used to get information 
-about installed plug-ins and help system preferences. If the home page of the help system is 
-<pre>http://&lt;hostname&gt;:&lt;port&gt;/help/index.jsp</pre> the about page has a url of 
-<pre>http://&lt;hostname&gt;:&lt;port&gt;/help/about.html</pre> 
-Without any parameters the about page shows a list of all plug-ins installed on the system. 
-Parameters can be added to show other kinds of information as follows:
-<ul>
-<li>
-<code>about.html?show=preferences</code> shows the values of the help system preferences.
-</li>
-<li>
-<code>about.html?show=agent</code> shows the user agent information from the Web Browser used to 
-read the page.
-</li>
-</ul>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_help_data.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_help_data.htm
deleted file mode 100644
index 73c95cc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_help_data.htm
+++ /dev/null

@@ -1,113 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Help Data</title>
-<link rel="stylesheet" href="../schema.css" charset="utf-8" type="text/css">
-<link rel="stylesheet" href="../book.css" charset="utf-8" type="text/css">
-</HEAD>
-<BODY>
-<CENTER>
-<H1>Help Data</H1></CENTER>
-<p></p>
-<h6 class=CaptionFigColumn id=header>Identifier: </h6>org.eclipse.help.HELP_DATA<p></p>
-<h6 class=CaptionFigColumn id=header>Since: </h6>3.3
-<p></p>
-
-<p></p>
-<h6 class=CaptionFigColumn id=header>Description: </h6>
-<p>The help data XML file is used by products to control the order of books in the help table of contents, as well whether or not books or keyword index sets should be displayed at all. The file must be referenced in the product's <code>plugin_customization.ini</code> file using the <code>org.eclipse.help/HELP_DATA</code> property.</p>
-<h6 class=CaptionFigColumn id=header>Configuration Markup:</h6>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.extensions">extensions</a> (<a href="#e.tocOrder">tocOrder</a>? , <a href="#e.hidden">hidden</a>?)&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-The extension data for Help.</p>
-<br><br>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.tocOrder">tocOrder</a> (<a href="#e.toc">toc</a> | <a href="#e.category">category</a>)*&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Specifies the order in which top-level table of contents entries (also called "books") or categories of books should appear in Help. If one of the items listed is not available, it is ignored. If there are items available that are not listed and not hidden, they will be displayed after the ones listed here.</p>
-<br><br>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.toc">toc</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST toc</p>
-<p class=code id=dtdAttlist>id&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A reference to a top-level table of contents (TOC) entry, also called a "book".</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>id</b> - The unique identifier for this book. For XML file TOC contributions, this is a path to the file in the form "<code>/&lt;plugin_id&gt;/&lt;path&gt;/&lt;file&gt;</code>" (e.g., "<code>/org.eclipse.platform.doc.user/toc.xml</code>"). In general, this is the ID of the <code>TocContribution</code> supplied by its originating <code>AbstractTocProvider</code>.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.category">category</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST category</p>
-<p class=code id=dtdAttlist>id&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A reference to a category of top-level table of contents (TOC) entries (books). Categories are implicitly created when a table of contents contribution declares itself to be of that category, for example, by specifying a <code>category</code> attribute for the <code>toc</code> element in the <code>org.eclipse.help.toc</code> extension point.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>id</b> - The unique id of the category.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.hidden">hidden</a> (<a href="#e.toc">toc</a> | <a href="#e.category">category</a> | <a href="#e.index">index</a>)*&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-Contains a set of help items that should be hidden from the user.</p>
-<br><br>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.index">index</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST index</p>
-<p class=code id=dtdAttlist>id&nbsp;CDATA #REQUIRED&gt;</p>
-<p></p>
-<p class=ConfigMarkup id=elementDesc>
-A reference to a contribution of help index keywords.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>id</b> - The unique identifier for this contribution of keywords. For XML file index contributions, this is a path to the file in the form "<code>/&lt;plugin_id&gt;/&lt;path&gt;/&lt;file&gt;</code>" (e.g., "<code>/org.eclipse.platform.doc.user/index.xml</code>"). In general, this is the ID of the <code>IndexContribution</code> supplied by its originating <code>AbstractIndexProvider</code>.</li>
-</ul>
-<br><h6 class=CaptionFigColumn id=header>Examples: </h6><p>
-The following example shows how to arrange the following books in the order shown:
-</p>
-
-<ul>
-<li>Book #1: "Introduction to XYZ" (category: "<code>user.intro</code>") in <code>/com.xyz.doc.user/introToc.xml</code></li>
-<li>Book #2: "Using XYZ" (category: "<code>user.content</code>") in <code>/com.xyz.doc.user/usingToc.xml</code></li>
-<li>Book #3: "Troubleshooting" (category: "<code>user.reference</code>") in <code>/com.xyz.doc.user/refToc.xml</code></li>
-</ul>
-
-<p>
-As well as hide the following books/categories and related keyword indexes:
-</p>
-
-<ul>
-<li>Book #4: "Platform ABC" (category: <code>none</code>) in <code>/org.abc.doc.isv/toc.xml</code></li>
-<li>Book #5: "DEF Toolkit" (category: "<code>isv.reference</code>") in <code>/com.def.doc.isv/toc.xml</code></li>
-<li>Book #6: "GHI Support" (category: "<code>isv.reference</code>") in <code>/com.ghi.doc.isv/toc.xml</code></li>
-</ul>
-
-<p>
-The markup would be the following:
-</p>
-
-<pre>
-<font color="#0000ff">&lt;extensions&gt;
-   &lt;tocOrder&gt;
-      &lt;toc id=</font><font color="#008000">&quot;/com.xyz.doc.user/introToc.xml&quot;</font><font color="#0000ff">/&gt;
-      &lt;category id=</font><font color="#008000">&quot;user.content&quot;</font><font color="#0000ff">/&gt;
-      &lt;toc id=</font><font color="#008000">&quot;/com.xyz.doc.user/refToc.xml&quot;</font><font color="#0000ff">/&gt;
-   &lt;/tocOrder&gt;
-   &lt;hidden&gt;
-      &lt;toc id=</font><font color="#008000">&quot;/org.abc.doc.isv/toc.xml&quot;</font><font color="#0000ff">/&gt;
-      &lt;category id=</font><font color="#008000">&quot;isv.reference&quot;</font><font color="#0000ff">/&gt;
-      &lt;index id=</font><font color="#008000">&quot;/org.abc.doc.isv/index.xml&quot;</font><font color="#0000ff">/&gt;
-      &lt;index id=</font><font color="#008000">&quot;/com.def.doc.isv/index.xml&quot;</font><font color="#0000ff">/&gt;
-   &lt;/hidden&gt;
-&lt;/extensions&gt;</font>
-</pre>
-
-<h6 class=CaptionFigColumn id=header>Supplied Implementation: </h6>This API is supported by any help implementation that is based on <code>org.eclipse.help</code>, including the default help implementation provided by Eclipse.
-<p class=note id=copyright>
-Copyright (c) 2006 IBM Corporation and others.<br>
-All rights reserved. This program and the accompanying materials are made 
-available under the terms of the Eclipse Public License v1.0 which accompanies 
-this distribution, and is available at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm
deleted file mode 100644
index a40bdaa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_infocenter.htm
+++ /dev/null

@@ -1,294 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Infocenter</title>
-</head>
-<body>
-
-<h2>Infocenter</h2>
-
-<p>
-You can allow your users to access the help system over the Internet or an 
-intranet by installing an infocenter and the documentation plug-ins on a
-server. Clients view help by navigating to a URL, and the help system is shown
-in their Web browser. The infocenter help system can be used for both client
-and web applications, either of which can have their help accessed remotely.
-All features of help system except context help, active help, command support,
-and the help view are supported.
-</p>
-
-<p>
-The infocenter help system allows passing number of options that can be used to
-customize various aspects of the infocenter. The following options are
-supported:
-</p>
-
-<ul>
-	<li>
-	<strong>-eclipsehome</strong> <em>eclipseInstallPath</em> - specifies
-	the Eclipse installation directory. This directory is the parent of the
-	plugins directory and Eclipse executable. The option must be provided when
-	the current directory from which the infocenter is launched is not the same
-	as the Eclipse installation	directory.
-	</li>
-
-	<li>
-	<strong>-data</strong> <em>instanceArea</em> - specifies a path that Eclipse
-	can use to write instance data. The value can be the absolute path of a
-	directory or a path relative to Eclipse installation directory. The option
-	must be provided when Eclipse is installed in a read only location, or has
-	been customized to override the <code>osgi.instance.area</code> or <code>
-	osgi.instance.area.default</code> properties.
-	</li>
-
-	<li>
-	<strong>-host</strong> <em>helpServerHost</em> - specifies the host name of
-	the	interface that the help server will use. This overrides the host name
-	specified in the application server plugin preferences.
-	</li>
-
-	<li>
-	<strong>-port</strong> <em>helpServerPort</em> - specifies the port number
-	that the help server will use. This overrides the port number specified in
-	the	application server plugin preferences.
-	</li>
-
-	<li>
-	<strong>-locales</strong> <em>localeList</em> - specifies a list of locales
-	that the infocenter	will recognize and provide customized content for. If
-	the option is not specified, the infocenter will build navigation and index
-	documents for each preferred locale of the browsers accessing the
-	infocenter. When the option is present, locales from browser requests will
-	be matched with locales in the list. If no browser preferred locale exists
-	in the list, but its language part does, it will be used instead.
-	Subsequently, additional browser locales in decreased order of preference
-	will be matched against the list. If none of the browser locales (or its
-	language part) match any locale on the list, the client will be served
-	content in the default locale - server locale or locale passed with -nl
-	option. For example, using options <code>-nl en -locales de en es fr it ja
-	ko pt_BR zh_CN zh_TW</code> will cause infocenter to operate in 10 locales.
-	All	other locales will receive content from the <code>en</code> locale.
-	</li>
-
-	<li>
-	<strong>-dir ltr</strong> or <strong>-dir rtl</strong> - forces
-	left-to-right or right-to-left rendering direction of the help UI in the
-	browser for all languages. By default, the direction is determined by the
-	browser locale.
-	</li>
-
-	<li>
-	<strong>-noexec</strong> - indicates that the Eclipse executable should not
-	be used. You need to use this option when running on a platform for which
-	the Eclipse executable is not available.
-	</li>
-
-	<li>
-	Additionally, most
-	<a href="../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">
-	options accepted by the Eclipse executable</a> are allowed. They are
-	especially useful during debugging and for applying customization to
-	Eclipse. For example, passing options <code>-vmargs -Xmx256M</code>
-	increases memory available to the infocenter and will allow serving of a
-	larger book collection.
-	</li>
-</ul>
-
-<h3>Installation/packaging</h3>
-
-<p>
-These steps are for the help system integrator and are not meant to address all
-the possible scenarios. It is assumed that all your documentation is delivered
-as Eclipse plug-ins and, in general, you are familiar with the eclipse help
-system.
-</p>
-
-<ol>
-	<li>
-	Download the Eclipse Platform Runtime Binary driver from
-	<a target="_blank" href="http://www.eclipse.org/downloads/">eclipse.org</a>.
-	</li>
-	
-	<li>
-	Install (unzip) the driver in a directory, say <code>d:\myApp</code>. This
-	will create an eclipse sub-directory, <code>d:\myApp\eclipse</code> that
-	contains the code required for the Eclipse platform (which includes the
-	help system).
-	</li>
-</ol>
-
-<h3>How to start or stop infocenter from command line</h3>
-
-<p>
-The <code>org.eclipse.help.standalone.Infocenter</code> class has a <code>
-main()</code> method that you can use to launch the infocenter from the command
-line. The command line argument syntax is:
-</p>
-
-<pre>-command start | shutdown | [-eclipsehome eclipseInstallPath] [-data instanceArea] [-host helpServerHost] [-locales localeList] [-port helpServerPort] [-dir rtl] [-noexec] [platform options] [-vmargs JavaVMarguments]</pre>
-
-<p>
-To start an infocenter on port 8081, issue a <code>start</code> command by running
-</p>
-
-<pre>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar org.eclipse.help.standalone.Infocenter -command start -eclipsehome d:\myApp\eclipse -port 8081</pre>
-
-<p>
-To shut down the infocenter issue a <code>shutdown</code> command by running
-</p>
-
-<pre>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar org.eclipse.help.standalone.Infocenter -command shutdown -eclipsehome d:\myApp\eclipse</pre>
-
-<h3>Using the infocenter</h3>
-
-<p>
-Start the infocenter using the instructions above. Point a web browser to the
-&quot;/help/index.jsp&quot; starting point for the Web application running on
-the port specified when starting the infocenter (e.g. 8081). For example, from
-the machine on which the infocenter is installed, this would be
-<code>http://localhost:8081/help/index.jsp</code>.
-</p>
-
-<h3>How to start and stop an infocenter from Java</h3>
-
-<p>
-When including an infocenter as part of another application, it may be more
-convenient to start it and stop it using Java API calls instead of system
-commands. If this is the case, follow the steps:
-</p>
-
-<ol>
-	<li>
-	Make sure <code>d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar
-	</code> is on your application's classpath. The class you use to start and
-	shut down the infocenter is <code>org.eclipse.help.standalone.Infocenter
-	</code>.
-	</li>
-	
-	<li>
-	Create an array of <code>String</code> objects containing options that you
-	want to pass to the infocenter. Typically, the <code>eclipsehome</code> and
-	<code>port</code> options are needed.
-	<pre>String[] options = new String[] { &quot;-eclipsehome&quot;, &quot;d:\\myApp\\eclipse&quot; , &quot;-port&quot;, &quot;8081&quot; };</pre>
-	</li>
-	
-	<li>
-	In your application, create an instance of the <code>Help</code> class by
-	passing in the options.
-	<pre>Infocenter infocenter = new Help(options);</pre>
-	</li>
-	
-	<li>
-	To start the help system:
-	<pre>infocenter.start();</pre>
-	</li>
-	
-	<li>
-	To shut down the infocenter:
-	<pre>infocenter.shutdown();</pre>
-	</li>
-</ol>
-
-<h3>Making infocenter available on the web</h3>
-
-<p>
-Eclipse contains a complete infocenter and does not require any other server
-software to run. However, in an unsecure environment like the Internet, it is
-not recommended to allow direct access by the clients, but instead made
-available through an HTTP server or an application server. Most servers come
-with modules or servlets for delegating certain request to other Web resources.
-For example, one may configure a proxy module of the Apache HTTP Server to
-redirect requests made to <code>http://mycompany.com/myproduct/infocenter</code>
-to <code>http://internalserver:8081/help</code> that runs an infocenter. Adding
-the lines
-</p>
-
-<pre>LoadModule proxy_module modules/ApacheModuleProxy.dll
-ProxyPass /myproduct/infocenter http://internalserver:8081/help
-ProxyPassReverse /myproduct/infocenter http://internalserver:8081/help</pre>
-
-<p>
-to the <code>conf/httpd.conf</code> file of Apache server running the mycompany
-web site accomplishes this.
-</p>
-
-<p>
-Some versions of the Apache HTTP server may contain an AddDefaultCharset
-directive enabled in configuration file. Remove the directive or replace it with
-</p>
-
-<pre>AddDefaultCharset Off</pre>
-
-<p>
-to have browsers display documents using correct character set.
-</p>
-
-<h3>Running multiple instances of an infocenter</h3>
-
-<p>
-Multiple instances of an infocenter can be run on a machine from one
-installation. Each started instance must use its own port and must be provided
-with a workspace, hence the <code>-port</code> and <code>-data</code> options
-must be specified. The instances can serve documentation from different sets of
-plug-ins by providing a valid platform configuration with the
-<code>-configuration</code> option.
-</p>
-
-<p>
-If <code>-configuration</code> is not used and the configuration directory is
-shared among multiple infocenter instances with overlapping sets of locales,
-you must be ensure that all search indexes are created by one infocenter
-instance before another instance is started. Indexes are saved in the
-configuration directory, and write access is not synchronized across infocenter
-instances.
-</p>
-
-<h3>Filtering</h3>
-
-<p>
-<a href="ua_dynamic_filters.htm">Filtering</a> support is turned
-<strong>off</strong> when running in infocenter mode, causing all content,
-including filtered content, to be visible. If you intent to host your
-documentation in both workbench and infocenter modes, you should use filters in
-a way that makes sense even if filtering is turned off.
-</p>
-
-<h3>[Optional] Installing a minimal set of plug-ins</h3>
-
-<p>The infocenter does not require the entire Eclipse Platform package. It is
-possible to run an infocenter with the following plug-ins (located in the
-<code>eclipse\plugins</code> directory):
-</p>
-
-<p>
-<code>
-org.apache.lucene<br>
-org.eclipse.core.runtime<br>
-org.eclipse.help<br>
-org.eclipse.help.appserver<br>
-org.eclipse.help.base<br>
-org.eclipse.help.webapp<br>
-org.eclipse.osgi<br>
-org.eclipse.tomcat<br>
-org.eclipse.update.configurator<br>
-</code>
-</p>
-
-<p>
-Some documentation plug-ins may have dependencies on other plug-ins, usually by
-specifying the required plug-ins in their bundle manifest. The dependent
-plug-ins need to be installed on the infocenter as well.
-</p>
-
-<p>
-See the <a href="ua_help_setup_preferences.htm">Product customization</a>
-topic for more information on customizing the help system.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm
deleted file mode 100644
index f2e484d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_nav.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Generated navigation topics</title>
-<link rel="stylesheet" href="../book.css" charset="utf-8" type="text/css">
-</head>
-<body>
-
-<h1>Generated navigation topics</h1>
-
-<p>
-If a topic in the table of contents does not specify an <code>href</code> attribute, or a toc
-element does not specify a <code>topic</code> element, Help will automatically generate a topic
-containing the topic's title, a heading to denote the start of the list of subtopics, and an
-unordered list of subtopic links (direct subtopics only).
-</p>
-
-<p>
-Products may customize the appearance of these generated topics using CSS. Help will look for
-a <code>book.css</code> file at the root of the currently running product's plug-in, and will use
-this stylesheet to style the generated document. You may rely on the elements with the following
-classes to be present in the generated document, and use these to style it:
-</p>
-
-<ul>
-<li><code>NavTitle</code>: The class of the heading containing the topic's title.</li>
-<li><code>NavListTitle</code>: The class of the heading before the list of topic links.</li>
-<li><code>NavList</code>: The class of the list containing the links to the direct subtopics.</li>
-</ul>
-
-<p>
-For example, to hide the list bullets, you would use the following CSS rule:
-</p>
-
-<pre>
-UL.NavList {
-   list-style-type: none;
-}
-</pre>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm
deleted file mode 100644
index 39f7c9f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preferences.htm
+++ /dev/null

@@ -1,517 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Help system customization</title>
-
-<style type="text/css">
-	.deprecated {
-		color: #444444;
-	}
-	.warning {
-		color: red;
-	}
-</style>
-
-</head>
-<body>
-
-<h2>Help system customization</h2>
-
-<p>The Eclipse help system can be configured and branded to suit your
-product by
-specifying custom defaults for number of help preferences.<br>
-</p>
-<p>The Help system itself is divided up into a number of separate
-plug-ins.
-These tables shows available preferences, and which plug-in
-defines them.
-</p>
-
-<h3>org.eclipse.help plug-in:</h3>
-
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;">Preference key</td>
-      <td style="font-weight: bold;">Usage<br>
-      </td>
-      <td style="font-weight: bold;">Default</td>
-    </tr>
-    <tr>
-      <td><code>HELP_DATA</code></td>
-      <td>Specifies the path of an XML file containing help data, such
-      as the order in which the table of contents should be displayed, and which books
-      and index contributions should be hidden from the user. The path may 
-      either be of the form PLUGINS_ROOT/ pluginId/path or &quot;path&quot;. If the value 
-      does not start with PLUGINS_ROOT the path is resolved relative to the 
-      product plugin.&nbsp; For example,
-      &quot;<code>helpData.xml</code>&quot; or &quot;PLUGINS_ROOT/org.eclipse.platform/helpData.xml&quot;. Consult the
-      <a href="ua_help_setup_help_data.htm">schema documentation</a> for details.</td>
-      <td><br></td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">baseTOCS</code> <span class="warning">(deprecated; use <code>HELP_DATA</code> instead)</span></td>
-      <td><span class="deprecated">Toc ordering. Ordered list of help TOC's (books) or TOC
-categories as they would appear on the bookshelf. All the other TOCS and categories
-will follow these. Non-present TOCs or categories on this list will be ignored. For TOCs, use
-the location of the TOC as /pluginId/path/to/toc.xml. For categories, use the category
-id.</span></td>
-      <td><br></td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">ignoredTOCS</code> <span class="warning">(deprecated; use <code>HELP_DATA</code> instead)</span></td>
-      <td><span class="deprecated">Disabling TOCs. List of help TOCs (books) or TOC categories that
-will be ignored by the help system.  The disabled TOCs/categories will not
-appear in the list of books, cannot be linked. Topics defined by disabled TOCs
-will not be available from search.
-Non-present TOCs or categories in this list will be ignored. For TOCs, use the
-location of the TOC as /pluginId/path/to/toc.xml. For categories, use the
-category id.</span></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">ignoredIndexes</code> <span class="warning">(deprecated; use <code>HELP_DATA</code> instead)</span></td>
-      <td><span class="deprecated">Disabling keyword indexes. List of help keyword index contributions that
-will be ignored by the help system. Keywords from the disabled indexes will not
-appear in the index view. For index XML files, use the path to the file in the form
-/pluginId/path/to/index.xml.</span></td>
-      <td><br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-
-<h3>org.eclipse.help.base plug-in:</h3>
-
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;">Preference key</td>
-      <td style="font-weight: bold;">Usage<br>
-      </td>
-      <td style="font-weight: bold;">Default</td>
-    </tr>
-    <tr>
-      <td><code>banner</code></td>
-      <td>Location of the banner page to display in the top frame<br>
-Example: <code>banner=/org.eclipse.help.webapp/advanced/banner.html</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>banner_height</code></td>
-      <td>Height of the banner frame<br>
-Example: <code>banner_height=60</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>footer</code></td>
-      <td>Location of the footer page to display in the bottom frame<br>
-Example: <code>footer=/org.eclipse.help.webapp/advanced/banner.html</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>footer_height</code></td>
-      <td>Height of the footer frame<br>
-Example: <code>footer_height=60</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>titleResource</code></td>
-      <td>The name of a project resource of the form &lt;plugin_name&gt;/&lt;resource_name&gt; which contains
-      the title of the help page.<br>
-Example: <code>titleResource=org.eclipse.help.webapp/help_webapp_plugin_name</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>help_home</code></td>
-      <td>The page to show in the content area when opening help.
-Specify your html page as <code>/pluginId/path/to/home.html</code>.</td>
-      <td><code>/org.eclipse.help.base/doc/help_home.html</code></td>
-    </tr>
-    <tr>
-      <td><code>page_not_found</code></td>
-      <td>The page to show in the content area when a topic file cannot be 
-      opened. If this variable is not specified the browser will show it's 
-      default 404 error page.</td>
-      <td><code>/org.eclipse.help.base/doc/page_not_found.html</code></td>
-    </tr>
-    <tr>
-      <td><code>showBreadcrumbs</code></td>
-      <td>Set to <code>true</code> or <code>false</code> to control the 
-      visibility of breadcrumbs.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>bookmarksView</code></td>
-      <td>Set to <code>true</code> or <code>false</code> to control the 
-      visibility of the bookmarks view.<br>
-      Note: this option has no effect in the infocenter.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>indexView</code></td>
-      <td>Set to <code>true</code> or <code>false</code> to control the 
-      visibility of the index view.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>windowTitlePrefix</code></td>
-      <td>Set to <code>true</code> or <code>false</code> to control the title of
-the browser
-window. If <code>true</code>, the
-title will have a form "Help - <code>&lt;PRODUCT_NAME&gt;</code>",
-otherwise the title will be
-"<code>&lt;PRODUCT_NAME&gt;</code>",
-where <code>&lt;PRODUCT_NAME&gt;</code>
-is the name of
-Eclipse product set in the primary feature.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>imagesDirectory</code></td>
-      <td>Directory containing images used in the help view. Images
-must have the same name as those in the org.eclipse.help.webapp
-plug-in.
-Use the <code>/pluginID/directory</code>
-format.</td>
-      <td><code>images</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.toolbarBackground</code></td>
-      <td>CSS background for toolbars. Value is used in browsers
-that display advanced help UI.</td>
-      <td><code>ButtonFace</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.viewBackground</code></td>
-      <td>CSS background for navigation views. Value is used in
-browsers that display advanced help UI. May be the empty string.</td>
-      <td><br></td>
-    </tr>
-    <tr>
-      <td><code>advanced.toolbarFont</code></td>
-      <td>CSS font for toolbars. Value is used in browsers that
-display advanced help UI.</td>
-      <td><code>icon</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.viewFont</code></td>
-      <td>CSS font for navigation views. Value is used in browsers
-that display advanced help UI.</td>
-      <td><code>icon</code></td>
-    </tr>
-    <tr>
-      <td><code>advanced.syncDefault</code></td>
-      <td>The default boolean value for whether the toc should automatically
-      be synchronized with the contents.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>basic.toolbarBackground</code></td>
-      <td>Background color for toolbars. Value is used in browsers
-displaying basic help UI.</td>
-      <td><code>#D4D0C8</code></td>
-    </tr>
-    <tr>
-      <td><code>basic.viewBackground</code></td>
-      <td>Background color for navigation views. Value is used in
-browsers displaying basic help UI.</td>
-      <td><code>#FFFFFF</code></td>
-    </tr>
-    <tr>
-      <td><code>locales</code></td>
-      <td>List of locales that infocenter will recognize and
-provide a customized content for; if locales (or languages) accepted by
-client browser are not matched with any locales in this list, the
-browser will be served content for default locale - the server locale,
-or locale specified by eclipse <code>-nl</code>
-command line option; if list is not
-specified, the browser will be served contents for its preferred
-locale; note: not providing this option may result in a large
-memory and disk space requirements as navigations and indexes will be
-created for each distinct preferred locale among browsers accessing the
-infocenter.<br>
-Example: <code>locales=en ja zh_CN
-zh_TW</code></td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>productIndex</code></td>
-      <td>If per-product, pre-built documentation index is provided with the
-product, the ID of the plug-in delivering the index must be specified
-to the help system here.</td>
-      <td><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>always_external_browser</code></td>
-      <td style="vertical-align: top;">Use embedded when possible (on
-Windows or Linux), or always external.&nbsp; Setting to true will force
-use of external browser.&nbsp; Option has no effect if embedded browser
-is not available on a given platform.<br>
-      </td>
-      <td><code>false</code></td>
-    </tr>
-    <tr>
-      <td><code>default_browser</code></td>
-      <td><p>Default external browser.&nbsp; ID of one of the external
-  web browsers contributed to org.eclipse.help.base.browser extension
-  point that help system will use. The browser's adapter <code>available()</code>
-  method must return true on the current system.</p>
-      <p>This preference controls external browsers in stand-alone help mode.
-      In the workbench mode, help uses browsers provided by workbench browser
-        support.</p></td>
-      <td>default dynamically set based on the browser available on a
-given system<br>
-      </td>
-    </tr>
-    <tr>
-      <td><code>custom_browser_path</code></td>
-      <td><p>Executable path for custom browser</p>
-      <p>This preference controls external browsers in stand-alone help mode.
-        In the workbench mode, help uses browsers provided by workbench browser
-      support.</p></td>
-      <td><code>C:\Program Files\Internet Explorer\IEXPLORE.EXE" %1</code> - on
-Windows,<br>
-      <code>"konqueror %1"</code> - on
-Linux<br>
-      <code>"mozilla %1"</code> - on
-other platforms
-      </td>
-    </tr>
-    <tr>
-      <td><code>showDisabledActivityTopics</code></td>
-      <td>Help system filters topics from disabled
-capabilities.&nbsp; This option controls this behavior and existence
-of&nbsp; Show All Topics button.<br>
-Accepted values: <code>never</code>, <code>off</code>, <code>on</code>, <code>always</code><br>
-&nbsp;<code>never</code> - topic from
-disabled capabilities are not shown<br>
-&nbsp;<code>off</code> - user can
-choose to show all topics, disabled topics
-initially hidden<br>
-&nbsp;<code>on</code> - user can choose
-to show all topics, all topics initially
-shown<br>
-&nbsp;<code>always</code> - topic from
-disabled capabilities are shown (filtering
-disabled)</td>
-      <td><code>off</code></td>
-    </tr>
-    <tr>
-      <td><code>activeHelp</code></td>
-      <td>Allows enabling and disabling execution of active help.
-The option has no effect in the infocenter setup, where active help is
-disabled.<br>
-Accepted values:<br>
-&nbsp;<code>true</code> - default
-active help actions enabled<br>
-&nbsp;<code>false</code> - active help
-framework disabled</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>restrictTopicParameter</code></td>
-      <td>Since 3.4. When true prevents topic parameters with an http or other 
-      protocol from causing an external URL to open in the content frame of the 
-      infocenter. This improves security and the recommended setting is true.</td>
-      <td><code>true</code></td>
-    </tr>
-    <tr>
-      <td><code>window_infopop</code></td>
-      <td>Allows enabling the old-style infopops when help key is pressed in 
-		workbench windows. If false, the new dynamic help view will open 
-		instead.</td>
-      <td><code>false</code></td>
-    </tr>
-    <tr>
-      <td><code>dialog_infopop</code><br>
-      </td>
-      <td>Allows enabling the old-style infopops 
-		when help key is pressed in dialogs. If false, the new dynamic help 
-		window will open instead.<br>
-      </td>
-      <td><code>false</code><br>
-      </td>
-    </tr>
-    <tr>
-      <td>help_view_open_mode</td>
-      <td>Controls where links in the help view are opened.&nbsp; <br>
-Accepted values:<br>
-&nbsp;<code>in_place</code> 
-      - open documents in the help view<br>
-&nbsp;<code>in_editor</code> - open document in an editor<br>
-&nbsp;<code>in_browser</code> - open document in a browser</td>
-      <td>in_place</td>
-    </tr>
-    <tr>
-      <td><a name="remoteHelp"></a>
-      <code>remoteHelpOn</code><br>
-      </td>
-      <td>Controls whether or not remote help is enabled.<br>
-Accepted values:<br>
-&nbsp;<code>true</code> - remote help enabled<br>
-&nbsp;<code>false</code> - remote help disabled</td>
-      <td><code>false</code><br></td>
-    </tr>
-    <tr>
-      <td colspan="3">The 5 remote help preferences below can each have multiple 
-      comma separated values if there is more than one infocenter contributing 
-      remote content. </td>
-    </tr>
-    <tr>
-      <td>remoteHostName</td>
-      <td>Specifies a name for this remote host which will appear in the table 
-      on the preference page</td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td><code>remoteHelpHost</code><br></td>
-      <td>Specifies the host name to access for remote help content. This must
-      be specified as a host name and cannot be a URL (i.e. do not include "http://").</td>
-      <td><br></td>
-    </tr>
-    <tr>
-      <td><code>remoteHelpPath</code><br>
-      </td>
-      <td>Specifies the context root of the Infocenter application running on the
-      specified host.</td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td><code>remoteHelpPort</code><br>
-      </td>
-      <td>Specifies the port to use to access remote help content.</td>
-      <td>&nbsp;</td>
-    </tr>   
-    <tr>
-      <td>remoteHelpICEnabled</td>
-      <td>Specifies that the infocenter will contribute remote content</td>
-      <td>&nbsp;</td>
-    </tr>   
-    <tr>
-      <td colspan="3">The four css preferences allow for the control of 
-      page appearance by inserting css files into every page served by the help 
-      server. Each can each contain zero or more comma separated paths of the 
-      form /plugin/path. These paths should contain only ASCII characters.<br>
-      If a path contains ${os} then that will be replaced with the name of the 
-      OS, any other parameters of the form ${parameter} are reserved for future 
-      use.</td>
-    </tr>
-    <tr>
-      <td><code>topic_css</code></td>
-      <td>A list of css file(s) to include in every non navigation page served by 
-      help system.</td>
-      <td >&nbsp;</td>
-    </tr>
-    <tr>
-      <td><code>nav_css</code></td>
-      <td>A list of css file(s) to include in every navigation page served by 
-      help system</td>
-      <td ><code>/PRODUCT_PLUGIN/book.css</code></td>
-    </tr>
-    <tr>
-      <td><code>narrow_css</code></td>
-      <td>A list of&nbsp; css file(s) to include in every page 
-      displayed in the help view or help tray .</td>
-      <td><code>/PRODUCT_PLUGIN/narrow_book.css,/PRODUCT_PLUGIN/${os}_narrow_book.css</code></td>
-    </tr>
-    <tr>
-      <td><code>disabled_css</code></td>
-      <td>A list of&nbsp; css file(s) to include in every page 
-      served by help system from a capability that is not enabled..</td>
-      <td><code>/PRODUCT_PLUGIN/disabled_book.css</code></td>
-    </tr>   
-  </tbody>
-</table>
-
-<h3 class="deprecated">org.eclipse.help.appserver plug-in:</h3>
-<span class="warning">Deprecated: This plug-in is no longer used by help. See table for alternative usage.</span>
-
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;"><span class="deprecated">Preference key</span></td>
-      <td style="font-weight: bold;"><span class="deprecated">Usage</span></td>
-      <td style="font-weight: bold;"><span class="deprecated">Default</span></td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">port</code> <span class="warning">(deprecated)</span></td>
-      <td><p class="deprecated">The port number on which the sever listens for http
-requests. If port is not given, an arbitrary
-port is picked by the system.</p>
-<p class="warning">Start Eclipse with "-vmargs -Dserver_port=&lt;port&gt;" instead</p></td>
-      <td>&nbsp;</td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">host</code> <span class="warning">(deprecated)</span><br>
-      </td>
-      <td><p class="deprecated">The host address or name to use
-  for connecting to the server. The default is nothing, and eclipse will
-  pick up an available local address.</p>
-        <p class="deprecated">Products using help in local mode (workbench or stand-alone, not infocenter),
-          can set this preference to &quot;<code>127.0.0.1</code>&quot; to
-          ensure help server is not exposed to other users on the network.<br>
-        </p>
-        <p class="warning">Start Eclipse with "-vmargs -Dserver_host=&lt;host&gt;" instead</p></td>
-      <td>&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-
-<h3 class="deprecated">org.eclipse.tomcat plug-in:</h3>
-<span class="warning">Deprecated: This plug-in is no longer used by help. No alternative commands available.</span>
-
-<table border="1">
-  <tbody>
-    <tr>
-      <td style="font-weight: bold;"><span class="deprecated">Preference key</span></td>
-      <td style="font-weight: bold;"><span class="deprecated">Usage</span></td>
-      <td style="font-weight: bold;"><span class="deprecated">Default</span></td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">acceptCount</code> <span class="warning">(deprecated)</span></td>
-      <td><span class="deprecated">The maximum queue length for incoming connection requests
-when all possible request processing threads are in use. Any requests
-received when the queue is full will be refused.</span></td>
-      <td><code class="deprecated">100</code></td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">maxProcessors</code> <span class="warning">(deprecated)</span><br>
-      </td>
-      <td><span class="deprecated">The maximum number of request
-processing threads to be created by this Connector, which therefore
-determines the maximum number of simultaneous requests that can be
-handled.</span>
-      </td>
-      <td><code class="deprecated">75</code><br>
-      </td>
-    </tr>
-    <tr>
-      <td><code class="deprecated">minProcessors</code> <span class="warning">(deprecated)</span><br>
-      </td>
-      <td><span class="deprecated">The number of request processing
-threads that will be created when this Connector is first started. This
-attribute should be set to a value smaller than that set for
-maxProcessors.</span>
-      </td>
-      <td><code class="deprecated">5</code><br>
-      </td>
-    </tr>
-  </tbody>
-</table>
-<br>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm
deleted file mode 100644
index 5357301..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_preindex.htm
+++ /dev/null

@@ -1,106 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Pre-indexing documentation</title>
-</head>
-<body>
-
-<h2>Pre-indexing documentation</h2>
-
-<p>When user searches help contents of a product, the search is performed
-within a documentation index. &nbsp;By default, this index &nbsp;is created
-on the first invocation of help search, but can be pre-built and delivered
-to the user with each plug-in, since 3.1, or as a complete index for a product. &nbsp;This
-prevents
-indexing
-from
-occurring
-on
-the user machine and lets the user obtain first search results faster.</p>
-
-<h3>Building a documentation index for a plug-in.</h3>
-
-<p>To build an index follow the steps:</p>
-<ul>
-  <li>add an <code>index</code> element to the <code>org.eclipse.help.toc
-      extension</code> in a documentation plug-in, to specify directory where
-      index will exist, for example 
-  <pre>&lt;extension
-      point=&quot;org.eclipse.help.toc&quot;&gt;
-   &lt;index
-         path=&quot;index&quot;&gt;
-   &lt;/index&gt;
-&lt;/extension&gt;</pre>
-  </li>
-  <li>Add the <code>help.buildHelpIndex</code> ANT task to the build.xml file in 
-  the plugin project by adding the lines below. A build.xml file can be created 
-  by right clinking on MANIFEST.MF in the package explorer and selecting the 
-  menu item PDE Tools/Create Ant Build File. This example build the index for 
-  the default locale and also for &quot;nl/fr&quot;. This should be modified to match the 
-  locales which you are using.<pre>&lt;target name=&quot;build.index&quot; description=&quot;Builds search index for the plug-in: org.eclipse.platform.doc.user.&quot; if=&quot;eclipse.running&quot;&gt;
-     &lt;help.buildHelpIndex manifest=&quot;plugin.xml&quot; destination=&quot;.&quot;/&gt;
-     &lt;help.buildHelpIndex manifest=&quot;plugin.xml&quot; destination=&quot;nl/fr&quot;/&gt;
-&lt;/target&gt;</pre>
-</li>
-  <li>create an index by building the target &quot;build.index&quot;. The ant task must be 
-  run in the same JRE as the workspace. To do this right click on build.xml, 
-  select the menu item Run As/Ant build... the ant dialog will appear. On the 
-  targets tab check only &quot;build.index&quot; and on the JRE tab select the radio 
-  button &quot;Run in the same JRE as the workspace&quot;. When you hit the 
-  &quot;Run&quot; button the indexes will be built.<br>
-</li>
-</ul>
-
-<h3>Building an index for a product</h3>
-
-<p>Per-product index is a one aggregate index of all documentation in the product.
-  It should be used in scenarios in which the set of documentation plug-ins is
-  not changing. For example an info-center installation will benefit
-  from per-product
-  index.</p>
-<p>To build an index follow the steps:<br>
-</p>
-<ul>
-  <li>build a product, including all documentation plug-ins,</li>
-  <li>create an index for a desired locale by running this command:     
-                          
-    <pre>eclipse -nosplash -application org.eclipse.help.base.indexTool -vmargs -DindexOutput=<i>outputDirectory</i> -DindexLocale=<i>locale</i></pre>
-from the directory containing the product. &nbsp;The following arguments
-need to be set :<br>
-    <b>outputDirectory</b> - specifies path of the directory where the index
-is to be saved<br>
-    <b>locale</b> - specifies locale for which the index will be built<br>
-  </li>
-</ul>
-<p>For example, running<br>
-</p>
-<pre>eclipse -nosplash -application org.eclipse.help.base.indexTool -vmargs -DindexOutput=d:/build/com.my.plugin -DindexLocale=en</pre>
-<p>will result in file <b>doc_index.zip</b> being saved in the <b>nl/en</b>
-directory that will be created under <b>d:/build/com.my.plugin</b>. &nbsp;The
-zip will contain index of contents of documents that are available to users
-when they run the product in the <b>en</b> locale.<br>
-</p>
-
-<h3>Packaging and Installation of the product's pre-built index</h3>
-
-Pre-built indices, the <b>doc_index.zip</b> files, need to be packaged as
-a plug-in. &nbsp; You can choose to use a plug-in associated with the primary
-feature, or choose to package the index for each language into separate fragments.<br>
-<br>
-For example, if product's documentation is available in three languages, say
-English, German and Simplified Chinese, a plug-in com.my.plugin can have the following structure:<br>
-<pre>com.my.plugin/<br>              plugin.xml<br>              nl/<br>                 de/<br>                    doc_index.zip<br>                 en/<br>                    doc_index.zip<br>                 zh/<br>                    CN/<br>                       doc_index.zip<br>              other files of this plugin</pre>
-<br>
- The ID of the plug-in needs to be specified as a <b>productIndex</b> preference
-for org.eclipse.help.base plug-in.&nbsp;For plug-in in the above example, the
-plugin_customization.ini
-file needs to contain the entry<br>
-<pre>org.eclipse.help.base/productIndex=com.my.plugin<br></pre>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm
deleted file mode 100644
index 0eafb64..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_rcp.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Rich Client Platform (RCP) help</title>
-</head>
-<body>
-
-<h2>Rich Client Platform (RCP) help</h2>
-
-<p>
-The Help system is an <em>optional</em> Rich Client Platform (RCP) component. That
-is, it is <em>not</em> part of the minimal RCP, but can be added to it. The following
-plug-ins and all of their dependencies, including optional dependencies must be added to the RCP base in order to run the Help system:
-</p>
-
-<p>
-<br>
-org.eclipse.help.ui<br>
-org.eclipse.help.webapp<br>
-</p>
-
-<p>
-<em>Note</em>: Help contents will only be made available to the user if there is
-content available. If there are no topics in the table of contents, the help will
-not be available.
-</p>
-
-<h3>Setting the Help Server Port and Hostname</h3>
-<p>The help server port and host name can be specified using virtual machine arguments as follows:</p><ul>	
-	<li><b>-Dserver_port=&lt;port number&gt;</b> specifies the port number that the
-	help server will use. </li>
-	<li><b>-Dserver_host=&lt;host name&gt;</b> specifies the host name which will be used
-	when the help system creates URLs which reference help pages.</li>
-</ul>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm
deleted file mode 100644
index 1e262c9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_setup_standalone.htm
+++ /dev/null

@@ -1,154 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Standalone help</title>
-</head>
-<body>
-
-<h2>Standalone help</h2>
-
-<p>If you are creating an application that is not based on 
-the Eclipse framework, you can still use the Eclipse help system. Your 
-application can package and install the stand-alone help system, a very small 
-version of Eclipse that has everything except the help system stripped out 
-of it. Then, your application can make API calls from its Help menu, or from UI 
-objects, to launch the help browser. The stand-alone help system has all the 
-features of the integrated help system, except workbench-integrated context help,
-the help view, and active help. When an application is not Java based, or help is
-required when the application is not running, it is possible to use stand-alone
-help from a system shell, a shell script or a desktop shortcut and provide command
-line options instead of calling Java APIs.</p>
-<P>The stand-alone help system allows passing number of options that can be used to customize various aspects of the help system. The following options are supported:</P><UL>
-	<LI><B>-eclipsehome</B> <I>eclipseInstallPath</I> - specifies Eclipse
-	installation directory. This directory is a parent to "plugins" directory
-	and eclipse executable.  The option must be provided, when current directory
-	from which infocenter is launched, is
-	not the same as Eclipse installation directory.</LI>
-	<LI><B>-host</B> <I>helpServerHost</I> - specifies host name of the
-	interface that help server will use. It overrides host name specified
-	the application server plugin preferences.</LI>
-	<LI><B>-data</B> <I>instanceArea</I> - specifies a path that Eclipse
-	can use to write instance data.  The value can be an absolute path of
-	a directory, or a path relative to Eclipse installation directory.
-	The option must be provided when Eclipse is installed in the read only
-	location, or has been customized to override osgi.instance.area or
-	osgi.instance.area.default properties. </LI>
-	<LI><B>-port</B> <I>helpServerPort</I> - specifies port number that
-	help server will use. It overrides port number specified the
-	application server plugin preferences.</LI>
-	<LI><B>-dir ltr </B> or<B> -dir rtl</B> - sets left-to right or right-to-left
-	  rendering direction of help UI in the browser.</LI>
-	<LI>Additionally, most <A
-		href="../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">options
-	accepted by Eclipse executable</A> can be passed. They are especially useful during debugging and for applying customization to Eclipse.
-	For example, passing an option
-	<PRE><EM><SPAN style="font-style: normal">-nl fr_FR</SPAN></EM> </PRE>
-	will start help system in French language instead of a language specified by the machine's locale.</LI>
-</UL>
-
-<h3>Installation/packaging</h3>
-
-These steps are for the help system integrator and are not meant to address all the
-possible scenarios. It is assumed that all your documentation is delivered as eclipse
-plug-ins and, in general, you are familiar with the eclipse help system.
-<ol>
-  <li>Download the eclipse Platform Runtime Binary driver from
-  <a target="_blank" href="http://eclipse.org/downloads/">eclipse.org</a>.</li>
-  <li>Install (unzip) the driver under your application directory, for 
-  example, <var>d:\myApp</var>. This will create an eclipse sub-directory,
-  d:\myApp\eclipse that contains the code required for the eclipse platform
-  (which includes the help system). </li>
-</ol>
-
-<h3>How to call the help classes from Java</h3>
-
-<ol>
-  <li>Make sure <code>d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar</code>
-  is on your classpath, where <code>[version]</code> is the version of the plugin
-  you're using (e.g. <code>org.eclipse.help.base_3.2.0.jar</code>). The class you use
-  to start, launch, and shut down the help system is
-  <code>org.eclipse.help.standalone.Help</code>.
-  </li>
-  <li>Create an array of <code>String</code> objects containing options that you want
-  to pass to help system support. Typically, the <code>eclipsehome</code> option is
-  needed.
-    
-  <pre>String[] options = new String[] { &quot;-eclipsehome&quot;, &quot;d:\\myApp\\eclipse&quot; };</pre>
-  
-  </li>
-	<LI>In your application, create an instance of the <code>Help</code> class by
-	passing in the options. This object should be held onto until the end of your
-	application.
-	<pre>Help helpSystem = new Help(options);</pre>
-	</LI>
-	<li>To start the help system:
-  <pre><em><span style="font-style: normal">helpSystem.start();</span></em> </pre>
-  </li>
-  <li>To invoke help when needed:
-  <pre><em><span style="font-style: normal">helpSystem.displayHelp();</span></em> </pre>
-  <p>You can also call help on specific primary TOC files or topics:</p>
-  <pre>helpSystem.displayHelp(&quot;/com.mycompany.mytool.doc/toc.xml&quot;);
-helpSystem.displayHelp(&quot;/com.mycompany.mytool.doc/tasks/task1.htm&quot;);</pre>
-  </li>
-  <li>To launch context sensitive help, call 
-  helpSystem.displayContext(contextId, x, y) where contextId is a fully 
-  qualified context id. The screen coordinates, x and y, are not currently used.
-  </li>
-	<LI>
-	<P>At the end of your application, to shutdown the help system:</P>
-	<PRE><EM><SPAN style="font-style: normal">helpSystem.shutdown();</SPAN></EM> </PRE></LI>
-</ol>
-
-<h3>How to call the help from the command line</h3>
-
-<p>
-The <code>org.eclipse.help.standalone.Help</code> class has a main method you can
-use to launch stand-alone help from the command line. The command line arguments
-syntax is:
-</p>
-<pre><em><span style="font-style: normal">-command start | shutdown | (displayHelp [href]) [-eclipsehome eclipseInstallPath] [-data instanceArea] [-host helpServerHost] [-port helpServerPort] [-dir rtl] [platform options] [-vmargs JavaVMarguments]</span></em></pre>
-<P>A simple way to display help is to invoke</P>
-<pre>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar org.eclipse.help.standalone.Help -command displayHelp</pre><P>from within d:\myApp\eclipse directory, where <code>version</code> is the plug-in's version. To display a specific TOC file or topic use</P>
-<PRE>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar org.eclipse.help.standalone.Help -command displayHelp /com.mycompany.mytool.doc/tasks/task1.htm</PRE>
-<P>The calls above to display help will cause help system to start, display help, and keep running to allow a user to continue browsing  help after the command is executed. To control the life cycle of the help system, use start and shutdown commands, in addition to the displayHelp command. For example, you may call</P>
-<PRE>java -classpath d:\myApp\eclipse\plugins\org.eclipse.help.base_[version].jar org.eclipse.help.standalone.Help -command start</PRE>
-
-<h3>[Optional] Installing a minimal stand-alone help system</h3>
-
-<p>
-The stand-alone help does not require the entire eclipse Platform package. It is 
-possible to run the stand-alone help using only those plugins from the feature 
-org.eclipse.help. To do this perform the following steps.</p>
-
-<ol>
-  <li>Download an eclipse SDK build and upzip it into two different locations, 
-  &lt;location1&gt; and &lt;location1&gt;</li>
-  <li>Remove the eclipse plugins directory from location1</li>
-  <li>Start Eclipse in location2 and import the org.eclipse.help feature into 
-  your workspace using File/Import/Plug-in Development/Features</li>
-  <li>Export the help feature and it's plugins to location1/eclipse using 
-  File/Export/Plug-in Development/Deployable Features. The plugins directory 
-  which was just deleted will be replaced by a directory containing a smaller 
-  number of plugins.</li>
-  <li>From location1 start standalone help from the command line as described in 
-  the previous section.</li>
-</ol>
-
-<p>
-Some documentation plug-ins may have dependencies on other plug-ins, usually by
-specifying required plug-ins in their manifest. The dependent plug-ins need to be
-installed as well. Additionally, plug-ins that were designed for earlier than 3.0
-version of eclipse implicitly require
-<code>org.eclipse.core.runtime.compatibility</code> plug-in being present to work.
-</p>
-
-<p>See <a href="ua_help_setup_preferences.htm">Product customization</a> for more
-information on customizing the help system.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm
deleted file mode 100644
index 7aa879b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_help_war.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Deploying the infocenter as a Web Archive</title>
-</head>
-<body>
-
-<h2>Deploying the infocenter as a Web Archive</h2>
-
-<p>Using Eclipse 3.4 or later it is possible to configure the help plugins to be deployed 
-as a web archive (war file) which will act as a fully <br>
-functioning infocenter. The instructions below assume a Tomcat server has been 
-installed, but with minor modifications <br>
-these steps should work for any full featured server. <br>
-<br>
-In your Eclipse installation locate the plugin org.eclipse.help.webapp.&lt;version&gt;.jar 
-and copy it to a temporary directory, <br>
-unzip the copy into that folder.</p>
-
-<ol>
-  <li>In the webapp plugin locate the web-archive directory and underneath that 
-there will be two directories titled &quot;help&quot; and <br>
-&quot;org.eclipse.help.infocenter-feature&quot;.</li>
-  <li>Import the org.eclipse.help.infocenter-feature using File-&gt;Import-&gt;Existing 
-Project.</li>
-  <li>Export org.eclipse.help.infocenter-feature as a deployable feature and set 
-the destination to be
-web-archive/help/WEB-INF/eclipse in the area where org.eclipse.help.webapp.&lt;version&gt;.jar 
-was unzipped.</li>
-  <li>Add some documentation plugins to the webapps/help/WEB-INF/eclipse/plugins 
-directory.</li>
-  <li>Download org.eclipse.equinox.http.servletbridge_&lt;version&gt;.jar and 
-  org.eclipse.equinox.servletbridge_&lt;version&gt;.jar from the
-  <a href="http://download.eclipse.org/eclipse/equinox/">equinox download site</a>. 
-  Select a version of Equinox that matches the version of Eclipse you are 
-  running to take you to the downloads page.</li>
-  <li>Extract servletbridge.jar from org.eclipse.equinox.servletbridge_&lt;version&gt;.jar.</li>
-  <li>Add the file servletbridge.jar to the help/WEB-INF/lib directory. You may 
-need to create this directory.</li>
-  <li>Add the file org.eclipse.equinox.http.servletbridge_&lt;version&gt;.jar to the 
-help/WEB-INFeclipse/plugins directory</li>
-  <li>At this stage you can create a war file from the help directory or you can 
-copy the directory and its contents to the webapps 
-folder of your Tomcat installation.</li>
-<li>For Tomcat only. In conf/server.xml add URIEncoding="UTF-8" to the connector element, for example
-<pre>
-&lt;Connector port="8080" URIEncoding="UTF-8" etc.&gt;</pre> If this step is not performed
-search will fail if the search term contains non ASCII characters.
- </li>
-  <li>Start Tomcat and see the help system start up.</li>
-</ol>Notes: If you look in the config.ini in the help.war file under directory help/WEB_INF/eclipse/configuration 
-you will notice the <br>
-line eclipse.product=org.eclipse.productname. If your product has help system 
-customizations in a product plugin you can <br>
-activate these by changing this line to point to your product plugin.<br>
-&nbsp;
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm
deleted file mode 100644
index 58c3ab4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Welcome</title>
-</head>
-<body>
-
-<h2>Welcome</h2>
-
-<p>Welcome (also referred to as Intro) support is a set of extension points that 
-control the initial user experience of a product or rich client application.&nbsp; 
-These extension points allow plug-ins to define specialized pages that introduce a
-platform product to new users. The Intro pages are&nbsp; shown the first time a 
-product is started&nbsp; guiding users into discovering a product's 
-functionality.&nbsp; An Intro can be anything from a single page displaying a Macromedia Flash demo, to multiple
-pages that are extensible and follow the Eclipse platform's pluggable architecture.
-</p>
-
-<p>Intro extensions define a class which extends
-the abstract class 
-org.eclipse.ui.part.IntroPart which is responsible for painting the contents of 
-the screen. An IntroPart shares some similarities with views and editors, which 
-are also Workbench parts. When the workbench initializes, it creates an 
-intro site that reserves space for the intro page. The intro part implementation 
-for the site is determined using product configuration information. Once an 
-intro part is shown, it can move between two modes: </p>
-
-<ul>
- <li>in <b>full mode</b>, the intro part takes over the main workbench area.</li>
- <li>in <b>standby mode</b>, the intro part moves to the side, allowing the current
-     perspective to remain visible.</li>
-</ul>
-
-<p>It is possible to write an intro part from 
-scratch but there are advantages to using the customizable intro part described 
-below. </p>
-
-<h3>The Customizable Intro Part</h3>
-
-<p>The intro part used by the Eclipse Platform 
-and SDK is based on the class org.eclipse.ui.intro.config.CustomizableIntroPart. 
-An intro of this kind will be based on a configuration which can be extended by 
-individual plugins. The configuration uses an xml file contributed using the 
-extension point org.eclipse.ui.intro.config to define the intro content. 
-Individual plugins can extend the configuration using the 
-org.eclipse.ui.intro.configExtension. extension point. The customizable intro 
-part has several benefits:</p>
-
-<ul>
-  <li>The content is separated from the 
-  presentation.</li>
-  <li>Individual plugins can extend the intro 
-  content using the org.eclipse.ui.intro.configExtension. extension point.</li>
-  <li>The presentation uses HTML allowing css 
-  to be used to set the background, layout the elements and style the text. for</li>
-  <li>On systems where a browser is unavailable the intro content will be presented using SWT.</li>
-</ul>
-
-<h3>Universal Intro</h3>
-
-<p>Universal Intro is an intro configuration based on the customizable intro 
-part and is used by the Eclipse Platform and SDK. The Universal Intro configuration provides a standardized set of pages and 
-anchors which can be extended by other plugins. Use of Universal Intro is 
-encouraged because it allows a plugin to contribute intro content to any product 
-that uses Universal Intro. Without Universal Intro it would be necessary to 
-write a config extension for each intro configuration that a plugin might 
-possibly contribute to.</p>
-
-<h3>Related Topics</h3>
-
-<p><a href="ua_intro_defining.htm">Defining an Intro Part</a><br>
-<a href="ua_intro_cust_intro_part.htm">Using the Customizable Intro Part</a><br>
-<a href="ua_intro_universal.htm">Universal Intro</a></p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm
deleted file mode 100644
index a2b041d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_intro_part.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Using the CustomizableIntroPart</title>
-</head>
-<body>
-
-<h2>Using the CustomizableIntroPart</h2>
-
-<p>The platform's <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a> 
-is an intro part which reads intro content from XML files and presents the 
-content using HTML. Cascading Style Sheets (css) can be used to control most 
-aspects of the presentation including background image, font style and layout.&nbsp; 
-The following extensions are required to use <b> <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html">CustomizableIntroPart</a>.</b></p>
-
-<ul>
-  <li><a href="../reference/extension-points/org_eclipse_ui_intro.html"><b>
-  org.eclipse.intro</b></a> to defines an intro id and specifies that it will 
-  use the <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a></li>
-  <li><b><a href="../reference/extension-points/org_eclipse_ui_intro.html">
-  org.eclipse.intro</a></b> to define the product binding which specifies which 
-  intro a product will use</li>
-  <li>
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a> </b>
-  to defines the intro content for a particular intro id</li>
-</ul>
-
-<p>In addition 
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a> </b>
-extensions can be used from any plugin to extend the intro content.  This structure allows product plug-in developers to focus on developing their intro content rather than
-implementing an intro part scheme from scratch.  If a different intro class is specified, then these two extension points
-are not utilized and the specified class must implement its own scheme for intro content format and configuration.
-</p>
-
-<h3>Related Topics</h3>
-
-<p>
-<a href="ua_intro_define_content.htm">Defining intro content</a><br>
-<a href="ua_intro_minimal.htm">Defining a minimal intro configuration</a><br>
-<a href="ua_intro_defining_config.htm">Defining an intro config</a></p>
-
-<p>&nbsp;</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
deleted file mode 100644
index 5dc30bc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_cust_static.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Displaying static HTML content in a CustomizableIntroPart</title>
-</head>
-<body>
-
-<h2>Displaying static HTML content in a CustomizableIntroPart</h2>
-
-<p>Just like any intro part implementation, to use a CustomizableIntroPart you need to follow the basic steps to bind it to a product. However, there is an extra step needed to use this intro part and it is binding a "configuration" with it. Just like you bind an intro to a product, you must bind an <em>introConfig </em> to a customizableIntroPart. Here is a sample configuration: </p>
-
-<pre>
-   &lt;extension point="org.eclipse.ui.intro.config"&gt;
-      &lt;config
-            id="static001_configId"
-            introId="org.eclipse.ui.intro.examples.static_introId"
-            content="introContent.xml"&gt;
-         &lt;presentation
-               home-page-id="homePageId" 
-               standby-page-id="standbyPageId"&gt;
-            &lt;implementation
-                  os="win32"
-                  kind="html"/&gt; 
-            &lt;implementation
-                  kind="swt"/&gt;
-         &lt;/presentation&gt;
-      &lt;/config&gt;
-   &lt;/extension&gt; 
-</pre>
-
-<p> In the above contribution a <em>configuration </em> is registered with an intro part with id <em>org.eclipse.ui.intro.examples.static_introId. </em>(It is assumed that this intro part is a customizable intro part instance that has already been registered with the workbench). This configuration defines the content to be presented in the intro part and dictates how it is presented to the user.&nbsp; The content is defined in an xml markup file, <em>introContent.xml, </em>while the presentation is dictated by two <em> implementation </em> elements in the markup.</p>
-<p>A config presentation can be either an SWT browser based or a UI forms based presentation. In the above contribution, the presentation will be&nbsp;"html", ie browser based on win32 platforms, while it will be "swt" ie: UI forms based on all other platforms. At runtime, when the workbench is trying to instantiate the CustomizableIntroPart, the operating system is determined and the correct implementation of the presentation is chosen. <br>
-  Also, a <em>home-page-id </em>or root page needs to be specified as it will be the first page displayed by the customizableIntroPart. If a <em>standby-page-id </em> is also specified, it will be displayed in the intro part when the intro part is put into standby mode.</p>
-<p>The details of what the content file can be found in the extension point documentation. For a simple example, and to contribute static content we will use the following as content: </p>
-
-<pre>
-   &lt;introContent&gt;
-      &lt;page
-            id="homePageId"
-            url="http://eclipse.org"/&gt;
-      &lt;page
-            id="standbyPageId"
-            url="./static001/standby.html"/&gt;
-   &lt;/introContent&gt; 
-</pre>
-
-<p> In the above contribution, a simple url is used as the root page, in this case is a url pointing to the eclipse.org web site. This was done for simplicity. The root page could have been any html file, for example, a local html file that loads a flash demo. There is also a standby page defined that will be displayed when the intro is placed into standby mode.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
deleted file mode 100644
index 5490d25..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_define_content.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining intro content</title>
-</head>
-<body>
-
-<h2>Defining intro content</h2>
-
-<p>
-Now we can look at the content itself.  Content is described in terms of pages.  All pages have an <b>id</b> attribute.
-This is the id that is used when defining the home and standby pages, and other places where there is a reference
-to a page.  Otherwise, the relevant attributes depend on the kind of page that is defined.
-There are two basic types of pages:
-</p>
-<ul>
-<li><b>Static pages</b> are plain HTML files.  These pages use the normal HTML mechanisms to link to other
-pages.  Static pages need not be defined in the config content file, except for the home page.  Since the home
-page is specified by id (<b>home-page-id</b>) in the <b>presentation</b> element, there must be a page definition
-using that id in the content file.  This page need only define a <b>url</b>.  All other subelements will be ignored
-since the HTML page itself will describe the page content. All other HTML intro pages contributed by the plug-in
-must be included with the plug-in, but do not need to be specified in the content file. HTML files located in other
-plug-ins or on the web may be referenced also. </li>
-<li><b>Dynamic pages</b> are described in the XML content file using subelements that describe the content of the
-page.  The subelements are UI items often found in HTML-like pages.  Depending on the implementation, these pages
-will either be dynamically translated to HTML (when the implementation <b>kind</b> is html) or else dynamically
-created as SWT-based UI forms (when the implementation <b>kind</b> is swt).  The following subelements
-can be defined in a page: 
-<ul>
-<li>A <b>group</b> is used to group other subelements and define a consistent style across the group.</li>
-<li>A <b>link</b> defines a link that can be displayed using an image and text.  The link can navigate to another
-page and optionally run an intro action.  Actions are specified as commands in the URL.</li>
-<li>The <b>text</b> and <b>img</b> elements show text and image content.</li>
-<li>The <b>include</b> element includes a previously defined subelement.  The element is referred to by its id.  </li>
-<li>The <b>head</b> element defines additional HTML to be included in the head section of the page
-when the html implementation is used. </li>
-<li>The <b>html</b> element defines additional HTML to be included in the body of the page
-when the html implementation is used.</li>
-</ul>
-A <b>title</b> for a page may also be defined.  A page may also specify that
-its content is defined in a separate <b>content</b> file.  Breaking up pages into separate
-files may be useful when performance is a concern, since an intro page's contents won't be initialized until needed.
-</li>
-</ul>
-
-<p>
-The best way to get a feel for the content definition format is to browse the
-implementations in the Eclipse SDK. The snippet below shows an example of this:
-</p>
-
-<pre>
-   &lt;introContent&gt;
-      &lt;page alt-style="css/root_swt.properties" style="css/root.css" id="root" style-id="page"&gt;
-         &lt;title style-id="intro-header"&gt;Welcome to Eclipse Platform&lt;/title&gt;
-         &lt;group id="links-background"&gt;
-            &lt;group id="page-links"&gt;
-               &lt;link label="Overview" url="http://org.eclipse.ui.intro/showPage?id=overview" id="overview" style-id="left"&gt;
-                  &lt;text&gt;Find out what Eclipse is all about&lt;/text&gt;
-               &lt;/link&gt;
-               &lt;link label="Tutorials" url="http://org.eclipse.ui.intro/showPage?id=tutorials" id="tutorials" style-id="left"&gt;
-                  &lt;text&gt;Let us guide you through Eclipse end-to-end tutorials&lt;/text&gt;
-               &lt;/link&gt;
-               &lt;link label="Samples" url="http://org.eclipse.ui.intro/showPage?id=samples" id="samples" style-id="right"&gt;
-                  &lt;text&gt;Explore Eclipse development through code samples&lt;/text&gt;
-               &lt;/link&gt;
-               &lt;link label="Whats New" url="http://org.eclipse.ui.intro/showPage?id=news" id="news" style-id="right"&gt;
-                  &lt;text&gt;Find out what is new in this release&lt;/text&gt;
-               &lt;/link&gt;
-            &lt;/group&gt;
-         &lt;/group&gt;
-      ...
-</pre>
-
-<p>
-Elements on a page can also be <b>filteredFrom</b> a particular implementation.  This allows page designers
-to design with particular platforms in mind.  There are many more powerful attributes that 
-can be used when describing a page and its contents.  See the extension point documentation for 
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></b>
-and its associated <a href="../reference/extension-points/introContentFileSpec.html">intro content file format specification</a> for a complete reference of 
-valid elements, subelements, and their attributes.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
deleted file mode 100644
index 1f881ef..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining an intro part</title>
-</head>
-<body>
-
-<h2>Defining an intro part</h2>
-
-<p>
-The <a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a> interface
-and the <b><a href="../reference/extension-points/org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></b>
-extension point make up the generic mechanism that can be used to create your own intro support for
-a given product.  The main purpose of this extension is to define the class that implements
-<a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a> and to
-specify the binding between a product id and an intro part.  For example, the following contribution
-defines a hypothetical intro part to be shown by the workbench on startup:
-</p>
-
-<pre>
-   &lt;extension  
-         point="org.eclipse.ui.intro"&gt;
-      &lt;intro
-            class="com.example.SampleIntroPart"
-            id="someId"
-            icon="someIcon.png"&gt;
-      &lt;/intro&gt;
-      &lt;introProductBinding
-            introId="someId"
-            productId="com.example.someProductId"&gt;
-      &lt;/introProductBinding&gt;
-   &lt;/extension&gt;
-</pre>
-
-This contribution first defines the intro part and assigns it the id "someId".  It then binds this
-intro part to a product whose id is "com.example.someProductId".  On platform startup, the class specified
-in the <b>class</b> attribute will be instantiated by the workbench and presented to the user as the
-introduction to the product.  This is the lowest level integration into the 
-<a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a>
-interface.
-<p>The platform supplies its own <a href="../reference/api/org/eclipse/ui/intro/IIntroPart.html"><b>IIntroPart</b></a>
-implementation called <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a>
-that allows for the content and presentation of the intro to be customized.  Below is the snippet that defines the intro part for the workbench.
-We won't go over the mechanics of implementing an intro part since we want to focus on defining
-the intro content.  (See the extension point documentation and javadoc referenced above for more detail
-if you need it.)
-</p>
-
-<pre>
-   &lt;extension  
-         point="org.eclipse.ui.intro"&gt;
-      &lt;intro
-            class="org.eclipse.ui.intro.config.CustomizableIntroPart"
-            id="org.eclipse.platform.intro"&gt;
-      &lt;/intro&gt;
-      &lt;introProductBinding
-            introId="org.eclipse.platform.intro"
-            productId="org.eclipse.platform"&gt;
-      &lt;/introProductBinding&gt;
-   &lt;/extension&gt;
-</pre>
-
-The above contribution defines the 
-<a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a> as the
-intro part to be used for the Eclipse SDK platform.  The rest of this discussion shows you how to use and extend
-this part.
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
deleted file mode 100644
index 4623668..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_defining_config.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining an intro config</title>
-</head>
-<body>
-
-<h2>Defining an intro config</h2>
-
-<p>
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></b>
-describes the id of the intro config that is to show our content, and the name of the
-XML file that contains the specific definition for the intro content.  It is expected that only one
-intro config should be defined for a given <a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a>.
-(Only the first intro config found can be shown in a
-<a href="../reference/api/org/eclipse/ui/intro/config/CustomizableIntroPart.html"><b>CustomizableIntroPart</b></a>.)
-</p>
-
-<pre>
-   &lt;extension   
-         id="intro"
-         point="org.eclipse.ui.intro.config"&gt;
-      <b>&lt;config
-            introId="org.eclipse.platform.intro"
-            id="org.eclipse.platform.introConfig"
-            content="$nl$/introContent.xml"&gt;</b>
-         &lt;presentation
-               home-page-id="root"
-               standby-page-id="standby"&gt;
-            &lt;implementation
-                  ws="win32"
-                  style="css/shared.css"
-                  kind="html"
-                  os="win32"&gt;
-            &lt;/implementation&gt;
-            &lt;implementation
-                  kind="swt"&gt;
-            &lt;/implementation&gt;
-         &lt;/presentation&gt;
-      &lt;/config&gt;
-   &lt;/extension&gt;  
-</pre>
-
-The path for the file is relative to the plug-in's directory.  (Note
-the use of the <tt>$nl$</tt> variable in the directory name, which means the file will be located in a directory specific
-to the national language of the target environment.)
-<p>
-The config extension allows you to specify both the content and the presentation of the content.
-While the <b>content</b> element focuses on defining pages, the
-<b>presentation</b> element describes presentation-related attributes that describe how
-pages will be shown.  The page id for the intro home page (in <b>full mode</b>) must be specified,
-and the standby page id (in <b>standby mode</b>) is optional.  The home page is the page that is shown when the product is first started.
-A presentation can specify one or more <b>implementations</b> for showing the pages.  Implementations are specified
-per platform and windowing system, allowing you to take advantage of platform-specific features for showing
-page content. For example, the windows platform has a robust HTML browser widget, so an HTML-based implementation
-is used for intro content.  Other platforms without this capability use an SWT-based implementation that maps
-page descriptions to an SWT-based form.  An implementation that does not specify either a windowing system or operating system will be considered
-the generic implementation; to ensure an intro is shown on all platforms, it is important to define
-such an implementation.  The workbench will first look for an implementation that matches the current operating system and
-windowing system.  If one cannot be found, it will choose the generic implementation.  Most of these details
-are handled at the product configuration level, so we won't discuss them any further here.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
deleted file mode 100644
index 46570ed..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_custom_url.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining a custom IntroURL action</title>
-</head>
-<body>
-
-<h2>Defining a custom IntroURL action</h2>
-
-<p>
-Using the <b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
-extension point, plug-ins can contribute their own custom actions that can be used as a <b>url</b> value for a link element in a page.
-For example, consider the following link:
-</p>
-<p><tt>http://org.eclipse.ui.intro/runAction?pluginId=org.eclipse.pde.ui&amp;amp;class=org.eclipse.pde.ui.internal.samples.ShowSampleAction&amp;amp;id=org.eclipse.sdk.samples.swt.examples</tt></p>
-<p>This IntroURL will run an action class called <b>ShowSampleAction</b>, which is in a package "org.eclipse.pde.ui.internal.samples" in the plug-in
-"org.eclipse.pde.ui".  The id of the sample to run is "org.eclipse.sdk.samples.swt.examples".
-</p>
-<p>To define a custom version of this intro URL, you can use the following markup:</p>
-
-<pre>
-   &lt;extension point="org.eclipse.ui.intro.configExtension"&gt;
-      &lt;action
-            name="myCommand"
-            <b>replaces="runAction?pluginId=org.eclipse.pde.ui&amp;amp;class=org.eclipse.pde.ui.internal.samples.ShowSampleAction"</b>&gt;
-      &lt;/action&gt;
-   &lt;/extension&gt;
-</pre>
-
-With the above extension you can now use the following URL to run the same action:
-<p><tt>http://org.eclipse.ui.intro/myCommand?id=org.eclipse.sdk.samples.swt.examples</tt></p>
-<p>
-The action "myCommand" will be replaced by the value of the <b>replaces</b> attribute and any remaining URL
-parameters will be appended to the end.  Once the substitution is made, the resulting URL will be expanded back into:</p>
-<p><tt>http://org.eclipse.ui.intro/runAction?pluginId=org.eclipse.pde.ui&amp;amp;class=org.eclipse.pde.ui.internal.samples.ShowSampleAction&amp;amp;id=org.eclipse.sdk.samples.swt.examples</tt></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
deleted file mode 100644
index 1717441..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_standbypart.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Contributing a standby content part</title>
-</head>
-<body>
-
-<h2>Contributing a standby content part</h2>
-
-<p>
-Plug-ins can also implement a part for displaying alternative content when the intro page is in standby mode.  For
-example, the platform defines a standby part that will show a cheat sheet for related intro content.  The part is launched using a page
-link with a specialized URL.  Standby parts are launched using a URL containing a special command for showing
-a standby part, such as <tt>http://org.eclipse.ui.intro/showStandby?partId=somePartId</tt>.
-The part is defined in the <b>standbyContentPart</b> subelement in the 
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
-extension. An <b>id</b>, <b>pluginId</b>, and <b>class</b> must be specified for the part.  The class must implement
-<a href="../reference/api/org/eclipse/ui/intro/config/IStandbyContentPart.html"><b>IStandbyContentPart</b></a>.
-The following snippet shows how the platform defines a standby part for showing cheat sheets.
-</p>
-
-<pre>
-   &lt;extension point="org.eclipse.ui.intro.configExtension"&gt;
-      &lt;standbyContentPart
-            id="org.eclipse.platform.cheatsheet"
-            class="org.eclipse.platform.internal.CheatSheetStandbyContent"
-            pluginId="org.eclipse.platform"/&gt;
-   &lt;/extension&gt;
-</pre>
-
-This cheat sheet could be launched from an intro page using a <b>link</b> subelement whose
-URL is <tt>http://org.eclipse.ui.intro/showStandby?partId=org.eclipse.platform.cheatsheet&amp;input=org.eclipse.pde.helloworld</tt>.
-This IntroURL would launch the org.eclipse.platform.cheatsheet standby content part and set its input to
-"org.eclipse.pde.helloworld".  The detailed mechanics for implementing a standby part are beyond the scope
-of this discussion.   See <a href="../reference/api/org/eclipse/ui/intro/config/IStandbyContentPart.html"><b>IStandbyContentPart</b></a>
-and its related classes for more information.
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm
deleted file mode 100644
index 332e6df..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_ext_theme.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining intro themes</title>
-</head>
-<body>
-
-<h2>Defining intro themes</h2>
-
-<p>
-A theme defines the overall <em>appearance</em> of the intro. It is simply a way
-of grouping all the presentation files (styles and images) in one place that can
-be pointed at or switched as one.
-</p>
-
-<h3>Definition</h3>
-
-<p>
-To define a theme, extend your intro configuration using the
-<code>org.eclipse.ui.intro.configExtension</code> and use the <code>theme</code>
-element, as shown in the example below:
-</p>
-
-<pre>
-   &lt;extension
-         point="org.eclipse.ui.intro.configExtension"&gt;
-      &lt;theme
-            default="true"
-            id="org.eclipse.ui.intro.universal.circles"
-            name="%theme.name.circles"
-            path="$nl$/themes/circles"
-            previewImage="themes/circles/preview.png"&gt;
-         &lt;property
-               name="launchbarBackground"
-               value="#a1c2cb"/&gt;
-         &lt;property
-               name="launchbarOverviewIcon"
-               value="$theme$graphics/launchbar/overview16.png"/&gt;
-         &lt;property
-               name="launchbarFirststepsIcon"
-               value="$theme$graphics/launchbar/firststeps16.png"/&gt;
-         &lt;property
-               name="launchbarTutorialsIcon"
-               value="$theme$graphics/launchbar/tutorials16.png"/&gt;
-         &lt;property
-               name="launchbarSamplesIcon"
-               value="$theme$graphics/launchbar/samples16.png"/&gt;
-         &lt;property
-               name="launchbarWhatsnewIcon"
-               value="$theme$graphics/launchbar/whatsnew16.png"/&gt;
-         &lt;property
-               name="launchbarMigrateIcon"
-               value="$theme$graphics/launchbar/migrate16.png"/&gt;
-         &lt;property
-               name="launchbarWebresourcesIcon"
-               value="$theme$graphics/launchbar/webresources16.png"/&gt;
-      &lt;/theme&gt;
-   &lt;/extension&gt;
-</pre>
-
-<p>
-Consult the <a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">schema documentation</a>
-for details on all the available attributes relating to themes.
-</p>
-
-<p>
-Each theme has a unique identifier, translatable name, preview image, and a path
-to the root theme folder. The intro plug-in does not provide any UI for theme
-manipulation. The only way to select a theme is via the preference
-<code>org.eclipse.ui.intro/INTRO_THEME</code> in plugin_customization.ini. 
-</p>
-
-<h3>Enabling themes</h3>
-
-<p>
-Theme support by itself does not make intro implementations theme-enabled.
-Concrete intro implementations can choose to expose themes in a more substantial
-way (and in fact Universal Welcome implementation does exactly that with the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.platform.introCustomization)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Welcome</b></a>
-
-preference page.
-</p>
-
-<p>
-Theme-enabled intro implementation must make all the references to style and
-presentation resources using the <code>$theme$</code> substitution variable. Absolute paths
-for images, pages, styles, etc. will be computed by resolving the substitution
-variable using the path of the currently active theme.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
deleted file mode 100644
index ad4e1f6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Extending an intro config</title>
-</head>
-<body>
-
-<h2>Extending an intro config</h2>
-
-<p>
-An intro configuration can be extended in several ways:
-</p>
-
-<ul>
-<li><a href="ua_intro_ext_theme.htm">Themes</a> can be contributed to define the
-   overall appearance.</li>
-<li>The <a href="ua_intro_extending_content.htm">content</a> of an existing
-   intro config can be extended.</li>
-<li>A custom <a href="ua_intro_ext_standbypart.htm">standby content part</a>,
-   such as a Cheat Sheet, can be contributed to provide content for the standby
-   area of the Intro part.</li>
-<li>Custom <a href="ua_intro_ext_custom_url.htm">IntroURL actions</a> can be
-   defined.</li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
deleted file mode 100644
index 1979f46..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_extending_content.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Extending the content of an intro config</title>
-</head>
-<body>
-
-<h2>Extending the content of an intro config</h2>
-
-<p>
-Plug-ins can contribute intro content to a page defined elsewhere.  However, the defining page must define an
-<b>anchor</b> attribute that acts as a location placeholder for new content.  The SDK overview page defines
-two anchors for adding JDT and PDE related elements on the overview page.
-</p>
-
-<pre>
-   &lt;group id="page-content"&gt;
-      &lt;text style-id="page-title" id="page-title"&gt;OVERVIEW&lt;/text&gt;
-      &lt;text style-id="page-description" id="page-description"&gt;Eclipse is a kind of universal tool platform - an open extensible IDE for anything and nothing in particular. It provides a feature-rich development environment that allows the developer to efficiently create tools that integrate seamlessly into the Eclipse Platform.&lt;/text&gt;
-      &lt;group id="overview-links"&gt;
-         &lt;link label="Workbench basics" url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.platform.doc.user/concepts/concepts-2.htm" id="basics"&gt;
-            &lt;text&gt;Learn about basic Eclipse workbench concepts&lt;/text&gt;
-         &lt;/link&gt;
-         &lt;link label="Team support" url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.platform.doc.user/concepts/concepts-26.htm" id="team"&gt;
-            &lt;text&gt;Find out how to collaborate with other developers&lt;/text&gt;
-         &lt;/link&gt;
-         <b>&lt;anchor id="jdtAnchor"/&gt;
-         &lt;anchor id="pdeAnchor"/&gt;</b>
-      &lt;/group&gt;
-   &lt;/group&gt;
-</pre>
-
-<p>
-These anchors can be referenced by plug-ins that add content to the page.  Content is added using the
-<b><a href="../reference/extension-points/org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></b>
-extension.  In addition to extending page content, this extension point also allows one to contribute standby content
-parts and custom actions.
-</p>
-
-<p>
-To extend an existing intro config, you can use the <b>configExtension</b> element.  In this element,
-you specify the <b>configId</b> of the intro config being extended and the <b>content</b> file that describes the new
-content.
-</p>
-
-<pre>
-   &lt;extension
-         point="org.eclipse.ui.intro.configExtension"&gt;
-      &lt;configExtension
-            configId="org.eclipse.platform.introConfig"
-            content="$nl$/overviewExtensionContent.xml"/&gt;  
-            ...
-   &lt;/extension&gt;
-</pre>
-
-<p>
-The format of the content file is similar to that of the intro config content, except that it must
-contain an <b>extensionContent</b> element that defines the path to the anchor where the extension content
-should be inserted.
-</p>
-
-<pre>
-   &lt;introContent&gt;
-      &lt;extensionContent
-            alt-style="css/swt.properties"
-            style="css/overview.css"
-            <b>path="overview/page-content/overview-links/jdtAnchor"</b>&gt;
-         &lt;link label="Java development" url="http://org.eclipse.ui.intro/showHelpTopic?id=/org.eclipse.jdt.doc.user/gettingStarted/qs-BasicTutorial.htm" id="java"&gt;
-            &lt;text&gt;Get familiar with developing Java programs using Eclipse&lt;/text&gt;
-         &lt;/link&gt;
-      &lt;/extensionContent&gt;
-   &lt;/introContent&gt;
-</pre>
-After contributing custom content to an intro's predefined anchor points, a given product can bind itself to that
-intro using the <b><a href="../reference/extension-points/org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></b>
-discussed above.  When the product is run, the intro that was extended will be shown with the additional
-content.  This allows the product to have its own branding and other product-specific information, while reusing
-a closely related product's intro along with key content of its own.
-<p>A given intro could also selectively include pieces of a related product's intro.  In this case, the product could define its
-own intro and intro config, and then reference important elements defined in another intro's config
-using an <b>include</b> in the content file.  This mechanism is valuable in situations where related products
-are built on top of one another and it is necessary to introduce users to key concepts in the higher level
-products.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
deleted file mode 100644
index 93902f4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_hello_world.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Contributing a HelloWorld intro Part</title>
-</head>
-<body>
-
-<h2>Contributing a HelloWorld intro Part</h2>
-
-<p>
- We will now contribute a very basic intro part just to illustrate the steps needed to contribute a part implementation to the Workbench and get it to show up as the welcome page. To do this:</p>
-<ol>
-  <li>use the <em>org.eclipse.ui.intro </em> extension point to register an intro part implementation and bind this intro part to your product.</li>
-  <li>implement the <em>org.eclipse.ui.intro.IIntroPart </em> interface and use this class as the class attribute in the above extension point contribution.</li>
-  <li>run your Eclipse based product with the correct product id. </li>
-</ol>
-<p> Here is the <em>org.eclipse.ui.intro </em>extension point registration needed: </p>
-
-<pre>
-   &lt;extension point="org.eclipse.ui.intro"&gt; 
-      &lt;intro
-            class="org.eclipse.ui.intro.HelloWorldIntroPart"
-            id="org.eclipse.ui.intro.examples.basic001_introId"
-            icon="some_icon.jpg"/&gt;
-      &lt;introProductBinding
-            introId="org.eclipse.ui.intro.HelloWorld_introId"
-            productId="org.eclipse.ui.intro.HelloWorld_product"&gt;
-      &lt;/introProductBinding&gt;
-   &lt;/extension&gt; 
-</pre>
-
-<p>An <em>intro </em> part is registered with the workbench. The class that implements this intro part is <em>org.eclipse.ui.intro..HelloWorldIntroPart </em>. An icon is also registered with the intro part and it will appear at the top right corner of the intro part window. An <em>introProductBinding </em> contribution tells the workbench that the intro part we just created is bound to our product with the id <em>org.eclipse.ui.intro.HelloWorld_product</em>. On startup, the workbench looks for the first intro bound to the current product, and instantiates the class registered with this intro contribution.</p>
-<p>The second step is to implement the <em>org.eclipse.ui.intro.IIntroPart </em> interface. The following is sample code that simply creates a label and centers it in the parent composite. This code can be used to actually create the IntroPart:</p> 
-
-<pre>
-   public void createPartControl(Composite container) {
-        Composite outerContainer = new Composite(container, SWT.NONE);
-        GridLayout gridLayout = new GridLayout();
-        outerContainer.setLayout(gridLayout);
-        outerContainer.setBackground(outerContainer.getDisplay().getSystemColor(
-             SWT.COLOR_TITLE_BACKGROUND_GRADIENT));
-        label = new Label(outerContainer, SWT.CENTER);
-        label.setText("WELCOME TO ECLIPSE");
-        GridData gd = new GridData(GridData.GRAB_HORIZONTAL | GridData.GRAB_VERTICAL);
-        gd.horizontalAlignment = GridData.CENTER;
-        gd.verticalAlignment = GridData.CENTER;
-        label.setLayoutData(gd);
-        label.setBackground(outerContainer.getDisplay().getSystemColor(
-             SWT.COLOR_TITLE_BACKGROUND_GRADIENT));
-   }
-</pre>
-
-<p> The third and last step is to make sure you run the correct product. For example, if you are self hosting, create a new runtime-workbench launch configuration, choose the "Run a product" option, and select <em>org.eclipse.ui.intro.HelloWorld_product </em>from the dropdown. <br>
-This is what you will see if you run the above HelloWorld sample:</p>
-<p align="center">	 <img src="images/basicIntro.png" border="0" alt="Image of a basic intro part"></p>
-<p>Note that the intro part is in control of the full real-estate of the window. A more elaborate intro part can be created that interacts with the workbench and progressively reveals the functionality of the product. <br>
-  <br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm
deleted file mode 100644
index 0314070..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_minimal.htm
+++ /dev/null

@@ -1,114 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining intro content</title>
-</head>
-<body>
-
-<h2>Defining a minimal intro configuration</h2>
-
-<p>
-The first stage in creating a new intro configuration is to add the necessary 
-extension points and create a minimal amount of content. This stage is often the 
-hardest. Below are the steps required to create a minimal intro configuration 
-and have it show up in a product.</p>
-
-<h3>
-Create a plugin project and add extension points</h3>
-
-<p>
-Create an new plugin project &quot;org.eclipse.intro.minimal&quot; which has a dependency 
-on org.eclipse.ui.intro. In the plugin manifest editor add the extension 
-org.eclipse.ui.intro. Edit plugin.xml until it looks like this:</p>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;?eclipse version=&quot;3.2&quot;?&gt;
-&lt;plugin&gt;
-    &lt;extension
-         point=&quot;org.eclipse.ui.intro&quot;&gt;
-      &lt;intro
-            class=&quot;org.eclipse.ui.intro.config.CustomizableIntroPart&quot;
-            icon=&quot;$nl$/icons/image_obj.gif&quot;
-            id=&quot;org.eclipse.intro.minimal&quot;
-            label=&quot;Minimal Intro&quot;/&gt;
-   &lt;/extension&gt;
-   &lt;extension
-         point=&quot;org.eclipse.ui.intro.config&quot;&gt;
-      &lt;config
-            content=&quot;$nl$/introContent.xml&quot;
-            id=&quot;org.eclipse.intro.minimal.config&quot;
-            introId=&quot;org.eclipse.intro.minimal&quot;&gt;
-         &lt;presentation
-               home-page-id=&quot;root&quot; standby-page-id=&quot;standby&quot;&gt;
-            &lt;implementation
-                  kind=&quot;html&quot;&gt;
-            &lt;/implementation&gt;
-         &lt;/presentation&gt;
-      &lt;/config&gt;
-   &lt;/extension&gt;
-&lt;/plugin&gt;</pre>
-
-<h3>
-Create the intro config file</h3>
-
-<p>
-Create a file introcontent.xml in the plugin project org.eclipse.intro.minimal 
-with these contents.</p>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;
-&lt;introContent&gt;
-    &lt;!-- Root page --&gt;
-    &lt;page id=&quot;root&quot; style=&quot;html/style.css&quot;  style-id=&quot;page&quot;&gt;	    
-        &lt;title style-id=&quot;intro-header&quot;&gt;Minimal Intro&lt;/title&gt;
-        &lt;link url=&quot;http://org.eclipse.ui.intro/switchToLaunchBar&quot; label=&quot;Go to theWorkbench&quot; id=&quot;workbench&quot; /&gt;
-        &lt;link label=&quot;Link to tutorials&quot; url=&quot;http://org.eclipse.ui.intro/showPage?id=tutorials&quot; id=&quot;tutorials&quot; /&gt;
-    &lt;/page&gt;
-	
-    &lt;!-- Standby page --&gt;
-    &lt;page id=&quot;standby&quot; style=&quot;html/style.css&quot; style-id=&quot;page&quot;&gt;
-   		 &lt;title style-id=&quot;intro-header&quot;&gt;Standby Page&lt;/title&gt; 
-    &lt;/page&gt;    
-    
-    &lt;!-- Tutorials page --&gt;
-	&lt;page id=&quot;tutorials&quot; style= &quot;html/style.css&quot; style-id=&quot;page&quot;&gt;
-        &lt;title style-id=&quot;intro-header&quot;&gt;Tutorials&lt;/title&gt;	
-        &lt;text&gt;This page under construction&lt;/text&gt;
-    &lt;/page&gt;   
-&lt;/introContent&gt;</pre>
-<h3>Define a product binding</h3>
-<p>In this step we need to determine the product which is being used and create 
-an intro product binding and modify its plugin.xml file. If you are using the 
-Eclipse SDK this will be in the plugin project org.eclipse.sdk&nbsp; which can 
-be found in the plugins directory of your Eclipse installation. The following 
-directions assume you are using the Eclipse SDK, with slight modifications these 
-will work equally well for an RCP or other Eclipse based product. Open 
-plugin.xml and locate the following section:</p>
-<pre>&lt;extension
-	 point=&quot;org.eclipse.ui.intro&quot;&gt;
-      &lt;introProductBinding
-            introId=&quot;org.eclipse.ui.intro.universal&quot;
-            productId=&quot;org.eclipse.sdk.ide&quot;&gt;
-      &lt;/introProductBinding&gt;
-&lt;/extension&gt;</pre>
-<p>Change the introId to &quot;org.eclipse.intro.minimal&quot; so that the extension code 
-looks like this.</p>
-<pre>&lt;extension
-		point=&quot;org.eclipse.ui.intro&quot;&gt;
-      &lt;introProductBinding
-            introId=&quot;org.eclipse.intro.minimal&quot;
-            productId=&quot;org.eclipse.sdk.ide&quot;&gt;
-      &lt;/introProductBinding&gt;
-    &lt;/extension&gt;</pre>
-<h3>Test and Customize</h3>
-<p>Launch a new Eclipse application from your workbench.&nbsp; Your intro screen 
-may already be showing (depending on the state when Eclipse last exited). If it 
-is not showing select Help/Minimal Intro from the workbench menu. By editing the 
-file html/style.css you can modify the appearance of your intro. You can now 
-extend your intro either by editing the intro.xml file or by adding config 
-extensions.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm
deleted file mode 100644
index 4edeb33..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal.htm
+++ /dev/null

@@ -1,121 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Universal intro</title>
-</head>
-<body>
-
-<h2>Universal intro</h2>
-
-<h3>What is the universal intro?</h3>
-
-<p>
-The universal intro is complete, ready out-of-the-box implementation of intro with a
-pre-defined page structure that all products can rely on (as API). It is a complete
-implementation, including presentation, but without content, and can be used by
-any product.
-</p>
-
-<h3>Motivation</h3>
-
-<p>
-Prior to 3.2, the intro framework provided for defining welcome pages with
-unique contribution points or 'anchors'. Other components could provide extensions
-that add content into these anchors. Although this mechanism worked well for closed
-solutions, it is increasingly hard to maintain for large products. Due to the
-'bottom-up' nature of contributions from clients into the welcome pages, it is hard
-to control the final result and resolve conflicting contributions.
-</p>
-
-<p>
-Take, for example, the provider of a reusable eclipse feature. He/she has
-created a useful feature consisting of a number of plug-ins. The feature can 
-take part in several products, each one having its own Welcome implementation. 
-There are several problems that the feature provider will face when creating 
-Welcome contribution:
-</p>
-
-<ul>
-  <li>
-    Since it must contribute into a number of different products, the feature 
-    must know about the page identifiers for each of the products upfront.
-  </li>
-  <li>
-    It is entirely possible that one of the products will have a Welcome 
-    implementation that is completely different from what the feature provider 
-    expects; the contribution will not show up in these products.
-  </li>
-  <li>
-    Even if the products share a common Welcome implementation, the importance 
-    of the feature (and hence its relative position on the page) is not going to 
-    be the same. The feature can be one of the most important components in the 
-    product, or may be ranked as 'See Also'. Nevertheless, the feature provider is 
-    asked to fully spell out the location on the target page in advance.
-  </li>
-</ul>
-
-<p>
-It is clear that the Welcome contribution of a reusable feature is be much easier
-to develop with the following conditions in place:
-</p>
-
-<ul>
-  <li>
-    There is a common Welcome implementation that can be counted on (as a form of API)
-  </li>
-  <li>
-    Delayed target page resolution (so that the decision of the final position 
-    of the contribution is left to the product assembler)
-  </li>
-</ul>
-
-<h3>Enter universal intro</h3>
-
-<p>
-The universal intro is based on experience with intro implementations and the
-need to have an implementation in place that contributors can count on. The
-implementation is built using the existing intro framework, and for this reason,
-all existing intro implementation will continue to work and clients will be able
-to switch to the new model according to their schedules. Of course, as long as
-they don't switch, they will not reap the benefits of the new implementation
-such as intelligent content merging, new visual solution etc.
-</p>
-
-<h3>Benefits</h3>
-
-<p>
-Some of the benefits of using the universal intro include:
-</p>
-
-<ul>
-  <li>
-    Products can simply to point to the universal intro without the need to
-    implement an intro from scratch
-  </li>
-  <li>
-    Each product should be able to configure the intro to a certain degree (title,
-    branding image, presentation theme)
-  </li>
-  <li>
-    A number of root pages that cover most of the products' needs are be provided.
-    The list of pages to show is also configurable
-  </li>
-  <li>
-    The presentation is sufficiently product-agnostic to better suit the
-    increasingly componentized world. It works well with both monolithic products
-    and 'best of breed' eclipse products assembled with components created by
-    different companies
-  </li>
-  <li>
-    End-users can configure the universal intro in a user-friendly way, via the
-    preference page
-  </li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm
deleted file mode 100644
index a743edd..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_contributing.htm
+++ /dev/null

@@ -1,162 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Contributing to universal intro</title>
-</head>
-<body>
-
-<h2>Contributing to universal intro</h2>
-
-<p>
-In order to hook into to the universal intro, developers should have a 
-product-based eclipse application. This requires the use of the
-<code><b>org.eclipse.runtime.products</b></code> extension point (the assumption is
-that the product has already been defined):
-</p>
-
-<pre>   &lt;extension
-         id="foo"
-         point="org.eclipse.core.runtime.products"&gt;
-      &lt;product
-            application="org.eclipse.ui.ide.workbench"
-            description="Product Foo to use for testing the universal intro"
-            name="Product Foo"&gt;
-      &lt;/product&gt;
-   &lt;/extension&gt;
-</pre>
-
-<p>
-For this example, assume that the extension is defined in the <code>plugin.xml
-</code> file in the <code><b>com.example.intro</b></code> plug-in. A
-long-standing feature of the eclipse intro support is the ability to hook
-products and intros using the product-intro binding:
-</p>
-
-<pre>   &lt;extension
-         point="org.eclipse.ui.intro"&gt;
-      &lt;introProductBinding
-            introId="org.eclipse.ui.intro.universal"
-            productId="com.example.intro.foo"/&gt;
-   &lt;/extension&gt;
-</pre>
-
-<p>
-The extension above binds the universal intro implementation
-(<b>org.eclipse.ui.intro.universal</b>) and our product id.
-</p>
-
-<p>
-Universal intro customization is split between product branding properties and 
-preferences. Product branding properties are set by the product and cannot be 
-modified. They include product title, branding image and branding image text:
-</p>
-
-<pre>   &lt;product
-         application="org.eclipse.ui.ide.workbench"
-         description="Product Foo to use for testing the universal intro"
-         name="Product Foo"&gt;
-      &lt;property
-            name="introTitle"
-            value="Welcome to Product Bar"/&gt;
-      &lt;property
-            name="introBrandingImage"
-            value="product:eclipse.png"/&gt;
-      &lt;property
-            name="introBrandingImageText"
-            value="XYZ Company"/&gt;
-   &lt;/product&gt;
-</pre>
-
-<p>
-Product properties whose values represent a file name relative to the product 
-bundle must be qualified with the 'product:' prefix. The following properties are 
-supported:
-</p>
-
-<ul>
-  <li>
-    <b>introTitle</b> - the value of the property will be used at the top of 
-    the root page (assuming that the current presentation theme elected to show 
-    the root page title)
-  </li>
-  <li>
-    <b>introBrandingImage</b> - the value of the property represents the 
-    file name of the image to be used as the root page brand mark. The image 
-    should ideally be PNG with alpha blending but other formats are also valid. 
-    Image file names relative to the product bundle must have a 'product:' 
-    prefix.
-  </li>
-  <li>
-    <b>introBrandingImageText</b> - an alternative text to be used for the 
-    branding image.
-  </li>
-  <li>
-    <b>introDescription-&lt;pageId&gt;</b> - an option description text that 
-    appears below the title on each of the sections, where pageId is one of the 
-    values listed further below (e.g. introDescription-overview, 
-    introDescription-samples etc.). This value should be translated in 
-    plugin.properties file.
-  </li>
-</ul>
-
-<p>
-Second half of universal intro variables are accessible as preferences. The 
-split is due to the fact that these variables can be configured by users and are 
-exposed in the new Welcome preference page. The initial values for these preferences 
-should be placed in the 'plugin_customization.ini' file that is referenced from 
-the product extension. These preferences are:
-</p>
-
-<ul>
-  <li>
-    <b>org.eclipse.ui.intro.universal/INTRO_ROOT_PAGES</b> - a comma-separated list of 
-    root page identifiers that should be visible in the home page. Valid values 
-    are:
-    <ul>
-      <li><b>overview</b></li>
-      <li><b>firststeps</b></li>
-      <li><b>tutorials</b></li>
-      <li><b>samples</b></li>
-      <li><b>whatsnew</b></li>
-      <li><b>migrate</b></li>
-      <li><b>webresources</b></li>
-    </ul>
-  </li>
-  <li>
-    <b>org.eclipse.ui.intro.universal/INTRO_DATA</b> - a file name pointing at 
-    the XML file with the page layout settings (see more about this below). The 
-    file name relative to the product bundle must have 'product:' prefix.
-  </li>
-  <li>
-    <b>org.eclipse.ui.intro/INTRO_THEME</b> - a unique identifier of the 
-    <a href="ua_intro_ext_theme.htm">presentation theme</a> to be used for this
-    product. <b>Note that this preference comes from 'org.eclipse.ui.intro
-    plug-in'</b> because active theme selection is performed at the framework
-    level.
-  </li>
-  <li>
-    <b>org.eclipse.ui.intro/INTRO_START_PAGE</b> - the id of the page which will 
-    be shown when Eclipse starts the first time.
-  </li>
-  <li>
-    <b>org.eclipse.ui.intro/INTRO_HOME_PAGE</b> - the id of the page which will 
-    be shown when the home button is pressed.
-  </li>
-  <li>
-    <b>org.eclipse.ui.intro/INTRO_STANDBY_PAGE</b> - the id of the page which will 
-    be shown when welcome is displayed in a non-maximized form.</li>
-  <li>
-    When using universal intro valid values for the three page related 
-    properties are are <b>root, overview,&nbsp; firststeps, tutorials, samples, whatsnew, migrate  </b>or&nbsp;<b> webresources</b> 
-    or the name of a page contributed using a config extension.</li>
-</ul>
-
-<p>&nbsp;</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm
deleted file mode 100644
index fb18645..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_defaults.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Configuring product defaults</title>
-</head>
-<body>
-
-<h2>Configuring product defaults</h2>
-
-<p>
-In addition to providing intro customization to the end users for the first 
-time, Welcome preference page will allow product authors to create the 
-introData.xml file to be used for the first startup. The procedure is simple:
-</p>
-
-<ol>
-	<li>Launch the product for the first time</li>
-	<li>Open the Welcome preference page (a quick way to do this is from the 
-	local tool bar of the Welcome view where a new tool bar button opens the 
-	Preferences into the right page)</li>
-	<li>For each page, manipulate the available extensions by moving them 
-	between the four page quadrants (upper-left, upper-right, lower-left, 
-	lower-right) and the Available list, or moving extensions up or down within 
-	the same list (relative order). Use drag and drop to get the desired 
-	results.</li>
-	<li>If needed, add the separator between the extension within the quadrant.</li>
-	<li>All extensions have the default importance setting of 'Low'. To change 
-	it, click on the extension image to get the drop-down list to open and pick 
-	a different setting from the list (e.g. High, Medium or Callout).</li>
-	<li>Press OK to see the preferences applied to Welcome.</li>
-	<li>If satisfied, open the preference page again and press 'Save As...' 
-	button.</li>
-	<li>Store the file as 'introData.xml' in the product plug-in.</li>
-	<li>Set <b>org.eclipse.ui.intro.universal/INTRO_DATA</b> preference to the
-	value 'product:introData.xml'.</li>
-	<li>Start the product on a fresh workspace to test if the data from the file 
-	has been picked up.</li>
-</ol>
-
-<p>
-List 'Available Extensions' holds all the extensions that are currently 
-hidden. They can be moved to one of the four quadrants of each page.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm
deleted file mode 100644
index 140065c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_extending.htm
+++ /dev/null

@@ -1,162 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Extending the universal intro</title>
-</head>
-<body>
-
-<h2>Extending the universal intro</h2>
-
-<p>
-When launching the universal Welcome configured as shown above, you will notice 
-that all of the second level page that branch off the root page have an empty 
-content area. This is because shared Welcome does not have content of its own. 
-These areas are populated using intro config extensions.
-</p>
-
-<p>
-The traditional way of contributing config extensions is to specify a full 
-path of the anchor element in the target page. This method is still supported 
-but it has proven to be somewhat fragile. As mentioned before, specifying an 
-exact place where the extension will end up in the target is premature for 
-extension authors. They may not know all the products in which their extension 
-will end up, and therefore don't know where they should appear according to each 
-product's focus. In the universal Welcome, this decision is left to product 
-authors. Extension authors now have the option of specifying an incomplete 
-target path, allowing the product author to fill in the blanks.
-</p>
-
-<p>
-Config extensions that want to use late target path resolution need to 
-fulfill three conditions:
-</p>
-
-<ol>
-	<li>Config extension needs to specify a unique identifier using the 'id' 
-	attribute. Extensions without the id will be ignored. This is important 
-	because id will be used to refer to the extension by the product author.</li>
-	<li>Config extension needs to specify a user-friendly name using the 'name' 
-	attribute. This is important if the customization preference page will be 
-	used because extensions will show up in the UI.</li>
-	<li>The target path should have the following form: "page_id/@" where 'page_id' 
-	is the identifier of the target page. When '/@' is detected in the target 
-	path, an attempt will be made to dynamically resolve the path into the 
-	expected full form.</li>
-</ol>
-
-<p>
-The ability to resolve extension target paths is a new intro support
-feature in Eclipse 3.2 added to make universal Welcome more powerful.
-The feature itself is generic in that it can be used in other Welcome
-implementations, not just the universal one. In Eclipse 3.2,
-CustomizableIntroPart can accept an optional intro customizer class
-that can affect its behavior in several ways. One of the roles of the
-customizer is to perform late target path resolution. Of course, as far
-as product authors are concerned, this is all just implementation
-detail because in universal Welcome implementation, late target path
-resolution is performed using the data file mentioned earlier. This
-file is stored using the org.eclipse.ui.intro/INTRO_DATA preference.
-</p>
-
-<p>
-The 'INTRO_DATA' file uses XML format and allows product authors to control 
-the content of the main Welcome pages. Welcome contribution authors are required 
-to specify only the page Id in their target paths. The rest is defined in this 
-file. The file contains a sequence of 'page' elements, each containing a number 
-of 'group' elements. Group elements specify page-relative path and have 
-contributions for children. Contribution elements are used to specify two 
-aspects:
-</p>
-
-<pre>
-   &lt;extensions&gt;
-      &lt;page id="overview"&gt;
-         &lt;group path="page-content/top-left"&gt;
-            &lt;extension id="foo1" importance="high"/&gt;
-            &lt;extension id="bar"  importance="high"/&gt;
-            &lt;extension id="foo2" importance="medium"/&gt;
-         &lt;/group&gt;
-         &lt;group path="page-content/top-right"&gt;
-            &lt;extension id="foo3" importance="low"/&gt;
-            &lt;extension id="foo4" importance="low"/&gt;
-            &lt;extension id="foo5" importance="callout"/&gt;
-         &lt;/group&gt;
-         &lt;hidden&gt;
-            &lt;extension id="foo6"/&gt;
-            &lt;extension id="foo7"/&gt;
-         &lt;/hidden&gt;
-      &lt;/page&gt;
-      &lt;page id="whatsnew"&gt;
-      ...
-      &lt;/page&gt;
-   &lt;/extensions&gt;
-</pre>
-
-<p>
-In the example above, contributions 'foo1', 'bar' and foo2' will be in the 
-left, and 'foo3', 'foo4' and 'foo5' in the right column on the page. The 
-relative order of contributions is also extracted from this file. In addition, 
-contributions are classified based on the <code>importance</code> attribute that 
-can have four valid values: <b>high</b>, <b>medium</b>, <b>low</b> and <b>
-callout</b>, with <b>low</b> as the default. Each value has matching 
-presentation that makes it stand out on the page. First three are simply 
-different levels of importance according to the product author (note that the 
-same contribution may receive a different importance classification in two 
-separate products). The last one (<b>callout</b>) is used to single out 
-contributions that are of a completely different nature (for example, a 
-contribution that offers links to videos or animation).
-</p>
-
-<p>
-Contributions that are not listed are appended after the listed contributions 
-and assigned a low importance value. This is important for contributions added 
-after the product has shipped - they still need to show up.
-</p>
-
-<p>
-Contributions not relevant to the project can be hidden by explicitly listing 
-them as children of the 'hidden' element.
-</p>
-
-<h3>Contributing into extensions</h3>
-
-<p>
-An extension contributed into one of the root pages can itself contain 
-anchors, providing for others to add content. This causes a problem because the 
-final resolved path of the content in the extension is not known in advance. For 
-this reason, target paths for content in extensions that use late path 
-resolution must itself be resolved:
-</p>
-
-<blockquote>
-	<pre>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
-&lt;introContent&gt;
-   &lt;extensionContent id="extra" name="Extra" alt-style="css/swt.properties" style="css/overview.css" path="overview/@"&gt;
-      &lt;group id="extra-group" style-id="content-group"&gt;
-         &lt;link label="Extra Overview link" url="http://org.eclipse.ui.intro/showPage?id=extraOverview" 
-					  id="extra-overview"&gt;
-      	    &lt;text&gt;Showing the third-level extra page for overview&lt;/text&gt;
-
-         &lt;/link&gt;
-         &lt;anchor id="additions"/&gt;
-      &lt;/group&gt;
-   &lt;/extensionContent&gt;
-&lt;/introContent&gt;</pre>
-</blockquote>
-
-<p>
-In order to contribute into the anchor 'additions' in the extension above, we 
-should use the following path: "overview/@extra/extra-group/additions". The 
-segment '@extra' will be replaced with the resolved path of the extension with 
-the id 'extra' in the 'overview' page. For example, if the extension is placed 
-in the upper left segment of the page, the resolved path will be: 
-"overview/page-content/upper-left/extra-group/additions".
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm
deleted file mode 100644
index be8fc95..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_links.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Managing links</title>
-</head>
-<body>
-
-<h2>Managing links</h2>
-
-<p>
-Most of the extensions coming into the main Welcome pages offer links to open 
-further pages contributed by the extensions themselves. It is recommended to 
-create these pages in such a way as to continue with the shared Welcome visual 
-design. The main requirement is to show the appropriate navigator at the top of 
-the page.
-</p>
-
-<p>
-It is fairly easy to do that using the 'include' element. The idea is to 
-include the navigation content at the beginning of contributed page. Unlike the 
-current Welcome implementation, shared Welcome main pages have navigation 
-section that is different for each page. For this reason, pages that branch off 
-these pages should include the navigation from the parent page. For example:
-</p>
-
-<pre>
-   &lt;introContent&gt;
-      &lt;extensionContent id="extra" name="Extra" alt-style="css/swt.properties" style="css/overview.css" path="overview/@"&gt;
-         &lt;link
-               label="Extra Overview link"
-               url="http://org.eclipse.ui.intro/showPage?id=extraOverview" 
-               id="extra-overview"&gt;
-            &lt;text&gt;Showing the third-level extra page for overview&lt;/text&gt;
-         &lt;/link&gt;
-      &lt;/extensionContent&gt;
-      &lt;page id="extraOverview" <b>style="$theme$/html/overview.css"</b> style-id="page"&gt;
-         <b>&lt;title style-id="intro-header"&gt;$introTitle$&lt;/title&gt;</b>
-         <b>&lt;group id="extra-group1" filteredFrom="swt"/&gt;</b>
-         <b>&lt;include path="overview/navigation-links"/&gt;</b>
-         &lt;group id="page-content"&gt;
-            &lt;group id="content-header" label="EXTRA OVERVIEW" filteredFrom="swt"&gt;
-            &lt;/group&gt;
-            &lt;text style-id="page-title" id="page-title" filteredFrom="html"&gt;EXTRA OVERVIEW&lt;/text&gt;
-            &lt;text style-id="page-description" id="page-description"&gt;Extra overview page description.&lt;/text&gt;
-            &lt;!-- Add content here --&gt;
-         &lt;/group&gt;
-      &lt;/page&gt;
-   &lt;/introContent&gt;
-</pre>
-
-<p>
-The extension above contributed into the overview page contributes a
-link that shows another page whose definition is part of the extension.
-Note how we define the title element using substitution variable (the
-variable will be resolved based on the product property). We also
-include the group 'navigation-links' that belongs to the 'overview'
-page at the beginning of the page content definition. We also add the
-'extra-group1' div because it is can be used by some themes for adding
-additional page decoration (indeed, it is used in 'Purple Mesh' theme
-for that exact purpose).
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm
deleted file mode 100644
index adc0a23..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_universal_preference.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Adding the preference page</title>
-</head>
-<body>
-
-<h2>Adding the preference page</h2>
-
-<p>
-The combination of product properties and default preference values can fully 
-configure the Universal Welcome if no further customization is desired. For 
-products that want to allow users to customize Welcome, a preference page is 
-available. The following code should be added to the product's plugin.xml:
-</p>
-
-<pre>
-   &lt;extension
-         point="org.eclipse.ui.preferencePages"&gt;
-      &lt;page
-            category="org.eclipse.ui.preferencePages.Workbench"
-            class="org.eclipse.ui.intro.universal.ExtensionFactory:welcomeCustomization"
-            id="com.example.intro.introCustomization"
-            name="%introCustomizationPreference.name"&gt;
-         &lt;keywordReference id="org.eclipse.ui.ide.appearance"/&gt;
-      &lt;/page&gt;
-   &lt;/extension&gt;
-</pre>
-   
-<p>
-This code will add the Welcome customization preference page. The page allows users
-to select the presentation theme. The original choice is provided by the theme
-preference in the plugin_customization.ini file. In addition, users can choose from
-the list of available root pages. Checking the root page causes the related tab to
-appear at the top of the dialog.
-</p>
-
-<p>
-When saved, this preference page will prefix the variables with 
-the product id so that it does not interfere with the settings made for other 
-products in the same workbench. Alternatively, selecting the checkbox above will 
-not prefix the variables, making the stored settings visible to all the 
-products.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
deleted file mode 100644
index 42cf4e8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_intro_xhtml.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Using XHTML as intro content</title>
-</head>
-<body>
-
-<h2>Using XHTML as intro content</h2>
-
-<p>Depending on the usage scenario of the intro framework,  XHTML files can be contributed as intro content. <span id="tooltip1" style="position: relative; display:none;" onclick="FP_changeProp(/*id*/'tooltip1',0,'style.display','none')"> <font color="#0000FF" style="cursor: hand;">(A reformulation of the three HTML 4 document types as applications of XML 1.0. For M5, only XHTML 1.0 is supported. XHTML 1.1 (module-based XHTML) can be supported, based on fee</font></span>The idea is to use the fact that XHTML is well formed XML and parse each document, manipulating the DOM to allow for contributions and extensions to be merged. Three xml elements from the 3.0 intro markup where used to extend the XHTML 1.0 element list. These where <code>include</code>, <code>anchor</code>, and <code> contentProvider</code>. </p>
-<ul>
-  <li>&nbsp;<code><b>include</b>: </code>this element can be added to a valid XHTML document to include content from another XHTML document. The content to be included must be a valid XHTML snippet.</li>
-</ul>
-<blockquote>
-  <dl>
-    <dd>e.g.: <code>&lt;include path=&quot;root/foo&quot; /&gt;</code> will include an element with id <code>foo</code> from a welcome page with id <code>root</code>. </dd>
-  </dl>
-</blockquote>
-<ul>
-  <li>&nbsp;<code><b>anchor</b>: </code>this element can be added to a valid XHTML document to declare that content can be contributed to this page by other welcome contributions. A page declares locations that are suitable to be extended by defining these anchor points.</li>
-</ul>
-<blockquote>
-  <dl>
-    <dd>e.g.: <code>&lt;anchor id=&quot;anchor1&quot; /&gt;</code> will allow for contribution into this page from other plugins. </dd>
-  </dl>
-</blockquote>
-<ul>
-  <li><code><b>contentProvider</b>: </code>this element can be added to a valid XHTML document to establish a hook into the workbench. When the intro framework encounters this element, an interface is called allowing for the manipulation of the DOM of the XHTML page. &nbsp;&nbsp; </li>
-</ul>
-<dl>
-  <dd>
-    <dl>
-      <dd>e.g.: <code>&lt;contentProvider id=&quot;contentProviderId&quot; class=&quot;org.eclipse.ui.intro.template2.IntroXHTMLContentProvider&quot; pluginId=&quot;org.eclipse.ui.intro.template2&quot;&gt; &lt;/contentProvider&gt; <br>
-      </code>&nbsp;will allow for dynamic content to be generated from the <code> org.eclipse.ui.intro.template2.IntroXHTMLContentProvider</code> class.</dd>
-    </dl>
-  </dd>
-</dl>
-<p>With these three elements, XHTML pages can be used to assemble a pluggable and dynamic welcome pages, just like what used to happen with the custom intro xml markup. PDE has a new template that allow for the creation of a sample RCP application with an Intro. That template is a good sample project for using Intro. </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm
deleted file mode 100644
index a2a0e22..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Status handling</title>
-</head>
-<body>
-
-<h2>Status handling</h2>
-
-<p>
-Status handling is a facility that 
-allow to introduce a custom way of showing problems in the product to users. 
-A part of the facility is an extension point which allows to plug new status handler
-specific for the product. This handler associated to the product is intended
-to present the problem in the useful for users way.
-</p>
-
-<p>
-The status handling is contributed using <em>org.eclipse.ui.statusHandlers</em> extension point.
-This contribution can be part of product plug-ins or can be provided separately in its own status handling plug-in.
-Separating the product handler into a separate plug-in is beneficial in those situations 
-where the product and status handling are provided by different groups, e.g. CompanyA provides the ProductA
-and other companies provide status handlers showing problems in ProductA differently. 
-</p>
-
-<p>
-If there is no handler defined for the product, the facility will use a handler defined for application
-in the workbench advisor. When the advisor shipped with Eclipse is used the
-<em>WorkbenchErrorHandler</em> will be used for handling of the product problems.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm
deleted file mode 100644
index ceb7b21..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_defining.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining a product status handler</title>
-</head>
-<body>
-
-<h2>Defining a product status handler</h2>
-
-<p> 
-The <a href="../reference/api/org/eclipse/ui/statushandlers/AbstractStatusHandler.html"><b>AbstractStatusHandler</b></a> 
-class and the <b><a href="../reference/extension-points/org_eclipse_ui_statusHandlers.html">org.eclipse.ui.statusHandlers</a></b> 
-extension point make up the generic mechanism that can be used to customize 
-problem handling for the given product. The main purpose of this extension is 
-to define status handlers (which extends <a href="../reference/api/org/eclipse/ui/statushandlers/AbstractStatusHandler.html"><b>AbstractStatusHandler</b></a>) 
-and to specify the binding between a product and a status handler. For example, 
-the following contribution defines a hypothetical status handler to be used 
-by the workbench:</p> 
-
-<pre>
-   &lt;extension point="org.eclipse.ui.statusHandlers"&gt; 
-      &lt;statusHandler
-            class="org.eclipse.ui.statushandlers.SampleStatusHandler"
-            id="sampleStatusHandler"/&gt;
-      &lt;statusHandlerProductBinding
-            handlerId="sampleStatusHandler"
-            productId="productId"&gt;
-      &lt;/introProductBinding&gt;
-   &lt;/extension&gt; 
-</pre>
-<p>
-This contribution first defines the status handler and assigns it the id "sampleStatusHandler".  It then binds this
-handler to a product whose id is "productId". When the status handling facility is accessed first time, 
-the class specified in the <b>class</b> attribute will be instantiated by the workbench and used for handling of
-status or error occurred in the product.
-</p>
-
-<p>
-The platform supplies its own <a href="../reference/api/org/eclipse/ui/statushandlers/AbstractStatusHandler.html"><b>AbstractStatusHandler</b></a>
-implementation called <a href="../reference/api/org/eclipse/ui/statushandlers/WorkbenchErrorHandler.html"><b>WorkbenchErrorHandler</b></a>.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm b/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm
deleted file mode 100644
index a847629..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/ua_statushandling_sample.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Contributing a sample handler</title>
-</head>
-<body>
-
-<h2>Contributing a sample handler</h2>
-
-<p>
-We will now contribute a very basic status handler just to illustrate the steps 
-needed to contribute a status handler implementation to the Workbench. To do this:</p>
-
-<ol>
-  <li>use the <em>org.eclipse.ui.statusHandlers</em> extension point to register 
-    a status handler implementation and bind it to your product</li>
-  <li>extend the <em>org.eclipse.ui.statushandlers.AbstractStatusHandler</em> 
-    class and use as the <b>class</b> attribute in the above extension point contribution</li>
-  <li>run your Eclipse based product with the correct product id</li>
-</ol>
-
-
-<p> 
-Here is the <em>org.eclipse.ui.statusHandlers</em> extension point markup:</p>
-
-<pre>
-   &lt;extension point="org.eclipse.ui.statusHandlers"&gt; 
-      &lt;statusHandler
-            class="org.eclipse.ui.statushandlers.SampleStatusHandler"
-            id="sampleStatusHandler"/&gt;
-      &lt;statusHandlerProductBinding
-            handlerId="sampleStatusHandler"
-            productId="productId"&gt;
-      &lt;/introProductBinding&gt;
-   &lt;/extension&gt; 
-</pre>
-
-
-<p> 
-A <em>statusHandler</em> is registered with the Workbench. The <em>statusHandlerProductBinding</em> 
-contribution tells the Workbench that the status handler we just defined is 
-bound to our product with the id "productId". The status handling facility 
-uses lazy initialization, so the handler will be instantiated during first access 
-to the facility in the product. 
-</p>
-
-<p> 
-The class defined by the class attribute extends <code>org.eclipse.ui.statushandlers.AbstractStatusHandler</code>. 
-The following is sample code that simply writes to the console the message set in the status adapter. 
-</p>
-<pre>
-   public void handle(final StatusAdapter statusAdapter, int style) {
-        System.out.println(statusAdapter.getStatus().getMessage());
-   }
-</pre>
-
-
-<p> 
-When you run the product with the id defined in the statusHandlerProductBinding 
-you will start to use your product handler. For example, if you are self hosting, 
-create a new runtime-workbench launch configuration, choose the "Run a product" 
-option, and select <em>productId</em> from the dropdown.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
deleted file mode 100644
index 6a2998e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Plugging into the workbench
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Plugging into the workbench</H1>
-<P >
-By now, you should be quite familiar with the operation of the workbench and how it uses views and editors to display information.
-If not, read the quick tour of the workbench below.</P>
-<P >
-The sections following the quick tour will look at the workbench user interface from an API
-perspective.&nbsp; We will show how a plug-in can contribute to the workbench
-UI.</P>
-<h2>
-Quick tour of the workbench</h2>
-<P >
-The workbench is the cockpit for navigating all of the function provided by plug-ins.
-By using the workbench, we can navigate resources and we can view and edit
-the content and properties of these resources. </P>
-<P >
-When you open your workbench on a set of projects, it looks something like this.</P>
-
-<p align="left"><img src="images/workbench.png" alt="Workbench with navigator view, editor, outliner, and task list" border="0" ></p>
-<P >
-The workbench is just a frame that can present various visual parts. These parts fall into two major categories:
-<b> views</b> and <b>editors</b>.</P>
-<ul>
-  <li>
-<b>
-Editors</b> allow the user to edit something in the workbench. Editors are &quot;document-centric,&quot; much like a file system editor.
-Like file system editors, they follow an open-save-close lifecycle.&nbsp; Unlike
-file system editors, they are tightly integrated into the workbench.</li>
-  <li>
-<b>
-Views</b> provide information about some object that the user is working with in the workbench. Views often change their content as the user selects different objects in the workbench.&nbsp;
-Views often support editors by providing information about the content in the
-active editor.</li>
-</ul>
-
-
-<h3>
-Views</h3>
-<P > The workbench provides several standard views that allow the user to navigate 
-  or view something of interest. For example, the project explorer lets the user 
-  navigate the workspace and select resources.</P>
-
-<img src="images/navigator.png" alt="" border="0">
-
-
-
-<h3>
-Editors</h3>
-<P >
-Editors allow the user to open, edit, and save objects. The workbench provides a standard editor for text resources.</P>
-
-<img src="images/texteditor.png" alt="" border="0">
-<P >
-Additional editors, such as Java code editors or HTML editors, can be supplied by
-plug-ins</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm
deleted file mode 100644
index f057b81..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_actionfilters.htm
+++ /dev/null

@@ -1,242 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Boolean expressions and action filters
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Boolean expressions and action filters</H2>
-<p>
-When a plug-in contributes an action to the workbench UI using one of the menu
-extension points, it can specify the conditions under which the menu item is
-visible and/or enabled in the menu. In addition to supplying simple enabling
-conditions, such as selection counts and selection classes, plug-ins can use <b>boolean
-expressions</b> for more flexibility in determining when an action should be visible or enabled.</p>
-
-
-<h3>Boolean enablement expressions</h3>
-<p>Boolean expressions can contain the boolean operators (NOT, AND, OR) combined with a predefined syntax
-for evaluating certain conditions.  Many of these conditions test a particular object.  The identity of the
-"object in focus" (the object being tested) depends upon the specific context of the enablement expression:
-</p>
-<ul>
-<li><b>instanceof</b> tests whether the type of the object in focus is a subtype of the specified type name.</li>
-<li><b>test</b> tests whether the value of a named property of the object in focus matches the specified value.</li>
-<li><b>systemTest</b> tests whether the value of a named system property matches the specified value. </li>
-<li><b>equals</b> tests whether the object in focus is equal to the specified value.</li>
-<li><b>count</b> tests the number of elements in a list.</li>
-<li><b>with</b> changes the object in focus to the object referenced by a supplied variable.</li>
-<li><b>resolve</b> changes the object in focus to the object referenced by a supplied variable, supplying additional
-arguments with the variable.</li>
-<li><b>adapt</b> adapts the object in focus to the type specified.</li>
-<li><b>iterate</b> iterates over a variable that is a collection and combines the boolean value of each value using AND or OR.</li>
-</ul>
-<p>
-When specifying a value to be tested against any of these expressions, the value is assumed to be a string except for when
-the following conversions are successful:
-</p>
-<ul>
-<li>the string "true" is converted into Boolean.TRUE</li>
-<li>the string "false" is converted into Boolean.FALSE</li>
-<li>if the string contains a dot, the interpreter tries to convert the value into a Float object</li>
-<li>if the string only consists of numbers, the interpreter converts the value into an Integer object</li>
-<li>the conversion into a Boolean, Float, or Integer can be suppressed by surrounding the string with single quotes.</li>
-</ul>
-<p>A complete definition of enablement XML syntax can be found in the extension point reference documentation for any
-extension that defines an <b>enablement</b> element, such as
-<b><a href="../reference/extension-points/org_eclipse_ui_popupMenus.html#e.enablement"> org.eclipse.ui.popupMenus</a></b>.
-</p>
-<p>Prior to R3.0, these generalized boolean expressions were not available.  The following predefined expressions were used to
-evaluate certain conditions without building a general expression.  Note that any of these expressions could now be expressed with
-the more generalized syntax.  The predefined expressions can still be used as follows:</p>
-<ul>
-  <li>
-    <p><b>objectClass</b> - true if each object in the
-    selection subclasses or implements the class.</p>
-  </li>
-  <li>
-    <p><b>objectState</b> - true if the named attribute equals the specified value.&nbsp; <b><a href="../reference/api/org/eclipse/ui/IActionFilter.html">IActionFilter</a>
-    </b>assists in evaluating the expression.&nbsp; An action filter dynamically computes the enablement
-criteria for an action based on the target selection and the value of named
-attributes.</p>
-  </li>
-  <li>
-    <p><b>systemProperty</b> - true if the named system
-    property equals the specified value.</p>
-  </li>
-  <li>
-    <p><b>pluginState</b> - specifies whether the specified
-    plug-in (by <b>id</b>) should be <b>installed</b> or <b>activated</b> </p>
-  </li>
-</ul>
-    <p>For example, the following snippets represent enablement
-    expressions that could be used on a hypothetical action in an action set: </p>
-    <pre>&lt;action id=&quot;org.eclipse.examples.actionEnablement.class&quot; 
-       label=&quot;Red Element&quot; 
-       menubarPath=&quot;additions&quot; 
-       class=&quot;org.eclipse.examples.actionEnablement.ObjectTestAction&quot;&gt; 
-       &lt;enablement&gt; 
-<b>	 &lt;and&gt;
-	   &lt;objectClass name=&quot;org.eclipse.examples.actionEnablement.TestElement&quot;/&gt; 
-           &lt;objectState name=&quot;name&quot; value=&quot;red&quot;/&gt; 
-	 &lt;/and&gt;
-</b>       &lt;/enablement&gt; 
-&lt;/action&gt;</pre>
-    <pre>&lt;action id=&quot;org.eclipse.examples.actionEnablement.property&quot; 
-       label=&quot;Property&quot; 
-       menubarPath=&quot;additions&quot; 
-       class=&quot;org.eclipse.examples.actionEnablement.PropertyTestAction&quot;&gt; 
-       &lt;enablement&gt; 
-<b>           &lt;systemProperty name=&quot;MyTestProperty&quot; value=&quot;puppy&quot;/&gt; 
-</b>       &lt;/enablement&gt; 
-&lt;/action&gt; </pre>
-    <pre>&lt;action id=&quot;org.eclipse.examples.actionEnablement.pluginState&quot; 
-       label=&quot;Installed&quot; 
-       menubarPath=&quot;additions&quot; 
-       class=&quot;org.eclipse.examples.actionEnablement.PluginTestAction&quot;&gt; 
-       &lt;enablement&gt; 
-           <b>&lt;pluginState id=&quot;x.y.z.anotherPlugin&quot; value=&quot;installed&quot;/&gt; </b>
-       &lt;/enablement&gt; 
-&lt;/action&gt; </pre>
-<p>See the reference documentation of the extension points
-for more elaborate samples of these expressions and a complete description of
-the XML.</p>
-
-
-<p>
-The following table lists extension points that contribute actions and
-summarizes how XML markup attributes and boolean expressions can be used to
-affect enablement.</p>
-
-
-<TABLE BORDER="1" width="671">
-<TR>
-<TH ROWSPAN="1" COLSPAN="1" width="118">
-<P CLASS="CellHeading">
-Extension point name</p>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="359">
-<P CLASS="CellHeading">
-Attributes affecting enablement</p>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="335">
-<P CLASS="CellHeading">
-Boolean expressions</p>
-</TH>
-</TR>
-<TR>
-<TD width="118">
-<p>
-<b>
-<a href="../reference/extension-points/org_eclipse_ui_viewActions.html">
-viewActions</a></b>,</p>
-<p><b><a href="../reference/extension-points/org_eclipse_ui_editorActions.html">editorActions</a></b>,</p>
-<p><b><a href="../reference/extension-points/org_eclipse_ui_actionSets.html">actionSets</a></b></p>
-</TD>
-<TD width="359">
-<p>
-<b>enablesFor</b> - specifies the selection count that must be met for the
-action to be enabled</p>
-<p>
-<b>selection</b> <b>class</b> - the class that the selected objects must
-subclass or implement in order for the action to be enabled</p>
-<p>
-<b>selection</b> <b>name</b> - a wild card filter that can be applied to the
-objects in the selection.</p>
-</TD>
-<TD width="335">
-<p>
-<b>visibility</b> - a boolean expression.&nbsp; Controls whether the menu item
-is visible in the menu.</p>
-<p>
-<b>enablement</b> - a boolean expression.&nbsp; Controls whether the menu item
-is enabled in the menu.&nbsp; The <b>enablesFor</b>  attribute and the <b>selection</b> <b>class</b>
-and <b>name</b>, and must be
-satisfied before applying the enablement expression.</p>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<p>
-<b>
-<a href="../reference/extension-points/org_eclipse_ui_popupMenus.html">
-popupMenus</a></b></p>
-</TD>
-<TD width="359">
-<p>
-(For object contributions only.)</p>
-<p>
-<b>objectClass</b> - specifies the class that objects in the selection must
-subclass or implement</p>
-<p>
-(For both object and viewer contributions)</p>
-<p>
-<b>enablesFor</b> - specifies the selection count that must be met for the
-action to be enabled</p>
-<p>
-<b>selection</b> <b>class</b> - the class that the selected objects must
-subclass or implement to enable the action</p>
-<p>
-<b>selection</b> <b>name</b> - a wild card filter that can be applied to the
-objects in the selection.</p>
-<p>
-&nbsp;</p>
-</TD>
-<TD width="335">
-<p>
-(For both object and viewer contributions)</p>
-<p>
-<b>visibility</b> - a boolean expression.&nbsp; Controls whether the menu item
-is visible in the menu.</p>
-<p><b>enablement</b> - a boolean expression.&nbsp; Controls
-whether the menu item is enabled in the menu.&nbsp;
-The <b>enablesFor</b>  attribute and the <b>selection</b> <b>class</b> and <b>name</b>, and must be
-satisfied before applying the enablement expression.</p>
-</TD>
-</TR>
-</TABLE>
-
-<h3>Using objectState with content types</h3>
-<p>The ability to define content types (see <a href="runtime_content.htm">Content types</a>) can be combined
-with boolean expressions to define very specific enablement or visibility conditions based on
-the content type of a resource.  For example, the following snippet makes a popup menu item visible only if the
-selected file's content matches the plug-in's specialized content types.
-</p>
-<pre>
-&lt;extension point="org.eclipse.ui.popupMenus"&gt;
-   &lt;objectContribution
-      id="com.example.objectContributions"
-      objectClass="org.eclipse.core.resources.IFile"
-      nameFilter="*.xml"&gt;
-         &lt;visibility&gt;
-            &lt;or&gt;
-               &lt;objectState
-                  <b>name="contentTypeId"</b>
-                  value="com.example.employeeRecordContentType"/&gt;
-               &lt;objectState
-                  <b>name="contentTypeId"</b>
-                  value="com.example.customerRecordContentType"/&gt;
-            &lt;/or&gt;
-         &lt;/visibility&gt;
-         &lt;action id="com.example.action1"
-         ...
-</pre>
-The <b>contentTypeId</b> attribute can be used in an objectState expression to check the content type of
-the selected xml file.  This allows a plug-in to apply very specific content checking before enabling or showing
-menu actions related to specific types of files.  See <a href="runtime_content.htm">Content types</a> for more detail
-about the content type extension.
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
deleted file mode 100644
index 0949141..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_activities.htm
+++ /dev/null

@@ -1,385 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page. Portions contributed by Jan-Hendrik Diederich (bug 228956).">
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript">
-</script>
-
-  <title>Activities</title>
-
-  <link rel="stylesheet" type="text/css" href="../book.css">
-</head>
-
-<body bgcolor="#ffffff">
-  <h3>Activities</h3>An <b>activity</b> is a logical grouping of function that
-  is centered around a certain kind of task. For example, developing Java
-  software is an activity commonly performed by users of the platform, and the
-  JDT defines many UI contributions (views, editors, perspectives, preferences,
-  etc.) that are only useful when performing this activity. Activities can be
-  used to implement <em>progressive disclosure</em> of UI elements; when used for
-  this purpose, they are called <em>capabilities</em> in the UI. The second use
-  for activities, added for Eclipse 3.4, is to filter available UI elements based
-  on other criteria such as the current user's access permissions as defined by
-  the application.
-  <p>
-  In the following text, we will be using the following terms to distinguish
-  between the two uses of activities:</p>
-
-  <ul>
-    <li>Activities that are used to <strong>declutter</strong> the user desktop from unnecessary UI
-    elements will be called <em><strong>conventional activities</strong></em>.</li> 
-
-    <li>Activities that filter out UI elements which are not supposed to be shown to the
-    user (e.g. based on their access rights) will be called
-    <strong><em>expression-based activities</em></strong>.</li>
-  </ul>
-
-
-  <h4>Conventional activities</h4>Conventional activities are exposed to the
-  user under the name <em>capabilities</em>, although not in a way that is
-  apparent to a new user. When an activity is enabled in the platform, the UI
-  contributions associated with that activity are shown. When a activity is
-  disabled in the platform, its UI contributions are not shown. Users
-  can enable and disable these conventional activities as needed using
-  the <A class=command-link href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.sdk.capabilities)")'  org.eclipse.ui.window.preferences(preferencePageId="org.eclipse.sdk.capabilities)&quot;)'&quot;" preferencepageid='org.eclipse.sdk.capabilities)")&amp;apos;"' org.eclipse.ui.window.preferences="" ><IMG height=32 src="PLUGINS_ROOT/org.eclipse.help/command_link.png" width=28 alt="Command link"> <b>General &gt;        
-  Capabilities</b></a> preference page.
-  <p>Certain user
-  operations serve as <b>trigger points</b> for enabling an activity. For
-  example, creating a new Java project could trigger the enabling of the Java
-  development activity. In this way, users are exposed to new function as they
-  need it, and gradually learn about the activities that are available to them
-  and how they affect the UI. When a user first starts the platform, it is
-  desirable for as many activities as possible to be disabled, so that the
-  application is as simple as possible. Choices made in the welcome page can
-  help determine what activities should be enabled.
-  </p>
-  <p>There are certain places in the UI where the user can ask to see all
-  contributions - even the ones filtered by conventional activities, for example
-  in the <b>New...</b> wizard. UI elements that are filtered by conventional
-  activities can also still be used programmatically using the Eclipse API.
-  </p>
-
-  <h4>Expression-based activities</h4>
-  
-  Expression-based activities differ from conventional activities in that:
-
-  <ul>
-    <li>they are <b>solely</b> controlled by 
-        expressions (see&nbsp;"org.eclipse.core.expressions.definitions").
-        All other declarations related to such an
-  		activity, such as "categories", "default enabled activities", and
-  		"requirement bindings" will be ignored.</li>
-    <li>they move an UI contribution completely out of reach for users and
-    programmers. The UI contributions cannot be accessed programmatically using
-    API calls, and they do not show up when the user asks to see all contributions
-    to, for example, the <b>New...</b> wizard.</li>
-  </ul>
-
-  <h3>Conventional Activities vs. perspectives</h3>We have seen
-  (in <A href="workbench_perspectives.htm">Perspectives</a>) how perspectives are used to
-  organize different view layouts and action sets into tasks. Why do we need
-  activities? While perspectives and activities define similar kinds of tasks,
-  the main difference is how the UI contributions for a plug-in are associated
-  with them. UI contributions are associated with perspectives in the extension
-  definition of the contribution. That is, a plug-in is in charge of
-  determining what perspectives its views and action sets belong to. Plug-ins
-  are also free to define their own perspectives. Even when a perspective is
-  not active, the user can access the views and actions associated with the
-  perspective through commands such as <b>Show View</b>.
-  <p>
-  Activities are a
-  higher level of organization. Individual UI contributions are not aware of
-  activities and do not refer to the activities in their extension definitions.
-  Rather, the activities are expected to be configured at a higher level such
-  as platform integration/configuration or product install. Individual plug-ins
-  typically do not define new activities, unless the plug-in is a systems-level
-  plug-in defined by a systems integrator. In a typical scenario, a systems
-  integrator determines how function is grouped into activities and which ones
-  are enabled by default. Activities are associated with UI contributions using
-  <b>activity pattern bindings</b>, patterns that are matched against the id of
-  the UI contributions made by plug-ins. An example will help demonstrate these
-  concepts.
-  </p>
-
-  <h3>Defining activities</h3>Activities are defined using the <b><A href="../reference/extension-points/org_eclipse_ui_activities.html">org.eclipse.ui.activities</a></b>
-
-  extension point.<br>
-  Let's look at first at a simplified version of how the Eclipse SDK
-  plug-in defines two&nbsp;conventional activities - one for
-  developing Java software and one for developing plug-ins:
-  <pre>&lt;extension
-  point="org.eclipse.ui.activities"&gt;
-  &lt;activity
-    name="Java Activity"
-    description="Developing Java Software"
-    id="org.eclipse.javaDevelopment"&gt;
-  &lt;/activity&gt;
-  
-  &lt;activity
-    name="Plug-in Activity"
-    description="Developing Eclipse Plug-ins"
-    id="org.eclipse.plugInDevelopment"&gt;
-
-  &lt;/activity&gt;
-  ...
-</pre>Activities are assigned a name and description. This name and description
-can be shown to the user whenever the they are enabling and disabling conventional
-activities, or otherwise shown information about an activity. The id of
-the activity is used when defining pattern bindings or other relationships
-between activities. For example, for conventional activities, it is
-possible&nbsp;to declare that one activity requires another activity.
-  <pre>&lt;activityRequirementBinding
-  activityId="org.eclipse.plugInDevelopment"
-  requiredActivityId="org.eclipse.javaDevelopment"&gt;
-
-&lt;/activityRequirementBinding&gt;
-</pre><br>
-  The requirement binding states that the plug-in development activity can only
-  be enabled when the Java development activity is enabled. Related
-  conventional activities can also be bound into <b>categories</b>,
-  that are shown to the user when the user is working with activities.
-  <pre>&lt;category
-  name="Development"
-  description="Software Development"
-  id="org.eclipse.categories.developmentCategory"&gt;
-&lt;/category&gt;
-
-&lt;categoryActivityBinding
-  activityId="org.eclipse.javaDevelopment"
-  categoryId="org.eclipse.categories.developmentCategory"&gt;
-
-&lt;/categoryActivityBinding&gt;
-      
-&lt;categoryActivityBinding
-  activityId="org.eclipse.plugInDevelopment"
-  categoryId="org.eclipse.categories.developmentCategory"&gt;
-&lt;/categoryActivityBinding&gt;
-</pre><br>
-  The category groups the related development conventional activities
-  together. This category is shown to the user when the user manually
-  configures conventional activities. Note that
-  expression-based activities can be also added to categories, but
-  they are ignored when the user changes states of these categories.
-
-  <h4>Binding activities to UI contributions</h4>Activities can be associated
-  with UI contributions by referring to them by id, or by pattern matching. The
-  pattern matching used in activity pattern bindings follows the rules
-  described in the <b>java.util.regex</b> package for regular expressions. The
-  patterns used by the workbench are composed of two parts. The first part uses
-  the identifier of the plug-in that is contributing the UI extension. The
-  second part is the id used by plug-in itself when defining the contribution
-  (which may or may not also include the plug-in id as part of the identifier).
-  The following format is used:
-  <pre>
-
-plug-in-identifier + "/" + local-identifier
-</pre>For example, the following activity pattern binding states that a UI
-contribution from any JDT plug-in id (<tt>org.eclipse.jdt.*</tt>) is associated
-with the Java development activity regardless of its local identifier
-(<tt>.*</tt>).
-  <pre>&lt;activityPatternBinding
-  activityId="org.eclipse.javaDevelopment"
-  pattern="org\.eclipse\.jdt\..*/.*"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>The next binding is more specific. It states that the contribution named
-<tt>javanature</tt> defined in the JDT core (<tt>org.eclipse.jdt.core</tt>) is
-associated with the Java development activity.
-  <pre>&lt;activityPatternBinding
-  activityId="org.eclipse.javaDevelopment"
-  pattern="org\.eclipse\.jdt\.core/javanature"&gt;
-
-&lt;/activityPatternBinding&gt;
-</pre>
-
-It is also possible to refer to a single UI contribution using its id without having to
-use regular expression syntax if the attribute
-<tt>isEqualityPattern</tt> is set to <tt>true</tt>.<br>
-  The following XML shows the previous example with the
-  <tt>isEqualityPattern</tt> set to <tt>true</tt>.<br>
-
-  <tt><br>
-  &lt;activityPatternBinding<br>&nbsp; activityId="org.eclipse.javaDevelopment"<br>&nbsp; pattern="org.eclipse.jdt.core/javanature"<br>&nbsp; isEqualityPattern="true"&gt;<br>
-  &lt;/activityPatternBinding&gt;<br>
-  <br></tt>As you can see, activity pattern bindings can be used to associate
-  large groups of contributions with a particular activity, or to associate
-  very specific contributions with an activity. The following contributions are
-  affected by activities:
-
-  <ul>
-
-    <li>Views and editors</li> 
-
-    <li>Perspectives</li> 
-
-    <li>Preference and property pages</li> 
-
-    <li>Menus and toolbars</li> 
-
-    <li>New wizard</li>
-
-    <li>Common Navigator Action Providers</li>
-  </ul>
-  
-  The convention used by the workbench (plug-in id + local id) allows easy
-  binding to plug-ins that do not necessarily follow the naming practice of
-  prefixing their UI contribution identifiers with their plug-in's
-  identifier. Plug-ins that directly interact with the activity API are free to
-  use their own format for identifying contributions and for pattern-matching
-  against those names.
-
-  <h4>Binding activities to help contributions</h4>Activities are associated
-  with help contributions using the same pattern matching scheme used for UI
-  contributions. The second part of the identifier (the local identifier)
-  indicates the name of the table of contents (TOC) file. For example, the
-  following activity pattern binding associates all TOC files contributed by
-  JDT plug-ins (org.eclipse.jdt.*) with the Java development activity:
-  <pre>&lt;activityPatternBinding
-  activityId="org.eclipse.javaDevelopment"
-  pattern="org\.eclipse\.jdt\..*/.*"&gt;
-&lt;/activityPatternBinding&gt;
-</pre>When the Java development activity is disabled, help books contributed by
-JDT plug-ins, or any sub-books (TOCs linked to, or linked by JDT books), even
-if contributed by a different plug-in, will not show in the help UI. The topics
-defined in these books will also not show in the search results. In the case
-where JDT TOCs were not displayed as primary TOCs, but were instead linked from
-another TOC to appear as sub-trees in a book, disabling the JDT activity has
-the effect of hiding the sub-trees. The containing book will appear to define
-less topics in the UI. Using more specific binding, it is possible to associate
-activities with selected TOCs from plug-ins that contribute multiple TOCs to
-the help system. For example, the following activity pattern binding associates
-the "Examples" TOC with the Java development examples activity.
-  <pre>&lt;activityPatternBinding
-  activityId="org.eclipse.javaDevelopmentExamples"
-  pattern="org\.eclipse\.jdt\.doc\.isv\.topics_Samples.xml"&gt;
-
-&lt;/activityPatternBinding&gt;
-</pre>With such pattern binding, disabling the Java development examples
-activity will hide the "Examples" section from the "JDT Plug-in
-Developer Guide" book.
-
-  <h4>Using the activities API</h4>
-  
-  The workbench activity support includes an API for working
-  with all defined activities (to some extent also expression-based
-  activities) and changing the enabled state (only for conventional
-  activities). Most plug-ins need not be concerned with this API, but it is
-  useful when implementing function that allows the user to work with
-  activities, or for implementing the trigger points that enable a particular
-  conventional activity. It is assumed that any plug-in that is
-  manipulating activities through API is quite aware of the ways that
-  activities are configured for a particular product. For example, the
-  workbench itself uses the API to trigger the enablement of conventional
-  activities such as Java development. We'll look at how the workbench
-  uses the generic activity API to implement triggers. The hub of all activity
-  in the workbench is <A href="../reference/api/org/eclipse/ui/activities/IWorkbenchActivitySupport.html"><b>
-
-  IWorkbenchActivitySupport</b></a>. The activity support works in tandem with
-  an <A href="../reference/api/org/eclipse/ui/activities/IActivityManager.html"><b>IActivityManager</b></a>.
-  Plug-ins can obtain the activity support instance from the workbench, and the
-  activity manager from there.
-  <pre>
-IWorkbenchActivitySupport workbenchActivitySupport = PlatformUI.getWorkbench().getActivitySupport();
-IActivityManager activityManager = workbenchActivitySupport.getActivityManager();
-</pre>The following snippet enables the Java development activity (if it is not
-already enabled). It shows a simplified version of a trigger.
-  <pre>
-...
-//the user did something Java related.  Enable the Java activity.
-Set enabledActivityIds = new HashSet(activityManager.getEnabledActivityIds());
-if (enabledIds.add("org.eclipse.javaDevelopment"))
-  workbenchActivitySupport.setEnabledActivityIds(enabledActivityIds);
-</pre>
-<p><A href="../reference/api/org/eclipse/ui/activities/IActivityManager.html"><b>IActivityManager</b></a>
-  also defines protocol for getting all defined activity and category ids, and
-  for getting the associated <A href="../reference/api/org/eclipse/ui/activities/IActivity.html"><b>IActivity</b></a>
-  or <A href="../reference/api/org/eclipse/ui/activities/IActivity.html"><b>ICategory</b></a>
-  for a particular id. These objects can be used to traverse the definition for
-  an activity or category in API, such as getting the pattern bindings or
-  requirement bindings. Listeners can be registered on the activity manager or
-  on the activities and categories themselves to detect changes in the
-  definition of a particular activity or in the activity manager itself. See
-  the package <b><A href="../reference/api/org/eclipse/ui/activities/package-summary.html">org.eclipse.ui.activities</a></b>
-  for more information.</p>
-
-  <p>
-  Note that the API methods will silently ignore attempts to enable expression-based
-  activities, or similar requests that do not apply to expression-based activities.
-  </p>
-
-  <h4>Using expression-based activities</h4>
-  
-  To filter a UI element using an expression-based activity, create an activity like the
-  following:<br>
-     
-  <tt>&lt;activity <br>&nbsp;id="forbiddenViewActivityId" name="Forbidden View Activity"&gt;<br>&nbsp;&nbsp;&lt;enabledWhen&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&lt;with variable="rightsVariable"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-  &lt;iterate ifEmpty="false" operator="or"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 
-  &lt;equals value="grantShowForbidden" /&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&lt;/iterate&gt;<br>&nbsp;&nbsp;&nbsp;                     
-  &lt;/with&gt;<br>               
-  &nbsp;&nbsp;&lt;/enabledWhen&gt;<br>
-  &lt;/activity&gt;
-  </tt><br><br>
-
-  Then, bind this activity to a UI element, for example a view:<br>
-  <tt>&lt;activityPatternBinding <br>&nbsp;activityId="forbiddenViewActivityId" <br><br>&nbsp;<font color="green">&lt;!-- Switches the interpretation of the pattern 
-     as regular expression off --&gt;</font> <br>&nbsp;isEqualityPattern="true" <br>&nbsp;pattern="DemoRCP/demorcp.views.ForbiddenView"&gt; <br>
-  &lt;/activityPatternBinding&gt;
-  </tt>
-
-   <p>The following code snippets show how to control the variable "rightsVariable"
-   that appears in the activity's "enabledWhen" expression. New variables can be added
-   through the <b>org.eclipse.ui.services</b> extension point as subclasses of
-   <b>AbstractSourceProvider</b>.        
-     </p>
-
-   <p align="left">
-   <tt>
-    <code>
-<font color="#7f0055"><b>import&nbsp;</b></font><font color="#000000">java.util.HashMap;<br>...</font><br>
-<font color="#7f0055"><b>import&nbsp;</b></font><font color="#000000">org.eclipse.ui.AbstractSourceProvider;</font><br>
-
-<font color="#7f0055"><b>import&nbsp;</b></font><font color="#000000">org.eclipse.ui.PlatformUI;</font><br>
-<font color="#7f0055"><b>import&nbsp;</b></font><font color="#000000">org.eclipse.ui.handlers.IHandlerService;</font><br>
-<font color="#7f0055"><b>import&nbsp;</b></font><font color="#000000">org.eclipse.ui.services.IEvaluationService;</font><br>
-<font color="#ffffff"></font><br>
-<font color="#7f0055"><b>public&nbsp;class&nbsp;</b></font><font color="#000000">RightsSourceProvider&nbsp;</font><font color="#7f0055"><b>extends&nbsp;</b></font><font color="#000000">AbstractSourceProvider&nbsp;</font><font color="#000000">{</font><br>
-
-<font color="#ffffff"></font><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#7f0055"><b>public&nbsp;final&nbsp;static&nbsp;</b></font><font color="#000000">String&nbsp;RIGHT_FORBIDDEN&nbsp;=&nbsp;<font color="#2a00ff">"grantShowForbidden"</font><font color="#000000">;</font></font><br>
-<font color="#ffffff"></font><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#7f0055"><b>public&nbsp;final&nbsp;static&nbsp;</b></font><font color="#000000">String&nbsp;RIGHTS_VARIABLE&nbsp;=&nbsp;</font><font color="#2a00ff">"rightsVariable"</font><font color="#000000">;</font><br>
-
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#7f0055"><b>private&nbsp;final&nbsp;static&nbsp;</b></font><font color="#000000">String</font><font color="#000000">[]&nbsp;</font><font color="#000000">PROVIDED_SOURCE_NAMES&nbsp;=&nbsp;</font><font color="#7f0055"><b>new&nbsp;</b></font><font color="#000000">String</font><font color="#000000">[]&nbsp;{&nbsp;</font><font color="#000000">RIGHTS_VARIABLE&nbsp;</font><font color="#000000">}</font><font color="#000000">;</font><br>
-<font color="#ffffff"></font><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#7f0055"><b>private&nbsp;final&nbsp;static&nbsp;</b></font><font color="#000000">Map&lt;String,&nbsp;List&lt;String&gt;&gt;&nbsp;stateMap&nbsp;=&nbsp;</font><font color="#7f0055"><b>new&nbsp;</b></font><font color="#000000">HashMap&lt;String,&nbsp;List&lt;String&gt;&gt;</font><font color="#000000">()</font><font color="#000000">;</font><br>
-
-<font color="#ffffff"></font><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#7f0055"><b>public&nbsp;</b></font><font color="#000000">Map&nbsp;getCurrentState</font><font color="#000000">()&nbsp;{<BR>&nbsp;&nbsp;&nbsp;&nbsp;<FONT 
-color="#008000">/*&nbsp;"YourRightsHandler" is here just an example for&nbsp;a 
-static class<BR>&nbsp;&nbsp;&nbsp;&nbsp; * which returns the list of 
-rights&nbsp;as&nbsp;a list of strings. */</FONT></font><br>
-
-<font color="#ffffff">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#000000">stateMap.put</font><font color="#000000">(</font><font color="#000000">RIGHTS_VARIABLE,&nbsp;<EM>YourRightsHandler</EM>.getUserRights</font><font color="#000000">())</font><font color="#000000">;</font><br>
-<font color="#ffffff">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#7f0055"><b>return&nbsp;</b></font><font color="#000000">stateMap;</font><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#000000">}</font><br><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#7f0055"><b>public&nbsp;</b></font><font color="#000000">String</font><font color="#000000">[]&nbsp;</font><font color="#000000">getProvidedSourceNames</font><font color="#000000">()&nbsp;{</font><br>
-
-<font color="#ffffff">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#7f0055"><b>return&nbsp;</b></font><font color="#000000">PROVIDED_SOURCE_NAMES;</font><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#000000">}</font><br><BR>&nbsp;&nbsp;<FONT 
-color="#008000">/*&nbsp;This triggers an update of the rights variable state, and 
-will update also all&nbsp;<BR>&nbsp;&nbsp; * listeners to the evaluation 
-service. So that every menu point, which is also <BR>&nbsp;&nbsp; * expression 
-controlled, gets updated too. */</FONT><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#7f0055"><b>public&nbsp;</b></font><font color="#7f0055"><b>void&nbsp;</b></font><font color="#000000">updateRights</font><font color="#000000">()&nbsp;{</font><br>
-
-<font color="#ffffff">&nbsp;&nbsp;&nbsp;&nbsp;</font><font color="#000000">fireSourceChanged</font><font color="#000000">(</font><font color="#990000">0</font><font color="#000000">,&nbsp;getCurrentState</font><font color="#000000">())</font><font color="#000000">;</font><br>
-<font color="#ffffff">&nbsp;&nbsp;</font><font color="#000000">}</font><br><BR>&nbsp; // ...<br>
-<font color="#000000">}</font></code>    
-   </tt></p>
-   
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
deleted file mode 100644
index 2ead60d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_contexts.htm
+++ /dev/null

@@ -1,145 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contexts</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>
-Contexts</h3>
-<P >
-A <b>context</b> can be used to influence what commands are available to the user at any given moment.
-Contexts are much more dynamic than activities.  While an activity represents a broad set of function that
-is available to the user most of the time, contexts describe a focus of the user at a specific point
-in time.  For example, the commands available to a user while editing text might be different than those
-available to a user while editing Java text or browsing packages in the package explorer.
-</P>
-<h4>Defining a context</h4>
-<p>
-Contexts are declared in the
-<b><a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></b>
-extension point. Consider the following context which is defined for editing text:
-</p>
-<pre>&lt;extension
-	point="org.eclipse.ui.contexts"&gt;
-	&lt;context
-		name="%context.editingText.name"
-		description="%context.editingText.description"
-		id="org.eclipse.ui.textEditorScope"
-		parentId="org.eclipse.ui.contexts.window"&gt;
-	&lt;/context&gt;
-</pre>
-Contexts are assigned a name and description that are used when showing information about the context to the user.
-The id of the context is used when binding UI contributions such as commands to a particular context.
-<h4>Context hierarchies</h4>
-<p>
-Contexts are hierarchical in nature.  When a context is active, the commands available in the context and in its parent contexts
-are also available.  This is useful for defining levels of contexts that move from very general situations down to more
-specific contexts.  In the context definition above, note that there is an id of a parent assigned to the context:
-</p>
-<pre>	&lt;context
-		name="%context.editingText.name"
-		description="%context.editingText.description"
-		id="org.eclipse.ui.textEditorScope"
-		<b>parentId="org.eclipse.ui.contexts.window"</b>&gt;
-	&lt;/context&gt;
-</pre>
-The parent context defines the more general context of working within a window.  Its parent defines an even
-more general context of working within a window or a dialog.
-<pre>
-&lt;context
-	name="%context.window.name"
-	description="%context.window.description"
-	id="org.eclipse.ui.contexts.window"
-	<b>parentId="org.eclipse.ui.contexts.dialogAndWindow"</b>&gt;
-&lt;/context&gt;
-&lt;context
-	name="%context.dialogAndWindow.name"
-	description="%context.dialogAndWindow.description"
-	id="org.eclipse.ui.contexts.dialogAndWindow"&gt;
-&lt;/context&gt;
-</pre>
-<h4>Associating a contribution with a context</h4>
-<p>
-So far, all we've done is define a hierarchy of contexts.  The context becomes useful when it is referenced in the
-description of another UI contribution.  The most common use of contexts is in key bindings.  When a context is
-associated with a key binding, the key binding will only be active when the user is in that context.  For example,
-the following markup specifies the root dialog and window context as the context for a key binding:
-</p>
-<pre>&lt;extension
-         point="org.eclipse.ui.bindings"&gt;
-      &lt;key
-            sequence="M1+X"
-            <b>contextId="org.eclipse.ui.contexts.dialogAndWindow"</b>
-            commandId="org.eclipse.ui.edit.cut"
-            schemeId="org.eclipse.ui.defaultAcceleratorConfiguration"/&gt;
-&lt;/extension&gt;
-</pre>
-<h4>
-Using Context API</h4>
-<p>
-The workbench context support includes an API for working with the defined contexts and defining
-criteria under which a particular context should become enabled.  Most plug-ins need not be 
-concerned with this API, but it is useful when defining specialized views or editors that define
-new contexts.  
-</p>
-<p>
-The starting point for working with contexts in the workbench is 
-<a href="../reference/api/org/eclipse/ui/contexts/IContextService.html"><b>IContextService</b></a>.
-Plug-ins can obtain the global context support instance from the workbench.  
-</p>
-<pre>IContextService contextService = (IContextService)PlatformUI.getWorkbench()
-	.getService(IContextService.class);
-</pre>
-<p>
-Services like <a href="../reference/api/org/eclipse/ui/contexts/IContextService.html"><b>IContextService</b></a>,
-<a href="../reference/api/org/eclipse/ui/handlers/IHandlerService.html"><b>IHandlerService</b></a>,
-and <a href="../reference/api/org/eclipse/ui/keys/IBindingService.html"><b>IBindingService</b></a>
-can be retrieved using an
-<a href="../reference/api/org/eclipse/ui/services/IServiceLocator.html"><b>IServiceLocator</b></a>. 
-<a href="../reference/api/org/eclipse/ui/IWorkbench.html"><b>IWorkbench</b></a>,
-<a href="../reference/api/org/eclipse/ui/IWorkbenchWindow.html"><b>IWorkbenchWindow</b></a>,
-and <a href="../reference/api/org/eclipse/ui/IWorkbenchSite.html"><b>IWorkbenchSite</b></a>
-are all <a href="../reference/api/org/eclipse/ui/services/IServiceLocator.html"><b>IServiceLocator</b></a>.
-</p>
-<p>
-<b>IContextService</b> defines 
-protocol for getting all defined or enabled context ids, and for getting the associated
-<a href="../reference/api/org/eclipse/core/commands/contexts/Context.html"><b>Context</b></a>
-for a particular id.
-These objects can be used to traverse the definition for a context in API, such as getting the
-id, name, or id of the parent context.
-Listeners can be registered on the context manager or on the contexts 
-themselves to detect changes in the definition of a particular context or in the context manager
-itself. 
-See the package <b><a href="../reference/api/org/eclipse/core/commands/contexts/package-summary.html">org.eclipse.core.commands.contexts</a></b>
-for more information.
-</p>
-
-<p><b>Contexts</b> can be enabled programmatically:</p>
-<pre>IContextActivation activation = contextService.activateContext(&quot;org.eclipse.ui.textEditorScope&quot;);
-</pre>
-<p>
-The <a href="../reference/api/org/eclipse/ui/contexts/IContextActivation.html"><b>IContextActivation</b></a>
-is a token that can be used to deactivate an active context.  You should ensure
-that you only activate defined <b>Context</b>s.
-</p>
-
-<p>
-If you are activating a more specific <b>Context</b> within your part (either 
-View or Editor) you can use the part site service locator to active your <b>Context</b>.
-The part's <b>IContextService</b> will take care of activating and deactivating the
-<b>Context</b> as your part is activated or deactivated.  It will also dispose the
-<b>Context</b> when the part is disposed.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm
deleted file mode 100644
index 683ba66..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_decorators.htm
+++ /dev/null

@@ -1,156 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Decorators</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>
-Decorators</H3>
-
-<p>Your plug-in can use <b>decorators</b> to annotate the images for resources
-and other objects that appear in the workbench views.&nbsp; Decorators are
-useful when your plug-in adds functionality for existing resource types.&nbsp;
-Many of the standard workbench views participate in showing decorations.&nbsp;&nbsp;</p>
-
-
-<p>For example, PDE contributes decorators that allow you to distinguish between
-binary and source projects.</p>
-
-
-<p><img src="images/workbenchdecorators.png" alt="Package explorer view with PDE decorators" border="0"></p>
-
-
-<p>The <b>com.example.helloworld&nbsp; </b>project is the only source project
-shown in the package explorer.&nbsp; Note how all of the other binary projects show the
-binary decorator at the top left of the Java project icon.&nbsp; This decorator
-is contributed by PDE using the <a href="../reference/extension-points/org_eclipse_ui_decorators.html"><b>org.eclipse.ui.decorators</b></a>
-extension point.</p>
-
-
-<pre>&lt;extension
-         point=&quot;org.eclipse.ui.decorators&quot;&gt;
-      &lt;decorator
-            <b>lightweight=&quot;true&quot;
-</b>            <b>quadrant=&quot;TOP_LEFT&quot;</b>
-            adaptable=&quot;true&quot;
-            label=&quot;%decorator.label&quot;
-            <b>icon=&quot;icons/full/ovr16/binary_co.png&quot;</b>
-            state=&quot;false&quot;
-            id=&quot;org.eclipse.pde.ui.binaryProjectDecorator&quot;&gt;
-         &lt;description&gt;
-            %decorator.desc
-         &lt;/description&gt;
-         &lt;enablement&gt;
-            ...
-         &lt;/enablement&gt;
-      &lt;/decorator&gt;
- &lt;/extension&gt;</pre>
-
-
-<p>There are several different ways to supply a decorator implementation.&nbsp;
-This markup uses the simplest way, known as a <b>declarative</b> <b>lightweight</b>
-decorator.&nbsp; When a declarative lightweight decorator is defined, the markup
-contains a complete description of the decorator's icon, placement, and enabling
-conditions.&nbsp; Declarative decorators are useful when only an icon is used to
-decorate the label.&nbsp; The plug-in need only specify the <b>quadrant</b> where the decorator should be
-overlayed on the regular icon and the <b>icon</b> for the overlay.&nbsp; As
-shown in the picture, the PDE binary icon is overlayed in the top left quadrant of the
-package icon.</p>
-
-
-<p>If your plug-in needs to manipulate the label text in addition to the icon,
-or if the type of icon is determined dynamically, you can use a non-declarative <b>lightweight</b>
- decorator.&nbsp; In this case, an implementation <strong>class</strong> that implements <a href="../reference/api/org/eclipse/jface/viewers/ILightweightLabelDecorator.html"><b>ILightweightLabelDecorator</b></a>
-must be defined.&nbsp; The designated class is responsible for supplying a prefix,
-suffix, and overlay image at runtime which are applied to the label.&nbsp; The mechanics of
-concatenating the prefix and suffix with the label text and performing the overlay
-are handled by the workbench code in a background thread.&nbsp; Thus, any work
-performed by your plug-in in its <a href="../reference/api/org/eclipse/jface/viewers/ILightweightLabelDecorator.html"><b>ILightweightLabelDecorator</b></a>
-implementation must be UI-thread safe.&nbsp; (See <a href="swt_threading.htm#syncExec">Executing
-code from a non-UI thread</a> for more details.)</p>
-
-
-<p>&nbsp; The following markup shows how the CVS
-client defines its decorator using this technique:</p>
-
-
-<pre>&lt;extension
-         point=&quot;org.eclipse.ui.decorators&quot;&gt;
-    &lt;decorator
-            objectClass=&quot;org.eclipse.core.resources.IResource&quot;
-            adaptable=&quot;true&quot;
-            label=&quot;%DecoratorStandard.name&quot;
-            state=&quot;false&quot;
-            <b>lightweight= &quot;true&quot;</b>
-            <b>quadrant = &quot;BOTTOM_RIGHT&quot;</b>
-            <b>class=&quot;org.eclipse.team.internal.ccvs.ui.CVSLightweightDecorator&quot;</b>
-            id=&quot;org.eclipse.team.cvs.ui.decorator&quot;&gt;
-         &lt;description&gt;
-            %DecoratorStandard.desc
-         &lt;/description&gt;
-    &lt;/decorator&gt;
-&lt;/extension&gt;</pre>
-
-
-<p>Decorators are ultimately controlled by the user via the workbench <b>Label
-Decorations</b> preferences page.&nbsp;
-Individual decorators can be turned on and off.&nbsp; Even so, it is a good idea
-to design your decorators so that they do not overlap or conflict with existing
-platform SDK decorators.&nbsp;If multiple plug-ins contribute lightweight
-decorators to the same quadrant, the conflicts are resolved
-non-deterministically.&nbsp;&nbsp;</p>
-
-
-<p>Your plug-in may also do all of the image and label management
-itself.&nbsp; In this case, the <b>lightweight</b> attribute should be set to
-false and the <b>class </b>attribute should name a class that implements <a href="../reference/api/org/eclipse/jface/viewers/ILabelDecorator.html"><b>ILabelDecorator</b></a>.&nbsp;
-This class allows you to decorate the original label's image and text with your
-own annotations.&nbsp;&nbsp;It gives you increased flexibility since you aren't
-limited to prefixes, suffixes, and simple quadrant overlays.</p>
-
-
-<p>Other attributes of a decorator are independent of the particular
-implementation style.&nbsp; The <b>label</b> and <b>description</b> attributes
-designate the text that is used to name and describe the decorator in the
-preferences dialog.&nbsp; The <b>objectClass</b> names the class of objects to
-which the decorator should be applied.&nbsp; The <b>enablement</b> attribute
-allows you to describe the conditions under which the object should be
-decorated.&nbsp;&nbsp; The <b>adaptable</b> flag indicates
-whether objects that adapt to <b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>
-should also be decorated.&nbsp; The <b>
-state</b> flag controls whether the decorator is visible by default.</p>
-
-
-<p> If your decorators include information that is
-expensive to compute or potentially distracting, you may want to contribute your
-own preferences that allow the user to further fine-tune the decorator once it
-is on.&nbsp; This technique is used by the CVS client.</p>
-
-
-<p><img src="images/cvsdecorators.png" alt="CVS decorators preference page" border="0"></p>
-
-
-<p>&nbsp;</p>
-<p><strong>Decorator Update Cycle</strong></p>
-<p>Decoration is initiated by refreshing label providers that use the DecoratorManager 
-  to provide decoration. As decoration processing is done in the background there 
-  will be a period between when the label is requested and the labelProviderChanged 
-  event is fired that will be taken up by decoration calculation. During this 
-  time decoration on an Object will only be calculated once for effeciency reasons. 
-  If the decorator changes during this time it is possible that a stale result 
-  will be broadcast as the second and subsequent calls to decorate an element 
-  will be ignored.</p>
-<p>Decorator contributors should avoid changing thier decorators while decoration 
-  is occuring. If this is not possible a second call to decorate an element after 
-  the labelProviderChanged in processed will be required.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm
deleted file mode 100644
index f0095af..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_elementFactories.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Element factories</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-<H3>Element factories</H3>
-<P >
-Element factories are used to recreate workbench model objects from data that was saved during workbench shutdown.</P>
-<P >
-Before we look closely at the element factory extension, we need to review a general technique
-that is used throughout the platform to add plug-in specific behavior to common platform model objects.</P>
-
-<H4>
-<a name="workbench_advext_adaptables">
-IAdaptables and workbench adapters</a></H4>
-<P >
-When browsing the various workbench classes, you will notice that many of the workbench interfaces extend the
-<b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"> IAdaptable</a></b> interface.</P>
-<P >
-Plug-ins use adapters to add specific behavior to pre-existing types in the system. For example, the workbench may want
-resources to answer a label and an image for display purposes. We know that it's not good design to add UI specific 
-behavior to low-level objects, so how can we add this behavior to the resource types?</P>
-<P >
- Plug-ins can register adapters that add behavior to pre-existing types.
-Application code can then query an object for a particular adapter. If there is one registered for it,
-the application can obtain the adapter and use the new behaviors defined in the adapter.</P>
-<P >
-By providing a facility to dynamically query an adapter for an object, we can improve the flexibility of the system 
-as it evolves. New adapters can be registered for platform types by new plug-ins without having to change the 
-definitions of the original types. The pattern to ask an object for a particular
-adapter is as follows: </P>
-<pre>
-   //given an object o, we want to do &quot;workbench&quot; things with it.
-   if (!(o instanceof IAdaptable)) {
-      return null;
-   }
-   IWorkbenchAdapter adapter = (IWorkbenchAdapter)o.getAdapter(IWorkbenchAdapter.class);
-   if (adapter == null)
-      return null;
-   // now I can treat o as an IWorkbenchAdapter
-   ...
-</pre>
-<P >
-If there is no adapter registered for the object in hand, null will be returned as the adapter. Clients must be 
-prepared to handle this case.  There may be times when an expected adapter has not been registered.</P>
-<P >
-The workbench uses adapters to obtain UI information from the base platform types, such as
-<b><a href="../reference/api/org/eclipse/core/resources/IResource.html">IResource</a></b>.
-Adapters shield the base types from UI-specific knowledge and allow the workbench to evolve its interfaces 
-without changing the definitions of the base. </P>
-<P >
-Without adapters, any class that might be passed around in the workbench API would have to implement the UI
-interfaces, which would increase the number of class definitions, introduces tight
-coupling, and create circular dependencies between the core and UI classes. With adapters, each class implements
-<b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"> IAdaptable</a></b>
-and uses the adapter registry to allow plug-ins to extend the behavior of the base types.</P>
-<P >
-Throughout the workbench code, you'll see cases where a platform core type is queried for an adapter.
-The query is used to obtain an object that knows how to answer UI oriented information about
-the type.</P>
-
-
-<H4>
-Element factories</H4>
-<P >
-When the workbench is shut down by the user, it must save the current state of the
-<b><a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"> IAdaptable</a></b>
-objects that are shown in the workbench. An object's state is stored by saving
-the primitive data parameters of the object in a special format, an
-<a href="../reference/api/org/eclipse/ui/IMemento.html"><b>IMemento</b></a>. The id of a factory that can recreate 
-the object from an <a href="../reference/api/org/eclipse/ui/IMemento.html"><b>IMemento</b></a>
-is also stored and the data is saved in the file system.</P>
-<P >
-When the platform is restarted, the workbench finds the element factory associated with the
-<a href="../reference/api/org/eclipse/ui/IMemento.html"><b>IMemento</b></a>'s
-factory id. It finds the factory by checking the plug-in registry for contributions to the
-<a href="../reference/extension-points/org_eclipse_ui_elementFactories.html"><b> org.eclipse.ui.elementFactories</b></a>
-extension.</P>
-<P >
-The markup is pretty simple. We just have to specify the id of the factory and the corresponding class that 
-implements the factory.</P>
-<P >
-The following code snippet is from the workbench <b>plugin.xml</b>.</P>
-<pre>
-&lt;extension
-         point=&quot;org.eclipse.ui.elementFactories&quot;&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.model.ResourceFactory&quot;
-            id=&quot;org.eclipse.ui.internal.model.ResourceFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.model.WorkspaceFactory&quot;
-            id=&quot;org.eclipse.ui.internal.model.WorkspaceFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.part.FileEditorInputFactory&quot;
-            id=&quot;org.eclipse.ui.part.FileEditorInputFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.dialogs.WelcomeEditorInputFactory&quot;
-            id=&quot;org.eclipse.ui.internal.dialogs.WelcomeEditorInputFactory&quot;&gt;
-      &lt;/factory&gt;
-      &lt;factory
-            class=&quot;org.eclipse.ui.internal.WorkingSetFactory&quot;
-            id=&quot;org.eclipse.ui.internal.WorkingSetFactory&quot;&gt;
-      &lt;/factory&gt;
-&lt;/extension&gt;
-
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm
deleted file mode 100644
index 5b7469a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectiveExtension.htm
+++ /dev/null

@@ -1,133 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>org.eclipse.ui.perspectiveExtensions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H3>
-org.eclipse.ui.perspectiveExtensions</H3>
-<P >
- Plug-ins can add their own action sets, views, and various shortcuts to existing
- perspectives by contributing to the <b><a href="../reference/extension-points/org_eclipse_ui_perspectiveExtensions.html">org.eclipse.ui.perspectiveExtensions</a></b>
- extension point.</P>
-
-
-<P >The contributions that can be defined for new perspectives (action sets, wizard entries, view layout,
-view shortcuts, and perspective shortcuts) can also be supplied for
-an existing perspective.&nbsp; One important difference is that these
-contributions are
-specified in the <b>plugin.xml</b> markup instead of
-configuring them into an
- <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a>.</b>
-</P>
-
-
-<P >The following markup shows how the JDT extends the platform's debug
-perspective.</P>
-
-
-<pre>
-&lt;extension point=&quot;org.eclipse.ui.perspectiveExtensions&quot;&gt;
-  &lt;perspectiveExtension 
-	<b>targetID</b>=&quot;org.eclipse.debug.ui.DebugPerspective&quot;&gt;
-	&lt;actionSet id=&quot;org.eclipse.jdt.debug.ui.JDTDebugActionSet&quot;/&gt;
-    	&lt;view id=&quot;org.eclipse.jdt.debug.ui.DisplayView&quot; 
-        	relative=&quot;org.eclipse.debug.ui.ExpressionView&quot; 
-    		relationship=&quot;stack&quot;/&gt;	
-        &lt;view id=&quot;org.eclipse.jdt.ui.PackageExplorer&quot; 
-                relative=&quot;org.eclipse.debug.ui.DebugView&quot; 
-                relationship=&quot;stack&quot;
-                visible=&quot;false&quot;/&gt;
-        &lt;view id=&quot;org.eclipse.jdt.ui.TypeHierarchy&quot; 
-                relative=&quot;org.eclipse.debug.ui.DebugView&quot; 
-                relationship=&quot;stack&quot;
-                visible=&quot;false&quot;/&gt;
-        &lt;view id=&quot;org.eclipse.search.SearchResultView&quot; 
-                relative=&quot;org.eclipse.debug.ui.ConsoleView&quot; 
-                relationship=&quot;stack&quot;
-                visible=&quot;false&quot;/&gt; 
-    	&lt;viewShortcut id=&quot;org.eclipse.jdt.debug.ui.DisplayView&quot;/&gt;
-  &lt;/perspectiveExtension&gt; 
-&lt;/extension&gt;</pre>
-
-
-<P >The <b>targetID</b> is the id of the perspective to which the plug-in is
-contributing new behavior.&nbsp; The <b>actionSet</b> parameter identifies the <b>id</b>
-of a previously declared action set that should be added to the target
-perspective.&nbsp; This markup is analogous to using<b>
-IPageLayout.addActionSet</b> in the&nbsp;<b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>.</P>
-
-
-<P >Contributing a view to a perspective is a little more involved, since the
-perspective page layout information must be declared.&nbsp; The <b>visible</b>
-attribute controls whether the contributed view is initially visible when the perspective is
-opened.&nbsp; In addition to
-supplying the <b>id</b> of the contributed view, the id
-of a view that already exists in the perspective ( a <b>relative</b>
-view) must be specified as a reference point for placing the new view.&nbsp; The
-<b>relationship</b> parameter specifies the layout
-relationship between the new view and the <b>relative</b>
-view.&nbsp;&nbsp;</P>
-
-
-<ul>
-  <li> <b>stack</b> indicates that the
-view will be stacked with the relative view in a folder</li>
-  <li><b>fast</b> indicates that the view will be shown as a fast
-    view&nbsp;&nbsp;</li>
-  <li> <b>left</b>, <b>right</b>,
-<b>top</b>, or <b>bottom</b> indicate that the new view will be placed beside the <b>relative</b>
-view.&nbsp; In this case, a <b> ratio</b> between 0.0 and 1.0 must be defined, which
-indicates the percentage of area in the <b>relative</b>
-view that will be allocated to the new view.&nbsp;&nbsp;</li>
-</ul>
-
-
-<P >Specifying a <b>perspectiveShortcut</b>
-indicates that another perspective (specified by <b>id</b>)
-should be added to the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Open Perspective...</b></a>
-
-menu of the target
-perspective.&nbsp; This markup is analogous to calling <b>IPageLayout.addPerspectiveShortcut</b>
-in the original perspective definition in the <b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>.&nbsp;
-Plug-ins can also add view shortcuts and new wizard shortcuts in a similar
-manner.&nbsp;&nbsp;</P>
-
-
-<P >You can also specify one or more views as a valid <b>showInPart</b>.&nbsp; The
-views should be specified by the id used in their <b><a href="../reference/extension-points/org_eclipse_ui_views.html">org.eclipse.ui.views</a></b>
-extension contribution.&nbsp;&nbsp; This controls which views are available as
-targets in the <b>Navigate &gt; Show In </b>menu.&nbsp; The ability to specify a
-&quot;show in&quot; view in the extension markup allows you to add your
-newly contributed views as targets in another perspective's &quot;show in&quot;
-menus.&nbsp; See <a href="workbench_perspectives.htm#showin">Linking views and
-editors</a> for more information on &quot;show in.&quot;</P>
-
-
-<P > See <b><a href="../reference/extension-points/org_eclipse_ui_perspectiveExtensions.html">org.eclipse.ui.perspectiveExtensions</a></b>
-for a complete definition of the extension point.</P>
-
-
-<P >&nbsp;</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm
deleted file mode 100644
index f3fe9c5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_perspectives.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.perspectives</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<H3>
-org.eclipse.ui.perspectives</H3>
-<P >
-The platform itself defines one perspective, the <b> Resource</b> perspective. Other platform plug-ins, such as
-the help system and the Java tooling, define additional perspectives. Your plug-in can define its own
-perspective by contributing to the <b><a href="../reference/extension-points/org_eclipse_ui_perspectives.html">org.eclipse.ui.perspectives</a></b>
-extension point.</P>
-<P >
-The specification of the perspective in the <b> plugin.xml</b> is straightforward. The following markup is used by the workbench in defining its own resource perspective.</P>
-<pre>
-&lt;extension
-         point=&quot;org.eclipse.ui.perspectives&quot;&gt;
-      &lt;perspective
-            name=&quot;%Perspective.resourcePerspective&quot;
-            icon=&quot;icons/full/cview16/resource_persp.png&quot;
-            class=&quot;org.eclipse.ui.internal.ResourcePerspective&quot;
-            id=&quot;org.eclipse.ui.resourcePerspective&quot;&gt;
-      &lt;/perspective&gt;
-   &lt;/extension&gt;</pre>
-<P >
-A plug-in must supply an <b> id</b> and <b> name</b> for the perspective, along with the name of the
-<b> class</b> that implements the perspective. An <b> icon</b> can also be specified. The perspective class should implement
-<b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm
deleted file mode 100644
index 2661b85..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_advext_resourceFilters.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Contributing resource filters</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-
-
-<H3>
-Contributing resource filters</H3>
-<P >
-The resource filters extension allows plug-ins to define filters that are useful for filtering out file types in the resource navigator view. This
-extension is useful when special file types are used to represent internal plug-in information
-but you do not want the files to be shown in the workbench or manipulated by the user.</P>
-<P >
-The workbench filters out the pattern &quot;<b>.*</b>&quot; to exclude internal files such as .metadata from the resource navigator. Likewise, the JDT plug-in filters out &quot;<b>*.class</b>&quot; files to hide compiled classes.</P>
-<P >
-The markup for the resource filters extension is simple.&nbsp; The following is
-from the workbench <b>plugin.xml</b>.</P>
-<pre>
-&lt;extension
-         point=&quot;org.eclipse.ui.ide.resourceFilters&quot;&gt;
-      &lt;filter
-            selected=&quot;false&quot;
-            pattern=&quot;.*&quot;&gt;
-      &lt;/filter&gt;
-   &lt;/extension&gt;
-</pre>
-<P >The filters can be enabled by the user using the resource navigator's local
-pull-down menu.</P>
-
-
-<P ><img src="images/filtersmenu.png" alt="Resource filters menu" border="0" ></P>
-
-
-<P >In addition to declaring the <b>filter pattern</b>,
-the plug-in can use the <b>selected</b> attribute to
-specify whether the filter should be enabled in the resource navigator.&nbsp;
-This attribute only determines the initial state of the filter pattern.&nbsp; The user can
-control which filter patterns are active.</P>
-
-
-<P ><img src="images/filtersselection.png" alt="Filter selection dialog" border="0" ></P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm
deleted file mode 100644
index 1a8c6bc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Basic workbench extension points
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Basic workbench extension points using actions</H2>
-<P >
-The workbench defines extension points that allow plug-ins to contribute
-behaviors to existing views and editors or to provide implementations for
-new views and editors. Using commands is covered in the <a href="workbench_cmd.htm" 
-class="XRef">Basic workbench extension points using commands</a> section. Here we are
- going to take a look at the
-contributions to these extension points from one of the workbench sample applications, the readme tool. </P>
-<P >
-The readme tool is a plug-in that provides custom editing and navigation for a specific resource
-, a
-<b> .readme</b> file. The example shows many typical (but simplified) ways that extensions can be used to provide specialized tools.</P>
-<P >
-The readme tool contributes to the menus of the navigator view, adds editor related actions to the workbench menus and
-tool bar, defines a custom view and content outliner, and defines markers
-and marker resolutions. The figure below shows some of the
-customized features added to the workbench by the readme tool.</P>
-<P >
-<img src="images/readmeoverview.png" alt="Workbench with readme tool contributing action sets, view and editor actions, custom editors and views, and outliner" border="0"></P>
-<P >
-The readme tool also contributes preference and properties pages to the workbench.  Later we'll also look
-at some wizard contributions in 
-<a HREF="dialogs.htm" CLASS="XRef"> Dialogs and wizards</a>.</P>
-<P >
-The readme tool is located in the <b>org.eclipse.ui.examples.readmetool</b> package. The
-<b> readmetool.jar</b> and <b> plugin.xml</b> can be found in the
-<b> org.eclipse.ui.examples.readmetool</b> directory underneath the
-<b> plugins</b> directory. To follow along, you will need to make sure that
-you have installed the platform examples.&nbsp; (See the <a href="../samples/samples.html">Examples
-Guide </a> for more information.)&nbsp; </P>
-<P >
-The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> implements many different workbench extensions.&nbsp; We will start
-with one of the simplest workbench extension points, a view.&nbsp; We'll
-continue by looking at additional readme tool extensions. </P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm
deleted file mode 100644
index cb3d32d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSetPartAssociations.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Action set part associations</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Action set part associations</H2>
-
-<P >
-Once your plug-in defines an <a href="workbench_basicext_actionSets.htm">action
-set</a>, it can use the
-<a href="../reference/extension-points/org_eclipse_ui_actionSets.html"><b> org.eclipse.ui.actionSetPartAssociations</b></a> 
-extension point to specify that an action set should be made visible when a
-particular view or editor is active.&nbsp;&nbsp; </P>
-
-<P >
- Ultimately, the user controls the
-appearance of action sets using
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Customize Perspectives...</b></a>
-
-in
-the workbench menu.&nbsp;If the user marks an action set visible, it will always be visible when the
-perspective is active, regardless of
-the active view or editor.&nbsp; Likewise, if the user marks the action set as hidden, it will always be hidden when the perspective is active.&nbsp; If the user does not change the state of
-an action set in this dialog, then the action set part associations are used to
-determine the visibility of the action set.</P>
-
-
-<P >
-The markup for an action set part association is straightforward.&nbsp; The
-following example comes from the Java development tools (JDT) UI plug-in.</P>
-<pre>
-   &lt;extension point=&quot;org.eclipse.ui.actionSetPartAssociations&quot;&gt;
-	&lt;actionSetPartAssociation 
-		<b>targetID</b>=&quot;org.eclipse.jdt.ui.CodingActionSet&quot;&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.PackageExplorer&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.TypeHierarchy&quot; /&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.CompilationUnitEditor&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.ClassFileEditor&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.ProjectsView&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.PackagesView&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.TypesView&quot;/&gt;
-		&lt;part id=&quot;org.eclipse.jdt.ui.MembersView&quot;/&gt;
-	&lt;/actionSetPartAssociation&gt;
-&lt;/extension&gt;
-</pre>
-<P >The <b>targetID</b> specifies the action set.&nbsp; (The <b> CodingActionSet</b> was
-previously defined in the JDT plug-in manifest.)&nbsp; One or more <b>part</b>
-attributes can be specified to indicate which views and editors will cause the
-action set to become visible in the menus and toolbar.&nbsp; The effect of this extension
-contribution is that the actions associated with writing Java code will only be
-visible when one of the specified views is active.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm
deleted file mode 100644
index ffc1e02..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_actionSets.htm
+++ /dev/null

@@ -1,158 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>org.eclipse.ui.actionSets</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.actionSets</H3>
-
-<P >
-Your plug-in can contribute menus, menu items, and tool bar items to the workbench menus and toolbar
-by using the
-<a href="../reference/extension-points/org_eclipse_ui_actionSets.html"><b> org.eclipse.ui.actionSets</b></a> 
-extension point. In order to reduce the clutter that would be caused by having every plug-in's menu contributions shown at once, the contributions are grouped into action sets which can be made visible by user preference.</P>
-<P >
-You can see which action sets have been contributed to your workbench by choosing
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Customize Perspective...</b></a>
-
-from the workbench menu. This option will show you a dialog that lists
-action sets as groups of commands.  A checkmark by a command group means that the menu and tool bar actions are visible in the workbench. 
-You can select the name of the command group to see the list of available menu and toolbar actions to the right. The figure below shows the
-list of command groups available in our workbench.&nbsp; (Your workbench may look different depending on which plug-ins you have
-installed and which perspective is active.)</P>
-
-<img src="images/actionsets.png" alt="Customize Perspective dialog with action set list" border="0">
-
-
-<P >
-The readme tool uses an action set to contribute several different &quot;Open Readme
-Browser&quot; actions to the workbench menu.&nbsp; (We contributed a similar
-action to the popup menu of the resource navigator.)&nbsp; The markup follows:</P>
-<pre>
-&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;org_eclipse_ui_examples_readmetool_actionSet&quot;
-		   label=&quot;%ActionSet.name&quot;
-		   visible=&quot;true&quot;&gt;
-		   &lt;menu id=&quot;org_eclipse_ui_examples_readmetool&quot;
-			   label=&quot;%ActionSet.menu&quot;
-			   path=&quot;window/additions&quot;&gt; 
-			   &lt;separator name=&quot;slot1&quot;/&gt;
-			   &lt;separator name=&quot;slot2&quot;/&gt;
-			   &lt;separator name=&quot;slot3&quot;/&gt;
-		   &lt;/menu&gt;
-		   &lt;action id=&quot;org.eclipse.ui.examples.readmetool.readmeAction&quot;
-			   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-			   toolbarPath=&quot;readme&quot;
-			   label=&quot;%ReadmeAction.label&quot;
-			   tooltip=&quot;%ReadmeAction.tooltip&quot;
-			   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-			   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-			   class=&quot;org.eclipse.ui.examples.readmetool.<b>WindowActionDelegate</b>&quot;
-			   definitionId=&quot;org.eclipse.ui.examples.readmetool.readmeAction&quot;
-			   enablesFor=&quot;1&quot;&gt;
-			   &lt;selection class=&quot;org.eclipse.core.resources.IFile&quot;
-					name=&quot;*.readme&quot;&gt;
-			   &lt;/selection&gt;
-		   &lt;/action&gt;
-		   ...
-	   &lt;/actionSet&gt;
-   &lt;/extension&gt;</pre>
-<P >
-Wow, there's a lot going on here!&nbsp; Let's take it a step at a time, looking
-only at the first action for now.&nbsp;&nbsp;</P>
-<P >
-First, the action set is declared and given a <b>label</b>.&nbsp;
-The label &quot;ReadMe Actions&quot; (defined for <b> %ActionSet.name</b>  key in the plug-in's
-properties file) is used to display the action set in the
-dialog shown above.&nbsp; Since we set <b> visible</b> to true, the workbench will initially have the action set
-checked in the action set list and the actions will be visible.</P>
-<P >
-The rest of the action set declaration is concerned with defining the menu in
-which the actions appears and the actions themselves.</P>
-<P >
-We define a menu whose <b>label</b> appears in the workbench menus.&nbsp; The menu's <b>path</b>
-tells the workbench to place the new menu in the <b>additions</b>
-slot of the <b>window</b> menu.&nbsp; (For a discussion
-of menu paths and slots, see <a HREF="workbench_menupaths.htm" CLASS="XRef"> Menu and toolbar paths</a>.)&nbsp;
-We also define some slots in our new menu so that actions can be inserted at specific locations in our menu.</P>
-<P >
-This markup alone is enough to cause the menu to appear in the workbench <b>Window</b>
-menu.</P>
-<P >
-<img src="images/readmeactionset.png" alt="Workbench Window menu with Readme File Editor entry" border="0" ></P>
-<P >
-Next, we define the actions themselves.&nbsp;&nbsp;</P>
-<P >
-The action definition (<b>id</b>,
-<b>label</b>, <b>icon</b>, <b>class</b>) is
-similar to the other actions we've seen in views, editors, and popups.&nbsp;
-We'll focus here on what's different:&nbsp; where does the action go?&nbsp; We
-use&nbsp; <b>menubarPath</b> and <b>toolbarPath</b>
-to indicate its location.&nbsp; First, we define the <b>menubarPath</b> to add the
-action to a slot in the menu
-that we just defined (&nbsp;<b>&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;</b>).</P>
-<P >
-<img src="images/readmeactionsetmenu.png" alt="Readme File Editor menu with menu items" border="0" ></P>
-<P >
-Then, we define a new <b> toolbarPath</b> to insert our actions in the workbench tool
-bar.&nbsp; Since we've defined a new tool path, <b>&quot;readme&quot;</b>, the workbench will decide where it goes
-relative to other plug-in's toolbar contributions.</P>
-<P >
-<img src="images/readmeactionsettoolbar.png" alt="Workbench tool bar with readme action" border="0" ></P>
-<P >
-What happens when the action is selected by the user?&nbsp; The action is
-implemented by the class specified in the <b>class</b>
-attribute.&nbsp; The action <b> class</b> must implement
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowActionDelegate.html"> IWorkbenchWindowActionDelegate</a></b>,
-or
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowPulldownDelegate.html"> IWorkbenchWindowPulldownDelegate</a></b> 
-if the action will be shown as a pull-down tool item in the tool bar.&nbsp; Since we are not
-creating a pull-down tool item, we provide <b>WindowActionDelegate</b>.&nbsp;
-This class is similar to <b>ObjectActionDelegate</b>.&nbsp;
-It launches the readme sections dialog when the user chooses the action.&nbsp; (We'll
-discuss the sections dialog in <a href="dialogs_applications.htm">Application
-dialogs</a>.)</P>
-
-
-<P >
-The action also supplies enabling conditions for its menu item and tool bar
-item.&nbsp; The menu and tool bar items will only be enabled when a single (<b>enablesFor=&quot;1&quot;</b>)
-readme file (<b>selectionClass =&quot;org.eclipse.core.resources.IFile&quot;
-name=&quot;*.readme&quot;</b>) is selected.&nbsp; This action's menu and toolbar
-item appear and are enabled by virtue of the markup
-in the <b>plugin.xml</b> file.&nbsp; None of the
-plug-in code will execute until the user chooses the action and the workbench
-runs the action <b>class</b>.</P>
-
-<p>The <b>definitionId</b> allows the action to be linked to a command created by the
-<b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></b>
-extension, which can be used for keybindings.  All <b>actions</b> in an <b>actionSets</b>
-should be linked to a command, either existing commands provided by the workbench or
-commands created by the contributing plugin. 
-See <a href="wrkAdv_keyBindings_actionDef.htm" class="XRef">Associating actions to commands</a>
-and <a href="workbench_cmd_commands.htm" class="XRef">org.eclipse.ui.commands</a> for
-defining commands.</p>
-
-<P >
-We'll look at the other two actions later in the context of <a href="wrkAdv_retarget_contribute.htm">retargetable
-actions</a>.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm
deleted file mode 100644
index 616daf4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editorActions.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.editorActions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.editorActions</H3>
-
-<P >
-We've just seen how editors
-can contribute their own actions to the workbench menus and tool bar when they
-become active.&nbsp; The <b><a href="../reference/extension-points/org_eclipse_ui_editorActions.html">org.eclipse.ui.editorActions</a></b> extension
-point allows a plug-in to add
-to the workbench menus and tool bar when another plug-in's editor becomes active.</P>
-<P >
-In the readme example, the plug-in uses the <b>editorActions</b>
-extension point to contribute additional actions to the menu contributed by the
-readme editor. The definition in our
-<b> plugin.xml</b> should look pretty familiar by now.</P>
-<pre>
-&lt;extension
-    point = &quot;org.eclipse.ui.editorActions&quot;&gt;
-      &lt;editorContribution 
-         id=&quot;org.eclipse.ui.examples.readmetool.ec1&quot; 
-         targetID=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;&gt;        
-	   &lt;action id=&quot;org.eclipse.ui.examples.readmetool.ea1&quot; 
-              label=&quot;%Editors.Action.label&quot; 
-              toolbarPath=&quot;ReadmeEditor&quot; 
-              icon=&quot;icons/obj16/editor.png&quot; 
-              tooltip=&quot;%Editors.Action.tooltip&quot; 
-              class=&quot;org.eclipse.ui.examples.readmetool.EditorActionDelegate&quot;
-              definitionId=&quot;org.eclipse.ui.examples.readmetool.ea1&quot;
-              /&gt; 
-      &lt;/editorContribution&gt;
- &lt;/extension&gt;</pre>
-<P >Similar to a view action, the extension must specify the <b> targetID</b> of the
-editor to which it is contributing actions.&nbsp; The action itself is very
-similar to a view action (<b>id</b>, <b>label</b>, <b>icon</b>, <b>toolbarPath</b>,
-...), except that the specified class
-must implement <b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>
-and a <b>definitionId</b> can be specified to link this action to a Command specified 
-by the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></b>
-extension, which is important for keybinding.  
-See <a href="wrkAdv_keyBindings_actionDef.htm" class="XRef">Associating actions to commands</a>
-and <a href="workbench_cmd_commands.htm" class="XRef">org.eclipse.ui.commands</a> for
-defining commands.</P>
-<P >Note that a menu bar path is not specified in this markup.&nbsp; Therefore,
-the action will appear in the workbench tool bar when the editor is active,
-but not in the workbench menu bar.&nbsp; (See <a HREF="workbench_menupaths.htm" CLASS="XRef"> Menu and toolbar paths</a> for a discussion of toolbar and menu paths.)</P>
-<P >Sure enough, when the editor is active, we see our editor action on the tool
-bar next to the actions that were contributed by the editor itself.</P>
-<P ><img src="images/editorAction.png" alt="Editor action appears next to original editor contributions in workbench toolbar" border="0" ></P>
-<P >
-The readme tool supplies <b> EditorActionDelegate</b>
-to implement the action.&nbsp; This class is very similar to the view action delegate
-we saw earlier.</P>
-
-<pre>
-public void run(IAction action) {
-	MessageDialog.openInformation(editor.getSite().getShell(),
-		MessageUtil.getString(&quot;Readme_Editor&quot;),  
-		MessageUtil.getString(&quot;Editor_Action_executed&quot;)); 
-}</pre>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm
deleted file mode 100644
index fe65f1f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_editors.htm
+++ /dev/null

@@ -1,171 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.editors</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.editors</H3>
-
-<P >
-An editor is a workbench part that allows a user to edit an object (often a
-file). Editors operate in a manner similar to file system editing tools, except that they are tightly integrated into the platform workbench UI. An editor is always associated with an input object
-(<a href="../reference/api/org/eclipse/ui/IEditorInput.html"><b>IEditorInput</b></a>). You can think of the input object as
-the document or file that is being edited. Changes made in an editor are not
-committed until the user saves them. </P>
-<P >
-Only one editor can be open for any particular editor input in a workbench page. For example, if the user is editing
-<b> readme.txt</b> in the workbench, opening it again
-in the same perspective will activate the same editor. (You can open another
-editor on the same file from a different workbench window or perspective).&nbsp;
-Unlike views, however, the same editor type, such as a text editor, may be open
-many times
-within one workbench page for different inputs.</P>
-<P >
-The workbench extension point <b><a href="../reference/extension-points/org_eclipse_ui_editors.html">org.eclipse.ui.editors</a></b>
-is used by plug-ins to add editors to the workbench. Plug-ins that contribute an editor must register the editor
-extension in their <b>plugin.xml </b> file, along with configuration information
-for the editor. Some
-of the editor information, such as the implementation <b> class</b> and the
-<b> name</b> and the <b>icon</b>  to be used in the workbench menus and
-labels, is similar to the view information. In addition, editor extensions specify the file extensions or file name patterns of the file types that the editor understands. Editors can also define a
-<b> contributorClass</b>, which is a class that adds actions to workbench menus and tool bars when the editor is active.</P>
-<P >
-The interface for editors is defined in <b><a href="../reference/api/org/eclipse/ui/IEditorPart.html">IEditorPart</a></b>, but plug-ins
-can choose to extend the
-<b><a href="../reference/api/org/eclipse/ui/part/EditorPart.html"> EditorPart</a></b> class rather than implement an
-<b><a href="../reference/api/org/eclipse/ui/IEditorPart.html">IEditorPart</a></b>
-from scratch.</P>
-<blockquote><i>
-Note:&nbsp; An editor extension can also be configured to launch an external program
-or to call pre-existing java code. In this discussion, we are focusing on those editors that are actually tightly integrated with the workbench and
-are implemented using
-<b><a href="../reference/api/org/eclipse/ui/IEditorPart.html">IEditorPart</a></b>.</i></blockquote> 
-<P >
-The readme tool provides a custom editor primarily for the purpose of contributing its own content outliner page to the
-workbench outline view.&nbsp;&nbsp;</P>
-<P >
- The configuration for the editor extension is defined as follows.</P>
-<pre>
-&lt;extension
-    point = &quot;org.eclipse.ui.editors&quot;&gt;
-	&lt;editor
-  	   id = &quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-  	   name=&quot;%Editors.ReadmeEditor&quot;
-      	   icon=&quot;icons/obj16/editor.png&quot;
-      	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-	   extensions=&quot;readme&quot;
-           contributorClass=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditorActionBarContributor&quot;&gt;
-	&lt;/editor&gt;
-&lt;/extension&gt;</pre>
-<P >
-We see the familiar configuration markup for <b>id</b>,
-<b>name</b>,
-<b>icon</b>, and <b>class</b>.&nbsp;&nbsp; The <b>extensions</b> attribute
-describes the file types that the editor understands.&nbsp; (You could also
-specify <b>filenames</b> if you need to be more specific.)&nbsp; The <b>class</b>
-implements the editor, and the <b>contributorClass</b> is responsible for
-providing editor-related actions.  The contributor is not normally used to
-contribute commands or handlers to the workbench menu or toolbar, that's done
-via <a href="workbench_cmd_menus.htm" class="XRef">org.eclipse.ui.menus</a>.
-Let's look at the contributor that's used for actions in more
-detail.</P>
-
-<H4>
-Editor action contributors</H4>
-<P >
-The contributor class adds editor-related actions to the workbench menu and toolbar. It must implement the
-<b><a href="../reference/api/org/eclipse/ui/IEditorActionBarContributor.html"> IEditorActionBarContributor</a></b> interface. The contributor is
-separate from the editor itself since any given workbench page can have multiple editors of the same type.
-A single contributor is shared by all the editors of a specific type, rather than
-having each instance of an editor create actions and images.&nbsp;</P>
-<P >
-In <b>ReadmeEditorActionBarContributor</b>, we contribute three actions,
-&quot;Editor Action1,&quot; &quot;Editor Action2,&quot; and &quot;Editor Action3.&quot;&nbsp;&nbsp;
-These are set up in the constructor.</P>
-<pre>
-   public ReadmeEditorActionBarContributor() {
-      	...
-	action1 = new EditorAction(MessageUtil.getString(&quot;Editor_Action1&quot;)); 
-	action1.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action1&quot;)); 
-	action1.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_DISABLE);
-	action1.setImageDescriptor(ReadmeImages.EDITOR_ACTION1_IMAGE_ENABLE);
-	...	
-	action2 = new RetargetAction(IReadmeConstants.RETARGET2, MessageUtil.getString(&quot;Editor_Action2&quot;)); 
-	action2.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action2&quot;)); 
-	action2.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_DISABLE);
-	action2.setImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_ENABLE);
-	...
-	action3 = new LabelRetargetAction(IReadmeConstants.LABELRETARGET3, MessageUtil.getString(&quot;Editor_Action3&quot;));
-	action3.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_DISABLE);
-	action3.setImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_ENABLE);
-	...   
-   }
-</pre>
-<P >
-The names and icons for the actions are set up in the code rather than in the <b>plugin.xml</b>.&nbsp;
-(We'll ignore the differences in the action classes for now until we look at <a href="wrkAdv_retarget_contribute.htm">retargetable
-actions</a>.)&nbsp;&nbsp;</P>
-<P >Note how similar the action information is to the
-<b> viewActions</b> information we saw in the markup
-for the view action.&nbsp; The actions are set up in code since we have to
-manage the sharing of the actions among different instances of the same editor.&nbsp;
-When the actions are created in the constructor, they are independent of any
-particular instance of the editor.</P>
-<P >
- When an editor becomes active and it has actions that need to be installed in the workbench menus and tool bar, the <b>setActiveEditor
-</b>message is sent to the contributor.&nbsp; The contributor connects the editor actions to a specific editor.&nbsp;&nbsp;</P>
-<pre>
-   public void setActiveEditor(IEditorPart editor) {
-      ...
-      action1.setActiveEditor(editor);
-      ...
-   }
-</pre>
-<P >
-As you can see, the actions show up in the workbench menu and tool bar when a readme editor is active. </P>
-
-<img src="images/editormenu.png" alt="Readme entry in workbench menu bar with three editor actions" border="0" >
-
-
-
-<p><img src="images/editortoolbar.png" alt="Workbench toolbar with three readme actions" border="0" ></p>
-<P >
-These menu and tool bar items are only shown when the editor is active. The location for the menu and tool bar items can be specified as described in
-<a HREF="workbench_menupaths.htm" CLASS="XRef">Menu and toolbar paths</a>.</P>
-
-
-
-<H4>
-Editors and content outliners
-</h4>
-<P >
-The readme editor itself, <b>ReadmeEditor</b>, is not very complicated. It extends the
-<b><a href="../reference/api/org/eclipse/ui/editors/text/TextEditor.html"> TextEditor</a></b> class so that it can contribute a customized content outliner page
-to the outline view when a readme file is being edited. It does not change any behavior inside the text editor.</P>
-<p><img src="images/readmeoutliner.png" alt="" border="0"></p>
-<P >
-Editors often have corresponding content outliners that provide a structured
-view of the editor's contents and assist the user in navigating through the
-contents of the editor.&nbsp; See <a href="editors_workbench_outliner.htm">Content
-outliners</a> for more detail. </P>
-
-
-<P >
-We'll look at the implementation of text editors in <a href="editors_jface.htm">Text
-editors and platform text</a>. </P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm
deleted file mode 100644
index 5b4ad1d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_popupMenus.htm
+++ /dev/null

@@ -1,137 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.popupMenus</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.popupMenus</H3>
-
-<P >
-The <b><a href="../reference/extension-points/org_eclipse_ui_popupMenus.html"> org.eclipse.ui.popupMenus</a></b> extension
-point allows a plug-in to contribute to the popup menus of other
-views and editors.</P>
-<P >
-You can contribute an action to a specific popup menu by its id (<b>viewerContribution</b>), or
-by associating it with a particular object type (<b>objectContribution</b>).&nbsp;</P>
-<ul>
-  <li>An <b>objectContribution</b> will cause the menu
-    item to appear in popup menus for views or editors where objects of
-    the specified type are selected.</li>
-  <li>A <b>viewerContribution</b> will cause the menu
-    item to appear in the popup menu of a view or editor specified by id in the
-    markup.&nbsp;&nbsp;</li>
-</ul>
-<p>
-You can add commands to context menus for a similar result, see the 
-<b>Contributing to popup menus</b> section in 
-<a href="workbench_cmd_menus.htm" class="XRef">org.eclipse.ui.menus</a>.
-</p>
-<P >
-The readme tool defines both. Let's look at the object contribution
-first.&nbsp;&nbsp;</P>
-<pre>
-&lt;extension point = &quot;org.eclipse.ui.popupMenus&quot;&gt;
-     &lt;objectContribution
-        id=&quot;org.eclipse.ui.examples.readmetool&quot;
-        objectClass=&quot;org.eclipse.core.resources.IFile&quot;
-	    nameFilter=&quot;*.readme&quot;&gt;
-	    &lt;action id=&quot;org.eclipse.ui.examples.readmetool.action1&quot;
-	       label=&quot;%PopupMenus.action&quot;
-	       icon=&quot;icons/ctool16/openbrwsr.png&quot;
-	       menubarPath=&quot;additions&quot;
-	       helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-	       class=&quot;org.eclipse.ui.examples.readmetool.PopupMenuActionDelegate&quot;	
-           definitionId=&quot;org.eclipse.ui.examples.readmetool.action1&quot;
-	       enablesFor=&quot;1&quot;&gt;
-	    &lt;/action&gt;
-	 &lt;/objectContribution&gt;
- 	 ...
-</pre><h4>
-   Object contribution
-</h4>
-<P >
-The action &quot;Show Readme Action&quot; is contributed for the object class <a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>. This means that any view containing
-<a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-objects will show the contribution if <a href="../reference/api/org/eclipse/core/resources/IFile.html"><b>IFile</b></a>
-objects are selected. We see that the selection criteria is restricted further with a name filter
-(<b>nameFilter=&quot;*.readme&quot;</b>) and for single selections (<b>enablesFor=&quot;1&quot;</b>). As we've discussed before, the registration of this menu does not run any code from our plug-in until the menu item is actually selected. </P>
-<P >
-When the menu item is selected, the workbench will run the specified class.&nbsp;
-Since the popup is declared as an <b>objectContribution</b>,
-the supplied class must implement <b><a href="../reference/api/org/eclipse/ui/IObjectActionDelegate.html">IObjectActionDelegate</a></b>.&nbsp;</P>
-<P >
-The action is implemented in <b>PopupMenuActionDelegate</b>.&nbsp;&nbsp;</P>
-<pre>
-   public void run(IAction action) {
-      MessageDialog.openInformation(
-         this.part.getSite().getShell(),
-         &quot;Readme Example&quot;,
-         &quot;Popup Menu Action executed&quot;);
-   }
-</pre>
-<P >
-We can see the popup menu contribution when we select a readme file from the resource navigator.</P>
-
-<img src="images/readmepopupmenu.png" alt="" border="0">
-<h4>Viewer contribution</h4>
-<p>
-A viewer contribution is used to contribute to a specific view or editor's popup menu
-by using its id.
-Here is the readme tool's viewer contribution:</p>
-<pre>      ...
-      &lt;viewerContribution
-        id=&quot;org.eclipse.ui.examples.readmetool2&quot;
-        targetID=&quot;org.eclipse.ui.examples.readmetool.outline&quot;&gt;
-	    &lt;action id=&quot;org.eclipse.ui.examples.readmetool.action1&quot;
-	       label=&quot;%PopupMenus.action&quot;
-	       icon=&quot;icons/ctool16/openbrwsr.png&quot;
-	       menubarPath=&quot;additions&quot;
-	       helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-           definitionId=&quot;org.eclipse.ui.examples.readmetool.action1&quot;
-	       class=&quot;org.eclipse.ui.examples.readmetool.ViewActionDelegate&quot;&gt;	
-	    &lt;/action&gt;
-       &lt;/viewerContribution&gt;
-&lt;/extension&gt;</pre>
-<blockquote><i>
-Note:&nbsp; The name <b> viewerContribution</b> is somewhat misleading, as it does not relate to JFace viewers. A better name would
-be <b>popupMenuContribution</b>.</i></blockquote>
-<P >
-When the extension is a <b>viewerContribution</b>, the
-supplied class must implement the
-<b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html"> IEditorActionDelegate</a></b> or
-<b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html"> IViewActionDelegate</a></b> interface, depending on whether the
-action is contributed to an editor's or view's popup menu.&nbsp;</P>
-
-
-<P >
-The <b>targetID</b> specifies the view whose popup menu will be altered.&nbsp; In this
-case, we are adding an action to one of the readme tool views, the
-outliner.&nbsp; The action itself is similar to others that we've seen.&nbsp; We specify the <b>id</b>,
-<b>definitionId</b>, <b>label</b>, and <b>icon</b> of the action, and
-the <b>path</b> within the popup for our contribution.&nbsp; The action will be
-shown only in the readme outline view's popup menu.</P>
-
-
-<P >
-<img src="images/readmeoutlinerpopup.png" alt="" border="0"></P>
-
-
- The interfaces required to contribute a <b>viewerContribution</b>
-to the <b> popupMenus</b> extension
-point are the same as those required by the <b> viewActions</b> and <b> editorActions</b> extension points. If you want to contribute the same action to the popup menu and the local menu of a view or editor, you can use the same class for both extensions.
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm
deleted file mode 100644
index facee8b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_viewActions.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>org.eclipse.ui.viewActions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.viewActions</H3>
-
-<P >
-It is common for plug-ins to contribute behavior to views that already exist in the workbench. This is done through the
-<b><a href="../reference/extension-points/org_eclipse_ui_viewActions.html"> org.eclipse.ui.viewActions</a></b> 
-extension point. This extension point allows plug-ins to contribute menu items, submenus and tool bar entries to an
-existing view's local
-pull-down menu and local tool bar. </P>
-<p>
-Contributing menu items to views is also done using the 
-<b><a href="../reference/extension-points/org_eclipse_ui_menus.html">org.eclipse.ui.menus</a></b>
-extension point.  This allows command targeted at a view to be contributed to
-an existing view's local pull-down menu and local tool bar, as in the <b>Contribution location</b> section
-covering the Info View of <a href="workbench_cmd_menus.htm" class="XRef">org.eclipse.ui.menus</a>.
-</p>
-<P >
-You may have noticed an item in the project explorer's local tool bar that becomes
-enabled whenever a readme file is selected. This item also appears in the
-project explorer's local
-pull-down menu. These actions appear because the readme tool plug-in contributes
-them using the
-<b> viewActions</b> extension.</P>
-
-<img src="images/readmeviewaction.png" alt="" border="0">
-<P >
-The relevant <b> plugin.xml</b> contribution is below.</P>
-<pre>
-&lt;extension
-    point = &quot;org.eclipse.ui.viewActions&quot;&gt;
-      &lt;viewContribution 
-         id=&quot;org.eclipse.ui.examples.readmetool.vc1&quot; 
-         targetID=&quot;org.eclipse.ui.navigator.ProjectExplorer&quot;&gt;        
-	   &lt;action id=&quot;org.eclipse.ui.examples.readmetool.va1&quot; 
-              label=&quot;%PopupMenu.ResourceNav.label&quot; 
-	      menubarPath=&quot;additions&quot;
-              toolbarPath=&quot;additions&quot; 
-              icon=&quot;icons/obj16/editor.png&quot; 
-              tooltip=&quot;%PopupMenu.ResourceNav.tooltip&quot; 
-   	      helpContextId=&quot;org.eclipse.ui.examples.readmetool.view_action_context&quot;
-              class=&quot;org.eclipse.ui.examples.readmetool.ViewActionDelegate&quot; 
-              enablesFor=&quot;1&quot;&gt; 
-		&lt;selection class=&quot;org.eclipse.core.resources.IFile&quot; name=&quot;*.readme&quot;/&gt; 
-	   &lt;/action&gt;
-      &lt;/viewContribution&gt;
- &lt;/extension&gt;
-</pre>
-<P >
-A view contribution with a unique id is specified. The view to which we are adding
-the action is specified in the
-<b> targetID</b>. We are contributing to the Project
-Explorer's menu.&nbsp; We specify the label and the menu bar and
-tool bar locations for the new action.&nbsp; (For a complete discussion of menu and toolbar locations, see
-<a HREF="workbench_menupaths.htm" CLASS="XRef"> Menu and toolbar paths</a>). </P>
-<P >
-We also specify the conditions under which the action should be enabled. You can see that this action will be enabled when there is one selection
-(<b>enablesFor=&quot;1&quot;</b>) of type
-<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a>
-(class=&quot;org.eclipse.core.resources.IFile&quot;)</b>, whose name has
-&quot;<b>.readme</b>&quot; in the file extension (<b>name=&quot;*.readme&quot;</b>). Sure enough, that's exactly what happens when you click around in the Project Explorer.&nbsp;&nbsp;</P>
-<P >
-The information in the <b> plugin.xml</b> is all that's needed to add items to menus and tool
-bars since plug-in code will only run when the action is actually selected from the menu or toolbar.
-To provide the action behavior, the implementation class specified in the
-<b> plugin.xml</b> must implement the <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html"> IViewActionDelegate</a></b> interface. </P>
-<P >
-In this example, the readme plug-in supplies <b> ViewActionDelegate</b> to implement the action. If you browse this class you will see that it includes methods for
-remembering its view, handling selection changes, and invoking its action.&nbsp;
-When invoked the action itself simply launches a dialog that announces it was executed.</P>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	MessageDialog.openInformation(view.getSite().getShell(),
-		MessageUtil.getString(&quot;Readme_Editor&quot;),  
-		MessageUtil.getString(&quot;View_Action_executed&quot;)); 
-}</pre>
-<P >
-Although this action is simple, we can imagine how using selections and more
-functional dialogs could make this action do something more interesting.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm
deleted file mode 100644
index 5c15592..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_basicext_views.htm
+++ /dev/null

@@ -1,157 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>org.eclipse.ui.views</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H3>
-org.eclipse.ui.views</H3>
-
-<P >A view is a workbench part that can navigate a hierarchy of information or display properties for an
-object.&nbsp; Only one instance of any given view
-is open in a workbench page.&nbsp; When the user makes selections or other changes in a view,
-those changes are immediately reflected in the workbench. Views are often provided to support a corresponding editor.&nbsp;
-For example, an <b>outline</b> view shows a structured view of the information
-in an editor.&nbsp; A <b>properties</b> view shows the properties of an object
-that is currently being edited.</P>
-
-<P >
-The extension point <b><a href="../reference/extension-points/org_eclipse_ui_views.html">org.eclipse.ui.views</a></b>
-allows plug-ins to add views to the workbench. Plug-ins that contribute a view must register the view in their
-<b> plugin.xml </b> file and provide&nbsp; configuration information about the view, such as its implementation class, the category (or group) of views to which it belongs, and the name and icon that should be used to describe the view in menus and labels.</P>
-<P >
-The interface for views is defined in <b><a href="../reference/api/org/eclipse/ui/IViewPart.html">IViewPart</a></b>, but plug-ins
-can choose to extend the
-<b><a href="../reference/api/org/eclipse/ui/part/ViewPart.html"> ViewPart</a></b> class rather than implement an
-<b><a href="../reference/api/org/eclipse/ui/IViewPart.html"> IViewPart</a></b> from scratch.</P>
-<P >
-We implemented a minimal view extension in the hello world example. Now we'll look at one that is aware of other workbench views and responds to user navigation and selection
-changes in the workbench. First,
-let's take a look at the declaration of the extension in the <b>plugin.xml</b>.</P>
-<pre>&lt;extension 
-   point=&quot;org.eclipse.ui.views&quot;&gt;
-	&lt;category 
-	   id=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   name=&quot;%Views.category&quot;&gt;
-	&lt;/category&gt;
-	&lt;view
- 	   id=&quot;org.eclipse.ui.examples.readmetool.views.SectionsView&quot;
-	   name=&quot;%Views.ReadmeSections&quot;
-	   icon=&quot;icons/view16/sections.png&quot;
-	   category=&quot;org.eclipse.ui.examples.readmetool&quot;
-	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeSectionsView&quot;&gt;
-	&lt;/view&gt;
-&lt;/extension&gt;
-</pre>
-<P >
-This should look pretty familiar. We see that a new view, <b>ReadmeSectionsView</b>, is contributed to the workbench. The
-<b>view id</b>, <b>name</b>,
-and
-<b> category</b> are specified as we've seen before. An <b> icon</b> is also provided
-for the view, using a path relative to the plug-in's installation directory. </P>
-<P >
-Let's look at the <b>ReadmeSectionsView</b>. You can show any view in the
-workbench by choosing
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other...</b></a>
-
-and selecting the view from the <b>Show View</b> list.</P>
-<P >
-When we show the <b>ReadmeSectionsView</b>, a view with a list in it pops up.
-The list is empty unless we click on a file with an extension of <b>.readme</b>, in which case
-the list is populated with sections from the readme file.</P>
-
-<img src="images/readmeview.png" alt="" border="0">
-<P >
-How does the plug-in recognize the readme file and how did it know about selection changes? If we can track down
-the answers to these questions, we are well on our way to understanding how to build integrated workbench plug-ins.</P>
-<P >
-We'll start with the familiar <b>createPartControl</b>
-method.&nbsp; As we saw in the Hello World example, this is where the widgets
-that represent a view are created.&nbsp; We'll ignore some of the code to get
-started.</P>
-<pre>
-   public void createPartControl(Composite parent) {
-      viewer = new ListViewer(parent);
-      ...
-      // add myself as a global selection listener
-      getSite().getPage().addSelectionListener(this);
-
-      // prime the selection
-      selectionChanged(null, getSite().getPage().getSelection());
-   }
-</pre>
-<P >
-The view creates and stores a ListViewer and registers itself as a selection listener
-on its page. It obtains the page from an
-<b><a href="../reference/api/org/eclipse/ui/IViewSite.html">IViewSite</a></b>, which contains information about the view's context, such as its workbench window,
-its containing page, its local services, and its plug-in. When we are notified of a selection change, what happens?&nbsp;
-The following code is executed:</P>
-<pre>
-   public void selectionChanged(IWorkbenchPart part, ISelection sel) {
-      //if the selection is a readme file, get its sections.
-      AdaptableList input = ReadmeModelFactory.getInstance().getSections(sel);
-      viewer.setInput(input);
-   }
-</pre>
-<P >
-It looks like the <b> ReadmeModelFactory</b> class is responsible for turning the selection into readme
-sections and these sections are input for
-the viewer that we created in the <b>createPartControl</b>
-method.</P>
-<P >
-But how did the viewer populate its list widgets?&nbsp; For now, let's assume that once the viewer was told its input element, it knew how to populate
-its list widget with the information - it is a ListViewer, after all.&nbsp; If you must know right now what this viewer is all about, go to <a HREF="jface_viewers.htm" CLASS="XRef">Viewers</a>.&nbsp;</P>
-<P >
-We still do not know how readme files are detected or where the file's section
-information comes from.&nbsp; A quick look at the
-<b> ReadmeModelFactory</b> sheds some light.</P>
-<pre>
-   public AdaptableList getSections(ISelection sel) {
-      // If sel is not a structured selection just return.
-      if (!(sel instanceof IStructuredSelection))
-         return null;
-      IStructuredSelection structured = (IStructuredSelection)sel;
-
-      //if the selection is a readme file, get its sections.
-      Object object = structured.getFirstElement();
-      if (object instanceof IFile) {
-         IFile file = (IFile) object;
-         String extension = file.getFileExtension();
-         if (extension != null &amp;&amp; extension.equals(IReadmeConstants.EXTENSION)) {
-            return getSections(file);
-         }
-      }
-
-      //the selected object is not a readme file
-      return null;
-   }
-</pre>
-<P >We check the selection to see if it is a structured (multiple)
-selection.&nbsp; (The concept of a structured selection comes from JFace <a href="jface_viewers.htm">viewers</a>.)&nbsp;
-For the first object in the selection, we check to see whether it is a file (<b><a href="../reference/api/org/eclipse/core/resources/IFile.html">IFile</a></b>)
-resource.&nbsp; If it is, we check its extension to see if it matches the &quot;<b>.readme</b>&quot;
-extension.&nbsp; Once we know we have a readme file, we can use other methods to
-parse the sections.&nbsp;&nbsp; You can browse the rest of <b>ReadmeModelFactory</b>,&nbsp;
-<b>MarkElement</b>, and <b> DefaultSectionsParser</b> for the
-details about the file parsing. </P>
-<P >
-We've covered a lot of common workbench concepts by studying this extension. Now we'll move on to some other workbench extensions and examine how your plug-in can further contribute to the workbench UI. </P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd.htm
deleted file mode 100755
index d067dbe..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Basic workbench extension points
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Basic workbench extension points using commands</H2>
-<p>
-Commands and handlers have been provided by the workbench in one form
-or another since 3.0.  In 3.2 the commands, handlers, and keybindings portion
-of the Command Framework became mature.  In 3.3 the menu contributions portion
-of the Command Framework became available.
-</p>
-<p>
-We are going to take a look at how commands, handlers, menu contributions,
-and keybindings can be used to contribute behaviour to the workbench,
-to views, and to editors.  We'll use the Info example from the
-contributions plugin.  It provides a view that lists people and an
-editor for updating their names.  Much of the contribution of editors
-and views has already been covered in the readme example in 
-<a href="workbench_basicext.htm" 
-   class="XRef">Basic workbench extension points using actions</a>.
-</p>
-
-<img src="images/contributions_window.png">
-<p>
-You can show any view in the workbench by choosing
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other...</b></a>
-and selecting the view from the <b>Show View</b> list.  Use this to select the Info View from
-the View Contributions category.
-</p>
-<p>
-The Info example is located in the <b>org.eclipse.ui.examples.contributions</b>
- package. To follow along, you will need to make sure that
-you have installed the platform examples. (See the <a href="../samples/samples.html">Examples
-Guide </a> for more information.)
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm
deleted file mode 100755
index c5e55c3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_bindings.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Key bindings</h3>
-
-
-<p>The association between a command and the key combinations that should
-invoke the command is called a <b>key binding</b> Plug-ins can define key
-bindings along with commands in the
-<a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a>
-extension point. From our InfoView example:</p>
-
-<pre>
-   &lt;extension
-         point=&quot;org.eclipse.ui.bindings&quot;&gt;
-      &lt;key
-            commandId=&quot;org.eclipse.ui.examples.contributions.view.edit&quot;
-            contextId=&quot;org.eclipse.ui.examples.contributions.view.context&quot;
-            sequence=&quot;M1+O&quot;
-            schemeId=&quot;org.eclipse.ui.examples.contributions.scheme&quot;&gt;
-      &lt;/key&gt;
-   &lt;/extension&gt;
-</pre>
-
-
-<p>The <b>sequence</b> attribute for a key binding defines the key
-combination that is used to invoke a command. As long as our InfoView
-context is active, we will try and execute the InfoView edit command when the
-user chooses <b>CTRL+O</b> and the scheme is set to
-<b>org.eclipse.ui.examples.contributions.scheme</b>.  The mapping of <b>M1</b> to <b>CTRL</b>
-is described in the extension point description for
-<a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a>.
-</p>
-<p>
-The <b>contextId</b> indicates what active context this key binding will
-be active in.  More information on defining contexts declaratively and
-activating them programmatically can be found in 
-<a href="workbench_advext_contexts.htm" 
-   class="XRef">Contexts</a>.  In this case, this key binding will be active
-when the <b>org.eclipse.ui.examples.contributions.view.context</b> context
-is active.
-</p>
-<p>
-In our InfoView we have code called from the end of createPartControl(Composite):</p>
-<pre>
-	private static final String VIEW_CONTEXT_ID = &quot;org.eclipse.ui.examples.contributions.view.context&quot;; //$NON-NLS-1$
-	...
-	/**
-	 * Activate a context that this view uses. It will be tied to this view
-	 * activation events and will be removed when the view is disposed.
-	 */
-	private void activateContext() {
-		IContextService contextService = (IContextService) getSite()
-				.getService(IContextService.class);
-		contextService.activateContext(VIEW_CONTEXT_ID);
-	}
-</pre>
-
-<p>
-As mentioned in <a href="workbench_cmd_handlers.htm" 
-   class="XRef">org.eclipse.ui.handlers</a> this context will be active
-only when the InfoView part is active.  It will also be deactivated when
-the InfoView part is disposed.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm
deleted file mode 100755
index 6901d0a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_commands.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Commands
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Commands</h3>
-
-
-<p>A <b>command</b> is the declaration of a behaviour by <b>id</b>.
-Commands are used to declare semantic behaviour so that action implementations defined
-elsewhere by handlers, or linked to the action extension points (see
-<a href="workbench_basicext.htm" 
-   class="XRef">Basic workbench extension points using actions</a>)
-can associate themselves with a particular semantic
-command. The separation of the command from the action
-implementation allows multiple plug-ins to define actions that implement the
-same semantic command. The command is what gets associated with a
-particular key binding.</p>
-
-
-<p>The workbench defines many common commands in its <b>plugin.xml</b>
-file, and plug-ins are encouraged to associate their own actions with these
-commands where it makes sense. In this way, semantically similar
-actions implemented in different plug-ins may share the same key binding.</p>
-
-
-<h4>Defining a command</h4>
-
-
-<p>Commands are defined using the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></b>
-extension point. The following comes from the Info example markup:</p>
-
-
-<pre>
-&lt;extension
-	point=&quot;org.eclipse.ui.commands&quot;&gt;
-	...
-      &lt;command
-            categoryId=&quot;org.eclipse.ui.examples.contributions.commands.category&quot;
-            id=&quot;org.eclipse.ui.examples.contributions.view.count&quot;
-            description=&quot;%contributions.view.count.desc&quot;
-            name=&quot;%contributions.view.count.name&quot;&gt;
-      &lt;/command&gt;
-	...
-</pre>
-
-
-<p>The command definition specifies a <b>name</b>, <b>description</b>, and <b>id</b> for
-the action. It also specifies the id of a category for the command, which is
-used to group commands in the preferences dialog.&nbsp; The categories are also
-defined in the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a>
-</b>
-extension point:</p>
-<pre>
-      ...
-      &lt;category
-            name=&quot;%contributions.commands.category.name&quot;
-            description=&quot;%contributions.commands.category.desc&quot;
-            id=&quot;org.eclipse.ui.examples.contributions.commands.category&quot;&gt;
-      &lt;/category&gt;
-      ...
-</pre>
-
-<p>Note that there is no implementation specified for a
-command. A command only becomes concrete when a plug-in
-associates its handler or action with the command id.  We'll
-talk about the different ways to associate handler implementations
-with commands in the
-<a href="workbench_cmd_handlers.htm" 
-class="XRef">org.eclipse.ui.handlers</a> section.  We'll talk about
-binding key sequences to commands in the <a href="workbench_cmd_bindings.htm" 
-class="XRef">org.eclipse.ui.bindings</a> section.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_expressions.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_expressions.htm
deleted file mode 100755
index 3503a25..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_expressions.htm
+++ /dev/null

@@ -1,968 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006,2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Workbench Core Expressions</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>Workbench Core Expressions</h1>
-
-<p>
-The workbench uses core expressions (See 
-<a href="../reference/extension-points/org_eclipse_core_expressions_definitions.html">org.eclipse.core.expressions.definitions</a>
-for a description) for <code>enabledWhen</code> and <code>activeWhen</code> for handlers, programmatic 
-activation of contexts, and for <code>visibleWhen</code> for menu contributions. Core expressions are also used
-as conditionals for certain property page contribution and object contribution expressions.
-In most cases, the workbench provides the 
-<a href="../reference/api/org/eclipse/core/expressions/IEvaluationContext.html">IEvaluationContext</a>
-that command core expressions are evaluate against.
-</p>
-
-<p>
-The <a href="../reference/api/org/eclipse/ui/services/IEvaluationService.html">IEvaluationService</a>
-provides methods that allow other clients and extension point builders to hook into the workbench
-core expressions.
-</p>
-
-<h2>Using Core Expressions in the Workbench</h2>
-
-<p>
-Core expressions are used declaratively in the plugin.xml files, and programmatically with some of the
-services provided in the workbench.
-</p>
-
-<p>
-Note: Elements from workbench extension points that use core expressions, like <code>enabledWhen</code>,
-take one child core expression element.  
-They do not <b>and</b> their elements together.
-</p>
-
-<h3>Declarative Expression Examples</h3>
-
-<ol>
-<li><a href="#ex1">Basic IStructuredSelection</a></li>
-<li><a href="#ex2">IResources and the Package or Project Explorer</a></li>
-<li><a href="#ex3">Active Contexts</a></li>
-<li><a href="#ex4">Active Views and Editor</a></li>
-<li><a href="#ex5">ActionSets and Contexts</a></li>
-</ol>
-
-<a name="ex1"></a><h4>Basic IStructuredSelection</h4>
-
-<p>
-Most of the tree or table like viewers return an
-<a href="../reference/api/org/eclipse/jface/viewers/IStructuredSelection.html">IStructuredSelection</a>.
-For example, the Project Explorer and Package Explorer. 
-</p>
-
-<p>
-When using the default variable you must treat it as an <code>java.util.Collection</code>.  
-That means using &lt;count&gt; or &lt;iterate&gt;.  The expression below returns true if all of
-the selected items are <code>Person</code>.
-</p>
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;iterate ifEmpty="false"&gt;
-        &lt;instanceof value="org.eclipse.ui.examples.contributions.model.Person"/&gt;
-    &lt;/iterate&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-<p>
-This is equivalent to:
-</p>
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;with variable="selection"&gt;
-        &lt;iterate ifEmpty="false"&gt;
-            &lt;instanceof value="org.eclipse.ui.examples.contributions.model.Person"/&gt;
-        &lt;/iterate&gt;
-    &lt;/with&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-<p>
-The behaviour of <code>iterate</code> is:
-</p>
-
-<ul>
-<li><code>iterate</code> <b>and</b>s the results of evaluating its child expressions for each
-element in the collection, unless you set the <code>operator</code> attribute.</li>
-<li><code>iterate</code> has the same semantics for its children as &lt;and&gt;</li>
-<li><code>iterate</code> with an operator of <b>and</b> returns true if the collection is empty,
-unless you set the <code>ifEmpty</code> attribute.</li>
-</ul>
-
-
-<p>
-If you want to be enabled if only one Person is selected, you can include a <code>count</code>
-element.
-</p>
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;with variable="selection"&gt;
-        &lt;count value="1"/&gt;
-        &lt;iterate ifEmpty="false"&gt;
-            &lt;instanceof value="org.eclipse.ui.examples.contributions.model.Person"/&gt;
-        &lt;/iterate&gt;
-    &lt;/with&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-<p>
-The same expression using the default variable:
-</p>
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;and&gt;
-        &lt;count value="1"/&gt;
-        &lt;iterate ifEmpty="false"&gt;
-            &lt;instanceof value="org.eclipse.ui.examples.contributions.model.Person"/&gt;
-        &lt;/iterate&gt;
-    &lt;/and&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-
-
-<a name="ex2"></a><h4>IResources and the Package or Project Explorer</h4>
-
-<p>
-The Package Explorer is a mixture of
-<a href="../reference/api/org/eclipse/core/resources/IResource.html">org.eclipse.core.resources.IResource</a>,
-<code>org.eclipse.jdt.core.IJavaElement</code> and other classes. If you are trying to find all of 
-the "*.java" files, you would need to:
-</p>
-<ol>
-<li>Iterate through the default variable.</li>
-<li>Adapt the selection elements to your class, in this case 
-<a href="../reference/api/org/eclipse/core/resources/IResource.html">org.eclipse.core.resources.IResource</a>.</li>
-<li>Use one of the org.eclipse.core.resources property testers to test the 
-<a href="../reference/api/org/eclipse/core/resources/IResource.html">org.eclipse.core.resources.IResource</a> property.</li>
-</ol> 
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;with variable="selection"&gt;
-        &lt;iterate ifEmpty="false"&gt;
-            &lt;adapt type="org.eclipse.core.resources.IResource"&gt;
-                &lt;test property="org.eclipse.core.resources.name"
-                         value="*.java"/&gt;
-            &lt;/adapt&gt;
-        &lt;/iterate&gt;
-    &lt;/with&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-<p>
-When working with the current selection and property testers it does not always make sense to use 
-<code>adapt</code>.  In these situations it is a good practice to check that the object under test
-is a valid type for that property tester:
-</p>
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;with variable="selection"&gt;
-        &lt;iterate ifEmpty="false"&gt;
-            &lt;instanceof type="org.eclipse.core.resources.IResource"/&gt;
-            &lt;test property="org.eclipse.core.resources.name"
-                     value="*.java"/&gt;
-        &lt;/iterate&gt;
-    &lt;/with&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-
-<a name="ex3"></a><h4>Active Contexts</h4>
-
-<p>
-If your handler should be enabled when your view or editor activates a context, you can use the
-<code>activeContexts</code> variable.  Contexts are defined in the 
-<a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a>
-extension point and activated programmatically using the 
-<a href="../reference/api/org/eclipse/ui/contexts/IContextService.html">org.eclipse.ui.contexts.IContextService</a>.
-</p>
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;with variable="activeContexts"&gt;
-        &lt;iterate ifEmpty="false" operator="or"&gt;
-            &lt;equals value="org.example.view.context"/&gt;
-        &lt;/iterate&gt;
-    &lt;/with&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-<a name="ex4"></a><h4>Active Views and Editor</h4>
-
-<p>
-For handlers that are to be contributed to a specific view or editor, you can use <code>activeEditorId</code>
-and <code>activePartId</code> in the <code>activeWhen</code> clause.  This is an example for a handler
-that should be active in text editors:
-</p>
-
-<pre>
-&lt;activeWhen&gt;
-    &lt;with variable="activeEditorId"&gt;
-        &lt;equals value="org.eclipse.ui.DefaultTextEditor"/&gt;
-    &lt;/with&gt;
-&lt;/activeWhen&gt;
-</pre>
-
-<p>
-The following clause is for a handler that's active while in the Project Explorer:
-</p>
-
-<pre>
-&lt;activeWhen&gt;
-    &lt;with variable="activePartId"&gt;
-        &lt;equals value="org.eclipse.ui.navigator.ProjectExplorer"/&gt;
-    &lt;/with&gt;
-&lt;/activeWhen&gt;
-</pre>
-
-<a name="ex5"></a><h4>ActionSets and Contexts</h4>
-
-<p>As of 3.3 all <a href="../reference/extension-points/org_eclipse_ui_actionSets.html">org.eclipse.ui.actionSets</a>
-generate a context with a parent of <code>org.eclipse.ui.contexts.actionSet</code>.  Contexts with
-this parent are filtered from the <a class="command-link" 
-href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'> 
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="command link, Keys Preference Page"> <b>General &gt; Keys</b></a> preference page.
-</p>
-
-<p>
-Showing an
-actionSet activates the matching context.  This allows contributed commands to "join" actionSets, like
-the debug launch actionSet. 
-</p>
-
-<pre>
-&lt;enabledWhen&gt;
-    &lt;with variable="activeContexts"&gt;
-        &lt;iterate ifEmpty="false" operator="or"&gt;
-            &lt;equals value="org.eclipse.debug.ui.launchActionSet"/&gt;
-        &lt;/iterate&gt;
-    &lt;/with&gt;
-&lt;/enabledWhen&gt;
-</pre>
-
-<p>
-Note: commands that are enabled or visible with actionSets are not currently displayed in the
-<b>Customize Perspective Dialog</b>.
-</p>
-
-<h3>Variables Provided in the Workbench</h3>
-
-<p>
-The <a href="../reference/api/org/eclipse/ui/services/IEvaluationService.html">IEvaluationService</a>
-provides the global selection as the default variable (in a <code>java.util.Collection</code>) for
-expression evaluation.
-It can either be empty, have one entry (if the 
-<a href="../reference/api/org/eclipse/jface/viewers/ISelection.html">ISelection</a> was something like an
-<a href="../reference/api/org/eclipse/jface/text/ITextSelection.html">ITextSelection</a>), 
-or have the contents of an 
-<a href="../reference/api/org/eclipse/jface/viewers/IStructuredSelection.html">IStructuredSelection</a>. 
-</p>
-
-<p>
-The workbench publishes variables in <a href="../reference/api/org/eclipse/ui/ISources.html">ISources</a>
-that can be used in the &lt;with/&gt; element and can be retrieved from the
-<a href="../reference/api/org/eclipse/core/expressions/IEvaluationContext.html">IEvaluationContext</a>.
-Some of the variables may not be set, depending on the current application context when they are evaluated.
-The following table explains some of the more commonly used ones: 
-</p>
-
-<table border="1">
-<tr>
-<th>Name</th>
-<th>Type</th>
-<th>Description</th>
-
-<th>Since</th>
-</tr>
-
-<tr>
-<td>activeContexts</td>
-<td>A <code>java.util.Collection</code> of <code>java.lang.String</code></td>
-<td>
-<p>This is a collection of the active context IDs as strings.  Most commonly used with &lt;iterate/&gt;, 
-&lt;count/&gt;, and &lt;test/&gt; with a combined <code>org.eclipse.core.expressions.PropertyTester</code>.  
-In <b>3.3</b> action sets are mirrored by contexts whose parent is <code>org.eclipse.ui.actionSet</code>, 
-and the active action sets show up in the list of active contexts.
-
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeShell</td>
-<td><code><a href="../reference/api/org/eclipse/swt/widgets/Shell.html">org.eclipse.swt.widgets.Shell</a></code></td>
-<td>
-<p>The currently active shell.  It can be a dialog or workbench window shell.
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeWorkbenchWindowShell</td>
-<td><code><a href="../reference/api/org/eclipse/swt/widgets/Shell.html">org.eclipse.swt.widgets.Shell</a></code></td>
-<td>
-<p>The active workbench window shell.
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeWorkbenchWindow</td>
-
-<td><code><a href="../reference/api/org/eclipse/ui/IWorkbenchWindow.html">org.eclipse.ui.IWorkbenchWindow</a></code></td>
-<td>
-<p>The active workbench window.
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeWorkbenchWindow.isCoolbarVisible</td>
-<td><code>java.lang.Boolean</code></td>
-<td>
-<p>Reports coolbar visibility for the currently active workbench window.
-
-</p>
-</td>
-<td>3.3</td>
-</tr>
-
-<tr>
-<td>activeWorkbenchWindow.isPerspectiveBarVisible</td>
-<td><code>java.lang.Boolean</code></td>
-<td>
-<p>Reports perspective bar visibility for the currently active workbench window.
-</p>
-</td>
-<td>3.3</td>
-
-</tr>
-
-<tr>
-<td>activeWorkbenchWindow.activePerspective</td>
-<td><code>java.lang.String</code></td>
-<td>
-<p>Reports the name of the current perspective of the active workbench window.
-</p>
-</td>
-<td>3.4</td>
-</tr>
-
-<tr>
-<td>activeEditor</td>
-
-<td><code><a href="../reference/api/org/eclipse/ui/IEditorPart.html">org.eclipse.ui.IEditorPart</a></code></td>
-<td>
-<p>The currently active editor.  This is remembered even if the editor is not the currently active part.
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeEditorId</td>
-<td><code>java.lang.String</code></td>
-<td>
-<p>The ID of the currently active editor.  This can be used for expressions on the editor type.
-
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeEditorInput</td>
-<td><code><a href="../reference/api/org/eclipse/ui/IEditorInput.html">org.eclipse.ui.IEditorInput</a></code></td>
-<td>
-<p>The input of the currently active editor.  This is useful for property testers.
-
-</p>
-</td>
-<td>3.5</td>
-</tr>
-
-
-
-<tr>
-<td>activePart</td>
-<td><code><a href="../reference/api/org/eclipse/ui/IWorkbenchPart.html">org.eclipse.ui.IWorkbenchPart</a></code></td>
-<td>
-<p>The active part, which can be the same as the active editor.
-</p>
-</td>
-<td>3.2</td>
-
-</tr>
-
-<tr>
-<td>activePartId</td>
-<td><code>java.lang.String</code></td>
-<td>
-<p>The ID of the currently active part.
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeSite</td>
-
-<td><code><a href="../reference/api/org/eclipse/ui/IWorkbenchPartSite.html">org.eclipse.ui.IWorkbenchPartSite</a></code></td>
-<td>
-<p>The site of the currently active part.
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>selection</td>
-<td><code><a href="../reference/api/org/eclipse/jface/viewers/ISelection.html">org.eclipse.jface.viewers.ISelection</a></code></td>
-<td>
-<p>The current global selection.  It is often used with &lt;test/&gt; elements with 
-<code>org.eclipse.core.expressions.PropertyTester</code>, in programmatic core expressions, 
-and in <b>3.3</b> with &lt;iterate/&gt; and &lt;count/&gt; elements.
-
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeMenu</td>
-<td>A <code>java.util.Collection</code> of <code>java.lang.String</code></td>
-<td>
-<p>This is the list of IDs of the showing context menu.  Examples are like #TextEditorRuler or 
-a part ID. Most commonly used with &lt;iterate/&gt;, &lt;count/&gt;, and &lt;test/&gt; with 
-a combined <code>org.eclipse.core.expressions.PropertyTester</code>.
-
-</p>
-</td>
-<td>3.2</td>
-</tr>
-
-<tr>
-<td>activeMenuSelection</td>
-<td><code><a href="../reference/api/org/eclipse/jface/viewers/ISelection.html">org.eclipse.jface.viewers.ISelection</a></code></td>
-<td>
-<p>This is a selection that is available while a context menu is showing.  It is the selection 
-from the selection provider used to register the context menu, usually from 
-<a href="../reference/api/org/eclipse/ui/IWorkbenchPartSite.html#registerContextMenu(org.eclipse.jface.action.MenuManager,%20org.eclipse.jface.viewers.ISelectionProvider)">getSite().registerContextMenu(*)</a>.
-It is usually the same as  the <code>selection</code>variable, but not always.
-</p>
-</td>
-<td>3.3</td>
-</tr>
-
-<tr>
-<td>activeMenuEditorInput</td>
-<td><code><a href="../reference/api/org/eclipse/jface/viewers/ISelection.html">org.eclipse.jface.viewers.ISelection</a></code></td>
-<td>
-<p>This is a selection that is available while a context menu is showing.  It is the selection from 
-the editor input, usually if includeEditorInput was set to <code>true</code> during 
-<code>getEditorSite().registerContextMenu(*)</code>.
-
-</p>
-</td>
-<td>3.3</td>
-</tr>
-
-<tr>
-<td>activeFocusControl</td>
-<td><code><a href="../reference/api/org/eclipse/swt/widgets/Control.html">org.eclipse.swt.widgets.Control</a></code></td>
-<td>
-<p>A control that has focus and has been registered with the 
-<a href="../reference/api/org/eclipse/ui/swt/IFocusService.html">IFocusService</a>.
-</p>
-</td>
-
-<td>3.3</td>
-</tr>
-
-<tr>
-<td>activeFocusControlId</td>
-<td><code>java.lang.String</code></td>
-<td>
-<p>The ID of a control that has focus and has been registered with the 
-<a href="../reference/api/org/eclipse/ui/swt/IFocusService.html">IFocusService</a>.
-</p>
-</td>
-<td>3.3</td>
-
-</tr>
-
-<tr>
-<td>org.eclipse.core.runtime.Platform</td>
-<td><code><a href="../reference/api/org/eclipse/core/runtime/Platform.html">org.eclipse.core.runtime.Platform</a></code></td>
-<td>
-<p>
-The runtime Platform class is available, for use with property testers like <code>org.eclipse.core.runtime.isBundleInstalled</code>
-and <code>org.eclipse.core.runtime.product</code>.
-</p>
-</td>
-<td>3.3</td>
-
-</tr>
-
-</table>
-
-
-<h3>Property Testers Provided in the Workbench</h3>
-
-
-<p>
-The workbench provides a couple of property testers that can be used in core expressions.  
-The expression defines a property attribute and then takes a combination of args and a value that 
-is tester implementation dependent.  The property attribute is the combination of the namespace 
-and property name.  For example, to test an IResource name the property would be 
-<code>org.eclipse.core.resources.name</code>.
-</p>
-
-<table border="1">
-<tr>
-<th>Namespace</th>
-<th>Type</th>
-<th>Implementation</th>
-</tr>
-
-<tr>
-<td>org.eclipse.core.runtime</td>
-<td>
-<p><code>org.eclipse.core.runtime.Platform</code>
-
-</p>
-</td>
-<td>
-<code>org.eclipse.core.internal.expressions.propertytester.PlatformPropertyTester</code>
-</td>
-</tr>
-
-
-<tr>
-<th>Property</th>
-<th colspan="2">Description</th>
-</tr>
-
-<tr>
-<td>
-<p>product
-</p>
-</td>
-<td colspan="2">
-<p>Test the id of the currently active product.
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>isBundleInstalled
-</p>
-</td>
-<td colspan="2">
-
-<p>Test if a given bundle is installed in the running environment.  Use the args attribute to pass in the bundle id.
-</p>
-</td>
-</tr>
-
-<tr>
-<td colspan="3" bgcolor="#000000" height="3" ></td>
-</tr>
-
-<tr>
-<th>Namespace</th>
-<th>Type</th>
-<th>Implementation</th>
-</tr>
-
-<tr>
-<td>org.eclipse.core.resources</td>
-<td>
-<p><code>org.eclipse.core.resources.IResource</code>
-</p>
-</td>
-<td>
-<code>org.eclipse.core.internal.propertytester.ResourcePropertyTester</code>
-</td>
-</tr>
-
-
-<tr>
-<th>Property</th>
-<th colspan="2">Description</th>
-</tr>
-
-
-
-<tr>
-<td>
-<p>name
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating the file name (value <code>"name"</code>). "*" and "?" wild cards are supported.
-
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>path
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating the file path (value <code>"path"</code>). "*" and "?" wild cards are supported.
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>extension
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating the file extension (value <code>"extension"</code>). "*" and "?" wild cards are supported.
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>readOnly
-</p>
-
-</td>
-<td colspan="2">
-<p>A property indicating whether the file is read only (value <code>"readOnly"</code>).
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>projectNature
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating the project nature (value <code>"projectNature"</code>).
-
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>persistentProperty
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating a persistent property on the selected resource (value <code>"persistentProperty"</code>). 
-If two arguments are given, this treats the first as the property name, and the second as the expected 
-property value. If only one argument (or just the expected value) is given, this treats it as the 
-property name, and simply tests for existence of the property on the resource.
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>projectPersistentProperty
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating a persistent property on the selected resource's project. 
-(value <code>"projectPersistentProperty"</code>). If two arguments are given, this treats the first 
-as the property name, and the second as the expected property value. If only one argument (or just 
-the expected value) is given, this treats it as the property name, and simply tests for existence 
-of the property on the resource.
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>sessionProperty
-</p>
-
-</td>
-<td colspan="2">
-<p>A property indicating a session property on the selected resource 
-(value <code>"sessionProperty"</code>). If two arguments are given, this treats the first as the 
-property name, and the second as the expected property value. If only one argument (or just the 
-expected value) is given, this treats it as the property name, and simply tests for existence 
-of the property on the resource.
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>projectSessionProperty
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating a session property on the selected resource's project. 
-(value <code>"projectSessionProperty"</code>). If two arguments are given, this treats the first 
-as the property name, and the second as the expected property value. If only one argument (or just 
-the expected value) is given, this treats it as the property name, and simply tests for existence 
-of the property on the resource.
-
-</p>
-</td>
-</tr>
-
-<tr>
-<td colspan="3" bgcolor="#000000" height="3" ></td>
-</tr>
-
-<tr>
-<th>Namespace</th>
-<th>Type</th>
-<th>Implementation</th>
-</tr>
-
-<tr>
-<td>org.eclipse.core.resources</td>
-<td>
-<p><code>org.eclipse.core.resources.IFile</code>
-</p>
-</td>
-<td>
-<code>org.eclipse.core.internal.propertytester.FilePropertyTester</code>
-</td>
-</tr>
-
-
-<tr>
-
-<th>Property</th>
-<th colspan="2">Description</th>
-</tr>
-
-
-
-<tr>
-<td>
-<p>contentTypeId
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating that we are looking to verify that the file matches the content 
-type matching the given identifier. The identifier is provided as the expected value.
-</p>
-</td>
-
-</tr>
-
-<tr>
-<td colspan="3" bgcolor="#000000" height="3" ></td>
-</tr>
-
-
-<tr>
-<th>Namespace</th>
-<th>Type</th>
-<th>Implementation</th>
-</tr>
-
-<tr>
-
-<td>org.eclipse.core.resources</td>
-<td>
-<p><code>org.eclipse.core.resources.IProject</code>
-</p>
-</td>
-<td>
-<code>org.eclipse.core.internal.propertytester.ProjectPropertyTester</code>
-</td>
-</tr>
-
-
-<tr>
-<th>Property</th>
-
-<th colspan="2">Description</th>
-</tr>
-
-<tr>
-<td>
-<p>open
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating whether the project is open (value <code>"open"</code>).
-</p>
-</td>
-</tr>
-
-<tr>
-<td colspan="3" bgcolor="#000000" height="3" ></td>
-</tr>
-
-
-<tr>
-<th>Namespace</th>
-<th>Type</th>
-<th>Implementation</th>
-</tr>
-
-<tr>
-<td>org.eclipse.core.resources</td>
-
-<td>
-<p><code>org.eclipse.core.resources.mapping.ResourceMapping</code>
-</p>
-</td>
-<td>
-<code>org.eclipse.core.internal.propertytester.ResourceMappingPropertyTester</code>
-</td>
-</tr>
-
-
-<tr>
-<th>Property</th>
-<th colspan="2">Description</th>
-
-</tr>
-
-<tr>
-<td>
-<p>projectPersistentProperty
-</p>
-</td>
-<td colspan="2">
-<p>A property indicating a persistent property on the selected resource's project. 
-(value <code>"projectPersistentProperty"</code>). If two arguments are given, this treats the 
-first as the property name, and the second as the expected property value. If only one argument 
-(or just the expected value) is given, this treats it as the property name, and simply tests for 
-existence of the property on the resource.
-</p>
-</td>
-</tr>
-
-<tr>
-<td colspan="3" bgcolor="#000000" height="3" ></td>
-
-</tr>
-
-
-<tr>
-<th>Namespace</th>
-<th>Type</th>
-<th>Implementation</th>
-</tr>
-
-<tr>
-<td>org.eclipse.ui</td>
-<td>
-<p><code>org.eclipse.ui.IWorkbench (not currently available)</code>
-
-</p>
-</td>
-<td>
-<code>org.eclipse.ui.internal.activities.ActivityPropertyTester</code>
-</td>
-</tr>
-
-
-<tr>
-<th>Property</th>
-<th colspan="2">Description</th>
-</tr>
-
-<tr>
-<td>
-<p>isActivityEnabled
-</p>
-</td>
-<td colspan="2">
-<p>Test if the activity in args is enabled.
-</p>
-</td>
-</tr>
-
-<tr>
-<td>
-<p>isCategoryEnabled
-</p>
-</td>
-
-<td colspan="2">
-<p>Test if the category in args is enabled.
-</p>
-</td>
-</tr>
-
-<tr>
-<td colspan="3" bgcolor="#000000" height="3" ></td>
-</tr>
-
-
-<tr>
-<th>Namespace</th>
-<th>Type</th>
-<th>Implementation</th>
-
-</tr>
-
-<tr>
-<td>org.eclipse.ui.workbenchWindow</td>
-<td>
-<p><code>org.eclipse.ui.IWorkbenchWindow</code>
-</p>
-</td>
-<td>
-<code>org.eclipse.ui.internal.OpenPerspectivePropertyTester</code>
-</td>
-</tr>
-
-<tr>
-<th>Property</th>
-<th colspan="2">Description</th>
-</tr>
-
-<tr>
-<td>
-<p>isPerspectiveOpen
-</p>
-</td>
-<td colspan="2">
-<p>Tests if any perspective is open.
-</p>
-</td>
-
-</tr>
-
-</table>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm
deleted file mode 100755
index a37f33f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_handlers.htm
+++ /dev/null

@@ -1,288 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Handlers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Handlers</h3>
-
-
-<p>
-A <b>handler</b> is the implementation of a command's behaviour.  Any plugin can
-contribute a handler implementation for any command.  The workbench uses core
-expressions and programmatic scoping rules to determine which handler is active
-at any time.  There can either be one handler active for the command, or no handlers
-active for the command (the command is effectively disabled).  When the
-command has an active handler, we say the command is handled.
-</p>
-
-<h4>Associating a default handler with a command</h4>
-
-<p>
-While there is a shortcut for a default handler, most handlers are associated
-with their command using the 
-<a href="../reference/extension-points/org_eclipse_ui_handlers.html">org.eclipse.ui.handlers</a>
-extension point.
-</p>
-
-<p>
-A command that has default behaviour (it works as long as the workbench is up)
-can have the default implementation associated in the command definition.  The
-Info example &quot;Global Command&quot; does this:</p>
-<pre>
-      &lt;command
-            categoryId=&quot;org.eclipse.ui.examples.contributions.commands.category&quot;
-            <b>defaultHandler=&quot;org.eclipse.ui.examples.contributions.handlers.GlobalMenuHandler&quot;</b>
-            id=&quot;org.eclipse.ui.examples.contributions.commands.globalCommand&quot;
-            name=&quot;%contributions.commands.globalCommand.name&quot;&gt;
-      &lt;/command&gt;
-</pre>
-
-<p>
-<b>defaultHandler</b> points to the IHandler class that implements the default
-behaviour for this command.  The default handler will always be available unless
-overriden by a handler association in a more specific scope.  This is a shortcut
-for the equivalent <b>org.eclipse.ui.handlers</b> entry:</p>
-<pre>
-      ...
-      &lt;handler
-            class=&quot;org.eclipse.ui.examples.contributions.handlers.GlobalMenuHandler&quot;
-            commandId=&quot;org.eclipse.ui.examples.contributions.commands.globalCommand&quot;&gt;
-      &lt;/handler&gt;
-      ...
-</pre>
-
-
-<h4>Associating a handler with a command while a part type is active</h4>
-
-<p>
-The &lt;activeWhen/&gt; expressions in the plugin.xml and programmatic core
-expressions are used to help determine the scope of a handlers activation.
-For example,  a specific window, a specific <b>Shell</b>, an active part type
-or active part.
-</p>
-<p>
-Here is an example where we are adding some commands to the Info view,
-<b>org.eclipse.ui.examples.contributions.view</b>.  Count to count the number
-of model elements in the view and swap to swap the 2 selected elements.
-The command definitions are in the global space as always:</p>
-<pre>
-   &lt;extension
-         point=&quot;org.eclipse.ui.commands&quot;&gt;
-      &lt;command
-            categoryId=&quot;org.eclipse.ui.examples.contributions.commands.category&quot;
-            id=&quot;org.eclipse.ui.examples.contributions.view.count&quot;
-            description=&quot;%contributions.view.count.desc&quot;
-            name=&quot;%contributions.view.count.name&quot;&gt;
-      &lt;/command&gt;
-      &lt;command
-            categoryId=&quot;org.eclipse.ui.examples.contributions.commands.category&quot;
-            id=&quot;org.eclipse.ui.examples.contributions.view.swap&quot;
-            name=&quot;%contributions.view.swap.name&quot;&gt;
-      &lt;/command&gt;
-      ...
-</pre>
-
-<p>
-We declaratively associate the swap command with a handler that is active
-while a view with the correct ID is active.  When declaring a handler, you
-can also provide a core expression for declarative enablement.  The extension
-point description for
-<a href="../reference/extension-points/org_eclipse_ui_handlers.html">org.eclipse.ui.handlers</a>
-lists valid elements for the core expression.
-</p>
-<pre>
-   &lt;extension
-         point=&quot;org.eclipse.core.expressions.definitions&quot;&gt;
-      ...
-      &lt;definition
-            id=&quot;org.eclipse.ui.examples.contributions.view.inView&quot;&gt;
-         &lt;with
-               variable=&quot;activePartId&quot;&gt;
-            &lt;equals
-                  value=&quot;org.eclipse.ui.examples.contributions.view&quot;&gt;
-            &lt;/equals&gt;
-         &lt;/with&gt;
-      &lt;/definition&gt;
-      ...
-   &lt;/extension&gt;
-   &lt;extension
-         point=&quot;org.eclipse.ui.handlers&quot;&gt;
-      ...
-      &lt;handler
-            class=&quot;org.eclipse.ui.examples.contributions.view.SwapInfoHandler&quot;
-            commandId=&quot;org.eclipse.ui.examples.contributions.view.swap&quot;&gt;
-         <b>&lt;activeWhen&gt;
-            &lt;reference
-                  definitionId=&quot;org.eclipse.ui.examples.contributions.view.inView&quot;&gt;
-            &lt;/reference&gt;
-         &lt;/activeWhen&gt;</b>
-         &lt;enabledWhen&gt;
-            &lt;count
-                  value=&quot;2&quot;&gt;
-            &lt;/count&gt;
-         &lt;/enabledWhen&gt;
-      &lt;/handler&gt;
-      ...
-</pre>
-
-<p>
-Here we are using another extension point
-<a href="../reference/extension-points/org_eclipse_core_expressions_definitions.html">org.eclipse.core.expressions.definitions</a>
-so we can reuse the same expression in multiple places.  The definition's id is
-<b>org.eclipse.ui.examples.contributions.view.inView</b> and the expression it
-defines is &lt;with variable=&quot;activePartId&quot;&gt;...&lt;/with&gt;.
-Whenever another core expression uses &lt;reference 
-definitionId=&quot;org.eclipse.ui.examples.contributions.view.inView&quot;/&gt;
-the &lt;with...&gt; expression will be evaluated.
-</p>
-<p>
-The &lt;activeWhen/&gt; clause here says the this handler will be active
-when the <b>activePartId</b> equals our Info view id.  The priorities defined in
-<a href="../reference/api/org/eclipse/ui/ISources.html">org.eclipse.ui.ISources</a>
-can give you an idea of the relative importance of different variables, although
-the priorities alone do not determine a variable's relative importance.
-</p>
-<p>
-Our handler definition also includes an &lt;enabledWhen&gt; clause.  In this
-case the handler will be enabled when the default variable (the current
-selection converted into a <b>java.util.Collection</b> of objects) has 2 elements.
-A core expression that does not include a &lt;with/&gt; element is evaluated
-against the default variable.
-</p>
-
-<h4>Associating a handler programmically with a command while a specific part is active</h4>
-
-<p>
-Sometimes it is desirable to instantiate your handlers when your part is
-created.  You can use the 
-<a href="../reference/api/org/eclipse/ui/handlers/IHandlerService.html">org.eclipse.ui.handlers.IHandlerService</a>
-to activate your handler for your part.  Here is the code that activates
-a handler for the count command.
-</p>
-<pre>
-	private static final String VIEW_COUNT_ID = &quot;org.eclipse.ui.examples.contributions.view.count&quot;; //$NON-NLS-1$
-	...
-	/**
-	 * Instantiate any handlers specific to this view and activate them.
-	 */
-	private void createHandlers() {
-		// 1 - get the handler service from the view site
-		IHandlerService handlerService = (IHandlerService) getSite()
-				.getService(IHandlerService.class);
-		// 2 - create the handler instance
-		countHandler = new AbstractHandler() {
-			public Object execute(ExecutionEvent event)
-					throws ExecutionException {
-				// viewer is an instance variable of InfoView
-				List elements = (List) viewer.getInput();
-				MessageDialog.openInformation(getSite().getShell(),
-						ContributionMessages.SampleHandler_plugin_name,
-						NLS.bind(ContributionMessages.InfoView_countElements,
-								new Integer(elements.size())));
-				return null;
-			}
-		};
-		// 3 - activate this handler instance for the count command
-		handlerService.activateHandler(VIEW_COUNT_ID, countHandler);
-	}
-</pre>
-<p>
-In the InfoView,  createHandlers() is called from the end of the
-createPartControl(Composite) method.
-<a href="../reference/api/org/eclipse/ui/handlers/IHandlerService.html">org.eclipse.ui.handlers.IHandlerService</a>
-and
-<a href="../reference/api/org/eclipse/ui/contexts/IContextService.html">org.eclipse.ui.context.IContextService</a>
-provide scoping of their activations depending on where you get the service.</p>
-<ol>
-<li><b>IHandlerService</b> from the workbench is the global handler service.
-it provides no special activation scoping or lifecycle.</li>
-<li><b>IHandlerService</b> from the workbench window is the window handler service.
-Any handlers activated through the window handler service will be active when
-that window is active.  Any listeners added to the window handler service
-will be removed when the window is disposed, and any active handlers will be deactivated
-(but not disposed).</li>
-<li><b>IHandlerService</b> from the workbench part site is the part handler service.
-Any handlers activated through the part handlers service will only be active
-when that part is active. Any listeners added to the part handler service
-will be removed when the part is disposed, and any active handlers will be deactivated
-(but not disposed).</li>
-</ol>
-
-
-<h4>Implementing the handler</h4>
-<p>
-A handler must implement 
-<a href="../reference/api/org/eclipse/core/commands/IHandler.html">org.eclipse.core.commands.IHandler</a>
-although in most cases it is easier to subclass
-<a href="../reference/api/org/eclipse/core/commands/AbstractHandler.html">org.eclipse.core.commands.AbstractHandler</a>.
-</p>
-<p>
-The bulk of the work is done in the <b>execute(ExecutionEvent)</b> method.  From the
-<a href="../reference/api/org/eclipse/core/commands/ExecutionEvent.html">org.eclipse.core.commands.ExecutionEvent</a>
-you can get any parameters from the calling command object as well as the application context
-the command was executed in.
-</p>
-
-<pre>
-		Object object = event.getApplicationContext();
-		if (object instanceof IEvaluationContext) {
-			IEvaluationContext appContext = (IEvaluationContext) object;
-			...
-		}
-</pre>
-
-<p>
-The application context provides access to much of the workbench current state.
-For example, the active workbench window, active shell, active part, active editor,
-and current selection to name a few.
-See 
-<a href="../reference/api/org/eclipse/ui/handlers/HandlerUtil.html">org.eclipse.ui.handlers.HandlerUtil</a>
-for an example of extracting variables from the application context and
-<a href="../reference/api/org/eclipse/ui/ISources.html">org.eclipse.ui.ISources</a>
-for a list of variables that are currently supported.
-</p>
-<p>
-The <b>GlobalMenuHandler</b> is an example of a simple handler that just
-opens an information popup with a message.  The example execute:</p>
-<pre>
-	public Object execute(ExecutionEvent event) throws ExecutionException {
-		IWorkbenchWindow window = HandlerUtil
-				.getActiveWorkbenchWindowChecked(event);
-		MessageDialog.openInformation(window.getShell(),
-				ContributionMessages.SampleHandler_plugin_name,
-				ContributionMessages.SampleHandler_hello_msg);
-		return null;
-	}
-</pre>
-<p>
-Handlers subclassing
-<a href="../reference/api/org/eclipse/core/commands/AbstractHandler.html">org.eclipse.core.commands.AbstractHandler</a>
-or implementing
-<a href="../reference/api/org/eclipse/core/commands/IHandler2.html">org.eclipse.core.commands.IHandler2</a>
-can implement <code>setEnabled(Object evaluationContext)</code>.  Before the workbench framework
-asks a handler for its enabled state, it will call <code>setEnabled</code> with an
-<a href="../reference/api/org/eclipse/core/expressions/IEvaluationContext.html">org.eclipse.core.expressions.IEvaluationContext</a>
-to allow the handler to update its state.
-</p>
-<p>
-Without getting into to many details, this uses a <b>HandlerUtil</b> convenience
-method to extract the active workbench window.  Then it opens an information
-dialog with a &quot;hello world&quot; message.  <b>ContributionMessages</b> is an
-<a href="../reference/api/org/eclipse/osgi/util/NLS.html">org.eclipse.osgi.util.NLS</a>
-subclass to help externalize our message strings.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm
deleted file mode 100755
index f4e6c11..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_cmd_menus.htm
+++ /dev/null

@@ -1,424 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006,2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>org.eclipse.ui.menus</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>org.eclipse.ui.menus</h3>
-
-<p>
-Commands can be implemented using 
-<a href="../reference/extension-points/org_eclipse_ui_handlers.html">org.eclipse.ui.handlers</a>
-and bound to keys using
-<a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a>.
-With the 
-<a href="../reference/extension-points/org_eclipse_ui_menus.html">org.eclipse.ui.menus</a>
-extension point they can be placed in the main menu, view dropdown menus, context
-menus.  They can also be added to the main toolbar, view toolbars, and various
-trim locations.
-</p>
-
-<h4>Contribution location</h4>
-<p>
-The older action contribution points use the concept of 
-<a href="workbench_menupaths.htm" class="XRef">menu and toolbar paths</a>
-to place menu items and tool items.  The <b>org.eclipse.ui.menus</b>
-extension point requires the id of a menu, toolbar, or trim area and an insertion
-point.  This is the <b>locationURI</b> of a &lt;menuContribution/&gt; element.
-Some examples of <b>locationURIs</b>:</p>
-<ul>
-<li>menu:org.eclipse.ui.main.menu?after=window - insert this contribution in the
-main menu after the <b>Window</b> menu.</li>
-<li>menu:file?after=additions - insert this contribution in the <b>File</b> menu
-after the additions group.  Equivalent to the old menubarPath="file/additions".</li>
-<li>menu:org.eclipse.ui.views.ContentOutline?after=additions - insert this
-contribution in the Content Outline view dropdown menu after the additions group.</li>
-<li>toolbar:org.eclipse.ui.views.ContentOutline?after=additions - insert this
-contribution in the Content Outline view toolbar, after the additions group.</li>
-<li>popup:org.eclipse.ui.examples.propertysheet.outline?after=additions - insert
-this contribution in the Property Sheet outline page context menu after
-the additions group.</li>
-</ul>
-
-<p>
-A word about popup: locationURIs.  In <code>popup:id</code>, the id refers to
-the id that comes from registering the context menu when the registerContextMenu(*)
-method is called.  If an no id is specified in the call, it defaults to the id of
-the view or editor registering the context menu.
-</p>
-<p>
-The workbench defines all of its group slot names in the classes 
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>
-and <b><a href="../reference/api/org/eclipse/ui/ide/IIDEActionConstants.html">IIDEActionConstants</a></b>.
-These ids, like the <b>file</b> example above, are available to menu contributions.
-</p>
-<p>
-After the <b>locationURI</b> specifies the insertion point, the &lt;menuContribution/&gt;
-elements are turned into IContributionItems and inserted in order.  Another
-difference between menu contributions and action contributions is that the menu
-contributions can be defined in the XML in the same kind of containing relationship
-that one would would see in a menu or toolbar.
-</p>
-<p>
-Let's start with a simple example from our Info example, adding some commands
-to the InfoView.</p>
-<pre>
-   &lt;extension
-         point=&quot;org.eclipse.ui.menus&quot;&gt;
-      &lt;menuContribution
-            locationURI=&quot;menu:org.eclipse.ui.examples.contributions.view?after=additions&quot;&gt;
-         &lt;command
-               commandId=&quot;org.eclipse.ui.examples.contributions.view.count&quot;
-               mnemonic=&quot;%contributions.view.count.mnemonic&quot;&gt;
-         &lt;/command&gt;
-         &lt;command
-               commandId=&quot;org.eclipse.ui.examples.contributions.view.edit&quot;
-               mnemonic=&quot;%contributions.view.edit.mnemonic&quot;&gt;
-         &lt;/command&gt;
-         &lt;command
-               commandId=&quot;org.eclipse.ui.file.refresh&quot;
-               mnemonic=&quot;%contributions.view.refresh.mnemonic&quot;&gt;
-         &lt;/command&gt;
-      &lt;/menuContribution&gt;
-      ...
-</pre>
-
-<p>
-Our <b>locationURI</b> marks this contribution for the org.eclipse.ui.examples.contributions.view
-view. Here we are adding 3 commands to the InfoView dropdown menu: Count Entries,
-Edit, and Refresh.
-</p>
-<img src="images/contributions_view_dropdown.png" >
-<p>Although you can specify a <b>label</b> in the menu
-contribution &lt;command/&gt; element, if you don't we will use the <b>name</b>
-attribute from the 
-<a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a>
-command definition.  Now clicking on the menu element will execute that command.
-</p>
-<p>
-We've also placed a command in the InfoView toolbar:</p>
-<pre>
-      &lt;menuContribution
-            locationURI=&quot;toolbar:org.eclipse.ui.examples.contributions.view?after=additions&quot;&gt;
-         &lt;command
-               commandId=&quot;org.eclipse.ui.examples.contributions.view.swap&quot;
-               label=&quot;%contributions.view.swap.name&quot;
-               tooltip=&quot;%contributions.view.swap.tooltip&quot;&gt;
-         &lt;/command&gt;
-      &lt;/menuContribution&gt;
-</pre>
-
-<p>
-<b>Note:</b> this command will appear in the view's toolbar.  To place the same command in the
-main toolbar, you have to create the toolbar as well by including a &lt;toolbar/&gt; element
-in the &lt;menuContribution/&gt; to contain the command.
-</p>
-
-<p>
-The &quot;Swap Entries&quot; button on the toolbar will be
-disabled until 2 Person entries are selected in the
-info view because we defined an &lt;enabledWhen&gt; expression
-in the handler definition:</p>
-<pre>
-         &lt;enabledWhen&gt;
-            &lt;count
-                  value=&quot;2&quot;&gt;
-            &lt;/count&gt;
-         &lt;/enabledWhen&gt;
-</pre>
-
-<h4>Contribution visibility</h4>
-
-<p>
-A command's enabled state is controlled by a combination of the command
-is handled and if so, the handler's enabled state.  Menu contributions
-can use core expressions to control the command's visibility in menus and
-toolbars.
-</p>
-<p>
-As an example, menu contributions can still be tied to an existing action
-set while being contributed to the main menu or main toolbar, as action sets
-are converted into contexts.  In this example
-we  place our command in the main menu and main toolbar.</p>
-<pre>
-   &lt;extension
-         point=&quot;org.eclipse.ui.actionSets&quot;&gt;
-      &lt;actionSet
-            id=&quot;org.eclipse.ui.examples.contributions.globalActionSet&quot;
-            label=&quot;%contributions.globalActionSet.label&quot;
-            visible=&quot;false&quot;&gt;
-      &lt;/actionSet&gt;
-   &lt;/extension&gt;
-   &lt;extension
-         point=&quot;org.eclipse.core.expressions.definitions&quot;&gt;
-      &lt;definition
-            id=&quot;org.eclipse.ui.examples.contributions.inGlobalActionSet&quot;&gt;
-         &lt;with
-               variable=&quot;activeContexts&quot;&gt;
-            &lt;iterate
-                  operator=&quot;or&quot;&gt;
-               &lt;equals
-                     value=&quot;org.eclipse.ui.examples.contributions.globalActionSet&quot;&gt;
-               &lt;/equals&gt;
-            &lt;/iterate&gt;
-         &lt;/with&gt;
-      &lt;/definition&gt;
-      ...
-</pre>
-
-<p>
-The above XML defines the action set to use, and a definition for a core expression
-that checks contexts to see if the action set is active.  See the <a href="workbench_cmd_handlers.htm"
-class="XRef">org.eclipse.ui.handlers</a> section for other examples of core
-expressions. 
-</p>
-<img src="images/contributions_global.png">
-<p>
-Now we can add our command to the main menu:</p>
-<pre>
-      &lt;menuContribution
-            locationURI=&quot;menu:org.eclipse.ui.main.menu?after=additions&quot;&gt;
-         &lt;menu
-               label=&quot;%contributions.menus.globalMenu.label&quot;
-               mnemonic=&quot;%contributions.menus.globalMenu.label&quot;
-               id=&quot;org.eclipse.ui.examples.contributions.menus.globalMenu&quot;&gt;
-            &lt;command
-                  commandId=&quot;org.eclipse.ui.examples.contributions.commands.globalCommand&quot;
-                  mnemonic=&quot;%contributions.menus.globalCommand.mnemonic&quot;
-                  id=&quot;org.eclipse.ui.examples.contributions.menus.globalCommand&quot;&gt;
-               &lt;visibleWhen&gt;
-                  &lt;reference
-                        definitionId=&quot;org.eclipse.ui.examples.contributions.inGlobalActionSet&quot;&gt;
-                  &lt;/reference&gt;
-               &lt;/visibleWhen&gt;
-            &lt;/command&gt;
-            &lt;separator
-                  name=&quot;additions&quot;
-                  visible=&quot;false&quot;&gt;
-            &lt;/separator&gt;
-         &lt;/menu&gt;
-      &lt;/menuContribution&gt;
-      &lt;menuContribution
-            locationURI=&quot;toolbar:org.eclipse.ui.main.toolbar?after=additions&quot;&gt;
-         &lt;toolbar
-               id=&quot;org.eclipse.ui.examples.contributions.toolbars.sampleToolbar&quot;&gt;
-            &lt;command
-                  commandId=&quot;org.eclipse.ui.examples.contributions.commands.globalCommand&quot;
-                  icon=&quot;icons/sample.gif&quot;
-                  tooltip=&quot;%contributions.toolbars.globalCommand.tooltip&quot;
-                  id=&quot;org.eclipse.ui.examples.contributions.toolbars.globalCommand&quot;&gt;
-               &lt;visibleWhen&gt;
-                  &lt;reference
-                        definitionId=&quot;org.eclipse.ui.examples.contributions.inGlobalActionSet&quot;&gt;
-                  &lt;/reference&gt;
-               &lt;/visibleWhen&gt;
-            &lt;/command&gt;
-            &lt;separator
-                  name=&quot;additions&quot;
-                  visible=&quot;false&quot;&gt;
-            &lt;/separator&gt;
-         &lt;/toolbar&gt;
-      &lt;/menuContribution&gt;
-      ...
-</pre>
-
-<p>
-In the above XML, we are adding the menu &quot;Global Menu&quot; to the main menu,
-and then placing the &quot;Global Command&quot; in it.  The &lt;visibleWhen/&gt;
-element will evaluate the body of the previously defined inGlobalActionSet
-core expression.  The &lt;separator/&gt; element adds and additions group
-that can be used by other contributions.  We are also creating a toolbar
-in the main coolbar (org.eclipse.ui.main.toolbar) and placing a our command
-in it with the sample.gif <img src="images/sample.gif"> icon.
-</p>
-<p>
-Other contributions can now contribute to the &quot;Global Menu&quot;
-menu by specifying its id as a contribution <b>locationURI</b>: 
-menu:org.eclipse.ui.examples.contributions.menus.globalMenu?after=additions.
-</p>
-<p>
-Currently, commands contributed to action sets don't show up in the 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Customize Perspective...</b></a> dialog.
-</p>
-
-<p>
-You can add menu contributions that work similar to <b>org.eclipse.ui.editorActions</b>.
-First you define your editor command and handler, like Reset.  Then you can
-add them in an editor menu like &quot;Info&quot; to the main menu:</p>
-<pre>
-      ... org.eclipse.core.expressions.definitions
-      &lt;definition
-            id=&quot;org.eclipse.ui.examples.contributions.view.activeEditor&quot;&gt;
-         &lt;with
-               variable=&quot;activeEditorId&quot;&gt;
-            &lt;equals
-                  value=&quot;org.eclipse.ui.examples.contributions.editor&quot;&gt;
-            &lt;/equals&gt;
-         &lt;/with&gt;
-      &lt;/definition&gt;
-      ... org.eclipse.ui.menus
-      &lt;menuContribution
-            locationURI=&quot;menu:org.eclipse.ui.main.menu?after=additions&quot;&gt;
-         &lt;menu
-               id=&quot;org.eclipse.ui.examples.contributions.editor.menu&quot;
-               label=&quot;%contributions.editor.menu.label&quot;
-               mnemonic=&quot;%contributions.editor.menu.mnemonic&quot;&gt;
-            &lt;command
-                  commandId=&quot;org.eclipse.ui.examples.contributions.editor.reset&quot;
-                  mnemonic=&quot;%contributions.editor.reset.mnemonic&quot;&gt;
-               &lt;visibleWhen&gt;
-                  &lt;reference
-                        definitionId=&quot;org.eclipse.ui.examples.contributions.view.activeEditor&quot;&gt;
-                  &lt;/reference&gt;
-               &lt;/visibleWhen&gt;
-            &lt;/command&gt;
-         &lt;/menu&gt;
-      &lt;/menuContribution&gt;
-</pre>
-
-<p>
-This is similar to adding to the main menu with our global action example.
-Here our core expression
-will make this element visible as long as the active editor id variable
-matches our editor.  You can check out
-<a href="../reference/api/org/eclipse/ui/ISources.html">org.eclipse.ui.ISources</a>
-for a list of supported variables names.
-</p>
-<p>
-<b>Note:</b> updating the main menu and especially the main toolbar are expensive
-operations.  You generally want to confine them to actionSet equivalent contexts
-and active editor type.  Although you can update the main toolbar on each
-selection change using the default variable or a &lt;with variable=&quot;selection&quot;/&gt;
-expression, it's not a good idea.  The common practice is to leave your command
-visibility at the action set or active editor level, and have your handler
-enabled state track the current selection.
-</p>
-
-<h4>Contributing to popup menus</h4>
-
-<p>
-As in <a href="workbench_basicext_popupMenus.htm" class="XRef">org.eclipse.ui.popupMenus</a>,
-commands can be contributed to a specific context menu by the context menu's id, or to any
-context menu where it can satisfy its &lt;visibleWhen&gt; clause.  For example, we can add
-our Refresh command to the Info View popup as a convenience.  Because we didn't call
-<code>registerContextMenu(*)</code> with a specific id it defaults to the view id.</p>
-<pre>
-      &lt;menuContribution
-            locationURI=&quot;popup:org.eclipse.ui.examples.contributions.view?after=additions&quot;&gt;
-         &lt;command
-               commandId=&quot;org.eclipse.ui.file.refresh&quot;
-               mnemonic=&quot;%contributions.view.refresh.mnemonic&quot;&gt;
-         &lt;/command&gt;
-      &lt;/menuContribution&gt;
-</pre>
-
-<p>
-To contribute a command to a popup if its selection matches a particular object type you
-can use the default variable, or for behaviour closest to <b>org.eclipse.ui.popupMenus</b>
-target a specific popup selection variable.  Here's an example using the context menu
-selection provider.  This just effects the popup menu visibility, not the command
-enabled state.</p>
-<pre>
-      &lt;menuContribution
-            locationURI=&quot;popup:org.eclipse.ui.popup.any?after=additions&quot;&gt;
-         &lt;command
-               commandId=&quot;org.eclipse.ui.examples.contributions.view.edit&quot;
-               mnemonic=&quot;%contributions.view.edit.mnemonic&quot;&gt;
-            &lt;visibleWhen&gt;
-               &lt;with
-                     variable=&quot;activeMenuSelection&quot;&gt;
-                  &lt;iterate&gt;
-                     &lt;adapt
-                           type=&quot;org.eclipse.ui.examples.contributions.model.Person&quot;&gt;
-                     &lt;/adapt&gt;
-                  &lt;/iterate&gt;
-               &lt;/with&gt;
-            &lt;/visibleWhen&gt;
-         &lt;/command&gt;
-      &lt;/menuContribution&gt;
-</pre>
-
-<img src="images/contributions_popup.png" >
-<p>
-Using &lt;iterate&gt;&lt;adapt type=&quot;Person&quot;/&gt;&lt;/iterate&gt; is
-the core expression equivalent of the old <b>objectClass</b> attribute.
-</p>
-
-
-<h4>Adding toolbars to trim areas</h4>
-<p>
-A 'trim' widget is a control that gets sited into a location (called a 'Trim Area') on the outer boundary of the Workbench Window. The
-most common example is the generic 'status line' which almost all GUI's place along the bottom of the window.
-The extension point <b><a href="../reference/extension-points/org_eclipse_ui_menus.html">org.eclipse.ui.menus</a></b>
-allows plug-ins to add elements to the workbench trim by contributing <i>toolbars</i> into trim areas and populating the toolbar with
-one or more controls (using the same mechanism as contributing controls into the main toolbar).
-</p>
-<p>
-Controls contributed to the trim must be a subclass of 
-<b><a href="../reference/api/org/eclipse/ui/menus/WorkbenchWindowControlContribution.html">WorkbenchWindowControlContribution</a></b>.
-This class will manage the life-cycle of the contribution, disposing and re-creating the contribution as necessary (such as when the user moves the control to another trim area). Note that the <code>getCurSide()</code> and <code>getOrientation()</code> methods
-allow the implementation of <code>createControl(parent)</code> to adjust the created control to it's current locaton in the trim.
-</p>
-<p>
-For this example we've contributed a fairly naive trim widget that simply displays a string and an indication of which side the trim iscurrently docked on.
-</p>
-<p>
-<img src="images/readmetrim.png" alt="" border="0">
-</p>
-<p>
-Let's take a look at the extension point definition used to contribute this piece of trim:
-</p>
-<pre>
-      &lt;menuContribution
-            locationURI=&quot;toolbar:org.eclipse.ui.trim.status&quot;&gt;
-         &lt;toolbar
-               id=&quot;org.eclipse.ui.examples.contributions.contributedTrim&quot;&gt;
-            &lt;command
-                  commandId=&quot;org.eclipse.ui.examples.contributions.item2&quot;
-                  icon=&quot;icons/editor.gif&quot;
-                  id=&quot;contributions.trimItem&quot;
-                  label=&quot;%Trim.item&quot;
-                  tooltip=&quot;%TrimItem.toolTip&quot;&gt;
-            &lt;/command&gt;
-            &lt;control
-                  class=&quot;org.eclipse.ui.examples.contributions.ExampleControlContribution&quot;
-                  id=&quot;contributions.controlContrib1&quot;&gt;
-            &lt;/control&gt;
-            &lt;command
-                  commandId=&quot;org.eclipse.ui.examples.contributions.item2&quot;
-                  icon=&quot;icons/editor.gif&quot;
-                  id=&quot;contributions.trimItem2&quot;
-                  label=&quot;%Trim2.item&quot;
-                  tooltip=&quot;%TrimItem2.toolTip&quot;&gt;
-            &lt;/command&gt;
-         &lt;/toolbar&gt;
-      &lt;/menuContribution&gt;
-</pre>
-<p>
-This extension defines the 'locationURI' for this extension; identifying it as being at the start of the 'status' trim area (i.e. at the beginning of the bottom). We then define a <i>toolbar</i> contribution at that location, adding a <i>control</i>
-contribution bracketed by two <i>command</i> contributions directly into its definition.
-</p>
-<p>
-One thing that is not reflected in this sample's code is the reliance of the trim layout manager on the trim control's proper implementation of the widget control's <code>computeSize</code> method. The widget must be capable of calculating and returning its 'preferred' size since this is used throughout the layout management implementation to determine, for example, how much space is needed for a particular trim area.
-</p>
-<p>
-For example, if you want to contribute a Text input control to the trim (i.e. a 'Search Bar') and you want to control the width it has you'll need to wrap the Text control in a Composite whose Layout's 'computeSize' returns the correct values.
-</p>
-<p>
-See the SWT documentation for notes on how to correctly implement '<code>computeSize</code>' correctly.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
deleted file mode 100644
index 4a3d40d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_jobs.htm
+++ /dev/null

@@ -1,267 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Workbench concurrency support</title>
-  <link href="../book.css" type="text/css" rel="stylesheet">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h2>
-Workbench concurrency support</h2>
-<p>
-We've seen that the JFace UI framework provides basic support for
-showing task progress in a dialog (see <a href="jface_operations.htm">Long
-running operations</a> for details). In <a href="runtime_jobs.htm">Concurrency
-infrastructure</a>, we reviewed the platform runtime support for
-concurrency and long running operations. Now we will look at how
-the platform UI enhances this infrastructure in the <b><a href="../reference/api/org/eclipse/ui/progress/package-summary.html">
-org.eclipse.ui.progress</a></b> package. This package supplies the UI
-for showing job progress in the workbench and defines additional
-support for jobs that run in the UI thread.<br>
-</p>
-<p>First, let's look at the different kinds of background operations that may be running
-and how they are shown in the workbench UI:</p>
-<ul>
-  <li>
-    <p><i>User initiated</i> jobs are those that the user has triggered. 
-The workbench will automatically show user jobs in a modal progress
-dialog with a button to allow the user to run the operation in the
-background and continue working. A global preference is used to indicate whether user
-jobs should always run in the background.  User jobs are distinguished as such
-in the Job API using (<a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html#setUser(boolean)">Job#setUser</a>).
-Examples of user jobs include building, checking out a project, synchronizing
-with the repository, exporting a plug-in, and searching. </p>
-  </li>
-  <li>
-    <p><i>Automatically triggered</i> jobs have a meaning for users but are not initiated by the 
-user. These jobs are shown in the progress view and in the
-status line, but a modal progress dialog won't be shown when they are run.  
-Examples include autobuild and scheduled synchronization.</p>
-  </li>
-  <li>
-    <p><i>System operations</i> are not triggered by the user and can be considered a platform
-implementation detail. These jobs are created by setting the system
-flag using(<a href="../reference/api/org/eclipse/core/runtime/jobs/Job.html#setSystem(boolean)">Job#setSystem</a>).
-Examples of system jobs include jobs that lazily populate widgets or compute decorations and annotations for views.
- </p>
-  </li>
-</ul>
-<p><br>
-Given an environment where several things may be happening at the same
-time, a user needs the following:</p>
-<ul>
-  <li>
-    <p>Indication that a long running operation has started.</p>
-    <p><br>
-User jobs are shown to the user in a progress dialog giving immediate
-feedback, whereas automatically triggered jobs are shown in the status
-line and progress view. Jobs that affect a part should
-be <a href="#site_service">scheduled or registered with the part</a>
-so that the workbench can provide hints to the user that something is running
-that affects the part.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>Indication that an operation has ended.</p>
-    <p><br>
-The user can easily know when a user job ends because the progress
-dialog closes. For non-user jobs, there are a couple of feedback mechanisms
-available. If the job is <a href="#site_service">scheduled or
-registered with a part</a> then the part's progress hint will show when
-it is complete. If a job returns an error, an error indicator will
-appear in the bottom right of the status line showing a hint that an
-error has occured.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>Indication of interesting new results, or new information, 
-    without stealing focus by using a dialog.</p>
-    <p><br>
-A user job can directly show the results to the user when the operation
-completes. For non-user jobs, it is recommended to use something other than a
-dialog to show results, so that the user is not interrupted.  For example, a view could be opened
-when the job starts and the results shown in this view without disrupting the
-user's workflow.  In addition, <a href="#job_properties">job properties</a> can be
-added to the job to indicate that it
-should be kept in the progress view and that it provides an action that will show
-the results. In this case, a warning indication will appear in the bottom right
-corner of the status line when a job remains in the progress view and
-has results to show the user.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>A general feeling of being in control of what is running, with
-    the ability to monitor and cancel background operations.</p>
-    <p><br>
-User jobs provide the best control for the user since they are easily
-cancelled and provide strong indication of blocking or conccurent operations running
-via the <b>Details</b> tab of the progress dialog. Note that the enhanced
-progress dialog that provides the <b>Details</b> area is only shown when plug-ins use
-<a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#busyCursorWhile(org.eclipse.jface.operation.IRunnableWithProgress)">IProgressService#busyCursorWhile</a>
-or <a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#runInUI(org.eclipse.jface.operation.IRunnableContext, org.eclipse.jface.operation.IRunnableWithProgress, org.eclipse.core.runtime.jobs.ISchedulingRule)">IProgressService#runInUI</a>.
-In addition, the progress view provides access to jobs that are running.</p>
-    <p><br>
-    </p>
-  </li>
-  <li>
-    <p>Consistent reporting of progress by all installed plug-ins.</p>
-    <p><br>
-The advantage of using the progress service API is that users get a consistent progress experience. </p>
-    <p><br>
-    </p>
-  </li>
-</ul>
-<h3>Progress service</h3>
-<p>
-The workbench progress service (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html">IProgressService</a>)
-is the primary interface to the workbench progress support. It can be
-obtained from the workbench and then used to show progress
-for both background operations and operations that run in the UI
-thread. The main purpose of this class is to provide one-stop shopping
-for running operations, removing the need for plug-in developers to 
-decide what mechanism should be used for showing progress in a given situation.
-Another advantage is that the progress dialog shown
-with these methods provides good support for indicating when an operation is
-blocked by another and gives the user control to resolve the conflict.
-Where possible, long running operations should be run using
-<a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#busyCursorWhile(org.eclipse.jface.operation.IRunnableWithProgress)">IProgressService#busyCursorWhile</a>:
-</p>
-<pre>
-   IProgressService progressService = PlatformUI.getWorkbench().getProgressService();
-   progressService.<b>busyCursorWhile</b>(new IRunnableWithProgress(){
-      public void run(IProgressMonitor monitor) {
-         //do non-UI work
-      }
-   });
-</pre>
-<p>This method will initially put up a busy cursor, and replace it with
-a progress dialog if the operation
-lasts longer than a specified time threshhold. The advantage of this
-method over using a progress dialog is that the progress dialog won't be shown
-if the operation is short
-running . If your operation must
-update the UI, you can always use <a
- href="../reference/api/org/eclipse/swt/widgets/Display.html#asyncExec(java.lang.Runnable)">Display.asyncExec</a>
-or <a
- href="../reference/api/org/eclipse/swt/widgets/Display.html#syncExec(java.lang.Runnable)">Display.syncExec</a>
-to run the code that modifies the UI.</p>
-<p> If an operation must be run in
-its entirety in the UI thread, then <a
- href="../reference/api/org/eclipse/ui/progress/IProgressService.html#runInUI(org.eclipse.jface.operation.IRunnableContext, org.eclipse.jface.operation.IRunnableWithProgress, org.eclipse.core.runtime.jobs.ISchedulingRule)">IProgressService#runInUI</a>
- should be used.  This method will also display a progress
-dialog if the operation is blocked and give the user control.</p>
-<pre>
-   progressService.<b>runInUI</b>(
-      PlatformUI.getWorkbench().getProgressService(),
-      new IRunnableWithProgress() {
-         public void run(IProgressMonitor monitor) {
-            //do UI work
-         }
-      },
-      Platform.getWorkspace().getRoot());
-</pre>
-<p>The third parameter can be null, or a scheduling rule for the
-operation. In this example, we are specifying the workspace root which will
-essentially lock the workspace while this UI operation is run.</p>
-<p>
-You can also register an icon for a job family with the progress service
-so that the progress view can show the icon next to the running
-job. Here is an example that shows how the auto-build job family is associated with its
-icon:</p>
-<pre>
-   IProgressService service = PlatformUI.getWorkbench().getProgressService();
-   ImageDescriptor newImage = IDEInternalWorkbenchImages.getImageDescriptor(
-      IDEInternalWorkbenchImages.IMG_ETOOL_BUILD_EXEC);
-   service.<b>registerIconForFamily</b>(newImage, ResourcesPlugin.FAMILY_MANUAL_BUILD);
-   service.registerIconForFamily(newImage, ResourcesPlugin.FAMILY_AUTO_BUILD);
-</pre>
-<h3><a name="site_service"></a>Showing that a part is busy</h3>
-<p>
-<a
- href="../reference/api/org/eclipse/ui/progress/IWorkbenchSiteProgressService.html"><b>IWorkbenchSiteProgressService</b></a>
-includes API for scheduling jobs that change the appearance of a workbench
-part while the job is running. If your plug-in is running background
-operations that affect the state of a part, you can schedule the job via
-the part and the user will get feedback that the part is busy. Here is
-an example:</p>
-<pre>
-   IWorkbenchSiteProgressService siteService =
-      (IWorkbenchSiteProgressService)view.getSite().getAdapter(IWorkbenchSiteProgressService.class);
-   siteService.<b>schedule</b>(job, 0 /* now */, true /* use the half-busy cursor in the part */);
-</pre>
-<h3><a name="job_properties"></a>Progress Properties for Jobs</h3>
-<p>The workbench defines progress-related properties for jobs in <a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html">IProgressConstants
-</a>.  These can be used to control how a job is shown in the progress
-view. These can be used to tell the progress view to keep (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#KEEP_PROPERTY">IProgressConstants#KEEP_PROPERTY</a>)
-your job in the view after it has finished, or only keep one (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#KEEPONE_PROPERTY">IProgressConstants#KEEPONE_PROPERTY</a>)
-job at a time in the view. You can also associate an action (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#ACTION_PROPERTY">IProgressConstants#ACTION_PROPERTY</a>)
-with a job. When a job has an associated action, the progress view
-shows a hyperlink so that a user can run the action. You can also find
-out if a user job is currently being shown in a progress dialog (<a
- href="../reference/api/org/eclipse/ui/progress/IProgressConstants.html#PROPERTY_IN_DIALOG">IProgressConstants#PROPERTY_IN_DIALOG</a>).
-A hint is provided in the bottom right of the status line when an
-action is available. The following example uses these properties:</p>
-<pre>
-   Job job = new Job("Do Work") {
-      public IStatus run(IProgressMonitor monitor) {
-         // do some work.  
-         // Keep the finished job in the progress view only if it is not running in the progress dialog
-         Boolean inDialog = (Boolean)getProperty(IProgressConstants.PROPERTY_IN_DIALOG);
-         if(!inDialog.booleanValue())
-            <b>setProperty</b>(IProgressConstants.KEEP_PROPERTY, Boolean.TRUE);
-      }
-   };
-   job.<b>setProperty</b>(IProgressConstants.ICON_PROPERTY, Plugin.getImageDescriptor(WORK_IMAGE));
-   IAction gotoAction = new Action("Results") {
-      public void run() {
-         // show the results
-      }
-   };
-   job.<b>setProperty</b>(IProgressConstants.ACTION_PROPERTY, gotoAction);
-   job.setUser(true);
-   job.schedule();
-</pre>
-<h3>Workbench jobs</h3>
-<p>
-Where possible, long running operations should be performed outside of
-the UI thread. However, this cannot always be
-avoided when the operation's purpose is to update the UI. <a
- href="swt_threading.htm">SWT threading issues</a> explains
-how this can be done using the SWT <b><a
- href="../reference/api/org/eclipse/swt/widgets/Display.html"> Display</a></b>.
-The workbench defines a special job, <a
- href="../reference/api/org/eclipse/ui/progress/UIJob.html"><b>UIJob</b></a>,
-whose run method runs inside an SWT <tt>asyncExec</tt>. Subclasses of <a
- href="../reference/api/org/eclipse/ui/progress/UIJob.html"><b>UIJob</b></a>
-should implement the method <b>runInUIThread</b> instead of the <b>run</b>
-method.
-</p>
-<p>
-<a href="../reference/api/org/eclipse/ui/progress/WorkbenchJob.html"><b>WorkbenchJob</b></a>
-extends
-<a href="../reference/api/org/eclipse/ui/progress/UIJob.html"><b>UIJob</b></a>
-so that the job can only be scheduled or run when the workbench is running.
-As always, you should avoid excessive work in the UI thread because the UI will
-not refresh for the duration of the UI Job.
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm
deleted file mode 100644
index d558416..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menupaths.htm
+++ /dev/null

@@ -1,338 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Menu and toolbar paths
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Menu and toolbar paths</h2>
-<P >
-We've seen many action contributions that specify the path for the location of their action. Let's take a close look at what these paths mean.&nbsp;&nbsp;</P>
-
-<h3 >
-Menu paths</h3>
-
-<P >
-We'll look at menu paths first by looking at the workbench <b>Help</b> menu.</P>
-
-<H4>
-Named groups in the workbench</H4>
-<P >
-The locations for inserting new menus and menu items are defined using named groups. You can think of
-a named group as a slot or placeholder that allows you to insert your menu items
-at certain points in a menu bar or pulldown menu.</P>
-<P >
-The workbench defines all of its group slot names in the classes <b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>
-and <b><a href="../reference/api/org/eclipse/ui/ide/IIDEActionConstants.html">IIDEActionConstants</a></b>. 
-(Two different classes are used since resource-related menu items are factored out of the generic workbench).
-For each workbench menu, named groups are placed in the menu at locations where it is expected that
-plug-ins will insert new actions.</P>
-<P >
-The following description of the help menu is adapted from the <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b> IWorkbenchActionConstants</b></a>
-class definition.</P>
-<pre>
-   Standard Help menu actions
-   Start group - HELP_START - &quot;start&quot;
-   End group - HELP_END - &quot;end&quot;
-</pre>
-<P >
-The standard workbench help menu defines a named group called &quot;<b>start</b>,&quot; followed by a named group called &quot;<b>end</b>,&quot;.
-Defining two groups gives plug-ins a little more control over where their contributed
-items will be positioned within the help menu.&nbsp; When you define a menu, you can define as many slots as you like. Adding more slots gives 
-other plug-ins more control over where their contributions appear relative to existing contributions. </P>
-<P >
-Plug-ins that add a menu item to the help menu can use these group names to decide where their
-menu item will go.  For example, the cheatsheet plug-in adds an action
-set containing the &quot;Cheat Sheets...&quot; menu to the workbench.&nbsp; Here's
-the markup from the <b>org.eclipse.ui.cheatsheets</b> plug-in's
-<b>plugin.xml</b>. </P>
-<pre>
-&lt;extension
-	point="org.eclipse.ui.actionSets"&gt;
-	&lt;actionSet
-		label="%CHEAT_SHEETS"
-		visible="true"
-		id="org.eclipse.ui.cheatsheets.actionSet"&gt;
-		&lt;action
-			label="%CHEAT_SHEETS_MENU"
-			class="org.eclipse.ui.internal.cheatsheets.actions.CheatSheetHelpMenuAction"
-			<b>menubarPath="help/helpStart"</b>
-			id="org.eclipse.ui.cheatsheets.actions.CheatSheetHelpMenuAction"&gt;
-		&lt;/action&gt;
-	&lt;/actionSet&gt;
-&lt;/extension&gt;
-</pre>
-<P >
-The new help action will be placed in the help menu, inside the <b>helpStart</b> group.</P>
-
-
-<H4>
-Fully qualified menu paths</H4>
-<P >
- A complete menu path is simply &quot;menu name/group
- name.&quot;&nbsp; Most menu names for the workbench are defined in
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>. 
-(Resource-related menu names are defined in <b><a href="../reference/api/org/eclipse/ui/ide/IIDEActionConstants.html">IIDEActionConstants</a></b>.)
-If we look for the name of the help menu in this class, we'll find
-that the fully qualified path name for our help action is
- &quot;<b>help/helpEnd</b>.&quot; </P>
-<P >
-Some menus have nested submenus. This is where longer paths come into play. If the help menu had defined a submenu 
-called &quot;<b>submenu</b>&quot; with a named group called &quot;<b>submenuStart</b>,&quot; 
-then the fully qualified menu path for an action in the new submenu would be 
-&quot;<b>help/submenu/submenuStart</b>.&quot;</P>
-
-
-<H4>
-<a name="workbench_menus_nls">
-Externalizing UI labels</a></H4>
-<p>The example above demonstrates a technique for externalizing strings
-that appear in the UI.&nbsp; Externalized strings are used to make translating the plug-in's UI to
-other languages simpler.&nbsp; We can externalize the strings in our <b>plugin.xml
-</b>files by replacing the string with a key (<b>%CHEAT_SHEETS_MENU</b>) and creating entries in the <b>plugin.properties</b>
-file of the form:</p>
-<pre>
-	CHEAT_SHEETS_MENU = Cheat Sheets...
-</pre>
-<P >
-The <b>plugin.properties</b> file can be
-translated for different languages and the <b>plugin.xml</b>
-will not need to be modified.</P>
-
-
-<H4>
-Adding new menus and groups</H4>
-<P >
-In many of the examples we've seen so far, the actions contributed by the sample plug-ins have been added to existing named groups within menus.</P>
-<P >
-The <b><a href="../reference/extension-points/org_eclipse_ui_menus.html">menus</a></b> extension point
-allows you to contribute to your menus using an alternative placement syntax, menu ids.
-The <b><a href="../reference/extension-points/org_eclipse_ui_actionSets.html">actionSets</a></b>,
-<b><a href="../reference/extension-points/org_eclipse_ui_viewActions.html">viewActions</a></b>,
-<b><a href="../reference/extension-points/org_eclipse_ui_editorActions.html">editorActions</a></b>, and
-<b><a href="../reference/extension-points/org_eclipse_ui_popupMenus.html"> popupMenus</a></b> extension points also allow you to define new menus and groups within your contribution. This means that you can define new submenus or new
-pull-down menus and contribute your actions to these new menus. In this case, the path for your new action will contain the name of your newly defined menu. </P>
-<P>
-We saw this technique when the readme tool defined a new menu for its action
-set.&nbsp; Let's look at the markup one more time now that we've looked at menu
-paths in more detail. </P>
-<pre>
-   &lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-   &lt;actionSet id=&quot;org_eclipse_ui_examples_readmetool_actionSet&quot;
-	   label=&quot;%ActionSet.name&quot;
-	   visible=&quot;true&quot;&gt;
-	   &lt;<b>menu id=&quot;org_eclipse_ui_examples_readmetool&quot;</b>
-		   label=&quot;%ActionSet.menu&quot;
-		   <b>path=&quot;window/additions&quot;</b>&gt; 
-		   &lt;separator name=&quot;slot1&quot;/&gt;
-		   &lt;separator name=&quot;slot2&quot;/&gt;
-		   &lt;separator name=&quot;slot3&quot;/&gt;
-	   &lt;/menu&gt;
-	   &lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeAction&quot;
-		   <b>menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;</b>
-		   toolbarPath=&quot;readme&quot;
-		   label=&quot;%ReadmeAction.label&quot;
-		   tooltip=&quot;%ReadmeAction.tooltip&quot;
-		   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-		   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-		   class=&quot;org.eclipse.ui.examples.readmetool.WindowActionDelegate&quot;
-		   enablesFor=&quot;1&quot;&gt;
-		   &lt;selection class=&quot;org.eclipse.core.resources.IFile&quot;
-				name=&quot;*.readme&quot;&gt;
-		   &lt;/selection&gt;
-	   &lt;/action&gt;
-	   ...
-</pre>
-<P >We added a new menu called&nbsp; &quot;<b>org_eclipse_ui_examples_readmetool</b>&quot;
-whose label is defined in by the key &quot;<b>%ActionSet.name</b>&quot; in the
-properties file. Within this menu, we define three named
-groups:&nbsp; &quot;<b>slot1</b>,&quot; &quot;<b>slot2</b>,&quot;
-and &quot;<b>slot3</b>.&quot;&nbsp; We add this new
-menu to the path &quot;<b>window/additions</b>.&quot;</P>
-<P >If we go back to <b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>,
-we see this definition of the window menu in the javadoc:</P>
-<pre>
-    * &lt;h3&gt;Standard Window menu actions&lt;/h3&gt;
-    * &lt;ul&gt;
-    * &lt;li&gt;Extra Window-like action group (&lt;code&gt;WINDOW_EXT&lt;/code&gt;)&lt;/li&gt; 
-</pre>
-<P >
-If we look further at the class definition, we will see these related
-definitions: </P>
-
-
-<pre>
-   public static final String MENU_PREFIX = &quot;&quot;;
-   ...
-   public static final String M_WINDOW = MENU_PREFIX+&quot;window&quot;;
-   ...
-   public static final String MB_ADDITIONS = &quot;additions&quot;;  // Group.
-   ...
-   public static final String WINDOW_EXT = MB_ADDITIONS;   // Group.
-</pre>
-
-
-<P >
-From this information, we can piece together the path for adding something to
-the workbench &quot;Window&quot; menu.&nbsp; The menu itself is called &quot;<b>window</b>&quot;
-and it defines one slot called &quot;<b>additions</b>.&quot;&nbsp;
-We use the path &quot;<b>window/additions</b>&quot; to
-add our new menu. </P>
-
-
-<P >
-In the action set declaration, we add an action to our newly defined menu, using
-the path &quot;<b>window/org_eclipse_ui_examples_readmetool/slot1</b>.&quot; </P>
-
-
-<P >
-<img src="images/readmeactionsetmenu.png" alt="" border="0"> </P>
-
-
-<P >Other plug-ins could add to our menu by using this same path (or perhaps one
-of the other slots) to add one of their own menus.&nbsp;&nbsp; </P>
-
-
-<P >In the readme tool example, we use the <b>separator</b> attribute to
-identify the group names.&nbsp; This will cause a separator line to appear
-between these groups when they contain items.&nbsp; We could instead use the <b>groupMarker</b>
-attribute if we want to define a named group without showing any separators in
-the menu to distinguish between the groups. </P>
-
-
-<h3 >Tool bar paths </h3>
-
-
-<p>Tool bar paths work similarly to menu paths.&nbsp;&nbsp;</p>
-
-
-<h4>Named tool bars in the workbench</h4>
-
-
-<p>The workbench tool bar is composed of
-tool bars contributed by different plug-ins, including the workbench
-itself.&nbsp; Within any particular tool bar, there are named groups or slots that can be used for inserting new tool bar items.
-&nbsp;&nbsp;&nbsp;</p>
-<P >
-The following description of the workbench tool bars is adapted from the <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b> IWorkbenchActionConstants</b></a>
-class definition.</P>
-<pre>// Workbench toolbar ids
-public static final String TOOLBAR_FILE = &quot;org.eclipse.ui.workbench.file&quot;
-public static final String TOOLBAR_NAVIGATE = &quot;org.eclipse.ui.workbench.navigate&quot;; 
-
-// Workbench toolbar group ids.  To add an item at the beginning of the group, 
-// use the GROUP id.  To add an item at the end of the group, use the EXT id.
-public static final String PIN_GROUP = &quot;pin.group&quot;; 
-public static final String HISTORY_GROUP = &quot;history.group&quot;; 
-public static final String NEW_GROUP = &quot;new.group&quot;; 
-public static final String SAVE_GROUP = &quot;save.group&quot;; 
-public static final String BUILD_GROUP = &quot;build.group&quot;; </pre>
-<p>In the simplest case, a plug-in can contribute a tool bar item in its own
-tool bar.&nbsp; For example, the readme tool actions contributed to the menu are
-also given a tool bar path:  </p>
-<pre>
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeAction&quot;&nbsp;&nbsp;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-&nbsp;&nbsp; <b>toolbarPath=&quot;readme&quot;
-</b>...</pre>
-<p>Since there is no reference to the workbench tool bar paths or groups, the
-readme actions appear in their own group on the tool bar.&nbsp; Specifying the
-following path would instead place the item in the file tool bar in the save
-group:</p>
-<pre>...
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeAction&quot;&nbsp;&nbsp;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-&nbsp;&nbsp; <b>toolbarPath=&quot;org.eclipse.ui.workbench.file/save.group&quot;
-</b>...</pre>
-<p>The paths defined in <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b> IWorkbenchActionConstants</b></a>
- may be referenced in the tool bar paths of other plug-ins.</p>
-<h4>Adding to action sets of another plug-in</h4>
-<p>Suppose a plug-in wants its tool bar items better integrated with actions
-from a different plug-in?&nbsp; Let's look at how the external
-tools plug-in (<b>org.eclipse.ui.externaltools</b>) integrates its action with the debugger tool bar.&nbsp; The
-debugger (<b>org.eclipse.debug.ui</b>) defines its tool bar actions like this:</p>
-<pre>&lt;extension
-      point=&quot;org.eclipse.ui.actionSets&quot;&gt;
-   &lt;actionSet
-         label=&quot;%LaunchActionSet.label&quot;
-         visible=&quot;false&quot;
-         id=&quot;org.eclipse.debug.ui.launchActionSet&quot;&gt;
-   ...
-   &lt;action
-         <b>toolbarPath=&quot;debug&quot;</b>
-         id=&quot;org.eclipse.debug.internal.ui.actions.RunDropDownAction&quot;
-         hoverIcon=&quot;icons/full/ctool16/run_exc.png&quot;
-         class=&quot;org.eclipse.debug.internal.ui.actions.RunToolbarAction&quot;
-         disabledIcon=&quot;icons/full/dtool16/run_exc.png&quot;
-         icon=&quot;icons/full/etool16/run_exc.png&quot;
-         helpContextId=&quot;run_action_context&quot;
-         label=&quot;%RunDropDownAction.label&quot;
-         pulldown=&quot;true&quot;&gt;
-   &lt;/action&gt;
-   ...</pre>
-<p>Just like the readme tool, the debugger plug-in defines its own tool bar
-path, which means its tool bar items will be inside their own tool bar on the
-workbench.&nbsp; What does the external tools plug-in do?</p>
-<pre>&lt;extension point=&quot;org.eclipse.ui.actionSets&quot;&gt;
-	&lt;actionSet
-		id=&quot;org.eclipse.ui.externaltools.ExternalToolsSet&quot;
-		label=&quot;%ActionSet.externalTools&quot;
-		visible=&quot;true&quot;&gt;
-		...
-		&lt;action
-			id=&quot;org.eclipse.ui.externaltools.ExternalToolMenuDelegateToolbar&quot;
-			definitionId= &quot;org.eclipse.ui.externaltools.ExternalToolMenuDelegateToolbar&quot;
-			label=&quot;%Action.externalTools&quot;
-			<b>toolbarPath=&quot;org.eclipse.debug.ui.launchActionSet/debug&quot;</b>
-			disabledIcon=&quot;icons/full/dtool16/external_tools.png&quot;
-			icon=&quot;icons/full/etool16/external_tools.png&quot;
-			hoverIcon=&quot;icons/full/ctool16/external_tools.png&quot;
-			tooltip=&quot;%Action.externalToolsTip&quot;
-			pulldown=&quot;true&quot;
-			class=&quot;org.eclipse.ui.externaltools.internal.menu.ExternalToolMenuDelegate&quot;&gt;
-		&lt;/action&gt;
-	&lt;/actionSet&gt;
-&lt;/extension&gt;</pre><p>Note the use of the action set ID of the
-debugger in the tool bar path.&nbsp; Using an action set ID in the path denotes
-that the tool bar item should be placed in the tool bar used by the referenced
-action set.&nbsp;  Within a toolbar group, items are ordered by action set id, so
-for our example, the external tools action will appear after the debugger actions.&nbsp;</p>
-<p>When adding to an action set's tool bar, new groups can also be defined.&nbsp;
-If the external tools plug-in defined its <b> toolbarpath</b> as 
-<b>&quot;org.eclipse.debug.ui.launchActionSet/external&quot;</b> a new group would be created 
-for the action on the tool bar.&nbsp;  As with menus, tool bar groups are delineated by separators.&nbsp;</p>
-<h3 >Using paths from another plug-in </h3>
-
-
-<P >In general, it's not good practice to contribute to another plug-in's menu
-or tool bar by deriving the path name from the <b>plugin.xml</b> unless it has
-been marked specifically as being available for clients.&nbsp; It's possible that a future version of the plug-in could change the names of the
-paths.&nbsp; Two common ways to mark your plug-in's action set ids and paths as
-fair game are: </P>
-
-
-<ul>
-  <li>annotate the XML with comments that explicitly mark the menu path or
-    action set as usable by clients</li>
-  <li>define a public interface (much like <b><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html">IWorkbenchActionConstants</a></b>)
-which specifies exactly which menus, tool bar groups, and slots are considered
-fair game for use by other plug-ins</li>
-</ul>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm
deleted file mode 100644
index 0369829..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_menus.htm
+++ /dev/null

@@ -1,150 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench menu contributions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workbench menu contributions</H2>
-<P >
-We've seen several different extension points that contribute to various menus and toolbars in the workbench. How do you know which one to use? The following table summarizes the various menu contributions and their use.</P>
-<TABLE BORDER="1" width="671">
-<TR>
-<TH ROWSPAN="1" COLSPAN="1" width="118">
-<P CLASS="CellHeading">
-Extension point name</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="359">
-<P CLASS="CellHeading">
-Location of Actions</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="335">
-<P CLASS="CellHeading">
-Details</P>
-</TH>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-viewActions</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions appear in a specific view's local toolbar and local pulldown menu.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Contribute an action class that implements <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html">IViewActionDelegate</a></b>. Specify the id of the contribution and the id of the target view that should show the action. The label and image
-dictate the appearance of the action in the UI. The path specifies the location relative to the view's menu and toolbar items.</P>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody"><b>editorActions</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions are associated with an editor and appear in the workbench menu and/or tool bar.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Contribute an action class that implements <b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>. Specify the id of the contribution and the id of the target editor that causes the action to be shown. The label and image specify the appearance of the action in the UI. Separate menu and toolbar paths specify the existence and location of the contribution in the workbench menu and toolbar.</P>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-popupMenus</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions appear in the popup menu of an editor or view. Actions associated with an object type show up in all popups of views
-and editors that show the object type. Actions associated with a specific popup menu appear only in that popup menu.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-<b>
-Object contributions</b> specify the type of object for which the action should appear in a popup menu. The action will be shown in all view
-and editor popups
-that contain the object type.&nbsp; Provide an action class that implements <b><a href="../reference/api/org/eclipse/ui/IObjectActionDelegate.html">IObjectActionDelegate</a></b>.&nbsp;<BR>
-<b>
-Viewer contributions</b> specify the id of the target popup menu in which the menu item should appear.&nbsp;
-Provide an action class that implements <b><a href="../reference/api/org/eclipse/ui/IEditorActionDelegate.html">IEditorActionDelegate</a></b>
-or <b><a href="../reference/api/org/eclipse/ui/IViewActionDelegate.html">IViewActionDelegate</a></b>.&nbsp;</P>
-</TD>
-</TR>
-<TR>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-actionSets</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Actions appear in the workbench main menus and toolbar. Actions are grouped into action sets. All actions in an action set will show up in the workbench menus and toolbars according to the user's selection of action sets
-and the current perspective shown in the workbench.&nbsp; May be influenced by
-actionSetPartAssociations (below).</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Contribute an action class that implements <b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowActionDelegate.html"> IWorkbenchWindowActionDelegate</a></b> or
-<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindowPulldownDelegate.html">IWorkbenchWindowPulldownDelegate</a></b>. Specify the
-<b> name</b> and <b> id</b> of the action set. Enumerate all of the actions that are defined for that action set. For each action, separate menu and toolbar paths specify the existence and location of the contribution in the workbench menu and toolbar.</P>
-</TD>
-</TR>
-<tr>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-actionSetPartAssociations</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody"> Actions sets are shown only when the specified views or
-editors are active.&nbsp; This is ignored if the user has customized the current
-perspective.</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-Specify an action set by <b>id</b> and followed by one or more parts (by <b>id</b>)
-that must be active in the current perspective in order to show the action set.</P>
-</TD>
-</tr>
-<TR>
-<TD width="118">
-<P CLASS="CellBody">
-<b>
-menus</b></P>
-</TD>
-<TD width="359">
-<P CLASS="CellBody">
-Commands can be placed in all of the locations covered by the 4 main action
-extension points, plus other trim areas.
-</P>
-</TD>
-<TD width="335">
-<P CLASS="CellBody">
-The extension point should be used to place commands in menus and toolbars 
-so they can be executed by the user.
-</P>
-</TD>
-</TR>
-</TABLE>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
deleted file mode 100644
index 9f9a75f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_perspectives.htm
+++ /dev/null

@@ -1,181 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Perspectives</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Perspectives</h2>
-<P >
-We've already seen some ways the workbench allows the user to control the appearance of plug-in functionality. Views can be hidden or shown using the
-<b>Window &gt;Show View</b> menu. Action sets can be hidden or shown using the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Customize Perspective...</b></a>
-
-menu. These features help the user organize the workbench. </P>
-
-<P >
-<b>
-Perspectives</b> provide an additional layer of organization inside a workbench
-window. Users can switch between perspectives as they move across tasks. A perspective defines
-a collection of views, a layout for the views, and the visible action sets that
-should be used when the user first opens the perspective.</P>
-<P >
-Perspectives are implemented using&nbsp; <b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a>.&nbsp;
-</b>Implementors of
-<b><a href="../reference/api/org/eclipse/ui/IPerspectiveFactory.html">IPerspectiveFactory</a></b>
-are expected to configure an <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b> with information that describes the
-perspective and its perspective page layout.</P>
-
-
-<h3>
-Workbench part layout</h3>
-<P >
-One of the main jobs of an <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>
-is to describe the placement of the editor and the views in the workbench window. Note that these layouts are different than the
-<a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><b> Layout</b></a> class in SWT. Although
-<b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>
-and <a href="../reference/api/org/eclipse/swt/widgets/Layout.html"><b> Layout</b></a>
-solve a similar problem (sizing and positioning widgets within a larger area), you do not have to understand SWT layouts in order to supply a
-perspective page layout.</P>
-<P >
-A perspective page layout is initialized with one area for displaying an editor. The perspective factory is responsible for adding additional views relative to the
-editor. Views are added to the layout relative to (top, bottom, left, right) another part. Placeholders (empty space) can also be added for
-items that are not initially shown.</P>
-<P >
-To organize related views and reduce clutter, you can use <a href="../reference/api/org/eclipse/ui/IFolderLayout.html"><b>IFolderLayout</b></a> to group views into tabbed folders. For example, the Resource perspective
-places the Project Explorer inside a folder at the top left corner of the
-workbench.&nbsp; Placeholders are commonly used with folder layouts.
-The Resource perspective defines a placeholder for the Bookmarks view in the
-same folder as the Project Explorer. If the user shows the Bookmarks view, it will appear in the same folder with the
-Project Explorer, with a tab for each view.</P>
-<P >
- <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>
-also allows you to define the available actions and shortcuts inside a
-perspective.&nbsp;&nbsp; </P>
-
-
-
-<ul>
-  <li><b>addActionSet</b> is used to add action sets to a perspective.&nbsp;&nbsp;</li>
-  <li><b>addNewWizardShortcut</b> adds a new entry to the <b>File &gt;New</b> menu for a perspective.</li>
-  <li><b>addShowViewShortcut</b> adds the names of
- views that should appear in the <b>Window &gt;Show View</b>  menu when the
- perspective is active.&nbsp;&nbsp;</li>
-  <li><b>addPerspectiveShortcut</b> adds the names of
- perspectives that should appear in the <b>Window &gt;Open Perspective</b> menu when
- the perspective is active.</li>
-</ul>
-
-
-
-<h3>
-<a name="showin">
-Linking views and editors</a> with &quot;show-in&quot;</h3>
-
-
-
-<p>
-Another valuable service provided by perspectives and the <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a>
-</b>
-is to aid in navigation between an editor and its related views.&nbsp; We
-typically think of views as helping the user find the objects to work with in
-editors.&nbsp; However, the converse operation is also useful:&nbsp; a user
-working with an object in an editor may need to navigate to that object inside a
-view.&nbsp; This can be accomplished using the workbench <b>Navigate &gt; Show
-In</b> menu.&nbsp; This command allows the user to jump to one of any number of
-related views in the context of the currently edited (or selected) object.&nbsp;
-For example, a user editing a file may want to jump over to that file in the
-Project Explorer.</p>
-
-
-
-<p>
-The plug-in architecture of the workbench allows developers to contribute views
-and editors in different plug-ins that are not even aware of each other.&nbsp;
-By implementing support for &quot;show in,&quot; your view or editor can support
-convenient navigation to or from the views and editors contributed by other
-plug-ins.&nbsp; </p>
-
-
-
-<p>
-This navigation allows users to move quickly between views and to easily open a
-view that is not usually shown in a particular perspective.&nbsp; For example, a
-user working in the Java perspective can use <b>Navigate &gt; Show
-In</b>  to view the currently edited Java file in the Navigator view. </p>
-
-
-
-<h4>
-Show-in source</h4>
-<p>If you want to allow users to use <b>Navigate &gt; Show In</b> from your
-editor or view to jump to another view, you must implement <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>.&nbsp;
-Your part can supply its <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>
-directly using protocol (<b>getShowInSource()</b>) or as an adapter.&nbsp; <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>
-allows your part to supply a context (<a href="../reference/api/org/eclipse/ui/part/ShowInContext.html"><b>ShowInContext</b></a>)
-which is used by the target to decide how to show the source.&nbsp; The show in
-context for an editor is typically its input element.&nbsp; For a view, the
-context is typically its selection.&nbsp; Both a selection and an input element
-are provided in a <a href="../reference/api/org/eclipse/ui/part/ShowInContext.html"><b>ShowInContext</b></a>
-to give the target flexibility in determining how to show the source.&nbsp;</p>
-
-
-
-<p>A default context for editors is provided, so that your editor can
-participate in &quot;show-in&quot; without any special coding.&nbsp; For
-editors, the input element and selection are used to create an appropriate
-context.&nbsp;</p>
-
-
-
-<p>For views, <a href="../reference/api/org/eclipse/ui/part/IShowInSource.html"><b>IShowInSource</b></a>
-must be implemented by the view in order to offer <b>Navigate &gt; Show In</b>
-functionality.</p>
-
-
-
-<h4>
-Show-in target</h4>
-
-
-
-<p>You must implement <a href="../reference/api/org/eclipse/ui/part/IShowInTarget.html"><b>IShowInTarget</b></a>
-if you want your view to be a valid target for a &quot;show in&quot;
-operation.&nbsp; The target is responsible for showing a given context in a
-manner appropriate for its presentation.&nbsp; For example, the Navigator view
-expands its tree to select and reveal a resource specified in the
-context.&nbsp;&nbsp;</p>
-<p>A target should check the selection in the <a href="../reference/api/org/eclipse/ui/part/ShowInContext.html"><b>ShowInContext</b></a>
-first in deciding what to show, since this is the more specific
-information.&nbsp; It should show the input element only if no selection is
-indicated.</p>
-<h4>Presenting appropriate targets</h4>
-
-
-
-<p>How is the list of available targets determined?&nbsp; You can specify the
-available targets for your perspective in its <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html"> IPageLayout</a></b>.&nbsp;
-Recall that a &quot;show in&quot; navigation may open a view that is not already
-present in the perspective.&nbsp; Using <b><a href="../reference/api/org/eclipse/ui/IPageLayout.html">IPageLayout</a>.addShowInPart</b>,
-you can specify a valid &quot;show in&quot; target by id.&nbsp; In this way, the
-valid targets can be established without unnecessarily creating any views. </p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm
deleted file mode 100644
index 26b8088..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_plugin.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-The plug-in class
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-The plug-in class</H2>
-<P >
-So far, we've been looking at the different extensions that are provided by the readme tool. Let's look at the general 
-definition of the readme tool plug-in.</P>
-
-<H3>
-Plug-in definition</H3>
-<P >
-The readme tool plug-in is defined in the <b>MANIFEST.MF</b> file.</P>
-<pre>
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %Plugin.name
-Bundle-SymbolicName: org.eclipse.ui.examples.readmetool; singleton:=true
-Bundle-Version: 3.3.0.qualifier
-Bundle-ClassPath: readmetool.jar
-Bundle-Activator: org.eclipse.ui.examples.readmetool.ReadmePlugin
-Bundle-Vendor: %Plugin.providerName
-Bundle-Localization: plugin
-Require-Bundle: org.eclipse.ui,
- org.eclipse.core.resources,
- org.eclipse.core.runtime,
- org.eclipse.ui.views,
- org.eclipse.ui.ide,
- org.eclipse.jface.text,
- org.eclipse.text,
- org.eclipse.ui.workbench.texteditor,
- org.eclipse.ui.editors
-Eclipse-AutoStart: true
-Eclipse-AutoStart-comment: Use Eclipse-AutoStart instead of Eclipse-LazyStart because the readme example should run against 3.1 as well as 3.2.
-</pre>
-<P >
-The plug-in definition includes the <b>Bundle-Name</b>, <b>Bundle-SymbolicName</b> (plug-in id),
-<b>Bundle-Version</b>, and <b>Bundle-Vendor</b> of the plug-in. We 
-saw most of these parameters before in our hello world plug-in. The readme tool also defines a specialized plug-in class,
-<b>ReadmePlugin</b>. </P>
-<P >
-The name of the jar file is also provided. File names specified in <b>Bundle-ClassPath</b> are relative to the
-plug-in's directory, so the readme tool's jar file should be located directly in the plug-in's directory.</P>
-<P >
-The <b>Require-Bundle</b> element informs the platform of the readme tool's dependencies. 
-The workbench UI plug-ins are listed as required plug-ins, along with the various core, jface, and text plug-ins.  </P>
-
-<H3>
-AbstractUIPlugin</H3>
-<P >
-The<b> ReadmePlugin</b> class represents the readme
-tool plug-in and manages the life cycle of the plug-in.&nbsp; As we saw in the
-Hello World example, you don't have to specify a plug-in class.&nbsp; The
-platform will provide one for you.&nbsp; In this case, our plug-in needs to
-initialize UI related data when it starts up.&nbsp; The platform class <a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a>
-provides a structure for managing UI resources and is extended by <b>
-ReadmePlugin</b>.</P>
-<P >
-<a href="../reference/api/org/eclipse/ui/plugin/AbstractUIPlugin.html"><b>AbstractUIPlugin</b></a>
- uses the generic startup and shutdown methods to manage images, dialog settings, and a preference store during the lifetime of the plug-in.&nbsp;
-We'll look at the specifics of the <b>ReadmePlugin</b> class when we work with dialogs and preferences.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
deleted file mode 100644
index 7f75158..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_resources.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Workbench resource support</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Workbench resource support</h2>
-<P>
-The Eclipse platform is structured so that you can develop a workbench application even if your application
-has nothing to do with the platform resource model.  However, the workbench does provide support for
-working with resources in a separate plug-in, <b>org.eclipse.ui.ide</b>.  This plug-in contains the
-parts of the SDK workbench that focus on IDE building and manipulating the workspace.
-</p>
-<p>
-If your plug-in uses the platform resource model, you may want to take advantage of the resource-oriented
-features in the workbench.  These include resource property pages, resource marker UI, resource filtering, 
-and other utilities.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
deleted file mode 100644
index 71d2218..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_scalability.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>Filtering large user interfaces</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>
-Filtering large user interfaces</h2>
-<P>
-The rich extensibility mechanisms in the workbench provide many ways for plug-ins to contribute to the platform
-UI.  However, extensibility can introduce its own set of problems.  While allowing for a rich set of features
-contributed by many different developers, it can also create an overwhelming experience for the new user who is
-trying to navigate through vast menus and preferences pages.  As the Eclipse platform matures, the need for
-filtering mechanisms that help reduce the UI clutter and guide the user to their desired tasks has become apparent.
-</P>
-<p>
-The activity and context mechanisms address the problem of too much clutter in the user interface:
-</p>
-<ul>
-<li><a href="../reference/extension-points/org_eclipse_ui_activities.html">
-<b>Activities</b></a>
-allow platform integrators to define large-grained groupings of function that are only
-shown when a particular user activity is enabled. Users can explicitly (or implicitly through trigger points)
-enable or disable activities.</li>
-<li><a href="../reference/extension-points/org_eclipse_ui_contexts.html">
-<b>Contexts</b></a> are used to dynamically enable function while the user is performing a specific task.
-They influence what commands are available to the user at any given moment.</li>
-</ul>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm
deleted file mode 100644
index 634042a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling.htm
+++ /dev/null

@@ -1,186 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Status handling</title>
-</head>
-<body>
-
-<h2>Status handling</h2>
-
-Status handling is a facility that allows to introduce a custom way of showing problems 
-in the Eclipse based applications to users. The facility can be configured at both 
-the application and the product level.
-
-<h3><a name="statusHandlers">Status handlers</a></h3>
-
-<p>
-The handlers are responsible for presenting problems by logging or showing appropriate 
-feedback to the user (generally dialogs). 
-</p>
-
-<p>
-All status handlers extend <em>org.eclipse.ui.statushandlers.AbstractStatusHandler</em> 
-which requires each handler to implement <em>handle(StatusAdapter status, int style)</em>. 
-This method handles statuses based on a handling style. The style indicates how status 
-handler should handle a status. See <a href="#acceptableStyles">Acceptable styles</a>.
-</p>
-
-<p>
-There are two ways for contributing handlers to the Workbench:</p>
-<ol>
-	<li>
-    	using the <em>org.eclipse.ui.statusHandlers</em> extension point, see 
-    	<a href="ua_statushandling.htm">User assistance and status handling</a>
-    </li><li>
-    	using the workbench advisor and its method <em>WorkbenchAdvisor#getWorkbenchErrorHandler()</em>
-    </li>
-</ol>
-<p><b>NOTE!</b> if there exists a handler associated with the product, it is used instead of the one defined in the advisor.
-</p>
-
-A status handler has an id and a set of parameters. The handler can use them during 
-the handling process. If the handler is added as an extension, both the id 
-and parameter set are set during initialization of the handler with the use of elements 
-and attributes of the <b>statusHandler</b> element. 
-
-<h4>Logging with the use of the default logging mechanism</h4>
-
-<p>
-In order to log extra information with the use of the default logging mechanism, 
-it is necessary to perform some additional steps. The status manager provides you 
-with an API that allows you to hook into the mechanism.</p>
-
-<pre>
-   StatusManager#addLoggedStatus(IStatus status)
-</pre>
-
-
-<p>
-And below is the example of <em>addLoggedStatus(IStatus status)</em> proper usage.</p>
-
-<pre>
-   public void handle(final StatusAdapter statusAdapter, int style) {
-      ...
-   
-      if ((style &amp; StatusManager.LOG) == StatusManager.LOG) {
-         StatusManager.getManager().addLoggedStatus(statusAdapter.getStatus());
-         WorkbenchPlugin.getDefault().getLog().log(statusAdapter.getStatus());
-      }
-   }
-</pre>
-
-
-<h4>The default status handler</h4>
-
-<p>
-The platform supplies its own status handler implementation <em>org.eclipse.ui.statushandlers.WorkbenchErrorHandler</em>.
-It respects all <a href="#acceptableStyles">acceptable styles</a>. It uses the default logging mechanism
-and a dialog based on the JFace <em>org.eclipse.jface.dialogs.ErrorDialog</em>.
-</p>
-
-<h4>Registering the ErrorSupportProvider with your status handler</h4>
-
-<p>
-There is a simple way to contribute a support area in the JFace <em>ErrorDialog</em>. 
-It is the <em>ErrorSupportProvider</em> which can be set in the JFace policy. Because the default workbench handler 
-uses a subclass of the <em>ErrorDialog</em> for its dialog, setting the provider on the JFace policy 
-will affect this dialog as well.
-</p>
-
-<p>
-When a handler like the one below is created</p>
-
-<pre>
-   public class CustomStatusHandler extends WorkbenchErrorHandler {
-      public CompanyStatusHandler() {
-         ErrorSupportProvider provider = createSupportProvider();
-         Policy.setErrorSupportProvider(provider);
-      }
-	
-      private ErrorSupportProvider createSupportProvider() {
-         ...
-      }
-   }
-</pre>
-<p>
-and is contributed to the Workbench in one of two available ways, all dialogs based on
-the <em>ErrorDialog</em> including the one shown by the default handler, will have an extra 
-support area.
-</p>
-
-<h3>Status manager</h3>
-
-<p>
-The status manager is the entry point for all statuses that are to be displayed in the user interface. 
-Handlers are not intended to be used directly. They should be referenced via the StatusManager 
-which selects the appropriate handler to apply.
-
-The following methods are the API entry points to the StatusManager</p>
-
-<pre>
-   StatusManager#handle(IStatus)
-   
-   StatusManager#handle(IStatus, int)
-   
-   StatusManager#handle(StatusAdapter)
-   
-   StatusManager#handle(StatusAdapter, int)
-</pre>
-
-<p>The StatusManager singleton is accessed using</p>
-
-<pre>
-   StatusManager.getManager()
-</pre>
-<p>
-The int parameters are used for supplying styles for handling. See <a href="#acceptableStyles">Acceptable styles</a>.
-</p>
-
-<p>
-<b>NOTE!</b> the style is only a suggestion and may not be honored by the current handler. 
-For instance a handler may choose not to show the user anything when the SHOW flag is sent. 
-See <a href="#statusHandlers">Status handlers</a> for more details.
-</p>
-
-<p>
-If a handler is associated with a product, it is used instead of the one that was defined in advisor. 
-However because product handler is lazy initialized, an error can occur during the first attempt to access it. 
-If any creation error occurs in the product handler, the workbench handler will process this error. 
-</p>
-
-<h3><a name="acceptableStyles">Acceptable styles</a></h3>
-
-<p>
-Below is a list of StatusManager styles which can be combined with logical OR:</p>
-
-<ol>
-	<li>
-  		<b>NONE</b> - a style indicating that the status should not be acted on. This is used by objects such as log listeners that do not want to report a status twice
-    </li><li>
-    	<b>LOG</b> - a style indicating that the status should be logged only
-    </li><li>
-    	<b>SHOW</b> - a style indicating that handlers should show a problem to a user without blocking the calling method while awaiting user response. This is generally done using a non modal dialog
-    </li><li>	
-    	<b>BLOCK</b> - a style indicating that the handling should block the calling method until the user has responded. This is generally done using a modal window such as a dialog 
-	</li>
-</ol>
-
-<h3><a name="statusAdapter">StatusAdapter</a></h3>
-
-<p>
-The StatusAdapter wraps an instance of IStatus subclass and can hold additional information 
-either by using properties or by adding a new adapter. It is used during status handling process.
-</p>
-
-<p>
-Each handler should specify what properties or types it accepts, being aware of the fact that 
-developers can pass status adapters with such extra information. 
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm
deleted file mode 100644
index 7754b68..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_statushandling_defining.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
-	type="text/css">
-<script language="JavaScript"
-	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Defining a status handler</title>
-</head>
-<body>
-
-<h2>Defining a status handler</h2>
-
-<p>There are two ways for contributing handlers to the Workbench:</p>
-<ol>
-	<li>using the <em>org.eclipse.ui.statusHandlers</em> extension
-	point, see <a href="ua_statushandling.htm">User assistance and
-	status handling</a></li>
-	<li>using a custom workbench advisor and overriding its <em>getWorkbenchErrorHandler()</em> method</li>
-</ol>
-
-
-<h3>Contributing a status handler using the custom advisor</h3>
-
-<p>First, a custom workbench advisor for your application has
-to be created. In this new custom advisor override <em>getWorkbenchErrorHandler()</em>. 
-This will now return the default error handler.</p>
-<pre>
-   public class CustomWorkbenchAdvisor extends WorkbenchAdvisor {
-      public AbstractStatusHandler getWorkbenchErrorHandler() {
-         ...
-         
-         return customStatusHandler;
-      }
-   }
-</pre>
-
-
-<p>In the custom application use your new advisor when creating the
-<code>Workbench</code>.</p>
-<pre>
-   public class CustomApplication implements IApplication{
-      public Object start(IApplicationContext appContext) throws Exception {
-         ...
-         Display display = createDisplay();
-         PlatformUI.createAndRunWorkbench(display, new CustomWorkbenchAdvisor());
-         ...
-      }
-
-      protected Display createDisplay() {
-         return PlatformUI.createDisplay();
-      }
-   }
-</pre>
-
-<p>For details how to run a custom application see the <b><a
-	href="../reference/extension-points/org_eclipse_core_runtime_applications.html">
-org.eclipse.core.runtime.applications</a></b> extension point documentation.</p>
-
-<p>When the status handling facility is accessed, the facility will
-get instance of the handler that is provided by the custom advisor. This handler will be 
-used for handling of status or error occurred in the application.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm b/bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm
deleted file mode 100644
index a6af1c9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/workbench_structure.htm
+++ /dev/null

@@ -1,136 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench under the covers
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H2>
-Workbench under the covers</H2>
-<P >
-The workbench provides an extensive set of classes and interfaces for building complex user interfaces. Fortunately you don't need to understand
-all of them to do something simple. We'll start by looking at some concepts that are exposed in the workbench user interface
-and their corresponding structure under the covers.</P>
-
-<H3>
-Workbench</H3>
-<P >
-We've been using the term <b> workbench</b> loosely to refer to &quot;that window that opens when you start the platform.&quot; Let's drill down a little and look at some of the visual components that make up
-the workbench.</P>
-
-<img src="images/workbench_decomposed.png" alt="Workbench with three views and one editor on a page" border="0">
-<P >
-For the rest of this discussion, when we use the term workbench, we will be referring to the workbench window
-(<b><a href="../reference/api/org/eclipse/ui/IWorkbenchWindow.html">IWorkbenchWindow</a></b>). The workbench window is the top-level window in a workbench. It is the frame that holds the menu bar,
-tool bar, status line, short cut bar, and pages. In general, you don't need to program to the workbench window. You just want to know that it's there.</P>
-<blockquote><i>
-Note:&nbsp; You can open multiple workbench windows; however each workbench window is a self-contained world of editors and views,
-so we'll just focus on a single workbench
-window.</i></blockquote>
-<P >
-From the user's point of view, a workbench contains views and editors. There are a few other classes used to implement the workbench window.&nbsp; </P>
-
-
-
-<H3>
-Page</H3>
-<P >
-Inside the workbench window, you'll find one page (<b><a href="../reference/api/org/eclipse/ui/IWorkbenchPage.html">IWorkbenchPage</a></b>) that in turn contains parts. Pages are an implementation mechanism for grouping parts. You typically don't need to program to the page, but you'll see it in the context of programming and debugging. </P>
-
-
-<h3 >
-Perspectives</h3>
-
-<P >
-Perspectives provide an additional layer of organization inside the workbench
-page.&nbsp; A perspective defines an appropriate collection of views, their
-layout, and applicable actions for a given user task.&nbsp; Users can switch
-between perspectives as they move across tasks.&nbsp;&nbsp; From an
-implementation point of view, the user's active perspective controls which views
-are shown on the workbench page and their positions and sizes.&nbsp; Editors are
-not affected by a change in perspective.</P>
-
-
-<H3>
-<a name="views_and_editors">
-Views and editors</a></H3>
-<P >
-Views and editors are where we move beyond implementation details into some common plug-in programming. When you add a visual component to the workbench, you must decide whether you want to implement a view or
-an editor. How do you decide this?</P>
-<ul>
-  <li>A <b>view</b> is typically used to navigate a hierarchy of information, 
-    open an editor, or display properties for the active editor.&nbsp; For example, 
-    the <b>project explorer</b> view allows you to navigate the workspace hierarchy.&nbsp; 
-    The <b>properties</b> and <b>outline</b> views show information about an object 
-    in the active editor.&nbsp; Any modifications that can be made in a view (such 
-    as changing a property value) are saved immediately.</li>
-  <li>An <b>editor</b> is typically used to edit or browse a document or input
-    object.&nbsp; Modifications made in an editor follow an open-save-close
-    model, much like an external file system editor.&nbsp; The platform text
-    editor and Java editor are examples of workbench editors.</li>
-</ul>
-<P >
-In either case, you will be building your view or editor according to a common lifecycle. </P>
-<ul>
-  <li>
-    
-You implement a <b> createPartControl</b> method to create the SWT widgets that represent your visual component. You must determine which widgets to use and allocate any related UI resources needed to display your view or editor.</li>
-  <li>
-    
-When your view or editor is given focus, you'll receive a <b> setFocus</b> notification so that you can set the focus to the correct widget.</li>
-  <li>
-    
-When the view or editor is closed, you will receive a <b> dispose</b>
- message to signify that the view or editor is being closed.&nbsp; At this point
-the controls allocated in <b>createPartControl</b>
- have already been disposed for you, but you must dispose of any graphics resources (such
-as cursors, icons, or fonts) that you allocated for the view or editor.</li>
-</ul>
-<P >
-Throughout this lifecycle, events will fire from the containing workbench page to notify interested parties about the opening, activation, deactivation, and closing of the
-views and editors.</P>
-<P >
-Seem simple?&nbsp; It can be. That's the beauty of workbench views and editors. They're just widget holders, and can be as simple or complex as you need them to be. We saw the simplest of views earlier when we built a hello world view.
-Let's look at it again now that we've explained more about what's going on.</P>
-<pre>
-   package org.eclipse.examples.helloworld;
-
-   import org.eclipse.swt.widgets.Composite;
-   import org.eclipse.swt.widgets.Label;
-   import org.eclipse.swt.SWT;
-   import org.eclipse.ui.part.ViewPart;
-
-   public class HelloWorldView extends ViewPart {
-      Label label;
-      public HelloWorldView() {
-      }
-      public void createPartControl(Composite parent) {
-         label = new Label(parent, SWT.WRAP);
-         label.setText(&quot;Hello World&quot;);
-      }
-      public void setFocus() {
-         // set focus to my widget.  For a label, this doesn't
-         // make much sense, but for more complex sets of widgets
-         // you would decide which one gets the focus.
-      }
-   }
-</pre>
-<P >
-Notice that we didn't have to implement a <b> dispose()</b> method since we didn't do anything but create a label in the
-<b> createPartControl(parent)</b> method. If we had allocated any UI resources, such as images or fonts, we would have disposed of them here. Since we extended the
-<b><a href="../reference/api/org/eclipse/ui/part/ViewPart.html"> ViewPart</a></b> class, we inherit the &quot;do nothing&quot; implementation of
-<b>dispose()</b>.</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm
deleted file mode 100644
index ae1db45..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Advanced workbench concepts
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>
-Advanced workbench concepts</H1>
-<p>
-<a href="workbench.htm">Plugging into the workbench</a> looks at the basic workbench extension points in the
-context of the readme tool example.  However, there are many more extension points available for contributing to the
-workbench.  
-</p>
-<p>The next topics cover additional workbench extensions and concepts that
-you will likely encounter once you've implemented your plug-in and have begun to
-refine its function.  In order to understand the next few topics, you should already be familiar
-with
-</p>
-<ul>
-  <li><a href="workbench.htm">Plugging into the Workbench</a></li>
-  <li><a href="jface.htm">JFace UI framework</a></li>
-  <li><a href="swt.htm">SWT</a></li>
-  <li><a href="resInt.htm">Resources overview</a></li>
-</ul>
-Since the readme tool does not contribute to all of these extension
-points, we will look at example extensions that are implemented by the platform
-workbench, the platform help system, and Java tooling (JDT).
-<p>When using any of these workbench features, it is a good idea to
-keep the rules of engagement for threading in mind.  See 
-<a href="swt_threading.htm#workbench_threads">The workbench and threads</a> for more information.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
deleted file mode 100644
index 7a6addc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_accessibility.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Accessible user interfaces
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Accessible user interfaces</h2>
-<p>The term accessible is used to refer to software that has been designed so
-that people who have disabilities have a successful interaction with it.&nbsp;
-Accessible software takes many different kinds of disabilities into account:</p>
-
-
-<ul>
-  <li>visual - people with color blindness, low vision, or who are completely
-    blind</li>
-  <li>audio - people who are hard of hearing or are completely deaf</li>
-  <li>mobility - people who have physical impairments that limit their movement
-    and fine motor controls</li>
-  <li>cognitive - people who have learning disabilities and may need more
-    consistency or simplicity in their interfaces</li>
-</ul>
-<h3>Assistive technology</h3>
-<p><b>Assistive technology</b> is equipment or software that is used to increase
-the accessibility of existing operating systems and applications.&nbsp; While it
-is beyond the scope of this programmer's guide to cover the broad scope of
-assistive technologies, it is important for you to know that they exist.&nbsp;
-Why?&nbsp; Because simple things you can do when programming your software or
-documentation, such as providing alternate text descriptions for images in your HTML, or
-keyboard equivalents for all of your software actions, can greatly improve the
-effectiveness of assistive technologies that make use of these techniques.</p>
-<h3>Accessibility resources</h3>
-<p>There are some basic coding tips you can use when building plug-in user
-interfaces that will increase the accessibility of your software.&nbsp; See <a href="../reference/misc/ui_accessibility_tips.html">Tips
-for Making User Interfaces More Accessible</a> for more information.</p>
-<p><a href="http://www-03.ibm.com/able/index.html">IBM's Accessibility Center
-Website</a> has many useful resources for accessibility, including <a href="http://www-03.ibm.com/able/guidelines">guidelines
-and checklists</a> for developing software and web interfaces.</p>
-<h3>SWT and accessibility</h3>
-<p>Because SWT uses the operating system's native widgets, user interfaces built
-with SWT will inherit any assistive technologies that have been installed on the
-host operating system.&nbsp; SWT implements an interface, <a href="../reference/api/org/eclipse/swt/accessibility/AccessibleListener.html"><b>AccessibleListener</b></a>,
-which provides basic accessibility information, such as descriptions of
-controls, help text, and keyboard shortcuts, to clients.&nbsp; If you are
-developing assistive technologies that need more information or want to improve
-upon the basic accessibiliity of the workbench, you can add your own listeners
-and override the default accessibility behavior in the platform.&nbsp; See the
-package <a href="../reference/api/org/eclipse/swt/accessibility/package-summary.html"><b>org.eclipse.swt.accessibility</b></a>
-for more detail.</p>
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm
deleted file mode 100755
index 2851b3c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_commands_handlers.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Commands
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Commands</h3>
-
-
-<p>A <b>command</b> is the declaration of a user action by <b>id</b>.&nbsp;
-Commands are used to declare semantic actions so that action implementations defined
-in action sets and editors can associate themselves with a particular semantic
-command.&nbsp; The separation of the command from the action
-implementation allows multiple plug-ins to define actions that implement the
-same semantic command.&nbsp; The command is what gets associated with a
-particular key binding.</p>
-
-
-<p>The workbench defines many common commands in its <b>plugin.xml</b>
-file, and plug-ins are encouraged to associate their own actions with these
-commands where it makes sense.&nbsp; In this way, semantically similar
-actions implemented in different plug-ins may share the same key binding.</p>
-
-
-<h4>Defining a command</h4>
-
-
-<p>Commands are defined using the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></b>
-extension point.&nbsp; The following comes from the workbench markup:</p>
-
-
-<pre>
-&lt;extension
-	point=&quot;org.eclipse.ui.commands&quot;&gt;
-	...
-	&lt;command
-		name="%command.save.name"
-		description="%command.save.description"
-		categoryId="org.eclipse.ui.category.file"
-		id="org.eclipse.ui.file.save"&gt;
-	&lt;/command&gt;
-	...
-</pre>
-
-
-<p>The command definition specifies a <b>name</b>, <b>description</b>, and <b>id</b> for
-the action.&nbsp;&nbsp; It also specifies the id of a category for the command, which is
-used to group commands in the preferences dialog.&nbsp; The categories are also
-defined in the <b><a href="../reference/extension-points/org_eclipse_ui_commands.html">org.eclipse.ui.commands</a>
-</b>
-extension point:</p>
-<pre>
-      ...
-      &lt;category
-            name=&quot;%category.file.name&quot;
-            description=&quot;%category.file.description&quot;
-            id=&quot;org.eclipse.ui.category.file&quot;&gt;
-      &lt;/category&gt;
-      ...
-</pre><p>Note that there is no implementation specified for a
-command.&nbsp; A command only becomes concrete when a plug-in
-associates its action with the command id.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm
deleted file mode 100644
index 7aa7548..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_efs_resources.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-User interface support for alternative file systems
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>User interface support for alternative file systems</h3>
-
-<p>In environments where there is more than one file system there are several 
-  places in the user interface where the user can select a file system.</p>
-<p>The UI support for additional file systems can be added via the<code> org.eclipse.ui.ide.fileSystemSupport 
-  </code>extension point. The class attribute of these schema must be a<code> 
-  org.eclipse.ui.ide.fileSystem.FileSystemContributor</code> which is used to 
-  supply validation and browsing of the other file systems.</p>
-<p><img src="images/efs-newProject.png" ></p>
-<p><strong>Figure 1. New Project wizard with support for selecting alternative 
-  file systems</strong></p>
-<p>Above is the new Project wizard showing the extra support for multiple file 
-  systems. When more than one <code> org.eclipse.ui.ide.fileSystem.FileSystemContributor</code> 
-  is registered with Eclipse this selection will become available in the file, 
-  folder and simple project wizards.</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
deleted file mode 100644
index 3ae92ea..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_encoding.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Text file encoding
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Text file encoding</h3>
-<p>If your plug-in reads text files, it should honor the <b>text file encoding</b>
-preference in the workbench.&nbsp; </p>
-
-
-<p><img src="images/textencoding.png" alt="text file encoding" border="0"></p>
-
-
-<p>Text files are encoded differently depending on the platform and the
-locale.&nbsp; Most of the time, using the default text file encoding for the
-locale of the host operating system is good enough.&nbsp; However, a user may
-want to work with text files that originate from another source.&nbsp; Given the
-ability to use the platform in a networked team environment, it's certainly possible
-that users will want to work with text files that use a different encoding
-scheme than their native encoding scheme so that they can easily interchange
-files with another team.</p>
-
-
-<p>For this reason, the workbench defines its own encoding profile that is specified 
-  by the user in the <b>Preferences</b> dialog.&nbsp; Users may choose from the 
-  available encoding choices in the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'> 
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"> <b>General &gt; Workspace</b></a> 
-  preference page or type in their own encoding.&nbsp; Plug-ins that interpret 
-  text files, such as editors and builders, should consult the workbench encoding 
-  preference rather than assume that the installed operating system encoding is 
-  in use.</p>
-
-
-<p>You can obtain the encoding preference using <b><a href="../reference/api/org/eclipse/core/resources/ResourcesPlugin.html">ResourcesPlugin</a>.getEncoding().&nbsp;
-</b>This encoding should be passed to <b>java.io </b>readers instead of using
-the default system encoding.&nbsp; If you need to track changes to this preference, you can hook a listener on
-the <b><a href="../reference/api/org/eclipse/core/resources/ResourcesPlugin.html">ResourcesPlugin</a>
-</b>preferences and react to changes in <b>ResourcesPlugin.PREF_ENCODING.&nbsp; </b>The
-following example comes from the default text editor: </p>
-
-
-<pre>public void initialize(StatusTextEditor textEditor) {
-	
-	fTextEditor= textEditor;
-	
-	fPropertyChangeListener= new Preferences.IPropertyChangeListener() {
-		public void propertyChange(Preferences.PropertyChangeEvent e) {
-			if (ResourcesPlugin.PREF_ENCODING.equals(e.getProperty()))
-				setEncoding(null, false);
-		}
-	};
-		
-	Preferences p= ResourcesPlugin.getPlugin().getPluginPreferences();
-	p.addPropertyChangeListener(fPropertyChangeListener);
-	
-	fEncodingActionGroup= new EncodingActionGroup(fTextEditor);
-	fEncodingActionGroup.update();
-}</pre>
-<p>Users may also change the encoding for a particular file in the <b>Edit &gt;
-Encoding</b> menu of an editor.&nbsp; If you are manipulating text inside an
-open editor, you should use <b><a href="../reference/api/org/eclipse/ui/editors/text/IEncodingSupport.html">IEncodingSupport</a>.getEncoding()</b>
-instead in order to get the encoding for the particular editor.&nbsp; The
-following example shows how to obtain this information from an editor:</p>
-<pre>IEncodingSupport encodingSupport = (IEncodingSupport) editor.getAdapter(IEncodingSupport.class);
-String encoding = encodingSupport.getEncoding();
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
deleted file mode 100644
index 3d4249c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Workbench key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Workbench key bindings</h2>
-<p>The workbench defines many keyboard accelerators for invoking common actions
-with the keyboard.&nbsp; In early versions of the platform, plug-ins could
-define the accelerator key to be used for their action when the action was
-defined.&nbsp; However, this strategy can cause several problems:</p>
-
-
-<ul>
-  <li>Different plug-ins may define the same accelerator key for actions that are
-    not related.</li>
-  <li>Plug-ins may define different accelerator keys for actions that are
-    semantically the same.</li>
-  <li>Plug-ins may define accelerator keys that later conflict with the workbench
-    (as the workbench is upgraded).</li>
-</ul>
-
-
-<p>In order to alleviate these problems, the platform defines a configurable key
-binding strategy that is extendable by plug-ins.&nbsp; It solves the problems
-listed above and introduces new capabilities:</p>
-
-
-<ul>
-  <li>The user can control which key bindings should be used.</li>
-  <li>Plug-ins can define key bindings that emulate other tools that may be
-    familiar to users of the plug-in.</li>
-  <li>Plug-ins can define contexts for key bindings so that they are only active
-    in certain situations.</li>
-</ul>
-<p>The basic strategy is that plug-ins use <b>commands</b> to define
-semantic actions.&nbsp; Commands are simply declarations of an action and its
-associated category.&nbsp; These commands can then be associated with key
-bindings, actions, and handlers.&nbsp; Commands do not define an implementation
-for the action.&nbsp; When a
-plug-in defines an action for an editor, action set, or view, the action can
-specify that it is an implementation of one of these commands.&nbsp;
-This allows semantically similar actions to be associated with the same command.</p>
-<p>Once a command is defined, a <b>key binding</b> may be defined that
-references the command.&nbsp; The key binding defines the key sequence that
-should be used to invoke the command.&nbsp; A key binding may reference a
-<b>scheme</b> which is used to group key bindings into different named
-schemes that the user may activate via the
-Preferences dialog.</p>
-<p>This is all best understood by walking through the workbench and looking at
-how commands and key bindings are declared.&nbsp; We'll look at all of this from
-the point of view of defining key bindings for existing workbench actions.&nbsp; </p>
-
-<p>
-See the <a href="workbench_cmd_bindings.htm" class="XRef">org.eclipse.ui.bindings</a>
-section for simple binding scenarios and the
-<a href="workbench_cmd.htm" class="XRef">Basic workbench extension points using commands</a>
-section for using the new command framework.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
deleted file mode 100644
index 9f1bc9b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelConfig.htm
+++ /dev/null

@@ -1,113 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>
-Schemes
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Schemes</h3>
-
-
-<p><b>Schemes</b> are used to represent a general style or theme of 
-  bindings. For example, the Workbench provides a &quot;Default&quot; scheme and
-  an &quot;Emacs&quot; scheme.&nbsp; Only one scheme is active at any
-  given time.&nbsp; End users control which one 
-  is active using the
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Keys</b>  </a>
-  
-  preference page.
-  </p>
-
-
-<p><img src="images/keybindings.png" alt="" border="0"></p>
-
-
-<p>From an implementation point of view, schemes are simply
-named groupings of bindings.&nbsp; A scheme won't
-accomplish anything on its own unless there are bindings associated with
-it.&nbsp;&nbsp;</p>
-
-
-<p>Let's look again at the workbench markup for <b><a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a>
-</b>to find the binding definitions and how a scheme gets
-associated with a binding.</p>
-
-
-<pre>...
-&lt;key
-       sequence=&quot;Ctrl+S&quot;
-       <b>commandId=&quot;org.eclipse.ui.file.save&quot;</b>
-       <b>schemeId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;</b>
-&lt;/key&gt;
-...
-&lt;key
-       sequence=&quot;Ctrl+X Ctrl+S&quot;
-       <b>commandId=&quot;org.eclipse.ui.file.save&quot;</b>
-       <b>schemeId=&quot;org.eclipse.ui.emacsAcceleratorConfiguration&quot;&gt;</b>
-&lt;/key&gt;
-...
-</pre>
-
-
-<p>There are two different key bindings defined for the &quot;org.eclipse.ui.file.save&quot;
-command.&nbsp; Note that each one has a different <b>schemeId</b>
-defined.&nbsp; When the default scheme is active, the &quot;Ctrl+S&quot;
-key binding will invoke the command.&nbsp; When the emacs scheme is
-active, the sequence &quot;Ctrl+X Ctrl+S&quot; will invoke the command. </p>
-
-
-<h4>Defining new schemes</h4>
-
-
-<p>When your plug-in defines a binding, it will most likely assign it to an existing
-scheme.&nbsp; However, your plug-in may want to define a
-completely new style of scheme.&nbsp; If this is the case, you can define
-a new type of scheme inside the <b><a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a></b>
-definition.&nbsp; The workbench markup that defines the default and emacs key
-configurations are shown below:</p>
-
-
-<pre>...
-&lt;scheme
-       name=&quot;%keyConfiguration.default.name&quot;
-       description=&quot;%keyConfiguration.default.description&quot;
-       <b>id=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;</b>
-&lt;/scheme&gt;
-&lt;scheme
-       name=&quot;%keyConfiguration.emacs.name&quot;
-       parentId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;
-       description=&quot;%keyConfiguration.emacs.description&quot;
-       <b>id=&quot;org.eclipse.ui.emacsAcceleratorConfiguration&quot;&gt;</b>
-&lt;/scheme&gt;
-...</pre>
-
-
-<p>Note that the <b>name</b>  defined here is the one used in the preferences page in the list of
-schemes.</p>
-
-
-<h4>Activating a scheme </h4>
-
-
-<p>The user controls the active scheme via the preferences page.&nbsp;
-However, you can define the default active scheme as a part of the 
-"plugin_customization.ini" file.  It is a preference:</p>
-<pre>
-org.eclipse.ui/KEY_CONFIGURATION_ID=org.eclipse.ui.defaultAcceleratorConfiguration
-</pre>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
deleted file mode 100644
index 3142124..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_accelSet.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Key bindings</h3>
-
-
-<p>The association between a command and the key combinations that should
-invoke the command is called a <b>key binding</b>.&nbsp; Plug-ins can define key
-bindings along with commands in the <b><a href="../reference/extension-points/org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a></b>
-extension point.</p>
-
-
-<pre>...
-&lt;key
-      <b>sequence=&quot;Ctrl+S&quot;</b>
-      <b>commandId=&quot;org.eclipse.ui.file.save&quot;</b>
-      schemeId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;
-&lt;/key&gt;
-...</pre>
-
-
-<p>There is our friend <b>org.eclipse.ui.file.save</b>.&nbsp; Recall our
-hypothetical action definition:</p>
-
-<pre>&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;com.example.actions.actionSet&quot;
-		   label=&quot;Example Actions&quot;
-		   visible=&quot;true&quot;&gt;
-		   &lt;action id=&quot;com.example.actions.action1&quot;
-			   menubarPath=&quot;additions&quot;
-			   label=&quot;Example Save Action&quot;
-			   class=&quot;org.example.actions.ExampleActionDelegate&quot;
-			   <b>definitionId=&quot;org.eclipse.ui.file.save&quot;</b>&gt;
-		   &lt;/action&gt;
-		   ...
-	   &lt;/actionSet&gt;
-&lt;/extension&gt;</pre>
-<p>The <b>sequence</b> attribute for a key binding defines the key
-combination that is used to invoke a command.&nbsp; So, it follows that when our example action set is active, our save action will be invoked
-when the user chooses <b>Ctrl+S</b>.</p>
-
-
-<p> Likewise, when the
-workbench <b>SaveAction</b> is active, the same key combination will invoke it
-instead, since the workbench uses the same command id for its <b>SaveAction</b>.</p>
-
-
-<p>To complete the example, we need to understand what the <b>configuration</b>
-is all about.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
deleted file mode 100644
index fc9febf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_actionDef.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Commands
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Commands</h3>
-
-<p>See the <a href="workbench_cmd_commands.htm" class="XRef">org.eclipse.ui.commands</a>
-section for defining command definitions.
-</p>
-
-<h4>Associating an action with a command</h4>
-
-
-<p>Actions can be associated with a command in code or in the <b>plugin.xml
-</b>for action sets.&nbsp;
-Your choice depends on where the action is defined.</p>
-
-
-<p>Actions that are instantiated in code can also be associated with an action
-definition using <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>
-protocol.&nbsp; This is typically done when the action is created.&nbsp; The <b>SaveAction</b>
-uses this technique when it initializes itself. </p>
-
-
-<pre>
-public SaveAction(IWorkbenchWindow window) {
-	...
-	setText...
-	setToolTipText...
-	setImageDescriptor...
-	<b>setActionDefinitionId(&quot;org.eclipse.ui.file.save&quot;)</b>; 
-}
-</pre>
-
-<p>(Note:&nbsp; The method name <b>setActionDefinitionID </b>could more
-appropriately be named <b>setCommandID</b>.&nbsp; The method name reflects the
-original implementation of key bindings and uses outdated terminology.)</p>
-
-
-<p>By invoking <b>setActionDefinitionID</b>, the implementation action (<b>SaveAction</b>) is associated with
-the command id that was used in the command definition markup. It is good practice to define constants for your action definitions so that
-they are easily referenced in code. </p>
-
-<p> If you define an
-action in an action set, then you typically do not need to
-instantiate an action yourself.&nbsp; The workbench will do it for you when the user
-invokes your action from a menu or the keyboard.&nbsp; In this case, you can
-associate your action with a command ID in your&nbsp; XML markup.&nbsp; The
-following shows a hypothetical markup for an action set:</p>
-
-<pre>
-&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;com.example.actions.actionSet&quot;
-		   label=&quot;Example Actions&quot;
-		   visible=&quot;true&quot;&gt;
-		   &lt;action id=&quot;com.example.actions.action1&quot;
-			   menubarPath=&quot;additions&quot;
-			   label=&quot;Example Save Action&quot;
-			   class=&quot;org.example.actions.ExampleActionDelegate&quot;
-			   <b>definitionId=&quot;org.eclipse.ui.file.save&quot;</b>&gt;
-		   &lt;/action&gt;
-		   ...
-	   &lt;/actionSet&gt;
-   &lt;/extension&gt;</pre>
-<p>The <b>definitionId</b> attribute is used to declare a command ID for the action.</p>
-
-
-<p>Using either technique, associating your action with a command ID causes any key bindings that get defined for the
-command <b>org.eclipse.ui.file.save
-</b>to invoke your action when appropriate.&nbsp; </p>
-
-
-<p>Now let's look at how these key bindings get defined. </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
deleted file mode 100644
index 6d054d2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_keyBindings_contexts.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contexts and key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contexts and key bindings</h3>
-
-<p>A <b> context</b> can be specified for a key binding so that the binding is only available when the user is
-working within a specific context.  Contexts are declared in the
-<b><a href="../reference/extension-points/org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></b>
-extension point.</p>
-
-<p>A context can be bound to a key binding by specifying the id of the context when the key binding is defined.
-For example, if we only wanted the save command to work while the user is editing text, we could specify
-a context for the key binding:
-</p>
-<pre>&lt;extension
-         point="org.eclipse.ui.bindings"&gt;
-  &lt;key
-      sequence=&quot;Ctrl+S&quot;
-      commandId=&quot;org.eclipse.ui.file.save&quot;
-      <b>contextId="org.eclipse.ui.textEditorScope"</b>
-      schemeId=&quot;org.eclipse.ui.defaultAcceleratorConfiguration&quot;&gt;
-  &lt;/key&gt;
-&lt;/extension&gt;
-...
-</pre>
-(See <a href="workbench_advext_contexts.htm">Contexts</a>) for a more detailed discussion
-of contexts and how they are defined.
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm
deleted file mode 100644
index f805564..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_marker_support.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<TITLE>Support for displaying markers</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</head>
-
-<body>
-<h2>Support for displaying markers</h2>
-<p>The <a
-	href="../reference/extension-points/org_eclipse_ui_ide_markerSupport.html">org.eclipse.ui.ide.markerSupport</a>
-extension point provides facilities for controlling how markers are
-displayed and organized in the UI. This extension point handles filters
-and grouping in views such as the Problems view as well as definition of custom marker views.</p>
-<p><strong>Marker Content Generators</strong></p>
-
-<p>Custom marker views can be created by specifying the view using a
-<tt>markerContentsGenerator</tt>. A <tt>markerContentsGenerator</tt>
-specifies the types used, the configurations available and the grouping
-to be shown in the view. The problems view, tasks view and bookmarks
-view are defined using <tt>markerContentsGenerator</tt> as of version
-3.4. A reusable superclass <tt>org.eclipse.ui.views.markers.AbstractMarkersView</tt>
-has been supplied for use by custom <tt>markerContentsGenerators</tt>.</p>
-<p><strong>Commands</strong></p>
-The menus defined in the markersViews now all use the
-<tt>org.eclipse.ui.menus</tt>
-extension point so they can be extended by clients at any desired point.
-The pop-up menus in the supplied markers views are available to all
-subclasses of
-<tt>org.eclipse.ui.views.markers.AbstractMarkersView</tt>
-but pull-down entries must be added for the new views explicitly. It is
-recommended that all new handlers for commands to be added to the
-markersView subclass
-<tt>org.eclipse.ui.views.markers.MarkerViewHandler</tt>
-so as to get access to the
-<tt>org.eclipse.core.resources.IMarkers</tt>
-currently selected.
-
-<p><strong>Configurations</strong></p>
-<p>The Problems view supports multiple configurations at once. When
-multiple configurations are enabled there are two possible modes of
-matching: <i>match any</i> (any marker that matches one or more selected
-filters will be displayed) or <i>match all</i>(any marker that matches all
-selected filters will be displayed). New configurations can be added
-using the <tt>markerFieldConfiguration</tt> element or manually by the
-user. Below is the configuration section of the Problems view showing
-user configurations and configurations added via the extension point).</p>
-<p><img src="images/problems_view_filters.png"></p>
-<p><strong>Groups</strong></p>
-<p>Markers can be grouped in two ways. The first way is to group
-marker types into groups using the <code>markerTypeCategory</code>
-element. This is shown when the user selects <b>Group By &gt; Type</b>.
-Below is an example showing Java Problems and some using a test
-grouping.</p>
-<p><img src="images/problems_view_groupByType.png"></p>
-<p>When marker types are grouped together they will be shown in
-those groups in the configurations dialog.</p>
-<p><img src="images/problems_view_markerTypeCat.png"></p>
-<p>You can also create your own grouping using the <code>markerGrouping</code>
-element, which will show up as an extra entry in the <b>Group By</b>
-menu of the markers view it is defined in. Top level markerGroupings are
-shown in the Problems View (this is for compatibility with previous
-Eclipse versions). The IDE provides a grouping based on severity (the
-default). The Java development tools provide a Java Type grouping.</p>
-<p><code>markerGroupings</code> are resolved by checking attributes
-on the <a
-	href="../reference/api/org/eclipse/core/resources/IMarker.html">IMarker</a>.
-<code>markerAttributeMappings</code> are used to specify these mappings.
-Below is the Group By menu with the extra <code>markerGroupings</code>
-that have been added. The Problems view is currently grouped by
-severity.</p>
-<p><img src="images/problemsview_groups.png"></p>
-<p></p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
deleted file mode 100644
index 2ebb3c4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerhelp.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing marker help
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Contributing marker help</h4>
-<p>Now we are ready to look at how to add help to the readme tool's
-markers.&nbsp; Adding marker help is done using the <b><a href="../reference/extension-points/org_eclipse_ui_ide_markerHelp.html">org.eclipse.ui.ide.markerHelp</a></b>
-extension point.&nbsp; This extension point allows plug-ins to associate a help
-context id with a particular type of marker.&nbsp; The marker can be qualified
-by marker type only, or it can be further qualified by the value of one or more of its
-attributes.&nbsp; The readme tool declares several different help contexts:</p>
-<pre>&lt;extension point=&quot;org.eclipse.ui.ide.markerHelp&quot;&gt; 
-   &lt;markerHelp 
-      <b>markerType=&quot;org.eclipse.ui.examples.readmetool.readmemarker&quot; </b>
-      helpContextId=&quot;org.eclipse.ui.examples.readmetool.marker_example1_context&quot;&gt; 
-     <b> &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.id&quot; value= &quot;1234&quot;/&gt; </b>
-   &lt;/markerHelp&gt; 
-   &lt;markerHelp 
-      markerType=&quot;org.eclipse.ui.examples.readmetool.readmemarker&quot; 
-      helpContextId=&quot;org.eclipse.ui.examples.readmetool.marker_example2_context&quot;&gt; 
-      &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.level&quot; value= &quot;7&quot;/&gt; 
-   &lt;/markerHelp&gt; 
-   &lt;markerHelp 
-      markerType=&quot;org.eclipse.ui.examples.readmetool.readmemarker&quot; 
-      helpContextId=&quot;org.eclipse.ui.examples.readmetool.marker_example3_context&quot;&gt; 
-      &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.level&quot; value= &quot;7&quot;/&gt; 
-      &lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.department&quot; value= &quot;infra&quot;/&gt; 
-   &lt;/markerHelp&gt; 
-   ...</pre>
-<p>Each marker help context is defined for the readme marker type.&nbsp;
-However, each help context is associated with a different combination of
-attribute values.&nbsp; The first marker help context will be used for markers
-whose <b>id</b> attribute is set to <b>&quot;1234&quot;</b>.&nbsp; The help
-contexts are defined in the plug-in's <b>HelpContexts.xml </b>file:</p>
-<pre>&lt;context id=&quot;marker_example1_context&quot; &gt;
-	&lt;description&gt;Readme marker example 1 &lt;b&gt;Help&lt;/b&gt; id = 1234 &lt;/description&gt;
-&lt;/context&gt;</pre>
-
-<p>Sure enough, when we select a readme marker with id=&quot;1234&quot; and select 
-  help using F1, we see our help in the help view. </p>
-<p><img src="images/readmemarkerhelp.png" alt="Tasks list with marker help" border="0" ></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
deleted file mode 100644
index 7b45ab8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markerresolution.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing marker resolution
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Contributing marker resolution</h4>
-<p>Plug-ins can also define marker resolutions, so that their problem markers can
-participate in the workbench <b>Quick Fix</b> feature. Users can select
-a problem marker and choose a <b>Quick Fix</b> from a popup containing the list of supplied
-fixes contributed for the marker.</p>
-
-
-<p><img src="images/markerquickfixmenu.png" alt="Marker quick fix menu" border="0"></p>
-
-
-<p>Marker resolutions are contributed using the <b><a href="../reference/extension-points/org_eclipse_ui_ide_markerResolution.html">org.eclipse.ui.ide.markerResolution</a></b>
-extension point. This extension point allows plug-ins to associate a <b>class</b>
-that implements <b><a href="../reference/api/org/eclipse/ui/IMarkerResolutionGenerator.html">IMarkerResolutionGenerator</a></b>
-with a particular type of marker.&nbsp; The marker can be qualified
-by marker type only, or it can be further qualified by the value of one or more of its
-attributes.  The JDT contributes a marker resolution for Java problems:</p>
-
-<pre>
-&lt;extension
-	point="org.eclipse.ui.ide.markerResolution"&gt;
-	&lt;markerResolutionGenerator
-		markerType="org.eclipse.jdt.core.problem"
-		class="org.eclipse.jdt.internal.ui.text.correction.CorrectionMarkerResolutionGenerator"&gt;
-	&lt;/markerResolutionGenerator&gt;
-&lt;/extension&gt;
-</pre>
-
-<p>The marker resolution generator is responsible for returning an array of
-marker resolutions (<a href="../reference/api/org/eclipse/ui/IMarkerResolution.html"><b>IMarkerResolution</b></a>)
-that will be shown in the <b>Quick Fix</b> popup. The resolution will
-be <b>run()</b> if the user selects one of the fixes.</p>
-<p><img src="images/markerresolution.png" alt="Marker resolutions" border="0"></p>
-<p>
-The Problems view supports resolving multiple problems at once.  The user can
-add other matching problems to the list of problems to fix, and then apply all
-fixes in one go.  To support multiple resolutions, your implementation of <a href="../reference/api/org/eclipse/ui/IMarkerResolution.html">IMarkerResolution</a> 
-must be a subclass of <a href="../reference/api/org/eclipse/ui/views/markers/WorkbenchMarkerResolution.html">WorkbenchMarkerResolution</a>.
-</p>
-<p><img src="images/quickfix.png"></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
deleted file mode 100644
index caaa064..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_markers.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Marker help and resolution
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Marker help and resolution</h3>
-<p>In <a href="resAdv_markers.htm">Resource markers</a>, we saw how plug-ins can
-define specialized marker types in order to annotate resources with
-information.&nbsp; The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> example defines its own markers in order to demonstrate two
-marker-related workbench extensions:&nbsp; <b>marker help</b> and <b>marker
-resolutions</b>.&nbsp; The marker definition is in the readme plug-in's manifest
-markup:</p>
-
-
-<pre>&lt;extension id=&quot;readmemarker&quot; point=&quot;org.eclipse.core.resources.markers&quot; name=&quot;%ReadmeMarker.name&quot;&gt;
-	&lt;super type=&quot;org.eclipse.core.resources.taskmarker&quot;/&gt;
-	&lt;super type=&quot;org.eclipse.core.resources.textmarker&quot;/&gt;
-	&lt;persistent value=&quot;true&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.id&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.level&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.department&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.code&quot;/&gt;
-	&lt;attribute name=&quot;org.eclipse.ui.examples.readmetool.language&quot;/&gt;
-&lt;/extension&gt;   </pre>
-
-
-<p>The tool defines a marker that inherits from the platform's text marker and
-task marker.&nbsp; It also defines named attributes for the marker.&nbsp;&nbsp;
-Marker attributes can be set and queried.</p>
-
-
-<p>Since the new readme marker is a kind of text marker, it
-inherits the text marker attributes.&nbsp; The text marker attributes include
-the character location of the marker.</p>
-
-
-<p>Markers can be added to a <b>.readme</b> file using the readme editor's popup
-menu.&nbsp; (The popup menu actions are added dynamically in <b>ReadmeTextEditor.<font SIZE="2" COLOR="#000000">editorContextMenuAboutToShow(IMenuManager</font>
-</b><font SIZE="2" COLOR="#000000"><b>parentMenu)</b>).&nbsp; Once added,
-the markers appear on the left side of the editor and in the tasks view.</font></p>
-
-
-<p><img src="images/readmemarkermenu.png" alt="Readme editor with readme markers on left side ruler" border="0"></p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm
deleted file mode 100644
index 51c6938..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget.htm
+++ /dev/null

@@ -1,132 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Retargetable actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Retargetable actions</h2>
-<p>It is common for a plug-in's views and editors to implement actions that are
-semantically similar to existing workbench actions, such as clipboard
-cut/copy/paste, view refresh, or properties.&nbsp; The popup menu for views and
-editors can become quite cluttered if every view or editor has to define unique
-actions for these operations and include them in their menus.&nbsp; </p>
-
-
-<p>To solve this problem, the workbench defines <b>retargetable</b> (also called
-<b>global</b>) actions that can be handled by any view or editor.&nbsp; When a
-view or editor is active, its handler will be run when the user chooses the
-action from the workbench menu or toolbar.&nbsp; This allows views and editors
-to share workbench menu space for semantically similar actions. </p>
-
-
-<p><a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b>IWorkbenchActionConstants</b></a>
-documents all of the workbench actions and denotes retargetable actions as
-global.&nbsp; For example, here is the definition of the <b>Properties</b> action.</p>
-
-
-<pre>public static final String PROPERTIES = &quot;properties&quot;; // Global action. </pre>
-
-
-<p>The following table summarizes some of the more common retargetable actions
-that are implemented by views and editors:</p>
-
-
-<table border="1" cellpadding="0" cellspacing="0" width="64%">
-  <tr>
-    <td width="20%">&nbsp;</td>
-    <td width="20%"><b>File menu</b></td>
-    <td width="20%"><b>Edit menu</b></td>
-    <td width="20%"><b>Navigate menu</b></td>
-    <td width="20%"><b>Project menu</b></td>
-  </tr>
-  <tr>
-    <td width="20%"><b>views</b></td>
-    <td width="20%">move<br>
-      rename<br>
-      refresh<br>
-      properties</td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">go into<br>
-      go to resource<br>
-      sync with editor<br>
-      back<br>
-      forward<br>
-      up<br>
-      next<br>
-      previous</td>
-    <td width="20%">open<br>
-      close<br>
-      build<br>
-      rebuild</td>
-  </tr>
-  <tr>
-    <td width="20%"><b>editors</b></td>
-    <td width="20%">revert<br>
-      print</td>
-    <td width="20%">find</td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">&nbsp;</td>
-  </tr>
-  <tr>
-    <td width="20%"><b>views and editors</b></td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">cut<br>
-      copy<br>
-      paste<br>
-      delete<br>
-      select all<br>
-      undo<br>
-      redo</td>
-    <td width="20%">&nbsp;</td>
-    <td width="20%">&nbsp;</td>
-  </tr>
-</table>
-<p>Retargetable actions are created using <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a></b>.&nbsp;
-The following snippet is from <b>WorkbenchActionBuilder</b>.</p>
-
-
-<pre> propertiesAction = createGlobalAction(IWorkbenchActionConstants.PROPERTIES, &quot;file&quot;, false); </pre>
-
-
-<p>The <b> createGlobalAction</b> method shows us exactly how to make a <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a></b>.</p>
-
-
-<pre>private RetargetAction createGlobalAction(String id, String actionDefPrefix, boolean labelRetarget) {
-	RetargetAction action;
-	if (labelRetarget) {
-		action = new LabelRetargetAction(id, WorkbenchMessages.getString(&quot;Workbench.&quot; + id)); 
-	}
-	else {
-		action = new RetargetAction(id, WorkbenchMessages.getString(&quot;Workbench.&quot; + id)); 
-	}
-	...
-	return action;
-}</pre>
-
-<p>When creating a retargetable action, the workbench assigns the id for the
-action and the default label.&nbsp; Note that there are two styles of retarget actions.&nbsp; <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>simply allows a view or editor to reimplement an action.&nbsp; <b><a href="../reference/api/org/eclipse/ui/actions/LabelRetargetAction.html">LabelRetargetAction</a>
-</b>also allows views and editors to reset the label of the action.&nbsp;&nbsp;
-This is useful for making the menu label more specific, such as relabeling an <b>Undo</b>
-action as <b>Undo Typing</b>.&nbsp;&nbsp;</p>
-
-
-<p>Now we know how the retarget actions are defined by the workbench.&nbsp; Let's look
-next at how your view or editor can provide an implementation for a retargetable action.&nbsp;
-This is done by <a href="wrkAdv_retarget_setting.htm">setting a global action
-handler</a>.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm
deleted file mode 100644
index 201def4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Contributing new retargetable actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Contributing new retargetable actions</h3>
-<p>The workbench is not the only plug-in that can create retargetable
-actions.&nbsp; Your plug-in can define its own retargetable action, so that
-views and editors within your plug-in can share the same menu actions.&nbsp;
-There are two ways to contribute retargetable actions from your plug-in:</p>
-<ul>
-  <li>An <b>editor</b> can define a retargetable action for which the editor and
-    related views can hook handlers.&nbsp; The action is only available in the
-    menu bar when the editor is open.&nbsp;&nbsp;</li>
-  <li>An <b>action set</b> can define a retargetable action for which editors
-    and views can hook handlers.&nbsp; The action will be visible as long as the
-    action set is visible, but it will only be enabled if the active part has
-    hooked a handler for the action.</li>
-</ul>
-<p>This mechanism is useful for providing tight integration between editors and
-related views.&nbsp; For example, a content outline view can implement a handler
-for an action defined by its associated editor.&nbsp;&nbsp;</p>
-<p>The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> example demonstrates both of these techniques.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm
deleted file mode 100644
index 46319be..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_actionsets.htm
+++ /dev/null

@@ -1,119 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Retargetable action set actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Retargetable action set actions</h4>
-<p>The <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> action set also defines retargetable actions.&nbsp; The action remains
-visible as long as the readme action set is visible, but it is only enabled when
-a view or editor that implements the action is active.&nbsp; When using action
-sets to define retargetable actions, the actions are created in the action set
-markup rather than in code.&nbsp; The following is from the readme tool's action
-set definition:</p>
-<pre>&lt;extension point = &quot;org.eclipse.ui.actionSets&quot;&gt;
-	   &lt;actionSet id=&quot;org_eclipse_ui_examples_readmetool_actionSet&quot;
-		   label=&quot;%ActionSet.name&quot;
-		   visible=&quot;true&quot;&gt;
-...
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeRetargetAction&quot;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-   toolbarPath=&quot;readme&quot;
-   label=&quot;%ReadmeRetargetAction.label&quot;
-   tooltip=&quot;%ReadmeRetargetAction.tooltip&quot;
-   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-   <b>retarget=&quot;true&quot;</b>&gt;
-&lt;/action&gt;
-&lt;action id=&quot;org_eclipse_ui_examples_readmetool_readmeRelabelRetargetAction&quot;
-   menubarPath=&quot;window/org_eclipse_ui_examples_readmetool/slot1&quot;
-   toolbarPath=&quot;readme&quot;
-   label=&quot;%ReadmeRelabelRetargetAction.label&quot;
-   tooltip=&quot;%ReadmeRelabelRetargetAction.tooltip&quot;
-   helpContextId=&quot;org.eclipse.ui.examples.readmetool.open_browser_action_context&quot;
-   icon=&quot;icons/ctool16/openbrwsr.png&quot;
-   <b>retarget=&quot;true&quot;	</b>
-   <b>allowLabelUpdate=&quot;true&quot;</b>&gt;
-&lt;/action&gt;
-...</pre>
-<p>Retargeted actions are specified by using the <b>retarget=&quot;true&quot;</b>
-attribute.&nbsp; This will cause a <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a></b>
-to be created in the action set.&nbsp; Note that the retargetable actions do not specify an implementing
-<b>class</b> since it is up to each view or editor in the plug-in to set up a
-handler that implements each action.&nbsp; If the <b>allowLabelUpdate</b>  is
-true, then a <b><a href="../reference/api/org/eclipse/ui/actions/LabelRetargetAction.html">LabelRetargetAction</a>
-</b>will be created instead.</p>
-<p>The retargeted actions will be visible in the window menu when the readme
-action set is visible.&nbsp; However, they will not be enabled if the readme
-tool's editor or outline view are not active.</p>
-<p><img src="images/readmeactionsetmenu.png" alt="Readme File Editor menu with two grayed items and one enabled item" border="0"></p>
-<p>&nbsp;</p>
-<p>What do the editor and view have to do?&nbsp; Again, the client side is
-similar to registering a handler for the workbench or an editor's retargetable
-action.&nbsp; The action id specified in the markup must be used when
-registering a global action handler.</p>
-<p>The <b>ReadmeEditorActionBarContributor </b>takes care of this for the
-editor.&nbsp; First, it defines the handlers for the actions.</p>
-<pre>public ReadmeEditorActionBarContributor() {
-	...
-	handler4 = new EditorAction(MessageUtil.getString(&quot;Editor_Action4&quot;)); 
-	handler5 = new EditorAction(MessageUtil.getString(&quot;Editor_Action5&quot;)); 
-	handler5.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action5&quot;));
-	...
-}</pre>
-<p>The handlers are registered at the same time that the handlers for the editor
-retargetable actions were registered.</p>
-<pre>public void init(IActionBars bars, IWorkbenchPage page) {
-	...
-	bars.setGlobalActionHandler(IReadmeConstants.ACTION_SET_RETARGET4, handler4);
-	bars.setGlobalActionHandler(IReadmeConstants.ACTION_SET_LABELRETARGET5, handler5);
-	...
-}</pre>
-<p>Recall that action bar contributors are shared among different instances of
-the same editor.&nbsp; This means the handlers must be notified if the active
-editor for the <b>ReadmeEditorActionBarContributor </b>changes.</p>
-<pre>public void setActiveEditor(IEditorPart editor) {
-	...
-	handler4.setActiveEditor(editor);
-	handler5.setActiveEditor(editor);
-	...
-}</pre>
-<p>That's it for the editor.&nbsp; We should see these actions enable when the
-editor is activated.</p>
-<p><img src="images/actionseteditorretargets.png" alt="Readme File Editor menu with actions enabled" border="0">&nbsp;</p>
-<p>Note that the label for the first retargetable action (&quot;Editor Action
-4&quot;) was not used since the action set XML markup did not set <b>allowLabelUpdate</b>.</p>
-<p>The <b>ReadmeContentOutlinePage</b>
- defines its handlers in the same place it defined handlers for the editor's
-retargetable actions:</p>
-<pre>public void createControl(Composite parent) {
-	...
-	action = new OutlineAction(MessageUtil.getString(&quot;Outline_Action4&quot;)); 
-	getSite().getActionBars().setGlobalActionHandler(
-		IReadmeConstants.ACTION_SET_RETARGET4, 
-		action);  
-	action = new OutlineAction(MessageUtil.getString(&quot;Outline_Action5&quot;)); 
-	action.setToolTipText(MessageUtil.getString(&quot;Readme_Outline_Action5&quot;)); 
-	getSite().getActionBars().setGlobalActionHandler(
-		IReadmeConstants.ACTION_SET_LABELRETARGET5, 
-		action);  
-}</pre>
-<p>We should see its relabeled action when the content outliner is active.</p>
-<p><img src="images/actionsetoutlineretargets.png" alt="Readme File Editor menu with renamed action" border="0"></p>
-<h4>&nbsp;</h4>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm
deleted file mode 100644
index 69328ce..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_contribute_editors.htm
+++ /dev/null

@@ -1,132 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Retargetable editor actions
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h4>Retargetable editor actions</h4>
-<p>Recall that the <a href="../samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html">readme
-tool</a> defines its own editor which contributes actions
-to the workbench menu bar using its <b>ReadmeEditorActionBarContributor</b>.&nbsp;&nbsp;</p>
-<pre>&lt;extension
-    point = &quot;org.eclipse.ui.editors&quot;&gt;
-	&lt;editor
-  	   id = &quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-  	   name=&quot;%Editors.ReadmeEditor&quot;
-      	   icon=&quot;icons/obj16/editor.png&quot;
-      	   class=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditor&quot;
-	   extensions=&quot;readme&quot;
-           <b>contributorClass=&quot;org.eclipse.ui.examples.readmetool.ReadmeEditorActionBarContributor</b>&quot;&gt;
-	&lt;/editor&gt;
-&lt;/extension&gt;</pre>
-<p>Let's look closer at what happens in the contributor class.</p>
-<pre>public ReadmeEditorActionBarContributor() {
-	...
-	action2 = new <b>RetargetAction</b>(<b>IReadmeConstants.RETARGET2</b>, MessageUtil.getString(&quot;Editor_Action2&quot;));
-	action2.setToolTipText(MessageUtil.getString(&quot;Readme_Editor_Action2&quot;));
-	action2.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_DISABLE);
-	action2.setImageDescriptor(ReadmeImages.EDITOR_ACTION2_IMAGE_ENABLE);
-	...
-	action3 = new <b>LabelRetargetAction</b>(<b>IReadmeConstants.LABELRETARGET3</b>, MessageUtil.getString(&quot;Editor_Action3&quot;));
-	action3.setDisabledImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_DISABLE);
-	action3.setImageDescriptor(ReadmeImages.EDITOR_ACTION3_IMAGE_ENABLE);
-	...&nbsp;&nbsp;
-	<b>handler2</b> = new EditorAction(MessageUtil.getString(&quot;Editor_Action2&quot;)); 
-	...
-	<b>handler3</b> = new EditorAction(MessageUtil.getString(&quot;Editor_Action3&quot;)); 
-	...</pre>
-<p>When the contributor is created, it creates two retargetable actions (one
-that allows label update and one that does not).&nbsp; Creation of the actions
-uses the same technique that the workbench uses.&nbsp; It also creates two
-handlers that will be used for the actions when the editor is the active
-part.&nbsp;&nbsp;</p>
-<p>But where are the handlers for the actions registered?&nbsp; Setting the
-global handlers is done a little differently when your editor defines the
-retargeted actions.&nbsp; Why?&nbsp; Because your contributor is in charge of
-tracking the active view and hooking different handlers as different views or
-the editor itself becomes active.&nbsp; (The workbench does this for you when
-you set a handler for one of its global actions).&nbsp; Here's how the <b>ReadmeEditorActionBarContributor</b>
-sets things up:</p>
-<pre>public void init(IActionBars bars, IWorkbenchPage page) {
-	super.init(bars, page);
-	bars.setGlobalActionHandler(IReadmeConstants.RETARGET2, handler2);
-	bars.setGlobalActionHandler(IReadmeConstants.LABELRETARGET3, handler3);
-	...</pre>
-<p>First, the contributor registers its handlers for the retargeted
-actions.&nbsp; This ensures that the contributor's actions will be run when the
-editor itself is active.&nbsp; The next step is to register each <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>as a part listener on the page.</p>
-<pre>	...
-	// Hook retarget actions as page listeners
-	page.addPartListener(action2);
-	page.addPartListener(action3);
-	IWorkbenchPart activePart = page.getActivePart();
-	if (activePart != null) {
-		action2.partActivated(activePart);
-		action3.partActivated(activePart);
-	}
-}</pre>
-<p>Adding each <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>as a part listener means that it will be notified when the active part
-changes.&nbsp; The action can get the correct global handler from the newly
-activated part.&nbsp; (See the implementation of <b><a href="../reference/api/org/eclipse/ui/actions/RetargetAction.html">RetargetAction</a>
-</b>for all the details.)&nbsp;&nbsp; Note that to start, the action is seeded
-with the currently active part. </p>
-<p>When the editor contributor is disposed, it should unhook the retargetable
-actions as page listeners.</p>
-<pre>public void dispose() {
-	// Remove retarget actions as page listeners
-	getPage().removePartListener(action2);
-	getPage().removePartListener(action3);
-}</pre>
-<p>Finally, recall that action bar contributors are shared among instances of
-the same editor class.&nbsp; For this reason, the handlers must be notified when
-the active editor changes so that they can connect to the proper editor
-instance.</p>
-<pre>public void setActiveEditor(IEditorPart editor) {
-	...
-	handler2.setActiveEditor(editor);
-	handler3.setActiveEditor(editor);
-	...
-}</pre>
-<p>That completes the setup on the editor side.&nbsp; When the editor is open
-and active, the handlers (and their labels) as defined by the <b>ReadmeEditorActionBarContributor
-</b>will appear in the workbench menu bar.</p>
-<p><img src="images/editorretargets.png" alt="Readme menu with three editor actions in workbench menu bar" border="0"></p>
-<p>Now that the editor's contributions are in place, what does a view do to register a handler?&nbsp; The code on the client side
-is similar to registering a handler for a workbench action, except that the
-action id is the one defined by the plug-in's editor.&nbsp; The <b>ReadmeContentOutlinePage</b>
-registers a handler for these actions.</p>
-<pre>public void createControl(Composite parent) {
-	super.createControl(parent);
-	...
-	getSite().getActionBars().<b>setGlobalActionHandler(
-		IReadmeConstants.RETARGET2, </b>
-		new OutlineAction(MessageUtil.getString(&quot;Outline_Action2&quot;)));  
-
-	OutlineAction action = new OutlineAction(MessageUtil.getString(&quot;Outline_Action3&quot;)); 
-	<b>action.setToolTipText(MessageUtil.getString(&quot;Readme_Outline_Action3&quot;)); </b>
-	getSite().getActionBars().<b>setGlobalActionHandler(
-		IReadmeConstants.LABELRETARGET3, </b>
-		action);  
-	...</pre>
-<p>Note that the outliner sets tool tip text and a label on the second action,
-since it allows relabeling.&nbsp; When the readme outliner view is made active,
-its handlers (and their labels) will now appear in the workbench menu bar.</p>
-<p><img src="images/editoroutlineretargets.png" alt="Readme menu with one renamed editor action" border="0"></p>
-<p>Note that the relabeled action shows the new label.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm
deleted file mode 100644
index e1a185e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_retarget_setting.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Setting a global action handler
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Setting a global action handler</h3>
-<p>A plug-in contributes a <a href="wrkAdv_retarget.htm">retargetable action</a>
-for a view or editor part by implementing an <a href="../reference/api/org/eclipse/jface/action/IAction.html"><b>IAction</b></a>
-and registering it as a global action handler with the part's action bars.&nbsp;
-In views, this is usually done at the time that the part creates its actions and
-controls. For editors see <a href="wrkAdv_retarget_contribute_editors.htm">Retargetable editor actions</a>.
-The name of the retargeted action (as defined in <a href="../reference/api/org/eclipse/ui/IWorkbenchActionConstants.html"><b>IWorkbenchActionConstants</b></a>)
-is used to specify which action the handler is intended for.&nbsp; The following
-shows how the workbench task list view registers its handler for the <b>PROPERTIES</b>
-action.</p>
-<pre>public void createPartControl(Composite parent) {
-	...
-	<b>makeActions();</b>
-	...
-
-	// Add global action handlers.
-	...	
-	getViewSite().getActionBars().<b>setGlobalActionHandler(
-		IWorkbenchActionConstants.PROPERTIES,
-		propertiesAction);</b>
-	...</pre>
-<p>The properties action is created in the local method <b>makeActions</b>:</p>
-<pre>void makeActions() {
-	...
-	// properties
-	propertiesAction = new TaskPropertiesAction(this, &quot;properties&quot;); 
-	propertiesAction.setText(TaskListMessages.getString(&quot;Properties.text&quot;)); 
-	propertiesAction.setToolTipText(TaskListMessages.getString(&quot;Properties.tooltip&quot;)); 
-	propertiesAction.setEnabled(false);
-}</pre>
-<p>That's all that is needed.&nbsp; Your action will be run when the user
-chooses the action from the workbench menu bar or tool bar and your view or
-editor is active.&nbsp; The workbench handles the details of ensuring that the
-retargeted action is always associated with the currently active view.  The
-same applies to editor actions supplied through the EditorActionBarContributor.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_services.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_services.htm
deleted file mode 100755
index ee0e72d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_services.htm
+++ /dev/null

@@ -1,269 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Services
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Services</h2>
-<p>The workbench defines a number of services that can be retrieved from the
-<a href="../reference/api/org/eclipse/ui/services/IServiceLocator.html">org.eclipse.ui.services.IServiceLocator</a>.
-Services provide a way for components to retrieve information about the workbench
-without always having to go to the global singleton: <code>PlatformUI.getWorkbench()</code>.
-For example:
-</p>
-<pre>
-		IHandlerService handlerService = (IHandlerService) getSite()
-				.getService(IHandlerService.class);
-</pre>
-<p>
-Some services provide 2 optional abilities, which are usually specified in the 
-service interface javadoc:</p>
-<ul>
-<li>Services that support listeners can clean up the listeners automatically
-when the component's 
-<a href="../reference/api/org/eclipse/ui/services/IServiceLocator.html">org.eclipse.ui.services.IServiceLocator</a>
-(used to get the service) is disposed.</li>
-<li>Services can provide more localized services depending on which component they
-are requested from.</li>
-</ul>
-<p>See <a href="workbench_cmd_handlers.htm" 
-   class="XRef">Associating a handler programmically with a command...</a>
-for an example of the activation localization provided by the 
-<a href="../reference/api/org/eclipse/ui/handlers/IHandlerService.html">org.eclipse.ui.handlers.IHandlerService</a>.
-</p>
-<h3>
-Services Provided by the Workbench
-</h3>
-<p>
-The services provided to by the workbench now includes some of the most
-common services that an
-<a href="../reference/api/org/eclipse/ui/IWorkbenchPart.html">org.eclipse.ui.IWorkbenchPart</a>
-would require.  Support for service related optional abilities are specified in the service javadoc.
-The availability of the service is at and below the level specified.</p>
-<table border="1">
-<tr>
-<th>Service</th>
-<th>Description</th>
-<th>Availability</th>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/keys/IBindingService.html">IBindingService</a>
-</td>
-<td>Provides services related to the binding architecture (e.g., keyboard
-shortcuts) within the workbench.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/commands/ICommandService.html">ICommandService</a>
-</td>
-<td>Provides services related to the command architecture within the workbench.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/commands/ICommandImageService.html">ICommandImageService</a>
-</td>
-<td>Provides a look-up facility for images associated with commands.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/contexts/IContextService.html">IContextService</a>
-</td>
-<td>Provides services related to contexts in the Eclipse workbench, like context
-activation and definitions.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/model/IContributionService.html">IContributionService</a>
-</td>
-<td>Instances of this service are capable of providing standard mechanisms that
-clients may use to order, display, and generally work with contributions to
-the Workbench.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/services/IEvaluationService.html">IEvaluationService</a>
-</td>
-<td>Evaluate a core expression against the workbench application context and
-report updates using a Boolean property.  Also provides the main source for
-the workbench application context.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/swt/IFocusService.html">IFocusService</a>
-</td>
-<td>Tracks focusGained and focusLost events for a Control registered with this
-service, and provides the control and its registered ID as variables to the
-application evaluation context for evaluation by the various services.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/handlers/IHandlerService.html">IHandlerService</a>
-</td>
-<td>Provides services related to activating and deactivating handlers within the
-workbench.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/menus/IMenuService.html">IMenuService</a>
-</td>
-<td>Provides services related to the menu architecture within the workbench.  It
-can be used to populate MenuManagers and ToolBarManagers by components.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/IPageService.html">IPageService</a>
-</td>
-<td>A page service tracks the page and perspective lifecycle events
- within a workbench window.</td>
-<td>Workbench Window</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/IPartService.html">IPartService</a>
-</td>
-<td>A part service tracks the creation and activation of parts within a
- workbench window.</td>
-<td>Workbench Window</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/progress/IProgressService.html">IProgressService</a>
-</td>
-<td>The progress service is the primary interface to the workbench progress support.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/progress/IWorkbenchSiteProgressService.html">IWorkbenchSiteProgressService</a>
-</td>
-<td>The part progress service is an IProgressService that adds API for jobs
-that change the state in a IWorkbenchPartSite while they are being run.</td>
-<td>Part Site</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/ISaveablesLifecycleListener.html">ISaveablesLifecycleListener</a>
-</td>
-<td>Parts that implement 
-<a href="../reference/api/org/eclipse/ui/ISaveablesSource.html">org.eclipse.ui.ISaveablesSource</a>
-should notify their
-<code>ISaveablesLifecycleListener</code>, available as a service from their site, about
-<a href="../reference/api/org/eclipse/ui/Saveable.html">org.eclipse.ui.Saveable</a>
-objects that have been added to or removed from the
-part.  Implementations of <code>ISaveablesSource</code> that are
-not parts should retrieve this service from the
-<a href="../reference/api/org/eclipse/ui/IWorkbench.html">org.eclipse.ui.IWorkbench</a> 
-object.</td>
-<td>Globally</td>
-</tr>
-
-<tr>
-<td><a href="../reference/api/org/eclipse/ui/ISelectionService.html">ISelectionService</a>
-</td>
-<td>A selection service tracks the selection within an a workbench window.</td>
-<td>Workbench Window</td>
-</tr>
-
-</table>
-
-<h3>
-Contributing a Service
-</h3>
-<p>
-Plug-in developers providing a framework in eclipse may also want to provide a service.
-This can be done using the
-<a href="../reference/extension-points/org_eclipse_ui_services.html">org.eclipse.ui.services</a>
-extension point.  Define a service factory based on 
-<a href="../reference/api/org/eclipse/ui/services/AbstractServiceFactory.html">org.eclipse.ui.services.AbstractServiceFactory</a>
-and then specify what services the factory can return.
-A factory can create more than one type of service, but multiple factories cannot
-contribute to the same service type.
-</p>
-<pre>
-      &lt;serviceFactory
-            factoryClass="org.eclipse.ui.examples.contributions.model.PersonServiceFactory"&gt;
-         &lt;service
-               serviceClass="org.eclipse.ui.examples.contributions.model.IPersonService"/&gt;
-      &lt;/serviceFactory&gt;
-</pre>
-<p>
-The create method of the 
-<a href="../reference/api/org/eclipse/ui/services/AbstractServiceFactory.html">org.eclipse.ui.services.AbstractServiceFactory</a>
-passes in 3 parameters:</p>
-<ul>
-<li><code>serviceInterface</code> - the interface class that needs to be created</li>
-<li><code>parentLocator</code> - an
-<a href="../reference/api/org/eclipse/ui/services/IServiceLocator.html">org.eclipse.ui.services.IServiceLocator</a>
-that can be used to get the parent service for <code>serviceInterface</code></li>
-<li><code>locator</code> - the 
-<a href="../reference/api/org/eclipse/ui/services/IServiceLocator.html">org.eclipse.ui.services.IServiceLocator</a>
-that requested this service be created.  It can be used to retrieve dependent services.</li>
-</ul>
-<p>
-Workbench services are organized so there is a global service providing the 
-needed functionality, and a chain of children services.  The children services provide
-the listener cleanup and any data needed to localize the service request.
-</p>
-<p>A service
-factory should return the global service when the <code>parentLocator</code> returns
-<code>null</code> when asked for the <code>serviceInterface</code>.  The global service
-may be the implementation, or a proxy to a plugin provided manager or OSGi service.
-</p>
-<pre>
-		Object parentService = parentLocator.getService(IPersonService.class);
-		if (parentService == null) {
-			return new PersonService(locator);
-		}
-		return new PersonServiceSlave(locator, (IPersonService) parentService);
-		
-		// or ...
-		Object parentService = parentLocator.getService(IPersonService.class);
-		if (parentService == null) {
-			return Activator.getDefault().getPersonManager();
-		}
-		return new PersonServiceSlave(locator, (IPersonService) parentService);
-		
-		//
-		// or as a front to an OSGi service.
-		Object parentService = parentLocator.getService(IPersonService.class);
-		if (parentService == null) {
-			PersonServiceProxy proxy = new PersonServiceProxy(locator,
-			        Activator.getDefault().getBundle().getBundleContext(),
-			        0);
-			proxy.findService();
-			return proxy;
-		}
-		PersonServiceProxy proxy = new PersonServiceProxy(locator,
-		     Activator.getDefault().getBundle().getBundleContext(),
-		     ((PersonServiceProxy)parentService).getLevel()+1);
-		proxy.findService();
-		return proxy;
-</pre>
-<p>In the OSGi service snippet above, instead of having each child <code>IPersonService</code> know
-its parent, each <code>IPersonService</code> talks directly to the OSGi service and uses
-the parent to calculate its "level" which allows it to localize any functionality
-it provides.
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
deleted file mode 100644
index 30ed806..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_singleclick.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Honoring single click support
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Honoring single click support</h2>
-<p>The General <b>Preferences</b> allow users to specify whether views should 
-  open their objects on single or double click. </p>
-
-
-<p><img src="images/singleclick.png" alt="General &quot;Open mode&quot; preferences with disclaimer that the preference may not take effect in all views" border="0"></p>
-
-
-<p>Why the disclaimer about this preference not working for all views?&nbsp;
-Because views contributed by plug-ins must explicitly support this preference in
-their implementation.</p>
-
-
-<p>Recall that a view can be implemented by creating SWT controls and writing
-standard SWT code, or by using <a href="jface_viewers.htm"> JFace viewers</a> 
-to handle the low level details.&nbsp; Honoring
-the single click preference can be done at either level.&nbsp; Most views that
-open other objects present them in a structured, list-like view.&nbsp; We'll
-focus on that kind of view for now.&nbsp; If your view displays objects in a
-different manner, you'll likely use the SWT-level concepts to support single
-click.</p>
-
-
-<h3>Single click in JFace viewers</h3>
-
-
-<p>If you are using a <a href="jface_viewers.htm#listviewer">JFace list-oriented
-viewer</a> to present your objects, supporting single click is
-straightforward.&nbsp; Instead of using <b>addDoubleClickListener</b> to trigger
-opening the items in your view, use <b>addOpenListener</b>.&nbsp; The open
-listener honors the current workbench preference, firing the open event when the
-specified mouse event occurs.</p>
-
-
-<p>You may still wish to use <b>addDoubleClickListener</b> for non-open actions,
-such as expanding the items in a tree on double-click.</p>
-
-
-<h3>Single click in SWT controls</h3>
-
-
-<p>JFace provides a utility class, <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>, 
-  to handle the logistics of single and double click at the SWT control level.&nbsp; 
-  The <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a> 
-  is configured by the General <b>Preferences</b> dialog so that it honors the 
-  current workbench open preference. In fact, the JFace viewers use this class 
-  to implement the open listener.&nbsp; </p>
-
-
-<p>You must create an <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>
-and associate it with your SWT control.&nbsp; The <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>
-will hook the appropriate events and interpret them based on the user
-preferences.&nbsp; Your job is to add an open listener to the strategy that
-implements the code for open.&nbsp; In this way, you are shielded from knowledge
-about which widget event triggered the open event.</p>
-
-
-<pre>OpenStrategy openHandler = new OpenStrategy(control);
-openHandler.addOpenListener(new IOpenEventListener() {
-	public void handleOpen(SelectionEvent e) {
-	// code to handle the open event.
-	...
-	}
-}</pre>
-<p>The other workbench preferences for open (select on hover,
-open using arrow keys) are also handled by <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>.&nbsp;
-This means that the &quot;right thing&quot; will happen if you use JFace viewers
-or the <a href="../reference/api/org/eclipse/jface/util/OpenStrategy.html"><b>OpenStrategy</b></a>
-class to implement open behavior.</p>
-<h3>Activating editors on open</h3>
-<p>When handling an open event, you should use <b>OpenStrategy.activateOnOpen() </b>to
-determine whether an opened editor should be activated by default.&nbsp;
-Activating an editor switches the focus from the view to the editor, which can
-be particularly confusing and undesirable in single click mode. </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
deleted file mode 100644
index 77e9dfa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo.htm
+++ /dev/null

@@ -1,316 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Undoable operations
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Undoable operations</h2>
-<p>We've looked at many different ways to contribute actions to the workbench, but we
-haven't focused on the implementation of an action's <tt>run()</tt> method.  The mechanics
-of the method depend on the specific action in question, but structuring the code as an
-<b>undoable operation</b> allows the action to participate in the platform undo and redo
-support.</p>
-<p>
-The platform provides an <b>undoable operations framework</b> in the package
-<b><a href="../reference/api/org/eclipse/core/commands/operations/package-summary.html">org.eclipse.core.commands.operations</a></b>.
-By implementing the code inside a <tt>run()</tt> method to create an
-<a href="../reference/api/org/eclipse/core/commands/operations/IUndoableOperation.html"><b>IUndoableOperation</b></a>,
-the operation can be made available for undo and redo.  Converting an action to use operations is straightforward, 
-apart from implementing the undo and redo behavior itself.</p>
-<h3>Writing an undoable operation</h3>
-<p>
-We'll start by looking at a very simple example.  Recall the simple 
-<b>ViewActionDelegate</b> provided in the readme example plug-in.  When
-invoked, the action simply launches a dialog that announces it was executed.</p>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	MessageDialog.openInformation(view.getSite().getShell(),
-		MessageUtil.getString(&quot;Readme_Editor&quot;),  
-		MessageUtil.getString(&quot;View_Action_executed&quot;)); 
-}</pre>
-
-Using operations, the run method is responsible for creating an operation that does
-the work formerly done in the run method, and requesting that an <b>operations history</b> 
-execute the operation, so that it can be remembered for undo and redo.
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation(
-		view.getSite().getShell()); 
-	...
-	operationHistory.execute(operation, null, null);
-}
-</pre>
-The operation encapsulates the old behavior from the run method, as well as the undo
-and redo for the operation.
-<pre>
-class ReadmeOperation extends AbstractOperation {
-	Shell shell;
-	public ReadmeOperation(Shell shell) {
-		super("Readme Operation");
-		this.shell = shell;
-	}
-	public IStatus execute(IProgressMonitor monitor, IAdaptable info) {
-		MessageDialog.openInformation(shell,
-			MessageUtil.getString(&quot;Readme_Editor&quot;),  
-			MessageUtil.getString(&quot;View_Action_executed&quot;));   
-		return Status.OK_STATUS;
-	}
-	public IStatus undo(IProgressMonitor monitor, IAdaptable info) {
-		MessageDialog.openInformation(shell,
-			MessageUtil.getString(&quot;Readme_Editor&quot;),  
-			&quot;Undoing view action&quot;);   
-		return Status.OK_STATUS;
-	}
-	public IStatus redo(IProgressMonitor monitor, IAdaptable info) {
-		MessageDialog.openInformation(shell,
-			MessageUtil.getString(&quot;Readme_Editor&quot;),  
-			&quot;Redoing view action&quot;);   
-		return Status.OK_STATUS;
-	}
-}
-</pre>
-
-<p>
-For simple actions, it may be possible to move all of the nuts and bolt work into the operation class.
-In this case, it may be appropriate to collapse the former action classes into a single action class
-that is parameterized.  The action would simply execute the supplied operation when it is time to run.
-This is largely an application design decision.  
-</p>
-<p>
-When an action launches a wizard, then the operation is typically created as part of the wizard's 
-<tt>performFinish()</tt> method or a wizard page's <tt>finish()</tt> method.  Converting the <tt>finish</tt> method
-to use operations is similar to converting a <tt>run</tt> method.  The method is responsible for creating
-and executing an operation that does the work previously done inline.
-</p>
-<h3>Operation history</h3>
-<p>
-So far we've used an <b>operations history</b> without really explaining it.
-Let's look again at the code that creates our example operation.</p>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation(
-		view.getSite().getShell()); 
-	...
-	<b>operationHistory.execute(operation, null, null);</b>
-}
-</pre>
-What is the <b>operation history</b> all about?  
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>
-defines the interface for the object that keeps track of all of the undoable operations.  When an operation history
-executes an operation, it first executes the operation, and then adds it to the undo history.
-Clients that wish to undo and redo operations do so by using 
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>
-protocol.  
-
-<p>
-The operation history used by an application can be retrieved in several ways.  The simplest way is to use the
-<a href="../reference/api/org/eclipse/core/commands/operations/OperationHistoryFactory.html"><b>OperationHistoryFactory</b></a>.</p>
-<pre>IOperationHistory operationHistory = OperationHistoryFactory.getOperationHistory();
-</pre>
-
-<p>
-The workbench can also be used to retrieve the operations history.  The workbench configures the default
-operation history and also provides protocol to access it.  The following snippet demonstrates how to
-obtain the operation history from the workbench. </p>
-<pre>
-IWorkbench workbench = view.getSite().getWorkbenchWindow().getWorkbench();
-IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-</pre>
-Once an operation history is obtained, it can be used to query the undo or redo history, find out which operation
-is the next in line for undo or redo, or to undo or redo particular operations.  Clients can add an
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistoryListener.html"><b>IOperationHistoryListener</b></a>
-in order to receive notifications about changes to the history.  Other protocol allows clients
-to set limits on the history or notify listeners about changes to a particular operation.  Before
-we look at the protocol in detail, we need to understand the <b>undo context</b>.
-
-<h4>Undo contexts</h4>
-<p>
-When an operation is created, it is assigned an <b>undo context</b> that describes the user context in which the original
-operation was performed.  The undo context typically depends on the view or editor that originated the undoable operation.  For
-example, changes made inside an editor are often local to that editor.  In this case, the editor should create its own
-own undo context and assign that context to operations it adds to the history.  In this way, all of the operations performed in the
-editor are considered local and semi-private.  Editors or views that operate on a shared model often use an undo context that is related
-to the model that they are manipulating.  By using a more general undo context, operations performed by one view or editor
-may be available for undo in another view or editor that operates on the same model.</p>
-<p>Undo contexts are relatively simple in behavior; the protocol for
-<a href="../reference/api/org/eclipse/core/commands/operations/IUndoContext.html"><b>IUndoContext</b></a> is fairly
-minimal.  The main role of a context is to "tag" a particular operation as belonging in that undo context, in order to distinguish
-it from operations created in different undo contexts.  This allows the operation history to keep track of the global history of all undoable
-operations that have been executed, while views and editors can filter the history for a specific point of view using the undo context.
-</p>
-<p>
-Undo contexts can be created by the plug-in that is creating the undoable operations, or accessed through API.  For
-example, the workbench provides access to an undo context that can be used for workbench-wide operations.  However they
-are obtained, undo contexts should be assigned when an operation is created.  The following snippet shows how the
-readme plug-in's <b>ViewActionDelegate</b> could assign a workbench-wide context to its operations.
-</p>
-<pre>
-public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation(
-		view.getSite().getShell()); 
-	IWorkbench workbench = view.getSite().getWorkbenchWindow().getWorkbench();
-	IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-	IUndoContext undoContext = workbench.getOperationSupport().getUndoContext();
-	operation.addContext(undoContext);
-	operationHistory.execute(operation, null, null);
-}
-</pre>
-<p>
-Why use undo contexts at all?  Why not use separate operation histories for separate views and editors?  Using separate operation
-histories assumes that any particular view or editor maintains its own private undo history, and that undo has no global meaning
-in the application.  This may be appropriate for some applications, and in these cases each view or editor should create its own
-separate undo context.  Other applications may wish to implement a global undo that applies to all user operations, regardless of
-the view or editor where they originated.  In this case, the workbench context should be used by all plug-ins that add operations
-to the history.  </p>
-<p>In more complicated applications, the undo is neither strictly local or strictly global.  Instead, there is some
-cross-over between undo contexts.  This can be achieved by assigning multiple contexts to an operation.  For example, an IDE workbench view may 
-manipulate the entire workspace and consider the workspace its undo context.  An editor that is open on a particular
-resource in the workspace may consider its operations mostly local.  However, operations performed inside the editor may 
-in fact affect both the particular resource and the workspace at large.  (A good example of this case is the JDT refactoring support,
-which allows structural changes to a Java element to occur while editing the source file).  In these cases, it is useful to be able to add both
-undo contexts to the operation so that the undo can be performed from the editor itself, as well as those views that manipulate the
-workspace.
-</p>
-<p>
-Now that we understand what an undo context does, we can look again at the protocol for
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>.
-The following snippet is used to perform an undo on the some context:</p>
-<pre>IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-try {
-	IStatus status = operationHistory.undo(myContext, progressMonitor, someInfo);
-} catch (ExecutionException e) {
-	// handle the exception 
-}
-</pre>
-The history will obtain the most recently performed operation that has the given context and ask it to undo
-itself.  Other protocol can be used to get the entire undo or redo history for a context, or to find the operation
-that will be undone or redone in a partcular context.  The following snippet obtains the label for the operation
-that will be undone in a particular context.
-<pre>
-IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-String label = history.getUndoOperation(myContext).getLabel();
-</pre>
-
-<p>
-The global undo context, <b>IOperationHistory.GLOBAL_UNDO_CONTEXT</b>, may be used to refer to the global
-undo history.  That is, to all of the operations in the history regardless of their specific context.  The
-following snippet obtains the global undo history.
-</p>
-<pre>
-IOperationHistory operationHistory = workbench.getOperationSupport().getOperationHistory();
-IUndoableOperation [] undoHistory = operationHistory.getUndoHistory(IOperationHistory.GLOBAL_UNDO_CONTEXT);
-</pre>
-<p>
-Whenever an operation is executed, undone, or redone using operation history protocol, clients can
-provide a progress monitor and any additional UI info that may be needed for performing the operation.
-This information is passed to the operation itself.  In our original
-example, the readme action constructed an operation with a shell parameter that could be used to open
-the dialog.  Instead of storing the shell in the operation, a better approach is to pass parameters
-to the execute, undo, and redo methods that provide any UI information needed to run the operation.  These
-parameters will be passed on to the operation itself.</p>
-<pre>public void run(org.eclipse.jface.action.IAction action) {
-	IUndoableOperation operation = new ReadmeOperation();
-	...
-	<b>operationHistory.execute(operation, null, infoAdapter);</b>
-}
-</pre> 
-The <b>infoAdapter</b> is an <a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"><b>IAdaptable</b></a>
-that minimally can provide the <a href="../reference/api/org/eclipse/swt/widgets/Shell.html"><b>Shell</b></a> that can
-be used when launching dialogs.  Our example operation would use this parameter as follows:
-<pre>
-public IStatus execute(IProgressMonitor monitor, IAdaptable info) {
-	if (info != null) {
-		Shell shell = (Shell)info.getAdapter(Shell.class);
-		if (shell != null) {
-			MessageDialog.openInformation(shell,
-				MessageUtil.getString(&quot;Readme_Editor&quot;),  
-				MessageUtil.getString(&quot;View_Action_executed&quot;));   
-			return Status.OK_STATUS;
-		}
-	}
-	// do something else...
-}
-</pre> 
-
-<h3>Undo and redo action handlers</h3>
-<p>The platform provides standard undo and redo <a href="wrkAdv_retarget.htm"><b>retargetable action handlers</b></a> 
-that can be configured by views and editors to provide undo and redo support for their particular context.  When the 
-action handler is created, a context is assigned to it so that the operations history is filtered in a way appropriate for
-that particular view.  The action handlers take care of updating the undo and redo labels to show the current
-operation in question, providing the appropriate progress monitor and UI info to the operation history, and
-optionally pruning the history when the current operation is invalid.  An action group that creates the action handlers
-and assigns them to the global undo and redo actions is provided for convenience.</p>
-<pre>new UndoRedoActionGroup(this.getSite(), undoContext, true);
-</pre>
-The last parameter is a boolean indicating whether the undo and redo histories for the specified context should
-be disposed when the operation currently available for undo or redo is not valid.  The setting for this parameter
-is related to the undo context provided and the validation strategy used by operations with that context.
-
-<h3>Application undo models</h3>
-<p>
-Earlier we looked at how undo contexts can be used to implement different kinds of application undo models.
-The ability to assign one or more contexts to operations allows applications to implement undo strategies that
-are strictly local to each view or editor, strictly global across all plug-ins, or some model in between.
-Another design decision involving undo and redo is whether any operation can be undone or redone at any time,
-or whether the model is strictly linear, with only the most recent operation being considered for undo or
-redo.
-</p>
-<p>
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>
-defines protocol that allows flexible undo models, leaving it up to individual implementations to determine what is allowed.
-The undo and redo protocol we've seen so far assumes that there is only one implied operation available for undo or redo in a particular
-undo context.  Additional protocol is provided to allow clients to execute a specific operation, regardless
-of its position in the history.  The operation history can be configured so that the model appropriate for an
-application can be implemented.  This is done with an interface that is used to pre-approve any undo or redo request
-before the operation is undone or redone.</p>
-<h4>Operation approvers</h4>
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationApprover.html"><b>IOperationApprover</b></a>
-defines the protocol for approving undo and redo of a particular operation.  An operation approver is installed on an operation history.  Specific
-operation approvers may in turn check all operations for their validity, check operations of only certain contexts,
-or prompt the user when unexpected conditions are found in an operation. 
-The following snippet shows how an application could configure the operation history to enforce a linear undo model for all
-operations.
-<pre>
-IOperationHistory history = OperationHistoryFactory.getOperationHistory();
-
-// set an approver on the history that will disallow any undo that is not the most recent operation
-history.addOperationApprover(new LinearUndoEnforcer());
-
-</pre>
-<p>
-In this case, an operation approver provided by the framework, 
-<a href="../reference/api/org/eclipse/core/commands/operations/LinearUndoEnforcer.html"><b>LinearUndoEnforcer</b></a>,
-is installed on the history to prevent the undo or redo of any operation that is not the most recently done or undone
-operation in all of its undo contexts.</p>
-<p>
-Another operation approver, 
-<a href="../reference/api/org/eclipse/ui/operations/LinearUndoViolationUserApprover.html"><b>LinearUndoViolationUserApprover</b></a>,
-detects the same condition and prompts the user as to whether the operation should be allowed to continue.  This operation
-approver can be installed on a particular workbench part.</p>
-<pre>IOperationHistory history = OperationHistoryFactory.getOperationHistory();
-
-// set an approver on this part that will prompt the user when the operation is not the most recent.
-IOperationApprover approver = new LinearUndoViolationUserApprover(myUndoContext, myWorkbenchPart);
-history.addOperationApprover(approver);
-</pre>
-
-<p>
-Plug-in developers are free to develop and install their own operation approvers for implementing 
-application-specific undo models and approval strategies.  In your plug-in, it may be appropriate to seek 
-approval for the original execution of an operation, in addition to the undo and redo of the operation.
-If this is the case, your operation approver should also implement 
-<a href="../reference/api/org/eclipse/core/commands/operations/IOperationApprover2.html"><b>IOperationApprover2</b></a>,
-which approves the execution of the operation.  When asked to execute an operation, the platform operation history 
-will seek approval from any operation approver that implements this interface.  </p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo_ide.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo_ide.htm
deleted file mode 100644
index 5081c73..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_undo_ide.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Undo and the IDE Workbench
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Undo and the IDE Workbench</h3>
-<p>
-We've seen code snippets that use workbench protocol for accessing the operations history and the workbench undo
-context.  This is achieved using <a href="../reference/api/org/eclipse/ui/operations/IWorkbenchOperationSupport.html"><b>IWorkbenchOperationSupport</b></a>,
-which can be obtained from the workbench.  The notion of a workbench-wide undo context is fairly general.  It is up to the workbench application
-to determine what specific scope is implied by the workbench undo context, and which views or editors use the
-workbench context when providing undo support.
-</p>
-<p>
-In the case of the Eclipse IDE workbench, the workbench undo context should be assigned to any operation that affects the IDE workspace at large.
-This context is used by views that manipulate the workspace, such as the Resource Navigator.  The IDE workbench installs an adapter on
-the workspace for <a href="../reference/api/org/eclipse/core/commands/operations/IUndoContext.html"><b>IUndoContext</b></a> that returns the
-workbench undo context.  This model-based registration allows plug-ins that manipulate the workspace to obtain the appropriate undo context, even if they are headless and
-do not reference any workbench classes.</p>
-<pre>// get the operation history
-IOperationHistory history = OperationHistoryFactory.getOperationHistory();
-
-// obtain the appropriate undo context for my model
-IUndoContext workspaceContext = (IUndoContext)ResourcesPlugin.getWorkspace().getAdapter(IUndoContext.class);
-if (workspaceContext != null) {
-	// create an operation and assign it the context
-}
-
-</pre>
-Other plug-ins are encouraged to use this same technique for registering
-model-based undo contexts.
-<h3>Undoable Workspace Operations</h3>
-<p>
-Undoable operations are provided by the IDE plug-in that allow you to execute, 
-undo, and redo common workspace manipulations.  Operations are provided for
-creating, moving, copying, and deleting projects, folders, and files.  The IDE
-plug-in uses these operations to provide undo support in the Resource Navigator.
-These classes can also be used by clients.  They are available in the package
-<a href="../reference/api/org/eclipse/ui/ide/undo/package-summary.html"><b>org.eclipse.ui.ide.undo</b></a>.
- </p>
-<p>
-Using the workspace undoable operations is similar to the examples shown for using
-any <a href="../reference/api/org/eclipse/core/commands/operations/IUndoableOperation.html"><b>IUndoableOperation</b></a>.
-The primary difference is that some of the details, such as assigning the appropriate
-undo context, are handled internally by the operation.  The following snippet shows
-how to use an undoable operation for creating a new file.
-</p>
-<pre>
-IFile newFileHandle = IDEWorkbenchPlugin.getPluginWorkspace().getRoot().
-	getFile(myNewFilePath);
-CreateFileOperation op = new CreateFileOperation(newFileHandle, null,
-	initialContentStream, "Create New File");
-</pre>
-<p>
-The operation is configured with a file handle for the file to be created, an
-input stream with the initial contents, and a label describing the operation.  Internally,
-the operation will assign the workspace undo context and handle other details such
-as keeping track of which resources the operation manipulates.  To execute the operation,
-the caller uses the standard <a href="../reference/api/org/eclipse/core/commands/operations/IOperationHistory.html"><b>IOperationHistory</b></a>
-protocol.  
-</p>
-<pre>
-try {
-	PlatformUI.getWorkbench().getOperationSupport().getOperationHistory()
-		.execute(op, myProgressMonitor, 
-			WorkspaceUndoUtil.getUIInfoAdapter(getShell()));
-} catch (final ExecutionException e) {
-	// handle exceptions
-}
-</pre>
-<p>
-Note that the caller is responsible for providing a progress monitor if desired, and
-an <a href="../reference/api/org/eclipse/core/runtime/IAdaptable.html"><b>IAdaptable</b></a> that
-can provide the shell that should be used for any prompting. The utility class
-<a href="../reference/api/org/eclipse/ui/ide/undo/WorkspaceUndoUtil.html"><b>WorkspaceUndoUtil</b></a>
-provides a utility method for creating the necessary adapter from a shell.  
-</p>
-<p>Callers are also responsible for determining whether to execute the operation in 
-the UI thread, the background, or a workbench job.  If the operation should be executed 
-in the background, then the caller should create the appropriate progress monitor and run the 
-snippet shown above in the appropriate runnable.  
-</p>
-<p>The undo and redo of the operation will be performed by the undo and redo action handlers
-when the user initiates undo or redo.  The standard workbench action handlers use 
-<a href="../reference/api/org/eclipse/core/commands/operations/IAdvancedUndoableOperation2.html"><b>IAdvancedUndoableOperation2</b></a>
-protocol to determine how to perform the undo and redo of operations.
-All of the workspace operations implement protocol that instructs clients to run the undo or redo 
-of the operation in the background if possible.
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm b/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
deleted file mode 100644
index e785452..0000000
--- a/bundles/org.eclipse.platform.doc.isv/guide/wrkAdv_workingsets.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-Working sets
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Working sets</h2>
-<p>Users often find it necessary to filter views such as the navigator view in
-order to reduce clutter.&nbsp; Plug-ins can assist in filtering using different
-techniques.</p>
-
-
-<ul>
-  <li><a href="workbench_advext_resourceFilters.htm">Resource filters</a>
-    can be used to filter by file name.&nbsp; Plug-ins contribute resource
-    filters that the user can enable using a view's filter selection dialog.</li>
-  <li><b>Working sets</b> can be used to filter resources by only including
-    specified resources.&nbsp; Working sets are selected using the view's
-    working set dialog.</li>
-</ul>
-<p><img src="images/workingset.png" alt="Working set selection dialog" border="0"></p>
-<p>If your plug-in implements a view that shows resources (or objects that are
-adaptable to <a href="../reference/api/org/eclipse/core/resources/IResource.html"><b>IResource</b></a>),
-you should support working sets.&nbsp; <b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>provides API for manipulating working sets.&nbsp; You can obtain an <b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>using <b><a href="../reference/api/org/eclipse/ui/IWorkbench.html">IWorkbench</a></b>
-API.</p>
-<pre>IWorkingSetManager manager = workbench.getWorkingSetManager();</pre>
-<p><b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>allows you to<b> </b>manipulate and create working sets:</p>
-<ul>
-  <li><b>createWorkingSetSelectionDialog</b> - returns a working set dialog that shows the user the current working
-  sets. You can get the selected working sets from the dialog once it is
-  closed.</li>
-  <li><b>createWorkingSetEditWizard</b> - returns a working set edit wizard for editing the specified working
-  set</li>
-  <li><b>getWorkingSets()</b> - returns a list of all defined working sets</li>
-  <li><b>getWorkingSet(String name) </b>- returns a working set specified by
-    name</li>
-</ul>
-<p><b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>also provides property change notification as working sets are added,
-removed, or as they change.&nbsp; If your view or editor needs to respond to
-changes in the selected working set, it can add a listener for <b>CHANGE_WORKING_SET_CONTENT_CHANGE.</b></p>
-<h3>Adding new working set types</h3>
-
-
-<p>For many plug-ins, using <b><a href="../reference/api/org/eclipse/ui/IWorkingSetManager.html">IWorkingSetManager</a>
-</b>to provide resource filtering is sufficient.&nbsp; If your plug-in needs to
-define working sets differently, it can register a new type of working set using
-<b><a href="../reference/extension-points/org_eclipse_ui_workingSets.html">org.eclipse.ui.workingSets</a></b>.&nbsp;
-The Java tooling uses this feature to define a Java working set type.&nbsp;
-Working set types are shown when the user decides to add a working set.</p>
-
-
-<p><img src="images/workingSetTypes.png" alt="Working set dialog showing list of available types" border="0"></p>
-
-
-<p>&nbsp;</p>
-
-
-<p>When you define your own type of working set, you can use <b><a href="../reference/api/org/eclipse/ui/IWorkingSet.html">IWorkingSet</a>.getId</b> protocol to ensure that the working set matches the type that you have
-defined.&nbsp; Any working sets that you create programmatically must have
-their id set to the id of a working set page that can display the working
-set elements.&nbsp; This id is used to ensure that the proper working set
-edit page is launched when the user edits the working set.&nbsp; A null
-id indicates that the working set should use the default resource working
-set type.</p>
-
-
-<p>See the
-<b><a href="../reference/extension-points/org_eclipse_ui_workingSets.html">org.eclipse.ui.workingSets</a>
-</b>extension point documentation and <b><a href="../reference/api/org/eclipse/ui/IWorkingSet.html">IWorkingSet</a></b>
-protocol for more detail.</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.isv/notices.html b/bundles/org.eclipse.platform.doc.isv/notices.html
deleted file mode 100644
index b2201a7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2009.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/platformOptions.txt b/bundles/org.eclipse.platform.doc.isv/platformOptions.txt
deleted file mode 100644
index 582634d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/platformOptions.txt
+++ /dev/null

@@ -1,398 +0,0 @@
--quiet
--encoding "iso-8859-1"
--charset "iso-8859-1"
-../org.eclipse.osgi/eclipseAdaptor/src/org/eclipse/core/runtime/adaptor/EclipseStarter.java
--sourcepath "
-;../org.eclipse.equinox.app/src
-;../org.eclipse.equinox.common/src
-;../org.eclipse.equinox.http.jetty_2.0.0/src
-;../org.eclipse.equinox.http.registry/src
-;../org.eclipse.equinox.http.servlet/src
-;../org.eclipse.equinox.jsp.jasper/src
-;../org.eclipse.equinox.jsp.jasper.registry/src
-;../org.eclipse.equinox.preferences/src
-;../org.eclipse.equinox.registry/src
-;../org.eclipse.equinox.security/src
-;../org.eclipse.core.jobs/src
-;../org.eclipse.core.contenttype/src
-;../org.eclipse.core.runtime.compatibility/src-runtime
-;../org.eclipse.core.runtime.compatibility/src-model
-;../org.eclipse.core.commands/src
-;../org.eclipse.platform/src
-;../org.eclipse.ant.core/src
-;../org.eclipse.compare/compare
-;../org.eclipse.compare.core/src
-;../org.eclipse.core.databinding/src
-;../org.eclipse.core.databinding.beans/src
-;../org.eclipse.core.databinding.observable/src
-;../org.eclipse.core.databinding.property/src
-;../org.eclipse.jface.databinding/src
-;../org.eclipse.debug.core/core
-;../org.eclipse.debug.ui/ui
-;../org.eclipse.help/src
-;../org.eclipse.help.base/src
-;../org.eclipse.help.base/src_demo
-;../org.eclipse.help.ui/src
-;../org.eclipse.help.webapp/src
-;../org.eclipse.core.runtime/src
-;../org.eclipse.core.resources/src
-;../org.eclipse.pde/src
-;../org.eclipse.jface/src
-;../org.eclipse.jface.text/src
-;../org.eclipse.jface.text/projection
-;../org.eclipse.text/src
-;../org.eclipse.text/projection
-;../org.eclipse.ui/src
-;../org.eclipse.ui.cheatsheets/src
-;../org.eclipse.ui.intro/src
-;../org.eclipse.ui.intro.universal/src
-;../org.eclipse.ui.console/src
-;../org.eclipse.ui.editors/src
-;../org.eclipse.ui.forms/src
-;../org.eclipse.ui.ide/src
-;../org.eclipse.ui.ide/extensions
-;../org.eclipse.ui.views/src
-;../org.eclipse.ui.views.properties.tabbed/src
-;../org.eclipse.ui.workbench/Eclipse UI
-;../org.eclipse.ui.workbench/Eclipse UI Editor Support
-;../org.eclipse.ui.navigator/src
-;../org.eclipse.ui.navigator.resources/src
-;../org.eclipse.ui.workbench.texteditor/src
-;../org.eclipse.swt/Eclipse SWT/win32/
-;../org.eclipse.swt/Eclipse SWT/common/
-;../org.eclipse.swt/Eclipse SWT/common_j2se/
-;../org.eclipse.swt/Eclipse SWT AWT/win32/
-;../org.eclipse.swt/Eclipse SWT AWT/common/
-;../org.eclipse.swt/Eclipse SWT Custom Widgets/common/
-;../org.eclipse.swt/Eclipse SWT Drag and Drop/win32/
-;../org.eclipse.swt/Eclipse SWT Drag and Drop/common/
-;../org.eclipse.swt/Eclipse SWT OLE Win32/win32/
-;../org.eclipse.swt/Eclipse SWT Printing/win32/
-;../org.eclipse.swt/Eclipse SWT Printing/common/
-;../org.eclipse.swt/Eclipse SWT Program/win32/
-;../org.eclipse.swt/Eclipse SWT Program/common/
-;../org.eclipse.swt/Eclipse SWT PI/win32/
-;../org.eclipse.swt/Eclipse SWT PI/common/
-;../org.eclipse.swt/Eclipse SWT PI/common_j2se/
-;../org.eclipse.swt/Eclipse SWT Accessibility/win32/
-;../org.eclipse.swt/Eclipse SWT Accessibility/common/
-;../org.eclipse.swt/Eclipse SWT Browser/win32/
-;../org.eclipse.swt/Eclipse SWT Browser/common/
-;../org.eclipse.team.core/src
-;../org.eclipse.team.ui/src
-;../org.eclipse.core.net/src
-;../org.eclipse.jsch.core/src
-;../org.eclipse.jsch.ui/src
-;../org.eclipse.update.configurator/src
-;../org.eclipse.update.core/src
-;../org.eclipse.update.core/jarprocessor
-;../org.eclipse.search/search
-;../org.eclipse.search/new search
-;../org.eclipse.core.filebuffers/src
-;../org.eclipse.core.variables/src
-;../org.eclipse.core.expressions/src
-;../org.eclipse.ltk.core.refactoring/src
-;../org.eclipse.ltk.ui.refactoring/src
-;../org.eclipse.osgi/core/adaptor
-;../org.eclipse.osgi/supplement/src
-;../org.eclipse.osgi/eclipseAdaptor/src
-;../org.eclipse.osgi/security/src
-;../org.eclipse.core.filesystem/src
-;../org.eclipse.swt/Eclipse SWT OpenGL/common
-;../org.eclipse.swt/Eclipse SWT OpenGL/emulated
-;../org.eclipse.swt/Eclipse SWT OpenGL/glx
-;../org.eclipse.swt/Eclipse SWT OpenGL/win32"
--d reference/api
--classpath @rt@
-;../com.ibm.icu_4.0.1.v20090822.jar
-;../org.apache.ant_1.7.1.v20090120-1145/lib/ant.jar
-;../org.eclipse.osgi/@dot
-;../org.eclipse.osgi.services/@dot
-;../javax.servlet_2.5.0.v200806031605.jar
-;../org.mortbay.jetty.server_6.1.15.v200905151201.jar
-;../org.mortbay.jetty.util_6.1.15.v200905182336.jar
-;../org.apache.lucene_1.9.1.v20080530-1600.jar
-;../org.apache.lucene.analysis_1.9.1.v20080530-1600.jar
-;../org.eclipse.help/@dot
-;../org.eclipse.help.appserver/@dot
-;../org.eclipse.help.base/@dot
-;../org.eclipse.help.webapp/@dot
-;../org.eclipse.update.ui/@dot
-;../org.eclipse.core.filesystem/@dot
-;../org.eclipse.core.jobs/@dot
-;../org.eclipse.core.runtime.compatibility.auth/@dot
-;../org.eclipse.equinox.registry/@dot
-;../org.eclipse.equinox.security/@dot
-;../org.eclipse.equinox.app/@dot
-;../org.eclipse.equinox.common/@dot
-;../org.eclipse.equinox.preferences/@dot
-;../org.eclipse.equinox.supplement/@dot
-;../org.eclipse.core.contenttype/@dot
-;../org.eclipse.ui.forms/@dot
-;../org.eclipse.ui.navigator.resources/@dot
-;../org.eclipse.ui.intro/@dot
-;../com.jcraft.jsch_0.1.41.v200903070017.jar
--breakiterator
--use
--splitIndex
--tag 'TrackedGetter:cm:"TrackedGetter"'
--tag 'noimplement:a:Restriction:'
--tag 'noextend:a:Restriction:'
--tag 'noreference:a:Restriction:'
--tag 'noinstantiate:a:Restriction:'
--tag 'nooverride:a:Restriction:'
--windowtitle "Eclipse Platform API Specification"
--doctitle "Eclipse Platform API Specification"
--header "<b>Eclipse Platform</b><br>Release 3.5"
--bottom '<font size="-1"><p><a href="{@docRoot}/../misc/api-usage-rules.html">Guidelines for using Eclipse APIs</a>.</p><p>Copyright (c) Eclipse contributors and others 2000, 2008. All rights reserved.</p></font>'
--link http://java.sun.com/j2se/1.4.2/docs/api
--link http://www.osgi.org/javadoc/r4v42
-
-org.eclipse.ant.core
-org.eclipse.compare
-org.eclipse.compare.contentmergeviewer
-org.eclipse.compare.patch
-org.eclipse.compare.rangedifferencer
-org.eclipse.compare.structuremergeviewer
-org.eclipse.core.commands
-org.eclipse.core.commands.common
-org.eclipse.core.commands.contexts
-org.eclipse.core.commands.operations
-org.eclipse.core.databinding
-org.eclipse.core.databinding.beans
-org.eclipse.core.databinding.conversion
-org.eclipse.core.databinding.observable
-org.eclipse.core.databinding.observable.list
-org.eclipse.core.databinding.observable.map
-org.eclipse.core.databinding.observable.masterdetail
-org.eclipse.core.databinding.observable.set
-org.eclipse.core.databinding.observable.value
-org.eclipse.core.databinding.property
-org.eclipse.core.databinding.property.list
-org.eclipse.core.databinding.property.map
-org.eclipse.core.databinding.property.set
-org.eclipse.core.databinding.property.value
-org.eclipse.core.databinding.util
-org.eclipse.core.databinding.validation
-org.eclipse.core.expressions
-org.eclipse.core.filebuffers
-org.eclipse.core.filebuffers.manipulation
-org.eclipse.core.filesystem
-org.eclipse.core.filesystem.provider
-org.eclipse.core.net.proxy
-org.eclipse.core.resources
-org.eclipse.core.resources.refresh
-org.eclipse.core.resources.team
-org.eclipse.core.resources.mapping
-org.eclipse.core.runtime
-org.eclipse.core.runtime.content
-org.eclipse.core.runtime.dynamichelpers
-org.eclipse.core.runtime.jobs
-org.eclipse.core.runtime.model
-org.eclipse.core.runtime.preferences
-org.eclipse.core.runtime.spi
-org.eclipse.core.variables
-org.eclipse.debug.core
-org.eclipse.debug.core.commands
-org.eclipse.debug.core.model
-org.eclipse.debug.core.sourcelookup
-org.eclipse.debug.core.sourcelookup.containers
-org.eclipse.debug.ui
-org.eclipse.debug.ui.actions
-org.eclipse.debug.ui.console
-org.eclipse.debug.ui.contexts
-org.eclipse.debug.ui.memory
-org.eclipse.debug.ui.sourcelookup
-org.eclipse.equinox.app
-org.eclipse.equinox.http.jetty
-org.eclipse.equinox.http.registry
-org.eclipse.equinox.http.servlet
-org.eclipse.equinox.jsp.jasper
-org.eclipse.equinox.jsp.jasper.registry
-org.eclipse.equinox.security.auth
-org.eclipse.equinox.security.auth.credentials
-org.eclipse.equinox.security.auth.module
-org.eclipse.equinox.security.storage
-org.eclipse.equinox.security.storage.provider
-org.eclipse.help
-org.eclipse.help.browser
-org.eclipse.help.search
-org.eclipse.help.server
-org.eclipse.help.standalone
-org.eclipse.help.ui
-org.eclipse.help.ui.browser
-org.eclipse.help.webapp
-org.eclipse.jface.action
-org.eclipse.jface.bindings
-org.eclipse.jface.bindings.keys
-org.eclipse.jface.bindings.keys.formatting
-org.eclipse.jface.commands
-org.eclipse.jface.contentassist
-org.eclipse.jface.contexts
-org.eclipse.jface.databinding.dialog
-org.eclipse.jface.databinding.preference
-org.eclipse.jface.databinding.swt
-org.eclipse.jface.databinding.util
-org.eclipse.jface.databinding.viewers
-org.eclipse.jface.databinding.wizard
-org.eclipse.jface.dialogs
-org.eclipse.jface.fieldassist
-org.eclipse.jface.layout
-org.eclipse.jface.menus
-org.eclipse.jface.operation
-org.eclipse.jface.preference
-org.eclipse.jface.resource
-org.eclipse.jface.text
-org.eclipse.jface.text.contentassist
-org.eclipse.jface.text.formatter
-org.eclipse.jface.text.hyperlink
-org.eclipse.jface.text.information
-org.eclipse.jface.text.link
-org.eclipse.jface.text.presentation
-org.eclipse.jface.text.projection
-org.eclipse.jface.text.quickassist
-org.eclipse.jface.text.reconciler
-org.eclipse.jface.text.revisions
-org.eclipse.jface.text.rules
-org.eclipse.jface.text.source
-org.eclipse.jface.text.source.projection
-org.eclipse.jface.text.templates
-org.eclipse.jface.text.templates.persistence
-org.eclipse.jface.util
-org.eclipse.jface.viewers
-org.eclipse.jface.viewers.deferred
-org.eclipse.jface.window
-org.eclipse.jface.wizard
-
-org.eclipse.jsch.core
-org.eclipse.jsch.ui
-
-org.eclipse.ltk.core.refactoring
-org.eclipse.ltk.core.refactoring.history
-org.eclipse.ltk.core.refactoring.model
-org.eclipse.ltk.core.refactoring.participants
-org.eclipse.ltk.core.refactoring.resource
-org.eclipse.ltk.ui.refactoring
-org.eclipse.ltk.ui.refactoring.actions
-org.eclipse.ltk.ui.refactoring.history
-org.eclipse.ltk.ui.refactoring.model
-org.eclipse.ltk.ui.refactoring.resource
-
-org.eclipse.osgi.service.datalocation
-org.eclipse.osgi.service.security
-org.eclipse.osgi.signedcontent
-org.eclipse.osgi.util
-
-org.eclipse.search.core.text
-org.eclipse.search.ui
-org.eclipse.search.ui.actions
-org.eclipse.search.ui.text
-
-org.eclipse.swt
-org.eclipse.swt.awt
-org.eclipse.swt.accessibility
-org.eclipse.swt.browser
-org.eclipse.swt.custom
-org.eclipse.swt.dnd
-org.eclipse.swt.events
-org.eclipse.swt.graphics
-org.eclipse.swt.layout
-org.eclipse.swt.ole.win32
-org.eclipse.swt.opengl
-org.eclipse.swt.printing
-org.eclipse.swt.program
-org.eclipse.swt.widgets
-
-org.eclipse.team.core
-org.eclipse.team.core.diff
-org.eclipse.team.core.diff.provider
-org.eclipse.team.core.history
-org.eclipse.team.core.history.provider
-org.eclipse.team.core.mapping
-org.eclipse.team.core.mapping.provider
-org.eclipse.team.core.subscribers
-org.eclipse.team.core.synchronize
-org.eclipse.team.core.variants
-org.eclipse.team.ui
-org.eclipse.team.ui.history
-org.eclipse.team.ui.mapping
-org.eclipse.team.ui.synchronize
-
-org.eclipse.text.edits
-org.eclipse.text.undo
-
-org.eclipse.ui
-org.eclipse.ui.about
-org.eclipse.ui.actions
-org.eclipse.ui.activities
-org.eclipse.ui.application
-org.eclipse.ui.branding
-org.eclipse.ui.browser
-org.eclipse.ui.cheatsheets
-org.eclipse.ui.commands
-org.eclipse.ui.console
-org.eclipse.ui.console.actions
-org.eclipse.ui.contentassist
-org.eclipse.ui.contexts
-org.eclipse.ui.databinding
-org.eclipse.ui.dialogs
-org.eclipse.ui.editors.text
-org.eclipse.ui.editors.text.templates
-org.eclipse.ui.fieldassist
-org.eclipse.ui.forms
-org.eclipse.ui.forms.editor
-org.eclipse.ui.forms.events
-org.eclipse.ui.forms.widgets
-org.eclipse.ui.handlers
-org.eclipse.ui.help
-org.eclipse.ui.ide
-org.eclipse.ui.ide.dialogs
-org.eclipse.ui.ide.fileSystem
-org.eclipse.ui.ide.undo
-org.eclipse.ui.intro
-org.eclipse.ui.intro.config
-org.eclipse.ui.intro.contentproviders
-org.eclipse.ui.intro.universal
-org.eclipse.ui.keys
-org.eclipse.ui.menus
-org.eclipse.ui.model
-org.eclipse.ui.navigator
-org.eclipse.ui.navigator.resources
-org.eclipse.ui.operations
-org.eclipse.ui.part
-org.eclipse.ui.plugin
-org.eclipse.ui.preferences
-org.eclipse.ui.presentations
-org.eclipse.ui.progress
-org.eclipse.ui.services
-org.eclipse.ui.splash
-org.eclipse.ui.statushandlers
-org.eclipse.ui.swt
-org.eclipse.ui.testing
-org.eclipse.ui.themes
-org.eclipse.ui.texteditor
-org.eclipse.ui.texteditor.link
-org.eclipse.ui.texteditor.quickdiff
-org.eclipse.ui.texteditor.rulers
-org.eclipse.ui.texteditor.spelling
-org.eclipse.ui.texteditor.templates
-org.eclipse.ui.views
-org.eclipse.ui.views.bookmarkexplorer
-org.eclipse.ui.views.contentoutline
-org.eclipse.ui.views.framelist
-org.eclipse.ui.views.markers
-org.eclipse.ui.views.navigator
-org.eclipse.ui.views.properties
-org.eclipse.ui.views.properties.tabbed
-org.eclipse.ui.views.tasklist
-org.eclipse.ui.wizards
-org.eclipse.ui.wizards.datatransfer
-org.eclipse.ui.wizards.newresource
-
-org.eclipse.update.configurator
-org.eclipse.update.configuration
-org.eclipse.update.core
-org.eclipse.update.core.model
-org.eclipse.update.operations
-org.eclipse.update.search
-org.eclipse.update.standalone

diff --git a/bundles/org.eclipse.platform.doc.isv/plugin.properties b/bundles/org.eclipse.platform.doc.isv/plugin.properties
deleted file mode 100644
index d695256..0000000
--- a/bundles/org.eclipse.platform.doc.isv/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2005 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName = Eclipse Platform Plug-in Developer Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.platform.doc.isv/plugin.xml b/bundles/org.eclipse.platform.doc.isv/plugin.xml
deleted file mode 100644
index 52ed2af..0000000
--- a/bundles/org.eclipse.platform.doc.isv/plugin.xml
+++ /dev/null

@@ -1,111 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-<plugin>
-
-<!-- ============================================================================= -->
-<!-- Small library containing a live help action used in doc                             -->
-<!-- ============================================================================= -->
-    
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-   <extension
-         point="org.eclipse.help.toc">
-      <toc
-            file="toc.xml"
-            primary="true">
-      </toc>
-      <index path="index"/>
-   </extension>
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-   <extension
-         point="org.eclipse.help.toc">
-      <toc
-            file="topics_Guide.xml">
-      </toc>
-      <toc
-            file="topics_Reference.xml">
-      </toc>
-      <toc
-            file="topics_Porting.xml">
-      </toc>
-      <toc
-            file="topics_Questions.xml">
-      </toc>
-      <toc
-            file="topics_Samples.xml">
-      </toc>
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- Define Javadoc locations                                                      -->
-<!-- ============================================================================= -->
-   <extension point="org.eclipse.pde.core.javadoc">
-       <javadoc path="reference/api">
-           <plugin id="org.eclipse.ant.core"/>
-           <plugin id="org.eclipse.compare"/>
-           <plugin id="org.eclipse.compare.core"/>
-           <plugin id="org.eclipse.core.commands"/>
-           <plugin id="org.eclipse.core.contenttype"/>
-           <plugin id="org.eclipse.core.databinding"/>
-           <plugin id="org.eclipse.core.databinding.beans"/>
-           <plugin id="org.eclipse.core.databinding.observable"/>
-           <plugin id="org.eclipse.core.databinding.property"/>
-           <plugin id="org.eclipse.core.expressions"/>
-           <plugin id="org.eclipse.core.filebuffers"/>
-           <plugin id="org.eclipse.core.filesystem"/>
-           <plugin id="org.eclipse.core.jobs"/>
-           <plugin id="org.eclipse.core.net"/>
-           <plugin id="org.eclipse.core.resources"/>
-           <plugin id="org.eclipse.core.runtime"/>
-           <plugin id="org.eclipse.core.variables"/>
-           <plugin id="org.eclipse.debug.core"/>
-           <plugin id="org.eclipse.debug.ui"/>
-           <plugin id="org.eclipse.equinox.app"/>
-           <plugin id="org.eclipse.equinox.common"/>
-           <plugin id="org.eclipse.equinox.http.jetty"/>
-           <plugin id="org.eclipse.equinox.http.registry"/>
-           <plugin id="org.eclipse.equinox.http.servlet"/>
-           <plugin id="org.eclipse.equinox.jsp.jasper"/>
-           <plugin id="org.eclipse.equinox.jsp.jasper.registry"/>           
-           <plugin id="org.eclipse.equinox.preferences"/>
-           <plugin id="org.eclipse.equinox.registry"/>
-           <plugin id="org.eclipse.help"/>
-           <plugin id="org.eclipse.help.base"/>
-           <plugin id="org.eclipse.help.ui"/>
-           <plugin id="org.eclipse.help.webapp"/>
-           <plugin id="org.eclipse.jface"/>
-           <plugin id="org.eclipse.jface.databinding"/>
-           <plugin id="org.eclipse.jface.text"/>
-           <plugin id="org.eclipse.jsch.core"/>
-           <plugin id="org.eclipse.jsch.ui"/>
-           <plugin id="org.eclipse.ltk.core.refactoring"/>
-           <plugin id="org.eclipse.ltk.ui.refactoring"/>
-           <plugin id="org.eclipse.osgi"/>
-           <plugin id="org.eclipse.search"/>
-           <plugin id="org.eclipse.swt"/>
-           <plugin id="org.eclipse.team.core"/>
-           <plugin id="org.eclipse.team.ui"/>
-           <plugin id="org.eclipse.text"/>
-           <plugin id="org.eclipse.ui.browser"/>
-           <plugin id="org.eclipse.ui.cheatsheets"/>
-           <plugin id="org.eclipse.ui.console"/>
-           <plugin id="org.eclipse.ui.editors"/>
-           <plugin id="org.eclipse.ui.forms"/>
-           <plugin id="org.eclipse.ui.ide"/>
-           <plugin id="org.eclipse.ui.intro"/>
-           <plugin id="org.eclipse.ui.intro.universal"/>
-           <plugin id="org.eclipse.ui.navigator"/>
-           <plugin id="org.eclipse.ui.navigator.resources"/>
-           <plugin id="org.eclipse.ui.views"/>
-           <plugin id="org.eclipse.ui.views.properties.tabbed"/>
-           <plugin id="org.eclipse.ui.workbench"/>
-           <plugin id="org.eclipse.ui.workbench.texteditor"/>
-           <plugin id="org.eclipse.update.configurator"/>
-           <plugin id="org.eclipse.update.core"/>
-       </javadoc>
-   </extension>
-
-</plugin>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.3/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/3.3/faq.html
deleted file mode 100644
index 58f05db..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.3/faq.html
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.3 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.3 Plug-in Migration FAQ</h1>
-<ol>
-	<li><a href="#signing">Impact of JAR signing</a></li>
-</ol>
-<h2><a name="signing">Impact of JAR signing</a></h2>
-<p>
-In Eclipse 3.3, plug-ins in the Eclipse platform are signed with a cryptographic
-signature supplied by the Eclipse Foundation. Signing of plug-ins can have an impact
-in three areas:</p>
-  <ul>
-    <li>Code that uses non-Eclipse class loaders.  Eclipse class loaders have a flag
-    that controls load-time verification of signature, and it is turned off by default.  Loaders in
-    the JDK such as URLClassLoader do not have this option, and will always verify
-    any JAR file that contains signatures.  If this performance impact is not acceptable,
-    the only solution is to avoid signing of JARs that are loaded by other class loaders.
-    A common example is JARs that are intended to be run with Ant. </li>
-    <li> Use of the constructor <tt>java.util.jar.JarFile(File)</tt> (i.e., without verify = false). 
-    JarFile will perform verification of signatures unless explicitly told not to. This will
-    have a performance impact when the JAR is signed. If you don't need signature verification,
-    be sure to use the <tt>JarFile</tt> API that does not perform verification.</li>
-    <li>Use of <tt>java.util.jar.Manifest</tt>.  Since the manifest file of a signed JAR can
-    be quite large, anyone reading and parsing entire manifest.mf files will see a
-    performance hit. The best solution in this case is to only read the manifest
-    main attribute rather than parsing the entire file.</li>
-  </ul>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.3/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/3.3/incompatibilities.html
deleted file mode 100644
index ff596ba..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.3/incompatibilities.html
+++ /dev/null

@@ -1,274 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.2 and 3.3</title>
-</head>
-<body>
-<h1>Incompatibilities between Eclipse 3.2 and 3.3</h1>
-
-<p> Eclipse changed in incompatible ways between 3.2 and 3.3 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.2 plug-ins to 3.3. Note that you only need to look 
-  here if you are experiencing problems running your 3.2 plug-in on 3.3.</p>
-<p></p>
-<ol>
-  <li><a href="#launchConfigWorkingCopies">Nested Launch Configuration Working Copies</a></li>
-  <li><a href="#FileEditorInput">Incompatible source change to getStorage() on FileEditorInput</a></li>
-  <li><a href="#BootDelegation">Boot delegation changes</a></li>
-  <li><a href="#LazyActivation">Lazy activation changes</a></li>
-  <li><a href="#getEntryPaths">Clarification to Bundle.getEntryPaths</a></li>
-  <li><a href="#HistoryView">History View didn't follow spec of IHistoryPageSource</a></li>
-  <li><a href="#Proxy">Proxy settings are now managed by the platform</a></li>
-  <li><a href="#startup.jar">Launching Eclipse with startup.jar</a></li>
-  <li><a href="#DeviceResourceDescriptor">Incompatible source change to DeviceResourceDescriptor#createResource</a></li>
-  <li><a href="#ResourceManager">Incompatible source change to ResourceManager resource creation methods</a></li>
-   <li><a href="#jface-backcalls">JFace viewers and recursive back-calls</a></li>
-   <li><a href="#IIDEActionConstants">IIDEActionConstants.FIND_EXT corrected to conform to specification</a></li>
-   <li><a href="#IDEEncoding">IDEEncoding#setResourceEncoding deleted</a></li>
-   <li><a href="#ErrorDialog">ErrorDialog client area has a potential extra column</a></li>
-   <li><a href="#IIndexEntry">Binary incompatibility in IIndexEntry</a></li>
-   <li><a href="#FormColors">Constant changed in FormColors</a></li>
-   <li><a href="#ActionHandler">UI ActionHandler depends on IAction#ENABLED</a></li>
-</ol>
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="launchConfigWorkingCopies">Nested Launch Configuration Working Copies</a></h2>
-<p><strong>What is affected:</strong> Launch configuration working copies support 
-  nesting in 3.3. Clients that programmatically create and save launch configurations 
-  may be affected by the change in behavior of the <code>ILaunchConfigurationWorkingCopy.doSave() 
-  </code> method. </p>
-<p><strong>Description:</strong> When a working copy (B) is created from a working 
-  copy (A) which was created from a launch configuration (X), the newly created 
-  working copy (B) is initialized with the attributes from the first working copy 
-  (A). In 3.3, whenever a working copy is saved, it is written back to the configuration 
-  from which it was created. In this example working copy B will saves changes 
-  back to working copy A, and A will save changes back to the original launch 
-  configuration. A nested working copy has a parent working copy that can be retrieved 
-  by calling <code>getParent()</code> (newly added in 3.3). In 3.2, working copies 
-  were not nested and saving a working copy always resulted in the changes being 
-  saved back to the original launch configuration.</p>
-<p><strong>Action required:</strong> APIs are binary compatible but clients should 
-  examine calls to <code>ILaunchConfiguration.getWorkingCopy()</code> and <code>ILaunchConfigurationWorkingCopy.doSave()</code> 
-  to determine if nested working copies might be created. Note that saving a nested 
-  working copy will not save changes back to the original launch configuration.</p>
-<!-- ############################################## -->
-<h2>2. <a name="FileEditorInput">Incompatible source change to getStorage() on FileEditorInput</a></h2>
-<p><strong>What is affected:</strong> Clients that call getStorage() on FileEditorInput.</p>
-<p><strong>Description:</strong> The signature of getStorage() was changed to
-no longer throw a checked exception. This may cause compile errors in source code
-previously compiled against Eclipse 3.2 that is recompiled against 3.3. This change
-does not break binary compatibility - existing clients built against Eclipse 3.2 or
-earlier will continue to function normally.</p>
-<p><strong>Action required:</strong> Clients should recompile against Eclipse 3.3,
-and remove any catch block that is now unnecessary due to the removed exception.</p>
-<!-- ############################################## -->
-<h2>3. <a name="BootDelegation">Boot delegation changes</a></h2>
-<p><strong>What is affected:</strong> The boot delegation order has changed in 3.3.  Bundles that depend on delegating 
-to the boot (parent) class loader first may be affected by this change.</p>
-<p><strong>Description:</strong> In Eclipse 3.3 the default class loader delegation model has been changed to the following order:</p>
-<ol>
-<li>Imported packages (i.e. packages specified in the Import-Package manifest header).</li>
-<li>Required bundles (i.e. bundles specified in the Require-Bundle manifest header).</li>
-<li>Local bundle and fragments.</li>
-<li>Boot (parent) class loader as a last resort.  This is only done if no source was found in the previous steps. </li>
-</ol>
-<p>In 3.2 the boot (parent) class loader is always delegated to first.  This provides no isolation from the 
-classes provided by the VM.  It also affects performance because the boot class loader must be delegated to for every 
-load even though it is known that the class or resource is located in a bundle.  Because of the boot delegation changes 
-in 3.3, a bundle can now provide their own version of a package which is also available from the VM boot classpath.
-See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=162231"> bug 162231</a>.</p>
-
-<p><strong>Action required:</strong> Bundles that export packages which may be available by the boot (parent) class loader 
-need to evaluate whether the classes/resources they export should be added to the content from the boot class loader or replace it.
-If the exporting bundle should replace the content of the boot class loader then no action is required.  If the exporting bundle should 
-add to the content of the boot class loader then the exporting bundle should add &quot;system.bundle&quot; as a required bundle
-(i.e. Require-Bundle: system.bundle).  To revert back to the behavior in 3.2 the configuration property 
-&quot;org.osgi.framework.bootdelegation=*&quot; can be added to the config.ini file. </p>
-<!-- ############################################## -->
-<h2>4. <a name="LazyActivation">Lazy activation changes</a></h2>
-<p><strong>What is affected:</strong> Bundles that use the lazy activation policy (i.e. &quot;Eclipse-LazyStart: true&quot;) 
-will enter the Bundle.STARTING state as soon as they are eligible for lazy activation.  Clients that monitor the Bundle.STARTING 
-state may be affected by this change.
-</p>
-<p><strong>Description:</strong> Eclipse 3.3 implements the OSGi R4.1 specification.  The OSGi R4.1 specification  
-standardizes the lazy activation policy implemented in Eclipse.  Part of the standardization work changed the behavior of how 
-bundles states are transitioned when a lazy activation policy is used.  When a bundle becomes available for lazy activation the bundle 
-enters the Bundle.STATING state and a BundleEvent.LAZY_ACTIVATION event is fired.  This occurs before any class load 
-request is made to the bundle.  The bundle will remain in the Bundle.STARTING state until the first class load is made and 
-the bundle is activated.  When the bundle is activated a BundleEvent.STARTING event is fired and the BundleActivator.start method
-is called.  See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=135885">bug 135885</a>.
-</p>
-<p>
-Bundles with a lazy activation policy could remain in the Bundle.STARTING state for a long time waiting for the first class load 
-(trigger load) to occur.  Entering the Bundle.STARTING state does not mean the BundleActivator.start method has been called.  
-The BundleActivator.start method is only called right after the BundleEvent.STARTING event is fired.  Bundles that monitor calls to 
-BundleActivators must use a SynchronousBundleListener to listen for the BundleEvent.STARTING and BundleEvent.STOPPING 
-events.
-</p>
-<p><strong>Action required:</strong> A SynchronousBundleListener must be used to monitor BundleEvent.STARTING and 
-BundleEvent.STOPPING events for clients that are monitoring the calls to BundleActivators.</p>
-<!-- ############################################## -->
-<h2>5. <a name="getEntryPaths">Clarification to Bundle.getEntryPaths</a></h2>
-<p><strong>What is affected:</strong> Clients of the Bundle.getEntryPaths method.
-</p>
-<p><strong>Description:</strong> The OSGi R4.1 specification has made a clarification on the behavior of the 
-org.osgi.framework.Bundle#getEntryPaths method.  The javadoc for the method Bundle#getEntryPaths did not 
-make it clear whether the String paths returned had a leading &quot;/&quot; character or not.  The following clarification has 
-been made:</p> 
-<p>
-The returned paths are all relative to the root of this bundle and must not begin with &quot;/&quot;. 
-</p>
-Eclipse 3.2 had a bug for directory (non-jarred) bundles where a leading &quot;/&quot; character was included in the result if 
-the client used a path argument that contained a leading &quot;/&quot;.  For jarred bundles Eclipse 3.2 always ensures 
-the returned paths do not have a leading &quot;/&quot; character.  This is inconsistent behavior.  Directory bundles have  
-been fixed to be consistent with jarred bundles.  See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=174101"> bug 174101</a>.
-
-<p><strong>Action required:</strong> Some clients may have a dependency on the old behavior for directory bundles.  If a client 
-uses the method Bundle#getEntryPaths then ensure that it can handle returned paths that do not begin with a &quot;/&quot; character.
-This dependency is a bug in the client code because it would have failed for jarred bundles.
-</p>
-<!-- ############################################## -->
-<h2>6. <a name="HistoryView">History View didn't follow spec of IHistoryPageSource</a></h2>
-<p><strong>What is affected:</strong> The History view may no longer show the history for certain elements.
-</p>
-<p><strong>Description:</strong> In 3.2, the History view did not follow the specification of IHistoryPageSource in 
-the sense that, in some situations, it did not call canShowHistoryFor(Object) before requesting a history page. 
-In 3.3, this was corrected which has lead to a situation where client code may have worked in 3.2 even though their implementation of
-IHistoryPageSource did not follow the specification in the javadoc. 
-</p>
-<p><strong>Action required:</strong> Implementors of IHistoryPageSource need to ensure that their implementation follows
-the specification defined in the javadoc of the interface.
-</p>
-<!-- ############################################## -->
-<h2>7. <a name="Proxy">Proxy settings are now managed by the platform</a></h2>
-<p><strong>What is affected:</strong> plug-ins in Eclipse that provided their own support for proxy specification 
-(e.g HTTP, SSL or SOCKS).</p>
-<p><strong>Description:</strong> A preference page and API was added in 3.3 to support the specification 
-of HTTP, SSL and SOCKS proxies. Any tooling that provided their own support for this may conflict with the new
-settings being managed by the Platform. The fix should be for tooling to remove their support for specifying
-proxies and adopt the support provided by the Platform.
-</p>
-<!-- ############################################## -->
-<h2>8. <a name="startup.jar">Launching Eclipse with startup.jar</a></h2>
-<p><strong>What is affected:</strong> Eclipse can no longer be started
-with <tt>java -jar startup.jar</tt>.<br>
-</p>
-<p><strong>Description:</strong> In 3.2, Eclipse was started using
-startup.jar from the root of the Eclipse install. In 3.3, this jar is a
-bundle in the plugins directory named org.eclipse.equinox.launcher. </p>
-<p><strong>Action required:</strong> Change the command to <tt>java
--jar
-plugins/org.eclipse.equinox.launcher_1.0.0.&lt;version&gt;.jar</tt> or
-use
-the eclipse launcher executable.
-</p>
-<!-- ############################################## -->
-<h2>9. <a name="DeviceResourceDescriptor">Incompatible source change to DeviceResourceDescriptor#createResource</a></h2>
-<p><strong>What is affected:</strong> Clients that call createResource(Device) on 
-DeviceResourceDescriptor.</p>
-<p><strong>Description:</strong> The DeviceResourceException thrown by JFace has been
-changed to a runtime exception.  As part of this change, the method signature of 
-createResource(Device) was changed to no longer throw the exception. This may cause 
-compile errors in source code
-previously compiled against Eclipse 3.2 that is recompiled against 3.3. This change
-does not break binary compatibility - existing clients built against Eclipse 3.2 or
-earlier will continue to function normally.</p>
-<p><strong>Action required:</strong> Clients should recompile against Eclipse 3.3,
-and remove any catch block that is now unnecessary due to the removed exception.</p>
-<!-- ############################################## -->
-<h2>10. <a name="ResourceManager">Incompatible source change to ResourceManager resource creation methods</a></h2>
-<p><strong>What is affected:</strong> Clients that call resource creation methods on 
-ResourceManager.</p>
-<p><strong>Description:</strong> The DeviceResourceException thrown by JFace has been
-changed to a runtime exception.  As part of this change, the following method signatures
-were changed to no longer throw the exception. 
-</p>
-<ul>
-<li>ResourceManager#create(DeviceResourceDescriptor)</li>
-<li>ResourceManager#createColor(ColorDescriptor)</li>
-<li>ResourceManager#createColor(RGB)</li>
-<li>ResourceManager#createFont(FontDescriptor)</li>
-<li>ResourceManager#createImage(ImageDescriptor)</li>
-</ul>
-<p>
-These changes may cause compile errors in source code
-previously compiled against Eclipse 3.2 that is recompiled against 3.3. This change
-does not break binary compatibility - existing clients built against Eclipse 3.2 or
-earlier will continue to function normally.</p>
-<p><strong>Action required:</strong> Clients should recompile against Eclipse 3.3,
-and remove any catch block that is now unnecessary due to the removed exception.</p>
-<!-- ############################################## -->
-
-<h2>11. <a name="jface-backcalls">JFace viewers and recursive back-calls</a></h2>
-<p><strong>What is affected:</strong> Clients of <tt>TableViewer</tt> and <tt>TreeViewer</tt>, implementers of <tt>IStructuredContentProvider</tt> or <tt>IBaseLabelProvider</tt></p>
-<p><strong>Description:</strong> <tt>StructuredViewer</tt> and its subclasses were never designed to handle
-recursive back-calls to methods such as <tt>setInput()</tt>, <tt>refresh()</tt>, <tt>add()</tt>,
-<tt>remove()</tt>, <tt>update()</tt> etc. In the past, calls to one of these update
-methods that happened while the viewer was already in the process of
-processing another update, lead to unpredictable behavior or even
-runtime errors later on that were hard to debug. Starting with 3.3,
-subclasses of ColumnViewer detect recursive back-calls, log an error and
-ignore the nested update request. This helps uncover programming errors
-such as spinning the event loop from a content provider or label
-provider, but potentially changes the behavior in cases where clients
-used recursive back-calls but didn't see immediate problems in the past in
-their particular usage scenarios. See <a
-	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=154571">bug
-154571</a> for details.</p>
-<p><strong>Action required:</strong> No action required if you don't see
-entries about ignored calls in the .log file. If you do see log entries,
-the provided stack trace should have sufficient information to find the
-problematic back-call. Depending on the situation, you might need to post
-an asyncExec runnable to avoid the back-call.</p>
-<!-- ############################################## -->
-<h2>12. <a name="IIDEActionConstants"> IIDEActionConstants.FIND_EXT corrected to conform to specification</a></h2>
-<p><strong>What is affected:</strong> Clients of <tt>IIDEActionConstants</tt> who use the values directly instead of via the constant.</p>
-<p><strong>Description:</strong> Edit menu: name of group for extra Find-like actions (value <code>"find.ext"</code>).</p>
-<p>The value of this constant has changed in 3.3 to match the specification; before 3.3, its value was incorrect (<code>"cut.ext"</code>).
-See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=155856">bug 155856</a> for details.</p>
-<p><strong>Action required:</strong> No action required if you refer to the constant rather than its value.</p>
-<!-- ############################################## -->
-<h2>13. <a name="IDEEncoding">IDEEncoding#setResourceEncoding deleted</a></h2>
-<p><strong>What is affected:</strong> Clients of <tt>IDEEncoding</tt>.</p>
-<p><strong>Description:</strong> <code>IDEEncoding#setResourceEncoding</code> was deprecated in 3.2 (the same release it was 
-added in) in favor of setting the ResourcesPlugin.PREF_ENCODING value
-in the Resources plug-ins preference store. It was not deleted in the 3.2 release despite never having been valid API. 
-It was deleted in the 3.3 release. </p>
-<p><strong>Action required:</strong> Update references to <code>IDEEncoding#setEncoding</code> to calls to 
-<code>ResourcesPlugin#getPlugin()#getPluginPreferences()#setValue(ResourcesPlugin.PREF_ENCODING,value)</code>.</p>
-<!-- ############################################## -->
-<h2>14. <a name="ErrorDialog">ErrorDialog client area has a potential extra column</a></h2>
-<p><strong>What is affected:</strong> Subclasses of <tt>ErrorDialog</tt>.</p>
-<p><strong>Description:</strong> <code>ErrorDialogs</code> will have an extra column in their client area
-if there is an <code>ErrorSupportProvider</code> registered in an install. ErrorDialog subclasses that assume
-there are 2 columns should call <code>IconAndMessageDialog#getColumnCount</code> instead.</p>
-<p><strong>Action required:</strong> Update hard coded column counts to call to  <code>IconAndMessageDialog#getColumnCount</code> .</p>
-<!-- ############################################## -->
-<h2>15. <a name="IIndexEntry">Binary incompatibility in IIndexEntry</a></h2>
-<p><strong>What is affected:</strong> Clients of IIndexEntry who rely on binary compatibility.</p>
-<p><strong>Description:</strong> The return type of function getTopics() has changed from IHelpResource[] to the subclass ITopic[].
-See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=191224">bug 191224</a> for details.</p>
-<p><strong>Action required:</strong> Source which uses this interface must be recompiled.</p>
-<!-- ############################################## -->
-<h2>16. <a name="FormColors">Constant changed in FormColors</a></h2>
-<p><strong>What is affected:</strong> Clients of FormColors who rely on binary compatibility.</p>
-<p><strong>Description:</strong> The value of the constant org.eclipse.ui.forms.FormColors.TB_GBG changed in Eclipse 3.3.
-See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=191233">bug 191233</a> for details.</p>
-<p><strong>Action required:</strong> Update hard coded column counts to call to  <code>IconAndMessageDialog#getColumnCount</code> .</p>
-<!-- ############################################## -->
-<h2>17. <a name="ActionHandler">UI ActionHandler depends on IAction#ENABLED</a></h2>
-<p><strong>What is affected:</strong> Clients using <code>IKeyBindingService#registerAction(IAction)</code> or using <code>org.eclipse.ui.commands.ActionHandler</code> 
-to submit <code>IActions</code> to the handler service.</p>
-<p><strong>Description:</strong> Commands now add listeners to their handlers.  The <code>ActionHandler</code> will now depend on
-the IAction firing the property change for <b>ENABLED</b> to update its enabled state.  One side effect is that
-<code>IAction#isEnabled()</code> will not be called frequently.</p>
-<p><strong>Action required:</strong>  Clients must ensure their <code>IActions</code> do not require frequent callings of <code>isEnabled()</code> to manage their enabled state,
-and must fire the <b>ENABLED</b> property at the appropriate times.</p>
-<!-- ############################################## -->
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.3/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/3.3/recommended.html
deleted file mode 100644
index d4c65d8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.3/recommended.html
+++ /dev/null

@@ -1,231 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adopting 3.3 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h2>Adopting 3.3 mechanisms and APIs</h2>
-<p>This section describes changes that are required if you are trying to change 
-  your 3.2 plug-in to adopt the 3.3 mechanisms and APIs.</p>
-  
-<ol>
-  <li><a href="#AppModel">Application model changes</a></li>
-  <li><a href="#ContextLaunch">Launch selection versus launch last</a></li>
-  <li><a href="#HyperlinkDetector">Replacing a hard-coded <code>IHyperlinkDetector</code> 
-    with an extension</a></li>
-  <li><a href="#FileBufferPerformance">Improve performance when working with file 
-    buffers</a></li>
-  <li><a href="#LaunchDelegate">Launch delegate names and descriptions</a></li>
-  <li><a href="#Compare">Support for file buffers added to Compare</a></li>
-  <li><a href="#Presentation">New Minimize/Maximize behavior</a></li>
-  <li><a href="#MenuContribution">Menu contributions and commands</a></li>
-</ol>
-<hr>
-
-<!-- ############################################## -->
-<h2><a name="AppModel">1. Application model changes</a></h2>
-<p>The Eclipse application container has been moved from <b>org.eclipse.core.runtime</b> 
-into the new bundle <b>org.eclipse.equinox.app</b>. The Eclipse application container included in the 
-org.eclipse.equinox.app bundle implements the Application Admin Service specification from the OSGi R4 specification.  
-</p>
-<p>
-The following extension points have also been moved into the org.eclipse.equinox.app bundle. Note that
-the fully qualified extension point ids are unchanged:</p>
-<ul>
- <li>org.eclipse.core.runtime.applications</li>
- <li>org.eclipse.core.runtime.products</li>
-</ul>
-The interface <b>org.eclipse.core.runtime.IPlatformRunnable</b> has been deprecated and the 
-org.eclipse.equinox.app.IApplication interface should be used instead.  IPlatformRunnable is supported for 
-backwards compatibility, and clients are encouraged to move to the new IApplication API
-instead.
-<p>
-As a result of the code move, custom configurations and scripts that explicitly 
-reference <b>org.eclipse.core.runtime</b> might need to add the <b>org.eclipse.equinox.app</b> bundle.
-</p>
-<p>See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=109893">bug 109893</a> 
-  for more details. </p> 
-<!-- ############################################## -->
-<p>&nbsp;</p>
-<h2><a name="ContextLaunch">2. Launch selection versus launch last</a></h2>
-<p>By default, running and debugging applications has been simplified to run or 
-  debug the selected file or active editor. When the selected resource (or active 
-  editor) is not executable, users can opt to launch the associated project or 
-  re-launch the previous launch. These settings are managed on the <strong>Run/Debug 
-  &gt; Launching</strong> preference page. Users can also revert to the 3.2 behavior 
-  of always launching the previous application.</p>
-<p>Pressing the <strong>Run</strong> or <strong>Debug</strong> toolbar button 
-  will launch the selected resource (as will the <strong>Run</strong> or <strong>Debug</strong> 
-  action in the top level Run menu). When no launch configuration exists for a 
-  file and there is only one way to launch it, the file will simply be launched 
-  in the mode selected. When there is more than one way to launch a file, the 
-  user will be prompted to select how to run or debug the application. For example, 
-  when running a JUnit test it can be run as a Java application or JUnit test. 
-  A launch configuration will be created and an entry will be added to the launch 
-  history for the application. When the same resource is launched again, it will 
-  use the most recent configuration in the launch history associated with that 
-  resource.</p>
-<p>The underlying infrastructure for selection based launching relies on the launch 
-  shortcuts applicable to a resource (or editor) and the resource mappings associated 
-  with existing launch configurations. As well, API (a new extension element) 
-  has been added to the <code>launchShortcuts</code> extension to associate a 
-  launch shortcut with one or more types of launch configurations. For example, 
-  this tells the platform that the &quot;Java Application&quot; launch shortcut 
-  is associated with &quot;Java Application&quot; launch configurations.</p>
-<p>The contextual launch support uses the following approach to determine how 
-  a selection or active editor should be launched.</p>
-<ol>
-  <li>An <code>IResource</code> adapter is retrieved from the selection or active 
-    editor (which can be <code>null</code>).</li>
-  <li>A set of applicable launch configuration types are computed from the set 
-    of launch shortcuts applicable to the selection/editor (using the new launch 
-    configuration type elements defined by launch shortcuts).</li>
-  <li>A set of applicable launch configurations is computed based on the launch 
-    configuration types applicable to the selection/editor and the existing launch 
-    configurations in the workspace.</li>
-  <li>The set of applicable launch configurations is reduced to those that have 
-    a resource mapping equal to or contained by the retrieved resource adapter</li>
-  <li>The set of applicable launch configurations is compared to the launch history 
-    and the most recently launched configuration in the set is selected for launching.</li>
-  <li>When there are applicable launch configurations, but none are in the recent 
-    launch history, the user is prompted to select one of the applicable configurations 
-    to launch.</li>
-  <li>When there are applicable launch shortcuts and no applicable launch configurations, 
-    the user is prompted on how they want to launch the selection (i.e. which 
-    shortcut they want to use).</li>
-</ol>
-<p>When there are no applicable launch configurations or launch shortcuts, the 
-  platform either attempts to launch the associated project or launches last, 
-  based on user preference settings. When the user has chosen to launch the associated 
-  project, the same steps as above are followed, except the resource used is the 
-  project.</p>
-<p>For selection based launching to work well, plug-in providers should ensure 
-  the following.</p>
-<ol>
-  <li>Resource mappings for launch configurations should be scoped to the appropriate 
-    resource. For example, to support projects with multiple Java executables, 
-    Java application launch configurations are associated with the the .java file 
-    containing the main class.</li>
-  <li>Launch shortcut extensions should be updated with <code>configurationType</code> 
-    elements so the platform can infer which launch configuration types to consider 
-    when resolving launch configurations applicable to a selection/editor. As 
-    well, launch shortcuts should be updated with the new <code>description</code> 
-    attribute. This attribute is used when presenting the user with a list of 
-    shortcuts to choose from.</li>
-  <li>Launch configuration migration delegates should be updated to create appropriate 
-    resource mappings for existing launch configurations. For example, if launch 
-    your launch configuration resource mappings in 3.2 were always associated 
-    with a project, but now you want to associated them with specific files in 
-    a project to better support context launching, your migration delegate should 
-    be updated to update resource mappings.</li>
-</ol>
-<!-- ############################################## -->
-<p>&nbsp;</p>
-<h2><a name="HyperlinkDetector">3. Replacing a hard-coded <code>IHyperlinkDetector</code> with an extension</a></h2>
-Before 3.3 it was not possible to contribute hyperlink detectors to existing source viewers and textual editors. Only
-their implementors could add them directly through code by providing their hyper link detectors via
-<code>SourceViewerConfiguration.getHyperlinkDetectors(ISourceViewer)</code>.
-<p>
-As of 3.3, clients can define hyperlink detector targets for their viewers and editors and they can contribute
-their own hyperlink detectors to such targets via the following extension points:</p>
-<ul>
-	<li><a href="../../reference/extension-points/org_eclipse_ui_workbench_texteditor_hyperlinkDetectorTargets.html">org.eclipse.ui.workbench.texteditor.hyperlinkDetectorTargets</a></li>
-	<li><a href="../../reference/extension-points/org_eclipse_ui_workbench_texteditor_hyperlinkDetectors.html">org.eclipse.ui.workbench.texteditor.hyperlinkDetectors</a></li>
-</ul>
-<!-- ############################################## -->
-<h2><a name="FileBufferPerformance">4. Improve performance when working with file buffers</a></h2>
-<p>In earlier versions file buffer manager API methods used to take an <code>IPath</code> and it was
-up to the file buffer manager to detect whether that path pointed to a workspace or an external location.
-Those API methods have been deprecated in 3.3 in order to improve performance as in most cases clients already
-know whether their path is a workspace path or an external path. New methods with same names have been added
-that take one of the following location kind arguments:</p>
-<ul>
-  <li><a href="../../reference/api/org/eclipse/core/filebuffers/LocationKind.html#IFILE">IFILE</a></li>
-  <li><a href="../../reference/api/org/eclipse/core/filebuffers/LocationKind.html#LOCATION">LOCATION</a></li>
-  <li><a href="../../reference/api/org/eclipse/core/filebuffers/LocationKind.html#NORMALIZE">NORMALIZE</a></li>
-</ul>
-<p>Clients using the deprecated methods are encouraged to adopt the new API in order
-to take advantage of the performance improvement.
-</p>
-<!-- ############################################## -->
-<p>&nbsp;</p>
-<h2><a name="LaunchDelegate">5. Launch delegate names and descriptions</a></h2>
-<p>New attributes have been added to the <code>launchConfigurationTypes</code> 
-  and <code>launchDelegates</code> extension points to provide names and descriptions 
-  for launch delegates. Since 3.3, the debug platform allows for more than one 
-  launcher to be contributed for the same kind of launch configuration type and 
-  launch mode. When more than one launcher is available the user must choose a 
-  preferred launcher and is presented with names and descriptions of available 
-  launchers. Clients contributing launch delegates with either of these extension 
-  points are encouraged to provide meaningful names and descriptions.</p>
-<p>Clients contributing to the <code>org.eclipse.debug.core.launchConfigruationTypes</code> 
-  extension point should define the following new attributes:</p>
-<ul>
-  <li><code>delegateName</code></li>
-  <li><code>delegateDescription</code></li>
-</ul>
-<p>Clients contributing to the <code>org.eclipse.debug.core.launchDelegates </code>extension 
-  point should define the following new attributes:</p>
-<ul>
-  <li><code>name</code></li>
-  <li><code>delegateDescription</code></li>
-</ul>
-
-<h2><a name="Compare">6. Support for file buffers added to Compare</a></h2>
-
-<p>Compare editors can now be configured to use the same file buffers that are used by regular editors.
-This means that changes made in a compare editor will immediately be reflected in any other
-editor on the same file buffer or vice versa. Both the compare client and the provider of the compare
-viewer must make changes to enable this feature.</p>
-
-<ul>
-<li>In order for compare viewer providers to enable this feature, they must subclass TextMergeViewer and
-override both the getDocumentPartitioning and getDocumentPartitioning methods if they provide custom syntax highlighting.
-File buffer support in the basic TextMergeViewer is enabled. It is only subclasses that provide syntax highlighting that
-need to makes changes to adopt the feature. Also, providers of structure creators should subclass StructureCreator and
-override the getDocumentPartition and getDocumentPartitioning in order for their structure merge viewer to use the file buffer
-as well. This is described in more detail in the 
-<a href="../../guide/compare_contentviewer.htm">Implementing a Content Viewer</a> section.</li>
-<li>Client can enable the use of file buffers by using the SaveableCompareEditorInput. The static method
-<code>createFileElement</code> can be used to create a typed element that wraps a file in order to enable the 
-file buffer support for the file. This is described in more detail in the 
-<a href="../../guide/compare_beyond.htm">Advanced compare techniques</a> section.</li>
-</ul>
-
-<h2><a name="Presentation">7. New Minimize/Maximize behavior</a></h2>
-
-<p>All RCP applications will, by default, get the new min/max behavior regardless of the presentation that is defined as long as it is capable of supporting the necessary operations (i.e. supports trim...). If the pre-3.3 min/max behavior is desired then the application should explicitly set the preference to false by adding the following line to their preference customization file (as defined by the product extension):
-</p>
-<p>
-org.eclipse.ui/ENABLE_MIN_MAX=false
-</p>
-
-
-<h2><a name="MenuContribution">8.  Menu contributions and commands</a></h2>
-
-<p>
-Support is now available to place commands in menus and toolbars through the
-<a href="../../reference/extension-points/org_eclipse_ui_menus.html">org.eclipse.ui.menus</a>
-extension point.
-</p>
-<p>
-<b>org.eclipse.ui.menus</b> focuses on the appearance (label, tooltip, icon),
-location, and visibility of the command in the menu or toolbar.  Command
-enabled state is still controlled via the <b>org.eclipse.ui.handlers</b> extension
-point or the <code>IHandlerService</code>.  
-</p>
-<p>
-In 3.2 placing a command in a toolbar or menu involved using one of the
-<code>IActionDelegate</code> extensions and coding the run method to use the
-<code>IHandlerService</code> to execute the command.
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.4/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/3.4/faq.html
deleted file mode 100644
index f202b29..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.4/faq.html
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.4 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.4 Plug-in Migration FAQ</h1>
-
-<ol>
-	<li><a href="#overviewRulerAnnotationColor">Why are my annotations in the editor's overview Ruler no longer discolored?</a></li>
-	<li><a href="#IDELTK">What happened to in-place Rename in the Project Explorer?</a></li>
-	<li><a href="#cvsPasswordManagment">What happened to my saved CVS passwords?</a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<h2><a name="overviewRulerAnnotationColor">Why are my annotations in the editor's overview ruler no longer discolored?</a></h2>
-<p>
-As of 3.4, temporary annotations are no longer discolored in the editor's overview ruler. There were many complaints
-that the color was computed by discoloring the color set on the <b>General &gt; Editors &gt; Text Editors &gt; Annotations</b> preference page. Clients that nevertheless
-want to stick to the old behavior can use <code>org.eclipse.jface.text.source.OverviewRuler.OverviewRuler(IAnnotationAccess, int, ISharedTextColors, boolean)</code>
-to create the overview ruler.
-</p>
-
-<!-- ############################################## -->
-<h2><a name="IDELTK">What happened to in-place Rename in the Project Explorer?</a></h2>
-<p>
-The IDE global actions for Delete, Rename, and Move now use LTK so they can
-participate in the refactoring support.  These actions now open the refactoring
-dialog which includes the preview button.  These actions will revert to their
-old behaviour if shipped without LTK support.
-</p>
-
-<!-- ############################################## -->
-<h2><a name="cvsPasswordManagment">What happened to my saved CVS passwords?</a></h2>
-<p>
-The passwords stored with the CVS integration would have to be re-entered as the
-CVS client switched to a new secure storage back end. On the plus side, the CVS 
-integration now stores passwords in an encrypted form.
-</p>
-
-<!-- ############################################## -->
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.4/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/3.4/incompatibilities.html
deleted file mode 100644
index c47fc0a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.4/incompatibilities.html
+++ /dev/null

@@ -1,86 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.3 and 3.4</title>
-</head>
-<body>
-<h1>Incompatibilities between Eclipse 3.3 and 3.4</h1>
-
-<p>
-  Eclipse changed in incompatible ways between 3.3 and 3.4 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.3 plug-ins to 3.4. Note that you only need to look 
-  here if you are experiencing problems running your 3.3 plug-in on 3.4.
-</p>
-
-<ol>
-  <li><a href="#FileEditorInput">FileEditorInput#getPath throws IllegalArgumentException for non local files</a></li>
-  <li><a href="#ModifyRule">Changed scheduling rules for IProject#setDescription</a></li>
-  <li><a href="#MarkersAdditions"><code>IWorkbenchActionConstants.MB_ADDITIONS</code> no longer supported in Marker views</a></li>
-  <li><a href="#TomcatRemoved">org.eclipse.tomcat no longer included</a></li>
-  <li><a href="#TabbedProperties">Corrected API for tabbed properties view to not require the usage of internal types</a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="FileEditorInput">FileEditorInput#getPath throws IllegalArgumentException for non local files</a></h2>
-<p><strong>What is affected:</strong> Clients that call getPath() on FileEditorInput.</p>
-<p><strong>Description:</strong>In release 3.3 and earlier, <code>FileEditorInput#getPath</code>
-returned <code>null</code> when called on an input whose file was not in the local
-file system.  This violated the contract of <code>IPathEditorInput#getPath</code> which
-did not allow a null result. The method now throws <code>IllegalArgumentException</code>
-in this case. The convenience method <code>FileEditorInput#isLocalFile</code>
-has been added so that callers who are unsure of the state of a supplied <code>IFile</code> can check
-before calling <code>#getPath</code>.</p>
-<p><strong>Action required:</strong> Clients that call <code>FileEditorInput#getPath</code>
-should check if they are calling it on an input that is not in the local file system, and react
-accordingly.</p>
-<!-- ############################################## -->
-<h2>2. <a name="ModifyRule">Changed scheduling rules for IProject#setDescription</a></h2>
-<p><strong>What is affected:</strong> Clients that call <code>IProject#setDescription</code>.</p>
-<p><strong>Description:</strong> In the 3.3 release, all calls to <code>IProject#setDescription</code>
-required the caller to own <code>IResourceRuleFactory#modifyRule</code>, which
-was implemented with the <code>IWorkspaceRoot</code> scheduling rule.  This was
-too restrictive in most cases, and unnecessarily prevented other threads from modifying 
-other projects in the workspace while <code>modifyRule</code> was held.  In the 3.4
-release, the <code>IWorkspaceRoot</code> scheduling rule is now only needed when configuring project
-natures: clients calling <code>IProject#setDescription</code> without the <code>AVOID_NATURE_CONFIG</code>
-flag.  <code>IResourceRuleFactory#modifyRule</code> now only locks the project resource by default, allowing
-more concurrency when opening or closing projects, or when setting the description but
-not configuring project natures.</p>
-<p><strong>Action required:</strong> Clients calling <code>IProject#setDescription</code>
-should ensure they own the correct scheduling rule. See the API javadoc for a description
-of what rules are required for this and other workspace operations.</p>
-<!-- ############################################## -->
-<h2>3. <a name="MarkersAdditions">Markers views no longer support additions entries</a></h2>
-<p><strong>What is affected:</strong> Clients adding to the Problems, Tasks or Markers Views using <code>IWorkbenchActionConstants.MB_ADDITIONS</code></p>
-<p><strong>Description:</strong> The Problems, Tasks or Markers Views no longer have an entry
- for <code>IWorkbenchActionConstants.MB_ADDITIONS</code> as the pop-up and view menus are now all commands
- based. </p>
-<p><strong>Action required:</strong> Additions to these views can be made using the <code>org.eclipse.ui.menus</code> extension point.</p>
-<!-- ############################################## -->
-<h2>4. <a name="TomcatRemoved">org.eclipse.tomcat no longer included</a></h2>
-<p><strong>What is affected:</strong> Any RCP application with a dependency on the org.eclipse.tomcat plugin. </p>
-<p><strong>Description:</strong> Up to and including Eclipse 3.2 the help system used a Tomcat server and included the plug-in org.eclipse.tomcat.  
-Since Eclipse 3.3 the help system no longer uses Tomcat and instead uses the Equinox web server. In Eclipse 3.4 org.eclipse.tomcat was removed
-from platform and sdk builds.</p>
-<p><strong>Action required:</strong> Remove any dependencies to org.eclipse.tomcat. If you need a web server use 
-the Equinox server defined in org.eclipse.equinox.http.jetty.</p>
-<!-- ############################################## -->
-<h2>5. <a name="TabbedProperties">Corrected API for tabbed properties view to not require the usage of internal types</a></h2>
-<p><strong>What is affected:</strong> Clients calling <code>TabbedPropertySheetPage.getCurrentTab()</code>,
- overriding <code>TabbedPropertySheetPage.updateTabs()</code>, or implementing <code>ITabSelectionListener</code>.</p>
-<p><strong>Description:</strong> The above mentioned methods and types were not usable because they required clients
- to refer to internal, non-API types. To fix the leakage of internal types, methods were removed/renamed in a binary
-  incompatible way. For details, please refer to bug 224390. </p>
-<p><strong>Action required:</strong> Clients who were referring to internal non-API types to make use of the mentioned
-methods and types will have to be updated to refer to the cleaned up API. Plug-ins that need to work against both versions
-3.3 and 3.4 will have to use reflection to protect themselves from the binary incompatibilities.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.4/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/3.4/recommended.html
deleted file mode 100644
index b0f9faa..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.4/recommended.html
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adopting 3.4 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Adopting 3.4 mechanisms and APIs</h1>
-<p>
-  This section describes changes that are required if you are trying to change 
-  your 3.3 plug-in to adopt the 3.4 mechanisms and APIs.
-</p>
-
-<ol>
-  <li><a href="#quickAssistContext">Quick Fix command moved to Dialogs and Windows context</a></li>
-  <li><a href="#getCharset">IFile.getCharset() caches character set values</a></li>
-  <li><a href="#updateSites">Optimizing your update site for use with p2</a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="quickAssistContext">Quick Fix command moved to Dialogs and Windows context</a></h2>
-<p>
-In order to enable Quick Fix in dialogs we moved the <code>org.eclipse.jdt.ui.edit.text.java.correction.assist.proposals</code>
-command to the <b>Dialogs and Windows</b> context. Clients who registered that command for the <b>Dialogs</b> or
-<b>Dialogs and Windows</b> context can now remove their contribution from their <code>plugin.xml</code>.
-</p>
-
-<!-- ############################################## -->
-
-<h2>2. <a name="getCharset">IFile.getCharset() caches character set values</a></h2>
-<p>
-The method <code>IFile.getCharset</code> returns a cached value for the file's encoding. 
-If the file's encoding has been changed externally, and has not since been synchronized with 
-the workspace using <code>IResource.refreshLocal</code>, it may return a stale result.  
-Clients that call this method should revisit their usage to determine if a cached result 
-is acceptable. While using a cached encoding has better performance, it could lead 
-to data corruption if the wrong encoding is used to write a file.
-</p>
-<!-- ############################################## -->
-
-<h2>3. <a name="updateSites">Optimizing your update site for use with p2</a></h2>
-<p>
-Eclipse 3.4 includes a new provisioning platform called p2.  This is a replacement
-for the Update Manager technology in previous Eclipse platform releases.  While
-p2 can load update sites designed for Update Manager, you can optimize your site
-for p2 by generating p2 metadata for your update site. This metadata contains
-higher fidelity dependency information about the plug-ins and features in your update
-site, allowing for more accurate resolution of dependencies at install-time. See
-<a href="../../guide/p2_metadata_generator.html">Generating p2 metadata</a>
-for more details on how to generate p2 metadata for your update site.
-</p>
-<p>
-p2 isn't capable of installing from update sites that make use of 
-<a href="../../reference/extension-points/org_eclipse_update_core_installHandlers.html">install handlers</a>.
-When install handlers are encountered, p2 defers installation to the classic Update
-Manager. Although end users will still be able to install such features, the end
-user experience is less polished and the more advanced download technology
-of p2 cannot be exploited. It is recommended that install handlers be avoided
-for this reason.
-</p>
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.5/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/3.5/faq.html
deleted file mode 100644
index c126c35..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.5/faq.html
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.5 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.5 Plug-in Migration FAQ</h1>
-
-<ol>
-	<li><a href="#noextendApiRestriction">Why is the @noextend API restriction supported on interfaces? </a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<h2><a name="noextendApiRestriction">Why is the @noextend API restriction supported on interfaces? </a></h2>
-<p>In release 3.4, API tooling supported one   restriction for API interfaces - <code>@noimplement</code>. This restriction specified   an interface was not to be implemented or extended by clients. To enrich API specifications, Eclipse 3.5 separates these concerns into   two restrictions - <code>@noimplement</code> and <code>@noextend</code>. This allows an interface to   be extended when it is not to be implemented directly. For   example, a clients may be permitted to subclass an existing implementation of a <code>@noimplement</code> interface and extend the base   interface with extra function.</p>
-<p>Component owners need to decide where to add <code>@noextend</code> tags on existing   interfaces.    To maintain exactly the same API contract as specified in 3.4, <code>@noextend</code> tags   can be added to all interfaces specified as <code>@noimplement</code>. This   can be decided on a case by case basis. Generally, the <code>@noextend</code> restriction can be   omitted, as clients that extend and implement a <code>@noimplement</code> interface   will still be flagged with errors. However, if you would like to reserve   the right to add constants (public static final fields) to an API   interface in the future, you must add the <code>@noextend</code> tag. This is because   adding a field to an interface is binary incompatible if clients can   extend or implement an interface (see <A href="http://wiki.eclipse.org/Evolving_Java-based_APIs_2#Evolving_API_Interfaces">Evolving API Interfaces</A>).   Adding an API restriction to a class/interface is usually an error -   however, API tooling allows you to add <code>@noextend</code> tags without penalty in   the 3.5 release, since this specifies the same contract that 3.4 tooling provided. If you were   to wait until a later release to add the additional tag, and error would   be generated to indicate a restriction has been added to an API interface. </p>
-<!-- ############################################## -->
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.5/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/3.5/incompatibilities.html
deleted file mode 100644
index 69c14c6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.5/incompatibilities.html
+++ /dev/null

@@ -1,113 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.4 and 3.5</title>
-</head>
-<body>
-<h1>Incompatibilities between Eclipse 3.4 and 3.5</h1>
-
-<p>
-  Eclipse changed in incompatible ways between 3.4 and 3.5 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.4 plug-ins to 3.5. Note that you only need to look 
-  here if you are experiencing problems running your 3.4 plug-in on 3.5.
-</p>
-
-<ol>
-  <li><a href="#launchConfigurationLocation">ILaunchConfiguration.getLocation() can return null</a></li>
-  <li><a href="#introConstants">CustomizableIntroPart no longer implements IIntroConstants</a></li>
-  <li><a href="#preRefresh">IResourceChangeEvent.getResource() may return null for PRE_REFRESH events</a></li>
-  <li><a href="#teamPluginLeaks">Methods and fields that leaks internal types are no longer accessible</a></li>
-  <li><a href="#commonNavigatorLink">CommonNavigator#IS_LINKING_ENABLED_PROPERTY has changed its value</a></li>
-  <li><a href="#commonNavigatorInitialInput">CommonNavigator#getInitialInput() has changed its return type</a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<h2>1. <a name="launchConfigurationLocation">ILaunchConfiguration.getLocation() can return null</a></h2>
-<p><strong>What is affected:</strong> Clients that call ILaunchConfiguration.getLocation()</p>
-<p><strong>Description:</strong> In release 3.4 and earlier, ILaunchConfiguration.getLocation() was not specified 
-to return <code>null</code>. Since 3.5, launch configuration infrastructure has been enhanced to support storage
-on external file systems (EFS). The #getLocation() method returns a location in the local file system - however, since 
-an external file system may not map to a local location, <code>null</code> can now be returned. </p>
-<p><strong>Action required:</strong> Clients that call ILaunchConfiguration.getLocation() should update
-code to handle a <code>null</code> result. The #getLocation() method has been deprecated since the return
-value is no longer reliable.</p>
-
-<!-- ############################################## -->
-
-<h2>2. <a name="introConstants">CustomizableIntroPart no longer implements IIntroConstants</a></h2>
-<p><strong>What is affected:</strong>Clients that reference constants from IIntroConstants via CustomizableIntroPart</p>
-<p><strong>Description:</strong> In release 3.4 and earlier, CustomizableIntroPart implemented the internal class IIntroConstants. 
-This had the side effect of accidentally exposing internal constants in an API class. Since Eclipse 3.5 this implements clause has been removed. </p>
-<p><strong>Action required:</strong> 
-Clients that reference any of these constants will see a compilation error in the source and will need to replace the reference 
-to the constant with a string literal of the same value. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=251472">bug 251472</a> for more information</p>
-
-<!-- ############################################## -->
-
-<h2>3. <a name="preRefresh">IResourceChangeEvent.getResource() may return null for PRE_REFRESH events</a></h2>
-<p><strong>What is affected: </strong>Clients that use IResourceChangeListeners and listen on IResourceChangeEvent#PRE_REFRESH events</p>
-<p><strong>Description:</strong> In release 3.4, clients were notified with PRE_REFRESH events only during a single project
-refresh. Since Eclipse 3.5, PRE_REFRESH events have been fired during every workspace refresh. For a workspace refresh 
-IResourceChangeEvent.getResource() returns null. To determine the scope of the refresh (a project or the workspace), 
-IResourceChangeEvent.getSource() should be used.</p>
-<p><strong>Action required:</strong> 
-Clients that listens on PRE_REFRESH events should use IResourceChangeEvent.getSource() instead of
-IResourceChangeEvent.getResource() to determine the scope of the refresh. See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=255325">bug 255325</a> for more information.</p>
-
-<!-- ############################################## -->
-
-<h2>4. <a name="teamPluginLeaks">Methods and fields that leaks internal types are no longer accessible</a></h2>
-<p><strong>What is affected: </strong>Clients that refer to ModelSynchronizeParticipant#refreshSchedule or call one of:
-<ul>
-<li>ThreeWaySynchronizer#flush</li>
-<li>SubscriberParticipant#getRefreshSchedule</li>
-<li>SubscriberParticipant#setRefreshSchedule</li>
-<li>SubscriberParticipant#getSubscriberSyncInfoCollector</li>
-</ul>
-</p>
-<p><strong>Description:</strong> In release 3.4 and earlier, ModelSynchronizeParticipant#refreshSchedule 
-and methods mentioned above were made accessible. #refreshSchedule is declared as an internal type 
-and referring it is illegal. Calling the methods was also illegal since attributes or returned parameters 
-were internal types. Since Eclipse 3.5, the field and methods are no longer accessible.
-</p>
-<p><strong>Action required:</strong> 
-Clients that illegally call the methods or refer ModelSynchronizeParticipant#refreshSchedule 
-will see a compilation error in the source and will need to remove all the calls and references.</p>
-
-<!-- ############################################## -->
-
-<h2>5. <a name="commonNavigatorLink">CommonNavigator#IS_LINKING_ENABLED_PROPERTY has changed its value</a></h2>
-<p><strong>What is affected: </strong>Clients that reference CommonNavigator#IS_LINKING_ENABLED_PROPERTY</p>
-<p><strong>Description:</strong> In release 3.4 and earlier, CommonNavigator#IS_LINKING_ENABLED_PROPERTY had
-the value of 1.  This value was the same as the IWorkbenchPartConstants#PROP_TITLE which caused confusion when
-properties changed.  Since Eclipse 3.5 the value of this property was changed to something that does
-not conflict with other property values.
-</p>
-<p><strong>Action required:</strong> 
-Any code that refers to CommonNavigator#IS_LINKING_ENABLED_PROPERTY must be recompiled to get the correct value.
-</p>
-
-<!-- ############################################## -->
-
-<h2>6. <a name="commonNavigatorInitialInput">CommonNavigator#getInitialInput() has changed its return type</a></h2>
-<p><strong>What is affected: </strong>Clients that illegally subclass CommonNavigator</p>
-<p><strong>Description:</strong> In release 3.4 and earlier, CommonNavigator#getInitialInput() returned a type of
-IAdaptable, in release 3.5 this has been changed to by Object to allow greater flexibility.  Subclassing
-the CommonNavigator is supported only in the 3.5 release, however this note is included because we are aware
-that many clients have subclassed CommonNavigator in prior releases.
-</p>
-<p><strong>Action required:</strong> 
-If you override CommonNavigator#getInitialInput(), you will need to fix and recompile your code to use the
-new return type of Object.
-See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=143430">bug 143430</a> for more information.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.5/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/3.5/recommended.html
deleted file mode 100644
index 8a7ca58..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.5/recommended.html
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adopting 3.5 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Adopting 3.5 mechanisms and APIs</h1>
-<p>
-  This section describes changes that are required if you are trying to change 
-  your 3.4 plug-in to adopt the 3.5 mechanisms and APIs.
-</p>
-
-<ol>
-  <li><a href="#ContentAssistAction">Delete creation of ContentAssistAction action</a></li>
-  <li><a href="#NewFilteredTreeLook">Switch to new look of FilteredTree</a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-
-<h2>1. <a name="ContentAssistAction">Delete creation of ContentAssistAction action</a></h2>
-<p>
-As of 3.5, the <code>AbstractTextEditor</code> creates and registers the content assist action. This means that subclasses no longer need to create and register their own content assist action.
-It is recommended to remove that code and to use <code>org.eclipse.ui.texteditor.ITextEditorActionConstants.CONTENT_ASSIST</code> when adding that action to the main menu or toolbar.
-</p><p>
-Same applies to the action that shows content assist context information (<code>org.eclipse.ui.texteditor.ITextEditorActionConstants.CONTENT_ASSIST_CONTEXT_INFORMATION</code>).
-</p>
-
-<!-- ############################################## -->
-
-<h2>2. <a name="NewFilteredTreeLook">Switch to new look of FilteredTree</a></h2>
-<p>
-As of 3.5, the <code>FilteredTree</code> comes with a new look. It is recommended to switch to that new look by using one of the two new constructors. Subclasses that switch to the
-new look must carefully review their UI because depending on what the subclass does, it might result in a broken look. In that case, the code in the subclass needs to be adjusted.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.6/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/3.6/faq.html
deleted file mode 100644
index 6194a2a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.6/faq.html
+++ /dev/null

@@ -1,30 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.6 Plug-in Migration FAQ</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.6 Plug-in Migration FAQ</h1>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2><a name="item1">Item 1</a></h2>
-<p>
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.6/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/3.6/incompatibilities.html
deleted file mode 100644
index ee35301..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.6/incompatibilities.html
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Incompatibilities between Eclipse 3.5 and 3.6</title>
-</head>
-<body>
-<h1>Incompatibilities between Eclipse 3.5 and 3.6</h1>
-
-<p>
-  Eclipse changed in incompatible ways between 3.5 and 3.6 in ways that affect 
-  plug-ins. The following entries describe the areas that changed and provide 
-  instructions for migrating 3.5 plug-ins to 3.6. Note that you only need to look 
-  here if you are experiencing problems running your 3.5 plug-in on 3.6.
-</p>
-
-<ol>
-	<li>None</li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-<!-- <h2><a name="item1">Item 1</a></h2>
-<p>
-Use an entry from a previous release as template
-</p>
--->
-
-<!-- ############################################## -->
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/3.6/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/3.6/recommended.html
deleted file mode 100644
index 3e75c6e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/3.6/recommended.html
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Adopting 3.6 mechanisms and APIs</title>
-</head>
-
-<body>
-
-<h1>Adopting 3.6 mechanisms and APIs</h1>
-<p>
-  This section describes changes that are required if you are trying to change 
-  your 3.5 plug-in to adopt the 3.6 mechanisms and APIs.
-</p>
-
-<ol>
-  <li><a href="#setDerived">Use IResource#setDerived(boolean, IProgressMonitor)</a></li>
-</ol>
-
-<hr>
-
-<!-- ############################################## -->
-
-<h2>1. <a name="setDerived">Use IResource#setDerived(boolean, IProgressMonitor)</a></h2>
-<p>
-As of 3.6, the <code>IResource#setDerived(boolean)</code> is deprecated. <code>IResource#setDerived(boolean, IProgressMonitor)</code>
-should be used instead and this change will be reported in a subsequent resource change event.</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_3_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_3_porting_guide.html
deleted file mode 100644
index 96fe278..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_3_porting_guide.html
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.3 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.3 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse 3.2 plug-ins to Eclipse 3.3.</p>
-<p>One of the goals of Eclipse 3.3 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.2 APIs should continue to work in 3.3 in spite of any API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.2 APIs remains valid for 
-  3.3, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.3 libraries.</p>
-<p>While every effort was made to avoid breakage, there are a few areas of incompatibility. 
-  This document describes the areas where Eclipse changed in incompatible ways 
-  between 3.2 and 3.3, and provides instructions for migrating 3.2 plug-ins to 
-  3.3.</p>
-<ul>
-  <li><a href="3.3/faq.html">Eclipse 3.3 Plug-in Migration FAQ</a></li>
-  <li><a href="3.3/incompatibilities.html">Incompatibilities between Eclipse 3.2 
-    and 3.3</a></li>
-  <li><a href="3.3/recommended.html">Adopting 3.3 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_4_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_4_porting_guide.html
deleted file mode 100644
index 4d44ab1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_4_porting_guide.html
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.4 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.4 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse 3.3 plug-ins to Eclipse 3.4.</p>
-<p>One of the goals of Eclipse 3.4 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.3 APIs should continue to work in 3.4 in spite of any API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.3 APIs remains valid for 
-  3.4, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.4 libraries.</p>
-<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
-  APIs that should be adopted by clients. 
-  This document describes those areas and provides instructions for migrating 3.3 plug-ins to 
-  3.4.</p>
-<ul>
-  <li><a href="3.4/faq.html">Eclipse 3.4 Plug-in Migration FAQ</a></li>
-  <li><a href="3.4/incompatibilities.html">Incompatibilities between Eclipse 3.3 and 3.4</a></li>
-  <li><a href="3.4/recommended.html">Adopting 3.4 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_5_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_5_porting_guide.html
deleted file mode 100644
index d8a19d8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_5_porting_guide.html
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.5 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.5 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse 3.4 plug-ins to Eclipse 3.5.</p>
-<p>One of the goals of Eclipse 3.5 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.4 APIs should continue to work in 3.5 in spite of any API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.4 APIs remains valid for 
-  3.5, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.5 libraries.</p>
-<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
-  APIs that should be adopted by clients. 
-  This document describes those areas and provides instructions for migrating 3.4 plug-ins to 
-  3.5.</p>
-<ul>
-  <li><a href="3.5/faq.html">Eclipse 3.5 Plug-in Migration FAQ</a></li>
-  <li><a href="3.5/incompatibilities.html">Incompatibilities between Eclipse 3.4 and 3.5</a></li>
-  <li><a href="3.5/recommended.html">Adopting 3.5 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_6_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_6_porting_guide.html
deleted file mode 100644
index d10391b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_3_6_porting_guide.html
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse 3.6 Plug-in Migration Guide</title>
-</head>
-
-<body>
-
-<h1>Eclipse 3.6 Plug-in Migration Guide</h1>
-<p>This guide covers migrating Eclipse 3.5 plug-ins to Eclipse 3.6.</p>
-<p>One of the goals of Eclipse 3.6 was to move Eclipse forward while remaining compatible 
-  with previous versions to the greatest extent possible. That is, plug-ins written 
-  against the Eclipse 3.5 APIs should continue to work in 3.6 in spite of any API changes.</p>
-<p>The key kinds of compatibility are API contract compatibility and binary compatibility. 
-  API contract compatibility means that valid use of 3.5 APIs remains valid for 
-  3.6, so there is no need to revisit working code. Binary compatibility means 
-  that the API method signatures, etc. did not change in ways that would cause 
-  existing compiled (&quot;binary&quot;) code to no longer link and run with the 
-  new 3.6 libraries.</p>
-<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
-  APIs that should be adopted by clients. 
-  This document describes those areas and provides instructions for migrating 3.5 plug-ins to 
-  3.6.</p>
-<ul>
-  <li><a href="3.6/faq.html">Eclipse 3.6 Plug-in Migration FAQ</a></li>
-  <li><a href="3.6/incompatibilities.html">Incompatibilities between Eclipse 3.5 and 3.6</a></li>
-  <li><a href="3.6/recommended.html">Adopting 3.6 mechanisms and API</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/questions/index.html b/bundles/org.eclipse.platform.doc.isv/questions/index.html
deleted file mode 100644
index aaeaf45..0000000
--- a/bundles/org.eclipse.platform.doc.isv/questions/index.html
+++ /dev/null

@@ -1,118 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   
-   <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Platform questions index</title>
-</head>
-<body>
-
-<h1>
-Platform questions index</h1>
-<h3>Getting started</h3>
-<ul>
-  <li><a href="../samples/samples.html">How do I install the examples?</a></li>
-</ul>
-<h3>Core runtime</h3>
-<ul>
-  <li><a href="../guide/arch.htm">What is an extension point?&nbsp; an
-    extension?</a></li>
- <li><a href="../reference/misc/plugin_manifest.html">What is the formal definition
-    for the manifest file?</a></li>
-  <li><a href="../guide/product_def_nl.htm">Where do I put translated files for
-    NLS?</a></li>
-</ul>
-<h3>Resources</h3>
-<ul>
-  <li><a href="../guide/resInt_workspace.htm">What is a workspace?</a>&nbsp;&nbsp;</li>
-  <li><a href="../guide/resInt.htm">What is a resource?</a></li>
-  <li><a href="../guide/resInt_properties.htm">What are resource properties?</a></li>
-  <li><a href="../guide/resAdv_saving.htm">How can I save my plug-in's
-    information when the workspace is saved?</a></li>
-  <li><a href="../guide/resAdv_events.htm">How do I know what changes are being
-    made to resources in the workspace?</a></li>
-  <li><a href="../guide/resAdv_markers.htm">How do I use markers?</a></li>
-  <li><a href="../guide/resAdv_markers.htm#resAdv_markers_extending">How do I
-    define my own marker?</a></li>
-  <li><a href="../guide/resAdv_natures.htm">What is a project nature?</a></li>
-  <li><a href="../guide/resAdv_builders.htm">How do I set up an incremental
-    project builder?</a></li>
-</ul>
-<h3>New file types in the UI</h3>
-<ul>
-  <li><a href="../guide/workbench_basicext_editors.htm">How do I set up an
-    editor for a particular file extension?</a></li>
-  <li><a href="../guide/preferences_prop_contribute.htm">How do I add a properties page for
-    a resource?</a></li>
-  <li><a href="../guide/dialogs_wizards_newWizards.htm">How do I add a new
-    resource wizard to the workbench?</a></li>
-  <li><a href="../guide/workbench_advext_decorators.htm">How do I provide
-    special icons for my new file type?</a></li>
-</ul>
-<h3>Workbench UI</h3>
-<ul>
-  <li><a href="../guide/workbench_structure.htm">What is a view?&nbsp; an
-    editor?&nbsp; a page?</a></li>
-  <li><a href="../guide/workbench_advext_perspectives.htm">What is a
-    perspective?&nbsp; How do I define one?</a></li>
-  <li><a href="../guide/workbench_structure.htm#views_and_editors">When do I
-    want to build a view vs. an editor?</a></li>
-  <li><a href="../guide/editors_workbench_outliner.htm">How do I customize a
-    content outliner for an editor?</a></li>
-  <li><a href="../guide/preferences_prefs.htm">How do I add a page to the
-    preferences dialog?</a></li>
-  <li><a href="../guide/workbench_basicext.htm">Where should I start learning
-    how to extend the workbench UI?</a></li>
-  <li><a href="../reference/extension-points/index.html">What extension points
-    are defined by the workbench UI?</a></li>
-  <li><a href="../guide/workbench_menus.htm">How do I add a menu to the
-    workbench?</a></li>
-  <li><a HREF="../guide/workbench_menupaths.htm">How do I
-    specify menu and toolbar paths?</a></li>
-  <li><a href="../guide/wrkAdv_retarget.htm">How do I implement common actions
-    like cut/copy/paste?</a></li>
-  <li><a href="../guide/jface_resources.htm">How should I manage the icons in my
-    plug-in?</a></li>
-  <li><a href="../guide/dialogs_standard.htm">How do I build an error or message
-    dialog?</a></li>
-  <li><a href="../guide/dialogs_applications.htm">How do I implement a simple
-    dialog of my own?</a></li>
-  <li><a href="../guide/dialogs_settings.htm">How should I remember the user
-    settings in a dialog?</a></li>
-  <li><a href="../guide/jface_viewers.htm">Why would I want a viewer instead of
-    an SWT widget?</a></li>
-  <li><a href="../guide/editors_jface.htm">How should I start learning about the
-    text framework?</a></li>
-  <li><a href="../guide/dialogs_wizards_wizarddialogs.htm">How do I launch a
-    wizard if I'm not adding it as a workbench extension?</a></li>
-  <li><a href="../guide/dialogs_wizards_multipage.htm">How do I build a wizard
-    with multiple pages?</a></li>
-  <li><a href="../guide/swt_widgets_controls.htm">What widgets are available in
-    SWT?</a></li>
-  <li><a href="../guide/swt_layouts.htm">How do I implement an SWT layout?</a></li>
-  <li><a href="http://www.eclipse.org/articles/Article-Writing%20Your%20Own%20Widget/Writing%20Your%20Own%20Widget.htm">How do I implement an
-    SWT native
-    widget?</a></li>
-  <li><a href="../guide/swt_widgets_custom.htm">How do I implement a custom
-    widget in SWT?</a></li>
-  <li><a href="../guide/swt_graphics.htm">How do I draw my own graphics?</a></li>
-</ul>
-<h3>Installation and upgrade</h3>
-<ul>
-  <li><a href="../guide/product_configproduct.htm">How do I configure my own splash
-    screens and product name?</a></li>
-  <li><a href="../guide/product_def_feature.htm">What is a feature?</a></li>
-  <li><a href="../reference/misc/feature_archive.html">How do I package a
-    feature so it will work with the update manager?</a></li>
-  <li><a href="../guide/ua_intro.htm">How do I configure a custom
-    welcome (intro) page?</a></li>
-  <li><a href="../reference/misc/eclipse-install.html">How do I install an
-    Eclipse based product?</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/.cvsignore b/bundles/org.eclipse.platform.doc.isv/reference/.cvsignore
deleted file mode 100644
index eedd89b..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/.cvsignore
+++ /dev/null

@@ -1 +0,0 @@
-api

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html b/bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html
deleted file mode 100644
index 92d35b8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/extension-points/index.html
+++ /dev/null

@@ -1,244 +0,0 @@
-<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <title>Platform Extension Points</title>
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body link="#0000FF" vlink="#800080">
-
-<center>
-<h1>Platform Extension Points
-</h1></center>
-
-The following extension points can be used to extend the capabilities
-of the platform infrastructure:
-<h3><a name="runtime"></a>Platform runtime</h3>
-<ul>
-  <li><a href="org_eclipse_core_contenttype_contentTypes.html">org.eclipse.core.contenttype.contentTypes</a></li>
-  <li><a href="org_eclipse_core_runtime_adapters.html">org.eclipse.core.runtime.adapters</a></li>
-  <li><a href="org_eclipse_core_runtime_applications.html">org.eclipse.core.runtime.applications</a></li>
-  <li><a href="org_eclipse_core_runtime_contentTypes.html">org.eclipse.core.runtime.contentTypes</a></li>
-  <li><a href="org_eclipse_core_runtime_preferences.html">org.eclipse.core.runtime.preferences</a></li>
-  <li><a href="org_eclipse_core_runtime_products.html">org.eclipse.core.runtime.products</a></li>
-  <li><a href="org_eclipse_equinox_preferences_preferences.html">org.eclipse.equinox.preferences.preferences</a></li>
-</ul>
-<h3><a name="workspace"></a>Workspace</h3>
-<ul>
-  <li><a href="org_eclipse_core_resources_builders.html">org.eclipse.core.resources.builders</a>
-  </li>
-   <li><a href="org_eclipse_core_resources_fileModificationValidator.html">org.eclipse.core.resources.fileModificationValidator</a>
-  </li>
-  <li><a href="org_eclipse_core_resources_markers.html">org.eclipse.core.resources.markers</a></li>
-  <li><a href="org_eclipse_core_resources_moveDeleteHook.html">org.eclipse.core.resources.moveDeleteHook</a></li>
-  <li><a href="org_eclipse_core_resources_natures.html">org.eclipse.core.resources.natures</a></li>
-  <li><a href="org_eclipse_core_resources_refreshProviders.html">org.eclipse.core.resources.refreshProviders</a></li>
-  <li><a href="org_eclipse_core_resources_teamHook.html">org.eclipse.core.resources.teamHook</a></li>
-  <li><a href="org_eclipse_core_filesystem_filesystems.html">org.eclipse.core.filesystem.filesystems</a></li>
-</ul>
-
-<h3><a name="text"></a>Platform Text</h3>
-<ul>
-	<li><a href="org_eclipse_core_filebuffers_annotationModelCreation.html">org.eclipse.core.filebuffers.annotationModelCreation</a></li>
-	<li><a href="org_eclipse_core_filebuffers_documentCreation.html">org.eclipse.core.filebuffers.documentCreation</a></li>
-	<li><a href="org_eclipse_core_filebuffers_documentSetup.html">org.eclipse.core.filebuffers.documentSetup</a></li>
-	<li><a href="org_eclipse_ui_editors_annotationTypes.html">org.eclipse.ui.editors.annotationTypes</a></li>
-	<li><a href="org_eclipse_ui_editors_documentProviders.html">org.eclipse.ui.editors.documentProviders</a></li>
-	<li><a href="org_eclipse_ui_editors_markerAnnotationSpecification.html">org.eclipse.ui.editors.markerAnnotationSpecification</a></li>
-	<li><a href="org_eclipse_ui_editors_markerUpdaters.html">org.eclipse.ui.editors.markerUpdaters</a></li>
-	<li><a href="org_eclipse_ui_editors_templates.html">org.eclipse.ui.editors.templates</a></li>
-	<li><a href="org_eclipse_ui_workbench_texteditor_hyperlinkDetectors.html">org.eclipse.ui.workbench.texteditor.hyperlinkDetectors</a></li>
-	<li><a href="org_eclipse_ui_workbench_texteditor_hyperlinkDetectorTargets.html">org.eclipse.ui.workbench.texteditor.hyperlinkDetectorTargets</a></li>
-	<li><a href="org_eclipse_ui_workbench_texteditor_rulerColumns.html">org.eclipse.ui.workbench.texteditor.rulerColumns</a></li>
-	<li><a href="org_eclipse_ui_workbench_texteditor_quickDiffReferenceProvider.html">org.eclipse.ui.workbench.texteditor.quickDiffReferenceProvider</a></li>
-	<li><a href="org_eclipse_ui_workbench_texteditor_spellingEngine.html">org.eclipse.ui.workbench.texteditor.spellingEngine</a></li>
-</ul>
-
-<h3><a name="workbench"></a>Workbench</h3>
-<ul>
-  <li><a href="org_eclipse_ui_acceleratorConfigurations.html">org.eclipse.ui.acceleratorConfigurations</a></li>
-  <li><a href="org_eclipse_ui_acceleratorScopes.html">org.eclipse.ui.acceleratorScopes</a></li>
-  <li><a href="org_eclipse_ui_acceleratorSets.html">org.eclipse.ui.acceleratorSets</a></li>
-  <li><a href="org_eclipse_ui_actionDefinitions.html">org.eclipse.ui.actionDefinitions</a></li>
-  <li><a href="org_eclipse_ui_actionSetPartAssociations.html">org.eclipse.ui.actionSetPartAssociations</a></li>
-  <li><a href="org_eclipse_ui_actionSets.html">org.eclipse.ui.actionSets</a></li>
-  <li><a href="org_eclipse_ui_activities.html">org.eclipse.ui.activities</a></li>
-  <li><a href="org_eclipse_ui_activitySupport.html">org.eclipse.ui.activitySupport</a></li>
-  <li><a href="org_eclipse_ui_bindings.html">org.eclipse.ui.bindings</a></li>
-  <li><a href="org_eclipse_ui_browser_browsers.html">org.eclipse.ui.browser.browsers</a></li>
-  <li><a href="org_eclipse_ui_browserSupport.html">org.eclipse.ui.browserSupport</a></li>
-  <li><a href="org_eclipse_ui_commands.html">org.eclipse.ui.commands</a></li>
-  <li><a href="org_eclipse_ui_commandImages.html">org.eclipse.ui.commandImages</a></li>
-  <li><a href="org_eclipse_ui_contexts.html">org.eclipse.ui.contexts</a></li>
-  <li><a href="org_eclipse_ui_decorators.html">org.eclipse.ui.decorators</a></li>
-  <li><a href="org_eclipse_ui_dropActions.html">org.eclipse.ui.dropActions</a></li>
-  <li><a href="org_eclipse_ui_editorActions.html">org.eclipse.ui.editorActions</a></li>
-  <li><a href="org_eclipse_ui_editors.html">org.eclipse.ui.editors</a></li>
-  <li><a href="org_eclipse_ui_elementFactories.html">org.eclipse.ui.elementFactories</a></li>
-  <li><a href="org_eclipse_ui_encodings.html">org.eclipse.ui.encodings</a></li>
-  <li><a href="org_eclipse_ui_exportWizards.html">org.eclipse.ui.exportWizards</a></li>
-  <li><a href="org_eclipse_ui_fontDefinitions.html">org.eclipse.ui.fontDefinitions</a></li>
-  <li><a href="org_eclipse_ui_handlers.html">org.eclipse.ui.handlers</a></li>
-  <li><a href="org_eclipse_ui_helpSupport.html">org.eclipse.ui.helpSupport</a></li>
-  <li><a href="org_eclipse_ui_ide_filesystemSupport.html">org.eclipse.ui.ide.filesystemSupport</a></li>
-  <li><a href="org_eclipse_ui_ide_markerHelp.html">org.eclipse.ui.ide.markerHelp</a></li>
-  <li><a href="org_eclipse_ui_ide_markerImageProviders.html">org.eclipse.ui.ide.markerImageProviders</a></li>
-  <li><a href="org_eclipse_ui_ide_markerResolution.html">org.eclipse.ui.ide.markerResolution</a></li>
-  <li><a href="org_eclipse_ui_ide_markerSupport.html">org.eclipse.ui.ide.markerSupport</a></li>
-  <li><a href="org_eclipse_ui_ide_projectNatureImages.html">org.eclipse.ui.ide.projectNatureImages</a></li>
-  <li><a href="org_eclipse_ui_ide_resourceFilters.html">org.eclipse.ui.ide.resourceFilters</a></li>
-  <li><a href="org_eclipse_ui_navigator_linkHelper.html">org.eclipse.ui.navigator.linkHelper</a></li>
-  <li><a href="org_eclipse_ui_navigator_navigatorContent.html">org.eclipse.ui.navigator.navigatorContent</a></li>
-  <li><a href="org_eclipse_ui_navigator_viewer.html">org.eclipse.ui.navigator.viewer</a></li>
-  <li><a href="org_eclipse_ui_importWizards.html">org.eclipse.ui.importWizards</a></li>
-  <li><a href="org_eclipse_ui_installationPages.html">org.eclipse.ui.installationPages</a></li>
-  <li><a href="org_eclipse_ui_intro.html">org.eclipse.ui.intro</a></li>
-  <li><a href="org_eclipse_ui_keywords.html">org.eclipse.ui.keywords</a></li>
-  <li><a href="org_eclipse_ui_menus.html">org.eclipse.ui.menus</a></li>
-  <li><a href="org_eclipse_ui_newWizards.html">org.eclipse.ui.newWizards</a></li>
-  <li><a href="org_eclipse_ui_perspectiveExtensions.html">org.eclipse.ui.perspectiveExtensions</a></li>
-  <li><a href="org_eclipse_ui_perspectives.html">org.eclipse.ui.perspectives</a></li>
-  <li><a href="org_eclipse_ui_popupMenus.html">org.eclipse.ui.popupMenus</a></li>
-  <li><a href="org_eclipse_ui_preferencePages.html">org.eclipse.ui.preferencePages</a></li>
-  <li><a href="org_eclipse_ui_preferenceTransfer.html">org.eclipse.ui.preferenceTransfer</a></li>
-  <li><a href="org_eclipse_ui_presentationFactories.html">org.eclipse.ui.presentationFactories</a></li>
-  <li><a href="org_eclipse_ui_propertiesView.html">org.eclipse.ui.propertiesView</a></li>    
-  <li><a href="org_eclipse_ui_propertyPages.html">org.eclipse.ui.propertyPages</a></li>
-  <li><a href="org_eclipse_ui_splashHandlers.html">org.eclipse.ui.splashHandlers</a></li>
-  <li><a href="org_eclipse_ui_startup.html">org.eclipse.ui.startup</a></li>
-  <li><a href="org_eclipse_ui_statusHandlers.html">org.eclipse.ui.statusHandlers</a></li>
-  <li><a href="org_eclipse_ui_systemSummarySections.html">org.eclipse.ui.systemSummarySections</a></li>
-  <li><a href="org_eclipse_ui_themes.html">org.eclipse.ui.themes</a></li>
-  <li><a href="org_eclipse_ui_viewActions.html">org.eclipse.ui.viewActions</a></li>
-  <li><a href="org_eclipse_ui_views.html">org.eclipse.ui.views</a></li>
-  <li><a href="org_eclipse_ui_views_properties_tabbed_propertyContributor.html">org.eclipse.ui.views.properties.tabbed.propertyContributor</a></li>
-  <li><a href="org_eclipse_ui_views_properties_tabbed_propertySections.html">org.eclipse.ui.views.properties.tabbed.propertySections</a></li>
-  <li><a href="org_eclipse_ui_views_properties_tabbed_propertyTabs.html">org.eclipse.ui.views.properties.tabbed.propertyTabs</a></li>
-  <li><a href="org_eclipse_ui_workingSets.html">org.eclipse.ui.workingSets</a></li>
-</ul>
-<h3><a name="team"></a>Team</h3>
-<ul>
-  <li><a href="org_eclipse_team_core_fileTypes.html">org.eclipse.team.core.fileTypes</a></li>
-  <li><a href="org_eclipse_team_core_ignore.html">org.eclipse.team.core.ignore</a></li>
-  <li><a href="org_eclipse_team_core_projectSets.html">org.eclipse.team.core.projectSets</a></li>
-  <li><a href="org_eclipse_team_core_repository.html">org.eclipse.team.core.repository</a></li>
-  <li><a href="org_eclipse_team_core_storageMergers.html">org.eclipse.team.core.storageMergers</a></li>
-  <li><a href="org_eclipse_team_ui_configurationWizards.html">org.eclipse.team.ui.configurationWizards</a></li>
-  <li><a href="org_eclipse_team_ui_synchronizeParticipants.html">org.eclipse.team.ui.synchronizeParticipants</a></li>
-  <li><a href="org_eclipse_team_ui_synchronizeWizards.html">org.eclipse.team.ui.synchronizeWizards</a></li>
-  <li><a href="org_eclipse_team_ui_teamContentProviders.html">org.eclipse.team.ui.teamContentProviders</a></li>
-  <li><a href="org_eclipse_team_ui_teamDecorators.html">org.eclipse.team.ui.teamDecorators</a></li>
- </ul>
-<h3><a name="debug"></a>Debug</h3>
-<ul>
-  <li><a href="org_eclipse_debug_core_breakpoints.html">org.eclipse.debug.core.breakpoints</a></li>
-  <li><a href="org_eclipse_debug_core_breakpointImportParticipants.html">org.eclipse.debug.core.breakpointImportParticipants</a></li>
-  <li><a href="org_eclipse_debug_core_launchConfigurationComparators.html">org.eclipse.debug.core.launchConfigurationComparators</a></li>
-  <li><a href="org_eclipse_debug_core_launchConfigurationTypes.html">org.eclipse.debug.core.launchConfigurationTypes</a></li>
-  <li><a href="org_eclipse_debug_core_launchDelegates.html">org.eclipse.debug.core.launchDelegates</a></li>
-  <li><a href="org_eclipse_debug_core_launchers.html">org.eclipse.debug.core.launchers</a></li>
-  <li><a href="org_eclipse_debug_core_launchModes.html">org.eclipse.debug.core.launchModes</a></li>
-  <li><a href="org_eclipse_debug_core_logicalStructureProviders.html">org.eclipse.debug.core.logicalStructureProviders</a></li>
-  <li><a href="org_eclipse_debug_core_logicalStructureTypes.html">org.eclipse.debug.core.logicalStructureTypes</a></li>
-  <li><a href="org_eclipse_debug_core_processFactories.html">org.eclipse.debug.core.processFactories</a></li>
-  <li><a href="org_eclipse_debug_core_sourceContainerTypes.html">org.eclipse.debug.core.sourceContainerTypes</a></li>
-  <li><a href="org_eclipse_debug_core_sourceLocators.html">org.eclipse.debug.core.sourceLocators</a></li>
-  <li><a href="org_eclipse_debug_core_sourcePathComputers.html">org.eclipse.debug.core.sourcePathComputers</a></li>
-  <li><a href="org_eclipse_debug_core_statusHandlers.html">org.eclipse.debug.core.statusHandlers</a></li>
-  <li><a href="org_eclipse_debug_core_watchExpressionDelegates.html">org.eclipse.debug.core.watchExpressionDelegates</a></li>
-  <li><a href="org_eclipse_debug_ui_breakpointOrganizers.html">org.eclipse.debug.ui.breakpointOrganizers</a></li>  
-  <li><a href="org_eclipse_debug_ui_consoleColorProviders.html">org.eclipse.debug.ui.consoleColorProviders</a></li>
-  <li><a href="org_eclipse_debug_ui_consoleLineTrackers.html">org.eclipse.debug.ui.consoleLineTrackers</a></li>
-  <li><a href="org_eclipse_debug_ui_contextViewBindings.html">org.eclipse.debug.ui.contextViewBindings</a></li>
-  <li><a href="org_eclipse_debug_ui_debugModelContextBindings.html">org.eclipse.debug.ui.debugModelContextBindings</a></li>
-  <li><a href="org_eclipse_debug_ui_debugModelPresentations.html">org.eclipse.debug.ui.debugModelPresentations</a></li>
-  <li><a href="org_eclipse_debug_ui_detailPaneFactories.html">org.eclipse.debug.ui.detailPaneFactories</a></li>
-  <li><a href="org_eclipse_debug_ui_launchConfigurationTabGroups.html">org.eclipse.debug.ui.launchConfigurationTabGroups</a></li>
-  <li><a href="org_eclipse_debug_ui_launchConfigurationTabs.html">org.eclipse.debug.ui.launchConfigurationTabs</a></li>
-  <li><a href="org_eclipse_debug_ui_launchConfigurationTypeImages.html">org.eclipse.debug.ui.launchConfigurationTypeImages</a></li>
-  <li><a href="org_eclipse_debug_ui_launchGroups.html">org.eclipse.debug.ui.launchGroups</a></li>
-  <li><a href="org_eclipse_debug_ui_launchShortcuts.html">org.eclipse.debug.ui.launchShortcuts</a></li>
-  <li><a href="org_eclipse_debug_ui_memoryRenderings.html">org.eclipse.debug.ui.memoryRenderings</a></li>    
-  <li><a href="org_eclipse_debug_ui_sourceContainerPresentations.html">org.eclipse.debug.ui.sourceContainerPresentations</a></li>
-  <li><a href="org_eclipse_debug_ui_stringVariablePresentations.html">org.eclipse.debug.ui.stringVariablePresentations</a></li>
-  <li><a href="org_eclipse_debug_ui_toggleBreakpointsTargetFactories.html">org.eclipse.debug.ui.toggleBreakpointsTargetFactories</a></li>
-  <li><a href="org_eclipse_debug_ui_variableValueEditors.html">org.eclipse.debug.ui.variableValueEditors</a></li>      
-</ul>
-<h3><a name="console"></a>Console</h3>
-<ul>
-  <li><a href="org_eclipse_ui_console_consoleFactories.html">org.eclipse.ui.console.consoleFactories</a></li>
-  <li><a href="org_eclipse_ui_console_consolePageParticipants.html">org.eclipse.ui.console.consolePageParticipants</a></li>
-  <li><a href="org_eclipse_ui_console_consolePatternMatchListeners.html">org.eclipse.ui.console.consolePatternMatchListeners</a></li>
-</ul>
-<h3><a name="ua"></a>User Assistance</h3>
-<ul>
-  <li><a href="org_eclipse_help_contentExtension.html">org.eclipse.help.contentExtension</a></li>
-  <li><a href="org_eclipse_help_contentProducer.html">org.eclipse.help.contentProducer</a></li>
-  <li><a href="org_eclipse_help_contexts.html">org.eclipse.help.contexts</a></li>
-  <li><a href="org_eclipse_help_index.html">org.eclipse.help.index</a></li>
-  <li><a href="org_eclipse_help_toc.html">org.eclipse.help.toc</a></li>
-  <li><a href="org_eclipse_help_base_activitySupport.html">org.eclipse.help.base.activitySupport</a></li>
-  <li><a href="org_eclipse_help_base_browser.html">org.eclipse.help.base.browser</a></li>
-  <li><a href="org_eclipse_help_base_luceneAnalyzer.html">org.eclipse.help.base.luceneAnalyzer</a></li>
-  <li><a href="org_eclipse_help_base_luceneSearchParticipants.html">org.eclipse.help.base.luceneSearchParticipants</a></li>
-  <li><a href="org_eclipse_help_base_server.html">org.eclipse.help.base.server</a></li>
-  <li><a href="org_eclipse_help_ui_searchEngine.html">org.eclipse.help.ui.searchEngine</a></li>
-  <li><a href="org_eclipse_help_webapp_contentFilter.html">org.eclipse.help.webapp.contentFilter</a></li>
-  <li><a href="org_eclipse_ui_cheatsheets_cheatSheetContent.html">org.eclipse.ui.cheatsheets.cheatSheetContent</a></li>
-  <li><a href="org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html">org.eclipse.ui.cheatsheets.cheatSheetItemExtension</a></li>
-  <li><a href="org_eclipse_ui_intro_config.html">org.eclipse.ui.intro.config</a></li>
-  <li><a href="org_eclipse_ui_intro_configExtension.html">org.eclipse.ui.intro.configExtension</a></li>
-</ul>
-<h3><a name="ltk"></a>Language Toolkit</h3>
-<ul>
-  <li><a href="org_eclipse_ltk_core_refactoring_refactoringContributions.html">org.eclipse.ltk.core.refactoring.refactoringContributions</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_copyParticipants.html">org.eclipse.ltk.core.refactoring.copyParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_createParticipants.html">org.eclipse.ltk.core.refactoring.createParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_deleteParticipants.html">org.eclipse.ltk.core.refactoring.deleteParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_moveParticipants.html">org.eclipse.ltk.core.refactoring.moveParticipants</a></li>
-  <li><a href="org_eclipse_ltk_core_refactoring_renameParticipants.html">org.eclipse.ltk.core.refactoring.renameParticipants</a></li>
-  <li><a href="org_eclipse_ltk_ui_refactoring_changePreviewViewers.html">org.eclipse.ltk.ui.refactoring.changePreviewViewers</a></li>
-  <li><a href="org_eclipse_ltk_ui_refactoring_statusContextViewers.html">org.eclipse.ltk.ui.refactoring.statusContextViewers</a></li>
-</ul>
-<h3><a name="security"></a>Security</h3>
-<ul>
-  <li><a href="org_eclipse_equinox_security_loginConfigurationProvider.html">org.eclipse.equinox.security.loginConfigurationProvider</a></li>
-  <li><a href="org_eclipse_equinox_security_loginModule.html">org.eclipse.equinox.security.loginModule</a></li>
-  <li><a href="org_eclipse_equinox_security_callbackHandler.html">org.eclipse.equinox.security.callbackHandler</a></li>
-  <li><a href="org_eclipse_equinox_security_callbackHandlerMapping.html">org.eclipse.equinox.security.callbackHandlerMapping</a></li>
-  <li><a href="org_eclipse_equinox_security_secureStorage.html">org.eclipse.equinox.security.secureStorage</a></li>
-</ul>
-<h3><a name="other"></a>Other</h3>
-<ul>
-  <li><a href="org_eclipse_ant_core_antProperties.html">org.eclipse.ant.core.antProperties</a></li>
-  <li><a href="org_eclipse_ant_core_antTasks.html">org.eclipse.ant.core.antTasks</a></li>
-  <li><a href="org_eclipse_ant_core_antTypes.html">org.eclipse.ant.core.antTypes</a></li>
-  <li><a href="org_eclipse_ant_core_extraClasspathEntries.html">org.eclipse.ant.core.extraClasspathEntries</a></li>
-  <li><a href="org_eclipse_compare_contentMergeViewers.html">org.eclipse.compare.contentMergeViewers</a></li>
-  <li><a href="org_eclipse_compare_contentViewers.html">org.eclipse.compare.contentViewers</a></li>
-  <li><a href="org_eclipse_compare_streamMergers.html">org.eclipse.compare.streamMergers</a></li>
-  <li><a href="org_eclipse_compare_structureCreators.html">org.eclipse.compare.structureCreators</a></li>
-  <li><a href="org_eclipse_compare_structureMergeViewers.html">org.eclipse.compare.structureMergeViewers</a></li>
-  <li><a href="org_eclipse_core_expressions_propertyTesters.html">org.eclipse.core.expressions.propertyTesters</a></li>
-  <li><a href="org_eclipse_core_expressions_definitions.html">org.eclipse.core.expressions.definitions</a></li>
-  <li><a href="org_eclipse_core_variables_dynamicVariables.html">org.eclipse.core.variables.dynamicVariables</a></li>
-  <li><a href="org_eclipse_core_variables_valueVariables.html">org.eclipse.core.variables.valueVariables</a></li>
-  <li><a href="org_eclipse_equinox_http_registry_httpcontexts.html">org.eclipse.equinox.http.registry.httpcontexts</a></li>
-  <li><a href="org_eclipse_equinox_http_registry_resources.html">org.eclipse.equinox.http.registry.resources</a></li>
-  <li><a href="org_eclipse_equinox_http_registry_servlets.html">org.eclipse.equinox.http.registry.servlets</a></li>
-  <li><a href="org_eclipse_search_searchPages.html">org.eclipse.search.searchPages</a></li>
-  <li><a href="org_eclipse_search_searchResultSorters.html">org.eclipse.search.searchResultSorters</a></li>
-  <li><a href="org_eclipse_search_searchResultViewPages.html">org.eclipse.search.searchResultViewPages</a></li>
-  <li><a href="org_eclipse_search_textSearchEngine.html">org.eclipse.search.textSearchEngine</a></li>
-  <li><a href="org_eclipse_search_textSearchQueryProvider.html">org.eclipse.search.textSearchQueryProvider</a></li>
-  <li><a href="org_eclipse_ui_externaltools_configurationDuplicationMaps.html">org.eclipse.ui.externaltools.configurationDuplicationMaps</a></li>
-  <li><a href="org_eclipse_update_core_featureTypes.html">org.eclipse.update.core.featureTypes</a></li>
-  <li><a href="org_eclipse_update_core_installHandlers.html">org.eclipse.update.core.installHandlers</a></li>
-  <li><a href="org_eclipse_update_core_siteTypes.html">org.eclipse.update.core.siteTypes</a></li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html
deleted file mode 100644
index c607ef4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/about_customization.html
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>About.ini File Format</title>
-</head>
-
-<body>
-
-<h1>About.ini File Format</h1>
-<p>Last revised March 25, 2003 for Eclipse 2.1</p>
-<p>A feature's &quot;about&quot; information is given by properties in the
-&quot;<code>about.ini</code>&quot; file located within the feature's <i>plug-in</i>.
-This is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with \u<i>xxxx </i>Unicode escapes),
-with the following keys:</p>
-<ul>
-  <li>&quot;<code>aboutText</code>&quot; - A multi-line text description of the
-    feature containing copyright, license terms, license registration info, etc.
-    URLs found in text are presented as links. Line breaks are indicated by
-    &quot;<code>\n</code>&quot;; lines should be no longer than 75 characters
-    each, and there is a limit of 15 lines. This information is shown in the
-    main &quot;about&quot; dialog (used in conjunction with a half-sized image),
-    and on the secondary &quot;about&quot; dialog describing individuals
-    feature. All features are required to have this property.</li>
-  <li>&quot;<code>windowImage</code>&quot; - A 16x16 pixel color image used to
-    brand windows created by a product. The value of this property is a
-    plug-in-relative path to an image file. This property is only required for
-    primary features; other features may omit it.</li>
-  <li>&quot;<code>featureImage</code>&quot; - A 32x32 pixel color image used as
-    an icon for this feature. The value of this property is a plug-in-relative
-    path to an image file. This image is shown on the &quot;about&quot; dialog
-    describing individual features, and is also used on the main
-    &quot;about&quot; dialog to indicate that the feature is present. This
-    property is optional. Related features supplied by a single provider should
-    contain copies of the identical image file; this allows duplicate images to
-    be eliminated.</li>
-  <li>&quot;<code>aboutImage</code>&quot; - A large color image that appears in
-    the main &quot;about&quot; dialog for a product. The value of this property
-    is a plug-in-relative path to an image file. This property is only required
-    for primary features; other features should omit it. Both graphic-and-text,
-    and graphic only layouts are supported, depending on the size of image
-    provided. A half-size image of up to 250 pixels wide by 330 pixels high is
-    shown on the main &quot;about&quot; dialog with text (&quot;<code>aboutText</code>&quot;
-    property) beside it. A full-size image of up to 500 pixels wide by 330
-    pixels high is shown without text.</li>
-  <li>&quot;<code>welcomePage</code>&quot;&nbsp; - A welcome page. The value of
-    this property is a plug-in-relative path to an XML-format file containing
-    the feature's welcome page. This property is recommended for all major
-    features; other features may omit it.</li>
-  <li>&quot;<code>welcomePerspective</code>&quot;&nbsp; - The preferred
-    perspective in which to show the welcome page. The value of this property is
-    a workbench perspective id. This property is recommended for features with
-    welcome pages that show better in the context of the feature's views and
-    editors. Features that do not have welcome pages, or have no strong opinion
-    where the welcome pages is shown, should omit it.</li>
-  <li>&quot;<code>appName</code>&quot; - A short, non-translatable string used to associate a name
-    with the application on platforms where this makes sense. In operating
-    environments with the Motif window system, the value is used for Motif
-    resource lookup (see xrdb and related). In addition, on the CDE window
-    manager (used on Solaris and AIX), this is the name which shows up under the
-    icon for windows which are minimized to the desktop. This property is
-    required for primary features; other features may omit it.</li>
-  <li>&quot;<code>tipsAndTricksHref</code>&quot;&nbsp; - Tips and tricks section
-    of help documentation. The value of this property is a reference to a help
-    book containing the feature's tips and trick section; for example, <code>tipsAndTricksHref=/org.eclipse.jdt.doc.user/tips/jdt_tips.html</code>.
-    This property is recommended for all major features; other features may omit
-    it.</li>
-</ul>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html
deleted file mode 100644
index 29cbccc..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/api-usage-rules.html
+++ /dev/null

@@ -1,343 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Eclipse Platform API - Rules of Engagement</title>
-  
-
-</head>
-<body>
-
-<h1>
-Eclipse platform<br>
-API rules of engagement</h1>
-<i><font size=-1>Version 0.15 - Last revised 12:00 May 30, 2001</font></i>
-<p>Here are the rules of engagement for clients of the Eclipse platform
-API (and other components).</p>
-<h2>
-What it means to be API</h2>
-<p>The Eclipse platform defines API elements for use by its clients, namely
-ISVs writing plug-ins. These plug-ins may in turn define API elements for
-their clients, and so on. API elements are the public face: they carry
-a specification about what they are supposed to do, and about how they
-are intended to be used. API elements are supported: the Eclipse platform
-team will fix implementation bugs where there is a deviation from the specified
-behavior. Since there is often a high cost associated with breaking API
-changes, the Eclipse platform team will also try to evolve API elements
-gracefully through successive major releases.</p>
-<h2>
-How to tell API from non-API</h2>
-<p>By their very nature, API elements are documented and have a specification,
-in contrast to non-API elements which are internal implementation details
-usually without published documentation or specifications. So if you cannot
-find the documentation for something, that's usually a good indicator that
-it's not API.</p>
-<p>To try to draw the line more starkly, the code base for the platform
-is separated into API and non-API packages, with all API elements being
-declared in designated API packages.</p>
-<ul>
-<li>
-<b>API package</b> - a Java package that contains at least one API class
-or API interface. The names of API packages are advertised in the documentation
-for that component; where feasible, all other packages containing only
-implementation details have "internal" in the package name. The names of
-API packages may legitimately appear in client code. For the Eclipse platform
-proper, these are:</li>
-
-</ul><ul>
-<li>
-<tt>org.eclipse.foo.*</tt> - for example, <tt>org.eclipse.swt.widgets</tt>,
-<tt>org.eclipse.ui</tt>,
-or <tt>org.eclipse.core.runtime</tt></li>
-
-<li>
-<tt>org.eclipse.foo.internal.*</tt> - not API; internal implementation
-packages</li>
-
-<li>
-<tt>org.eclipse.foo.examples.*</tt> - not API; these are examples</li>
-
-<li>
-<tt>org.eclipse.foo.tests.*</tt> - not API; these are test suites</li>
-</ul>
-<ul>
-<li>
-<b>API class or interface</b> - a <tt>public</tt> class or interface in
-an API package, or a <tt>public</tt> or <tt>protected</tt> class or interface
-member declared in, or inherited by, some other API class or interface.
-The names of API classes and interfaces may legitimately appear in client
-code.</li>
-
-<li>
-<b>API method or constructor</b> - a <tt>public</tt> or <tt>protected</tt>
-method or constructor either declared in, or inherited by, an API class
-or interface. The names of API methods may legitimately appear in client
-code.</li>
-
-<li>
-<b>API field</b> - a <tt>public</tt> or <tt>protected</tt> field either
-declared in, or inherited by, an API class or interface. The names of API
-fields may legitimately appear in client code.</li>
-</ul>
-Everything else is considered internal implementation detail and off limits
-to all clients. Legitimate client code must never reference the names of
-non-API elements (not even using Java reflection). In some cases, the Java
-language's name accessibility rules are used to disallow illegal references.
-However, there are many cases where this is simply not possible. Observing
-this one simple rule avoids the problem completely:
-<ul>
-<li>
-<b>Stick to officially documented APIs. </b>Only reference packages that
-are documented in the <b><i>published API Javadoc</i></b> for the component.
-Never reference a package belonging to another component that has "internal"
-in its name---these are never API. Never reference a package for which
-there is no published API Javadoc---these are not API either.</li>
-</ul>
-
-<h2>
-General rules</h2>
-The specification of API elements is generated from Javadoc comments in
-the element's Java source code. For some types of elements, the specification
-is in the form of a contract. For example, in the case of methods, the
-contract is between two parties, the caller of the method and the implementor
-of the method. The fundamental ground rule is:
-<ul>
-<li>
-<b>Honor all contracts.</b> The contracts are described in the published
-Javadoc for the API elements you are using.</li>
-</ul>
-The term "must", when used in an API contract, means that it is incumbent
-on the party to ensure that the condition would always be met; any failure
-to do so would be considered a programming error with unspecified (and
-perhaps unpredictable) consequences.
-<ul>
-<li>
-<b>You must honor "must". </b>Pay especially close heed to conditions where
-"must" is used.</li>
-</ul>
-Other common sense rules:
-<ul>
-<li>
-<b>Do not rely on incidental behavior. </b>Incidental behavior is behavior
-observed by experiment or in practice, but which is not guaranteed by any
-API specification.</li>
-
-<li>
-<b>Do not treat null as an object.</b> Null is more the lack of an object.
-Assume everything is non-null unless the API specification says otherwise.</li>
-
-<li>
-<b>Do not try to cheat with Java reflection.</b> Using Java reflection
-to circumvent Java compiler checking buys you nothing more. There are no
-additional API contracts for uses of reflection; reflection simply increases
-the likelihood of relying on unspecified behavior and internal implementation
-detail.</li>
-
-<li>
-<b>Use your own packages. </b>Do not declare code in a package belonging
-to another component. Always declare your own code in your own packages.</li>
-</ul>
-
-<h2>
-Calling public API methods</h2>
-For most clients, the bulk of the Eclipse API takes the form of public
-methods on API interfaces or classes, provided for the client to call when
-appropriate.
-<ul>
-<li>
-<b>Ensure preconditions.</b> Do ensure that an API method's preconditions
-are met before calling the method. Conversely, the caller may safely assume
-that the method's postconditions will have been achieved immediately upon
-return from the call.</li>
-
-<li>
-<b>Null parameters.</b> Do not pass null as a parameter to an API method
-unless the parameter is explicitly documented as allowing null. This is
-perhaps the most frequently made programming error.</li>
-
-<li>
-<b>Restricted callers.</b> Do not call an API method that is documented
-as available only to certain callers unless you're one of them. In some
-situations, methods need to be part of the public API for the benefit of
-a certain class of callers (often internal); calling one of these methods
-at the wrong time has unspecified (and perhaps unpredictable) consequences.</li>
-
-<li>
-<b>Debugging methods.</b> Do not call an API method labelled "for debugging
-purposes only". For example, most <tt>toString()</tt> methods are in this
-category.</li>
-
-<li>
-<b>Parameter capture.</b> Do not pass an array, collection, or other mutable
-object as a parameter to an API method and then modify the object passed
-in. This is just asking for trouble.</li>
-</ul>
-
-<h2>
-Instantiating platform API classes</h2>
-Not all concrete API classes are intended to be instantiated by just anyone.
-API classes have an instantiation contract indicating the terms under which
-instances may be created. The contract may also cover things like residual
-initialization responsibilities (for example, configuring a certain property
-before the instance is fully active) and associated lifecycle responsibilities
-(for example, calling <tt>dispose()</tt> to free up OS resources hung on
-to by the instance). Classes that are designed to be instantiated by clients
-are explicitly flagged in the Javadoc class comment (with words like "Clients
-may instantiate.").
-<ul>
-<li>
-<b>Restricted instantiators.</b> Do not instantiate an API class that is
-documented as available only to certain parties unless you're one of them.
-In some situations, classes need to be part of the public API for the benefit
-of a certain party (often internal); instantiating one of these classes
-incorrectly has unspecified (and perhaps unpredictable) consequences.</li>
-</ul>
-
-<h2>
-Subclassing platform API classes</h2>
-Only a subset of the API classes were designed to be subclassed. API classes
-have a subclass contract indicating the terms under which subclasses may
-be declared. This contract also covers initialization responsibilities
-and lifecycle responsibilities. Classes that are designed to be subclassed
-by clients are explicitly flagged in the Javadoc class comment (with words
-like "Clients may subclass.").
-<ul>
-<li>
-<b>Restricted subclassers.</b> Do not subclass an API class that is not
-intended to be subclassed. Treat these classes as if they had been declared
-final. (These are sometimes referred to as "soft final" classes).</li>
-</ul>
-
-<h2>
-Calling protected API methods</h2>
-Calling inherited protected and public methods from within a subclass is
-generally allowed; however, this often requires more care to correctly
-call than to call public methods from outside the hierarchy.
-<h2>
-Overriding API methods</h2>
-Only a subset of the public and protected API methods were designed to
-be overridden. Each API method has a subclass contract indicating the terms
-under which a subclass may override it. By default, overriding is not permitted.
-It is important to check the subclass contract on the actual method implementation
-being overridden; the terms of subclass contracts are not automatically
-passed along when that method is overridden.
-<ul>
-<li>
-<b>Do not override a public or protected API method unless it is explicitly
-allowed.</b> Unless otherwise indicated, treat all methods as if they had
-been declared final. (These are sometimes known as "soft final" methods).
-If the kind of overriding allowed is:
-
-<ul>
-<li>"<b>implement</b>" - the abstract method declared on the subclass must
-be implemented by a concrete subclass</li>
-<li>"<b>extend</b>" - the method declared on the subclass must invoke the
-method on the superclass (exactly once)</li>
-<li>"<b>re-implement</b>" - the method declared on the subclass must not
-invoke the method on the superclass</li>
-<li>"<b>override</b>" - the method declared on the subclass is free to
-invoke the method on the superclass as it sees fit</li></ul></li>
-
-<li>
-<b>Ensure postconditions. </b>Do ensure that any postconditions specified
-for the API method are met by the implementation upon return.</li>
-
-<li>
-<b>Proactively check preconditions. </b>Do not presume that preconditions
-specified for the API method have necessarily been met upon entry. Although
-the method implementation would be within its rights to not check specified
-preconditions, it is usually a good idea to check preconditions (when feasible
-and reasonably inexpensive) in order to blow the whistle on misbehaving
-callers.</li>
-
-<li>
-<b>Null result. </b>Do not return null as a result from an API method unless
-the result is explicitly documented (on the specifying interface or superclass)
-as allowing null.</li>
-
-<li>
-<b>Return copies. </b>Do not return an irreplaceable array, collection,
-or other mutable object as the result from an API method. Always return
-a copy to avoid trouble from callers that might modify the object.</li>
-</ul>
-
-<h2>
-Implementing platform API interfaces</h2>
-Only a subset of the API interfaces were designed to be implemented by
-clients. API interfaces have a contract indicating the terms under which
-it may be implemented. Interfaces that are designed to be implemented by
-clients are explicitly flagged in the Javadoc class comment (with words
-like "Clients may implement."). A client may declare a subinterface of
-an API interface if and only if they are allowed to implement it.
-<ul>
-<li>
-<b>Restricted implementors.</b> Do not implement an API interface that
-is documented as available only to certain parties unless you're one of
-them. In many situations, interfaces are used to hide internal implementation
-details from view.</li>
-</ul>
-
-<h2>
-Implementing public API methods</h2>
-See "Overriding API methods".
-<h2>
-Accessing fields in API classes and interfaces</h2>
-<p>Clients may read API fields, most of which are final. Certain struct-like
-objects may have non-final public fields, which clients may read and write
-unless otherwise indicated.</p>
-<ul>
-<li>
-<b>Null fields.</b> Do not set an API field to null unless this is explicitly
-allowed.</li>
-</ul>
-
-<h2>
-Casting objects of a known API type</h2>
-<p>
-An object of a known API type may only be cast to a different API type
-(or conditionally cast using instanceof) if this is explicitly allowed
-in the API.
-</p>
-<ul>
-<li>
-<b>Cast and instanceof.</b> Do not use instanceof and cast expressions
-to increase what is known about an object beyond what the API supports.
-Improper use exposes incidental implementation details not guaranteed by
-the API.</li>
-</ul>
-<p>
-And, of course, casting any object to a non-API class or interface is always
-inappropriate.
-</p>
-<h2>
-Not following the rules</h2>
-<p>Whether done knowingly or unwittingly, there are consequences for transgressing
-the rules. It might be easier for all involved if there were API police
-that would bust you for breaking the rules. However, that is not the case.
-For the most part, API conformance operates as an honor system, with each
-client responsible for knowing the rules and adhering to them.</p>
-<p>The contracts on the API elements delimit the behavior that is supported
-and sustained. As the Eclipse platform matures and evolves, it will be
-the API contracts that guide how this evolution happens. Outside of these
-contracts, everything is unsupported and subject to change, without notice,
-and at any time (even mid-release or between different OS platforms). Client
-code that oversteps the above rules might fail on different versions and
-patch levels of the platform; or when run on different underlying OSes;
-or when run with a different mix of co-resident plug-ins; or when run with
-a different workbench perspective; and so on. Indeed, no one is even particularly
-interested in speculating exactly how any particular transgression might
-come back to bite you. To those who choose to ignore the rules, don't say
-that you weren't warned. And don't expect much more than a sympathetic
-"Told you so."</p>
-<p>On the other hand, client plug-in code that lives by the above rules
-should continue to work across different versions and patch levels of the
-platform, across different underlying OSes, and should peacefully co-exist
-with other plug-ins. If everyone plays by the rules, the Eclipse platform
-will provide a stable and supported base on which to build exciting new
-products.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html
deleted file mode 100644
index 8284148..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.html
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Supporting bidirectional text</title>
-</head>
-<BODY BGCOLOR="#ffffff">
-<h1>Supporting bidirectional text</h1>
-<p>A bidirectional language is one that can write either right to left or left to 
-right based on context. Bidirectional text is supported throughout the platform.
-Eclipse will recognize Hebrew, Arabic, Farsi and Urdu as bidirectional by default.</p>
-<h2>Enabling Bidirectional Support</h2>
-<p>The orientation of the workbench is determined in one of the following ways 
-  (in order of priority):</p>
-<ul>
-  <li><strong>-dir command line parameter</strong>. If the -dir command line option 
-    is used this will be the default orientation. Valid values are -dir rtl or -dir ltr.</li>
-  <li><strong>system properties</strong>. If the system property <tt>eclipse.orientation</tt> 
-    is set this will be used. The recognized values of this property are the same as
-    the -dir command line argument.</li>
-  <li><strong>-nl command line parameter</strong>. If the -nl option is used and 
-    the language is Hebrew, Arabic, Farsi or Urdu the orientation will be right 
-    to left.</li>
-  <li>Failing all of the above, the platform defaults to a left to right orientation.</li>
-</ul>
-<p>
-In JFace, the orientation can be determined by calling 
-<b>org.eclipse.jface.Window#getDefaultOrientation()</b>.  Standalone JFace
-applications must set the default orientation by calling 
-<b>org.eclipse.jface.Window#setDefaultOrientation()</b>, otherwise it
-will assume a default value of <b>SWT.NONE</b>. The default orientation is 
-set automatically when running the Workbench.  All subclasses of <tt>org.eclipse.jface.Window</tt>
-inherit this default orientation.</p>
-<p>Views and editors inherit the window orientation from their 
-  parent. Dialogs should inherit orientation by using the shell style of their 
-  superclass by calling <b>super.getShellStyle()</b> when creating or configuring their shell.</p>
-<p><img src="bidi.png" alt="bidi image"></p>
-<p><strong>Figure 1 - Screen shot of right to left orientation of the resource 
-  perspective in English</strong></p>
-<h2>Enabling Text Processing</h2>
-<p>The orientation of the workbench is independant of the special case processing 
-  for bidirectional languages. If the language of the current Locale is Hebrew, 
-  Arabic, Farsi or Urdu text processing will be enabled. Text processing is used 
-  to handle special case characters that should not be processed as birdirectional 
-  text such as path seperators. See <code>org.eclipse.osgi.util.TextProcessor</code> 
-  for more details. </p>
-<h2>Enabling your plug-in for looking up alternate icons</h2>
-<p>In many cases your icons will not make any sense in right to left mode. In 
-  particular any icon to do with editing will have this issue.To enable lookup 
-  of images in a fragment, use $nl$ in your icon path and use
-  the <b>org.eclipse.core.runtime.FileLocator</b> class to find icons at runtime.
-</p>
-<p>For example</p>
-<pre>
-   String iconPath = &quot;$nl$/icons/myicon.gif&quot;;
-   URL url = FileLocator.find( Platform.getBundle(MyPluginId), new Path(iconPath), null);
-   Image Descriptor descriptor = ImageDescriptor.createFromURL(url);
-</pre>
-<p>
-  If the icon reference is in your <tt>plugin.xml</tt> file, make sure you have the $nl$ 
-  prefix on your path and the lookup will be handled for you. If you define your
-  own extension points that involve icons, be sure to load images in the same way.
-</p>
-<h3>How to choose icons to override</h3>
-<p>There are no hard and fast rules for determining what icons need to be overridden
-in a right to left language.  In general, focus on icons that imply a textual direction with a 
-horizontal arrow.</p>
-
-</BODY></HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png b/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png
deleted file mode 100644
index d86004c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/bidi.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html
deleted file mode 100644
index 481645c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/buddy_loading.html
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Third party libraries and classloading</title>
-</head>
-<body>
-<h1>Third party libraries and classloading</h1>
-Because OSGi makes use of multiple classloaders, the transparent usage of extensible / configurable third party libraries 
-in eclipse requires the usage of an eclipse specific mechanism called "buddy loading". This mechanism allows a 
-bundle to indicate that it needs assistance to load classes or resources when it can not find them 
-among its prerequisites. Note that we call "extensible libraries", libraries that needs to see classes or resources provided
-by user code (for example log4j logger mechanism, hibernate,...).
-<p>
-To indicate its need for buddy loading, a bundle must modify its manifest and add the following header:</p>
-<pre>    Eclipse-BuddyPolicy: &lt;value&gt;
-</pre>
-<p>
-&lt;value&gt; refers to the policy used to look for the classes. Here are the
-supported policies:</p>
-<ul>
-  <li> registered -  indicates that the buddy mechanism will consult bundles
-that have been registered to it. Bundle willing to be registered to a particular
-  bundle add in their manifest: "Eclipse-RegisterBuddy: &lt;bundleSymbolicName&gt;";</li>
-  <li> dependent - indicates that the classes/resources will be looked up
-transitively in all the dependent of the bundle;</li>
-  <li> global - indicates that the classes/resources will be looked up in the
-global pool of exported package;</li>
-  <li> app - indicates that the application classloader will be consulted;</li>
-  <li> ext - indicates that the extensiont classloader will be consulted;</li>
-  <li> boot - indicates that the boot classloader will be consulted.</li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
deleted file mode 100644
index 94fd391..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/bundle_manifest.html
+++ /dev/null

@@ -1,455 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2005, 2008. This page is made available under license. Full for details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>OSGi Bundle Manifest</title>
-</head>
-
-<body lang="EN-US" link=blue vlink=blue style='tab-interval:.5in'>
-
-<div class=Section1>
-
-<h1>OSGi Bundle Manifest Headers</h1>
-
-<p class=MsoNormal><span style='font-size:10.0pt'>Version 3.3 - Last revised May 5, 2008</span></p>
-
-<p>
-A bundle can carry descriptive information about itself in the manifest file 
-named META-INF/MANIFEST.MF.  The OSGi R4.1 Framework specification defines a set of 
-manifest headers such as Export-Package and Bundle-Classpath, which bundle developers 
-use to supply descriptive information about a bundle.  The Eclipse OSGi Framework 
-implements the complete OSGi R4.1 Framework specification and all of the Core Framework 
-services. The OSGi R4.1 Core Framework services include the following:</p>
-<ul>
-  <li>Package Admin Service Specification</li>
-  <li>URL Handlers Service Specification</li>
-  <li>Start Level Service Specification</li>
-  <li>Conditional Permission Admin Specification</li>
-  <li>Permission Admin Service Specification</li>
-</ul>
-  <p> There are a number of optional services defined in the OSGi R4.1 specification. 
-    The optional services are not included with the Eclipse OSGi Framework implementation. 
-    For information on OSGi R4.1 manifest headers and services refer to the <a href="http://www.osgi.org/Download/Release4V41">OSGi 
-    specifications</a>. </p>
-
-<h2>Eclipse Bundle Manifest Headers</h2>
-
-<p>
-The Eclipse OSGi Framework supports a number of additional bundle manifest headers 
-and directives.  A bundle developer may use these additional headers and directives 
-to take advantage of some additional features of the Eclipse OSGi Framework which 
-are not specified as part of a standard OSGi R4 Framework.
-</p>
-<h3>Additional Export-Package Directives</h3>
-
-<p>
-The Eclipse OSGi Framework supports additional directives on the Export-Package 
-header.  These directives are used to specify the access restriction rules of an 
-exported package.  See <a href="runtime-options.html#osgiresolvermode">osgi.resolverMode</a> 
-to configure the Eclipse OSGi Framework to enforce the access restriction rules at 
-runtime.
-</p>
-
-<h4>The x-internal Directive</h4>
-
-<p>
-The x-internal directive can be used in an Export-Package header to specify whether 
-the package is an internal package.  The Plug-in Development Environment will discourage 
-other bundles from using an internal package.  If the x-internal directive is not 
-specified then a default value of 'false' is used.  The x-internal directive must 
-use the following syntax:
-</p>
-
-<pre>
-x-internal ::= ( 'true' | 'false' )
-</pre>
-
-<p>
-The following is an example of the x-internal directive:
-</p>
-
-<pre>
-Export-Package: org.eclipse.foo.internal; x-internal:=true
-</pre>
-
-<h4>The x-friends Directive</h4>
-
-<p>
-The x-friends directive can be used in an Export-Package header to specify a list 
-of bundles which are allowed access to the package.  The Plug-in Development 
-Environment will discourage other bundles from using the package.  The x-friends 
-directive must use the following syntax:
-</p>
-
-<pre>
-x-friends ::= '&quot;' ( target-bundle ) ( ',' target-bundle ) * '&quot;'
-target-bundle ::= a bundle symbolic name
-</pre>
-
-<p>
-The following is an example of the x-friends directive:
-</p>
-
-<pre>
-Export-Package: org.eclipse.foo.formyfriends; x-friends:=&quot;org.eclipse.foo.friend1, org.eclipse.foo.friend2&quot;
-</pre>
-
-<p>
-The example specifies that only the bundles org.eclipse.foo.friend1 and 
-org.eclipse.foo.friend2 should be encouraged to use the org.eclipse.foo.formyfriends 
-package.  The x-internal package takes priority over the x-friends directive.  If 
-the x-internal directive specifies 'true' then The Plug-in Development 
-Environment will discourage all bundles from using the package even if they are
-specified as a friend.
-</p>
-
-<h3>The Eclipse-LazyStart Header</h3>
-
-<p>
-The Eclipse-LazyStart header is used to specify if a bundle should be started 
-before the first class or resource is accessed from that bundle. 
-This feature allows Eclipse to activate bundles lazily the first time they are
-needed.  Using this model Eclipse can startup with as few active bundles as 
-possible.  The Eclipse-LazyStart header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-LazyStart ::= ( 'true' | 'false' ) ( ';' 'exceptions' '=' '&quot;' exceptions-list '&quot;' ) ?
-exceptions-list ::= a comma ',' separated list of packages
-</pre>
-
-<p>
-When Eclipse-LazyStart is true, the 'exceptions' attribute specifies a list of
-packages that <b>will not</b> cause the bundle to be activated when classes are
-loaded from them. 
-When Eclipse-LazyStart is false, the 'exceptions' attribute specifies a list of
-packages that <b>will</b> cause the bundle to be activated when classes are
-loaded from them.
-The exception rules apply to all classes in the listed packages.  When a bundle 
-is activated the bundle's BundleActivator.start(BundleContext) method will be
-called.
-</p>
-<p>  
-If the Eclipse-LazyStart header is not defined in the bundle manifest then a default 
-value of 'false' is used.  The following is an example of the Eclipse-LazyStart header:
-</p>
-
-<pre>
-Eclipse-LazyStart: true; exceptions=&quot;org.eclipse.foo1, org.eclipse.foo2&quot;
-</pre>
-
-<p>
-The example specifies that this bundle must be activated for any classes 
-that are loaded from this bundle, except the classes in the packages
-'org.eclipse.foo1' and 'org.eclipse.foo2'.
-</p>
-
-<p>
-The Eclipse-AutoStart and Eclipse-LazyStart headers have been deprecated in Eclipse 3.4.
-As of the OSGi R4.1 specification the lazy activation policy has been adopted by the OSGi 
-specification.  The new OSGi bundle manifest header Bundle-ActivationPolicy can be used to 
-specify a lazy activation policy.
-</p>
-
-<p>
-The Equinox Framework version 3.4 or later will continue to support the deprecated  Eclipse-LazyStart and 
-Eclipse-AutoStart headers. Bundle developers that want their bundles to work across other OSGi 
-Framework implementations should add the Bundle-ActivationPolicy header to their manifest. In most cases you can simply add the following header: 
-</p>
-
-<pre>
-Bundle-ActivationPolicy: lazy
-</pre>
-
-<p>
-If the 'exceptions' attribute is used with the Eclipse-LazyStart or Eclipse-AutoStart header then the 'include' or 'exclude' directive can be used 
-with the Bundle-ActivationPolicy header.  Consider the following Eclipse-LazyStart header:
-</p>
-
-<pre>
-Eclipse-LazyStart: true; exceptions=&quot;org.eclipse.foo1, org.eclipse.foo2&quot;
-</pre>
-
-<p>
-The equivalent Bundle-ActivationPolicy header would be the following:
-</p>
-
-<pre>
-Bundle-ActivationPolicy: lazy; exclude:=&quot;org.eclipse.foo1, org.eclipse.foo2&quot;
-</pre>
-
-<p>
-The following is an example Eclipse-LazyStart header that uses a false value with the exceptions attribute:
-</p>
-
-<pre>
-Eclipse-LazyStart: false; exceptions=&quot;org.eclipse.foo1, org.eclipse.foo2&quot;
-</pre>
-
-<p>
-The equivalent Bundle-ActivationPolicy header would be the following:
-</p>
-
-<pre>
-Bundle-ActivationPolicy: lazy; include:=&quot;org.eclipse.foo1, org.eclipse.foo2&quot;
-</pre>
-
-<h3>The Eclipse-PlatformFilter Header</h3>
-
-<p>
-The Eclipse-PlatformFilter is used to specify a platform filter for a bundle.  A platform
-filter must evaluate to true in a running platform in order for a bundle to be allowed
-to resolve.  The Eclipse-PlatformFilter header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-PlatformFilter ::= a valid LDAP filter string
-</pre>
-
-<p>
-The Framework supports filtering on the following system properties:
-</p>
-
-<ul type=disc>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.nl</b> - the platform 
-     language setting.</li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.os</b> - the platform 
-     operating system.</li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.arch</b> - the platform 
-     architecture.</li>
- <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
-     mso-list:l2 level1 lfo3;tab-stops:list .5in'><b>osgi.ws</b> - the platform 
-     windowing system.</li>
-</ul>
-
-<p>
-The following is an example of the Eclipse-PlatformFilter header:
-</p>
-
-<pre>
-Eclipse-PlatformFilter: (&amp; (osgi.ws=win32) (osgi.os=win32) (osgi.arch=x86))
-</pre>
-
-<p>
-This example specifies that this bundle can only be resolved if the platform 
-properties are osgi.ws=win32 and osgi.os=win32 and osgi.arch=x86.  In other words 
-a platform running on an x86 architecture, using a win32 operating system and 
-the win32 windowing system.
-</p>
-
-<h3>The Eclipse-BuddyPolicy Header</h3>
-
-<p>
-The Eclipse-BuddyPolicy header is used to specify the buddy classloading policies for a bundle.
-The Eclipse-BuddyPolicy header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-BuddyPolicy ::= ( policy-name ) ( ',' policy-name ) *
-policy-name ::= ( 'dependent' | 'global' | 'registered' | 
-                  'app' | 'ext' | 'boot' | 'parent' )
-</pre>
-
-<p>
-The following is an example of the Eclipse-BuddyPolicy header:
-</p>
-
-<pre>
-Eclipse-BuddyPolicy: dependent
-</pre>
-
-<h3>The Eclipse-RegisterBuddy Header</h3>
-
-<p>
-The Eclipse-RegisterBuddy header is used to specify a list of bundles for which this bundle is 
-a registered buddy.  The Eclipse-RegisterBuddy header must use the following syntax:
-</p>
-
-<pre>
-Eclipse-RegisterBuddy ::= ( target-bundle ) ( ',' target-bundle ) *
-target-bundle ::= a bundle symbolic name
-</pre>
-
-<p>
-The following is an example of the Eclipse-RegisterBuddy header:
-</p>
-
-<pre>
-Eclipse-RegisterBuddy: org.eclipse.foo.bundle1, org.eclipse.foo.bundle2
-</pre>
-
-<h3>The Eclipse-ExtensibleAPI Header</h3>
-
-<p>
-The Eclipse-ExtensibleAPI is used to specify whether a host bundle allows fragment bundles 
-to add additional API to the host.  This header should be used if a host bundle wants to allow 
-fragments to add additional packages to the API of the host.  If this header is not 
-specified then a default value of 'false' is used.  Note that this header is only used by tooling
-(PDE) to construct proper class paths for building. <b>The runtime does not use this header 
-at all.</b>  At runtime a fragment is always allowed to add additional packages, classes and 
-resources to the API of the host.  The Eclipse-ExtensibleAPI header must use the following 
-syntax:
-</p>
-
-<pre>
-Eclipse-ExtensibleAPI ::= ( 'true' | 'false' )
-</pre>
-
-<p>
-The following is an example of the Eclipse-ExtensibleAPI header:
-</p>
-
-<pre>
-Eclipse-ExtensibleAPI: true
-</pre>
-
-<h3>The Eclipse-BundleShape Header</h3>
-
-<p>
-The Eclipse-BundleShape header is used to specify the deployment shape a bundle should use when 
-the bundle is provisioned to an Eclipse installation. 
-<b>The runtime does not use this header at all.</b>  This header is only used by the build and 
-provisioning systems to determine how to deploy a bundle.  The Eclipse-BundleShape header must 
-use the following syntax:
-</p>
-
-<pre>
-Eclipse-BundleShape ::= ( 'jar' | 'dir' )
-</pre>
-
-<p>
-The &quot;jar&quot; value indicates that the bundle should be deployed as a jar.  The &quot;dir&quot;
-value indicates that the bundle should be unpacked into a directory when deployed to an Eclipse installation.
-</p>
-
-<p>
-If a product uses PDE to build a feature based product then, if specified, the value of the unpack attribute in the feature.xml file 
-takes precedence over the Eclipse-BundleShape header.
-</p>
-
-<p>
-The following is an example of the Eclipse-BundleShape header:
-</p>
-
-<pre>
-Eclipse-BundleShape: jar
-</pre>
-
-<h3>The Eclipse-GenericCapability Header</h3>
-
-<p>
-The Eclipse-GenericCapability header is used to specify a generic capability 
-of a bundle.  Generic capabilities can be used to describe features of your 
-bundle which can be required by other bundles in the system (using the 
-Eclipse-GenericRequire header).  Generic capabilities are given a name 
-and a capability type.  Capability types are defined by the bundle which is 
-offering the capability.  Capabilities can also have a set of typed matching
-attributes which are used to match against when resolving Eclipse-GenericRequire 
-headers.  Matching attributes may be one of the following types; 
-[string | version | uri | long | double | set].  The set type can be used 
-to define a set of strings as a comma separated list of strings.
-
-The Eclipse-GenericCapability header must use the following syntax:
-</p>
-
-<pre>
-  Eclipse-GenericCapability ::= capability ( ',' capability ) *
-  capability                ::= typed-name ( ';' typed-name ) * 
-                                ( ';' typed-param ) *
-  typed-name                ::= name ( ':' capability-type )
-  typed-param               ::= typed-key '=' quouted-string
-  typed-key                 ::= name ( ':' 
-                                [string | version | uri | long | double | set] )</pre>
-
-<p>
-The following is an example of the Eclipse-GenericCapability header that could be used
-to specify a bundle with an OSGi service org.acme.stuff.SomeService implementation:
-</p>
-
-<pre>
-  Eclipse-GenericCapability: 
-   org.acme.stuff.SomeService:osgi.service; 
-   version:version=&quot;1.0.1&quot;</pre>
-
-<h3>The Eclipse-GenericRequire Header</h3>
-
-<p>
-The Eclipse-GenericRequire header is used to specify a requirement on ageneric 
-capability which is offered by another bundle (using the Eclipse-GenericCapability
-header).  Generic requirements are given a name and a capability type.  Capability 
-types are defined by the bundle which is offering the capability.  Generic 
-requirements can specify an LDAP filter string which is used as a selection filter
-to resolve against matching generic capabilities.
-
-The Eclipse-GenericRequire header must use the following syntax:
-</p>
-
-<pre>
-  Eclipse-GenericRequire   ::= generic-require ( ',' generic-require ) *
-  generic-require          ::= typed-name ( ';' typed-name ) *
-                               ( ';' selection-filter '=' quoated-ldapFilter )
-                               ( ';' optional '=' [true|false] )
-                               ( ';' multiple '=' [true|false] )
-  typed-name                ::= name ( ':' capability-type )</pre>
-
-<p>
-The following is an example of the Eclipse-GenericRequire header that could be used
-to specify a bundle that depends on an OSGi service org.acme.stuff.SomeService 
-implementation:
-</p>
-
-<pre>
-  Eclipse-GenericRequire: 
-   org.acme.stuff.SomeService:osgi.service; 
-   selection-filter=&quot;(version&gt;=1.0.1)&quot;</pre>
-
-<h3>Generic Aliases</h3>
-<p>
-The <a href="runtime-options.html#osgigenericAliases">osgi.genericAliases</a> option 
-can be used to map existing OSGi manifest headers onto Eclipse-GenericCapability and
-Eclipse-GenericRequire manifest headers.  For example, consider the following manifest 
-headers
-</p>
-<pre>
-  Export-Service: org.acme.stuff.SomeService
-  Import-Service: org.acme.stuff.SomeService</pre>
-
-<p>
-These headers can be mapped to Eclipse-GenericCapability and Eclipse-GenericRequire 
-headers using the following property:
-</p>
-<pre>  osgi.genericAliases=Export-Service:Import-Service:osgi.service</pre>
-<p>
-Under the covers this would translate into the following generic headers:
-</p>
-<pre>
-  Eclipse-GenericRequire: org.acme.stuff.SomeService:osgi.service
-  Eclipse-GenericCapability: org.acme.stuff.SomeService:osgi.service
-</pre>
-
-<h3>The Plugin-Class Header</h3>
-
-<p>
-The Plugin-Class header is only used to support plugins developed for the Eclipse 2.1 
-platform.  This header is used to specify a class name that will be used to activate 
-a plug-in using the old Eclipse 2.1 activation model.  New bundles developed for
-Eclipse 3.0 or greater should not use this header.
-The following is an example of the Plugin-Class header:
-</p>
-
-<pre>
-Plugin-Class: org.eclipse.foo.FooPlugin
-</pre>
-
-</div>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html
deleted file mode 100644
index a71d222..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipse-install.html
+++ /dev/null

@@ -1,523 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>How to write an Eclipse installer</title>
-</head>
-
-<body>
-
-<h1>How to write an Eclipse installer</h1>
-<p>Last modified 15:20 Friday June 18, 2004</p>
-<p>Eclipse-based products need to be correctly installed on the end user's
-computer. Special-purpose packaging tools, such as <a href="http://www.installshield.com/">InstallShield</a>
-and <a href="http://www.rpm.org/">RPM</a>, are often used to build executable
-installers that automate installing, updating, and uninstalling. This note
-describes how to write an installer for an Eclipse-based product, and for
-separately-installable extensions to Eclipse-based products.</p>
-<p>We assume that a product development team is responsible for providing the
-raw ingredients that will need to find their way to end users' computers
-packaged as an executable installer. The creation of executable installers is
-scripted, as are the install time actions needed to interact with the end user
-and deposit files on their computer. This note described in detail what these
-installers need to do and how they should work.&nbsp;</p>
-<p>This note should be treated as a recipe for the person responsible for
-writing an installer for an Eclipse-based products. Two good reasons why we
-recommend all installers writers follow our recipe:</p>
-<ul>
-  <li><b>Product and extension interoperability.</b> By behaving in standard
-    ways, an installer for one Eclipse-based product or extension automatically
-    works with products and extensions laid down by other installers. Otherwise
-    the idiosyncrasies of one product's installer would require matching quirks
-    in all extension installers that expected to work with that product.</li>
-  <li><b>Uniformity of install time user interaction.</b> All installers for
-    Eclipse-based products and extension should interact with the user in the
-    same manner. There is nothing to having gratuitous variety in this matter.</li>
-</ul>
-
-<h2>Product installer creation script</h2>
-
-<p>A product installer should be self-contained - the kind of thing that could
-be distributed on a CD and installed on any machine with a suitable operating
-system.</p>
-<p>Eclipse requires a Java2 Java Runtime Environment (JRE) to run Java code.
-JREs are licensed software, obtained from Java vendors. With a license to
-redistribute a JRE from a JRE vendor, a company can include a JRE with its
-product, and install it on the end user's computer at the same time as the
-product. The alternative is to require that a JRE be pre-installed on the end
-user's computer, and associated with at product install time. One way or the
-other, an Eclipse-based product requires a suitable JRE, and the product
-installer must play a role in either installing a JRE or locating and linking to
-a pre-existing JRE.&nbsp;</p>
-<p>Assume that a JRE is to be installed with the product. A directory containing
-the JRE is one input to the installer creation script. Denote this directory
-&lt;<i>JRE</i>&gt;. This directory must have a standard JRE directory structure,
-with the Java executable is located at <code>jre/bin/java.exe</code> and the class
-library at <code>jre/lib/rt.jar</code> below the &lt;<i>JRE</i>&gt; directory.
-For reference, the skeletal structure of this directory looks like:</p>
-<p><code>&lt;<i>JRE</i>&gt;/<br>
-&nbsp; jre/<br>
-&nbsp;&nbsp;&nbsp; bin/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; java.exe<br>
-&nbsp;&nbsp;&nbsp; lib/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rt.jar
-</code></p>
-<p>There are additional files (and subdirectories) in these directories; we've
-only shown a sample to give the general structure. Italicized names in italics
-are product-specific.</p>
-<p>The second input to the installer creation script is a directory, &lt;<code><i>product
-head</i></code>&gt;,
-containing the product-specific executable launcher and any files unrelated to
-Eclipse. For reference, the skeletal
-structure of this directory would look like (italics indicate file names that
-will vary from product to product):</p>
-<p><code>&lt;<i>product head</i>&gt;/<br>
-<i>&nbsp; acmeproduct.exe<br>
-</i>
-<br>
-</code>The third input to the installer creation script is a directory, &lt;<code><i>product
-body</i></code>&gt;,
-containing the features and plug-ins developed for the product. For reference, the skeletal
-structure of this directory would look like:</p>
-<p><code>&lt;<i>product body</i>&gt;/<br>
-&nbsp; eclipse/<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.acmefeature</i>_<i>1.0.0</i>/<br>
-&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.otherfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature.xml<br>
-&nbsp;&nbsp;&nbsp; plugins/<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.acmefeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.properties<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.mappings<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin_customization.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; splash.bmp<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.otherfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.properties<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.mappings<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.myplugin</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>myplugin</i>.jar<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.acme.otherplugin</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>otherplugin</i>.jar
-</code></p>
-<p>The fourth input to the installer creation script is a directory, &lt;<code><i>platform</i></code>&gt;,
-containing the features and plug-ins for the Eclipse platform itself and any third-party tools being included.
-This directory also includes the standard Eclipse executable launcher, <code>eclipse.exe</code>,
-(named <code>eclipse</code> on Unix operating environment), and any other Eclipse platform files
-required to be at the root of the install. For reference, the skeletal
-structure of this directory would look like:</p>
-<p><code>
-&lt;<i>platform</i>&gt;<br>
-&nbsp; eclipse/<br>
-&nbsp; &nbsp; eclipse.exe<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.platform_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.platform.win32_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.jdt_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.pde_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; plugins/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.equinox.launcher_1.0.0.v20070530.jar<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.equinox.launcher.win32.win32.x86_1.0.0.v20070523/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.platform_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.core.runtime_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.core.boot_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.core.resources_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.ui_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.jdt_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.jdt.core_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.jdt.ui_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; org.eclipse.pde_2.0.0/<br>
-&nbsp;&nbsp;&nbsp; &nbsp; org.eclipse.pde.core_2.0.0/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; org.eclipse.pde.ui_2.0.0/<br>
-&nbsp; &nbsp;&nbsp;&nbsp; (more org.eclipse.* plug-in directories)<br>
-<br>
-</code>The exact contents of the &lt;<i><code>JRE</code></i>&gt;, &lt;<i><code>product
-head</code></i>&gt;, &lt;<i><code>product body</code></i>&gt;,
-and &lt;<code><i>platform</i></code>&gt; input directories determine what files
-will eventually be installed on the end user's computer.</p>
-<p>The final inputs to the installer creation script are the id and version
-strings for the product's primary feature; e.g., &quot;<code><i>com.example.acme.acmefeature&quot;</i></code>,
-and &quot;<code><i>1.0.0</i></code>&quot;;
-and the name of the product executable; e.g., &quot;<code><i>acmeproduct</i></code><code>.exe</code>&quot;.
-For products that do not require their own product executable, this would be the
-path of the standard Eclipse executable launcher &quot;<code>eclipse/eclipse.exe</code>&quot;.
-These strings have special significance to the installer, appearing in file and
-directory names, and in the contents of marker files created at install time.</p>
-<p>At install time, the installer should behave in the standard manner (further
-details follow the list of steps):</p>
-<ol>
-  <li>warn user to exit all programs</li>
-  <li>introduce the product to be installed</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the product's licensing agreement and ask the user to accept</li>
-  <li>recommend a location on the disk to install the product (but allow user to
-    override this default)</li>
-  <li>check that a product or extension is not already stored at the specified
-    location</li>
-  <li>ask user to confirm all details of the install</li>
-  <li>create marker file to mark root of product install</li>
-  <li>copy files to disk&nbsp; (see below)</li>
-  <li>if appropriate, insert name of registered owner and license key into the &quot;about
-    &quot; description</li>
-  <li>create a desktop shortcut to run the product executable</li>
-  <li>create an appropriate entry to allow the user to uninstall the product</li>
-  <li>launch the product executable with -initialize option to perform all
-    first-time processing</li>
-  <li>offer to show the product release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>If the location specified in step 5 is &lt;<code><i>install</i></code>&gt;,
-the installer copies all the files in the &lt;<i><code>JRE</code></i>&gt;, <code>&lt;<i>platform</i>&gt;, </code> &lt;<i><code>product</code></i>&gt;,&nbsp;
-and <code>&lt;<i>product plug-ins</i>&gt;</code> directories into &lt;<code><i>install</i></code>&gt;.</p>
-<table border="1" width="50%">
-  <tr>
-    <td width="50%">Input file</td>
-    <td width="50%">Installed file</td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>JRE</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/eclipse/*</code></td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>product head</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>product body</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>platform</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-</table>
-<p>The marker file created in step 8 is <code>&lt;<i>install</i>&gt;/eclipse/.eclipseproduct</code>
- is used to mark a directory into which an Eclipse-based product has been
-installed, primarily for extension installers to locate. This marker file is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with &quot;\&quot; escaping) and
-contains the following information that identifies the product to the user and distinguishes
-one Eclipse-based product from one another:</p>
-<blockquote>
-<p><code>name=<i>Acme Visual Tools Pro</i><br>
-id=<i>com.example.acme.acmefeature<br>
-</i>version=<i>1.0.0</i></code></p>
-</blockquote>
-<p>The values of the &quot;id&quot; and &quot;version&quot; property are inputs
-to the installer creation script; the name of the product is presumably known
-and hard-wired. (Products would not ordinarily access this marker file; only
-product and extension installers write or read it.)</p>
-<p>Step 6 requires checking for an existing <code>&lt;<i>install</i>&gt;/eclipse/.eclipseproduct</code>
-or <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code> file. A
-product cannot be installed in exactly the same place as another product or extension.</p>
-<p>After installing all files, the top-level structure of the install directory
-would contain the following files and subdirectories (and perhaps others):</p>
-<p><code>&lt;<i>install</i>&gt;/<br>
-&nbsp; <i>acmeproduct</i>.exe<br>
-&nbsp; eclipse/<br>
-&nbsp;&nbsp;&nbsp; .eclipseproduct<br>
-&nbsp; &nbsp; eclipse.exe<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp; plugins/<br>
-&nbsp;&nbsp;&nbsp; jre/<br>
-<br>
-</code>If a product installer solicits license information from the user, such as
-the name of the registered owner and the license key, this information should
-make it into the product &quot;about&quot; dialog (step 10).</p>
-<p>This is done by recording the user responses in the &quot;<code>about.mapping</code>&quot;
-file in the primary feature's plug-in. For example, at <code>&lt;<i>install</i>&gt;/plugins/<i>com.example.acme.acmefeature</i>_<i>1.0.0</i>/about.mapping</code>.
-The &quot;<code>about.mapping</code>&quot; file may be pre-existing in the &lt;<i><code>product
-head</code></i>&gt;
-input, or may need to be created by the installer at install time.
-The keys are numbers; the value of the &quot;<i>n</i>&quot; key is substituted
-for the substring &quot;<code>{<i>n</i>}</code>&quot; in the &quot;<code>aboutText</code>&quot; property.
-For example, if a license key was field number 0, an &quot;<code>about.mapping</code>&quot;
-file containing a line like &quot;<code>0=T42-24T-ME4U-U4ME</code>&quot; should
-be created.</p>
-<p>N.B.
-The &quot;<code>about.mapping</code>&quot; file is a&nbsp; <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with "\" escaping).
-When the native character encoding at install time is different from ISO 8859-1,
-the installer is responsible for converting the native character encoding to
-Unicode and for adding &quot;\&quot; escapes where required. Escaping is required
-when the strings contain special characters (such as &quot;\&quot;) or non-Latin characters. For example, field number 1 containing the first 3 letters of the Greek
-alphabet would be written &quot;<code>1=\u03B1\u03B2\u03B3</code>&quot;.</p>
-<p>At step 12, the product installer launches the product executable,<code>&nbsp;&lt;<i>install</i>&gt;/<i>acmeproduct</i>.exe</code>,
-with the special -initialize option [exact details TBD]. This causes the Eclipse platform to quietly
-perform all time-consuming first-time processing and cache the results, so that
-when the user starts the product it comes up promptly in an open-for-business
-state.</p>
-<h3>Uninstaller behavior</h3>
-<p>At uninstall time, the uninstaller should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially the product being uninstalled</li>
-  <li>ask user to confirm that the product is to be uninstalled</li>
-  <li>remove all installed files from the &lt;<i><code>install</code></i>&gt;
-    directory, and <b>all</b> files in &lt;<i><code>install</code></i>&gt;<code>/eclipse/features</code>
-    and &lt;<i><code>install</code></i>&gt;<code>/eclipse/plugins</code> including ones put there by parties other than
-    this installer (e.g., by the Eclipse update manager)</li>
-  <li>remove desktop shortcut for the product executable</li>
-  <li>remove entry for product uninstaller</li>
-  <li>inform user of any files that were not removed</li>
-</ol>
-<p>When the product is uninstalled, files deposited at
-install time should be deleted, along with updated features and plug-ins created
-by the Eclipse update manager. <b>Important:</b> At uninstall time, there may be
-other directories and files in the <code>&lt;<i>install</i>&gt;</code>
-directory, notably <code>&lt;<i>install</i>&gt;/eclipse/workspace/</code>,
-<code>&lt;<i>install</i>&gt;/eclipse/links/</code>, and <code>&lt;<i>install</i>&gt;/eclipse/configuration/</code>,
-that contain important data
-which must be retained when the product is uninstalled. The user must be able to
-uninstall and reinstall a product at the same location without losing important
-data.</p>
-<h3>Installer behavior when product already installed</h3>
-<p>When the product is already installed on the user's computer, the installer
-should allow a service update or version upgrade to be applied to the installed
-product.</p>
-<p>At install time, the installer should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially the product being updated</li>
-  <li>locate the installed product to be updated, if necessary by searching the
-    disk for an existing product install or by allowing the user to locate it</li>
-  <li> determine where this installer is a compatible update</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the product's updated licensing agreement and ask the user to accept</li>
-  <li>ask user to confirm all details of the update</li>
-  <li>update files to disk&nbsp; (see below)</li>
-  <li>if required, alter the desktop shortcut to run the product executable</li>
-  <li>should add modified or newly added files to the list of ones to be removed at uninstall
-    time (where feasible)</li>
-  <li>offer to show the product release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>In step 2, an installed product can be recognized by the presence of an &quot;<code>eclipse</code>&quot;
-directory immediately containing a file named &quot;<code>.eclipseproduct</code>&quot;.
-The parent of the &quot;<code>eclipse</code>&quot; directory is a product's install
-directory; i.e., <code>&lt;<i>install</i>&gt;/eclipse/.eclipseproduct</code>.
-The information contained within this marker file should be shown to the user for
-confirmation that the correct product is being updated (there may be several
-Eclipse-based product on the user's computer).</p>
-<p>The installer should perform compatibility checks in step 3 by simple pattern
-matching against subdirectories in the <code>&lt;<i>install</i>&gt;/eclipse/features</code>
-directory. For example, the presence of a folder matching &quot;<code><i>com.example.acme.otherfeature</i>_<i>1.0.1</i></code>&quot;
-would ensure that a certain service update had been applied to the installed
-product.</p>
-<p>For step 7, the installer may delete or replace any of the files that it
-originally installed, and add more files. <b>Important:</b> Several files and directories,
-including <code>&lt;<i>install</i>&gt;/eclipse/workspace/</code>, <code>&lt;<i>install</i>&gt;/eclipse/configuration</code>,
-may be co-located with the install and contain important data files
-which need to be retained
-when the product is upgraded.&nbsp;</p>
-<p>In upgrade situations, there is a good chance that most of the files below <code>&lt;<i>install</i>&gt;/eclipse/plugins/</code>
-are the same (likewise for <code>&lt;<i>install</i>&gt;/eclipse/features/</code>).
-There is significant opportunity for optimization in <code>&lt;<i>install</i>&gt;/eclipse/plugins/</code>
-since the sub-directory name, which embeds the plug-in (or fragment) version
-number, changes if and only iff any of the files below it change. In other
-words, there is no need to touch any files in <code>&lt;<i>install</i>&gt;/eclipse/plugins/org.eclipse.ui_2.0.0</code>/
-if this sub-directory should also exist after the upgrade; if any of the plug-in's
-files were to change, the plug-in's version number is revised, causing the files
-for the upgraded plug-in to be installed in a parallel directory <code>&lt;<i>install</i>&gt;/eclipse/plugins/org.eclipse.ui_2.0.1</code>/.&nbsp;</p>
-<h3>Associating a JRE installed elsewhere</h3>
-<p>The JRE is expected to be located at <code>&lt;<i>install</i>&gt;/eclipse/jre/bin/javaw.exe</code>.
-If it is located elsewhere, the absolute path should be specified using the <code>-vm</code>
-option on the command line; e.g.,<code>   -vm C:\j2jre1.3.0\jre\bin\javaw.exe</code>.
-In which case, the installer should add this option to the command line of the desktop shortcut
-it creates.</p>
-<h2>Extension installer creation script</h2>
-
-<p>By extension we mean a separately installable set of features and their plug-ins that
-can be associated with, and used from, one ore more Eclipse-based products installed on the
-same computer. In contrast to a product, an extension is not self-contained; an extension does not include
-a product executable, the Eclipse platform, a JRE.</p>
-<p>Without loss of generality, assume that an extension consists of a single
-feature. The first input to the installer creation script is a directory, &lt;<code><i>extension</i></code>&gt;,
-containing its feature and plug-ins. We are assuming that an extension has no
-files that are related to Eclipse; if it did, they would go in <code>&lt;<i>extension</i>&gt;/</code>,
-and not in <code>&lt;<i>extension</i>&gt;/eclipse/</code>. For reference, the skeletal
-structure of this directory would look like:</p>
-<p><code>&lt;<i>extension</i>&gt;/<br>
-&nbsp; eclipse/<br>
-&nbsp; &nbsp; features/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.anvilfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; feature.xml<br>
-&nbsp; &nbsp; plugins/<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.anvilfeature</i>_<i>1.0.0</i>/<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; plugin.xml<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.ini<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.properties<br>
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about.mappings<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.mainplugin</i>_<i>1.0.0</i>/<br>
-</code>&nbsp; <code>&nbsp;&nbsp;&nbsp;&nbsp; <i>com.example.wiley.otherplugin</i>_<i>1.0.0</i>/
-</code></p>
-<p>The exact contents of the &lt;<i><code>extension</code></i>&gt; input
-directory determines what files
-will eventually be installed on the end user's computer.</p>
-<p>The final inputs to the installer creation script are the id and version
-strings for the extension's feature; e.g., &quot;<i><code>com.example.wiley.anvil</code></i>&quot;
-and &quot;<code><i>1.0.0</i></code>&quot;. These strings have special
-significance to the installer, appearing in file and directory names, and in the
-contents of marker files created at install time.</p>
-<p>An extension installer is similar to a product installer in most respects.
-The areas where it differs are highlighted below:</p>
-<p>At install time, the installer behaves in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs</li>
-  <li>introduce the extension to be installed</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the extension's licensing agreement and ask the user to accept</li>
-  <li>recommend a location on the disk to install the extension (but allow user to
-    override this default)</li>
-  <li>check that a product or a different extension is not already stored at the specified
-    location</li>
-  <li> ask user which product(s) to are to use this extension (search disk;
-    browse; or skip)
-  </li>
-  <li>optionally, determine if extension is compatible with selected products</li>
-  <li>ask user to confirm all details of the install</li>
-  <li>create marker file to mark root of extension install</li>
-  <li>copy files to disk&nbsp; (see below)</li>
-  <li>insert name of registered owner and license key into the &quot;about
-    &quot; description</li>
-  <li>create an appropriate entry to allow the user to uninstall the extension</li>
-  <li>write link file in each of the selected products to associate extension
-    with product</li>
-  <li>offer to show the extension release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>If the location specified in step 5 is &lt;<code><i>install</i></code>&gt;,
-the installer copies all the files in the <code>&lt;<i>extension</i>&gt; </code>directory
-into &lt;<code><i>install</i></code>&gt; in step 11.</p>
-<table border="1" width="50%">
-  <tr>
-    <td width="50%">Input file</td>
-    <td width="50%">Installed file</td>
-  </tr>
-  <tr>
-    <td width="50%"><code>&lt;<i>extension</i>&gt;/*</code></td>
-    <td width="50%"><code>&lt;<i>install</i>&gt;/*</code></td>
-  </tr>
-</table>
-<p>For step 7, any Eclipse product might be a candidate. Eclipse-based product
-can be recognized by the presence of a <code>&lt;<i>product install</i>&gt;/eclipse/.eclipseproduct</code>
-file; the user should be able to request a limited disk search for installed
-products (a &quot;search for installed products&quot; button), or would navigate
-to a directory containing a product (i.e., a &quot;browse&quot; button).</p>
-<p>The installer should perform compatibility checks in step 8 by simple pattern
-matching against subdirectories in the <code>&lt;<i>product install</i>&gt;/eclipse/features</code>
-directory. For example, the presence of a folder matching &quot;<code>org.eclipse.jdt_2.*</code>&quot;
-means that JDT is included in the installed product.&nbsp;</p>
-<p>The marker file created in step 10 is <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code>
- is used to mark a directory into which an Eclipse-based extension has been
-installed, primarily for extension installers to locate
-(analogous to a product's <code>.eclipseproduct</code> marker file). This
-marker file is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with &quot;\&quot; escaping) and
-contains the following information that identifies the extension to the user and distinguishes
-one Eclipse-based extension from one another:</p>
-<blockquote>
-<p><code>name=<i>Wiley Anvil Enterprise Edition</i><br>
-id=<i>com.example.wiley.anvilfeature<br>
-</i>version=<i>1.0.0</i></code></p>
-</blockquote>
-<p>The values of the &quot;id&quot; and &quot;version&quot; property are inputs
-to the installer creation script; the name of the extension is presumably known
-and hard-wired. (Products would not ordinarily access this marker file; only
-product and extension installers write or read it.)</p>
-<p>After installing all files, the top-level structure of the install directory
-would contain the following files and subdirectories:</p>
-<p><code>&lt;<i>install</i>&gt;/<br>
-&nbsp; eclipse/<br>
-&nbsp; &nbsp; .eclipseextension<br>
-&nbsp;&nbsp;&nbsp; features/<br>
-&nbsp;&nbsp;&nbsp; plugins/</code></p>
-<p>The only significant difference from a product installer is that an extension
-installer also creates link files in other Eclipse-based products already
-installed on the user's computer. (This saves the user from having to manually
-associate the new extension from within each product using the Eclipse update
-manager.)&nbsp;</p>
-<p>The link file created in step 14 is <code>&lt;<i>product install</i>&gt;/eclipse/links/<i>com.example.wiley.anvilfeature.</i>link</code>;
-that is, the file has the same name of as the extension's feature directory less
-the version number suffix. A link file is a <a href="http://java.sun.com/j2se/1.3/docs/api/java/util/Properties.html">java.io.Properties</a>
-format file (ISO 8859-1 character encoding with "\" escaping).
-The key is &quot;path&quot; and the value is the absolute path of the installed
-extension, <code>&lt;<i>install</i>&gt;</code>; e.g., an entry might looks like &quot;<code>path=C:\\Program
- Files\\Wiley\\Anvil</code>&quot;<code>.</code> The installer is responsible for converting
-from native character
-encoding to Unicode and adding &quot;\&quot; escapes where required. Escaping is
-usually required since <code>&lt;<i>install</i>&gt;</code>
- typically contains special characters (such as &quot;\&quot;)
-and may mention directories with non-Latin characters in their names. The product reads
-link files when it starts up. The installer keeps a record of any link
-files it creates so that they can be located when the extension is updated or
-uninstalled.</p>
-<h3>Uninstaller behavior</h3>
-<p>At un install time, the un installer should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially products using the extension
-    being uninstalled</li>
-  <li>ask user to confirm that the extension is to be un installed</li>
-  <li>remove all installed files from the &lt;<i><code>install</code></i>&gt;
-    directory, and <b>all</b> files in &lt;<i><code>install</code></i>&gt;<code>/eclipse/features</code>
-    and &lt;<i><code>install</code></i>&gt;<code>/eclipse/plugins</code> including ones put there by parties other than
-    this installer (e.g., by the Eclipse update manager)</li>
-  <li>if feasible, remove the link file from any products to which it had been
-    added&nbsp;</li>
-  <li>remove entry for extension uninstaller</li>
-  <li>inform user of any files that were not removed</li>
-</ol>
-<p>When an extension is uninstalled, all plug-in and feature files should be deleted; there are no
-important data files to be kept in these subdirectories. This allows the user to uninstall an extension
-completely, including any updates applied by the Eclipse update manager.</p>
-<h3>Installer behavior when extension already installed</h3>
-<p>When the extension is already installed on the user's computer, the installer
-should allow a service update or version upgrade to be applied to the installed
-extension.</p>
-<p>At install time, the installer should behave in the standard manner:</p>
-<ol>
-  <li>warn user to exit all programs, especially products using the extension
-    being updated</li>
-  <li>locate the installed extension to be updated, if necessary by searching
-    the disk for an existing extension install or by allowing the user to locate
-    it</li>
-  <li> determine where this installer is a compatible update</li>
-  <li>if appropriate, ask the user for the name of the registered owner and for
-    the license key</li>
-  <li>display the product's updated licensing agreement and ask the user to accept</li>
-  <li>ask user to confirm all details of the update</li>
-  <li>update files on disk&nbsp; (see below)</li>
-  <li>should add modified or newly added files to the list of ones to be removed at uninstall
-    time (where feasible)</li>
-  <li>offer to show the extension release notes (&quot;readme&quot; file)</li>
-</ol>
-<p>In step 2, an installed extension can be recognized by the presence of an &quot;<code>eclipse</code>&quot;
-directory immediately containing a file named &quot;<code>.eclipseextension</code>&quot;.
-The parent of the &quot;<code>eclipse</code>&quot; directory is an extension's install
-directory; i.e., <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code>.
-The information contained within this marker file should be shown to the user for
-confirmation that the correct extension is being updated (there may be several
-Eclipse-based extension on the user's computer).</p>
-<p>For step 7, the installer should not delete or overwrite any of the files
-that it originally installed; rather, it should only add the files for new
-versions of features and plug-in, and possibly rewrite the marker file <code>&lt;<i>install</i>&gt;/eclipse/.eclipseextension</code>. Leaving the old versions around gives the user
-the option to back out of the update. As with upgrading a product install, there
-is no need to touch any files in <code>&lt;<i>install</i>&gt;/eclipse/plugins/<i>com.example.wiley.otherplugin</i>_<i>1.0.0</i></code>/
-if this sub-directory should also exist after the upgrade; if any of the plug-in's
-files were to change, the plug-in's version number is revised, causing the files
-for the upgraded plug-in to be installed in a parallel directory <code>&lt;<i>install</i>&gt;/eclipse/plugins/<i>com.example.wiley.otherplugin</i>_<i>1.0.1</i></code>/.&nbsp;</p>
-
-
-
-</body>
-
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html
deleted file mode 100644
index 46992f1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/eclipsestarter.html
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Starting Eclipse from Java</title>
-</head>
-
-<body>
-
-<h1>Starting Eclipse from Java</h1>
-<p>Last modified June 1, 2007</p>
-<p>
-The Eclipse Platform makes heavy use of Java class loaders for loading plug-ins. Even the Eclipse Runtime itself 
-and the OSGi framework need to be loaded by special class loaders. Client programs, such as a Java main program
-or a servlet, cannot directly reference any part of Eclipse directly. Instead, a client must use 
-the <b>EclipseStarter</b> class in <b>org.eclipse.core.runtime.adaptor</b> to start the platform, 
-invoking functionality defined in plug-ins, and shutting down the platform when done. 
-</p>
-<p>
-Clients that do not need to access any particular function, but just need to start the platform, can use
-<tt>org.eclipse.equinox.launcher.Main.run()</tt> in the bundle <tt>org.eclipse.equinox.launcher</tt>.  However, clients that need to invoke specific function should use
-<b>EclipseStarter</b>.  See the javadoc inside this class for details.
-</p>  
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html
deleted file mode 100644
index 005945a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_archive.html
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Feature Archives</title>
-</head>
-<body>
-
-<h1>
-Feature Archives</h1>
-<p>The feature packaging information is placed into a separate Java .jar.
-Standard Java jar facilities are used for constructing feature archives.
-Feature archives reference separately packaged plug-in archives (see next
-section) and non-plug-in files.</p><p>Features are identified using a structured identifier based on the provider
-internet domain name. For example, organization eclipse.org produces
-feature org.eclipse.jdt. The character set used for feature identifiers
-is as specified for plug-in identifiers (see <a href="plugin_manifest.html">Plug-in
-Manifest</a>).</p>
-<p>The recommended convention for naming the feature archives is
-<br><tt>&lt;id&gt;_&lt;version&gt;.jar</tt> </p>
-<p>Where <tt>&lt;id&gt;</tt> is the feature identifier and <tt>&lt;version&gt;</tt>
-is the full version identifier contained in the respective feature.xml.
-Note that this is a recommended convention that minimizes chance of collisions,
-but is not required by the Eclipse architecture. For example, the following
-are valid feature archive names</p>
-<p><tt>org.eclipse.jdt_2.0.0.jar</tt>
-<br><tt>org.eclipse.pde_2.0.jar</tt>
-<br><tt>my_feature.jar</tt></p>
-<p>Internally, each feature archive is packaged relative to its feature
-directory (but not including the directory path element). The archive has
-the following structure	</p>
-<p><tt>feature.xml</tt>
-<br><tt>feature&lt;_locale&gt;.properties (see "Translated Feature Information")</tt>
-<br><tt>other feature files and subdirectories (TBD)</tt>
-<br><tt>META-INF/</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt>
-</p>
-Note that feature archives do not contain their constituent plug-ins and fragments.
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html
deleted file mode 100644
index 6d7e651..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/feature_manifest.html
+++ /dev/null

@@ -1,538 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Feature Manifest</title>
-</head>
-<body>
-
-<h1>
-Eclipse platform feature manifest</h1>
-<p class=MsoNormal><span style='font-size:10.0pt'>Version 3.0 - Last revised June 3, 2009</span></p>
-
-<p>The feature manifest format is defined by the following dtd:</p>
-<p><tt>&lt;?xml encoding="ISO-8859-1"?&gt;</tt></p>
-<p><tt>&lt;!ELEMENT feature (install-handler? | description? | copyright? |
-license? | url? | includes* | requires? | plugin* | data*)&gt;</tt>
-<br><tt>&lt;!ATTLIST feature</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; provider-name CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; image&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; colocation-affinity</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; primary&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-(true | false) "false"<br>
-&nbsp;&nbsp;&nbsp; exclusive&nbsp;&nbsp;&nbsp;&nbsp; (true | false)
-&quot;false&quot;<br>
-&nbsp;&nbsp;&nbsp; plugin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
-#IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; application&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT install-handler EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST install-handler</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; library&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; handler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT description (#PCDATA)&gt;</tt>
-<br><tt>&lt;!ATTLIST description</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT copyright (#PCDATA)&gt;</tt>
-<br><tt>&lt;!ATTLIST copyright</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT license (#PCDATA)&gt;</tt>
-<br><tt>&lt;!ATTLIST license</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT url (update?, discovery*)&gt;</tt></p>
-<p><tt>&lt;!ELEMENT update EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST update</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT discovery EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST discovery<br>
-&nbsp;&nbsp;&nbsp; type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-(web | update) &quot;update&quot;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT includes EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST includes</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED<br>
-&nbsp;&nbsp;&nbsp;
-name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED<br>
-&nbsp;&nbsp;&nbsp;
-optional&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true | false)
-&quot;false&quot;<br>
-&nbsp;&nbsp;&nbsp; search-location&nbsp;&nbsp; (root | self | both)
-&quot;root&quot;</tt><br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt> <tt><br>
-&gt;</tt></p>
-<p><tt>&lt;!ELEMENT requires (import+)&gt;</tt></p>
-<p><tt>&lt;!ELEMENT import EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST import</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; plugin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED<br>
-&nbsp;&nbsp;&nbsp; feature&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; match&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-(perfect | equivalent | compatible | greaterOrEqual) "compatible"<br>
-&nbsp;&nbsp;&nbsp; patch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true |
-false) &quot;false&quot;</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT plugin EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST plugin</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; fragment&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true
-| false) "false"</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; download-size CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; install-size&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; unpack&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (true |
-false) &quot;true&quot;</tt>
-<br><tt>&gt;</tt></p>
-<p><tt>&lt;!ELEMENT data EMPTY&gt;</tt>
-<br><tt>&lt;!ATTLIST data</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #REQUIRED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; os&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; arch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; ws&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; nl&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; download-size CDATA #IMPLIED</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; install-size&nbsp; CDATA #IMPLIED</tt>
-<br><tt>&gt;</tt></p>
-<p>The element and attribute definitions are as follows:</p>
-<ul>
-
-<li>&lt;feature&gt; - defines the feature
-<ul>
-<li>id - required feature identifier (eg. com.xyz.myfeature)</li>
-<li>version - required component version (eg. 1.0.3)</li>
-<li>label - optional displayable label (name). Intended to be translated.</li>
-<li>provider-name - optional display label identifying the organization providing
-this component. Intended to be translated.</li>
-<li>image - optional image to use when displaying information about the feature.&nbsp;
-Specified relative to the feature.xml.</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-OS systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-WS's. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this feature should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the feature can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of feature
-regardless of this setting).</li>
-<li>colocation-affinity - <em>(deprecated)</em> optional reference to another feature identifier
-used to select the default installation location for this feature. When
-this feature is being installed as a new feature (no other versions of
-it are installed), an attempt is made to install this feature in the same
-installation location as the referenced feature.</li>
-<li>primary - <em>(deprecated)</em> optional indication specifying whether this feature can be used
-as a primary feature. Default if <i>false</i>
-(not a primary feature).</li>
-<li>application - optional identifier of the Eclipse application that is to
-be used during startup when the declaring feature is the primary feature. The application identifier must represent a valid application
-registered in the <tt>org.eclipse.core.runtime.applications</tt> extension
-point. Default is <tt>org.eclipse.ui.ide.workbench</tt>.</li>
-<li> plugin - optional identifier that represents the id of the plug-in 
-listed in the feature that is used to carry branding information for 
-the feature (images, translations, splash screens in case of primary feature 
-etc.). If not specified, the assumption will be made the attribution plug-in 
-has the same id as the feature.</li>
-<li>exclusive  - optional flag that, if &quot;true&quot;, indicates that
-the feature cannot be installed in a group with other features.</li>
-</ul>
-</li>
-
-<li>&lt;install-handler&gt;
-<ul>
-<li><b>Note:</b> The install-handler element is deprecated. Install handlers
-are still supported using a compatibility mechanism, but they should be avoided.</li>
-<li>library - optional .jar library containing the install handler classes.
-If specified, the referenced .jar must be contained in the feature archive.
-It is specified as a path within the feature archive, relative to the feature.xml
-entry. If not specified, the feature archive itself is used to load the
-install handler classes. This attribute is only interpreted if <i>class</i>
-attribute is also specified</li>
-<li>handler - optional identifier of the install handler. The value is interpreted
-depending on the value of the <i>library</i> attribute. If <i>library</i>
-is specified,&nbsp; the value is interpreted as a fully qualified name
-of a class contained in the specified <i>library</i>. If <i>library</i>
-is not specified, the value is is interpreted as an extension identifier
-of an extension registered in the <i>org.eclipse.update.installHandlers</i>
-extension point. In either case, the resulting class must implement the
-<i>IInstallHandler</i>
-interface. The class is dynamically loaded and called at specific points
-during feature processing. When the handler is specified as a class, it has visibility to the API classes
-from the org.eclipse.update.core plug-in, and Eclipse plug-ins required by this 
-plug-in; otherwise, when is specified as extension, it has access to all the 
-classes as the plug-in defining the extension.</li>
-</ul>
-</li>
-
-<li>&lt;description&gt; - brief component description as simple text. Intended
-to be translated.
-<ul>
-<li>url - optional URL for the full description as HTML. The URL can be specified
-as absolute of relative. If relative, it is assumed to be relative to (and
-packaged in) the feature archive. Note, that for NL handling the URL value
-should be separated to allow alternate URLs to be specified for each national
-language.</li>
-</ul>
-</li>
-
-<li>&lt;copyright&gt; - feature copyright as simple text. Intended to be translated.
-<ul>
-<li>url - optional URL for the full description as HTML. The URL can be specified
-as absolute of relative. If relative, it is assumed to be relative to (and
-packaged in) the feature archive. Note, that for NL handling the URL value
-should be separated to allow alternate URLs to be specified for each national
-language.</li>
-</ul>
-</li>
-
-<li>&lt;license&gt; - feature "click-through" license as simple text. Intended
-to be translated. It is displayed in a standard dialog with [Accept] [Reject]
-actions during the download/ installation process. Note, that click-through
-license must be specified for any feature that will be selected for installation
-or update using the Eclipse update manager. When using nested features,
-only the nesting parent (i.e. the feature selected for installation or update)
-must have click-through license text defined. The license text is required
-even if the optional <i>url</i> attribute is specified.
-<ul>
-<li>url - optional URL for the full description as HTML. The URL can be specified
-as absolute of relative. If relative, it is assumed to be relative to (and
-packaged in) the feature archive. Note, that for NL handling the URL value
-should be separated to allow alternate URLs to be specified for each national
-language. Note, that the "content" of this URL is <b>not</b> what is presented
-as the click-through license during installation processing. The click-through
-license is the actual value of the <i>&lt;license&gt;</i> element (eg. <tt>&lt;license&gt;click
-through text&lt;/license&gt;</tt>)</li>
-</ul>
-</li>
-
-<li>&lt;url&gt; - optional URL specifying site(s) contain feature updates, or new features
-<ul>
-<li>&lt;update&gt; - URL to go to for updates to this feature
-<ul>
-<li>url - actual URL</li>
-<li>label - displayable label (name) for the referenced site</li>
-</ul>
-</li>
-<li>&lt;discovery&gt; - URL to go to for new features. In general, a provider
-can use this element to reference its own site(s), or site(s) of partners
-that offer complementary features. Eclipse uses this element simply as
-a way to distribute new site URLs to the clients. Sites that belong to root
-features (at the top of the hierarchy) typically appear in &quot;Sites to
-Visit&quot; in Update Manager.
-<ul>
-<li>url - actual URL</li>
-<li>label - displayable label (name) for the referenced site</li>
-<li>type (deprecated) - by default, discovery sites are assumed to be update sites
-(&quot;update&quot;). Setting the value of this attribute to &quot;web&quot;
-indicates that the URL should be treated as a
-regular Web hyperlink that can be directly displayed in a suitable browser.</li>
-</ul>
-</li>
-</ul>
-</li>
-
-<li>&lt;includes&gt; - optional reference to a nested feature that is considered
-to be part of this feature. Nested features must be located on the same
-update site as this feature
-<ul>
-<li>id - required nested feature identifier. If the feature is a patch (see the 
-&lt;requires&gt; section below), this must be the id of another patch.</li>
-<li>version - required nested feature version</li>
-<li>optional - it is possible to include a feature as optional when
-this attribute is &quot;true&quot;. Users are allowed to not install optional
-features, disable them if they are installed, and install them later. A missing
-optional feature is not treated as an error.</li>
-<li>name - if an optional feature is missing, Eclipse cannot render its
-name properly. This attribute can be used as a 'place holder' to allow Eclipse
-to render the name of the optional feature when it is not installed.</li>
-<li>search-location - an included feature can be updated by patches. 
-By default, search location is &quot;root&quot;
-which means that URL specified in the &quot;update&quot; element within the
-&quot;url&quot; element of the parent will be considered. If an included feature
-has its own &quot;update&quot; element defined, it will be ignored by default.
-If the parent feature wants to allow the child to be updated from its own
-location, it can set this attribute to &quot;both&quot; or &quot;self&quot;.</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified OS
-systems. If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified WS's.
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this entry should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the entry can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of entry
-regardless of this setting).</li>
-</ul>
-</li>
-
-<li>&lt;requires&gt; - optional feature dependency information. Is expressed in
-terms of plug-in dependencies. If specified, is enforced by the installation
-and update support at the time of installation
-<ul>
-<li>&lt;import&gt; - dependency entry. Specification and processing is a subset
-of the &lt;import&gt; specification in plugin.xml
-<ul>
-<li>plugin - identifier of dependent plug-in, if plug-in is used to express dependency</li>
-<li>feature (new in 2.1) - identifier of dependent feature, if feature is used to
-express dependency. <b>Either plugin or feature attribute must be set, but not
-both. </b>If &quot;patch&quot; is &quot;true&quot;, feature attribute must be
-used.</li>
-<li>version - optional plug-in version specification. If &quot;patch&quot; is
-&quot;true&quot;, version must be set.</li>
-<li>match - optional matching rule. Valid values and processing are as follows:
-<ul>
-<li>if version attribute is not specifies, the match attribute (if specified) is ignored.</li>
-<li><b><i>perfect</i></b> - dependent plug-in version must match exactly the
-specified version. If &quot;patch&quot; is &quot;true&quot;, &quot;perfect&quot;
-is assumed and other values cannot be set.</li>
-<li><b><i>equivalent</i></b> - dependent plug-in version must be at least at
-the version specified, or at a higher service level (major and minor version
-levels must equal the specified version).</li>
-<li><b><i>compatible</i></b> - dependent plug-in version must be at least at
-the version specified, or at a higher service level or minor level (major
-version level must equal the specified version).</li>
-<li><b><i>greaterOrEqual</i></b> - dependent plug-in version must be at least
-at the version specified, or at a higher service, minor or major level.</li>
-</ul>
-</li>
-<li>patch - if &quot;true&quot;, this constraint declares the enclosing
-feature to be a patch for the referenced feature. Certain rules must be followed
-when this attribute is set:
-<ul>
-  <li>feature attribute must be used to identifier of feature being patched</li>
-  <li>version attribute must be set</li>
-  <li>match attribute should not be set and &quot;perfect&quot; value will be
-    assumed.</li>
-  <li>if other features are &lt;include&gt;'ed, they must also be patches.</li>
-</ul>
-A patch is a special feature that carries newer versions of plug-ins for
- the feature it is patching.  It does not replace the feature.  A patch can also
- carry other patches by inclusion.</li>
-</ul>
-</li>
-</ul>
-</li>
-
-<li>&lt;plugin&gt; - identifies referenced plug-in
-<ul>
-<li>id - required plug-in identifier (from plugin.xml)</li>
-<li>version - required plug-in version (from plugin.xml)</li>
-<li>fragment - optional specification indicating if this entry is a plug-in fragment. Default is "false"</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified os
-systems. If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified WS's.
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this entry should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the entry can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of entry
-regardless of this setting).</li>
-<li>download-size - optional hint supplied by the feature packager, indicating
-the download size in KBytes of the referenced plug-in archive. If not specified,
-the download size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-<li>install-size - optional hint supplied by the feature packager, indicating
-the install size in KBytes of the referenced plug-in archive. If not specified,
-the install size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-<li>unpack (new in 3.0) - optional specification supplied by the feature packager,
-indicating that plugin is capable of running from a jar, and contents of plug-in
-jar should not be unpacked into a directory.  Default is "true".
-(<b>Implementation Note:</b> partial plug-ins - delivered in a feature specifying
-<tt>org.eclipse.update.core.DeltaInstallHandler</tt> as an install handler should
-not set unpack to &quot;false&quot;)</li>
-</ul>
-</li>
-
-<li>&lt;data&gt; - identifies non-plugin data that is part of the feature
-<ul>
-<li>id - required data identifier in the form of a relative path.</li>
-<li>os - optional operating system specification. A comma-separated list of
-operating system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified OS's.
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>arch - optional machine architecture specification. A comma-separated list
-of architecture designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this feature should only be installed on one of the specified
-systems. If this attribute is not specified, the feature can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of feature regardless of this setting).</li>
-<li>ws - optional windowing system specification. A comma-separated list of
-window system designators defined by Eclipse (see Javadoc for <tt>
-org.eclipse.core.runtime.Platform)</tt>.
-Indicates this entry should only be installed on one of the specified WS's
-If this attribute is not specified, the entry can be installed
-on all systems (portable implementation). This information is used as a
-hint by the installation and update support (user can force installation
-of entry regardless of this setting).</li>
-<li>nl - optional locale specification. A comma-separated list of locale designators
-defined by Java. Indicates this entry should only be installed on a system
-running with a compatible locale (using Java locale-matching rules). If
-this attribute is not specified, the entry can be installed on all systems
-(language-neutral implementation). This information is used as a hint by
-the installation and update support (user can force installation of entry
-regardless of this setting).</li>
-<li>download-size - optional hint supplied by the feature packager, indicating
-the download size in KBytes of the referenced data archive. If not specified,
-the download size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-<li>install-size - optional hint supplied by the feature packager, indicating
-the install size in KBytes of the referenced data archive. If not specified,
-the install size is not known (<b>Implementation Note:</b> the implementation
-needs to distinguish between "not known" and 0 size)</li>
-</ul>
-</li>
-</ul>
-<p>When interacting with
-the update site, the feature implementation maps the <tt>&lt;plugin&gt;</tt>
-and <tt>&lt;data&gt;</tt> elements into path identifiers used by the site
-to determine the actual files to download and install. The default feature
-implementation supplied by Eclipse constructs the path identifiers as follows:</p>
-<ul>
-<li>
-<tt>&lt;plugin&gt;</tt> element results in a path entry in the form "<tt>plugins/&lt;pluginId&gt;_&lt;pluginVersion&gt;.jar</tt>"
-(for example, "<tt>plugins/org.eclipse.core.boot_2.0.0.jar</tt>")</li>
-
-<li>
-<tt>&lt;data&gt;</tt> element results in a path entry in the form "<tt>features/&lt;featureId&gt;_&lt;featureVersion&gt;/&lt;dataId&gt;</tt>"
-(for example, "f<tt>eatures/com.xyz.tools_1.0.3/examples.zip</tt>")</li>
-</ul>
-<p>Note, that in general the feature.xml&nbsp; manifest documents should specify
-UTF-8 encoding. For example:</p>
-<pre>&lt;?xml version="1.0" encoding="UTF-8"?&gt;</pre>
-<p>Translatable text contained in the feature.xml can be separated into
-feature&lt;_locale&gt;.properties files using Java property bundle conventions.
-Note that the translated strings are used at installation time (i.e. do
-not employ the plug-in fragment runtime mechanism).&nbsp;
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/gcj.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/gcj.html
deleted file mode 100644
index 5655ecb..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/gcj.html
+++ /dev/null

@@ -1,107 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Running on GCJ</title>
-</head>
-
-<body>
-<h1>GCJ</h1>
-<p>GCJ is an effort by the GCC team to provide an open source Java compiler and
-runtime environment to interpret Java bytecode. Unfortunately, the GCJ runtime
-environment is not an environment that is often tested on by Eclipse
-developers.</p>
-
-<p>The most common problems surrounding GCJ are:
--Eclipse does not start at all
--Eclipse throws a 'java.lang.ClassNotFoundException:
-org.eclipse.core.runtime.Plugin' that can be found in the logs (located in
-workspace/.metadata/.log)</p>
-
-<p>The workspace's log file is a good place to check to identify whether GCJ is
-being used or not. Every Eclipse log session should be prepended with
-information about the runtime environment that was used to run Eclipse. The log
-may include something like the following:</p>
-
-<code>java.fullversion=GNU libgcj 4.2.1 (Debian 4.2.1-5)</code>
-
-<p>If Eclipse does start, one can check which runtime environment is being used to
-run Eclipse by going to 'Help &gt; About Eclipse SDK &gt; Configuration Details'. The
-About Dialog itself can also provide other information, the build identifier
-can be of particular interest as it is tagged by some distros. This allows the
-user to identify whether Eclipse was downloaded through the distribution's
-package management system or directly from the eclipse.org website.</p>
-
-Eg: <code>Build id: M20070212-1330 (Ubuntu version: 3.2.2-0ubuntu3)</code>
-
-<p>The two most common workarounds would be to:</p>
-<ul>
-<li>download the Eclipse binary from eclipse.org directly</li>
-<li>run Eclipse using an alternate Java runtime environment</li></ul>
-
-<p>To download Eclipse, try one of the links below:</p>
-<ul>
-<li><a href="http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</a></li>
-<li><a href="http://download.eclipse.org/eclipse/downloads/">http://download.eclipse.org/eclipse/downloads/</a></li></ul>
-
-It is imperative that 64-bit builds are downloaded and used if a 64-bit Java
-runtime environment has been installed. Below are two sample tarball names of
-version 3.3.2 of the Eclipse SDK packaged for 32-bit and 64-bit processors.
-
-<pre>eclipse-SDK-3.3.2-linux-gtk.tar.gz (32-bit)
-eclipse-SDK-3.3.2-linux-gtk-x86_64.tar.gz (64-bit)</pre>
-
-<p>To run Eclipse with an alternate Java runtime environment, the path to the Java
-virtual machine's binary must be identified. With an Eclipse installation from
-the distribution, altering the $PATH variable to include the path to the
-alternate Java runtime environment is often not enough as the Eclipse that
-Linux distributions package often performs a scan internally to pick up GCJ by
-itself whilst ignoring what's on the $PATH. An example of the terminal's output
-can be seen below:</p>
-
-<code>searching for compatible vm...<br>
-  testing /usr/lib/jvm/java-7-icedtea...not found<br>
-  testing /usr/lib/jvm/java-gcj...found</code>
-
-<p>Once the path to the virtual machine's binary has been identified, try running
-Eclipse with the following command:</p>
-
-<code>./eclipse -vm /path/to/jre/bin/java</code>
-
-<p>For an actual example, it might look something like the following:</p>
-
-<code>./eclipse -vm /usr/lib/jvm/sun-java-6/bin/java<br>
-./eclipse -vm /opt/sun-jdk-1.6.0.02/bin/java</code>
-
-<p>If this seems to solve the problem, it is likely that the problem really was
-related to the use of GCJ as the Java runtime for running Eclipse. The
-eclipse.ini file located within Eclipse's folder can be altered to
-automatically pass this argument to Eclipse at startup. An example of its
-content is presented below:</p>
-
-<code>-showsplash<br>
-org.eclipse.platform<br>
---launcher.XXMaxPermSize<br>
-256m<br>
--vm<br>
-/opt/sun-jdk-1.6.0.02/bin/java<br>
--vmargs<br>
--Xms40m<br>
--Xmx512m</code>
-
-<p>Note that every argument must be on its own line. More information about the
-eclipse.ini file can be found at <a href="http://wiki.eclipse.org/Eclipse.ini">http://wiki.eclipse.org/Eclipse.ini</a>.</p>
-
-<p>If problems persists after downloading an installation of Eclipse from
-eclipse.org and using a supported Java runtime environment (a list of which may be found in the readme_eclipse.html supplied with your installation), one should seek
-assistance from the Eclipse team via its plethora of communication channels
-like the <a href="http://www.eclipse.org/newsgroups/">newsgroups</a>, the IRC <a href="irc://irc.freenode.net/#eclipse">channel</a>, and/or <a href="https://bugs.eclipse.org/bugs/">bugzilla</a>.</p>
-<p></p>
-<p> </p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/index.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/index.html
deleted file mode 100644
index 76756f5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/index.html
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Other Reference Information</title>
-</head>
-<body>
-
-<h1>
-Other Reference Information</h1>
-The following specifications, white papers, and design notes describe various
-aspects of the Eclipse Platform.
-<h2>Basic platform information</h2>
-<ul>
-  <li> <a href="launcher.html">The Eclipse Launcher</a></li>
-  <li> <a href="runtime-options.html">Runtime options</a></li>
-  <li> <a href="api-usage-rules.html">API rules of engagement</a></li>
-  <li> <a href="naming.html">Naming conventions</a></li>
-  <li> <a href="terminology.html">Glossary of terms</a></li>
-  <li> <a href="overview-platform.html">Map of platform plug-ins</a></li>
-  <li> <a href="eclipsestarter.html">Starting Eclipse from Java</a></li>
-  <li> <a href="multi_user_installs.html">Multi-user installs</a></li>
-  <li> <a href="buddy_loading.html">Third party libraries and classloading</a></li>
-  <li> <a href="plugin_manifest.html">Plug-in manifest</a></li>
-  <li> <a href="bundle_manifest.html">OSGi bundle manifest</a></li>
-  <li> <a href="project_description_file.html">Project description file</a></li>
-  <li> <a href="message_bundles.html">Message bundles</a></li>
-  <li> <a href="gcj.html">Running on GCJ</a></li>
-  <li> <a href="platform-scheme-uri.html">A description of the &quot;platform&quot; URL protocol</a></li>
-</ul>
-
-<h2>User interface information</h2>
-<ul>
-<li><a href="ui_accessibility_tips.html">Tips for making user interfaces accessible</a></li>
-<li><a href="bidi.html">Supporting bidirectional text</a></li>
-</ul>
-
-<h2>Product install and configuration information</h2>
-<ul>
-  <li> <a href="eclipse-install.html">How to write an Eclipse installer</a></li>
-  <li> <a href="about_customization.html">About.ini file format</a></li>
-  <li> <a href="plugin_archive.html">Plug-in archives</a></li>
-  <li> <a href="feature_manifest.html">Feature manifest</a></li>
-  <li> <a href="feature_archive.html">Feature archives</a></li>
-  <li> <a href="update_platform_xml.html">The platform.xml file</a></li>
-  <li> <a href="update_standalone.html">Running update manager from command line</a></li>
-  <li> <a href="launcher_ini.html">The Executable configuration file</a></li>
-  <li> <a href="p2_dropins_format.html">The dropins folder and supported file layouts</a></li>
-</ul>
-<h2><a href="http://www.eclipse.org/articles/index.html">Eclipse.org articles
-index</a></h2>
-<p>The eclipse.org site contains technical articles about many topics of
-interest. Check the index regularly for the latest technical information
-regarding Eclipse.</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/launcher.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/launcher.html
deleted file mode 100644
index 45d96ee..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/launcher.html
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en"><head>
-   <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-   <title>Eclipse Launcher</title>
-</head>
-<body>
-<h1>Eclipse Launcher<br>
-</h1>
-<h2>Description</h2>
-<p>Eclipse contains a native executable launcher that is used to start
-Eclipse.&nbsp; There is more to the launcher than just the eclipse
-executable in the root of the install.<br>
-</p>
-<h3>The launcher and its shared library</h3>
-<p>The launcher executable comes in 2 pieces:
-the executable (eclipse.exe), and a shared library (eclipse_1017.dll). The
-executable lives in the root of the eclipse install. The shared library
-is in a platform specific fragment,
-<tt>org.eclipse.equinox.launcher.[config]</tt>, in the plugins directory.
-</p>
-<p>Having the majority of the launcher code in a shared library
-that lives in a fragment means that that portion of the launch code can
-now be updated from an update site. Also, when starting from java, the
-shared library can be loaded via JNI in order to display the splash
-screen.
-</p>
-<h3>The launcher bundle</h3>
-<p>Previous versions of Eclipse had a startup.jar JAR file in the root
-of the install.&nbsp; In 3.3, this code has been moved to a plug-in <tt>org.eclipse.equinox.launcher</tt> in
-the plugins directory. Eclipse can still be started directly with java
-using, for example:
-</p>
-<div style="text-align: center;">
-<pre>java -jar plugins/org.eclipse.equinox.launcher_1.0.0.v20070606.jar</pre>
-</div>
-<p>Launching Eclipse involves 3 main pieces: the native executable, the
-launcher platform specific fragment and the launcher jar. In the
-example below, notice that the launcher fragment is in folder form,
-this is necessary so that the native eclipse.exe can load the shared
-library:
-</p>
-<div style="text-align: left; margin-left: 50px;">
-<pre>eclipse/ <br>	eclipse.exe<br>	plugins/<br>		org.eclipse.equinox.launcher_1.0.0.v20070606.jar<br>		org.eclipse.equinox.launcher.win32.win32.x86_1.0.0.v20070523/<br>			eclipse_1017a.dll<br></pre>
-</div>
-<p>
-The version numbers above are for illustration purposes only (e.g. 1.0.0.v20070606).  The actual version
-numbers may vary depending on the version of Eclipse you are using.
-</p>
-<h3>Finding a VM and using the JNI Invocation API</h3>
-<p>The Eclipse launcher is capable of loading the Java VM in the
-eclipse process using the Java Native Interface Invocation API.&nbsp;
-The launcher is still capable of starting the Java VM in a separate
-process the same as previous version of Eclipse did.&nbsp; Which method
-is used depends on how the VM was found.<br>
-</p>
-<h4>No -vm specified</h4>
-<div style="margin-left: 40px;">
-<p>When no -vm is specified, the launcher looks for a virtual machine
-first in a jre directory in the root of eclipse and then on the search
-path. If java is found in either location, then the launcher looks for a jvm
-shared library (jvm.dll on Windows, libjvm.so on *nix platforms)
-relative to that java executable. </p>
-<ul>
-<li>If a jvm shared library is found the launcher loads it and uses the JNI invocation API to start the vm.
-</li><li>If no jvm shared library is found, the launcher executes the java launcher to start the vm in a new process.</li>
-</ul>
-</div>
-<h4>-vm specified on the command line or in eclipse.ini</h4>
-<p style="margin-left: 40px;">Eclipse can be started with "-vm &lt;location&gt;" to indicate a
-virtual machine to use. There are several possibilities for the value
-of &lt;location&gt;:
-</p>
-<ol style="margin-left: 40px;">
-<li><span style="font-weight: bold;">directory</span>:&nbsp;  &lt;location&gt; is a directory. We look in that
-directory for: (1) a java launcher or (2) the
-jvm shared library. If we find the jvm shared library, we use JNI
-invocation. If we find a launcher, we attempt to find a jvm library in
-known locations relative to the launcher. If we find one, we use JNI
-invocation. If no jvm library is found, we exec java in a new process.<br>
-    <span style="font-weight: bold;"></span></li><li><span style="font-weight: bold;"> java.exe/javaw.exe</span>: &lt;location&gt; is a path to a java
-launcher. We exec that java launcher to start the vm in a new process.
-  </li>
-<li><span style="font-weight: bold;">jvm dll or so</span>: &lt;location&gt; is a path to a jvm
-shared library. We attempt to load that library and use the JNI
-Invocation API to start the vm in the current process.
-</li>
-</ol>
-
-<h4>Exceptions</h4>
-<ul>
-  <li><span style="font-weight: bold;">linux.ppc, linux.x86_64, aix.ppc</span>:&nbsp;
-The launcher is not able to load some older vms using the JNI
-invocation API.&nbsp; By default on these platforms the launcher will
-prefer to execute java in a separate process.&nbsp; To force the
-launcher to load the vm using JNI, specify a -vm option pointing
-directly to the vm's shared library (libjvm.so).</li>
-  <li><span style="font-weight: bold;">MacOSX</span>:&nbsp; The launcher uses the system JavaVM framework and will always load the vm in-process using the JNI invocation API.<br>
-  </li>
-</ul>
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/launcher_ini.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/launcher_ini.html
deleted file mode 100644
index b6e7ec9..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/launcher_ini.html
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse launch configuration</title>
-</head>
-
-<body>
-<h1>Eclipse launcher configuration</h1>
-<h2>Description</h2>
-<p>
-When starting Eclipse there are many command-line arguments which are valid
-to pass along to the executable. Rather than creating a shortcut or script for
-launching, users are able to create a launcher configuration file which will be 
-read by the executable on startup. 
-</p><p>
-The format of the launcher configuration file is as follows:
-</p>
-<ul>
-<li>The configuration file must have the same name as the executable itself, with a file
-extension of <code>.ini</code>. For instance, the default launcher configuration file
-is called <code>eclipse.ini</code>.</li>
-<li>The file must contain only one command-line argument per line.</li>
-<li>Whitespace is important...there cannot be any extra spaces at the end of each line.</li>
-<li>The file should be located as a sibling of the executable.</li>
-</ul>
-<p>
-Sample file content:</p>
-<blockquote><pre><code>
--vm
-c:/path/to/my/java.exe
--debug
--console
--data
-d:/path/to/my/workspace
--vmargs
--Xmx384m
-</code></pre></blockquote>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html
deleted file mode 100644
index 4db768c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/message_bundles.html
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Message Bundles</title>
-</head>
-
-<body>
-<h1>Message Bundles</h1>
-<h2>Description </h2>
-<p>Standard Java ResourceBundles have quite inefficient space characteristics. 
-  Since a running Eclipse tends to have many externalized messages, we have implemented 
-  a new message bundle system to be used in Eclipse. The mechanism is quite simple 
-  and completely generic - it can be used anywhere.</p>
-<h3>Summary of the new approach:</h3>
-<ul>
-  <li><code> messages.properties </code>- this file is same as before except all 
-    keys need to be valid Java identifiers.</li>
-  <li> Each message file has a corresponding Java class.</li>
-  <li> Each key/value pair in the file has a <code>public static String</code> 
-    field whose name is the same as the message key.</li>
-  <li> When message bundles are loaded, the values of the fields are set to be 
-    the values from the <code>messages.properties </code>files.</li>
-  <li> The message properties files are purged from memory. </li>
-</ul>
-<h3>When creating a new message:</h3>
-<ul>
-  <li> Create a field in your <code>Messages.java </code>file.</li>
-  <li> Create a key/value pair in your <code>messages.properties </code>file where 
-    the key name matches the field name,</li>
-  <li> To reference the message, simply reference the field (e.g. <code>Messages.my_key</code>) 
-    rather than the standard lookup.</li>
-</ul>
-<h2>Example Files:</h2>
-<h3>Client Code</h3>
-<h4>Old Code: </h4>
-<pre><code>public class MyClass {
-  public void myMethod() {
-    String message;
-    ...
-    // no args
-    message = Messages.getString(&quot;key.one&quot;); //$NON-NLS-1$
-    ...
-    // bind one arg
-    message = MessageFormat.format(Messages.getString(&quot;key.two&quot;), new Object[] {&quot;example usage&quot;}); //$NON-NLS-1$ //$NON-NLS-2$
-    ...
-  }
-}</code></pre>
-<h4>New Code:</h4>
-<pre><code>public class MyClass {
-  public void myMethod() {
-    String message;
-    ...
-    // no args
-    message = Messages.key_one;
-    ...
-    // bind one arg
-    message = NLS.bind(Messages.key_two, &quot;example usage&quot;); //$NON-NLS-1$
-    ...
-  }
-}</code></pre>
-<h3>Messages.java</h3>
-<h4>Old Code:</h4>
-<pre><code>public class Messages {
-  private static final String BUNDLE_NAME = &quot;org.eclipse.core.utils.messages&quot;; //$NON-NLS-1$
-  private static final ResourceBundle bundle = ResourceBundle.getBundle(BUNDLE_NAME);
-   
-  public static String getString(String key) {
-    try {
-      return bundle.getString(key);
-    } catch (MissingResourceException e) {
-      return key;
-    }
-  }
-}</code></pre>
-<h4>New Code:</h4>
-<pre><code>import org.eclipse.osgi.util.NLS;</code></pre>
-<pre><code>public class Messages extends NLS {
-  private static final String BUNDLE_NAME = &quot;org.eclipse.core.utils.messages&quot;; //$NON-NLS-1$
-   
-  public static String key_one;
-  public static String key_two;
-  ...
-  static {
-    NLS.initializeMessages(BUNDLE_NAME, Messages.class);
-  }
-}</code></pre>
-<h3> messages.properties</h3>
-<h4> Old Code:</h4>
-<pre>key.one = Hello world.
-key.two = This is an {0} of binding with one argument.</pre>
-<h4>New Code:</h4>
-<pre>key_one = Hello world.
-key_two = This is an {0} of binding with one argument.</pre>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html
deleted file mode 100644
index 33d51c1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/multi_user_installs.html
+++ /dev/null

@@ -1,140 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse Multi-user Installs</title>
-</head>
-<body text="#000000" bgcolor="#ffffff">
-<h1>Eclipse multi-user installs</h1>
-<p> 
-  Eclipse provides a number of strategies for supporting multi-user installs. 
-  Each strategy satisfies a specific scenario. This document covers these strategies, 
-  describing when each one should be used. The intended readers are product engineers 
-  configuring an Eclipse-based product for distribution, system administrators 
-  setting up Eclipse-based products to be used through a network and developers 
-  interested in creating plug-ins that are good citizens in such setups.</p>
-<p>Last Modified: June 17th, 2005</p>
-<h2>Basic concepts</h2>
-<h3>Locations</h3>
-<p>As described in the <a href="runtime-options.html#locations">Eclipse Runtime 
-  options</a> article, there are three different locations that are important 
-  in the context of deploying Eclipse in a multi-user setup:</p>
-<ul>
-  <li> <strong>install area</strong> - the location where the Eclipse Platform 
-    is installed. This location can be read-only, since neither the Eclipse runtime 
-    nor plug-ins are supposed to write there. However, in a single user scenario, 
-    the configuration area, which is typically writable, defaults to a directory 
-    called &quot;configuration&quot; stored under the install area.</li>
-  <li> <strong>configuration area</strong> - the location where Eclipse stores 
-    essential runtime metadata (such as information about the set of plug-ins 
-    installed and the dependencies between them) and cached data in general. Eclipse 
-    cannot run without a configuration area. Plug-ins may choose to store data 
-    here that should be available regardless the workspace in use (for instance, 
-    help index files). User settings shared across workspaces are also stored 
-    under this location.</li>
-  <li><strong>instance area</strong> - the location where user files are stored, 
-    commonly called the <em>workspace</em>. It is optional, however most Eclipse-based 
-    products require an instance area to work. The instance area cannot be shared, 
-    although a single user might maintain multiple instance areas. Inside the 
-    instance area there is a special directory called .metadata, where plug-ins 
-    store their own workspace-specific metadata and user settings.</li>
-</ul>
-<h3>Configuration initialization</h3>
-<p>Before Eclipse has been run for the first time, the configuration area is basically 
-  an empty directory. This location is gradually populated by the Eclipse runtime, 
-  and other plug-ins, across Eclipse sessions. Most of the metadata kept by the 
-  Eclipse runtime (e.g. plug-in dependencies, the extension registry) is written 
-  during the shutdown of the first session. If no changes are made to the set 
-  of installed plug-ins, no data has to be written during subsequent sessions. 
-  We say the configuration is <em>initialized</em>. When the configuration is 
-  in this state, it is even possible to make the configuration area read-only. 
-  Making the configuration area read-only is useful in scenarios such as shared 
-  configurations (more on this later).</p>
-<p>The <code>-initialize</code> command-line option allows one to initialize the 
-  configuration area without requiring an Eclipse application to run. The initialization 
-  procedure forces the creation of any metadata that is written out to the configuration 
-  location during the first Eclipse session. However, there are other files kept 
-  in the configuration area that are created only when needed. Examples are:</p>
-<ul>
-  <li>Help indexes - only created for the first time the Eclipse Help system is 
-    opened. After it is created, provided the user locale does not change, no 
-    files are ever written again.</li>
-  <li>files extracted out of plug-in JARs - plug-ins shipped as JARs often need 
-    to access embedded files as plain files on the file system. For that, plug-ins 
-    call the Eclipse Runtime API <code><a href="../api/org/eclipse/core/runtime/Platform.html#asLocalURL(java.net.URL)">
-	Platform.asLocalURL(URL)</a></code>. The result is that 
-    if the URL refers to a file inside a JAR, that file will be extracted to the 
-    file system under the configuration area. Once a file is extracted, subsequent 
-    calls to <code>Platform.asLocalURL()</code> will be able to find it, so no additional extractions 
-    will occur <em>for that file</em>. A similar (actually, the original) scenario 
-    where <code>Platform.asLocalURL</code> is used that has the same consequences relates to 
-    making sure remote contents (for instance, a file accessible via a http URL) 
-    are available locally.</li>
-</ul>
-<p>For these cases (and others that 3rd-party plug-ins might introduce), the initialization 
-  procedure is not sufficient to fully initialize the configuration area. There 
-  will still be need to write to the configuration area although this need tends 
-  to disappear as all the execution paths in the application that cause files 
-  to be created in the configuration area are visited. Only after that it can 
-  be said the configuration area is fully initialized and no write access to it 
-  will ever be required in order for Eclipse to run.</p>
-<h2>Scenario #1 - private install</h2>
-<p>This is actually a single-user scenario. The Eclipse install is used by a single 
-  user, and the user has full access privileges to it. The configuration area 
-  location defaults to the configuration directory under the install location.</p>
-<p>The procedure to set up this scenario requires just making sure the user has 
-  full rights to the install location.</p>
-<h2>Scenario #2 - shared install</h2>
-<p>In this scenario, a single install area is shared by many users. The &quot;configuration&quot; 
-  directory under the install area is home only to the config.ini as shipped with 
-  the product (it is not initialized). Every user has their own local standalone 
-  configuration location.</p>
-<p>The set up for this scenario requires making the install area read-only for 
-  regular users. When users start Eclipse, this causes the configuration area 
-  to automatically default to a directory under the user home dir. If this measure 
-  is not taken, all users will end up using the same location for their configuration 
-  area, which is not supported.</p>
-<h2>Scenario #3 - shared configuration</h2>
-<p>Here users share not only an install area but also a master configuration area. 
-  Users still have, by default, their own private writable configuration areas. 
-  A user's private configuration area is cascaded to the master configuration 
-  and will not contain any interesting data if the master configuration has been 
-  fully initialized and no changes to the set of plug-ins to be installed has 
-  occurred.</p>
-<p>In this scenario, the system administrator initializes the master configuration 
-  (typically under the install location), and ensures the whole install and configuration 
-  areas are read-only to users. When users run the Eclipse-based product from 
-  the shared install location, since they do not have write access privileges 
-  to the configuration area under the install area, a local configuration area 
-  will be automatically computed and initialized.</p>
-<p>The more fully initialized the shared configuration is, the less need there 
-  is for files to be created under the local configuration.</p>
-<h3>Setting the private configuration area location</h3>
-<p>The default location for a private configuration area is:</p>
-<p><code>&lt;user-home-dir&gt;/.eclipse/&lt;product-id&gt;_&lt;product-version&gt;/configuration</code></p>
-<p>The user home dir is determined by the <code>user.home</code> Java system property. 
-  The product id and version are obtained from the product marker file <code>.eclipseproduct</code> 
-  under the Eclipse install.</p>
-<p>A non-default configuration area can be defined by setting the <a href="runtime-options.html#osgiconfigurationarea"><code>osgi.configuration.area</code></a> 
-  system property. This property can be set by the end user, but it is more convenient 
-  to set it either in the <a href="runtime-options.html#launcher">launcher .ini 
-  file</a> or in the config.ini file at the base configuration location.</p>
-<h3>Updating</h3>
-<h4>Shared configuration</h4>
-<p>Plug-ins can be installed in/removed from the shared configuration. Users will 
-  catch up with those changes the next time Eclipse runs. It is necessary to make 
-  sure users having the shared configuration as their master configuration are 
-  not running Eclipse.</p>
-<h4>Private configuration</h4>
-<p>Users can modify their local configuration areas by installing additional plug-ins. 
-  This does not cause any changes to the shared configuration, so other users 
-  will not see the changes. Note that plug-ins configured at the shared configuration 
-  <em>cannot</em> be removed. If they are, they will be reinstalled the next time 
-  the platform starts.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html
deleted file mode 100644
index f58192f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/naming.html
+++ /dev/null

@@ -1,222 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Eclipse Platform - Naming Conventions</title>
-</head>
-<body>
-<h1>
-Eclipse Platform<br>
-Naming Conventions</h1>
-<font size=-1>Last revised June 6, 2007</font>
-<p>Naming conventions and guidelines for the Eclipse Platform:</p>
-<ul>
-<li>
-<a href="#Java Packages">Java packages</a></li>
-
-<li>
-<a href="#Classes and Interfaces">Classes and interfaces</a></li>
-
-<li>
-<a href="#Methods">Methods</a></li>
-
-<li>
-<a href="#Variables">Variables</a></li>
-
-<li>
-<a href="#Plug-ins">Plug-ins and extension points</a></li>
-</ul>
-
-<h2>
-<a NAME="Java Packages"></a><b>Java Packages</b></h2>
-The Eclipse Platform consists of a collection of Java packages. The package
-namespace is managed in conformance with <a href="http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html#367">Sun's
-package naming guidelines</a>; subpackages should not be created without
-prior approval from the owner of the package sub-tree. The packages for
-the Eclipse platform are all subpackages <b><tt>org.eclipse</tt></b>. The
-first package name component after <b><tt>org.eclipse</tt></b> is called
-the <i>major </i>package name. The following major packages of <b><tt>org.eclipse</tt></b>
-are assigned in the Eclipse 3.3 release:
-<blockquote><b><tt>org.eclipse.ant[.*]</tt> </b>- Ant support
-<br><b><tt>org.eclipse.compare[.*]</tt></b> - Compare support
-<br><b><tt>org.eclipse.core[.*]</tt> </b>- Platform core
-<br><b><tt>org.eclipse.debug[.*]</tt> </b>- Debug
-<br><b><tt>org.eclipse.equinox[.*]</tt> </b>- Equinox sub-project
-<br><b><tt>org.eclipse.help[.*]</tt></b> - Help support
-<br><b><tt>org.eclipse.jdi[.*]</tt> </b>- Eclipse implementation of Java
-Debug Interface (JDI)
-<br><b><tt>org.eclipse.jdt[.*]</tt> </b>- Java development tools
-<br><b><tt>org.eclipse.jface[.*]</tt> </b>- JFace
-<br><b><tt>org.eclipse.jsch[.*]</tt> </b>- Jsch SSH library support
-<br><b><tt>org.eclipse.ltk[.*]</tt> </b>- Generic language tool infrastructure
-<br><b><tt>org.eclipse.osgi[.*]</tt> </b>- Eclipse API for interacting with OSGi
-<br><b><tt>org.eclipse.pde[.*]</tt></b> - Plug-in Development Environment
-<br><b><tt>org.eclipse.search[.*]</tt></b> - Search support
-<br><b><tt>org.eclipse.swt[.*]</tt> </b>- Standard Widget Toolkit
-<br><b><tt>org.eclipse.team[.*]</tt> </b>- Team support and Version and
-  Configuration Management
-<br><b><tt>org.eclipse.text[.*]</tt> </b>- Text editor framework
-<br><b><tt>org.eclipse.tomcat[.*]</tt> </b>- Apache tomcat support
-<br><b><tt>org.eclipse.ui[.*]</tt></b> - Workbench
-<br><b><tt>org.eclipse.update[.*]</tt></b> - Update/install
-<br><b><tt>org.eclipse.webdav[.*]</tt> </b>- WebDAV support</blockquote>
-The following package name segments are reserved:
-<blockquote><b><tt>internal</tt></b> - indicates an internal implementation
-package that contains no API
-<br><b><tt>tests</tt></b> - indicates a non-API package that contains only
-test suites
-<br><b><tt>examples</tt></b> - indicates a non-API package that contains
-only examples</blockquote>
-These name are used as qualifiers, and must only appear following the major
-package name. For example,
-<blockquote><b><tt>org.eclipse.core.internal.resources</tt></b> - Correct
-usage
-<br><b><tt>org.eclipse.internal.core.resources</tt></b> - Incorrect. <b><tt>internal</tt></b>
-precedes major package name.
-<br><b><tt>org.eclipse.core.resources.internal</tt></b> - Incorrect. <b><tt>internal</tt></b>
-does not immediately follow major package name.</blockquote>
-<p>
-Aside on how the Eclipse Platform is structured: The Eclipse Platform is
-divided up into <i>Core </i>and <i>UI</i>. Anything classified as Core
-is independent of the window system; applications and plug-ins that depend
-on the Core and not on the UI can run headless. The distinction between
-Core and UI does not align with the distinction between API and non-API;
-both Core and UI contain API. The UI portion of the Eclipse Platform is
-known as the Workbench. The Workbench is a high-level UI framework for
-building products with sophisticated UIs built from pluggable components.
-The Workbench is built atop JFace, SWT, and the Platform Core. SWT (Standard
-Widget Toolkit) is a low-level, OS-platform-independent means of talking
-to the native window system. JFace is a mid-level UI framework useful for
-building complex UI pieces such as property viewers. SWT and JFace are
-UI by definition. The Java tooling is a Java IDE built atop the workbench.
-End aside.</p>
-<p><b>API Packages</b>&nbsp; API packages are ones that contain classes
-and interfaces that must be made available to ISVs. The names of API packages
-need to make sense to the ISV. The number of different packages that the
-ISV needs to remember should be small, since a profusion of API packages
-can make it difficult for ISVs to know which packages they need to import.
-Within an API package, all public classes and interfaces are considered
-API. The names of API packages should not contain <b><tt>internal</tt></b>,
-<b><tt>tests</tt></b>,
-or <b><tt>examples</tt></b> to avoid confusion with the scheme for naming
-non-API packages.</p>
-<p><b>Internal Implementation Packages</b>&nbsp; All packages that are
-part of the platform implementation but contain no API that should be exposed
-to ISVs are considered internal implementation packages. All implementation
-packages should be flagged as <b><tt>internal</tt></b>, with the tag occurring
-just after the major package name. ISVs will be told that all packages
-marked <b><tt>internal</tt></b> are out of bounds. (A simple text search
-for "<tt>.internal.</tt>" detects suspicious reference in source files;
-likewise, "/<tt>internal/</tt>" is suspicious in .class files).</p>
-<p><b>Test Suite Packages</b>&nbsp; All packages containing test suites
-should be flagged as <b><tt>tests</tt></b>, with the tag occurring just
-after the major package name. Fully automated tests are the norm; so, for
-example,
-<tt>org.eclipse.core.tests.resources</tt> would contain automated
-tests for API in <tt>org.eclipse.core.resources</tt>. Interactive tests
-(ones requiring a hands-on tester) should be flagged with <b><tt>interactive</tt></b>
-as the <i>last</i> package name segment; so, for example, <tt>org.eclipse.core.tests.resources.interactive</tt>
-would contain the corresponding interactive tests.</p>
-<p><b>Examples Packages</b>&nbsp; All packages containing examples that
-ship to ISVs should be flagged as <b><tt>examples</tt></b>, with the tag
-occurring just after the major package name. For example,
-<tt>org.eclipse.swt.examples</tt>
-would contain examples for how to use the SWT API.</p>
-<p>Additional rules:</p>
-<ul>
-<li>
-Package names should contain only lowercase ASCII alphanumerics, and avoid
-underscore <tt>_</tt> or dollar sign <tt>$</tt> characters.</li>
-</ul>
-
-<h2>
-<a NAME="Classes and Interfaces"></a><b>Classes and Interfaces</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>Class names should be nouns, in mixed case with the first letter
-of each internal word capitalized. Try to keep your class names simple
-and descriptive. Use whole words - avoid acronyms and abbreviations (unless
-the abbreviation is much more widely used than the long form, such as URL
-or HTML).<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; class Raster;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; class ImageSprite;</tt> <br>&nbsp;
-<br>Interface names should be capitalized like class names.</blockquote>
-<p>For interface names, we follow the "I"-for-interface convention: all interface
-names are prefixed with an "<tt>I</tt>". For example, "<tt>IWorkspace</tt>"
-or "<tt>IIndex</tt>". This convention aids code readability by making interface
-names more readily recognizable. (Microsoft COM interfaces subscribe to
-this convention).</p>
-<p>Additional rules:</p>
-<ul>
-<li>
-The names of exception classes (subclasses of <tt>Exception</tt>) should
-follow the common practice of ending in "<tt>Exception</tt>".</li>
-</ul>
-
-<h2>
-<a NAME="Methods"></a><b>Methods</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>Methods should be verbs, in mixed case with the first letter
-lowercase, with the first letter of each internal word capitalized.<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; run();</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; runFast();</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; getBackground();</tt></blockquote>
-Additional rules:
-<ul>
-<li>
-The named of methods should follow common practice for naming getters (<tt>get<i>X</i>()</tt>),
-setters (<tt>set<i>X</i>()</tt>), and predicates (<tt>is<i>X</i>()</tt>,
-<tt>has<i>X</i>()</tt>).</li>
-</ul>
-
-<h2>
-<a NAME="Variables"></a><b>Variables</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>Except for variables, all instance, class, and class constants
-are in mixed case with a lowercase first letter. Internal words start with
-capital letters. Variable names should not start with underscore <tt>_</tt>
-or dollar sign <tt>$ </tt>characters, even though both are allowed.<br>&nbsp;
-<br>Variable names should be short yet meaningful. The choice of a variable
-name should be mnemonic - that is, designed to indicate to the casual observer
-the intent of its use. One-character variable names should be avoided except
-for temporary "throwaway" variables. Common names for temporary variables
-are <tt>i</tt>, <tt>j</tt>, <tt>k</tt>, <tt>m</tt>, and <tt>n</tt> for
-integers; <tt>c</tt>, <tt>d</tt>, and <tt>e</tt> for characters.<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; int i;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; char c;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; float myWidth;</tt></blockquote>
-<p>(Note: we are no longer following the convention that prefixes non-constant
-field names with "<tt>f</tt>", such as "<tt>fWidget</tt>".)</p>
-<h2>
-<a NAME="Constants"></a><b>Constants</b></h2>
-<p><a href="http://java.sun.com/docs/codeconv/index.html">Sun's naming guidelines</a>
-states</p>
-<blockquote>The names of variables declared class constants and of ANSI
-constants should be all uppercase with words separated by underscores (&quot;_&quot;).<br>&nbsp;
-<br>Examples:
-<br><tt>&nbsp;&nbsp;&nbsp; static final int MIN_WIDTH = 4;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; static final int MAX_WIDTH = 999;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; static final int GET_THE_CPU = 1;</tt></blockquote>
-
-<h2>
-<a NAME="Plug-ins"></a><b>Plug-ins and Extension Points</b></h2>
-<p>All plug-ins, including the ones that are part of the Eclipse Platform,
-like the Resources and Workbench plug-ins, must have unique identifiers
-following the same naming pattern as Java packages. For example, workbench
-plug-ins are named <b><tt>org.eclipse.ui[.*]</tt></b>.</p>
-<p>The plug-in namespace is managed hierarchically; do not create plug-in
-without prior approval from the owner of the enclosing namespace.</p>
-<p>Extension points that expect multiple extensions should have plural
-names. For example, "<tt>builders</tt>" rather than "<tt>builder</tt>".
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html
deleted file mode 100644
index 704ff7a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/overview-platform.html
+++ /dev/null

@@ -1,628 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css">
-<title>Map of platform plug-ins</title>
-</head>
-
-<body>
-
-<h1>Map of platform plug-ins</h1>
-<p>The Eclipse Platform provides basic support for plug-ins, resources, and the
-workbench.</p>
-<p>The Eclipse Platform itself is divided up into a number of separate plug-ins.
-The following table shows which API packages are found in which plug-ins as of
-Eclipse 3.5. This table is useful for
-determining which plug-ins a given plug-in should include as prerequisites.</p>
-<center>
-<table border="1" width="80%">
-  <tr>
-    <td><b>API Package</b></td>
-    <td><b>Required plug-in id</b></td>
-    <td>Notes</td>
-  </tr>
-  <tr>
-    <td><tt>org.apache.tools.ant[.*]<br>
-   org.apache.tools.bzip2<br>
-   org.apache.tools.mail<br>
-   org.apache.tools.tar<br>
-   org.apache.tools.zip</tt></td>
-    <td><tt>org.apache.ant</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.apache.lucene[.*]</tt></td>
-    <td><tt>org.apache.lucene</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ant.core</tt></td>
-    <td><tt>org.eclipse.ant.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.compare.patch (split)<br>
-    org.eclipse.compare.rangedifferencer<br></tt></td>
-    <td><tt>org.eclipse.compare.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.compare<br>
-    org.eclipse.compare.contentmergeviewer<br>
-    org.eclipse.compare.patch (split)<br>
-    org.eclipse.compare.structuremergeviewer</tt></td>
-    <td><tt>org.eclipse.compare</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.commands<br>
-    org.eclipse.core.commands.common<br>
-    org.eclipse.core.commands.contexts<br>
-    org.eclipse.core.commands.operations</tt></td>
-    <td><tt>org.eclipse.core.commands</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-  	<td>
-  		<tt>org.eclipse.core.databinding<br>
-  		org.eclipse.core.databinding.conversion<br>
-  		org.eclipse.core.databinding.validation</tt>
-  	</td>
-  	<td><tt>org.eclipse.core.databinding</tt></td>
-  	<td>&nbsp;</td>
-  </tr>
-  <tr>
-  	<td>
-  		<tt>org.eclipse.core.databinding.beans</tt>  		
-  	</td>
-  	<td><tt>org.eclipse.core.databinding.beans</tt></td>
-  	<td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td>
-        <tt>org.eclipse.core.databinding.observable<br>
-  		org.eclipse.core.databinding.observable.list<br>
-  		org.eclipse.core.databinding.observable.map<br>
-  		org.eclipse.core.databinding.observable.masterdetail<br>
-  		org.eclipse.core.databinding.observable.set<br>
-  		org.eclipse.core.databinding.observable.value<br>
-  		org.eclipse.core.databinding.util</tt>
-    </td>
-    <td><tt>org.eclipse.core.databinding.observable</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td>
-        <tt>org.eclipse.core.databinding.property<br>
-  		org.eclipse.core.databinding.property.list<br>
-  		org.eclipse.core.databinding.property.map<br>
-  		org.eclipse.core.databinding.property.set<br>
-  		org.eclipse.core.databinding.property.value</tt>
-    </td>
-    <td><tt>org.eclipse.core.databinding.property</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.expressions</tt></td>
-    <td><tt>org.eclipse.core.expressions</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.filebuffers<br>
-    org.eclipse.core.filebuffers.manipulation</tt></td>
-    <td><tt>org.eclipse.core.filebuffers</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.filesystem<br>
-    org.eclipse.core.filesystem.provider</tt></td>
-    <td><tt>org.eclipse.core.filesystem</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.net.proxy</tt></td>
-    <td><tt>org.eclipse.core.net</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.resources<br>
-    org.eclipse.core.resources.mapping<br>
-    org.eclipse.core.resources.refresh<br>
-    org.eclipse.core.resources.team</tt></td>
-    <td><tt>org.eclipse.core.resources</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.runtime</tt></td>
-    <td><tt>org.eclipse.core.runtime<br>
-    org.eclipse.equinox.registry<br>
-    org.eclipse.equinox.common</tt></td>
-    <td>[<a href="#Note 1">1</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.runtime.dynamichelpers<br>
-    org.eclipse.core.runtime.spi<br>
-    org.eclipse.equinox.http.registry<br></tt></td>
-    <td><tt>org.eclipse.equinox.registry</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.runtime.content</tt></td>
-    <td><tt>org.eclipse.core.contenttype</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.runtime.jobs</tt></td>
-    <td><tt>org.eclipse.core.jobs</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-   <tr>
-    <td><tt>org.eclipse.core.runtime.preferences</tt></td>
-    <td><tt>org.eclipse.equinox.preferences</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt><i>org.eclipse.core.boot (obsolete)<br>
-      org.eclipse.core.runtime.model (obsolete)</i></tt></td>
-    <td><tt>org.eclipse.core.runtime.compatibility</tt></td>
-    <td>[<a href="#Note 2">2</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.core.variables</tt></td>
-    <td><tt>org.eclipse.core.variables</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.debug.core<br>
-    org.eclipse.debug.core.commands<br>
-    org.eclipse.debug.core.model<br>
-    org.eclipse.debug.core.sourcelookup<br>
-    org.eclipse.debug.core.sourcelookup.containers</tt></td>
-    <td><tt>org.eclipse.debug.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.debug.ui<br>
-    org.eclipse.debug.ui.actions<br>
-    org.eclipse.debug.ui.console<br>
-    org.eclipse.debug.ui.contexts<br>
-    org.eclipse.debug.ui.memory<br>
-    org.eclipse.debug.ui.sourcelookup</tt></td>
-    <td><tt>org.eclipse.debug.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.equinox.app</tt></td>
-    <td><tt>org.eclipse.equinox.app</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.equinox.http.jetty<br>
-    org.eclipse.equinox.http.servlet<br></tt></td>
-    <td><tt>org.eclipse.equinox.http.servlet</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.equinox.jsp.jasper<br></tt></td>
-    <td><tt>org.eclipse.equinox.jsp.jasper</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.equinox.jsp.jasper.registry<br></tt></td>
-    <td><tt>org.eclipse.equinox.jsp.jasper.registry</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.equinox.security.auth<br>
-    org.eclipse.equinox.security.auth.credentials<br>
-    org.eclipse.equinox.security.auth.module<br>
-    org.eclipse.equinox.security.storage<br>
-    org.eclipse.equinox.security.storage.provider<br></tt></td>
-    <td><tt>org.eclipse.equinox.security</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.help</tt></td>
-    <td><tt>org.eclipse.help</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.help.browser<br>
-     org.eclipse.help.search<br>
-     org.eclipse.help.server <br>
-     org.eclipse.help.standalone</tt></td>
-    <td><tt>org.eclipse.help.base</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.help.ui<br>
-    org.eclipse.help.ui.browser</tt></td>
-    <td><tt>org.eclipse.help.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr> 
-  <tr>
-    <td><tt>org.eclipse.help.webapp</tt></td>
-    <td><tt>org.eclipse.help.webapp</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.jface<br>
-    org.eclipse.jface.action<br>
-    org.eclipse.jface.action.images<br>
-    org.eclipse.jface.bindings<br>
-    org.eclipse.jface.bindings.keys<br>
-    org.eclipse.jface.bindings.keys.formatting<br>
-    org.eclipse.jface.commands<br>
-    org.eclipse.jface.contexts<br>
-    org.eclipse.jface.dialogs<br>
-    org.eclipse.jface.dialogs.images<br>
-	org.eclipse.jface.fieldAssist<br>
-	org.eclipse.jface.fieldAssist.images<br>
-    org.eclipse.jface.images<br>
-	org.eclipse.jface.layout<br>
-	org.eclipse.jface.menus<br>
-    org.eclipse.jface.operation<br>
-    org.eclipse.jface.preference<br>
-    org.eclipse.jface.preference.images<br>
-    org.eclipse.jface.resource<br>
-    org.eclipse.jface.util<br>
-    org.eclipse.jface.viewers<br>
-    org.eclipse.jface.viewers.deferred<br>
-    org.eclipse.jface.window<br>
-    org.eclipse.jface.wizard<br>
-    org.eclipse.jface.wizard.images</tt></td>
-      <td><tt>org.eclipse.jface</tt></td>
-    <td>[<a href="#Note 3">3</a>]</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.jface.contentassist<br>
-    org.eclipse.jface.contentassist.images<br>
-    org.eclipse.jface.text (split)<br>
-    org.eclipse.jface.text.contentassist<br>
-    org.eclipse.jface.text.formatter<br>
-    org.eclipse.jface.text.hyperlink<br>
-    org.eclipse.jface.text.information<br>
-    org.eclipse.jface.text.link (split)<br>
-    org.eclipse.jface.text.presentation<br>
-    org.eclipse.jface.text.quickassist<br>
-    org.eclipse.jface.text.reconciler<br>
-    org.eclipse.jface.text.revisions<br>
-    org.eclipse.jface.text.rules<br>
-    org.eclipse.jface.text.source (split)<br>
-    org.eclipse.jface.text.source.projection<br>
-    org.eclipse.jface.text.source.projection.images<br>
-    org.eclipse.jface.text.templates (split)<br>
-    org.eclipse.jface.text.templates.persistence</tt></td>
-    <td><tt>org.eclipse.jface.text</tt></td>
-    <td>[<a href="#Note 4">4</a>]</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.jface.text (split)<br>
-    org.eclipse.jface.text.link (split)<br>
-    org.eclipse.jface.text.projection<br>
-    org.eclipse.jface.text.source (split)<br>
-    org.eclipse.jface.text.templates (split)<br>
-    org.eclipse.text.edits<br>
-    org.eclipse.text.undo</tt></td>
-    <td><tt>org.eclipse.text</tt></td>
-    <td>[<a href="#Note 4">4</a>]</td>
-  </tr>
-  <tr>
-  	<td>
-  		<tt>org.eclipse.jface.databinding.dialog<br>
-  		org.eclipse.jface.databinding.preference<br>
-  		org.eclipse.jface.databinding.swt<br>
-  		org.eclipse.jface.databinding.util<br>
-  		org.eclipse.jface.databinding.viewers<br>
-  		org.eclipse.jface.databinding.wizard</tt>
-  	</td>
-  	<td>
-  		<tt>org.eclipse.jface.databinding</tt>
-  	</td>
-  	<td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.jsch.core</tt></td>
-    <td><tt>org.eclipse.jsch.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.jsch.ui</tt></td>
-    <td><tt>org.eclipse.jsch.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ltk.core.refactoring<br>
-    org.eclipse.ltk.core.refactoring.history<br>
-    org.eclipse.ltk.core.refactoring.model<br>
-    org.eclipse.ltk.core.refactoring.participants<br>
-    org.eclipse.ltk.core.refactoring.resource</tt></td>
-    <td><tt>org.eclipse.ltk.core.refactoring</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ltk.ui.refactoring<br>
-    org.eclipse.ltk.ui.refactoring.actions<br>
-    org.eclipse.ltk.ui.refactoring.history<br>
-    org.eclipse.ltk.ui.refactoring.model<br>
-    org.eclipse.ltk.ui.refactoring.resource</tt></td>
-    <td><tt>org.eclipse.ltk.ui.refactoring</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.osgi.event<br>
-    org.eclipse.osgi.framework.console<br>
-    org.eclipse.osgi.framework.eventmgr<br>
-    org.eclipse.osgi.framework.log<br>
-    org.eclipse.osgi.service.datalocation<br>
-    org.eclipse.osgi.service.debug<br>
-    org.eclipse.osgi.service.environment<br>
-    org.eclipse.osgi.service.localization<br>
-    org.eclipse.osgi.service.pluginconversion<br>
-    org.eclipse.osgi.service.resolver<br>
-    org.eclipse.osgi.service.runnable<br>
-    org.eclipse.osgi.service.security<br>
-    org.eclipse.osgi.signedcontent<br>
-    org.eclipse.osgi.service.urlconversion<br>
-    org.eclipse.osgi.storagemanager<br>
-    org.eclipse.osgi.util</tt></td>
-    <td><tt>org.eclipse.osgi</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.search.core.text<br>
-	org.eclipse.search.ui<br>
-	org.eclipse.search.ui.actions<br>
-    org.eclipse.search.ui.text</tt></td>
-    <td><tt>org.eclipse.search</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.swt<br>
-    org.eclipse.swt.accessibility<br>
-    org.eclipse.swt.awt<br>
-    org.eclipse.swt.browser<br>
-    org.eclipse.swt.custom<br>
-    org.eclipse.swt.dnd<br>
-    org.eclipse.swt.events<br>
-    org.eclipse.swt.graphics<br>
-    org.eclipse.swt.layout<br>
-    org.eclipse.swt.printing<br>
-    org.eclipse.swt.program<br>
-    org.eclipse.swt.widgets</tt></td>
-    <td><tt>org.eclipse.ui</tt></td>
-    <td>[<a href="#Note 5">5</a>]</td>
-  </tr>
-  <tr>
-    <td><tt> org.eclipse.swt.ole.win32</tt></td>
-    <td><tt>org.eclipse.swt.win32.win32.x86</tt></td>
-    <td>[<a href="#Note 6">6</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.team.core<br>
-    org.eclipse.team.core.diff<br>
-    org.eclipse.team.core.diff.provider<br>
-    org.eclipse.team.core.history<br>
-    org.eclipse.team.core.history.provider<br>
-    org.eclipse.team.core.mapping<br>
-    org.eclipse.team.core.mapping.provider<br>
-    org.eclipse.team.core.subscribers<br>
-    org.eclipse.team.core.synchronize<br>
-    org.eclipse.team.core.variants</tt></td>
-    <td><tt>org.eclipse.team.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.team.ui<br>
-    org.eclipse.team.ui.history<br>
-    org.eclipse.team.ui.mapping<br>
-    org.eclipse.team.ui.synchronize</tt></td>
-    <td><tt>org.eclipse.team.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.browser</tt></td>
-    <td><tt>org.eclipse.ui.browser</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.cheatsheets</tt></td>
-    <td><tt>org.eclipse.ui.cheatsheets</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.console<br>
-    org.eclipse.ui.console.actions</tt></td>
-    <td><tt>org.eclipse.ui.console</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.editors.text<br>
-      org.eclipse.ui.editors.text.templates<br>
-      org.eclipse.ui.texteditor (split)</tt></td>
-    <td><tt>org.eclipse.ui.editors</tt></td>
-    <td>[<a href="#Note 7">7</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.forms<br>
-    org.eclipse.ui.forms.editor<br>
-    org.eclipse.ui.forms.events<br>
-    org.eclipse.ui.forms.widgets</tt></td>
-    <td><tt>org.eclipse.ui.forms</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.navigator</tt></td>
-    <td><tt>org.eclipse.ui.navigator</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.navigator.resources</tt></td>
-    <td><tt>org.eclipse.ui.navigator.resources</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui (split)<br>
-    org.eclipse.ui.about<br>
-    org.eclipse.ui.actions (split)<br>
-    org.eclipse.ui.activities<br>
-    org.eclipse.ui.application<br>
-    org.eclipse.ui.branding<br>
-    org.eclipse.ui.browser<br>
-    org.eclipse.ui.commands<br>
-    org.eclipse.ui.contexts<br>
-    org.eclipse.ui.dialogs (split)<br>
-	org.eclipse.ui.dnd<br>
-    org.eclipse.ui.fieldassist<br>
-    org.eclipse.ui.handlers<br>
-    org.eclipse.ui.help<br>
-    org.eclipse.ui.intro<br>
-    org.eclipse.ui.keys<br>
-	org.eclipse.ui.menus<br>
-    org.eclipse.ui.model (split)<br>
-    org.eclipse.ui.operations<br>
-    org.eclipse.ui.part (split)<br>
-    org.eclipse.ui.plugin<br>
-    org.eclipse.ui.preferences<br>
-    org.eclipse.ui.presentations<br>
-    org.eclipse.ui.progress<br>
-    org.eclipse.ui.services<br>
-    org.eclipse.ui.splash<br>
-    org.eclipse.ui.statushandlers<br>
-    org.eclipse.ui.swt<br>
-    org.eclipse.ui.testing<br>
-    org.eclipse.ui.themes<br>
-    org.eclipse.ui.views<br>
-    org.eclipse.ui.wizards</tt></td>
-      <td><tt>org.eclipse.ui.workbench</tt></td>
-    <td>[<a href="#Note 8">8</a>,<a href="#Note 9">9</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui (split)<br>
-    org.eclipse.ui.actions (split)<br>
-    org.eclipse.ui.dialogs (split)<br>
-    org.eclipse.ui.ide<br>
-    org.eclipse.ui.ide.dialogs<br>
-	org.eclipse.ui.ide.fileSystem<br>
-	org.eclipse.ui.ide.undo<br>
-    org.eclipse.ui.model (split)<br>
-    org.eclipse.ui.part (split)<br>
-    org.eclipse.ui.views.bookmarkexplorer<br>
-    org.eclipse.ui.views.framelist<br>
-    org.eclipse.ui.views.markers<br>
-    org.eclipse.ui.views.navigator<br>
-    org.eclipse.ui.views.properties<br>
-    org.eclipse.ui.views.tasklist<br>
-    org.eclipse.ui.wizards.datatransfer<br>
-    org.eclipse.ui.wizards.newresource</tt></td>
-    <td><tt>org.eclipse.ui.ide</tt></td>
-    <td>[<a href="#Note 9">9</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.intro.config<br>
-    org.eclipse.ui.intro.contentproviders</tt></td>
-    <td><tt>org.eclipse.ui.intro</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.intro.universal</tt></td>
-    <td><tt>org.eclipse.ui.intro.universal</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.views.contentoutline<br>
-      org.eclipse.ui.views.properties</tt></td>
-    <td><tt>org.eclipse.ui.views</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.ui.contentassist<br>
-      org.eclipse.ui.texteditor (split)<br>
-      org.eclipse.ui.texteditor.link<br>
-      org.eclipse.ui.texteditor.quickdiff<br>
-      org.eclipse.ui.texteditor.rulers<br>
-      org.eclipse.ui.texteditor.spelling<br>
-      org.eclipse.ui.texteditor.templates</tt></td>
-    <td><tt>org.eclipse.ui.workbench.texteditor</tt></td>
-    <td>[<a href="#Note 7">7</a>]</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.update.configurator</tt></td>
-    <td><tt>org.eclipse.update.configurator</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.update.configuration<br>
-    org.eclipse.update.core<br>
-    org.eclipse.update.core.model<br>
-    org.eclipse.update.operations<br>
-    org.eclipse.update.search<br>
-    org.eclipse.update.standalone</tt></td>
-    <td><tt>org.eclipse.update.core</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.eclipse.update.ui</tt></td>
-    <td><tt>org.eclipse.update.ui</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-  <tr>
-    <td><tt>org.osgi.framework<br>
-    org.osgi.service.condpermadmin<br>
-    org.osgi.service.packageadmin<br>
-    org.osgi.service.permissionadmin<br>
-    org.osgi.service.startlevel<br>
-    org.osgi.service.url<br>
-    org.osgi.util.tracker</tt></td>
-    <td><tt>org.eclipse.osgi</tt></td>
-    <td>&nbsp;</td>
-  </tr>
-</table>
-</center>
-
-<p><a name="Note 1">Note 1</a>: 
-The content of the <tt>org.eclipse.core.runtime</tt> package is provided by the following plug-ins:</p>
-<ul><li><tt>org.eclipse.equinox.common</tt></li>
-<li><tt>org.eclipse.equinox.registry</tt></li>
-<li><tt>org.eclipse.core.runtime</tt></li>
-</ul>
-<p>For convenience, plug-ins can continue to specify dependency on the <tt>org.eclipse.core.runtime</tt> 
-plug-in that combines all APIs present in this package. However, to improve modularity, plug-ins are 
-encouraged to list only the required prerequisites.</p>
-
-<p><a name="Note 2">Note 2</a>: These pre-3.0 API packages are obsolete and have been moved to the 
-<tt>org.eclipse.core.runtime.compatibility</tt> plug-in.</p>
-
-<p><a name="Note 3">Note 3</a>: Plug-ins needing access to the JFace API must list <tt>org.eclipse.ui</tt> 
-as a prerequisite plug-in. <tt>org.eclipse.ui</tt> re-exports API from the JFace plug-in. 
-The <tt>org.eclipse.jface</tt>plug-in should never be explicitly listed as a prerequisite.</p>
-
-<p><a name="Note 4">Note 4</a>: Some of the JFace text packages are split between the <tt>org.eclipse.jface.text</tt>
-and the <tt>org.eclipse.text</tt> plug-ins.</p>
-
-<p><a name="Note 5">Note 5</a>: Plug-ins needing access to the SWT API must list <tt>org.eclipse.ui</tt> as 
-a prerequisite plug-in. <tt>org.eclipse.ui</tt> re-exports API from the SWT plug-in. The <tt>org.eclipse.swt</tt> 
-plug-in should never be explicitly listed as a prerequisite.</p>
-
-<p><a name="Note 6">Note 6</a>: The plug-in <tt>org.eclipse.swt.win32.win32.x86</tt> is available on Win32/x86 
-platforms only.</p>
-
-<p><a name="Note 7">Note 7</a>: The <tt>org.eclipse.ui.texteditor</tt> package is split between the 
-<tt>org.eclipse.ui.editors</tt> and the <tt>org.eclipse.ui.workbench.texteditor</tt> plug-ins.</p>
-
-<p><a name="Note 8">Note 8</a>: Plug-ins needing access to the Workbench UI API must list <tt>org.eclipse.ui</tt> 
-as a prerequisite plug-in. <tt>org.eclipse.ui</tt> re-exports API from the <tt>org.eclipse.ui.workbench</tt> plug-in.
-The <tt>org.eclipse.ui.workbench </tt>plug-in should never be explicitly listed as a prerequisite.</p>
-
-<p><a name="Note 9">Note 9</a>: Some of the UI packages are split between the <tt>org.eclipse.ui</tt>
-and the <tt>org.eclipse.ui.ide</tt> plug-ins.</p>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/p2_dropins_format.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/p2_dropins_format.html
deleted file mode 100644
index 917034a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/p2_dropins_format.html
+++ /dev/null

@@ -1,99 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<title>The dropins folder and supported file layouts</title>
-</head>
-<body>
-<h1>The dropins folder and supported file layouts</h1>
-<p>Provisioning operations should generally occur using the software updates dialog,
-or by invoking p2 tools or APIs. However, there are situations where
-scripts need to install plugins and features via file system operations,
-and have the new content dynamically discovered by the system either at
-startup, or while running. To support this kind of low-level
-manipulation of the system, p2 supports the notion of watched
-directories. A watched directory is a place where a user or script can
-drop files and have them discovered by p2. Various policies can be
-applied to watched directories to configure when they are checked for
-new content, and whether to eagerly install discovered content.</p>
-
-<p>The Eclipse platform ships with a default watched directory
-called <code>dropins</code>. The dropins folder is configured to be scanned during
-startup. Thus the dropins folder can be used much like the plugins
-directory was used in the past. A subtle twist on old behavior here is
-that plug-ins and features added to the dropins folder are properly
-installed into the system rather than being forced in. This means p2 has
-an opportunity to confirm that the new plug-in doesn't conflict with
-other installed plug-ins, and it could even go out and fetch any missing
-prerequisites of the newly dropped in plug-ins. This also means you can
-later use the GUI to install extra functionality that depends on the
-plug-ins in the dropins folder, since p2 knows about them and can reason
-about their dependencies. In other words, new plug-ins installed via the
-dropins folder behave exactly like plug-ins installed via the user
-interface.</p>
-
-<h2>Supported file layouts</h2>
-<p>The dropins folder supports a variety of layouts, depending on
-the scale of your application and the desired degree of separation of
-its parts. The simplest layout is to just drop plug-ins in either jar or
-directory format directly into the dropins folder:</p>
-<pre>
-<code>
- eclipse/
-   dropins/
-     org.eclipse.core.tools_1.4.0.200710121455.jar
-     org.eclipse.releng.tools_3.3.0.v20070412/
-       plugin.xml
-       tools.jar
-       ... etc ...
-   ...
-</code>
-</pre>
-<p>You can also drop in the traditional Eclipse application or
-extension layout directly in the dropins folder:</p>
-<pre>
-<code>
- eclipse/
-   dropins/
-     eclipse/
-       features/
-       plugins/
-</code>
-</pre>
-<p>If you have various different components being dropped in, and
-you want to keep them separate, you can add an additional layer of
-folders immediately below the dropins folder that contain traditional
-Eclipse extensions:</p>
-<pre>
-<code>
- eclipse/
-   dropins/
-     emf/
-       eclipse/
-         features/
-         plugins/
-     gef/
-       eclipse/
-         features/
-         plugins/
-     ... etc ...
-</code>
-</pre>
-<p>Finally, you can add link files as in the traditional Eclipse
-links folder:</p>
-<pre>
-<code>
- eclipse/
-   dropins/
-     emf.link
-</code>
-</pre>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/platform-scheme-uri.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/platform-scheme-uri.html
deleted file mode 100644
index f7084d5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/platform-scheme-uri.html
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../../book.css" type="text/css">
-  <title>Generating Metadata</title>
-</head>
-<body>
-<h2>Platform URLs in Eclipse</h2>
-
-<p>Frequently people wonder how to &quot;locate&quot; files in Eclipse. In 80% of the cases, the
-conversation is about things like <code><a href="http://help.eclipse.org/stable/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IFile.html">IFile</a></code>
-and <code><a href="http://help.eclipse.org/stable/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IWorkspace.html">IWorkspace</a></code>. Sometimes it digresses 
-to files available inside bundles and, rarely, it involves the &quot;state location&quot; of a bundle 
-(see the <a href="http://help.eclipse.org/stable/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/runtime/Plugin.html#getStateLocation%28%29">Plugin.getStateLocation()</a> 
-javadoc for more details). Obviously you can use <code><a href="http://help.eclipse.org/stable/topic/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/resources/IResource.html">IResource</a></code> or <code>java.io.File</code>
-to work with files in these places. There is another way, though: platform URI. 
-</p>
-
-<p>There are a few ways to work with the "platform" scheme:</p>
-
-<table border="1">
-<tbody>
-
-<tr><td valign="top">platform:/resource</td>
-<td>It is used to identify a resource located in the workspace. The next path
-segment after &quot;resource&quot; should be the name of a project, which can be
-followed by the folder and/or file we want to locate.</td></tr>
-
-<tr><td valign="top">platform:/plugin</td><td><p>It
-is used to locate a resource available in a plug-in/bundle. One really cool thing about this one is that it doesn't really
-matter if this resource is available in a directory or in a jar file.
-It also doesn't matter if the bundle is installed in a link folder or in the default directory.</p>
-<p>The path segment after &quot;plugin&quot; should be the identifier of the bundle,
-which can be followed by the path of the resource in the bundle.</p></td></tr>
-
-<tr><td valign="top">platform:/fragment</td><td>This
-one is quite similar to &quot;platform:/plugin&quot;, being used to locate
-fragment resources instead of bundle resources. As you are probably
-guessing, the segment after &quot;fragment&quot; should be the fragment's
-identifier.</td></tr>
-
-<tr><td valign="top">platform:/meta</td><td>We can
-use this to access a bundle's stage location. The path segment after
-&quot;meta&quot; should be the bundle's identifier, followed by the path of the
-resource we want to refer to.</td></tr>
-
-<tr><td valign="top">platform:/config</td><td>The &quot;config&quot; segment causes the 
-platform URI to refer to the configuration area of the running Eclipse (usually the <i>eclipse/configuration</i> directory). This can 
-be useful to read the <i>config.ini</i> file, for example.</td></tr>
-
-<tr><td valign="top">platform:/base</td><td>This always 
-refers to the directory of the Eclipse being executed.<br><br>It is interesting to note that, for example, 
-<code>platform:/base/plugins/org.eclipse.mybundle/plugin.xml</code> and <code>platform:/plugin/org.eclipse.mybundle/plugin.xml</code> 
-don't necessarily refer to the same resource. The former is a &quot;pointer&quot; to a <i>plugin.xml</i> file located in a directory 
-<i>plugins/org.eclipse.mybundle</i> under the directory that Eclipse is installed. The latter points to the <i>plugin.xml</i> of the 
-&quot;org.eclipse.mybundle&quot; bundle regardless of where it is installed and whether it is jarred or not.</td></tr>
-</tbody>
-</table>
-
-<p>
-So what can we do with platform URIs? For one, read the contents of the
-resources pointed by them. We may also be able to write to such
-resources or even delete or create them.  
-URIs can be a good fit for APIs that would normally use &quot;plain&quot; paths. Take as 
-an example the <code>icon</code>
-attribute of the extension point below. Because its value is handled as
-a URI, we are allowed to refer to an image located in a different
-bundle.</p>
-
-<blockquote>
-<pre>
-&lt;extension point=&quot;org.eclipse.ui.editorActions&quot;&gt;
-  &lt;editorContribution ...&gt;
-    &lt;action
-          icon=&quot;platform:/plugin/com.myplugin/icons/me.gif&quot;
-          ...
-    /&gt;
-  &lt;/editorContribution&gt;
-&lt;/extension&gt;
-</pre>
-</blockquote>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html
deleted file mode 100644
index 3b50004..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_archive.html
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Plugin-in Archives</title>
-</head>
-<body>
-
-<h1>
-Plug-in Archives</h1>
-Plug-ins and plug-in fragments are individually packaged as separate Java
-.jars. Standard Java jar facilities are used for constructing plug-in archives.
-There is no distinction made between a plug-in archive containing a plug-in
-and one containing a plug-in fragment.
-<p>The recommended convention for naming the plug-in archives is
-<br><tt>&lt;id&gt;_&lt;version&gt;.jar</tt></p>
-<p>Where <tt>&lt;id&gt;</tt> is the plug-in or fragment identifier and <tt>&lt;version&gt;</tt>
-is the full version identifier contained in the respective plugin.xml or
-fragment.xml. Note that this is a recommended convention that minimizes
-chance of collisions, but is not required by the Eclipse architecture.
-For example, the following are valid plug-in archive names:</p>
-<p><tt>org.eclipse.platform_1.0.3.jar</tt>
-<br><tt>org.eclipse.ui.nl_2.0.jar</tt>
-<br><tt>my_plugin.jar</tt></p>
-<p>Internally, each plug-in archive packages all the relevant plug-in or
-fragment files relative to its plug-in or fragment directory (but not including
-the directory path element). The archive has the following structure </p>
-<p><tt>plugin.xml *OR* fragment.xml</tt>
-<br><tt>other plug-in or fragment files and subdirectories</tt>
-<br><tt>META-INF/</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; Java jar manifest and security files</tt>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html
deleted file mode 100644
index ea86bcf..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd.html
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-
-<title>Plug-in manifest dtd</title>
-</head>
-
-
-<body lang="EN-US" style='tab-interval:.5in'>
-
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt;
-&lt;?eclipse version=&quot;3.2&quot;?&gt;
-
-&lt;!ELEMENT plugin (extension-point*, extension*)&gt;
-
-&lt;!ELEMENT fragment (extension-point*, extension*)&gt;
-
-&lt;!ELEMENT extension-point EMPTY&gt;
-&lt;!ATTLIST extension-point
- name                CDATA #REQUIRED
- id                  CDATA #REQUIRED
- schema              CDATA #IMPLIED
-&gt;
-
-&lt;!ELEMENT extension ANY&gt;
-&lt;!ATTLIST extension
- point               CDATA #REQUIRED
- name                CDATA #IMPLIED
- id                  CDATA #IMPLIED
-&gt;
-</pre>
-
-<hr>
-<p><span style='font-size:10.0pt'>Older versions of the plug-in DTD can be found here:</span></p>
-<ul>
-  <li><span style='font-size:10.0pt'>Version <a href="plugin_dtd_30.html">3.0</a></span></li>
-</ul>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd_30.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd_30.html
deleted file mode 100644
index bd155c5..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_dtd_30.html
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-
-<title>Plug-in manifest dtd</title>
-</head>
-
-<body lang="EN-US" style='tab-interval:.5in'>
-
-<p><b>This is an archived version of the document. The current version can be found <a href="plugin_dtd.html">here</a>.</b></p>
-<hr>
-
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt;
-
-&lt;!ELEMENT plugin (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST plugin
- name                CDATA #REQUIRED
- id                  CDATA #REQUIRED
- version             CDATA #REQUIRED
- provider-name       CDATA #IMPLIED
- class               CDATA #IMPLIED
-&gt;
-
-&lt;!ELEMENT fragment (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST fragment
- name                CDATA #REQUIRED
- id                  CDATA #REQUIRED
- version             CDATA #REQUIRED
- provider-name       CDATA #IMPLIED
- plugin-id           CDATA #REQUIRED
- plugin-version      CDATA #REQUIRED
- match               (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
-&gt;
-
-&lt;!ELEMENT requires (import+)&gt;
-&lt;!ELEMENT import EMPTY&gt;
-&lt;!ATTLIST import
- plugin              CDATA #REQUIRED
- version             CDATA #IMPLIED
- match               (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
- export              (true | false) &quot;false&quot;
- optional            (true | false) &quot;false&quot;
-&gt;
-
-&lt;!ELEMENT runtime library+)&gt;
-
-&lt;!ELEMENT library (export*, packages?)&gt;
-&lt;!ATTLIST library
- name                CDATA #REQUIRED
- type                (code | resource) &quot;code&quot;
-&gt;
-
-&lt;!ELEMENT export EMPTY&gt;
-&lt;!ATTLIST export
- name                CDATA #REQUIRED
-&gt;
-
-&lt;!ELEMENT packages EMPTY&gt;
-&lt;!ATTLIST packages
- prefixes            CDATA #REQUIRED
-&gt;
-
-&lt;!ELEMENT extension-point EMPTY&gt;
-&lt;!ATTLIST extension-point
- name                CDATA #REQUIRED
- id                  CDATA #REQUIRED
- schema              CDATA #IMPLIED
-&gt;
-
-&lt;!ELEMENT extension ANY&gt;
-&lt;!ATTLIST extension
- point               CDATA #REQUIRED
- name                CDATA #IMPLIED
- id                  CDATA #IMPLIED
-&gt;
-</pre>
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html
deleted file mode 100644
index 17d2365..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest.html
+++ /dev/null

@@ -1,167 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Plug-in manifest</title>
-</head>
-
-<body>
-
-<h1>Eclipse platform plug-in manifest</h1>
-
-<p><span style='font-size:10.0pt'>Version 3.2 - Last revised May 9, 2006</span></p>
-
-<p>The manifest markup definitions below make use of various naming tokens and
-identifiers. To eliminate ambiguity, here are some production rules for these [are
-referenced in text below]. In general, all identifiers are case-sensitive. </p>
-
-<pre>SimpleToken := sequence of characters from ('a-z','A-Z','0-9','_')
-ComposedToken := SimpleToken | (SimpleToken '.' ComposedToken)
-QualifiedId := ComposedToken '.' SimpleToken
-ExtensionId := SimpleToken | QualifiedId
-ExtensionPointId := SimpleToken | QualifiedId
-ExtensionPointReference := SimpleToken | QualifiedId</pre>
-
-<p>The remainder of this section describes the plugin.xml file structure as a series
-of DTD fragments. File <a href="plugin_dtd.html">plugin.dtd</a> presents the DTD
-definition in its entirety. </p>
-
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt;
-&lt;?eclipse version=&quot;3.2&quot;?&gt;
-&lt;!ELEMENT plugin (extension-point*, extension*)&gt;
-</pre>
-
-<p>The &lt;plugin&gt; element defines the body of the manifest. It optionally contains
-declarations of any new extension points being introduced by the
-plug-in, as well as configuration of functional extensions (configured into
-extension points defined by other plug-ins, or introduced by this plug-in).</p>
-
-<p>The XML DTD construction rule <tt><i>element*</i></tt> means zero
-or more occurrences of the element; <tt><i>element?</i></tt> means zero or
-one occurrence of the element; and <tt><i>element+</i></tt> (used below) means one or more
-occurrences of the element. Based on the &lt;plugin&gt; definition above, this
-means, for example, that a plug-in containing no
-extension point declarations or extension configurations is valid (for example,
-common libraries that other plug-ins depend on). Similarly, a plug-in
-containing only extension configurations and no extension points of
-its own is also valid (for example, configuring classes delivered in other
-plug-ins into extension points declared in other plug-ins). </p>
-
-<p>The Eclipse architecture is based on the notion of configurable extension
-points. The platform itself predefines a set of extension points that cover the
-task of extending the platform and desktop (for example, adding menu actions,
-contributing embedded editor). In addition to the predefined extension points,
-each supplied plug-in can declare additional extension points. By declaring an
-extension point the plug-in is essentially advertising the ability to configure
-the plug-in function with externally supplied extensions. For example, the Page
-Builder plug-in may declare an extension point for adding new Design Time
-Controls (DTCs) into its builder palette. This means that the Page Builder has
-defined an architecture for what it means to be a DTC and has implemented the
-code that looks for DTC extensions that have been configured into the extension
-points. </p>
-
-<pre>&lt;!ELEMENT extension-point EMPTY&gt;  
-&lt;!ATTLIST extension-point 
-  name               CDATA #REQUIRED 
-  id                 CDATA #REQUIRED    
-  schema             CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;extension-point&gt; element has the following attributes:</p>
-
-<ul>
- <li><b>name</b> - user-displayable (translatable) name for the extension point</li>
- <li><b>id</b> - Either a simple id token, or a fully qualified id. Simple id should be
- used unless there is an actual need to specify a fully qualified id.
- <ul>
-  <li>Simple id token should be unique within this plug-in. The simple id token cannot contain dot (.) or 
-  whitespace</li>
-  <li>Qualified id should uniquely identify this extension point among all Eclipse extension points</li>
-  <li>[production rule: ExtensionPointId]</li>
- </ul>
- </li>
- <li><b>schema</b> - schema
-     specification for this extension point. The exact details are being
-     defined as part of the Plug-In Development Environment (PDE). The schema
-     is currently not used at runtime. The reference is a file name relative to
-     the plug-in installation location.</li>
-</ul>
-
-<p>Actual extensions are configured into extension points (predefined, or newly declared
-in this plug-in) in the &lt;extension&gt; section. The configuration
-information is specified as well-formed XML contained between the &lt;extension&gt;
-and &lt;/extension&gt; tags. The platform does not specify the actual form of
-the configuration markup (other than requiring it to be well-formed XML). The
-markup is defined by the supplier of the plug-in that declared the extension
-point. The platform does not actually interpret the configuration markup. It
-simply passes the configuration information to the plug-in as part of the
-extension point processing (at the time the extension point logic queries all
-of its configured extensions). </p>
-
-<pre>&lt;!ELEMENT extension ANY&gt; 
-&lt;!ATTLIST extension 
-  point              CDATA #REQUIRED 
-  id                 CDATA #IMPLIED 
-  name               CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;extension&gt; element has the following attributes: </p>
-<ul>
- <li><b>point</b> - reference to
-     an extension point being configured. The extension point can be one
-     defined in this plug-in or another plug-in
- <ul>
-  <li>[production rule: ExtensionPointReference]</li>
- </ul>
- </li>
- <li><b>id</b> - optional identifier for this extension point configuration instance. This is used
-     by extension points that need to uniquely identify (rather than just enumerate) the specific 
-     configured extensions. Can be specified as either a simple id token, or a fully qualified id
- <ul>
-  <li>Simple id token should be unique within the definition of the declaring plug-in. The simple id 
-  token cannot contain dot (.) or whitespace.</li>
-  <li>Qualified id should uniquely identify this extension among all Eclipse extensions</li>
-  <li>[production rule: ExtensionId]</li>
- </ul>
- </li>
- <li><b>name</b> - user-displayable (translatable) name for the extension</li>
-</ul>
-
-<p><b>Important:</b>
-The content of the &lt;extension&gt; element is declared using the <tt>ANY</tt> rule. 
-This means that any well-formed XML can be specified within the extension
-configuration section (between &lt;extension&gt; and &lt;/extension&gt; tags). </p>
-
-<h2>Fragments</h2>
-<p>Fragments are used to increase the scope of a plug-in.
-An example would be to incorporate data such as messages or labels in another language.</p>
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt; 
-&lt;?eclipse version=&quot;3.2&quot;?&gt;
-&lt;!ELEMENT fragment (extension-point*, extension*)&gt;</pre>
-
-<p>The &lt;extension-point&gt;, and &lt;extension&gt; components of a fragment will be logically added to the hosting plug-in.
-</p>
-
-<h2>Note on the ExtensionId and ExtensionPointId</h2>
-<p> Special processing was added to support backward compatibility for ExtensionId and ExtensionPointId
-that used to contain dots ('.') prior to the version 3.2. Depending on the version specified in 
-the &lt;?eclipse version?&gt; tag:</p>
-<ul>
-<li>If the version is below 3.2, then qualified name = PluginID '.' (ExtensionID | ExtensionPointID)</li>
-</ul>
-<p> This rule applies only to the ExtensionId and ExtensionPointId that contain dot ('.') character(s).</p>
-
-<hr>
-<p><span style='font-size:10.0pt'>Older versions of the plug-in manifest can be found here:</span></p>
-<ul>
-  <li><span style='font-size:10.0pt'>Version <a href="plugin_manifest_30.html">3.0</a></span></li>
-</ul>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest_30.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest_30.html
deleted file mode 100644
index 2f6905d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/plugin_manifest_30.html
+++ /dev/null

@@ -1,323 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Plug-in manifest</title>
-</head>
-
-<body>
-
-<h1>Eclipse platform plug-in manifest</h1>
-
-<p><span style='font-size:10.0pt'>Version 3.0 - Last revised June 24, 2004</span></p>
-
-<p><b>This is an archived version of the document. The current version can be found <a href="plugin_manifest.html">here</a>.</b></p>
-
-<p>The manifest markup definitions below make use of various naming tokens and
-identifiers. To eliminate ambiguity, here are some production rules for these [are
-referenced in text below]. In general, all identifiers are case-sensitive. </p>
-
-<pre>SimpleToken := sequence of characters from ('a-z','A-Z','0-9','_')
-ComposedToken := SimpleToken | (SimpleToken '.' ComposedToken)
-JavaClassName := ComposedToken
-PlugInId := ComposedToken
-PlugInPrereq := PlugInId | 'export' PlugInId
-ExtensionId := SimpleToken
-ExtensionPointId := SimpleToken
-ExtensionPointReference := ExtensionPointID | (PlugInId '.' ExtensionPointId)</pre>
-
-<p>The remainder of this section describes the plugin.xml file structure as a series
-of DTD fragments. File <a href="plugin_dtd_30.html">plugin.dtd</a> presents the DTD
-definition in its entirety. </p>
-
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt;
-&lt;!ELEMENT plugin (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST plugin
-  name                CDATA #REQUIRED
-  id                  CDATA #REQUIRED
-  version             CDATA #REQUIRED 
-  provider-name       CDATA #IMPLIED
-  class               CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;plugin&gt; element defines the body of the manifest. It optionally contains
-definitions for the plug-in runtime, definitions of other plug-ins required by
-this one, declarations of any new extension points being introduced by the
-plug-in, as well as configuration of functional extensions (configured into
-extension points defined by other plug-ins, or introduced by this plug-in).
-&lt;plugin&gt; attributes are as follows: </p>
-
-<ul>
- <li><b>name</b> - user displayable (translatable) name for the plug-in</li>
- <li><b>id</b> - unique identifier for the plug-in.
- <ul>
-  <li>To minimize potential for naming collisions, the identifier should be derived
-      from the internet domain id of the supplying provider (reversing the domain name
-      tokens and appending additional name tokens separated by dot [.]). For example,
-      provider ibm.com could define plug-in identifier com.ibm.db2</li>
-  <li>[production rule: PlugInId]</li>
- </ul></li>
- <li><b>version</b> - plug-in
-     version number. See org.eclipse.core.runtime.PluginVersionIdentifier for
-     details. Plug-in version format is <b>major.minor.service.qualifier</b>.
-     Change in the major component is interpreted as an incompatible version
-     change. Change in the minor component is interpreted as a compatible
-     version change. Change in the service component is interpreted as <i>cumulative</i>
-     service applied to the minor version. Change in the qualifier component is interpreted as
-     different source code control version of the same component.</li>
- <li><b>provider-name</b> - user-displayable name of the provider supplying the plug-in.</li>
- <li><b>class</b> - name of the
-     plug-in class for this plug-in. The class must be a subclass of
-     org.eclipse.core.runtime.Plugin.</li>
-</ul>
-
-<p>The XML DTD construction rule <tt><i>element*</i></tt> means zero
-or more occurrences of the element; <tt><i>element?</i></tt> means zero or
-one occurrence of the element; and <tt><i>element+</i></tt> (used below) means one or more
-occurrences of the element. Based on the &lt;plugin&gt; definition above, this
-means, for example, that a plug-in containing only a run-time definition and no
-extension point declarations or extension configurations is valid (for example,
-common libraries that other plug-ins depend on). Similarly, a plug-in
-containing only extension configurations and no runtime or extension points of
-its own is also valid (for example, configuring classes delivered in other
-plug-ins into extension points declared in other plug-ins). </p>
-
-<p>The &lt;requires&gt; section of the manifest declares any dependencies on other plug-ins.</p>
-
-<pre>&lt;!ELEMENT requires (import+)&gt;
-&lt;!ELEMENT import EMPTY&gt;
-&lt;!ATTLIST import
- plugin               CDATA #REQUIRED
- version              CDATA #IMPLIED
- match                (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
- export               (true | false) &quot;false&quot;
- optional             (true | false) &quot;false&quot;
-&gt;</pre>
-
-<p>Each dependency is specified using an &lt;import&gt; element. It contains the
-following attributes: </p>
-
-<ul>
- <li><b>plugin</b> - identifier of the required plug-in</li>
- <li><b>version</b> - optional version specification</li>
- <li><b>match</b> - version
-     matching rule. Ignored if version attribute is not specified. Determines
-     whether the dependency is satisfied only with a plug-in that has this exact
-     specified version, with a plug-in
-     that has a service or qualifier more recent than this one, with any
-     compatible version (including a more recent minor version of the plug-in)
-     or with any more recent version of this plug-in</li>
- <li><b>export</b> - specifies
-     whether the dependent plug-in classes are made visible (are (re)exported)
-     to users of this plug-in. By default, dependent classes are not exported
-     (are not made visible)</li>
- <li><b>optional</b> - specifies
-     whether or not this dependency will be strictly enforced. If set to &lt;true&gt; and this
-     dependency cannot be satisfied, the dependency will be ignored</li>
-</ul>
-
-<p><a name=runtime></a>The &lt;runtime&gt; section of the manifest contains a
-definition of one or more libraries that make up the plug-in runtime. The
-referenced libraries are used by the platform execution mechanisms (the plug-in
-class loader) to load and execute the correct code required by the plug-in. </p>
-
-<pre>&lt;!ELEMENT runtime (library+)&gt;
-&lt;!ELEMENT library (export*, packages?)&gt;
-&lt;!ATTLIST library
-  name               CDATA #REQUIRED
-  type               (code | resource) &quot;code&quot;
-&gt;
-&lt;!ELEMENT export EMPTY&gt;
-&lt;!ATTLIST export
-  name               CDATA #REQUIRED
-&gt;
-&lt;!ELEMENT packages EMPTY&gt;
-&lt;!ATTLIST packages
-  prefixes           CDATA #REQUIRED
-&gt;</pre>
-
-<p>The &lt;runtime&gt; element has no attributes. </p>
-
-<p>The &lt;library&gt; elements collectively define the plug-in runtime. At least one
-&lt;library&gt; must be specified. Each &lt;library&gt; element has the
-following attributes: </p>
-
-<ul>
- <li><b>name</b> - string
-     reference to a library file or directory containing classes (relative to
-     the plug-in install directory). Directory references must contain trailing
-     file separator.</li>
- <li><b>type</b> - specifies
-     whether this library contains executable code (&lt;code&gt;) or just
-     resources.<span style="mso-spacerun: yes">  </span>If the library is
-     of type &lt;code&gt; accessing anything in this library will cause activation of
-     the plug-in.<span style="mso-spacerun: yes">  </span>Accessing a
-     &lt;resource&gt; will not cause plug-in activation (a potential for significant
-     performance improvement).<span style="mso-spacerun: yes">  </span>It
-     should be noted that specifying a library of type &lt;code&gt; allows it to
-     contain both code and resources.<span style="mso-spacerun: yes"> 
-     </span>But specifying a library of type &lt;resource&gt; assumes it will only be
-     used for resources.</li>
-</ul>
-
-<p>Each &lt;library&gt; element can specify which portion of the library should be
-exported. The export rules are specified as a set of export masks. By default
-(no export rules specified), the library is considered to be private. Each export mask
-is specified using the <b>name</b> attribute, which can have the following values:
-</p>
-<ul>
-  <li><b>*</b> - indicates all contents of library are exported (public)</li>
-  <li><b>package.name.*</b> - indicates
-      all classes in the specified package are exported. The matching rules are
-      the same as in the Java import statement.</li>
- <li><b>package.name.ClassName</b> - fully qualified java class name</li>
-</ul>
-<p>
-<b>Eclipse 2.1 plug-ins only:</b>  Each library can also specify the package prefixes. These are used to enhance 
-  the classloading performance for the plug-in and/or fragment. If the &lt;packages&gt; 
-  element is not specified, then by default the classloading enhancements are 
-  not used. The &lt;packages&gt; element has the following attribute:</p>
-<ul>
- <li><b>prefixes</b> - a comma-separated
-	 list of package prefixes for the runtime library</li>
-</ul>
-
-<p>The platform's architecture is based on the notion of configurable extension
-points. The platform itself predefines a set of extension points that cover the
-task of extending the platform and desktop (for example, adding menu actions,
-contributing embedded editor). In addition to the predefined extension points,
-each supplied plug-in can declare additional extension points. By declaring an
-extension point the plug-in is essentially advertising the ability to configure
-the plug-in function with externally supplied extensions. For example, the Page
-Builder plug-in may declare an extension point for adding new Design Time
-Controls (DTCs) into its builder palette. This means that the Page Builder has
-defined an architecture for what it means to be a DTC and has implemented the
-code that looks for DTC extensions that have been configured into the extension
-points. </p>
-
-<pre>&lt;!ELEMENT extension-point EMPTY&gt;  
-&lt;!ATTLIST extension-point 
-  name               CDATA #REQUIRED 
-  id                 CDATA #REQUIRED    
-  schema             CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;extension-point&gt; element has the following attributes:</p>
-
-<ul>
- <li><b>name</b> - user-displayable (translatable) name for the extension point</li>
- <li><b>id</b> - simple id token,
-     unique within this plug-in. The token cannot contain dot (.) or
-     whitespace.
- <ul>
-  <li>[production rule: ExtensionPointId]</li>
- </ul>
- </li>
- <li><b>schema</b> - schema
-     specification for this extension point. The exact details are being
-     defined as part of the Plug-In Development Environment (PDE). The schema
-     is currently not used at runtime. The reference is a file name relative to
-     the plug-in installation location.</li>
-</ul>
-
-<p>Actual extensions are configured into extension points (predefined, or newly declared
-in this plug-in) in the &lt;extension&gt; section. The configuration
-information is specified as well-formed XML contained between the &lt;extension&gt;
-and &lt;/extension&gt; tags. The platform does not specify the actual form of
-the configuration markup (other than requiring it to be well-formed XML). The
-markup is defined by the supplier of the plug-in that declared the extension
-point. The platform does not actually interpret the configuration markup. It
-simply passes the configuration information to the plug-in as part of the
-extension point processing (at the time the extension point logic queries all
-of its configured extensions). </p>
-
-<pre>&lt;!ELEMENT extension ANY&gt; 
-&lt;!ATTLIST extension 
-  point              CDATA #REQUIRED 
-  id                 CDATA #IMPLIED 
-  name               CDATA #IMPLIED 
-&gt;</pre>
-
-<p>The &lt;extension&gt; element has the following attributes: </p>
-<ul>
- <li><b>point</b> - reference to
-     an extension point being configured. The extension point can be one
-     defined in this plug-in or another plug-in
- <ul>
-  <li>[production rule: ExtensionPointReference]</li>
- </ul>
- </li>
- <li><b>id</b> - optional
-     identifier for this extension point configuration instance. This is used
-     by extension points that need to uniquely identify (rather than just
-     enumerate) the specific configured extensions. The identifier is specified
-     as a simple token unique within the definition of the declaring plug-in.
-     When used globally, the extension identifier is qualified by the plug-in
-     identifier
- <ul>
-  <li>[production rule: ExtensionId]</li>
- </ul>
- </li>
- <li><b>name</b> - user-displayable (translatable) name for the extension</li>
-</ul>
-
-<p><b>Important:</b>
-The content of the &lt;extension&gt; element is declared using the <tt>ANY</tt> rule. 
-This means that any well-formed XML can be specified within the extension
-configuration section (between &lt;extension&gt; and &lt;/extension&gt; tags). </p>
-
-<p>Fragments are used to increase the scope of a plug-in.
-An example would be to incorporate data such as messages or labels in another language.</p>
-<pre>&lt;?xml encoding=&quot;US-ASCII&quot;?&gt; 
-&lt;!ELEMENT fragment (requires?, runtime?, extension-point*, extension*)&gt;
-&lt;!ATTLIST fragment
-  name                CDATA #REQUIRED
-  id                  CDATA #REQUIRED
-  version             CDATA #REQUIRED
-  provider-name       CDATA #IMPLIED
-  plugin-id           CDATA #REQUIRED
-  plugin-version      CDATA #REQUIRED
-  match               (perfect | equivalent | compatible | greaterOrEqual) &quot;compatible&quot;
-&gt;</pre>
-<p>Each fragment must be associated with a specific plug-in.  
-The associated plug-in is identified with &lt;plugin-id&gt;, &lt;plugin-version&gt; and optionally, &lt;match&gt;.
-Note that if this specification matches more than one plug-in, the matching plug-in with the highest version number will be used.
-</p>
-<p>The &lt;requires&gt;, &lt;runtime&gt;, &lt;extension-point&gt;, and &lt;extension&gt; components of a fragment will be logically added to the matching plug-in.
-</p>
-<p>&lt;fragment&gt; attributes are as follows: </p>
-
-<ul>
- <li><b>name</b> - user displayable (translatable) name for the fragment</li>
- <li><b>id</b> - unique identifier for the fragment.
- <ul>
-  <li>To minimize potential
-      for naming collisions, the identifier should be derived from the id of
-      the associated plug-in in addition to something which identifies the
-      scope of this fragment. For example, org.eclipse.core.runtime.nl1 
-      could define a natural language fragment
-      for the org.eclipse.core.runtime plug-in</li>
-  <li>[production rule: PlugInId]</li>
- </ul>
- </li>
- <li><b>version</b> - fragment
-     version number. See org.eclipse.core.runtime.PluginVersionIdentifier for
-     details. Fragment version format is the same as plug-in version format.</li>
- <li><b>provider-name</b> - user-displayable name of the provider
-     supplying the fragment.</li>
- <li><b>plugin-id</b> - matches the id of the associated plug-in</li>
- <li><b>plugin-version</b> - matches the version of the associated plug-in</li>
- <li><b>match</b> - the matching rule used to find an
-     associated plug-in using &lt;plugin-id&gt; and &lt;plugin-version&gt;. See
-     the definition of &lt;match&gt; in the &lt;requires&gt; clause for
-     complete details.</li>
-</ul>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html
deleted file mode 100644
index c713b7e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/project_description_file.html
+++ /dev/null

@@ -1,168 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-  <link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-  <title>Project description file</title>
-</head>
-<body link="#0000FF" vlink="#800080">
-
-<h1 align="left">
-The project description file</h1>
-<b><i>Description:</i></b> When a project is created in the workspace,
-a project description file is automatically generated that describes the
-project.&nbsp; The purpose of this file is to make the project self-describing,
-so that a project that is zipped up or released to a server can be correctly
-recreated in another workspace.&nbsp; This file is always called ".project",
-and is located as a direct member of the project's content area.&nbsp;
-The name of the file is exposed through the static field <tt>DESCRIPTION_FILE_NAME</tt>
-on <tt>org.eclipse.core.resources.IProjectDescription.</tt>
-
-<p>The name, location, and content of this file are part of the workspace
-API.&nbsp; This means they are guaranteed not to change in a way that would
-break existing users of the file.&nbsp; However, the right to add additional
-elements and attributes to the markup is reserved for possible future additions
-to the file.&nbsp; For this reason, clients that read the description file
-contents should tolerate unknown elements and attributes.
-</p>
-
-<p>Clients that modify, delete, or replace the project description file
-do so at their own risk.&nbsp; Projects with invalid or missing description
-files will not be generally usable.&nbsp; If a project with an invalid
-description file is discovered on workspace startup, the project is closed,
-and it will not be possible to open it until the project description file
-has been repaired.&nbsp; The workspace will not generally attempt to automatically
-repair a missing or invalid description file.&nbsp; One exception is that
-missing project description files will be regenerated during workspace
-save and on calls to <tt>IProject.setDescription</tt>.
-</p>
-
-<p>Modifications to the project description file have mostly the same effect
-as changing the project description via <tt>IProject.setDescription</tt>.&nbsp;
-One exception is that adding or removing project natures will not trigger
-the corresponding nature's configure or deconfigure method.&nbsp; Another
-exception is that changes to the project name are ignored.
-</p>
-
-<p>If a new project is created at a location that contains an existing
-project description file, the contents of that description file will be
-honoured as the project description.&nbsp; One exception is that the project
-name in the file will be ignored if it does not match the name of the project
-being created.&nbsp; If the description file on disk is invalid, the project
-creation will fail.
-</p>
-
-<br>&nbsp;
-<p><b><i>Configuration Markup:</i></b></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT projectDescription (name, comment, projects,
-buildSpec, natures, linkedResources)&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT name EMPTY&gt;</tt></p>
-<ul>
-<li>
-<b>name </b>- the name of the project.&nbsp; Ignored if it does match the
-name of the project using this description.&nbsp; Corresponds to <tt>IProjectDescription.getName()</tt>.</li>
-</ul>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT comment EMPTY&gt;</tt></p>
-<ul>
-<li>
-<b>comment</b> - a comment for the project.&nbsp; The comment can have
-arbitrary contents that are not interpreted by the project or workspace.&nbsp;
-Corresponds to <tt>IProjectDescription.getComment()</tt>.</li>
-</ul>
-<tt>&nbsp;&nbsp; &lt;!ELEMENT projects (project)*&gt;</tt>
-<br><tt>&nbsp;&nbsp; &lt;!ELEMENT project EMPTY&gt;</tt>
-<ul>
-<li>
-<b>projects</b> - the names of the projects that are referenced by this
-project.&nbsp; Corresponds to <tt>IProjectDescription.getReferencedProjects().</tt></li>
-</ul>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT buildSpec (buildCommand)*&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT buildCommand (name, arguments)&gt;</tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT name EMPTY&gt;</tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT arguments (dictionary?)&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT dictionary (key, value)*&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT key EMPTY&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT value EMPTY&gt;</tt></p>
-<ul>
-<li><b>buildSpec</b> - the ordered list of build commands for this project.&nbsp;
-Corresponds to <tt>IProjectDescription.getBuildSpec().</tt></li>
-<li><b>buildCommand </b>- a single build commands for this project.&nbsp; Corresponds
-to <tt>org.eclipse.core.resources.ICommand.</tt></li>
-<li><b>name</b> - the symbolic name of an incremental project builder.&nbsp;
-Corresponds to <tt>ICommand.getBuilderName().</tt></li>
-<li><b>arguments</b> - optional arguments that may be passed to the project
-builder.&nbsp; Corresponds to <tt>ICommand.getArguments()</tt>.</li>
-<li><b>dictionary</b> - a list of &lt;key, value&gt; pairs in the argument list.&nbsp;
-Analagous to <tt>java.util.Map.</tt></li>
-</ul>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT natures (nature)*&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT nature EMPTY&gt;</tt></p>
-<ul>
-<li>
-<b>natures </b>- the names of the natures that are on this project.&nbsp;
-Corresponds to <tt>IProjectDescription.getNatureIds().</tt></li>
-<li><b>nature </b>- the name of a single natures on this project.</li>
-</ul>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT linkedResources (link)*&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT link (name, type, location)&gt;</tt></p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT name EMPTY&gt;</tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT type EMPTY&gt;</tt> </p>
-<p><tt>&nbsp;&nbsp; &lt;!ELEMENT location EMPTY&gt;</tt></p>
-
-<ul>
-<li><b>linkedResources</b> - the list of linked resources for this project.</li>
-<li><b>link</b> - the definition of a single linked resource.</li>
-<li><b>name</b> - the project-relative path of the linked resource as it appears in the workspace.</li>
-<li><b>type</b> - the resource type.  Value values are: &quot;1&quot; for a file,
-or &quot;2&quot; for a folder.</li>
-<li><b>location</b> - the local file system path of the target of the linked resource.  Either an
-absolute path, or a relative path whose first segment is the name of a workspace
-path variable.</li>
-<li><b>locationURI</b> - if the file is not in the local file system, this attribute
-contains the absolute URI of the resource in some backing file system.
-</li>
-</ul>
-
-<b><i>Examples: </i></b>The following is a sample project description file.&nbsp;
-The project has a single nature and builder configured, and some project
-references.
-<p><tt>&lt;?xml version="1.0" encoding="UTF-8"?&gt;</tt>
-<br><tt>&lt;projectDescription&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;name&gt;WinterProject&lt;/name&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;comment&gt;This is a cool project.&lt;/comment&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;projects&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;project&gt;org.seasons.sdt&lt;/project&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;project&gt;CoolStuff&lt;/project&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;/projects&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;buildSpec&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;buildCommand&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;name&gt;org.seasons.sdt.seasonBuilder&lt;/name&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;arguments&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;dictionary&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;key&gt;climate&lt;/key&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;value&gt;cold&lt;/value&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;/dictionary&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-&lt;/arguments&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/buildCommand&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;/buildSpec&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;natures&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;nature&gt;org.seasons.sdt.seasonNature&lt;/nature&gt;</tt>
-<br><tt>&nbsp;&nbsp;&nbsp; &lt;/natures&gt;</tt>
-<br><tt>&lt;/projectDescription&gt;</tt>
-<br></p>
-<p><b><i>API Information:</i></b> The contents of the project description
-file map to the <tt>org.eclipse.core.resources.IProjectDescription</tt>
-interface. The project description file can be overwritten by the method
-<tt>IProject.setDescription()</tt>.</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
deleted file mode 100644
index 8c31990..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html
+++ /dev/null

@@ -1,955 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse runtime options</title>
-</head>
-
-<body>
-
-<h1>The Eclipse runtime options</h1>
-<p>Version 3.6 - Last revised August 5, 2009</p>
-<p>The Eclipse platform is highly configurable. Configuration input takes the
-  form of command line arguments and System property settings. In many cases
-  the command line arguments are simply short cuts for setting the related System
-  properties. In fact, there are many more System property settings than command
-line arguments. </p>
-<h2><a name="commandline"></a>Command line arguments </h2>
-<p>Listed below are the command line arguments processed by various parts of
-  the Eclipse runtime. Many of these values can also be specified using System
-  properties either on the command line using -D VM arguments, by specifying
-  their values in a config.ini file or by using a &lt;launcher&gt;.ini file.
-  Using the two latter techniques it is possible to customize your Eclipse without
-  using command line arguments at all.</p>
-<p>For each argument in the list, its corresponding System property key is given
-  (in {}). Also given is the Eclipse runtime layer in which the command line
-  argument is processed (in ()). This is useful for people replacing parts of
-  the runtime to suit special needs.</p>
-<dl>
-  <dt>-application &lt;id&gt; (Runtime)</dt>
-  <dd>equivalent to setting  <a href="#eclipseapplication">eclipse.application</a>
-    to &lt;id&gt;</dd>
-  <dt>-arch &lt;architecture&gt; (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiarch">osgi.arch</a> to &lt;architecture&gt;</dd>
-  <dt>-clean (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiclean">osgi.clean</a> to &quot;true&quot;</dd>
-  <dt>-configuration &lt;location&gt;   (Main)</dt>
-  <dd>equivalent to setting <a href="#osgiconfigurationarea">osgi.configuration.area</a>
-    to &lt;location&gt;</dd>
-  <dt>-console [port] (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiconsole">osgi.console</a> to [port].</dd>
-  <dt>-consoleLog (Runtime)</dt>
-  <dd>equivalent to setting <a href="#eclipseconsolelog">eclipse.consoleLog</a> to
-    &quot;true&quot;</dd>
-  <dt>-data &lt;location&gt;    (OSGi)<br>
-  </dt>
-  <dd>equivalent to setting <a href="#osgiinstancearea">osgi.instance.area</a>
-    to &lt;location&gt;</dd>
-  <dt>-debug [options file] (OSGi)</dt>
-  <dd> equivalent to setting <a href="#osgidebug">osgi.debug</a> to [options
-    file] or the empty string to simply enable debug (i.e., if the options file
-    location is not specified)</dd>
-  <dt>-dev [entries] (OSGi)</dt>
-  <dd>equivalent to setting <a href="#osgidev">osgi.dev</a> to [entries] or
-    the empty string to simply enable dev mode (i.e., if entries are not specified)</dd>
-  <dt>-eclipse.keyring &lt;file path&gt;    (Equinox)</dt>
-  <dd>Set to override location of the default secure storage</dd>
-  <dt>-eclipse.password &lt;file path&gt;    (Equinox)</dt>
-  <dd>If specified, the secure storage treats contents of the file as a default password. 
-    When not set, password providers are used to obtain a password.</dd>
-  <dt>-feature &lt;feature id&gt;    (Runtime)</dt>
-  <dd>equivalent to setting  <a href="#eclipseproduct">eclipse.product</a>
-    to &lt;feature id&gt;</dd>
-  <dt>-framework &lt;location&gt; (Main) </dt>
-  <dd>equivalent to setting  <a href="#o.pngramework">osgi.framework</a> to
-    &lt;location&gt;</dd>
-  <dt>-initialize (Main)</dt>
-  <dd>initializes the configuration being run. All runtime related data structures
-    and caches are refreshed. Any user/plug-in defined configuration data is
-    not purged. No application is run, any product specifications are ignored
-    and no UI is presented (e.g., the splash screen is not drawn)</dd>
-  <dt>-install &lt;location&gt; (Main)</dt>
-  <dd>equivalent to setting  <a href="#osgiinstallarea">osgi.install.area</a> to
-    &lt;location&gt;</dd>
-  <dt>-keyring &lt;location&gt; (Runtime)</dt>
-  <dd>the location of the authorization database on disk. This argument has to
-    be used together with the -password argument. </dd>
-  <dt>--launcher.library &lt;location&gt; (Executable)</dt>
-  <dd>the location of the eclipse executable's companion shared
-library.&nbsp; If not specified the executable looks in the plugins
-directory for the appropriate org.eclipse.equinox.launcher.[platform]
-fragment with the highest version and uses the shared library named
-eclipse_* inside.</dd>
-  <dt>--launcher.ini &lt;location&gt; (Executable)</dt>
-  <dd>the location of the product .ini file to use.&nbsp; If not
-specified the executable will look for a file beside the launcher with
-the same name and the extension .ini.&nbsp; (ie eclipse.exe looks for
-eclipse.ini, product.exe looks for product.ini)</dd>
-  <dt>--launcher.suppressErrors (Executable)</dt>
-  <dd>If specified the executable will not display any error or message
-dialogs.&nbsp; This is useful if the executable is being used in an
-unattended situation.</dd>
-  <dt>--launcher.secondThread (Executable)&nbsp; <span
- style="font-style: italic;">MACOSX ONLY</span></dt>
-  <dd>If specified the executable will create the Java VM on a
-secondary thread.&nbsp; This should used if a swing application is
-being run. <span style="font-weight: bold;">SWT will NOT work</span>
-if this option is specified.</dd>
-  <dt>--launcher.XXMaxPermSize &lt;value&gt; (Executable)</dt>
-  <dd>If specified, and the executable detects that the VM being used
-is a Sun VM, then the launcher will automatically add the
--XX:MaxPermSize=&lt;value&gt; vm argument.&nbsp; The executable is not
-capable of detecting Sun VMs on all platforms.<br>
-  </dd>
-  <dt>-name &lt;string&gt;</dt>
-  <dd>The name to be displayed in task bar item when the application starts up. When not set, the name is the name of the executable.</dd>
-  <dt>-nl &lt;locale&gt; (OSGi)</dt>
-  <dd>equivalent to setting <a href="#osginl">osgi.nl</a> to &lt;locale&gt;</dd>
-  <dt>-noExit (OSGi)</dt>
-  <dd>equivalent to setting <a href="#osginoshutdown">osgi.noShutdown</a> to &quot;true&quot;</dd>
-  <dt>-noLazyRegistryCacheLoading (Runtime) </dt>
-  <dd>equivalent to setting <a href="#eclipsenolazyregistrycacheloading">eclipse.noLazyRegistryCacheLoading</a>
-    to &quot;true&quot;</dd>
-  <dt>-noRegistryCache
-    (Runtime) </dt>
-  <dd>equivalent to setting  <a href="#eclipsenoregistrycache">eclipse.noRegistryCache</a>
-  to &quot;true&quot;</dd>
-  <dt>-noSplash (Executable, Main)</dt>
-  <dd>controls whether or not the splash screen is shown</dd>
-  <dt>-os &lt;operating system&gt; (OSGi) </dt>
-  <dd>equivalent to setting  <a href="#osgios">osgi.os</a> to &lt;operating system&gt;</dd>
-  <dt>-password &lt;password&gt; (Runtime) </dt>
-  <dd>the password for the authorization database </dd>
-  <dt> -pluginCustomization &lt;location&gt; (Runtime) </dt>
-  <dd>equivalent to setting <a href="#eclipseplugincustomization">eclipse.pluginCustomization</a> to
-  &lt;location&gt;</dd>
-  <dt> -product &lt;id&gt; (OSGi) </dt>
-  <dd>equivalent to setting  <a href="#eclipseproduct">eclipse.product</a> to
-  &lt;id&gt;</dd>
-  <dt>-showSplash &lt;bitmap&gt; (Executable, Main)
-  </dt>
-  <dd>specifies the bitmap to use in the splash screen. If specified,
-the launcher may be able to show the splash screen before starting the
-Java VM.&nbsp; If not specified, Main will find the bitmap using the
-osgi.splashLocation and osgi.splashPath properties.<br>
-  </dd>
-  <dt>-startup &lt;location&gt; (Executable)</dt>
-  <dd>The location of jar used to startup eclipse. The jar referred to
-should have the Main-Class attribute set to
-org.eclipse.equinox.launcher.Main. If this parameter is not set, the
-executable will look in the plugins directory for
-theorg.eclipse.equinox.launcher bundle with the highest version.<br>
-  </dd>
-  <dt>-user &lt;location&gt; (OSGi) </dt>
-  <dd>equivalent to setting <a href="#osgiuserarea">osgi.user.area</a> to &lt;location&gt;</dd>
-  <dt>-vm &lt;path to java vm&gt; (Executable, Main) </dt>
-  <dd>when passed to the Eclipse executable, this option is used to
-locate the Java VM to use to run Eclipse. It should be the full file
-system path to an appropriate: Java jre/bin directory, Java Executable,
-Java shared library (jvm.dll or libjvm.so), or a Java VM Execution
-Environment description file.&nbsp; If not specified,
-the Eclipse executable uses a search algorithm to locate a suitable VM.
-In any event, the executable then passes the path to the actual VM used
-to Java Main using the -vm argument. Java Main then stores this value
-in <a href="#eclipsevm">eclipse.vm</a>.</dd>
-  <dt>-vmargs [vmargs*] (Executable,
-    Main) </dt>
-  <dd>when passed to the Eclipse, this option is used to customize the operation
-    of the Java VM to use to run Eclipse. If
-    specified, this option must come at the end of the command line. Even if
-    not specified on the executable command line, the executable will automatically
-    add the relevant arguments (including the class being launched) to the command
-    line passed into Java using the -vmargs argument.
-    Java Main then stores this value in <a href="#eclipsevmargs">eclipse.vmargs</a>.</dd>
-  <dt>-ws &lt;window system&gt; (OSGi) </dt>
-  <dd>equivalent to setting  <a href="#osgiws">osgi.ws</a> to &lt;window system&gt;</dd>
-</dl>
-<h3>Obsolete command line arguments </h3>
-<p>The following command line arguments are no longer relevant or have been superceded
-  and are consumed by the runtime and not passed on to the application being
-  run to maintain backward compatibility. .</p>
-<dl>
-  <dt> -boot</dt>
-  <dd>see -configuration</dd>
-  <dt>-classLoaderProperties</dt>
-  <dd>no longer relevant</dd>
-  <dt>-endSplash &lt;command&gt; <br>
-  </dt>
-  <dd>no longer relevant<br>
-  </dd>
-  <dt>-firstUse</dt>
-  <dd>no longer relevant</dd>
-  <dt>-newUpdates</dt>
-  <dd>no longer relevant</dd>
-  <dt>-noPackagePrefixes</dt>
-  <dd>no longer relevant</dd>
-  <dt>-noUpdate</dt>
-  <dd>no longer relevant</dd>
-  <dt>-plugins</dt>
-  <dd>no longer relevant</dd>
-  <dt>-update</dt>
-  <dd>no longer relevant</dd>
-</dl>
-<h3>Others</h3>
-<p>The following command line arguments are defined by various Eclipse plug-ins
-  and are only supported if the defining plug-in is installed, resolved and activated.</p>
-<dl>
-  <dt>-noVersionCheck (workbench)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-perspective (workbench)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-refresh (org.eclipse.core.resources)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-showLocation (org.eclipse.ui.ide.workbench)</dt>
-  <dd>&lt;description&gt;</dd>
-  <dt>-allowDeadlock</dt>
-  <dd>&lt;description&gt;</dd>
-</dl>
-<h2>System properties</h2>
-<p>The following System properties are used by the Eclipse runtime. Note that
-  those starting with &quot;osgi&quot; are specific to the OSGi framework implementation
-  while those starting with &quot;eclipse&quot; are particular to the Eclipse
-  runtime layered on top of the OSGi framework. </p>
-<p>Many of these properties have command line equivalents (see the <a href="#commandline">command
-    line arguments</a> section and the value in braces {}). Users are free to
-    use either command line or property settings to specify a value. Properties
-    can
-    be set
-  in
-  the
-  following
-  ways:</p>
-<ul>
-  <li>use -DpropName=propValue as a VM argument to the Java VM</li>
-  <li>set the desired property in the config.ini file in the appropriate configuration
-    area</li>
-</ul>
-<dl>
-  <dt><a name="activateRuntimePlugins" id="activateRuntimePlugins"></a>eclipse.activateRuntimePlugins</dt>
-  <dd>controls activation of runtime plug-ins. RCP applications not requiring services provided by runtime 
-    plug-ins can set this property to &quot;false&quot; to avoid activation of runtime plug-ins on Eclipse startup</dd>
-  <dt><a name="eclipseallowAppRelaunch" id="eclipseallowAppRelaunch"></a>eclipse.allowAppRelaunch</dt>
-  <dd>if set to &quot;true&quot; then the main thread will continue to  wait for another application descriptor to be 
-  launched after the currently running application has quit.  Stopping the system.bundle (i.e. the bundle with a 
-  bundle ID equel to zero) will force the main thread to stop waiting for another application to launch.  
-  The default value is &quot;false&quot;</dd>
-  <dt><a name="eclipseapplication" id="eclipseapplication"></a>eclipse.application {-application}</dt>
-  <dd>the identifier of the application to run. The value given here overrides
-    any application defined by the product (see <a href="#eclipseproduct">eclipse.product</a>) being run</dd>
-  <dt><a name="eclipseapplicationlaunchdefault" id="eclipseapplicationlaunchdefault"></a>eclipse.application.launchDefault</dt>
-  <dd>Controls launching the default application automatically once the platform is running.  A default application is identified 
-  by the <a href="#eclipseproduct">eclipse.product</a> or the <a href="#eclipseapplication">eclipse.application</a> 
-  options.  The default value is &quot;true&quot;.  Setting this property to &quot;false&quot; will prevent the default 
-  application from launching automatically.  Once the platform is running the main thread will wait for an application to be 
-  launched using an application descriptor service.</dd>
-  <dt><a name="eclipseapplicationregisterDescriptors"  id="eclipseapplicationregisterDescriptors"></a>eclipse.application.registerDescriptors</dt>
-  <dd>Controls registration of application descriptor services for all installed applications.  The default value is 
-  &quot;false&quot;.  If set to &quot;false&quot; only the default application will have an application descriptor service 
-  registered.  If set to &quot;true&quot; then all installed applications will have an application descriptor service registered.</dd>
-  <dt><a name="eclipsecommands" id="eclipsecommands"></a>eclipse.commands</dt>
-  <dd>a new-line separated list of all command-line arguments passed in when launching 
-    Eclipse </dd>
-  <dt><a name="eclipseconsolelog" id="eclipseconsolelog"></a>eclipse.consoleLog</dt>
-  <dd>if &quot;true&quot;, any log output is also sent to Java's System.out (typically
-    back to the command shell if any). Handy when combined with -debug </dd>
-  <dt><a name="eclipsedebugstartuptime" id="eclipsedebugstartuptime"></a>eclipse.debug.startupTime</dt>
-  <dd>the time in milliseconds when the Java VM for this session was started</dd>
-  <dt><a name="eclipseeeinstallverify" id="eclipseeeinstallverify"></a>eclipse.ee.install.verify</dt>
-  <dd>if set to &quot;true&quot; then the framework will check the required execution 
-    environment at bundle install time.  The default value is &quot;false&quot;.</dd>
-  <dt><a name="eclipseexitOnError" id="eclipseexitOnError"></a>eclipse.exitOnError</dt>
-  <dd>if set to &quot;true&quot; then the platform will exit if an unhandled error occurs.  The default value is
-  &quot;true&quot;.</dd>
-  <dt><a name="eclipsegcj" id="eclipsegcj"></a>eclipse.gcj</dt>
-  <dd>An option, if "true", that supresses any warnings Eclipse may provoke when running on GCJ.  See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=191254">bug 191254</a> for details.</dd>
-  <dt><a name="eclipseignoreApp" id="eclipseignoreApp"></a>eclipse.ignoreApp</dt>
-  <dd>if set to &quot;true&quot; then the main launching thread will not start the default application and 
-  will proceed in shutting down the platform and exiting.
-  The default value is &quot;false&quot;.  This is different than the 
-  <a href="#eclipseapplicationlaunchDefault">eclipse.application.launchDefault</a> option because the main thread will 
-  not wait for an application descriptor service to be launched.</dd>
-  <dt><a name="eclipseloglevel" id="eclipseloglevel"></a>eclipse.log.level</dt>
-  <dd>
-    sets the level used when logging messages to the eclipse log.
-    <ul type=disc>
-      <li><b>ERROR</b> - enables logging only ERROR messages.</li>
-      <li><b>WARNING</b> - enables logging of ERROR and WARNING messages.</li>
-      <li><b>INFO</b> - enables logging of ERROR, WARNING and INFO messages.</li>
-      <li><b>ALL</b> - enables logging of all messages (default value)</li>
-    </ul>
-  </dd>
-  <dt><a name="eclipselogbackupmax" id="eclipselogbackupmax"></a>eclipse.log.backup.max</dt>
-  <dd>the max number of backup log files to allow.  The oldest backup log file will be deleted
-     after the max number of backup log files is reached as a result of rotating the log file.
-     The default value is &quot;10&quot;.  A negative or zero value will cause the default
-     value to be used.</dd>
-  <dt><a name="eclipselogsizemax" id="eclipselogsizemax"></a>eclipse.log.size.max</dt>
-  <dd>the max size in Kb that the log file is allowed to grow.  The log file is rotated when
-     the file size exceeds the max size.  The default value is &quot;1000&quot;.
-     A negative value will cause the default value to be used.  A zero value indicates
-     no max log size.</dd>
-  <dt><a name="eclipsenoextensionmunging" id="eclipsenoextensionmunging"></a>eclipse.noExtensionMunging</dt>
-  <dd>if &quot;true&quot;, legacy registry extension are left as-is. By default such extensions
-    are updated to use the new extension point ids found in Eclipse 3.0.</dd>
-  <dt><a name="eclipsenolazyregistrycacheloading" id="eclipsenolazyregistrycacheloading"></a>eclipse.noLazyRegistryCacheLoading {-noLazyRegistryCacheLoading}</dt>
-  <dd>if &quot;true&quot;, the platform's plug-in registry cache loading optimization is
-      deactivated. By default, configuration elements are loaded from the registry
-      cache (when available)
-      only on demand, reducing memory footprint. This option forces the registry
-  cache to be fully loaded at startup. </dd>
-  <dt><a name="eclipsenoregistrycache" id="eclipsenoregistrycache"></a>eclipse.noRegistryCache {-noRegistryCache}</dt>
-  <dd>if &quot;true&quot;, the internal extension registry cache is neither read or written</dd>
-  <dt><a name="eclipseplugincustomization" id="eclipseplugincustomization"></a>eclipse.pluginCustomization {-pluginCustomization}</dt>
-  <dd>the file system location of a properties file containing default settings
-      for plug-in preferences. These default settings override default settings
-      specified in the primary feature. Relative paths are interpreted relative
-  to the current working directory for Eclipse itself.</dd>
-  <dt><a name="eclipseproduct" id="eclipseproduct"></a>eclipse.product {-product}</dt>
-  <dd>the identifier of the product being run. This controls various branding
-  information and what application is used.</dd>
-  <dt><a name="serviceJobs" id="serviceJobs"></a>eclipse.service.jobs</dt>
-  <dd>controls registration of OSGi services. Set to &quot;false&quot; to suppress registration of OSGi 
-    services by the <code>org.eclipse.core.jobs</code> plug-in</dd>
-  <dt><a name="servicePref" id="servicePref"></a>eclipse.service.pref</dt>
-  <dd>Controls registration of OSGi services. Set to &quot;false&quot; to suppress registration of OSGi 
-     services by the <code>org.eclipse.equinox.preferences</code> plug-in</dd>
-  <dt><a name="eclipsestarttime" id="eclipsestarttime"></a>eclipse.startTime</dt>
-  <dd>This property is set at the time Eclipse is started.  The value of this property a string 
-      representation of the value returned by System.currentTimeMillis().  This value is not
-      intended to be set by users.</dd>
-  <dt><a name="eclipsestateSaveDelayInterval" id="eclipsestateSaveDelayInterval"></a>eclipse.stateSaveDelayInterval</dt>
-  <dd>the delay interval (in milliseconds) for persisting state change requests.  The default 
-    is 30000 ms (30 seconds).  State change requests are delayed to prevent massive amounts 
-    of disk writes while performing administrative operations (e.g. installing bundles).  
-    The delay interval is used to wait for a period of inactivity before persisting the 
-    framework state information.</dd>
-  <dt><a name="eclipsesecurity"></a>eclipse.security</dt>
-  <dd>specifies that a security policy and manager should be configured when the framework is launched.  If the launcher is used (org.eclipse.equinox.launcher)
-   and this property is set to any value then the launcher will configure a java.security.Policy that grants all permissions to the launcher
-   and the framework.  When the framework is launched it will use this property to determine the security manager to use.  If set to <b>osgi</b>
-   then the Equinox security manager is used.  This security manager is required to fully support the OSGi Conditional Permission Admin specification.  If
-   the property is set to the empty string then java.lang.SecurityManager will be used; otherwise the property specifies a security manager 
-   class that should be used as the security manager.</dd>
-  <dt><a name="eclipsetracesizemax"></a>eclipse.trace.size.max <span style="font-style: italic;">NEW</span></dt>
-  <dd>the max size in Kb that the trace file is allowed to grow. The trace file is rotated when the file size exceeds the max size. 
-  The default value is "1000". A negative value will cause the default value to be used. A zero value indicates no max trace size.</dd>
-  <dt><a name="eclipsetracebackupmax"></a>eclipse.trace.backup.max <span style="font-style: italic;">NEW</span></dt>
-  <dd>the max number of backup trace files to allow. The oldest backup trace file will be deleted after the max number of backup trace 
-  files is reached as a result of rotating the trace file. The default value is "10". A negative or zero value will cause the default value to be used.</dd>
-  <dt><a name="eclipsevm" id="eclipsevm"></a>eclipse.vm {-vm}</dt>
-  <dd>the path to the Java executable used to run Eclipse. This information is
-  used to construct relaunch command lines.</dd>
-  <dt><a name="eclipsevmargs" id="eclipsevmargs"></a>eclipse.vmargs {-vmargs}</dt>
-  <dd>lists the VM arguments used to run Eclipse. This
-      information is used to construct relaunch command
-  lines.</dd>
-  <dt><a name="equinoxsecurityvm"></a>equinox.security.vm</dt>
-  <dd>If set to &quot;server&quot;, security modules will not attempt to substitute VM's JAAS processing.</dd>
-  <dt><a name="osgiadaptor"></a>osgi.adaptor</dt>
-  <dd>the class name of the OSGi framework adaptor to use.</dd>
-  <dt><a name="osgiarch"></a>osgi.arch {-arch}</dt>
-  <dd>see -arch</dd>
-  <dt><a name="osgibaseconfigurationarea"></a>osgi.baseConfiguration.area</dt>
-  <dd>specifies a base configuration that is used when 
-      <a href="#osgiconfigurationarea">osgi.configuration.area</a> is not specified.</dd>
-  <dt><a name="osgibundlefilelimit"></a>osgi.bundlefile.limit</dt>
-  <dd>specifies a limit on the number of jar files the framework will keep open.  
-      The minimum value allowed is 10.  By default the value is unlimited.</dd>
-  <dt><a name="osgibundles"></a>osgi.bundles</dt>
-  <dd>The comma-separated list of bundles which are automatically installed
-    and optionally started
-     once the system is up and running. Each entry is of the form:<br>
-	 <pre>    &lt;URL | simple bundle location&gt;[@ [&lt;start-level&gt;] [&quot;:start&quot;]]</pre>
-     If the start-level (&gt;0 integer) is omitted then the framework will use the
-     default start level for the bundle. If the &quot;start&quot; tag is added
-     then the bundle will be marked as started after being installed.
-     Simple bundle locations are interepreted as relative to the framework's
-    parent directory.
-     The start-level indicates the OSGi start level at which the bundle should
-  run. If this value is not set, the system computes an appropriate default.  </dd>
-  <dt><a name="osgibundlesdefaultStartLevel"></a>osgi.bundles.defaultStartLevel</dt>
-  <dd>this is the startlevel that all bundles will be set to if installed by Eclipse Update.  
-  Bundles which are specified on the <a href="#osgibundles">osgi.bundles</a> list can specify a particular startlevel.  
-  If they do not specify a startlevel then they default to the value of 
-  osgi.bundles.defaultStartLevel.  The default value of osgi.bundles.defaultStartLevel is 4.</dd>
-  <dt><a name="osgicompatibilitybootdelegation" id="osgicompatibilitybootdelegation"></a>osgi.compatibility.bootdelegation</dt>
-  <dd>if set to &quot;true&quot; then the parent (boot by default) classloader is delegated to as a last resort if a 
-  class or resource cannot be found.  The default value is &quot;true&quot;.</dd>
-  <dt><a name="osgicompatibilityerrorOnFailedStart" id="osgicompatibilityerrorOnFailedStart"></a>osgi.compatibility.errorOnFailedStart</dt>
-  <dd>A bundle may specify a lazy activation policy using the bundle manifest headers Eclipse-LazyStart or Bundle-ActivationPolicy.  According 
-  to the OSGi R4.1 specification, if a bundle with a lazy activation policy fails to start then class loads must still succeed.  Before the OSGi
-  R4.1 specification Eclipse defined the lazy activation policy such that failed starts would cause class loading errors to be thrown.  If 
-  osgi.compatibility.errorOnFailedStart is set to &quot;true&quot; then failed starts will result in class loading errors; otherwise the 
-  activation error is logged and the classes are allowed to load from bundles which failed to start.  The default value is &quot;true&quot;.</dd>
-  <dt><a name="osgicompatibilityeagerStart.LazyActivation" id="osgicompatibilityeagerStart.LazyActivation"></a>osgi.compatibility.eagerStart.LazyActivation</dt>
-  <dd>The OSGi R4.1 specification mandates that all bundles must be marked for start before they are allowed to activate.  This includes bundles 
-  which specify a lazy activation policy.  A new method Bundle.start(options) has been added to allow lazy activated bundles to be activated 
-  according to their lazy activation policy.  Before the OSGi R4.1 specification Eclipse defined the lazy activation policy such that 
-  lazy activated were automatically activated on first class load even though they were not marked for activation.
-  If osgi.compatibility.eagerStart.LazyActivation is set to &quot;true&quot; then bundles with the lazy activation policy will automatically be
-  marked for activation; otherwise bundles with the lazy activation policy must be started with the new Bundle.start(options) method before 
-  being allowed to lazy activate.  The default value is &quot;true&quot;.</dd>
-  <dt><a name="osgicheckConfiguration" id="osgicheckConfiguration"></a>osgi.checkConfiguration</dt>
-  <dd>if set to &quot;true&quot; then timestamps are check in the configuration cache to ensure that the cache 
-  is up to date with respect to the contents of the installed bundles.  The default value is &quot;false&quot;.</dd>
-  <dt><a name="osgiclassloadersingleThreadLoads" id="osgiclassloadersingleThreadLoads"></a>osgi.classloader.singleThreadLoads</dt>
-  <dd>if set to &quot;true&quot; then only one thread is allowed to load a class at a time.  The default value is 
-   &quot;false&quot;.  This option can be used to work around certain VM bugs which can cause deadlock.
-   See <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=121737">bug 121737</a>.  Note that recent 
-   discussions in <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=227587">bug 227587</a> have shown
-   that this option introduces another kind of deadlock.</dd>
-  <dt><a name="osgiclassloaderlock" id="osgiclassloaderlock"></a>osgi.classloader.lock</dt>
-  <dd>
-    the classloader locking strategy to use when defining classes.  The valid types are the following:
-    <ul type=disc>
-      <li><b>classname</b> - lock on the classname.</li>
-      <li><b>classloader</b> - lock on the classloader (default value).</li>
-    </ul>
-    There are cases where bundle cycles may cause class loader deadlock to occur (see 
-    <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=229621">bug 229621</a>).  This option 
-    can be used to work around this deadlock by locking on the class name instead of the class loader
-    when defining a class.  This option should be used with caution because some VMs still lock the 
-    class loader natively (e.g. the Sun VM).  When running on these kinds of VMs deadlock can still 
-    occur because of the VM lock. 
-  </dd>
-  <dt><a name="osgiclassloadercopynatives" id="osgiclassloadercopynatives"></a>osgi.classloader.copy.natives <span style="font-style: italic;">NEW</span></dt>
-  <dd>
-    If set to &quot;true&quot; then native code which is loaded from a bundle will be copied to a unique
-    location on disk each time a class loader asks to load the library from the bundle.  This may be needed in 
-    scenarios where the framework is restarted without shutting down the VM.  The default value is &quot;false&quot;.
-  </dd>
-  <dt><a name="osgiclassloadertype" id="osgiclassloadertype"></a>osgi.classloader.type <span style="font-style: italic;">NEW</span></dt>
-  <dd>
-    If set to &quot;parallel&quot; then a check is done on JavaSE 7 for the ClassLoader#registerAsParallelCapable
-    method and if found then it is called to allow for parallel class loads.  On Java SE 7 this is the preferred 
-    way to avoid class loader deadlock because of cyclic class loaders.
-  </dd>
-  <dt><a name="osgiclean"></a>osgi.clean</dt>
-  <dd>if set to &quot;true&quot;, any cached data used by the OSGi framework and eclipse runtime 
-will be wiped clean.  This will clean the caches used to store bundle 
-dependency resolution and eclipse extension registry data.  Using this option 
-will force eclipse to reinitialize these caches.</dd>
-  <dt><a name="osgiconfigurationcascaded"></a>osgi.configuration.cascaded</dt>
-  <dd>if set to &quot;true&quot;, this configuration is cascaded to a parent
-    configuration.  The parent configuration is specified by the <a href="#osgisharedconfigurationarea">osgi.sharedConfiguration.area</a>. 
-    See the section on <a href="#locations">locations</a> for more details.</dd>
-  <dt><a name="osgiconfigurationarea"></a>osgi.configuration.area {-configuration}</dt>
-  <dd>the configuration location for this run of the platform. The configuration
-    determines what plug-ins will run as well as various other system settings.
-    See the section on <a href="#locations">locations</a>  for
-    more details.</dd>
-  <dt><a name="osgiconfigurationareadefault" id="osgiconfigurationareadefault"></a>osgi.configuration.area.default</dt>
-  <dd>the default configuration location for this run of the platform. The configuration
-    determines what plug-ins will run as well as various other system settings.
-    This value (i.e., the default setting) is only used if no value for the osgi.configuration.area
-    is set. See the section on <a href="#locations">locations</a>  for
-    more details.</dd>
-  <dt><a name="osgiconsole"></a>osgi.console {-console} </dt>
-  <dd>if set to a non-null value, the OSGi console (if installed) is enabled.
-    This is handy for investigating the state of the system.
-    If the value is a suitable integer, it is interpreted as the port on which
-    the console listens and directs its output to the given port.  If the value is 
-    not a suitable interger (including the empty string) then the console will
-    listen to System.in and direct its output to System.out.</dd>
-  <dt><a name="osgiconsoleclass"></a>osgi.console.class</dt>
-  <dd>the class name of the console to run if requested</dd>
-  <dt><a name="osgiconsoleencoding"></a>osgi.console.encoding</dt>
-  <dd>if set then the specified value is used as the encoding for the console (see
-    <a href="#osgiconsole">osgi.console</a>).  If not set then the value of the file.encoding 
-    property is used.  If file.encoding is not set then iso8859-1 is used as the default.
-  </dd>
-  <dt><a name="osgicontextClassLoaderParent"></a>osgi.contextClassLoaderParent</dt>
-  <dd>the classloader type to use as the parent classloader of the context
-    classloader used by the Framework.  The valid types are the following:
-    <ul type=disc>
-      <li><b>app</b> - the application classloader.</li>
-      <li><b>boot</b> - the boot classloader.</li>
-      <li><b>ext</b> - the extension classloader.</li>
-      <li><b>fwk</b> - the framework classloader.</li>
-      <li><b>ccl</b> - the original context classloader 
-     that was set when the framework launched (default value).</li>
-    </ul>
-  </dd>
-  <dt><a name="osgidebug"></a>osgi.debug {-debug}</dt>
-  <dd>if set to a non-null value, the platform is put in debug mode. If the value
-    is a string it is interpreted as the location of the
-    .options file. This file indicates what debug
-    points are
-    available
-    for a plug-in and whether or not they are enabled. If a location is not specified,
-  the platform searches for the .options file under the install directory.</dd>
-  <dt><a name="osgidev"></a>osgi.dev {-dev}</dt>
-  <dd>if set to the empty string, dev mode is simply turned on. This property
-    may also be set to a comma-separated class path entries
-    which are added to
-    the class
-    path of each
-    plug-in or a URL to a Java properties file containing custom classpath additions
-    for a set of plug-ins. For each plug-in requiring a customized dev time classpath
-    the file will contain an entry of the form<br>
-<pre>    &lt;plug-in id&gt;=&lt;comma separated list of classpath entries to add&gt;</pre>
-    where plug-in id &quot;*&quot; matches any plug-in not otherwise mentioned.</dd>
-  <dt><a name="osgifilepermissionscommand"></a>osgi.filepermissions.command</dt>
-  <dd>specifies an optional OS specific command to set file permissions on extracted
-      native code.  On some operating systems it is required that native libraries be 
-      set to executable.  This optional property allows you to specify the command. 
-      For example, on a UNIX style OS you could have the following value:
-      <pre>    osgi.filepermissions.command=&quot;chmod +rx [fullpath]&quot;</pre>
-      The [fullpath] is used to substitute the actual file path by the framework.
-  </dd>
-  <dt><a name="o.pngramework"></a>osgi.framework</dt>
-  <dd>the URL location of the OSGi framework. Useful if the Eclipse install
-  is disjoint. See the section on <a href="#locations">locations</a> for more details. </dd>
-  <dt><a name="o.pngrameworkclasspath"></a>osgi.frameworkClassPath</dt>
-  <dd>a comma separated list of classpath entries for the OSGi framework implementation.
-    Relative locations are interpreted as relateve to the framework location
-    (see <a href="#o.pngramework">osgi.framework</a>)</dd>
-  <dt><a name="osgiframeworkextensions"></a>osgi.framework.extensions</dt>
-  <dd>a comma-separated list of framework extensions.  Each entry is of the form:<br>
-	 <pre>    &lt;simple bundle location&gt;</pre>
-      Simple bundle locations are searched in the parent directory of the 
-      org.eclipse.osgi bundle.  Framework extensions may be used to run Eclipse with a different
-      framework adaptor.  The framework extension may contain an eclipse.properties file to set 
-      system properties.  For example, a framework extension that provides a framework adaptor 
-      implementation can specify what the adaptor class is by setting the 
-      <a href="#osgiadaptor">osgi.adaptor</a> property.</dd>
-  <dt><a name="osgiframeworkshape"></a>osgi.framework.shape</dt>
-  <dd>set to the shape of the Eclipse OSGi Framework implementation.  This property is set when
-  the Eclipse platform is started and is not intended by be set by the user.  The value
-  &quot;jar&quot; indicates that the Eclipse OSGi Framework is contained in a single jar.
-  The value &quot;folder&quot; indicates that the Eclipse OSGi Framework is contained in a 
-  directory.</dd>
-  <dt><a name="osgiframeworklibraryextensions"></a>osgi.framework.library.extensions</dt>
-  <dd>a comma separated list of additional library file extensions that
-    must be searched for.  If not set then only the library name returned by
-    System.mapLibraryName(String) will be used to search.  This is needed for
-    certain operating systems which allow more than one extension for a library. 
-    For example AIX allows library extensions of .a and .so, but
-    System.mapLibraryName(String) will only return names with the .a extension.</dd>
-  <dt><a name="osgiframeworkParentClassloader"></a>osgi.frameworkParentClassloader</dt>
-  <dd>the classloader type to use as the parent classloader for the the Framework.  The valid types are the following:
-    <ul type=disc>
-      <li><b>app</b> - the application classloader.</li>
-      <li><b>boot</b> - the boot classloader.</li>
-      <li><b>ext</b> - the extension classloader.</li>
-      <li><b>current</b> - the classloader used to load the equinox launcher.</li>
-    </ul>
-  </dd>
-  <dt><a name="osgiframeworkactiveThreadType"></a>osgi.framework.activeThreadType</dt>
-  <dd>
-   if set to <b>normal</b> then an active framework thread is started when the framework is launched
-   that monitors the lifecycle of the framework.  This thread is a non-daemon thread and is used to prevent
-   the VM from shutting down when the framework is active and only daemon threads are active in the VM.
-   When the framework is shutdown then the active framework thread will quit which should allow the VM to
-   shutdown as long as no other non-deamon threads are active in the VM.  By default no active framework
-   thread is started when the framework is launched.
-  </dd>
-  <dt><a name="osgiframeworkuseSystemProperties"></a>osgi.framework.useSystemProperties</dt>
-  <dd>controls whether the framework properties are backed by the global System properties 
-    or held privately for each instance of the framework.  By default the framework properties
-    are backed by the System properties (e.g. true).  This property is useful when running 
-    multiple instances of the OSGi Framework within the same VM and each instance has a separate
-    set of configuration properties (e.g. set in the config.ini).</dd>
-  <dt><a name="osgigenericAliases"></a>osgi.genericAliases</dt>
-  <dd>a comma separated list of generic aliases that can be used to map existing manifest 
-    headers onto Eclipse-GenericCapability and Eclipse-GenericRequire manifest headers.  The 
-    osgi.genericAliases property uses the following syntax:
-    <pre>
-  osgi.genericAliases ::= generic-alias ( ',' generic-alias ) *
-  generic-alias       ::= capability-alias ':' require-alias ':' capability-type</pre>
-    For example, to map the OSGi headers Export-Service and Import-Service headers
-    onto Eclipse-GenericCapability and Eclipse-GenericRequire headers you would use 
-    the following value:
-    <pre>  osgi.genericAliases=Export-Service:Import-Service:osgi.service</pre>
-  </dd>
-  <dt><a name="osgihookconfigurators"></a>osgi.hook.configurators</dt>
-  <dd>a comma separated list of hook configurators.  If this property is set then the list of 
-    configurators specified will be the only configurators used.  Any hook configurators 
-    specified in hookconfigurators.properties files will be ignored.</dd>
-  <dt><a name="osgihookconfiguratorsinclude"></a>osgi.hook.configurators.include</dt>
-  <dd>a comma separated list of additional hook configuratiors.  This is helpful for 
-    configuring optional hook configurators.  This option is ignored if the 
-    <a href="#osgihookconfigurators">osgi.hook.configurators</a> option is used.</dd>
-  <dt><a name="osgihookconfiguratorsexclude"></a>osgi.hook.configurators.exclude</dt>
-  <dd>a comma separated list of hook configurators to exclude.  This is helpful for disabling 
-    hook configurators that are specified in hook configurator properties files.  This option 
-    is ignored if the <a href="#osgihookconfigurators">osgi.hook.configurators</a> option is used.</dd>
-  <dt><a name="osgijavaprofile"></a>osgi.java.profile</dt>
-  <dd>a URL to the JRE profile file to use.  The specified URL is read as a Java properties 
-     file.  A JRE profile contains values for the properties org.osgi.framework.system.packages, 
-     org.osgi.framework.bootdelegation and org.osgi.framework.executionenvironment.  If the 
-     osgi.java.profile is not set then a profile is selected based on the 
-     java.specification.version value of the running JRE.</dd>
-  <dt><a name="osgijavaprofilebootdelegation"></a>osgi.java.profile.bootdelegation</dt>
-  <dd>
-    a java profile <a href="#osgijavaprofile">osgi.java.profile</a> may contain a 
-    &quot;org.osgi.framework.bootdelegation&quot; property.  This value may be used to set the system 
-	property &quot;org.osgi.framework.bootdelegation&quot;.  The osgi.java.profile.bootdelegation 
-	indicates the policy for bootdelegation to be used.  The following values are valid 
-	(default is ignore):
-    <ul type=disc>
-      <li><b>ignore</b> - indicates that
-          the &quot;org.osgi.framework.bootdelegation&quot; value in the java profile should be ingored.  
-          The system property &quot;org.osgi.framework.bootdelegation&quot; will be used to 
-          determine which packages should be delegated to boot.
-      </li>
-      <li><b>override</b> - 
-          indicates that the &quot;org.osgi.framework.bootdelegation&quot; in the java profile should 
-          override the system property &quot;org.osgi.framework.bootdelegation&quot;.
-      </li>
-      <li><b>none</b> - 
-          indicates that the &quot;org.osgi.framework.bootdelegation&quot; in the java profile AND 
-          the system properties should be ignored.  This is the most strict option.  
-          Running with this option causes the framework to use the OSGi R4 strict boot 
-          delegation model.
-      </li>
-    </ul>
-  </dd>
-  <dt><a name="osgiinstallarea" id="osgiinstallarea"></a>osgi.install.area {-install}</dt>
-  <dd>the install location of the platform. This setting indicates the location
-    of the basic Eclipse plug-ins and is useful if the Eclipse install is disjoint.
-  See the section on <a href="#locations">locations</a> for more details. </dd>
-  <dt><a name="osgiinstancearea"></a>osgi.instance.area {-data}</dt>
-  <dd>the instance data location for this session. Plug-ins use this location
-    to store their data. For example, the Resources plug-in uses this as the
-    default location for projects (aka the workspace). See the section on <a href="#locations">locations</a> for
-    more details.</dd>
-  <dt><a name="osgiinstanceareadefault" id="osgiinstanceareadefault"></a>osgi.instance.area.default</dt>
-  <dd>the default instance data location for this session. Plug-ins use this
-    location to store their data. For example, the Resources plug-in uses this
-    as the
-    default location for projects (aka the workspace). This value (i.e., the
-    default setting) is only used if no value for the osgi.instance.area
-    is set. See the section on <a href="#locations">locations</a> for
-    more details.</dd>
-  <dt><a name="osgilocking"></a>osgi.locking</dt>
-  <dd>the locking type to use for this run of the platform.  The valid locking types
-  are &quot;java.io&quot;, &quot;java.nio&quot;, and &quot;none&quot;.  The default value is
-  &quot;java.nio&quot; unless the JRE does not support &quot;java.nio&quot; then &quot;java.io&quot;
-  is the default.</dd>
-  <dt><a name="osgimanifestcache"></a>osgi.manifest.cache</dt>
-  <dd>the location where generated manifests are discovered and generated. The
-    default is in the configuration area but the manifest cache can be stored
-    separately.</dd>
-  <dt><a name="osginl"></a>osgi.nl {-nl}</dt>
-  <dd>the name of the locale on which Eclipse platform will run. NL values should
-    follow the standard Java locale naming conventions.</dd>
-  <dt><a name="osginluser"></a>osgi.nl.user</dt>
-  <dd>the name of the locale when the user explicitly adds -nl to the command-line arguments.</dd>
-  <dt><a name="osginoshutdown"></a>osgi.noShutdown {-noExit}</dt>
-  <dd>if &quot;true&quot;, the OSGi Framework will not be shut down after the Eclipse application has ended.  This
-      is useful for examining the OSGi Framework after the Eclipse application has ended.  Note that the VM will terminate
-      if no active non-daemon threads exists. See <a href="#osgiframeworkactiveThreadType">osgi.framework.activeThreadType</a>.</dd>
-  <dt><a name="osgios"></a>osgi.os {-os}</dt>
-  <dd>the operating system value. The value should be one of the operating system
-  names known to Eclipse (e.g., win32, linux, ...). See <tt>org.eclipse.osgi.service.environment.Constants</tt> for known values.</dd>
-  <dt><a name="osgiparentclassloader"></a>osgi.parentClassloader</dt>
-  <dd>the classloader type to use as the parent classloader for all bundles installed
-  in the Framework.  The valid types are the following:
-    <ul type=disc>
-      <li><b>app</b> - the application classloader.</li>
-      <li><b>boot</b> - the boot classloader.</li>
-      <li><b>ext</b> - the extension classloader.</li>
-      <li><b>fwk</b> - the framework classloader.</li>
-    </ul>
-  </dd>
-  <dt><a name="osgirequiredjavaversion"></a>osgi.requiredJavaVersion</dt>
-  <dd>The minimum java version that is required to launch Eclipse.  The default value is
-      &quot;1.4.1&quot;.</dd>
-  <dt><a name="osgiresolvermode"></a>osgi.resolverMode</dt>
-  <dd>the mode used to resolve bundles installed in the Framework.  The default resolver
-      mode is not strict.  The following options are available.
-    <ul type=disc>
-      <li><b>strict</b> - the resolver is in strict mode and will enforce access restriction rules when loading classes and resources from exported packages which specify the x-internal or x-friends directives.</li>
-      <li><b>development</b> - used for development time resolution.  This mode disables certain resolver rules that are not needed at development time.  For example, singleton selection is disabled to allow the development of multiple versions of a singleton bundle</li>
-    </ul>     
-  </dd>
-  <dt><a name="osgi.resolver.usesMode"></a>osgi.resolver.usesMode</dt>
-  <dd>
-    the resolver mode used to resolve <b>uses</b> directives on Export-Package statements.  
-     <ul type=disc>
-      <li><b>aggressive</b> - aggressively seeks a solution with no class space inconsistencies (default value).  This mode may be very expensive depending on the number of bundles and number of duplicate exports in the system.</li>
-      <li><b>tryFirst</b> - only tries the first solution selected by the resolver.  This mode is very fast but may result in unresolved bundles because of class space inconsistencies.</li>
-      <li><b>ignore</b> - ignores all uses directives on exports.  This mode is very fast by may result in inconsistent class spaces in resolved bundles.</li>
-    </ul>
-  </dd>
-  <dt><a name="osgisharedconfigurationarea"></a>osgi.sharedConfiguration.area</dt>
-  <dd>the shared configuration location for this run of the platform.  If the
-  <a href="#osgiconfigurationcascaded">osgi.configuration.cascaded</a> property is set
-  to &quot;true&quot; then shared configuration area is used as the parent configuration.</dd>
-  <dt><a name="osgisignedcontentsupport"></a>osgi.signedcontent.support</dt>
-  <dd>A comma separated list of options for signed content support.  The valid types are the following:
-    <ul type=disc>
-      <li><b>certificate</b> - enables parsing and verification of certificates.</li>
-      <li><b>trust</b> - enables verification of certificate trust.  This option implies
-      &quot;certificate&quot;.</li>
-      <li><b>runtime</b> - enables verification of signed bundle content at runtime.  
-      This option implies &quot;certificate&quot;.</li>
-      <li><b>authority</b> - enables the default authorization engine.  This option implies &quot;certificate&quot; and &quot;trust&quot;..</li>
-      <li><b>all</b> - same as &quot;certificate,trust,runtime,authority&quot;.</li>
-    </ul>
-  </dd>
-  <dt><a name="osgisignedcontenttrustengine"></a>osgi.signedcontent.trust.engine</dt>
-  <dd>
-  A service property key used to identify an implementation of the <b>org.eclipse.osgi.service.security.TrustEngine</b> service.
-  A TrustEngine service should be registered with a unique value for this property to allow selection of the TrustEngine
-  service implementation.  The <b>osgi.signedcontent.trust.engine</b> property can be used as a configuration 
-  property to select particular TrustEngine service implementations at runtime.  If this property is not set then
-  all available TrustEngine services are used at runtime.
-  </dd>
-  <dt><a name="osgisplashlocation"></a>osgi.splashLocation</dt>
-  <dd>the absolute URL location of the splash screen (.bmp file) to to show while
-    starting Eclipse. This property overrides any value set in <a href="#osgisplashpath">osgi.splashPath</a>.</dd>
-  <dt><a name="osgisplashpath"></a>osgi.splashPath</dt>
-  <dd>a comma separated list of URLs to search for a file called splash.bmp.
-  This property is overriden by any value set in <a href="#osgisplashlocation">osgi.splashLocation</a>.</dd>
-  <dt><a name="osgistartlevel"></a>osgi.startLevel</dt>
-  <dd>the start level value the framework will be set to at startup.  The default value is 6.</dd>
-  <dt><a name="osgisupportmultipleHosts"></a>osgi.support.multipleHosts <span style="font-style: italic;">NEW</span></dt>
-  <dd>
-    if set to <b>true</b> then the framework will attempt to attach a fragment to all available host 
-    bundles which satisfy the fragment bundle's Fragment-Host constraint.  The default value is <b>false</b>.
-  </dd>
-  <dt><a name="osgisupportsignatureverify"></a>osgi.support.signature.verify</dt>
-  <dd>This option has been deprecated.  Use <a href="#osgisignedcontentsupport">osgi.signedcontent.support</a> instead.
-  </dd>
-  <dt><a name="osgisupportclasscertificate"></a>osgi.support.class.certificate</dt>
-  <dd>
-   if set to <b>true</b> then the certificates available from a signed bundle are used when defining the classes from 
-   the signed bundle.  The default value is <b>true</b>.
-   This option only takes effect when <a href="#osgisignedcontentsupport">osgi.signedcontent.support</a> is set
-   to <b>certificate</b>.
-  </dd>
-  <dt><a name="osgisyspath"></a>osgi.syspath</dt>
-  <dd>set to the path where the eclipse OSGi Framework (org.eclipse.osgi) implementation 
-  is located.  For example, &quot;&lt;eclipse install path&gt;/eclipse/plugins&quot;.
-  This property is set when the Eclipse platform is started and is not intended by be 
-  set by the user.</dd>
-  <dt><a name="osgiuserarea"></a>osgi.user.area {-user}</dt>
-  <dd>the location of the user area. The user area contains data (e.g., preferences)
-    specific to the OS user and independent of any Eclipse install, configuration
-    or instance. See the section on <a href="#locations">locations</a> for more
-    details.</dd>
-  <dt><a name="osgiuserareadefault" id="osgiuserareadefault"></a>osgi.user.area.default</dt>
-  <dd>the default location of the user area. The user area contains data (e.g.,
-    preferences) specific to the OS user and independent of any Eclipse install,
-    configuration
-    or instance. This value (i.e., the default setting) is only used if no value
-    for the osgi.user.area is set. See the section on <a href="#locations">locations</a> for
-    more details.</dd>
-  <dt><a name="osgiws"></a>osgi.ws {-ws}</dt>
-  <dd>the window system value. The value should be one of the Eclipse window
-    system names known to Eclipse (e.g., win32, motif, ...).</dd>
-</dl>
-<h2><a name="locations"></a>Locations
-</h2>
-<p>The Eclipse runtime defines a number of <i>locations</i> which give plug-in
-  developers context for reading/storing data and Eclipse users a control over
-  the scope of data sharing and visibility. Eclipse defines the following notions
-  of location:</p>
-<dl>
-    <dt>User (-user) {<a href="#osgiuserarea">osgi.user.area</a>} [@none, @noDefault, @user.home, @user.dir,
-      filepath, url]</dt>
-    <dd>User locations are specific to, go figure, users. Typically the user
-      location is based on the value of the Java <code>user.home</code> system
-      property but this can be overridden. Information such as user scoped preferences
-      and login information may be found in the user location.</dd>
-    <dt>Install (-install) {osgi.install.area} [@user.home, @user.dir, filepath,
-      url]</dt>
-    <dd>An install location is where Eclipse itself is installed. In practice
-      this location is the directory (typically &quot;eclipse&quot;) which is
-      the parent of the eclipse.exe being run or the plugins directory containing the org.eclipse.equinox.launcher bundle. This location should
-      be considered read-only to normal users as an install may be shared by
-      many users. It is possible to set the install location and decouple eclipse.exe 
-      from the rest of Eclipse.</dd>
-    <dt>Configuration (-configuration) {osgi.configuration.area} [@none, @noDefault,
-      @user.home, @user.dir, filepath, url]</dt>
-    <dd>Configuration locations contain files which identify and manage the (sub)set
-      of an install to run. As such, there may be many configurations per install.
-      Installs may come with a default configuration area but typical startup
-      scenarios involve the runtime attempting to find a more writable configuration
-      location. </dd>
-    <dt>Instance (-data) {osgi.instance.area} [@none, @noDefault, @user.home,
-      @user.dir, filepath, url]</dt>
-    <dd>Instance locations contain user-defined data artifacts. For example,
-      the Resources plug-in uses the instance area as the workspace location
-      and thus the default home for projects. Other plugins are free to write
-      whatever files they like in this location.</dd>
-</dl>
-<p>While users can set any of these locations, Eclipse will compute reasonable
-  defaults if values are not given. The most common usecase for setting location
-  is the instance area or, in the IDE context, the workspace. To run the default
-  Eclipse configuration on a specific data set you can specify:</p>
-<pre>    eclipse -data c:\mydata</pre>
-<h3>More detail</h3>
-<p>Locations are URLs. For simplicity, file paths are also accepted and automatically
-  converted to file: URLs. For better control and convenience, there are also
-  a number of predefined symbolic locations which can be used. Note that not
-  all combinations of location type and symbolic value are valid. A table below
-  details which combinations are possible. Since the default case is for all
-  locations to be set, valid and writable, some plug-ins may fail in other setups
-  even if they are listed as possible. For example, it is unreasonable to expect
-  a plug-in focused on user data (e.g., the Eclipse Resources plug-in) to do much
-  if the instance area is not defined. It is up to plug-in developers to choose
-  the setups they support and design their function accordingly.</p>
-<dl>
-    <dt>@none</dt>
-    <dd>Indicates that the corresponding location should never be set either
-      explicitly or to its default value. For example, an RCP style application
-      which has no user data may use osgi.instance.area=@none to prevent
-      extraneous files being written to disk. @none must not be followed by any
-      additional path segments.</dd>
-    <dt>@noDefault</dt>
-    <dd>Forces a location to be undefined or explicitly defined (i.e., Eclipse
-      will not automatically compute a default value). This is useful where you
-      want to allow for data in the corresponding location but the Eclipse default
-      value is not appropriate. @noDefault must not be followed by any
-      additional path segments.</dd>
-    <dt>@user.home</dt>
-    <dd>Directs Eclipse to compute a location value relative to the user's home
-      directory. @user.home can be followed
-      by additional path segments. In all cases, the string &quot;@user.home&quot; is
-      simply replaced with the value of the Java &quot;user.home&quot; System
-      property. For example, setting<br>
-      &nbsp;&nbsp;&nbsp;&nbsp;osgi.instance.area=@user.home/myWorkspace<br>
-      results in a value of
-      <br>
-      &nbsp;&nbsp;&nbsp;&nbsp;file:/users/bob/myWorkspace</dd>
-    <dt>@user.dir</dt>
-    <dd>Directs Eclipse to compute a location value relative to the current working
-      directory. @user.dir can be followed
-      by additional path segments. In all cases, the string &quot;@user.dir&quot; is
-      simply replaced with the value of the Java &quot;user.dir&quot; System
-      property. For example, setting<br>
-&nbsp;&nbsp;&nbsp;&nbsp;osgi.instance.area=@user.dir/myWorkspace<br>
-results in a value of <br>
-&nbsp;&nbsp;&nbsp;&nbsp;file:/usr/share/eclipse/myWorkspace</dd>
-</dl>
-<table width="100%" border="0" bgcolor="#FFFFFF">
-  <tr bgcolor="#CCCCCC">
-    <td width="10%">location/value</td>
-    <td width="17%"><div align="center">supports default</div></td>
-    <td width="17%"><div align="center">file/URL</div>
-    </td>
-    <td width="17%"><div align="center">@none</div>
-    </td>
-    <td width="17%"><div align="center">@noDefault</div>
-    </td>
-    <td width="17%"><div align="center">@user.home</div>
-    </td>
-    <td width="17%"><div align="center">@user.dir</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">instance</div>
-    </td>
-    <td><div align="center">yes</div></td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes (default)</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">configuration</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes*</div>
-    </td>
-    <td><div align="center">yes*</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">install</div>
-    </td>
-    <td><div align="center">no</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">no</div>
-    </td>
-    <td><div align="center">no</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-  </tr>
-  <tr>
-    <td bgcolor="#CCCCCC"><div align="center">user</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-    <td><div align="center">yes</div>
-    </td>
-  </tr>
-</table>
-<p>* indicates that this setup is technically possible but pragmatically quite
-  difficult to manage. In particular, without a configuration location the Eclipse
-  runtime may only get as far as starting the OSGi framework.</p>
-
-<h3>Read-only Locations</h3>
-
-<p>
-A location may be specified as a read-only location by appending &quot;.readOnly&quot; 
-to the location property and setting it to the value &quot;true&quot;.  The following properties
-can be used to specify their corresponding locations as read-only:</p>
-    <ul type=disc>
-      <li>
-          osgi.configuration.area.readOnly <a href="#osgiconfigurationarea">osgi.configuration.area</a>
-      </li>
-      <li>
-          osgi.sharedConfiguration.area.readOnly <a href="#osgisharedconfigurationarea">osgi.sharedConfiguration.area</a>
-      </li>
-      <li>
-          osgi.instance.area.readOnly <a href="#osgiinstancearea">osgi.instance.area</a>
-      </li>
-      <li>
-          osgi.user.area.readOnly <a href="#osgiuserarea">osgi.user.area</a>
-      </li>
-    </ul>
-
-<h2><a name="launcher"></a>Launcher ini file</h2>
-<p>
-The eclipse.exe and more generally executables for RCP applications now read their parameters from an associated 
-ini file. This file offers a platform independent way to pass in arguments that previously had to be specified directly on
-the command line such as vm or vm arguments. Although all parameters can be specified in this file, it recommend for maintainability
-and consistency across various installations to only specifiy the vm location and the vm arguments in this ini file and use the config.ini
-file for others.</p>
-
-<h3>File format</h3>
-<p>This file must be named after the executable name (for example, eclipse.exe will read eclipse.ini, whereas launcher.exe will read launcher.ini) and every parameter
-must be specified on a new line in the file. Here is an example of such a file specifying the vm location and some parameters:</p>
-<pre>-vm
-c:/myVm/java.exe
--vmargs
--Dms40M
-</pre>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html
deleted file mode 100644
index fba65e3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/terminology.html
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Glossary of terms</title>
-</head>
-<body>
-
-<h1>
-Glossary of terms</h1>
-It can be confusing when one person refers to the same thing with different
-terms, and downright misleading if they refer to different things using
-the same term. That's why it's important to choose the right words when
-referring to things in comments, code, and documentation.
-<p><b>Eclipse</b></p>
-<blockquote>Eclipse is the name for the overall project supporting the
-construction of integrated tools for developing applications. It represents
-a collection of related <a href="http://www.eclipse.org/projects/main.html">projects</a>
-that include the <a href="#Platform"> Eclipse Platform,</a> the <a href="#JDT"> Java development tools
-  (JDT)</a>, and
-the <a href="#PDE"> Plug-in Development Environment (PDE)</a>.</blockquote>
-<a NAME="Eclipse Platform"></a><b>Eclipse Platform</b>
-<blockquote>Eclipse Platform is the name for&nbsp; the core frameworks
-and services upon which plug-in extensions are created. It provides the
-runtime in which plug-ins are loaded and run. In order to use the term
-with the right degree of (im)precision, it is useful to know some things
-about the Platform. First off, the Eclipse Platform itself is not really
-a true product that would ship by itself. The Platform's direct consumers
-are tool builders, or ISVs, since they add the value to the Eclipse Platform
-that makes it useful to people.
-<br>
-The Eclipse Platform is divided up into <i>Core </i>and <i>UI</i>.
-Anything classified as "UI" needs a window system, whereas things classified
-as "Core" can run "headless". The UI portion of the Eclipse Platform is
-known as the <a href="#Workbench">Workbench</a>. The core portion of the
-Eclipse Platform is simply called the <a href="#Core">Platform Core</a>,
-or Core.
-<br>
-So the Eclipse Platform is just the nucleus around which tool builders
-build tool plug-ins.
-</blockquote>
-<b>Eclipse SDK</b>
-<blockquote>The Eclipse SDK is the <a href="#Eclipse Platform">Eclipse
-Platform</a>, <a href="#JDT">JDT</a>, and <a href="#PDE">PDE</a>.
-In addition to the Platform, the SDK provides the development tools required
-to, among other things, enable Eclipse to be a development environment
-for itself.</blockquote>
-<p><a NAME="Platform"></a><b>Platform - </b>Short for "<a href="#Eclipse Platform">Eclipse
-Platform</a>".</p>
-<a NAME="RCP"></a><b>Rich Client Platform (RCP)</b>
-<blockquote>A subset of the <a href="#Eclipse Platform">Eclipse
-Platform</a> that forms a generic application framework,
-rather than a framework for building development tools.  This subset does
-not contain the Resources plug-in, or any UI relating to resources.
-</blockquote>
-<p><a NAME="Workbench"></a><b>Workbench</b> - Short for "Eclipse Platform
-UI".</p>
-<blockquote>The Workbench is a high-level UI framework for building products
-with sophisticated UIs built from pluggable components. The Workbench is
-built atop <a href="#JFace">JFace</a>, <a href="#SWT">SWT</a>, and the
-<a href="#Core">Platform
-Core</a>.</blockquote>
-<a NAME="Core"></a><b>Core</b> - Short for "Eclipse Platform Core".
-<blockquote>All the UI-free infrastructure of the <a href="#Eclipse Platform">Eclipse
-Platform</a>. The major divisions are: platform runtime and plug-in management,
-workspaces and resource management, and version and configuration management.</blockquote>
-<a NAME="Runtime"></a><b>Runtime</b> - Short for "Eclipse Platform Core
-Runtime".
-<blockquote>The lowest level part of the <a href="#Core">Platform Core</a>,
-responsible for the plug-in registry and plug-ins. Note that the Platform
-Core Runtime does not include workspaces and resources (they're in the
-Resources plug-in).</blockquote>
-<a NAME="Workspace"></a><b>Workspace</b>
-<blockquote>A workspace is the general umbrella for managing resources
-in the Eclipse Platform. Note that workspaces and resources are an optional
-part of the Platform; some configurations of the Platform will not have
-a workspace.</blockquote>
-<a NAME="UI"></a><b>UI</b> - Short for "Eclipse Platform UI".
-<blockquote>All-inclusive term for the UI portion of the <a href="#Eclipse Platform">Eclipse
-Platform</a>.</blockquote>
-<a NAME="JFace"></a><b>JFace</b>
-<blockquote>JFace is the mid-level UI framework useful for building complex
-UI pieces such as property viewers. JFace works in conjunction with <a href="#SWT">SWT</a>.</blockquote>
-<a NAME="SWT"></a><b>SWT</b>
-<blockquote>SWT (Standard Widget Toolkit) is a small, fast widget toolkit
-with a portable API and a native implementation. So far, SWT has been ported
-to Windows, Linux (GTK and Motif window systems), AIX (Motif), Solaris (GTK),
-HP-UX (Motif), QNX (Photon) and Mac OS X (Carbon).</blockquote>
-<a name="JDT"><b>JDT</b>
-</a>
-<blockquote>Java development tools (n.b. &quot;development tools&quot; in
-  lowercase, for legal reasons) adds Java program development capability to the
-  Eclipse Platform.</blockquote>
-
-<a name="PDE"><b>PDE</b>
-</a>
-<blockquote>The Plug-in Development Environment adds specialized tools for
-  developing Eclipse plug-ins.</blockquote>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html
deleted file mode 100644
index 321fb3d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/ui_accessibility_tips.html
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tips For making user interfaces accessible</title>
-</head>
-<body>
-<h1>Tips for making user interfaces accessible </h1>
-<p>Below is a series of tips for making applications compatible with accessibility
-programs, such as the Accessibility interface provided by Windows. </p>
-<dl>
-<dt><b>Use groups instead of labels.</b></dt>
-<dd>If you use a <b>Label</b> to title a group of related widgets, remove the label and
-  replace their parent composite with a <b>Group</b> whose text is the same as the
-  title <b>Label</b>. <br>&nbsp;</dd>
-  
-<dt><b>Avoid intermediate composites.</b></dt>
-<dd>Accessibility tools will read as far up the parent hierarchy of a widget
-  with focus as possible. Be sure there are no widgets without text anywhere in the tree.<br>&nbsp;</dd>
-  
-<dt><b>Use read-only texts instead of labels.</b></dt>
-<dd>A <b>Text</b> can be accessed using the keyboard and should be used if you want
-  the information in a label to be accessible to keyboard navigation. Note that a 
-  label beside a text will be treated as a title and so if you have a title/value pair, 
-  it is only required that you make the value widget a <b>Text</b>.<br>&nbsp;</dd>
-
-<dt><b>Read and understand the IBM checklist.</b></dt>
-<dd>IBM provides a useful checklist for good accessibility at <a href="http://www.ibm.com/able/guidelines/software/accesssoftware.html">
-http://www.ibm.com/able/guidelines/software/accesssoftware.html</a><br>&nbsp;</dd>
-
-<dt><b>Assign mnemonics to all menus and menu items.</b></dt>
-<dd>Ensure they are unique within a given menu. If a menu
-  is dynamically composed from multiple plugins, it may be better to not assign
-  mnemonics since conflicts cannot be avoided in general (e.g. the <b>File &gt; New</b>
-  list, or <b>Window &gt; Show View</b> list)<br>&nbsp;</dd>
-
-<dt><b>Assign mnemonics to all labels of controls in
-dialogs / preference pages / property pages (e.g. buttons, check-boxes, radio
-buttons, etc)</b></dt>
-<dd>Ensure they are unique within the dialog. Be careful to
-avoid collisions with the default buttons (e.g. Restore &amp;Defaults,
-&amp;Apply in preference pages; &amp;Next, &amp;Back, &amp;Finish in wizards).
-Do not assign mnemonics to OK and Cancel buttons. If you make OK the default
-button of the shell, and Cancel is equivalent to closing the shell, then Enter
-and Esc map to these by default. Generally doing something with Esc or Enter is
-a bad idea.<br>&nbsp;</dd>
-
-<dt><b>Ensure that controls that do not have labels are preceded by a label.</b></dt>
-<dd>If a control does not have its own label (e.g. a text field), use a preceding label
-ending with ':' and assign a mnemonic to it. Screen readers like JAWS will read this label 
-when the control has focus (see <b>Window &gt; Preferences &gt; General</b>)<br>&nbsp;</dd>
-  
-<dt><b>Avoid extra free-standing labels.</b></dt>
-<dd>You cannot navigate to free-standing labels with the keyboard and screen readers
-like JAWS skip these since they do not take focus<br>&nbsp;</dd>
-
-<dt><b>Do not assign mnemonics to controls in the main window.</b></dt>
-<dd>Do not put mnemonics on controls in the main window (other than main
-menus and main menu items), even if it looks like a dialog (e.g. the form editors in
-org.eclipse.ui.forms) as these will usually conflict with menu mnemonics<br>&nbsp;</dd>
-
-<dt><b>Assign shortcut keys for frequently used functions (and <em>only</em> frequently used functions).</b></dt>
-<dd>There are currently only two ways to hook shortcut keys in SWT:
-<ul>
-    <li>by setting an accelerator on a menu item in the
-      main menu bar (they are ignored in context menus) -- JFace actions have
-      support for this</li>
-    <li>by hooking a key listener on a particular control
-      (e.g. in the implementation of a view or editor)</li>
-</ul>
-Consult the table of Eclipse SDK shortcut keys, available within Eclipse from the <b>General &gt; Keys</b>
-preference page, to avoid collision.<br>&nbsp;</dd>
-
-<dt><b>Avoid Alt+{key}, Ctrl+Alt+{key} and Ctrl+Space+{key} combinations.</b></dt>
-<dd><ul>
-<li>Alt+{key} combinations may conflict with menu mnemonics</li>
-<li>Ctrl+Alt+{key} combinations can conflict with entering special characters on international keyboards (alt Gr = Ctrl+Alt)</li>
-<li>Ctrl+Space+{key} combinations can conflict with Ctrl-Space, used for mode switching in Asian languages.</li>
-</ul></dd>
-
-<dt><b>Try to save navigation context.</b></dt>
-<dd>For example, in <b>Window &gt; Preferences</b>, we now remember
-which page you had selected last. This avoids having to navigate through the
-list each time<br>&nbsp;</dd>
-
-<dt><b>Assign a specific person on the team to be responsible for accessibility on your project.</b></dt>
-<dd>Everything that is important needs an advocate. Make sure that everyone on the team knows
-that good accessibility is crucial, and is willing to give the person their full cooperation.<br>&nbsp;</dd>
-
-<dt><b>Test for accessibility.</b></dt>
-<dd>Have your team hold an occasional &quot;unplug your mouse day&quot; where they
-try to use the product using keyboard only. If you are developing on Window, get a copy of
-<a href="http://www.freedomscientific.com/">JAWS<font size="-1"><sup>TM</sup></font></a>
-and ensure that your UI is usable with it<br>&nbsp;</dd>
-</dl>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html
deleted file mode 100644
index c461cc4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_platform_xml.html
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>The platform.xml file</title>
-</head>
-<body>
-<h1>The platform.xml file</h1>
-<h3><strong>Since: </strong></h3>
-<p>3.0</p>
-<h3>Description:</h3>
-<p>The primary update manager configuration information is maintained by the platform.xml 
-  file located in the configuration directory (usually, eclipse/configuration/org.eclipse.update/platform.xml). 
-  This file format is internal and can change any time, but, in practice, it should 
-  not change much, if at all.</p>
-<p>As some people would like to take advantage of shipping an eclipse based product 
-  with a pre-defined installation configuration, this document provides some syntax 
-  and semantics info for this configuration file.</p>
-<p>Given that the platform.xml originated from the old platform.cfg and installConfig*.xml 
-  file, there are still some deprecated elements/attributes that will not be mentioned 
-  in this doc, as well as some relatively convoluted way of specifying the configuration 
-  info. If platform.xml is to become API, then some re-work is needed (both syntax 
-  and semantics).</p>
-<h3>Configuration Markup:</h3>
-<p class=code id=dtd>&lt;!ELEMENT <a name="e.extension">extension</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST extension</p>
-<p class=code id=dtdAttlist>point&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>name&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
-
-<ul class=ConfigMarkup id=attlistDesc>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.config">config</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST config</p>
-<p class=code id=dtdAttlist>version&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p>
-<p class=code id=dtdAttlist>transient&nbsp;(true | false) &quot;false&quot;</p>
-<p class=code id=dtdAttlist>shared_ur&nbsp;CDATA #IMPLIED&gt;</p>
-
-<p class=ConfigMarkup id=elementDesc> describes the current install configuration.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>version</b> - this attribute may be used to indentify the version of the configuration specification</li>
-<li><b>date</b> - this is an internal attribute that is generated by the update configurator code. If you manually create or modify the platform.xml file then remove this attribute, and let the update code add it when it first runs. In this scenario, update will not try to reconcile the platform.xml with what is on the disk, it takes the platform.xml as is, and slaps the date attribute.</li>
-<li><b>transient</b> - a transient configuration is not modified by the update code, it is just read and used to configure the plugins to run. Its main point is to avoid doing any reconciliation with what's on the disk. This flag is a bit of a hack for PDE to run self hosting without having features in the workspace, and it is better if it is left set to false.</li>
-
-<li><b>shared_ur</b> - points to the shared configuration location. This is particularly useful on unix/linux, when the admin sets up a shared installation and each user's configuration consists of the shared installation data (as pointed at by this attribute) and any local changes.</li>
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.site">site</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST site</p>
-<p class=code id=dtdAttlist>url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>enabled&nbsp;&nbsp;&nbsp;&nbsp;(true | false) </p><p class=code id=dtdAttlist>updateable&nbsp;(true | false) </p><p class=code id=dtdAttlist>policy&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(USER-EXCLUDE|USER-INCLUDE|MANAGED-ONLY) </p><p class=code id=dtdAttlist>linkfile&nbsp;&nbsp;&nbsp;CDATA #IMPLIED</p><p class=code id=dtdAttlist>list&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #IMPLIED&gt;</p>
-
-<p class=ConfigMarkup id=elementDesc>
-defines an installation location, which is a location that contains features and plugins.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>url</b> - location of this installation site. The url is absolute, but there is a special url for the base location (where eclipse.exe is located), of the form platform:/base/</li>
-<li><b>enabled</b> - a boolean value that defines whether the plugins and features from this location will be considered at runtime.</li>
-<li><b>updateable</b> - defines whether any update/install/enable/uninstall/etc. operations can be performed on features on this site.</li>
-
-  <li><b>policy</b> - defines the way the &quot;list&quot; attribute is interpreted: 
-    <br>
-    USER-EXCLUDE: all the plugins from the site are run, except those listed in 
-    the &quot;list&quot; attribute. This is what's currently used by the update 
-    code. <br>
-    USER-INCLUDE: only the plugins listed by the &quot;list&quot; attribute are 
-    run. This is what PDE generated configurations use. <br>
-    MANAGED-ONLY: only plugins from the features define by this site (see the &lt;feature&gt; element) are run (new in 3.1)</li>
-<li><b>linkfile</b> - if this site has been contributed from a .link file, then this attribute points to that file.</li>
-  <li><b>list</b> - lists the plugins to be included or excluded (see the &quot;policy&quot; 
-    attribute) at runtime.</li>
-
-</ul>
-<br><p class=code id=dtd>&lt;!ELEMENT <a name="e.feature">feature</a> EMPTY&gt;</p>
-<p class=code id=dtd>&lt;!ATTLIST feature</p>
-<p class=code id=dtdAttlist>id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>version&nbsp;CDATA #REQUIRED</p><p class=code id=dtdAttlist>url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CDATA #REQUIRED&gt;</p>
-
-<p class=ConfigMarkup id=elementDesc> defines a feature installed on this site.</p>
-<br>
-<ul class=ConfigMarkup id=attlistDesc>
-<li><b>id</b> - the feature id</li>
-<li><b>version</b> - the feature version</li>
-<li><b>url</b> - the feature location, relative to the site. By default, the url is of the form features/some_feature_id_version.</li>
-</ul>
-
-<br>
-<h4 class=CaptionFigColumn id=header>Example: </h4>
-<div class="e"> 
-  <pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;config date=&quot;1119300698390&quot; transient=&quot;false&quot; version=&quot;3.0&quot;&gt;<br>  &lt;site enabled=&quot;true&quot; policy=&quot;USER-EXCLUDE&quot; updateable=&quot;true&quot; url=&quot;platform:/base/&quot;&gt;<br>    &lt;feature id=&quot;org.eclipse.platform&quot; url=&quot;features/org.eclipse.platform_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;
-    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.platform.source&quot; url=&quot;features/org.eclipse.platform.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;
-    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.rcp&quot; url=&quot;features/org.eclipse.rcp_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;
-    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.jdt&quot; url=&quot;features/org.eclipse.jdt_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.jdt.source&quot; url=&quot;features/org.eclipse.jdt.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.pde&quot; url=&quot;features/org.eclipse.pde_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.sdk&quot; url=&quot;features/org.eclipse.sdk_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.pde.source&quot; url=&quot;features/org.eclipse.pde.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>    &lt;feature id=&quot;org.eclipse.rcp.source&quot; url=&quot;features/org.eclipse.rcp.source_3.1.0/&quot; version=&quot;3.1.0&quot;&gt;<br>    &lt;/feature&gt;<br>  &lt;/site&gt;<br>  &lt;site enabled=&quot;true&quot; policy=&quot;USER-EXCLUDE&quot; updateable=&quot;true&quot; url=&quot;file:/d:/extensions/org.eclipse.core.tools/eclipse/&quot;&gt;
-  &lt;/site&gt;<br>&lt;/config&gt;
-</pre>
-</div>
-
-</body></html>

diff --git a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html b/bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html
deleted file mode 100644
index 6aaaf08..0000000
--- a/bundles/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html
+++ /dev/null

@@ -1,138 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<link REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Running update manager from command line</title>
-</head>
-<body>
-
-<h1>Running update manager from command line</h1>
-<p>
-<b>Note:</b> The update manager command line application is deprecated. Use
-the <a href="../../guide/p2_director.html">p2 director application</a> instead.
-</p>
-In addition to the install wizard and configuration dialog, it is possible to perform
-update manager operations by running eclipse in a command line mode. You can install, update, enable, disable features,
-or list installed features, or features available on an update site, or adding an extension product site to the local install, etc.
-<br>
-You can also, mirror chosen features from an update site to a local update site location.<br>
- <br>
-Launch eclipse as follows, where [ ] means optional argument and arguments in italics must be provided by the user, and &lt;version&gt; means the specific version of the org.eclipse.equinox.launcher jar in your install.<br>
-	<br>
-<b>Installing a feature from a remote site</b>:<br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
-&nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command install <br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<p> <b>Example:</b> <code>java -jar
-plugins/org.eclipse.equinox.launcher_1.0.0.v20070530.jar -application
-org.eclipse.update.core.standaloneUpdate -command install -from
-http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-update-home/optionalSite/
--featureId com.example.root -version 1.0.0</code> </p>
-<br>
-<b>Updating an existing feature or all features</b>:<br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command update<br>
- &nbsp;&nbsp;&nbsp; [-featureId <i>feature_id </i>]<br>
-  &nbsp;&nbsp;&nbsp; [-version <i>version </i>]<br>
-<br>
-<b>Enabling (configuring) a specified feature:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command enable<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-<b>Disabling (unconfiguring) a specified feature:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command disable<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-<b>Uninstalling a specified feature:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command uninstall<br>
- &nbsp;&nbsp;&nbsp; -featureId <i>feature_id </i><br>
- &nbsp;&nbsp;&nbsp; -version <i>version </i><br>
- &nbsp;&nbsp;&nbsp; [-to <i>target_site_dir</i>] <br>
-<br>
-In all the above commands where the -to target_site_dir is specified, corresponding
-configured target site at given directory will be used. If it is not specified,
-then the default local product site is used.<br>
-<br>
-If you only need to verify if the operation would succeed, in the above commands, (i.e. it satisfies the constraints), without actually performing it,
-then add <b><em>-verifyOnly true</em></b> to the list of arguments.<br>
-
-<br><b>Searching a remote site, listing all available features for install:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command search<br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
-
-<br><b>Listing installed features:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command listFeatures<br>
- &nbsp;&nbsp;&nbsp; -from <i>local_site_dir</i> <br>
- <br>
- The features are listed as:
- <br>
- <code>
- Site: <em>site url </em><br>
-  &nbsp;&nbsp;Feature: <em>id version</em>  enabled (or disabled)
- </code>
- <br>
-
-<br><b>Adding a local site with more features:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command addSite<br>
- &nbsp;&nbsp;&nbsp; -from <i>local_site_dir</i> <br>
-
-<br><b>Removing a local site:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command removeSite<br>
- &nbsp;&nbsp;&nbsp; -to <i>local_site_dir</i> <br>
- 
-<br>
-<b>Mirroring feature(s) from a remote site:</b><br>
-java -jar plugins/org.eclipse.equinox.launcher_&lt;version&gt;.jar<br>
- &nbsp;&nbsp;&nbsp; -application&nbsp; org.eclipse.update.core.standaloneUpdate<br>
- &nbsp;&nbsp;&nbsp; -command mirror<br>
- &nbsp;&nbsp;&nbsp; -from <i>remote_site_url</i> <br>
- &nbsp;&nbsp;&nbsp; -to <i>target_site_dir</i><br>
- &nbsp;&nbsp;&nbsp; [-featureId <i>feature_id</i>]<br>
- &nbsp;&nbsp;&nbsp; [-version <i>version</i>]<br>
- &nbsp;&nbsp;&nbsp; [-mirrorURL <i>mirror_site_url</i>]<br>
-<br>
-If -mirrorURL is specified, an update policy will be generated in
-&lt;target_site_dir&gt;/policy.xml file.  The resulting policy.xml
-maps all features from the mirror site to the specified URL.
-The policy.xml can be used as is, or its fragments
-can be included into custom designed policy file.
-<br>
-<br>
-The return code for each command is either 0 (success) or 1 (failure).<br>
-<br>
-All the above commands should be able to be run using the eclipse executable instead of java -jar.  On windows using the eclipsec executable provides better console support.
-Additionally, most <A
-	href="../../../org.eclipse.platform.doc.user/tasks/running_eclipse.htm">options
-	accepted by Eclipse executable</A> can be passed. They are especially
-	useful during debugging and for specifying target environment for installed features.
-	For example, passing option
-	<code>-data some_path</code> will set the workspace to some_path.<br>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/samples/samples.html b/bundles/org.eclipse.platform.doc.isv/samples/samples.html
deleted file mode 100644
index b7e6f8c..0000000
--- a/bundles/org.eclipse.platform.doc.isv/samples/samples.html
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-   <title>Installation of Examples</title>
-   <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body>
-
-<h1>
-<b>Installing the examples</b></h1>
-
-<h3>
- Installing examples via the Update Manager</h3>
-
-<p>
-The Eclipse SDK examples are found on the Eclipse project update site.
-To locate and install them into a product:</p>
-
-<ol>
-  <li>Open the main update manager by clicking
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.equinox.p2.ui.sdk.install")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Install New Software...</b></a>.
-
-  This opens the Install Wizard.</li>
-  <li> Select <b>The Eclipse Project Updates</b>  site.</li>
-  <li>Ensure <b>Group items by category</b> is unchecked.</li>
-  <li>Type &quot;Eclipse SDK Examples&quot; in the search field.</li>
-  <li>Select &quot;Eclipse SDK Examples&quot; and click <b>Next</b>.</li>
-  <li>Review the items being installed, and click <b>Next</b>.</li>
-  <li>Review and accept the license terms, and click <b>Finish</b>.</li>
-  <li> Click <b>Yes</b> when asked to exit and restart the workbench for the
-    changes to take effect. The examples are now installed in the workbench. 
-  Note: you can also click on <b>Apply Now</b> to dynamically install the 
-  examples into the current configuration.</li>
-</ol>
-
-<h3>
- Installing examples manually</h3>
-To install the examples from a stand-alone zip file:
-<ol>
-	<li>Download the appropriate Eclipse SDK Example zip file from the Eclipse project 
-	web site at <a href="http://download.eclipse.org/eclipse">http://download.eclipse.org/eclipse</a>.
-	</li>
-	<li>Extract the contents of the zip file to a new empty directory inside the <tt>dropins</tt> directory of your Eclipse installation.</li>
-	<li>Start or restart Eclipse.</li>
-</ol>
-
-<p>You can verify that examples have been installed by looking for <b>File &gt;
-New &gt; Example...</b> in the workbench menu bar.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/schema.css b/bundles/org.eclipse.platform.doc.isv/schema.css
deleted file mode 100644
index 10aee31..0000000
--- a/bundles/org.eclipse.platform.doc.isv/schema.css
+++ /dev/null

@@ -1,71 +0,0 @@
-/*******************************************************************************

- * Copyright (c) 2003 IBM Corporation and others.

- * All rights reserved. This program and the accompanying materials 

- * are made available under the terms of the Eclipse Public License v1.0

- * which accompanies this distribution, and is available at

- * http://www.eclipse.org/legal/epl-v10.html

- * 

- * Contributors:

- *     IBM Corporation - initial API and implementation

- *******************************************************************************/

-

-H6.SchemaHeader {

-	font-size:16px; 

-	display:inline

-}

-

-P.SchemaCopyright {

-	font-size: smaller; 

-	font-style: normal;

-	color: #336699; 

-	display:inline;

-	margin-top: 3.000000pt;

-	margin-bottom: 11.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 0.000000pt;

-}

-

-P.SchemaDtd {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-P.SchemaDtdAttlist {

-	color: #800000; 

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 20.000000pt;

-}

-

-span.SchemaTag {

-	color: #000080;

-}

-

-span.SchemaCstring {

-	color: #008000;

-}

-

-pre.Example {

-	margin-top: 0.000000pt;

-}

-

-.ConfigMarkupElementDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 10.000000pt;

-}

-

-.ConfigMarkupAttlistDesc {

-	color: black;

-	margin-top: 0.000000pt;

-	margin-bottom: 0.000000pt;

-	margin-right: 0.000000pt;

-	margin-left: 32.000000pt;

-}

-


diff --git a/bundles/org.eclipse.platform.doc.isv/toc.xml b/bundles/org.eclipse.platform.doc.isv/toc.xml
deleted file mode 100644
index 54c2c85..0000000
--- a/bundles/org.eclipse.platform.doc.isv/toc.xml
+++ /dev/null

@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="Platform Plug-in Developer Guide">
-	<topic label="Programmer&apos;s Guide">
-		<link toc="topics_Guide.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<topic label="What's new" href="whatsNew/platform_isv_whatsnew.html"/>
-	<topic label="3.6 Plug-in Migration Guide">
-		<link toc="topics_Porting.xml"/>
-	</topic>
-	<topic label="Examples Guide">
-		<link toc="topics_Samples.xml" />
-	</topic>
-	<topic label="Questions Index" href="questions/index.html">
-		<link toc="topics_Questions.xml" />
-	</topic>
-	<topic label="Legal" href="notices.html"/>
-	<enablement>
-		<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.pde.ui"/>
-	</enablement>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Guide.xml b/bundles/org.eclipse.platform.doc.isv/topics_Guide.xml
deleted file mode 100644
index 48fdd40..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Guide.xml
+++ /dev/null

@@ -1,479 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the main guide                                              -->
-<!-- ============================================================================= -->
-<toc label="Guide">
-	<topic label="Welcome to Eclipse" href="guide/int.htm">
-		<topic label="Who needs a platform?" href="guide/int_who.htm" />
-		<topic label="The challenge" href="guide/int_goal.htm" />
-		<topic label="What is Eclipse?" href="guide/int_eclipse.htm" />
-		<topic label="Go to eclipse.org" href="http://www.eclipse.org" />
-	</topic>
-
-	<topic label="Platform architecture" href="guide/arch.htm">
-		<topic label="Platform SDK roadmap" href="guide/arch_struct.htm" />
-	</topic>
-
-	<topic label="Simple plug-in example" href="guide/firstplugin.htm">
-		<topic label="A minimal plug-in" href="guide/firstplugin_minimal.htm" />
-		<topic label="Creating the plug-in project" href="guide/firstplugin_create.htm" />
-		<topic label="The Hello World view" href="guide/firstplugin_view.htm" />
-		<topic label="The Hello World manifests" href="guide/firstplugin_manifest.htm" />
-		<topic label="Running the plug-in" href="guide/firstplugin_run.htm" />
-		<topic label="Beyond the basics" href="guide/firstplugin_btb.htm" />
-	</topic>
-
-	<topic label="Runtime overview"  href="guide/runtime.htm">
-		<topic label="The runtime plug-in model" href="guide/runtime_model.htm">
-			<topic label="Plug-ins and bundles" href="guide/runtime_model_bundles.htm"/>
-			<topic label="Extension points and the registry" href="guide/runtime_registry.htm"/>
-		</topic>
-		<topic label="Runtime components" href="guide/runtime_components.htm"/>
-		<topic label="Runtime preferences" href="guide/runtime_preferences.htm"/>
-		<topic label="Runtime application model" href="guide/runtime_app_model.htm"/>
-		<topic label="Content types" href="guide/runtime_content.htm">
-			<topic label="Using content types" href="guide/runtime_content_using.htm"/>
-			<topic label="Contributing content types" href="guide/runtime_content_contributing.htm"/>		
-		</topic>
-		<topic label="Concurrency infrastructure" href="guide/runtime_jobs.htm">
-			<topic label="Reporting progress" href="guide/runtime_jobs_progress.htm"/>
-			<topic label="Job scheduling" href="guide/runtime_jobs_scheduling.htm"/>
-			<topic label="Scheduling rules" href="guide/runtime_jobs_rules.htm"/>
-			<topic label="Locks" href="guide/runtime_jobs_locks.htm"/>
-		</topic>
-	    <topic label="Network support" href="guide/network.htm">
-	    </topic>
-     <topic label="Security">
-        <topic href="guide/secure_storage.htm" label="Secure storage">
-           <topic href="guide/secure_storage_architecture.htm" label="Secure storage architecture">
-           </topic>
-           <topic href="guide/secure_storage_dev.htm" label="Developing with secure storage">
-           </topic>
-           <topic href="guide/secure_storage_providers.htm" label="Creating password providers">
-           </topic>
-        </topic>
-        <topic href="guide/bundle_security.html" label="Signed bundles and protecting against malicious code">
-        </topic>
-        <topic href="guide/login_extensions.html" label="Login based on JAAS">
-        </topic>
-     </topic>
-	</topic>
-
-	<topic label="Plugging into the workbench"  href="guide/workbench.htm">
-		<topic label="Workbench under the covers" href="guide/workbench_structure.htm" />
-		<topic label="Basic workbench extension points using actions" href="guide/workbench_basicext.htm" >
-			<topic label="org.eclipse.ui.views" href="guide/workbench_basicext_views.htm" />
-			<topic label="org.eclipse.ui.viewActions" href="guide/workbench_basicext_viewActions.htm" />
-			<topic label="org.eclipse.ui.editors" href="guide/workbench_basicext_editors.htm" />
-			<topic label="org.eclipse.ui.editorActions" href="guide/workbench_basicext_editorActions.htm" />
-			<topic label="org.eclipse.ui.popupMenus" href="guide/workbench_basicext_popupMenus.htm" />
-			<topic label="org.eclipse.ui.actionSets" href="guide/workbench_basicext_actionSets.htm" />
-		</topic>
-		<topic label="Basic workbench extension points using commands" href="guide/workbench_cmd.htm" >
-			<topic label="org.eclipse.ui.commands" href="guide/workbench_cmd_commands.htm" />
-			<topic label="org.eclipse.ui.menus" href="guide/workbench_cmd_menus.htm" />
-			<topic label="org.eclipse.ui.handlers" href="guide/workbench_cmd_handlers.htm" />
-			<topic label="org.eclipse.ui.bindings" href="guide/workbench_cmd_bindings.htm" />
-   <topic href="guide/workbench_cmd_expressions.htm" label="Workbench Core Expressions">
-   </topic>
-		</topic>
-		<topic label="The plug-in class" href="guide/workbench_plugin.htm" />
-		<topic label="Preference pages" href="guide/preferences_prefs.htm">
-			<topic label="Contributing a preference page" href="guide/preferences_prefs_contribute.htm" />
-			<topic label="Implementing a preference page" href="guide/preferences_prefs_implement.htm" />
-			<topic label="Field editors" href="guide/preferences_prefs_fieldeditors.htm" />
-		</topic>
-	</topic>
-
-	<topic label="Dialogs and wizards"  href="guide/dialogs.htm">
-		<topic label="Standard dialogs" href="guide/dialogs_standard.htm" />
-		<topic label="Application dialogs" href="guide/dialogs_applications.htm" />
-		<topic label="Dialog settings" href="guide/dialogs_settings.htm" />
-		<topic label="Wizards" href="guide/dialogs_wizards.htm" />
-		<topic label="Workbench wizard extension points" href="guide/dialogs_wizards_extensions.htm" >
-			<topic label="org.eclipse.ui.newWizards" href="guide/dialogs_wizards_newWizards.htm" />
-			<topic label="org.eclipse.ui.importWizards" href="guide/dialogs_wizards_importWizards.htm" />
-			<topic label="org.eclipse.ui.exportWizards" href="guide/dialogs_wizards_exportWizards.htm" />
-		</topic>
-		<topic label="Wizard dialogs" href="guide/dialogs_wizards_wizarddialogs.htm" />
-		<topic label="Multi-page wizards" href="guide/dialogs_wizards_multipage.htm" />
-		<topic label="Filtered items selection dialog" href="guide/dialogs_FilteredItemsSelectionDialog.htm">
-			<topic label="Creating a custom filtered items selection dialog" href="guide/dialogs_FilteredItemsSelectionDialog_example.htm" />
-			<topic label="Advanced use of the filtered items selection dialog" href="guide/dialogs_FilteredItemsSelectionDialog_example_advanced.htm" />
-	    </topic>
-	</topic>
-	
-	<topic label="JFace UI framework" href="guide/jface.htm">
-		<topic label="Viewers" href="guide/jface_viewers.htm" />
-		<topic label="Actions and contributions" href="guide/jface_actions.htm" />
-		<topic label="User interface resources" href="guide/jface_resources.htm" />
-		<topic label="Long-running operations" href="guide/jface_operations.htm" />
-		<topic label="Field assist" href="guide/jface_fieldassist.htm" />
-	</topic>
-
-	<topic label="Standard Widget Toolkit" href="guide/swt.htm">
-		<topic label="Widgets" href="guide/swt_widgets.htm" >
-			<topic label="Controls" href="guide/swt_widgets_controls.htm" />
-			<topic label="Events" href="guide/swt_widgets_events.htm" />
-			<topic label="Custom widgets" href="guide/swt_widgets_custom.htm" />
-		</topic>
-		<topic label="Layouts" href="guide/swt_layouts.htm" >
-			<topic label="Custom Layouts" href="guide/swt_layouts_custom.htm" />
-		</topic>
-		<topic label="Threading issues " href="guide/swt_threading.htm" />
-		<topic label="Error handling" href="guide/swt_error.htm" />
-		<topic label="Graphics" href="guide/swt_graphics.htm" />
-		<topic label="Examples" href="guide/swt_examples.htm" />
-	</topic>
-	
-	<topic label="UI Forms" href="guide/forms.htm">
-       <topic label="Controls" href="guide/forms_controls.htm">
- 		   <topic label="Form" href="guide/forms_controls_form.htm"/>
-		   <topic label="Hyperlink" href="guide/forms_controls_link.htm"/>
-		   <topic label="Section" href="guide/forms_controls_section.htm"/>
-		   <topic label="FormText" href="guide/forms_controls_text.htm">
-   		      <topic label="XML Markup" href="guide/forms_controls_text_markup.htm"/>
-   		   </topic>
-	   </topic>
-	   <topic label="Layouts" href="guide/forms_layouts.htm">
-	      <topic label="TableWrapLayout" href="guide/forms_layouts_table.htm"/>
-	      <topic label="ColumnLayout" href="guide/forms_layouts_column.htm"/>
-	   </topic>
-	   <topic label="Advanced Topics">
-	      <topic label="Color and font management" href="guide/forms_colors.htm"/>
-	      <topic label="Managed forms" href="guide/forms_managed.htm"/>
-	      <topic label="Master/Details block" href="guide/forms_master_details.htm"/>
-	   </topic>
-	   <topic label="Multi-page form editors" href="guide/forms_editors.htm"/>
-	</topic>
- <topic href="guide/cnf.htm" label="Common Navigator Framework">
-    <topic href="guide/cnf_config.htm" label="Configuring the Common Navigator">
-    </topic>
-    <topic href="guide/cnf_operation.htm" label="Operational Topics">
-    </topic>
-    <topic href="guide/cnf_steps.htm" label="Step-by-step Instructions">
-       <topic href="guide/cnf_steps_general.htm" label="Creation of Common Navigator View">
-       </topic>
-       <topic href="guide/cnf_steps_content.htm" label="Content and Action Binding">
-       </topic>
-       <topic href="guide/cnf_steps_rn_migration.htm" label="Migrating from the ResourceNavigator">
-       </topic>
-    </topic>
-    <topic href="guide/cnf_troubleshooting.htm" label="Troubleshooting">
-    </topic>
- </topic>
-	
-	<topic label="Resources overview"  href="guide/resInt.htm">
-		<topic label="Resources and the workspace" href="guide/resInt_workspace.htm" />
-		<topic label="Resources and the file system" href="guide/resInt_filesystem.htm" />
-		<topic label="Resource properties" href="guide/resInt_properties.htm" />
-		<topic label="Project-scoped preferences" href="guide/resInt_preferences.htm" />
-		<topic label="File encoding and content types" href="guide/resInt_content.htm" />
-		<topic label="Linked resources" href="guide/resInt_linked.htm" />
-		<topic label="Resource markers" href="guide/resAdv_markers.htm" />
-		<topic label="Modifying the workspace" href="guide/resAdv_modify.htm" >
-			<topic label="Batching resource changes" href="guide/resAdv_batching.htm" />
-			<topic label="Tracking resource changes" href="guide/resAdv_events.htm" />
-			<topic label="Concurrency and the workspace" href="guide/resAdv_concurrency.htm" />
-		</topic>
-	</topic>
-
-	<topic label="Advanced resource concepts"  href="guide/resAdv.htm">
-		<topic label="Project natures" href="guide/resAdv_natures.htm" />
-		<topic label="Incremental project builders" href="guide/resAdv_builders.htm" />
-		<topic label="Derived resources" href="guide/resAdv_derived.htm" />
-		<topic label="Workspace save participation" href="guide/resAdv_saving.htm" />
-		<topic label="Resource modification hooks" href="guide/resAdv_hooks.htm" />
-		<topic label="Refresh providers" href="guide/resAdv_refresh.htm" />
-		<topic label="Alternate file systems" href="guide/resAdv_efs_intro.htm" >
-			<topic label="Using the file system API" href="guide/resAdv_efs_api.htm" />
-			<topic label="Working with resources in other file systems" href="guide/resAdv_efs_resources.htm" />
-			<topic label="User interface support in other file systems" href="guide/wrkAdv_efs_resources.htm" />
-			<topic label="File system providers" href="guide/resAdv_efs_providers.htm" />
-		</topic>
-	</topic>
-
-	<topic label="Advanced workbench concepts" href="guide/wrkAdv.htm">
-		<topic label="Workbench menu contributions" href="guide/workbench_menus.htm" />
-		<topic label="Menu and toolbar paths" href="guide/workbench_menupaths.htm" />
-		<topic label="Action set part associations" href="guide/workbench_basicext_actionSetPartAssociations.htm" />
-		<topic label="Boolean expressions and action filters" href="guide/workbench_actionfilters.htm" />
-		<topic label="Retargetable actions" href="guide/wrkAdv_retarget.htm" >
-			<topic label="Setting a global action handler" href="guide/wrkAdv_retarget_setting.htm" />
-			<topic label="Contributing new retargetable actions" href="guide/wrkAdv_retarget_contribute.htm" >
-				<topic label="Retargetable editor actions" href="guide/wrkAdv_retarget_contribute_editors.htm" />
-				<topic label="Retargetable action set actions" href="guide/wrkAdv_retarget_contribute_actionsets.htm" />
-			</topic>
-		</topic>
-		<topic label="Undoable operations" href="guide/wrkAdv_undo.htm" >
-			<topic label="Undo and the IDE Workbench" href="guide/wrkAdv_undo_ide.htm" />
-		</topic>
-		<topic label="Perspectives" href="guide/workbench_perspectives.htm" >
-			<topic label="org.eclipse.ui.perspectives" href="guide/workbench_advext_perspectives.htm" />
-			<topic label="org.eclipse.ui.perspectiveExtensions" href="guide/workbench_advext_perspectiveExtension.htm" />
-		</topic>
-		<topic label="Decorators" href="guide/workbench_advext_decorators.htm" />
-		<topic label="Workbench key bindings" href="guide/wrkAdv_keyBindings.htm" >
-			<topic label="Associating actions to commands" href="guide/wrkAdv_keyBindings_actionDef.htm" />
-			<topic label="Bindings" href="guide/wrkAdv_keyBindings_accelSet.htm" />
-			<topic label="Schemes" href="guide/wrkAdv_keyBindings_accelConfig.htm" />
-			<topic label="Contexts and key bindings" href="guide/wrkAdv_keyBindings_contexts.htm" />
-		</topic>
-		<topic label="Element factories" href="guide/workbench_advext_elementFactories.htm" />
-		<topic label="Accessible user interfaces" href="guide/wrkAdv_accessibility.htm" />
-		<topic label="Honoring single click support" href="guide/wrkAdv_singleclick.htm" />
-		<topic label="Working sets" href="guide/wrkAdv_workingsets.htm" />
-		<topic label="Filtering large user interfaces" href="guide/workbench_scalability.htm" >
-			<topic label="Activities" href="guide/workbench_advext_activities.htm" />
-			<topic label="Contexts" href="guide/workbench_advext_contexts.htm" />
-		</topic>
-		<topic label="Workbench concurrency support" href="guide/workbench_jobs.htm" />
-		<topic label="Workbench resource support" href="guide/workbench_resources.htm" >
-			<topic label="Contributing a property page" href="guide/preferences_prop_contribute.htm" />
-			<topic label="Implementing a property page" href="guide/preferences_prop_implement.htm" />
-			<topic label="Support for displaying markers" href="guide/wrkAdv_marker_support.htm" />
-			<topic label="Marker help and resolution" href="guide/wrkAdv_markers.htm" >
-				<topic label="Contributing marker help" href="guide/wrkAdv_markerhelp.htm" />
-				<topic label="Contributing marker resolution" href="guide/wrkAdv_markerresolution.htm" />
-			</topic>
-			<topic label="Contributing resource filters" href="guide/workbench_advext_resourceFilters.htm" />
-			<topic label="Text file encoding" href="guide/wrkAdv_encoding.htm" />	
-		</topic>
-		<topic label="Status handling" href="guide/workbench_statushandling.htm" >
-			<topic label="Defining a status handler" href="guide/workbench_statushandling_defining.htm" />
-		</topic>
-  <topic href="guide/wrkAdv_services.htm" label="Services">
-  </topic>
-	</topic>
-	
-	<topic label="Editors" href="guide/editors.htm">
-		<topic label="Workbench editors" href="guide/editors_workbench.htm" />
-		<topic label="Text editors and platform text" href="guide/editors_jface.htm" />
-		<topic label="Documents and partitions" href="guide/editors_documents.htm" />
-		<topic label="Source viewers and annotations" href="guide/editors_annotations.htm" />
-		<topic label="Configuring a source viewer" href="guide/editors_sourceviewers.htm" />
-		<topic label="Text and ruler hover" href="guide/editors_hover.htm" />
-		<topic label="Syntax coloring" href="guide/editors_highlighting.htm" />
-		<topic label="Content assist" href="guide/editors_contentassist.htm" />
-		<topic label="Registering editor actions" href="guide/editors_actions.htm" />
-		<topic label="Other text editor responsibilities" href="guide/editors_utilities.htm" />
-		<topic label="Content outliners" href="guide/editors_workbench_outliner.htm" />
-	</topic>
-	
-	<topic label="Search support" href="guide/search.htm">
-		<topic label="Contributing a search page" href="guide/search_page.htm" />
-		<topic label="Contributing a search result page" href="guide/search_result.htm" />
-	</topic>
-	
-	<topic label="Compare support" href="guide/compare.htm">
-		<topic label="Merging multiple files" href="guide/compare_streammerger.htm" />
-		<topic label="Implementing a content viewer" href="guide/compare_contentviewer.htm" />
-		<topic label="Implementing a structure viewer" href="guide/compare_structureviewer.htm" />
-		<topic label="Advanced compare techniques" href="guide/compare_beyond.htm" />
-	</topic>
-	
-	<topic label="Team support" href="guide/team.htm">
-		<topic label="Repository providers" href="guide/team_provider_repository.htm" />
-		<topic label="Resource management" href="guide/team_resources.htm" />
-		<topic label="Synchronization Support" href="guide/team_synchronize.htm" >
-			<topic label="Local History Synchronization Example" href="guide/team_synchronize_localhistory_example.htm" />
-			<topic label="Beyond the basics" href="guide/team_synchronize_beyond_basics.htm" />
-		</topic>
-	    <topic label="Support for Logical Model Integration" href="guide/team_model.htm" >
-			<topic label="Repository Roadmap for Logical Model Integration" href="guide/team_model_repo.htm" />
-			<topic label="Model Roadmap for Logical Model Integration" href="guide/team_model_model.htm" />
-		</topic>
-		<topic label="Rich Team Integration" href="guide/team_howto.htm" >
-			<topic label="Adding team actions" href="guide/team_ui_actions.htm" />
-			<topic label="Team decorators" href="guide/team_ui_decorators.htm" />
-			<topic label="Adding preferences and properties" href="guide/team_ui_prefs.htm" />
-			<topic label="Project sets" href="guide/team_resources_projects.htm" />
-			<topic label="Team and linked resources" href="guide/team_resources_linked.htm" />
-			<topic label="Team private resources" href="guide/team_resources_private.htm" />
-			<topic label="File types" href="guide/team_resources_filetypes.htm" /><topic
-				label="Adding History support" href="guide/team_ui_history.htm">
-</topic>
-		</topic>
-	</topic>
-	
-	<topic label="Program debug and launch support" href="guide/debug.htm">
-		<topic label="Launching a program" href="guide/debug_launch.htm" >
-			<topic label="Adding launchers to the platform" href="guide/debug_launch_adding.htm" >
-				<topic label="Obtaining a program's source code" href="guide/debug_launch_sourcelocators.htm" />
-				<topic label="Comparing launch configurations" href="guide/debug_launch_comparators.htm" />
-				<topic label="Process factories" href="guide/debug_launch_processfactories.htm" />
-				<topic label="Launching Java applications" href="guide/debug_launch_java.htm" />		
-			</topic>
-			<topic label="Handling errors from a launched program" href="guide/debug_launch_status.htm" />		
-			<topic label="Launch configuration dialog" href="guide/debug_launch_ui.htm" />
-			<topic label="Launch configuration type images" href="guide/debug_launch_uiimages.htm" />
-			<topic label="Launch shortcuts" href="guide/debug_launch_uishortcuts.htm" />
-		</topic>
-		<topic label="Debugging a program" href="guide/debug_debug.htm" >
-			<topic label="Platform debug model" href="guide/debug_model.htm" />
-			<topic label="Breakpoints" href="guide/debug_breakpoints.htm" />
-			<topic label="Expressions" href="guide/debug_expressions.htm" />
-			<topic label="Debug model presentation" href="guide/debug_presentation.htm" />
-			<topic label="Debug UI utility classes" href="guide/debug_ui.htm" />
-		</topic>
-	</topic>
-	
-	<topic label="Platform Ant support" href="guide/ant.htm">
-		<topic label="Running Ant buildfiles programmatically" href="guide/ant_running_buildfiles_programmatically.htm" />
-		<topic label="Ant tasks provided by the platform" href="guide/ant_eclipse_tasks.htm" />
-		<topic label="Contributing tasks and types" href="guide/ant_contributing_task.htm" />
-		<topic label="Developing Ant tasks and types within Eclipse" href="guide/ant_developing.htm" />
-		<topic label="Expanding the Ant classpath" href="guide/ant_expanding_classpath.htm" />
-	</topic>
-	
-	<topic label="User assistance support" href="guide/ua.htm">
-		<topic label="Welcome" href="guide/ua_intro.htm" >
-			<topic href="guide/ua_intro_defining.htm" label="Defining an intro part">
-      <topic href="guide/ua_intro_hello_world.htm" label="Contributing a HelloWorld intro Part">
-      </topic>
-   </topic>
-			<topic label="Using the CustomizableIntroPart" href="guide/ua_intro_cust_intro_part.htm" >
-				<topic label="Defining an intro config" href="guide/ua_intro_defining_config.htm" />
-				<topic label="Defining intro content" href="guide/ua_intro_define_content.htm" />
-    <topic href="guide/ua_intro_minimal.htm" label="Defining a minimal intro configuration">
-    </topic>
-				<topic label="Using XHTML as intro content" href="guide/ua_intro_xhtml.htm" />
-				<topic label="Displaying static HTML content in the CustomizableIntroPart" href="guide/ua_intro_cust_static.htm" />
-				<topic label="Extending an intro config" href="guide/ua_intro_extending.htm" >
-					<topic label="Extending the content of an intro config" href="guide/ua_intro_extending_content.htm" />
-					<topic label="Defining intro themes" href="guide/ua_intro_ext_theme.htm" />
-					<topic label="Contributing a standby content part" href="guide/ua_intro_ext_standbypart.htm" />
-					<topic label="Defining a custom IntroURL action" href="guide/ua_intro_ext_custom_url.htm" />
-					<topic label="Intro Content File XML Format" href="reference/extension-points/introContentFileSpec.html" />
-				</topic>
-			</topic>
-   <topic href="guide/ua_intro_universal.htm" label="Universal intro">
-      <topic href="guide/ua_intro_universal_contributing.htm" label="Contributing to universal intro">
-      </topic>
-      <topic href="guide/ua_intro_universal_preference.htm" label="Adding the preference page">
-      </topic>
-      <topic href="guide/ua_intro_universal_extending.htm" label="Extending the universal intro">
-      </topic>
-      <topic href="guide/ua_intro_universal_defaults.htm" label="Configuring product defaults">
-      </topic>
-      <topic href="guide/ua_intro_universal_links.htm" label="Managing links">
-      </topic>
-   </topic>
-		</topic>
-		<topic label="Help" href="guide/ua_help.htm">
-			<topic label="Configuration/setup" href="guide/ua_help_setup.htm" >
-				<topic label="Rich Client Platform (RCP) help" href="guide/ua_help_setup_rcp.htm"/>
-				<topic label="Standalone help" href="guide/ua_help_setup_standalone.htm"/>
-				<topic label="Infocenter" href="guide/ua_help_setup_infocenter.htm"/>
-				<topic label="Help system customization" href="guide/ua_help_setup_preferences.htm">
-					<topic label="Help data XML format" href="guide/ua_help_setup_help_data.htm"/>
-					<topic label="Generated navigation topics" href="guide/ua_help_setup_nav.htm"/>
-     <topic href="guide/ua_help_menu.htm" label="The Help Menu">
-     </topic>
-               <topic href="guide/ua_help_infocenter_preferences.htm" label="Infocenter customization">
-               </topic>
-               <topic href="guide/ua_help_setup_about.htm" label="Using about.html to debug infocenters">
-               </topic>
-				</topic>
-				<topic label="Pre-indexing documentation" href="guide/ua_help_setup_preindex.htm"/>
-			</topic>
-			<topic label="Help content" href="guide/ua_help_content.htm" >
-				<topic label="Table of contents (toc) files" href="guide/ua_help_content_toc.htm" />
-				<topic label="Help server and file locations" href="guide/ua_help_content_files.htm" />
-				<topic label="Completing the plug-in manifest" href="guide/ua_help_content_manifest.htm" />
-				<topic label="Building nested documentation structures" href="guide/ua_help_content_nested.htm" />
-				<topic label="Contributing XHTML help documents" href="guide/ua_help_content_xhtml.htm" />
-				<topic label="Remote Help" href="guide/ua_help_content_remote.htm" />				
-				<topic label="Active help" href="guide/ua_help_content_active.htm" >
-					<topic label="Writing the help action" href="guide/ua_help_content_active_action.htm" />
-					<topic label="Invoking the action from HTML" href="guide/ua_help_content_active_invoke.htm" />
-					<topic label="Tips for debugging active help" href="guide/ua_help_content_active_debug.htm" />
-				</topic>
-				<topic label="Embedding commands in help" href="guide/ua_help_content_command.htm" >
-					<topic label="Authoring a command link" href="guide/ua_help_content_command_authoring.htm" />
-				</topic>
-            <topic href="guide/ua_help_content_process.htm" label="Processing Help Content">
-            </topic>
-            <topic href="guide/ua_help_content_child_links.htm" label="Adding child links to help topics">
-            </topic>
-			</topic>
-			<topic label="Context-sensitive help" href="guide/ua_help_context.htm" >
-				<topic label="Declaring a context id" href="guide/ua_help_context_id.htm" />
-				<topic label="Describing and packaging context-sensitive help" href="guide/ua_help_context_xml.htm" />
-				<topic label="Dynamic context help" href="guide/ua_help_context_dynamic.htm"/>
-				<topic label="Infopops" href="guide/ua_help_context_infopops.htm"/>
-			</topic>
-			<topic label="Help search" href="guide/ua_help_search.htm">
-			   <topic label="Plugging in search engines" href="guide/ua_help_search_types.htm"/>		
-			</topic>
-   <topic href="guide/ua_help_war.htm" label="Deploying the infocenter as a Web Archive">
-   </topic>
-		</topic>
-		<topic label="Cheat sheets" href="guide/ua_cheatsheet.htm" >
-			<topic label="Simple cheat sheets" href="guide/ua_cheatsheet_simple.htm" />		    
-			<topic label="Cheat sheet content file XML format" href="reference/extension-points/cheatSheetContentFileSpec.html" />
-			<topic label="Composite cheat sheets" href="guide/ua_cheatsheet_composite.htm" />		    
-			<topic label="Composite cheat sheet content file XML format" href="reference/extension-points/compositeContentFile.html" />			
-			<topic label="Cheat sheet authoring guidelines" href="guide/ua_cheatsheet_guidelines.htm" />
-		</topic>
-		<topic label="Status handling" href="guide/ua_statushandling.htm">
-			<topic label="Defining a product status handler" href="guide/ua_statushandling_defining.htm" />
-			<topic label="Contributing a sample handler" href="guide/ua_statushandling_sample.htm" />
-		</topic>
-		<topic label="Dynamic content" href="guide/ua_dynamic.htm">
-			<topic label="Filters" href="guide/ua_dynamic_filters.htm" />
-			<topic label="Includes" href="guide/ua_dynamic_includes.htm" />
-			<topic label="Extensions" href="guide/ua_dynamic_extensions.htm" />
-		</topic>
-	</topic>
- <topic href="guide/p2_overview.htm" label="Provisioning platform, p2">
-    <topic href="guide/p2_metadata.html" label="Metadata management">
-       <topic href="guide/p2_publisher.html" label="Publishing metadata">
-       </topic>
-       <topic href="guide/p2_publishingtasks.htm" label="Ant tasks for publishing metadata">
-       </topic>
-       <topic href="guide/p2_customizing_metadata.html" label="Customizing metadata">
-       </topic>
-    </topic>
-    <topic href="guide/p2_director.html" label="Installation management">
-    </topic>
-    <topic label="Repository management">
-       <topic href="guide/p2_mirror.html" label="Mirroring repositories">
-       </topic>
-       <topic href="guide/p2_composite_repositories.htm" label="Composite repositories">
-       </topic>
-       <topic href="guide/p2_category_generation.htm" label="Content categorization">
-       </topic>
-       <topic href="guide/p2_repositorytasks.htm" label="Ant tasks for managing repositories">
-       </topic>
-    </topic>
- </topic>
-
-	<topic label="Packaging and delivering Eclipse based products" href="guide/product.htm">
-		<topic label="Defining a Product" href="guide/product_def.htm" >
-			<topic label="The products extension point" href="guide/product_def_extpt.htm" />
-			<topic label="Customizing a product" href="guide/product_configproduct.htm" />
-		</topic>
-		<topic label="Features" href="guide/product_def_feature.htm" />
-		<topic label="Plug-ins and fragments" href="guide/product_def_plugins.htm" />
-		<topic label="Locale specific files" href="guide/product_def_nl.htm" />
-		<topic label="Product installation guidelines" href="guide/product_config_install.htm" />
-		<topic label="Product extensions" href="guide/product_extension.htm" />
-		<topic label="Updating a product or extension" href="guide/product_update.htm" />
-		<topic label="Deploying eclipse based application with Java Web Start" href="guide/java_web_start.htm"/>
-	</topic>
-	
-	<topic label="Building a Rich Client Platform application" href="guide/rcp.htm">
-		<topic label="The browser example" href="guide/rcp_browser.htm" />
-		<topic label="Defining a rich client application" href="guide/rcp_define.htm" />
-		<topic label="Customizing the workbench" href="guide/rcp_advisor.htm" />
-		<topic label="Making UI contributions" href="guide/rcp_extensions.htm" >
-			<topic label="Adding the perspective" href="guide/rcp_perspective.htm" />
-			<topic label="Adding views" href="guide/rcp_view.htm" />
-			<topic label="Defining the actions" href="guide/rcp_actions.htm" />
-		</topic>
-	</topic>			
-	
-	<topic label="Http Service and JSP Support" href="guide/httpservice.htm" />
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml b/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml
deleted file mode 100644
index ac3e41a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml
+++ /dev/null

@@ -1,31 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the porting guide index                                     -->
-<!-- ============================================================================= -->
-<toc label="Migration">
-	<topic label="Migrating to Eclipse 3.6 from 3.5">
-		<topic label="Introduction" href="porting/eclipse_3_6_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.6/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.6/incompatibilities.html" />
-		<topic label="Adopting 3.6 mechanisms and API" href="porting/3.6/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse 3.5 from 3.4">
-		<topic label="Introduction" href="porting/eclipse_3_5_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.5/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.5/incompatibilities.html" />
-		<topic label="Adopting 3.5 mechanisms and API" href="porting/3.5/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse 3.4 from 3.3">
-		<topic label="Introduction" href="porting/eclipse_3_4_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.4/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.4/incompatibilities.html" />
-		<topic label="Adopting 3.4 mechanisms and API" href="porting/3.4/recommended.html" />
-	</topic>
-	<topic label="Migrating to Eclipse 3.3 from 3.2">
-		<topic label="Introduction" href="porting/eclipse_3_3_porting_guide.html"/>
-		<topic label="FAQ" href="porting/3.3/faq.html" />
-		<topic label="Incompatibilities" href="porting/3.3/incompatibilities.html" />
-		<topic label="Adopting 3.3 Mechanisms and API" href="porting/3.3/recommended.html" />
-	</topic>
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Questions.xml b/bundles/org.eclipse.platform.doc.isv/topics_Questions.xml
deleted file mode 100644
index ad5a504..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Questions.xml
+++ /dev/null

@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the questions index                                         -->
-<!-- ============================================================================= -->
-<toc label="Questions">
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Reference.xml b/bundles/org.eclipse.platform.doc.isv/topics_Reference.xml
deleted file mode 100644
index 92a2266..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Reference.xml
+++ /dev/null

@@ -1,471 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the references                                              -->
-<!-- ============================================================================= -->
-<toc label="Reference">
-
-	<topic label="API Reference" href="reference/api/overview-summary.html">
-      <topic label="org.eclipse.ant.core" href="reference/api/org/eclipse/ant/core/package-summary.html"/>
-      <topic label="org.eclipse.compare" href="reference/api/org/eclipse/compare/package-summary.html"/>
-      <topic label="org.eclipse.compare.contentmergeviewer" href="reference/api/org/eclipse/compare/contentmergeviewer/package-summary.html"/>
-      <topic label="org.eclipse.compare.patch" href="reference/api/org/eclipse/compare/patch/package-summary.html"/>
-      <topic label="org.eclipse.compare.rangedifferencer" href="reference/api/org/eclipse/compare/rangedifferencer/package-summary.html"/>
-      <topic label="org.eclipse.compare.structuremergeviewer" href="reference/api/org/eclipse/compare/structuremergeviewer/package-summary.html"/>
-      <topic label="org.eclipse.core.commands" href="reference/api/org/eclipse/core/commands/package-summary.html"/>
-      <topic label="org.eclipse.core.commands.common" href="reference/api/org/eclipse/core/commands/common/package-summary.html"/>
-      <topic label="org.eclipse.core.commands.contexts" href="reference/api/org/eclipse/core/commands/contexts/package-summary.html"/>
-      <topic label="org.eclipse.core.commands.operations" href="reference/api/org/eclipse/core/commands/operations/package-summary.html"/>
-      <topic label="org.eclipse.core.databinding" href="reference/api/org/eclipse/core/databinding/package-summary.html"/>
-      <topic label="org.eclipse.core.databinding.beans" href="reference/api/org/eclipse/core/databinding/beans/package-summary.html"/>
-      <topic label="org.eclipse.core.databinding.conversion" href="reference/api/org/eclipse/core/databinding/conversion/package-summary.html"/>
-      <topic label="org.eclipse.core.databinding.observable" href="reference/api/org/eclipse/core/databinding/observable/package-summary.html"/>
-      <topic label="org.eclipse.core.databinding.observable.list" href="reference/api/org/eclipse/core/databinding/observable/list/package-summary.html"/>
-      <topic label="org.eclipse.core.databinding.observable.map" href="reference/api/org/eclipse/core/databinding/observable/map/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.observable.masterdetail" href="reference/api/org/eclipse/core/databinding/observable/masterdetail/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.observable.set" href="reference/api/org/eclipse/core/databinding/observable/set/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.observable.value" href="reference/api/org/eclipse/core/databinding/observable/value/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.property" href="reference/api/org/eclipse/core/databinding/property/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.property.list" href="reference/api/org/eclipse/core/databinding/property/list/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.property.map" href="reference/api/org/eclipse/core/databinding/property/map/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.property.set" href="reference/api/org/eclipse/core/databinding/property/set/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.property.value" href="reference/api/org/eclipse/core/databinding/property/value/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.util" href="reference/api/org/eclipse/core/databinding/util/package-summary.html"/>      
-      <topic label="org.eclipse.core.databinding.validation" href="reference/api/org/eclipse/core/databinding/validation/package-summary.html"/>   
-      <topic label="org.eclipse.core.expressions" href="reference/api/org/eclipse/core/expressions/package-summary.html"/>
-      <topic label="org.eclipse.core.filebuffers" href="reference/api/org/eclipse/core/filebuffers/package-summary.html"/>
-      <topic label="org.eclipse.core.filebuffers.manipulation" href="reference/api/org/eclipse/core/filebuffers/manipulation/package-summary.html"/>
-      <topic label="org.eclipse.core.filesystem" href="reference/api/org/eclipse/core/filesystem/package-summary.html"/>
-      <topic label="org.eclipse.core.filesystem.provider" href="reference/api/org/eclipse/core/filesystem/provider/package-summary.html"/>
-      <topic label="org.eclipse.core.net.proxy" href="reference/api/org/eclipse/core/net/proxy/package-summary.html"/>
-      <topic label="org.eclipse.core.resources" href="reference/api/org/eclipse/core/resources/package-summary.html"/>
-      <topic label="org.eclipse.core.resources.refresh" href="reference/api/org/eclipse/core/resources/refresh/package-summary.html"/>
-      <topic label="org.eclipse.core.resources.team" href="reference/api/org/eclipse/core/resources/team/package-summary.html"/>
-      <topic label="org.eclipse.core.resources.mapping" href="reference/api/org/eclipse/core/resources/mapping/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime" href="reference/api/org/eclipse/core/runtime/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.adaptor" href="reference/api/org/eclipse/core/runtime/adaptor/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.content" href="reference/api/org/eclipse/core/runtime/content/package-summary.html"/>
-	  <topic label="org.eclipse.core.runtime.dynamichelpers" href="reference/api/org/eclipse/core/runtime/dynamichelpers/package-summary.html"/>
-	  <topic label="org.eclipse.core.runtime.spi" href="reference/api/org/eclipse/core/runtime/spi/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.jobs" href="reference/api/org/eclipse/core/runtime/jobs/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.model" href="reference/api/org/eclipse/core/runtime/model/package-summary.html"/>
-      <topic label="org.eclipse.core.runtime.preferences" href="reference/api/org/eclipse/core/runtime/preferences/package-summary.html"/>
-      <topic label="org.eclipse.core.variables" href="reference/api/org/eclipse/core/variables/package-summary.html"/>
-      <topic label="org.eclipse.debug.core" href="reference/api/org/eclipse/debug/core/package-summary.html"/>
-      <topic label="org.eclipse.debug.core.commands" href="reference/api/org/eclipse/debug/core/commands/package-summary.html"/>
-      <topic label="org.eclipse.debug.core.model" href="reference/api/org/eclipse/debug/core/model/package-summary.html"/>
-      <topic label="org.eclipse.debug.core.sourcelookup" href="reference/api/org/eclipse/debug/core/sourcelookup/package-summary.html"/>
-      <topic label="org.eclipse.debug.core.sourcelookup.containers" href="reference/api/org/eclipse/debug/core/sourcelookup/containers/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui" href="reference/api/org/eclipse/debug/ui/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.actions" href="reference/api/org/eclipse/debug/ui/actions/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.console" href="reference/api/org/eclipse/debug/ui/console/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.contexts" href="reference/api/org/eclipse/debug/ui/contexts/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.memory" href="reference/api/org/eclipse/debug/ui/memory/package-summary.html"/>
-      <topic label="org.eclipse.debug.ui.sourcelookup" href="reference/api/org/eclipse/debug/ui/sourcelookup/package-summary.html"/>
-      <topic label="org.eclipse.equinox.app" href="reference/api/org/eclipse/equinox/app/package-summary.html"/>
-      <topic label="org.eclipse.equinox.http.jetty" href="reference/api/org/eclipse/equinox/http/jetty/package-summary.html"/>
-      <topic label="org.eclipse.equinox.http.registry" href="reference/api/org/eclipse/equinox/http/registry/package-summary.html"/>
-      <topic label="org.eclipse.equinox.http.servlet" href="reference/api/org/eclipse/equinox/http/servlet/package-summary.html"/>
-      <topic label="org.eclipse.equinox.jsp.jasper" href="reference/api/org/eclipse/equinox/jsp/jasper/package-summary.html"/>
-      <topic label="org.eclipse.equinox.jsp.jasper.registry" href="reference/api/org/eclipse/equinox/jsp/jasper/registry/package-summary.html"/>
-      <topic label="org.eclipse.equinox.security.auth" href="reference/api/org/eclipse/equinox/security/auth/package-summary.html"/>
-      <topic label="org.eclipse.equinox.security.auth.credentials" href="reference/api/org/eclipse/equinox/security/auth/credentials/package-summary.html"/>
-      <topic label="org.eclipse.equinox.security.auth.module" href="reference/api/org/eclipse/equinox/security/auth/module/package-summary.html"/>
-      <topic label="org.eclipse.equinox.security.storage" href="reference/api/org/eclipse/equinox/security/storage/package-summary.html"/>
-      <topic label="org.eclipse.equinox.security.storage.provider" href="reference/api/org/eclipse/equinox/security/storage/provider/package-summary.html"/>
-      <topic label="org.eclipse.help" href="reference/api/org/eclipse/help/package-summary.html"/>
-      <topic label="org.eclipse.help.browser" href="reference/api/org/eclipse/help/browser/package-summary.html"/>
-      <topic label="org.eclipse.help.search" href="reference/api/org/eclipse/help/search/package-summary.html"/>
-      <topic label="org.eclipse.help.server" href="reference/api/org/eclipse/help/server/package-summary.html"/>
-      <topic label="org.eclipse.help.standalone" href="reference/api/org/eclipse/help/standalone/package-summary.html"/>
-      <topic label="org.eclipse.help.ui" href="reference/api/org/eclipse/help/ui/package-summary.html"/>
-      <topic label="org.eclipse.help.ui.browser" href="reference/api/org/eclipse/help/ui/browser/package-summary.html"/>
-      <topic label="org.eclipse.help.webapp" href="reference/api/org/eclipse/help/webapp/package-summary.html"/>
-      <topic label="org.eclipse.jface.action" href="reference/api/org/eclipse/jface/action/package-summary.html"/>
-      <topic label="org.eclipse.jface.bindings" href="reference/api/org/eclipse/jface/bindings/package-summary.html"/>
-      <topic label="org.eclipse.jface.bindings.keys" href="reference/api/org/eclipse/jface/bindings/keys/package-summary.html"/>
-      <topic label="org.eclipse.jface.bindings.keys.formatting" href="reference/api/org/eclipse/jface/bindings/keys/formatting/package-summary.html"/>
-      <topic label="org.eclipse.jface.commands" href="reference/api/org/eclipse/jface/commands/package-summary.html"/>
-      <topic label="org.eclipse.jface.contentassist" href="reference/api/org/eclipse/jface/contentassist/package-summary.html"/>
-      <topic label="org.eclipse.jface.contexts" href="reference/api/org/eclipse/jface/contexts/package-summary.html"/>
-      <topic label="org.eclipse.jface.databinding.dialog" href="reference/api/org/eclipse/jface/databinding/dialog/package-summary.html"/>
-      <topic label="org.eclipse.jface.databinding.preference" href="reference/api/org/eclipse/jface/databinding/preference/package-summary.html"/>
-      <topic label="org.eclipse.jface.databinding.swt" href="reference/api/org/eclipse/jface/databinding/swt/package-summary.html"/>
-      <topic label="org.eclipse.jface.databinding.util" href="reference/api/org/eclipse/jface/databinding/util/package-summary.html"/>
-      <topic label="org.eclipse.jface.databinding.viewers" href="reference/api/org/eclipse/jface/databinding/viewers/package-summary.html"/>
-      <topic label="org.eclipse.jface.databinding.wizard" href="reference/api/org/eclipse/jface/databinding/wizard/package-summary.html"/>
-      <topic label="org.eclipse.jface.dialogs" href="reference/api/org/eclipse/jface/dialogs/package-summary.html"/>
-      <topic label="org.eclipse.jface.fieldassist" href="reference/api/org/eclipse/jface/fieldassist/package-summary.html"/>
-      <topic label="org.eclipse.jface.layout" href="reference/api/org/eclipse/jface/layout/package-summary.html"/>
-      <topic label="org.eclipse.jface.menus" href="reference/api/org/eclipse/jface/menus/package-summary.html"/>
-      <topic label="org.eclipse.jface.operation" href="reference/api/org/eclipse/jface/operation/package-summary.html"/>
-      <topic label="org.eclipse.jface.preference" href="reference/api/org/eclipse/jface/preference/package-summary.html"/>
-      <topic label="org.eclipse.jface.resource" href="reference/api/org/eclipse/jface/resource/package-summary.html"/>
-      <topic label="org.eclipse.jface.text" href="reference/api/org/eclipse/jface/text/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.contentassist" href="reference/api/org/eclipse/jface/text/contentassist/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.formatter" href="reference/api/org/eclipse/jface/text/formatter/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.hyperlink" href="reference/api/org/eclipse/jface/text/hyperlink/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.information" href="reference/api/org/eclipse/jface/text/information/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.link" href="reference/api/org/eclipse/jface/text/link/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.presentation" href="reference/api/org/eclipse/jface/text/presentation/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.projection" href="reference/api/org/eclipse/jface/text/projection/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.quickassist" href="reference/api/org/eclipse/jface/text/quickassist/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.reconciler" href="reference/api/org/eclipse/jface/text/reconciler/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.revisions" href="reference/api/org/eclipse/jface/text/revisions/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.rules" href="reference/api/org/eclipse/jface/text/rules/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.source" href="reference/api/org/eclipse/jface/text/source/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.source.projection" href="reference/api/org/eclipse/jface/text/source/projection/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.templates" href="reference/api/org/eclipse/jface/text/templates/package-summary.html"/>
-      <topic label="org.eclipse.jface.text.templates.persistence" href="reference/api/org/eclipse/jface/text/templates/persistence/package-summary.html"/>
-      <topic label="org.eclipse.jface.util" href="reference/api/org/eclipse/jface/util/package-summary.html"/>
-      <topic label="org.eclipse.jface.viewers" href="reference/api/org/eclipse/jface/viewers/package-summary.html"/>
-       <topic label="org.eclipse.jface.viewers.deferred" href="reference/api/org/eclipse/jface/viewers/deferred/package-summary.html"/>
-      <topic label="org.eclipse.jface.window" href="reference/api/org/eclipse/jface/window/package-summary.html"/>
-      <topic label="org.eclipse.jface.wizard" href="reference/api/org/eclipse/jface/wizard/package-summary.html"/>
-      <topic label="org.eclipse.jsch.core" href="reference/api/org/eclipse/jsch/core/package-summary.html"/>
-      <topic label="org.eclipse.jsch.ui" href="reference/api/org/eclipse/jsch/ui/package-summary.html"/>
-      <topic label="org.eclipse.ltk.core.refactoring" href="reference/api/org/eclipse/ltk/core/refactoring/package-summary.html"/>
-      <topic label="org.eclipse.ltk.core.refactoring.history" href="reference/api/org/eclipse/ltk/core/refactoring/history/package-summary.html"/>
-      <topic label="org.eclipse.ltk.core.refactoring.model" href="reference/api/org/eclipse/ltk/core/refactoring/model/package-summary.html"/>
-	  <topic label="org.eclipse.ltk.core.refactoring.participants" href="reference/api/org/eclipse/ltk/core/refactoring/participants/package-summary.html"/>
-      <topic label="org.eclipse.ltk.core.refactoring.resource" href="reference/api/org/eclipse/ltk/core/refactoring/resource/package-summary.html"/>
-      <topic label="org.eclipse.ltk.ui.refactoring" href="reference/api/org/eclipse/ltk/ui/refactoring/package-summary.html"/>
-      <topic label="org.eclipse.ltk.ui.refactoring.actions" href="reference/api/org/eclipse/ltk/ui/refactoring/actions/package-summary.html"/>
-      <topic label="org.eclipse.ltk.ui.refactoring.history" href="reference/api/org/eclipse/ltk/ui/refactoring/history/package-summary.html"/>
-      <topic label="org.eclipse.ltk.ui.refactoring.model" href="reference/api/org/eclipse/ltk/ui/refactoring/model/package-summary.html"/>
-      <topic label="org.eclipse.ltk.ui.refactoring.resource" href="reference/api/org/eclipse/ltk/ui/refactoring/resource/package-summary.html"/>
-      <topic label="org.eclipse.osgi.service.datalocation" href="reference/api/org/eclipse/osgi/service/datalocation/package-summary.html"/>
-      <topic label="org.eclipse.osgi.service.security" href="reference/api/org/eclipse/osgi/service/security/package-summary.html"/>
-      <topic label="org.eclipse.osgi.signedcontent" href="reference/api/org/eclipse/osgi/signedcontent/package-summary.html"/>
-      <topic label="org.eclipse.osgi.util" href="reference/api/org/eclipse/osgi/util/package-summary.html"/>
-      <topic label="org.eclipse.search.core.text" href="reference/api/org/eclipse/search/core/text/package-summary.html"/>
-      <topic label="org.eclipse.search.ui" href="reference/api/org/eclipse/search/ui/package-summary.html"/>
-      <topic label="org.eclipse.search.ui.actions" href="reference/api/org/eclipse/search/ui/actions/package-summary.html"/>
-      <topic label="org.eclipse.search.ui.text" href="reference/api/org/eclipse/search/ui/text/package-summary.html"/>
-      <topic label="org.eclipse.swt" href="reference/api/org/eclipse/swt/package-summary.html"/>
-      <topic label="org.eclipse.swt.accessibility" href="reference/api/org/eclipse/swt/accessibility/package-summary.html"/>
-      <topic label="org.eclipse.swt.awt" href="reference/api/org/eclipse/swt/awt/package-summary.html"/>
-      <topic label="org.eclipse.swt.browser" href="reference/api/org/eclipse/swt/browser/package-summary.html"/>
-      <topic label="org.eclipse.swt.custom" href="reference/api/org/eclipse/swt/custom/package-summary.html"/>
-      <topic label="org.eclipse.swt.dnd" href="reference/api/org/eclipse/swt/dnd/package-summary.html"/>
-      <topic label="org.eclipse.swt.events" href="reference/api/org/eclipse/swt/events/package-summary.html"/>
-      <topic label="org.eclipse.swt.graphics" href="reference/api/org/eclipse/swt/graphics/package-summary.html"/>
-      <topic label="org.eclipse.swt.layout" href="reference/api/org/eclipse/swt/layout/package-summary.html"/>
-      <topic label="org.eclipse.swt.ole.win32" href="reference/api/org/eclipse/swt/ole/win32/package-summary.html"/>
-      <topic label="org.eclipse.swt.opengl" href="reference/api/org/eclipse/swt/opengl/package-summary.html"/>
-      <topic label="org.eclipse.swt.printing" href="reference/api/org/eclipse/swt/printing/package-summary.html"/>
-      <topic label="org.eclipse.swt.program" href="reference/api/org/eclipse/swt/program/package-summary.html"/>
-      <topic label="org.eclipse.swt.widgets" href="reference/api/org/eclipse/swt/widgets/package-summary.html"/>
-      <topic label="org.eclipse.team.core" href="reference/api/org/eclipse/team/core/package-summary.html"/>
-      <topic label="org.eclipse.team.core.diff" href="reference/api/org/eclipse/team/core/diff/package-summary.html"/>
-      <topic label="org.eclipse.team.core.diff.provider" href="reference/api/org/eclipse/team/core/diff/provider/package-summary.html"/>
-      <topic label="org.eclipse.team.core.history" href="reference/api/org/eclipse/team/core/history/package-summary.html"/>
-      <topic label="org.eclipse.team.core.history.provider" href="reference/api/org/eclipse/team/core/history/provider/package-summary.html"/>
-      <topic label="org.eclipse.team.core.mapping" href="reference/api/org/eclipse/team/core/mapping/package-summary.html"/>
-      <topic label="org.eclipse.team.core.mapping.provider" href="reference/api/org/eclipse/team/core/mapping/provider/package-summary.html"/>
-      <topic label="org.eclipse.team.core.subscribers" href="reference/api/org/eclipse/team/core/subscribers/package-summary.html"/>
-      <topic label="org.eclipse.team.core.synchronize" href="reference/api/org/eclipse/team/core/synchronize/package-summary.html"/>
-      <topic label="org.eclipse.team.core.variants" href="reference/api/org/eclipse/team/core/variants/package-summary.html"/>
-      <topic label="org.eclipse.team.ui" href="reference/api/org/eclipse/team/ui/package-summary.html"/>
-      <topic label="org.eclipse.team.ui.history" href="reference/api/org/eclipse/team/ui/history/package-summary.html"/>
-      <topic label="org.eclipse.team.ui.mapping" href="reference/api/org/eclipse/team/ui/mapping/package-summary.html"/>
-      <topic label="org.eclipse.team.ui.synchronize" href="reference/api/org/eclipse/team/ui/synchronize/package-summary.html"/>
-      <topic label="org.eclipse.text.edits" href="reference/api/org/eclipse/text/edits/package-summary.html"/>
-      <topic label="org.eclipse.text.undo" href="reference/api/org/eclipse/text/undo/package-summary.html"/>
-      <topic label="org.eclipse.ui" href="reference/api/org/eclipse/ui/package-summary.html"/>
-      <topic label="org.eclipse.ui.about" href="reference/api/org/eclipse/ui/about/package-summary.html"/>
-      <topic label="org.eclipse.ui.actions" href="reference/api/org/eclipse/ui/actions/package-summary.html"/>
-      <topic label="org.eclipse.ui.activities" href="reference/api/org/eclipse/ui/activities/package-summary.html"/>
-      <topic label="org.eclipse.ui.application" href="reference/api/org/eclipse/ui/application/package-summary.html"/>
-      <topic label="org.eclipse.ui.branding" href="reference/api/org/eclipse/ui/branding/package-summary.html"/>
-      <topic label="org.eclipse.ui.browser" href="reference/api/org/eclipse/ui/browser/package-summary.html"/>
-      <topic label="org.eclipse.ui.cheatsheets" href="reference/api/org/eclipse/ui/cheatsheets/package-summary.html"/>
-      <topic label="org.eclipse.ui.commands" href="reference/api/org/eclipse/ui/commands/package-summary.html"/>
-      <topic label="org.eclipse.ui.console" href="reference/api/org/eclipse/ui/console/package-summary.html"/>
-      <topic label="org.eclipse.ui.console.actions" href="reference/api/org/eclipse/ui/console/actions/package-summary.html"/>
-      <topic label="org.eclipse.ui.contentassist" href="reference/api/org/eclipse/ui/contentassist/package-summary.html"/>
-      <topic label="org.eclipse.ui.contexts" href="reference/api/org/eclipse/ui/contexts/package-summary.html"/>
-      <topic label="org.eclipse.ui.databinding" href="reference/api/org/eclipse/ui/databinding/package-summary.html"/>
-      <topic label="org.eclipse.ui.dialogs" href="reference/api/org/eclipse/ui/dialogs/package-summary.html"/>
-      <topic label="org.eclipse.ui.editors.text" href="reference/api/org/eclipse/ui/editors/text/package-summary.html"/>
-      <topic label="org.eclipse.ui.editors.text.templates" href="reference/api/org/eclipse/ui/editors/text/templates/package-summary.html"/>
-      <topic label="org.eclipse.ui.fieldassist" href="reference/api/org/eclipse/ui/fieldassist/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms" href="reference/api/org/eclipse/ui/forms/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms.editor" href="reference/api/org/eclipse/ui/forms/editor/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms.events" href="reference/api/org/eclipse/ui/forms/events/package-summary.html"/>
-      <topic label="org.eclipse.ui.forms.widgets" href="reference/api/org/eclipse/ui/forms/widgets/package-summary.html"/>
-      <topic label="org.eclipse.ui.handlers" href="reference/api/org/eclipse/ui/handlers/package-summary.html"/>
-      <topic label="org.eclipse.ui.help" href="reference/api/org/eclipse/ui/help/package-summary.html"/>
-      <topic label="org.eclipse.ui.ide" href="reference/api/org/eclipse/ui/ide/package-summary.html"/>
-      <topic label="org.eclipse.ui.ide.dialogs" href="reference/api/org/eclipse/ui/ide/dialogs/package-summary.html"/>
-      <topic label="org.eclipse.ui.ide.fileSystem" href="reference/api/org/eclipse/ui/ide/fileSystem/package-summary.html"/>
-      <topic label="org.eclipse.ui.ide.undo" href= "reference/api/org/eclipse/ui/ide/undo/package-summary.html"/>
-      <topic label="org.eclipse.ui.intro" href="reference/api/org/eclipse/ui/intro/package-summary.html"/>
-      <topic label="org.eclipse.ui.intro.config" href="reference/api/org/eclipse/ui/intro/config/package-summary.html"/>
-      <topic label="org.eclipse.ui.intro.contentproviders" href="reference/api/org/eclipse/ui/intro/contentproviders/package-summary.html"/>
-      <topic label="org.eclipse.ui.intro.universal" href="reference/api/org/eclipse/ui/intro/universal/package-summary.html"/>
-      <topic label="org.eclipse.ui.keys" href="reference/api/org/eclipse/ui/keys/package-summary.html"/>
-      <topic label="org.eclipse.ui.menus" href="reference/api/org/eclipse/ui/menus/package-summary.html"/>
-      <topic label="org.eclipse.ui.model" href="reference/api/org/eclipse/ui/model/package-summary.html"/>
-      <topic label="org.eclipse.ui.navigator" href="reference/api/org/eclipse/ui/navigator/package-summary.html"/>      
-	  <topic label="org.eclipse.ui.navigator.resources" href="reference/api/org/eclipse/ui/navigator/resources/package-summary.html"/>            
-      <topic label="org.eclipse.ui.operations" href="reference/api/org/eclipse/ui/operations/package-summary.html"/>
-      <topic label="org.eclipse.ui.part" href="reference/api/org/eclipse/ui/part/package-summary.html"/>
-      <topic label="org.eclipse.ui.plugin" href="reference/api/org/eclipse/ui/plugin/package-summary.html"/>
-      <topic label="org.eclipse.ui.preferences" href="reference/api/org/eclipse/ui/preferences/package-summary.html"/>
-      <topic label="org.eclipse.ui.presentations" href="reference/api/org/eclipse/ui/presentations/package-summary.html"/>
-      <topic label="org.eclipse.ui.progress" href="reference/api/org/eclipse/ui/progress/package-summary.html"/>
-      <topic label="org.eclipse.ui.services" href="reference/api/org/eclipse/ui/services/package-summary.html"/>
-      <topic label="org.eclipse.ui.splash" href="reference/api/org/eclipse/ui/splash/package-summary.html"/>
-      <topic label="org.eclipse.ui.statushandlers" href="reference/api/org/eclipse/ui/statushandlers/package-summary.html"/>
-      <topic label="org.eclipse.ui.swt" href="reference/api/org/eclipse/ui/swt/package-summary.html"/>
-      <topic label="org.eclipse.ui.testing" href="reference/api/org/eclipse/ui/testing/package-summary.html"/>
-      <topic label="org.eclipse.ui.themes" href="reference/api/org/eclipse/ui/themes/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor" href="reference/api/org/eclipse/ui/texteditor/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.link" href="reference/api/org/eclipse/ui/texteditor/link/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.quickdiff" href="reference/api/org/eclipse/ui/texteditor/quickdiff/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.rulers" href="reference/api/org/eclipse/ui/texteditor/rulers/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.spelling" href="reference/api/org/eclipse/ui/texteditor/spelling/package-summary.html"/>
-      <topic label="org.eclipse.ui.texteditor.templates" href="reference/api/org/eclipse/ui/texteditor/templates/package-summary.html"/>
-      <topic label="org.eclipse.ui.views" href="reference/api/org/eclipse/ui/views/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.bookmarkexplorer" href="reference/api/org/eclipse/ui/views/bookmarkexplorer/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.contentoutline" href="reference/api/org/eclipse/ui/views/contentoutline/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.framelist" href="reference/api/org/eclipse/ui/views/framelist/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.markers" href="reference/api/org/eclipse/ui/views/markers/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.navigator" href="reference/api/org/eclipse/ui/views/navigator/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.properties" href="reference/api/org/eclipse/ui/views/properties/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.properties.tabbed" href="reference/api/org/eclipse/ui/views/properties/tabbed/package-summary.html"/>
-      <topic label="org.eclipse.ui.views.tasklist" href="reference/api/org/eclipse/ui/views/tasklist/package-summary.html"/>
-      <topic label="org.eclipse.ui.wizards" href="reference/api/org/eclipse/ui/wizards/package-summary.html"/>
-      <topic label="org.eclipse.ui.wizards.datatransfer" href="reference/api/org/eclipse/ui/wizards/datatransfer/package-summary.html"/>
-      <topic label="org.eclipse.ui.wizards.newresource" href="reference/api/org/eclipse/ui/wizards/newresource/package-summary.html"/>
-      <topic label="org.eclipse.update.configurator" href="reference/api/org/eclipse/update/configurator/package-summary.html"/>
-      <topic label="org.eclipse.update.configuration" href="reference/api/org/eclipse/update/configuration/package-summary.html"/>
-      <topic label="org.eclipse.update.core" href="reference/api/org/eclipse/update/core/package-summary.html"/>
-      <topic label="org.eclipse.update.core.model" href="reference/api/org/eclipse/update/core/model/package-summary.html"/>
-      <topic label="org.eclipse.update.operations" href="reference/api/org/eclipse/update/operations/package-summary.html"/>
-      <topic label="org.eclipse.update.search" href="reference/api/org/eclipse/update/search/package-summary.html"/>
-      <topic label="org.eclipse.update.standalone" href="reference/api/org/eclipse/update/standalone/package-summary.html"/>
-    </topic>
-
-	<topic label="Extension Points Reference" href="reference/extension-points/index.html">
-       <topic label="org.eclipse.ant.core.antProperties" href="reference/extension-points/org_eclipse_ant_core_antProperties.html"/>
-       <topic label="org.eclipse.ant.core.antTasks" href="reference/extension-points/org_eclipse_ant_core_antTasks.html"/>
-       <topic label="org.eclipse.ant.core.antTypes" href="reference/extension-points/org_eclipse_ant_core_antTypes.html"/>
-       <topic label="org.eclipse.ant.core.extraClasspathEntries" href="reference/extension-points/org_eclipse_ant_core_extraClasspathEntries.html"/>
-       <topic label="org.eclipse.compare.contentMergeViewers" href="reference/extension-points/org_eclipse_compare_contentMergeViewers.html"/>
-       <topic label="org.eclipse.compare.contentViewers" href="reference/extension-points/org_eclipse_compare_contentViewers.html"/>
-       <topic label="org.eclipse.compare.streamMergers" href="reference/extension-points/org_eclipse_compare_streamMergers.html"/>
-       <topic label="org.eclipse.compare.structureCreators" href="reference/extension-points/org_eclipse_compare_structureCreators.html"/>
-       <topic label="org.eclipse.compare.structureMergeViewers" href="reference/extension-points/org_eclipse_compare_structureMergeViewers.html"/>
-       <topic label="org.eclipse.core.contenttype.contentTypes" href="reference/extension-points/org_eclipse_core_contenttype_contentTypes.html"/>
-       <topic label="org.eclipse.core.expressions.propertyTesters" href="reference/extension-points/org_eclipse_core_expressions_propertyTesters.html"/>
-       <topic label="org.eclipse.core.expressions.definitions" href="reference/extension-points/org_eclipse_core_expressions_definitions.html"/>
-       <topic label="org.eclipse.core.filebuffers.annotationModelCreation" href="reference/extension-points/org_eclipse_core_filebuffers_annotationModelCreation.html"/>
-       <topic label="org.eclipse.core.filebuffers.documentCreation" href="reference/extension-points/org_eclipse_core_filebuffers_documentCreation.html"/>
-       <topic label="org.eclipse.core.filebuffers.documentSetup" href="reference/extension-points/org_eclipse_core_filebuffers_documentSetup.html"/>
-       <topic label="org.eclipse.core.filesystem.filesystems" href="reference/extension-points/org_eclipse_core_filesystem_filesystems.html"/>
-       <topic label="org.eclipse.core.resources.builders" href="reference/extension-points/org_eclipse_core_resources_builders.html"/>
-       <topic label="org.eclipse.core.resources.fileModificationValidator" href="reference/extension-points/org_eclipse_core_resources_fileModificationValidator.html"/>
-       <topic label="org.eclipse.core.resources.markers" href="reference/extension-points/org_eclipse_core_resources_markers.html"/>
-       <topic label="org.eclipse.core.resources.modelProviders" href="reference/extension-points/org_eclipse_core_resources_modelProviders.html"/>
-       <topic label="org.eclipse.core.resources.moveDeleteHook" href="reference/extension-points/org_eclipse_core_resources_moveDeleteHook.html"/>
-       <topic label="org.eclipse.core.resources.natures" href="reference/extension-points/org_eclipse_core_resources_natures.html"/>
-       <topic label="org.eclipse.core.resources.refreshProviders" href="reference/extension-points/org_eclipse_core_resources_refreshProviders.html"/>
-       <topic label="org.eclipse.core.resources.teamHook" href="reference/extension-points/org_eclipse_core_resources_teamHook.html"/>
-       <topic label="org.eclipse.core.runtime.adapters" href="reference/extension-points/org_eclipse_core_runtime_adapters.html"/>
-       <topic label="org.eclipse.core.runtime.applications" href="reference/extension-points/org_eclipse_core_runtime_applications.html"/>
-       <topic label="org.eclipse.core.runtime.contentTypes" href="reference/extension-points/org_eclipse_core_runtime_contentTypes.html"/>
-       <topic label="org.eclipse.core.runtime.preferences" href="reference/extension-points/org_eclipse_core_runtime_preferences.html"/>
-       <topic label="org.eclipse.core.runtime.products" href="reference/extension-points/org_eclipse_core_runtime_products.html"/>
-       <topic label="org.eclipse.core.variables.dynamicVariables" href="reference/extension-points/org_eclipse_core_variables_dynamicVariables.html"/>
-       <topic label="org.eclipse.core.variables.valueVariables" href="reference/extension-points/org_eclipse_core_variables_valueVariables.html"/>
-       <topic label="org.eclipse.debug.core.breakpoints" href="reference/extension-points/org_eclipse_debug_core_breakpoints.html"/>
-       <topic label="org.eclipse.debug.core.launchConfigurationComparators" href="reference/extension-points/org_eclipse_debug_core_launchConfigurationComparators.html"/>
-       <topic label="org.eclipse.debug.core.launchConfigurationTypes" href="reference/extension-points/org_eclipse_debug_core_launchConfigurationTypes.html"/>
-       <topic label="org.eclipse.debug.core.launchDelegates" href="reference/extension-points/org_eclipse_debug_core_launchDelegates.html"/>
-       <topic label="org.eclipse.debug.core.launchers" href="reference/extension-points/org_eclipse_debug_core_launchers.html"/>
-       <topic label="org.eclipse.debug.core.launchModes" href="reference/extension-points/org_eclipse_debug_core_launchModes.html"/>
-       <topic label="org.eclipse.debug.core.logicalStructureProviders" href="reference/extension-points/org_eclipse_debug_core_logicalStructureProviders.html"/>
-       <topic label="org.eclipse.debug.core.logicalStructureTypes" href="reference/extension-points/org_eclipse_debug_core_logicalStructureTypes.html"/>
-       <topic label="org.eclipse.debug.core.processFactories" href="reference/extension-points/org_eclipse_debug_core_processFactories.html"/>
-       <topic label="org.eclipse.debug.core.sourceContainerTypes" href="reference/extension-points/org_eclipse_debug_core_sourceContainerTypes.html"/>
-       <topic label="org.eclipse.debug.core.sourceLocators" href="reference/extension-points/org_eclipse_debug_core_sourceLocators.html"/>
-       <topic label="org.eclipse.debug.core.sourcePathComputers" href="reference/extension-points/org_eclipse_debug_core_sourcePathComputers.html"/>
-       <topic label="org.eclipse.debug.core.statusHandlers" href="reference/extension-points/org_eclipse_debug_core_statusHandlers.html"/>
-       <topic label="org.eclipse.debug.core.watchExpressionDelegates" href="reference/extension-points/org_eclipse_debug_core_watchExpressionDelegates.html"/>
-       <topic label="org.eclipse.debug.ui.breakpointOrganizers" href="reference/extension-points/org_eclipse_debug_ui_breakpointOrganizers.html"/>
-       <topic label="org.eclipse.debug.ui.consoleColorProviders" href="reference/extension-points/org_eclipse_debug_ui_consoleColorProviders.html"/>
-       <topic label="org.eclipse.debug.ui.consoleLineTrackers" href="reference/extension-points/org_eclipse_debug_ui_consoleLineTrackers.html"/>
-       <topic label="org.eclipse.debug.ui.contextViewBindings" href="reference/extension-points/org_eclipse_debug_ui_contextViewBindings.html"/>
-       <topic label="org.eclipse.debug.ui.debugModelContextBindings" href="reference/extension-points/org_eclipse_debug_ui_debugModelContextBindings.html"/>
-       <topic label="org.eclipse.debug.ui.debugModelPresentations" href="reference/extension-points/org_eclipse_debug_ui_debugModelPresentations.html"/>
-       <topic label="org.eclipse.debug.ui.detailPaneFactories" href="reference/extension-points/org_eclipse_debug_ui_detailPaneFactories.html"/>       
-       <topic label="org.eclipse.debug.ui.launchConfigurationTabGroups" href="reference/extension-points/org_eclipse_debug_ui_launchConfigurationTabGroups.html"/>
-       <topic label="org.eclipse.debug.ui.launchConfigurationTabs" href="reference/extension-points/org_eclipse_debug_ui_launchConfigurationTabs.html"/>
-       <topic label="org.eclipse.debug.ui.launchConfigurationTypeImages" href="reference/extension-points/org_eclipse_debug_ui_launchConfigurationTypeImages.html"/>
-       <topic label="org.eclipse.debug.ui.launchGroups" href="reference/extension-points/org_eclipse_debug_ui_launchGroups.html"/>
-       <topic label="org.eclipse.debug.ui.launchShortcuts" href="reference/extension-points/org_eclipse_debug_ui_launchShortcuts.html"/>
-       <topic label="org.eclipse.debug.ui.memoryRenderings" href="reference/extension-points/org_eclipse_debug_ui_memoryRenderings.html"/>
-       <topic label="org.eclipse.debug.ui.sourceContainerPresentations" href="reference/extension-points/org_eclipse_debug_ui_sourceContainerPresentations.html"/>
-       <topic label="org.eclipse.debug.ui.stringVariablePresentations" href="reference/extension-points/org_eclipse_debug_ui_stringVariablePresentations.html"/>
-       <topic label="org.eclipse.debug.ui.toggleBreakpointsTargetFactories" href="reference/extension-points/org_eclipse_debug_ui_toggleBreakpointsTargetFactories.html"/>
-       <topic label="org.eclipse.debug.ui.variableValueEditors" href="reference/extension-points/org_eclipse_debug_ui_variableValueEditors.html"/>
-       <topic label="org.eclipse.equinox.preferences.preferences" href="reference/extension-points/org_eclipse_equinox_preferences_preferences.html"/>
-       <topic label="org.eclipse.equinox.http.registry.httpcontexts" href="reference/extension-points/org_eclipse_equinox_http_registry_httpcontexts.html"/>
-       <topic label="org.eclipse.equinox.http.registry.resources" href="reference/extension-points/org_eclipse_equinox_http_registry_resources.html"/>
-       <topic label="org.eclipse.equinox.http.registry.servlets" href="reference/extension-points/org_eclipse_equinox_http_registry_servlets.html"/>
-       <topic label="org.eclipse.equinox.security.loginConfigurationProvider" href="reference/extension-points/org_eclipse_equinox_security_loginConfigurationProvider.html"/>
-       <topic label="org.eclipse.equinox.security.loginModule" href="reference/extension-points/org_eclipse_equinox_security_loginModule.html"/>
-       <topic label="org.eclipse.equinox.security.callbackHandler" href="reference/extension-points/org_eclipse_equinox_security_callbackHandler.html"/>
-       <topic label="org.eclipse.equinox.security.callbackHandlerMapping" href="reference/extension-points/org_eclipse_equinox_security_callbackHandlerMapping.html"/>
-       <topic label="org.eclipse.equinox.security.secureStorage" href="reference/extension-points/org_eclipse_equinox_security_secureStorage.html"/>
-       <topic label="org.eclipse.help.contentExtension" href="reference/extension-points/org_eclipse_help_contentExtension.html"/>
-       <topic label="org.eclipse.help.contentProducer" href="reference/extension-points/org_eclipse_help_contentProducer.html"/>
-       <topic label="org.eclipse.help.contexts" href="reference/extension-points/org_eclipse_help_contexts.html"/>
-       <topic label="org.eclipse.help.index" href="reference/extension-points/org_eclipse_help_index.html"/>
-       <topic label="org.eclipse.help.toc" href="reference/extension-points/org_eclipse_help_toc.html"/>
-       <topic label="org.eclipse.help.base.activitySupport" href="reference/extension-points/org_eclipse_help_base_activitySupport.html"/>
-       <topic label="org.eclipse.help.base.browser" href="reference/extension-points/org_eclipse_help_base_browser.html"/>
-       <topic label="org.eclipse.help.base.luceneAnalyzer" href="reference/extension-points/org_eclipse_help_base_luceneAnalyzer.html"/>
-       <topic label="org.eclipse.help.base.luceneSearchParticipants" href="reference/extension-points/org_eclipse_help_base_luceneSearchParticipants.html"/>
-       <topic label="org.eclipse.help.base.server" href="reference/extension-points/org_eclipse_help_base_server.html"/>
-       <topic label="org.eclipse.help.ui.searchEngine" href="reference/extension-points/org_eclipse_help_ui_searchEngine.html"/>
-       <topic label="org.eclipse.help.webapp.contentFilter" href="reference/extension-points/org_eclipse_help_webapp_contentFilter.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.copyParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_copyParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.createParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_createParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.deleteParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_deleteParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.moveParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_moveParticipants.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.refactoringContributions" href="reference/extension-points/org_eclipse_ltk_core_refactoring_refactoringContributions.html"/>
-       <topic label="org.eclipse.ltk.core.refactoring.renameParticipants" href="reference/extension-points/org_eclipse_ltk_core_refactoring_renameParticipants.html"/>
-       <topic label="org.eclipse.ltk.ui.refactoring.changePreviewViewers" href="reference/extension-points/org_eclipse_ltk_ui_refactoring_changePreviewViewers.html"/>
-       <topic label="org.eclipse.ltk.ui.refactoring.statusContextViewers" href="reference/extension-points/org_eclipse_ltk_ui_refactoring_statusContextViewers.html"/>
-       <topic label="org.eclipse.search.searchPages" href="reference/extension-points/org_eclipse_search_searchPages.html"/>
-       <topic label="org.eclipse.search.searchResultSorters" href="reference/extension-points/org_eclipse_search_searchResultSorters.html"/>
-       <topic label="org.eclipse.search.searchResultViewPages" href="reference/extension-points/org_eclipse_search_searchResultViewPages.html"/>
-       <topic label="org.eclipse.search.textSearchEngine" href="reference/extension-points/org_eclipse_search_textSearchEngine.html"/>
-       <topic label="org.eclipse.search.textSearchQueryProvider" href="reference/extension-points/org_eclipse_search_textSearchQueryProvider.html"/>
-       <topic label="org.eclipse.team.core.fileTypes" href="reference/extension-points/org_eclipse_team_core_fileTypes.html"/>
-       <topic label="org.eclipse.team.core.ignore" href="reference/extension-points/org_eclipse_team_core_ignore.html"/>
-       <topic label="org.eclipse.team.core.projectSets" href="reference/extension-points/org_eclipse_team_core_projectSets.html"/>
-       <topic label="org.eclipse.team.core.repository" href="reference/extension-points/org_eclipse_team_core_repository.html"/>
-       <topic label="org.eclipse.team.core.storageMergers" href="reference/extension-points/org_eclipse_team_core_storageMergers.html"/>
-       <topic label="org.eclipse.team.ui.configurationWizards" href="reference/extension-points/org_eclipse_team_ui_configurationWizards.html"/>
-       <topic label="org.eclipse.team.ui.synchronizeParticipants" href="reference/extension-points/org_eclipse_team_ui_synchronizeParticipants.html"/>
-       <topic label="org.eclipse.team.ui.synchronizeWizards" href="reference/extension-points/org_eclipse_team_ui_synchronizeWizards.html"/>
-       <topic label="org.eclipse.team.ui.teamContentProviders" href="reference/extension-points/org_eclipse_team_ui_teamContentProviders.html"/>
-       <topic label="org.eclipse.team.ui.teamDecorators" href="reference/extension-points/org_eclipse_team_ui_teamDecorators.html"/>
-       <topic label="org.eclipse.ui.acceleratorConfigurations" href="reference/extension-points/org_eclipse_ui_acceleratorConfigurations.html"/>
-       <topic label="org.eclipse.ui.acceleratorScopes" href="reference/extension-points/org_eclipse_ui_acceleratorScopes.html"/>
-       <topic label="org.eclipse.ui.acceleratorSets" href="reference/extension-points/org_eclipse_ui_acceleratorSets.html"/>
-       <topic label="org.eclipse.ui.actionDefinitions" href="reference/extension-points/org_eclipse_ui_actionDefinitions.html"/>
-       <topic label="org.eclipse.ui.actionSetPartAssociations" href="reference/extension-points/org_eclipse_ui_actionSetPartAssociations.html"/>
-       <topic label="org.eclipse.ui.actionSets" href="reference/extension-points/org_eclipse_ui_actionSets.html"/>
-       <topic label="org.eclipse.ui.activities" href="reference/extension-points/org_eclipse_ui_activities.html"/>
-	    <topic label="org.eclipse.ui.activitySupport" href="reference/extension-points/org_eclipse_ui_activitySupport.html"/>
-		 <topic label="org.eclipse.ui.bindings" href="reference/extension-points/org_eclipse_ui_bindings.html"/>
-       <topic label="org.eclipse.ui.browser.browsers" href="reference/extension-points/org_eclipse_ui_browser_browsers.html"/>
-		 <topic label="org.eclipse.ui.browserSupport" href="reference/extension-points/org_eclipse_ui_browserSupport.html"/>
-       <topic label="org.eclipse.ui.cheatsheets.cheatSheetContent" href="reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetContent.html"/>
-       <topic label="org.eclipse.ui.cheatsheets.cheatSheetItemExtension" href="reference/extension-points/org_eclipse_ui_cheatsheets_cheatSheetItemExtension.html"/>
-       <topic label="org.eclipse.ui.commands" href="reference/extension-points/org_eclipse_ui_commands.html"/>
-       <topic label="org.eclipse.ui.commandImages" href="reference/extension-points/org_eclipse_ui_commandImages.html"/>
-       <topic label="org.eclipse.ui.console.consoleFactories" href="reference/extension-points/org_eclipse_ui_console_consoleFactories.html"/>
-       <topic label="org.eclipse.ui.console.consolePageParticipants" href="reference/extension-points/org_eclipse_ui_console_consolePageParticipants.html"/>
-       <topic label="org.eclipse.ui.console.consolePatternMatchListeners" href="reference/extension-points/org_eclipse_ui_console_consolePatternMatchListeners.html"/>
-	    <topic label="org.eclipse.ui.contexts" href="reference/extension-points/org_eclipse_ui_contexts.html"/>
-       <topic label="org.eclipse.ui.decorators" href="reference/extension-points/org_eclipse_ui_decorators.html"/>
-       <topic label="org.eclipse.ui.dropActions" href="reference/extension-points/org_eclipse_ui_dropActions.html"/>
-       <topic label="org.eclipse.ui.editorActions" href="reference/extension-points/org_eclipse_ui_editorActions.html"/>
-       <topic label="org.eclipse.ui.editors" href="reference/extension-points/org_eclipse_ui_editors.html"/>
-       <topic label="org.eclipse.ui.editors.annotationTypes" href="reference/extension-points/org_eclipse_ui_editors_annotationTypes.html"/>
-       <topic label="org.eclipse.ui.editors.documentProviders" href="reference/extension-points/org_eclipse_ui_editors_documentProviders.html"/>
-       <topic label="org.eclipse.ui.editors.markerAnnotationSpecification" href="reference/extension-points/org_eclipse_ui_editors_markerAnnotationSpecification.html"/>
-       <topic label="org.eclipse.ui.editors.markerUpdaters" href="reference/extension-points/org_eclipse_ui_editors_markerUpdaters.html"/>
-       <topic label="org.eclipse.ui.editors.templates" href="reference/extension-points/org_eclipse_ui_editors_templates.html"/>
-       <topic label="org.eclipse.ui.elementFactories" href="reference/extension-points/org_eclipse_ui_elementFactories.html"/>
-	    <topic label="org.eclipse.ui.encodings" href="reference/extension-points/org_eclipse_ui_encodings.html"/>
-       <topic label="org.eclipse.ui.exportWizards" href="reference/extension-points/org_eclipse_ui_exportWizards.html"/>
-       <topic label="org.eclipse.ui.externaltools.configurationDuplicationMaps" href="reference/extension-points/org_eclipse_ui_externaltools_configurationDuplicationMaps.html"/>
-       <topic label="org.eclipse.ui.fontDefinitions" href="reference/extension-points/org_eclipse_ui_fontDefinitions.html"/>
-	    <topic label="org.eclipse.ui.handlers" href="reference/extension-points/org_eclipse_ui_handlers.html"/>
-       <topic label="org.eclipse.ui.helpSupport" href="reference/extension-points/org_eclipse_ui_helpSupport.html"/>
-       <topic label="org.eclipse.ui.ide.filesystemSupport" href="reference/extension-points/org_eclipse_ui_ide_filesystemSupport.html"/>
-       <topic label="org.eclipse.ui.ide.markerHelp" href="reference/extension-points/org_eclipse_ui_ide_markerHelp.html"/>
-       <topic label="org.eclipse.ui.ide.markerImageProviders" href="reference/extension-points/org_eclipse_ui_ide_markerImageProviders.html"/>
-       <topic label="org.eclipse.ui.ide.markerResolution" href="reference/extension-points/org_eclipse_ui_ide_markerResolution.html"/>
-        <topic label="org.eclipse.ui.ide.markerSupport" href="reference/extension-points/org_eclipse_ui_ide_markerSupport.html"/>
-       <topic label="org.eclipse.ui.ide.projectNatureImages" href="reference/extension-points/org_eclipse_ui_ide_projectNatureImages.html"/>
-       <topic label="org.eclipse.ui.ide.resourceFilters" href="reference/extension-points/org_eclipse_ui_ide_resourceFilters.html"/>
-       <topic label="org.eclipse.ui.importWizards" href="reference/extension-points/org_eclipse_ui_importWizards.html"/>
-       <topic label="org.eclipse.ui.installationPages" href="reference/extension-points/org_eclipse_ui_installationPages.html"/>
-       <topic label="org.eclipse.ui.intro" href="reference/extension-points/org_eclipse_ui_intro.html"/>
-       <topic label="org.eclipse.ui.intro.config" href="reference/extension-points/org_eclipse_ui_intro_config.html"/>
-       <topic label="org.eclipse.ui.intro.configExtension" href="reference/extension-points/org_eclipse_ui_intro_configExtension.html"/>
-	    <topic label="org.eclipse.ui.keywords" href="reference/extension-points/org_eclipse_ui_keywords.html"/>	    
-	    <topic label="org.eclipse.ui.menus" href="reference/extension-points/org_eclipse_ui_menus.html"/>
-       <topic label="org.eclipse.ui.navigator.linkHelper" href="reference/extension-points/org_eclipse_ui_navigator_linkHelper.html"/>
-	   <topic label="org.eclipse.ui.navigator.navigatorContent" href="reference/extension-points/org_eclipse_ui_navigator_navigatorContent.html"/>
-	   <topic label="org.eclipse.ui.navigator.viewer" href="reference/extension-points/org_eclipse_ui_navigator_viewer.html"/>
-       <topic label="org.eclipse.ui.newWizards" href="reference/extension-points/org_eclipse_ui_newWizards.html"/>
-       <topic label="org.eclipse.ui.perspectiveExtensions" href="reference/extension-points/org_eclipse_ui_perspectiveExtensions.html"/>
-       <topic label="org.eclipse.ui.perspectives" href="reference/extension-points/org_eclipse_ui_perspectives.html"/>
-       <topic label="org.eclipse.ui.popupMenus" href="reference/extension-points/org_eclipse_ui_popupMenus.html"/>
-       <topic label="org.eclipse.ui.preferencePages" href="reference/extension-points/org_eclipse_ui_preferencePages.html"/>
-       <topic label="org.eclipse.ui.preferenceTransfer" href="reference/extension-points/org_eclipse_ui_preferenceTransfer.html"/>
-       <topic label="org.eclipse.ui.presentationFactories" href="reference/extension-points/org_eclipse_ui_presentationFactories.html"/>
-       <topic label="org.eclipse.ui.propertiesView" href="reference/extension-points/org_eclipse_ui_propertiesView.html"/>
-       <topic label="org.eclipse.ui.propertyPages" href="reference/extension-points/org_eclipse_ui_propertyPages.html"/>
-       <topic label="org.eclipse.ui.splashHandlers" href="reference/extension-points/org_eclipse_ui_splashHandlers.html"/>
-       <topic label="org.eclipse.ui.startup" href="reference/extension-points/org_eclipse_ui_startup.html"/>
-       <topic label="org.eclipse.ui.statusHandlers" href="reference/extension-points/org_eclipse_ui_statusHandlers.html"/>
-       <topic label="org.eclipse.ui.systemSummarySections" href="reference/extension-points/org_eclipse_ui_systemSummarySections.html"/>
-       <topic label="org.eclipse.ui.themes" href="reference/extension-points/org_eclipse_ui_themes.html"/>
-       <topic label="org.eclipse.ui.viewActions" href="reference/extension-points/org_eclipse_ui_viewActions.html"/>
-       <topic label="org.eclipse.ui.views" href="reference/extension-points/org_eclipse_ui_views.html"/>
-       <topic label="org.eclipse.ui.views.properties.tabbed.propertyContributor" href="reference/extension-points/org_eclipse_ui_views_properties_tabbed_propertyContributor.html"/>
-       <topic label="org.eclipse.ui.views.properties.tabbed.propertySections" href="reference/extension-points/org_eclipse_ui_views_properties_tabbed_propertySections.html"/>
-       <topic label="org.eclipse.ui.views.properties.tabbed.propertyTabs" href="reference/extension-points/org_eclipse_ui_views_properties_tabbed_propertyTabs.html"/>
-       <topic label="org.eclipse.ui.workbench.texteditor.hyperlinkDetectors" href="reference/extension-points/org_eclipse_ui_workbench_texteditor_hyperlinkDetectors.html"/>
-       <topic label="org.eclipse.ui.workbench.texteditor.hyperlinkDetectorTargets" href="reference/extension-points/org_eclipse_ui_workbench_texteditor_hyperlinkDetectorTargets.html"/>
-       <topic label="org.eclipse.ui.workbench.texteditor.quickDiffReferenceProvider" href="reference/extension-points/org_eclipse_ui_workbench_texteditor_quickDiffReferenceProvider.html"/>
-       <topic label="org.eclipse.ui.workbench.texteditor.rulerColumns" href="reference/extension-points/org_eclipse_ui_workbench_texteditor_rulerColumns.html"/>
-       <topic label="org.eclipse.ui.workbench.texteditor.spellingEngine" href="reference/extension-points/org_eclipse_ui_workbench_texteditor_spellingEngine.html"/>
-       <topic label="org.eclipse.ui.workingSets" href="reference/extension-points/org_eclipse_ui_workingSets.html"/>
-       <topic label="org.eclipse.update.core.featureTypes" href="reference/extension-points/org_eclipse_update_core_featureTypes.html"/>
-       <topic label="org.eclipse.update.core.installHandlers" href="reference/extension-points/org_eclipse_update_core_installHandlers.html"/>
-       <topic label="org.eclipse.update.core.siteTypes" href="reference/extension-points/org_eclipse_update_core_siteTypes.html"/>
-       <topic href="reference/extension-points/org_eclipse_debug_core_breakpointImportParticipants.html" label="org.eclipse.debug.core.breakpointImportParticipants">
-       </topic>
-    </topic>
-
-	<topic label="OSGi API Reference" href="http://www.osgi.org/javadoc/r4v42"/>
-
-	<topic label="Other reference information" href="reference/misc/index.html">
-      	<topic label="Runtime options" href="reference/misc/runtime-options.html"/>
-      	<topic label="Eclipse Launcher" href="reference/misc/launcher.html"/>
-      	<topic label="API rules of engagement" href="reference/misc/api-usage-rules.html"/>
-      	<topic label="Naming conventions" href="reference/misc/naming.html"/>
-      	<topic label="Glossary of terms" href="reference/misc/terminology.html"/>
-      	<topic label="Map of platform plug-ins" href="reference/misc/overview-platform.html"/>
-      	<topic label="Starting Eclipse from Java" href="reference/misc/eclipsestarter.html"/>
-      	<topic label="Multi-user installs" href="reference/misc/multi_user_installs.html"/>		
-       	<topic label="Third party libraries and classloading" href="reference/misc/buddy_loading.html"/>
-      	<topic label="Plug-in manifest " href="reference/misc/plugin_manifest.html"/>
-       	<topic label="OSGi bundle manifest" href="reference/misc/bundle_manifest.html"/>
-     	<topic label="Project description file" href="reference/misc/project_description_file.html"/>
-		<topic label="Message bundles" href="reference/misc/message_bundles.html"/>
-		<topic label="Running on GCJ" href="reference/misc/gcj.html"/>
-		<topic label="The &quot;platform&quot; URL protocol" href="reference/misc/platform-scheme-uri.html"/>
-      	<topic label="Tips for making user interfaces accessible" href="reference/misc/ui_accessibility_tips.html"/>
-		<topic label ="Supporting bidirectional text" href="reference/misc/bidi.html"/>
-       	<topic label="How to write an Eclipse installer" href="reference/misc/eclipse-install.html"/>
-       	<topic label="About.ini file format" href="reference/misc/about_customization.html"/>
-       	<topic label="Plug-in archives" href="reference/misc/plugin_archive.html"/>
-       	<topic label="Feature manifest" href="reference/misc/feature_manifest.html"/>
-       	<topic label="Feature archives" href="reference/misc/feature_archive.html"/>
-       	<topic label="The platform.xml file" href="reference/misc/update_platform_xml.html"/>
-       	<topic label="Running update manager from command line" href="reference/misc/update_standalone.html"/>
-        <topic href="reference/misc/p2_dropins_format.html" label="The dropins folder and supported file layouts"/>
-   	</topic>
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Samples.xml b/bundles/org.eclipse.platform.doc.isv/topics_Samples.xml
deleted file mode 100644
index 17fee3e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/topics_Samples.xml
+++ /dev/null

@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define topics for the samples                                                 -->
-<!-- ============================================================================= -->
-<toc label="Examples" >
-   <topic label="Installing the examples" href="samples/samples.html" />
-   <topic label="Standard Widget Toolkit">
-      <topic label="Using the SWT example launcher" href="samples/org.eclipse.swt.examples.launcher/doc-html/swt_launcher_ex.html" />
-      <topic label="Running and browsing the SWT examples manually" href="samples/org.eclipse.swt.examples/doc-html/swt_manual_setup.html" />
-      <topic label="Stand-alone examples" >
-        <topic label="Address book" href="samples/org.eclipse.swt.examples/doc-html/swt_addressbook_ex.html" />
-        <topic label="Clipboard" href="samples/org.eclipse.swt.examples/doc-html/swt_clipboard_ex.html" />
-        <topic label="File viewer" href="samples/org.eclipse.swt.examples/doc-html/swt_fileviewer_ex.html"/>
-        <topic label="Hello world" href="samples/org.eclipse.swt.examples/doc-html/swt_helloworld_ex.html"/>
-        <topic label="Hover help" href="samples/org.eclipse.swt.examples/doc-html/swt_hoverhelp_ex.html"/>
-        <topic label="Image analyzer" href="samples/org.eclipse.swt.examples/doc-html/swt_imageanalyzer_ex.html"/>
-        <topic label="Java syntax viewer" href="samples/org.eclipse.swt.examples/doc-html/swt_javaviewer_ex.html"/>
-        <topic label="Text editor" href="samples/org.eclipse.swt.examples/doc-html/swt_texteditor_ex.html"/>
-      </topic>
-      <topic label="Workbench views" >
-        <topic label="Browser" href="samples/org.eclipse.swt.examples.browser/doc-html/swt_browser_ex.html"/>
-        <topic label="Controls" href="samples/org.eclipse.swt.examples.controls/doc-html/swt_controls_ex.html"/>
-        <topic label="Custom Controls" href="samples/org.eclipse.swt.examples.controls/doc-html/swt_customcontrols_ex.html"/>
-        <topic label="Layout" href="samples/org.eclipse.swt.examples.layouts/doc-html/swt_layout_ex.html"/>
-        <topic label="OLE" href="samples/org.eclipse.swt.examples.ole.win32/doc-html/swt_ole_ex.html" />
-        <topic label="Paint" href="samples/org.eclipse.swt.examples.paint/doc-html/swt_paint_ex.html"/>
-      </topic>
-   </topic>
-
-   <topic label="Workbench">
-      <topic label="Field assist example" href="samples/org.eclipse.ui.examples.fieldassist/doc-html/ui_fieldassist_ex.html" />
-      <topic label="Java editor" href="samples/org.eclipse.ui.examples.javaeditor/doc-html/ui_javaeditor_ex.html" />
-      <topic label="Template editor" href="samples/org.eclipse.ui.examples.javaeditor/doc-html/ui_templateeditor_ex.html" />
-      <topic label="Multi page editor" href="samples/org.eclipse.ui.examples.multipageeditor/doc-html/ui_multipageeditor_ex.html" />
-      <topic label="Property sheet" href="samples/org.eclipse.ui.examples.propertysheet/doc-html/ui_propertysheet_ex.html" />
-      <topic label="Readme tool" href="samples/org.eclipse.ui.examples.readmetool/doc-html/ui_readmetool_ex.html" />
-      <topic label="Undo example" href="samples/org.eclipse.ui.examples.undo/doc-html/ui_undo_ex.html" />
-   </topic> 
-
-   <topic label="Team">
-      <topic label="Repository Providers" href="samples/org.eclipse.team.examples.filesystem/doc-html/team_filesystem_ex.html" />
-      <topic label="Synchronize Participants" href="samples/org.eclipse.team.examples.filesystem/doc-html/team_localhistory_ex.html" />
-      <topic label="Logical Model Integration" href="samples/org.eclipse.team.examples.filesystem/doc-html/team_model_ex.html" />
-   </topic>
-     
-   <topic label="Compare">
-   	  <topic label="Structured Compare" href="samples/org.eclipse.compare.examples/doc-html/ui_structurecreator_ex.html" />
-   	  <topic label="XML Compare" href="samples/org.eclipse.compare.examples.xml/doc-html/ui_xmlcompare_ex.html" />
-   </topic>
-   
-</toc>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/blockselection.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/blockselection.png
deleted file mode 100644
index e0e9b68..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/blockselection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/button-order.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/button-order.png
deleted file mode 100644
index f55c0be..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/button-order.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/cairoaix.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/cairoaix.png
deleted file mode 100644
index 809e361..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/cairoaix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/datetime-dropdown.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/datetime-dropdown.png
deleted file mode 100644
index 83cf860..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/datetime-dropdown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/dnd.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/dnd.png
deleted file mode 100644
index f7f7ae2..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/dnd.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/editor.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/editor.png
deleted file mode 100644
index 6600d0d..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/filtered-tree.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/filtered-tree.png
deleted file mode 100644
index a3feda3..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/filtered-tree.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/injection_graph_func.js b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/injection_graph_func.js
deleted file mode 100644
index 7216ce4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/injection_graph_func.js
+++ /dev/null

@@ -1,463 +0,0 @@
-var skype_injection_path = 'chrome://skype_ff_toolbar_win/content/';

-var skype_tool = null;

-

-/*window.addEventListener("click",skype_click_handler,true);

-function skype_click_handler(event)

-{

-	if (skype_tool)

-		skype_tool.closemenu();

-	//HideSkypeMenuFull();

-} */

-

-//CALL BUTTON

-var SkypeActiveCallButtonPart = 0;

-function SkypeSetCallButtonPart(obj)

-{

-	if (obj.getAttribute('id') == '__skype_highlight_id_left')

-	{

-		SkypeActiveCallButtonPart = 0;

-	}

-	else if (obj.getAttribute('id') == '__skype_highlight_id_right')

-	{

-		SkypeActiveCallButtonPart = 1;

-	}

-}

-

-function SkypeSetCallButton(obj, hl, isInternational, isFax)

-{

-	var cb_part_l = null;

-	var cb_part_ml = null;

-	var cb_part_mr = null;

-	var cb_part_r = null;

-	if (obj.getAttribute('rtl') == 'false')

-	{

-		cb_part_l = obj.firstChild.firstChild;

-		cb_part_ml = obj.firstChild.lastChild;

-		cb_part_mr = obj.lastChild.firstChild;

-		cb_part_r = obj.lastChild.lastChild;

-

-		cb_flag = obj.firstChild.lastChild.firstChild;

-		if (cb_flag && cb_flag.isSameNode(obj.firstChild.firstChild.firstChild) == true)

-			cb_flag = null;

-	}

-	else

-	{

-		cb_part_l = obj.lastChild.lastChild;

-		cb_part_ml = obj.lastChild.firstChild;

-		cb_part_mr = obj.firstChild.lastChild;

-		cb_part_r = obj.firstChild.firstChild;

-

-		cb_flag = obj.lastChild.firstChild.lastChild;

-		if (cb_flag && cb_flag.isSameNode(obj.lastChild.lastChild.lastChild) == true)

-			cb_flag = null;

-	}

-

-	if (hl == 1)

-	{

-		cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_l.gif')";

-		if (cb_part_l.isSameNode(cb_part_ml) != true)

-			cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_m.gif')";

-		cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_m.gif')";

-

-

-		if (isInternational == "0")

-		{

-			if (SkypeActiveCallButtonPart == 0)    //left

-			{

-				cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseonflag_r"+(isFax?"_fax":"")+".gif')";

-				//shadow

-				if (cb_flag)

-				{

-					cb_flag.style.top = '1px';

-					cb_flag.style.left = '1px';

-					/*top right bottom left*/

-					cb_flag.style.padding = '1px 0px 0px 1px';//'2px 0px 0px 0px';

-				}

-			}

-			else                            //right

-			{

-				cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_r"+(isFax?"_fax":"")+".gif')";

-				//flag

-				if (cb_flag)

-				{

-					cb_flag.style.top = '0px';

-					cb_flag.style.left = '0px';

-					cb_flag.style.padding = '0px 1px 1px 0px';//'0px 1px 1px 0px';

-					cb_flag.style.margin = '0px 0px 2px 0px;';

-				}

-			}

-		}

-		else

-		{

-			cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_r"+(isFax?"_fax":"")+".gif')";

-			//flag

-			if (cb_flag)

-			{

-				cb_flag.style.top = '0px';

-				cb_flag.style.left = '0px';

-				cb_flag.style.padding = '0px 1px 1px 0px';

-				cb_flag.style.margin = '0px 0px 2px 0px;';

-			}

-		}

-	}

-	else

-	{

-		cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_l.gif')";

-		if (cb_part_l.isSameNode(cb_part_ml) != true)

-			cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_m.gif')";

-		cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_m.gif')";

-		cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_r"+(isFax?"_fax":"")+".gif')";

-

-		//flag

-		if (cb_flag)

-		{

-			cb_flag.style.top = '0px';

-			cb_flag.left = '0px';

-			cb_flag.style.padding = '0px 1px 1px 0px';

-			cb_flag.style.margin = '0px 0px 2px 0px;';

-		}

-	}

-}

-var skype_cb_l = '';

-var skype_cb_m = '';

-var skype_cb_r = '';

-

-function SkypeSetCallButtonPressed(obj, pr, isInternational, isFax)

-{

-	var cb_part_l = null;

-	var cb_part_ml = null;

-	var cb_part_mr = null;

-	var cb_part_r = null;

-	if (obj.getAttribute('rtl') == 'false')

-	{

-		cb_part_l = obj.firstChild.firstChild;

-		cb_part_ml = obj.firstChild.lastChild;

-		cb_part_mr = obj.lastChild.firstChild;

-		cb_part_r = obj.lastChild.lastChild;

-

-		cb_flag = obj.firstChild.lastChild.firstChild;

-		if (cb_flag && cb_flag.isSameNode(obj.firstChild.firstChild.firstChild) == true)

-			cb_flag = null;

-	}

-	else

-	{

-		cb_part_l = obj.lastChild.lastChild;

-		cb_part_ml = obj.lastChild.firstChild;

-		cb_part_mr = obj.firstChild.lastChild;

-		cb_part_r = obj.firstChild.firstChild;

-

-		cb_flag = obj.lastChild.firstChild.lastChild;

-		if (cb_flag && cb_flag.isSameNode(obj.lastChild.lastChild.lastChild) == true)

-			cb_flag = null;

-	}

-	if (pr == 1)

-	{

-		skype_cb_l = cb_part_l.style.backgroundImage;//getAttribute('src');

-		skype_cb_m = cb_part_mr.style.backgroundImage;

-		skype_cb_r = cb_part_r.style.backgroundImage;//getAttribute('src');

-

-		if (isInternational == "0")

-		{

-			if (SkypeActiveCallButtonPart == 0)    //left

-			{

-				//obj.firstChild.firstChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_l.gif');

-				cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_l.gif')";

-				if (cb_part_l.isSameNode(cb_part_ml) != true)

-					cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-			}

-			else                            //right

-			{

-				//obj.firstChild.firstChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_l.gif');

-				cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_l.gif')";

-				if (cb_part_l.isSameNode(cb_part_ml) != true)

-					cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-				cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-				//obj.lastChild.lastChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif');

-				cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif')";

-			}

-		}

-		else

-		{

-			//obj.firstChild.firstChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_l.gif');

-			cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_l.gif')";

-			if (cb_part_l.isSameNode(cb_part_ml) != true)

-				cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-			cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-				//obj.lastChild.lastChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif');

-			cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif')";

-		}

-	}

-	else

-	{

-		//obj.firstChild.firstChild.setAttribute('src', skype_cb_l);

-		cb_part_l.style.backgroundImage = skype_cb_l;

-		if (cb_part_l.isSameNode(cb_part_ml) != true)

-			cb_part_ml.style.backgroundImage = skype_cb_m;

-		cb_part_mr.style.backgroundImage = skype_cb_m;

-		//obj.lastChild.lastChild.setAttribute('src', skype_cb_r);

-		cb_part_r.style.backgroundImage = skype_cb_r;

-	}

-}

-

-//COMMANDS

-function SkypeToolBarInit(tb)

-{

-	skype_tool = tb;

-}

-

-function doRunCMDSkype(event, link, id, name)

-{

-	if (skype_tool)

-	{

-		if (link == 'chdial')

-		{

-			var obj=event.originalTarget;

-			if (!obj)

-				obj=event;

-

-			/*var brd=SkypeGetBounds(obj);

-		   var docelem = document.documentElement;

-		   if ((docelem.scrollTop == 0 && document.body.scrollTop != 0) || (docelem.scrollLeft == 0 && document.body.scrollLeft != 0))

-			   docelem=document.body;

-   

-		   scrollY=docelem.scrollTop;

-		   scrollX=docelem.scrollLeft;

-   

-		   var my=brd.top+16, mx=brd.left;/*brd.height*/

-

-			//var oDoc = obj.ownerDocument;

-

-			/*var obj2 = document.getBoxObjectFor(element);

-   

-		   var html_box = new XPCNativeWrapper(obj2).wrappedJSObject;

-		   if (!html_box)

-			 html_box = obj2;

-   

-		   var screenX = html_box.screenX;

-		   var screenY = html_box.screenY;

-			   */

-

-			SkypeFlagColor='rgb(184, 203, 255)';

-			skype_tool.chprefix(id, document, obj, screenY);

-		}

-		else if (link == 'copy')

-			skype_tool.copy_num(id, document);

-		else if (link == 'sms')

-			skype_tool.sms(id);

-		else if (link == 'add')

-			skype_tool.add(id, name);

-		else

-			skype_tool.call(id);

-	}

-}

-

-function runCMDSkype(link)

-{

-	HideSkypeFull();

-	doRunCMDSkype(null, link, skype_curid, skype_cur_name);

-}

-

-//FLAG TOOLTIP

-function HideSkypeFull()

-{

-	//   skype_active=false;

-	document.getElementById('skype_dc').style.visibility = "hidden";

-}

-

-function ShowSkype(event, title)

-{

-	//  skype_active=true;

-	DoShowSkype(event.pageX, event.pageY + 20, title);

-}

-

-function DoShowSkype(cX, cY, title)

-{

-	var menu = document.getElementById('skype_dc');

-	menu.firstChild.nodeValue = title;

-	menu.style.visibility = "visible";

-

-	menu.style.left = cX + 'px';

-	menu.style.top = cY + 'px';

-

-}

-var SkypeFlagColor = 'rgb(184, 203, 255)';

-function doSkypeFlag(obj, brd)

-{

-	SkypeFlagColor = brd;

-}

-

-//MENU

-var skype_curid = 0,skype_active = false,skype_showseed = 0,skype_ctm = 0,skype_cur_name = '';

-var skype_curbutton = null;

-function SkypeCheckCallButton(obj)

-{

-	var res = false;

-	if (skype_curbutton && skype_curbutton.isSameNode(obj) == true)

-		res = true;

-

-	skype_curbutton = obj;

-	return res;

-}

-

-function HideSkypeMenu()

-{                       //skype_tool.sd('HideSkypeMenu skype_active='+skype_active);

-	if (!skype_active)

-		HideSkypeMenuFull();

-	else

-		setTimeout("HideSkypeMenu()", 1000);

-}

-

-function HideSkypeMenu2(event)

-{

-	skype_showseed = 0;

-	if (!skype_active)

-		HideSkypeMenuFull();

-	else

-	{

-		skype_active = false;

-		setTimeout("HideSkypeMenu()", 1000);

-	}

-}

-

-function HideSkypeMenuFull()

-{                                 //skype_tool.sd('HideSkypeMenuFull skype_active='+skype_active);

-	/*   skype_active=false;

-	document.getElementById('skype_menu').style.visibility="hidden";*/

-}

-

-function CheckSkype()

-{

-	skype_active = true;

-}

-

-function ShowSkypeMenu(event, call_msg, id, callto, isMobile, name, x, y)

-{

-	try {

-		/*  	skype_active=true;       						//skype_tool.sd('ShowSkypeMenu skype_curid='+skype_curid+'   callto='+callto+'  id='+id);

-		if(document.getElementById('skype_menu').style.visibility!="hidden" && skype_curid==callto)//id

-		  return;

-		skype_showseed=Math.random();

-		clearTimeout(skype_ctm);

-	  var obj=event.originalTarget;

-	  if (!obj)

-		  obj=event;

-  //  	var brd=SkypeGetBounds(obj);

-		//var pcx=brd.left, pcy=brd.top+16;/*brd.height;* /   //alert(pcx+'--'+pcy);

-  

-	  scrolls=SkypeGetDivScroll(obj);

-  

-		var pcx = x+scrolls.left, pcy = y+scrolls.top;

-  

-		skype_ctm=setTimeout('DoShowSkypeMenu(\''+call_msg+'\','+skype_showseed+',"'+callto+'",'+pcx+','+pcy+','+isMobile+',"'+name+'")',0);*/

-	} catch(e) {

-	}

-}

-

-function DoShowSkypeMenu(call_msg, seed, callto, pcx, pcy, isMobile, name)

-{

-	try {                                                        //skype_tool.sd('DoShowSkypeMenu seed='+seed+'   skype_showseed='+skype_showseed);

-		/*  	if(seed!=skype_showseed)

-		  return;

-		skype_showseed=0;

-		skype_curid=callto;

-	  skype_cur_name=name;

-		var menu=document.getElementById('skype_menu');

-  

-		var my=pcy, mx=pcx;

-  

-	  var menubox=document.getBoxObjectFor(menu);

-	  //var docelem = document.documentElement;

-									//alert(menubox.height);

-									//alert('doc h='+document.height + ' y='+my+' menu h='+menubox.height);

-	  var docH=document.height;

-	  if (docH < document.documentElement.clientHeight) docH=document.documentElement.clientHeight;

-	  if (docH < document.documentElement.scrollHeight) docH=document.documentElement.scrollHeight;

-	  if (docH < document.body.clientHeight) docH=document.body.clientHeight;

-	  if (docH < document.body.scrollHeight) docH=document.body.scrollHeight;

-	  if ((my + menubox.height) > docH)

-		  my=my - 16 - menubox.height;

-	  if (my < 0) my=0;

-  //    if (document.height != 0 && (my + menubox.height) > document.height && (my + menubox.height) > document.documentElement.scrollHeight)//docelem.clientHeight)

-		  //my=document.height - menubox.height;

-  

-	  var docW=document.width;

-	  if (docW < document.documentElement.clientWidth) docW=document.documentElement.clientWidth;

-	  if (docW < document.documentElement.scrollWidth) docW=document.documentElement.scrollWidth;

-	  if (docW < document.body.clientWidth) docW=document.body.clientWidth;

-	  if (docW < document.body.scrollWidth) docW=document.body.scrollWidth;

-	  if ((mx + menubox.width) > docW)

-		  mx=document.width - menubox.width;

-	  if (mx < 0) mx=0;

-  //	if (document.width != 0 && (mx + menubox.width) > document.width && (mx + menubox.width) > document.documentElement.scrollWidth)//docelem.clientWidth)

-  

-		menu.style.left=mx+'px';

-		menu.style.top=my+'px';

-  

-	  skype_tool.doFixMenu(menu, isMobile, document);

-  

-	  menu.style.visibility="visible";  */

-	} catch(e) {

-	}

-}

-

-function SkypeSetBgColor(obj, color)

-{

-	try {

-		obj.lastChild.style.backgroundColor = color;

-	} catch(e) {

-	}

-}

-

-//UTIL

-function SkypeGetBounds(element)

-{

-	try {

-		var left = element.left;

-		var top = element.top;

-		while (!(element.tagName.toLowerCase() == 'span' && element.getAttribute('id') == '__skype_highlight_id'))

-		{

-			element = element.parentNode;

-		}

-		left = element.offsetLeft;

-		top = element.offsetTop;

-		for (var parent = element.offsetParent; parent; parent = parent.offsetParent)

-		{

-			left += parent.offsetLeft;

-			top += parent.offsetTop;

-			if (parent.tagName.toLowerCase() == 'div')

-			{

-				left -= parent.scrollLeft;

-				top -= parent.scrollTop;

-			}

-		}

-

-

-		return {left: left, top: top, width: element.offsetWidth, height: element.offsetHeight};

-	} catch(e) {

-	}

-}

-

-function SkypeGetDivScroll(element)

-{

-	try {

-		var left = 0;

-		var top = 0;

-		while (!(element.tagName.toLowerCase() == 'span' && element.getAttribute('id') == '__skype_highlight_id'))

-		{

-			element = element.parentNode;

-		}

-

-		for (var parent = element.offsetParent; parent; parent = parent.offsetParent)

-		{

-			if (parent.tagName.toLowerCase() == 'div')

-			{

-				left -= parent.scrollLeft;

-				top -= parent.scrollTop;

-			}

-		}

-

-

-		return {left: left, top: top};

-	} catch(e) {

-	}

-}
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/jnigen.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/jnigen.png
deleted file mode 100644
index 6dd493f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/jnigen.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/link.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/link.png
deleted file mode 100644
index 952fce1..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/link.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/margins.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/margins.png
deleted file mode 100644
index e42745f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/margins.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/modified.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/modified.png
deleted file mode 100644
index f43bcbe..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/modified.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/multi-font-labels.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/multi-font-labels.png
deleted file mode 100644
index 430ecac..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/multi-font-labels.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/nautiluscopy.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/nautiluscopy.png
deleted file mode 100644
index bd491da..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/nautiluscopy.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/printdialog.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/printdialog.png
deleted file mode 100644
index e72548f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/printdialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/search.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/search.png
deleted file mode 100644
index bbd6eee..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet-prompt.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet-prompt.png
deleted file mode 100644
index ca022e8..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet-prompt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet.png
deleted file mode 100644
index 26ca3d7..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/sheet.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/showwelcome.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/showwelcome.png
deleted file mode 100644
index b5e3d16..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/showwelcome.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-intro.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-intro.png
deleted file mode 100644
index 2d6d150..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-intro.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-overview.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-overview.png
deleted file mode 100644
index b1d51e4..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/slate-overview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/solarisx86-browser.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/solarisx86-browser.png
deleted file mode 100644
index 7495671..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/solarisx86-browser.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout1.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout1.png
deleted file mode 100644
index c74901a..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout2.png b/bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout2.png
deleted file mode 100644
index addd05e..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/images/uiabout2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html b/bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html
deleted file mode 100644
index 59ecbe6..0000000
--- a/bundles/org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html
+++ /dev/null

@@ -1,578 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2009. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page.">
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../book.css"  type="text/css">
-<style type="text/css">
-td {border-top: solid thin black;}
-img[alt] {background-color:#ffdddd;}
-tr {vertical-align: top;}
-</style>
-<title>Eclipse Platform What's New in 3.5</title>
-</head>
-
-<body>
-
-<h1>What's New in 3.5</h1>
-
-<p>Here are descriptions of some of the changes of interest to plug-in developers
-made to the Eclipse <a href="#Platform">Platform</a>, <a href="#Equinox">Equinox</a> and
-<a href="#SWT">SWT</a> for the 3.5 release of Eclipse.</p>
-
-<p>
-There are also many new features oriented towards end-users of the platform
-that can be viewed in the 
-<a href="../../org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html">What's new</a>
-section of the Workbench User Guide.
-</p>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table cellpadding="10" cellspacing="0" width="600">
-  <colgroup>
-  <col width="20%">
-  <col width="80%">
-  </colgroup>
-  <tbody>
-
-<!-- ******************** Platform ********************** -->
-<tr>
-
-<td colspan="2"><a name="Platform"></a>
-<div style="font-size: 20px; font-weight: bold;">Platform Changes</div>
-</td>
-</tr>
-
-  <tr id="added-ds">
-    <td width="30%" valign="top" align="left"><b>Declarative services added to the platform</b></td>
-    <td width="70%" valign="top">The Eclipse rich client platform now includes an implementation 
-    of OSGi declarative services (DS). This allows a lazy-starting plug-in to make OSGi services available
-    to other plug-ins before it has been started. Finally the powerful OSGi dynamic service architecture
-    can be fully exploited in the Eclipse world of lazy activation. DS also includes support for
-    dependency injection, so services can be injected into plain old Java objects (POJOs),
-    without adding a dependency on the OSGi framework into your application code. This
-    new platform bundle is complemented by new tooling support in PDE for declarative services.
-    </td>
-  </tr>
-
-    <TR id="comparePlugin">
-      <TD vAlign=top align=left width="30%"><B>Compare Core Plug-in</B></TD>
-      <TD vAlign=top width="70%">Some of the patching functionality provided
-        by the compare plug-in has been refactored into a separate <code>org.eclipse.compare.core</code> plug-in
-        that can be used by headless Eclipse applications</TD>
-    </TR>
-
-  <tr id="filteredtree">
-    <td width="30%" valign="top" align="left"><b>Improved look for filtered tree</b></td>
-    <td width="70%" valign="top">The button for clearing the filter field of filtered trees has
-     been moved into the text box, even for platforms that don't have a native search field with
-     this functionality. 
-     <p>For backwards compatibility reasons, existing subclasses of <code>FilteredTree</code>
-     will not get the new look automatically. Clients of the <code>FilteredTree</code> 
-     are encouraged to switch to the new look as recommended in the 
-     <a href="../porting/3.5/recommended.html#NewFilteredTreeLook">porting guide</a>.</p>  
-     <p><img src="images/filtered-tree.png" alt="New look of filter field"></p>
-    </td>
-  </tr>
-
-  <tr id="multifontlabels">
-    <td width="30%" valign="top" align="left"><b>Multiple fonts in one cell</b></td>
-    <td width="70%" valign="top">The existing owner draw support for JFace <code>TableViewer</code> and
-    <code>TreeViewer</code> has been extended to allow multiple fonts within cells. For example, this can be used to
-    highlight matching text in search results using a bold font.
-      <p><img src="images/multi-font-labels.png" alt="Table with normal and bold font within the same cells"></p>
-    </td>
-  </tr>
-
-  <tr id="sheets">
-    <td width="30%" valign="top" align="left"><b>Using sheets on Mac Cocoa</b></td>
-    <td width="70%" valign="top">For general prompts and dialogs regarding editors, or
-    the current Workbench window, sheets are now used on Mac Cocoa. In addition to the 
-    new style bit <code>SWT.SHEET</code>, new API has been added to <code>MessageDialog</code> 
-    and <code>MessageDialogWithToggle</code> so that clients can set the appropriate style for their dialogs.
-      <p><img src="images/sheet-prompt.png" alt="Prompting to save using a sheet" ></p>
-  </td>
-  </tr>
-
-  <tr id="jface-button-order">
-    <td width="30%" valign="top" align="left"><b>JFace dialog button order on GTK+</b></td>
-    <td width="70%" valign="top">JFace dialogs now respect the default button
-    order on the GTK+ platform.  Example: "Cancel" "OK".  It is possible to revert
-    the order used by SWT and JFace, see
-    <a href="../../org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html#buttonorder">Alternate button order</a>.
-    <p><img src="images/button-order.png" alt="Preference Dialog showing Cancel, OK"></p>
-    </td>
-  </tr>
-
-  <tr id="checkstateprovider">
-    <td width="30%" valign="top" align="left"><b>New "check state" provider</b></td>
-    <td width="70%" valign="top">
-      JFace now has a new type of provider, called <code>ICheckStateProvider</code>, that can be used to
-      manage the checked and gray states of elements in <code>CheckboxTableViewer</code> or <code>CheckboxTreeViewer</code>
-      objects. This is useful in situations where the viewer should come up with pre-checked
-      elements, or when the check state changes are not always triggered by the user.
-    </td>
-  </tr>
-
-  <tr id="showWelcomeCheckbox">
-    <td width="30%" valign="top" align="left"><b>Show welcome checkbox</b></td>
-    <td width="70%" valign="top">A checkbox can be added to a welcome page that will cause the 
-      welcome to show when Eclipse is restarted, even if it was closed previously. The 
-      unextended Eclipse platform does not show this checkbox, but it can be added using 
-      an intro extension that uses the class <code>AlwaysWelcomeCheckbox</code> as a content provider.
-      <p>The example below shows this checkbox added to the <b>What's New</b> page.</p>
-      <p> <img src="images/showwelcome.png" alt="Show Welcome checkbox"></p>
-     </td>
-  </tr>
-
-  <tr id="helpContentFilter">
-    <td width="30%" valign="top" align="left"><b>Help content filter</b></td>
-    <td width="70%" valign="top">A new extension point <code>org.eclipse.help.webapp.contentFilter</code> 
-    allows for pre-processing of help content before it is delivered from the help server.</td>
-  </tr>
-
-   <tr id="jetty">
-    <td width="30%" valign="top" align="left"><b>Jetty version 6.1</b></td>
-    <td width="70%" valign="top">Version 6.1 of the <a href="http://www.mortbay.org/jetty/">Jetty</a> Web server is now included in the platform,
-    replacing the 5.1 version in the previous release. This brings along an implementation
-    of version 2.5 of the <code>javax.servlet</code> API, replacing the 2.4 version in the Ganymede release.
-    </td>
-  </tr>
-
-  <tr id="new-icu4j">
-    <td valign="top" align="left"><b>New release of ICU4J</b></td>
-    <td valign="top">The platform has adopted a major new release of the
-    <a href="http://icu-project.org/">ICU4J</a> localization library: version 4.0. This
-    release includes support for Unicode 5.1, and the Unicode standard 
-    <a href="http://www.unicode.org/press/pr-cldr1.6.html">Common Locale Data Repository (CLDR) 1.6</a>
-    See the ICU4J 4.0 <a href="http://icu-project.org/download/4.0.html">release notes</a> for more details.
-    </td>
-  </tr>
-
-  <tr id="extensible-about">
-    <td width="30%" valign="top" align="left"><b>Extensible installation details</b></td>
-    <td width="70%" valign="top">The <b>About Dialog</b> now provides a mechanism for plug-ins to 
-       contribute <b>installation pages</b> to the platform about dialog.  The buttons for showing feature, 
-       plug-in, and configuration details have been replaced by a single <b>Installation Details</b> button.
-       <p> <img src="images/uiabout1.png" alt="About Dialog with Installation Details button" title="About Dialog"></p>
-       <p>Pushing this button will launch a dialog that shows all of the installation pages contributed by
-       plug-ins in a single <b>Installation Details</b> dialog.  Plug-ins may contribute installation pages and
-       define buttons that operate on the information in the installation page.</p>
-       <p> <img src="images/uiabout2.png" alt="Installation Details dialog showing contributions from multiple plug-ins" title="Installation Details Dialog"></p>
-       <p>The new extension point is <b>org.eclipse.platform.ui.installationPages</b>.  Example implementations
-       can be found by browsing the hierarchy of <b>org.eclipse.ui.about.InstallationPage</b>.</p>
-    </td>
-  </tr>
-
-  <tr id="intro_slate_theme">
-    <td width="30%" valign="top" align="left"><b>New intro theme</b></td>
-    <td width="70%" valign="top">A new intro theme called "Slate" has been added. 
-     Slate is not the default theme for Eclipse but can be specified using the 
-        preference <code>org.eclipse.ui.intro/INTRO_THEME=org.eclipse.ui.intro.universal.slate</code>. The main differences in the root page between the new
-      theme and the two existing themes are:
-      <ul>
-        <li>Each link has a label.</li>
-        <li>The images are transparent and will display well if a background is
-        added using an extension.</li>
-        <li>The page displays well at high screen resolutions.</li>
-      </ul>
-      <p> <img src="images/slate-intro.png" alt="Slate intro theme"></p>
-      <p>Non root pages also have a label for each link.</p>
-      <p> <img src="images/slate-overview.png" alt="Slate overview page."></p>
-     </td>
-  </tr>
-
-<!-- ******************** Equinox ********************** -->
-<tr>
-
-<td colspan="2"><a name="Equinox"></a>
-<div style="font-size: 20px; font-weight: bold;">Equinox Changes</div>
-</td>
-</tr>
-
-  <tr id="p2-publisher"> 
-    <td width="30%" valign="top" align="left"><b>New publisher bundle</b></td>
-    <td width="70%" valign="top"><a href="http://wiki.eclipse.org/p2">p2</a> has introduced a new bundle
-    called the publisher, which provides infrastructure for generating, packaging, and publishing metadata and artifacts
-    into p2 repositories. The publisher provides an extensible API that clients
-    can extend to perform customized publishing to repositories, and includes an <i>advice</i> mechanism for injecting
-    additional metadata into the generation and packaging process.</td>
-  </tr>
-
-  <tr id="equinox-concurrency"> 
-    <td width="30%" valign="top" align="left"><b>New Equinox concurrency API</b></td>
-    <td width="70%" valign="top">This release includes a new provisional API for futures. Futures 
-      facilitate handling of concurrency and synchronization in multi-threaded and/or 
-      distributed systems. They serve as a proxy for a result that is not known, 
-      because the computation of the result is not yet complete. See the 
-      <a href="http://wiki.eclipse.org/Equinox/Futures">wiki documentation</a>
-      for more details on this new experimental concurrency API.
-    </td>
-  </tr>
-
-  <tr id="dynamicDebugOptions"> 
-    <td width="30%" valign="top" align="left"><b>Enhanced DebugOptions</b></td>
-    <td width="70%" valign="top">The Equinox <code>DebugOptions</code> API has been enhanced
-    to support dynamic changes to option settings. Now debug option settings can be modified while
-    an application is running to facilitate problem determination and support. A new interface,
-    <code>DebugOptionsListener</code>, can be registered as a service to enable your plug-in to
-    respond to dynamic debug option changes.
-    </td>
-  </tr>
-
-  <tr id="debugTrace"> 
-    <td width="30%" valign="top" align="left"><b>New tracing API</b></td>
-    <td width="70%" valign="top">A new debug tracing API, <code>org.eclipse.osgi.service.debug.DebugTrace</code>,
-    has been added to enhance and simply writing of debug trace messages in your code. 
-    The <code>DebugTrace</code> object will take care of writing additional trace information along
-    with your message, such as your bundle symbolic name, and the class, method, and line
-    in which the tracing message was written. This reduces clutter in the code being traced, while ensuring
-    that consistent and complete contextual information is recorded. The tracing data can
-    either be directed to a file, or written on stdout, depending on the setting of <code>DebugOptions#setFile</code>.
-    By default the Eclipse platform will write trace data to the file <code>trace.log</code> in the workspace
-    metadata location (next to the platform log file).
-    </td>
-  </tr>
-
-  <tr id="permission-admin"> 
-    <td width="30%" valign="top" align="left"><b>Security Manager enhancements</b></td>
-    <td width="70%" valign="top">This release includes an implementation of the updated Conditional Permission Admin
-    Specification included in the OSGi Service Platform Core Specification Release 4, Version 4.2.
-    This version of the specification includes enhancements to the Conditional Permission Admin service which is used to manage 
-    the permissions assigned to bundles.  The enhancements include adding the ability to grant or deny permissions based on conditions,
-    and to manage conditions as an ordered list of rules.  For more information see the <a href="http://www.osgi.org/Release4/Download">OSGi Release 4 Version 4.2 specification</a>.</td>
-  </tr>
-
-  <tr id="service-hooks">
-    <td width="30%" valign="top" align="left"><b>OSGi service registry enhancements</b></td>
-    <td width="70%" valign="top">
-       This release includes an implementation of the new Service Hooks Specification
-       included in the OSGi Service Platform Core Specification Release 4, Version 4.2.  
-       Certain specialized bundles need to be able to alter 
-       output results of service layer's find and event delivery operations to 
-       affect their purpose.  The Service Hooks Specification enhances the service registry to allow 
-       service registry hooks to affect the service registry's find and event 
-       delivery operations.  
-    <p>The Service Hooks Specification is targeted at bundles which need to observe and react to
-       selected service layer operations. In general these will be highly 
-       specialized bundles written by systems programmers.  The service hooks are not 
-       intended to be used by so-called "normal" application bundles.
-       For more information see the <a href="http://www.osgi.org/Release4/Download">OSGi Release 4 Version 4.2 specification</a>.</p></td>
-  </tr>
-
-  <tr id="framework-launching">
-    <td width="30%" valign="top" align="left"><b>OSGi framework launching</b></td>
-    <td width="70%" valign="top">
-       The OSGi Service Platform Core Specification Release 4, Version 4.2 defines a standard 
-       way to launch an OSGi framework implementation.
-       This release of Equinox includes an implementation the OSGi standard launching APIs.
-       A framework implementation must provide a factory class. A factory class is 
-       an indirection to create a framework implementation object. The implementation factory 
-       class must implement the FrameworkFactory interface.  A launcher can use the following ways 
-       to get this class name:
-       <ul>
-        <li>The Java-SE Service Provider Configuration model.</li>
-        <li>Get it from some configuration and use Class.forName.</li>
-        <li>Hardcode the factory name.</li>
-       </ul>
-       To create a framework instance a launcher uses the FrameworkFactory to constructs the 
-       implementation's Framework object.  The Framework can then be
-       used to control the lifecycle of the framework (e.g. start, stop, update
-       etc.)  The <code>org.eclipse.osgi.launch.EquinoxFactory</code> class is the public
-       class in Equinox which implements the new 
-       <code>org.osgi.framework.launch.FrameworkFactory</code> interface.  
-    <p>This Release 4, Version 4.2 specification also defines standard configuration properties which all 
-       framework implementations must recognize.  This allows for a generic
-       framework launcher to be implemented that can launch any framework 
-       implementation. 
-       For more information see the <a href="http://www.osgi.org/Release4/Download">OSGi Release 4 Version 4.2 specification</a>.</p></td>
-  </tr>
-
-  <tr id="declarative-services">
-    <td width="30%" valign="top" align="left"><b>OSGi Declarative Services Changes</b></td>
-    <td width="70%" valign="top">
-      This release includes an implementation of the updated Declarative Services
-      Specification included in the OSGi Service Platform Core Specification Release 4, Version 4.2.
-      The following list highlights the changes to Declarative Services for Version 4.2 of the 
-      OSGi Specification:
-      <ul>
-        <li>The definition of the <code>Service-Component</code> header now uses the definition of a 
-	  header from the module layer. It also allows wild-cards to be used in the 
-	  last component of  the path of a header entry.</li>
-        <li>The DS runtime now follows the recommendations of Property Propagation and
-	   does not propagate properties whose names start with '.' to service properties. </li>
-        <li>The component description now allows for a configuration policy to 
-	  control whether component configurations are activated when configuration 
-	  objects are present or not.</li>
-        <li>The component description now allows the names of the activate and 
-	  deactivate methods to be specified. The signatures of the activate and 
-	  deactivate methods are also modified.</li>
-        <li>Additional signatures of the bind and unbind methods have been added.</li>
-        <li>The definition of accessible methods for activate, deactivate, bind and 
-	  unbind methods is expanded to include any method accessible from the 
-	  component implementation class. This allows private and package 
-	  private method declared in the component implementation class to be 
-	  used.</li>
-        <li>The XML schema and name space have been updated to v1.1.0. It now 
-	  allows for wild-carded attributes and elements for extensibility. The 
-	  name attribute of the component element is now optional and the 
-	  default value of this attribute is the value of the class attribute of the 
-	  nested implementation element. The name attribute of the reference 
-	  element is now optional and the default value of this attribute is the 
-	  value of the interface attribute of the reference element. The Char type 
-	  for the property element has been renamed Character to match the Java 
-	  type name. The attributes configuration-policy, activate and deactivate 
-	  have been added to the component element.</li>
-        <li>When logging error messages, SCR now uses a <code>LogService</code> obtained 
-	  using the component's bundle context so that the resulting log entry is 
-	  associated with the component's bundle. </li>
-        <li>Target properties are now component properties that can be set 
-	  wherever component properties can be set, including configurations.</li>
-      </ul>
-    <p>
-       For more information see the <a href="http://www.osgi.org/Release4/Download">OSGi Release 4 Version 4.2 specification</a>.
-    </p></td>
-  </tr>
-
-  <tr id="OSGiR42">
-    <td width="30%" valign="top" align="left"><b>New core framework API</b></td>
-    <td width="70%" valign="top">
-        The OSGi Service Platform Core Specification Release 4, Version 4.2 is adding a number of small API additions
-        to the core Framework.  The following is a list of API additions included in this release.
-        <br>
-        <dl>
-          <dt><b>org.osgi.framework.Bundle#getVersion()</b></dt> 
-            <dd>Returns the Version of a bundle.</dd>
-          <dt><b>org.osgi.framework.Bundle#getSignerCertificates()</b></dt>
-            <dd>Returns the signers of a bundle.</dd>
-          <dt><b>org.osgi.framework.BundleException#getType()</b></dt>
-            <dd>Returns the error type for a BundleException.  For example, a resolver error.</dd>
-          <dt><b>org.osgi.framework.BundleReference</b></dt>
-            <dd>Interface which must be implemented by bundle classloaders.  This gives clients the ability to determine what bundle a ClassLoader is for.</dd>
-          <dt><b>org.osgi.framework.Constants</b></dt>
-            <dd>A number of new constants have been added to define standard launching configuration properties.</dd>
-          <dt><b>org.osgi.framework.FrameworkEvent</b></dt>
-            <dd>A number of new FrameworkEvent types have been added give launchers standard notification when a framework is stopped or restarted.</dd>
-          <dt><b>org.osgi.framework.FrameworkUtil#getBundle(Class)</b></dt>
-            <dd>Utility to get a Bundle object for a given class.  A static method equivalent to the PackageAdmin#getBundle(Class) method.</dd>
-          <dt><b>org.osgi.framework.FrameworkUtil#matchDistinguishedNameChain(String, List)</b></dt>
-            <dd>Utility to match a certificate chain against a pattern.  This is used for permission and condition checks against signed bundles.</dd>
-          <dt><b>org.osgi.framework.ServiceEvent</b></dt>
-            <dd>A new ServiceEvent type has been added to indicate the properties of a registered service have been modified and the new
-            properties no longer match a listener's filter.</dd>
-          <dt><b>org.osgi.framework.ServiceException</b></dt>
-            <dd>A new ServiceException type has been added to indicate that a service problem occurred.</dd>
-          <dt><b>org.osgi.util.tracker.BundleTracker</b></dt>
-            <dd>The BundleTracker class simplifies tracking bundles much like the ServiceTracker simplifies tracking services.</dd>     
-        </dl>
-    </td>
-  </tr>
-
-  <tr id="rfc132">
-    <td width="30%" valign="top" align="left"><b>Composite bundles</b></td>
-    <td width="70%" valign="top">
-        This release includes an implementation of the Composite Bundles specification.  
-        The Composite Bundles specification is a proposed specification for the OSGi 
-        Release 4, Version 4.2 specification.  In a large system built upon a large number of modules, 
-        sometimes it is necessary to provide a mechanism for isolating the various 
-        modules from each other at runtime. Composite Bundles introduces a concept  
-        to provide isolation for a group of bundles.
-        <p>  
-        Conceptually a composite bundle is composed of 
-        a set of bundles which are contained in another (nested) framework instance.
-        New API is introduced in the <code>org.osgi.service.framework</code> package to 
-        manage composite bundles.  The <code>CompositeBundleFactory</code> service interface is 
-        used to install composite bundles.  The <code>CompositeBundle</code> interface is used to 
-        manage the bundles which compose a composite bundle.
-        </p>
-        <p>
-        For more information see the <a href="http://www.osgi.org/Release4/Download">OSGi Release 4 Version 4.2 specification</a>.
-        </p>
-        <p>
-        <b>Note:</b> The API introduced in the <code>org.osgi.service.framework</code> package 
-        is a proposed OSGi API.  This API is considered provisional in Equinox and 
-        may change drastically or be dropped altogether in a future release of 
-        Equinox.  We encourage use of the API and any feedback on the 
-        specification, but consumers must be aware that breaking changes may occur
-        in a future release. 
-        </p>  
-    </td>
-  </tr>
-
-<!-- *********************** SWT *********************** -->
-<tr>
-<td colspan="2"><a name="SWT"></a>
-<div style="font-size: 20px; font-weight: bold;">SWT Changes</div>
-</td>
-</tr>
-
-    <TR id="cairoAIX">
-      <TD vAlign=top align=left width="30%"><B>Cairo on AIX</B></TD>
-      <TD vAlign=top width="70%">Cairo support has been added to Eclipse on AIX.
-        This enables advanced graphics support on AIX.
-        <P><IMG alt="Cairo on AIX" src="images/cairoaix.png" ></p></TD>
-    </tr>
-	<tr id="jni-generator"> 
-    <td width="30%" valign="top" align="left"><b>JNI Generator</b></td>
-    <td width="70%" valign="top">A new plug-in based tool has been added to simplify the process of generating the SWT JNI code. 
-    	For more info click <a href="http://www.eclipse.org/swt/jnigen.php">here</a>.
-     <p><img src="images/jnigen.png" alt="Cairo on AIX"></p>
-	 </td>
-  </tr>
-
-  <tr id="blockselection">
-    <td width="30%" valign="top" align="left"><b>Block selection in StyledText</b></td>
-    <td width="70%" valign="top"><code>StyledText</code> can be switched into block selection mode with new API <code>StyledText.setBlockSelection(true)</code>.
-	<p>
-	  <img src="images/blockselection.png" alt="Block Selection in StyledText">
-	</p>
-    </td>
-  </tr>
-
-   <tr id="jstojava">
-    <td width="30%" valign="top" align="left"><b>JavaScript-to-Java</b></td>
-    <td width="70%" valign="top">JavaScript can now call out to Java in the <code>Browser</code> widget.
-    Supported types are numbers, booleans, strings, null, and arrays (example 
-    <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet307.java?view=co">
-    snippet</a>).
-    </td>
-  </tr>
-
-   <tr id="javatojs">
-    <td width="30%" valign="top" align="left"><b>Improved Java-to-JavaScript</b></td>
-    <td width="70%" valign="top">Java can now call into JavaScript.  An expression is evaluated in the context of a Browser document and 
-     a value is returned.  Supported types are numbers, booleans, strings, null's, and arrays (example 
-    <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet308.java?view=co">
-    snippet</a>).
-    </td>
-  </tr>  
-
-   <tr id="caretListener">
-    <td width="30%" valign="top" align="left"><b>New caret listener</b></td>
-    <td width="70%" valign="top">New API has been added to <code>StyledText</code> to allow you to listen for changes in the caret offset.
-    See <code>StyledText.addCaretListener()</code> and <code>StyledText.removeCaretListener()</code> for more information.
-    </td>
-  </tr>
-
-   <tr id="texteditor">
-    <td width="30%" valign="top" align="left"><b>New text editor demo</b></td>
-    <td width="70%" valign="top">This new example makes extensive use of <code>StyledText</code> to demonstrate how it can be
-	used to create a multi-font rich text editor with bullets, links and embedded objects.
-    	<p>
-	  		<img src="images/editor.png" alt="Text Editor">
-		</p>
-    </td>
-  </tr>    
-
-  <tr id="swtsearch">
-    <td width="30%" valign="top" align="left"><b>Improved search field</b></td>
-    <td width="70%" valign="top">The <code>SWT.SEARCH</code> style is now supported on 
-	all platforms, allowing the application to display a text message when 
-	the control is awaiting input. The <code>SWT.ICON_SEARCH</code> and 
-	<code>SWT.ICON_CANCEL</code> hints control the appearance of the search field (example 
-	<a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet309.java?view=co">
-	snippet</a>).
-	<p><img src="images/search.png" alt="Text with SWT.SEARCH"></p></td>
-  </tr>
-
-  <tr id="nautilus-copypaste"> 
-    <td width="30%" valign="top" align="left"><b>Improved copy and paste 
-	support</b></td>
-    <td width="70%" valign="top">Support has been added to the <code>FileTransfer</code> 
-	class to allow for copy/paste operations between the Explorer and 
-	the Nautilus file manager.
-     <p><img src="images/nautiluscopy.png" alt="Nautilus copy"></p></td>
-  </tr>
-
-  <tr id="stlinks"> 
-    <td width="30%" valign="top" align="left"><b>Links in StyledText</b></td>
-    <td width="70%" valign="top"><code>StyledText</code> now allows users to add
-	hyperlinks to the text in the widget. 
-     <p><img src="images/link.png" alt="Link in StyledText"></p></td>
-  </tr>
-
-  <tr id="setMargins">
-    <td width="30%" valign="top" align="left"><b>StyledText margin spacing and color</b></td>
-    <td width="70%" valign="top">
-		New API has been added to <code>StyledText</code> to set margin spacing and color. 
-		See <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet316.java?revision=1.1&amp;view=markup">Snippet316</a>.
-		<p><img src="images/margins.png" alt="StyledText with margins"></p>
-	</td>
-  </tr>
-  
-  <tr id="disablescript">
-    <td width="30%" valign="top" align="left"><b>Disabling Javascript</b></td>
-    <td width="70%" valign="top">
-		Javascript can be disabled from running in a Browser with the new API <code>Browser.setJavascriptEnabled(boolean)</code>.
-	</td>
-  </tr>
-
-  <tr id="cookies">
-    <td width="30%" valign="top" align="left"><b>Browser wants a cookie</b></td>
-    <td width="70%" valign="top">
-		Cookies can be created and accessed in the Browser with new API <code>Browser.setCookie()</code> and <code>Browser.getCookie()</code>.
-	</td>
-  </tr>
-
-  <tr id="authlistener">
-    <td width="30%" valign="top" align="left"><b>Authentication listener</b></td>
-    <td width="70%" valign="top">
-		Browser clients can now provide a listener that responds to basic authentication challenges.  This is 
-		useful for enabling users to access sites without presenting them with a manual authentication prompter.
-		See <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet317.java?revision=1.1&amp;view=markup">Snippet317</a>.
-	</td>
-  </tr>
-
-  <tr id="modifiedshell">
-    <td width="30%" valign="top" align="left"><b>Shell modified state hint</b></td>
-    <td width="70%" valign="top">
-		New API has been added to <code>Shell</code> to provide a user hint that the window is in a modified state.
-		See <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet314.java?revision=1.1&amp;view=markup">Snippet314</a>.
-		<p><img src="images/modified.png" alt="Shell.setModified"></p>
-	</td>
-  </tr>
-
-  <tr id="datetimedropdown"> 
-    <td width="30%" valign="top" align="left"><b>DateTime DROP_DOWN</b></td>
-    <td width="70%" valign="top"><code>DateTime</code> widgets created with <code>SWT.DATE</code> style can now also have <code>SWT.DROP_DOWN</code> style.
-     <p><img src="images/datetime-dropdown.png" alt="DateTime with DROP_DOWN style"></p></td>
-  </tr>
-
-  <tr id="sheet">
-    <td width="30%" valign="top" align="left"><b>SWT.SHEET style for Shell and Dialog</b></td>
-	<td width="70%" valign="top">Sheet windows are now supported on Mac OS X Cocoa.
-      <p><img src='images/sheet.png' alt="Shell with SWT.SHEET style"></p>
-	</td>
-  </tr>
-
-  <tr> 
-    <td width="30%" valign="top" align="left"><b>Mozilla browser support on Solaris x86</b></td>
-    <td width="70%" valign="top">Mozilla browser support has been added to the Solaris x86 platform.
-		<p><img src="images/solarisx86-browser.png" alt="Solaris x86 Browser"></p>
-	</td>
-  </tr>
-
-  <tr id="cocoadnd">
-    <td width="30%" valign="top" align="left"><b>Improved DND feedback on Cocoa</b></td>
-    <td width="70%" valign="top">Cocoa drag and drop in trees and tables is now fully supported. Aside
-	from the visual feedback, other native features are supported, such as automatic collapse of tree items
-	when the drag is finished.
-	<p><img src='images/dnd.png' alt='Cocoa drag and drop feedback'></p>
-	</td>
-  </tr>
-
-  <tr id="paperorientation"> 
-    <td width="30%" valign="top" align="left"><b>Paper orientation</b></td>
-    <td width="70%" valign="top">Applications can now programmatically select portrait or landscape mode when printing,
-    or when opening a PrintDialog.
-     See <a href="http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet318.java?view=co">Snippet318</a>.
-     <p><img src="images/printdialog.png" alt="PrintDialog seeded with Landscape orientation"></p></td>
-  </tr>
-
-<!-- ****************** END OF N&N TABLE ****************** -->
-  </tbody>
-</table>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.isv/workbench.png b/bundles/org.eclipse.platform.doc.isv/workbench.png
deleted file mode 100644
index c3f7d3f..0000000
--- a/bundles/org.eclipse.platform.doc.isv/workbench.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/.project b/bundles/org.eclipse.platform.doc.user/.project
deleted file mode 100644
index 24f4a52..0000000
--- a/bundles/org.eclipse.platform.doc.user/.project
+++ /dev/null

@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>org.eclipse.platform.doc.user</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-		<buildCommand>
-			<name>org.eclipse.pde.ManifestBuilder</name>
-			<arguments>
-			</arguments>
-		</buildCommand>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.pde.PluginNature</nature>
-	</natures>
-</projectDescription>

diff --git a/bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs b/bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs
deleted file mode 100644
index f7c96b7..0000000
--- a/bundles/org.eclipse.platform.doc.user/.settings/org.eclipse.pde.prefs
+++ /dev/null

@@ -1,12 +0,0 @@
-#Tue May 03 09:54:45 EDT 2005
-compilers.p.deprecated=1
-compilers.p.no-required-att=0
-compilers.p.not-externalized-att=1
-compilers.p.unknown-attribute=0
-compilers.p.unknown-class=0
-compilers.p.unknown-element=1
-compilers.p.unknown-resource=1
-compilers.p.unresolved-ex-points=0
-compilers.p.unresolved-import=0
-compilers.use-project=true
-eclipse.preferences.version=1

diff --git a/bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF b/bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF
deleted file mode 100644
index 2fd59c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/META-INF/MANIFEST.MF
+++ /dev/null

@@ -1,8 +0,0 @@
-Manifest-Version: 1.0
-Bundle-ManifestVersion: 2
-Bundle-Name: %pluginName
-Bundle-SymbolicName: org.eclipse.platform.doc.user; singleton:=true
-Bundle-Version: 3.6.0.qualifier
-Bundle-Vendor: %providerName
-Bundle-Localization: plugin
-Require-Bundle: org.eclipse.help;bundle-version="[3.2.0,4.0.0)"

diff --git a/bundles/org.eclipse.platform.doc.user/about.html b/bundles/org.eclipse.platform.doc.user/about.html
deleted file mode 100644
index b71e25d..0000000
--- a/bundles/org.eclipse.platform.doc.user/about.html
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<title>About</title>
-</head>
-<body lang="EN-US">
-<h2>About This Content</h2>
- 
-<p>June 2, 2006</p>	
-<h3>License</h3>
-
-<p>The Eclipse Foundation makes available all content in this plug-in (&quot;Content&quot;).  Unless otherwise 
-indicated below, the Content is provided to you under the terms and conditions of the
-Eclipse Public License Version 1.0 (&quot;EPL&quot;).  A copy of the EPL is available 
-at <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
-For purposes of the EPL, &quot;Program&quot; will mean the Content.</p>
-
-<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is 
-being redistributed by another party (&quot;Redistributor&quot;) and different terms and conditions may
-apply to your use of any object code in the Content.  Check the Redistributor's license that was 
-provided with the Content.  If no such license exists, contact the Redistributor.  Unless otherwise
-indicated below, the terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at <a href="http://www.eclipse.org">http://www.eclipse.org</a>.</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/book.css b/bundles/org.eclipse.platform.doc.user/book.css
deleted file mode 100644
index c65a811..0000000
--- a/bundles/org.eclipse.platform.doc.user/book.css
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/build.properties b/bundles/org.eclipse.platform.doc.user/build.properties
deleted file mode 100644
index a0fd002..0000000
--- a/bundles/org.eclipse.platform.doc.user/build.properties
+++ /dev/null

@@ -1,21 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2007 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-#
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-customBuildCallbacks=customBuildCallbacks.xml
-
-
-bin.includes = META-INF/,\
-               plugin.properties,\
-               *.xml, *.zip,*.html,*.htm,*.png,book.css,concepts/, gettingStarted/, images/,\
-               reference/, tasks/, tips/, whatsNew/, index*/
-               
-               
-bin.excludes = build.properties,\
-			   customBuildCallbacks.xml

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm
deleted file mode 100644
index 2049658..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/accessmain.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html lang="en">
-
- <head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
- <meta name="keyword" content="shortcut key, accelerator key, hot key, hotkey">
- <meta name="keyword" content="shortcut keys, accelerator keys, hot keys, hotkeys">
- <meta name="keyword" content="accessibility, disability, special needs">
- <meta name="keyword" content="accessible, disabilities, special need">
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>Accessibility features for Eclipse</title>
- <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
- <body>
-
- <h1>Accessibility features in Eclipse</h1>
- <p>
- Accessibility features help people with a physical disability, such as 
- restricted mobility or limited vision, or those with special needs to use 
- software products successfully. These are the major accessibility features in
- Eclipse:</p>
- <ul>
-   <li>Eclipse uses Microsoft Active 
-   Accessibility (MSAA) APIs to render user interface elements accessible to 
-   assistive technology.</li>
-   <li>You can operate all features using the keyboard instead of the mouse. See 
-   the related task. </li>
-   <li>You can use screen-reader software such as Freedom Scientific's JAWS <sup>TM</sup>
-    and a digital speech synthesizer to hear what is displayed on the 
-   screen. You can also use voice recognition software,
-   such as IBM ViaVoice <sup>TM</sup> to enter data and to navigate the user 
-   interface.</li>
-   <li>You can magnify what is displayed on your screen in the graphical views.
-   </li>
-   <li>Fonts and colors defined by Eclipse can be set using the
-   <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-   <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-   <strong>General &gt; Appearance &gt; Colors and Fonts</strong></a>
-   preference page. See the related link.
-   </li>
- </ul>
- <p><strong>Note: </strong>The Accessibility features mentioned in 
- this document apply to the Windows operating system.
- </p>
- <p><img src="../../images/ngrelt.png" alt="Related tasks" border="0" ><br>
- 	<a href="navigation.htm">Navigating the user interface using the keyboard</a><br>
- 	<a href="text_editor.htm">Configuring accessibility features for textual editors</a></p>
- <p><img src="../../images/ngrelr.png" alt="Related references" border="0" ><br>
- <a href="keyboardshortcuts.htm">Keys</a><br>
-  <a href="fontsandcolors.htm">Font and color settings in Eclipse</a><br>
-  <a href="../../reference/ref-7.htm">Accessibility preference page</a></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm
deleted file mode 100644
index cf6f1a9..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/colordialog.htm
+++ /dev/null

@@ -1,535 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-  <title>Color Dialog Mappings Table</title>
-</head>
-
-<body>
-<h1>Windows Color Dialog Reference</h1>
-<p>Below are the tables that show the colors of the fonts in the matrix of the 
-  Windows color dialog and the color settings that each of these correspond to.</p>
-<h2>Windows Color Dialog Color Matrix</h2>
-<table border="1">
-  <col >
-  <col span=2 >
-  <col  span=5 >
-  <tr bordercolor="#000000" > 
-    <td > <div align="center">salmon</div></td>
-    <td> <div align="center">pale yellow</div></td>
-    <td > <div align="center">pale green</div></td>
-    <td > <div align="center">spring green</div></td>
-    <td> <div align="center">pale turquoise</div></td>
-    <td > <div align="center">deep sky blue</div></td>
-    <td> <div align="center">pale rose</div></td>
-    <td > <div align="center">pink</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">red</div></td>
-    <td > <div align="center">yellow</div></td>
-    <td > <div align="center">apple green</div></td>
-    <td > <div align="center">light green</div></td>
-    <td > <div align="center">aqua</div></td>
-    <td > <div align="center">turquoise</div></td>
-    <td > <div align="center">pale slate blue</div></td>
-    <td > <div align="center">magenta</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">chocolate</div></td>
-    <td > <div align="center">pumpkin</div></td>
-    <td > <div align="center">lime</div></td>
-    <td > <div align="center">teal</div></td>
-    <td > <div align="center">dark turquoise</div></td>
-    <td > <div align="center">medium slate blue</div></td>
-    <td > <div align="center">maroon</div></td>
-    <td > <div align="center">rose</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">dark red</div></td>
-    <td > <div align="center">dark orange</div></td>
-    <td > <div align="center">green</div></td>
-    <td > <div align="center">sea green</div></td>
-    <td > <div align="center">blue</div></td>
-    <td > <div align="center">medium blue</div></td>
-    <td > <div align="center">purple</div></td>
-    <td > <div align="center">blueviolet</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">dark brown</div></td>
-    <td > <div align="center">saddle brown</div></td>
-    <td > <div align="center">dark forest green</div></td>
-    <td > <div align="center">dark teal</div></td>
-    <td > <div align="center">navy </div></td>
-    <td > <div align="center">midnight blue</div></td>
-    <td > <div align="center">dark purple</div></td>
-    <td > <div align="center">dark blueviolet</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="center">black</div></td>
-    <td > <div align="center">olive</div></td>
-    <td > <div align="center">dark olive</div></td>
-    <td > <div align="center">grey</div></td>
-    <td > <div align="center">light teal</div></td>
-    <td > <div align="center">light grey</div></td>
-    <td > <div align="center">dark purple</div></td>
-    <td > <div align="center">white</div></td>
-  </tr>
-</table>
-<h2>Settings for Default Colors in the Windows Color Dialog</h2>
-<p></p>
-<table border="1">
-  <col >
-  <col span=2 >
-  <col  span=5 >
-  <tr bordercolor="#000000"  > 
-    <td width="95"  > <div align="left"><strong>Color</strong></div></td>
-    <td width="22" > <div align="right"><strong>Hue</strong></div></td>
-    <td width="58" > <div align="right"><strong>Saturation</strong></div></td>
-    <td width="63" > <div align="right"><strong>Lumination</strong></div></td>
-    <td width="21" > <div align="right"><strong>Red</strong></div></td>
-    <td width="37" > <div align="right"><strong>Green </strong></div></td>
-    <td width="26" > <div align="right"><strong>Blue</strong></div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">apple green</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">aqua</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">black</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">blueviolet</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">chocolate</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark blueviolet</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark brown</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark forest green</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark olive</div></td>
-    <td  > <div align="right">40</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark orange</div></td>
-    <td  > <div align="right">20</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark purple</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark purple</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark red</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark teal</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">dark turquoise</div></td>
-    <td  > <div align="right">140</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">deep sky blue</div></td>
-    <td  > <div align="right">140</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">green</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">grey</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">light green</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">light grey</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">181</div></td>
-    <td  > <div align="right">192</div></td>
-    <td  > <div align="right">192</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">light teal</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">lime</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">magenta</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">maroon</div></td>
-    <td  > <div align="right">220</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">medium blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">75</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">160</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">medium slate blu<span style='display:
-  none'>e</span></div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">midnight blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">30</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">navy </div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">olive</div></td>
-    <td  > <div align="right">40</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale green</div></td>
-    <td  > <div align="right">80</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale rose</div></td>
-    <td  > <div align="right">220</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale slate blue</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">81</div></td>
-    <td  > <div align="right">151</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale turquoise</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pale yellow</div></td>
-    <td  > <div align="right">40</div></td>
-    <td > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pink</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">pumpkin</div></td>
-    <td  > <div align="right">13</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">150</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">purple</div></td>
-    <td  > <div align="right">200</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">red</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">rose</div></td>
-    <td  > <div align="right">220</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">saddle brown</div></td>
-    <td  > <div align="right">20</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">salmon</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">180</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">sea green</div></td>
-    <td  > <div align="right">100</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">64</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">spring green</div></td>
-    <td  > <div align="right">100</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">teal</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">60</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">128</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">turquoise</div></td>
-    <td  > <div align="right">133</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">90</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">128</div></td>
-    <td  > <div align="right">192</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">white</div></td>
-    <td  > <div align="right">160</div></td>
-    <td  > <div align="right">0</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-  </tr>
-  <tr bordercolor="#000000"  > 
-    <td  > <div align="left">yellow</div></td>
-    <td  > <div align="right">40</div></td>
-    <td  > <div align="right">240</div></td>
-    <td  > <div align="right">120</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">255</div></td>
-    <td  > <div align="right">0</div></td>
-  </tr>
-</table>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm
deleted file mode 100644
index 1278cfa..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/fontsandcolors.htm
+++ /dev/null

@@ -1,144 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
-  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-  <title>Fonts and colors in Eclipse</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-
-<h1>Fonts and colors in Eclipse</h1>
-<p>Eclipse uses the fonts and colors provided by the operating system as much 
-  as possible. On Windows the platform color and font settings are found on the 
-  <b>Preferences &gt; Colors and Fonts</b> page. The font used by most widgets 
-  in Eclipse is the one set in the Message Box settings of the properties. However, 
-  operating systems do not provide enough colors to handle all of the extra information 
-  that colors and fonts provide in Eclipse.&nbsp;</p>
-<h2>Fonts</h2>
-
-<p>There are 4 main fonts in use by the Eclipse platform. They are: </p>
-
-<dl>
-  <dt><em>Banner Font</em></dt>
-  <dd>Used in PDE editors, welcome pages and in the title area of many wizards. 
-    For instance the New Project wizard uses this font for the top title,</dd>
-  <dt><em>Header Font</em></dt>
-  <dd>Used as a section heading. For instance the Welcome page for the Eclipse 
-    Platform uses this font for the top title,</dd>
-  <dt><em>Text Font</em></dt>
-  <dd>Used in text editors.</dd>
-  <dt><em>Dialog Font</em></dt>
-  <dd>Used in dialogs.</dd>
-</dl>
-<p>These fonts can be set via the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a> preference page. 
-  As well as these 4 fonts there are several other secondary font settings. These 
-  default to the text font. They can be found on the Colors and Fonts preference 
-  page:</p>
-<ul>
-  <li><b>Compare Text Font</b></li>
-  <li><b>Console Text Font</b></li>
-  <li><b>CVS Console Font</b></li>
-  <li><b>Debug Console Font</b></li>
-  <li><b>Detail Pane Text Font</b></li>
-  <li><b>Java Compare Text Font</b></li>
-  <li><b>Java Editor Text Font</b></li>
-  <li><b>Memory Views Table Font</b></li>
-  <li><b>Part Title Font</b> (optional: used by some presentations)</li>
-  <li><b>View Message Font</b> (optional: used by some presentations)</li>
-</ul>
-<h2>Colors</h2>
-<p>Eclipse uses colors as an information enhancement in many places. Whenever
-possible the operating system color settings are used, but in cases where the
-operating system settings are not enough, Eclipse defines other colors. All of
-these colors can be adjusted via the following preference pages:</p>
-<ul>
-  <li><b><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a> &gt; Basic </b> (Error text, hyperlink text, active hyperlink text)</li>
-  <li><b><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.GeneralTextEditor)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Editors &gt; Text Editors</b></a></b> (Foreground, background and other appearance colors)</li>
-  <li><b><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Annotations)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Editors &gt; Text Editors &gt; Annotations</b></a></b> (Text editors annotation colors)</li>
-  <li><b><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.LinkedModePreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Editors &gt; Text Editors &gt; Linked Mode</b></a></b> (Text editors linked mode colors)</li>
-  <li><b><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.QuickDiff)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Editors &gt; Text Editors &gt; Quick Diff</b></a></b> (Colors used by text editors quick diff feature)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.search.preferences.SearchPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Search</b></a> (Foreground for potential matches)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.ConsolePreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Run/Debug &gt; Console</b></a> (Standard Out, Standard Error, Standard In)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.DebugPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Run/Debug</b></a> (Variable Views changed value, Memory View unbuffered lines)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Ant</b></a> (Error, Warning, Information, Verbose, Debug)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Java &gt; Editor</b></a> (Line number, matching brackets, current line, 
-    print, find scope, hyperlink, selection foreground, selection background)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.JavaEditorColoringPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Java &gt; Editor &gt; Syntax Coloring</b></a> (Javadoc HTML tags, 
-    Javadoc keywords, Javadoc links, Javadoc others, keyword 'return', keywords 
-    excluding 'return', Method names, Multi line comment, Operators and brackets, 
-    Others, Single-line comment, Strings, Task Tags)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jdt.ui.preferences.CodeAssistPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Java &gt; Editor &gt; Content Assist</b></a> (completion proposal background, 
-    completion proposal foreground, method parameter background, method parameter 
-    foreground, completion overwrite background, completion overwrite foreground)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.pde.ui.EditorPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Plug-in Development &gt; Editors</b></a> (Text, Processing instructions, 
-    Constant strings, Tags, Comments)</li>
-  <li><a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ConsolePreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Team &gt; CVS &gt; Console</b></a> (Command line, Message, Error)</li>
-</ul>
-<h2><img src="../../images/win_only.png" alt="Windows only" border="0" >Accessibility 
-  and the Windows Color Dialog</h2>
-<p>For color selection, Eclipse uses a dialog provided by the operating system. 
-  On windows, the color selection dialog does not respond properly to assistive 
-  technology. When you first get into the dialog, focus is on one of the basic 
-  colors, but the dialog provides no indication of this through assistive technology. 
-  You can select colors in Eclipse with this dialog in the following way:</p>
-<ol>
-  <li> Select to customize the color of something in Eclipse, for example the 
-    color of Error Text in your Workbench Colors and Fonts Basic preferences.</li>
-  <li> In the color selection dialog, tab twice to go from the Basic Color matrix 
-    to the Define Custom Colors button and press Enter.</li>
-  <li> You can now enter the basic colors using an HSL or RGB specification according 
-    to the following definitions. See the<a href="colordialog.htm"> Windows Color 
-    Dialog Reference</a> for a tables and values for these colors.<br>
-  </li>
-</ol>
-<p><img src="../../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-<a href="accessmain.htm">Accessibility features in Eclipse</a><br>
-<a href="navigation.htm">Navigating the user interface by using the keyboard</a>
-</p>
-
-<p><img src="../../images/ngrelr.png" alt="Related references" border="0" ><br>
-<a href="keyboardshortcuts.htm">Keys</a><br>
-<a href="colordialog.htm"> Windows Color 
-    Dialog Reference</a> 
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm
deleted file mode 100644
index 496baab..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/keyboardshortcuts.htm
+++ /dev/null

@@ -1,209 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-	<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
-	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-	<title>Keys</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-<h1>Keys</h1>
-<p>
-The function of the keyboard can be extensively customized in Eclipse using the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Keys</strong></a>
-
-preference page. Within Eclipse, key strokes and key sequences are assigned to
-invoke particular commands. 
-</p>
-<h2>Key Strokes, Key Sequences, and Key Bindings</h2>
-<p>
-A 'key stroke' is the pressing of a key on the keyboard, while optionally holding down one 
-or more of these modifier keys: <code>Ctrl</code>, <code>Alt</code> (<code>Option</code> on the Macintosh), <code>Shift</code>, or 
-<code>Command</code> (only on the Macintosh.) For example, holding down <code>Ctrl</code> then 
-pressing <code>A</code> produces the key stroke <code>Ctrl+A</code>. The pressing of the modifier keys themselves
-do not constitute key strokes.
-</p>
-<p>
-A 'key sequence' is one or more key strokes. Traditionally, Emacs assigned two or three key stroke key sequences to particular 
-commands. For example, the normal key sequence assigned to <code>Close All</code> in emacs is <code>Ctrl+X Ctrl+C</code>. 
-To enter this key sequence, one presses the key stroke <code>Ctrl+X</code> followed by the key stroke <code>Ctrl+C</code>.
-While Eclipse supports key sequences of arbitrary lengths, it is recommended
-that keyboard shortcuts be four key strokes in length (or less).
-</p>
-<p>
-A 'key binding' is the assignment of a key sequence to a command.
-</p>
-<h2>Schemes</h2>
-<p>
-A 'scheme' is a set of bindings. Eclipse includes two schemes:
-</p>
-<ul>
-<li>Default</li>
-<li>Emacs (extends Default)</li>
-</ul>
-<p>
-The <em>Default</em> scheme contains a general set of bindings, in many cases recognizable 
-as traditional key sequences for well known commands. For instance, <code>Ctrl+A</code> 
-is assigned to <code>Select All</code>, and <code>Ctrl+S</code> is assigned to <code>Save</code>.
-</p>
-<p>
-The <em>Emacs</em> scheme contains a set of key bindings familiar to users of Emacs.
-For instance, <code>Ctrl+X H</code> is assigned to <code>Select All</code>, and <code>Ctrl+X S</code> is assigned to <code>Save</code>.
-</p>
-<p>
-It is important to understand why the <em>Emacs</em> scheme says that it 'extends Default'. The <em>Emacs</em> scheme
-is not a complete set of bindings like the <em>Default</em> scheme. Rather, it borrows from the <em>Default</em>
-scheme where possible, only defining explicit Emacs-style bindings where they vary from the
-<em>Default</em> scheme. Generally, only well known commands like <code>Select All</code>, <code>Save</code>, etc. have specific Emacs key sequences associated with them. 
-</p>
-<p>Choose the scheme you are most comfortable with by changing the 'Scheme' setting on the
-keys preference page. If you choose the <em>Default</em> scheme, all <em>Emacs</em> bindings are ignored. If you choose
-the <em>Emacs</em> scheme, explicit Emacs-style key sequence assignments take precedence over any conflicting assignments in the <em>Default</em> scheme.
-</p>
-<h2>Contexts</h2>
-<p>
-Key bindings can vary based on the current context of Eclipse. 
-</p>
-<p> Sometimes the active part might be a Java file editor, for instance, where 
-  a different set of key sequence assignments may be more appropriate than if 
-  the active part was an html file editor. As a specific example, typically <code>Ctrl+B</code> 
-  is assigned to <code>Build</code> in a context such as Java file editing, while 
-  <code>Ctrl+B</code> is assigned to <code>Make Text Bold</code> in a context 
-  such as HTML file editing. This context is usually determined by the active
-  part, but it can be influenced by the active window or dialog as well. If the
-  active part does not choose a particular context, the workbench will set the 
-  active context to <em>In Windows</em>.</p>
-<p>Eclipse includes a number of different contexts. Some examples are: </p>
-<ul>
-  <li>In Dialogs and Windows</li>
-  <li>In Windows (extends In Dialogs and Windows)</li>
-  <li>In Dialogs (extends In Dialogs and Windows)</li>
-  <li>Editing Text (extends In Windows)</li>
-  <li>Editing Java Source (extends Editing Text)</li>
-  <li>Debugging (extends In Windows)</li>
-  <li>Debugging Java (extends Debugging)</li>
-  <li>In Console</li>
-  <li>Editing Ant buildfiles<br>
-    <br>
-  </li>
-</ul>
-<p> Much like configurations, contexts can extend other contexts. For example, 
-  the <em>Editing Java Source</em> context borrows key bindings from the <em>Editing Text</em> 
-  context, which in turn borrows key bindings from the <em>In Windows</em> context. 
-</p>
-<p>Note: It is not recommended to promote a key binding to a context which it
-extends.  For example, it is not recommended to move an <em>Editing Text</em> key
-binding to the <em>In Dialogs and Windows</em> context.  This may have unexpected
-results.</p>
-<p>It is possible for some key bindings to work in dialogs.  Those key bindings
-are assigned to the <em>In Dialogs and Windows</em> context.  One example of such a
-key binding is the key binding for "cut".  It is possible to change these key
-bindings.  For example, it is possible to have Ctrl+X as cut in dialogs, but
-Ctrl+W as cut in windows.</p>
-<h2>Platform and Locale</h2>
-<p>
-Key bindings also vary by platform and locale. On the Macintosh platform, <code>Command+S</code> is assigned to <code>Save</code>, instead of the usual <code>Ctrl+S</code>. On Chinese locales (zh), <code>Alt+/</code> is assigned to <code>Content Assist</code>, instead of the usual <code>Ctrl+Space</code>.
-</p>
-<p>
-The current platform and locale is determined when Eclipse starts, and does not vary over the course of an Eclipse instance.
-</p>
-<h2>Customizing Key bindings</h2>
-<p> With multi-stroke key sequences, schemes, and contexts, there are a 
-  lot of things to keep in mind when customizing key bindings. To make things 
-  easier, all key customization is done on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Keys</b></a> preference page.
-</p>
-<p> <img src="../../images/keys1.png" alt="Keys preference page the About command with no binding" > 
-</p>
-<p>
-In this example we want to bind <b>CTRL+5</b> to the About command.  By default
-the keys preference page will show you all possible keybindings.  You can see
-the About command listed in the Help category.  You can bind the command
-by putting focus in the Binding text box and pressing CTRL and 5 like you
-would if you were executing the command.
-</p>
-<p> <img src="../../images/keys2.png" alt="Keys preference page the About command bound to CTRL+5" ></p>
-<p>
-When you type CTRL+5 you have created a binding for About.  The right-most column 
-will indicate that this is a user binding by displaying a <b>U</b>.  If there was
-a conflict with another key, this column would also display a <b>C</b>. The binding
-will be in the default context, &quot;In Windows&quot;.  You can now
-use the When combo box to change the key binding context (for example, to move
-this binding to &quot;Editing Text&quot;).
-</p>
-<p>
-If you wanted to add a second key binding to About, you can use the
-<b>Copy Command</b> button to create a second command entry for you to bind
-another key to.  If you want to delete a binding, you can either use the
-<b>Remove Binding</b> button or simply give focus to the Binding text box
-and hit <b>Backspace</b>.
-</p>
-
- <h2>The Dynamic Nature of Key bindings</h2>
-<p>
-Key bindings are provided by plug-ins, and in Eclipse, plug-ins can be added or removed. 
-This can cause key bindings declared by these plug-ins to be added or removed. 
-Eclipse stores custom key bindings in a way to compensate for this. 
-Consider the example above where <code>CTRL+6</code> was assigned 
-to <code>About</code> in the <em>Default</em> scheme. Say you install a new 
-plug-in that assigns <code>CTRL+6</code> to a particular 
-command. Eclipse will preserve your assignment to <code>About</code>.
-</p>
-<h2>Conflict Resolution</h2>
-<p> There are only a finite number of simple, common key strokes available to 
-  assign to a multitude of commands. We have seen that scheme, context, 
-  platform, and locale all partition key sequence assignments into domains where 
-  they don't conflict with one another. Consider the case for <code>Ctrl+B</code> 
-  above if contexts did not exist. One plug-in would assign <code>Ctrl+B</code> 
-  to <code>Build</code>, the other plug-in would assign <code>Ctrl+B</code> to 
-  <code>Make Bold Text</code>. How would Eclipse properly resolve this conflict? 
-</p>
-<p> Though conflicts are drastically reduced by employing the above mechanisms, 
-  they can still occur. Two plug-ins, independent of one another, could assign 
-  the same key sequence to different commands with the same context, scheme, 
-  platform, and locale. Consider if a plug-in assigned <code>Ctrl+F4</code> in 
-  the <em>In Windows</em> context and <em>Default</em> scheme to one of its 
-  commands. This directly conflicts with Eclipse assigning <code>Ctrl+F4</code> 
-  to the close command in the same context and scheme. </p>
-<p>
-This is a conflict. It wouldn't be proper to invoke both commands, nor would it be proper to simply choose one of the two commands to receive the key stroke.
-We pop up the Key Assist Dialog with the conflicting commands and allow the user
-to select one.  The Key Assist Dialog is the same dialog that displays
-command choices for multiple key stroke key bindings.  For example, if 2 commands
-were bound to <b>F12</b> you might see:
-</p>
-<p> <img src="../../images/keys3.png" alt="Keys Assist dialog" ></p>
-<p>
-If the user sets a keybinding and creates a conflict, the conflicting bindings
-will be displayed in the conflicts list.  This can be used to navigate between
-conflicting keybindings so that they can be changed.
-</p>
-<p> <img src="../../images/keys4.png" alt="Keys preference page conflict list" ></p>
-<p> These types of conflicts can be resolved by explicitly assigning 
-  the key sequence to one of the commands, or remove it from the other. </p>
-<p>
-Another type of conflict can be caused by multiple-key stroke key sequences. For example, in the <em>Emacs</em> scheme, there are many multiple-key stroke key sequences beginning with the key stroke <code>Ctrl+X</code>. <code>Ctrl+X K</code> is assigned to <code>Close</code>. <code>Ctrl+X H</code> is assigned to <code>Select All</code>.
-</p>
-<p>
-As previously mentioned, the <em>Emacs</em> scheme borrows key bindings from the <em>Default</em> scheme. In the default scheme, <code>Ctrl+X</code> is assigned to <code>Cut</code>. Though the <em>Emacs</em> scheme doesn't explicitly redefine <code>Ctrl+X</code>, pressing <code>Ctrl+X</code> is required as part of many of its key bindings. In the <em>Emacs</em> scheme, when one presses <code>Ctrl+X</code>, one is half way to entering one of many possible assigned key sequences. One would not expect the <code>Cut</code> action to be invoked at this time.
-</p>
-<p>
-For this type of conflict, the rule is that the <code>Ctrl+X</code> key sequence assigned to <code>Cut</code> would be ignored. Otherwise, it would not be possible to complete many of the key bindings in the <em>Emacs</em> configuration. 
-</p>
-<p><img src="../../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="accessmain.htm">Accessibility features in Eclipse</a><br>
-<a href="../../tasks/tkeybindings.htm">Changing the key bindings</a><br>
-<a href="../help.htm">Help</a></p>
-<p><img src="../../images/ngrelr.png" alt="Related references" ><br>
-  <a href="fontsandcolors.htm">Font and color settings in Eclipse</a></p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm
deleted file mode 100644
index cb15d1b..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/navigation.htm
+++ /dev/null

@@ -1,123 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
- <LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
- <title>Navigating the user interface using the keyboard</title>
-</head>
-
- <body>
-
- <h1>Navigating the user interface using the keyboard</h1>
- <p>The user interface is navigable using the keyboard. The Tab key is used to
- iterate through the controls in a particular scope (for example, a dialog or a view and
- its related icons). To navigate to the main controls for the Workbench window
- or to tab out of views that use the Tab key (such as editors) use Ctrl+Tab.</p>
- <h2>Menus</h2>
- <p>Most menus are assigned mnemonics for each entry which allow you to
- select them by typing the underlined letter instead of the mouse. You can also
- select an item by moving through the menus and sub-menus with the arrow keys. </p>
- <p>The various menus available can be accessed using the keyboard in the
- following ways: </p>
- <ul>
-  <li>F10 accesses the menus on the main menu bar.</li>
-  <li>Shift+F10 pops up the context menu for the current view. (Note: this
-  shortcut is actually dependent on your window manager, but for most people it
-  should be Shift+F10.)</li>
-  <li>Ctrl+F10 will open the pull down menu for the current view if there is
-    one.  For editors, Ctrl+F10 will open the menu for the marker bar on the left of the
-    editor area.</li>
-  <li>Alt+mnemonic will activate the Workbench menu for a particular entry
-    (e.g., Alt+W will bring down the <u>W</u>indow menu).</li>
-  <li>Microsoft Windows only: Pressing Alt will give focus to the menu
-  bar.</li>
- </ul>
- <h2>Controls</h2>
- <p>Mnemonics are assigned to most control labels (e.g., buttons, checkboxes,
- radio buttons, etc.) in dialog boxes, preference pages, and property pages. To
- access the control associated with a label, use the Alt key along with the
- letter that is underlined in the label.</p>
- <h2>Navigation Context</h2>
- <p>Navigation context is saved for the packages, navigator views, Workbench preferences and properties dialogs.
- The selected page for the preferences and properties dialog is saved between
- invocations of the dialog but are not saved between workbench invocations. </p>
- <h2>Cycling Editors, Views and Perspectives </h2>
- <p>To switch between editors, views and perspectives, the workbench provides a cycling
- function that is invoked by Ctrl and a function key. All of these cycling
- functions recall the last thing selected to allow for rapid cycling back and
- forth between two items. The cycling functions are </p>
- <ul>
-  <li>Ctrl+F6 - Cycle to Editor</li>
-  <li>Ctrl+F7 - Cycle to View</li>
-  <li>Ctrl+F8 - Cycle to Perspective</li>
- </ul>
- <p>Also, Ctrl+E can be used to activate the editor drop-down, and Ctrl+PageUp
- and Ctrl+PageDown can be used for switching between the open editors.</p>
- <h2>Accelerators </h2>
- 
-<p>Many of the actions in Eclipse have an accelerator assigned to them. For additional 
-  information on accelerators, see <a href="keyboardshortcuts.htm">Keys</a>. </p>
- <h2>Quick Access </h2>
- 
-<p>To quickly access UI elements such as views,
-commands, preference pages, and others, you can use the Quick Access dialog,
-available under <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.quickAccess")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Navigation &gt; Quick Access</b></a> and bound to <b>Ctrl+3</b> by
-default. Start typing in the filter field to see matches. For example,
-to open the help view, type Ctrl+3 followed by &quot;help&quot;. One
-of the first matches will be to open the help view; other matches show
-commands and preference pages related to help. You can use the
-arrow keys to select a different match for a given filter string. Press
-Enter to select the highlighted entry. This will execute the command, or
-open the view, perspective, or wizard etc.</p>
- <h2>Help system</h2>
- <p>You can navigate the help system by keyboard using the following key 
- combinations:</p>
- <ul>
-   <li>Pressing Tab inside a frame (page) takes you to the next link, button or 
-   topic node. </li>
-   <li>To expand/collapse a tree node, press Right/Left arrows. </li>
-   <li>To move to the next topic node, press Down arrow or Tab </li>
-   <li>To move to the previous topic node, press Up arrow or Shift+Tab </li>
-   <li>To display selected topic, press Enter. </li>
-   <li>To scroll all the way up or down press Home or End. </li>
-   <li>To go back press Alt+Left arrow; to go forward press Alt+Right arrow.
-   </li>
-   <li>To go to the next frame, or toolbar press Ctrl+Tab
-     (Ctrl+F6, if using Mozilla, or Mozilla based browser).</li>
-   <li>To move to previous frame, press Shift+Ctrl+Tab.
-     (Shift-Ctrl+F6, if using Mozilla, or Mozilla based browser).</li>
-
-   <li>To move to the frame displaying topic content press Alt+K (when using
-     embedded help browser on Windows, or Internet Explorer).</li>
-   <li>To move to Contents tab, press Alt+C</li>
-   <li>To move to Search Results tab, press Alt+R</li>
-   <li>To move between tabs, press Right/Left arrows.</li>
-   <li>To switch view, select a tab and press Enter.</li>
-   <li>To switch and move to a view, select a tab and press Up arrow.</li>
-   <li>To move to the search entry field, press Alt+S</li>
-   <li>To print the current page or active frame, press Ctrl+P. </li>
-   <li>To find a string in the current page or active frame, press Ctrl+F
-     (when using embedded help browser on Windows, or Internet Explorer). </li>
- </ul>
-<p>Most labels of controls
-on help system pop-up dialogs have mnemonics are assigned to them. To access
-  the control associated with a label, use the Alt key along with the letter
-  that
- is underlined.</p>
-
-<p><img src="../../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-  <a href="accessmain.htm">Accessibility features in Eclipse</a><br>
- <a href="../../tasks/tkeybindings.htm">Changing the key bindings</a><br>
- <a href="keyboardshortcuts.htm">Keys</a> <br>
-<a href="../help.htm">Help</a></p>
- <p><img src="../../images/ngrelr.png" alt="Related references" border="0" ><br>
-  <a href="fontsandcolors.htm">Font and color settings in Eclipse</a></p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/text_editor.htm b/bundles/org.eclipse.platform.doc.user/concepts/accessibility/text_editor.htm
deleted file mode 100644
index 27313b7..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/accessibility/text_editor.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> 
-  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-  <title>Configuring accessibility options for textual editors</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-
-<h1>Configuring accessibility options for textual editors</h1>
-Besides the options to change colors and fonts as shown by the related tasks listed below, textual editors in Eclipse can be configured to better fit the needs of people with a physical disability. This document describes the relevant options.
-
-<h2>Accessing Annotations</h2>
-<p>You can navigate to the next annotation by pressing <b>Ctrl+.</b> and to the previous ony by pressing <b>Ctrl+,</b>. Out of the box not all available annotation types are included in that navigation,
-e.g. breakpoints are not part of it. Breakpoints and other annotation types can either be enabled via the <b>Next Annotation</b> toolbar button drop-down menu or by checking <b>Include in next/previous navigation</b> on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Annotations)")'>
-   <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-   <strong>General &gt; Editors &gt; Text Editors &gt; Annotations</strong></a> preference page.</p>
-<p>Navigating to an annotation lets its text appear in the status line. The next section explains how to read the status line under Windows.</p>
-<p>Some annotation types like e.g. warnings and errors, can
-be accessed by pressing <b>F2</b> after having navigated to one of them or setting the caret inside the annotation.</p> 
-
-<h2><img src="../../images/win_only.png" alt="Windows only" border="0" >Reading the status line with JAWS</h2>
-JAWS desktop users press <b>Insert+PageDown</b> to read the Eclipse status line and JAWS laptop users press <b>Caps Lock+PageDown</b>.
-
-
-<h2>Quick Diff Hover</h2>
-Like normal hovers can be shown by pressing <b>F2</b>, the quick diff diff and revision hovers that appear when hovering over the quick diff ruler on the left can also be shown by pressing a key sequence.
-However, out of the box no key sequence is defined for that. Go to the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-   <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-   <strong>General &gt; Keys</strong></a> preference page to assign a key sequence to the <b>Show Quick Diff Ruler Tooltip</b> command.
-
-
-
-<p><img src="../../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-<a href="accessmain.htm">Accessibility features in Eclipse</a><br>
-<a href="navigation.htm">Navigating the user interface by using the keyboard</a>
-</p>
-
- <p><img src="../../images/ngrelr.png" alt="Related references" border="0" ><br>
-	<a href="../../reference/ref-7.htm">Accessibility preference page</a><br>
-	<a href="keyboardshortcuts.htm">Keys</a><br>
-	<a href="fontsandcolors.htm">Font and color settings in Eclipse</a></p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm b/bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm
deleted file mode 100644
index 225e917..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cbookmrk.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
- Bookmarks </H1>
-<P CLASS="Para">You can place an &quot;anchor&quot; either on a resource within
-the Workbench, or at a specific line within a file, by creating a bookmark. Then
-you can use the Bookmarks view to return to those files quickly.</P>
-<P CLASS="Para">The Bookmarks&nbsp; view (<b>Window &gt; Show View &gt;
-Bookmarks</b>) displays all bookmarks&nbsp;that you have created.&nbsp;</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="ctskview.htm">Tasks view</a></p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-81b.htm">Creating a bookmark for an entire file</a><a href="../tasks/tasks-81.htm"><br>
-Creating a bookmark within a file</a><a href="../tasks/tasks-82.htm"><br>
-Deleting a bookmark<br>
-</a><a href="../tasks/tasks-77.htm">Adding line items in the Tasks view</a><a href="../tasks/tasks-77b.htm"><br>
-Associating a task with an editable resource</a></p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-11.htm">Markers</a><br>
-<a href="ctskview.htm">Tasks view</a><br>
-<a href="cprbview.htm">Problems view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-28.htm">Bookmarks view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm b/bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm
deleted file mode 100644
index b0db31a..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cdecorations.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Label decorations</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
- Label decorations </H1>
-<P CLASS="Para">Label decorations are used to show extra information about an
-item by modifying its label or icon. They can be used to obtain information
-about the state of an item without having to look at its properties in the
-Properties view or open its Properties dialog.</P>
-<P CLASS="Para">A number of label decorators may be available. To control which 
-  decorators are visible, go to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Appearance &gt; Label Decorations</b></a> preference page.
-  This preference page provides a selectable 
-  list and description of the available decorations.</P>
-<P CLASS="Para">The following is the Project Explorer view showing resources with CVS
-decorations:</P>
-<P CLASS="Para"><img src="../images/Image273_nav-decorators.png" alt="Project Explorer view with CVS decorators on" border="0" ></P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cnav.htm b/bundles/org.eclipse.platform.doc.user/concepts/cnav.htm
deleted file mode 100644
index da99c52..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cnav.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Project Explorer view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>
-Project Explorer view</H1>
-<P CLASS="Intro">
-
-The Project Explorer view provides a hierarchical view of the resources in the Workbench.
-From here, you can open files for editing or select resources for operations such
-as exporting.</p>
-<P CLASS="Para">
-<img src="../images/Image241_nav_view.png" alt="Picture of Project Explorer view showing a simple hierarchy (project, folders, files)" border="0"></P>
-<P CLASS="Para">
-Right-click on any resource in the Project Explorer view to open a pop-up menu that
-allows you to perform operations such as copying, moving, creating new
-resources, comparing resources with each other, or performing team
-operations. To see a description of what each menu item does, move selection
-highlight to that menu item and press the context-sensitive help key (e.g., F1
-on Microsoft Windows).</P>
-<P CLASS="Para">
-By default, the Project Explorer view is included in the Resources perspective. To add it
-to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ResourceNavigator)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Project Explorer</b></a>.</P>
-<h2>
-Toolbar</h2>
-<P>
-The toolbar of the Project Explorer view contains the following buttons:</P>
-<dl>
-  <dt>Collapse All</dt>
-  <dd>Collapses the tree expansion state of all resources in the view.</dd>
-  <dt>Link with Editor</dt>
-  <dd>Toggles whether the Project Explorer view selection is linked to the active editor.
-  When this option is selected, changing the active editor will automatically update the 
-  Project Explorer selection to the resource being edited.</dd>
-  <dt>Menu</dt>
-  <dd>Provides menu items that allow you to sort or filter the contents of the
-  Project Explorer view as well as select a working set.</dd>
-</dl>
-<h2>
-Icons</h2>
-<p CLASS="Para">The following icons can appear in the Project Explorer view.</p>
-<table BORDER="1" cellspacing="0">
-    <thead>
-    <tr>
-      <th ROWSPAN="1" COLSPAN="1">
-        <p CLASS="Para">Icon</p>
-      </th>
-      <th ROWSPAN="1" COLSPAN="1">
-        <p CLASS="Para">Description</p>
-      </th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left"><img src="../images/ref-10.png"  alt="Open project icon" border="0"></td>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-        Project (open)      </td>
-    </tr>
-    <tr>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left"><img src="../images/ref-12.png"  alt="Folder icon" border="0"></td>
-      <td ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-       Folder
-      </td>
-    </tr>
-    <tr>
-      <td COLSPAN="1" valign="top" align="left"><img src="../images/ref-15.png"  alt="File icon" border="0"></td>
-      <td COLSPAN="1" valign="top" align="left"> File</td>
-    </tr>
-  </tbody>
-</table>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-12.htm">Resources</a><br>
-<a href="concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-48b.htm">Showing or hiding files in the Project Explorer view</a><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a>
-</p>
-<P><IMG border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-27.htm">Project Explorer view</a>
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm
deleted file mode 100644
index ffa88cf..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-11.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Markers</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Markers</H1>
-<p CLASS="Head">Markers are objects that may be associated with Workbench resources.&nbsp; 
-  There are many uses of markers in the Workbench.&nbsp; The three main uses of 
-  markers in the Workbench are:</p>
-<ul>
-  <li>Tasks</li>
-  <li>Problems</li>
-  <li>Bookmarks</li>
-</ul>
-<p CLASS="Head">Markers are shown in a marker view (Tasks, Problems or Bookmark 
-  view) or on the marker bar in the editor area.</p>
-<p CLASS="Head">The following sections give more detail on each of these marker 
-  types. </p>
-<DIV CLASS="Subtopic">
-<h2>
-Tasks</h2>
-  <P CLASS="Para"> A task marker represents a work item. There are two kinds of 
-    tasks: </P>
-<UL CLASS="UnorderedList">
-    <LI CLASS="Item"> Automatically-generated information associated with the 
-      resource</LI>
-    <LI CLASS="Item"> User specified tasks that may or may not be associated with 
-      a resource</LI>
-</UL>
-  <p>Both of these task types appear in the Tasks view.</p>
-<h2>
-Problems</h2>
-  <P CLASS="Para" Label=Type> Problem markers represent invalid states and are 
-    categorized as follows..</P>
-</DIV>
-<ul>
-  <li> 
-    <DIV CLASS="Subtopic"> <strong>Errors</strong>: Error markers are often used 
-      to indicate the source location of syntax or compilation errors.</DIV>
-  </li>
-  <li> 
-    <DIV CLASS="Subtopic"> <strong>Warnings</strong>: Warning markers indicate 
-      the source location of, for example, compilation warnings.</DIV>
-  </li>
-  <li> 
-    <DIV CLASS="Subtopic"> <strong>Information</strong>: Information markers indicate 
-      the source location of information only tasks.</DIV>
-  </li>
-</ul>
-<p>Problems are shown in the Problems view. </p>
-<h2>
-Bookmarks</h2>
-<P CLASS="Para" Label=Type> Bookmarks place an anchor either at a specific line 
-  in a resource or on the resource itself. They are shown in the Bookmarks view.</P>
-
-<P CLASS="Para" Label=Type>
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="cbookmrk.htm">Bookmarks</a><br>
-<a href="ctskview.htm">Tasks view</a><br>
-  <a href="cprbview.htm">Problems view</a></P>
-
-<P CLASS="Para" Label=Type>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-81.htm">Creating a bookmark within a file</a><br>
-<a href="../tasks/tasks-81b.htm">Creating a bookmark for an entire file</a></P>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm
deleted file mode 100644
index 86058d7..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-12.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resources</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Resources</H1>
-<p CLASS="Head"> <i>Resources</i> is a collective term for the projects, folders, 
-  and files that exist in the Workbench. The navigation views provide a hierarchical 
-  view of resources and allows you to open them for editing. Other tools may display 
-  and handle these resources differently.&nbsp;</p>
-<p CLASS="Head">There are three basic types of resources that exist in the
-Workbench:</p>
-<dl>
-  <dt>Files</dt>
-  <dd>Comparable to files as you see them in the file system.&nbsp;</dd>
-  <dt>Folders</dt>
-  <dd>Comparable to directories on a file system.&nbsp; In the Workbench,
-    folders are contained in projects or other folders. Folders can contain
-    files and other folders.</dd>
-  <dt>Projects</dt>
-  <dd>Contain folders and files. Projects are used for builds, version
-    management, sharing, and resource organization. Like folders, projects map
-    to directories in the file system. (When you create a project, you specify a
-    location for it in the file system.)</dd>
-
-  <dd>A project is either open or closed. When a project is closed, it cannot be
-    changed in the Workbench.&nbsp; The resources of a closed project will not
-    appear in the Workbench, but the resources still reside on the local file
-    system.&nbsp; Closed projects require less memory.&nbsp; Since they are not
-    examined during builds, closing a project can improve build time.</dd><dd>When a project is open, the structure of the project can be changed and
-    you will see the contents.&nbsp;</dd>
-</dl>
-<p>
-Folders and files can be linked to locations in the file system
-outside of the project's location.  These special folders and files are called 
-<a href="concepts-13.htm">linked resources</a>.
-</p>
-<p>Different tools that plug into the Workbench use their own specialized types
-of projects, folders, and files.&nbsp;</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="cnav.htm">Project Explorer view</a><br>
-<a href="concepts-17.htm">Resource hierarchies</a><br>
-<a href="concepts-13.htm">Linked resources</a><br>
-<a href="concepts-22.htm">Builds</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-53.xhtml">Importing resources into the Workbench</a><br>
-<a href="../tasks/tasks-42.htm">Creating a project</a><br>
-<a href="../tasks/tasks-43.htm">Creating a folder</a><br>
-<a href="../tasks/tasks-44.htm">Creating a file</a><br>
-<a href="../tasks/tasks-45.htm">Creating linked resources</a><br>
-<a href="../tasks/tasks-47.htm">Closing projects</a><br>
-<a href="../tasks/tasks-49.htm">Viewing resource properties</a><br>
-<a href="../tasks/tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="../tasks/tasks-63cg.htm">Copying resources</a><br>
-<a href="../tasks/tasks-63.htm">Moving resources</a><br>
-<a href="../tasks/tasks-68.htm">Comparing resources</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm
deleted file mode 100644
index 89dc570..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-13.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Linked resources</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Linked resources</H1>
-<p>
-Linked resources are files and folders that are stored in locations 
-in the file system outside of the project's location.  These special resources can be
-used to add files and folders to your project that for some reason must be stored in a 
-certain place outside of your project.  For example, a linked folder can be used
-to store build output separately from your source files.
-</p>
-<p>
-You can even use linked resources to overlap other resources in the workspace, so
-resources from one project can appear in another project.
-If you do want to have overlapping resources in your workspace, do so with caution.
-Keep in mind that this means changing a resource in one place will cause simultaneous 
-changes in the duplicate resource.  Deleting one duplicate resource will delete both!
-</p>
-<p>
-Deleting a linked resource will <em>not</em> cause the corresponding resource
-in the file system to be deleted.  However, deleting child resources of linked folders
-<em>will</em> cause them to be removed from the file system.
-</p>
-<p>
-Some plug-ins built on top of the Eclipse platform are not compatible with linked resources.
-If this is the case, you can completely disable the linked resource feature to prevent them
-from being created in your workspace.  Linked resources can be disabled from the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Workspace &gt; Linked Resources</b></a> preference page.
-Certain types of projects or team repository providers may also disallow linked resources
-from being created in some projects.</p>
-<p>
-
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="cnav.htm">Project Explorer view</a><br>
-<a href="concepts-12.htm">Resources</a><br>
-<a href="concepts-17.htm">Resource hierarchies</a><br>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-45.htm">Creating linked resources</a><br>
-<a href="../tasks/tasks-67.htm">Deleting resources</a><br>
-<a href="../tasks/tasks-49.htm">Viewing resource properties</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br>
-  <a href="../reference/ref-14b.htm">Linked resources</a> 
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm
deleted file mode 100644
index fb26d07..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resource hierarchies</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Resource hierarchies</H1>
-<p CLASS="Head">Resources are stored and displayed in the Workbench in
-hierarchies.&nbsp; Described below are the terms used when referring to
-resources that are stored and displayed in a hierarchical structure.</p>
-<dl>
-  <dt>Root</dt>
-  <dd>The top level of the Workbench contents (in the file system).</dd>
-  <dt>Parent resource</dt>
-  <dd>Any resource that contains another resource. Only projects and folders can be parent resources.</dd>
-  <dt>Child resource</dt>
-  <dd>Any resource that is contained within another resource. Only files and folders can be child resources.</dd>
-</dl>
-<P>Resource hierarchies are displayed in the Project Explorer view, which is one of the
-default views in the Resource perspective.
-</P>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-12.htm">Resources</a>
-<a href="cnav.htm"><br>Project Explorer view</a></p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46ag.htm">
-Finding a resource quickly</a><br>
-<a href="../tasks/tasks-48b.htm"><br>
-Showing or hiding files in the Project Explorer view</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm
deleted file mode 100644
index e935473..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-17a.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Local history</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Local history</H1>
-<p>A local edit history of a file is maintained when you create or modify a
-file. Each time you edit and save the file,&nbsp; a copy is saved so that you can replace the current
-file with a previous edit or even restore a deleted file.&nbsp; You can also
-compare the contents of all the local edits.&nbsp; Each edit in the local
-history is uniquely represented by the date and time the file was
-saved.&nbsp;&nbsp;</p>
-<p>Only files have local history; projects and folders do not.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-27.htm">Versions</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-70.htm">Comparing resources with local history</a><br>
-<a href="../tasks/tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="../tasks/tasks-87b.htm">Restoring deleted resources from local history</a><br>
-<a href="../tasks/tasks-88.htm">Setting local history preferences<br></a><br>
-<a href="../tasks/tasks-100.htm">Creating a version of a project</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm
deleted file mode 100644
index 0cd795d..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-18.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Toolbars in the Workbench</title>
-<meta name="keyword" content="shortcut bar">
-<meta name="keyword" content="fast view">
-</HEAD>
-
-<BODY>
-
-<H1 CLASS="Head">Toolbars </H1>
-
-<p CLASS="Para" Label="Type">There are five kinds of toolbars in the Workbench.</p>
-
-
-<p CLASS="Para" Label="Type">The <i> main toolbar</i>, sometimes called the Workbench toolbar,
-is displayed at the top of
-the Workbench window directly beneath the menu bar. The contents of this toolbar change based on the active perspective. Items in the toolbar
-might be enabled or disabled based on
-the state of either the active view or editor. Sections of the main toolbar can be rearranged using the mouse.
-</p>
-
-
-<p CLASS="Para" Label="Type">There are also individual <i>view toolbars</i>,
-which appear in the title
-bar of a view. Actions in a view's toolbar apply only to the view in which
-they appear. Some view toolbars include a <b>Menu</b> button, shown as an
-inverted triangle, that contain actions for that view.</p>
-<p CLASS="Head">A third type of toolbar is the perspective switcher.  The
-perspective switcher allows quick access to perspectives that are currently
-open.  It also has a button that can open new perspectives.  The perspective
-switcher is normally located in the top-right, next to the main toolbar.
-However, it is also possible to position it below the main toolbar
-("top-left"), or to position it vertically on the left-hand side of the
-workbench ("left").  The name of the perspectives is shown by default, but
-it is possible to hide the text and show only the icons.  To reposition the
-perspective or hide the text, right-click on it and choose the appropriate
-item from the context menu.</p>
-<p CLASS="Head">Minimizing a view stack will also produce a toolbar
-in the trim at the outer edge of the workbench window (a <i>Trim Stack</i>). This bar will contain
-an icon for each of the views in the stack. Clicking on one of these icons will
-result in the view being displayed as an overlay onto the existing presentation.</p>
-<p CLASS="Head">Finally, the fast view bar is a toolbar that contains icons representing 
-  the current set of fast views. A fast view is a shortcut to a view that is frequently 
-  used; see the section on fast views for more information. The fast view bar 
-  appears in the bottom left corner of the workbench by default. However, it is 
-  possible to position it on the left or right as well.</p>
-<p CLASS="Head">In all cases, you can find out what toolbar buttons do by moving
-your mouse pointer over the button and reading the tooltip that opens. See the
-list of related reference topics below for a table of all toolbar buttons.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="concepts-5.htm">Views</a><br>
-<a href="concepts-4.htm">Perspectives</a><br>
-<a href="concepts-21.htm">Fast views</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a><br>
-<a href="../tasks/ttoolbars.htm">Rearranging the main toolbar</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-68.htm">Toolbar buttons</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm
deleted file mode 100644
index 1dbf3a4..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-2.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>The Workbench</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Workbench</H1>
-<P>The term <i>Workbench</i> refers to the desktop development environment. 
-The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation of workspace resources.</P>
-
-
-<P>
-Each Workbench window contains one or more
-perspectives.&nbsp; Perspectives contain views and editors and control
-what appears in certain menus and tool bars.&nbsp; More than one Workbench window can exist
-on the desktop at any given time.</P>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><a href="concepts-25.htm"><br>
-Features<br>
-</a><a href="concepts-12.htm">Resources</a><a href="concepts-4.htm"><br>
-Perspectives</a><a href="concepts-5.htm"><br>
-Views<br>
-</a><a href="concepts-6.htm">Editors<br>
-</a><a href="concepts-27c.htm">CVS Repositories</a></P>
-
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-9f.htm">Opening perspectives</a><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-28.htm">Switching between perspectives</a><br>
-<a href="../tasks/tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a></P>
-<a href="../tasks/tasks-9m.htm">Configuring perspective command groups</a><br>
-<a href="../tasks/tasks-9k.htm">Configuring perspective shortcuts</a><br>
-<a href="../tasks/tasks-124.htm">Installing new software</a><br>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" ><a href="../reference/ref-68.htm"><br>
-Toolbar buttons</a></P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm
deleted file mode 100644
index fa182b4..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-21.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Fast views</title>
-<meta name="keyword" content="shortcut bar">
-
-</HEAD>
-<body>
-<H1 CLASS="Head">
-Fast views</H1>
-<p>
-<strong>NOTE:</Strong> The Fast View feature, while still available, has effectively been subsumed by the new
-minimize behavior (which places minimized stacks into the trim where they subsequently work by showing views in
-the same manner as the Fast Views). While there's only one Fast View Bar you can have as many minimized stacks
-as you want and can place them where you want in the trim. See '<a href="../gettingStarted/qs-39g.htm">Maximizing a view or editor</a>'
-for details.
-</p>
-<P CLASS="Para" Label=Type>
-   Fast views are hidden views that can be quickly opened and closed. They work
-   like other views except they do not take up space in your Workbench window.&nbsp;</P>
-<P CLASS="Para" Label=Type> Fast views are represented by toolbar buttons on the 
-  <i>fast view bar</i>, which is the toolbar initially on the bottom 
-  left of the Workbench window. When you click the toolbar button for a fast view, 
-  that view opens temporarily in the current perspective (overlaying it). As soon as you click 
-  outside that view or the view loses focus it is hidden again. The fast view bar can also be docked 
-  on the other sides of the Workbench window.</P> 
-<P CLASS="Para" Label=Type>  
- By default the fast view bar is always visible. You can use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Perspectives</b></a>
-  preference page to hide the fast view bar if it is empty.</P>
-<P CLASS="Para" Label=Type>
-You can create a new fast view by dragging any open view to the
-fast view bar or by selecting <b>Fast View</b> from the menu that opens when you
-right-click the icon of the view's tab. You can also click on the left-most button of the fast View bar
-to open a menu which will show a list of views. Selecting a view from this list (or from the dialog that appears
-if you select '<b>Other...</b>' will result in the selected view being added to the fast view bar and activating
-(i.e. shown as the active part).</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="concepts-2.htm">Workbench</a><a href="concepts-18.htm"><br>
-Toolbars</a></P>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a><a href="../tasks/tasks-3e.htm"><br>
-Moving and docking views</a><br>
-<a href="../gettingStarted/qs-39g.htm">Maximizing a view or editor</a></P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference." ><br>
-<a href="../reference/ref-3a.htm">Fast View bar</a></P>
-
-
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-21a.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-21a.htm
deleted file mode 100644
index 0c465b4..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-21a.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Detached views</title>
-
-</HEAD>
-<body>
-<H1 CLASS="Head">
-Detached views</H1>
-<P CLASS="Para" Label=Type>
-   <img src="../images/win_only.png" alt="Windows only" border="0" > Detached views are
-   views that are shown in a separate window with a smaller trim. They work like other views
-   except they are always shown in front of the Workbench window.&nbsp;</P>
-<P CLASS="Para">
-<img src="../images/detachview2.png" alt="Picture of Workbench window with a detached view containing the Task view on top of it " border="0"></P>
-<P CLASS="Para" Label=Type>
-You can create a new detached view by dragging any open view outside of the Workbench window
-or by selecting <b>Detached</b> from the menu that opens when you
-right-click the view's tab.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="concepts-2.htm">Workbench</a></P>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-9l.htm">Detaching views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../gettingStarted/qs-39g.htm">Maximizing a view or editor</a></P>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm
deleted file mode 100644
index f90ee3d..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-22.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Builds</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Builds</H1>
-<p CLASS="Head">
-A <i>build</i> is a process that derives new resources from existing ones, updates existing resources, or both.&nbsp;</p>
-<p CLASS="Head">
-In the Workbench,&nbsp;different <i>builders</i> are invoked for different types
-of projects. For example, when a build is triggered for a Java project, a Java
-builder converts each Java source file (.java files) into one or more executable class files
-(.class files). Builders usually enforce the constraints of some
-domain. For example, a Web link builder could update links to files
-whose name/location changes.</p>
-
-<p CLASS="Para" Label="Type">There are two kinds of builds:&nbsp;</p>
-<ul>
-  <li>
-    <p CLASS="Para" Label="Type">An <i>incremental build</i> leverages a
-    previously built state and applies the transforms of the configured builders
-    to the resources that have changed since the previous state was computed
-    (that is, since the last build).</p></li>
-  <li>
-    <p CLASS="Para" Label="Type">A clean build discards any problems and 
-    previously built state.  The next build after a clean will transform all resources according to
-    the domain rules of the configured builders.</p></li>
-</ul>
-<p>Incremental and clean builds can be done over a specific set of projects or
-the workspace as a whole.&nbsp;Specific files and folders cannot be built. There are two ways that builds can be performed:</p>
-<ul>
-  <li> Automatic builds are performed as resources are saved. Automatic builds 
-    are always incremental and always operate over the entire workspace. You can 
-    configure your preferences
-    (<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Window &gt; Preferences &gt; General &gt; Workspace</b></a>) to 
-    perform builds automatically on resource modification.&nbsp;</li>
-  <li>
-Manual builds are initiated when you explicitly select a menu item or press the
-equivalent shortcut key. Manual builds can be either clean or incremental and can operate over collections of projects 
-or the entire workspace.</li>
-</ul>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="concepts-exttools.htm">External tools</a>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-73.htm">Building resources</a>
-<br><a href="../tasks/tasks-75.htm">Performing builds manually</a>
-<br><a href="../tasks/tasks-16.htm">Performing builds automatically</a>
-<br><a href="../tasks/tasks-17.htm">Saving resources automatically before a manual build</a><a href="../tasks/tasks-14.htm"><br>
-Changing build order</a></p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm
deleted file mode 100644
index 3fc3448..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-25.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Features</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head" dir="ltr">
-Features</H1>
-
-<p>On disk, an Eclipse based product is structured as a collection of <em>plug-ins</em>.
-Each plug-in contains the code that provides some of the product's
-functionality. The code and other files for a plug-in are installed on the local
-computer, and get activated automatically as required. A product's plug-ins are
-grouped together into features. A <em>feature</em> is a unit of separately downloadable and installable
-functionality.</p>
-<p>The fundamentally modular nature of the Eclipse platform makes it easy 
-to install additional features and plug-ins into an Eclipse based
-product, and to update the product's existing features and plug-ins. You 
-can do this using the Eclipse platform's install and update support found
-in the <b>Help</b> menu. Eclipse allows you to discover, download, and install features and
-plug-ins from special web-based Eclipse software sites.
-</p>
-
-<p>Large Eclipse based products can organize their features into trees starting
-from the root feature that represents the entire product. This root feature then
-includes smaller units of functionality all the way down to leaf features that
-list one or more plug-ins and fragments. The capability to group features
-hierarchically allows products to be stacked using a 'Russian doll' approach - a
-large product can build on top of a smaller one by including it and adding more
-features.</p>
-
-<p>Some included features may be useful add-ons, but are not vital to the proper
-functioning of the overall product. Feature providers can elect to mark them as <b>optional</b>.
-Optional features will only be installed if all their required features and plug-ins are
-available. If not installed right away, optional features can be added at a later date.</p>
-
-<p>The <b>About</b> option on the <b>Help</b> menu provides information 
-about installed features and plug-ins. The <b>Check for Updates</b>
-and <b>Install New Software</b> commands on the <b>Help</b> menu provide the ability to update
-existing features, and to find, download, and install new features.
-</p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-2.htm">Workbench</a></P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-132.htm">Installation Details for Features </a>
-<br><a href="../tasks/tasks-131.htm">Installation Details for Plug-ins</a>
-<br><a href="../tasks/tasks-120.htm">Updating the installation</a>
-<br><a href="../tasks/tasks-124.htm">Installing new software</a>
-<br><a href="../tasks/tasks-126.htm">Uninstalling software</a>
-<br><a href="../tasks/tasks-123.htm">Reverting to a previous install configuration</a>
-</P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm
deleted file mode 100644
index ebc66ee..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-26.htm
+++ /dev/null

@@ -1,196 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-             
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-             
-  <meta http-equiv="Content-Style-Type" content="text/css">
-              
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Team programming with CVS</title>
-                       
-  <meta name="keyword" content="team">
-</head>
-  <body style="background-color: rgb(255,255,255);">
-       
-<h1 class="Head">Team programming with CVS</h1>
-       
-<p class="Para">In the Concurrent Versions System (CVS) team programming environment,
-   team members do all of their work in their own Workbenches, isolated from
-others.    Eventually they will want to share their work. They do this via
-a CVS Repository.</p>
-       
-<h2 class="Para">Branches</h2>
-       
-<p class="Para">CVS uses a branch model to support multiple courses of work 
- that    are somewhat isolated from each other but still highly interdependent. 
- Branches    are where a development team shares and integrates ongoing work. 
- A branch can    be thought of as a shared workspace that is updated by team 
- members as they    make changes to the project. This model allows individuals 
- to work on a CVS    team project, share their work with others as changes 
- are made, and access the    work of others as the project evolves. A special 
- branch, referred to as HEAD,    represents the main course of work in the 
-repository (HEAD is often referred    to as the trunk).</p>
-       
-<h2 class="Para">Sharing work</h2>
-       
-<div class="Topic">      
-<p class="Para">As team members produce new work, they share this work by 
- <i>committing</i>      those changes to the branch. Similarly, when they 
-wish to get the latest available      work, they <i>update</i> their local 
-workspaces to the changes on the branch.&nbsp;      Thus the branch is constantly 
-changing, moving forward as team members submit      new work.</p>
-         
-<p class="Para">The branch effectively represents the current state of the 
- project.      At any point a team member can update their workspaces from the branch and know
- they are up      to date.</p>
-         
-<div class="Figure">        
-<div> <img src="../images/ref-9.png"
- alt="Interaction with Branches and Workbenches" >
-        </div>
-      </div>
-         
-<div class="XRefList">   </div>
-    </div>
-       
-<div class="Topic">      
-<h2>Optimistic team model</h2>
-         
-<p class="Para">CVS provides two important features required for working in
-     a team:</p>
-         
-<ul>
-        <li>                      
-    <p class="Para">A history of the work submitted by the team     </p>
-     </li>
-     <li>                      
-    <p class="Para">A way to coordinate and integrate this work   </p>
-     </li>
-     
-</ul>
-         
-<p class="Para">Maintaining history is important so that one can compare the
-     current work against previous drafts, revert to older work that is better, and
-so on.      Coordinating the work is critical so that there exists one definition
-of the      current project state, containing the integrated work of the
-team. This coordination      is provided via the branch model.</p>
-         
-<p class="Para">An optimistic model is one where any member of the team can 
-      make changes to any resource he or she has access to.&nbsp; Because 
-two team      members can commit to the branch changes to the same resource, 
- conflicts      can occur and must be dealt with. This model is termed <i>
-   optimistic</i> because      it is assumed that conflicts are rare.</p>
-         
-<h2>Recommended work flow</h2>
-         
-<p class="Para">Usually resources do not exist in isolation, they typically
-    contain implicit or explicit dependencies on other resources.&nbsp; For
-    example, Web pages have links to other Web pages, and source code has
-  references to artifacts described in other source code resources.&nbsp; 
- No resource is an island.</p>
-         
-<p class="Para">As resources are committed to the branch, these dependencies 
-      can be affected. Ensuring the integrity of the dependencies is important 
- because      the branch represents the current project state: at any point 
- a team member      could take the branch contents as a basis for new work.</p>
-         
-<p class="Para">The ideal work flow therefore is one in which the branch integrity
-     is preserved. </p>
-
-<h3 class="Para"><a name="IdealWorkFlow">Ideal flow enumerated</a></h3>
-
-<p class="Para">The ideal work flow proceeds as follows:</p>
-         
-<ol>
-        <li>                      
-    <p class="Para">Start fresh. Before starting work, update the resources
-    in the workspace with 
- the          current branch state. If you are sure that you have no local 
- work that          you care about, the fastest way to get caught up is to 
- select the projects          you are interested in from the branch (or HEAD) 
- and select <b>Checkout</b> (or <b>Replace with &gt; Latest from Repository</b>
- if the projects already exist locally). This will overwrite your 
-local resources with those from          the branch.          </p>
-     </li>
-     <li>                      
-    <p class="Para">Make changes. Work locally in your Workbench, creating 
- new       resources, modifying existing ones, saving locally as you go. 
-   </p>
-     </li>
-     <li>                      
-    <p class="Para">Synchronize. When you are ready to commit your work, synchronize
-         with the repository.</p>
-                 
-    <ol type="a">
-            <li>                                      
-        <p class="Para">Update. Examine incoming changes and add them to your
-             local Workbench. This allows you to determine if there are changes
-             which might affect the integrity of what you are about to commit.
-             Resolve conflicts. Test again, run integrity checkers (for example,
-			 check for broken hypertext links, ensure your code compiles,
-			 and so on).</p>
-         </li>
-         <li>                                      
-        <p class="Para">Commit. Now that you are confident that your changes 
-              are well integrated with the latest branch contents, commit your 
-              changes to the branch. To be prudent, you may repeat the previous              
-              step if there are new incoming changes.           
-    </p>
-         </li>
-                 
-    </ol>
-        </li>
-         
-</ol>
-         
-<p class="Para">Of course this is an <i>ideal</i> work flow. Under certain 
- conditions      you may be confident that the incoming changes do not affect 
- you and choose      to commit without updating. However, in general team 
-members should make an      effort to follow a flow similar to the above in
-order to ensure that the branch      integrity is not accidentally compromised.&nbsp;
-    </p>
-     
-<p class="Para">You can find more information on CVS at <a
- href="http://ximbiot.com/cvs/" class="URL" target="_blank">http://ximbiot.com/cvs/</a>.
-    </p>
-   </div>
-        
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="concepts-27c.htm">CVS Repositories</a>
-<br><a href="concepts-27b.htm">Branches</a>
-<br><a href="concepts-27.htm">Versions</a>
-<br><a href="concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-         
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-   <a href="../tasks/tasks-92.htm"><br>
-    Creating a CVS repository location</a><a
- href="../tasks/tasks-96.htm"><br>
-    Checking out a project from a CVS repository</a>&nbsp;<a
- href="../tasks/tasks-103.htm"><br>
-    Replacing resources in the Workbench</a><a
- href="../tasks/tasks-117.htm"><br>
-    Sharing a new project using CVS</a><a href="../tasks/tasks-115.htm"><br>
-    Synchronizing with the repository</a><a
- href="../tasks/tasks-113.htm"><br>
-    Updating</a><a href="../tasks/tasks-113b.htm"><br>
-    Resolving conflicts </a><a href="../tasks/tasks-100b.htm"><br>
-    Merging from a branch</a><a href="../tasks/tasks-114.htm"><br>
-    Committing</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br><a href="../reference/ref-47.htm">CVS</a>
-</p>
-           
-
-        
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm
deleted file mode 100644
index f359194..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Versions</title>
-         
-  <meta name="keyword" content="team">
-</head>
-  <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> Versions</h1>
-   
-<p class="Para"> Resources are versioned in order to capture a snapshot 
-of the current state of the resources at one specific point in time. Resources
-in CVS are versioned by tagging them with a version label. When a resource
-is versioned, it means that a non-modifiable copy of it can be retrieved
-from the repository. </p>
-   
-<p class="Intro">Versioning a project saves the line up of all resource versions 
-in the project. Resources other than projects (files and folders) 
-can be versioned. However, it is more common to version entire projects 
-together as the resources contained in a project are often highly interdependent. 
-Projects can be versioned from the workspace or from the branch (including HEAD) in the 
-CVS Repositories view. The difference between these two approaches is in
-deciding which child resource versions should be part of the project version.
- </p>
- 
-<p class="Para"> When tagging a project as a version from the <i>Workbench</i>,    
-the base revisions of the files in the Workbench are tagged as belonging 
-to that version.&nbsp; This is the preferred method of versioning a project 
-because you know exactly which file revisions will be in the version.&nbsp;This 
-operation is allowed if you have outgoing changes or uncommitted changes. 
-Uncommitted changes are simply ignored and resources with outgoing changes 
-can still have their base revisions be part of the version.&nbsp; Versioning 
-a project with uncommitted or outgoing changes is handy if you have to 
-split the project at the point where you started making changes to the 
-resources and commit the resources to another branch.</p>
-   
-<p class="Para"> When tagging a project as a version from a <i>branch</i>
-in the CVS Repositories view, you are versioning whatever the latest 
-resource versions are in the branch at that moment in time. You should
-not version your projects from the branch if you do not know what is committed
-in the branch. For this reason, versioning from the Workbench is often
-preferable.</p>
-     
-<p class="Para"> <img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="concepts-27c.htm">CVS Repositories</a><br>
-<a href="concepts-27b.htm">Branches</a><br>
-<a href="concepts-17a.htm">Local history</a><br>
-<a href="concepts-12.htm">Resources</a>
-</p>
-    
-<p class="Para"> <img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/tasks-100.htm">Creating a version of a project</a><br>
-<a href="../tasks/tasks-118.htm">Versioning projects in the repository</a><br>
-<a href="../tasks/tasks-107b.htm">Enabling the CVS resource decorations</a><br>
-<a href="../tasks/tasks-105c.htm">Moving version tags</a>
-</p>
-    
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-     
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm
deleted file mode 100644
index 9e0cbd2..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27b.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Branches</title>
-<meta name="keyword" content="team">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>Branches</H1>
-
-<p>In CVS, teams share and integrate their ongoing work in <i>branches</i>. Think 
-  of a branch as a shared work area that can be updated at any time by team members. 
-  In this way, individuals can work on a team project, share their work with others 
-  on the team, and access the work of others during all stages of the project. 
-  The branch effectively represents the current shared state of the project. 
-</p>
-<p>Resources can be changed in the Workbench without affecting the branch. 
-  Individuals must explicitly provide their changed resources to the branch.
-</p>
-<p>Every CVS repository has at least one branch, referred to as HEAD. Under 
-  certain conditions, more than one branch may exist in a repository. For 
-  example, one branch may be for ongoing work, and another branch may be for maintenance 
-  work.&nbsp; </p>
-<p>As you make changes locally in your Workbench, you are working alone. When you are ready to make your local resource changes 
-  available to other team members, you'll need to <i>commit</i> your work to 
-  the branch. All such changes are classified as outgoing changes when you do a synchronization. 
-</p>
-  
-<p>Ideally, you should update your local workspace with any changes others have 
-  made in a branch before committing to it. This ensures that you have the very 
-  latest work from the other team members. After you have updated from the branch, 
-  merged any conflicting changes in your local Workbench, and tested your changes 
-  locally, you can more easily commit your Workbench's changes to the branch.</p>
-
-  
-<p>When you commit changes to the branch, your changes are copied from your local 
-  Workbench to the branch. As a result, these changes are then seen as incoming 
-  changes when other developers update from the branch later.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="concepts-26.htm">Team programming with CVS</a><br>
-<a href="concepts-27c.htm">CVS Repositories</a><br>
-<a href="concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="../tasks/tasks-96.htm"> Checking out a project from a CVS repository</a><br>
-<a href="../tasks/tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="../tasks/tasks-100a.htm">Branching</a><br>
-<a href="../tasks/tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="../tasks/tasks-113.htm">Updating</a><br>
-<a href="../tasks/tasks-114.htm">Committing</a><br>
-<a href="../tasks/tasks-113b.htm">Resolving conflicts </a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm
deleted file mode 100644
index c69e025..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-27c.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
- 
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
- 
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Repositories</title>
-  
-  <meta name="keyword" content="team">
-</head>
-  <body bgcolor="#ffffff">
- 
-<h1 class="Head">CVS Repositories</h1>
- 
-<p class="Intro"> </p>
-<p class="Para"> A Concurrent Versions System (CVS) repository is a persistent
-   data store that coordinates multi-user access to projects and their contents.
-   Projects in a repository can be of two forms: immutable (a project version)
-   or modifiable (a project in a branch). Communication between the repository
-   and Workbench clients is possible over local or wide area networks.&nbsp;
-Currently    the Workbench supports two internal authentication protocols
-for CVS: pserver    and ssh. Authentication protocols provided by external
-tools can also be used    by CVS.</p>
- 
-<div class="Topic"> 
-<p class="Para"> You can find more information on CVS at <a
- href="http://ximbiot.com/cvs/" class="URL" target="_blank">http://ximbiot.com/cvs/</a>.</p>
- </div>
-   
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-<br>
- <a href="concepts-26.htm">Team programming with CVS</a> <a
- href="concepts-27b.htm"><br>
- Branches</a><a href="concepts-27.htm"><br>
- Versions<br>
- </a><a href="concepts-17a.htm">Local history</a></p>
-   
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
- <br>
-<a href="../tasks/tasks-92.htm">Creating a CVS repository location</a> </p>
-   
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-<br><a href="../reference/ref-47.htm"> CVS</a> <br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a> </p>
-  
-
-  
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm
deleted file mode 100644
index 0769c41..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-29.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-         
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-         
-  <meta http-equiv="Content-Style-Type" content="text/css">
-          
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Three way comparisons</title>
-    
-</head>
-  <body style="background-color: rgb(255,255,255);">
-     
-<h1 class="Head"> Three way comparisons </h1>
-     
-<p class="Para"> Three way comparisons show the differences between three different 
-  versions of a resource.&nbsp;This feature is most useful when merging resources 
-  or when there is a conflict during synchronization.&nbsp;Conflicts occur when 
-  two developers add a version from the same branch to their Workbench, then each 
-  developer modifies it, then one developer attempts to commit the resource after 
-  the other developer has already committed it.&nbsp; </p>
-     
-<p class="Para"> When this situation arises, you can view the differences between 
-  three resource versions: the resource in the Workbench, the version of the resource 
-  that is committed in the branch, and the <i> common ancestor</i> from which the 
-  two conflicting versions are based.&nbsp;&nbsp;If a common ancestor cannot 
-  be determined, for example because a resource with the same name and path was 
-  created and committed by two different developers, the comparison becomes a 
-  two-way comparison. </p>
-<h2>Interpreting compare results</h2>
-<p>The Synchronize view allows you to view the differences between two or three 
-  files. If a common ancestor is available, the sync view performs a three way 
-  comparison. It is possible that a common ancestor for two conflicting resource 
-  versions cannot be determined, (e.g. a resource with the same name and path 
-  is created and committed by two different developers). In this case the compare 
-  becomes a regular two way compare.&nbsp;&nbsp;</p>
-<p class="Para">In a three way compare the Workbench shows you: </p>
-<ul class="UnorderedList">
-  <li class="Item"> what has been changed in the first child in comparison to 
-    the common ancestor.&nbsp;</li>
-  <li class="Item"> what has been changed in the second child in comparison to 
-    the common ancestor.</li>
-</ul>
-
-<p class="Para"> In the picture below, the common ancestor is displayed in the top pane of the text 
-  compare pane.&nbsp; The differences that you see 
-  highlighted are what has changed in the Workbench resource as compared to the 
-  common ancestor, and what has been changed in the branch resource as compared 
-  to the common ancestor. The sections that differ in all three files are highlighted 
-  as differences.&nbsp;Conflicts are shown in red, incoming changes in blue, and 
-  outgoing changes in gray. </p>
-  
-<p class="Para"> <img src="../images/Image49_3_way_compare.png" alt="Synchronize View with 3 way compare" border="0" >
-</p>
-       
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a></p>
-       
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="../tasks/tasks-68.htm">Comparing resources</a> <br>
-<a href="../tasks/tasks-115.htm">Synchronizing with a repository</a><br>
-<a href="../tasks/tasks-68dg.htm">Merging changes in the compare editor</a><br>
-<a href="../tasks/tasks-113.htm">Updating</a><br>
-<a href="../tasks/tasks-113b.htm"> Resolving conflicts</a><br>
-<a href="../tasks/tasks-68b.htm">Setting preferences for comparing files</a><br>
-<a href="../tasks/tasks-101.htm">Comparing resources with repository versions</a></p>
-       
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-25.htm">Compare editor</a><br>
-<a href="../reference/ref-33.htm">CVS Synchronize view</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm
deleted file mode 100644
index a996920..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-30.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Synchronizing with a CVS repository</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> Synchronizing with a CVS repository</h1>
-   
-<p class="Para"> In the CVS team programming environment, there are    two
-distinct processes involved in synchronizing resources: <i>updating</i> 
-   with the latest changes from a branch and <i>committing</i> to the branch.&nbsp;</p>
-   
-<p class="Para">When you make changes in the Workbench, the resources   
-are saved locally.&nbsp; Eventually you will want to commit your changes
-to the branch so others can have access to them.&nbsp; Meanwhile, others
-may have committed changes to the branch.&nbsp; You will want to update
-your Workbench resources with their changes.</p>
-   
-<p class="Para"><b>Important!</b>: It is preferable to update <i> before</i>
-    committing, in case there are conflicts with the resources in your Workbench
-   and the resources currently in the branch.&nbsp;&nbsp;</p>
-   
-<p>The synchronize view contains filters to control whether you want to view only 
-  <i>incoming changes</i> or <i>outgoing changes</i>. Incoming changes come from 
-  the branch. If accepted, they will update the Workbench resource to the latest 
-  version currently committed into the branch. Outgoing changes come from the 
-  Workbench. If committed, they will change the branch resources to match those 
-  currently present in the Workbench. </p>
-     
-<p>Regardless of which mode (filter) you select, the Synchronize view always 
-shows    you conflicts that arise when you have locally modified a resource 
-for which    a more recent version is available in the branch. In this 
-situation you    can choose to do one of three things: update the resource 
-from the branch, commit    your version of the resource to the branch, or 
-merge your work with the changes    in the branch resource. Typically 
-you will want to merge, as the other    two options will result in loss of 
-work. </p>
-     
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
- <br>
-  <a href="concepts-26.htm">Team programming with CVS</a>
-  <a href="concepts-27b.htm"><br>Branches</a>
-</p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
- <a href="../tasks/tasks-115.htm"><br>
-  Synchronizing with the repository</a><a href="../tasks/tasks-113.htm"><br>
-Updating</a><a href="../tasks/tasks-113b.htm"><br>
-  Resolving conflicts</a><a href="../tasks/tasks-100b.htm"><br>
-  Merging from a branch</a><a href="../tasks/tasks-114.htm"><br>
-Committing</a> </p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">CVS Synchronize view</a>
-</p>
-   
-
-
-     
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm
deleted file mode 100644
index 20d5cfb..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-4.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspectives</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Perspectives</H1>
-<p CLASS="Para" Label="Type">Each Workbench window contains one or more
-perspectives. A perspective defines the initial set and layout of views
-in the Workbench window. Within the window, each perspective shares the same set
-of editors. Each perspective provides a set of functionality aimed
-at accomplishing a specific type of task or works with specific types of
-resources.&nbsp;For example, the Java perspective combines views that you would
-commonly use while editing Java source files, while the Debug perspective
-contains the views that you would use while debugging Java programs. As you work
-in the Workbench, you will probably switch perspectives frequently.</p>
-<P CLASS="Para" Label=Type>Perspectives control what appears in certain menus
-and toolbars. They define visible <i> action sets</i>, which you
-can change to customize a perspective. You can save a perspective that you
-build in this manner, making your own custom perspective that you can open again
-later.&nbsp;&nbsp;</p>
-<P CLASS="Para" Label=Type>You can use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Perspectives</b></a>
-preference page to open perspectives 
-in the same window or in a new window.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="concepts-6.htm">Editors</a><br>
-<a href="concepts-5.htm">Views</a></p>
-<P CLASS="Para" Label=Type><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><a href="../tasks/tasks-9f.htm"><br>
-Opening perspectives<br>
-</a><a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-24.htm">Changing where perspectives open<br></a>
-<a href="../tasks/tasks-31.htm">Specifying the default perspective</a><br>
-<a href="../tasks/tasks-28.htm">Switching between perspectives</a><br>
-<a href="../tasks/tasks-9k.htm">Configuring perspective shortcuts</a><br>
-<a href="../tasks/tasks-9m.htm">Configuring perspective command groups</a><br>
-<a href="../tasks/tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a><br>
-  <a href="../tasks/tasks-9i.htm">Saving a user defined perspective</a><a href="../tasks/tasks-9j.htm"><br>
-Resetting perspectives</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm
deleted file mode 100644
index 2f372d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-5.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Views</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Views</H1>
-<P CLASS="Para" Label=Type> Views support editors and provide alternative presentations 
-  as well as ways to navigate the information in your Workbench.&nbsp; For example, 
-  the Project Explorer and other navigation views display projects and other resources that you are working 
-  with.</P>
-<P CLASS="Para" Label=Type>
- Views also have their own menus. To open the menu for a view, click the icon at the left
-end of the view's title bar. Some views also have their own toolbars. The actions represented by buttons on view
-toolbars only affect the items within that view.&nbsp;</P>
-<P CLASS="Para" Label=Type>
-A view might appear by itself, or stacked with other
-views in a tabbed notebook.&nbsp;You can change the layout of a perspective by
-opening and closing views and by docking them in different
-positions in the Workbench window.&nbsp; </P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-4.htm">Perspectives</a><br>
-<a href="concepts-21.htm">Fast views</a><br>
-<a href="concepts-21a.htm">Detached views</a><br>
-<a href="concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a><br>
-<a href="../tasks/tasks-9l.htm">Detaching views</a><br>
-<a href="../gettingStarted\qs-39g.htm">Maximizing a view or editor</a><br>
-  <a href="../tasks/tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="../tasks/tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm
deleted file mode 100644
index 53da9f8..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editors and the editor area</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Editors</H1>
-<P CLASS="Para" Label=Type>
-Most perspectives in the Workbench are comprised of an editor area and one or more
-views. </P>
-<P CLASS="Para" Label=Type>You can associate different editors with different
-types of files. For example, when you open a file for editing by double-clicking
-it in one of the navigation views, the associated editor opens in the Workbench.
-If there is no
-associated editor for a resource, the Workbench attempts to launch an <i>external
-editor</i>  outside the Workbench. (On Windows, the Workbench will first
-attempt to launch the editor in place as an OLE document. This type
-of editor is referred to as an <i>embedded editor</i>. For example, if you have a
-.doc file in the Workbench and Microsoft Word is registered as the editor for .doc
-files in your operating system, then opening the file will launch Word as an OLE document within the Workbench editor
-area. The Workbench menu bar and toolbar will be updated with options for
-Microsoft Word.)&nbsp; </P>
-<P CLASS="Para" Label=Type>Any number of editors can be open at once, but only
-one can be active at a time. The main menu bar and toolbar for the
-Workbench window contain operations that are applicable to the active
-editor.&nbsp; </P>
-<P CLASS="Para" Label=Type>Tabs in the editor area indicate the names of
-resources that are currently open for editing. An asterisk (*) indicates that an editor has unsaved
-changes.&nbsp;&nbsp; </P>
-<P CLASS="Para" Label=Type>By default, editors are stacked in the editor area,
-but you can choose to tile them in order to view source files simultaneously.</P>
-<P CLASS="Para" Label=Type>
-Here is an example of a text editor in the Workbench:</P>
-<P CLASS="Para" Label=Type> <img src="../images/Image5_text_editor.png" alt="Text editor" border="0"> 
-</P>
-<P>&nbsp;The gray border at the left margin of the editor area may contain
-icons that flag errors, warnings, or problems detected by the system. Icons also
-appear if you have created bookmarks, added breakpoints for debugging, or
-recorded notes in the Tasks view. You can view details for any icons in the left
-margin of the editor by moving the mouse cursor over them.
-</P>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><a href="concepts-2.htm"><br>
-Workbench<br>
-</a><a href="concepts-6a.htm">External editors</a><a href="cbookmrk.htm"><br>
-Bookmarks</a><a href="ctskview.htm"><br>
-Tasks view<br>
-</a><a href="cnav.htm">
-Project Explorer view</a></p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46.htm">Opening files for editing</a><br>
-<a href="../tasks/tasks-51.xhtml">Associating editors with file types</a><br>
-<a href="../tasks/tasks-52.htm">Editing files outside the Workbench</a></p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm
deleted file mode 100644
index 8bf5325..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-6a.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>External editors</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-External editors</H1>
-<P CLASS="Para" Label=Type>Sometimes you may need to use an external program to
-edit a file in the Workbench. This can occur, for example, when the Workbench
-has no editor for that file type.</P>
-<P CLASS="Para" Label=Type>The external program will be used as the default editor if that program is
-registered as the system default editor for that file type and no other editor
-is registered for that file type in the Workbench. For example, on most systems the default
-editor for JPEG files is an application for editing or viewing image files. If there is no other editor
-associated with .jpg or .jpeg files in the Workbench, then opening a JPEG file from the
-Workbench would cause the file to be opened externally, in the system default editor.</P>
-<P CLASS="Para" Label=Type>To open an external program that is not the default editor, you can use
-<b>Open With &gt; Other...</b> from the context menu of a file. External programs can also be registered in
-Eclipse as the associated editor for a given file type. Use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Editors &gt; File Associations</b></a> preference page to register editors.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="concepts-2.htm">Workbench</a><br>
-<a href="concepts-6.htm">Editors</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46.htm">Opening files for editing</a><br>
-<a href="../tasks/tasks-51.xhtml">Associating editors with file types</a><br>
-<a href="../tasks/tasks-52.htm">Editing files outside the Workbench</a></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-antexttools.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-antexttools.htm
deleted file mode 100644
index 7a09828..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-antexttools.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <title>Ant &amp; External tools</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body>
-<h1>Ant &amp; External tools</h1>
-<h2>Ant</h2>
-<p><a href="concepts-antsupport.htm">Ant support</a> allows you to <a href="../gettingStarted/qs-82_create.htm">create</a>, import, export, configure and <a href="../gettingStarted/qs-84_run_ant.htm">run tasks / buildfiles</a> using the Workbench.
-Any <a href="../gettingStarted/qs-92_project_builders.htm">Ant buildfile</a> configuration you create can be used as part of the build process
-for a project, which will run in the specified order every time the project is built.
-</p>
-<p>
-Whether run as a stand-alone Ant task or as a project builder, each At buildfile can be configured to provide its output in either (or all of) of:
-</p>
-<ul>
-<li>The <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b></li>
-<li>A file in the local filesystem</li>
-<li>A custom Ant logger</li>
-</ul>
-
-<h2>External tools</h2>
-<p><a href="concepts-exttools.htm">External tools</a> allow you to configure and run programs,
-batch files, Ant buildfiles, and others using the Workbench.
-Any <a href="../gettingStarted/qs-96_non_ant_pjs.htm">external tool</a> configuration you create can be used as part of the build process
-for a project, which will run in the specified order every time the project is built.
-</p>
-<p>
-Whether run as a stand-alone tool or as a project builder, each external tool can be configured to provide its output in either (or both) of:
-</p>
-<ul>
-<li>The <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b></li>
-<li>A file in the local filesystem</li>
-</ul>
-
-<p>
-	<br>
-	<img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-	<a href="concepts-antsupport.htm">Ant support</a><br>
-	<a href="concepts-exttools.htm">External tools</a><br>
-	<a href="concepts-22.htm">Builds</a>
-</p>
-<p>
-	<img src="../images/ngrelt.png" alt="Related tasks" BORDER=0 ><br>
-	<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-	<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a>
-</p>
-<p>
-	<img src="../images/ngrelr.png" alt="Related reference" BORDER=0 ><br>
-	<a href="../reference/ref-exttoolsprefs.htm">External Tools preferences</a><br>
-	<a href="../reference/ref-anticons.htm">External Tools and Ant icons</a><br>
-	<a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm
deleted file mode 100644
index 8c9a233..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-antsupport.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant support</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-
-<h1>Ant support</h1>
-<p>
-Apache Ant is an open source, Java-based build tool. &nbsp;See <a href="http://ant.apache.org" target="_blank">http://ant.apache.org</a>
-for more details.</p>
-<p>
-Ant support allows you to create and run Ant buildfiles from the Workbench.
-These Ant buildfiles can operate on resources in the file system as well as
-resources in the workspace. 
-</p>
-<p>
-Output from an Ant buildfile is displayed in the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b> in the same hierarchical
-format seen when running Ant from the command line. Ant tasks (for example <code>[mkdir]</code>)
-are hyper-linked to the associated Ant buildfile, and <code>javac</code> error reports are hyper-linked
-to the associated Java source file and line number.
-</p>
-<p>
-You can add classes to the Ant classpath and add Ant tasks and types from the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Ant &gt; Runtime</b></a> preference page.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-22.htm">Builds</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a><br>
-<a href="../tasks/antRunner.htm">antRunner application entry point</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-antprefs.htm">Ant preference page</a><br>
-<a href="../reference/ref-anteditorprefs.htm">Ant editor preference page</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preference page</a><br>
-<a href="../reference/ref-antview.htm">Ant view</a><br>
-<a href="../reference/ref-anteditor.htm">Ant editor</a><br>
-<a href="../reference/ref-anticons.htm">External Tools and Ant icons</a><br>
-<a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm
deleted file mode 100644
index b4a1f0f..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-cvs-watch.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Watch/Edit</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-<h1 class="Head"> Watch/Edit</h1>
-   
-<p class="Para"> CVS provides a notification scheme which allows a group of developers 
-  to know if somebody is working on a given file. This facility is known as <em>watches</em>. 
-  By setting a <em>watch</em> on a file, you can have CVS notify you via email 
-  if someone else starts to <em>edit</em> this file. This mechanism is notification 
-  based only; the file is not locked in any way on the server, and several people 
-  are allowed to edit the same file at the same time.</p>
-<p class="Para">In addition to watch list notification, <em>edit</em> on its own 
-  is useful for discovering if others are also editing that file. This is because 
-  when you edit a file, you will be informed if someone else is already editing 
-  it. </p>
-<p class="Para">Normally with CVS clients, you would need to issue an explicit <em>edit</em>.
-  With Team CVS support however, an <em>edit</em> is 
-  automatically issued by the client when you start to modify a file. In addition, 
-  when <em>editing</em> a file, Team CVS provides you with the list of people 
-  already editing a file. This allows you to find out who is working on a file 
-  before you start to edit it.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
- <br>
-  <a href="concepts-26.htm">Team programming with CVS</a> </p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- > <a href="../tasks/tasks-cvs-watch.htm"><br>
-  Finding out who's working on what: watch/edit</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br>
-  <a href="../reference/ref-47.htm">CVS</a> </p>
-   
-
-     
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm b/bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm
deleted file mode 100644
index de3458e..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm
+++ /dev/null

@@ -1,228 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <title>External tools</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body>
-<h1>External tools</h1>
-
-<p>External tools allow you to configure and run programs,
-batch files, Ant buildfiles, and others using the Workbench. You can save
-these external tool configurations and run them at a later time.</p>
-
-<p>Output from external tools is displayed in the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b>.</p>
-
-<p>You can add external tools as part of the build process
-for a project. These external tools will run in the specified order every
-time a project is built.</p>
-
-<p>The following variables are available when you configure
-an external tool. These variables are automatically expanded each time
-the external tool is run.</p>
-
-<table border="1" width="80%" cellpadding="5" cellspacing="0" summary="Variables available to external tools">
-  <thead>
-    <tr>
-      <th width="25%" colspan="1" rowspan="1"> <p> Variable Name </p></th>
-      <th colspan="1" rowspan="1"> <p> Description </p></th>
-    </tr>
-  </thead>
-  <tbody>
-  	<tr>
-  		<td><b>${workspace_loc}</b></td>
-  		<td>The absolute path on the system's hard drive to Eclipse's workspace directory</td>
-  	</tr>
-  	<tr>
-  		<td><b>${workspace_loc:<i>&lt;resource path&gt;</i>}</b></td>
-  		<td>The	absolute path on the system's hard drive to the specified resource. The
-			<i>&lt;resource
-			path&gt;</i> is the full path of the resource relative to the workspace root.
-			For example ${workspace_loc:/MyProject/MyFile.txt}. Note that the expanded
-			result of this variable is not the same as ${workspace_loc}/MyProject/MyFile.txt
-			if the project's contents directory for MyProject is outside the workspace
-			directory.
-		</td>
-  	</tr>
-  	<tr>
-  		<td><b>${project_loc}</b></td>
-  		<td>The absolute path on the system's
-			hard drive to the currently selected resource's project or to the project
-			being built if the external tool is run as part of a build.
-		</td>
-  	</tr>
-  	<tr>
-  		<td><b>${project_loc:<i>&lt;resource path&gt;</i>}</b></td>
-  		<td>The absolute path on the system's hard drive to the specified resource's project.
-			The <i>&lt;resource path&gt;</i> is the full path of the resource relative
-			to the workspace root. For example ${workspace_loc:/MyProject/MyFile.txt}.
-			Note that the expanded result of this variable is not the same as ${workspace_loc}/MyProject
-			if the project's contents directory for MyProject is outside the workspace
-			directory.
-		</td>
-  	</tr>
-  	<tr>
-  		<td><b>${container_loc}</b></td>
-  		<td>The absolute path on the system's hard drive to the currently selected resource's parent (either a folder or project).</td>
-  	</tr>
-  	<tr>
-  		<td><b>${container_loc:<i>&lt;resource path&gt;</i>}</b></td>
-  		<td>The absolute path on the system's hard drive to the specified resource's parent
-			(either a folder or project). The <i>&lt;resource path&gt;</i> is the full
-			path of the resource relative to the workspace root. For example:${workspace_loc:/MyProject/MyFolder/MyFile.txt}.
-			Note that the expanded result of this variable is not the same as ${workspace_loc}/MyProject/MyFolder
-			if the project's contents directory for MyProject is outside the workspace
-			directory.
-		</td>
-  	</tr>
-  	<tr>
-  		<td><b>${resource_loc}</b></td>
-  		<td>The absolute path on the system's hard drive to the currently selected resource.</td>
-  	</tr>
-  	<tr>
-  		<td><b>${resource_loc:<i>&lt;resource path&gt;</i>}</b></td>
-  		<td>The absolute path on the system's hard drive to the specified resource. The
-			<i>&lt;resource path&gt;</i> is the full path of the resource relative to the workspace root.
-			For example ${workspace_loc:/MyProject/MyFile.txt}. Note that the expanded
-			result of this variable is not the same as ${workspace_loc}/MyProject/MyFile.txt
-			if the project's contents directory for MyProject is outside the workspace
-			directory.
-		</td>
-  	</tr>
-  	<tr>
-  		<td><b>${project_path}</b></td>
-  		<td>The full path, relative to the
-			workspace root, of the currently selected resource's project or of the
-			project being built if the external tool is run as part of a build.
-		</td>
-  	</tr>
-  	<tr>
-  		<td><b>${container_path}</b></td>
-  		<td>The full path, relative to the
-			workspace root, of the currently selected resource's parent (either a folder
-			or project).
-		</td>
-  	</tr>
-  	<tr>
-  		<td><b>${resource_path}</b></td>
-  		<td>The full path, relative to the workspace root, of the currently selected resource.</td>
-  	</tr>
-  	<tr>
-  		<td><b>${project_name}</b></td>
-  		<td>The name of the currently selected resource's project or of the project being built if the external tool is
-		run as part of a build.</td>
-  	</tr>
-  	<tr>
-  		<td><b>${container_name}</b></td>
-  		<td>The name of the currently selected resource's parent (either a folder or project).</td>
-  	</tr>
-  	<tr>
-  		<td><b>${resource_name}</b></td>
-  		<td>The name of the currently selected resource.</td>
-  	</tr>
-  	<tr>
-  		<td><b>${build_type}</b></td>
-  		<td>The kind of build when the external
-			tool is run as part of a build. The value can be one of "full", "incremental",
-			or "auto". If the external tool is run outside of a build, the value is
-			then "none".
-		</td>
-  	</tr>
-  </tbody>
-</table>
-
-<p>Lets assume your Eclipse workspace directory is <code>c:\eclipse\workspace</code>
-and you have two projects, <code>MyProject1</code> and <code>MyProject2</code>. The first project,
-<code>MyProject1</code>, is located inside the workspace directory, the second project,
-<code>MyProject2</code>, is located outside the workspace directory at <code>c:\projects\MyProject2</code>.
-Lets look at how the variable examples below will be expanded when an
-external tool is run, if the resource <code>/MyProject2/MyFolder/MyFile.txt</code> is
-selected.</p>
-<table border="1" width="50%" cellpadding="5" cellspacing="0" summary="Variables available to external tools">
-	<thead>
-    	<tr>
-      		<th width="25%" colspan="1" rowspan="1"> <p> Variable Example </p></th>
-      		<th colspan="1" rowspan="1"> <p> Expanded Results </p></th>
-    	</tr>
-	</thead>
-	<tbody>
-		<tr>
-			<td>${workspace_loc}</td>
-			<td>c:\eclipse\workspace</td>
-		</tr>
-		<tr>
-			<td>${workspace_loc:/MyProject1/MyFile.txt}</td>
-			<td>c:\eclipse\workspace\MyProject\MyFile.txt</td>
-		</tr>
-		<tr>
-			<td>${workspace_loc:/MyProject2/MyFile.txt}</td>
-			<td>c:\projects\MyProject2\MyFile.txt</td>
-		</tr>
-		<tr>
-			<td>${project_loc}</td>
-			<td>c:\projects\MyProject2</td>
-		</tr>
-		<tr>
-			<td>${project_loc:/MyProject1/MyFile.txt}</td>
-			<td>c:\eclipse\workspace\MyProject</td>
-		</tr>
-		<tr>
-			<td>${container_loc}</td>
-			<td>c:\projects\MyProject2\MyFolder</td>
-		</tr>
-		<tr>
-			<td>${resource_loc}</td>
-			<td>c:\projects\MyProject2\MyFile.txt</td>
-		</tr>
-		<tr>
-			<td>${project_path}</td>
-			<td>/MyProject2</td>
-		</tr>
-		<tr>
-			<td>${container_path}</td>
-			<td>/MyProject2/MyFolder</td>
-		</tr>
-		<tr>
-			<td>${resource_path}</td>
-			<td>/MyProject2/MyFolder/MyFile.txt</td>
-		</tr>
-		<tr>
-			<td>${project_name}</td>
-			<td>MyProject2</td>
-		</tr>
-		<tr>
-			<td>${container_name}</td>
-			<td>MyFolder</td>
-		</tr>
-		<tr>
-			<td>${resource_name}</td>
-			<td>MyFile.txt</td>
-		</tr>
-		<tr>
-			<td>${build_type}</td>
-			<td>none</td>
-		</tr>
-	</tbody>
-</table>
-<p>
-	<br>
-	<img src="../images/ngrelc.png" alt="Related concepts" border="0" ><br>
-	<a href="concepts-antsupport.htm">Ant support</a><br>
-	<a href="concepts-22.htm">Builds</a>
-</p>
-<p>
-	<img src="../images/ngrelr.png" alt="Related reference" BORDER=0 ><br>
-	<a href="../reference/ref-exttoolsprefs.htm">External Tools preferences</a><br>
-	<a href="../reference/ref-anticons.htm">External Tools and Ant icons</a><br>
-	<a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a>
-</p>
-<p>
-	<img src="../images/ngrelt.png" alt="Related tasks" BORDER=0 ><br>
-	<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-	<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/coutline.htm b/bundles/org.eclipse.platform.doc.user/concepts/coutline.htm
deleted file mode 100644
index a48448f..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/coutline.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Outline view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY>
-<H1 CLASS="Head">
-Outline view</H1>
-
-<P>The Outline view displays an outline of a structured file that is currently 
-  open in the editor area, and lists structural elements.&nbsp;The contents of 
-  the Outline view are editor specific. In the example below, which is for a Java 
-  source file, the structural elements are classes, fields, and methods. The contents 
-  of the toolbar are also editor specific. </p>
-
-<P><img src="../images/ref-8.png" alt="Picture of Outline view showing structure for a Java file" border="0" > 
-</p>
-<p>
-  To add the Outline view to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ContentOutline)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Outline</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-5.htm">Views</a><br>
-<a href="concepts-4.htm">Perspectives</a><br>
-<a href="concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-9b.htm">Creating fast views</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm b/bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm
deleted file mode 100644
index abc408f..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cpathvars.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Path variables</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Path variables</H1>
-<p>
-Path variables specify locations on the file system. The location of linked resources
-may be specified relative to these path variables. They allow you to avoid references to 
-a fixed location on your file system.
-</p>
-<p>
-By using a path variable, you can share projects containing linked resources with
-team members without requiring the exact same directory structure as on your file 
-system.
-</p>
-<p>
-You can load a project that uses path variables even if you do not currently have all 
-the path variables defined in your workspace. A linked resource that uses a missing path
-variable is flagged using a special decorator icon. In addition, the
-<b>File &gt; Properties &gt; Info</b> 
-property page and the Properties view
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>)
-for a linked resource indicate the 
-variable and whether it is defined or not. A path variable can also specify a 
-location that does not currently exist on the file system. Linked resources that use such
-a path variable are indicated using the same decorator icon mentioned above.
-</p>
-<p>
-You can create new path variables and edit and remove existing path variables on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Workspace &gt; Linked Resources</b></a> preference page.
-</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-13.htm">Linked resources</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-45.htm">Creating linked resources</a><br>
-<a href="../tasks/tasks-49.htm">Viewing resource properties</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br>
-  <a href="../reference/ref-14b.htm">Linked resources</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm b/bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm
deleted file mode 100644
index 9cefd47..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cprbview.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Problems view (concept)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<H1 CLASS="Head">Problems view</H1>
-<P CLASS="Para"> As you work with resources in the workbench, various builders 
-  may automatically log problems, errors, or warnings in the Problems view. For 
-  example, when you save a Java source file that contains syntax errors, those 
-  will be logged in the Problems view. When you double-click the icon for a problem, 
-  error, or warning, the editor for the associated resource automatically opens 
-  to the relevant line of code.&nbsp;</P>
-<p><img src="../images/prob.png" alt="Picture of the Problems view with two warnings added to it." border="0" ></p>
-<p CLASS="Head">By default the problems view will group your problems by severity. 
-  You can also group them by type or not at all. Certain components will add their 
-  own grouping. For instance the Java development tools (JDT) support adds a Java 
-  Problem Type group. The grouping can be selected using the <b>Group By</b> menu.</p>
-<p CLASS="Head">The first column of the Problems view displays an icon that denotes 
-  the type of line item, the category and the description. Left-click the item to 
-  open the file in an editor and highlight the line containing the problem. 
-</p>
-<p CLASS="Head">You can configure the contents of the Problems view to view only warnings 
-  and errors associated with a particular resource or group of resources. This is done
-  using the <b>Configure Contents</b> dialog available from the drop down menu. You can
-  add multiple filters to the problems view and enable or disable 
-  them as required. Filters can either be additive (any problem that satisfies at least 
-  one of the enables filters will be shown) or exclusive (only problems that satisfy all
-  of the filters will be shown)  The two most popular filters (All Errors and Warnings on
-  Selection) are provided by default.</p>
-<p><img src="../images/prbfil.png" alt="Picture of the Filters options." border="0" ></p>
-<p>Problems can be fixed by selecting <b>Quick Fix</b> from the context menu. The list 
-  of possible resolutions will be shown.</p>
-<p><br>
-  <img src="../images/prb_quickfix.png" alt="Picture of the Quick Fix dialog"></p>
-<p CLASS="Head">
-  To add the Problems view to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ProblemView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Problems</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="concepts-11.htm">Markers</a><br>
-  <a href="cbookmrk.htm">Bookmarks</a><br>
-  <a href="ctskview.htm">Tasks view</a><br>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tquickfix.htm">Automatically fixing problems</a><br>
-</p>
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm b/bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm
deleted file mode 100644
index bdbf679..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cpropview.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Properties view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Properties view</H1>
-<P CLASS="Para">
-The properties view displays property names and values for a selected item such
-as a resource.
-Here is an example:</P>
-<P CLASS="Para">
-<img src="../images/Image240_props_view.png" alt="Picture of a Properties sheet with 3 columns, including a column for property and a column for value." border="0" ></P>
-<P CLASS="Para">Toolbar buttons allow you to toggle to display
-properties by category or to filter advanced properties. Another
-toolbar button allows you to restore the selected property to its default value.</P>
-<P>To see more detailed information about a resource than the Properties view
-gives you, right-click the resource name in one of the navigation views and select
-Properties from the pop-up menu.
-</P>
-<p>
-  To add the Properties view to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>.
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm b/bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm
deleted file mode 100644
index 52e6988..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/csearchview.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Search view</title></head><body>
-<h1>
-Search view</h1>
-
-<p>
-This view displays the results of a search.&nbsp;&nbsp;</p>
-
-<p>
-Text searches will only search for expressions in files with extensions (file
-types) specified in the search dialog.</p>
-
-<p>
-Here is what the Search view looks like:</p>
-<p>
-<img src="../images/Image237_search_view.png" alt="Search View" border="0" ></p>
-<h2>
-Toolbar</h2>
-<p>The toolbar in the Search view contains the following buttons:</p>
-<dl>
-	<dt>Show Next Match</dt>
-		<dd>This command highlights the next match of the search expression in the editor area, opening the file if required.</dd>
-	<dt>Show Previous Match</dt>
-		<dd>This command highlights the previous match of the search expression in the editor area, opening the file if required.</dd>
-	<dt>Remove Selected Matches</dt>
-		<dd>Removes all highlighted matches from the search results.</dd>
-	<dt>Remove All Matches</dt>
-		<dd>Removes all search result form the search view</dd>
-	<dt>Expand all</dt>
-		<dd>Expands every tree item in the search view</dd>
-	<dt>Collapse all</dt>
-		<dd>Collapses every tree item in the search view</dd>
-	<dt>Run the Current Search Again</dt>
-		<dd>This command reruns the current search again, so that removed search
-		results reappear or changes are reflected.</dd>
-	<dt>Cancel Current Search</dt>
-		<dd>Cancels the current search</dd>
-	<dt>Show Previous Searches</dt>
-		<dd>This command allows you to browse previously conducted searches and repeat 
-		a previous search.&nbsp; You can select a previous search from the drop-down 
-		menu or clear the search history.</dd>
-	<dt>Pin the Search view</dt>
-		<dd>Pinning the search view means that subsequent searches will shown their
-		results in another search view and that the pinned view remains unchanged.</dd>
-</dl>
-
-<p><br>
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<a href="concepts-12.htm"><br>Resources</a>&nbsp;
-<br>
-<a href="concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a>
-<br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br><a href="../reference/ref-26.htm">Search view</a><br><a href="../reference/ref-45.htm">File search</a><br></p>
-
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm b/bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm
deleted file mode 100644
index f33beb2..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/ctskview.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tasks view (concept)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-
-<H1 CLASS="Head">
-Tasks view</H1>
-<P CLASS="Para"> You can assign tasks within your project by right clicking marker 
-  bar's context menu and selecting <strong>Add Task</strong> or you can add items 
-  within the Tasks view by selecting <strong>Add Task </strong><img src="../images/addtask.png" alt="Picture of the Tasks view with two dummy tasks added to it." border="0" >. 
-  For example, if you would like to record reminders to follow up on something 
-  later, add it to the tasks view. When you add a task, you have the option of 
-  associating it with a resource so that you can use the Tasks view to quickly 
-  open that resource for editing.</P>
-<p><img src="../images/Image243_tasks_view.png" alt="Picture of the Add Task icon" border="0" ></p>
-<p CLASS="Head"> The first column of the Tasks view displays an icon that denotes 
-  the type of line item. You can sort and filter line items in the task view, 
-  to view only high-priority tasks or tasks associated with a particular resource 
-  or group of resources.&nbsp;</p>
-<p CLASS="Head"> By default, the Tasks view is included in the Resource perspective. 
-  To add it to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.TaskList)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Tasks</b></a>.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="concepts-11.htm">Markers</a><br>
-<a href="cbookmrk.htm">Bookmarks</a><br>
-<a href="cprbview.htm">Problems view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../tasks/tasks-3e.htm">Moving and docking views</a><br>
-<a href="../tasks/tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="../tasks/tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="../tasks/tasks-79.htm">Filtering the Tasks view</a><br>
-<a href="../tasks/tasks-78.htm">Deleting tasks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-31.htm">Tasks view</a>
-</p>
-
-
-</body>
-
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm b/bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm
deleted file mode 100644
index a3cacd0..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/cworkset.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working sets</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Working sets</H1>
-<P CLASS="Para" Label=Type>
-Working sets group elements for display in views or for operations on a set 
-of elements. </P>
-
-<P CLASS="Para" Label=Type> The navigation views use working sets to restrict 
-  the set of resources that are displayed. If a working set is selected in the 
-  navigator, only resources, children of resources, and parents of resources contained 
-  in the working set are shown. The problems view, tasks view and bookmarks view 
-  can all be filtered based on a working set via the <b>Configure Contents</b> view menu item. 
-  When using the search facility, 
-  you can also use working sets to restrict the set of elements that are searched. 
-</P>
-
-<P CLASS="Para" Label=Type> Different views provide different ways to specify 
-  a working set.  The views in the Eclipse SDK use the <b>Window Working Set</b> by 
-  default. The Window Working Set is specified in <b>Window &gt; Working Sets</b> menu
-  and is initially empty. Views that support working sets typically use the following 
-  working set selection dialog to manage existing working sets and to create new working sets:</P>
-<P CLASS="Para" Label=Type> &nbsp; <img src="../images/Image87_workset_sel.png" alt="Picture of working set selection dialog" border="0" > 
-</P>
-
-<P CLASS="Para" Label=Type>&nbsp;
-</P>
-
-<P CLASS="Para" Label=Type>
-When you create a new working set you can choose from different types
-of working sets. In the example below you can create a resource working set, a
-Java working set or a help working set.
-</P>
-
-<P CLASS="Para" Label=Type>
-&nbsp;
-<img src="../images/Image88_workset_new_type.png" alt="Picture of type selection page of new working set wizard" border="0" >
-</P>
-
-<P CLASS="Para" Label=Type>&nbsp;
-
-</P>
-
-<P CLASS="Para" Label=Type>
-If you create a new resource working set you will be able to select the working 
-set resources as shown below. The same wizard is used to edit an existing working
-set. Different types of working sets provide different kinds of working set 
-editing wizards.
-</P>
-
-<P CLASS="Para" Label=Type>
-&nbsp;
-<img src="../images/Image89_workset_new_res.png" alt="Picture of edit page of working set wizard" border="0" >
-</P>
-
-<P CLASS="Para" Label=Type>&nbsp;
-
-</P>
-<p CLASS="Para" Label=Type>
-Working sets may also be a part of a manual build workflow.  With autobuild disabled the 
-<b>Project &gt; Build Working Set</b> menu becomes enabled.  From here you are able to selectively build working sets of your choosing.
-</p>
-
-<DIV CLASS="Note">
-  <P CLASS="Para" Label=Type> <strong>Note:</strong> Newly created resources are 
-    not automatically included in the active working set. They are implicitly 
-    included in a working set if they are children of an existing working set 
-    element. If you want to include other resources after you have created them 
-    you have to explicitly add them to the working set. </P>
-</DIV>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="cnav.htm">Project Explorer view</a><br>
-<a href="ctskview.htm">Tasks view</a><br>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks." ><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-<a href="../tasks/tasks-48b.htm">Showing or hiding resources in the Project Explorer view</a><br>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/help.htm b/bundles/org.eclipse.platform.doc.user/concepts/help.htm
deleted file mode 100644
index 51152a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/help.htm
+++ /dev/null

@@ -1,126 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Help</title>
-</head>
-<body>
-
-<h1>Help</h1>
-
-<p>
-The Help system lets you browse, search, bookmark, and print help documentation.
-The documentation is organized into sets of information that are analogous to
-books. The help system also supplies a text search capability for finding the
-information you need by search phrase or keyword, and context-sensitive help for
-finding information to describe the particular function you are working with.
-</p>
-
-<p>
-You can interact with help system in the workbench using the <strong>Help
-view</strong> or in the separate <strong>Help window</strong>. The view and
-window provide the same information but in different ways.
-</p>
-
-<h2>The Help view</h2>
-
-<p>
-The Help view provides help inside the workbench. You can open the view from
-the main menu by selecting <b>Help &gt; Dynamic Help</b> or <b>Help &gt;
-Search</b>. The view will open showing the Related Topics or Search page,
-respectively. You can use links at the bottom of the help view to turn to other
-pages.
-</p>
-
-<p>
-You can <a href="help_view.htm">read more</a> about the Help view and its
-various pages.
-</p>
-
-<p>
-<img src="../images/help_view_context.png"
-alt="Help view showing Related Topics page">
-</p>
-
-<h2>The Help window</h2>
-
-<p>
-The Help window provides the same content as the Help view, but in a
-<em>separate</em> window instead of in a view. You can open the window from the
-main menu by selecting <b>Help &gt; Help Contents</b>. The first view shown in
-the window is called Contents. This view displays the table of contents for the
-product documentation. Click on one of the links to expand the navigation tree
-for a set of documentation.
-</p>
-
-<p>
-<img src="../images/help_window.png" alt="Help window">
-</p>
-
-<p>
-Note that if your browser does not have JavaScript enabled or is an does not support the features 
-required to display the normal help application "basic" help which will be displayed - this can 
-easily be identified because closed
-books in the table of contents do not have an expander icon. You can find the user agent of your
-browser <a href="../../../about.html?show=agent">here.</a>
-</p>
-
-<h2>Context-sensitive help</h2>
-
-<p>
-If you are working through a task and encounter a part of the interface that
-you do not understand, you can summon context-sensitive help. By default, this
-will display the Help view and give you some specific information about the
-view/editor/dialog you are using, and possibly some links to topics for further
-help.
-</p>
-
-<p>
-Context-sensitive help can be accessed by bringing focus to the interface part
-in question by clicking on it or using the Tab key, and then pressing
-<code>F1</code> (<code>Shift+F1</code> on GTK+, and <code>Help</code> on the
-Mac). Alternatively, in dialogs you can achieve the same result by pressing
-the <img src="../images/help_icon.png" alt="Help button"> help button in the
-dialog's button bar.
-</p>
-
-<h3>Infopops</h3>
-
-<p>
-An alternative way of presenting context-sensitive information is using
-<b>infopops</b>. You can use the 
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.help.ui.browsersPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help preference page</b>
-</a>
-
-to configure Help to use infopops instead of the Help view for displaying
-context-sensitive help.
-</p>
-
-<p>
-<img src="../images/help_infopop.png" alt="Help infopop" border="0">
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="help_view.htm">Help view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/help.xhtml">Accessing help</a><br>
-<a href="../tasks/help_navigate.htm">Navigating help topics</a><br>
-<a href="../tasks/help_context.htm">Accessing context-sensitive help</a><br>
-<a href="../tasks/help_search.htm">Searching help</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/help_preferences.htm">Help preferences</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/help_view.htm b/bundles/org.eclipse.platform.doc.user/concepts/help_view.htm
deleted file mode 100644
index e91e128..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/help_view.htm
+++ /dev/null

@@ -1,241 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Help view</title>
-</head>
-<body>
-
-<h1>Help view</h1>
-
-<p>
-The Help view provides user assistance inside the workbench. The view consists
-of several pages. Each page presents help in a different fashion. Hyper links at
-the bottom of the help view allow switching among pages, and clicking any topic
-will display its contents.
-</p>
-
-<h2>Related Topics</h2>
-
-<p>
-<img src="../images/help_view_context.png" alt="Related Topics">
-</p>
-
-<p>
-The <strong>Related Topics</strong> page shows description and help topics
-related to the current workbench context. The <b>About</b> section shows context
-help specific to your current context, and the <b>Search</b> link allows you to search 
-for more results based on the name of the view or dialog that has focus. 
-The Related Topics page tracks changes in the workbench and
-continuously updates displayed information.
-</p>
-
-<h2>Contents</h2>
-
-<p>
-<img src="../images/help_view_toc.png" alt="All Topics">
-</p>
-
-<p>
-The <strong>Contents</strong> page shows the table of contents. It is a
-hierarchy of all help topics arranged in a tree. The tree branches can be
-expanded to browse topics that can be displayed using a single mouse click.
-</p>
-
-<h2>Search</h2>
-
-<p>
-<img src="../images/help_view_search.png" alt="Search">
-</p>
-
-<p>
-The <strong>Search</strong> page allows locating local topics, cheat sheets,
-welcome content, remote documents, and other documents given a search query.
-Links to search hits are displayed along with a summary of topic contents.
-Search scope controls a subset of documentation being searched. Multiple search
-scopes can be configured, each defining a custom set of resources from among
-local documentation, additional local search engines or remote engines on the
-web.
-</p>
-
-<h2>Index</h2>
-
-<p>
-<img src="../images/help_view_index.png" alt="Index">
-</p>
-
-<p>
-The <strong>Index</strong> page provides an index of keywords that direct the
-user to specific help topics, similar to indexes found at the back of a book. As
-you type in the text field, the best match will automatically be highlighted in
-the list of keywords. Pressing enter or clicking on a keyword will display the
-given topic.
-</p>
-
-<p>
-<i>Note: The index page will only appear when index content is available in
-the workbench.</i>
-</p>
-
-<h2>Bookmarks</h2>
-
-<p>
-<img src="../images/help_view_bookmarks.png" alt="Bookmarks">
-</p>
-
-<p>
-The <strong>Bookmarks</strong> shows topics marked as personal bookmarks.
-</p>
-
-<h2>Toolbar</h2>
-
-<p>The toolbar of the Help view contains the following buttons. The
-available buttons depends on the currently displayed page.</p>
-
-<dl>
-<dt>Back</dt>
-
-<dd>Displays the page or the topic that was displayed immediately
-prior to the current display.</dd>
-
-<dt>Forward</dt>
-
-<dd>Displays the page or the topic was displayed immediately after
-the current display.</dd>
-
-<dt>Collapse All</dt>
-
-<dd>Collapses the tree expansion state of all topics on the
-page.</dd>
-
-<dt>Show All Topics</dt>
-
-<dd>When filtering of workbench elements is enabled, the buttons
-enables displaying topics for disabled elements.</dd>
-
-<dt>Show Result Categories</dt>
-
-<dd>Switches between sorting search results by relevance and by
-logical containers for example books.</dd>
-
-<dt>Show Result Descriptions</dt>
-
-<dd>Displays short description of each search hit, when
-available.</dd>
-
-<dt>Menu</dt>
-
-<dd>Provides menu items that allow you switching help view
-pages.</dd>
-</dl>
-
-<h2>Icons</h2>
-
-<p>
-The following icons can appear in the various pages of the Help view.
-</p>
-
-<table border="1" cellspacing="0">
-<thead>
-<tr>
-<th rowspan="1" colspan="1">
-<p class="Para">Icon</p>
-</th>
-<th rowspan="1" colspan="1">
-<p class="Para">Description</p>
-</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_book_closed.png" alt="Open project icon" border="0"></td>
-<td rowspan="1" colspan="1" valign="top" align="left">Book
-(closed)</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_book_open.png" alt="Folder icon" border="0"></td>
-<td rowspan="1" colspan="1" valign="top" align="left">Book
-(open)</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_topic_container.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Topic (container)</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_topic.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Topic</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_search_local.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Search of local help</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_search_infocenter.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Search of remote
-info-center</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_search_web.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Search of web engine</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_highlight.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Highlight search terms</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_external.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Open link in a help
-window</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_bookmark_add.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Bookmark document</td>
-</tr>
-
-<tr>
-<td colspan="1" valign="top" align="left"><img src=
-"../images/help_icon_bookmark.png" alt="File icon" border="0"></td>
-<td colspan="1" valign="top" align="left">Bookmarked document</td>
-</tr>
-</tbody>
-</table>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="help.htm">Help</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/help.xhtml">Accessing help</a><br>
-<a href="../tasks/help_navigate.htm">Navigating help topics</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/help_preferences.htm">Help preferences</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/concepts/welcome.htm b/bundles/org.eclipse.platform.doc.user/concepts/welcome.htm
deleted file mode 100644
index 18eec86..0000000
--- a/bundles/org.eclipse.platform.doc.user/concepts/welcome.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Welcome</title>
-</head>
-<body>
-
-<h1>Welcome</h1>
-
-<p>
-The welcome page is the first page you see when you first launch eclipse. Its purpose
-is to introduce you to the product. Welcome content typically includes an overview
-the product and its features, tutorials to guide you through some basic tasks,
-samples to get you started, etc.
-</p>
-
-<p align="center">
-<img src="../images/welcome.png" alt="Welcome screenshot" width="508" height="384">
-</p>
-
-<p>
-There are many possible forms of welcome, ranging from simple static text to
-elaborate extendable multi-page presentations. The Eclipse platform and platform 
-SDK uses a form known as&nbsp; <strong>Universal Welcome</strong>, which
-defines a common page structure, allowing several products to share the welcome
-space. If your product is using the Universal Welcome, you can
-<a href="../tasks/welcome.htm">customize</a> its appearance using the "customize page" button. 
-Products which use universal welcome will display a welcome page the first time 
-they are restarted after new features with welcome content are installed and 
-highlight the new welcome content.</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/welcome.htm">Customizing welcome</a><br>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml b/bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml
deleted file mode 100644
index 82277b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_AntUI.xml
+++ /dev/null

@@ -1,189 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-  <context id="remove_all_action_context">
-    <description>This command removes all buildfiles from the Ant view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="search_for_buildfiles_action_context">
-    <description>This command searches for buildfiles and adds them to the Ant view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="edit_launch_configuration_action_context">
-    <description>This command opens a dialog to edit a launch configuration associated with the selected buildfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="run_target_action_context">
-    <description>This command executes the selected target or the default target of the selected buildfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="remove_project_action_context">
-    <description>This command removes the selected buildfiles from the Ant view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="refresh_buildfile_action_context">
- 	<description>This command refreshes the selected buildfiles in the Ant view. All buildfiles are refreshed if the Ant view has no selection.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="add_buildfile_action_context">
-    <description>This command prompts you to select a buildfile in the workspace to be added to the view.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="add_task_dialog_context">
-    <description>This dialog allows you to define an Ant task for Ant builds. You must set the name, location and classfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="edit_task_dialog_context">
-    <description>This dialog allows you to edit an exisitng Ant task defined for Ant builds.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="add_type_dialog_context">
-    <description>This dialog allows you to define an Ant type for Ant builds. You must set the name, location and classfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="edit_type_dialog_context">
-    <description>This dialog allows you to edit an existing Ant type defined for Ant builds.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="add_property_dialog_context">
-    <description>This dialog allows you to define an Ant property used in an Ant build.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="edit_property_dialog_context">
-    <description>This dialog allows you to edit an existing Ant property.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="search_for_buildfiles_dialog_context">
-    <description>This dialog allows you to search for buildfiles within the workspace.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="target_order_dialog_context">
-    <description>This dialog allows you to specify the order in which the selected Ant targets will be run. This ordering does not override the dependencies specified in your buildfile.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_preference_page_context">
-    <description>On this page, you can configure Ant preferences.</description>
-   	<topic label="Preferences - Ant" href="reference/ref-antprefs.htm"/>    
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_runtime_preference_page_context">
-    <description>On this page, you can configure the runtime environment of Ant.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_editor_preference_page_context">
-    <description>On this page, you can configure Ant editor preferences.</description>
-    <topic label="Preferences - Ant Editor" href="reference/ref-anteditorprefs.htm"/>
-    <topic label="Ant Editor" href="reference/ref-anteditor.htm"/> 
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_types_page_context">
-    <description>On this page, you can add or edit custom Ant types, specified within a Java class file, to be used when running Ant buildfiles.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_classpath_page_context">
-    <description>On this page, you can configure the Ant runtime classpath.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_properties_page_context">
-    <description>On this page, you can configure the properties available to Ant.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_tasks_page_context">
-    <description>On this page, you can add or edit custom Ant tasks, specified within a Java class file, to be used when running Ant buildfiles.</description>
-    <topic label="Preferences - Ant Runtime" href="reference/ref-antruntimeprefs.htm"/>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_view_context">
-    <description>This view allows you to view your Ant buildfiles in one place and quickly execute a target or the default target of a buildfile.</description>
-    <topic label="Ant View" href="reference/ref-antview.htm"/>
-    <topic label="Ant Editor" href="reference/ref-anteditor.htm"/> 
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-  <context id="ant_editor_context">
-    <description>The Ant editor provides you with Ant buildfile specific text editing support.</description>
-    <topic label="Ant Editor" href="reference/ref-anteditor.htm"/> 
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_main_tab_context">
-    <description>This tab allows you to configure the buildfile location and other attributes of this launch configuration.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_targets_tab_context">
-    <description>This tab allows you to configure which targets will be executed by this launch configuration.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_properties_tab_context">
-    <description>This tab allows you to configure the properties that will be passed in to Ant when this launch configuration is executed.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="ant_classpath_tab_context">
-    <description>This tab allows you to configure the runtime classpath that will be used when this launch configuration is executed.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-  
-   <context id="ant_jre_tab_context">
-    <description>This tab allows you to configure the JRE used for the Ant build.  By default Ant runs in a separate Java virtual machine (JVM) from Eclipse. You can specify the build to occur in the same JRE as Eclipse.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_CommonNavigator.xml b/bundles/org.eclipse.platform.doc.user/contexts_CommonNavigator.xml
deleted file mode 100644
index 0304a71..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_CommonNavigator.xml
+++ /dev/null

@@ -1,18 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-
-<contexts>
- 
-  <!-- ===================== -->
-  <!-- Help                  -->
-  <!-- ===================== -->
-
-  <context id="common_navigator">
-    <description>The Project Explorer provides a hierarchical view of the artifacts in the Workbench.</description>
-    <topic label="Project Explorer" href="reference/ref-73.htm"/>
-    <topic label="Views" href="concepts/concepts-5.htm"/>
-  </context>
-    
-   
-  
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Compare.xml b/bundles/org.eclipse.platform.doc.user/contexts_Compare.xml
deleted file mode 100644
index 435941b..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Compare.xml
+++ /dev/null

@@ -1,99 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Compare plugin -->
-
-	<context id="compare_editor_context">
-		<description>Compare and merge files and folders in a Compare Editor.</description>
- 		<topic label="Compare editor" href="reference/ref-25.htm"/>
- 		<topic label="Comparing Resources" href="tasks/tasks-68.htm"/>
- 		<topic label="Understanding the comparison" href="tasks/tasks-68bg.htm"/>
- 		<topic label="Merging changes in the Compare editor" href="tasks/tasks-68dg.htm"/>
- 		<topic label="Three way comparisons" href="concepts/concepts-29.htm"/>
-	</context>
-
-	<context id="patch_input_wizard_page_context">
-		<description>This wizard helps you applying a patch to files and folders in your workspace. On the first page you can select the file or folders on which to apply the patch and whether the patch is loaded from an external file or from the clipboard.</description>
- 		<topic label="Working with patches" href="tasks/tasks-68c.htm"/>
-	</context>
-
-	<context id="patch_preview_wizard_page_context">
-		<description>On this page you can see how well the patch matches with your workspace. You can adjust some parameters to influence the matching.</description>
- 		<topic label="Working with patches" href="tasks/tasks-68c.htm"/>
-	</context>
-
-	<context id="compare_dialog_context">
-		<description>A dialog displaying the results of comparing files.</description>
- 		<topic label="Comparing Resources" href="tasks/tasks-68.htm"/>
- 		<topic label="Understanding the comparison" href="tasks/tasks-68bg.htm"/>
-	</context>
-	
-	<context id="add_from_history_dialog_context">
-		<description>A dialog that lets you restore deleted files from the local history.</description>
- 		<topic label="Restoring deleted resources from the local history" href="tasks/tasks-87b.htm"/>
- 		<topic label="Local history" href="concepts/concepts-17a.htm"/>
- 		<topic label="Working with local history" href="tasks/tasks-1f.htm"/>
- 		<topic label="Local history" href="reference/ref-6a.htm"/>
-	</context>
-	
-	<context id="compare_with_edition_dialog_context">
-		<description>A dialog that lets you compare files with entries from the local history.</description>
- 		<topic label="Comparing resources with the local history" href="tasks/tasks-70.htm"/>
- 		<topic label="Local history" href="concepts/concepts-17a.htm"/>
- 		<topic label="Working with local history" href="tasks/tasks-1f.htm"/>
- 		<topic label="Local history" href="reference/ref-6a.htm"/>
-	</context>
-	
-	<context id="replace_with_edition_dialog_context">
-		<description>A dialog that lets you replace files with entries from the local history.</description>
- 		<topic label="Replacing a resource with local history" href="tasks/tasks-87.htm"/>
- 		<topic label="Local history" href="concepts/concepts-17a.htm"/>
- 		<topic label="Working with local history" href="tasks/tasks-1f.htm"/>
- 		<topic label="Local history" href="reference/ref-6a.htm"/>
-	</context>
-	
-	
-		
-	<context id="text_merge_view_context">
-		<description>This editor provides support for comparing and merging text files.</description>
-	</context>
-		
-	<context id="image_compare_view_context">
-		<description>This view shows two images side-by-side.</description>
-	</context>
-
-	<context id="binary_compare_view_context">
-		<description>This view shows the first position where two files differ.</description>
-	</context>
-		
-
-	<context id="global_next_diff_action_context">
-		<description>Goto next difference globally.</description>
-	</context>
-	
-	<context id="global_previous_diff_action_context">
-		<description>Goto previous difference globally.</description>
-	</context>
-	
-	<context id="next_diff_action_context">
-		<description>Goto next difference.</description>
-	</context>
-	
-	<context id="previous_diff_action_context">
-		<description>Goto previous difference.</description>
-	</context>
-	
-	<context id="ignore_whitespace_action_context">
-		<description>Ignore whitespace.</description>
-	</context>
-
-	
-  	<context id="compare_preference_page_context" >
-		<description>This preference page is used to set preferences for the compare, merge, and patch functionality in the workbench.</description>
- 		<topic label="Setting preferences for comparing files" href="tasks/tasks-68b.htm"/>
- 		<topic label="Preferences - Compare/Patch" href="reference/ref-11.htm"/>
-   		<topic label="Comparing Resources" href="reference/ref-25.htm"/>
-	</context>
-
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml b/bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml
deleted file mode 100644
index e272963..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_ExternalTools.xml
+++ /dev/null

@@ -1,33 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-  <context id="file_selection_dialog_context">
-    <description>This dialog allows you to select a file in the workspace.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="preference_page_context">
-    <description>On this page, you can configure External Tool preferences.</description>
-   	<topic label="Preferences - External Tools" href="reference/ref-exttoolsprefs.htm"/>    
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="builder_property_page_context">
-    <description>On this page, you can configure the External Tool builders that are run when this project is built.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="builders_tab_context">
-    <description>This tab allows you to configure when this project builder will be executed.</description>
-    <topic label="Ant Support" href="concepts/concepts-antsupport.htm"/> 
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-
-  <context id="program_main_tab_context">
-    <description>This tab allows you to configure the program location and other attributes of this launch configuration.</description>
-    <topic label="External Tools" href="concepts/concepts-exttools.htm"/>
-  </context>
-</contexts>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_JSch.xml b/bundles/org.eclipse.platform.doc.user/contexts_JSch.xml
deleted file mode 100644
index 28665cd..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_JSch.xml
+++ /dev/null

@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-	
- 	<!-- ********************************** -->
- 	<!-- Preference Pages 					-->
- 	<!-- ********************************** -->
- 	
- 	<context id="ssh2_preference_page_context" >
-      <description>This page allows you to manage SSH2 related settings.</description>
-      <topic label="SSH2 Preferences" href="reference/ref-ssh2-preferences.htm"/>
-   	</context>
-   	
- 
-</contexts>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Net.xml b/bundles/org.eclipse.platform.doc.user/contexts_Net.xml
deleted file mode 100644
index 132073f..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Net.xml
+++ /dev/null

@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-	
- 	<!-- ********************************** -->
- 	<!-- Preference Pages 					-->
- 	<!-- ********************************** -->
- 	
- 	<context id="proxy_preference_page_context" >
-      <description>This page allows you to specify the proxy settings to be used when connecting to the network.</description>
-      <topic label="Network Connections Preferences" href="reference/ref-net-preferences.htm"/>
-   	</context>
-   	
- 
-</contexts>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_P2.xml b/bundles/org.eclipse.platform.doc.user/contexts_P2.xml
deleted file mode 100644
index 0db3091..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_P2.xml
+++ /dev/null

@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-    <!-- Dialogs -->
-    
-    <context id="installed_software_context">
-        <description>In this page, you can work with your installation.</description>
-        <topic label="Updating the installation" href="tasks/tasks-120.htm"/>   
-        <topic label="Uninstalling software" href="tasks/tasks-126.htm"/>
-     </context>
-    
-     <context id="revert_configuration_wizard_context">
-        <description>In this page, you can review your installation history and revert your installation to a previous state.</description>
-        <topic label="Reverting to a previous install configuration" href="tasks/tasks-123.htm"/>   
-    </context>
-
-    <context id="uinstall_wizard_context">
-        <description>In this wizard, you can uninstall items from your installation.</description>
-       <topic label="Uninstalling software" href="tasks/tasks-126.htm"/>
-    </context>
- 
-    <context id="update_wizard_context">
-        <description>In this wizard, you can update the selected items.</description>
-       <topic label="Updating software using the Available Updates wizard" href="tasks/tasks-125.htm"/>
-    </context>
-
-    <context id="add_repository_dialog_context">
-        <description>In this dialog, you can add new software sites in order to install or update items from that site.</description>
-       <topic label="Adding a new update site" href="tasks/tasks-127.htm"/>
-    </context>
-
-    <context id="repository_manipulation_dialog_context">
-        <description>This page allows you to add and remove software sites, or select the sites that should be consulted whenever you install new software or update your installation.</description>
-       <topic label="Working with the Available Software sites" href="tasks/tasks-128.htm"/>
-    </context>
-
-    <context id="install_wizard_context">
-        <description>In this wizard, you can install new software from one or more software sites.</description>
-         <topic label="Installing new software" href="tasks/tasks-124.htm"/>
-     </context>
-
-    <!-- Preference Pages -->
-    <context id="provisioning_preference_page_context">
-        <description>This page allows you to configure general install/update preferences.</description>
-       <topic label="Preferences - Install/Update" href="reference/ref-p2-installupdate.htm"/>
-    </context>
-
-    <context id="automatic_updates_preference_page_context">
-        <description>This page allows you to configure the preferences for automatic updates.</description>
-       <topic label="Preferences - Automatic Updates" href="reference/ref-p2-autoupdate.htm"/>
-    </context>
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Search.xml b/bundles/org.eclipse.platform.doc.user/contexts_Search.xml
deleted file mode 100644
index 81665ee..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Search.xml
+++ /dev/null

@@ -1,60 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-<!-- Search plugin -->
-   <context  id="search_dialog_context" >
-      <description>You can search the workbench for resources matching the indicated conditions.</description>
- 	<topic label="Text searching" href="tasks/tasks-84.htm"/>
- 	<topic label="File searching" href="tasks/tasks-84b.htm"/>
-   	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-   <context  id="text_search_page_context" >
-      <description>Type a file pattern and/or expression for which you want to search the workbench. You can use the indicated wildcards and/or search only the specific file types as needed.</description>
- 	<topic label="Text searching" href="tasks/tasks-84.htm"/>
- 	<topic label="File searching" href="tasks/tasks-84b.htm"/>
-   	<topic label="File search" href="reference/ref-45.htm"/>
-   	<topic label="Text search/replace with regular expressions" href="reference/ref-regex-find-replace.htm" />
-   </context>
-
-   <context  id="replace_dialog_context" >
-      <description>Replace matches in the search results view with a replacement string.</description>
-      <topic label="Replace with regular expressions" href="reference/ref-regex-find-replace.htm" />
-   </context>
- 
-   <context  id="search_view_context" >
-      <description>This view displays the results of recent searches.</description>
- 	<topic label="Search view" href="reference/ref-26.htm"/>
- 	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-   
-   <context  id="new_search_view_context" >
-      <description>This view displays the results of recent searches.</description>
- 	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-   <context  id="search_preference_page_context" >
-      <description>This page displays the search preferences.</description>
- 	<topic label="Search preferences" href="reference/ref-search.htm"/>
- 	<topic label="Search view" href="reference/ref-26.htm"/>
- 	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-   <context  id="open_search_dialog_action_context" >
-      <description>This command opens the search dialog.</description>
-   </context>
-
-   <context  id="file_search_action_context" >
-      <description>This command opens the file search dialog.</description>
- 	<topic label="Text searching" href="tasks/tasks-84.htm"/>
- 	<topic label="File searching" href="tasks/tasks-84b.htm"/>
-   	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-   <context  id="file_search_result_page">
-      <description>This view displays the results of a file searche.</description>
-   	<topic label="File search" href="reference/ref-45.htm"/>
-   </context>
-
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_SecureStorage.xml b/bundles/org.eclipse.platform.doc.user/contexts_SecureStorage.xml
deleted file mode 100644
index 5c22796..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_SecureStorage.xml
+++ /dev/null

@@ -1,20 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-	
- 	<context id="sec_storage_preferences_context" >
-      <description>This page allows you to change secure storage preferences.</description>
-      <topic label="Secure storage preference page" href="reference/ref-securestorage-prefs.htm"/>
-   	</context>
-   	
- 	<context id="challenge_response_dialog" >
-      <description>This dialog sets up recovery of the secure storage password.</description>
-      <topic label="Password recovery" href="reference/ref-securestorage-recovery.htm"/>
-   	</context>
-   	
- 	<context id="password_recovery_dialog" >
-      <description>This dialog attempts to recover secure storage password.</description>
-      <topic label="Password recovery" href="reference/ref-securestorage-recovery.htm"/>
-   	</context>
- 
-</contexts>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Team.xml b/bundles/org.eclipse.platform.doc.user/contexts_Team.xml
deleted file mode 100644
index 83cd4d4..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Team.xml
+++ /dev/null

@@ -1,178 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-
-	<!-- ********************************** -->
- 	<!-- Dialogs							-->
- 	<!-- ********************************** -->
- 	
- 	<context id="sync_view_preference_dialog_context">
-      <description>This dialog allows you set configure the active synchronization in the Synchronize View.</description>
-   	</context>
-   	
-   	<context id="configre_refresh_schedule_dialog_context">
-      <description>This dialog allows you to configure the active synchronization to be automatically refreshed at a specified interval.</description>
-   	</context>
-   	
-	<!-- ********************************** -->
- 	<!-- Wizard Pages 						-->
- 	<!-- ********************************** -->
- 	
- 	<context id="share_project_page_context">
-      <description>This page helps you select what type of target site you wish to connect the project to.</description>
-   	</context>
-   	
-   	<context id="import_project_set_page_context">
-      <description>This page helps you import a project set from a file on the file system. A project set is a lightweight description of a set of shared projects. It can be used to reconstruct a lineup of shared projects that you have in your workspace.</description>
-   	</context>
-	
-	<context id="export_project_set_page_context">
-      <description>This page helps you export a project set to a file which can be shared with other team members. A project set is a lightweight description of a set of shared projects. It can be used to reconstruct a lineup of shared projects that you have in your workspace.</description>
-   	</context>
-   	
-    <context id="sync_resource_selection_page_context">
-      <description>This page allows you to choose the resources that are to be synchronized.</description>
-   	</context>
-   	
-   	<context id="refresh_wizard_selection_page_context">
-      <description>This page allows you to choose the type of synchronization you want to create.</description>
-   	</context>
-	
-	
- 	<!-- ********************************** -->
- 	<!-- Preference Pages 					-->
- 	<!-- ********************************** -->
- 	
- 	<context id="ignore_preference_page_context" >
-      <description>You may wish to exclude certain resources from version control. Resources whose names match any enabled pattern will not be released. The wildcard characters '*' and '?' are permitted. Examples: '/*/a/*' matches all files and sub-folders in '/x/a/' and also in '/x/y/z/a/', '/?/a/*' matches all in '/x/a/', '/?/a/*.doc' matches all .doc files in '/x/a/' folder and its sub-folders. These settings will not affect resources already under version control.</description>
-      <topic label="Creating a global ignore pattern" href="tasks/tasks-100d1.htm"/>
-   	</context>
-   	
-   	<context id="model_preference_page_context" >
-      <description>This page allows you to manage which models are available in the Synchronize view.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-
- 	<context id="sync_preference_page_context" >
-      <description>This page allows you to configure various aspects of the Synchronize View.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-   	
-   	<context id="sync_startup_preference_page_context" >
-      <description>This page allows you to configure whether the Synchronize view is populated automatically when Eclipse starts.</description>
-   	</context>
-   	
-   	<context id="resource_model_preference_page_context" >
-      <description>This page allows you to configure how file system resources appear in the synchronize view.</description>
-   	</context>
-
- 	<context id="file_type_preference_page_context" >
-      <description>This page allows you to associate a file extension with its content type (ASCII or binary). These setting are used by repository providers, such as CVS</description>
-      <topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm"/>
-   	</context>
-   	   	  	
-   	<!-- ********************************** -->
- 	<!-- TargetMenuActions 					-->
- 	<!-- ********************************** -->
-	
-	<context id="target_get_action_context">
-   		<description>Downloads the selected resources from the site into your workspace.</description>
-   	</context>
-
- 	<context id="target_put_action_context">
-   		<description>Uploads the selected resources from your workspace to the site.</description>
-   	</context>
-   	
-   	<context id="target_synchronize_action_context">
-   		<description>Show any differences between the local and remote site state of the selected resources in the Synchronize view.</description>
-   	</context>
-   	
-   	<context id="target_getas_action_context">
-   		<description>Downloads the selected resources from the site into your workspace. You may specify the local name of the resources.</description>
-   	</context>
-   	
-   	<context id="target_getasproject_action_context">
-   		<description>Downloads the selected resources from the site into your workspace. A project is created in the workspace for each of the selected items.</description>
-   	</context>
-   	
-   	<context id="target_disconnect_action_context">
-   		<description>Discards the selected target sites from the list of remembered sites.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- TargetCatchupReleaseViewer			-->
- 	<!-- ********************************** -->
-	
-	<context id="target_catchup_release_viewer_context">
-   		<description>This view shows incoming, outgoing and conflicting changes.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- TargetActions						-->
- 	<!-- ********************************** -->
-   	
-   	<context id="sync_get_action_context">
-   		<description>Downloads the selected resources from the site into your workspace.</description>
-   	</context>
-   	
-   	<context id="sync_put_action_context">
-   		<description>Uploads the selected resources from your workspace to the site.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- Views					            -->
- 	<!-- ********************************** -->
- 	
- 	<context id="site_explorer_view_context">
-      <description>The Site Explorer view allows you to browse of the contents of known target sites and download remote resources into the local workspace.</description>
-   	</context>
-
- 	<context id="sync_view_context">
-      <description>The Synchronize view allows the synchronization of the local contents of the workspace with a remote repository or target.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-   	
-    <context id="local_history_context">
-      <description>The Local History view allows users to view the local history of a file or an element contained in a file.</description>
-      <topic label="Local History" href="gettingStarted/qs-55.htm"/>
-      <topic label="Local History Preferences" href="reference/ref-14.htm"/>
-      <topic label="Working with Local History" href="tasks/tasks-1f.htm"/>
-   	</context>
-   	   	
-   	<!-- ********************************** -->
- 	<!-- SiteExplorerViewActions		    -->
- 	<!-- ********************************** -->
- 	
- 	<context id="add_site_action_context">
-      <description>Creates a new target site to which you can upload or download resources.</description>
-   	</context>
-   	
-   	<context id="new_folder_action_context">
-      <description>Creates a new folder on the target site.</description>
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- SyncViewActions				    -->
- 	<!-- ********************************** -->
- 	
- 	<context id="refresh_action_context">
-      <description>Refreshes the contents of the view.</description>
-   	</context>
-
-   	<context id="open_action_context">
-      <description>Show the comparison of the local and remote contents of the file in the comparison viewer.</description>
-   	</context>
-   	 	
-   	<context id="expandall_action_context">
-      <description>Fully expands all selected items.</description>
-   	</context>
-   	
-   	<context  id="remove_action_context">
-      <description>Removes the selected items from the Synchronize view.</description>
-   	</context>
-   	
-   	<context  id="navigator_show_action_context">
-      <description>Selects and reveals the selected items in the Navigator view.</description>
-   	</context>
- 
-</contexts>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml b/bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml
deleted file mode 100644
index a2c8785..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Team_CVS.xml
+++ /dev/null

@@ -1,732 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-   
-	<!-- ********************************** -->
- 	<!-- TagSelectionDialog 				-->
- 	<!-- ********************************** -->
-	
-	<context id="replace_tag_selection_dialog_context">
-   		<description>You have chosen to replace the selected resources with a branch or version tag. This dialog allows you to select the tag to use for this operation. The selected resources will be replaced with those tagged with the selected tag. If the desired tag does not appear in the list of Versions or Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository. Disabling the "Recurse into sub-folders" option will restrict the operation to selected folders and their direct children and selected files only.</description>
-   		<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-   	</context>
-   	
-   	<context id="compare_tag_selection_dialog_context">
-   		<description>You have chosen to compare the selected resources with a branch or version tag. This dialog allows you to select the tag to use for this operation. The selected resources will be compared with those tagged with the selected tag. If the desired tag does not appear in the list of Versions or Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository.</description>
-        <topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm" />
-   	</context>
-   	
-   	<context id="tag_remote_with_existing_dialog_context">
-   		<description>You have chosen to tag the selected resources with an existing branch or version tag. This dialog allows you to select the tag to use for this operation. If the tag already exists on another revision of any of the selected resources, it will be moved to the revision in the selection. If the desired tag does not appear in the list of Versions or Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository. Disabling the "Recurse into sub-folders" option will restrict the operation to selected folders and their direct children and selected files only.</description>
-        <topic label="Moving version tags" href="tasks/tasks-105c.htm" />
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- TagAsVersionDialog 				-->
- 	<!-- ********************************** -->
- 	
- 	<context id="tag_as_version_dialog_context">
-   		<description>This dialog allows you to create a version. Enter the version name to be used to tag to the selected resources.</description>
-   		<topic label="Creating a version of a project" href="tasks/tasks-100.htm" />
-   	</context>
-   	
-   	<context id="tag_outgoing_changes_dialog_context">
-   		<description>Local changes within your workspace will not be tagged. This dialog allows you to see what resources have been modified locally.</description>
-   		<topic label="Creating a version of a project" href="tasks/tasks-100.htm" />
-   	</context>
-   	
-   	<!-- ********************************** -->
- 	<!-- WizardPages 						-->
- 	<!-- ********************************** -->
- 	
- 	<context id="sharing_autoconnect_page_context">
-   		<description>The local project has CVS information associated with it but is not registered as a CVS project. This page shows the CVS information associated with the local project. Clicking "Finish" will register this project as a CVS project and enable the use of CVS menu commands. If "Validate Connection on Finish" is enabled, a connection will be attempted to the server.</description>
-		<topic label="Project checked out with another CVS tool" href="tasks/tasks-117a.htm" />
-   	</context>
-   	
-   	<context id="sharing_select_repository_page_context">
-   		<description>Either choose the repository you want from the list of existing repositories or indicate that a new repository location is to be created.</description>
- 		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-
- 	<context id="sharing_new_repository_page_context">
-   		<description>Enter the information that identifies the repository you would like to connect with and the user and connection information required to access this repository.</description>
-   		<topic label="New Repository Location Wizard" href="reference/ref-40.htm"/>
-		<topic label="CVS Repositories" href="concepts/concepts-27c.htm"/>
-		<topic label="Creating a CVS repository location" href="tasks/tasks-92.htm"/>
-	   	<topic label="Discarding a CVS repository location" href="tasks/tasks-94.htm"/>
-   	</context>
-
- 	<context id="sharing_module_page_context">
-   		<description>Specify the remote module with which the local project is shared. You can either choose to use the project name as the name that will be given to the remote module, to specify a custom module path or to select an existing module. In the first two cases, the name is relative to the repository root directory and, if the remote module does not exist, it is created.</description>
-		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-
- 	<context id="sharing_tag_selection_page_context">
-   		<description>The project being shared already exists remotely. This page allows the you to select the branch with which the project is to be shared. If the desired branch is not HEAD and does not appear in the list of Branches, perform a "Refresh from Repository" or a "Configure Tags" to automatically or manually find the tags that exist in the repository.</description>
-		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-   	
- 	<context id="sharing_sync_page_context">
-   		<description>Inspect the resources being shared and decide which resources should be shared and which should be ignored. Clicking "Finish" will provide an option to commit all outgoing changes.</description>
-		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-   	</context>
-
- 	<context id="patch_selection_page_context">
-   		<description>This wizard allows you to generate a patch of any local changes that can be reapplied at a later time. This page allows you to specify the location where you would like the patch to be saved.</description>
- 		<topic label="Working with patches" href="tasks/tasks-68c.htm" />
-   	</context>
-
- 	<context id="patch_options_page_context">
-   		<description>This wizard page allows you to customize the format of patch that will be generated.</description>
-   		<topic label="Working with patches" href="tasks/tasks-68c.htm" />
-   	</context>
-
- 	<context id="keyword_substitution_page_context">
-   		<description>This dialog lets you change the keyword substitution mode associated with one or more files.</description>
-		<topic label="Setting the CVS keyword substitution mode" href="tasks/tasks-cvs-11.htm" />
-   	</context>
-  
-   	<context id="merge_wizard_page_context">
-   		<description>This dialog allows you to merge the changes from another branch or version into the files in your local workspace.</description>
-		<topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-   		<topic label="Merge Wizard" href="reference/ref-41a.htm"/> 
-   	</context>
-   	
- 	<context id="merge_start_page_context">
-   		<description>Select a version of the project that will be the starting (base) point of the merge operation. If the tag is not available try refreshing from the repository or configuring tags.</description>
-		<topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-   		<topic label="Merge Wizard" href="reference/ref-41a.htm"/> 
-   	</context>
-   	
- 	<context id="merge_end_page_context">
-   		<description>Select either a version or branch that will act as the end point of the merge.</description>
-		<topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-   		<topic label="Merge Wizard" href="reference/ref-41a.htm"/> 
-   	</context>
-   	
-   	<context id="checkout_module_selection_context">
-   		<description>Specify one or more remote modules to be checked out. You can either type in the module path or choose one or more existing modules to be checked out. The existing modules are not fetched until the option to select an existing module is enabled.</description>
-		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="checkout_configuration_context">
-   		<description>Specify how the selected modules are to be checkout out. For a one or more selected modules, you have the option to check out as projects or as folders in an already existing project or folder. For a single selection that has no .project file in the remote module, you will also have the option of configuring the project using the New Project wizard.</description>
-		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="checkout_location_selection_context">
-   		<description>Specify the project location in the local file system. For a single project, the location is the location of the project directory. For multiple projects, the location is the location of the parent directory for the projects.</description>
-		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="checkout_tag_selection_page_context">
-   		<description>Specify the tag to be used for the modules being checked out.</description>
-   		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-   	</context>
-   	
-   	<context id="update_tag_selection_page_context">
-   		<description>This dialog allows you to select a branch or version tag and update the workspace to that tag while keeping any local changes.</description>
-   		<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-   	</context>
-   	
-   	<context id="checkout_into_resource_selection_page_context">
-   		<description>Select the parent folder under which the selected modules should be created. When checking out a single moduel, you can also specify the name of the folder to be created.</description>
-   		<topic label="Checking out a folder into an existing project" href="tasks/tasks-96b.htm"/> 
-   	</context>
-   	
-   	<context id="restore_from_repository_file_selection_page_context">
-   		<description>Browse files that have been deleted from the repository and check the revision of each file to be restored to the local workspace.</description>
-		<topic label="Restoring deleted files from the repository" href="tasks/tasks-105a.htm" />
-   	</context>
-   	
-   	<context id="working_set_folder_selection_page_context">
-        <description>Select the folders you wish to add to the working set as projects.</description>
-        <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm" />
-    </context>
-    
-    <context id="commit_comment_page_context">
-       <description>Enter a comment to describe the contents of this commit.</description>
-       <topic label="Committing" href="tasks/tasks-114.htm"/>
-    </context>
-    
-    <context id="commit_file_types_page_context">
-       <description>The type of the listed file names or extensions are not known. Assign a type to thee files so the contents can be properly committed to the repository.</description>
-       <topic label="Committing" href="tasks/tasks-114.htm"/>
-    </context>
-    
-   	<!-- ********************************** -->
- 	<!-- TeamMenuActions 					-->
- 	<!-- ********************************** -->
-	
-	<context  id="manage_action_context" >
-      <description>These commands allow you to perform version/configuration management operations.</description>
-	</context>
-  
-	<context id="team_synchronize_action_context">
-   		<description>Shows any differences between the local and remote state of the selected resources in the Synchronize view.</description>
-   		<topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm"/>
- 		<topic label="Synchronizing with the repository" href="tasks/tasks-115.htm"/>
-	 	<topic label="Updating" href="tasks/tasks-113.htm"/>
-	 	<topic label="Committing" href="tasks/tasks-114.htm"/>
-   	</context>
-   	
-   	<context id="team_synchronize_outgoing_action_context">
-  		<description>Shows any differences between the local and remote state of any selected resources that have outgoing changes in the Synchronize View.</description>
-		<topic label="Synchronizing with the repository" href="tasks/tasks-115.htm"/>
-	 	<topic label="Committing" href="tasks/tasks-114.htm"/>
-   	</context>
-
- 	<context id="team_commit_action_context">
-    		<description>Commits any outgoing changes in the selected resources to the server.</description>
-   		<topic label="Committing" href="tasks/tasks-114.htm"/>
-   	</context>
-
- 	<context id="team_update_action_context">
-   		<description>Updates the selected resources with any remote changes.</description>
-   		<topic label="Updating" href="tasks/tasks-113.htm"/>
-   	</context>
-   	
-   	<context id="team_switch_action_context">
-   		<description>Switch the selected resources to another branch or version while keeping any local changes.</description>
-   		<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-   	</context>
-
- 	<context id="team_create_patch_action_context">
-   		<description>Creates a patch that, when applied to the same base as the local resources, will duplicate the selected resources.</description>
-   		<topic label="Working with patches" href="tasks/tasks-68c.htm"/>
-   	</context>
-
- 	<context id="team_tag_as_version_action_context">
-   		<description>Tags the selected resources in the repository with a provided version name.</description>
-   		<topic label="Creating a version of a project" href="tasks/tasks-100.htm"/>
-   		<topic label="Versioning projects in the repository" href="tasks/tasks-118.htm"/>
-   	</context>
-
- 	<context id="team_branch_action_context">
-   		<description>Creates a branch using the selected resources as the base and optionally updates the local resources to be on the new branch.</description>
-   		<topic label="CVS" href="reference/ref-47.htm"/>
- 		<topic label="Branching" href="tasks/tasks-100a.htm"/>
-   	</context>
-
- 	<context id="team_merge_action_context">
-   		<description>Merges the changes from one branch into another.</description>
-   		<topic label="CVS" href="reference/ref-47.htm"/>
-   	</context>
-
- 	<context id="team_set_keyword_mode_action_context">
-   		<description>Sets the keyword substitution mode of the selected resources.</description>
-   		<topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm"/>
-   	</context>
-
- 	<context id="team_disconnect_action_context">
-   		<description>Disconnects the project from CVS control and optionally deletes the CVS folders.</description>
-		<topic label="Discarding a CVS repository location" href="tasks/tasks-94.htm"/>
-   	</context>
-
- 	<context id="team_add_action_context">
-   		<description>Adds the selected resources to CVS control so they can be committed and shared.</description>
-   	</context>
-
- 	<context id="team_ignore_action_context">
-   		<description>Ignores the selected resources so that they will not be considered for version control.</description>
-   	</context>
-
-   	<context id="team_restore_from_repository_action_context">
-   		<description>Load the contents of files that have been deleted from the repository so they can be restored.</description>
-   	</context>
-   		
-   	<!-- ********************************** -->
- 	<!-- Other Menu Actions 				-->
- 	<!-- ********************************** -->
-	
-	<context id="compare_with_tag_action_context">
-   		<description>Compares the selected resources with the corresponding remote resources tagged with a user specified version or branch tag.</description>
-   		<topic label="Comparing resources" href="tasks/tasks-68.htm"/>
-	 	<topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm"/>
-   	</context>
-   	
-   	<context id="compare_with_latest_action_context">
-   		<description>Compares the selected resources with the corresponding remote resources with the same tag or on the same branch.</description>
-   	</context>
-
-   	<context id="compare_with_revision_action_context">
-   		<description>Compares the selected file with a user specified revision of the file.</description>
-   		<topic label="Comparing resources" href="tasks/tasks-68.htm"/>
-	 	<topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm"/>
-   	</context>
-   	
- 	<context id="replace_with_tag_action_context">
-   		<description>Replaces the selected resources with the corresponding remote resources tagged with a user specified version or branch tag.</description>
-	 	<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm"/>
-   	</context>
-   	
-   	 <context id="replace_with_latest_action_context">
-   		<description>Replaces the selected resources with the corresponding remote resources with the same tag or on the same branch.</description>
-   	</context>
-    
-   	<context id="replace_with_revision_action_context">
-   		<description>Replaces the selected file with a user specified revision of the file.</description>
-   		<topic label="Project Explorer View" href="reference/ref-27.htm"/>
-	 	<topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm"/>
-   	</context>
-   	
-   	<context id="checkout_into_action_context">
-   		<description>Checks out the selected folder into an existing project.</description>
-   		<topic label="Checking out a folder into an existing project" href="tasks/tasks-96b.htm"/>
-   	</context>
-   	
-   	<context id="checkout_as_action_context">
-   		<description>Checks out the selected folder into a user configured project. This new project can have a different name from the default one.</description>
-   	</context>
-   	
-   	<context id="checkout_as_project_action_context">
-   		<description>Checks out the selected folders into projects that corresponds to the name of each remote folder.</description>
-   		<topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm"/>
-   	</context>
-
-   	<context id="checkout_module_action_context">
-   		<description>Checks out the selected modules into the local workspace.</description>
-   	</context>
-   	   	
-   	<context id="open_remote_file_action_context">
-   		<description>Opens the contents of the selected remote file in an editor.</description>
-   	</context>
-
- 	<context id="show_in_history_action_context">
-   		<description>Displays the revision history of the selected local or remote file in the history view.</description>
-   		<topic label="Viewing a File's Revision History" href="tasks/tasks-119.htm"/>
-   	</context>
-
-    <context id="confirm_merge_action_context">
-   		<description>Marked the selected resources as merged. This will change the base of the local resource to match that of the conflicting incoming change so the changes in the local resource can be committed. Only do this after you have manually accepted any incoming changes that should be preserved.</description>
-   		<topic label="Updating" href="tasks/tasks-113.htm"/>
-   	</context>
-   	
-    <context id="select_new_action_context">
-   		<description>Select all resources that are new and have not yet been added to CVS control.</description>
-   	</context>
-   	
- 	<context id="compare_remote_resources_action_context">
-   		<description>Compares the two selected remote resources with each other.</description>
-   		<topic label="Comparing resources" href="tasks/tasks-68.htm"/>
-	 	<topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm"/>
-   	</context>
-   	
-   	<context id="compare_remote_with_tag_action_context">
-   		<description>Compares the selected resource with another branch or version of the same resource.</description>
-   	</context>
-   	
-   	<context id="copy_repository_name_action_context">
-   		<description>Copies the name of the selected repository location to the clipboard.</description>
-   	</context>
-   	
-   	<context id="remove_root_action_context">
-   		<description>Removes the selected repository locations from the Repositories View.</description>
-   	</context>
-   	
-   	<context id="add_to_branch_context">
-   		<description>Adds the selected project to the branch list in this view. This operation only adds the project to the branch in the view and does not affect the repository itself.</description>
-   	</context>
-   	
-   	<context id="move_remote_tag_action_context">
-   		<description>Tags the selected resources with an existing user specified tag, moving the tag if required.</description>
-   	</context>
-   	
-   	<context id="tag_remote_action_context">
-   		<description>Tags the selected resources with a user specified tag.</description>
-   	</context>
-
-   	<context id="show_comment_in_history_action_context">
-   		<description>Shows the complete multi-line comment of the selected entry in a separate text pane.</description>
-   		<topic label="CVS Resource History view " href="reference/ref-32a.htm"/>
-   	</context>
-   	
-   	<context id="show_tag_in_history_action_context">
-   		<description>Shows the complete list of tags for the selected entry in a separate list pane.</description>
-   		<topic label="CVS Resource History view " href="reference/ref-32a.htm"/>
-   	</context>
-   	
-   	<context id="tag_with_existing_action_context">
-   		<description>Tags the selected resources with an existing user specified tag, moving the tag if required.</description>
-   	</context>
-   	
-   	<context id="select_working_set_action_context">
-   		<description>This filter removes all root folders from the view whose name does not match a project in the selected working set.</description>
-   	</context>
-   	
-   	<context id="deselect_working_set_action_context">
-   		<description>This action removes the currently installed working set filter.</description>
-   	</context>
-   	
-    <context id="edit_working_set_action_context">
-   		<description>This action edits the currently installed working set filter.</description>
-   	</context>
-   	
- 	<!-- ********************************** -->
- 	<!-- TagConfiguration 					-->
- 	<!-- ********************************** -->
-	
-	<context id="refresh_tags_action_context">
-   		<description>Refresh the branch and version tags displayed in this view by contacting the server</description>
-   		<topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   	
-	<context id="refresh_remote_project_selection_page_context">
-   		<description>Refresh the branch and version tags for the checked folders by contacting the server</description>
-   		<topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   	
-	<context  id="tag_configuration_overview" >
-   		<description>Configure the branch and version tags that are shown in the workbench. By browsing remote CVS files for tags you can selectively choose, from the list of tags on each file, which tags should be remembered and which should not. You can also select the files that will be automatically examined for tags.</description>
-   		<topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   
-    <context  id="tag_configuration_refreshlist" >
-      <description>This lists the files that are automatically examined for tags. By default, the .project file	is examined. But in some cases other files may have a more complete tag history and should be examined instead.</description>
-      <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-   
-   	<context  id="tag_configuration_refreshaction" >
-      <description>This will fetch branch and version tags from the files that have been configured to be automatically searched for tags. If tags that you expected to see do not appear, try changing the list of files to examined via the tag configuration dialog.</description>
-      <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm"/>
-   	</context>
-
- 	<!-- ********************************** -->
- 	<!-- Watch/Edit							-->
- 	<!-- ********************************** -->
- 	
- 	<context  id="team_edit_action_context" >
-      <description>Notify the server that you wish to edit this file.</description>
-   	</context>
-   	
-   	<context  id="team_unedit_action_context" >
-      <description>Notify the server that you are no longer editing this file and revert the contents to that of the base revision from which it was derived.</description>
-   	</context>
-   	
-   	<context  id="team_show_editors_action_context" >
-      <description>Show all editors of the selected resource and any of its children in the CVS Editors view.</description>
-   	</context>
-   	
-   	<context  id="cvs_editors_view_context" >
-      <description>This view shows all registered editors of one or more files.</description>
-   	</context>
-   	
-   	<context  id="editors_dialog_context" >
-      <description>This dialog shows all registered editors of the file that you are requesting to edit.</description>
-   	</context>
-   	
-   	<context  id="watch_edit_preference_page_context" >
-      <description>This page supports the configuration of CVS watch/edit. Enabling the use of watch/edit will result in all files being checked out read-only from the server. Editing a file will make the file writtable and send an edit notification to the server.</description>
-   	</context>
-   	
- 	<!-- ********************************** -->
- 	<!-- Dialogs					        -->
- 	<!-- ********************************** -->
- 	
- 	<context id="release_comment_dialog_context">
-       <description>Enter a comment to describe the contents of this commit.</description>
-    </context>
-   	<context id="user_validation_dialog_context">
-      <description>In this dialog, enter the appropriate information to log in to the repository.</description> 
-    </context>
-    <context id="tag_local_as_version_dialog_context">
-      <description>Enter the name of the version tag to be applied to the revisions that exist locally.</description>
-    </context>
-    <context id="branch_dialog_context">
-		<description>This dialog lets you specify the name of the branch you want to create and optionally lets you start working in the branch by updating the tag of the local resources to be the newly created branch tag.</description>
-    </context>
-    <context id="add_to_cvsignore_context">
-    	<description>In this dialog choose how to add the selected resources to the .cvsignore files. For each resource to be ignored, a .cvsignore file will created in its parent directory containing the pattern specified in the dialog. This will not affect resources already under version control.</description>
-    </context>
-    <context id="add_to_version_control_dialog_context">
-    	<description>Select which new resources should be added to version control before the commit. Any resources listed in this dialog which are not added first will not be committed to the server.</description>
-    </context>
-    <context id="disconnect_action_context">
-    	<description>This dialog allows you to disconnect the project from CVS control. Keeping the CVS meta information allows the project to be easily re-shared or used with other CVS tools.</description>
-    </context>
-    <context id="history_filter_dialog_context">
-        <description>This dialog allows you to specify filters that reduce the number of entries displayed in the History View. </description>
-    </context>
-    <context id="date_tag_dialog_context">
-        <description>This dialog allows you to specify a date tag which can be used to retrieve the resources that were in the repository at that time.</description>
-    </context>
-    <context id="keyboard_interactive_dialog_context">
-        <description>This dialog allows you to perform keyboard-interactive authentication for a CVS connection.</description>
-    </context>
-    <context id="replace_outgoing_changes_dialog_context">
-        <description>There are modified resources in the selection and these local changes will be overwritten by the replace operation and lost. This dialog allows you to decide whether to continue.</description>
-    </context>
-    <context id="tag_uncommmited_dialog_context">
-        <description>There are modified resources in the selection and these changes will not be included in the version created by the tag operation. This dialog allows you to decide whether to continue.</description>
-    </context>
-    <context id="commit_set_dialog_context">
-        <description>This dialog allows you to create or edit the name and comment for a CVS change set.</description>
-    </context>
-    <context id="alternative_repository_dialog_context">
-        <description>When the project set contains only partial repository information (not all locations are known) this dialog allows to choose a known repository location or create a new one or at last use a default.</description>
-        <topic href="tasks/tasks-cvs-project-set.htm" label="Using Project Sets"/>
-    </context>
-    <context id="repository_filter_dialog_context">
-        <description>Allows the turning on/off of filters that affect which entries are displayed in the CVS Repositories View.</description>
-    </context>
-    
- 	<!-- ********************************** -->
- 	<!-- Preference Pages 					-->
- 	<!-- ********************************** -->
- 	
- 	<context  id="prune_empty_directories_pref" >
-      <description>Enables pruning of empty directories on update and in the synchronization view. Although pruned directories aren't shown in the workbench there is actually still an empty directory in the repository.</description>
-   	</context>
-   	
-   	<context  id="quietness_level_pref" >
-      <description>Sets the amount of status information CVS prints for a command. In "Somewhat quiet" mode the printing of unimportant informational messages is suppressed. The consideration of what is important depends on each command. In "Very quiet" mode all output except what is absolutely necessary to complete the command is suppressed. In "Very Quiet" mode, some CVS servers may not communicate important information about errors that have occurred. You may want to consider using "Somewhat quiet" mode instead.</description>
-   	</context>
-   	
-  	<context  id="compression_level_pref" >
-      <description>Sets the compression level on communications with the server if it is supported by the server. Level 1 is minimal compression (slower communication but less CPU needed) and level 9 is maximum compression (faster communication but more CPU needed).</description>
-   	</context>
-
-	<context  id="default_keywordmode_pref" >
-      <description>Sets the default keyword substitution mode to use for ASCII files.</description>
-      <topic label="Setting the CVS keyword substitution mode" href="tasks/tasks-cvs-11.htm"/>
-   	</context>
-   	
-	<context  id="comms_timeout_pref" >
-      <description>Sets the amount of time in seconds to wait before timing out from a connection to the CVS server.</description>
-   	</context>
-   	
-   	<context  id="consider_content_pref" >
-      <description>Sets the default compare method for comparing and synchronizing CVS resources. By default timestamps are used to compare CVS files, and this is by far the fastest method. However, in some cases a more accurate comparison can be achieved by comparing file content. This setting can be toggled from within a compare editor or the synchronization view.</description>
-   	</context>
-   	
-	<context  id="replace_deletion_of_unmanaged_pref" >
-      <description>Allows resources not under CVS control to be deleted when replacing with resources from the repository.</description>
-   	</context>
-   	
-    <context  id="save_dirty_editors_pref" >
-      <description>Configures what happens when there are open editors with unsaved changes when a CVS operation is performed.</description>
-   	</context>
-   	
-   	<context  id="debug_protocol_pref" >
-      <description>Enabling this options will output the CVS communications trace to the console if eclipse was started with the -consolelog and -debug flags the java executable (as opposed to javaw).</description>
-   	</context>
-   	
-   	<context  id="treat_new_files_as_binary_pref" >
-      <description>Sets whether all new files are to be treated as binary. If disabled, the Team file content type preferences are used to determine the file type.</description>
-      <topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm"/>
-   	</context>
-   	
-   	<context  id="determine_server_version" >
-      <description>Sets whether the server version should be queried on the first connection to determine compatibility.</description>
-   	</context>
-
-   	<context  id="confirm_move_tag" >
-      <description>Sets whether you are prompted for confirmation when you perform a tag operation that requests an existing tag be moved.</description>
-   	</context>
-   	
-   	<context  id="line_end_pref" >
-      <description>Sets whether the line endings for text files should be translated to the platform line ending or left alone when files are downloaded from the server.</description>
-   	</context>
-   	
-   	<context  id="auto_refresh_tag" >
-      <description>Sets whether the tags are automatically refreshed from the repository when comparing or replacing tags from another branch or version.</description>
-   	</context>
-
-   	<context  id="change_perspective_on_show_annotations" >
-      <description>Configure how the target perspective is opened when showing annotations.</description>
-   	</context>
-   	
-   	<context  id="show_annotations_perspective" >
-      <description>Set the perspective to be opened when showing annotations.</description>
-   	</context>
-   	
-   <context  id="allow_empty_commit_comment" >
-      <description>When enabled, empty commit comments will be allowed without prompting. When disabled, you will be prompted to confirm the use of an empty commit comment.</description>
-   	</context>
-   	
-   	<context  id="console_preference_page_context" >
-      <description>This page supports the configuration of the CVS console. Properties that can be set are outpu colors and text font. The console can also be configured to open automatically when there is output.</description>
-   	</context>
-   	
-   	<context  id="comment_template_preference_page_context" >
-    <description>Use this page to add, remove or edit comment templates. Comment templates can be used to avoid having to type the same message for a commit.</description>
-   	</context>
-   	
-   	<context  id="update_merge_preference_page_context" >
-    <description>This page allows you to customize how CVS handles updates and merges.</description>
-   	</context>
-
-   	<context  id="ext_preference_page_context" >
-      <description>This page supports the configuration of the EXT connection parameters.</description>
-      <topic label="CVS" href="reference/ref-47.htm"/>
-   	</context>
-   	
-   	<context id="ext_preference_rsh_context">
-		<description>This program will be called to connect to the remote CVS server. The RSH command is invoked with following calling pattern: &lt;CVS_RSH&gt; &lt;Parameters&gt; &lt;CVS_SERVER&gt;</description> 
-	</context>
-	
-	<context id="ext_preference_param_context">
-		<description>The default parameter pattern is {host} -l {user}. It can be tailored using {host}, {user}, {password} and {port}.</description>
-	</context>
-	
-	<context id="ext_preference_server_context">
-		<description>This is the name of the remote CVS server program. Change this setting only if the remote CVS server name is different than the default</description>
-	</context>
-
-   	<context  id="decorators_preference_page_context" >
-      <description>This page supports the configuration of the CVS label and icons decorations.</description>
-      <topic label="CVS" href="reference/ref-19cvs.htm"></topic>
-      <topic label="Enabling the CVS resource decorations" href="tasks/tasks-107b.htm"/>
-   	</context>
-   	
-   	<context  id="password_management_preference_page_context" >
-      <description>This page allows you to view which repository locations have authentication information cached and allows you to purge this information.</description>
-		<topic label="CVS" href="reference/ref-19cvs.htm"></topic>
-   	</context>
-   	
-    <context  id="cvs_compare_preference_page_context" >
-      <description>This page allows you to configure various aspects of CVS synchronizations and comparisons.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-   	
-   	<context  id="general_preference_page_context" >
-      <description>This page allows you to configure various aspects of CVS.</description>
-   	</context>
-   	
-   	<context  id="ssh2_preference_page_context" >
-      <description>This page allows you to configure the extssh (SSH2) connection method.</description>
-   	</context>
-   	   	   	   	
-   	<!-- ********************************** -->
- 	<!-- Views					            -->
- 	<!-- ********************************** -->
- 	
- 	<context  id="console_view_context" >
-      <description>This view shows the output of CVS operations.</description>
-      <topic label="Team programming with CVS" href="concepts/concepts-26.htm"/>
-   	</context>
-   	<context  id="repositories_view_context" >
-      <description>This view allows the browsing of the contents of known CVS repositories and the checkout of modules into the local workspace as projects.</description>
-		<topic label="CVS Repositories View " href="reference/ref-32.htm"/>
-		<topic label="Refreshing the CVS Repositories view" href="tasks/tasks-93.htm"/>
-   	</context>
-   	<context  id="resource_history_view_context" >
-      <description>This view shows the revision history of a file under CVS control.</description>
-      <topic label="CVS Resource History view " href="reference/ref-32a.htm"/>
-      <topic label="Viewing a File's Revision History" href="tasks/tasks-119.htm"/>
-   	</context>
-   	<context  id="catchup_release_viewer_context" >
-      <description>This view shows the incoming, outgoing and conflicting changes.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-		<topic label="Synchronizing with the repository" href="tasks/tasks-115.htm"/>
-   	</context>
-   	<context  id="compare_revision_view_context" >
-      <description>This view allows the comparison of the local copy of a file with the revisions from the repository. Actions available for a revision are "Get Contents" and "Get Revision". Although both replace the local file with the contents of the remote revision, "Get Revision" will make the local file "sticky". This means that changes to the file cannot be committed back to the repository.</description>
-   	</context>
-    <context  id="annotate_view_context" >
-      <description>This view shows the user and revision annotations for a file in the CVS repository.</description>
-   	</context>
-   	<context id="cvs_sync_view_context">
-      <description>This view shows the differences between the local Workbench resources and their remote counterparts located in a CVS repository.</description>
-      <topic label="CVS Synchronize view" href="reference/ref-33.htm"/>
-   	</context>
-   	
-   	
-   	<!-- ********************************** -->
- 	<!-- Actions					        -->
- 	<!-- ********************************** -->
- 	
- 	<context  id="get_file_revision_action_context" >
-      <description>Loads the revision of the file into the workspace. The file will be "sticky" and you will be unable to commit changes to the repository.</description>
-   	</context>
- 	<context  id="get_file_contents_action_context" >
-      <description>Loads the contents of the file into the workspace. The base revision of the local file will not change and the file will become dirty. Perform this action if you wish to revert to the contents of an older revision of the file.</description>
-   	</context>
-   	<context  id="get_annotate_action_context" >
-      <description>Perform the CVS annotate command on the selected resource.  This command displays the resource with the contributor and revision noted for each line.</description>
-   	</context>
-   	<context  id="new_repository_location_action_context" >
-      <description>Creates a new CVS repository location and adds it to the CVS Repositories view.</description>
-      <topic label="Create a Repository Location" href="tasks/tasks-92.htm"/>
-   	</context>
-   	<context  id="new_dev_eclipse repository_location_action_context" >
-      <description>Creates a new CVS repository location for dev.eclipse.org and adds it to the CVS Repositories view.</description>
-      <topic label="Create a Repository Location" href="tasks/tasks-92.htm"/>
-   	</context>
-   	<context  id="show_remote_folders_action_context" >
-      <description>Toggles the CVS Repositories view to show folders.</description>
-      <topic label="CVS Repositories View " href="reference/ref-32.htm"/>
-   	</context>
-   	<context  id="show_remote_modules_action_context" >
-      <description>Toggles the CVS Repositories view to show modules defined in the CVSROOT/modules file.</description>
-      <topic label="CVS Repositories View " href="reference/ref-32.htm"/>
-   	</context>
-   		
-   	<!-- ********************************** -->
- 	<!-- Sync Actions					    -->
- 	<!-- ********************************** -->
- 	
-   	<context id="sync_commit_action_context" >
-      <description>Commits the selected outgoing changes to the CVS repository. Conflicting changes are not committed; to commit them you must use the "Override and Commit" action.</description>
-   	</context>
-   	
-   	<context id="sync_forced_commit_action_context">
-      <description>Commits the selected conflicting and incoming changes to the CVS repository. Non-conflicting outgoing changes are not committed; to commit them you must use the "Commit" action.</description>
-   	</context>
-	
-	<context id="sync_update_action_context">
-      <description>Gets the selected incoming changes from the CVS repository. Conflicting changes are not updated; to update them you must use the "Override and Update" action.</description>
-   	</context>
-	
-	<context id="sync_forced_update_action_context">
-      <description>Gets the selected conflicting and outgoing changes from the CVS repository. Non-conflicting incoming changes are not updated; to update them you must use the "Update" action. If some of the selected resources are auto-mergeable (i.e. they have no line-based conflicts) then you have the option of either performing an auto-merge or replacing with the remote content.</description>
-   	</context>
-	
-	<context id="sync_add_action_context">
-      <description>Adds the selected resources to CVS control.</description>
-   	</context>
-	
-	<context id="sync_ignore_action_context">
-      <description>Adds the selected resources to the appropriate .cvsignore file. These resources will no longer be considered for repository operations.</description>
-   	</context>
-	
-	<context id="merge_update_action_context">
-      <description>Gets the selected incoming changes from the CVS repository. Conflicting changes are not updated; to update them you must use the "Override and Update" action.</description>
-   	</context>
-	
-	<context id="merge_forced_update_action_context">
-      <description>Gets the selected conflicting changes from the CVS repository. Non-conflicting incoming changes are not updated; to update them you must use the "Update" action. If some of the selected resources are auto-mergeable (i.e. they have no line-based conflicts) then you have the option of either performing an auto-merge or replacing with the remote content.</description>
-   	</context>
-	
-	<context id="merge_update_with_joinaction_context">
-      <description>Gets the selected conflicting changes from the CVS repository. Non-conflicting incoming changes are not updated; to update them you must use the "Update" action. When performing a merge, it is difficult to detect if conflicts are auto-mergeable (i.e. they have no line-based conflicts). If you believe the file is auto-mergeable, you may use this action. You will then have the option of either performing an auto-merge or replacing with the remote content.</description>
-   	</context>
-
-   	<!-- ********************************** -->
- 	<!-- Properties pages				    -->
- 	<!-- ********************************** -->
- 	
-   	<context id="repository_location_property_page_context" >
-      <description>This page shows the properties of a repository location and allows the modification of the connection method, user name and password. If properties are changed on this page, they are changed for all projects shared with this location.</description>
-      <topic label="Changing the properties of a CVS Repository Location" href="tasks/tasks-95.htm"/>
-   	</context>
-   	
-   	<context id="repository_encoding_property_page_context" >
-      <description>This page allows you to set the file system encoding used by the server hosting the repository. Setting this properly will ensure that file names and commit messages are translated properly. This setting has no effect on file contents.</description>
-   	</context>
-
-   	<context id="project_property_page_context" >
-      <description>This page shows the CVS properties of the project. The project's CVS sharing information can be changed to another compatible repository location.</description>
-      <topic label="Changing the sharing of a Project" href="tasks/tasks-117b.htm"/>
-   	</context>
-   	
-   	<context id="folder_property_page_context" >
-      <description>This page shows the CVS properties of the folder.</description>
-   	</context>
-   	
-   	<context id="file_property_page_context" >
-      <description>This page shows the CVS properties of the file.</description>
-   	</context>
-   		
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Update.xml b/bundles/org.eclipse.platform.doc.user/contexts_Update.xml
deleted file mode 100644
index a1d2fbc..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Update.xml
+++ /dev/null

@@ -1,186 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-
-<contexts>
-   
-   <!-- Context IDs added in the  code, ID is class name, where context ID is set -->
-   
-   <context  id="ConfigurationView" >
-      <description>This dialog can be used to work with installed features. By default, it only shows the features that are currently enabled. On the dialog toolbar, turn on the "Show disabled features" filter so you can see the disabled features as well.</description>
-      <topic label="Inspecting the configuration" href="tasks/tasks-33.htm"/>
-      <topic label="Enabling, disabling, and uninstalling features" href="tasks/tasks-35.htm"/>
-   </context>
-     
-   <context  id="ReviewPage" >
-      <description>Results of the feature searches are shown on this page. Select features you want to install.</description>
-   </context>
-   
-   
-   <context  id="CofigurationView_showUnconfFeaturesAction" >
-      <description>Show disabled features.</description>
-   </context>
-   
-   <context  id="CofigurationView_revertAction" >
-      <description>Restore your configuration to match the selected history.</description>
-   </context>
-   
-   <context  id="CofigurationView_showStatusAction" >
-      <description>Show the current configuration status for the selected feature.</description>
-   </context>
-   
-   <context  id="CofigurationView_preserveAction" >
-      <description>Save the selected configuration in the <b>Saved Configurations</b> folder.</description>
-   </context>
-   
-   <context  id="CofigurationView_removePreservedAction" >
-      <description>Delete the selected configuration from the <b>Saved Configurations</b> folder.</description>
-   </context>
-   
-   <context  id="CofigurationView_unlinkAction" >
-      <description>Unlink the selected site from the configuration.</description>
-   </context>
-   
-   <context  id="CofigurationView_propertiesAction" >
-      <description>Display properties for the selection.</description>
-   </context>
-   
-   <context  id="UpdatesView_newAction" >
-      <description>Create a new site bookmark.</description>
-   </context>
-   
-   <context  id="UpdatesView_newFolderAction" >
-      <description>Create a new folder in the Feature Updates View. Folders can be used to organize site bookmarks and search queries.</description>
-   </context>
-   
-   <context  id="UpdatesView_newSearchAction" >
-      <description>Create a new search query.</description>
-   </context>
-   
-   <context  id="UpdatesView_newLocalAction" >
-      <description>Create a site bookmark for the selected local site.</description>
-   </context>
-   
-   <context  id="UpdatesView_deleteAction" >
-      <description>Delete the selected item.</description>
-   </context>
-   
-   <context  id="UpdatesView_refreshAction" >
-      <description>Refresh the selected item.</description>
-   </context>
-   
-   <context  id="UpdatesView_fileFilterAction" >
-      <description>Select to show individual files in <b>My Computer</b>. Deselect to show only local sites and directories.</description>
-   </context>
-   
-   <context  id="UpdatesView_filterEnvironmentAction" >
-      <description>Select to show only features matching current environment. Deselect to show all available features (features not matching current environment cannot be installed).</description>
-   </context>
-   
-   <context  id="UpdatesView_showCategoriesAction" >
-      <description>Select to see features organized into site categories. Deselect to see all features as a list.</description>
-   </context>
-   
-   <context  id="UpdatesView_linkExtensionAction" >
-      <description>Link the selected site into the configuration.</description>
-   </context>
-   
-   <context  id="DetailsView_homeAction" >
-      <description>Display the Update Manager Welcome page.</description>
-   </context>
-   
-   <context  id="DetailsView_backAction" >
-      <description>Go back to the previous details page.</description>
-   </context>
-   
-   <context  id="DetailsView_forwardAction" >
-      <description>Go forward to the next details page.</description>
-   </context>
-   
-   <context  id="MainPreferencePage" >
-      <description>Set Update Manager preferences - <b>number of histories</b> to maintain before deleting; scoping of <b>new updates</b> search to service updates only, or compatible minor release updates; <b>update policy</b> to alternate update sites; <b>proxy</b> settings</description>
-       <topic label="Preferences - Install/Update" href="reference/ref-21.htm"/>
-      <topic label="Controlling the Eclipse update policy"  href="tasks/tasks-37.htm"/>
-   </context>
-
-      
-   <context  id="LicensePage2" >
-      <description>You must view the presented license agreement(s) and either accept or reject.</description>
-   </context>
-   
-   <context  id="ModeSelectionPage" >
-      <description>Select whether you want to search for available updates to installed features, or to search for any features found on selected update sites</description>   
-      <topic label="Installing features with the update manager" href="tasks/tasks-34.htm"/>
-      <topic label="Updating features with the update manager" href="tasks/tasks-36.htm"/>   
-   </context>
-   
-   <context  id="SitePage" >
-      <description>Add, remove or edit an update site bookmark. 
-Select the site(s) to search for features and patches.
-
-<b>Remote site</b>: the url to a web site containing features
-<b>Local site</b>: a site that is on the current machine
-<b>Archive site</b>: a local site packaged as a ZIP or JAR file
-
-You can turn on or off searching for features that don't match the environment (OS, locale, etc.)
-	</description>
-   </context>
-   
-   <context  id="NewUpdatesWizardPage" >
-      <description>Select one or more of the available updates to install.</description>
-   </context>
-   
-   <context  id="MultiTargetPage2" >
-      <description>For each feature to be installed, select an installation location from the presented choices, or add a new one. Due to co-location constraints, you may not be able to define a new location for some features.</description>
-   </context>
-   
-   <context id="OptionalFeaturesPage">
-   	  <description>Choose which optional features that are included in the main feature will be installed.</description>
-   </context>
-   
-   <context id="MultiOptionalFeaturesPage2">
-   	  <description>Choose which optional features that are included in the main features will be installed.</description>
-   </context>
-   
-   <context  id="JarVerificationPage" >
-      <description>You must accept or reject the certificate of the JAR file</description>
-   </context>
-   
-   <context  id="UserValidationDialog" >
-      <description>Enter user information.</description>
-   </context>
-   
-   <context id="MultiReviewPage2">
-      <description>Select the features you want to install. If there are errors, press <b>Error Details</b> and try fixing them by selecting or unselecting the appropriate features.</description>
-     <topic label="Installing features with the update manager" href="tasks/tasks-34.htm"/>
-   </context>
-
-   
-   <context  id="InstallableSiteForm" >
-      <description>Displays details about local site that is part of the configuration.</description>          
-   </context>
-   
-   
-   <context  id="SiteForm" >
-      <description>Displays current installation configuration details.</description> 
-      <topic label="Inspecting the configuration" href="tasks/tasks-33.htm"/>
-      <topic label="Enabling, disabling, and uninstalling features" href="tasks/tasks-35.htm"/>       
-   </context>
-   
-   <context  id="UnknownObjectForm" >
-      <description>Displays when an unknown object or no object has been selected in the active part.</description>
-   </context>
-   
-   
-   <context id ="SiteBookmarkPropertyPage">
-      <description>Change properties of the bookmark object.</description>
-   </context>
-   
-   <context id ="NamedObjectPropertyPage">
-      <description>Change the name of the selected object.</description>
-   </context>
-   
-   <context id ="ConfigurationPropertyPage">
-      <description>Change the name of the selected configuration.</description>
-   </context>
-   
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_UserAssistance.xml b/bundles/org.eclipse.platform.doc.user/contexts_UserAssistance.xml
deleted file mode 100644
index 49c1461..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_UserAssistance.xml
+++ /dev/null

@@ -1,51 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-
-<contexts>
-
-  <!-- ===================== -->
-  <!-- Welcome               -->
-  <!-- ===================== -->
-
-  <context id="universalWelcomePreference">
-    <description>Use this dialog to configure Welcome appearance. Page tabs can be used to customize layout of each welcome page.</description>
-    <topic label="Welcome customization" href="/org.eclipse.platform.doc.user/reference/welcome_preferences.htm"/>
-  </context>
-
-  <!-- ===================== -->
-  <!-- Help                  -->
-  <!-- ===================== -->
-
-  <context id="f1Shell">
-    <description>Context-sensitive help is provided for many interfaces, including views, wizards, fields, buttons, and menu items. To access this help, bring focus to the item by clicking it or using the tab key, and then press F1 (Shift-F1 on Linux, Help on Mac). Some infopops include links to topics within the online help where you can find more information about the item. This infopop opened because you requested help while an infopop was already open.</description>
-  </context>
-  
-  <context id="prefPageHelp">
-    <description>Use this preference page to control <b>where</b> help is opened, as well as searching behavior.</description>
-    <topic label="Help preferences" href="/org.eclipse.platform.doc.user/reference/help_preferences.htm"/>
-  </context>
-
-  <context id="prefPageHelpContent">
-    <description>Use this preference page to configure help to download help content from a remote server (an infocenter).</description>
-	<topic label="Help Content preferences" href="/org.eclipse.platform.doc.user/reference/help_preferences_content.htm"/>
-	<topic label="Remote Help" href="/org.eclipse.platform.doc.isv/guide/ua_help_content_remote.htm"/>
-  </context>
-
-  <!-- ===================== -->
-  <!-- Cheat Sheets          -->
-  <!-- ===================== -->
-
-  <context id="cheatSheetSelection">
-    <description>This dialog is used to open a cheat sheet. A cheat sheet may be selected from the list or by browsing to a cheat sheet file.</description>
-    <topic label="Working with cheat sheets" href="/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm"/>
-  </context>
-  <context id="cheatSheetView">
-    <description>Cheat sheets are displayed in this view. A cheat sheet provides step by step guidance on how to complete a task.</description>
-    <topic label="Working with cheat sheets" href="/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm"/>
-  </context>
-   <context id="searchScope">
-      <description>Use this dialog to define search scopes which can be used to restrict the search to specific books.</description>
-      <topic href="tasks/help_search.htm" label="Searching Help"/>
-   </context>
-  
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml b/bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml
deleted file mode 100644
index 7de901b..0000000
--- a/bundles/org.eclipse.platform.doc.user/contexts_Workbench.xml
+++ /dev/null

@@ -1,1212 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.contexts"?>
-<contexts>
-    <!-- Actions -->
-    
-    <context id="missing">
-        <description>The context help for this user interface element could not be found.</description>
-    </context>
-    <context id="dock_on_perspective_action_context">
-        <description>This docks the perspective bar in different locations.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Perspective Bar" href="reference/ref-3.htm"/>
-    </context>
-    <context id="toggle_coolbar_action">
-        <description>This toggles the visibility of the window toolbar and perspective bar.</description>
-        <topic label="Perspective Bar" href="reference/ref-3.htm"/>
-        <topic label="Window Menu - Customize Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="show_text_perspective_action_context">
-        <description>This toggles whether text is shown for items on the perspective bar.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Perspective Bar" href="reference/ref-3.htm"/>
-    </context>
-    
-    <context id="add_bookmark_action_context">
-        <description><b>Bookmarks</b> place an &quot;anchor&quot; at a specific line in a workbench resource.</description>
-        <topic label="Adding a Bookmark" href="tasks/tasks-81.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="add_task_action_context">
-        <description><b>Tasks</b> place an &quot;anchor&quot; at a specific line in a workbench resource.</description>
-        <topic label="Adding a Task" href="tasks/tasks-77b.htm"/>
-        <topic label="Tasks View" href="concepts/ctskview.htm"/>
-    </context>
-    <context id="incremental_build_action_context">
-        <description>An <b>incremental build</b> compiles only the resources in the selected project that have been modified since the last build.</description>
-        <topic label="Project Explorer View - Rebuild All" href="reference/ref-27.htm"/>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="full_build_action_context">
-        <description>A <b>full build</b> compiles the resources in the selected project from scratch. This kind of build is only performed when a manual build is done.</description>
-        <topic label="Project Explorer View - Rebuild All" href="reference/ref-27.htm"/>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="global_incremental_build_action_context">
-        <description>An incremental build compiles only the resources that have been modified since the last build.</description>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="global_full_build_action_context">
-        <description>A <b>full build</b> compiles the entire workbench from scratch. This kind of build is only performed when a manual build is done.</description>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-        <topic label="Building Resources" href="tasks/tasks-73.htm"/>
-    </context>
-    <context id="close_resource_action_context">
-        <description>This closes the selected resource.</description>
-        <topic label="Closing Resources" href="tasks/tasks-47.htm"/>
-        <topic label="Project Explorer View - Close" href="reference/ref-27.htm"/>
-    </context>
-    <context id="open_resource_action_context">
-        <description>This opens the selected resource.</description>
-        <topic label="Opening Resources" href="tasks/tasks-46.htm"/>
-        <topic label="Project Explorer View - Open" href="reference/ref-27.htm"/>
-    </context>
-    <context id="open_file_action_context">
-        <description>This causes the selected resource to open in the editor area or in the specified external editor.</description>
-        <topic label="Project Explorer View - Open With..." href="reference/ref-27.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="open_local_file_action_context">
-        <description>This opens a file system dialog that allows to open the selected files in the corresponding editor.</description>
-    </context>
-    <context id="open_system_editor_action_context">
-        <description>This causes the selected resource to open in the default system editor for this file type.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-        <topic label="Editing a File Externally" href="tasks/tasks-52.htm"/>
-    </context>
-    <context id="refresh_action_context">
-        <description>This refreshes the contents and display of the view.</description>
-        <topic label="Project Explorer View - Refresh" href="reference/ref-27.htm"/>
-    </context>
-    <context id="move_resource_action_context">
-        <description>This command allows you to move a resource from one location to another.</description>
-        <topic label="Moving Resources" href="tasks/tasks-63.htm"/>
-        <topic label="Project Explorer View - Move" href="reference/ref-27.htm"/>
-    </context>
-    <context id="copy_resource_action_context">
-        <description>This command allows you to copy a resource from one location to another.</description>
-        <topic label="Project Explorer View - Copy" href="reference/ref-27.htm"/>
-    </context>
-    <context id="move_project_action_context">
-        <description>This command allows you to move a project from one location to another.</description>
-        <topic label="Moving Resources" href="tasks/tasks-63.htm"/>
-        <topic label="Project Explorer View - Move" href="reference/ref-27.htm"/>
-    </context>
-    <context id="copy_project_action_context">
-        <description>This command allows you to copy a project from one location to another.</description>
-        <topic label="Project Explorer View - Copy" href="reference/ref-27.htm"/>
-    </context>
-    <context id="rename_resource_action_context">
-        <description>This command allows you to supply a new name for the selected resource.</description>
-        <topic label="Renaming Resources" href="tasks/tasks-66.htm"/>
-        <topic label="Project Explorer View - Rename" href="reference/ref-27.htm"/>
-    </context>
-    <context id="delete_resource_action_context">
-        <description>This command allows you to delete the selected resource.</description>
-        <topic label="Deleting Resources" href="tasks/tasks-67.htm"/>
-        <topic label="Project Explorer View - Delete" href="reference/ref-27.htm"/>
-    </context>
-    <context id="delete_retarget_action_context">
-        <description>This command deletes the selected resource or element.</description>
-        <topic label="Deleting Resources" href="tasks/tasks-67.htm"/>
-        <topic label="Project Explorer View - Delete" href="reference/ref-27.htm"/>
-    </context>
-    <context id="property_dialog_action_context">
-        <description>This command displays the various properties of the selected resource.</description>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-        <topic label="Project Explorer View - Properties" href="reference/ref-27.htm"/>
-    </context>
-    <context id="project_property_dialog_action_context">
-        <description>This command displays the various properties of the project for the selected resource.</description>
-        <topic label="Project Menu - Properties" href="reference/ref-59.htm"/>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <context id="create_folder_action_context">
-        <description>This command allows you to create a new folder container.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Folders" href="tasks/tasks-43.htm"/>
-        <topic label="New Folder Wizard" href="reference/ref-38.htm"/>
-    </context>
-    <context id="create_file_action_context">
-        <description>This command allows you to create a new file.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Files" href="tasks/tasks-44.htm"/>
-        <topic label="New File Wizard" href="reference/ref-39.htm"/>
-    </context>
-    <context id="new_action_context">
-        <description>This command allows you to create a new item such as a resource.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Workbench New Wizards" href="reference/ref-37.htm"/>
-    </context>
-    <context id="import_action_context">
-        <description>This command allows you to import resources.</description>
-        <topic label="Importing" href="tasks/tasks-53.xhtml"/>
-        <topic label="Importing from a Directory" href="tasks/tasks-55.htm"/>
-        <topic label="Importing from a Zip File" href="tasks/tasks-55bg.htm"/>
-        <topic label="File Menu - Import" href="reference/ref-56.htm"/>
-    </context>
-    <context id="export_action_context">
-        <description>This command allows you to export resources.</description>
-        <topic label="Exporting" href="tasks/tasks-57.xhtml"/>
-        <topic label="Exporting to the File System" href="tasks/tasks-59.htm"/>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-        <topic label="File Menu - Export" href="reference/ref-56.htm"/>
-    </context>
-    <context id="scrub_local_action_context">
-        <description>The workbench is preparing for a build.</description>
-        <topic label="Builds" href="concepts/concepts-22.htm"/>
-    </context>
-    <context id="save_perspective_action_context">
-        <description>This menu option allows you to save the current perspective as a defined perspective.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Saving Perspectives" href="tasks/tasks-9i.htm"/>
-        <topic label="Window Menu - Save Perspective As" href="reference/ref-60.htm"/>
-    </context>
-    <context id="save_as_action_context">
-        <description>This command allows you to save the resource being edited to another workbench location.</description>
-        <topic label="File Menu - Save As" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="save_all_action_context">
-        <description>This command allows you to save all open resources in the editor area at once.</description>
-        <topic label="File Menu - Save All" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="save_action_context">
-        <description>This command saves the resource that is currently active in the editor area.</description>
-        <topic label="File Menu - Save" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="about_action_context">
-        <description>This command displays product information.</description>
-      	<topic label="About your installation" href="tasks/tasks-134.htm" />
-        <topic label="Help Menu - About" href="reference/ref-61.htm"/>
-      	<topic label="Installation Details" href="tasks/tasks-130.htm" />
-    </context>
-    <context id="close_all_action_context">
-        <description>This command closes all editors that are currently open in the editor area.</description>
-        <topic label="File Menu - Close All" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="close_page_action_context">
-        <description>This command closes the active perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Window Menu - Close Perspective" href="reference/ref-60.htm"/>
-        <topic label="Perspectives - Reference" href="reference/ref-6.htm"/>
-    </context>
-    <context id="close_part_action_context">
-        <description>This command closes the currently-active editor.</description>
-        <topic label="File Menu - Close" href="reference/ref-56.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="hide_menu_or_toolbar_items">
-        <description>This command allows you to show or hide menu items and toolbar buttons.</description>
-        <topic label="Configuring Perspectives" href="tasks/tasks-9n.htm"/>
-        <topic label="Window Menu - Customize Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="edit_action_sets_action_context">
-        <description>This command allows you to customize the command groups available in the workbench menu bar and toolbar.</description>
-        <topic label="Configuring Perspectives" href="tasks/tasks-9m.htm"/>
-        <topic label="Window Menu - Customize Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="customize_shortcuts">
-        <description>This command allows you to customize the shortcuts available in the New, Show Window and Show View menus.</description>
-        <topic label="Configuring Perspectives" href="tasks/tasks-9k.htm"/>
-        <topic label="Window Menu - Customize Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="edit_perspectives_action_context">
-        <description>This command allows you to delete or reset defined perspectives or to define the default perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Changing Where Perspectives Open" href="tasks/tasks-24.htm"/>
-        <topic label="Perspectives - Reference" href="reference/ref-6.htm"/>
-    </context>
-    <context id="close_all_pages_action_context">
-        <description>This closes all the perspectives that are currently open.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Window Menu - Close All Perspectives" href="reference/ref-60.htm"/>
-    </context>
-    <context id="open_preferences_action_context">
-        <description>This opens the preferences dialog.</description>
-        <topic label="Workbench - Preferences" href="reference/ref-10.htm"/>
-    </context>
-    <context id="open_new_window_action_context">
-        <description>This opens a new window.</description>
-        <topic label="Opening perspectives" href="tasks/tasks-9f.htm"/>
-        <topic label="Changing Where Perspectives Open" href="tasks/tasks-24.htm"/>
-        <topic label="Workbench" href="concepts/concepts-2.htm"/>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="quick_start_action_context">
-        <description>This will open the welcome editor.</description>
-        <topic label="Help Menu - Welcome" href="reference/ref-61.htm"/>
-    </context>
-    <context id="tips_and_tricks_action_context">
-        <description>This will open the tips and tricks help page.</description>
-        <topic label="Help Menu - Tips and Tricks" href="reference/ref-61.htm"/>
-    </context>
-    <context id="quit_action_context">
-        <description>This will save the workspace and exit.</description>
-        <topic label="File Menu - Exit" href="reference/ref-56.htm"/>
-    </context>
-    <context id="reset_perspective_action_context">
-        <description>This will reset the perspective to its original (default) layout.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Reset Perspectives" href="tasks/tasks-9j.htm"/>
-        <topic label="Window Menu - Reset Perspective" href="reference/ref-60.htm"/>
-    </context>    
-    <context id="target_editors_visibility_action_context">
-        <description>This allows you to hide or show the editor area.  You can increase the area other views have to display themselves when you hide the editor area.</description>
-        <topic label="Window Menu - Show/Hide Editors" href="reference/ref-60.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="show_view_action_context">
-        <description>This will show a view based on your selection.</description>
-        <topic label="Displaying Views" href="tasks/tasks-3.htm"/>
-        <topic label="Window Menu - Show View" href="reference/ref-60.htm"/>
-    </context>
-    <context id="show_view_other_action_context">
-        <description>Opens a dialog to select a view to show.</description>
-        <topic label="Displaying Views" href="tasks/tasks-3.htm"/>
-        <topic label="Window Menu - Show View" href="reference/ref-60.htm"/>
-    </context>
-    <context id="open_perspective_action_context">
-        <description>Opens the selected perspective.</description>
-        <topic label="Opening Perspectives" href="tasks/tasks-9f.htm"/>
-        <topic label="Window Menu - Open Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="remove_bookmark_action_context">
-        <description>Remove a bookmark.</description>
-        <topic label="Deleting a Bookmark" href="tasks/tasks-82.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="open_bookmark_action_context">
-        <description>Open resource in which a bookmark resides.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="select_all_bookmark_action_context">
-        <description>Select all bookmarks.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="filter_selection_action_context">
-        <description>This command allows filtering of the types shown in the resource navigator.</description>
-        <topic label="Project Explorer View - Filters" href="reference/ref-27.htm"/>
-    </context>
-    <context id="goto_resource_action_context">
-        <description>Go to the selected resource.</description>
-        <topic label="Project Explorer View - Go To" href="reference/ref-27.htm"/>
-    </context>
-    <context id="resource_navigator_move_action_context">
-        <description>Move the selected resource to another location.</description>
-        <topic label="Moving Resources" href="tasks/tasks-63.htm"/>
-        <topic label="Project Explorer View - Move" href="reference/ref-27.htm"/>
-    </context>
-    <context id="resource_navigator_rename_action_context">
-        <description>Rename the selected resource.</description>
-        <topic label="Renaming Resources" href="tasks/tasks-66.htm"/>
-        <topic label="Project Explorer View - Rename" href="reference/ref-27.htm"/>
-    </context>
-    <context id="show_in_navigator_action_context">
-        <description>Show the selected resource in the Project Explorer view.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Project Explorer View" href="reference/ref-27.htm"/>
-    </context>
-    <context id="properties_categories_action_context">
-        <description>Show property values grouped according to category.</description>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="properties_defaults_action_context">
-        <description>Sets the value of the selected property to its default value.</description>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="properties_filter_action_context">
-        <description>Filter properties.</description>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="purge_completed_task_action_context">
-        <description>Remove all completed tasks from the list.</description>
-        <topic label="Deleting Tasks" href="tasks/tasks-78.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="new_task_action_context">
-        <description>Create a new task.</description>
-        <topic label="Adding an Unassociated Task" href="tasks/tasks-77.htm"/>
-        <topic label="Adding an Associated Task" href="tasks/tasks-77b.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="remove_task_action_context">
-        <description>Remove a task from this list.</description>
-        <topic label="Deleting Tasks" href="tasks/tasks-78.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="goto_task_action_context">
-        <description>Opens the resource associated with a task.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="undo_action_context">
-        <description>Undo the previous edit.</description>
-        <topic label="Edit Menu - Undo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="redo_action_context">
-        <description>Redo the previous edit.</description>
-        <topic label="Edit Menu - Redo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cut_action_context">
-        <description>Cut the selected text to the clipboard.</description>
-        <topic label="Edit Menu - Cut" href="reference/ref-57.htm"/>
-    </context>
-    <context id="copy_action_context">
-        <description>Copy the selection to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="paste_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-    </context>
-    <context id="delete_action_context">
-        <description>Delete the selection.</description>
-        <topic label="Edit Menu - Delete" href="reference/ref-57.htm"/>
-    </context>
-    <context id="selectAll_action_context">
-        <description>Select all contents of the file.</description>
-        <topic label="Edit Menu - Select All" href="reference/ref-57.htm"/>
-    </context>
-    <context id="ShiftLeft_action_context">
-        <description>Shift selected text to the left, reducing the indentation.</description>
-    </context>
-    <context id="ShiftRight_action_context">
-        <description>Shift selected text to the right, increasing the indentation.</description>
-    </context>
-    <context id="find_action_context">
-        <description>This will bring up a dialog to specify text to search for in the editor.</description>
-        <topic label="Edit Menu - Find/Replace" href="reference/ref-57.htm"/>
-    </context>
-    <context id="bookmark_action_context">
-        <description>Add a bookmark on this resource.</description>
-        <topic label="Edit Menu - Add Bookmark" href="reference/ref-57.htm"/>
-    </context>
-    <context id="addTask_action_context">
-        <description>Add a task associated with this resource.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="revert_action_context">
-        <description>Revert to saved contents.</description>
-    </context>
-    <context id="GotoLine_action_context">
-        <description>Place cursor position at beginning of a specified line.</description>
-    </context>
-    <context id="open_workspace_file_action_context">
-        <description>Opens an editor on a specified resource.</description>
-        <topic label="Navigate Menu - Open Resource" href="reference/ref-58.htm"/>
-    </context>
-    <context id="print_action_context">
-        <description>This command prints the resource that is currently active in the editor area.</description>
-    </context>
-    <context id="select_working_set_action_context">
-        <description>Selects a working set from the list to be the active one.</description>
-    </context>
-    <context id="clear_working_set_action_context">
-        <description>Deselects the active working set.</description>
-    </context>
-    <context id="edit_working_set_action_context">
-        <description>Edits the contents of the active working set.</description>
-    </context>
-    <context id="show_in_action_context">
-        <description>Shows the current selection in the specified view.</description>
-    </context>
-    <context id="navigation_history_forward">
-        <description>Moves forward in the navigation history.</description>
-        <topic label="Navigate Menu - Forward" href="reference/ref-58.htm"/>
-    </context>
-    <context id="navigation_history_backward">
-        <description>Moves backward in the navigation history.</description>
-        <topic label="Navigate Menu - Back" href="reference/ref-58.htm"/>
-    </context>
-    <!-- Dialogs -->
-    <context id="about_dialog_context">
-        <description>This dialog displays product information.</description>
-     	<topic label="About your installation" href="tasks/tasks-134.htm" />
-       	<topic label="Installation Details" href="tasks/tasks-130.htm" />
-        <topic label="Help Menu - About" href="reference/ref-61.htm"/>
-    </context>
-    <context id="action_set_selection_dialog_context">
-        <description>This dialog allows you to customize the menu items and toolbar buttons which are visible in a perspective. You can change which wizards, views and perspectives are listed in submenus, change the availability of command groups, and tweak the visibility of menu items and toolbar buttons.</description>
-		<topic label="Showing and hiding menu items and toolbar buttons" href="tasks/tasks-9n.htm"/>
-		<topic label="Configuring perspective command groups" href="tasks/tasks-9m.htm"/>
-        <topic label="Configuring perspective shortcuts" href="tasks/tasks-9k.htm"/>
-        <topic label="Window Menu - Customize Perspective" href="reference/ref-60.htm"/>
-    </context>
-    <context id="editor_selection_dialog_context">
-        <description>In this dialog, you can associate various embedded and external editors with the various types of workbench resources.</description>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="file_extension_dialog_context">
-        <description>In this dialog, indicate the extension for the file type you wish to identify.</description>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="preference_dialog_context">
-        <description>This dialog allows you to set your workbench preferences.</description>
-        <topic label="Preferences Dialog" href="reference/ref-72.htm"/>
-    </context>
-    <context id="property_dialog_context">
-        <description>This dialog allows you to view or change the properties of the selected resource.</description>
-        <topic label="Project Explorer View - Properties Page" href="reference/ref-27.htm"/>
-        <topic label="Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <context id="save_perspective_dialog_context">
-        <description>This dialog allows you to save a perspective under a new name.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Saving Perspectives" href="tasks/tasks-9i.htm"/>
-    </context>
-    <context id="select_perspective_dialog_context">
-        <description>Dialog to select a perspective.</description>
-        <topic label="Perspectives - Concept" href="concepts/concepts-4.htm"/>
-        <topic label="Saving Perspectives" href="tasks/tasks-9i.htm"/>
-        <topic label="Window Menu" href="reference/ref-60.htm"/>
-    </context>
-    <context id="project_location_selection_dialog_context">
-        <description>Dialog to select the location of a project.</description>
-    </context>
-    <context id="show_view_dialog_context">
-        <description>Dialog to select a view to show.</description>
-        <topic label="Displaying Views" href="tasks/tasks-3.htm"/>
-    </context>
-    <context id="save_as_dialog_context">
-        <description>Dialog to specify the name and location of the a resource to save.</description>
-    </context>
-    <context id="type_filtering_dialog_context">
-        <description>Use this dialog to filter file types.</description>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-        <topic label="Import Wizard" href="reference/ref-70.htm"/>
-    </context>
-    <context id="container_selection_dialog_context">
-        <description>Dialog to select a folder.</description>
-    </context>
-    <context id="file_selection_dialog_context">
-        <description>Dialog to select a file.</description>
-    </context>
-    <context id="list_selection_dialog_context">
-        <description>Dialog to select an item from a list.</description>
-    </context>
-    <context id="yes_no_cancel_list_selection_dialog_context">
-        <description>Dialog to accept, reject, or cancel a selection from a list.</description>
-    </context>
-    <context id="resource_selection_dialog_context">
-        <description>Dialog to select a resource.</description>
-    </context>
-    <context id="goto_resource_dialog_context">
-        <description>Dialog to select a resource to find in the workspace.</description>
-    </context>
-    <context id="task_filters_dialog_context">
-        <description>Dialog that allows you to show or hide tasks based on certain criteria.</description>
-        <topic label="Filtering Your Task List" href="tasks/tasks-79.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="find_replace_dialog_context">
-        <description>Dialog to find and replace specified text.</description>
-		<topic label="Find/Replace with regular expressions" href="reference/ref-regex-find-replace.htm" />
-    </context>
-    <context id="switch_workspace_dialog_context">
-        <description>Dialog to switch workspaces.</description>
-		<topic label="Switching Workspaces" href="reference/ref-workspaceswitch.htm" />
-    </context>
-    <!-- Editors -->
-    <context id="welcome_editor_context">
-        <description>A quick, simple guide to introduce new users to some basic tasks.</description>
-        <topic label="Help Menu" href="reference/ref-61.htm"/>
-    </context>
-    <context id="text_editor_context">
-        <description>A text editor is used to edit files.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-        <topic label="Configuring accessibility options for textual editors" href="concepts/accessibility/text_editor.htm"/>
-    </context>
-    <context id="system_summary_dialog_context">
-        <description>Shows the product configuration details.</description>
-  	    <topic label="Installation Details for the Configuration" href="tasks/tasks-133.htm" />
-    </context>
-    <!-- Preference pages -->
-    <context id="file_editors_preference_page_context">
-        <description>On this preferences page, you can associate various embedded and external editors with the various types of workbench resources.</description>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="build_order_preference_page_context">
-        <description>Allows you to change the order that projects in the workspace are built.</description>
-        <topic label="Changing the Build Order" href="tasks/tasks-14.htm"/>
-    </context>
-    <context id="file_states_preference_page_context">
-        <description>This preference page is used to configure the local file history for the workbench.</description>
-        <topic label="Local History" href="concepts/concepts-17a.htm"/>
-        <topic label="Preferences - Local History" href="reference/ref-14.htm"/>
-        <topic label="Project Explorer - Local History" href="reference/ref-27.htm"/>
-    </context>
-    <context id="perspectives_preference_page_context">
-        <description>Allows you to set the state of existing perspectives.</description>
-        <topic label="Preferences - Perspectives" href="reference/ref-15.htm"/>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="views_preference_page_context">
-        <description>This preference page is used to set preferences for the look and layout of views in the workbench.</description>
-        <topic label="Preferences - Appearance" href="reference/ref-16.htm"/>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-    </context>
-    <context id="workspace_preference_page_context">
-        <description>This preference page is used to set the IDE-specific preferences settings related in workspace.</description>
-        <topic label="Preferences - Workspace" href="reference/ref-9.htm"/>
-    </context>    
-    <context id="workbench_preference_page_context">
-        <description>Allows you to set general workbench preferences.</description>
-        <topic label="Preferences - General" href="reference/ref-10.htm"/>
-    </context>
-    <context id="font_preference_page_context">
-        <description>This preference page is used to set the fonts used within the workbench.</description>
-        <topic label="Preferences - Colors and Fonts" href="reference/ref-fonts.htm"/>
-    </context>
-    <context id="keys_preference_page_context">
-        <description>This preference page is used to set the key bindings used within the workbench.</description>
-        <topic label="Preferences - Keys" href="concepts/accessibility/keyboardshortcuts.htm"/>
-    </context>
-    <context id="workbench_editor_preference_page_context">
-        <description>This preference page is used to set preferences for the editor area in the workbench.</description>
-        <topic label="Preferences - Editors" href="reference/ref-texteditorprefs.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-	<context id="capabilities_preference_page_context">
-		<description>This preference page is used to set preferences relating to workbench capabilities.</description>
-		<topic label="Preferences - Capabilities" href="reference/ref-capabilitiespref.htm"/>
-	</context>
-    <context id="content_types_preference_page_context">
-        <description>This preference page is used to set preferences relating to resource content types.</description>
-        <topic label="Preferences - Content Types" href="reference/ref-content-type.htm"/>
-        <topic label="Preferences - File Associations" href="reference/ref-13.htm"/> 
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <!-- Property pages -->
-    <context id="project_reference_property_page_context">
-        <description>Allows you to set referenced projects.</description>
-        <topic label="Project Explorer View - Properties Page" href="reference/ref-27.htm"/>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <context id="resource_info_property_page_context">
-        <description>Allows you to view information about the selected resource.</description>
-        <topic label="Project Explorer View - Properties Page" href="reference/ref-27.htm"/>
-        <topic label="Viewing Resource Properties" href="tasks/tasks-49.htm"/>
-    </context>
-    <!-- Views -->
-    <context id="bookmark_view_context">
-        <description>View to show all bookmarks.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Bookmarks View" href="reference/ref-28.htm"/>
-    </context>
-    <context id="content_outline_context">
-        <description>View to show the outline (if applicable) of a resource being edited.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Outline View" href="concepts/coutline.htm"/>
-    </context>
-    <context id="resource_view_context">
-        <description>This view shows all resources in the workspace.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-    </context>
-    <context id="property_sheet_view_context">
-        <description>This view shows the properties of a selected resource.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <context id="task_list_view_context">
-        <description>This view shows tasks (reminders) that are either user-created or are automatically generated during building.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="problem_view_context">
-        <description>This view shows problems that are generated during building.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Problems View" href="reference/ref-31a.htm"/>
-        <topic label="Quick Fix" href="tasks/tquickfix.htm"/>
-    </context>    
-    <!-- Property sheet -->
-    <context id="property_sheet_page_help_context">
-        <description>The Properties view displays the properties of the selected resource.</description>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-        <topic label="Properties View" href="concepts/cpropview.htm"/>
-    </context>
-    <!-- Windows -->
-    <context id="detached_window_context">
-        <description>Views can be undocked from a workbench window and can exist in floating windows on the desktop.</description>
-        <topic label="Docking Views" href="tasks/tasks-3e.htm"/>
-        <topic label="Workbench Window Layout" href="reference/ref-23.htm"/>
-        <topic label="Views" href="concepts/concepts-5.htm"/>
-    </context>
-    <context id="workbench_window_context">
-        <description>Each workbench window contains one or more perspectives, which are made up of various views and editors.</description>
-        <topic label="Workbench" href="concepts/concepts-2.htm"/>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-        <topic label="Customizing the Workbench" href="tasks/tasks-1.htm"/>
-    </context>
-    <!-- Wizard pages -->
-    <context id="new_project_wizard_page_context">
-        <description>This wizard helps you create a new project in the workbench.</description>
-        <topic label="New Project Wizard" href="reference/ref-37.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Projects" href="tasks/tasks-42.htm"/>
-    </context>
-    <context id="new_project_reference_wizard_page_context">
-        <description>This wizard page allows you to select other projects which this project will reference.</description>
-        <topic label="Select Referenced Projects Page" href="reference/ref-37.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <context id="new_folder_wizard_page_context">
-        <description>Wizard to guide you through creation of a new folder resource.</description>
-        <topic label="New Folder Wizard" href="reference/ref-38.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Folders" href="tasks/tasks-43.htm"/>
-    </context>
-    <context id="new_folder_dialog">
-        <description>This dialog allows to create a new folder in the file system.</description>
-    </context>
-    <context id="new_file_wizard_page_context">
-        <description>Wizard to guide you through creation of a new file resource.</description>
-        <topic label="New File Wizard" href="reference/ref-39.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Files" href="tasks/tasks-44.htm"/>
-    </context>
-    <context id="new_wizard_selection_wizard_page_context">
-        <description>Choose the type of resource you would like to create.</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <context id="export_wizard_selection_wizard_page_context">
-        <description>Choose the type of export you would like to do.</description>
-        <topic label="Using the Export Wizard" href="reference/ref-71.htm"/>
-        <topic label="Exporting resources" href="tasks/tasks-57.htm"/>
-        <topic label="Exporting to the File System" href="tasks/tasks-59.htm"/>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-    </context>
-    <context id="import_wizard_selection_wizard_page_context">
-        <description>Choose the type of import you would like to do.</description>
-        <topic label="Using the Import Wizard" href="reference/ref-70.htm"/>
-        <topic label="Importing resources with the Import Wizard" href="tasks/tasks-55.htm"/>
-    </context>
-    <context id="file_system_export_wizard_page">
-        <description>This page helps you provide all the information required to export resources to the file system.</description>
-        <topic label="Using the Export Wizard" href="tasks/tasks-59.htm"/>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-    </context>
-    <context id="file_system_import_wizard_page">
-        <description>This page helps you provide all the information required to import files from the file system.</description>
-        <topic label="Importing from File System" href="tasks/tasks-55.htm"/>
-        <topic label="Import Wizard" href="reference/ref-70.htm"/>
-    </context>
-    <context id="zip_file_export_wizard_page">
-        <description>This page helps you provide all the information required to export resources from the workspace to an archive file.</description>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-    </context>
-    <context id="zip_file_import_wizard_page">
-        <description>This page helps you provide all the information required to import files from an archive file into the workspace.</description>
-        <topic label="Importing from a Zip File" href="tasks/tasks-55bg.htm"/>
-        <topic label="Import Wizard" href="reference/ref-70.htm"/>
-    </context>
-    <!-- Wizards -->
-    <context id="new_wizard_context">
-        <description>These wizards allow you to create new resources and/or elements</description>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-    </context>
-    <context id="new_wizard_shortcut_context">
-        <description>Opens a creation wizard.</description>
-    </context>
-    <context id="new_file_wizard_context">
-        <description>Wizard to assist in creating a new file resource.</description>
-        <topic label="New File Wizard" href="reference/ref-39.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Files" href="tasks/tasks-44.htm"/>
-    </context>
-    <context id="new_folder_wizard_context">
-        <description>Wizard to assist in creating a new folder resource.</description>
-        <topic label="New Folder Wizard" href="reference/ref-38.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Folders" href="tasks/tasks-43.htm"/>
-    </context>
-    <context id="new_project_wizard_context">
-        <description>Wizard to assist in creating a new project.</description>
-        <topic label="New Project Wizard" href="reference/ref-37.htm"/>
-        <topic label="Resources" href="concepts/concepts-12.htm"/>
-        <topic label="Creating Resources - Projects" href="tasks/tasks-42.htm"/>
-    </context>
-    <context id="import_wizard_context">
-        <description>Wizard to assist in importing resources.</description>
-        <topic label="Using the Import Wizard" href="tasks/tasks-55.htm"/>
-    </context>
-    <context id="export_wizard_context">
-        <description>Wizard to assist in exporting resources.</description>
-        <topic label="Exporting files" href="tasks/tasks-57.htm"/>
-        <topic label="Exporting to the File System" href="tasks/tasks-59.htm"/>
-        <topic label="Exporting to a Zip File" href="tasks/tasks-59ag.htm"/>
-        <topic label="Export Wizard" href="reference/ref-71.htm"/>
-    </context>
-    <!-- terminal reference commented out in org.eclipse.ui.internal.WorkbenchActionBuilder, line 301 
-  <context id="close_all_saved_action_context">
-    <description></description>
-  </context>
-  -->
-    <context id="show_view_menu_action_context">
-        <description>Displays the menu for the active view.</description>
-    </context>
-    <context id="workbench_editors_action_context">
-        <description>Displays the Switch to Editors dialog.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="text_cut_action_context">
-        <description>Cut the selected text to the clipboard.</description>
-        <topic label="Edit Menu - Cut" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_copy_action_context">
-        <description>Copy the selection to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_paste_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_select_all_action_context">
-        <description>Select all contents.</description>
-        <topic label="Edit Menu - Select All" href="reference/ref-57.htm"/>
-    </context>
-    <context id="text_delete_action_context">
-        <description>Delete the selection.</description>
-        <topic label="Edit Menu - Delete" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_cut_action_context">
-        <description>Cut the selected text to the clipboard.</description>
-        <topic label="Edit Menu - Cut" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_copy_action_context">
-        <description>Copy the selection to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_paste_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_delete_action_context">
-        <description>Delete the selection.</description>
-        <topic label="Edit Menu - Delete" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_find_action_context">
-        <description>This will bring up a dialog to specify text to search for in the editor.</description>
-        <topic label="Edit Menu - Find/Replace" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_select_all_action_context">
-        <description>Select all contents.</description>
-        <topic label="Edit Menu - Select All" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_undo_action_context">
-        <description>Undo the previous edit.</description>
-        <topic label="Edit Menu - Undo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="cell_redo_action_context">
-        <description>Redo the previous edit.</description>
-        <topic label="Edit Menu - Redo" href="reference/ref-57.htm"/>
-    </context>
-    <context id="working_set_selection_dialog_context">
-        <description>This dialog allows you to add, remove, or configure working sets for use within the workbench.  A working set is a subset of the workspace.</description>
-    </context>
-    <context id="delete_project_dialog_context">
-        <description>This dialog asks you to confirm whether or not you wish to delete the selected project, and if so, whether you wish to also delete the underlying project files on the local file system corresponding to your project.</description>
-    </context>
-    <context id="marker_resolution_selection_dialog_context">
-        <description>This dialog allows you to select from a list of possible resolutions.</description>
-    </context>
-    <context id="workbench_editors_dialog">
-        <description>This dialog displays all open editors, allowing you to conveniently choose those you wish to close or save.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="welcome_page_selection_dialog">
-        <description>This dialog allows you to one of the set of available welcome pages. Welcome pages can help you get started using particular parts of the workbench.</description>
-    </context>
-    <context id="decorators_preference_page_context">
-        <description>This page allows you to specify which decorators you would like to be displayed on items within the workbench. Decorators give you more information about an item, at the expense of visual clutter.</description>
-        <topic label="Preferences - Label decorations" href="reference/ref-decorations.htm"/>
-    </context>
-    <context id="startup_preference_page_context">
-        <description>This page shows you all of the plug-ins that are activated when the workbench starts.</description>
-        <topic label="Preferences - Startup" href="reference/ref-startup.htm"/>
-    </context>
-    <context id="workspaces_preference_page_context">
-        <description>This page allows you to control the prompting to select a workspace when the workbench starts.</description>
-        <topic label="Preferences - Startup Workspaces" href="reference/ref-startup-workspaces.htm"/>
-    </context>
-    <context id="working_set_new_wizard_context">
-        <description>This wizard will guide you through the process of creating a working set.</description>
-    </context>
-    <context id="working_set_edit_wizard_context">
-        <description>This wizard will guide you through the process of editing a working set.</description>
-    </context>
-    <context id="filters_action_context">
-        <description>Displays a dialog to allow you to select filters to isolate specific elements of the workspace only.</description>
-    </context>
-    <context id="mark_completed_action_context">
-        <description>Marks the currently selected task as &apos;complete&apos;.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="resolve_marker_action_context">
-        <description>Displays a dialog to allow you to select from a list of possible resolutions.</description>
-    </context>
-    <context id="select_all_tasks_action_context">
-        <description>Selects all tasks in the task view.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_properties_action_context">
-        <description>Displays a dialog to allow you to set properties for the selected task.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="back_action_context">
-        <description>Move back one frame.</description>
-        <topic label="Project Explorer View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="forward_action_context">
-        <description>Move forward one frame.</description>
-        <topic label="Project Explorer View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="go_into_action_context">
-        <description>Drill down into selected element</description>
-        <topic label="Project Explorer View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="up_action_context">
-        <description>Move up one frame.</description>
-        <topic label="Project Explorer View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="lock_toolbar_action_context">
-        <description>Locks the toolbars within the workbench.</description>
-    </context>
-    <context id="about_plugins_dialog_context">
-        <description>This dialog shows details about all installed plug-ins.</description>
-     	<topic label="Installation Details for Plug-ins" href="tasks/tasks-131.htm" />
-  	</context>
-    <context id="about_features_plugins_dialog_context">
-        <description>This dialog shows details about all plug-ins within a particular feature.</description>
-        <topic label="Installation Details for Features" href="tasks/tasks-132.htm" />
-      	<topic label="Installation Details for Plug-ins" href="tasks/tasks-131.htm" />
-  	</context>
-    <context id="about_features_dialog_context">
-        <description>This dialog shows details about all installed features.</description>
-        <topic label="Installation Details for Features" href="tasks/tasks-132.htm" />
-  	 </context>
-    <context id="working_set_resource_page">
-        <description>This page allows you to choose the resources that will be part of your working set.</description>
-    </context>
-    <context id="working_set_type_page">
-        <description>This page allows you to select the type of working set you want to create.</description>
-    </context>
-    <context id="copy_bookmark_action_context">
-        <description>Copies the selected bookmark to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="paste_bookmark_action_context">
-        <description>Pastes the bookmark(s) on the clipboard.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_properties_action_context">
-        <description>Displays a dialog to allow you to set properties for the selected bookmark.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_ascending_action_context">
-        <description>Sorts bookmarks in ascending order.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_descending_action_context">
-        <description>Sorts bookmarks in descending order.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_description_action_context">
-        <description>Sorts bookmarks by description.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_resource_action_context">
-        <description>Sorts bookmarks by resource.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_folder_action_context">
-        <description>Sorts bookmarks by folder.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_location_action_context">
-        <description>Sorts bookmarks by location.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="bookmark_sort_creation_time_action_context">
-        <description>Sorts bookmarks by creation time.</description>
-        <topic label="Bookmarks" href="concepts/cbookmrk.htm"/>
-    </context>
-    <context id="resource_navigator_copy_action_context">
-        <description>Copies the selected resource to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-        <topic label="Project Explorer View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="resource_navigator_paste_action_context">
-        <description>Pastes the resource on the clipboard to the location of the currently selected resource.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-        <topic label="Project Explorer View" href="concepts/cnav.htm"/>
-    </context>
-    <context id="properties_copy_action_context">
-        <description>Copies the selected property to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-    </context>
-    <context id="copy_task_action_context">
-        <description>Copies the selected task to the clipboard.</description>
-        <topic label="Edit Menu - Copy" href="reference/ref-57.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="paste_task_action_context">
-        <description>Paste the contents of the clipboard at the current cursor position.</description>
-        <topic label="Edit Menu - Paste" href="reference/ref-57.htm"/>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_properties_dialog_context">
-        <description>This dialog allows you to set properties for the selected task.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_type_action_context">
-        <description>Sorts tasks by type.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_completed_action_context">
-        <description>Sorts tasks by completion.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_priority_action_context">
-        <description>Sorts tasks by priority.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_description_action_context">
-        <description>Sorts tasks by description.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_resource_action_context">
-        <description>Sorts tasks by resource.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_folder_action_context">
-        <description>Sorts tasks by folder.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_location_action_context">
-        <description>Sorts tasks by location.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_creation_time_action_context">
-        <description> Sorts tasks by creation time.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_ascending_action_context">
-        <description>Sorts tasks in ascending order.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="task_sort_descending_action_context">
-        <description>Sorts tasks in descending order.</description>
-        <topic label="Tasks View" href="reference/ref-31.htm"/>
-    </context>
-    <context id="show_part_pane_menu_action_context">
-        <description>Opens the system menu of the active view or editor.</description>
-    </context>
-    <context id="cycle_part_forward_action_context">
-        <description>Displays a menu which allows you navigate forward through the currently open views.</description>
-    </context>
-    <context id="cycle_part_backward_action_context">
-        <description>Displays a menu which allows you navigate backward through the currently open views.</description>
-    </context>
-    <context id="cycle_editor_forward_action_context">
-        <description>Displays a menu which allows you navigate forward through the currently open editors.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="cycle_editor_backward_action_context">
-        <description>Displays a menu which allows you navigate backward through the currently open editors.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="cycle_perspective_forward_action_context">
-        <description>Displays a menu which allows you navigate forward through the currently open perspectives.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="cycle_perspective_backward_action_context">
-        <description>Displays a menu which allows you navigate backward through the currently open perspectives.</description>
-        <topic label="Perspectives" href="concepts/concepts-4.htm"/>
-    </context>
-    <context id="activate_editor_action_context">
-        <description>Activates the editor pane.</description>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-
-    <!--new context ids-->
-    <context id="goto_last_edit_position_action_context">
-        <description>This command navigates back to the last edit location.</description>
-    </context>
-    
-    <context id="goto_next_annotation_action_context">
-        <description>Selects the next annotation in the resource that is currently active in the editor area.</description>
-    </context>
-
-    <context id="goto_previous_annotation_action_context">
-        <description>Selects the previous annotation in the resource that is currently active in the editor area.</description>
-    </context>
-    
-    <context id="ConvertLineDelimitersToMAC_action_context">
-        <description>This command converts the file to use classic MacOS line delimiters (CR).</description>
-    </context>
-    <context id="ConvertLineDelimitersToUNIX_action_context">
-        <description>This command converts the file to use Unix/MacOS X line delimiters (LF).</description>
-    </context>
-    <context id="ConvertLineDelimitersToWindows_action_context">
-        <description>This command converts the file to use Windows line delimiters (CRLF).</description>
-    </context>
-    <context id="FindIncrementalReverse_action_context">
-        <description>This command enters the incremental find previous mode or goes to the previous match if already in incremental mode. Esc quits the incremental find mode.</description>
-    </context>
-    <context id="DeleteLineToBeginning_action_context">
-        <description>This command deletes the text form the current caret position to the beginning of the line.</description>
-    </context>
-    <context id="DeleteLineToEnd_action_context">
-        <description>This command deletes the text from the current caret position to the end of the line.</description>
-    </context>
-    <context id="SetMark_action_context">
-        <description>This command sets a mark in the editor.</description>
-    </context>
-    <context id="FindNext_action_context">
-        <description>This command finds the next match in the editor.</description>
-    </context>
-    <context id="CutLine_action_context">
-        <description>This command cuts the whole line to the clipboard.</description>
-    </context>
-    <context id="DeleteLine_action_context">
-        <description>This command deletes the whole line.</description>
-    </context>
-    <context id="CutLineToEnd_action_context">
-        <description>This command cuts the text from the current caret position to the end of the line to the clipboard.</description>
-    </context>
-    <context id="JoinLines_action_context">
-        <description>This command joins the selected lines or appends the next line if the selection is empty.</description>
-    </context>
-    <context id="ClearMark_action_context">
-        <description>This command clears the previously set mark in the editor.</description>
-    </context>
-    <context id="SwapMark_action_context">
-        <description>Swaps the current curet position with the previously set mark.</description>
-    </context>
-    <context id="FindIncremental_action_context">
-        <description>This command enters the incremental find mode or goes to the next match if already in incremental mode. Esc quits the incremental find mode.</description>
-    </context>
-    <context id="FindPrevious_action_context">
-        <description>This command finds the previous match in the editor.</description>
-    </context>
-    <context id="CutLineToBeginning_action_context">
-        <description>This command cuts the text from the current caret position to the beginning of the line to the clipboard.</description>
-    </context>
-    <context id="US-ASCII_action_context">
-        <description>This command sets the encoding to US-ASCII.</description>
-    </context>
-    <context id="ISO-8859-1_action_context">
-        <description>This command sets the encoding to ISO-8859-1.</description>
-    </context>
-    <context id="UTF-8_action_context">
-        <description>This command sets the encoding to UTF-8.</description>
-    </context>
-    <context id="UTF-16BE_action_context">
-        <description>This command sets the encoding to UTF-16 (big-endian).</description>
-    </context>
-    <context id="UTF-16LE_action_context">
-        <description>This command sets the encoding to UTF-16 (little-endian).</description>
-    </context>
-    <context id="UTF-16_action_context">
-        <description>This command sets the encoding to UTF-16.</description>
-    </context>
-    <context id="System_action_context">
-        <description>This command sets the encoding to the current system encoding.</description>
-    </context>
-    <context id="Default_action_context">
-        <description>This command sets the encoding to the default encoding.</description>
-    </context>
-    <context id="Custom_action_context">
-        <description>This command allows to set a custom encoding.</description>
-    </context>
-    <context id="text_editor_preference_page_context">
-        <description>This preference page is used to set preferences for the text editor.</description>
-        <topic label="Preferences - Text Editor" href="reference/ref-texteditorprefs.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="accessibility_preference_page_context">
-        <description>On this page you can configure the text editor's accessibility preferences.</description>
-        <topic label="Accessibility preference page" href="reference/ref-7.htm"/>
-        <topic label="Configuring accessibility options for textual editors" href="concepts/accessibility/text_editor.htm"/>
-        <topic label="Accessibility in Eclipse" href="concepts/accessibility/accessmain.htm"/>
-        <topic label="Preferences - Text Editor" href="reference/ref-texteditorprefs.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="spelling_preference_page_context">
-        <description>On this page you can indicate your spelling preferences.
-
-<b>Hint</b>: If your preferred language is not available as <b>Platform dictionary</b> choose <b>none</b> and then search the internet for a word list with the words of your preferred language and set it as <b>User defined dictionary</b>. 
-</description>
-        <topic label="Preferences - Text Editor" href="reference/ref-texteditorprefs.htm"/>
-        <topic label="Editors" href="concepts/concepts-6.htm"/>
-    </context>
-    <context id="content_assist_action_context">
-        <description>This command opens content assist.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-    <context id="content_assist_context_information_action_context">
-        <description>This command shows content assist context information.</description>
-        <topic label="Edit actions" href="reference/ref-menu-edit.htm"/>
-    </context>
-    <context id="quick_assist_action_context">
-        <description>This command provides quick assists and quick fixes.</description>
-    </context>
-    <context id="show_information_action_context">
-        <description>This command displays information for the current caret location in a sticky hover.</description>
-    </context>
-    <context id="show_whitepsace_characters_action_context">
-        <description>This command allows to show whitespace characters in the editor.</description>
-    </context>
-    <context id="block_selection_mode_action_context">
-        <description>This command toggles the block (aka column) selection mode in the editor.</description>
-    </context>
-    <context id="templates_view_context">
-        <description>The Templates view shows the templates for the active editor.</description>
-        <topic label="Templates view" href="reference/ref-templates-view.htm"/>
-    </context>    
-    
-	 <context id="responsive_ui_context">
-        <description>This view displays the current state of background processes.</description>
-        <topic label="Responsive UI" href="gettingStarted/qs-responsiveUI.htm"/>
-    </context>
-     <context id="tips_and_tricks_page_selection_dialog">
-        <description>This dialog allows you to open a feature specific tips and tricks page.</description>
-        <topic label="Help Menu - Tips and Tricks" href="reference/ref-61.htm"/>
-    </context>
-	<!-- Help Menu: Help Contents -->
-    <context  id="help_contents_action_context" >
-        <description>This command displays the help view. The help view contains help books, topics, and information related to the workbench and installed components.</description>
-        <topic label="Help" href="/org.eclipse.platform.doc.user/concepts/help.htm"/>
-        <topic label="Help Menu - Help Contents" href="/org.eclipse.platform.doc.user/reference/ref-61.htm"/>
-    </context>
-    <context  id="help_search_action_context" >
-        <description>This command displays the help view opened on the search page.</description>
-        <topic label="Searching help" href="/org.eclipse.platform.doc.user/tasks/help_search.htm"/>
-        <topic label="Help Menu - Search" href="/org.eclipse.platform.doc.user/reference/ref-61.htm"/>
-    </context>
-   <!-- Browser support: Help Contents -->
-    <context id="browser_preference_page_context">
-        <description>This preference page is used to set preferences for launching Web browsers from the workbench.</description>
-        <topic label="Web Browser preferences" href="/org.eclipse.platform.doc.user/reference/ref-42.htm"/>
-    </context>
-    <context id="browser_preference_page_dialog_context">
-        <description>This dialog allows you to modify the properties of an externally launched browser.</description>
-    </context>
-    <context id="browser_context">
-        <description>This view allows you to display web pages. By default, it is used to display web pages when they are opened from the workbench. You can modify this setting in the Web Browser preferences available from the link below.</description>
-        <topic label="Web Browser preferences" href="/org.eclipse.platform.doc.user/reference/ref-42.htm"/>
-    </context>
-</contexts>

diff --git a/bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml b/bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml
deleted file mode 100644
index e708e32..0000000
--- a/bundles/org.eclipse.platform.doc.user/customBuildCallbacks.xml
+++ /dev/null

@@ -1,149 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- ===================================================================== -->
-<!-- Custom targets called from a project's generated build.xml            -->
-<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.-->
-<!-- ===================================================================== -->
-<project name="Build specific targets and properties" default="noDefault">
-
-	<!-- ===================================================================== -->
-	<!-- Default target                                                        -->
-	<!-- ===================================================================== -->
-	<target name="noDefault">
-		<echo message="This file must be called with explicit targets" />
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.jars                              -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.jars">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.jars                               -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.jars">
-		<antcall target="build.index"/>		
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target build.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="pre.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target build.sources                            -->
-	<!-- Available parameters :                                                -->
-	<!--   build.result.folder - folder to contain the build results           -->
-	<!-- ===================================================================== -->
-	<target name="post.build.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the compilation target <name>                      -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   source.foldern : n = 1 ... N, the source folders                    -->
-	<!--   target.folder  : where the results of the compilation go            -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="pre.name">
-	</target>
-
-	<target name="pre.@dot">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the compilation target <name>                       -->
-	<!-- Substitute "name" with the name of the compilation target, eg @dot    -->
-	<!-- Available parameters :                                                -->
-	<!--   jar.location - the location of the compilation results              -->
-	<!--   <name>.classpath : name = name of the compilation target. A         -->
-	<!--                      reference to the classpath structure.            -->
-	<!-- ===================================================================== -->
-	<target name="post.name">
-	</target>
-
-	<target name="post.@dot">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.bin.parts                        -->
-	<!-- Available parameters :                                                -->
-	<!--  destination.temp.folder - the directory plugins will be collected to -->
-	<!--  feature.directory - the directory containing the resulting feature   -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.bin.parts">
-	</target>
-	
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.bin.parts                         -->
-	<!-- Available parameters :                                                -->
-	<!--   base.dir - root of the project                                      -->
-	<!--   build.result.folder - folder containing the build results           -->
-	<!--   target.folder - destination folder                                  -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.bin.parts">
-	</target>
-
-	<target name="build.index" description="Builds search index for the plug-in: org.eclipse.platform.doc.user." if="eclipse.running">
-		<help.buildHelpIndex manifest="plugin.xml" destination="."/>
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.sources                          -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.sources                           -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.sources">
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target gather.logs                             -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.gather.logs">        
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target gather.logs                              -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="post.gather.logs">       
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do before the target clean                                   -->
-	<!-- Available parameters :                                                -->
-	<!--   destination.temp.folder - destination folder                        -->
-	<!-- ===================================================================== -->
-	<target name="pre.clean">              
-	</target>
-
-	<!-- ===================================================================== -->
-	<!-- Steps to do after the target clean                                    -->
-	<!-- Available parameters :                                                -->
-	<!--   plugin.destination - final destination of the build                 -->
-	<!--   build.result.folder - results of the compilation                    -->
-	<!--   temp.folder - temporary folder                                      -->
-	<!-- ===================================================================== -->
-	<target name="post.clean">             
-	</target>
-</project>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book b/bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book
deleted file mode 100644
index c3e7b15..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/gs_htmldoc_book.book
+++ /dev/null

@@ -1,99 +0,0 @@
-#HTMLDOC  1.8.23
--t pdf13 -f test.pdf --book --toclevels 3 --no-numbered --toctitle "Table of Contents" --no-title --linkstyle underline --size Universal --left 1.00in --right 0.50in --top 0.50in --bottom 0.50in --header .t. --footer h.1 --nup 1 --tocheader .t. --tocfooter ..i --portrait --color --no-pscommands --no-xrxcomments --compression=5 --jpeg=0 --fontsize 11.0 --fontspacing 1.2 --headingfont Helvetica --bodyfont Times --headfootsize 11.0 --headfootfont Helvetica --charset iso-8859-1 --links --no-embedfonts --pagemode outline --pagelayout single --firstpage p1 --pageeffect none --pageduration 10 --effectduration 1.0 --no-encryption --permissions all  --owner-password ""  --user-password "" --browserwidth 680
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02d.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-24a.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-24c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34a.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-62b_sync.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-62c_releasing.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync2.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync3_rel.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-86_use_cases.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-87_plugin_deploy.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-88_create_plugin.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-89_generate_buildxml.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-90_build_jar.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-91_build_options.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm
-../../../Program Files/Eclipse/eclipse/workspace/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm
deleted file mode 100644
index aad9075..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/intro/overview.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Eclipse platform overview</title>
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Eclipse platform overview</h1>
-
-<p>The Eclipse platform itself is structured as subsystems which are implemented 
-in one or more plug-ins.&nbsp; The subsystems are built on top of a small runtime 
-engine. The figure below depicts a simplified view. </p>
-<p align="center">
-<img alt="Platform runtime base with groups of plug-ins adding function" src="../../images/arch-npi.jpg" border="0">
-</p>
-<h2>Workbench</h2>
-<P>The term <i>Workbench</i> refers to the desktop development environment. 
-The Workbench aims to achieve seamless tool integration and controlled openness by providing a common paradigm for the creation, management, and navigation of workspace resources.</P>
-
-
-<P>
-Each Workbench window contains one or more
-perspectives.&nbsp; Perspectives contain views and editors and control
-what appears in certain menus and tool bars.&nbsp; More than one Workbench window can exist
-on the desktop at any given time.</P>
-<P>
-<img border="0" src="../../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../../concepts/concepts-25.htm">Features</a><br>
-<a href="../../concepts/concepts-12.htm">Resources</a><br>
-<a href="../../concepts/concepts-4.htm">Perspectives</a><br>
-<a href="../../concepts/concepts-5.htm">Views</a><br>
-<a href="../../concepts/concepts-6.htm">Editors</a><br>
-<a href="../../concepts/concepts-27c.htm">CVS Repositories</a>
-</P>
-<P>
-<img border="0" src="../../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../../tasks/tasks-124.htm">Installing new software</a><br>
-<a href="../../tasks/tasks-9f.htm">Opening perspectives</a><br>
-<a href="../../tasks/tasks-3.htm">Opening views</a><br>
-<a href="../../tasks/tasks-28.htm">Switching between perspectives</a><br>
-<a href="../../tasks/tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a><br>
-<a href="../../tasks/tasks-9m.htm">Configuring perspective command groups</a><br>
-<a href="../../tasks/tasks-9k.htm">Configuring perspective shortcuts</a><br>
-
-
-</P>
-<P>
-<img border="0" src="../../images/ngrelr.png" alt="Related reference"><br>
-<a href="javaScript:openRelatedLink('reference/ref-68.htm')">Toolbar buttons</a></P>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm
deleted file mode 100644
index 8f3d6e9..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-01.htm
+++ /dev/null

@@ -1,24 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Basic tutorial</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Basic tutorial</H1>
-<P>This tutorial provides a step by step walk-through of the
-Workbench.&nbsp;<br>
-</P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm
deleted file mode 100644
index fa3a166..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02a.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>The Workbench</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>
-The Workbench</h2>
-<P CLASS="Para"> When the Workbench is launched, the first thing you see is a 
-  dialog that allows you to select where the workspace should be located. The
-  workspace is the directory where your work will be stored. For now, just
-  click OK to pick the default location.</p>
-<p>After the workspace location is chosen, a single Workbench window is displayed. 
-  A Workbench window offers one or more perspectives. A perspective contains 
-  editors and views, such as the Project Explorer. Multiple Workbench windows can be 
-  opened simultaneously. Initially, in the first Workbench window that is opened,
-  the Java perspective is displayed, with only the Welcome view visible. 
-  Click the arrow labeled <b>Workbench</b> in the Welcome view to cause the other
-  views in the perspective to become visible. Note you can get the Welcome view back at any time by selecting
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.quickStartAction")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Welcome</b></a>.</p>
-<p>A shortcut bar appears in the top right corner of the window. This allows you
-  to open new perspectives and switch between ones already open. The name of the 
-  active perspective is shown in the title of the window and its item in the shortcut 
-  bar is highlighted.</p>
-<p>You should be seeing the Java perspective. We will switch to the simpler Resource perspective
-  to simplify this tutorial. Select 
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.ui.resourcePerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Open Perspective &gt; Other... &gt; Resource</b></a>.
-  The Project Explorer, Outline, and Tasks views should now be visible. <br>
-</p>
-<P CLASS="Para"><img src="../images/Image1.png" alt="Workbench" border="0"></P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm
deleted file mode 100644
index 05ef5b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02b.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editors and views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Editors and views</h2>
-<P CLASS="Intro">Prior to commencing the Workbench tutorials found in this section, 
-  it is important to first be familiar with the various elements of the Workbench. 
-  A Workbench consists of:</p> 
-<ul>
-  <li>
-    perspectives</li>
-  <li>
-    views</li>
-  <li>
-    editors</li>
-</ul>
-<p CLASS="Intro">A perspective is a group of views and editors in 
-the Workbench window. One or more perspectives can exist in a single Workbench 
-window. Each perspective contains one or more views and editors. Within a
-window, each perspective may have a different set of views but all perspectives
-share the same set of editors.</p>
-<p CLASS="Intro">A view is a visual component within the Workbench. It is typically 
-  used to navigate a list or hierarchy of information (such as the resources in the Workbench), 
-  or display properties for the active editor. Modifications made in a view are saved immediately.</p>
-<p CLASS="Intro">An editor is also a visual component within the Workbench. It is typically used to edit or browse a
-resource.  The visual presentation might be text or a diagram. 
-Typically, editors are launched by clicking on a resource in a view. 
-Modifications made in an editor follow an open-save-close lifecycle model.
-</p>
-<p CLASS="Intro">Some features are common to both views and editors. We use the 
-  term &quot;part&quot; to mean either a view or an editor. Parts can be active 
-  or inactive, but only one part can be active at any one time.&nbsp; The active 
-  part is the one whose title bar is highlighted. The active part is the target 
-  for common operations like cut, copy and paste. The active part also determines 
-  the contents of the status line. If an editor tab is not highlighted it indicates 
-  the editor is not active, however views may show information based on the last 
-  active editor.</p>
-<p CLASS="Intro">In the image below, the Project Explorer view is active. </p>
-<p CLASS="Intro"><img src="../images/Image2_active_view.png"  alt="Workbench" border="0"></p>
-<P CLASS="Intro">Clicking on the Outline view causes the Outline's title bar to 
-  become highlighted and the Project Explorer's title bar to no longer be highlighted, 
-  as shown below. The Outline view is now active. </p>
-<P CLASS="Intro"><img src="../images/Image2_active_editor.png"  alt="Welcome page selected" border="0">
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml
deleted file mode 100644
index 32e93f8..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02d.xhtml
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Editors</h3>
-<p class="Para"> Depending on the type of file that is being edited, the appropriate 
-  editor is displayed in the editor area. For example, if a .TXT file is being 
-  edited, a text editor is displayed in the editor area. The figure below shows 
-  an editor open on the file file1.txt. The name of the file appears in the tab 
-  of the editor. An asterisk (*) appearing at the left side of the tab indicates 
-  that the editor has unsaved changes. If an attempt is made to close the editor 
-  or exit the Workbench with unsaved changes, a prompt to save the editor's changes 
-  will appear.</p>
-<p><img src="../images/Image5_text_editor.png" alt="Eclipse Workbench, one editor" border="0" />
-</p>
-
-
-<p class="Para">When an editor is active, the Workbench menu bar and toolbar contain 
-  operations applicable to the editor. When a view becomes active, the editor 
-  operations are disabled. However, certain operations may be appropriate 
-  in the context of a view and will remain enabled.</p>
-
-
-<p class="Para"> The editors can be stacked in the editor area and individual 
-  editors can be activated by clicking the tab for the editor. Editors can also 
-  be tiled side-by-side in the editor area so their content can be viewed simultaneously. 
-  In the figure below, editors for JanesFile.txt and JanesFile2.txt have been placed 
-  above the editor for JanesText.txt. Instructions will be given later in this tutorial explaining 
-  how to rearrange views and editors.</p>
-<p><img src="../images/Image57_two_editors.png" alt="Eclipse Workbench, two editors" border="0" /> 
-</p>
-
-
-<p>If a resource does not have an associated editor, the Workbench 
-  will attempt to launch an external editor registered with the platform. These 
-  external editors are not tightly integrated with the Workbench and are not embedded 
-  in the Workbench's editor area. </p>
-<p>Editors can be cycled through using the back and forward arrow buttons 
-  in the toolbar. These move through the last mouse selection points and permit moving through several points 
-  in a file before moving to another one. Additionally, editors can be cycled by using 
-  the Ctrl+F6 accelerator (Command+F6 on the Macintosh).  Ctrl+F6 pops up a list of currently 
-  open editors. By default, the list will have selected the editor used before the current one, allowing
-  you to easely go back to the previous editor.
-  </p>
-<p filter="ws=win32"><img src="../images/win_only.png" alt="Windows only" border="0" />
-  On Windows, if the associated editor is an external editor, the Workbench may attempt
-  to launch the editor in-place as an 
-  OLE document editor. For example, editing a DOC file will cause Microsoft Word 
-  to be opened in-place within the Workbench if Microsoft Word is installed on 
-  the machine. If Microsoft Word has not been installed, Word Pad will open instead.</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm
deleted file mode 100644
index 8fe4522..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-02e.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Views</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h3>
-Views</h3>
-<P CLASS="Para">The primary use of Views is to provide navigation of the information
- in the Workbench. For example:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-The Bookmarks view displays all bookmarks in the Workbench along with the names
-of the files with which the bookmarks are associated.</LI>
-  <LI CLASS="Item"> The Project Explorer view displays the Workbench projects, their folders and files.</LI>
-</UL>
-<P CLASS="Para">
-A view might appear by itself or stacked with other views in a tabbed notebook.&nbsp;&nbsp;</P>
-<blockquote>
-  <blockquote>
-<P CLASS="Para" align="center">
-<img src="../images/Image3_single.png"  alt="Task View" border="0"></P>
-  </blockquote>
-</blockquote>
-<P CLASS="Para"> To activate a view that is part of a tabbed notebook simply click 
-  its tab.</P>
-<P CLASS="Para" align="center">
-<img src="../images/Image3_tabbed.png" alt="Two views with tabs, project explorer view active" border="0"></P>
-<P CLASS="Para">Views have two menus. The first, which is accessed by right clicking on the
-  view's tab, allows the view to be manipulated in much the 
-  same manner as the menu associated with the Workbench window.</P>
-<P CLASS="Para" align="center"><img src="../images/Image8_view.png" alt="Project Explorer view menu, top left" border="0"></P>
-<P CLASS="Para">The second menu, called the "view pull-down menu", is accessed by clicking the down arrow <img src="../images/Image9_viewdownarrow.png" alt="View down arrow" border="0" >. 
-  The view pull-down menu typically contains operations that apply to the entire 
-  contents of the view, but not to a specific item shown in the view. Operations 
-  for sorting and filtering are commonly found in the view pull-down.&nbsp;</P>
-<P CLASS="Para" align="center"><img src="../images/Image7_view_pulldown.png" alt="Project Explorer view menu, arrow pulldown" border="0"></P>
-<P CLASS="Para">&nbsp;</P>
-<P CLASS="Para"> A view can be displayed by selecting it from the <b>Window &gt; 
-  Show View</b> menu. A perspective determines which views may be required and 
-  displays these on the <b>Show View</b> sub-menu. Additional views are available 
-  by choosing
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Other...</b></a>
-  at the bottom of the <b>Show View</b> sub-menu. This 
-  is just one of the many features that provide for the creation of a custom work 
-  environment. </P>
-<P CLASS="Para" align="center">
-<img src="../images/Image4_showview.png" alt="Show View menu" border="0"></P>
-<P CLASS="Para">&nbsp;</P>
-<P CLASS="Para">Through the normal course of using the Workbench you will open, move, resize, and close views.
-  If you'd like to restore the perspective back to its original state, you can 
-  select the <b>Window &gt; Reset Perspective</b> menu operation.</P>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm
deleted file mode 100644
index 164676c..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07a.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>A simple project</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2> A simple project</h2>
-<P CLASS="Para"> Now that the basic elements of the Workbench have been explained, 
-  here are some instructions for creating a simple project. New projects, folders, 
-  and files can be created using several different approaches. In this section 
-  resources will be created using three different approaches:</P>
-<ol>
-  <li><b>File</b> menu</li>
-  <li>Project Explorer's view context menu</li>
-  <li>New Wizard button</li>
-</ol>
-<P>A project can be created using the <b>File</b> menu. Once the project has been 
-  created a folder and file can be created as well. </P>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm
deleted file mode 100644
index 2a0b186..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07b.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the File menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Using the File menu</h3>
-<P CLASS="Para">
-You can create new resources by using the <b>File &gt; New</b> menu on the Workbench menu bar.
-Start by creating a simple project as follows:</P>
-<ol>
-  <li>
-<P CLASS="Para">
-From the menu bar, select <b>File &gt; New &gt; Project...</b></P>
-<P CLASS="Para">
-<img src="../images/Image11_new_wizard.png"  alt="New Project Wizard" border="0"></P>
-  </li>
-  <li>
-    <P CLASS="Para"> In the New Project wizard, select <b>General</b> <strong>&gt;</strong> 
-      <b>Project</b> then click <b>Next</b>.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> In the <b> Project name </b> field, type your name as the 
-      name of your new project. Do not use spaces or special characters in the 
-      project name (for example, &quot;JaneQuser&quot;).</P>
-  </li>
-  <li>
-<P CLASS="Para">
-Leave the box checked to use the default location for your new project. Click
-<b>Finish</b> when you are done.</P>
-<P CLASS="Para">
-<img src="../images/Image12_new_project_wizard.png"  alt="New Project Wizard" border="0"></P>
-<P CLASS="Para">&nbsp;
-</P>
-  </li>
-</ol>
-<P>If you sneak a peek at the navigation view, you will see that it now contains 
-  the simple project we just created.&nbsp; </P>
-
-
-<P align="center"><img src="../images/Image13_project_in_nav.png" alt="Project Explorer view" border="0">
-</P>
-
-
-<P>Create a second project called JaneQuser2 using the same steps, but instead 
-  of clicking <b>Finish</b>, click <b>Next</b>. At this point you can specify 
-  other projects that project JaneQuser2 depends on. Since we want to create two 
-  independent projects we will not select any of the projects in the <b>Project 
-  References </b> table. Click <b>Finish</b> to create your second simple project. 
-</P>
-
-
-<P align="center"><img src="../images/Image15_project_depend.png" alt="New Project Wizard" border="0">
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm
deleted file mode 100644
index 40644c5..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07c.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the popup</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Using the popup</h3>
-<P CLASS="Para">
-Now that we have our project we will create a folder. We will create
-our folder using the Project Explorer view's popup menu.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Activate the Project Explorer view and select the project JaneQuser 
-      (the first project we created in the Project Explorer view). From the view's popup 
-      menu choose <b>New &gt; Folder</b>.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the New Folder wizard, your project name appears by default 
-      in the <b>Enter or select the parent folder </b> field. This is because 
-      we chose to create the new folder from your project's context menu.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b> Folder name</b> field, type a unique name for 
-      your new folder. 
-      Depending on the platform you are running on, some characters will not be allowed
-      (for example, &quot;Jane's Folder?&quot;).</P>
-    <P CLASS="Para"> <img src="../images/Image14_new_folder_wizard.png"  alt="New Folder Wizard" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>Finish</b> when you are done. The Project Explorer view 
-      will update to show your newly created folder.</P>
-  </li>
-</ol>
-<P><strong>Note:</strong> There is now also an <b>Advanced</b> button. This button 
-  when selected allows you to enter a location outside of a project's hierarchy 
-  as the location for one of its folders. This is called a linked folder.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm
deleted file mode 100644
index 4acd4cc..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-07d.htm
+++ /dev/null

@@ -1,118 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the New button</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Using the New button</h3>
-<P CLASS="Para">We have seen how to create resources using <b>File &gt; New</b> 
-  and <b>New</b> from the context menu of one of the navigation views. We will 
-  now create a file for our project using the third alternative, the toolbar <b>New</b> 
-  button.</P>
-<ol>
-  <li> 
-    <P CLASS="Para">Select the folder JanesFolder in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para">In the Workbench window's toolbar, activate the drop-down 
-      menu on the New Wizard button <img src="../images/Image15_new_button.png" alt="New Wizard Button" border="0"> 
-      and select <b>File</b>. To activate the drop-down menu simply click on the 
-      down arrow.</P>
-    <P CLASS="Para"> <img src="../images/Image16_new_pulldown.png" alt="New Wizard Pulldown" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the New File wizard, your folder's name and path already 
-      appear by default in the <b> Enter or select the parent folder </b> field. 
-      This is because you chose to create the new file while this folder was selected 
-      in one of the navigation views and the view was active.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b> File name</b> field, type a unique name for a 
-      new text file, including the .txt file extension. Do not use spaces or special 
-      characters in this file name (for example, &quot;JanesFile.txt&quot;).</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>Finish</b> when you are done.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> The Workbench has an editor capable of editing text files. 
-      A text editor is automatically opened on the newly created file.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the text editor, type in the following five lines:</P>
-    <blockquote> 
-      <P CLASS="Para"><i>This is a sample text file.<br>
-        There is not much else<br>
-        we can really say about it other<br>
-        than it has five lines of<br>
-        text that are rather dull.</i></P>
-    </blockquote>
-    <P CLASS="Para">Notice that the editor tab has an asterisk (*) at the left 
-      of the filename. The asterisk indicates that the editor has unsaved changes.</P>
-    <blockquote> 
-      <P CLASS="Para"><img src="../images/Image17b_unsaved_changes.png" alt="Editor Unsaved Changes" border="0"></P>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Workbench window's toolbar, click the Save button 
-      <img src="../images/Image17_save_button.png"  alt="Save Button" border="0"> 
-      to save your work.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In one of the navigation views ensure your folder is still 
-      selected and the navigation view is active.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <strong>New Wizard </strong>in the Workbench toolbar. 
-      Previously we clicked on the drop-down arrow of the New button. Here we 
-      clicked on the button itself which has the same effect as choosing <b>File 
-      &gt; New &gt; Other...</b></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the New wizard, select <b>General &gt; File</b>. 
-    Then click <b>Next</b>.</P>
-  </li>
-  <li> <P CLASS="Para"> Once again, your folder's name and path appears by default in the <b> Enter 
-    or select the parent folder </b> field.&nbsp;</P></li>
-  <li>
-    <P CLASS="Para"> In the <b>File name</b> field, type a unique name for an 
-      .ini file. Do not use any spaces or special characters in the file name 
-      (for example, &quot;JanesINIFile.ini&quot;). Click Finish when you are done.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Since the Workbench does not have any editors registered 
-      for .ini files, it may launch an external editor on the file if one is registered 
-      with the operating system. For the moment, close the editor. </P>
-  </li>
-</ol>
-<P>Now that we have created our resources, one of the navigation views shows our two projects, 
-  the folder and its two files. To the right of one of the navigation views is the text 
-  editor open on the first file we created (JanesFile.txt). To proceed with the 
-  following example create a second file (JanesFile2.txt). </P>
-
-
-<P><img src="../images/Image18_created_resources.png" alt="Eclipse Workbench" border="0">
-</P>
-
-
-<P>Click the new JanesFile2.txt editor tab. Now select the file JanesINIFile.ini 
-  in one of the navigation views. Then select the <b>Link with Editor</b> <img src="../images/synced.png" alt="Link with Editor" border="0">
-  button in the local toolbar or view menu <img src="../images/view_menu.png" alt="Link with Editor" border="0">
-  of one of the navigation views. Lastly, click on the editor tab for JanesFile.txt.
-  Notice how the navigation view updated itself to select the file you are currently 
-  editing (JanesFile.txt). If you don't like this automatic update you can easily 
-  turn it off by deselecting <b>Link with Editor</b>.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm
deleted file mode 100644
index 0b25854..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-10b.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Closing an editor</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>
-Closing an editor</h2>
-<P CLASS="Para"> Now that there are a couple of editors open, here's how to close 
-  them.&nbsp;</P>
-<ol>
-  <li>
-<P CLASS="Para">
-Select the JanesFile.txt editor tab.&nbsp;</P>
-  </li>
-  <li>
-<p CLASS="Para">
-In the text area add a 6th line of text:</p>
-<blockquote>
-  <p CLASS="Para">This is a 6th line</p>
-</blockquote>
-  </li>
-  <li>
-    <P CLASS="Para"> To close the editor, choose one of the following options:</P>
-<ul>
-  <li>
-    <p CLASS="Para">
-    Click the close button (&quot;X&quot;)
-    <img src="../images/Image19_close_on_tab.png"  alt="Editor Tab" border="0">
-    in the tab of the editor.</p>
-  </li>
-  <li>
-        <p CLASS="Para"> Select <b>File &gt; Close</b> from the menu bar.</p></li>
-</ul>
-  </li>
-  <li>
-    <P CLASS="Para"> Note the prompt to save the file before the editor is closed.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Click OK to save any changes and close the editor.</P>
-  </li>
-</ol>
-<P>If the editor was closed using <b>File &gt; Close</b>, notice that the option 
-  <b>File &gt; Close All</b> was also displayed. This is a quick way to close 
-  all of the open editors. If <b>File &gt; Close All</b> is chosen, a prompt will 
-  appear to choose which editors with unsaved changes should be saved. </P>
-
-<P>The preference to close editors automatically can be found in the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Editors</b></a> preference page. There you can configure the number of editors that 
-  can be opened prior to editors being reused and what should occur when all editors 
-  have unsaved changes.</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm
deleted file mode 100644
index 04d1f33..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigating resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Navigating resources </h2>
-<P CLASS="Para"> This section will work with the Project Explorer and Tasks views. 
-  These views are initially part of the resource perspective. To experiment with 
-  other views, they can be displayed by using the <b>Window &gt; Show View</b> 
-  menu.</P>
-<P CLASS="Para">
-One important view to become familiar with is one of the navigation views, which displays information 
-about the contents of the Workbench and how the resources relate to each other in a hierarchy.</P>
-<P CLASS="Para">
-The Workbench contains projects, which in turn contain folders and/or files.
-Projects, folders, and files are collectively called resources.</P>
-<blockquote>
-  <blockquote>
-<P CLASS="Para" align="center">
-<img src="../images/Image20_nav_with_resources.png"  alt="Project Explorer View" border="0"></P>
-  </blockquote>
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm
deleted file mode 100644
index 2a358aa..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12b.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening resources in the Project Explorer</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h3>
-Opening resources in the Project Explorer </h3>
-<P CLASS="Para">Using the Project Explorer there are several ways to open an
-editor.</P>
-<ol>
-  <li> 
-    <P CLASS="Para">In one of the navigation views select the file JanesFile.txt</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> To open an editor on the file choose one of the following 
-      approaches:</P>
-    <ul>
-      <li><p>To edit a resource using the default editor for that resource, either 
-        double click on the resource (in one of the navigation views), or select 
-        the resource and choose <b>Open</b> from its popup menu.; 
-        </p></li>
-      <li><p>To use a specific editor to edit the resource, start by selecting the 
-        resource in one of the navigation views, and choose the <b>Open With</b> 
-        option from the popup menu. 
-        </p> </li>
-    </ul>
-    <p CLASS="Para">The Workbench remembers the last editor that was used for 
-      editing a specific file. This makes it easier to use the same editor down 
-      the road.</p>
-  </li>
-</ol>
-<P CLASS="Para"> The default editors can be configured using the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Editors &gt; File Associations</b></a> preference page.
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm
deleted file mode 100644
index 55e3f28..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-12c.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Go To</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Go
-To</h3>
-<P CLASS="Para"> The Go To operation makes it easy to jump to a specific resource 
-  in the navigation views.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Select one of the navigation views. Its title bar will be 
-      highlighted (according to the operating system's color scheme).</P>
-  </li>
-  <li> 
-    <P CLASS="Para">From the menu bar choose <b>Navigate &gt; Go To &gt; Resource...</b>.</P>
-  </li>
-  <li> 
-    <P CLASS="Para">In the Go To Resource dialog type &quot;JanesF&quot; into 
-      the pattern field at the top of the dialog.</P>
-    <P CLASS="Para">As the filename is typed, the dialog filters the set of possible 
-      matches based on what has been entered so far.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select JanesFile.txt from the <b>Matching items</b> field 
-      and click OK or simply press Enter. </P>
-  </li>
-  <li> 
-    <p CLASS="Para"> The navigation view will select the file JanesFile.txt.</p>
-  </li>
-</ol>
-<P align="center"><img src="../images/Image30_goto_resource.png"  alt="Goto Resource popup" border="0">
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm
deleted file mode 100644
index 7401b49..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-13.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Files</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Files</h2>
-<p CLASS="Para">The projects, folders and files that you create with the Workbench are
-  all stored under a single directory that represents your workspace. The location of
-  the workspace was set in the dialog that first opens when you start the Workbench.</p>
-<p>If you have forgotten where that location is, you can find it by selecting
-  <b>File &gt; Switch Workspace...</b>. The workspace directory will be displayed in
-  the dialog that appears.
-  <b>IMPORTANT:</b> After recording this location, hit <b>Cancel</b> to close the dialog,
-  or the Workbench will exit and re-open on whatever workspace was selected.</p>
-<p CLASS="Para">All of the projects, folders and files that you create with the 
-  Workbench are stored as normal directories and files on the machine. This allows
-  the use of other tools when working with the files. 
-  Those tools can be completely oblivious to the Workbench. A later section will 
-  look at how to work with external editors that are not integrated into the Workbench.</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml
deleted file mode 100644
index e3f4c20..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-24a.xhtml
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-	<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Exporting files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>
-Exporting files </h1>
-<p class="Para">Files can be exported from the Workbench either by:</p>
-<ul>
-  <li> Dragging and dropping to the file system (Windows and Linux GTK only), or</li>
-  <li filter="ws=win32"> <img align="texttop" border="0" src="../images/win_only.png" alt="Windows only" />
-    Copying and pasting to the file system, or</li>
-  <li> Using the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.file.export&quot;)">
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"/>
-  <b>Export wizard</b></a>.</li>
-</ul>
-<h2>
-Drag and drop or copy and paste</h2>
-<p class="Para" filter="ws=win32"> <img align="texttop" border="0" src="../images/win_only.png" alt="Windows only" /> 
-  The operating system's file system explorer can be used to export a copy of 
-  a folder or file from the Workbench to the file system.</p>
-<ol>
-  <li> 
-    <p class="Para"> Open the operating system's file system explorer.</p>
-  </li>
-  <li> 
-    <p class="Para"> Drag the file JanesFile.txt from one of the navigation view 
-      to the file system explorer.</p>
-  </li>
-  <li> 
-    <p class="Para">Depending on where you are dragging to, you may need to hold 
-      down the Ctrl or Shift key while dragging to ensure the file is copied. 
-      Look for a small plus sign on the drag cursor to know whether the file is 
-      being copied or moved. </p>
-  </li>
-  <li filter="ws=win32"> 
-    <p class="Para"> The export can also be achieved by selecting the file in 
-      the Project Explorer and choosing <b>Edit &gt; Copy</b>, then</p> 
-    <p class="Para">pasting it in the file system explorer.</p> </li>
-</ol>
-<h2>
- Export wizard</h2>
-<p class="Para"> The Export wizard can be used to export from the Workbench to 
-  the file system.</p>
-<ol>
-  <li> 
-    <p class="Para"> Select the project JaneQuser in the navigation view. </p>
-  </li>
-  <li> 
-    <p class="Para"> From the popup menu, select <b>Export</b>.</p>
-  </li>
-  <li> 
-    <p class="Para"> In the Export wizard, select <b>File system</b>, then click 
-      <b>Next</b>.</p>
-    <p class="Para"> <img src="../images/Image42_export.png" alt="Export Wizard. Select an export destination." border="0" /></p>
-  </li>
-  <li> 
-    <p class="Para">Expand JaneQuser project, and click on JanesFolder. In the 
-      right pane ensure that only JanesINIFile.ini is selected. Notice the 
-      folder and project in the left pane now have a grayed checkbox indicating 
-      that some, but not all, of their contents will be exported.</p>
-    <p class="Para">The <b>Select Types</b> button can be used to filter the types 
-      of resources to export.</p>
-    <p class="Para"><strong>Note:</strong> To export JanesINIFile.ini only, simply 
-      select it in the navigation view and choose <b>File &gt; Export</b>. The 
-      Export wizard will automatically ensure it is the only file selected for 
-      export. </p>
-    <p class="Para"> <img src="../images/Image43_export_tree.png" alt="Export Wizard. Enter a destination directory." border="0" /></p>
-  </li>
-  <li> 
-    <p class="Para"> In the <b> To directory</b> field, type or browse to select 
-      a location in the file system for the exported resources to reside.</p>
-    <p class="Para"> If the name of a directory that does not exist is entered 
-      the Export wizard will offer to create it once <b>Finish</b> is selected.</p>
-  </li>
-  <li> 
-    <p class="Para"> In the <b>Options</b> area, options are given to:</p>
-    <ul class="UnorderedList">
-      <li class="Item"> Overwrite existing resources without warning </li>
-      <li class="Item"> Create directory structure for files or Create only selected 
-        directories</li>
-    </ul>
-  </li>
-  <li> 
-    <p class="Para"> Click <b>Finish</b> when done.</p>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm
deleted file mode 100644
index 0238560..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31a.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h2>
-Importing files </h2>
-<P CLASS="Para"> Files can be imported into the Workbench either by :</P>
-<ul>
-  <li>
-    dragging and dropping from the file system, or</li>
-  <li>
-    copying and pasting from the file system, or</li>
-  <li>
-     Using the
-     <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-     <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-     <b>Import wizard</b></a>.</li>
-</ul>
-<p>Using drag and drop or copy/paste to import files relies on operating system support
-  that is not necessarily available on all platforms. If the platform you are using
-  does not have this support, you can always use the Import wizard.</p>
-<p CLASS="Para"> In this section the two files that were just exported will be 
-  imported and placed into the second project JaneQuser2. <br>
-</p>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm
deleted file mode 100644
index beaca2a..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31b.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Drag and drop or copy and paste</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Drag and drop or copy and paste</h3>
-<P CLASS="Para"> 
-  On some platforms, for example on the Macintosh and Microsoft Windows,
-  the operating system's file system browser can be used to copy folders and files 
-  from the file system into the Workbench.</P>
-<P CLASS="Para"> <strong>Note: </strong>The resource(s) must be dragged to the 
-  exact location in the hierarchy of one of the navigation views where the resources 
-  are to reside; they cannot be simply dragged and dropped onto a blank area in 
-  the navigation view.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Open the operating system's file system explorer.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Locate the file JanesFile.txt that was recently exported 
-      and drag it to a specific location in one of the navigation views in the 
-      Workbench.&nbsp;&nbsp;</P>
-    <P CLASS="Para">When dragging resources into one of the navigation views, 
-      the project/folder that the resource is being dropped into will be selected.</P>
-    <blockquote> 
-      <blockquote> 
-        <P CLASS="Para"> <img src="../images/Image37drop.png"  alt="Project Explorer view" border="0"></P>
-      </blockquote>
-    </blockquote>
-    <P CLASS="Para"> Drag the file over JaneQuser2 and release the mouse button.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that the file is copied into the Workbench and placed 
-      into JaneQuser2.</P>
-  </li>
-  <li>This can also be achieved by copying the file in the file system explorer, 
-    then selecting the destination in the navigation view and choosing <b>Edit 
-    &gt; Paste</b>. </li>
-</ol>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm
deleted file mode 100644
index 6df3804..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-31c.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Import wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Import wizard</h3>
-<P CLASS="Para"> The Import wizard can be used to copy resources into the Workbench.</P>
-<ol>
-  <li> 
-    <p CLASS="Para"> Select the project JaneQuser.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select <b>Import</b> from the popup.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Import wizard, select <b>File system</b>, then click 
-      <b>Next</b>.</P>
-    <P CLASS="Para"> <img src="../images/Image38_import.png"  alt="Import Wizard. Import resources from the local file system." border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b>From directory</b> field, type or browse to select 
-      the directory containing the file JanesINIFile.ini that was recently exported.</P>
-    <P CLASS="Para">Recent directories that have been imported from are shown 
-      on the <b>From directory</b> field's combo box.</P>
-    <blockquote> 
-      <P CLASS="Para">&nbsp;<img src="../images/Image41_import_combo.png"  alt="Import Wizard. From directory field." border="0"></P>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para">In the right pane check the file JanesINIFile.ini&nbsp;&nbsp;</P>
-    <P CLASS="Para"> Checking a folder in the left pane will import its entire 
-      contents into the Workbench. A grayed checkbox (as shown below) indicates 
-      that only some of the files in the folder will be imported into the Workbench.</P>
-    <P CLASS="Para">The <b>Filter Types</b> button can be used to filter the types 
-      of files that will be imported.</P>
-    <P CLASS="Para"><img src="../images/Image39_import_tree.png"  alt="Import Wizard. Filter types." border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> The <b>Into folder</b> field should already be filled in 
-      with the name of the project (JaneQuser).&nbsp; </P>
-  </li>
-  <li> 
-    <P CLASS="Para">The destination project or folder can be changed by clicking 
-      <b>Browse</b>; </P>
-    <P CLASS="Para">Click the <b>Browse</b> button and choose the second project 
-      JaneQuser2.&nbsp; </P>
-    <blockquote> 
-      <blockquote> 
-        <P CLASS="Para"> <img src="../images/Image40_import_target.png"  alt="Import Wizard. Select a folder to import into." border="0"></P>
-      </blockquote>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b>Options</b> area, options are given to: </P>
-    <UL CLASS="UnorderedList">
-      <LI CLASS="Item"> Overwrite existing resources without warning </LI>
-      <LI CLASS="Item"> Create complete folder structure or Create selected folders 
-        only</LI>
-    </UL>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>Finish</b> when done. The file JaneINIFile.ini is 
-      now shown in the one of the navigation views in the project JaneQuser2.</P>
-  </li>
-</ol>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm
deleted file mode 100644
index 5ee9863..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-32.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Deleting resources</h2>
-<P CLASS="Para">Now that a few files have been imported into the second project 
-  (JaneQuser2), here are instructions on how to delete the project.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para">Select project JaneQuser2 in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> To delete the project do one of the following:</P>
-    <ul>
-      <li> From the project's pop-up menu choose <b>Delete</b> </li>
-      <li>Press the DEL key </li>
-      <li>Choose <b>Edit &gt; Delete</b> from the pull-down menu</li>
-    </ul>
-  </li>
-  <li> 
-    <P CLASS="Para"> A prompt will ask for confirmation of the deletion and also 
-      what type of deletion should be performed.</P>
-    <P CLASS="Para"> It is possible to:</P>
-    <ul>
-      <li> 
-        <p CLASS="Para">Delete the contents of the project from the file system</p>
-      </li>
-      <li> 
-        <p CLASS="Para">Delete the project from the workspace but keep its contents 
-          in the file system</p>
-      </li>
-      <li>Accept the default (do not delete contents) and click <b>Yes</b>.</li>
-    </ul>
-  </li>
-</ol>
-<p><strong>Note:</strong> This is only an option for projects. Files and folders 
-  are always deleted from the file system when deleted.</p>
-<P> The same steps work for any resource shown in the navigation view. <br>
-</P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml
deleted file mode 100644
index 9172ff7..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34a.xhtml
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Working with other editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h2>
-Working with other editors</h2>
-<p class="Para"> Instructions have been given explaining how to import and export 
-  resources from the Workbench. This section will look at how to edit Workbench 
-  resources using the following three approaches:</p>
-<ul>
-  <li>
-    External editors launched by the Workbench</li>
-  <li filter="ws=win32">
-    Embedded OLE documents <img src="../images/win_only.png" alt="Windows only" border="0" /></li>
-  <li>
-    External editors launched without the Workbench's knowledge</li>
-</ul>
-<p class="Para">Before continuing, take a moment and confirm that the Project Explorer 
-  contains the following resources:</p>
-<blockquote>
-  <blockquote>
-    <p class="Para" align="center"><img src="../images/Image44_confirm_state.png" alt="Project Explorer view" border="0" /></p>
-  </blockquote>
-</blockquote>
-
-
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml
deleted file mode 100644
index dd91df1..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34b.xhtml
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>External editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h3>
-External editors</h3>
-<p class="Para">When opening a resource the Workbench first consults its list 
-  of registered editors. If no registered editors are found for the resource the 
-  Workbench checks with the underlying operating system to determine if it has 
-  any editors registered for the particular file type. If an editor is located, 
-  the Workbench will automatically launch that editor. This type of editor is 
-  referred to as an external editor because it does not show up as an editor tab 
-  in the Workbench.</p>
-<ol>
-  <li>
-<p class="Para">Select the file JanesINIFile.ini.</p>
-  </li>
-  <li>
-<p class="Para">
-Double-click the file in one of the navigation views to launch the external editor.</p>
-    <p class="Para"> If an editor for INI files is not registered with the underlying 
-      operating system the Workbench will attempt to use its own default text 
-      editor. If this happens, to see an external editor, import another file 
-      (see previous sections) that is associated with a third party editor. Double 
-      click again on this new file and the selected editor will open in its own 
-      window.</p>
-<p class="Para" filter="ws=win32"><img src="../images/win_only.png" alt="Windows only" border="0" /><br />
-      The Workbench supports OLE document editors, and some editors provide OLE 
-      document support allowing it to be opened in its own window, or embedded 
-      inside another window like the Workbench. This will be discussed in more 
-      detail in the next section.</p>
-  </li>
-</ol>
-
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml
deleted file mode 100644
index b34e9a6..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34c.xhtml
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Embedded editors</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Embedded editors</h3>
-<p class="Para"> <img src="../images/win_only.png" alt="Windows only" border="0" />The 
-  Workbench supports OLE document editors.</p>
-<p class="Para"><img src="../images/Image619_ole.png" alt="OLE document editor." border="0" /></p>
-<ol>
-  <li> 
-    <p class="Para"> Select JanesFolder in the navigation view.</p>
-  </li>
-  <li>Create the file Jane.doc. </li>
-  <li> 
-    <p class="Para">Notice how the Workbench automatically opens the OLE document 
-      editor in place and integrates its pull-down menu options into the menu 
-      bar. There should also be an editor tab for Jane.doc.</p>
-  </li>
-  <li> 
-    <p class="Para"> Make a change to the file.</p>
-  </li>
-  <li> 
-    <p class="Para"> Close the editor by clicking the X on the editor tab; when 
-      prompted, save its contents.</p>
-  </li>
-  <li> 
-    <p class="Para"> Reopen the file by double-clicking it in the navigation view.</p>
-  </li>
-</ol>
-
-
-
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm
deleted file mode 100644
index 8e6d561..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-34d.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editing files outside the Workbench</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Editing files outside the Workbench</h3>
-<P CLASS="Para"> In a previous section an external editor was launched on the 
-  file JanesINIFile.ini by double clicking on it in the Project Explorer. The same external 
-  editor can also be used by launching it outside of the Workbench.&nbsp;</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Close any editors that are open on JanesINIFile.ini.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the file system explorer, navigate to the directory where 
-      the Workbench was installed and go into the workspace sub-directory.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Edit the file JanesINIFile.ini and save it . Do not use the 
-      Workbench's Project Explorer to open the editor.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Return to the Workbench and in the Project Explorer view, select 
-      the project JaneQuser.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Choose <b>Refresh</b> from the project's context menu. This 
-      instructs the Workbench to look for any changes to the project that have 
-      been made in the local file system by external tools.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select the file JanesINIFile.ini.</P>
-  </li>
-  <li> 
-    <p CLASS="Para"> For a little variety choose <b>Open With &gt; Text Editor</b> 
-      from the file's popup menu.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> Observe that the Workbench's own default text editor is opened.&nbsp;</P>
-    <P CLASS="Para"> In the default text editor verify that the externally made 
-      changes are reflected in the Workbench.</P>
-  </li>
-</ol>
-<P>The Workbench stores all of its resources in the local file system. This means 
-  the system file explorer can be used to copy files from the Workbench's workspace 
-  area even when the Workbench is not running. Resources can also be copied into 
-  the workspace directory. Use Refresh to update the Workbench with any changes 
-  made outside the Workbench.&nbsp; &nbsp; </P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm
deleted file mode 100644
index 24727da..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Copying, renaming and moving</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Copying, renaming and moving</h1>
-<P CLASS="Para">Workbench resources can be copied, moved and renamed using popup 
-  menu operations in one of the navigation views. In this section several of the 
-  files that have been created will be copied and renamed.&nbsp;</P>
-<P CLASS="Para">Prior to copying files, some setup is required:</P>
-<p CLASS="Head"><b><a name="Setup">Setup</a></b></p>
-<ol>
-  <li> 
-    <p CLASS="Head">In one of the navigation views, delete the file JanesWordDoc.doc. 
-      The navigation view should look like this:</p>
-    <blockquote> 
-      <P CLASS="Para"> <img src="../images/Image44_confirm_state.png" alt="Project Explorer view" border="0"></P>
-    </blockquote>
-    <p CLASS="Head">&nbsp;</p>
-  </li>
-  <li> 
-    <P CLASS="Para">Double click on JanesFile.txt and ensure that it contains 
-      the following text.</P>
-    <blockquote> 
-      <P><i>This is a sample text file<br>
-        There is not much else<br>
-        we can really say about it other<br>
-        than it has five lines of<br>
-        text that are rather dull.</i></P>
-    </blockquote>
-  </li>
-  <li> 
-    <p CLASS="Head">Close the editor on JanesFile.txt.</p>
-  </li>
-  <li> 
-    <p CLASS="Para"> Select the project JaneQuser. Using the project's pop-up 
-      menu create a folder named JanesOtherFolder.</p>
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image45_setup.png" alt="Project Explorer view" border="0"></p>
-    </blockquote>
-  </li>
-</ol>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm
deleted file mode 100644
index bdfd41a..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35b.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Copying</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Copying</h3>
-<p CLASS="Head">You can copy JanesFile.txt to the new folder (JanesOtherFolder) using
-  the following steps. </p>
-<ol>
-  <li> 
-    <p CLASS="Head"> Ensure that the setup described in the introduction to this 
-      <a href="qs-35.htm#setup">section</a> has been performed.</p>
-  </li>
-  <li> 
-    <p CLASS="Para"> In one of the navigation views, select JanesFile.txt.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> From the file's context menu, select <b>Copy</b> (or Ctrl+C)</P>
-  </li>
-  <li>In one of the navigation views, select JanesOtherFolder as the destination.</li>
-  <li> 
-    <p CLASS="Head"> From the folder's context menu, select <b>Paste</b> (or Ctrl+V).</p>
-  </li>
-</ol>
-<P>As an alternative to copying files using the copy operation, it is also possible 
-  to copy files by holding down the Ctrl key while dragging a file from one folder 
-  to another folder. (On the Macintosh, the Option key is used for this.)</P>
-<p>Once the file has been copied it can be renamed.</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm
deleted file mode 100644
index ac1ba61..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35c.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Renaming</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Renaming</h3>
-<p CLASS="Head">Now that JanesFile.txt has been copied from JanesFolder to JanesOtherFolder 
-  it is ready to be renamed as something else.&nbsp;</p>
-<ol>
-  <li>
-    <p CLASS="Head">In one of the navigation views, select JanesFile.txt in JanesOtherFolder.</p>
-  </li>
-  <li>
-<P CLASS="Para">
-From the file's context menu, select <b>Rename</b>.</P>
-  </li>
-  <li>
-    <p CLASS="Para">The navigation view overlays the file's name with a text field.&nbsp;&nbsp;Type 
-      in JanesText.txt and press Enter.</p>
-<DIV CLASS="Note">
-<P CLASS="Para">&nbsp;
-</P>
-<blockquote>
-  <P CLASS="Para">
-<img src="../images/Image48_rename.png"  alt="Project Explorer view" border="0"></P>
-</blockquote>
-      <P CLASS="Para">To halt the renaming of a resource, Escape can be pressed 
-        to dismiss the text field.</P>
-</DIV>
-  </li>
-</ol>
-<P>Copy and rename works on folders as well.&nbsp; </P>
-
-
-<ol>
-  <li> 
-    <P CLASS="Para"> In one of the navigation views, select the folder JanesOtherFolder.</P>
-  </li>
-  <li> 
-    <p CLASS="Para"> From the folder's context menu choose <b>Rename</b>.</p>
-  </li>
-  <li>Once again the navigation view overlays the folder name with an entry field 
-    to allow the typing in of a new name. Change the folder name to be JanesSecondFolder.</li>
-  <li>Rename the folder back to its original name (JanesOtherFolder).</li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm
deleted file mode 100644
index 91c185b..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-35d.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Moving</h3>
-<p CLASS="Head">Having copied and renamed several of the resources, now it's time 
-  to move some resources around. JanesOtherFolder and its file will be moved to 
-  be a sub-folder of the original folder JanesFolder.</p>
-<ol>
-  <li>In the Project Explorer view, select JanesOtherFolder. </li>
-  <li>From the file's context menu, select <b>Move</b>.</li>
-  <li><p>In the Folder Selection dialog choose JanesFolder and click <b>OK</b>.</p>
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image48_move.png"  alt="Folder dialog" border="0"></p>
-</blockquote>
-  </li>
-  <li>In the Project Explorer JanesFolder now contains JanesOtherFolder. Expand
-JanesOtherFolder and confirm that it contains JanesText.txt.
-<blockquote>
-  <p><img src="../images/Image48_rename_done.png"  alt="Project Explorer view" border="0"></p>
-</blockquote>
-  </li>
-</ol>
-
-
-<P>As an alternative to moving files using the move operation, it is also possible 
-  to move files by dragging a file from one folder to another folder. Remember 
-  that to copy files from one folder to the other, Ctrl needs to be held down 
-  while performing the drag and drop operation. (On the Macintosh, the Option 
-  key is used for this.) </P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm
deleted file mode 100644
index 3e2d259..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36.htm
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Searching</title></head>
-<body>
-
-<h2>Searching</h2>
-
-<p>Text strings and files can be searched for in the Workbench.&nbsp;In this section, 
-  <strong>Search </strong><img src="../images/Image50_search.png"  alt="Search button" border="0"> 
-  will be used to perform a text search across the resources that are shown in 
-  the navigation view. Instruction will also be given on how to use the Search 
-  view to work with the results.</p>
-
-
-
-
-</body></html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm
deleted file mode 100644
index 65495c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36a.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Starting a search</title>
-
-</HEAD>
-<body>
-<h3>Starting a search</h3>
-
-<p>Text strings can be searched for in the Workbench as follows:</p>
-
-<ol>
-  <li>In the Workbench toolbar, click the search button <img src="../images/Image50_search.png"  alt="Search button" border="0">.</li>
-  <li>In the <b>Containing text</b> field, type in: <i>it</i> <br>
-    The combo box for the <b>Containing text</b> field also displays a list of 
-    recently performed searches to select from.<br>
-    <img src="../images/Image51_search_it.png"  alt="Search dialog" border="0"></li>
-  <li> The <b>Case sensitive</b> checkbox can be selected or deselected depending 
-    on whether or not a case sensitive or insensitive search is to be performed.
-    You can also select the <b>Regular expression</b> checkbox to enable more powerful searching
-    capabilities. To see what is available in regular expression mode, you can hit
-    Ctrl-Space over the text field to get content assistance that lists the possibilities.
-    For this example, just check the <b>Case sensitive</b> box to search for lowercase 
-    &quot;<i>it</i>&quot;.</li>
-  <li> The kinds of files to include in the search can be specified in the <b>File 
-    name patterns</b> field. Click <b>Choose...</b> to open the Select Types dialog. 
-    This dialog provides a quick way to select from a list of registered extensions. 
-    <blockquote><img src="../images/Image51_choose_ext.png" alt="Type Selection Dialog" border="0"></blockquote>
-    For the moment, the search will be confined to .txt files. Ensure *.txt is 
-    checked and click <b>OK</b>.</li>
-  <li>In the <b>Scope</b> field, specify the files and folders to include in the 
-    search. The choices are: the entire workspace, the currently selected resources 
-    in the Workbench, or a working set which is a named, customized group of files 
-    and folders. Leave the scope as workspace.</li>
-  <li> Use the <b>Customize</b> button to choose what kinds of searches are available 
-    in the dialog. This setting may be left unchanged.</li>
-  <li>Click <b>Search</b>. At this point, the Search view will be made visible, 
-    and it will begin to fill in with the results of the search. The stop button 
-    in the Search view can be clicked to cancel the search while it is in progress. 
-  </li>
-  <li>Observe that the Search view displays: 
-    <blockquote> <img src="../images/Image51_search_view.png" alt="Search view" border="0"></blockquote>
-  </li>
-</ol>
-
-<p> The next section will describe how to work with the Search view.</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm
deleted file mode 100644
index 0763ca8..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-36b.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-	<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-
-	<title>The Search view</title>
-</head>
-
-<body>
-
-<h3>The Search view&nbsp;</h3>
-
-<p>Now that the search for &quot;it&quot; has been completed, the Search view 
-  is visible. The title of the Search view shows that four matches were found.&nbsp;</p>
-<blockquote> 
-  <p> <img src="../images/Image51_search_view.png"  alt="Search view. Four matches for the word it found in the Workspace." border="0">&nbsp;&nbsp;</p>
-</blockquote>
-<p CLASS="Head"> Within the Search view two files are shown and within each file 
-  there were 2 matches found.&nbsp; </p>
-    <ol>
-  <li>Click the Show Next Match button <img src="../images/Image51_search_next.png"  alt="Show next match button" border="0">to 
-    navigate to the first match of the search expression (&quot;it&quot;). <br>
-    Notice that the file JanesFile.txt is automatically selected and opened in 
-    the editor area. <br>
-    Click Show Next Match button two more times. Once again the Search view automatically 
-    opens the file (JanesText.txt).</li>
-  <li>It is sometimes useful to remove uninteresting matches from the search results. 
-    The Search view's popup menu allows you to do this using <b>Remove Selected 
-    Matches</b> which removes any selected file entries (and all matches in them) 
-    from the Search view. Note that this <strong>only</strong> removes the entries 
-    in the Search view, it does <strong>not</strong> effect the files themselves. 
-    Select JanesFile.txt and choose <b>Remove Selected Matches</b> from the popup 
-    menu. The Search view now shows only the matches for JanesText.txt 
-    <blockquote><img src="../images/Image51_search_reduced.png"  alt="Search view. One match in Workspace." border="0"></blockquote>
-  </li>
-  <li>Perform a second search for &quot;that&quot; by clicking on the Search button 
-    <img src="../images/Image50_search.png"  alt="Search button" border="0"> in 
-    the Workbench's toolbar.</li>
-  <li>The Search view updates to show the results of the new search. <br>
-    Use the drop down button on the Search view's toolbar to move back and forth 
-    between the two search results. 
-    <blockquote><img src="../images/Image51_search_switching.png"  alt="Search view. Drop down button." border="0"></blockquote>
-  </li>
-  <li>In the drop down button choose <b>'it' - 1 match in workspace</b>. The Search 
-    view switches back to show the original search. On the context menu choose 
-    <b>Search Again</b> to repeat the initial search. Notice that once again there 
-    are four matches.</li>
-</ol>
-<p>So far you have seen how to manage your search results and how to switch between
-different searches. However, it might happen that you do not want the search view to 
-change even if further searches are performed. For this you can <strong>pin</strong> 
-the search view, which causes subsequent searches to be shown in a second Search 
-view.</p>
-<blockquote>
-<img 
-	src="../images/Image51_search_pinview.png" 
-	alt="Search view. Pin button" 
-	border="0">
-</blockquote>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm
deleted file mode 100644
index 84b0dff..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2b.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tasks and markers</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Tasks and markers</h2>
-<P CLASS="Para"> There are various types of markers including bookmarks, task 
-  markers, debugging breakpoints and problems. This section will focus on tasks 
-  and the Tasks view.</P>
-<P CLASS="Para"> The Tasks view displays all the tasks in the Workbench. 
-  The view displays tasks associated with specific files, specific lines in specific 
-  files, as well as generic tasks that are not associated with any specific file.</P>
-<P CLASS="Para">
-In the figure below &quot;sample task&quot; is a generic task not associated
-with any specific resource. The second task (&quot;add sixth line to the
-text&quot;) is associated with the file JanesFile.txt.</P>
-<P>&nbsp;<img src="../images/Image21_task_view.png" alt="Task view" border="0">
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm
deleted file mode 100644
index cf9d029..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Unassociated tasks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Unassociated
-tasks</h3>
-<P CLASS="Para">
-Unassociated tasks are not associated with any specific resource. To create an 
-unassociated task: </P>
-<ol>
-  <li> 
-    <P CLASS="Para"> In the Tasks view, click the New Task button <img src="../images/Image52_new_task.png" alt="New task button" border="0" >. 
-      A new task dialog appears. </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Type a brief description for the task and press Enter. To 
-      cancel the dialog while entering the description press Escape . The new 
-      task appears in the Tasks view.</P>
-    <p CLASS="Para"><img src="../images/Image53_newtask.png" alt="Tasks view" border="0" ></p></li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm
deleted file mode 100644
index 998f3c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2d2.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Associated tasks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Associated tasks</h3>
-<P CLASS="Para"> Associated tasks are associated with a specific location in a 
-  resource. To associate a task with the&nbsp;JanesFile.txt:</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Open a text file (JanesFile.txt) by double clicking on it 
-      in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the editor area directly to the left of any line in the 
-      text editor, access the context menu from the marker bar. The marker bar 
-      is the vertical bar to the left of the main text area.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> From the marker bar's context menu, select <b>Add Task</b>.</P>
-    <P CLASS="Para"> The marker bar displays any marker including bookmarks, task 
-      markers (for associated tasks), and/or debugging breakpoints. Various markers 
-      can be associated with specific lines in a file by accessing the context 
-      menu from the marker bar directly to the left of that line.</P>
-    <P CLASS="Para"> <img src="../images/Image53_marker1.png"  alt="Marker bar menu" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the <b>Description</b> field, type a brief description 
-      for the task that will be associated with that line in the text file.</P>
-    <blockquote> 
-      <P CLASS="Para"> <img src="../images/Image53_add_task_dlg.png"  alt="Add Task dialog" border="0"></P>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click <b>OK</b> when done.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that a new task marker appears in the marker bar, 
-      directly to the left of the line where the task was added. Also, notice 
-      that the new task appears in the Tasks view.</P>
-    <P CLASS="Para"> <img src="../images/Image53_task_updated.png"  alt="Tasks view" border="0"></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> After the new task has been added, click in the editor on 
-      the first line or any other line above the line with which the new task 
-      is associated.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Add several lines of text to the file at this point.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that as lines of text are added above it, the task 
-      marker moves down in the marker bar in order to remain with the associated 
-      line in the file. The line number in the Tasks view is updated when the 
-      file is saved.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Tasks view, access the context menu for the task that 
-      was just created.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Select <b>Mark Completed</b>. </P>
-  </li>
-  <li>Now select <b>Delete Completed Tasks</b> from the marker's context menu.</li>
-  <li> 
-    <P CLASS="Para"> Notice that the task marker disappears from the marker bar 
-      and the task is removed from the Tasks view.</P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm
deleted file mode 100644
index e7f452a..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-2f.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening files</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Opening
-files</h3>
-<P CLASS="Para">
-The Tasks view provides two approaches for opening the file associated with a
-task:</P>
-<ul>
-  <li> Select the task, and from the context menu choose <b>Go To</b></li>
-  <li>
-    Double click on the task</li>
-</ul>
-<p CLASS="Para">In both cases the file's editor is opened and the line with which the selected task is associated is highlighted.
-<br>
-</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm
deleted file mode 100644
index 474be4d..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3b.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Bookmarks</h2>
-<P CLASS="Para"> Bookmarks are a simple way to navigate to resources that are 
-  used frequently. This section will look at setting and removing bookmarks and 
-  viewing them in the Bookmarks view.</P>
-<P CLASS="Para"> The Bookmarks&nbsp;view displays all bookmarks&nbsp;in the Workbench. 
-  To show the Bookmarks view select <b>Window &gt; Show View &gt; Bookmarks</b> 
-  while in the Resource perspective.</P>
-<blockquote>
-  <P>&nbsp;<img src="../images/Image54_bookmark1.png" alt="Bookmarks view" border="0" >
-</P>
-
-
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm
deleted file mode 100644
index 3385852..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3c.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding and viewing bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Adding and viewing bookmarks</h3>
-<p CLASS="Head">The Workbench allows the bookmarking of individual files or locations 
-  within a file. This section will demonstrate how to set several bookmarks and 
-  how to view them using the Bookmarks view.</p>
-<ol>
-  <li>
-<p CLASS="Head">From the menu bar, select <b>Window &gt; Show View &gt; Bookmarks</b>. The
-Bookmarks view appears in the Workbench.&nbsp;</p>
-  </li>
-  <li>
-    <P CLASS="Para"> Edit the file JanesFile.txt.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Position the cursor over the editor's marker bar next to 
-      any line in the file. Then, from the context menu on the marker bar, select 
-      <b>Add Bookmark</b>.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_menu.png"  alt="Bookmark Menu" border="0"></P>
-</blockquote>
-<P CLASS="Para">When the Add Bookmark dialog opens type in a description for 
-this bookmark. Type in &quot;My Bookmark&quot;.</P>
-  </li>
-  <li>
-<P CLASS="Para">
-Notice that a new bookmark appears in the marker bar.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_added.png" alt="Editor with bookmark" border="0" >&nbsp;</P>
-</blockquote>
-<P CLASS="Para">
-The new bookmark also appears in the Bookmarks view.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_added2.png" alt="Bookmark view" border="0" ></P>
-</blockquote>
-  </li>
-  <li>
-    <P CLASS="Para"> In one of the navigation views select the file JanesText.txt. From 
-      the main Workbench menu select <strong>Edit &gt; </strong><b>Add Bookmark</b>.</P>
-<P CLASS="Para">
-This will bookmark the file using the filename to describe the bookmark. Observe the Bookmarks view now contains two
-bookmarks.</P>
-<blockquote>
-<P CLASS="Para">
-<img src="../images/Image54_bookmark_two.png" alt="Bookmark view" border="0" ></P>
-</blockquote>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm
deleted file mode 100644
index acc4f01..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3e.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Using bookmarks</h3>
-<p CLASS="Head"> Now that some bookmarks have been created, instructions will 
-  be given on how to get to the files associated with the bookmarks.</p>
-<ol>
-  <li> 
-    <P CLASS="Para"> Close all of the files in the editor area.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> In the Bookmarks view, double-click on the first bookmark 
-      that was created (My Bookmark).</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that a file editor opens displaying the file with 
-      which the bookmark is associated and that the line associated with the bookmark 
-      is highlighted.<br> 
-	  <strong>Note:</strong> The Bookmarks view supports an additional 
-      way to open the file associated with a selected bookmark, simply select 
-      <b>Go To </b>from the bookmark's context menu.<b> </b></P>
-  </li>
-</ol>
-<p CLASS="Head"> In the Bookmarks view, select the associated file in the Project Explorer. 
-</p>
-<ol>
-  <li>In the Bookmarks view, select My Bookmark.</li>
-  <li>From the bookmark's context menu choose <b>Show in Project Explorer</b>. </li>
-  <li>
-    <P CLASS="Para"> Notice that the Project Explorer view is now visible and the file 
-      JanesFile.txt is automatically selected. JanesFile.txt is the file My Bookmark 
-      was associated with.</P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm
deleted file mode 100644
index 58e739a..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-37-3f.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Removing bookmarks</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Removing bookmarks</h3>
-<p CLASS="Head">This section will demonstrate how to remove the bookmarks that 
-  have been created.</p>
-<ol>
-  <li> 
-    <P CLASS="Para"> In the Bookmarks view, select JanesFile.txt (the second bookmark 
-      we created) and do one of the following:</P>
-    <ul>
-      <li> Click the Delete button <img src="../images/Image54_bookmark_del1.png" alt="Bookmark delete button" border="0" > 
-        on the view's toolbar. </li>
-      <li> From the bookmark's context menu choose delete.</li>
-      <li> Hit the Delete key on the keyboard.</li>
-    </ul>
-    <P CLASS="Para"> Notice that the bookmark is removed from the Bookmarks view.</P>
-    <blockquote> 
-      <P CLASS="Para"> <img src="../images/Image54_bookmark_oneleft.png" alt="Bookmark view" border="0" ></P>
-    </blockquote>
-  </li>
-  <li>There should be one remaining bookmark. This bookmark is associated with 
-    a line in the file JanesFile.txt. There are two other approaches to removing 
-    this bookmark. 
-    <ul>
-      <li>Use <b>Remove Bookmark</b> in the marker bar of the JanesFile.txt editor. 
-        Remember, <b>Add Bookmark</b> was used <b></b>in the marker bar when the 
-        bookmark was first created.<br>
-        <img src="../images/Image54_bookmark_remove2.png" alt="Bookmark menu" border="0" ></li>
-      <li>Delete the bookmark (as was done above) by using <b>Delete</b> from 
-        the bookmark's popup menu in the Bookmarks view.</li>
-    </ul>
-    <p>Here is the second approach.&nbsp;</p>
-  </li>
-  <li> 
-    <P CLASS="Para">Ensure there is an editor open on JanesFile.txt.&nbsp;</P>
-    <P CLASS="Para">Although the editor doesn't actually need to be open, the 
-      editor update will be viewable as the bookmark is deleted.</P>
-  </li>
-  <li> 
-    <p CLASS="Head">In the Bookmarks view, select JanesFile.txt (the remaining 
-      bookmark). Click the Delete button <img src="../images/Image54_bookmark_del1.png" alt="Bookmark delete button" border="0" > 
-      on the view's toolbar. Notice that the bookmark is removed from the Bookmarks 
-      view and the JanesFile.txt editor.&nbsp; </p>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm
deleted file mode 100644
index 5aae71c..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging views and editors</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Rearranging views and editors</h2>
-<P CLASS="Para">This section will explain how to rearrange editors and views to 
-  customize the layout of the Workbench.</P>
-<P CLASS="Para"><b>Setup</b></P>
-<P CLASS="Para">Before rearranging the Workbench, a little housekeeping is required.</P>
-<ol>
-  <li>
-<P CLASS="Para">Start by choosing <b>Window &gt; Reset Perspective</b> and selecting <b>OK</b>. This will reset the
-current perspective to its original views and layout.</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Ensure there are editors open for JanesFile.txt and JanesText.txt. 
-      Close any other editors.</P>
-  </li>
-</ol>
-<P>The Workbench should now look like this:&nbsp;&nbsp;&nbsp; </P>
-
-
-<P>&nbsp;<img src="../images/Image55_reset.png" alt="Workbench after reset" border="0">
-</P>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm
deleted file mode 100644
index d39f1d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39c.htm
+++ /dev/null

@@ -1,86 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Drop cursors</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Drop cursors</h3>
-<P CLASS="Para"> Drop cursors indicate where it is possible to dock views in the 
-  Workbench window. Several different drop cursors may be displayed when rearranging 
-  views.</P>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-</THEAD>
-<TBODY>
-<TR>
-<TD height="38" valign="top" align="left">
-<P CLASS="Para">
-<img src="../images/drop_top_source.png" alt="Up arrow" border="0" >
-</P>
-</TD>
-      <TD height="38" valign="top" align="left"> <P CLASS="Para"> Dock above: 
-          If the mouse button is released when a dock above cursor is displayed, 
-          the view will appear above the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<P CLASS="Para">
-<img src="../images/drop_bottom_source.png" alt="Down arrow" border="0" >
-</P>
-</TD>
-      <TD height="38" valign="top" align="left"> <p CLASS="Para"> Dock below: 
-          If the mouse button is released when a dock below cursor is displayed, 
-          the view will appear below the view underneath the cursor.</p></TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<P CLASS="Para"><img src="../images/drop_right_source.png" alt="Right arrow" border="0" >
-</P>
-</TD>
-      <TD height="38" valign="top" align="left"> <p CLASS="Para"> Dock to the right: 
-          If the mouse button is released when a dock to the right cursor is displayed, 
-          the view will appear to the right of the view underneath the cursor.</p> 
-      </TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<img src="../images/drop_left_source.png" alt="Left arrow" border="0" >
-</TD>
-      <TD height="38" valign="top" align="left"> Dock to the left: If the mouse button 
-        is released when a dock to the left cursor is displayed, the view will 
-        appear to the left of the view underneath the cursor. </TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<img src="../images/drop_stack.png" alt="Stack icon" border="0" >
-</TD>
-      <TD height="38" valign="top" align="left"> Stack: If the mouse button is 
-        released when a stack cursor is displayed, the view will appear as a tab 
-        in the same pane as the view underneath the cursor. </TD>
-</TR>
-<TR>
-<TD height="38" valign="top" align="left">
-<img src="../images/drop_invalid_source.png" alt="Restricted icon" border="0" >
-</TD>
-      <TD height="38" valign="top" align="left"> Restricted: If the mouse button 
-        is released when a restricted cursor is displayed, the view will not dock 
-        there. For example, a view cannot be docked in the editor area. </TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm
deleted file mode 100644
index 4c1533f..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39d.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Rearranging views</h3>
-<p CLASS="Head"> The position of the Project Explorer (or any other) view in the Workbench window can 
-  be changed.</p>
-<ol>
-  <li> 
-    <p CLASS="Head"> Click in the title bar of the Project Explorer view and drag the 
-      view across the Workbench window. Do not release the mouse button yet.</p>
-  </li>
-  <li> 
-    <p CLASS="Head"> While still dragging the view around on top of the Workbench 
-      window, note that various drop cursors appear. These drop cursors (see previous 
-      section) indicate where the view will dock in relation to the view or editor 
-      area underneath the cursor when the mouse button is released. Notice also that
-      a rectangular highlight is drawn that provides additional feedback on where the
-      view will dock.</p>
-  </li>
-  <li> 
-    <P CLASS="Para"> Dock the view in any position in the Workbench window, and 
-      view the results of this action. </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click and drag the view's title bar to re-dock the view in 
-      another position in the Workbench window. Observe the results of this action. 
-    </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click and drag the view's title bar outside the Workbench window. Notice that
-      it becomes a "Detached" window (hosted in its own shell).
-    </P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Finally, drag the Project Explorer view over the Outline view. A 
-      stack cursor will be displayed. If the mouse button is released the Project Explorer 
-      will be stacked with the Outline view into a tabbed notebook.&nbsp;&nbsp;Please note that you
-      must grab the view tab, <b>NOT</b> the window title.  This is used only for repositoning the 
-      window containing the detached view.
-    </P>
-  </li>
-</ol>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm
deleted file mode 100644
index 3223706..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39e.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tiling editors</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Tiling editors</h3>
-<P CLASS="Para"> The Workbench allows for the creation of two or more sets of 
-  editors in the editor area. The editor area can also be resized but views cannot 
-  be dragged into the editor area.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Open at least two editors in the editor area by double-clicking 
-      editable files in one of the navigation views.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click and drag one of the editor's tabs out of the editor 
-      area. Do not release the mouse button.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that the restricted cursor displays if an attempt 
-      is made to drop the editor either on top of any view or outside the Workbench 
-      window.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Still holding down the mouse button, drag the editor over 
-      the editor area and move the cursor along all four edges as well as in the 
-      middle of the editor area, on top of another open editor. Notice that along 
-      the edges of the editor area the directional arrow drop cursors appear, 
-      and in the middle of the editor area the stack drop cursor appears.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Dock the editor on a directional arrow drop cursor so that 
-      two editors appear in the editor area.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Notice that each editor can also be resized as well as the 
-      entire editor area to accommodate the editors and views as necessary.</P>
-  </li>
-  <li> 
-    <p CLASS="Para"> It is important to observe the color of an editor tab (in 
-      the figure below there are two groups, one above the other)</p> 
-    <p CLASS="Para"><b>blue</b> - indicates that the editor is currently active</p>
-    <p CLASS="Para"><b>default </b>(gray on Windows XP) - indicates that the editor 
-      was the last active editor. If there is an active view, it will be the editor 
-      that the active view is currently working with. This is important when working 
-      with views like the Outline and Properties that work closely with the editor.</p></li>
-  <li> 
-    <P CLASS="Para"> Drag and dock the editor somewhere else in the editor area, 
-      noting the behavior that results from docking on each kind of drop cursor. 
-      Continue to experiment with docking and resizing editors and views until 
-      the Workbench has been arranged to satisfaction. The figure below illustrates 
-      the layout if one editor is dragged and dropped below another.</P>
-  </li>
-</ol>
-<P>&nbsp;<img src="../images/Image57_two_editors.png" alt="Two editors" border="0"><br>
-</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm
deleted file mode 100644
index 3da9963..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39f.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging tabbed views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Rearranging tabbed views</h3>
-<P CLASS="Para">In addition to dragging and dropping views on the Workbench the 
-  order of views can also be rearranged within a tabbed notebook.</P>
-<ol>
-  <li> 
-    <P CLASS="Para"> Choose <b>Window &gt; Reset Perspective</b> to reset the 
-      Resource perspective back to its original layout.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para">Click on the Outline title bar and drag it on top of one of 
-      the navigation views. The Outline will now be stacked on top of one of the 
-      navigation views.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Click the tab of the navigation views and drag it to the 
-      right of the Outline tab.</P>
-    <P CLASS="Para"><img src="../images/Image60_tabs.png" alt="tabs" border="0" ></P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Once the cursor is to the right of the Outline tab and the 
-      cursor is a stack cursor release the mouse button.</P>
-    <P CLASS="Para">Observe the Project Explorer tab is now to the right of the Outline 
-      tab.</P>
-    <P CLASS="Para"><img src="../images/Image60_tabs2.png" alt="tabs" border="0" ></P>
-  </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm
deleted file mode 100644
index 0108705..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-39g.htm
+++ /dev/null

@@ -1,119 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Maximizing and minimizing</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h3>Maximizing and minimizing elements of the eclipse presentation</h3>
-
-<p>
-The eclipse presentation provides a rich environment consisting of (in its basic form) an
-<i>Editor Area</i> (containing one or more stacks showing the open editors) surrounded by
-one or more <i>View Stacks</i> (each containing one or more views).These various parts compete
-for valuable screen real-estate and correctly managing the amount of screen given to each
-can greatly enhance your productivity within the IDE.
-</p>
-<p>
-The two most common mechanisms for managing this issue are 'minimize' (i.e. make me use as
-little space as possible) and 'maximize' (i.e. give me as much space as you can). The eclipse
-presentation provides a variety of ways to access these operations:</p>
-<ol>
-  <li>Using the minimize and maximize buttons provided on a stack's border</li>
-  <li>Selecting the 'Minimize' or 'Maximize' item on the context (right-click) menu for a stack</li>
-  <li>Double-clicking on a stack</li>
-  <li>Using 'Ctrl + M': this is a key binding for a command that will toggle the currently active
-part between its 'maximized' and its 'restored' (i.e. normal) states.</li>
-</ol>
-
-<P CLASS="Para">
-   <img src="../images/minmaxOptions.png" alt="Access to the minimize and maximize operations" border="0" >
-</P>
-
-<h4>Maximize:</h4>
-<p>
-It is desirable at times to focus your attention on one particular part to the exclusion of
-the others. The most popular candidate for this is, of course, maximizing the editor area in
-order to make as much of the display available for editing as possible (but there are workflows
-where it would make sense to focus on a view as well).
-</p>
-<p>
-As of 3.3 the default presentation implements the maximize behavior by minimizing all stacks
-<i>except</i> the one being maximized. This allows the maximized stack to completely occupy
-the main presentation while still allowing access any open views in your perspective by using
-the icons in their <i>Trim Stack</i> (the area around the edges of the window is called the 'trim').
-</p>
-<p>
-Also in 3.3 the behavior for managing the editor maximization has been changed to operate on
-the complete Editor Area (rather than simply maximizing the particular Editor Stack as is the
-case in the 3.0 and 2.1 presentations). This allows for 'compare' workflows which require the
-ability to see both files in a split editor area at the same time.
-</p>
-
-<h4>Minimize:</h4>
-<p>
-Another way to optimize the use of the screen area is to directly minimize stacks that are of no current
-interest. As of 3.3 the default presentation minimizing a stack will cause it to be moved into
-the trim area at the edges of the workbench window, creating a <i>Trim Stack</i>. View Stacks
-get minimized into a trim representation that contains the icons for each view in the stack:
-</p>
-<P CLASS="Para">
-   <img src="../images/TrimStack.png" alt="Trim representation of a View Stack" border="0" >
-</P>
-<p>
-The minimize behavior for the Editor Area is somewhat different; minimizing the Editor Area
-results in a trim stack containing only a placeholder icon representing the entire editor area
-rather than icons for each open editor (since in most cases all the icons would be the same, making
-them essentially useless).
-</p>
-<P CLASS="Para">
-   <img src="../images/EATrim.png" alt="Trim representation of the Editor Area" border="0" >
-</P>
-<p>
-If your particular workflow is such that you need to have more than one element (i.e. having the
-Editor Area <i>and</i> a View Stack in the presentation at the same time)
-you can still gain additional screen space by minimizing the stacks that aren't of current interest.
-This will remove them from the main presentation and place them on the outer edge of the workbench
-window as <i>Trim Stacks</i>,
-allowing more space for the remaining stacks in the presentation.
-</p>
-<p>
-<b>Note:</b> There are two ways to end up with a stack in the trim:</p>
-<ul>
-<li>Directly minimizing the stack</li>
-<li>As the result of another stack being maximized</li>
-</ul>
-
-<p>
-Depending on how the Trim Stack was created its behavior is different; when un-maximizing only those
-trim stacks that were created during the initial maximize will be restored to the main presentation
-while stacks that were independently minimized stay that way.
-</p>
-<p>
-<b><i>Tip:</i></b> This difference is important in that it allows you fine grained control over the presentation. While
-using maximize is a one-click operation it's an 'all or nothing' paradigm (i.e. no other stack is allowed
-to share the presentation with a maximized stack). While adequate for most tasks you may find yourself wanting to
-have the presentation show more than stack. In these scenarios don't maximize; minimize all the other stacks <i>except</i>
-the ones you want in the presentaton. Once you have it set up you can still subsequently maximize the editor area but
-the un-maximize will only restore the particular stack(s) that were sharing the presentation, not the ones you've
-explicitly minimized.
-</p>
-<h4>Normal Presentation</h4>
-<P CLASS="Para">
-   <img src="../images/EANormal.png" alt="Normal Presentation" border="0" >
-</p>
-
-<h4>Editor Area Maximized</h4>
-<P CLASS="Para">
-   <img src="../images/EAMaxed.png" alt="Editor Area Maximized" border="0" >
-</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm
deleted file mode 100644
index 9eea838..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Fast views</h2>
-<p CLASS="Head">Fast views are hidden views, which can be quickly made visible. 
-  They work the same as normal views, only when they are hidden they do not take 
-  up screen space on the Workbench window.&nbsp;</p>
-
-
-<P> This section we will explain how to convert the Project Explorer view into a fast 
-  view. </P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm
deleted file mode 100644
index 11e11da..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40a.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Creating fast views</h3>
-<p CLASS="Head">Fast views are hidden views, which can be quickly made visible. 
-  These instructions commence by creating a fast view from one of the navigation views 
-  and then explain how to use the view once it is a fast view.&nbsp;</p>
-<p CLASS="Head">There are two ways to create a fast view</p>
-<ul>
-  <li> Using drag and drop.</li>
-  <li> Using a menu operation available from the view System menu.</li>
-</ul>
-<p CLASS="Head">Create a fast view using drag and drop as follows.</p>
-<ol>
-  <li>
-    <P CLASS="Para"> In the Project Explorer view click on the title bar and drag it 
-      to the shortcut bar at the bottom left of the window.&nbsp;</P>
-  </li>
-  <li>
-    <P CLASS="Para"> Once over the shortcut bar, the cursor will change to a &quot;fast view&quot; 
-      cursor. Release the mouse button to drop the Project Explorer onto the shortcut 
-      bar. </P>
-<P CLASS="Para">The shortcut bar now includes a button for the Project Explorer fast view </P>
-<blockquote>
-<P CLASS="Para"><img src="../images/Image60_fast_view1.png" alt="Fast view" border="0" ></P>
-</blockquote>
-  </li>
-</ol>
-<P>To create a fast view using the second approach, start by popping up the context 
-  menu over the Project Explorer view's tab. From this menu, 
-  select <b>Fast View</b>. </P>
-
-
-<blockquote> 
-  <P><img src="../images/Image61_fast_options.png" alt="Project Explorer view menu" border="0"> 
-  </P>
-
-
-</blockquote>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm
deleted file mode 100644
index 87611f0..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-40b.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Working with fast views</h3>
-<p CLASS="Head">The Project Explorer has now been converted into a fast view. This section 
-  will demonstrate what can now be done with it.</p>
-<p CLASS="Head">Confirm that the shortcut bar at the bottom left of the window 
-  still has the Project Explorer view and looks like this:</p>
-<blockquote>
-  <p CLASS="Head"><img src="../images/Image60_fast_view1.png" alt="Fast view on shortcut bar" border="0" ></p>
-</blockquote>
-<ol>
-  <li> 
-    <P CLASS="Para">In the shortcut bar click on the Project Explorer fast view button.</P>
-  </li>
-  <li> 
-    <P CLASS="Para"> Observe the Project Explorer view slides out from the left side of the window.&nbsp; 
-    </P>
-    <P CLASS="Para"> <img src="../images/Image61_nav_fast.png" alt="Project Explorer view" border="0" ></P>
-  </li>
-  <li> 
-    <p CLASS="Head">The Project Explorer fast view can be used as it would be normally.&nbsp;&nbsp;To 
-      resize a fast view, move the mouse to the right edge of the fast view where 
-      the cursor will change to a double-headed arrow. Then hold the left mouse 
-      button down as the mouse is moved. </p>
-  </li>
-  <li> 
-    <P CLASS="Para"> To hide the fast view simply click on another view or editor 
-      or click on the <b>Minimize</b> button on the fast view's toolbar </P>
-    <P CLASS="Para"> <img src="../images/Image61_fast_minimize.png" alt="Minimize fast icon" border="0" > 
-    </P>
-    <P CLASS="Para">&nbsp; </P>
-    <P CLASS="Para"><b>Note:</b> If a file is opened from the a navigation view 
-      fast view, the fast view will automatically hide itself to allow the file 
-      to be worked with.</P>
-  </li>
-</ol>
-<P>To convert a fast view back to a regular view either: </P>
-<ul>
-  <li>Choose <b>Fast View</b> from the context menu of the icon in the top left 
-    corner of the view. </li>
-  <li>Drag the fast view icon from the tool bar, and drop it somewhere in the 
-    Workbench window. </li>
-</ul>
-
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm
deleted file mode 100644
index 96e0e22..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Perspectives</h2>
-<p class="Para" Type Label>A perspective defines the initial set and layout of
-views in the Workbench window. One or more perspectives can exist in a single
-Workbench window.&nbsp;&nbsp;</p>
-<p class="Para" Type Label>Perspectives can be opened in one of two ways:</p>
-<ul>
-  <li><p>In the same (existing) Workbench window.</p> </li>
-  <li><p>In a new Workbench window.</p></li> 
-</ul>
-<p class="Para" Type Label>Perspectives define visible action sets, which can 
-  be changed to customize a perspective. A perspective that is built in this manner 
-  can be saved, creating a custom perspective that can be opened again later.&nbsp;&nbsp;&nbsp;</p>
-<P CLASS="Para"> The Workbench window displays one or more perspectives. Each 
-  product determines initially what default perspective is displayed, in this 
-  example it is the Resource perspective. A perspective consists of views such 
-  as the Project Explorer as well as editors for working with resources. More than one 
-  Workbench window can be open at any given time.&nbsp; </P>
-<P CLASS="Para"> So far, only the Resource perspective (shown below) has been 
-  used in this tutorial. This section will explore how to open and work with other 
-  perspectives. </P>
-<P CLASS="Para"> A perspective provides a set of functionality aimed at accomplishing 
-  a specific type of task, or working with a specific type of resource.&nbsp;&nbsp; 
-</P>
-<P CLASS="Para">
-<img src="../images/Image1.png" alt="Eclipse Workbench" border="0" > </P>
-<P>&nbsp;</P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm
deleted file mode 100644
index 4934e04..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43b.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-New perspectives</h3>
-<p CLASS="Head">There are several ways to open a new perspective within
-this Workbench window:</p>
-<ul>
-  <li>
-    Using the Open Perspective button 
-    <img src="../images/Image70_shortcut2.png" alt="Open Perspectives" border="0" >
-    on the shortcut bar.</li>
-  <li>
-    Choosing a perspective from the <b>Window &gt; Open Perspective</b> menu.&nbsp;</li>
-</ul>
-<p>To open one by using the shortcut bar button:</p>
-<ol>
-  <li> 
-    <p CLASS="Para">Click on the Open Perspective button <img src="../images/Image70_shortcut2.png" alt="Open Perspectives" border="0" >.&nbsp;</p>
-  </li>
-  <li> 
-    <p CLASS="Head">A menu appears showing the same choices as shown on the <b>Window 
-      &gt; Open Perspective</b> menu. Choose <b>Other</b> from the menu.</p>
-    <blockquote> 
-      <p CLASS="Head"> <img src="../images/Image70_shortcut3.png" alt="Open Perspective Menu" border="0" ></p>
-    </blockquote>
-  </li>
-  <li> 
-    <p CLASS="Para">In the Select Perspective dialog choose <b>Debug</b> and click 
-      <b>OK</b>.</p>
-    <blockquote> 
-      <p CLASS="Para"> <img src="../images/Image70_select_pers.png" alt="Select Perspective" border="0" ></p></blockquote>
-    <p CLASS="Para">The Debug perspective is displayed.&nbsp;&nbsp;</p>
-  </li>
-  <li> 
-    <p CLASS="Para">There are several other interesting things to take note of.</p>
-    <ul>
-      <li> 
-        <p CLASS="Para">The title of the window now indicates that the Debug perspective 
-          is in use.</p></li>
-      <li> 
-        <p CLASS="Para">The shortcut bar contains several perspectives, the original 
-          Resource perspective, the new Debug perspective and a few others.&nbsp;The 
-          Debug perspective button is pressed in, indicating that it is the current 
-          perspective.</p></li>
-      <li> 
-        <p CLASS="Para">To display the full name of the perspective right click 
-          the perspective bar and check <strong>Show Text</strong>.<br>
-          <img src="../images/Image70_shortcut4.png" alt="Debug Perspective" border="0" ></p></li>
-    </ul>
-  </li>
-  <li> 
-    <p CLASS="Para">In the shortcut bar, click on the Resource perspective button. 
-      The Resource perspective is once again the current perspective. Notice that 
-      the set of views is different for each of the perspectives.&nbsp;</p>
-  </li>
-</ol>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm
deleted file mode 100644
index 40d1473..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43c.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New windows</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-New windows</h3>
-<p CLASS="Head">As well as opening a perspective inside the current Workbench 
-  window, new perspectives can also be opened in their own window.</p>
-<p CLASS="Head">By default, new perspectives are opened in the current window. 
-  This default behavior can be configured using <b>Window &gt; Preferences &gt; 
-  General &gt; Perspectives</b>.</p>
-<blockquote> 
-  <P>&nbsp;<img src="../images/Image71_pers_pref.png" alt="Perspective preferences"> 
-  </P>
-
-
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm
deleted file mode 100644
index 70d33d5..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43e.htm
+++ /dev/null

@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Saving perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Saving
-perspectives</h3>
-<P CLASS="Para">This tutorial has demonstrated how to add new views to the perspective, 
-  rearrange the views and convert views into fast views. The Workbench also allows 
-  this layout to be saved for future use.</P>
-<ol>
-  <li> 
-    <p CLASS="Para">In the shortcut bar click on the Resource perspective.&nbsp;The 
-      Resource perspective is now active.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Drag the Outline view and stack it with one of the navigation 
-      views.</p></li>
-  <li> 
-    <p CLASS="Para">Choose <b>Window &gt; Save Perspective As...</b></p>
-  </li>
-  <li> 
-    <p CLASS="Para">The Save Perspective As dialog allows for an existing perspective 
-      to be redefined or for a new perspective to be created.</p> 
-    <p CLASS="Para">Click <b>OK</b> to update the Resource perspective and <b>Yes</b> 
-      to the subsequent confirmation dialog. The new perspective layout will be 
-      used if the perspective is reset or if a new one is opened.</p>
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image71_pers_save.png" alt="Saving Perspective" border="0" ></p>
-    </blockquote>
-  </li>
-  <li> 
-    <P CLASS="Para">In the Resource perspective move the Outline view so that 
-      it is now stacked with the Tasks view.</P>
-  </li>
-  <li> 
-    <p CLASS="Para">Choose <b>Window &gt; Reset Perspective</b>. Notice the Outline 
-      view is stacked with the navigation view. Originally when the Workbench 
-      was first started it was below the navigation view, but because the perspective 
-      was saved with the navigation view and Outline stacked, it now considers 
-      this its initial layout.&nbsp;&nbsp;</p>
-  </li>
-  <li> 
-    <P CLASS="Para">Choose <b>Window &gt; New Window</b> to open a second window 
-      showing the resource perspective. Observe that it uses the newly saved layout.&nbsp;</P>
-  </li>
-  <li> 
-    <P CLASS="Para">Close the second window.</P>
-  </li>
-</ol>
-<p CLASS="Para">While the Resource perspective has been changed, there is a way 
-  to get back the original layout. To reset the Resource perspective to its original 
-  layout:</p>
-<ol>
-  <li> 
-    <p CLASS="Para">Choose <b>Window &gt; Preferences</b>.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Expand <b>General</b> and select <b>Perspectives</b>.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Select <b>Resource (default) &gt; Make Default</b> and then 
-      click <b>OK</b>.</p> 
-    <blockquote> 
-      <p CLASS="Para"><img src="../images/Image71_pers_reset.png" alt="Reset Perspective" border="0"></p></blockquote>
-  </li>
-  <li> 
-    <p CLASS="Para">Any changes to the saved state of the perspective has now 
-      been undone. To update the current copy of the Resource perspective that 
-      is being worked with, also choose <b>Window &gt; Reset Perspective</b> from 
-      the Workbench's menu bar.&nbsp;</p>
-  </li>
-</ol>
-
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm
deleted file mode 100644
index 1b2abc7..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-43f.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Hiding Menu and Tool Bar Items</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Turning menu and tool bar items on and off</h3>
-<p CLASS="Para">In addition to configuring the layout of a perspective you can 
-  also control several other key aspects of a perspective. These include:</p>
-<ul>
-  <li> The visibility of individual menu and tool bar items. </li>
-  <li> The availability of command groups (groupings of menu items, tool bar 
-       items and key bindings).</li>
-  <li> The items in the <b>New</b>, <b>Window &gt; Open Perspective</b> and
-       <b>Window &gt; Show View</b> menus.</li>
-</ul>
-
-<p CLASS="Para">Try turning off a tool bar item:</p>
-<ol>
-  <li>
-    <p CLASS="Para">Select <b>Window &gt; Customize Perspective...</b></p></li>
-  <li><p CLASS="Para">Select the <b>Tool Bar Visibility</b> tab.</p></li>
-  <li><p CLASS="Para">Expand the <b>File</b> item.</p></li>
-  <li><p CLASS="Para">Uncheck <b>Print</b> and click <b>OK</b>.</p>
-        <blockquote>
-          <img src="../images/Image71_dialog_toolbar.png" alt="Turning off the 'Print' tool bar item" border="0" >
-        </blockquote>
-      </li>
-  <li><p CLASS="Para">Observe that the toolbar no longer includes the
-    <b>Print</b> icon.</p>
-    <table>
-      <tr>
-        <td align="center"><b>Before</b></td>
-        <td align="center"><b>After</b></td>
-      </tr>
-      <tr>
-        <td>
-          <img src="../images/Image71_file_toolbar_before.png" alt="Before picture for the 'Print' tool bar item (visible)" border="0" >
-        </td>
-        <td>
-        	<img src="../images/Image71_arrow.png" alt="Arrow" border="0" >
-        </td>
-        <td>
-          <img src="../images/Image71_file_toolbar_after.png" alt="After picture for the 'Print' tool bar item (visible)" border="0" >
-        </td>
-      </tr>
-    </table>
-  </li>
-</ol>
-
-<p CLASS="Para">Try turning off a menu item:&nbsp;</p>
-<ol>
-  <li>
-    <p CLASS="Para">Select <b>Window &gt; Customize Perspective...</b></p></li>
-  <li><p CLASS="Para">Select the <b>Menu Visibility</b> tab.</p></li>
-  <li><p CLASS="Para">Expand the <b>File</b> item.</p></li>
-  <li><p CLASS="Para">Uncheck <b>Print</b> and click <b>OK</b>.</p>
-      <blockquote>
-        <img src="../images/Image71_dialog_menu.png" alt="Turning off the 'Print' menu item" border="0" >
-      </blockquote>
-    </li>
-  <li><p CLASS="Para">Observe that the <b>File</b> menu no longer includes the
-    <b>Print</b> item.</p>
-    <table>
-      <tr>
-        <td align="center"><b>Before</b></td>
-        <td align="center"><b>After</b></td>
-      </tr>
-      <tr>
-        <td>
-          <img src="../images/Image71_file_menu_before.png" alt="Before picture for the 'Print' menu item (visible)" border="0" >
-        </td>
-        <td>
-        	<img src="../images/Image71_arrow.png" alt="Arrow" border="0" >
-        </td>
-        <td>
-          <img src="../images/Image71_file_menu_after.png" alt="After picture for the 'Print' menu item (visible)" border="0" >
-        </td>
-      </tr>
-    </table>
-  </li>
-</ol>
-
-<p CLASS="Para">After experimenting with the other options on the Customize 
-   Perspective dialog, choose <b>Window &gt; Reset Perspective</b> to return 
-   the perspective to its original state.&nbsp; </p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm
deleted file mode 100644
index 4db14df..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Comparing</h2>
-<P CLASS="Para"> The Workbench allows for the comparison of multiple resources 
-  and for the presentation of the results in a special compare editor. </P>
-<P CLASS="Para"><b>Setup</b> </P>
-<P CLASS="Para">Before commencing with compare a few files must be created. This 
-  will also be a good time to recap some of the basic features that have already 
-  been introduced.</P>
-<ol>
-  <li> 
-    <p CLASS="Para">Start by selecting all of the projects in one of the navigation 
-      views and deleting them by using <b>Delete</b> on the pop-up menu.</p>
-  </li>
-  <li> 
-    <p CLASS="Para">Create a new simple project using <b>File &gt; New &gt; Project</b>. 
-      Be sure to give the project a distinct name by typing unique name as the 
-      name of the new project (for example, &quot;JaneQUserCompare&quot;). Do 
-      not use spaces or special characters in the project name.</p></li>
-  <li> 
-    <p CLASS="Para">Use the project's pop-up menu to create a file called file1.txt.</p>
-    <p CLASS="Para">In the editor for file1.txt type the following lines of text 
-      and save the file:</p>
-    <blockquote> 
-      <p CLASS="Para"><i>This is line 1.<br>
-        This is line 2.<br>
-        This is line 3.<br>
-        This is line 4.<br>
-        This is line 5.</i></p>
-    </blockquote>
-  </li>
-  <li> 
-    <p CLASS="Para">In one of the navigation views select file1.txt and use Ctrl+C 
-      to copy the file.</p></li>
-  <li> 
-    <p CLASS="Para">Use Ctrl+V (Paste) to create the copy. In the name conflict 
-      dialog which appears, rename the file to file2.txt.</p></li>
-</ol>
-<p>(On the Mac, use Command+C and Command+V.)</p>
-<P>There are now two identical files, file1.txt and file2.txt. </P>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm
deleted file mode 100644
index 13f6c17..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52c.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Simple compare</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Simple compare</h3>
-<p CLASS="Head"> In one of the navigation views select file1.txt and file2.txt 
-  choose <b>Compare With &gt; Each Other</b> from the context menu.&nbsp;</p>
-<p CLASS="Head"> A dialog will appear indicating that the two files are the same.&nbsp;</p>
-<p CLASS="Head"><img src="../images/Image80_compare.png" alt="Compare popup" border="0" ></p>
-<p CLASS="Head">Edit file1.txt as follows:</p>
-<ul>
-  <li>
-    delete&nbsp; line 1&nbsp; &quot;<i>This is line 1.&quot;</i></li>
-  <li>
-    change line 3 to be &quot;This is a much better line
-    3.&quot;</li>
-  <li>
-    insert a line 4a (before line 5) that reads &quot;This is
-    line 4a and it is new&quot; </li>
-</ul>
-<p CLASS="Head">The file (file1.txt) should now read as follows:&nbsp; </p>
-<blockquote>
-  <p><i>This is line 2.<br>
-  This is a much better line 3.<br>
-  This is line 4.<br>
-  This is line 4a and it is new<br>
-  This is line 5.</i></p>
-</blockquote>
-<p>Save the contents of the file by choosing <b>File &gt; Save</b> (or pressing
-Ctrl+S).</p>
-<p>To compare the files, once again select file1.txt and file2.txt and choose 
-  <b>Compare With &gt; Each Other</b> in the navigation view context menu.</p>
-<p>A special compare editor opens. The next section will explain how to use this 
-  compare editor.</p>
-<blockquote> 
-  <P><img src="../images/Image80_compare_editor.png" alt="Compare Editor" border="0" > 
-  </P>
-
-
-</blockquote>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm
deleted file mode 100644
index af228da..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52d.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Understanding the comparison</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Understanding the comparison</h3>
-<p CLASS="Head">Comparing file1.txt and file2.txt resulted in the following
-compare editor. The left side shows the contents of file1.txt and the right side
-shows the contents of file2.txt. The lines connecting the left and right panes
-indicate the differences between the files.</p>
-<p CLASS="Head">If more room is needed to look at the comparison, the editor tab 
-  can be double clicked to maximize the editor.&nbsp;</p>
-<p CLASS="Head">
-<img src="../images/Image80_compare_editor2.png" alt="Compare editor" border="0" >&nbsp;&nbsp;</p>
-<p CLASS="Head"> The numbered changes on the left side of the difference editor 
-  are as follows:</p>
-<ul>
-  <li> Starting with the top line (in the left pane) the difference bar (in the 
-    area of the blue circle) indicates something is missing from the very top 
-    of the left file. Follow the difference band (see #1) to the right file. It 
-    contains &quot;This is line 1&quot; .</li>
-  <li> The next line &quot;This is line 2.&quot; is white indicating it matches 
-    the right file.</li>
-  <li> Moving onto the next line (colored in the background color), see that the 
-    left file and right file have different contents for this line (see #2).</li>
-  <li> The next line (This is line 4) is once again in white, so it can be skipped.</li>
-  <li> The next line exists in the left file&nbsp; but since it is in the background 
-    color its difference bar can be followed to the right (see #3) and notice 
-    that the right file does not contain the line (see red circle).</li>
-</ul>
-<p CLASS="Head">Initially the compare editor might seem a bit daunting but when 
-  simply working down the left side and focusing on the items marked as gray, 
-  and those items missing from the left side, it turns out not to be as tricky 
-  as it first seems.</p> 
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm
deleted file mode 100644
index 1612100..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-52e.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with the comparison</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>
-Working with the comparison</h3>
-<p CLASS="Head">Comparing file1.txt and file2.txt resulted in the following compare 
-  editor. This section demonstrates how to use the compare editor to resolve the 
-  differences between the two files.</p>
-<p>
-<img src="../images/Image80_compare_editor.png" alt="Compare editor" border="0" ></p>
-<p>There are two parts to the compare editor's local toolbar. Move to the next 
-  or previous change using the right group of local toolbar buttons.</p>
-<blockquote>
-<p>
-<img src="../images/Image80_compare_editor3.png" alt="Compare buttons" border="0" ></p>
-</blockquote>
-<ol>
-	<li>
-	<p CLASS="Para">Click the <b>Select Next Change</b> button <img
-		src="../images/next_change_nav.gif" alt="Compare editor next button"
-		border="0">. Observe how it selects the next difference.</p>
-	</li>
-	<li>
-	<p CLASS="Para">Click the <b>Select Next Change</b> button a second time to go
-	to the next change.</p>
-	</li>
-	<li>
-	<p CLASS="Para">Click the <b>Select Previous Change</b> button.</p>
-	</li>
-</ol>
-<p>To merge changes from the left file to the right file and vice versa use the 
-  left group of local toolbar buttons. There are four types of merges that can 
-  be performed:</p>
-<ul>
-  <li>Copy whole document from left to right.</li>
-  <li>Copy whole document from right to left.</li>
-  <li>Copy current change from left to right.</li>
-  <li>Copy current change from right to left.</li>
-</ul>
-<p> Typically the copy whole document actions are used when the entire file on 
-  either the left or right can just be replaced by the contents of the other file.</p>
-<p> The Copy current change buttons allow a single change to be merged.</p>
-<ol>
-  <li>
-        <p CLASS="Para">Ensure that the second difference is selected (as shown
-        below):</p>
-        <p CLASS="Para">
-        <img src="../images/Image80_compare_change2.png" alt="Compare editor" border="0" ></p>
-        </li>
-  <li>
-        
-    <p CLASS="Para">Click&nbsp;<strong>Copy Current Change from Right to Left 
-      </strong><img src="../images/copycont_l_co.gif" alt="Compare editor right to left button" border="0">. 
-      Observe that the selected text from the right file is copied to the left 
-      file.</p> 
-    <p CLASS="Para"><img src="../images/Image80_compare_after.png" alt="Compare editor" border="0" ></p>
-      </li>
-  <li>
-        
-    <p CLASS="Para">Close the compare editor and choose <b>Yes</b> to save the 
-      changes. Alternatively, save the changes by choosing <b>File &gt; Save</b> 
-      (Ctrl+S).</p>
-      </li>
-</ol>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm
deleted file mode 100644
index cd57290..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<LINK REL="STYLESHEET" HREF="team-cvs.css" CHARSET="ISO-8859-1" TYPE="text/css">
-
-<title>Local history</title>
-
-</HEAD>
-<BODY>
-<h2>Local history</h2>
-<p> Every time an editable file is saved in the Workbench, the Workbench 
-  updates the local history of that file and logs the changes that have been made. 
-  The local history of a file can then be accessed and a previously saved copy 
-  of the file can be reverted to, as long as the desired state is recent enough 
-  in the save history.</p>
-<ol>
-  <li class="Steps">Create a new file named <em class="FileName">sampleFile.txt</em>.
-  </li>
-  <li class="Steps">In the editor for <em class="FileName">sampleFile.txt</em> modify the file by adding the line
-     &quot;change1&quot; and saving the file.
-  </li>
-  <li class="Steps">Repeat this by entering a new line &quot;change2&quot; and saving it again.
-  </li>
-  <li class="Steps">Add a third line &quot;change3&quot; and save it again. </li>
-  <li class="Steps">Right-click the file in a navigation view (e.g. the Project Explorer) and
-     select <em class="UILabel">Team &gt; Show Local History</em>.
-  <p><em>Note:</em> Repository tooling may override the <em class="UILabel">Team &gt; Show Local History</em>
-  operation to provide a unified history for a file. The Eclipse CVS client does override this action. 
-  To get the history for 
-  a file in a project that is shared with CVS, you will need to right-click the file and select
-  <em class="UILabel">Team &gt; Show History</em>. See 
-  <a href="qs-70_workingWithHistory.htm">Working with CVS History</a> for more details about the
-  CVS history of a file.</p>
-  </li>
-  
-  <li class="Steps">The History view opens and shows the history for the file.
-  <img class="Big" src="../images/localHistoryView.png" alt="Local History view" border="0">
-  </li>
-  <li class="Steps">The top entry in the view represents the current contents of the file.
-  The next represents the previous contents and so on.
-  Right-click on the previous entry and select <em class="UILabel">Compare Current with Local</em>
-  to open a Compare editor that displays the differences between 
-      the Workbench file and the specific copy of the file selected in the local 
-      history.
-  <img class="Big" src="../images/localHistoryCompare.png" alt="Local History Compare Editor" border="0">
-  </li>
-  <li class="Steps">Right-click on the previous entry again and select <em class="UILabel">Get Contents</em>. 
-  This replaces the Workbench's copy of
-  <em class="FileName">sampleFile.txt</em> with the chosen local history item.
-  </li>
-  <li class="Steps">Observe that the <em class="FileName">sampleFile.txt</em> editor now contains two lines.
-  </li>
-</ol>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm
deleted file mode 100644
index 1ed0dbf..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-55b.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Exiting the Workbench</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>
-Exiting the Workbench</h2>
-<P CLASS="Para"> Each time the Workbench is exited, the Workbench is automatically 
-  saved, including all open perspectives and windows. The next time the Workbench 
-  is reopened, it will appear exactly as it was when it was last closed.</P>
-<p> To exit the Workbench, select <b>File &gt; Exit</b> from the menu bar or close 
-  the workbench with the window close button (x). When the latter option is used 
-  a prompt will ask if you really wish to exit the workbench. </p>
-<p><strong>Note: </strong>This dialog also presents an option to turn off the 
-  prompting. To turn it back on, select <strong>Window &gt; Preferences</strong> 
-  from the main Workbench menu bar, in the Preferences Dialog select <strong>General 
-  &gt; Startup and Shutdown</strong> and check Confirm exit when closing last 
-  window.</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm
deleted file mode 100644
index 67e68bc..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60_team.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Team CVS tutorial</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Team CVS tutorial</H1>
-<P>This chapter will explain how to use the CVS team capabilities built into the 
-  Workbench. The steps in this chapter are team oriented; it will be difficult 
-  to complete these tutorials if others are not simultaneously working through 
-  this chapter. </P>
-
-
-<P>You will learn how to work on a project and then commit 
-  changes to the repository for others on the team to use. By continuing to work 
-  on the project alongside other users, this section will demonstrate how to commit 
-  resources that other users may be simultaneously working on, and how to update 
-  a workspace with changes others make in the project. </P>
-<P>Remember, before getting started, that you need to entice at least one co-worker into working 
-  through these steps as well. Another option is to start up two Eclipse instances
-  at once and step through both roles yourself.</P>
-
-
-<UL CLASS="UnorderedList">
-
-</UL>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm
deleted file mode 100644
index 971e302..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-60a_setup.htm
+++ /dev/null

@@ -1,27 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting up a CVS repository</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2> Setting up a CVS repository</h2>
-<P CLASS="Para">
-A repository is a persistent store that coordinates multi-user access to the
-resources being developed by a team. The Workbench comes with CVS support
-built-in. The CVS server is available at <a href="http://ximbiot.com/cvs/" target="_blank">http://ximbiot.com/cvs/</a>.&nbsp;</P>
-<P CLASS="Para"> Refer to this site for information on how to install and configure 
-  a CVS repository including user access and passwords.</P>
-<p>In order to continue with this tutorial, access to a CVS repository is required.</p>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm
deleted file mode 100644
index f34da93..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61c_offline.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Starting offline</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h2>Starting offline</h2>
-  
-<P CLASS="Para">The team CVS tutorial will start by working offline and creating 
-  a simple project. Once the project is created, instructions will be given explaining 
-  how to commit it to the repository.&nbsp;</P>
-<ol>
-  <li> 
-   Create a new &quot;General&quot; project using <b>File &gt; 
-   New &gt; Project &gt; General &gt; Project</b>. Use a unique name as the project name (e.g. JanesTeamProject).&nbsp; 
-  </li>
-  <li>Create a folder named folder1. </li>
-  <li>Create two text files (.txt) in folder1 called&nbsp; file1.txt and file2.txt. 
-    Their contents should be as follows: 
-    <p>file1.txt</p>
-    <blockquote> 
-      <p><i>This is the contents<br>
-        of file 1.</i></p>
-    </blockquote>
-    <p>file2.txt</p>
-    <blockquote> 
-      <p><i>File2 is a small file&nbsp;&nbsp;<br>
-        with simple text.</i></p>
-    </blockquote>
-    <p>The navigation view should now appear as follows:</p>
-    <blockquote> 
-      <p> <img src="../images/Image82_nav.png" alt="Project Explorer view" border="0"></p>
-    </blockquote>
-  </li>
-</ol>
-
-
-<P>The project can be continued within this mode but unless the project is committed 
-  into the repository, others on the team will be unable to work on the project 
-  as well. </P>
-
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm
deleted file mode 100644
index 53a18d3..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repoloca.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Sharing the project</title>
-</head>
-<body bgcolor="#ffffff">
-<h2> Sharing the project</h2>
-<div class="Subtopic">Now that a project has been created in the
-workspace you can make it available to other Team members. To do this
-the following steps will have to occur:<br>
-<br>
-<ol>
-  <li>Create a CVS location identifying the team's shared CVS
-repository.<br>
-    <br>
-  </li>
-  <li>Share the project with the CVS location and commit the changes.<br>
-  </li>
-</ol>
-</div>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm
deleted file mode 100644
index 605b75d..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61d_repolocb.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Specifying a repository location</title>
-</head>
-<body bgcolor="#ffffff">
-<h3>
-Specifying a repository location</h3>
-<p class="Head">You must specify an available repository before it
-is possible to share the project with others.
-</p>
-<ol>
-  <li>Open the CVS Repository Exploring perspective. The top left view
-shows all of the CVS repositories that are currently being worked with.
-As you can see, the view is empty, meaning a repository still needs to
-be specified.<br>
-    <br>
-  </li>
-  <li>In the context menu of the CVS Repositories view choose <b>New
-&gt;&nbsp;Repository Location</b>.
-    <blockquote>
-      <blockquote>
-        <p> <img  border="0"
- alt="CVS Repositories view" src="../images/Image82_repo_new.png"></p>
-      </blockquote>
-    </blockquote>
-  </li>
-  <li>In the CVS Repository Location wizard, the location of the
-repository and the login information needs to be filled in. You may need
-assistance from a repository administrator in order to fill in the necessary information.
-    <blockquote>
-      <p> <img  border="0"
- alt="Add CVS Repository dialog" src="../images/Image82_repo_new3.png"></p>
-    </blockquote>
-  </li>
-  <li>
-    <p class="Para"> In the <b> Host </b> field, type the address of
-the host (for example, &quot;teamsamples.com&quot;).<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para"> In the <b> Repository path </b> field, type the
-path for the repository at the host address (for example,
-"/home/cvsroot/repositoryName").<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para">In the <b> User </b> field, type the user name
-under which to connect.<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para">In the <b>Password</b> field, type the password.<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para"> In the <b> Connection type </b> field, select
-the type of CVS connection for the repository (The default is pserver).<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para"> Leave<b> Use Default Port</b> enabled. <br>
-    <br>
-    </p>
-  </li>
-  <li>By default the <b>Validate Connection on Finish<b> option </b></b>is
-checked. <br>
-    <br>
-  </li>
-  <li>
-    <p class="Para"> Click <b>Finish</b> when done.</p>
-    <p class="Para"> Since <b>Validate location on finish </b>was
-checked,<b> </b>the wizard will now attempt to validate the
-information by connecting to the repository. In doing so it may prompt
-for a password. <strong>Note: </strong>The repository connection is
-only used to validate the information.<br>
-    <br>
-    </p>
-  </li>
-  <li>
-    <p class="Para">Observe that the CVS Repositories view now shows
-the new repository location.</p>
-    <p class="Para"> <img  border="0"
- alt="CVS Repositories view" src="../images/Image82_repo_view1.png"></p>
-  </li>
-</ol>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm
deleted file mode 100644
index fa92e56..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61e_whatisloc.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Repository locations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h3>Repository locations</h3>
-<DIV CLASS="Subtopic">
-
-  <p CLASS="Para">Now that a new repository location has been added to the CVS 
-    Repositories view, the following will explain what a repository location is 
-    or, more importantly, what it isn't.</p>
-  <p CLASS="Para">A repository location is not an actual live connection. Instead, 
-    it is a description of where the repository is located. At a later time, when 
-    instructions are given explaining how to commit work to the repository or 
-    update with work done by others, the Workbench will create a connection based 
-    on this location information. Connections will be opened and closed as required 
-    when performing CVS team operations, and those connections will be based on 
-    the information provided in the repository location. </p>
-  <p CLASS="Para">When disconnected from the network the CVS Repositories view 
-    continues to display the list of known repository locations. In addition, 
-    the projects themselves will still know the repository location they are associated 
-    with.</p> 
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm
deleted file mode 100644
index 5d3df11..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-61f_syncproject.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Sharing a project</title>
-</head>
-<body bgcolor="#ffffff">
-<h3> Sharing a project</h3>
-<p class="Para"> Now that a project has been created and a repository
-location has been specified, the project can be made available to other
-team members.</p>
-<ol>
-  <li>
-    <p class="Para"> In one of the navigation views select the project
-JanesTeamProject.</p>
-  </li>
-  <li>
-    <p class="Para">From the project's context menu choose <b>Team
-&gt; Share Project</b>. If more than one repository provider is
-installed, select <strong>CVS </strong>and select <strong>Next</strong>.</p>
-  </li>
-  <li>
-    <p class="Para"> In the sharing wizard page, select the location
-that was previously created.</p>
-    <blockquote>
-      <p><img  border="0"
- alt="Set Project Sharing" src="../images/Image82_repo_sync1.png"></p>
-    </blockquote>
-  </li>
-  <li>The next page will ask you the module name to create on the
-server. Simply use the default value and use the name of the project
-you are sharing. Click <span style="font-weight: bold;">Next</span>.<br>
-    <br>
-    <div style="text-align: left; margin-left: 40px;"><img alt="Set Module Name" src="../images/Image82_repo_sync2.png">
-<br>
-    </div>
-    <br>
-  </li>
-  <li>The next page will allow you to see the files that are going to
-be shared with your team. The arrows with the plus sign show that the
-files are new outgoing additions. They have never existed on the server
-yet. <br>
-    <br>
-    <div style="margin-left: 40px;"><img alt="File sharing preview" src="../images/Image82_repo_team.png">
-</div>
-  </li>
-  <li>Press <span style="font-weight: bold;">Finish</span> and you will be prompted 
-    to commit the files. Enter a commit comment to describe the commit you are 
-    making. You can enter anything you like. Press <strong>Finish</strong> when 
-    you are done and the files will be committed.<br>
-  </li>
-  <li>Now you have shared the project and all the files have been
-committed to the CVS repository. Others can now see your files!<br>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm
deleted file mode 100644
index 3be859d..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64a_another.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Working with another user</title>
-</head>
-
-<body>
-<h2>Working with another user</h2>
-
-<p>Instructions were given explaining how to create a project and
-commit it to the repository. First a repository location was specified.
-Next the project was shared with that location and the HEAD branch and
-the resources were added then committed.</p>
-
-<p>The repository currently contains the project and the two files
-that were committed (<em class="FileName">file1.txt</em> and <em class="FileName">file2.txt</em>). </p>
-<p>It's time to find that co-worker (let's call him Fred) to work
-through some steps with you (for the remainder your name is Jane). This
-section will demonstrate how two
-people can work on the same project and simultaneously commit changes
-to the repository. Specifically, the following actions will be taken: </p>
-<ul>
-  <li>Fred will import the project to his Workbench</li>
-  <li>Fred will make changes to <em class="FileName">file1.txt</em> and <em class="FileName">file2.txt</em>.</li>
-  <li>You will update these new changes and also add a new file called
-<em class="FileName">file3.txt</em>.</li>
-  <li>Fred will make more changes to some files while you change the
-same files. Fred will release his changes first.
-  </li>
-  <li>You will have to resolve the conflicts between files that you
-both changed.</li>
-</ul>
-Here is some terminology commonly used to describe changes:<br>
-<table border="0" cellspacing="0" cellpadding="3" width="568">
-  <tbody>
-    <tr>
-      <td valign="top" width="71" align="left"> <b>incoming</b> </td>
-      <td valign="top" width="481" align="left">Changes that are in the
-repository, which you have not yet updated to. </td>
-    </tr>
-    <tr>
-      <td valign="top" width="71" align="left"> <b>outgoing</b> </td>
-      <td valign="top" width="481" align="left">Changes that you are
-committing. </td>
-    </tr>
-    <tr>
-      <td valign="top" width="71" align="left"> <b>conflict</b> </td>
-      <td valign="top" width="481" align="left">Both you and the
-repository have modifications to the same resource. </td>
-    </tr>
-  </tbody>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm
deleted file mode 100644
index 4853b26..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredadd.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Checking out a project</title>
-</head>
-
-<body>
-<h3> Checking out a project</h3>
-<p>Coworker Fred has several tasks in front of him:&nbsp;</p>
-<ul>
-  <li>Fred will import the project that Jane committed to the CVS
-repository into his Workbench.</li>
-  <li>Fred will make changes to <em class="FileName">file1.txt</em> and <em class="FileName">file2.txt</em>.</li>
-  <li>Fred will synchronize and commit his outgoing changes to the two
-files.</li>
-</ul>
-<p>Fred's first step is to import the project into his workspace as
-follows:</p>
-<ol>
-  <li class="Steps">Run the import wizard via the 
-     <em class="UILabel">File &gt; Import</em> menu item.
-     <img class="Big" src="../images/Image82_import_project_fred.png" alt="Screenshot of Import type selection">
-  </li>
-  <li class="Steps">Select the <em class="UILabel">Projects from CVS</em> 
-  item and press <em class="UILabel">Next</em>.
-  </li>
-  <li class="Steps">Create a repository location as described when Jane <a
- href="qs-61d_repolocb.htm">created a repository</a>.
-  </li>
-  <li class="Steps">On the next page select the "Use an existing module" radio button
-     and wait while the repository is contacted.
-     <img class="Big" src="../images/Image82_import2_project_fred.png" alt="Screenshot of CVS module selection page">
-  </li>
-  <li class="Steps">From the list of available projects, select <em class="ProjectName">JanesTeamProject</em>
-     and press <em class="UILabel">Finish</em>. A progress dialog will
-     appear showing the progress of the import operation.<br>
-    <img class="Big" src="../images/Image82_import3_project_fred.png" alt="Screenshot of progress dialog">
-  </li>
-  <li class="Steps">Open one of the navigation views and observe that it now includes
-     the project <em class="ProjectName">JanesTeamProject</em>.
-     Notice that there are CVS decorators indicating the file revisions, the
-      repository name, and the file types.
-      <img class="Big" src="../images/Image82_import4_project_fred.png" alt="Screenshot of Fred's Project Explorer after checkout">
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm
deleted file mode 100644
index 86d9e7d..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64b_fredmod.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Another user making changes</title>
-</head>
-
-<body>
-<h3>Another user making changes</h3>
-<p>Now that Fred has the project in his Workbench he needs
-to modify several of the files and synchronize with the repository in
-order to commit them.</p>
-<ul>
-  <li>Fred will make changes to <em class="FileName">file1.txt</em> and <em class="FileName">file2.txt</em></li>
-  <li>Fred will synchronize and commit his outgoing changes to the two files.</li>
-</ul>
-<p>Fred should proceed as follows:</p>
-<ol>
-  <li class="Steps">Modify <em class="FileName">file1.txt</em> as follows
-    <div class="FileContentsDescription">Original contents:
-    <pre class="FileContents">
-This is the contents
-of file 1.
-    </pre>
-    </div>
-    <div class="FileContentsDescription">New contents (changes shown in bold):
-    <pre class="FileContents">
-This is the contents
-<b>Fred-update</b>
-of file 1.
-    </pre>
-    </div>
-  </li>
-  <li class="Steps">Modify <em class="FileName">file2.txt</em> as follows
-     <div class="FileContentsDescription">Original contents:
-     <pre class="FileContents">
-File2 is a small file
-with simple text.
-    </pre>
-    </div>
-    <div class="FileContentsDescription">New contents (changes shown in bold):
-       <pre class="FileContents">
-File2 is a (<b>Fred was here)</b> small file
-with simple text.
-    </pre>
-    </div>
-  </li>
-  <li class="Steps">Observe that the Project Explorer updates the CVS state of a resource.
-     Notice that the two files which Fred has changed are preceded by "&gt;".
-    <img class="Big" src="../images/Image83_fred_verson.png" alt="Project Explorer View">
-  </li>
-  <li class="Steps">To commit his changes to the repository Fred can either:
-    <ul>
-      <li>Select the two files and choose 
-          <em class="UILabel">Team &gt; Synchronize with Repository</em> or,</li>
-      <li>Select the project and choose 
-          <em class="UILabel">Team &gt; Synchronize with Repository</em></li>
-    </ul>
-    <p>Often choosing the project is the easiest thing to do. Let's do
-that. Select the project and choose <em class="UILabel">Team &gt; Synchronize with
-Repository</em> from its context menu. When you are asked to switch to
-the Team Synchronizing perspective select 
-<em class="UILabel">Yes</em>.
-    <img class="Big" alt="Team Synchronizing preview" src="../images/Image83_fred_verson2.png">
-    </p>
-  </li>
-  <li class="Steps">When the Synchronize View opens Fred can browse the changes he
-made and at the end should commit his changes to
-<em class="FileName">file1.txt</em> and <em class="FileName">file2.txt</em> by selecting 
-<em class="ProjectName">JanesTeamProject</em> in the
-Synchronize View and from the context menu select 
-<em class="UILabel">Commit</em>. You will have to enter a
-commit comment before committing the changes.
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm
deleted file mode 100644
index 2b824fc..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_mod.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Making our own changes</title>
-</head>
-<body>
-
-<h3>Making our own changes</h3>
-
-<p>Fred has made several changes to <em class="FileName">file1.txt</em> and
-<em class="FileName">file2.txt</em> and committed them to the repository. In this section
-additional changes will be made and then synchronized with the
-repository. When synchronizing, expect to see the changes made in this
-section along with changes that have been made by Fred.</p>
-<ol>
-  <li class="Steps">Add <em class="FileName">file3.txt</em> as follows:
-    <div class="FileContentsDescription">New contents: (add the following lines to the file)
-        <pre class="FileContents">
-This is the brief contents
-of file 3</pre>
-    </div>
-  </li>
-  <li class="Steps">Observe that the Project Explorer displays the CVS state of a resources. Notice 
-    that the new file added by Jane is preceded by "&gt;".
-    <img class ="Big" src="../images/Image83_jane1.png" alt="Project Explorer View">
-  </li>
-  <li class="Steps">Select the project <em class="ProjectName">JanesTeamProject</em> 
-      and from the project's context menu, select 
-      <em class="UILabel">Team &gt; Synchronize with Repository</em>. 
-      When asked to switch perspective select 
-      <em class="UILabel">Yes</em>. The Team Synchronizing perspective will 
-      open and you will see the files you have changed appear in the Synchronize 
-      View. Double click on <em class="FileName">file1.txt</em> and you should see a compare editor open:
-	  <img class="Big" src="../images/Image83_jane-sync.png" alt="Synchronize View">
-  </li>
-  <li class="Steps">There are a couple of other things worth observing. First, the icon next 
-    to <em class="FileName">file1.txt</em> (in the structured compare area) indicates that <em class="FileName">file1.txt</em> has 
-    an incoming change. This means a change was released to the server which you 
-    need to take. Looking at <em class="FileName">file1.txt</em> we can see the text that Fred has added 
-    to the file. Also, notice at the bottom of the window, in the status line, 
-    there are arrows with numbers beside them. These show the number of files 
-    you have incoming, outgoing, and in conflict. The first number beside a file 
-    is the revision you have in the workspace, and the other is the revision on 
-    the server when you last synchronized.
-  </li>
-  <li class="Steps">Normally you should update the changes made by others, then test your workspace 
-    with the changes, then commit your changes once you are sure that the new 
-    changes by others didn't break anything in your workspace.
-  </li>
-  <li class="Steps">Before deciding to accept Fred's changes you may want to find out why he 
-    made the changes. Select <em class="FileName">file1.txt</em> and from the context menu select 
-    <em class="UILabel">Show in History</em>.
-    <img class ="Big" src="../images/Image83_jane-history.png" alt="History View">
-  </li>
-  <li class="Steps">The row starting with a * indicates 
-      that this is the current revision loaded. In this case you can see the comment 
-      made by Fred when he released revision 1.2.
-       <p class="Tip">
-          <b>Tip</b>: You can select the <em class="UILabel">Link with 
-          Editor and Selection</em> toolbar button in the History view to have the history automatically 
-          update when a new editor is opened or when the selection changes. This allows for quick browsing of comments.
-       </p>
-  </li>
-  <li class="Steps">To update simply select <em class="ProjectName">JanesTeamProject</em> 
-      in the Synchronize View and from the context menu select 
-      <em class="UILabel">Update</em>.
-  </li>
-  <li class="Steps">The Synchronize View will update to reflect the fact that <em class="FileName">file1.txt</em> and 
-      <em class="FileName">file2.txt</em> are no longer out-of-sync with the repository. You should only have 
-      <em class="FileName">file3.txt</em> visible now.
-  </li>
-  <li class="Steps">Next you can commit <em class="FileName">file3.txt</em>.
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm
deleted file mode 100644
index 64bd5dd..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-64c_catch_sync_view.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Working with conflicting changes</title>
-</head>
-<body>
-<h3>Working with conflicting changes<br>
-</h3>
-<p>There are cases where two users are editing the same files and 
-  when the second to commit to the repository tries to commit their changes, the 
-  repository won't allow the commit to succeed because of the conflict. Let's 
-  simulate this by making Fred and Jane change the same files.<br>
-</p>
-<ol>
-  <li class="Steps">In Fred's workspace open one of the navigation views and edit 
-      <em class="FileName">file1.txt</em>. Make the text the following:
-<pre class="FileContents">
-Fred line 1
-This is the contents
-Fred-update
-of file 1.
-</pre>
-  </li>
-  <li class="Steps">Fred will also change <em class="FileName">file2.txt</em> with the following change:
-<pre class="FileContents">
-File2 is a (Fred was here again)
-with simple text.
-</pre>
-  </li>
-  <li class="Steps">Fred committed his changes to the repository.
-  </li>
-  <li class="Steps">Next, at the same time Jane was making changes to <em class="FileName">file1.txt</em>. She
-    added the following line to the end of the file:
-<pre class="FileContents">
-This is the contents
-Fred-update
-of file 1.
-Jane was at the end
-</pre>
-  </li>
-  <li class="Steps">And finally, Jane changed <em class="FileName">file2.txt</em> to the following:
-<pre class="FileContents">
-File2 is a (Jane was here) small file
-with simple text.
-</pre>
-  </li>
-  <li class="Steps">When Jane was finished making changes she synchronized the
-project and found the following appear in the Synchronize View:
-    <img class="Big" src="../images/Image83_jane3_conflict.png" alt="Conflict shown in Synchronize view and Compare editor">
-  </li>
-  <li class="Steps">Both <em class="FileName">file1.txt</em> and <em class="FileName">file2.txt</em> 
-    show with a red icon indicating that they have 
-    conflicting changes. You can't commit the files until the conflicts are resolved. 
-    Click on <em class="FileName">file1.txt</em> and notice that Fred and Jane made changes to two different 
-    parts of the file. In this case, Jane can simply update the file and the lines 
-    added by Fred will be merged into Jane's local file. Select <em class="FileName">file1.txt</em> and 
-    from the context menu select <em class="UILabel">Update</em>.
-  </li>
-  <li class="Steps">Next, double on <em class="FileName">file2.txt</em> to see the conflict. In this case you can see 
-    that both Jane and Fred changed the same line. For this type of conflicting 
-    change a regular update can't resolve the conflict. Here you have three options 
-    (with the command to use in brackets): accept the changes from Fred (<em class="UILabel">Override 
-    and Update</em>), ignore Fred's changes (<em class="UILabel">Mark 
-    as Merged</em>), or manually merge the files within the compare editor.
-    <img class="Big" src="../images/Image83_jane3_conflict2.png" alt="Compare editor showing conflict">
-  </li>
-  <li class="Steps">For this example, let's say Jane updated <em class="FileName">file1.txt</em> and selected
-override and update for <em class="FileName">file2.txt</em>. After the operations are run the
-conflicts turn into outgoing changes. Jane can review the changes and
-commit them.<br>
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm
deleted file mode 100644
index 8b1ff62..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_replace.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Replacing</title>
-</head>
-
-<body>
-<h3> Replacing</h3>
-<p>Suppose after further reflection, it becomes apparent
-to Jane that the revision of <em class="FileName">file1.txt</em> that was just received is incorrect and
-an earlier revision is required. A Workbench resource can be replaced
-with an earlier revision of the resource from the repository. To roll
-back to an earlier revision:</p>
-<ol>
-  <li class="Steps">In one of the navigation views select the <em class="FileName">file1.txt</em>.
-  </li>
-  <li class="Steps"> From the file's context menu, select <em class="UILabel">Replace With &gt; History....</em>
-  </li>
-  <li class="Steps">The history view will open and display the revisions available for the 
-     selected file. Make sure that the history view is in Remote Revisions mode. (If it is not you can put it in
-     Remote mode by clicking on the <em class="UILabel">Remote Revisions</em> button in the History view toolbar.) 
-     Select revision <b>1.3</b> in the
-     table and from the pop-up menu choose <em class="UILabel">Get Contents</em>.
-     <img class="Big" src="../images/Image84_replace3.png"  alt="History View">
-  </li>
-  <li class="Steps">Observe that the navigation view updates to show the CVS state of a resource. 
-      Notice that the modified file is preceded by "&gt;" indicating 
-      that <em class="FileName">file1.txt</em> has changed (by replacing it with the earlier version).
-      <img class="Big" src="../images/Image84_replace2.png"  alt="File selection">
-  </li>
-  <li class="Steps">Now assume that this older revision is not as good as it initially seemed 
-    and in fact the revision in the repository is better after all.
-    <p>Instead of choosing <em class="UILabel">Team &gt; Synchronize with Repository</em>, choose 
-      <em class="UILabel">Replace With &gt; Latest from HEAD</em>.</p>
-    <p>Observe that <em class="FileName">file1.txt</em> is updated to have the same contents as the latest revision from the repository, 
-      and that the leading indicator "&gt;" has been removed since it is now the 
-      same revision as the repository. </p>
-  </li>
-</ol>
-<p>Now that you have a file's revisions displayed in the History View, it is possible to compare revisions directly
-  by selecting the revisions in the table and choosing <em class="UILabel">Compare With Each Other.</em></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_workingWithHistory.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_workingWithHistory.htm
deleted file mode 100644
index 7b33413..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-70_workingWithHistory.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Working With CVS History</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h3>Working With CVS History</h3>
-
-<p>Projects that are managed by CVS now have their file local history and remote history 
-appear together in the same view. To view the consolidated history for a shared file in the History View,
-perform the following steps:</p>
-<ol>
-  <li class="Steps">In any navigation view, select a file that is contained in a project that is shared using CVS.<br>
-  </li>
-  <li class="Steps">Right-click the file in order to access one of the following history related options:
-       <ul>
-     	<li><em class="UILabel">Team&gt;Show History...</em> which opens the History View
-      with the revisions of the selected file displayed in the table.</li>
-        <li><em class="UILabel">Compare With&gt;History...</em> which does the same as <em class="UILabel">Show History</em> 
-        but which launches comparisons when entries in the history table are double-clicked (for more info see
-       <a href="../reference/ref-32a.htm">CVS History View</a>).</li>
-        <li><em class="UILabel">Replace With&gt;History...</em> which does the same as the comparison operation.</li>
-      </ul>
-  </li>
-  <li class="Steps">The history view will open and display the revisions available for the 
-     selected file. You can control what type of revisions are shown in the table by selecting
-     the appropriate toggle button in the History View tooblar. The options are: <em class="UILabel">Local and Remote
-     Revisions</em>, <em class="UILabel">Local Revisions</em> and <em class="UILabel">Remote Revisions</em>.
-    <img class="Big" src="../images/Image84_replace3.png"  alt="History View">
-  </li>
-  <li class="Steps">The following operations are available when right-clicking the entries in the History view:
-  <ul>
-     <li><em class="UILabel">Open</em>: opens the selected revision</li>
-     <li><em class="UILabel">Compare Current with Revision</em>: compares the selected file with
-      the current revision of the file that resides in the workspace</li>
-      <li><em class="UILabel">Compare with Each Other</em>: compares two selected revisions</li>
-      <li><em class="UILabel">Get Contents</em>: replaces the current workspace file with the contents 
-      of the selected revision.</li>
-     </ul>
-  </li>
-</ol>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm
deleted file mode 100644
index 6bf9a66..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_review.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <title>A quick review</title>
-</head>
-<body>
-<h3>
-A quick review</h3>
-<p> Here are some of the more important but subtle issues
-associated with working in a repository . </p>
-<ul>
-  <li>The project was tagged as a version by versioning the project as
-it appeared in the Workbench. For this reason it is important to
-synchronize the project with the repository (that is the HEAD or the
-branch that is being worked in) prior to versioning it. Otherwise
-another user may have committed interesting changes to the project
-which have yet to be updated in the Workbench. By proceeding to version
-the project without updating, it will be versioned without these
-changes.</li>
-  <li>The repository contains all projects in the repository.
-Individuals pick the projects they are interested in and check
-them out into the workspace. From that point on they are synchronizing
-those projects (only) with respect to the repository.</li>
-  <li>The repository represents a large in-progress collection of all
-known projects. From the repository's perspective, everything in HEAD
-or on a branch is always open for change.</li>
-  <li>The act of versioning a project effectively snapshots it and
-places it into the Versions section of the repository, however the
-repository branches are still open for change.</li>
-  <li>It is important to first update to changes made to the
-repository, retest with those changes and the soon to be committed
-changes and then commit the changes. By first taking the latest
-changes in the branch, and retesting, it helps to ensure that the
-changes about to be committed will actually work with the current state
-of the branch.</li>
-  <li>Each project is associated with a specific repository. Different
-projects can be associated with different repositories that may be on
-completely different servers.</li>
-</ul>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm
deleted file mode 100644
index f20d514..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-74_version.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <link type="text/css" charset="ISO-8859-1" href="team-cvs.css" rel="STYLESHEET">
-  <title>Versioning a project</title>
-</head>
-
-<body>
-<h3>Versioning a project</h3>
-<p> Now that the project is complete it is time to version
-it. While committing the file resources the repository automatically
-assigned them version numbers, or to be more accurate "revision
-numbers". As the files were committed the only information supplied was
-a commit comment.</p>
-<p>To version a project proceed as follows:</p>
-<ol>
-  <li class="Steps">Select the project <em class="ProjectName">JanesTeamProject</em>.
-  </li>
-  <li class="Steps">In one of the navigation views select <em class="UILabel">Team &gt; Tag as Version...</em>
-  </li>
-  <li class="Steps">When the Tag Resources dialog opens enter the version name <em>A1</em> and click <em class="UILabel">OK</em>.
-  </li>
-  <li class="Steps">Select the CVS Repositories view.</li>
-  <li class="Steps">Expand <b>Versions</b>, and <em class="ProjectName">JanesTeamProject</em>. 
-    Observe that under <em class="ProjectName">JanesTeamProject</em> there is now a version of this project 
-    whose version number is <em>A1</em>. Looking closely at the contents of <em class="FileName">folder1</em> note 
-    that the version numbers of the individual files match the version numbers 
-    in the Workbench.
-  </li>
-</ol>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm
deleted file mode 100644
index 6e44130..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-80_ant.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Ant &amp; external tools tutorial</title>
-
-</head>
-<body>
-	<h1>Ant &amp; external tools tutorial</h1>
-	<p>
-		This chapter covers Eclipse's external tools framework, and its 
-	  	integration with <a href="http://ant.apache.org/">Ant</a>, the build tool from 
-	  	the <a href="http://www.apache.org/">Apache Software Foundation</a>. For more 
-	  	information on Ant, see the <a href="http://ant.apache.org/manual/index.html">Apache 
-	  	Ant manual</a> for documentation. This chapter assumes a basic knowledge of 
-	  	Ant.
-	</p>
-	<p>
-	This chapter is split into three main sections. 
-	</p>
-	<ol>
-		<li><a href="qs-81_basics.htm">Eclipse Ant basics</a>: the basics of working with Ant buildfiles in Eclipse are covered</li>
-		<li><a href="qs-92_project_builders.htm">Ant build files as project builders</a>: several Eclipse use cases are discussed</li>
-		<li><a href="qs-95_external_tools.htm">External tools</a>: the external tools framework and how to use non-Ant tools are covered</li>
-	</ol>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm
deleted file mode 100644
index ed03ceb..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-81_basics.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse Ant basics</title>
-
-</head>
-<body>
-<h1>Eclipse Ant basics</h1>
-  
-<p>This section covers the basics of working with Ant buildfiles 
-  in Eclipse. 
-</p>
-<p>
-  Specifically, the following topics are covered:
-</p> 
-  <ul>
-	  <li><a href="qs-82_create.htm">Creating</a></li>
-	  <li><a href="qs-83_edit.htm">Editing</a></li>
-	  <li><a href="qs-84_run_ant.htm">Running Ant buildfiles</a></li>
-	  <li><a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a></li>
-	  <li><a href="qs-85a_ant_view.htm">Using the Ant view</a></li>
-  </ul>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm
deleted file mode 100644
index 7145383..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-82_create.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js" type="text/javascript"> </script>
-<title>Creating Ant buildfiles</title>
-</head>
-<body>
-<h1>Creating Ant buildfiles</h1>
-  
-<p> Ant buildfiles are just text files, so the most straightforward 
-  way to create an Ant buildfile in Eclipse is:</p>
-<ol>
-  <li><b>File &gt; New &gt; File</b>.</li>
-  <li>Enter a name for the file.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-<p>
-	By default the <a href="../reference/ref-anteditor.htm">Ant editor</a> only has an association with <code>build.xml</code> named files.
-	As the user you can designate the Ant editor to be considered for all xml
-	files.
-</p>
-<ol>
-  	<li>File associations can be set using the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'> 
-  											 <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the File Associations preference page"><b> Window &gt; Preferences &gt; General &gt; Editors &gt;File Associations</b></a></li>
-	<li>Add an association between <code>*.xml</code> and the <a href="../reference/ref-anteditor.htm">Ant editor</a>.</li>
-</ol>
-
-<p>Now, as long as the file has a .xml extension, Eclipse will consider it to be a 
-  possible Ant buildfile, and will enable Ant-related actions when it is selected.
-  Until a file has Ant buildfile content, you will need to open it using <b>Open With &gt; <a href="../reference/ref-anteditor.htm">Ant Editor</a></b>.</p>
-<p>An example is the use of <a href="qs-92_project_builders.htm">project builders</a>, where an Ant buildfile is created 
-  for an Eclipse plug-in that contains predefined targets that are useful for deploying the plug-in.</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm
deleted file mode 100644
index 120528e..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-83_edit.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Editing Ant buildfiles</title>
-
-</head>
-<body>
-<h1>Editing Ant buildfiles</h1>
-<p class="Para">Because Ant buildfiles are simple text files, any text editor 
-  can be used to edit them. But there are several advantages to using the Eclipse 
-  Ant editor, including syntax coloring, content assist, navigation, occurrence marking and an outline view. To 
-  get familiar with the Eclipse <b><a href="../reference/ref-anteditor.htm">Ant editor</a></b>, create a simple Ant buildfile using 
-  this editor.</p>
-<ol>
-  <li>Create an Ant buildfile called <code>HelloWorld.xml</code>.</li>
-  <li>Open the <b><a href="../reference/ref-anteditor.htm">Ant editor</a></b> on the file by selecting <b>Open With &gt; Ant Editor</b> 
-    from the file's context menu. <br>
-    <strong>Note:</strong> The default editor for a <code>.xml</code> file is a simple text 
-    editor until it has buildfile content - which can be changed on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'> 
-  											 <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png" alt="Opens the File Associations preference page"><b> Window &gt; Preferences &gt; General &gt; Editors &gt;File Associations</b></a> preference page.</li>
-  <li>Enter the following content in the editor:
-<pre>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;project name=&quot;Hello World&quot; default=&quot;Hello&quot; basedir=&quot;.&quot;&gt; 
-  &lt;property name=&quot;HelloText&quot; value=&quot;Hello&quot;/&gt;
-  &lt;target name=&quot;Hello&quot;&gt;
-    &lt;echo&gt;${HelloText}&lt;/echo&gt;
-  &lt;/target&gt;
-&lt;/project&gt;
-</pre>
-    <p><img src="../images/first_anteditor.png" alt="HelloWorld.xml file content" border="0" ></p>
-  </li>
-  <li>Notice the syntax coloring for property values.</li>
-  <li>Begin to enter a second target by typing <code>&lt;tar</code>, then hit <strong>Ctrl-Space</strong>
-    to activate content assist. A list of valid completions is presented. Select the <code>&lt;target&gt;</code> completion and 
-    notice that the editor inserts both the opening and closing tags and leaves 
-    the cursor positioned to enter attributes for this tag.</li>
-  <li>Name this target <code>World</code>.</li>
-  <li>Enter an <code>echo</code> task for this target similar to that for the Hello target, 
-    but change the text to <code>${WorldText}</code>.</li> 
-    <li>Add a dependency on the <code>World</code> target from the <code>Hello</code> target. Place the cursor after the definition of the name attribute, hit <strong>Ctrl-Space</strong>
-    and select the <code>depends</code> attribute completion. Hit <strong>Ctrl-Space</strong> again to get the completion for the other target <code>World</code> in the buildfile.</li>
-    <li>Save the buildfile contents.</li>
-    <li>The full content will now be:
-<pre>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;project name=&quot;Hello World&quot; default=&quot;Hello&quot; basedir=&quot;.&quot;&gt;
-  &lt;property name=&quot;HelloText&quot; value=&quot;Hello&quot;/&gt;
-  &lt;property name=&quot;WorldText&quot; value=&quot;World&quot;/&gt;
-  &lt;target name=&quot;Hello&quot;&gt;
-    &lt;echo&gt;${HelloText}&lt;/echo&gt;
-  &lt;/target&gt;
-
-  &lt;target name=&quot;World&quot;&gt;
-    &lt;echo&gt;${WorldText}&lt;/echo&gt;
-  &lt;/target&gt;
-  &lt;/project&gt;
-</pre>
-
-</li>
-  <li>Save the changes to <code>HelloWorld.xml</code>.</li>
-  <li>Make the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm">Outline view</a></b> visible and notice that there are entries for each 
-    property and each target. In addition, each task under a target has an entry.<br><br>
-    <img src="../images/outline_hello.png" alt="Outline view for an Ant buildfile" border="0" >
-    <br><br></li>
-  <li>Clicking on an entry in the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm">Outline view</a></b> will scroll the editor to that 
-    entry. In addition, when the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm">Outline view</a></b> has focus, typing a character will 
-    move the selection in the view to the next visible entry beginning with that character.</li>
-  <li>Position the cursor just past the end of one of the <code>&lt;target&gt;</code> tags, 
-    type <code>&lt;tar</code>, then hit <b>Ctrl-Space</b> to activate content assist. Notice that 
-    now the only valid completions are the <code>&lt;/target&gt;</code> and the <code>tar</code> tag. This is because the Ant editor 
-    knows that nested targets are not allowed.<br><br>
-    <img src="../images/Image602_tar_assist.png" alt="Code assist in Ant editor" border="0"> 
-    <br></li>
-  <li>Close the editor and do not save changes.</li>
-</ol>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm
deleted file mode 100644
index c2aa4dc..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-84_run_ant.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Running Ant buildfiles</title>
-
-</head>
-<body>
-<h1>Running Ant buildfiles</h1>
-  
-<p>Any file with a <code>.xml</code> extension can be run as an Ant buildfile. 
-  Of course, not all such files really are Ant buildfiles, but no harm is done 
-  if an attempt is made to mistakenly run a non-Ant <code>.xml</code> file as an Ant buildfile.</p>
-<p>In this section, the basic mechanisms for running Ant buildfiles 
-  in Eclipse will be covered, using the <code>HelloWorld.xml</code> file created in the <a href="qs-83_edit.htm">Editing Ant buildfiles</a> task.</p>
-<ol>
-  <li>Select <code>HelloWorld.xml</code> in one of the navigation views and choose <b>Run As 
-    &gt; Ant Build... </b> from its context menu.</li>
-  <li>The launch configuration dialog is opened on a launch configuration for this Ant buildfile.
-    <p><img src="../images/ant_run_dialog.png"  alt="Run Ant dialog" border="0"></p>
-  </li>
-  <li>This dialog allows the configuration of many aspects of the way an Ant 
-    buildfile is run, but for now concentrate on the <b>Targets</b> tab which 
-    allows the selection of which Ant targets to run and their order. Select both 
-    targets and leave the order as the default. </li>
-  <li>Click the <b>Run</b> button.</li>
-  <li>The Ant buildfile is run, and the output is sent to the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b>.</li>
-</ol>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm
deleted file mode 100644
index 113c1e9..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85_ant_configs.htm
+++ /dev/null

@@ -1,74 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Saving &amp; Reusing Ant options</title>
-
-</head>
-<body>
-<h1>Saving &amp; Reusing Ant options</h1>
-  
-<p>When we ran the <code>HelloWorld.xml</code> Ant buildfile in the <a href="./qs-84_run_ant.htm">last section</a>, 
-  the choice of targets, along with all other options in the launch configuration dialog were 
-  saved in an entity called a 'launch configuration'. Launch configurations contain 
-  all details necessary to run an Ant buildfile in a particular way. It is 
-  perfectly valid to have multiple launch configurations associated with a single 
-  Ant buildfile. Therefore, in addition to the launch configuration that was created in 
-  the last step, specifying that our <code>HelloWorld.xml</code> buildfile should execute the 
-  targets <code>&quot;Hello&quot;</code> and <code>&quot;World&quot;</code> in that order, a second launch configuration could be created
-  for the same buildfile specifying different targets or just different ordering.
-  Creating multiple launch configurations in this manner allows you to quickly run 
-  your Ant buildfile in any configuration by simply specifying the corresponding 
-  launch configuration.</p>
-<ol>
-  <li>From the Workbench toolbar, select <b>Run &gt; External Tools &gt; Open External Tools Dialog...</b>.</li>
-  <li>The External Tools dialog opens and presents a choice of launch configurations 
-    to view and edit. The launch configuration we created when we ran the <code>HelloWorld.xml</code> 
-    buildfile is selected in the tree at the left, and the tabs on the right show 
-    the options for this launch configuration.<br><br>
-    <img src="../images/et_dialog.png" alt="External tools dialog" border="0" > 
-    <br><br>
-  </li>
-  <li>At the top of the dialog, change the Name to <code>Hello World</code> and <b>Apply</b> 
-    the change.</li>
-  <li>In the tree at left, bring up on the context menu on the selected launch 
-    configuration and choose <b>Duplicate</b>, or select the <b>Duplicate</b> on the 
-    toolbar above the tree. A copy of the launch configuration 
-    for the Hello World buildfile is created, <code>(1)</code> is appended to the name, and 
-    the new launch configuration is selected in the tree.</li>
-  <li>Rename the new configuration to <code>World Hello</code>.</li>
-  <li>In the <b>Targets</b> tab, click the <b>Order...</b> button, change the 
-    order of the targets so that the <code>World</code> target executes first, and <b>Apply</b> 
-    the change.</li>
-  <li>Click <b>Run</b>.</li>
-  <li>As before, the <code>HelloWorld.xml</code> buildfile runs and sends its output to the 
-    <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b>. 
-    This time however, because the targets were reversed, the output is reversed as well.</li>
-  <li>Go back to the External Tools drop down in the toolbar. <br><br>
-    <img src="../images/et_dropdown.png" alt="External tools drop-down menu" border="0" >
-    <br><br>
-    Notice now that there are two entries in the history, one for <code>Hello World</code> 
-    and one for <code>World Hello</code>. In order to rerun the Ant buildfile so that it outputs 
-    <code>Hello World</code>, just select this launch configuration in the history. To rerun 
-    the launch configuration that outputs <code>World Hello</code>, select this configuration 
-    in the history.<br>
-    <strong>Note</strong>: The history is ordered so that the most frequently 
-    run configurations are at the top of the drop-down.</li>
-</ol>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm
deleted file mode 100644
index 445f648..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-85a_ant_view.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Using the Ant view</title>
-</head>
-<body>
-<h1>Using the Ant view</h1>
-  
-<p>Eclipse provides a standard view, the <b><a href="../reference/ref-antview.htm">Ant view</a></b>, that lets you 
-  work with your Ant buildfiles. This view is tree-structured, showing Ant buildfiles 
-  as top-level entries and targets &amp; internal targets as children. The main 
-  advantage of this view is that you can work with all of your Ant buildfiles 
-  in one place, as opposed to hunting them down in one of the navigation views.</p>
-<ol>
-  <li>Open the <b><a href="../reference/ref-antview.htm">Ant view</a></b> from the workbench menu by selecting <b>Window &gt; Show 
-    View &gt; Ant</b>.</li>
-  <li>By default, the Ant view is empty. There are three ways to add Ant buildfiles 
-    to this view: 
-    <ul>
-      <li>Click <strong>Add Buildfile [<img src="../images/org.eclipse.ui.externaltools/clcl16/add_co.png" alt="Add buildfile to Ant view" border="0">]</strong>. 
-        This brings up a dialog in which you explicitly select those Ant buildfiles 
-        you want to add</li>
-      <li>Click <strong>Add Buildfiles with Search [<img src="../images/org.eclipse.ui.externaltools/clcl16/search.png" alt="Add buildfiles with search">]</strong>. 
-        This brings up a search dialog in which you can specify a filename pattern 
-        for your Ant buildfiles and search within the entire workspace or a specified 
-        working set.<br></li>
-        <li>Drag and drop buildfiles from other views to the <b><a href="../reference/ref-antview.htm">Ant view</a></b>.<br>
-        <br>
-        Once added to the Ant view, Ant buildfile entries remain in the view across 
-        workbench invocations until explicitly removed or the associated project is closed.</li>
-    </ul>
-  </li>
-  <li>Click <strong>Add Buildfiles with Search</strong>. Suppose you only remember 
-    that the buildfile you want to work with starts with <code>H</code>. Enter <code>H*.xml</code> for 
-    the buildfile name. Make sure <b>Workspace</b> is selected for the scope, then click 
-    <b>Search</b>. The <code>HelloWorld.xml</code> file is found and placed in the <b><a href="../reference/ref-antview.htm">Ant view</a></b>.</li>
-  <li>Expand the top-level entry to see the default target <code>Hello</code>, and the internal 
-    target <code>World</code>.<br><br>
-    <img src="../images/ant_view.png" alt="Ant view" border="0" >
-    <br><br> 
-  </li>
-  <li>Select the <code>World</code> internal target and click <strong>Run the Selected Target [<img src="../images/org.eclipse.ui.externaltools/clcl16/run_tool.png" alt="Run selected buildfile or selected target">]</strong>. 
-    Notice that just the <code>World</code> target gets executed. </li>
-  <li>Select the top-level <code>HelloWorld</code> buildfile and click <strong>Run the Default 
-    Target of the Selected Buildfile [<img src="../images/org.eclipse.ui.externaltools/clcl16/run_tool.png"  alt="Run selected buildfile or selected target">]</strong>. 
-    Notice that just the default target, <code>Hello</code>, gets executed.</li>
-  <li>To edit your buildfile, bring up the context menu on the <code>HelloWorld</code> file 
-    and select <b>Open With &gt; Ant Editor</b>.</li>
-  <li>To edit the default launch configuration, select <strong>Run As &gt; Ant Build...</strong> from 
-    the context menu.</li>
-  <li>The Run Ant launch configuration dialog appears. Here you can modify the way in which the buildfile 
-    is run from the <b><a href="../reference/ref-antview.htm">Ant view</a></b>.</li>
-  <li>Select the <code>HelloWorld</code> file, then click the <b>Remove</b> button. The buildfile 
-    is removed from the view.<br>
-    <strong>Note</strong>: This does not delete the file from the workspace.</li>
-</ol>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm
deleted file mode 100644
index 55a8374..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-92_project_builders.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Ant buildfiles as project builders</title>
-</head>
-<body>
-<h1>Ant buildfiles as project builders</h1>
-  
-<p>Our second practical example of using Ant buildfiles in Eclipse 
-  is a 'project builder'. This is an Ant buildfile that has been designated to 
-  run whenever a project is built. The uses for such a buildfile are many:</p>
-<ul>
-  <li>Generate a <code>.jar</code> file containing class files from your project</li>
-  <li>Perform some type of pre- or post-build processing on source or binary files 
-    in your project. For example: 
-    <ul>
-      <li>Pre-processing source files to instrument them for performance analysis</li>
-      <li>Obfuscating binary files to prevent reverse engineering</li>
-    </ul>
-  </li>
-  <li>Copy class files to some location (for instance, on a network)</li>
-</ul>
-<p>For this example, we will create an Ant buildfile that creates a <code>.jar</code> archive 
-  of the class files in a project. Note that this is similar to the example in 
-  the last chapter, in which we used an Ant buildfile to generate <code>.jar</code> files for 
-  an Eclipse plug-in. This example differs in that it works for any Eclipse project,
-  whether or not it is also an Eclipse plug-in.
-</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm
deleted file mode 100644
index 7cdd93f..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-93_project_builder.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Creating a project builder Ant buildfile</title>
-
-</head>
-<body>
-<h1>Creating a project builder Ant buildfile</h1>
-<p>To see how project builders work, we will create a simple project 
-  with a single source file and an Ant buildfile that jars up the single class file. 
-  Though this example uses Java, it should be noted that project builders are 
-  available for all projects, Java or otherwise.</p>
-<ol>
-  <li>Create a Java project named <code>HW</code>.</li>
-  <li>Create a Java source file named <code>HelloWorld</code> with a main method.</li>
-  <li>Put a single <code>System.out.println()</code> statement in the main method, and make 
-    it print a greeting of your choice.</li>
-  <li>Save changes.</li>
-  <li>Create a file named <code>projectBuilder.xml</code>, open the <b><a href="../reference/ref-anteditor.htm">Ant editor</a></b> on it, enter 
-    the following content, and save changes.
-<pre>
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-  &lt;project name="HW.makejar" default="makejar" basedir="."&gt;
-  &lt;target name ="makejar" description="Create a jar for the HW project"&gt;
-    &lt;jar jarfile="HelloWorld.jar" includes="*.class" basedir="bin"/&gt;
-  &lt;/target&gt;
-  &lt;/project&gt;
-</pre>
-  </li>
-  <li>In one of the navigation views, select the HW project and choose <b>Properties</b> 
-    from its context menu.</li>
-  <li>In the project properties dialog, select <b>Builders</b>, then click <b>New...</b>. 
-  </li>
-  <li>In the <strong>Choose configuration type</strong> dialog, select <strong>Ant 
-    build</strong>, and click <b>OK</b>. </li>
-  <li>The <strong>External Tools</strong> dialog appears. Set the name to <code>Makejar</code>. 
-    In the <b>Main tab</b>, click the <strong>Buildfile</strong> <b>Browse Workspace...</b> 
-    and set the <b>Location</b> to be the <code>projectBuilder.xml</code> buildfile created 
-    above. Then click the <strong>Base Directory</strong> <b>Browse Workspace...</b> 
-    and set the Base Directory to be the HW project.
-    <p><img src="../images/Image611_et_main_tab.png" alt="Main tab of External tools dialog" border="0" ></p>
-  </li>
-  <li>In the <b>Refresh</b> tab, we want to be sure that when our <code>HelloWorld.jar</code> 
-    is created, we see it in Eclipse. By default, no refreshing is done when a 
-    project builder finishes running, so check <b>Refresh resource upon completion</b>, 
-    then select <b>The project containing the selected resource</b> in the list 
-    of scoped variables. Because refreshing can be expensive, you should, in general,
-    refresh the smallest entity that contains all resources that will be affected 
-    by your buildfile.
-    <p><img src="../images/Image612_et_refresh_tab.png" alt="Refresh tab of External tools dialog" border="0"></p>
-  </li>
-  <li>In the <b>Targets</b> tab, you can specify when this project builder 
-    is executed and which targets. By default, the <code>default</code> target is set to run <strong>After a &quot;Clean&quot; 
-    </strong> and <strong>Manual Build</strong>. You can specify other targets and other triggers. Running your project builder 
-    during auto builds is possible, though not recommended because of performance 
-    concerns.
-    <p><img src="../images/Image610_et_targets_tab.png" alt="Targets tab of External tools dialog" border="0" ></p>
-  </li>
-  <li>Apply the changes and click <b>OK</b>.</li>
-  <li>Back in the project properties dialog, you will now see a project builder 
-    named <code>Makejar</code> that is set to run after the default <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm">Java builder</a></b>. Click <b>OK</b> 
-    to save the project builder and close the dialog. <br>
-    <strong>Note:</strong>You can change the order so that your Ant buildfile runs before 
-    the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm">Java builder</a></b>, though that wouldn't make sense in this example. 
-    <p><img src="../images/Image613_project_properties.png" alt="Project properties dialog" border="0" ></p>
-  </li>
-</ol>
-<p>The <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm">Java builder</a></b> runs the internal Eclipse Java compiler which in 
-  turn is responsible for indexing your source so that searching, refactoring and 
-  many other features are available. Thus it is not possible to replace the internal 
-  Eclipse Java compiler by using a project builder. You can disable the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm">Java builder</a></b> and you can control 
-  when the Java Builder runs with respect to the project builders that you define.</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm
deleted file mode 100644
index 4559dce..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-94_run_pj.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Executing project builders</title>
-</head>
-<body>
-<h1>Executing project builders</h1>
-  
-<p>The whole point of project builders is that you don't need to 
-explicitly tell them to run.  Instead, they run automatically whenever a qualifying build takes place 
-  for the project that owns the buildfile. Remember that the builders are triggered as indicated
-  on the <strong>Build Options</strong> tab in the <b>External Tools</b> dialog and can be 
-  any combination of after a clean, during a manual build or during auto builds. Let's see how this works.</p>
-<ol>
-  <li>Select the <code>HW</code> project in one of the navigation views. In the workbench menu 
-    bar, choose <b>Project &gt; Clean...</b> Select <b>Clean selected projects</b> 
-    and click <b>Ok</b></li>
-  <li>The project is rebuilt and the <code>projectBuilder.xml</code> buildfile is run. Notice 
-    the output from this buildfile in the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b>. </li>
-  <li>Make sure the Autobuild preference is turned on, then make some trivial 
-    change to <code>HelloWorld.java</code> and save the change. The save triggers an auto build, 
-    but the auto build does not trigger the project builder. </li>
-  <li>Suppose we don't want to see the buildfile output every time it runs. Go 
-    back to the <b>External Tools Builders</b> page of the project properties dialog 
-    on <code>HW</code>. Select the <code>Makejar</code> entry and click <b>Edit...</b>. On the <b>Main</b> 
-    tab, un-check the <b>Capture Output</b> option, apply the change and exit back 
-    to the workbench. </li>
-</ol>
-<p>This concludes our look at Ant buildfiles as project builders 
-  in Eclipse. It's worth repeating that though this example used a Java project, 
-  project builders are not tied to Java, and may be used for <a href="qs-96_non_ant_pjs.htm">any type of project</a>. 
-</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm
deleted file mode 100644
index fc4f9b1..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-95_external_tools.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>External tools</title>
-</head>
-<body>
-<h1>External tools</h1>
-  
-<p>Up to this point in the tutorial, we've discussed Ant as if it 
-  were the only type of external tool available for use in Eclipse. The fact is 
-  that Eclipse's external tools framework handles two broad classes of external 
-  tools:</p>
-<ul>
-  <li>Ant: <a href="qs-82_create.htm">buildfiles</a> and <a href="qs-93_project_builder.htm">project builders</a></li>
-  <li>Non-Ant: <a href="qs-97_standalone_ets.htm">stand alone tools</a> and <a href="qs-96_non_ant_pjs.htm">non-Ant project builders</a></li>
-</ul>
-<p> In this section, we look at ways to set up and use non-Ant external 
-  tools. 
-</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm
deleted file mode 100644
index 5f920e9..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-96_non_ant_pjs.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Non-Ant project builders</title>
-</head>
-<body>
-<h1>Non-Ant project builders</h1>
-<p> When we worked through our <a href="qs-93_project_builder.htm">project builder example</a>, you may have 
-  noticed that when we created our project builder Ant buildfile, we had a choice 
-  of external tool type:<br><br>
-  <img src="../images/Image614_et_type_dialog.png" alt="Choice of external tool type dialog" border="0" > 
-</p>
-<p>The <b>Program</b> option is essentially a catch-all, allowing you 
-  to define an external tool for any executable file that is accessible on your 
-  local or network file system. Suppose that instead of Ant, you prefer to use 
-  your own shell scripts or Windows <code>.bat</code> files to jar up and deploy your Eclipse 
-  projects. You would then create a <b>Program</b> external tool that specified where 
-  and how to execute your script. </p>
-<ol>
-  <li>Create a script that performs your preferred deployment steps.</li>
-  <li>Select the project that you wish to build in one of the navigation views, 
-    and choose <b>Properties</b> from the context menu.</li>
-  <li>Select <b>Builders</b>, click <b>New...</b>, select <b>Program</b> and click 
-    <b>OK</b>.</li>
-  <li>The <b>External Tools</b> dialog appears, configured for <b>Program</b> type tools.</li>
-  <li>Enter the location of your script, its working directory, and any required 
-    arguments. <br><br>
-    <img src="../images/Image615_program_builder.png" alt="External tools dialog for program type tools" border="0" >
-    <br><br> 
-  </li>
-  <li>In this case, the script is a Windows <code>.bat</code> file, but it could be a Linux 
-    shell script, a Perl script or just about anything else that can be executed 
-    on your system. </li>
-  <li>The <b>Refresh</b> and <b>Build Options</b> tabs are identical to the tabs 
-    we saw for Ant project builders. In particular, the <b>Build Options</b> tab 
-    allows us to control what types of builds trigger our project builder buildfile.</li>
-  <li>Apply the changes, and click <b>OK</b>.</li>
-  <li>As with Ant project builders, we can control the ordering of this project 
-    builder with respect to other project builders (such as the default <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/concepts/concept-java-builder.htm">Java builder</a></b> 
-    for Java projects).</li>
-  <li>Rebuild your project. This will trigger your script to execute. Any output 
-    it generates will be sent to the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b>.</li>
-</ol>
-<p>Ant is a popular tool for configuring and deploying projects. But if you prefer 
-  some other tool, or prefer to do it yourself, you can set up a Program external 
-  tool project builder. This allows you customize the deployment of your project 
-  as you see fit, while keeping the convenience of automatically running your 
-  script every time your project is built.
-</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-97_standalone_ets.htm">Stand-alone external tools</a>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm
deleted file mode 100644
index 16c8860..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-97_standalone_ets.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Stand-alone external tools</title>
-</head>
-<body>
-<h1>Stand-alone external tools</h1>
-  
-<p>For the ultimate in external tool flexibility, create a 'stand-alone' 
-  external tool launch configuration. This is similar to the project builder launch 
-  configurations discussed in the last section, except that it need have nothing 
-  to do with project building, and you can explicitly run it whenever you choose. 
-  Suppose you wanted to have a way to quickly see the contents of a <code>.jar</code> file 
-  in your workspace using the jar utility. </p>
-<ol>
-  <li>Select some <code>.jar</code> file in your workspace.</li>
-  <li>Select <b>Run &gt; External Tools &gt; Open External Tools Dialog...</b> from the workbench 
-    toolbar.<br><br>
-    <img src="../images/Image616_et_dropdown.png" alt="External tools drop-down menu" border="0" >
-    <br><br> 
-  </li>
-  <li>Select <b>Program</b> in the tree, then click <b>New</b>.<br><br>
-    <img src="../images/Image617_jar_inspector.png" alt="External tools dialog for jar inspector script" border="0" >
-    <br><br>  
-  </li>
-  <li>Name the launch configuration <code>jar inspector</code>.</li>
-  <li>Use the first <b>Browse File System...</b> button to locate the jar executable.</li>
-  <li>In the <b>Arguments</b> field, type <code>-tvf</code> and a space, then click <b>Variables...</b>.</li>
-  <li>In the Select Variable dialog, you will see a number of variables you can 
-    pass as arguments to the program specified in Location. Select <b>resource_loc</b> 
-    and click <b>OK</b>. </li>
-  <li>When this buildfile is run, the absolute path of the resource selected in 
-    the workbench will be passed to the jar utility in the position specified. 
-  </li>
-  <li>Click <b>Run</b>.</li>
-  <li>Notice that the buildfile sends the jar utility output to the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b>.</li>
-  <li>Select a different <code>.jar</code> file in your workspace.</li>
-  <li>Click the External Tools button in the toolbar. Notice the contents of this 
-    jar are sent to the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b> as well. 
-    Now you have a quick and easy way to see the output of the jar utility for any <code>.jar</code> file in your workspace.</li>
-</ol>
-<p>This example has only scratched the surface of what you can do with external 
-  tools. The important things to remember are that you can create an external 
-  tool for anything you can run on your system, and that you can pass arguments 
-  to the external tool related to the current workbench selection. In many cases, 
-  this allows you to loosely integrate tools that do not have corresponding Eclipse 
-  plug-ins. 
-</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-	<a href="qs-82_create.htm">Creating Ant buildfiles</a><br>
-	<a href="qs-83_edit.htm">Editing Ant buildfiles</a><br>
-	<a href="qs-85_ant_configs.htm">Saving &amp; Reusing Ant options</a><br>
-	<a href="qs-84_run_ant.htm">Running Ant buildfiles</a><br>
-	<a href="qs-93_project_builder.htm">Creating a project builder Ant buildfile</a><br>
-	<a href="qs-92_project_builders.htm">Ant buildfiles as project builders</a><br>
-	<a href="qs-94_run_pj.htm">Executing project builders</a><br>
-	<a href="qs-95_external_tools.htm">External tools</a><br>
-	<a href="qs-96_non_ant_pjs.htm">Non-Ant project builders</a><br>
-</p>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm b/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm
deleted file mode 100644
index e7ad021..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/qs-responsiveUI.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Responsive UI</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1> Responsive UI</h1>
-<P CLASS="Para">By default all Eclipse operations run in the user interface thread. 
-  Employing the Responsive UI, which allows the threading of sequential code, 
-  will enable you to continue working elsewhere in Eclipse. Without the Responsive 
-  UI support you would be locked out of performing any other actions when met 
-  with a slow operation.</P>
-<P CLASS="Para">While some operations automatically run in the background (such 
-  as auto build), in many cases a dialog will be displayed providing you with 
-  the option to run an operation in the background. For example, building a project 
-  manually can sometimes take more than a few minutes, during which time you may 
-  wish to continue to use other functions in Eclipse.</p> 
-<P CLASS="Para"><img src="../images/res.png" alt="Image of the Build All Menu Item." border="0" > </p>
-<p>While the project is being built, select <strong>Run in Background </strong>from 
-  the <strong>Building Workspace</strong> dialog and the Responsive UI will allow 
-  you to carry on with other tasks in Eclipse.</p>
-<p><img src="../images/res_build.png" alt="Image of the Building Workspace window" border="0" ></p>
-<p>For information on the status of the action and additional operations that 
-  are currently running, click <strong>Details</strong>.</p>
-<p><img src="../images/res_details.png" alt="Image of the Building Workspace window with the Details displayed" border="0" ></p>
-<p>The <strong>Details </strong>panel displays the status information of the operation 
-  at hand as well as any additional operations that may be running simultaneously.</P>
-<p><img src="../images/res_otherjobs.png" alt="Image of the Building Workspace window with the Details showing simultaneous operations" border="0" ></P>
-<p>The Progress Information dialog also indicates when one operation is being 
-  blocked by another. </P>
-<p><img src="../images/res_blocked.png" alt="Image of Progress Information view with an operation that is waiting for another to complete." border="0" ></P>
-<p>To have operations running in the background set as the default, select <strong>Window 
-  &gt; Preferences &gt; General </strong> and check <strong>Always run in background.</strong> 
-</P>
-<p><img src="../images/res_pref.png" alt="Image of Workbench Preferences Window" border="0"></P>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/gettingStarted/team-cvs.css b/bundles/org.eclipse.platform.doc.user/gettingStarted/team-cvs.css
deleted file mode 100644
index 88c7277..0000000
--- a/bundles/org.eclipse.platform.doc.user/gettingStarted/team-cvs.css
+++ /dev/null

@@ -1,49 +0,0 @@
-li.Steps { margin-top: 15px; margin-bottom: 15px; }
-img.Big { margin-top: 15px; display: block; }
-em.ProjectName { font-weight: bold; font-style: normal;}
-em.FileName { font-weight: normal; font-style: italic;}
-p.Tip {
-	display: block;
-	text-align: left;
-	text-indent: 0pt;
-	margin-top: 15px;
-	margin-bottom: 15px;
-	margin-right: 0.000000pt;
-	margin-left: 30pt;
-	font-weight: normal;
-	font-style: Italic;
-	color: #000000;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-}
-div.FileContentsDescription {
-	display: block;
-	text-align: left;
-	text-indent: 0pt;
-	margin-top: 15px;
-	margin-bottom: 15px;
-	margin-right: 0.000000pt;
-	margin-left: 15pt;
-	font-weight: normal;
-	font-style: normal;
-	color: #000000;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-}
-pre.FileContents {
-	display: block;
-	text-align: left;
-	text-indent: 0pt;
-	margin-top: 15px;
-	margin-bottom: 15px;
-	margin-right: 0.000000pt;
-	margin-left: 30pt;
-	font-weight: normal;
-	font-style: Italic;
-	color: #000000;
-	text-decoration: none;
-	vertical-align: baseline;
-	text-transform: none;
-}
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/images/EAMaxed.png b/bundles/org.eclipse.platform.doc.user/images/EAMaxed.png
deleted file mode 100644
index 7459473..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/EAMaxed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/EANormal.png b/bundles/org.eclipse.platform.doc.user/images/EANormal.png
deleted file mode 100644
index d103c85..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/EANormal.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/EATrim.png b/bundles/org.eclipse.platform.doc.user/images/EATrim.png
deleted file mode 100644
index 80127b7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/EATrim.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image1.png b/bundles/org.eclipse.platform.doc.user/images/Image1.png
deleted file mode 100644
index 8d812b8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png b/bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png
deleted file mode 100644
index 78e8231..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image11_new_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png b/bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png
deleted file mode 100644
index 27cd3f3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image12_new_project_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png b/bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png
deleted file mode 100644
index 80e9052..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image13_project_in_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png b/bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png
deleted file mode 100644
index e26186e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image14_new_folder_wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png b/bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png
deleted file mode 100644
index 5d54b6a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image15_new_button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png b/bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png
deleted file mode 100644
index 3bb1b81..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image15_project_depend.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png b/bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png
deleted file mode 100644
index 885ef16..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image16_new_pulldown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png b/bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png
deleted file mode 100644
index 8934246..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image17_save_button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png b/bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png
deleted file mode 100644
index d9cba16..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image17b_unsaved_changes.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png b/bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png
deleted file mode 100644
index 8c24e94..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image18_created_resources.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png
deleted file mode 100644
index 07ff602..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image19_close_on_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png b/bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png
deleted file mode 100644
index d49a5a5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image201_filetype.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png b/bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png
deleted file mode 100644
index 41126ff..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image202_editorsel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png b/bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png
deleted file mode 100644
index a3ddbd5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image206_persp_saveas.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png
deleted file mode 100644
index 4705699..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image207_persp_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png
deleted file mode 100644
index c2f1f4d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image208_view_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png b/bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png
deleted file mode 100644
index 1858ec1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image209_workspace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png b/bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png
deleted file mode 100644
index f9501b4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image20_nav_with_resources.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png b/bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png
deleted file mode 100644
index c296192..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image210_filefilter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png b/bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png
deleted file mode 100644
index 5ee086f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image211_fastview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png b/bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png
deleted file mode 100644
index 4794b0c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image211_perspective.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png b/bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png
deleted file mode 100644
index 5c7dd40..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image214_toobar_rsrc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png b/bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png
deleted file mode 100644
index 744007e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image215_toolbar_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png b/bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png
deleted file mode 100644
index 0958234..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image216_history_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png b/bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png
deleted file mode 100644
index 1e2ce70..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image217_pref_wb.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png b/bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png
deleted file mode 100644
index 5f2e8d8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image218_pref_app.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png b/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png
deleted file mode 100644
index adcfcca..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv2.png b/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv2.png
deleted file mode 100644
index dae82a1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image219_pref_cv2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png b/bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png
deleted file mode 100644
index bbcb0d5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image21_task_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png b/bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png
deleted file mode 100644
index c9002d6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image220_pref_dte.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png b/bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png
deleted file mode 100644
index 1371198..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image221_pref_fe.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png b/bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png
deleted file mode 100644
index db9c612..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image222_pref_lh.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png b/bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png
deleted file mode 100644
index b5d4d0b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image223_pref_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png b/bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png
deleted file mode 100644
index 170e718..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image224_pref_build.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png b/bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png
deleted file mode 100644
index 09193e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image229_editor_popup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png b/bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png
deleted file mode 100644
index e28c5bb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image229_view_popup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png b/bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png
deleted file mode 100644
index 0495666..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image230_editor_area.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png b/bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png
deleted file mode 100644
index e91e19c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image231_marker_bar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png b/bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png
deleted file mode 100644
index a00fa67..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image232_marker_context.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png b/bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png
deleted file mode 100644
index 397ec82..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image237_search_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png b/bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png
deleted file mode 100644
index 5fd607c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image240_props_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png b/bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png
deleted file mode 100644
index 15de9b8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image241_nav_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png b/bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png
deleted file mode 100644
index ec3b22f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image242_repo_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png b/bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png
deleted file mode 100644
index dfc461d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image243_tasks_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png b/bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png
deleted file mode 100644
index 4308aa0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image244_bmark_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png b/bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png
deleted file mode 100644
index 2d700d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image245_sync_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png
deleted file mode 100644
index 533d192..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image246_file_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png
deleted file mode 100644
index 16fc41c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image247_projsel_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png
deleted file mode 100644
index fd7501f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image248_folder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png
deleted file mode 100644
index a1db01d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image249_repo_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png b/bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png
deleted file mode 100644
index 5369ff6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image251_proj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png b/bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png
deleted file mode 100644
index ebd1d44..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image252_projref_page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png b/bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png
deleted file mode 100644
index e616458..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image258_perps_custom.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png
deleted file mode 100644
index 288ccf3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image261_import_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png b/bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png
deleted file mode 100644
index 33414d9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image262_import_file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png b/bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png
deleted file mode 100644
index ad52dd2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image262_import_preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png b/bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png
deleted file mode 100644
index 86bd74e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image263_import_cvs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png b/bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png
deleted file mode 100644
index 3314fbb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image263_import_zip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png b/bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png
deleted file mode 100644
index e7f11c7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image264_existing_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png
deleted file mode 100644
index fc01538..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image264_export_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png b/bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png
deleted file mode 100644
index 7d57d4c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image265_export_file.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png b/bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png
deleted file mode 100644
index 4042690..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image265_team_project.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png
deleted file mode 100644
index ae9fa36..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_ant.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png
deleted file mode 100644
index f686c2a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png b/bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png
deleted file mode 100644
index e289ba0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image266_export_zip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png b/bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png
deleted file mode 100644
index 8db3d1c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image268_export_team.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png b/bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png
deleted file mode 100644
index e63b81c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image269_merge_init.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png b/bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png
deleted file mode 100644
index ffd4d1f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image273_local_hist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png b/bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png
deleted file mode 100644
index c54387f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image273_nav-decorators.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png b/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png
deleted file mode 100644
index 8977ae1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png b/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png
deleted file mode 100644
index 204f353..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image274_fonts_preference2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image275_project_explorer.png b/bundles/org.eclipse.platform.doc.user/images/Image275_project_explorer.png
deleted file mode 100644
index 6f2b8e8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image275_project_explorer.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png b/bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png
deleted file mode 100644
index 040f837..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image275_startup_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image276_available_content.png b/bundles/org.eclipse.platform.doc.user/images/Image276_available_content.png
deleted file mode 100644
index 0ad301b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image276_available_content.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image276_available_filters.png b/bundles/org.eclipse.platform.doc.user/images/Image276_available_filters.png
deleted file mode 100644
index 48a320d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image276_available_filters.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png b/bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png
deleted file mode 100644
index 3db775b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image276_search_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png b/bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png
deleted file mode 100644
index 8c1fbd2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image2_active_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png b/bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png
deleted file mode 100644
index aeb1347..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image2_active_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png b/bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png
deleted file mode 100644
index 98a208e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image30_goto_resource.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png b/bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png
deleted file mode 100644
index 81d5d18..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image36_linkedresources.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image37drop.png b/bundles/org.eclipse.platform.doc.user/images/Image37drop.png
deleted file mode 100644
index 6ca4def..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image37drop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image38_import.png b/bundles/org.eclipse.platform.doc.user/images/Image38_import.png
deleted file mode 100644
index 3a6e81f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image38_import.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png b/bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png
deleted file mode 100644
index 2b9502d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image39_import_tree.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image3_single.png b/bundles/org.eclipse.platform.doc.user/images/Image3_single.png
deleted file mode 100644
index e592f18..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image3_single.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png b/bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png
deleted file mode 100644
index b00de0e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image3_tabbed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png b/bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png
deleted file mode 100644
index 379cc4d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image400_filterbutton.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png b/bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png
deleted file mode 100644
index 1a41b95..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image40_import_target.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png b/bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png
deleted file mode 100644
index 1241b52..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image41_import_combo.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image42_export.png b/bundles/org.eclipse.platform.doc.user/images/Image42_export.png
deleted file mode 100644
index 1d20ed8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image42_export.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png b/bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png
deleted file mode 100644
index 1059bf6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image43_export_tree.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png b/bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png
deleted file mode 100644
index 6383d1b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image44_confirm_state.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png b/bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png
deleted file mode 100644
index ce871de..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image45_file_search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image45_setup.png b/bundles/org.eclipse.platform.doc.user/images/Image45_setup.png
deleted file mode 100644
index 6102d96..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image45_setup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image48_move.png b/bundles/org.eclipse.platform.doc.user/images/Image48_move.png
deleted file mode 100644
index f69e4bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image48_move.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image48_rename.png b/bundles/org.eclipse.platform.doc.user/images/Image48_rename.png
deleted file mode 100644
index b28a8fc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image48_rename.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png b/bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png
deleted file mode 100644
index f068edc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image48_rename_done.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png b/bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png
deleted file mode 100644
index df0885e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image49_3_way_compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image4_showview.png b/bundles/org.eclipse.platform.doc.user/images/Image4_showview.png
deleted file mode 100644
index af10210..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image4_showview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image50_search.png b/bundles/org.eclipse.platform.doc.user/images/Image50_search.png
deleted file mode 100644
index 44519f5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image50_search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png b/bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png
deleted file mode 100644
index 0c99729..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_choose_ext.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png
deleted file mode 100644
index eb5722f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_it.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png
deleted file mode 100644
index a98a55e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_next.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_pinview.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_pinview.png
deleted file mode 100644
index 41c395d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_pinview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png
deleted file mode 100644
index 6bb05d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_reduced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png
deleted file mode 100644
index b68c973..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_switching.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png b/bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png
deleted file mode 100644
index dd4ae2e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image51_search_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png b/bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png
deleted file mode 100644
index d660641..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image52_new_task.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png b/bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png
deleted file mode 100644
index cc48634..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_add_task_dlg.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png b/bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png
deleted file mode 100644
index 14d8c55..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_marker1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png b/bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png
deleted file mode 100644
index e592f18..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_newtask.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png b/bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png
deleted file mode 100644
index 336eb16..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image53_task_updated.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png
deleted file mode 100644
index e48f46b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png
deleted file mode 100644
index a6019eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png
deleted file mode 100644
index 43e84a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_added2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png
deleted file mode 100644
index 1314da7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_del1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png
deleted file mode 100644
index c1575bc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png
deleted file mode 100644
index 43e84a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_oneleft.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png
deleted file mode 100644
index 9f5eba2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_remove2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png b/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png
deleted file mode 100644
index e48f46b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image54_bookmark_two.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image55_reset.png b/bundles/org.eclipse.platform.doc.user/images/Image55_reset.png
deleted file mode 100644
index 664db54..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image55_reset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png b/bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png
deleted file mode 100644
index 2471883..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image57_two_editors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png b/bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png
deleted file mode 100644
index 331563c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image5_text_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png b/bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png
deleted file mode 100644
index cad2712..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image602_tar_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png b/bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png
deleted file mode 100644
index e949496..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image60_fast_view1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png b/bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png
deleted file mode 100644
index ae9d23a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png b/bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png
deleted file mode 100644
index 12b7472..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image60_tabs2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image610_et_targets_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image610_et_targets_tab.png
deleted file mode 100644
index 7f87ae7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image610_et_targets_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png
deleted file mode 100644
index 4e94239..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image611_et_main_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png b/bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png
deleted file mode 100644
index e883a73..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image612_et_refresh_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png b/bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png
deleted file mode 100644
index 24f502e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image613_project_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png b/bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png
deleted file mode 100644
index 8fb61dc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image614_et_type_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png b/bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png
deleted file mode 100644
index 9cb138b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image615_program_builder.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png b/bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png
deleted file mode 100644
index f2a0047..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image616_et_dropdown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png b/bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png
deleted file mode 100644
index 32fcade..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image617_jar_inspector.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image619_ole.png b/bundles/org.eclipse.platform.doc.user/images/Image619_ole.png
deleted file mode 100644
index 3e9533b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image619_ole.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png b/bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png
deleted file mode 100644
index db5b218..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_minimize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png b/bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png
deleted file mode 100644
index 5772a1b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image61_fast_options.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png b/bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png
deleted file mode 100644
index f1cb9aa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image61_nav_fast.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png b/bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png
deleted file mode 100644
index 475655c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_select_pers.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png b/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png
deleted file mode 100644
index 95cdae6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png b/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png
deleted file mode 100644
index 97cbdfd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png b/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png
deleted file mode 100644
index 1eb9e0b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image70_shortcut4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_arrow.png b/bundles/org.eclipse.platform.doc.user/images/Image71_arrow.png
deleted file mode 100644
index 05a11e4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_arrow.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_dialog_menu.png b/bundles/org.eclipse.platform.doc.user/images/Image71_dialog_menu.png
deleted file mode 100644
index 39692b3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_dialog_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_dialog_toolbar.png b/bundles/org.eclipse.platform.doc.user/images/Image71_dialog_toolbar.png
deleted file mode 100644
index 6c0a9b6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_dialog_toolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_after.png b/bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_after.png
deleted file mode 100644
index 6ce8bb7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_after.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_before.png b/bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_before.png
deleted file mode 100644
index 4b5fd0b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_file_menu_before.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_after.png b/bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_after.png
deleted file mode 100644
index 01e998e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_after.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_before.png b/bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_before.png
deleted file mode 100644
index 0868862..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_file_toolbar_before.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png
deleted file mode 100644
index 98acdc1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png
deleted file mode 100644
index 0ea9bbf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_reset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png b/bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png
deleted file mode 100644
index 5b0cce4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image71_pers_save.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png b/bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png
deleted file mode 100644
index 224c3d2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image7_view_pulldown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare.png
deleted file mode 100644
index 55adc06..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png
deleted file mode 100644
index ad1146b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_after.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png
deleted file mode 100644
index f86758c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_change2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png
deleted file mode 100644
index 73387a4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png
deleted file mode 100644
index 5c1acd1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png b/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png
deleted file mode 100644
index 670bb1e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image80_compare_editor3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png
deleted file mode 100644
index c2f1406..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import2_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png
deleted file mode 100644
index 9a50921..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import3_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png
deleted file mode 100644
index 56a23e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import4_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png b/bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png
deleted file mode 100644
index fd0aa66..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_import_project_fred.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_nav.png b/bundles/org.eclipse.platform.doc.user/images/Image82_nav.png
deleted file mode 100644
index 9209ac1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png
deleted file mode 100644
index a48b26a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png
deleted file mode 100644
index 226b895..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_new3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png
deleted file mode 100644
index 3cda50b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png
deleted file mode 100644
index 6dba7de..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_sync2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png
deleted file mode 100644
index ae43f8d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_team.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png b/bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png
deleted file mode 100644
index 5ff24f4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image82_repo_view1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png b/bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png
deleted file mode 100644
index ffe6b16..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_cvs_savedpasswords.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png b/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png
deleted file mode 100644
index 0f444f5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png b/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png
deleted file mode 100644
index 5c96d77..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_fred_verson2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png
deleted file mode 100644
index ede9035..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png
deleted file mode 100644
index f180853..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane-sync.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png
deleted file mode 100644
index 348e9fa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png
deleted file mode 100644
index afa9e0e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png b/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png
deleted file mode 100644
index 0fe3020..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image83_jane3_conflict2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_pref.png
deleted file mode 100644
index 05cf66e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_decorator_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png b/bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png
deleted file mode 100644
index a89f487..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_replace2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image84_replace3.png b/bundles/org.eclipse.platform.doc.user/images/Image84_replace3.png
deleted file mode 100644
index 88649a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image84_replace3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png b/bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png
deleted file mode 100644
index 98678d0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image87_workset_sel.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png b/bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png
deleted file mode 100644
index 3864695..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image88_workset_new_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png b/bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png
deleted file mode 100644
index 6c3aa7b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image89_workset_new_res.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image8_view.png b/bundles/org.eclipse.platform.doc.user/images/Image8_view.png
deleted file mode 100644
index a76054d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image8_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png b/bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png
deleted file mode 100644
index 398ce77..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image90_locked_toolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png b/bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png
deleted file mode 100644
index 6f329ad..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image90_unlocked_toolbar.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png b/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png
deleted file mode 100644
index d34f833..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png b/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png
deleted file mode 100644
index 8f0fcd6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png b/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png
deleted file mode 100644
index 37062f0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image91_ant_prefs_3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png b/bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png
deleted file mode 100644
index cb0d2c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image9_viewdownarrow.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png
deleted file mode 100644
index 9dd1873..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_ignore_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png b/bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png
deleted file mode 100644
index 8291e5a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_pref_inup.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png b/bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png
deleted file mode 100644
index 3ff5544..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/Image_team_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/TrimStack.png b/bundles/org.eclipse.platform.doc.user/images/TrimStack.png
deleted file mode 100644
index 2f2fcb5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/TrimStack.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png b/bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png
deleted file mode 100644
index fbb4cea..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/addbkmrk_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/addtask.png b/bundles/org.eclipse.platform.doc.user/images/addtask.png
deleted file mode 100644
index 8d42cbf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/addtask.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/alpha_mode.png b/bundles/org.eclipse.platform.doc.user/images/alpha_mode.png
deleted file mode 100644
index 585fd8a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/alpha_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ancestorpane_co.gif b/bundles/org.eclipse.platform.doc.user/images/ancestorpane_co.gif
deleted file mode 100644
index ff06855..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ancestorpane_co.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png b/bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png
deleted file mode 100644
index 466f492..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_code_assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png
deleted file mode 100644
index c6012c5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_appearance.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png
deleted file mode 100644
index cff1140..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_folding.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png
deleted file mode 100644
index c51b299..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_problems.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png b/bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png
deleted file mode 100644
index cb726e6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_editor_syntax.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_formatter.png b/bundles/org.eclipse.platform.doc.user/images/ant_formatter.png
deleted file mode 100644
index 0f61905..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_formatter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_prefs.png b/bundles/org.eclipse.platform.doc.user/images/ant_prefs.png
deleted file mode 100644
index 844950a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png b/bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png
deleted file mode 100644
index 870f32f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_run_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png b/bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png
deleted file mode 100644
index 4084009..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_runtime_properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_templates.png b/bundles/org.eclipse.platform.doc.user/images/ant_templates.png
deleted file mode 100644
index 60699a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_templates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ant_view.png b/bundles/org.eclipse.platform.doc.user/images/ant_view.png
deleted file mode 100644
index 2dcbdde..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ant_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg b/bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg
deleted file mode 100644
index 99e4170..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/arch-npi.jpg
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/backward_nav.png b/bundles/org.eclipse.platform.doc.user/images/backward_nav.png
deleted file mode 100644
index 8b022d1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/backward_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/block_selection_mode.gif b/bundles/org.eclipse.platform.doc.user/images/block_selection_mode.gif
deleted file mode 100644
index dc486d1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/block_selection_mode.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/build_exec.png b/bundles/org.eclipse.platform.doc.user/images/build_exec.png
deleted file mode 100644
index fdf4f82..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/build_exec.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cap-conf.png b/bundles/org.eclipse.platform.doc.user/images/cap-conf.png
deleted file mode 100644
index 59f8887..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cap-conf.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png b/bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png
deleted file mode 100644
index 93da5f8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cap-pref-advanced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cap-pref.png b/bundles/org.eclipse.platform.doc.user/images/cap-pref.png
deleted file mode 100644
index 2f04243..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cap-pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/change-obj.gif b/bundles/org.eclipse.platform.doc.user/images/change-obj.gif
deleted file mode 100644
index ce8bdb9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/change-obj.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png b/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png
deleted file mode 100644
index c323a94..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_running.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png b/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png
deleted file mode 100644
index 0e08eb8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cheatsheet_composite_start.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/close_view.png b/bundles/org.eclipse.platform.doc.user/images/close_view.png
deleted file mode 100644
index f69be2f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/close_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/compare-editor-diff-change.png b/bundles/org.eclipse.platform.doc.user/images/compare-editor-diff-change.png
deleted file mode 100644
index efd26bb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/compare-editor-diff-change.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/compare-editor.png b/bundles/org.eclipse.platform.doc.user/images/compare-editor.png
deleted file mode 100644
index 7029654..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/compare-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/confadd_ov.png b/bundles/org.eclipse.platform.doc.user/images/confadd_ov.png
deleted file mode 100644
index c5d4b6d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/confadd_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/confchg_ov.png b/bundles/org.eclipse.platform.doc.user/images/confchg_ov.png
deleted file mode 100644
index 806aad1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/confchg_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/confdel_ov.png b/bundles/org.eclipse.platform.doc.user/images/confdel_ov.png
deleted file mode 100644
index 8cfd1c1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/confdel_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/content_type.png b/bundles/org.eclipse.platform.doc.user/images/content_type.png
deleted file mode 100644
index 6d46301..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/content_type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png b/bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png
deleted file mode 100644
index c7d0795..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/contenttype-pref-charset.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/copy_edit.png b/bundles/org.eclipse.platform.doc.user/images/copy_edit.png
deleted file mode 100644
index a3d7188..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/copy_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/copy_l_co.gif b/bundles/org.eclipse.platform.doc.user/images/copy_l_co.gif
deleted file mode 100644
index e029948..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/copy_l_co.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/copy_r_co.gif b/bundles/org.eclipse.platform.doc.user/images/copy_r_co.gif
deleted file mode 100644
index 0659813..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/copy_r_co.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/copycont_l_co.gif b/bundles/org.eclipse.platform.doc.user/images/copycont_l_co.gif
deleted file mode 100644
index db2b1e3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/copycont_l_co.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/copycont_r_co.gif b/bundles/org.eclipse.platform.doc.user/images/copycont_r_co.gif
deleted file mode 100644
index 9ebd50a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/copycont_r_co.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cut_edit.png b/bundles/org.eclipse.platform.doc.user/images/cut_edit.png
deleted file mode 100644
index 3d32818..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cut_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-annotate.png b/bundles/org.eclipse.platform.doc.user/images/cvs-annotate.png
deleted file mode 100644
index e95ee1e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-annotate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png
deleted file mode 100644
index 63ad2fe..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png
deleted file mode 100644
index 4bfd7e2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png
deleted file mode 100644
index 4e8653d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png
deleted file mode 100644
index ea4d74a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png b/bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png
deleted file mode 100644
index 967966d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-checkout5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates.png b/bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates.png
deleted file mode 100644
index f3214af..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates2.png b/bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates2.png
deleted file mode 100644
index 5b0cf93..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-commenttemplates2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-connection.png b/bundles/org.eclipse.platform.doc.user/images/cvs-connection.png
deleted file mode 100644
index ddd686e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-connection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png b/bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png
deleted file mode 100644
index 7287095..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-console-prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-console.png b/bundles/org.eclipse.platform.doc.user/images/cvs-console.png
deleted file mode 100644
index d560816..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-console.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png b/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png
deleted file mode 100644
index a926402..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png b/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png
deleted file mode 100644
index 1bdb117..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-icon.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png b/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png
deleted file mode 100644
index 0f89e59..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-decoration-text.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-ext.png b/bundles/org.eclipse.platform.doc.user/images/cvs-ext.png
deleted file mode 100644
index 0e52a17..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-ext.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-files.png b/bundles/org.eclipse.platform.doc.user/images/cvs-files.png
deleted file mode 100644
index 934d05f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-files.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-general.png b/bundles/org.eclipse.platform.doc.user/images/cvs-general.png
deleted file mode 100644
index 357e3c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png b/bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png
deleted file mode 100644
index 6fea480..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-merge-sync.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-password.png b/bundles/org.eclipse.platform.doc.user/images/cvs-password.png
deleted file mode 100644
index a2f2651..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-password.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png b/bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png
deleted file mode 100644
index e821bdc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-prompting.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share1.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share1.png
deleted file mode 100644
index 88017ea..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share2.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share2.png
deleted file mode 100644
index d09f690..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share3.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share3.png
deleted file mode 100644
index 22fbb06..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-share4.png b/bundles/org.eclipse.platform.doc.user/images/cvs-share4.png
deleted file mode 100644
index df3c131..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-share4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-specify-repository.png b/bundles/org.eclipse.platform.doc.user/images/cvs-specify-repository.png
deleted file mode 100644
index 035abd0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-specify-repository.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png b/bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png
deleted file mode 100644
index 1bccf71..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-sync-compare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-updatemerge.png b/bundles/org.eclipse.platform.doc.user/images/cvs-updatemerge.png
deleted file mode 100644
index f57d2ad..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-updatemerge.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png b/bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png
deleted file mode 100644
index 6c57603..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs-watch-edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_change_ascii_binary_prop.png b/bundles/org.eclipse.platform.doc.user/images/cvs_change_ascii_binary_prop.png
deleted file mode 100644
index 5df14b5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_change_ascii_binary_prop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_configure_branches_and_versions.png b/bundles/org.eclipse.platform.doc.user/images/cvs_configure_branches_and_versions.png
deleted file mode 100644
index efd0fac..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_configure_branches_and_versions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_filter_res_history.png b/bundles/org.eclipse.platform.doc.user/images/cvs_filter_res_history.png
deleted file mode 100644
index 365aec3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_filter_res_history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png b/bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png
deleted file mode 100644
index a01ac81..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_folder_rep.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png b/bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png
deleted file mode 100644
index 235ec1e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_module_rep.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_new_branch.png b/bundles/org.eclipse.platform.doc.user/images/cvs_new_branch.png
deleted file mode 100644
index 8732bec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_new_branch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/cvs_refresh_branches.png b/bundles/org.eclipse.platform.doc.user/images/cvs_refresh_branches.png
deleted file mode 100644
index 01e6dad..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/cvs_refresh_branches.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/debug_exec.png b/bundles/org.eclipse.platform.doc.user/images/debug_exec.png
deleted file mode 100644
index c76ecad..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/debug_exec.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/defaults_ps.png b/bundles/org.eclipse.platform.doc.user/images/defaults_ps.png
deleted file mode 100644
index 6fc29e6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/defaults_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/delete_edit.png b/bundles/org.eclipse.platform.doc.user/images/delete_edit.png
deleted file mode 100644
index e93c632..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/delete_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/detachview2.png b/bundles/org.eclipse.platform.doc.user/images/detachview2.png
deleted file mode 100644
index b74b62f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/detachview2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/dirty_ov.png b/bundles/org.eclipse.platform.doc.user/images/dirty_ov.png
deleted file mode 100644
index 253d03d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/dirty_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png
deleted file mode 100644
index aaa56d1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_bottom_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png
deleted file mode 100644
index 66e2b7a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_invalid_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_left_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_left_source.png
deleted file mode 100644
index d009b50..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_left_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_offscreen_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_offscreen_source.png
deleted file mode 100644
index 9527b55..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_offscreen_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_right_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_right_source.png
deleted file mode 100644
index 36ccf37..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_right_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_stack.png b/bundles/org.eclipse.platform.doc.user/images/drop_stack.png
deleted file mode 100644
index 813c553..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_stack.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/drop_top_source.png b/bundles/org.eclipse.platform.doc.user/images/drop_top_source.png
deleted file mode 100644
index 49b9743..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/drop_top_source.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/edited_ov.png b/bundles/org.eclipse.platform.doc.user/images/edited_ov.png
deleted file mode 100644
index fd40606..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/edited_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_pswd.png b/bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_pswd.png
deleted file mode 100644
index 3891584..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_pswd.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_start.png b/bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_start.png
deleted file mode 100644
index 7e653f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/equinox_secure_storage_start.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/et_dialog.png b/bundles/org.eclipse.platform.doc.user/images/et_dialog.png
deleted file mode 100644
index 3855fdc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/et_dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/et_dropdown.png b/bundles/org.eclipse.platform.doc.user/images/et_dropdown.png
deleted file mode 100644
index 25895c8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/et_dropdown.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/export_wiz.png b/bundles/org.eclipse.platform.doc.user/images/export_wiz.png
deleted file mode 100644
index f83ccda..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/export_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/external_tools.png b/bundles/org.eclipse.platform.doc.user/images/external_tools.png
deleted file mode 100644
index 5dfe6da..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/external_tools.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png b/bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png
deleted file mode 100644
index 34e6985..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/external_tools_prefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/fast_view_menu.png b/bundles/org.eclipse.platform.doc.user/images/fast_view_menu.png
deleted file mode 100644
index 2f7c97d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/fast_view_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/filter_ps.png b/bundles/org.eclipse.platform.doc.user/images/filter_ps.png
deleted file mode 100644
index ace1090..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/filter_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/first_anteditor.png b/bundles/org.eclipse.platform.doc.user/images/first_anteditor.png
deleted file mode 100644
index 2bab7a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/first_anteditor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/forward_nav.png b/bundles/org.eclipse.platform.doc.user/images/forward_nav.png
deleted file mode 100644
index a6afdee..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/forward_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png b/bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png
deleted file mode 100644
index cc5e088..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/gotoobj_tsk.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon.png b/bundles/org.eclipse.platform.doc.user/images/help_icon.png
deleted file mode 100644
index e073dd6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_back.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_back.png
deleted file mode 100644
index ee3f975..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_back.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_book_closed.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_book_closed.png
deleted file mode 100644
index 3f1da0f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_book_closed.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_book_open.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_book_open.png
deleted file mode 100644
index ac3129c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_book_open.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark.png
deleted file mode 100644
index 42d2478..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark_add.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark_add.png
deleted file mode 100644
index 73580b2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_bookmark_add.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_capabilities.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_capabilities.png
deleted file mode 100644
index bd8803a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_capabilities.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_external.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_external.png
deleted file mode 100644
index 49a30bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_external.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_forward.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_forward.png
deleted file mode 100644
index 262a94f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_forward.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_highlight.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_highlight.png
deleted file mode 100644
index a220145..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_highlight.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_home.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_home.png
deleted file mode 100644
index 2e69ffd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_home.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_maximize.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_maximize.png
deleted file mode 100644
index ee67ced..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_maximize.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_print.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_print.png
deleted file mode 100644
index 1d46567..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_print.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_restore.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_restore.png
deleted file mode 100644
index b29a407..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_restore.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_search_infocenter.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_search_infocenter.png
deleted file mode 100644
index 54c089d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_search_infocenter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_search_local.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_search_local.png
deleted file mode 100644
index a32d1a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_search_local.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_search_web.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_search_web.png
deleted file mode 100644
index 5017276..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_search_web.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_sync.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_sync.png
deleted file mode 100644
index ed24449..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_sync.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_toc.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_toc.png
deleted file mode 100644
index 442b0c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_toc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_topic.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_topic.png
deleted file mode 100644
index b790314..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_topic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_icon_topic_container.png b/bundles/org.eclipse.platform.doc.user/images/help_icon_topic_container.png
deleted file mode 100644
index d092562..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_icon_topic_container.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_infopop.png b/bundles/org.eclipse.platform.doc.user/images/help_infopop.png
deleted file mode 100644
index e00d90b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_infopop.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_preference.png b/bundles/org.eclipse.platform.doc.user/images/help_preference.png
deleted file mode 100644
index 8d6fab0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_preference_content.png b/bundles/org.eclipse.platform.doc.user/images/help_preference_content.png
deleted file mode 100644
index 5856d55..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_preference_content.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_preference_infocenter.png b/bundles/org.eclipse.platform.doc.user/images/help_preference_infocenter.png
deleted file mode 100644
index 59e1acf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_preference_infocenter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_preference_server.png b/bundles/org.eclipse.platform.doc.user/images/help_preference_server.png
deleted file mode 100644
index 55a04d4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_preference_server.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_view_bookmarks.png b/bundles/org.eclipse.platform.doc.user/images/help_view_bookmarks.png
deleted file mode 100644
index 7a0f835..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_view_bookmarks.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_view_context.png b/bundles/org.eclipse.platform.doc.user/images/help_view_context.png
deleted file mode 100644
index 3883710..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_view_context.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_view_index.png b/bundles/org.eclipse.platform.doc.user/images/help_view_index.png
deleted file mode 100644
index afb1c54..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_view_index.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_view_search.png b/bundles/org.eclipse.platform.doc.user/images/help_view_search.png
deleted file mode 100644
index f573b97..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_view_search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_view_toc.png b/bundles/org.eclipse.platform.doc.user/images/help_view_toc.png
deleted file mode 100644
index 91184ea..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_view_toc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_window.png b/bundles/org.eclipse.platform.doc.user/images/help_window.png
deleted file mode 100644
index 8bc27e9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_window.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/help_window_external.png b/bundles/org.eclipse.platform.doc.user/images/help_window_external.png
deleted file mode 100644
index 0cc7ec9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/help_window_external.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-begin.png b/bundles/org.eclipse.platform.doc.user/images/image92-begin.png
deleted file mode 100644
index 6762771..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-begin.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-check.png b/bundles/org.eclipse.platform.doc.user/images/image92-check.png
deleted file mode 100644
index 3152095..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-check.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-close.png b/bundles/org.eclipse.platform.doc.user/images/image92-close.png
deleted file mode 100644
index e97c452..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-close.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-collapse.png b/bundles/org.eclipse.platform.doc.user/images/image92-collapse.png
deleted file mode 100644
index a57ea8b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-collapse.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-complete.png b/bundles/org.eclipse.platform.doc.user/images/image92-complete.png
deleted file mode 100644
index b6ab32b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-complete.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-expand.png b/bundles/org.eclipse.platform.doc.user/images/image92-expand.png
deleted file mode 100644
index 8cb2274..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-expand.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-help.png b/bundles/org.eclipse.platform.doc.user/images/image92-help.png
deleted file mode 100644
index 787e064..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-help.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-hide.png b/bundles/org.eclipse.platform.doc.user/images/image92-hide.png
deleted file mode 100644
index f16ba73..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-hide.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png b/bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png
deleted file mode 100644
index 76e5b76..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-opencheat.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-perform.png b/bundles/org.eclipse.platform.doc.user/images/image92-perform.png
deleted file mode 100644
index 93e8f53..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-perform.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-redo.png b/bundles/org.eclipse.platform.doc.user/images/image92-redo.png
deleted file mode 100644
index c958d59..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-redo.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-restart.png b/bundles/org.eclipse.platform.doc.user/images/image92-restart.png
deleted file mode 100644
index 501931a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-restart.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-save.png b/bundles/org.eclipse.platform.doc.user/images/image92-save.png
deleted file mode 100644
index 61e5d54..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-save.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-select.png b/bundles/org.eclipse.platform.doc.user/images/image92-select.png
deleted file mode 100644
index 3c6c587..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-select.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png b/bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png
deleted file mode 100644
index 73b7743..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-skip-mark.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/image92-skip.png b/bundles/org.eclipse.platform.doc.user/images/image92-skip.png
deleted file mode 100644
index 934a2e6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/image92-skip.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/import_wiz.png b/bundles/org.eclipse.platform.doc.user/images/import_wiz.png
deleted file mode 100644
index f65ecb2..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/import_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/keys1.png b/bundles/org.eclipse.platform.doc.user/images/keys1.png
deleted file mode 100644
index 6cdf51a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/keys1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/keys2.png b/bundles/org.eclipse.platform.doc.user/images/keys2.png
deleted file mode 100644
index 0ef0aba..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/keys2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/keys3.png b/bundles/org.eclipse.platform.doc.user/images/keys3.png
deleted file mode 100644
index b5af876..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/keys3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/keys4.png b/bundles/org.eclipse.platform.doc.user/images/keys4.png
deleted file mode 100644
index 815c8f6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/keys4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png b/bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png
deleted file mode 100644
index 11391fc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/last_edit_pos.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/localHistoryCompare.png b/bundles/org.eclipse.platform.doc.user/images/localHistoryCompare.png
deleted file mode 100644
index 28bce31..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/localHistoryCompare.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/localHistoryView.png b/bundles/org.eclipse.platform.doc.user/images/localHistoryView.png
deleted file mode 100644
index 7783343..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/localHistoryView.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/local_history_mode.png b/bundles/org.eclipse.platform.doc.user/images/local_history_mode.png
deleted file mode 100644
index 8b8b883..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/local_history_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png b/bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png
deleted file mode 100644
index e4cb1d0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/mark_occurrences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/max.png b/bundles/org.eclipse.platform.doc.user/images/max.png
deleted file mode 100644
index 84e7584..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/max.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/merged_ov.png b/bundles/org.eclipse.platform.doc.user/images/merged_ov.png
deleted file mode 100644
index b00a69b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/merged_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/minmaxOptions.png b/bundles/org.eclipse.platform.doc.user/images/minmaxOptions.png
deleted file mode 100644
index f575a05..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/minmaxOptions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/net-general.png b/bundles/org.eclipse.platform.doc.user/images/net-general.png
deleted file mode 100644
index fdf036d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/net-general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/new_persp.png b/bundles/org.eclipse.platform.doc.user/images/new_persp.png
deleted file mode 100644
index 18f50e0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/new_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/new_wiz.png b/bundles/org.eclipse.platform.doc.user/images/new_wiz.png
deleted file mode 100644
index 80b3a54..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/new_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png b/bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png
deleted file mode 100644
index 356239b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/newfile_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png b/bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png
deleted file mode 100644
index 86a4f30..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/newfolder_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png b/bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png
deleted file mode 100644
index bbee775..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/newprj_wiz.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/next_change_nav.gif b/bundles/org.eclipse.platform.doc.user/images/next_change_nav.gif
deleted file mode 100644
index 6f7b277..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/next_change_nav.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/next_diff_nav.gif b/bundles/org.eclipse.platform.doc.user/images/next_diff_nav.gif
deleted file mode 100644
index 79cda13..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/next_diff_nav.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/next_nav.png b/bundles/org.eclipse.platform.doc.user/images/next_nav.png
deleted file mode 100644
index 0328357..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/next_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngrelc.png b/bundles/org.eclipse.platform.doc.user/images/ngrelc.png
deleted file mode 100644
index 161e3aa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngrelc.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngrelr.png b/bundles/org.eclipse.platform.doc.user/images/ngrelr.png
deleted file mode 100644
index 4726f8c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngrelr.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ngrelt.png b/bundles/org.eclipse.platform.doc.user/images/ngrelt.png
deleted file mode 100644
index 74bee2b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ngrelt.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png b/bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png
deleted file mode 100644
index 2aa0e84..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/no_remotedir_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/open_persp.png b/bundles/org.eclipse.platform.doc.user/images/open_persp.png
deleted file mode 100644
index 47616cd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/open_persp.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png
deleted file mode 100644
index 01d1608..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/add_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png
deleted file mode 100644
index 7d42ca5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/ant_targets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/filter_internal_targets.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/filter_internal_targets.png
deleted file mode 100644
index c13bd06..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/filter_internal_targets.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png
deleted file mode 100644
index dedd6f7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png
deleted file mode 100644
index a3884fb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/refresh.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png
deleted file mode 100644
index ea14834..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png
deleted file mode 100644
index 8308efe..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/remove_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png
deleted file mode 100644
index 5bd0e13..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/run_tool.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png
deleted file mode 100644
index c549447..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/clcl16/search.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png
deleted file mode 100644
index 5dfe6da..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/ctool16/external_tools.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png
deleted file mode 100644
index f304510..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/cview16/ant_view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png
deleted file mode 100644
index cf88df0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png
deleted file mode 100644
index 653215a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png
deleted file mode 100644
index e66c98e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/ant_target_err.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png
deleted file mode 100644
index c87f431..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/build_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png
deleted file mode 100644
index 0b5d271..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/classpath.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png
deleted file mode 100644
index 1e3df57..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png
deleted file mode 100644
index 5bf4a40..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/import_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png
deleted file mode 100644
index 0e02f53..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png
deleted file mode 100644
index 281b5e8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png
deleted file mode 100644
index 365cfbb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png
deleted file mode 100644
index 2cbe988..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/main_tab.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png
deleted file mode 100644
index dedd6f7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/prop_ps.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png
deleted file mode 100644
index 7841e76..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/property_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png
deleted file mode 100644
index 4e10cf4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png
deleted file mode 100644
index 705a33e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png
deleted file mode 100644
index 0a915c6..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/task_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png b/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png
deleted file mode 100644
index 9fd1b3f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/org.eclipse.ui.externaltools/obj16/type.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/outline_hello.png b/bundles/org.eclipse.platform.doc.user/images/outline_hello.png
deleted file mode 100644
index 13b61fc..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/outline_hello.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/paste_edit.png b/bundles/org.eclipse.platform.doc.user/images/paste_edit.png
deleted file mode 100644
index b66e9dd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/paste_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/pin_editor.png b/bundles/org.eclipse.platform.doc.user/images/pin_editor.png
deleted file mode 100644
index 903588d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/pin_editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prb_quickfix.png b/bundles/org.eclipse.platform.doc.user/images/prb_quickfix.png
deleted file mode 100644
index d996b2a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prb_quickfix.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prbfil.png b/bundles/org.eclipse.platform.doc.user/images/prbfil.png
deleted file mode 100644
index 3ef6312..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prbfil.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prev_change_nav.gif b/bundles/org.eclipse.platform.doc.user/images/prev_change_nav.gif
deleted file mode 100644
index 3e79ebf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prev_change_nav.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prev_diff_nav.gif b/bundles/org.eclipse.platform.doc.user/images/prev_diff_nav.gif
deleted file mode 100644
index d5a96ec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prev_diff_nav.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prev_nav.png b/bundles/org.eclipse.platform.doc.user/images/prev_nav.png
deleted file mode 100644
index 830c2c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prev_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/print_edit.png b/bundles/org.eclipse.platform.doc.user/images/print_edit.png
deleted file mode 100644
index 1d46567..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/print_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/prob.png b/bundles/org.eclipse.platform.doc.user/images/prob.png
deleted file mode 100644
index b50e4f1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/prob.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/question_ov.png b/bundles/org.eclipse.platform.doc.user/images/question_ov.png
deleted file mode 100644
index 921a272..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/question_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png
deleted file mode 100644
index c69417d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_inadd_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png
deleted file mode 100644
index 995e896..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_inchg_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png
deleted file mode 100644
index 050859a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_indel_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png
deleted file mode 100644
index 2a919c8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_outadd_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png
deleted file mode 100644
index 2a126be..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_outchg_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png b/bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png
deleted file mode 100644
index 8ea3b58..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/r_outdel_ov.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/redo_edit.png b/bundles/org.eclipse.platform.doc.user/images/redo_edit.png
deleted file mode 100644
index 4442683..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/redo_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-1.png b/bundles/org.eclipse.platform.doc.user/images/ref-1.png
deleted file mode 100644
index 666a5ec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-10.png b/bundles/org.eclipse.platform.doc.user/images/ref-10.png
deleted file mode 100644
index 0430baa..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-10.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-11.png b/bundles/org.eclipse.platform.doc.user/images/ref-11.png
deleted file mode 100644
index fddcb8c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-11.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-12.png b/bundles/org.eclipse.platform.doc.user/images/ref-12.png
deleted file mode 100644
index 835714b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-12.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-15.png b/bundles/org.eclipse.platform.doc.user/images/ref-15.png
deleted file mode 100644
index 0c63917..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-15.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-16.png b/bundles/org.eclipse.platform.doc.user/images/ref-16.png
deleted file mode 100644
index 7be849e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-16.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-17.png b/bundles/org.eclipse.platform.doc.user/images/ref-17.png
deleted file mode 100644
index 60c9c4b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-17.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-18.png b/bundles/org.eclipse.platform.doc.user/images/ref-18.png
deleted file mode 100644
index bd6fce8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-18.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-2.png b/bundles/org.eclipse.platform.doc.user/images/ref-2.png
deleted file mode 100644
index bf3dd39..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-20.png b/bundles/org.eclipse.platform.doc.user/images/ref-20.png
deleted file mode 100644
index 6cb6b84..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-20.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-21.png b/bundles/org.eclipse.platform.doc.user/images/ref-21.png
deleted file mode 100644
index de00eec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-21.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-22.png b/bundles/org.eclipse.platform.doc.user/images/ref-22.png
deleted file mode 100644
index 68759f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-22.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-23.png b/bundles/org.eclipse.platform.doc.user/images/ref-23.png
deleted file mode 100644
index 0a2fa7f..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-23.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-24.png b/bundles/org.eclipse.platform.doc.user/images/ref-24.png
deleted file mode 100644
index 77a4a7e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-24.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-25.png b/bundles/org.eclipse.platform.doc.user/images/ref-25.png
deleted file mode 100644
index 28d36eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-25.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-3.png b/bundles/org.eclipse.platform.doc.user/images/ref-3.png
deleted file mode 100644
index 67389bf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-4.png b/bundles/org.eclipse.platform.doc.user/images/ref-4.png
deleted file mode 100644
index 7655e93..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-4.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-5.png b/bundles/org.eclipse.platform.doc.user/images/ref-5.png
deleted file mode 100644
index dfa9678..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-5.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-52.png b/bundles/org.eclipse.platform.doc.user/images/ref-52.png
deleted file mode 100644
index d887221..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-52.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-7.png b/bundles/org.eclipse.platform.doc.user/images/ref-7.png
deleted file mode 100644
index 7a92e05..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-7.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-79.png b/bundles/org.eclipse.platform.doc.user/images/ref-79.png
deleted file mode 100644
index 4d4b6e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-79.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-8.png b/bundles/org.eclipse.platform.doc.user/images/ref-8.png
deleted file mode 100644
index 58a4190..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-8.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-9.png b/bundles/org.eclipse.platform.doc.user/images/ref-9.png
deleted file mode 100644
index 2bb8b3d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-9.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png b/bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png
deleted file mode 100644
index e2c0fb3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-accessibility.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png b/bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png
deleted file mode 100644
index c76eb80..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-annotationspref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-p2-autoupdate.png b/bundles/org.eclipse.platform.doc.user/images/ref-p2-autoupdate.png
deleted file mode 100644
index d19326c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-p2-autoupdate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-p2-installupdate.png b/bundles/org.eclipse.platform.doc.user/images/ref-p2-installupdate.png
deleted file mode 100644
index a306449..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-p2-installupdate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-p2-siteprefs.png b/bundles/org.eclipse.platform.doc.user/images/ref-p2-siteprefs.png
deleted file mode 100644
index 6d54efe..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-p2-siteprefs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png
deleted file mode 100644
index 520dfec..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-quickdiffpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png
deleted file mode 100644
index 6f8dc4e..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-spellingpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-templates-view.png b/bundles/org.eclipse.platform.doc.user/images/ref-templates-view.png
deleted file mode 100644
index fc91c6d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-templates-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png
deleted file mode 100644
index 9a9eb9b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-texteditorpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png b/bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png
deleted file mode 100644
index c7f40a3..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ref-webbrowserpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/refresh_nav.png b/bundles/org.eclipse.platform.doc.user/images/refresh_nav.png
deleted file mode 100644
index e920f9b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/refresh_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/remote_history_mode.png b/bundles/org.eclipse.platform.doc.user/images/remote_history_mode.png
deleted file mode 100644
index 28e2be7..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/remote_history_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res.png b/bundles/org.eclipse.platform.doc.user/images/res.png
deleted file mode 100644
index 819888d..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_blocked.png b/bundles/org.eclipse.platform.doc.user/images/res_blocked.png
deleted file mode 100644
index 196b25b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_blocked.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_build.png b/bundles/org.eclipse.platform.doc.user/images/res_build.png
deleted file mode 100644
index 0aac923..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_build.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_details.png b/bundles/org.eclipse.platform.doc.user/images/res_details.png
deleted file mode 100644
index 2371d52..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_details.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png b/bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png
deleted file mode 100644
index d236a35..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_otherjobs.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/res_pref.png b/bundles/org.eclipse.platform.doc.user/images/res_pref.png
deleted file mode 100644
index 7b41927..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/res_pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/run_exec.png b/bundles/org.eclipse.platform.doc.user/images/run_exec.png
deleted file mode 100644
index 5bd0e13..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/run_exec.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/save_edit.png b/bundles/org.eclipse.platform.doc.user/images/save_edit.png
deleted file mode 100644
index 5f0fb5b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/save_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/saveall_edit.png b/bundles/org.eclipse.platform.doc.user/images/saveall_edit.png
deleted file mode 100644
index eeea6be..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/saveall_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/saveas_edit.png b/bundles/org.eclipse.platform.doc.user/images/saveas_edit.png
deleted file mode 100644
index 5c364cf..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/saveas_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/search_src.png b/bundles/org.eclipse.platform.doc.user/images/search_src.png
deleted file mode 100644
index c549447..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/search_src.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/searchm_obj.png b/bundles/org.eclipse.platform.doc.user/images/searchm_obj.png
deleted file mode 100644
index 5a2a75a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/searchm_obj.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/segment_edit.png b/bundles/org.eclipse.platform.doc.user/images/segment_edit.png
deleted file mode 100644
index aa0dc0b..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/segment_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/show_whitespace_chars.gif b/bundles/org.eclipse.platform.doc.user/images/show_whitespace_chars.gif
deleted file mode 100644
index a2587b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/show_whitespace_chars.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/showcat_co.png b/bundles/org.eclipse.platform.doc.user/images/showcat_co.png
deleted file mode 100644
index f61cb45..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/showcat_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/showdesc_co.png b/bundles/org.eclipse.platform.doc.user/images/showdesc_co.png
deleted file mode 100644
index 647885c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/showdesc_co.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ssh2-general.png b/bundles/org.eclipse.platform.doc.user/images/ssh2-general.png
deleted file mode 100644
index c820cc4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ssh2-general.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ssh2-hosts.png b/bundles/org.eclipse.platform.doc.user/images/ssh2-hosts.png
deleted file mode 100644
index 29a4480..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ssh2-hosts.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/ssh2-keys.png b/bundles/org.eclipse.platform.doc.user/images/ssh2-keys.png
deleted file mode 100644
index ea22f81..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/ssh2-keys.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/stop_nav.png b/bundles/org.eclipse.platform.doc.user/images/stop_nav.png
deleted file mode 100644
index c42305a..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/stop_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/switch_workspace.png b/bundles/org.eclipse.platform.doc.user/images/switch_workspace.png
deleted file mode 100644
index 2f6aa98..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/switch_workspace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/synced.png b/bundles/org.eclipse.platform.doc.user/images/synced.png
deleted file mode 100644
index b2e9aa4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/synced.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/synch_participants.png b/bundles/org.eclipse.platform.doc.user/images/synch_participants.png
deleted file mode 100644
index 6cf2deb..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/synch_participants.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png b/bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png
deleted file mode 100644
index 6a2bfa8..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/tasks-96b-module_rep.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/team-file-content.png b/bundles/org.eclipse.platform.doc.user/images/team-file-content.png
deleted file mode 100644
index 1467241..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/team-file-content.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/team-models.png b/bundles/org.eclipse.platform.doc.user/images/team-models.png
deleted file mode 100644
index b3f4ad4..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/team-models.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/tree_mode.png b/bundles/org.eclipse.platform.doc.user/images/tree_mode.png
deleted file mode 100644
index e72e897..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/tree_mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/twowaycompare_co.gif b/bundles/org.eclipse.platform.doc.user/images/twowaycompare_co.gif
deleted file mode 100644
index 12788ba..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/twowaycompare_co.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/undo_edit.png b/bundles/org.eclipse.platform.doc.user/images/undo_edit.png
deleted file mode 100644
index adbf2e1..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/undo_edit.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/up_nav.png b/bundles/org.eclipse.platform.doc.user/images/up_nav.png
deleted file mode 100644
index d7c890c..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/up_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/version_controlled.png b/bundles/org.eclipse.platform.doc.user/images/version_controlled.png
deleted file mode 100644
index ed401bd..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/version_controlled.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/view_menu.png b/bundles/org.eclipse.platform.doc.user/images/view_menu.png
deleted file mode 100644
index 3fae7f5..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/view_menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/welcome.png b/bundles/org.eclipse.platform.doc.user/images/welcome.png
deleted file mode 100644
index 4bc9491..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/welcome.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/welcome_preference.png b/bundles/org.eclipse.platform.doc.user/images/welcome_preference.png
deleted file mode 100644
index aef4793..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/welcome_preference.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/images/win_only.png b/bundles/org.eclipse.platform.doc.user/images/win_only.png
deleted file mode 100644
index 7523f99..0000000
--- a/bundles/org.eclipse.platform.doc.user/images/win_only.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/notices.html b/bundles/org.eclipse.platform.doc.user/notices.html
deleted file mode 100644
index b2201a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/notices.html
+++ /dev/null

@@ -1,22 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-   <LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-   <title>Legal Notices</title>
-</head>
-<body>
-
-<h3>
-<a NAME="Notices"></a>Notices</h3>
-<p>
-The material in this guide is Copyright (c) IBM Corporation and others 2000, 2009.
-</p>
-<p>
-<a href="about.html">Terms and conditions regarding the use of this guide.</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/plugin.properties b/bundles/org.eclipse.platform.doc.user/plugin.properties
deleted file mode 100644
index 5dd7d1a..0000000
--- a/bundles/org.eclipse.platform.doc.user/plugin.properties
+++ /dev/null

@@ -1,12 +0,0 @@
-###############################################################################
-# Copyright (c) 2000, 2008 IBM Corporation and others.
-# All rights reserved. This program and the accompanying materials
-# are made available under the terms of the Eclipse Public License v1.0
-# which accompanies this distribution, and is available at
-# http://www.eclipse.org/legal/epl-v10.html
-# 
-# Contributors:
-#     IBM Corporation - initial API and implementation
-###############################################################################
-pluginName=Eclipse Workbench User Guide
-providerName=Eclipse.org

diff --git a/bundles/org.eclipse.platform.doc.user/plugin.xml b/bundles/org.eclipse.platform.doc.user/plugin.xml
deleted file mode 100644
index bf4f851..0000000
--- a/bundles/org.eclipse.platform.doc.user/plugin.xml
+++ /dev/null

@@ -1,142 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?eclipse version="3.0"?>
-
-<!-- ===================================================== -->
-<!-- Declare the documentation for the Platform User Guide  -->
-<!-- We will declare only one infoset (book)               -->
-<!-- ===================================================== -->
-
-<plugin>
-
-
-<!-- ============================================================================= -->
-<!-- Define primary TOC                                                            -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc">
-       <toc file="toc.xml" primary="true" />
-       <index path="index"/>
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- Define TOCs                                                                   -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.toc">
-       <toc file="topics_GettingStarted.xml" />
-       <toc file="topics_Concepts.xml" />
-       <toc file="topics_Tasks.xml" />
-       <toc file="topics_Reference.xml" />
-   </extension>
-
-<!-- ============================================================================= -->
-<!-- F1 context files                                                              -->
-<!-- ============================================================================= -->
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui"/> 
-   </extension>
-   
-    <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.ide"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.workbench.texteditor"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.editors"/> 
-   </extension>
-   
-   <extension point="org.eclipse.help.contexts">
-   		<contexts file="contexts_ExternalTools.xml" plugin="org.eclipse.ui.externaltools"/>
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Workbench.xml" plugin="org.eclipse.ui.browser"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts">
-   		<contexts file="contexts_AntUI.xml" plugin="org.eclipse.ant.ui"/>
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Team.xml" plugin="org.eclipse.team.ui"/> 
-   </extension>
-
-   <extension point="org.eclipse.help.contexts"> 
-       <contexts file="contexts_Team_CVS.xml" plugin="org.eclipse.team.cvs.ui"/> 
-   </extension>
-
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_Compare.xml" plugin="org.eclipse.compare"/> 
-	</extension>
-   
-   <extension point="org.eclipse.help.contexts"> 
-      <contexts file="contexts_Search.xml" plugin="org.eclipse.search"/> 
-   </extension>
-
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_P2.xml"  plugin="org.eclipse.equinox.p2.ui"/> 
-	</extension>
-
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_P2.xml"  plugin="org.eclipse.equinox.p2.ui.sdk"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_P2.xml"  plugin="org.eclipse.equinox.p2.ui.sdk.scheduler"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_Update.xml"  plugin="org.eclipse.update.ui"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_UserAssistance.xml"  plugin="org.eclipse.help.ui"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_UserAssistance.xml"  plugin="org.eclipse.ui.cheatsheets"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_UserAssistance.xml"  plugin="org.eclipse.ui.intro"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_UserAssistance.xml"  plugin="org.eclipse.ui.intro.universal"/> 
-	</extension>
-	
-    <extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_Net.xml"  plugin="org.eclipse.ui.net"/> 
-	</extension>
-	
-    <extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_SecureStorage.xml"  plugin="org.eclipse.equinox.security.ui"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_JSch.xml"  plugin="org.eclipse.jsch.ui"/> 
-	</extension>
-	
-	<extension point="org.eclipse.help.contexts"> 
-		<contexts file="contexts_CommonNavigator.xml"  plugin="org.eclipse.ui.navigator"/> 
-	</extension>
-
-<!-- ============================================================================= -->
-<!-- Dynamic Content                                                               -->
-<!-- ============================================================================= -->
-
-    <extension
-          point="org.eclipse.help.contentProducer">
-       <binding producerId="org.eclipse.help.dynamic"/>
-    </extension>
-    
-    <extension
-          point="org.eclipse.help.base.luceneSearchParticipants">
-       <binding participantId="org.eclipse.help.base.xhtml"/>
-    </extension>
-
-</plugin>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/help_preferences.htm b/bundles/org.eclipse.platform.doc.user/reference/help_preferences.htm
deleted file mode 100644
index aef9c2e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/help_preferences.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Help preferences</title>
-</head>
-<body>
-
-<h1>Help preferences</h1>
-
-<P CLASS="Para">
-On the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.help.ui.browsersPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Help</strong></a>
-
-preferences page, you can indicate how to display help information.</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Use external browsers</span></TH>
-      <TH align="left"> <span style="font-weight: 400">If embedded web browser 
-        is supported on your system, help window uses an embedded help browser
-        to display help contents, whenever possible, and this option is available.
-        Select it, to force help to use external browsers.  Use &quot;Web
-        Browser&quot; preference page to select browser to use.</span> </TH>
-      <TH align="left"> <span style="font-weight: 400">Off</span></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Open window context help 
-        </span></TH>
-      <TH align="left"><span style="font-weight: 400">This option allows you to 
-        determine whether the window context help will be opened in a dynamic 
-        help view or in an infopop.</span></TH>
-      <TH align="left"> <span style="font-weight: 400">in a dynamic help view 
-        </span></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Open dialog context help</span></TH>
-      <TH align="left"><span style="font-weight: 400">This option allows you to 
-        determine whether the dialog context help will be opened in a dynamic 
-        help section of help view or in an infopop.</span></TH>
-      <TH align="left"> <span style="font-weight: 400">in dialog tray</span></TH>
-    </TR>
-    <TR> 
-      <TH align="left"> <span style="font-weight: 400">Open help view documents</span></TH>
-      <TH align="left"><span style="font-weight: 400">This option allows you to 
-        determine whether the documents selected in the help view will be opened
-        in-place or in the editor area.</span></TH>
-      <TH align="left"> <span style="font-weight: 400">in-place </span></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-  </TBODY>
-</TABLE>
-
-
-<P>Here is what the Help preferences page looks like:&nbsp;&nbsp;
-</P>
-
-
-<P>
-<img src="../images/help_preference.png" alt="Help Preference Page" border="0">
-</P>
-
-<p>
-<b>Note:</b>  Selection performed on this page can affect how the help view is presented.  If the selected browser is not fully compatible with Internet Explorer or Mozilla, or has JavaScript disabled, the help view shown in the browser might be a simplified version.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/help.htm">Help</a><br>
-<a href="../concepts/help_view.htm">Help view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/help.xhtml">Accessing help</a><br>
-<a href="../tasks/help_settings.htm">Help display settings</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="help_preferences_content.htm">Help Content preferences</a><br>
-<a href="ref-42.htm">Web Browser preferences</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/help_preferences_content.htm b/bundles/org.eclipse.platform.doc.user/reference/help_preferences_content.htm
deleted file mode 100644
index ae3e591..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/help_preferences_content.htm
+++ /dev/null

@@ -1,157 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Help Content preferences</title>
-</head>
-<body>
-
-<h1>Help Content preferences</h1>
-
-<P CLASS="Para">
-Help topics from remote servers can be included seamlessly into the local help system.
-Use the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.help.ui.contentPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Help &gt; Content</strong></a>
-
-preference page to configure one or more remote server to include content from.
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Button</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Include help content from a remote infocenter</span></TH>
-<TH align="left">
-<span style="font-weight: 400">If checked, this option enables the use of remote
-help content. The rest of the fields on the page are only enabled if this option
-is checked.</span>
-</TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Add/Edit/Delete</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Add, edit or delete a remote data source</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">View Properties</span></TH>
-<TH align="left">
-<span style="font-weight: 400">View the properties for this remote data source</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Test Connection</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Tests to see if it is possible to connect to this 
-host/port combination</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Disable/Enable</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Allows a data source to be disabled so the help 
-system will not try to read topics from that source.</span></TH>
-</TR>
-</THEAD>
-<TBODY>
-</TBODY>
-</TABLE>
-
-
-<P>Here is what the Help Content preferences page looks like:&nbsp;&nbsp;
-</P>
-
-
-<P>
-<img src="../images/help_preference_content.png" alt="Help Content Preference Page" border="0" width="737" height="543"></P>
-
-
-<P>
-Pressing the &quot;Add&quot; button opens a dialog to add a new infocenter, these are the 
-fields that can be entered in the Add new infocenter dialog.&nbsp;
-</P>
-
-<TABLE BORDER="1" cellspacing="0">
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Name</span></TH>
-<TH align="left">
-<span style="font-weight: 400">A name for this infocenter</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Host</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Specifies the host name of the system that is running the
-infocenter to server remote help content. This must be a host name and cannot be a URL
-(i.e. it cannot start with "http://")</span>
-</TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Path</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Specifies the context root of the Infocenter application
-running on the host.</span>
-</TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Port</span></TH>
-<TH align="left">
-<span style="font-weight: 400">If "Use default port" is selected, port 80 will be used
-to access remote content on the host. To use any other port the "Use port" option must
-be selected and the correct port must be specified in the text field.</span>
-</TH>
-</TR>
-</TABLE>
-
-
-<P>
-&nbsp;<img border="0" src="../images/help_preference_infocenter.png" width="407" height="345"></P>
-
-<p>
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/help.htm">Help</a><br>
-</p>
-
-<p>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="../tasks/help.xhtml">Accessing help</a><br>
-</p>
-
-<p>
-<img border="0" src="../images/ngrelr.png" alt="Related reference" width="159" height="27"><br>
-<a href="help_preferences.htm">Help preferences</a><br>
-<a href="ref-42.htm">Web Browser preferences</a><br>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-10.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-10.htm
deleted file mode 100644
index 4d7bd37..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-10.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-   <title>General</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body bgcolor="#FFFFFF">
-<h1 CLASS="Head">General</h1>
-
-<div CLASS="Intro">General settings for the Workbench.  The term <i>Workbench</i> refers to the desktop development
-environment.</div>
-
-
-<p CLASS="Para" Label="Type">Each Workbench window contains one or more
-perspectives.&nbsp; Perspectives contain views and editors and control
-what appears in certain menus and tool bars.&nbsp; More than one Workbench
-window can exist on the desktop at any given time.</p>
-
-<p CLASS="Para">The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General</strong></a>
-
-preference page. </p>
-<table width="75%" border="1">
-  <tr> 
-    <td><strong>Option</strong></td>
-    <td><strong>Description</strong></td>
-    <td><strong>Default</strong></td>
-  </tr>
-  <tr> 
-    <td>Always run in background</td>
-    <td>Turn this option on to perform long running operations in the background 
-    without blocking you from doing other work.<br></td>
-    <td>Off<br></td>
-  </tr>
-  <tr> 
-    <td>Keep next/previous part dialog open </td>
-    <td>If this option is turned on then the editor and view cycle dialogs will 
-      remain open when their activation key is let go. Normally the dialog closes 
-      as soon as the key combination is release.</td>
-    <td>Off </td>
-  </tr>
-  <tr> 
-    <td>Show Heap Status</td>
-    <td>Turn this option on to display an indicator
-    showing information about current Java heap usage.<br></td>
-    <td>Off<br></td>
-  </tr>
-  <tr> 
-    <td>Open mode...</td>
-    <td><div CLASS="Para">You can select one of the following methods for opening 
-        resources:</div>
-      <div CLASS="Para"></div>
-      &nbsp; <ul>
-        <li CLASS="Item"> Double click - Single clicking on a resource will select 
-          it and double clicking on it will open it in an editor.</li>
-        <li CLASS="Item"> Single click (Select on hover) - Hovering the mouse 
-          cursor over the resource will select it and clicking on it once will 
-          open it in an editor.</li>
-        <li CLASS="Item"> Single click (Open when using arrow keys) - Selecting 
-          a resource with the arrow keys will open it in an editor.
-         <p CLASS="Para"><strong>Note:</strong> Depending on which view has focus, 
-          selecting and opening a resource may have different behavior. </p></li>
-      </ul></td>
-    <td>Double click</td>
-  </tr>
-</table>
-<table width="75%" border="1">
-  <tr> 
-
-  </tr>
-</table>
-<p>Here is what the General preferences page looks like:</p> 
-<p><img src="../images/Image217_pref_wb.png" alt="Preference dialog" ></p>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-23.htm">Workbench Window Layout</a>
-</P>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-11.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-11.htm
deleted file mode 100644
index fd248b7..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-11.htm
+++ /dev/null

@@ -1,195 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <title>Compare/Patch</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body bgcolor="#FFFFFF">
-
-<h1 CLASS="Head">
-Compare/Patch</h1>
-
-<p>The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.compare.internal.ComparePreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Compare/Patch</strong></a>
-
-page.</p>
-
-<h2>General options</h2>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Open structure 
-          compare automatically
-        </div></td>
-      <td align="left" valign="top"> <div class="Para"> 
-          <div CLASS="Para">This option controls whether a structure compare is 
-            automatically performed whenever a content compare is done. Turn this 
-            option off if you don't want to see the structural differences.</div>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-	<tr> 
-		<td style="vertical-align: top; width: 25%;">Show structure compare in Outline 
-		view when possible</td>
-		<td style="vertical-align: top;">If this option is on, structure compare will
-		be displayed in the Outline view whenever it is possible.</td>
-		<td style="vertical-align: top;">Off </td>
-	</tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show additional compare information 
-        in the status line </td>
-      <td style="vertical-align: top;">If this option is on, additional information 
-        about a change is shown in
-        the status line. Turn this option on if you are interested in additional 
-        information about a change. </td>
-      <td style="vertical-align: top;">Off </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Ignore white space</td>
-      <td style="vertical-align: top;">This option controls whether or not whitespace 
-        change are shown in the compare viewer. Turn this option on if you want 
-        to see changes in whitespace. </td>
-      <td style="vertical-align: top;">Off </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Automatically save dirty editors before browsing patches</td>
-      <td style="vertical-align: top;">This option controls whether any unsaved 
-        changes are automatically saved before a patch is applied. Turn this option 
-        on if you want to save changes automatically. </td>
-      <td style="vertical-align: top;">Off </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Added/Removed lines</td>
-      <td style="vertical-align: top;">These options control  which lines should
-       be counted as added and removed lines when applying a patch. Both options
-       are based on regular expressions. </td>
-      <td style="vertical-align: top;"><br></td>
-    </tr>    
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Filtered Members</td>
-      <td style="vertical-align: top;"><p>This option allows you to filter members 
-          that should be excluded from 'Compare With Each Other'. </p>
-        <p><strong>Note: </strong>The names in the list must be separated by a 
-          comma.
-        </p></td>
-      <td style="vertical-align: top;"><br> </td>
-    </tr>
-  </tbody>
-</table>
-<h2>Text Compare options</h2>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Synchronize 
-          scrolling between panes in compare viewers
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">
-          <div CLASS="Para">The two comparison viewers will "lock scroll" along 
-            with one another in order to keep identical and corresponding portions 
-            of the code in each pane side-by-side. Turn this option off if you 
-            do not want the compare viewers to lock scroll.</div>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Initially show ancestor pane</td>
-      <td style="vertical-align: top;">Sometimes you want to compare two versions 
-        of a resource with the previous version from which they were both derived. 
-        This is called their <i>common ancestor</i>, and it appears in its own 
-        comparison pane during a three way compare. Turn this option on if you 
-        want the ancestor pane to always appear at the start of a comparison. </td>
-      <td style="vertical-align: top;">Off </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show pseudo conflicts </td>
-      <td style="vertical-align: top;">Displays pseudo conflicts, which occur 
-        when two developers make the same change (for example, both add or remove 
-        the exact same line of code or comment). Turn this option on if you want 
-        pseudo conflicts to appear in compare browsers. </td>
-      <td style="vertical-align: top;">Off </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Connect ranges with single 
-        line</td>
-      <td style="vertical-align: top;">Controls whether differing ranges are visually 
-        connected by a single line or a range delimited by two lines. </td>
-      <td style="vertical-align: top;">On </td>
-    </tr>
-	<tr> 
-		<td style="vertical-align: top; width: 25%;">Highlight individual changes</td>
-		<td style="vertical-align: top;">Controls whether the individual changes inside
-		conflicts are highlighted.</td>
-		<td style="vertical-align: top;">On </td>
-	</tr>
-	<tr> 
-		<td style="vertical-align: top; width: 25%;">When the end/beginning is 
-		reached while navigating an element</td>
-		<td style="vertical-align: top;">Use this option to configure what occurs when
-		the end/beginning is reached while navigating an element.
-		<ul>
-			<li><strong>Prompt: </strong>If this option is on and you selected 
-			to compare a single element you will be asked whether you want to go
-			to the beginning/end of the element after the end/beginning is reached.
-			If you are comparing two or more elements you will be asked whether 
-			you want to go to the beginning/end	of the current element or to go 
-			to the next/previous element. Moreover,	if you choose to remember your
-			decision, this option will be changed to one of the below respectively.</li>
-			<li><strong>Loop back to the beginning/end: </strong>When this option
-			is on, the selection will me moved back to the beginning/end after you reach
-			the end/beginning of an element.</li>
-			<li><strong>Go to the next/previous element: </strong>If you are comparing
-			two or more elements and this option is on after you reach the end/beginning
-			of an element the next/previous element will be opened.</li>
-		</ul>
-		</td>
-		<td style="vertical-align: top;">Prompt </td>
-	</tr>
-
-
-
-  </tbody>
-</table>
-
-
-<p>Here is what the Compare preference page looks like:</p>
-<p><img src="../images/Image219_pref_cv.png" alt="Compare preference page (General tab)" border="0" ></p>
-<p><img src="../images/Image219_pref_cv2.png" alt="Compare preference page (Text Compare tab)" border="0" ></p>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-25.htm">Compare Editor</a>
-<br><a href="ref-33.htm">CVS Synchronization View</a>
-</P>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-12.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-12.htm
deleted file mode 100644
index 3d47b1c..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-12.htm
+++ /dev/null

@@ -1,71 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Editors preference page</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h1 class="Head">Editors preference page</h1>
-
-<p class="Para">You can change the following preferences on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"><strong>General &gt; Editors</strong></a>
-preference page:
-</p>
-
-<table border="1" cellspacing="0" cellpadding="5">
-<thead>
-<tr valign="top">
-<th>Option</th>
-<th>Description</th>
-<th>Default</th>
-</tr>
-</thead>
-<tbody>
-<tr valign="top">
-<td><b>Size of recently opened files list</b></td>
-<td>Each file that is opened in an editor is stored in a list of 
-recently used files in the <b>File</b> menu. 
-This option controls the number of files that is displayed in that list.
-</td>
-<td>4</td>
-</tr>
-<tr valign="top">
-<td><b>Show multiple editor tabs</b></td>
-<td>Specifies whether you wish to show multiple editor tabs. 
-If off, editor workbooks have one large tab and all non-visible editors are accessible only from 
-the chevron.
-</td>
-<td>On</td>
-</tr>
-<tr valign="top">
-<td><b>Close editors automatically</b></td>
-<td>Specifies whether or not to re-use editors in the Workbench. 
-If on, you may specify the number of editors to use before they are recycled 
-(the default is 8). 
-You can also specify if a prompt dialog should be opened or if a new editor should be opened 
-when all editors are "dirty" (have unsaved changes). 
-Once it is turned on, the Pin Editor action is added to the toolbar and editor tab menu. 
-Pinned editors are not recycled.
-</td>
-<td>Off</td>
-</tr>
-</tbody>
-</table>
-
-<p>The <b>Editors</b> preference page:
-</p>
-
-<p><img src="../images/Image220_pref_dte.png" alt="Editors Preference Page" border="0">
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference">
-<br><a href="ref-24.htm">Editor Area</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-13.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-13.htm
deleted file mode 100644
index 61b50d3..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-13.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>File Associations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-File Associations</H1>
-<P CLASS="Intro">
-On the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Editors &gt; File Associations</strong></a>
-
-preference page, you can add or remove file
-types recognized by the Workbench.&nbsp; You can also associate
-editors with file types in the file types list.</p>
-<DIV CLASS="Topic">
-<h2>
-File types list</h2>
-<UL CLASS="UnorderedList">
-    <LI CLASS="Item"> <strong>Add...</strong>:&nbsp; Adds a new file or file type 
-      (extension) to the predefined list. In the resulting New File Type dialog, 
-      type the name of a file or a file extension. If you are adding a file extension, 
-      you must type either a dot or a &quot;*.&quot; before the file type (e.g., 
-      &quot;.xml&quot; or &quot;*.xml&quot; as opposed to simply &quot;xml&quot;).</LI>
-    <LI CLASS="Item"><strong> Remove</strong>:&nbsp; Removes the selected file 
-      type from the list</LI>
-</UL>
-<p>Dialog to create a new file type:</p>
-<p><img src="../images/Image201_filetype.png" alt="New file type dialog" border="0" ></p>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Associated editors list</h2>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item"> <strong>Add...</strong>:&nbsp; Adds a new editor to the 
-      list of editors associated with the file type selected above. In the resulting 
-      Editor Selection dialog, you can choose an editor to launch either inside 
-      the Workbench (internal) or outside the Workbench (external); click <b>Browse</b> 
-      to locate an editor yourself if the editor you want is not displayed in 
-      the list.</LI>
-    <LI CLASS="Item"> <strong>Remove</strong>:&nbsp; Removes the association between 
-      an editor and the file type selected above.<strong> Note:</strong> Any editor 
-      that is bound by content type may not be removed from this list. Currently, 
-      there is no mechanism available to remove these editors.</LI>
-    <LI CLASS="Item"> <strong>Default</strong>:&nbsp; Sets the selected editor 
-      as the default editor for the file type selected above. The editor moves 
-      to the top of the Associated Editors list to indicate that it is the default 
-      editor for that file type.</LI>
-  </UL>
-</DIV>
-<P>Dialog to create a new file association:
-</P>
-
-
-<P><img src="../images/Image202_editorsel.png" alt="Editor Selection dialog" border="0" >
-</P>
-
-
-<P>&nbsp;
-</P>
-
-
-<P>Here is what the File Associations preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image221_pref_fe.png" alt="File associations preference page" border="0" >
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-14.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-14.htm
deleted file mode 100644
index 91babc5..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-14.htm
+++ /dev/null

@@ -1,114 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Local History</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Local History</H1>
-<P CLASS="Intro"> The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Workspace &gt; Local History</strong></a>
-
-page.</p>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Limit history size</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">If enabled, then options below will be used to limit the local history size on disk.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Enabled</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Days to keep files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Indicates for how many days you want to maintain changes in the local history.
-History state older than this value will be lost.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-7 days</P>
-</TD>
-</TR>
-<TR>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Maximum entries per File</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Indicates how many history states per file you want to maintain in the local
-history.&nbsp;If you exceed this value, you will lose older history to make room
-for new history.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-50 entries</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Maximum file size (MB)</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Indicates the maximum size of individual states in the history store.&nbsp; If a
-file is over this size, it will not be stored.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-1 MB</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-<P>&nbsp;Here is what the Local History preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image222_pref_lh.png" alt="Local history preference page" border="0"> 
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-6a.htm">Local History</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm
deleted file mode 100644
index cd77944..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-14b.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Linked Resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Linked Resources</H1>
-<P CLASS="Intro">
-
-The 
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Workspace &gt; Linked Resources</strong></a>
-
-preference page is used when working with 
-<a href="../concepts/concepts-13.htm">linked resources</a>. The preference 
-<b>Enable linked resources</b> is used to globally enable or disable the linked resource
-feature for the entire workspace.  By default, linked resources are enabled. If you
-disable linked resources, then you will not be able to create any new linked resources,
-or import existing projects that contain linked resources.
-</P>
-<P CLASS="Para">
-Not all versions of the workbench support linked resources and recognize them as such. 
-You may not want to use linked resources if you plan to share your workspace data with 
-other users. Disable this preference if they will not be able to work with linked resources.
-
-</P>
-<P CLASS="Para"> The remainder of this page is for defining <a href="../concepts/cpathvars.htm">path 
-  variables</a> that are used when creating linked resources. Use the <b>New</b> 
-  button to define new variables, the <b>Edit</b> button to change the value of 
-  an existing variable, and the <b>Remove</b> button to get rid of an existing 
-  variable. Note if you change a path variable that is currently in use, you will 
-  need to perform a local refresh on those projects to &quot;discover&quot; what 
-  is different in the file system. You can refresh a resource by opening the one 
-  of the navigation views' context menu for that resource and selecting <b>Refresh</b>. 
-  It is not recommended that you remove a path variable that is currently in use. 
-</P>
-
-
-<P>&nbsp;Here is what the Linked Resources preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image36_linkedresources.png" alt="Linked resources preference page" border="0">
-</P>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-13.htm">Linked resources</a>
-<br><a href="../concepts/cpathvars.htm">Path variables</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-15.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-15.htm
deleted file mode 100644
index 7efe4e2..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-15.htm
+++ /dev/null

@@ -1,202 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Perspectives</H1>
-<P CLASS="Para">
-On the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Perspectives</strong></a>
-
-preference page, you can manage the various perspectives defined in the Workbench.&nbsp;&nbsp;</P>
-
-
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Open a new perspective
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use this option to set what happens when you open a new perspective. Do you want the perspective opened within
-the current Workbench window or opened in a new window?
-</P>
-</TD>
-<TD>
-In the same window
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Open a new view
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use this option to specify what happens when a new view is opened. It is either
-opened to its default position within the current perspective or it is opened as a fast view
-and docked to the side of the current perspective.
-</P>
-</TD>
-<TD>
-Within the perspective
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Hide empty fast view bar
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use this option to specify visibility of an empty fast view bar. If this preference is set and the current perspective 
-doesn't contain any fast views, the fast view bar becomes invisible.
-</P>
-</TD>
-<TD>
-Fast view bar is always visible
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-New project options
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use this option to specify the perspective behavior when a new project is created. You can set it
-to switch the current perspective to be the one associated with the project type and 
-open the perspective in the same Workbench window as the current one, switch the perspective and
-open it in a new Workbench window, or not to switch perspectives at all.
-</P>
-</TD>
-<TD>
-Open perspective in the same window
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-
-
-<h2>Available Perspectives Options:</h2>
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Make Default</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Sets the selected perspective as the default perspective.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Resource</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Reset</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Resets the definition of the selected perspective to the default configuration. This option is only applicable 
-to built-in perspectives that have been overwritten using Window &gt; Save Perspective As...</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-n/a</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Delete</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deletes the selected perspective. This option is only applicable to user-defined
-perspectives (built-in perspectives can not be deleted).</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-n/a</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<P>&nbsp;
-</P>
-
-
-<P>&nbsp;Here is what the Perspectives preferences page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image223_pref_persp.png" alt="Perspectives Preference Page" border="0">
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-6.htm">Perspectives</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-16.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-16.htm
deleted file mode 100644
index a7742c0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-16.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation, Red Hat, and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Appearance preference page</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h1 class="Head">Appearance preference page</h1>
-
-<p class="Para">You can change the following preferences on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"><strong>General &gt; Appearance</strong></a> preferences page.
-</p>
-
-<table width="80%" border="1" cellspacing="0" cellpadding="5">
-<tr>
-<th>Option</th>
-<th>Description</th>
-<th>Default</th>
-</tr>
-<tr valign="top">
-<td><b>Current presentation</b></td>
-<td>Specify the currently active presentation (look and feel).</td>
-<td>Default (current)</td>
-</tr>
-<tr valign="top">
-<td><b>Override presentation settings</b></td>
-<td>Locally override the settings from the current presentation's defaults.</td>
-<td>Disabled</td>
-</tr>
-<tr valign="top">
-<td><b>Editor tab positions</b></td>
-<td>Specify either top or bottom to indicate where you want tabs for stacked 
-editors to appear.</td>
-<td>Top</td>
-</tr>
-<tr valign="top">
-<td><b>View tab positions</b></td>
-<td>Specify either top or bottom to indicate where you want tabs for stacked 
-views to appear.</td>
-<td>Top</td>
-</tr>
-<tr valign="top">
-<td><b>Perspective switcher positions</b></td>
-<td>Specify the location of the perspective switcher bar.</td>
-<td>Top right</td>
-</tr>
-<tr valign="top">
-<td><b>Current theme</b></td>
-<td>Specify the currently active theme (color and font set).</td>
-<td>Default (current)</td>
-</tr>
-<tr valign="top">
-<td><b>Show text on perspective bar</b></td>
-<td>Specify whether labels should be shown in the perspective bar as well 
-as icons.</td>
-<td>Enabled</td>
-</tr>
-<tr valign="top">
-<td><b>Show traditional style tabs</b></td>
-<td>Specify whether traditional (square) tabs should be used in place of the 
-curved tabs.</td>
-<td>Disabled</td>
-</tr>
-<tr valign="top">
-<td><b>Enable animations</b></td>
-<td>Enable/disable the feature where views animate to their location when 
-closed or opened.</td>
-<td>Enabled</td>
-</tr>
-</table>
-
-<p>The <b>Appearance</b> preferences page:
-</p>
-
-<p><img src="../images/Image218_pref_app.png" alt="Appearance preference page" border="0">
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-17.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-17.htm
deleted file mode 100644
index 0df9f28..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-17.htm
+++ /dev/null

@@ -1,91 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Build Order</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Build Order</H1>
-<P CLASS="Para">
-Often the order in which projects are built is important.&nbsp; For
-example, if one project requires the Java classes which were defined in another
-project, the first project must be built after its prerequisite classes have
-been built.&nbsp; The Workbench allows users to explicitly define the order in
-which projects are built. Alternatively, users can let the platform compute the
-build order by interpreting project references as prerequisite relationships.
-The build order is applied for both building the entire workspace or for a group
-of projects.&nbsp;</P>
-<P CLASS="Para">You can change this order on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.BuildOrder)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Workspace &gt; Build Order</strong></a>
-
-preferences page.&nbsp;</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Use default builder order</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This<b></b> option allows the platform to computes the build ordering. 
-          Turning off this option enables access to the projects list, the ordering 
-          of which can be manipulated. </P></TD>
-      <TD>On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Project build order</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">This 
-          option allows you to select projects and use the <b>Up</b> and <b>Down</b> 
-          buttons to change the build order. Add and remove projects in the build 
-          order using the <b>Add Project</b> and <b>Remove Project</b> buttons. 
-          Projects removed from the build order <i>will</i> be built, but they 
-          will be built after all projects in the build order are built.</P></TD>
-      <TD>&nbsp; </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Max iterations when building with cycles</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">This 
-          preference allows you to deal with build orders that contain cycles. 
-          Ideally, you should avoid cyclic references between projects. Projects 
-          with cycles really logically belong to a single project, and so they 
-          should be collapsed into a single project if possible. However, if you 
-          absolutely must have cycles, it may take several iterations of the build 
-          order to correctly build everything. Changing this preference will alter 
-          the maximum number of times the workbench will attempt to iterate over 
-          the build order before giving up.</P></TD>
-      <TD> 10</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<P CLASS="Para">Here is what the Build Order preference page looks like:&nbsp; 
-</P>
-<P><img src="../images/Image224_pref_build.png" alt="Build order preference page" border="0"> 
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-5.htm">Builds</a>
-<br><a href="ref-59.htm">Project menu</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19.htm
deleted file mode 100644
index ac1f1ae..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19.htm
+++ /dev/null

@@ -1,109 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Team</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Team</H1>
-<P CLASS="Para"> The
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.TeamPreferences)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team</strong></a>
-
-preferences page contains options which 
-  affect the version management Team support.</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD COLSPAN="1" valign="top" align="left">Show all synchronization information 
-        in a resource's text label</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to have the synchronization 
-        state of a resource displayed as text in the resource's label. By default, 
-        only an icon decorator is used to identify a resource's synchronization 
-        state.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Disabled</TD>
-    </TR>
-  	<TR> 
-      <TD COLSPAN="1" valign="top" align="left">Show the file author in compare
-      editors</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to display the file
-      author in all compare editors opened by an action on a repository provider (if 
-      supported by the repository provider)</TD>
-      <TD COLSPAN="1" valign="top" align="left">Disabled</TD>
-    </TR>
-  	<TR> 
-      <TD COLSPAN="1" valign="top" align="left">When editing file in non-shared projects, automatically make files writable if prompting is not possible</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to make the file 
-      writable in a non-shared project if prompting is not possible.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Disabled</TD>
-    </TR>
-  	<TR> 
-      <TD COLSPAN="1" valign="top" align="left">Reuse open compare editors when opening comparisons</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to have a new comparison open in an existing 
-      compare editor. Enabling this option will decrease number of compare editors open.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Enabled</TD>
-    </TR>    
-  	<TR> 
-      <TD COLSPAN="1" valign="top" align="left">Run Project Set import in the background</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to run Project Set import in the background.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Disabled</TD>
-    </TR>         
-    <TR> 
-      <TD COLSPAN="1" valign="top" align="left">Choose the presentation to be used when displaying 
-        Workspace projects</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to configure the 
-        default layout used when a synchronization is first added to the Synchronize 
-        view. The layout can be subsequently changed in the view drop down menu.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Compressed Folders</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open the associated perspective when a synchronize operation completes</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Use 
-          this option to configure what happens when a synchronization operation 
-          is run. The options are:</P>
-        <ul>
-          <li><strong class="Para">Always</strong>: always switch perspectives</li>
-          <li><strong class="Para">Never</strong>: never switch perspectives</li>
-          <li><strong class="Para">Prompt</strong>: prompt to switch perspectives</li>
-        </ul></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Prompt</P></TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" valign="top" align="left">Perspectives</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to configure which 
-        perspective is to be shown when a synchronize operation is run.</TD>
-      <TD COLSPAN="1" valign="top" align="left">Team Synchronizing</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<P>Here is what the Team preference page looks like:&nbsp;&nbsp; </P>
-<P> </P>
-<img src="../images/Image_team_pref.png" alt="Team Preference Page" border="0">
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- > <br>
-  <a href="ref-33.htm">CVS Synchronize view</a> </p>
-<p><a href="ref-6.htm">Perspectives</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-annotate.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-annotate.htm
deleted file mode 100644
index bc05950..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-annotate.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>CVS Annotate</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Annotate</H1>
-<P class="Para">The following preference can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.AnnotatePreferences)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team &gt; CVS &gt; Annotate</strong></a>
-
-preference page.</P>
-<TABLE border="1" cellspacing="0">
-<THEAD>
-    <TR> 
-      <TH width="164"> <P class="Para">Option</P></TH>
-      <TH width="490"> <P class="Para">Description</P></TH>
-      <TH width="152"> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Attempt to annotate a binary file</TD>
-    <TD valign="top" align="left">Use this option to configure whether the annotate operation should attempt to annotate
-    a binary file. The choices are:
-    <ul>
-      <li><strong>Yes:</strong> Always attempt to annotate a binary file.</li>
-      <li><strong>No:</strong> Never attempt to annotate a binary file.</li>
-      <li><strong>Prompt:</strong> Prompt user whether to attempt to annotate a binary file.</li>
-    </ul></TD>
-    <TD valign="top" align="left">Prompt</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img alt="CVS Annotate preference page" src="../images/cvs-annotate.png"></p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" > <br>
-  <a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- > <a href="../tasks/tasks-cvs-watch.htm"><br>
-  Finding out who's working on what: watch/edit</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-commenttemplates.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-commenttemplates.htm
deleted file mode 100644
index fc36371..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-commenttemplates.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>CVS Comment Templates</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Comment Templates</H1>
-<P class="Para">The
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CommentTemplatesPreferences)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team &gt; CVS &gt; Comment Templates</strong></a>
-
-preference page allows you to create, edit and remove
-comments that will show up in the comments section of the commit dialog. This can be helpful if
-you need to enter the same string (or some part of a string) for a comment in all commits.</P>
-<TABLE border="1" cellspacing="0">
-<THEAD>
-    <TR> 
-      <TH width="240"> <P class="Para">Button</P></TH>
-      <TH width="566"> <P class="Para">Description</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">New...</TD>
-    <TD valign="top" align="left">Opens the 'Enter Template Comment' dialog which allows you to enter
-    a new comment.</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Edit...</TD>
-    <TD valign="top" align="left">Opens the selected comment in the 'Enter Template Comment' dialog.</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Remove</TD>
-    <TD valign="top" align="left"> Removes the selected comment.</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img alt="Comment Templates preference page" src="../images/cvs-commenttemplates.png"></p>
-<p>Here is the commit dialog with the comment templates displayed:</p>
-<p><img alt="Commit dialog with comment templates displayed" src="../images/cvs-commenttemplates2.png"></p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm
deleted file mode 100644
index 0fdd640..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-console.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>CVS Console</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Console</H1>
-<P class="Para">The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ConsolePreferences)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team &gt; CVS &gt; Console</strong></a>
-
-preference page.</P>
-<TABLE width="100%" border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH>Default</TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Fixed width</TD>
-    <TD valign="top" align="left">Use this option to fix the width of console 
-      lines. Enabling this option allows the width to be specified. The default 
-      width is 80.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Limit console output</TD>
-    <TD valign="top" align="left">Use this option to limit the number of characters 
-      to be buffered by the console. The default buffer size is 500000.</TD>
-    <TD valign="top" align="left">Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Show CVS output in Console view</TD>
-    <TD valign="top" align="left">Use this option to show the output of CVS commands 
-      in the Console view. Enabling this option may show useful information but 
-      will slow down command operation.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Console text color settings</TD>
-    <TD valign="top" align="left">Use these options to change the colors for the 
-      text shown in CVS Console. 
-      <UL>
-        <LI>Command line text <I>(black)</I></li>
-        <LI>Message text <I>(blue)</I></li> 
-        <LI>Error text <I>(red)</I></LI>
-      </UL></TD>
-    <TD valign="top" align="left">&nbsp;</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img alt="Console preference page" src="../images/cvs-console-prefs.png"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm
deleted file mode 100644
index 3a7bc78..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-decorations.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>CVS Labels Decorations</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Label Decorations</H1>
-<P class="Para">The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSDecoratorPreferences)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team &gt; CVS &gt; Label Decorations</strong></a>
-
-preference page.</P>
-<TABLE width="100%" border="1" cellspacing="0">
-  <TR> 
-    <TD valign="top" align="left">General </TD>
-    <TD valign="top" align="left"> Use the options on this page to configure general 
-      preferences about the decorators: 
-      <ul>
-        <li><STRONG>Compute deep outgoing state for folders: </STRONG>Use this 
-          option to configure if the outgoing indicators on folders should be 
-          calculated. Disabling this option improves the performance of the decorators 
-          because calculating the dirty state for folders requires computing the 
-          dirty state for all child resources. (<EM>enabled by default</EM>)</li>
-        <li><strong>Enable font and color decorations: </strong>Use this option 
-          to enable font and color decorations. The colors and fonts used for 
-          outgoing changes, ignored resources, etc. can be configured on the 
-          <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-    	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    	<b>General &gt; Appearance &gt; Colors and Fonts</b></a> preference page</li>
-      </ul></TD>
-  </TR>
-  <TR> 
-    <TD valign="middle" align="left">Text </TD>
-    <TD valign="top" align="left"> Use the options on this page to configure how 
-      CVS information will be added to text labels.</TD>
-  </TR>
-  <TR> 
-    <TD valign="middle" align="left">Icons </TD>
-    <TD valign="top" align="left">Use the options on this page to configure the 
-      which icons can be used as overlays to show CVS specific information in 
-      views. </TD>
-  </TR>
-</TABLE>
-<p>This is what the General tab group of the CVS Label Decorations preference 
-  page looks like:</p>
-<p><img alt="General tab from the CVS Label Decorations preference page" src="../images/cvs-decoration-general.png"></p>
-<p>This is what the Text tab group of the CVS Label Decorations preference page 
-  looks like:</p>
-<p><img alt="Text tab from the CVS Label Decorations preference page" src="../images/cvs-decoration-text.png"></p>
-<p>This is what the Icons tab group of the CVS Label Decorations preference page 
-  looks like:</p>
-<p><img alt="Icons tab from the CVS Label Decorations preference page" src="../images/cvs-decoration-icon.png"></p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm
deleted file mode 100644
index a084f6d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-ext.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>CVS Ext Connection Method</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Ext Connection Method</H1>
-<P class="Para">The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ExtMethodPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team &gt; CVS &gt; Ext Connection Method</strong></a>
-  
-preference page.</P>
-<TABLE border="1" cellspacing="0">
-  <TR> 
-    <TD width="150" align="left" valign="top">Use external program vs. Use internal 
-      connection method </TD>
-    <TD width="650" align="left" valign="top">This page allows you to configure 
-      the ext connection method to use an external program or another connection 
-      method to to connect to a server. The later option is provided to allow 
-      custom connection method such as extssh to remain compatible with external 
-      CVS client tools.</TD>
-    <TD width="65" valign="top">Use external program</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">CVS_RSH </TD>
-    <TD valign="top" align="left"> Use this option to configure the program that 
-      will be called to connect to the remote CVS server. The RSH command is invoked 
-      with following calling pattern: 
-      <P><EM>CVS_RSH Parameters CVS_SERVER</EM></P></TD>
-    <TD valign="top">ssh </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Parameters </TD>
-    <TD valign="top" align="left"> Use this option to configure the parameters 
-      passed to the CVS_RSH program. The default parameter pattern is {host} -l 
-      {user}. It can be tailored using the {host}, {user}, {password} and {port} 
-      variables.</TD>
-    <TD valign="top">-l {host} {user} </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">CVS_SERVER </TD>
-    <TD valign="top" align="left">Use this option to configure the name of the 
-      remote CVS server program to run. Change this setting only if the remote 
-      CVS server binary name is different than the default. </TD>
-    <TD valign="top">cvs </TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left">Connection type</TD>
-    <TD valign="top" align="left">Use this option to set the connection method 
-      to be used for repository locations that use the ext connection method, 
-      if the option to use another connection method is enabled.</TD>
-    <TD>pserver</TD>
-  </TR>
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img alt="Ext Connection Method preference page" src="../images/cvs-ext.png"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm
deleted file mode 100644
index b2b40e4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-sync.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css"><link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>CVS Synchronize/Compare</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>																						  
-</head>
-
-
-<body bgcolor="#ffffff">
-<h1 class="Head">CVS Synchronize/Compare</h1>
-<p class="Para">The following preferences can be changed on the
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ComparePreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; CVS &gt; Synchronize/Compare</strong></a>
-
-  preference page.</p>
-<table border="1" cellspacing="0" width="100%">
-<thead>
-    <tr> 
-      <th width="164"> <p class="Para">Option</p></th>
-      <th width="490"> <p class="Para">Description</p></th>
-      <th width="152"> <p class="Para">Default</p></th>
-    </tr>
-  </thead>
-  <tbody><tr> 
-    <td align="left" valign="top" width="21%">Consider file contents in comparisons</td>
-    <td align="left" valign="top" width="58%"> Use this option to compare contents 
-      for changed files found when comparing CVS resources. Usually, time stamps 
-      are used to compare CVS files, and this is by far the fastest method. However, 
-      in some cases a more accurate comparison can be achieved by comparing file 
-      content. Disabling this option will speed up comparisons but may result 
-      in compare entries whose contents are the same. This option only applies 
-      to comparisons and merges but not Workspace synchronizations.</td>
-    <td align="left" valign="top" width="21%">Enabled</td>
-  </tr>
-  <tr> 
-    <td align="left" valign="top">Show revision comparisons in dialog</td>
-    <td align="left" valign="top">Use this this option to show revision comparisons 
-      in a dialog instead of a compare editor.</td>
-    <td align="left" valign="top">Disabled</td>
-  </tr>
-  <tr> 
-    <td align="left" valign="top">Automatically enable change set grouping in CVS synchronizations</td>
-    <td align="left" valign="top">Use the option to have change sets enabled by 
-      default in those CVS synchronizations that support them.</td>
-    <td align="left" valign="top">Disabled</td>
-  </tr><tr>
-      <td style="vertical-align: top;">Allow models (e.g. Java) to participate in&nbsp; synchronizations<br>
-      </td>
-      <td style="vertical-align: top;">Use this option to display model
-elements (such as Java packages) in the sync view. If&nbsp; this
-element is disabled, only resources will be shown in the sync view.<br>
-      </td>
-      <td style="vertical-align: top;">Enabled<br>
-      </td>
-    </tr>
-    <tr> 
-    	<td align="left" valign="top">Open a compare editor when comparing a single file</td>
-    	<td align="left" valign="top">Use this this option to open a compare editor when comparing a single file. 
-    	If disabled, the results of the comparison will be displayed in the Synchronize view.</td>
-    	<td align="left" valign="top">Enabled</td>
-  	</tr>
-
-</tbody></table>
-<p>Here is what the preference page looks like:</p>
-<p><img alt ="Synchronize/Compare preference page" src="../images/cvs-sync-compare.png"></p>
-<p><img alt="Related reference" src="../images/ngrelr.png" border="0"><br>
-<a href="ref-19.htm">Team</a><br>
-<a href="ref-33.htm">CVS Workspace Synchronization</a><br>
-<a href="ref-33a.htm">CVS Merge Synchronization</a></p>
-
-</body></html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-updatemerge.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-updatemerge.htm
deleted file mode 100644
index d034fed..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-updatemerge.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>CVS Update/Merge</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">CVS Update/Merge</H1>
-<P CLASS="Para"> The
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.UpdateMergePreferences)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team &gt; CVS &gt; Update/Merge</strong></a>
-
-preferences page contains options which 
-  affect the update/merge workflows.</P>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1">Option</TH>
-      <TH ROWSPAN="1" COLSPAN="1">Description</TH>
-      <TH ROWSPAN="1" COLSPAN="1">Default</TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-  	<TR> 
-      <TD COLSPAN="1" valign="top" align="left">When performing an update</TD>
-      <TD COLSPAN="1" valign="top" align="left">Use this option to select what the workflow
-      should be for performing an update. The options are:
-      <ul>
-          <li><strong>Preview all incoming changes before updating</strong>:
-          <br>All incoming changes are displayed in either the synchronize view or a dialog. You must explicitly
-          select which resources to update and deal with conflicts.</li>
-       
-          <li><strong>Update all non-conflicting changes and preview remaining updates</strong>:
-          <br>All non-conflicting resources are updated automatically and a list of conflicts (if applicable) are presented to you in
-          either the synchronize view or a dialog.</li>
-        
-          <li><strong>Never preview and use CVS text markup to indicate conflicts</strong>: 
-          <br>All non-conflicting resources are updated automatically and conflicts are dealt with by adding the conflicting code to the file
-          and using CVS text markup to delineate the boundaries of the conflict. You must then go through each file that had a conflict, look
-          for the markup, and manually merge the contents.</li>
-        </ul>
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left">Never preview and use CVS text markup to indicate conflicts</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> 
-          When an update preview is required</TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> Use 
-          this option to configure how to preview incoming changes. Changes can be previewed in
-          a dialog or in the Synchronize view.
-	 </TD>	  
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> 
-          Preview updates in the Synchronize view.</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<P>Here is what the CVS Update/Merge preference page looks like:&nbsp;&nbsp; </P>
-<P> </P>
-<img src="../images/cvs-updatemerge.png" alt="Team Preference Page" border="0">
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"> <br>
-<a href="ref-33.htm">CVS Synchronize view</a> </p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm
deleted file mode 100644
index f903be1..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs-watch-edit.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>CVS Watch/Edit</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS Watch/Edit</H1>
-<P class="Para">The following preferences can be changed on the
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.WatchEditPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; CVS &gt; Watch/Edit</strong></a>
-
-  preference page.</P>
-<TABLE border="1" cellspacing="0">
-<THEAD>
-    <TR> 
-      <TH width="164"> <P class="Para">Option</P></TH>
-      <TH width="490"> <P class="Para">Description</P></TH>
-      <TH width="152"> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Configure projects to use Watch/edit on checkout</TD>
-    <TD valign="top" align="left"> Use this option to indicate that files checked 
-      out out from the repository should be made read-only.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Enable temporary watches on edit</TD>
-    <TD valign="top" align="left"> Use this option to receive a notification whenever a user 
-    starts to edit a file that you are currently editing.</TD>
-    <TD valign="top" align="left">Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">When read-only files are modified in an editor</TD>
-    <TD valign="top" align="left"> Use this option to configure what occurs when 
-      a read-only file is modified in an open editor or by another tool. The options 
-      are: 
-      <ul>
-        <li><strong>Send a cvs edit notification to the server: </strong>Issues 
-          a cvs edit notification to the server before making the file writable. 
-          If other editors exist on the file, you will be prompted and may 
-          continue or cancel.</li>
-        <li><strong>Send a cvs edit notification to the server in the background: 
-          </strong>Issues a cvs edit notification to the server in the background 
-          after making the file writable. This allows you to keep typing 
-          uninterrupted while the edit notification is sent to the server.</li>
-        <li><strong>Edit the file without informing the server: </strong>Makes 
-          the file read-only without notifying the server.</li>
-      </ul></TD>
-    <TD valign="top" align="left">Send a cvs edit notification to the server in 
-      the background</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Before a CVS edit notification is sent to the 
-      server </TD>
-    <TD valign="top" align="left">Use this option to configure what occurs when 
-      a cvs edit notification needs to be send to the server. 
-      The options are: <ul>
-        <li><strong>Always Prompt: </strong>Always prompt for confirmation.</li>
-        <li><strong>Only prompt if there are other editors: </strong>Shows the 
-          user the list of current editors and allows you to confirm or cancel 
-          the edit.</li>
-        <li><strong>Never Prompt: </strong>Send the edit notification without 
-          prompting</li>
-      </ul></TD>
-    <TD valign="top" align="left">Only prompt if there are other editors</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Update edited files</TD>
-    <TD valign="top" align="left">Use this option to configure what occurs before
-    editing a file. The options are: <ul>
-        <li><strong>Always update before editing: </strong>Always update a file before editing.</li>
-        <li><strong>Prompt to update if out of date: </strong>Prompt for confirmation of update
-        only if a file is out of date.</li>
-        <li><strong>Never update: </strong>Never update a file before editing.</li>
-      </ul></TD>
-    <TD valign="top" align="left">Never update</TD>
-  </TR>  
-</TABLE>
-<p>Here is what the preference page looks like:</p>
-<p><img alt="CVS Watch/Edit preference page" src="../images/cvs-watch-edit.png"></p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" > <br>
-  <a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a></p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- > <a href="../tasks/tasks-cvs-watch.htm"><br>
-  Finding out who's working on what: watch/edit</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm
deleted file mode 100644
index c755cf0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-19cvs.htm
+++ /dev/null

@@ -1,252 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>CVS</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">CVS</H1>
-<p class="Head">The following sections describe the preferences available in the 
-  tab groups of the
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; CVS</strong></a>
-  
-  preferences page.</p>
-<h2 class="Para">General</h2>
-<p>On the General tab group of the CVS preference page you can customize several 
-  aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Validate server version compatibility on first 
-      connection </TD>
-    <TD valign="top" align="left">Use this option to enable a query of the CVS 
-      server version on the first connection to determine server compatibility. 
-      The server version will be output to the console and if an incompatibility 
-      is detected a warning message will be logged when connecting. </TD>
-    <TD>Enabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Confirm move tag on tag operation</TD>
-    <TD valign="top" align="left">Use this option to be prompted when the Move 
-      tag option is chosen when tagging.</TD>
-    <TD>Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Display detailed protocol output to stdout</TD>
-    <TD valign="top" align="left">Use this option to display the communication 
-      trace between the Workbench and a CVS server.</TD>
-    <TD>Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Refresh tags when comparing or replacing tags</TD>
-    <TD valign="top" align="left">Use this option to have the Compare with and 
-      Replace With tag dialogs automatically refresh the known tags by contacting 
-      the server.</TD>
-    <TD>Disabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Automatically share projects containing CVS 
-      meta information </TD>
-    <TD valign="top" align="left">Use this option to have any imported project 
-      that was checked out from CVS using a different CVS tool automatically shared 
-      with CVS. </TD>
-    <TD>Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Use .project project name instead of module name on check out</TD>
-    <TD valign="top" align="left">Use this option to use the project name stored in the .project file as the 
-    project name. If the checkout wizard cannot find a .project file, it will fallback to use the module name.</TD>
-    <TD>Disabled</TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left">Maximum number of files displayed when committing</TD>
-    <TD valign="top" align="left">Use this option to limit the number of files 
-      that get displayed in the commit dialog.</TD>
-    <TD>1000</TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left">Maximum number of comments on history</TD>
-    <TD valign="top" align="left">Use this option to limit the number of comments 
-      that get displayed in the commit dialog.</TD>
-    <TD>10</TD>
-  </TR>  
-</TABLE>
-<p>This is what the General tab group of the CVS preference page looks like:</p>
-<p><img alt="CVS preference page - General tab" src="../images/cvs-general.png"></p>
-<h2><strong>Files and Folders</strong></h2>
-<p>On the File and Folders tab group of the CVS preference page you can customize 
-  several aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Treat all new files as binary </TD>
-    <TD valign="top" align="left">Use this option to override the file content 
-      settings and treat all new files as binary. </TD>
-    <TD>Disabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Convert text files to use platform line ending</TD>
-    <TD valign="top" align="left">Use the option to convert the line endings of 
-      text files to the line ending used by the platform. This option can be disabled 
-      if you are checking out resources to a *nix drive that is mounted on a Windows 
-      machine. The option applies to both the files and the CVS control 
-files.</TD>
-    <TD>Enabled</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left"> Prune empty directories</TD>
-    <TD valign="top" align="left"> Use this option to specify the pruning of empty 
-      directories on update and in the synchronization view. Although pruned directories 
-      aren't shown in the workbench there is actually still an empty directory 
-      in the repository. This is helpful because CVS doesn't provide a client 
-      with the ability to remove directories from the server. It should be noted that
-      pruning is always on when checking out from a branch of version regardless 
-      of the value of this preference, in accordance with the CVS specification.</TD>
-    <TD>Enabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Delete unmanaged resources on replace </TD>
-    <TD valign="top" align="left">Use this option to allows resources not under 
-      CVS control to be deleted when replacing with resources from the repository. 
-    </TD>
-    <TD>Enabled </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Default text mode</TD>
-    <TD valign="top" align="left">Use this option to set the default keyword substitution 
-      for text files. </TD>
-    <TD>ASCII with keyword expansion (-kkv)</TD>
-  </TR>
-</TABLE>
-<p>This is what the File and Folders tab group of the CVS preference page looks 
-  like:</p>
-<p><img alt="CVS preference page - File and Folders tab" src="../images/cvs-files.png"></p>
-<h2>Connection</h2>
-<p>On the Connections tab group of the CVS preference page you can customize several 
-  aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left">Communication timeout </TD>
-    <TD valign="top" align="left">Use this option to configure the amount of time 
-      in seconds to wait before timing out from a connection to the CVS server. 
-    </TD>
-    <TD>60 seconds </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Quietness level </TD>
-    <TD valign="top" align="left">Sets the amount of status information CVS prints 
-      for a command. In <STRONG>Somewhat quiet</STRONG> mode the printing of unimportant 
-      informational messages is suppressed. The consideration of what is important 
-      depends on each command. In <STRONG>Very quiet</STRONG> mode all output 
-      except what is absolutely necessary to complete the command is suppressed. 
-      In <STRONG>Very Quiet</STRONG> mode, some CVS servers may not communicate 
-      important information about errors that have occurred. You may want to consider 
-      using <STRONG>Somewhat quiet</STRONG> mode instead. </TD>
-    <TD>Verbose </TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left">Compression</TD>
-    <TD valign="top" align="left">Use this option to set the compression level 
-      used when sending files between the client and server. Setting this option to
-      0 means that the compression is disabled.</TD>
-    <TD>0 (disabled)</TD>
-  </TR>
-</TABLE>
-<p>This is what the Connection tab group of the CVS preference page looks like:</p>
-<p><img alt="CVS preference page - Connection tab" src="../images/cvs-connection.png"></p>
-<h2>Prompting</h2>
-<p>On the Prompting tab group of the CVS preference page you can customize several 
-  aspects of the CVS Plug-in.</p>
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-    <TR> 
-      <TD valign="top" align="left">Allow empty commit comments</TD>
-      <TD valign="top" align="left"><p>Use the option to configure what happens 
-          if a commit comment is not provided when committing.</p>
-        <ul>
-          <li><STRONG>Yes: </STRONG>Allow the commit to occur without a comment.</li>
-          <li><strong>No: </strong>Do not allow the commit to proceed until a 
-            comment is provided.</li>
-          <li><STRONG>Prompt: </STRONG>Ask whether you want to allow 
-            the commit to proceed without a comment.</li>
-        </ul></TD>
-      <TD valign="top" align="left">Prompt</TD>
-    </TR>
-  <TR> 
-    <TD valign="top" align="left">Automatically save dirty editors before CVS 
-      operations </TD>
-    <TD valign="top" align="left"> Use this option to configure what happens when 
-      there are open editors with unsaved changes when a CVS operation is performed. 
-      Options are: 
-      <ul>
-        <li><STRONG>Yes: </STRONG>Automatically save unsaved changes in open editors 
-          before each CVS operation.</li>
-        <li><strong>No: </strong>Continue CVS operations even if there are unsaved 
-          changes in open editors.</li>
-        <li><STRONG>Prompt: </STRONG>Ask what to do with unsaved changes 
-          in open editors.</li>
-      </ul></TD>
-    <TD valign="top" align="left">Prompt </TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Consult change sets when synchronizing or committing</TD>
-    <TD valign="top" align="left">Use this option to configure whether all the resources that
-    are contained in the same change set should be included in the operation when synchronizing or
-    committing.</TD>
-    <TD valign="top" align="left">No</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Commit resources with warnings</TD>
-    <TD valign="top" align="left">Use this option to configure whether the resources with warnings
-    should be committed.</TD>
-    <TD valign="top" align="left">Yes</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Commit resources with errors</TD>
-    <TD valign="top" align="left">Use this option to configure whether the resources with errors
-    should be committed.</TD>
-    <TD valign="top" align="left">Prompt</TD>
-  </TR>  
-    
-</TABLE>
-<p>This is what the Prompting tab group of the CVS preference page looks like:</p>
-<p><img alt="CVS preference page - Prompting tab" src="../images/cvs-prompting.png"></p>
-<P><IMG alt="Related reference" src="../images/ngrelr.png" border="0"><BR>
-  <A href="ref-6.htm">Perspectives</A></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-2.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-2.htm
deleted file mode 100644
index d2545e7..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-2.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Workbench toolbar</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Workbench toolbar </H1>
-<P CLASS="Intro">The Workbench toolbar is displayed
-at the top of the Workbench window, directly underneath the menu bar.&nbsp; The
-contents of the toolbar change based on the active editor.&nbsp; Actions in the
-toolbar may apply to particular views, so these actions may be enabled or
-disabled based on the state of the currently active view or editor.</p>
-<P CLASS="Para">
-Here is an example of the toolbar in the Resource perspective:</P>
-<P CLASS="Para">
-<img src="../images/Image214_toobar_rsrc.png" alt="Workbench toolbar" border="0" ></P>
-<DIV CLASS="XRefList">
-
-<h2>
-New Wizard</h2>
-<P CLASS="Para">
-This command brings up a dialog where you can choose
-the type of resource to create.</P>
-
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Save The Open Editor Contents</h2>
-<P CLASS="Para">
-This command saves the file currently displayed in the editor area.</P>
-</DIV>
-<DIV CLASS="Topic"> 
-  <h2> Print</h2>
-  <P CLASS="Para"> This command opens a dialog which allows you to specify where 
-    you would like to print the contents of the file currently being displayed 
-    in the editor.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-External Tools</h2>
-  <P CLASS="Para"> This command presents a drop-down menu which allows you to run 
-    or configure external tools. <br>
-  </P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Search</h2>
-<P CLASS="Para">
-This command opens the search dialog, which allows you to search the
-workspace for
-specified text.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Navigation</h2>
-  <P CLASS="Para"> This tool group contains a variety of editor navigation commands. <br>
-  </P>
-</DIV>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-3.htm">Shortcut Bar</a>
-<br><a href="ref-4.htm">View Toolbars</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm
deleted file mode 100644
index fe2d628..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-20-fileContent.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Team File Content</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Team File Content</H1>
-<P CLASS="Intro"> On the
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.TextPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; File Content</strong></a>
-
-  preference page, you can associate 
-  file names or extensions with the type of data the file contains. The two choices 
-  for file content type are ASCII and Binary. Repository providers such as CVS 
-  can then use this information to provide content type appropriate behavior. 
-  For example, for ASCII files, CVS ensures that line terminators conform to those 
-  of the OS platform.</p> 
-<P CLASS="Intro">Entries are added to the File Content page in two ways. The first 
-  is through contributions from workbench plug-ins. Tools integrated into the 
-  workbench provide the workbench with the file content types for file extensions 
-  specific to the tool. The workbench itself also defines the file content type 
-  for file extensions that are common and appear frequently in the workbench (e.g. 
-  html,.png, etc.).</p> 
-<P CLASS="Intro">The second method is for users to add file content types explicitly 
-  on the File Content preference page. To do so, you can simply click on 
-  the <strong>Add Extension</strong> button and enter an extension or click on 
-  the <strong>Add Name</strong> button and add a name.. Following this, you can 
-  toggle the type associated with the name or extension by selecting the entry 
-  for the extension in the table and clicking <strong>Change</strong>. Entries 
-  can be removed from the list by selecting them and clicking <strong>Remove</strong>. 
-  Only those entries that were manually added can be removed. Entries contributed 
-  through the plug-in manifest can only be changed.</p> 
-<P CLASS="Intro">Here is what the Team File Content preference pages looks like:</p>
-<P CLASS="Intro"><img alt="Team File Content preference page" src="../images/team-file-content.png"></p>
-<p>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-cvs-11.htm">Setting the CVS keyword substitution mode</a>
-</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-20.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-20.htm
deleted file mode 100644
index 9341744..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-20.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Ignored Resources</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Team Ignored Resources</H1>
-<P CLASS="Intro"> On the
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.IgnorePreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; Ignored Resources</strong></a>
-
-  preference 
-  page, you can specify file name patterns to exclude from the version control 
-  management system. There is a list of file patterns against which resources 
-  will be matched before they are considered as version control candidates.&nbsp; 
-  These patterns may contain the wildcard characters "*" and "?".&nbsp; This pattern 
-  "*" represents any sequence of zero or more characters.&nbsp; This pattern "?" 
-  represents any one character.&nbsp; For example, you can specify a pattern of 
-  "*~", which would match any temporary files that end with "~".&nbsp;&nbsp; Any 
-  file or directory that matches any one of the patterns will be ignored during&nbsp; 
-  update or commit operations.</p> 
-<P CLASS="Para"> To add a file type to the ignore list, simply click <strong>Add 
-  Pattern</strong>. In the dialog, enter a file type (e.g. *.class). To remove 
-  a file type from the ignore list, simply select the file type in the ignore 
-  list and click <strong>Remove</strong>.&nbsp;</P>
-<P CLASS="Para"> You can temporarily disable ignoring the file pattern by de-selecting 
-  it from the list. You do not have to remove the specified file pattern from 
-  the list to temporarily disable it.</P>
-<P>Here is what the Ignored Resources preference page looks like:&nbsp;&nbsp; 
-</P>
-<P> </P>
-<img src="../images/Image_ignore_pref.png" alt="Ignored Resources Preference Page" border="0">
-<P CLASS="Para">&nbsp;</P>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-     <a href="ref-48a.htm">Ignoring Resources from Version Control</a>
-   </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-20team-models.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-20team-models.htm
deleted file mode 100644
index 3ddadee..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-20team-models.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Team Models</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Team Models</H1>
-<p>The
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.enabledModels)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Team &gt; Models</strong></a>
-
-preference page allows you to select which model providers
- are to be included in Team operations.</p> 
-
-<p>Here is what the Team Models preference page looks like:</p>
-<p><img alt="Team Models preference page" src="../images/team-models.png"></p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-21.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-21.htm
deleted file mode 100644
index fe30b36..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-21.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Install/Update</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Install/Update</H1>
-<P CLASS="Intro"> The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.update.internal.ui.preferences.MainPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Install/Update</strong></a>
-
-  page:</p> 
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <tr> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Maximum number of 'History' configurations</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Maximum number of configurations you want maintained in the configuration 
-          history. These configurations are maintained to allow you to revert 
-          to a previous configuration of installed feature versions.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          100</P></TD>
-    </tr>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Check digital signatures of downloaded archives</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option will check for digital signatures of downloaded archives.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Automatically select mirros</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option will automatically select a mirror when updating.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Valid updates</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Assuming that feature versions use the form 'major.minor.service', you 
-          can select what update level you want to choose from:</P> 
-        <dl>
-          <dt>equivalent</dt> 
-          <dd>Only service updates will be displayed.</dd>
-          <dt>compatible</dt>
-          <dd>Service updates and minor updates will be displayed.</dd>
-        </dl><br></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          equivalent </P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Update Policy</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          The update policy URL that controls the redirection of update sites 
-          within an organization.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          No policy</P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-
-<p>Here is what the Install/Update preference page looks like:&nbsp;&nbsp; </p>
-<P> </P><img src="../images/Image_pref_inup.png" alt="Install/Update Preference Page" border="0">
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a HREF="../tasks/tasks-36.htm">Updating Eclipse with the update manager</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a HREF="ref-net-preferences.htm">Network Connections</a>
-<br><a HREF="ref-61.htm">Help Menu</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-22.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-22.htm
deleted file mode 100644
index 885814e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-22.htm
+++ /dev/null

@@ -1,83 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Annotations preference page</title>
-   
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-
-<h1 class="Head">Annotations preference page</h1>
-<div class="Para">
-  <p>The following preferences can be changed on the
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Annotations)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Editors &gt; Text Editors &gt; Annotations</strong></a>
-  
-  preference page.</p>
-</div>
-
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th style="width: 25%;"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> Show in Text as </td>
-      <td align="left" valign="top">This option controls whether the selected 
-        annotation type is shown in the text. The corresponding text will be underlined 
-        with squiggles or highlighted.<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Show in Overview 
-          ruler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
-        </div></td>
-      <td align="left" valign="top"> This option controls whether the overview 
-        ruler on the right side of the text editor is shown.</td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show in Vertical ruler&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
-          <br>
-        </div></td>
-      <td align="left" valign="top"> This option controls whether the selected 
-        annotation type is shown in the vertical ruler.</td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Color</div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls the 
-          color for the selected annotation type.<br>
-        </div></td>
-    </tr>
-  </tbody>
-</table>
-
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-  
-  </tbody>
-</table>
-<p></p>
-<p>Here is what the Annotations preference page looks like: </p>
-<p><img src="../images/ref-annotationspref.png" alt="Image of the Annotations preference page"><br>
-</p>
-<p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-23.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-23.htm
deleted file mode 100644
index debaddd..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-23.htm
+++ /dev/null

@@ -1,249 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Workbench window layout</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Workbench window layout</H1>
-<P CLASS="Para">
-You can rearrange the layout of Workbench windows as follows:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-Drag views to different positions within the Workbench window.</LI>
-<LI CLASS="Item">
-Drag views to the shortcut bar to create a fast view.</LI>
-<LI CLASS="Item">
-Drag editors such that they are simultaneously visible beside, above, or below
-another editor.</LI>
-<LI CLASS="Item">
-Resize views and editors by dragging the sashes which separate them.</LI>
-</UL>
-<DIV CLASS="Topic">
-<h2>
-Drop cursors</h2>
-<P CLASS="Para">
-<i>Drop cursors</i> indicate where a view will dock when you release your mouse
-button. This indication is relative to the view or editor area underneath the cursor. </P>
-<TABLE BORDER="1" width="669" cellspacing="0">
-<CAPTION>
-Drop Cursors</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">
-Cursor</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Name</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-Description</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-1.png"  align="BASELINE" alt="Up arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock above</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear above the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-2.png"  align="BASELINE" alt="Down arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock below</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear below the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-3.png"  align="BASELINE" alt="Right arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock to the right</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear to the right of the view underneath the cursor.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-4.png"  align="BASELINE" alt="Left arrow">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Dock to the left</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear to the left of the view underneath the cursor. </P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" width="54">
-<P CLASS="Para">&nbsp;
-</P>
-<img src="../images/ref-5.png"  align="BASELINE" alt="Stack">
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="113">
-<P CLASS="Para">
-Stack</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" width="480">
-<P CLASS="Para">
-The view will appear as a tab in the same pane as the view underneath the cursor. </P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-<DIV CLASS="Topic">
-<DIV CLASS="Subtopic">
-<H2>
-Fast views</H2>
-<P CLASS="Para">
-From a view's title bar context menu, you can select Fast View to minimize the view
-as a&nbsp; button on the shortcut bar.</P>
-<P CLASS="Para">
-If a view is minimized in this way, you can click its
-button on the shortcut bar to bring it up in a fast view. To revert the fast
-view back to a docked view again, select the <i>Fast View</i> button on its title
-bar.</P>
-See <A HREF="ref-3.htm" CLASS="XRef">Perspective Bar</A></DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Double-Click</H2>
-    <P CLASS="Para"> Double-clicking a view or editor's title bar maximizes the 
-      part in the Workbench window.</P>
-  </DIV>
-  <DIV CLASS="Subtopic">
-<H2 CLASS="Head"> Title bar context menu and fast view toolbars</H2>
-    <P CLASS="Para"> From the context menu of a view or editor's title bar, you 
-      can select how you want the view to appear within the Workbench window.</P>
-    <TABLE BORDER="1" cellspacing="0">
-      <CAPTION>
-      View and editor title bar context menu options 
-      </CAPTION>
-      <THEAD>
-        <TR> 
-          <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> <A NAME="pgfId-1096571">O</A>ption</P></TH>
-          <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-        </TR>
-      </THEAD>
-      <TBODY>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Restore</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Restores the view to its originating (non-maximized/non-minimized) 
-              size and position within the Workbench.</P></TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Fast View<BR>
-              (views only)</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Minimizes the view and places a button for it in the shortcut bar.</p>
-            <P CLASS="Para"> This option, when used in a fast view, will restore 
-              the view to its originating (docked) position in the Workbench.</P>
-            <P CLASS="Para">See  <A HREF="ref-3.htm" CLASS="XRef">Perspective Bar</A> </p>
-          </TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left">Restore</TD>
-          <TD COLSPAN="1" valign="top" align="left">Restores the view or editor 
-            to its originating (non-maximized/non-minimized) size and position 
-            within the Workbench.</TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left">Move</TD>
-          <TD COLSPAN="1" valign="top" align="left">Move the part or part group.</TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left">Size</TD>
-          <TD COLSPAN="1" valign="top" align="left">Change the size of the part 
-            in the direction specified.</TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Maximize</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Maximizes the part in the Workbench window.</P></TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Minimize</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Minimizes the part in the Workbench window.</P></TD>
-        </TR>
-        <TR> 
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Close</P></TD>
-          <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-              Closes the part.&nbsp;&nbsp;</P></TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left"><p>Close Others</p>
-            <p>(editors only)</p></TD>
-          <TD COLSPAN="1" valign="top" align="left">Closes all editors except 
-            the current editor.</TD>
-        </TR>
-        <TR> 
-          <TD COLSPAN="1" valign="top" align="left"><p>Close All </p>
-            <p>(editors only)</p></TD>
-          <TD COLSPAN="1" valign="top" align="left">Closes all editors.</TD>
-        </TR>
-      </TBODY>
-    </TABLE>
-</DIV>
-</DIV>
-<P>Here is what a view's context menu looks like:
-</P>
-
-
-<P><img src="../images/Image229_view_popup.png" alt="View's context menu" border="1" >
-</P>
-<P>Here is what an editor's context menu looks like:
-</P>
-
-
-<P><img src="../images/Image229_editor_popup.png" alt="Editor's context menu" border="1" >
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-24.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-24.htm
deleted file mode 100644
index 01d6513..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-24.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editor area</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Editor area</H1>
-<P CLASS="Intro">
-
-The editor area is where you modify the contents of files in the Workbench.</p>
-<P CLASS="Para">
-Here is what the editor area looks like when multiple files are open and a text
-file is being edited:</P>
-<P CLASS="Para">
-<img src="../images/Image230_editor_area.png" alt="Editor Area" border="0" ></P>
-<DIV CLASS="Topic"> 
-  <h2>
-Marker bar</h2>
-<P CLASS="Para">
-The marker bar is the vertical bar located at the left of the editor area.&nbsp;&nbsp;</P>
-<P CLASS="Para">
-Here is what the marker bar looks like:</P>
-  <P CLASS="Para"> <img src="../images/Image231_marker_bar.png" alt="Marker Bar" border="0" ></P>
-<h2>Markers</h2>
-<P CLASS="Para">
-Markers are displayed in the marker bar, to the left of the text editor.</P>
-<P CLASS="Para">
-Depending on the type of file displayed in the editor area, three kinds of markers
-may be displayed:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-Bookmarks </LI>
-<LI CLASS="Item">
-Task markers (for associated tasks) </LI>
-<LI CLASS="Item">
-Debugging breakpoints </LI>
-</UL>
-<P CLASS="Para">
-You can create and associate a marker with a specific line in a file by accessing the context menu from the marker bar,
-which is directly to the left of that line. </P>
-  <P CLASS="Para"> Here is what the context menu of the marker bar for a java 
-    editor looks like: </P>
-  <P CLASS="Para"> <img src="../images/Image232_marker_context.png" alt="Marker Bar Menu" border="1" > 
-  </P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Types of editors</h2>
-<P CLASS="Para">
-The Workbench uses three types of editors:</P>
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-Internal: These editors are launched inside the editor area in the Workbench window.</LI>
-<LI CLASS="Item">
-External: You can go outside the Workbench in the file system, edit a Workbench file outside the Workbench, and save the edited file. For example, 
-imagine that you add an SGML file to the Workbench. Later, you go into the file system and open the 
-file in an SGML editor, then save the file. The edited SGML file is still represented in the Workbench, even 
-though you did not edit the file in the Workbench. If you associate a file type with an external editor in 
-the Workbench
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Editors &gt; File Associations</b></a>
-preference page), then the Workbench
-will launch this external editor.</LI>
-<LI CLASS="Item">
-ActiveX: On Microsoft Windows platforms, the Workbench makes use of ActiveX controls for applications that allow for them. For example, Microsoft Word supports being embedded as an OLE
-document. Thus if you have a <i>.doc</i> file in the Workbench, and Word is registered as the editor for
-<i>.doc </i>files in your operating system, then opening the file will launch Word as an OLE document within the Workbench editor area. Notice how OLE documents also add such features as menus
-and toolbar buttons.</LI>
-</UL>
-<p>The following illustrates Microsoft Word embedded as an OLE document:</p>
-<DIV CLASS="Figure">
-    <DIV> <IMG SRC="../images/ref-7.png"  alt="Workbench with OLE Editor" > 
-    </DIV>
-</DIV>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-25.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-25.htm
deleted file mode 100644
index 16e2b41..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-25.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-             
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-             
-  <meta http-equiv="Content-Style-Type" content="text/css">
-              
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Compare editor</title>
-</head>
-  <body bgcolor="#ffffff">
-       
-<h1 class="Head"> Compare editor</h1>
-       
-<p class="Para"> You can view the differences between two files by comparing 
- them. You can compare different files, you can compare versions in 
- the Workbench with versions in the repository, or with the local edit history.
- In some cases you can compare three files (when a common ancestor exists).</p>
-       
-<p class="Para"> After a comparison is carried out, the compare editor opens 
- in the editor area. In the compare editor, you can browse through 
- all the differences and copy highlighted differences between the compared 
- resources. You can save changes to resources that are made in the comparison 
- editor.</p>
- 
-<p class="Para"> Compare editor allows for two kind of navigation: using differences
-or changes. A change is a portion of text that has been modified within the line,
-and the difference is a section of file consisting of one or more lines, and can contain
-many changes.</p>
-
-<p class="Para">
-<img
- src="../images/compare-editor-diff-change.png"
- alt="Differences and changes."  border="0" align="top"> 
-</p>
-
-<p class="Para">
- Differences are marked with blue color, changes with red.
-</p>  
-       
-<p class="Para">Here is how the compare editor looks when you open it from a CVS 
-Workspace synchronization.</p>
-       
-<p class="Para"><img
- src="../images/compare-editor.png"
- alt="Picture of 3-paned editor. Top pane compares project structure; bottom 2 panes (side by side) compare lines of source."  border="0" align="top"> 
-</p>
-       
-<div class="Topic">    
-<div class="Subtopic">    
-<h2>Toolbar</h2>
-       
-<p>The toolbar of the Compare editor includes the following buttons:</p>
-           
-<dl>
-  <dt>Switch Compare Viewer&nbsp;<img src="../images/view_menu.png"></dt>
-  <dd>Basing on the content type the system determines which compare viewer 
-  should be used during a comparison. The button opens a drop down menu which allows to choose between other 
-  viewers registered for the same content type. If there is no alternative 
-  content viewer available the button is hidden.</dd>
-  <dt>Control Visibility of Ancestor Pane&nbsp;<img src="../images/ancestorpane_co.gif"></dt>
-  <dd>There are two conditions under which a three way compare will occur, 
-		both when using the Team version management support: when comparing 
-		a file that is in conflict, and when comparing a file being merged 
-		from a branch. In both cases, the system will determine a common 
- 		ancestor in the repository to compare the conflict or merge against. 
- 		This button determines the visibility of the third editor. By default, 
- 		the ancestor pane is not visible.</dd>
-  <dt>Perform Three way/Two way Compare&nbsp;<img src="../images/twowaycompare_co.gif"></dt>
-  <dd>The compare editor can be toggled between performing a three way compare 
-		or a two way compare which ignores the common ancestor.</dd>
-  <dt>Copy All from Left to Right&nbsp;<img src="../images/copy_r_co.gif"></dt>
-  <dd>Copies the entire contents of the file in the left pane into the file 
-          in the right pane, making the contents of the two files identical.</dd>
-  <dt>Copy All Non-Conflicting Changes from Right to Left&nbsp;<img src="../images/copy_l_co.gif"></dt>
-  <dd>Copies all the non-conflicting changes from the right pane into the left
-  pane. Conflicting changes must be copied individually.</dd>
-  <dt>Copy Current Change from Left to Right&nbsp;<img src="../images/copycont_r_co.gif"></dt>
-  <dd>Merges changes in two files by copying the highlighted change in the 
-		left pane into the highlighted fragment on the right. This 
- 		will overwrite the highlighted fragment in the right pane.</dd>
-  <dt>Copy Current Change from Right to Left&nbsp;<img src="../images/copycont_l_co.gif"></dt>
-  <dd>Does the opposite of the one just described.</dd>
-  <dt>Select Next Difference&nbsp;<img src="../images/next_diff_nav.gif"></dt>
-  <dd>Highlights the next difference that is found between the compared resources.</dd>
-  <dt>Select Previous Difference&nbsp;<img src="../images/prev_diff_nav.gif"></dt>
-  <dd>Highlights the previous difference that is found between the compared 
-          resources.</dd>
-  <dt>Select Next Change&nbsp;<img src="../images/next_change_nav.gif"></dt>
-  <dd>Highlights the next change that is found between the compared resources.</dd>
-  <dt>Select Previous Change&nbsp;<img src="../images/prev_change_nav.gif"></dt>
-  <dd>Highlights the previous change that is found between the compared resources.</dd>
-</dl>
-           
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts">
-   <br>
-   <a href="../concepts/concepts-30.htm">Synchronizing with a CVS Repository</a><br>
-   <a href="../concepts/concepts-29.htm">Three way comparisons</a>
-</p>
-         
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks">
-   <br>
-    <a href="../tasks/tasks-68.htm">Comparing resources</a><br>
-    <a href="../tasks/tasks-115.htm">Synchronizing with the repository</a><br>
-    <a href="../tasks/tasks-68dg.htm">Merging changes in the compare editor</a><br>
-    <a href="../tasks/tasks-113b.htm">Resolving conflicts</a><br>
-    <a href="../tasks/tasks-68b.htm">Setting preferences for comparing files</a><br>
-    <a href="../tasks/tasks-101.htm">Comparing resources with repository versions</a>    
-</p>
-      </div>
-    </div>
-        
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-26.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-26.htm
deleted file mode 100644
index ef46974..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-26.htm
+++ /dev/null

@@ -1,89 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Search view</title></head><body bgcolor="#ffffff">
-
-<h1>Search view</h1>
-
-<p>
-This view displays the results of a search.&nbsp;&nbsp;</p>
-
-<p>
-Text searches will only search for expressions in files with extensions (file
-types) specified in the search dialog.</p>
-
-<p>
-Here is what the Search view looks like:</p>
-
-<p>
-<img src="../images/Image237_search_view.png" alt="Search View" border="0" ></p>
-
-<dl>
-<dt>Show Next Match</dt>
-<dd>
-This command highlights the next match of the search
-expression in the editor area, opening the file if required.</dd>
-
-<dt>Show Previous Match</dt>
-<dd>
-This command highlights the previous match of the
-search expression in the editor area, opening the file if required.</dd>
-
-
-<dt>Remove Selected Matches</dt>
-<dd>Removes all highlighted matches from the search results.</dd>
-
-<dt>Remove All Matches</dt>
-<dd>Remove all matches from the search results.</dd>
-
-<dt>Expand All</dt>
-<dd>Expand all matches in the hierarchical view.</dd>
-
-<dt>Collapse All</dt>
-<dd>Collapse all matches in the hierarchical view.</dd>
-
-<dt>Run the current search again</dt>
-<dd>Re-runs the most recent search.</dd>
-
-<dt>Cancel Current Search</dt>
-<dd>Cancel a search that is running.</dd>
-
-
-<dt>Previous Search Results</dt>
-<dd>
-This command allows you to browse previously
-conducted searches and repeat a previous search.&nbsp; You can select a previous
-search from the drop-down menu or clear the search history.</dd>
-
-<dt>Pin the Search view</dt>
-<dd>
-Pinning the search view means that subsequent searches will shown their
-results in another search view and that the pinned view remains unchanged.
-</dd>
-
-</dl>
-
-
-<p><img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-<br>
-<a href="../concepts/csearchview.htm">Search view</a><br>
-</p>
-
-<p><img src="../images/ngrelt.png" alt="Related tasks" border="0" >
-<br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-</p>
-
-<p><img src="../images/ngrelr.png" alt="Related reference" border="0" >
-<br>
-<a href="ref-45.htm">File search</a><br>
-</p>
-
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-27.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-27.htm
deleted file mode 100644
index d4687bb..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-27.htm
+++ /dev/null

@@ -1,221 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Project Explorer view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>
-Project Explorer view</H1>
-<P CLASS="Intro">
-
-This view provides a hierarchical view of the resources in the Workbench.</p>
-<P CLASS="Para">
-Here is what the Project Explorer view looks like:</P>
-<P CLASS="Para">
-<img src="../images/Image241_nav_view.png" alt="Project Explorer View" border="0" ></P>
-<p CLASS="Head">
-To add the Project Explorer view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ResourceNavigator)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Project Explorer</b></a>.
-</p>
-<P CLASS="Para">&nbsp;
-</P>
-<h2>Toolbar</h2>
-<H3>Collapse All</H3>
-<P>This command collapses the tree expansion state of all resources in the
-view.</P>
-<H3>Link with Editor</H3>
-<P>This command toggles whether the Project Explorer view selection is linked to
-the active editor. When this option is selected, changing the active editor
-will automatically update the Project Explorer selection to the resource being
-edited.</P>
-<P><BR>
-</P>
-<H2>Menus</H2>
-<P>Click the black upside-down triangle icon to
-open a menu of items specific to the Project Explorer view. Right-click inside
-the view to open a context menu.&nbsp;</P>
-<H3>Top Level Elements</H3>
-<P>Choose whether to show working sets or projects as top level elements.  Chosing working sets allows easy grouping of projects in large workspaces.</P>
-<H3>Select Working Set</H3>
-<P>Opens the <B>Select Working Set</B> dialog to allow selecting a working set for the Project Explorer view.</P>
-<H3>Deselect Working Set</H3>
-<P>Deselects the current working set. </P>
-<H3>Edit Active Working Set</H3>
-<P>Opens the <B>Edit Working Set</B> dialog to allow changing the current working set.</P>
-<DIV CLASS="Topic">
-<h3>
-Package Presentation</h3>
-<P CLASS="Para">
-Toggles package compression on and off.  If it's Flat, certain folder structures (such as Java packages) will be compressed to make
-navigation easier.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3>
-Customize View</h3>
-<P CLASS="Para">
-This command allows customization of view filters and content modules.  The previous will allow you to supress the display of certain
-types of files while the later will allow entirely new types of content to be shown in the view.  Here
-is what the Customize View dialog looks like:</P>
-<P CLASS="Para">
-<img src="../images/Image210_filefilter.png" alt="Filters dialog" border="0" ></P>
-</DIV>
-<H3>Link with Editor</H3>
-<P>See the toolbar item description above.</P>
-<P><BR>
-In addition to these menu items, the Project Explorer view menu shows a list of
-recently used working sets that have been selected in the view.</P>
-<P><BR>
-</P>
-<h2>Context menu</h2>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-New</H3>
-<P CLASS="Para">
-This command allows you to create a new resource in the Workbench. Select the
-type of resource to create from the submenu.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Copy</H3>
-<P CLASS="Para">This command copies the selected resource to the clipboard.</P>
-</DIV>
-<H3>Paste</H3>
-<P>This command pastes resources on the clipboard into the selected project
-or folder. If a resource is selected the resources on the clipboard are
-pasted as siblings of the selected resource.</P>
-<h3 CLASS="Head">
-Delete</H3>
-<P CLASS="Para">This command deletes the selected resource from the workspace.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Move</H3>
-<P CLASS="Para">
-This command moves the selected resource to another location.
-A dialog will appear, prompting for the destination location to which the resource
-will be moved.&nbsp;&nbsp;</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Rename</H3>
-<P CLASS="Para">
-This command allows you to specify a new name for the selected resource.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Import</H3>
-<P CLASS="Para">
-This command opens the import wizard and allows you to select resources
-to import into the Workbench.
-</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Export</H3>
-<P CLASS="Para">
-This command opens the export wizard and allows you to export resources
-to an external location.
-</P>
-</DIV>
-
-<h3 CLASS="Head">
-Refresh</H3>
-<P CLASS="Para">This command refreshes the Workbench's view of the selected resource and
-its children. For example, this is used when you create a new file for
-an existing project outside the Workbench and want the file to appear in
-the Project Explorer view.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Close Project</H3>
-<P CLASS="Para">The close project command is visible when an open project is selected.
-This command closes the selected project.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Close Unrelated Projects</H3>
-<P CLASS="Para">This command will close any project which are unrelated to the selected project.</P>
-</DIV>
-<H3>Open Project</H3>
-<P>The open project command is visible when a closed project is selected.
-This command opens the selected project.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Team</H3>
-  <p CLASS="Head"> Menu items in the Team sub-menu are related to version control 
-    management and are determined by the version control management system that 
-    is associated with the project. Eclipse provides the special menu item<b> 
-    Share Project...</b> for projects that are not under version control management. 
-    This command will present a wizard that allows you to choose to share 
-    the project with any version control management systems that has been added 
-    to Eclipse. Eclipse ships with support for CVS.</p>
-  </DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Compare With</H3>
-
-<P CLASS="Para">
-Commands on the Compare With sub-menu allow you to do one of the following
-types of compares: </P>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item"> Compare two or three selected resources with each other</LI>
-    <LI CLASS="Item"> Compare the selected resource with remote versions (if the 
-      project is associated with a version control management system).</LI>
-    <LI CLASS="Item"> Compare the selected resource with a local history state</LI>
-  </UL>
-
-<P CLASS="Para">After you select the type of compare you want to do, you will 
-      either see a compare editor or a compare dialog. In the compare editor, 
-      you can browse and copy various changes between the compared resources.&nbsp; 
-      In the compare dialog, you can only browse through the changes.&nbsp;&nbsp;</P>
-
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Replace With</h3>
-  <P CLASS="Para"> Commands on the Replace With sub-menu allow you to replace the 
-    selected resource with another state from the local history. If the project 
-    is under version control management, there may be additional items supplied 
-    by the version control management system as well.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">
-Properties</H3>
-  <P CLASS="Para"> This command displays the properties of the selected resource. 
-    The kinds of properties that are displayed depend on what type of resource 
-    is selected. Resource properties may include (but are not limited to):</P>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item">Path relative to the project in which it is held</LI>
-    <LI CLASS="Item">Type of resource</LI>
-    <LI CLASS="Item">Absolute file system path, or name of path variable when using linked resources</LI>
-    <LI CLASS="Item">Resolved path variable when using a path variable for a linked resource</LI>
-    <LI CLASS="Item">Size of resource</LI>
-    <LI CLASS="Item">Last modified date</LI>
-    <LI CLASS="Item">Read-only status</LI>
-    <LI CLASS="Item">Derived resource status</LI>
-    <LI CLASS="Item">Execution arguments, if it is an executable resource</LI>
-    <LI CLASS="Item">Program launchers, if it is launchable</LI>
-    <LI CLASS="Item">Project dependencies, if any</LI>
-  </UL>
-</DIV>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-<br><A HREF="../concepts/concepts-29.htm">Three-way compare</A>
-<br><a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="ref-25.htm">Compare editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-28.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-28.htm
deleted file mode 100644
index 63a073d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-28.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Bookmarks view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Bookmarks view</H1>
-<P CLASS="Para">
-The Bookmarks view displays user defined bookmarks.</P>
-<P CLASS="Para">
-<img align="texttop" border="0" src="../images/Image244_bmark_view.png" alt="Bookmarks view" ></P>
-<p CLASS="Head">
-To add the Bookmarks view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>.
-</p>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Description column contains a description of the bookmark.&nbsp;
-You can edit the description by selecting <b>Properties</b> from the context menu.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Resource and Path columns provide the name and location of the resource
-associated with each bookmark.</P>
-</DIV>
-<P CLASS="Para">
-The Location column indicates the line number of the bookmark within its associated resource.</P>
-<h2>Toolbar</h2>
-<p>The toolbar of the Bookmarks view includes the following buttons.</p>
-<dl>
-  <dt>Delete</dt>
-  <dd>Delete the selected bookmark.</dd>
-  <dt>Go to</dt>
-  <dd>Open the bookmark's resource and navigate to the bookmarked region.</dd>
-</dl>
-<h2>Menus</h2>
-<p>Click the icon at the left end of the view's title bar to open a menu of items
-generic to all views. Click the black upside-down triangle icon to open a menu of items
-specific to the Bookmarks view. Right-click inside the view to open a context menu.&nbsp;</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-81b.htm">Creating a bookmark for an entire file</a><br><a href="../tasks/tasks-81.htm">
-Creating a bookmark within a file</a><br><a href="../tasks/tasks-82.htm">
-Deleting a Bookmark</a><br></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-29.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-29.htm
deleted file mode 100644
index c01c14a..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-29.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Properties view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Properties view</H1>
-<P CLASS="Para">
-This view displays property names and basic properties of a selected resource.
-Here is an example:</P>
-<P CLASS="Para">
-<img src="../images/Image240_props_view.png" alt="Properties view" border="0" ></P>
-<P CLASS="Para">Toolbar buttons allow you to toggle whether to display
-properties by category and whether to filter advanced properties. Another
-toolbar button allows you to restore the selected property to its default value.</P>
-<P>To see more detailed information about a resource than the Properties view
-gives you, right-click the resource name in one of the navigation views and select
-Properties from the pop-up menu.
-</P>
-<p CLASS="Head">
-To add the Properties view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>.
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-3.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-3.htm
deleted file mode 100644
index e906877..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-3.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspective bar</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Perspective Bar</H1>
-<P CLASS="Intro">
-The perspective bar allows quick access to perspectives that are currently open, as well
-as providing an easy way to open a new perspective.&nbsp; The perspective bar may be docked in three different positions.  It may be docked in the upper right corner (the default position), the upper left corner (under the main toolbar) and to the far left.</p>
-<P CLASS="Para">
-Here is an example of what the perspective bar looks like:&nbsp;</P>
-<P CLASS="Para">
-<img src="../images/Image211_perspective.png" alt="Perspective Bar" border="0"></P>
-<DIV CLASS="Topic">
-<h3>
-Open Perspective</h3>
-<P CLASS="Para">
-This command opens a new perspective that is
-selected from a drop-down menu.  All of the perspectives that are open within a single Workbench window are
-shown on the shortcut bar.</P>
-</DIV>
-<DIV CLASS="Topic"> 
-  <h3>Perspective Buttons</h3>
-  <P CLASS="Para"> These buttons provide a quick way to switch to one of the open 
-    perspectives in the current Workbench window.&nbsp; </P>
-  <P CLASS="Para"></P>
-  <h3>Available Perspectives</h3>
-  <p>There are several available perspectives, while one is set as a default, 
-    others can be manually added to the perspective bar. To add new perspectives 
-    to your workspace, click <strong>Open Perspective</strong> <img src="../images/open_persp.png" alt="Open Perspective Icon" border="0" >, 
-    select <strong>Other</strong> and choose from the following
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    available perspectives</a>:</p>
-</DIV>
-<ul>
-  <li>CVS Repository Exploring;</li>
-  <li>Debug;</li>
-  <li>Java;</li>
-  <li>Java Browsing;</li>
-  <li>Java Type Hierarchy;</li>
-  <li>Plug-in Development;</li>
-  <li>Resource;</li>
-  <li>Team Synchronizing.</li>
-</ul>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" > <br>
-  <a href="ref-6.htm">Perspectives</a> <br>
-  <a href="ref-4.htm">View Toolbars</a> <br>
-  <a href="ref-2.htm">Workbench Toolbar</a> <br>
-  <a href="ref-23.htm">Workbench Window Layout</a> </p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-30.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-30.htm
deleted file mode 100644
index 3b8ed0a..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-30.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Outline view</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<body>
-<H1 CLASS="Head">
-Outline view</H1>
-
-<P>This view displays an outline of a structured file
-that is currently open in the editor area, and&nbsp; lists structural
-elements.&nbsp;The contents of the outline view are editor-specific. In the
-example below, which is for a Java source file, the structural elements are classes, variables, and methods.
-The contents of the toolbar are also editor-specific.
-</p>
-
-<P><img src="../images/ref-8.png" alt="Picture of Outline view showing structure for a Java file" border="0" >
-</p>
-<p CLASS="Head">
-To add the Outline view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ContentOutline)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Outline</b></a>.
-</p>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm
deleted file mode 100644
index c46a55d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-30a.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS views</title>
-
-</HEAD>
-<body>
-<H1 CLASS="Head">
-CVS views</H1>
-
-<P>There are several CVS specific views, the CVS Repositories view, the CVS Resource 
-History view, the CVS Console view and the Synchronize view.
-</p>
-<P>  See Team Support in the
-Reference section for details on these views.
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-     <a href="ref-32.htm">CVS Repositories view</a><br>
-     <a href="ref-32a.htm">CVS Resource History View</a><br>
-     <a href="ref-32b.htm">CVS Console view</a><br>
-     <a href="ref-33.htm">Synchronize view</a>
-     
-   </p>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-31.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-31.htm
deleted file mode 100644
index 64c5ce6..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-31.htm
+++ /dev/null

@@ -1,101 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tasks view (reference)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Tasks view</H1>
-<P CLASS="Para"> The Tasks view displays tasks that you add manually. You can 
-  associate a task with a resource in the Workbench, but this is not required.</P>
-<p><img src="../images/Image243_tasks_view.png" alt="Picture of the Tasks view with two dummy tasks added to it." border="0"></p>
-<p CLASS="Head">
-By default, the Tasks view is included in the Resources perspective. To add it
-to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.TaskList)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Tasks</b></a>.
-</p>
-<p CLASS="Head">
-The following icons are used by the Tasks view:</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Icon table">
-  <tr> 
-    <th valign="top" align="center">Icon</th>
-    <th valign="top" align="left">Description</th>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/ref-21.png" alt=" High priority task item" border="0" ></td>
-    <td valign="top" align="left"> High priority task</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/ref-23.png" alt=" Low priority task icon" border="0"></td>
-    <td valign="top" align="left"> Low priority task </td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/ref-25.png"  alt="Completed task icon" border="0"></td>
-    <td valign="top" align="left"> Completed task </td>
-  </tr>
-    <tr> 
-    <td valign="top" align="center"><img src="../images/addtask.png" alt="Add task" border="0" ></td>
-    <td valign="top" align="left"> Add task</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/delete_edit.png" alt="Delete" border="0"></td>
-    <td valign="top" align="left"> Delete</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/filter_ps.png" alt="Filter" border="0" ></td>
-    <td valign="top" align="left"> Filter</td>
-  </tr>
-
-</table>
-
-<p CLASS="Head"> The first column indicates whether the task is completed. Completed 
-  tasks are flagged with a check mark, which you add manually.</p>
-<p CLASS="Head"> The second column indicates whether the task is high, normal, 
-  or low priority.&nbsp;</p>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Description column contains a description of the line item.&nbsp;
-You can edit the description of user-defined tasks by selecting <b>Properties</b> from the context menu.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Resource and Path columns provide the name and location of the resource
-associated with each line item.</P>
-</DIV>
-<P CLASS="Para">
-The Location column indicates the line number of the line item within its associated resource.</P>
-<h2>Toolbar</h2>
-<p>The toolbar of the Tasks view includes the following buttons.</p>
-<dl>
-  <dt>Add task</dt>
-  <dd>Manually add a &quot;to do&quot; item to the Tasks view.</dd>
-  <dt>Delete</dt>
-  <dd>Delete the selected line item.</dd>
-  <dt>Filter</dt>
-  <dd>Filter the view according to the type of item.</dd>
-</dl>
-<h2>Menus</h2>
-<p>Click the icon at the left end of the view's title bar to open a menu of items 
-  generic to all views. Click the upside-down triangle icon to open a menu of 
-  items specific to the Tasks view. Right-click inside the view to open a context 
-  menu.&nbsp;</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-77.htm">Adding line items in the Tasks view</a>
-<a href="../tasks/tasks-77b.htm"><br>Associating a task with a resource</a>
-<a href="../tasks/tasks-78.htm"><br>Deleting tasks</a>
-<a href="../tasks/tasks-79.htm"><br>Filtering the task view</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm
deleted file mode 100644
index 56748ae..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-31a.htm
+++ /dev/null

@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Problems view (reference)</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Problems view</H1>
-<P CLASS="Para"> The Problems view displays system-generated errors, warnings, 
-  or information associated with a resource. These are typically produced by builders. 
-  For example, if you save a Java source file that contains syntax errors, the 
-  errors will automatically be logged in this view.</P>
-<p><img src="../images/prob.png" alt="Picture of the Problems view with two warnings added to it." border="0" ></p>
-<p CLASS="Head"> By default, the Problems view is included in the Resources perspective. 
-  To add it to the current perspective, click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.ProblemView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Problems</b></a>.
-</p>
-<p CLASS="Head"> The following icons are used by the Problems view:</p>
-<table border="1" cellspacing="0" cellpadding="5" summary="Icon table">
-  <tr>
-    <th valign="top" align="center">Icon</th>
-    <th valign="top" align="left">Description</th>
-  </tr>
-  <tr>
-    <td valign="top" align="center"><img src="../images/ref-20.png" alt=" Information icon" border="0" ></td>
-    <td valign="top" align="left">
-      Information&nbsp;    </td>
-  </tr>
-  <tr>
-    <td valign="top" align="center"><img src="../images/ref-22.png" alt="Warning icon" border="0"></td>
-    <td valign="top" align="left">
-      Warning    </td>
-  </tr>
-  <tr>
-    <td valign="top" align="center"><img src="../images/ref-24.png" alt="Error icon" border="0"></td>
-    <td valign="top" align="left">
-      Error    </td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/delete_edit.png" alt="Delete" border="0"></td>
-    <td valign="top" align="left"> Delete</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="center"><img src="../images/filter_ps.png" alt="Filter" border="0" ></td>
-    <td valign="top" align="left"> Filter</td>
-  </tr>
-</table>
-
-<p CLASS="Head"> The first column indicates whether the line item is a task or 
-  a compiler generated error, warning or info.</p>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Description column contains a description of the line item.&nbsp;
-You can edit the description of user-defined tasks by selecting <b>Properties</b> from the context menu.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<P CLASS="Para">
-The Resource and Path columns provide the name and location of the resource
-associated with each line item.</P>
-</DIV>
-<P CLASS="Para">
-The Location column indicates the line number of the line item within its associated resource.</P>
-<h2>Toolbar</h2>
-<p>The toolbar of the Problems view includes the following buttons.</p>
-<dl>
-  <dt>Delete</dt>
-  <dd>Delete the selected line item.</dd>
-  <dt>Filter</dt>
-  <dd>Filter the view according to the type of item.</dd>
-</dl>
-<h2>Menus</h2>
-<p>Click the icon at the left end of the view's title bar to open a menu of items 
-  generic to all views. Click the upside-down triangle icon to open a menu of 
-  items specific to the Problems view. Right-click inside the view to open a context 
-  menu.&nbsp;</p>
-
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-32.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-32.htm
deleted file mode 100644
index 28a5a86..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-32.htm
+++ /dev/null

@@ -1,232 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-         
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-         
-  <meta http-equiv="Content-Style-Type" content="text/css">
-          
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>CVS Repositories view</title>
-    
-</head>
- <body bgcolor="#ffffff">
-     
-<h1> CVS Repositories view</h1>
-     
-<p class="Para">The CVS Repositories view, which is part of the CVS Repository
-    Exploring perspective, shows the CVS repository locations that you have
- added to your Workbench.&nbsp;Expanding a location reveals the main trunk
- (HEAD), project versions and branches in that repository. You can further
- expand the project versions and branches to reveal the folders and files
- contained within them. </p>
-     
-<p>The pop-up menu for this view also allows you to specify new repository
- locations. Use the CVS Repositories view to check out resources from
- the repository to the Workbench, configure the branches and versions
-shown by the view, view resource history, and compare resource versions.
-</p>
-     
-<p class="Para"> Here is what the CVS Repositories view looks like:</p>
-     
-<p class="Para"> <img
- src="../images/Image242_repo_view.png" alt="CVS Repositories View"  border="0" align="top"> 
-</p>
-     
-     
-  
-<p>There are two types of folders displayed in the repositories view. For the 
-  most part, they can be treated in the same fashion. That is, they can be checked 
-  out from the Repositories view, etc. However, there are some cases where modules 
-  cannot be expanded in the Repositories view even though they can still be checked 
-  out. </p>
-<table width="75%" border="1">
-  <tr>
-    <td width="9%" align="center"><img alt="Image for a CVS module that maps to a folder on the CVS server." src="../images/cvs_folder_rep.png"></td>
-    <td width="91%">A CVS module that maps to a folder on the CVS server.</td>
-  </tr>
-  <tr>
-    <td align="center"><img alt="Image for a CVS module defined in the CVSROOT/modules file of the repository." src="../images/cvs_module_rep.png"></td>
-    <td>A CVS module defined in the CVSROOT/modules file of the repository.</td>
-  </tr>
-</table>
-<p>Like other views in the Workbench, the CVS Repositories view has its own toolbar. 
-  Toolbar buttons are provided for refreshing the view, navigating and creating 
-  new repository locations. The toolbar also contains a drop-down menu that allows 
-  you to filter the view by working set.</p>
-       
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Home</h3>  
-<p class="Para">This command redraws the view, showing the repository locations as the roots 
-displayed by the view.</p>
-</div>
-     
-<div class="Topic">     
-<h3>Back</h3> 
-<p class="Para"> This command redraws the view, showing the roots that
- where displayed immediately prior to the previous issued Go Into command.</p>
-</div>
-     
-<div class="Topic">     
-<h3> Go Into</h3>  
-<p class="Para"> This command redraws the view, making the children of the  selected entry 
-the roots displayed by the view.</p>
-</div>
-     
-<div class="Topic">     
-<h3> Refresh View</h3>
-<p class="Para"> This command refreshes the contents of the Repositories view.</p>
-</div>
-     
-<div class="Topic">     
-<h3>Collapse All</h3>
-  <p class="Para"> This command collapses all expanded entries in the Repositories 
-    view.</p>
-</div>
-
-<div class="Topic">     
-<h3>Add CVS Repository</h3>
-  <p class="Para"> This command brings up the wizard to help you specify a new repository 
-  location.</p>
-</div>
-
-<h3 class="Para">Drop-Down Menu</h3>
-<p class="Para">The drop down menu in the title bar allows the repositories view 
-  to be filtered by a working set. It also allows to hide CVS modules defined in
-  the CVSROOT/modules file.</p>
-     
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the Repositories view you can  perform
-a number of interesting operations.</p>
-     
-<h3>New &gt; Repository Location&nbsp;</h3>
-     
-<p class="Para">This command brings up the wizard to help you specify a new repository 
-  location (same as Add CVS Repository toolbar item).</p>
-  
-  <h3>New &gt; Date Tag</h3>
-     
-<p class="Para">This command, available on the repository location and Date category 
-  entries, brings up the dialog which allows the specification of a date tag that 
-  is to be added to the Date category of the location entry in the Repositories 
-  view.</p>
-
-<h3>Check Out</h3>
-<p>This command checks the selected CVS modules out into projects in the Workbench 
-  with the same names as the remote modules (for remote modules that are folders 
-  on the server) or into projects with the name specified with the module (if 
-  the module is defined in the CVSROOT/modules file on the server).</p>
-     
-<h3>Check Out As...</h3>
-<p>This command open the Check Out wizard in order to allow the configuration of how the selected remote modules
-are checked out into the Workbench.</p>
-
-<h3>Tag as Version...</h3>  
-<p> This command versions the selected resource based on the current branch
- contents.</p>
-     
-<h3>Tag with Existing...</h3>  
-<p> This command versions the selected resource based on the current branch
- contents, moving the tag from previously tagged resources if required.</p>
-
-<h3> Compare</h3>   
-<p class="Para">This command will compare two selected resources.</p>
-
-<h3>Compare With...</h3>
-<p class="Para">This command will compare the selected folder with a branch or 
-version of the same folder.</p>
-
-<h3>Expand All</h3>
-<p class="Para">This command will fetch all of the subfolders of the selected item
-in one pass.</p>
-
-<h3>Refresh View</h3>
-<p class="Para">This command will refresh the repository folder tree.</p>
-
-<h3>Paste connection</h3>
-<p class="Para">Creates a new repository location based on the content of the clipboard. 
-There must a valid repository location string (eg. :pserver:dev.eclipse.org:/cvsroot/eclipse) 
-in the clipboard in order paste a new connection.</p>
-
-<h3>Copy to clipboard</h3>
-<p class="Para">Copies the identification string of the selected repository to the clipboard.</p>
-
-<h3>Discard Location</h3>
-<p class="Para">This command will remove the selected repository location. Note that
-all projects that were previously mapped to this repository must first be unmapped.</p>
-  
-<h3>Configure Branches and Versions</h3>
-<p class="Para"> This command brings up the wizard to help you discover the branch 
-  and version tags that exist in the repository for the selected folder so they 
-  can be added to the repositories view to allow the resources that have these 
-  tags can be browsed.</p>
-
-<h3>Refresh Branches...</h3>
-<p class="Para"> This command, available on repository location entries, allows 
-  you to refresh the list of known branches and versions that are displayed in 
-  the repositories view for selected projects. This operation makes use of the 
-  defined auto-refresh files for each project. If the operation fails for a particular 
-  project, use Configure Branches and Versions on the project to select one or 
-  more appropriate refresh files.</p>
-  
-<h3>Add to Branch List...</h3>
-<p> This command adds the selected project to the list of projects that are displayed 
-  under the specified branch in the repositories view. This command only modifies 
-  the repositories view and does not effect the repository in any way. If you 
-  want to add the project to a branch, you can perform a <strong>Tag with Existing</strong> 
-  after performing this operation.</p>
-  
-<h3> Open</h3>
-<p> This command opens the selected file in an editor.&nbsp; Since file revisions
-    in the repository are immutable, the editor opens in a read-only state,
- so it is not modifiable.&nbsp; </p>
-
-<h3> Show Annotation</h3>   
-<p> This command shows the contents of file with annotations identifying the author
-of each line of code in the file.</p>
-   
-<h3> Show History</h3>   
-<p> This command shows the revision history of the selected file in the History view.</p>
-     
-
-<h3>Properties</h3>   
-<p> Available on repository location entries, this command allows the modification 
-  of any of the properties of the location. It also allows the assignment of a 
-  display name and a server encoding which is used to translate file paths and 
-  commit comments between the client and server (but does not affect file contents).</p>
-
-      
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts">
-  <br>
-     <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-     <a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-     <a href="../concepts/concepts-27b.htm">Branches</a><br>
-     <a href="../concepts/concepts-27.htm">Versions</a><br>
-     <a href="../concepts/concepts-17a.htm">Local history</a></p>
-     
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks">
-  <br>
-     <a href="../tasks/tasks-92.htm">Creating a CVS repository location</a><br>
-     <a href="../tasks/tasks-94.htm">Discarding a CVS repository location</a><br>
-     <a href="../tasks/tasks-93.htm">Refreshing the CVS repositories view</a><br>
-     <a href="../tasks/tasks-95.htm">Changing the properties of a CVS Repository Location</a><br>
-     <a href="../tasks/tasks-96.htm">Checking out a project from a CVS repository</a><br>
-     <a href="../tasks/tasks-103.htm">Replacing resources in the Workbench</a><br>
-     <a href="../tasks/tasks-117.htm">Sharing a new project using CVS</a><br>
-     <a href="../tasks/tasks-119.htm">Viewing a file's revision history</a>
-   </p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference">
-  <br>
-     <a href="ref-47.htm">CVS</a><br>
-     <a href="ref-32a.htm">CVS Resource History View</a>
-   </p>
-      
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm
deleted file mode 100644
index 7e876ef..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-32a.htm
+++ /dev/null

@@ -1,234 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS History View</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> CVS History view</h1>
-    
-<p class="Intro"> This view provides a list of all the revisions of a resource in the repository as
-well as all the revisions of a resource in the local history. From this view you can compare revisions,
-load a revision, revert the corresponding workspace file to a revision, tag
-with an existing tag, show annotations and open an editor on a revision. </p>
- 
-<p class="Para">Here is what the CVS History View looks like:</p>
-   
-<p class="Para"><img
- src="../images/Image216_history_view.png"
- alt="CVS Resource History View"  border="0" align="top"> </p>
-
-<h2>Columns</h2>
-<p class="Para">The History View is able to display both local and remote revisions. Local History revisions have
-minimal information associated with them - only a time stamp. As a result, the majority of the column items will appear
-blank for Local History revisions. Remote revisions, on the other hand, will have a much more complete set
-of information. Here are the columns: </p>
-   
-<div class="Topic">    
-<h3> Revision</h3>
-<p class="Para"> Since the CVS History view can display both remote and local revisions.
-For remote revisions:
-</p>
-	<ul>
-		<li>the column displays the remote revision icon: 
-		<img
-	     src="../images/remote_history_mode.png"
-	     alt="Remote History Mode icon"  border="0" align="top"> </li>
-		<li>the column displays the revision number in the history. </li>
-	</ul>
-	
-	For local history revisions:
-	<ul>
-		<li>the column displays the local history revision icon: 
-		<img
-	     src="../images/local_history_mode.png"
-	     alt="Local History Mode icon"  border="0" align="top"> </li>
-	</ul>
-
-</div>
-   
-<div class="Topic">    
-<h3>Tags</h3>   
-<p class="Para">The tags that are associated with the revision. Selecting 
-a      revision line will list the tags in the lower left pane of the view. <i>(Remote revisions only)</i></p>
-</div>
-   
-<div class="Topic">  
-<h3> Revision Time</h3>   
-<p class="Para"> This column displays the creation date and time of the revision 
-     in the history.</p>
-</div>
-   
-<div class="Topic">       
-<h3> Author</h3>
-<p class="Para"> This column displays the name of the person who created and
-authored the version. <i>(Remote revisions only)</i></p>
-</div>
-   
-<div class="Topic">  
-<h3> Comment</h3>   
-<p class="Para"> This column displays the comment (if any) supplied for this 
-     revision at the time it was committed. Selecting a revision line will 
-show the complete comment in the lower right pane of the view. 
-Also, mousing over a dotted comment will result in showing a tooltip with complete comment. <i>(Remote revisions only)</i></p>
-</div>
-
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Refresh</h3>  
-<p class="Para">This command refreshes the contents of the view, 
-fetching the latest history information for the resource from the server.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Link with Editor and Selection</h3>  
-<p class="Para">When enabled, the view will display the history for the resource 
-of the active editor or of the active selection.</p>
-</div> 
-
-<div class="Topic"> 
-<h3>Pin</h3>  
-<p class="Para">When enabled will pin the view and its contents. Any new requests for history
-will open a new instance of the History View.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Navigation History</h3>  
-<p class="Para">When enabled will allow you to select from a drop down menu a 
-resource for which a history has been viewed in the past. The action is disabled 
-when the History view is opened for the first time.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Group Revisions by Date</h3>  
-<p class="Para">When enabled, all history items will be sorted into one of the following date
-categories: </p>
-<ul>
-<li>Today</li>
-<li>Yesterday</li>
-<li>This Month</li>
-<li>Previous</li>
-</ul>
-
-</div>
-
-<div class="Topic"> 
-<h3>Local and Remote Revisions</h3>  
-<p class="Para">When enabled will display both local and remote revisions of the resource in the
-History view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Local Revisions</h3>  
-<p class="Para">When enabled will display only the local revisions of the resource in the
-History view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Remote Revisions</h3>  
-<p class="Para">When enabled will display only the remote revisions of the resource in the
-History view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Collapse All</h3>  
-<p class="Para">Will the view is in the Group by Date mode, Collapse All will collapse all of the
-date categories.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Compare Mode</h3>  
-<p class="Para">When enabled, a double click (or a single click depending on your Open Mode strategy set
-in <b>Preferences&gt;General</b>) will open a compare editor. When it is disabled, clicking on a revision
-will open that revision.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Drop Down Menu</h3>  
-<p class="Para">The drop down menu contains the following items:</p>
-<ul>
-<li><b>Wrap Comments</b>: Will wrap comments in the Comment Viewer.</li>
-<li><b>Show Comment Viewer</b>: shows the Comment Viewer.</li>
-<li><b>Show Tag Viewer</b>: shows the Tag Viewer.</li>
-<li><b>Show Search Field</b>: shows the Search Field.</li>
-<li><b>Filter....</b>: Opens the Filter Dialog.</li>
-<li><b>Remove Filters</b>: Removes any filtering from the History View.</li>
-</ul>
-</div> 
-
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the CVS Resource History view you can  perform
-a number of interesting operations.</p>
-     
-<h3>Open</h3>   
-<p class="Para">This command will open the contents of the selected revision in a read only
-editor. (The editor used is the one that is registered as the default editor for the file type).
-<i>Note</i>: If the revision being opened is the current version of the file, then it will be opened
-in a regular editor.</p>
-
-<h3>Open With</h3>   
-<p class="Para">This menu allows choosing an editor to open the contents of the selected revision.
-<i>Note</i>: If the revision being opened is the current version of the file, then it will be opened
-in a regular editor, otherwise a read only editor is used.</p>
-
-<h3>Compare Current With Revision/Compare With Each Other</h3>   
-<p class="Para">The compare command differs based on the number of revisions selected in the 
-history view. For a single selection, <b>Compare Current With Revision</b> will the compare the
-current version of the resource with the selected revision. For two selections, <b>Compare with Each
-Other</b> will compare the selected revisions.</p>
-
-<h3>Get Contents</h3>   
-<p class="Para">This command will load the contents of the selected revision
-into the local copy of the file whose history
-is displayed in the view. The local file can then be committed to make
-the contents of latest revision in HEAD (or a branch) match the contents of
-the selected revision.</p>
-
-<h3>Get Sticky Revision</h3>   
-<p class="Para">This command will load the selected revision over the local 
-  file whose history is being displayed. This operation is rarely needed and is 
-  mainly used to change the tag on one or more resources. The loaded revision 
-  cannot be subsequently committed but can be tagged.</p>
-
-<h3>Tag with Existing...</h3>   
-<p class="Para">This command allows an existing tag to be moved to the
-selected file revision.</p>
-
-<h3> Show Annotation</h3>   
-<p> This command shows the contents of file with annotations identifying the author
-of each line of code in the file.</p>
-
-<h3>Refresh View</h3>   
-<p> This command refreshes the contents of the view.</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br>
-    <a href="ref-32.htm">CVS Repositories view</a>  </p>
-    
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
- <a href="../concepts/concepts-12.htm">Resources</a> <br>
- <a href="../concepts/concepts-27c.htm">CVS Repositories</a> <br>
- <a href="../concepts/concepts-17a.htm">Local history</a> </p>
-    
-
-    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm
deleted file mode 100644
index 1d64679..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-32b.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Console</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head"> CVS Console</h1>
-    
-<p class="Intro">The CVS Console is shown in the Workbench Console view. The CVS 
-  entry in this view shows the output from CVS commands. This output is similar 
-  to that of the CVS command line client. If an error occurs during a CVS operation 
-  opening the console can help troubleshoot the cause of the error.</p>
- 
-<p class="Para">Here is what the CVS Console in the Console view looks like:</p>
-<p class="Para"><img src="../images/cvs-console.png" alt="Console View" ></p>
-   
-<div class="Topic">
-<img border="0" src="../images/ngrelr.png" alt="Related reference"
- > <br>
-    <a href="ref-32.htm">CVS Repositories view</a>
-</div>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
-  <br>
- <a href="../concepts/concepts-12.htm">Resources</a> <br>
- <a href="../concepts/concepts-27c.htm">CVS Repositories</a> <br>
- <a href="../concepts/concepts-17a.htm">Local history</a> </p>
-    
-
-    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-33.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-33.htm
deleted file mode 100644
index 2fe25f4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-33.htm
+++ /dev/null

@@ -1,363 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-  <title>CVS Workspace Synchronization</title>
-</head>
-<body>
-
-<h1>CVS Workspace Synchronization</h1>
-
-<p>A CVS workspace synchronization launched using the <em class="UILabel">Team &gt; Synchronize</em>
-menu command or the <em class="UILabel">Synchronize</em> toolbar command in the Team Perspective will appear
-in the Synchronize view. This view allows you to inspect the differences between the local 
-Workbench resources and their remote counterparts as well as
-update resources in the Workbench 
-and commit resources from the Workbench to a repository.</p>
-   
-<p>Here is what the CVS Workspace Synchronization in the Synchronize view looks like:</p>
-<p>
-<img align="top" border="0" src="../images/Image245_sync_view.png" alt="CVS Workspace Synchronization" >
-</p>
-
-<h2>Features</h2>
-
-<p>The following is a brief summary of some of the features of the synchronize view.</p>
-
-<h3>Synchronization state</h3>
-
-  <p>The synchronize view shows the synchronization 
-    state of resources in your workspace compared to those in the repository. 
-    This state is shown by using icons and can also be configured to show the 
-    state as text appended to the resource name. A description of the icons is 
-    shown in the table below:</p>
-  <table width="100%" border="1">
-    <tr> 
-      <td width="9%" align="center"><img src="../images/r_inadd_ov.png" alt="Incoming addition icon" ></td>
-      <td width="91%">An incoming addition means that a resource has been added 
-        to the repository. <strong>Updating</strong> will transfer the resource 
-        to your workspace.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_inchg_ov.png" alt="Incoming change icon" ></td>
-      <td>An incoming change means that the file has changed in the repository. 
-        <strong>Updating</strong> will transfer the new file revision to your 
-        workspace.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_indel_ov.png" alt="Incoming deletion icon" ></td>
-      <td>An incoming deletion means that a resource was deleted from the server. 
-        <strong>Updating</strong> will delete your local resource.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_outadd_ov.png" alt="Outgoing addition icon" ></td>
-      <td>An outgoing addition means that the file was added to your workspace 
-        and is not yet in the repository. <strong>Adding</strong> then <strong>Committing</strong> 
-        will transfer the new file to the repository.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_outchg_ov.png" alt="Outgoing change icon" ></td>
-      <td>An outgoing change means that the file was change locally. <strong>Committing</strong> 
-        the file will transfer the changes to the repository and create a new 
-        revision of the file.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/r_outdel_ov.png" alt="Outgoing deletion icon" ></td>
-      <td>An outgoing deletion is a resource that has been deleted locally. <strong>Committing 
-        </strong>these resources will cause the remote resource to be deleted. 
-        <strong>Note</strong>: in CVS directories are never really deleted from 
-        the repository. Instead, files are deleted and empty directories are pruned 
-        from your workspace. </td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/confadd_ov.png" alt="Conflicting addition icon" ></td>
-      <td>A conflicting additions means that the resource has been added locally 
-        and remotely.</td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/confchg_ov.png" alt="Conflicting change icon" ></td>
-      
-    <td>A conflicting change means that the file has been changed locally and 
-      remotely. A manual or automatic merge will be required. Also, 
-      any entries in the view that contain children that are conflicts will also 
-      be decorated with the conflict icon. This is done to make conflicts easy 
-      to find. </td>
-    </tr>
-    <tr> 
-      <td align="center"><img src="../images/confdel_ov.png" alt="Conflicting deletion icon" ></td>
-      <td>A conflicting deletion means that the resource was deleted locally and 
-        remotely. </td>
-    </tr>
-  </table>
-
-<h3>Mode</h3>
-
-<p>The Synchronize view can be filtered using modes using either the toolbar actions or
-the menu items in the view's drop down menu. 
-Modes can be used to show only incoming, outgoing or conflicting changes.
-The advantages to modes are: </p>
-<ul>
-  <li>
-    They support and encourage the <a href="../concepts/concepts-26.htm#IdealWorkFlow"> ideal work flow.</a></li>
-  <li>
-    They reduce the amount of information you are faced with at any one time.</li>
-    <li> They provide a degree of safety restricting you to those operations appropriate 
-      to that mode. For example, you can't accidentally commit a conflict when 
-      in incoming mode.</li>
-</ul>
-     
-  <p> <b>Important</b>: It is preferable to update resources in the 
-    Workbench first, resolve any conflicts that exist by merging, then commit 
-    Workbench resources to the repository.</p>
-   
-<h3>Models</h3>
-<p> The Synchronize view is capable of displaying different model representations of the resources. Each product
-may contain its own product specific representations. The Eclipse SDK comes with three models:</p> 
-<ul>
-  <li><b>Workspace Model</b>: displays a resource based model. Layout options for this model can be controlled
-  from the Preferences dialog in the drop down menu. The layout options for the Workspace model are:<br>
-  <ul>
-	 <li>Flat layout shows all the out-of-sync resources as direct children of their project.</li>
-	  <li>Tree layout shows the resource hierarchy as it is shown in the 
-	    Project Explorer.</li>
-	  <li>Compress Folders shows changes grouped by project and then by folder. This 
-	    results in a hierarchy that is at most three levels deep with folder paths 
-	    being compressed into a single level (similar to a Java package).</li>
-  	</ul>
-  </li>
-  <li><b>Java Model</b>: displays a Java based model (similar to what appears in the Package Explorer).</li>
-  <li><b>Change Sets</b>: displays a Change Set based model. This model shows incoming 
-   	  changes grouped by commit 
-      comment which is handy for seeing who released what and why. For outgoing changes, 
-      you can create Change Sets for grouping related 
-      changes together. Grouping is performed using various commands in the context 
-      menu. </li>
-  </ul>
-  <p> In addition to to the models, there is also a <b>Flat Presentation</b> which 
-  displays all the out-of-sync elements as top level elements.</p>
-
-<h3>Navigation</h3>
-
-The Synchronize view provides toolbar actions for navigating through the changes in the view.
-These actions not only navigate between files but also go from change to change within a file.
-
-<h3>Update and Commit Operations</h3>
-
-<p> There are several flavours of update and commit operations available in the 
-  Synchronize view. You can perform the standard update and commit operation on 
-  all visible applicable changes or a selected subset. You can also choose to 
-  override and update, thus ignoring any local changes, or override and commit, 
-  thus making the remote resource match the contents of the local resource. You 
-  can also choose to clean the timestamps for files that have been modified locally 
-  (perhaps by an external build tool) but whose contents match that of the server.</p> 
-<h3>Conflict Handling</h3>
-
-<p> When dealing with conflicts, you can first perform an update and any conflicting 
-  changes The update operation will correctly update conflicts that are auto-mergeable 
-  (i.e. files content changes do not overlap) but will skip files that contain 
-  changes that overlap. Alternatively, conflicts can be handled using a Compare 
-  editor. A Compare editor can be opened by double-clicking (or single-clicking 
-  if you have change your open strategy in the preferences) on the conflict or 
-  by choosing <b>Open in Compare Editor</b> from the context menu. The Compare 
-  editor allows you to manually resolve the conflicts in the file. Once completed, 
-  perform a <b>Mark as Merged</b> on the conflict to indicate that you are done. 
-  This will change the conflict into an outgoing change.</p> 
-<h3>Problem Markers</h3>
-
-<p>
-The Synchronize view will show <i>error</i> or <i>warning</i> problem markers on any change that appears
-in the view or any folder or project that appears in the view that contains a resource that has such a problem
-marker. This is done to prevent resources with problems from getting committed to the repository.</p>
-
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Synchronize</h3>  
-  <p class="Para">This command allows you to repeat the current synchronization 
-    which refetches the remote state of the resources. The drop down of the toolbar 
-    item allows you to select other existing synchronizations or create new ones 
-    using the <b>Synchronize...</b> menu command.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Pin Current Synchronization</h3>  
-<p>This command allows you to pin or unpin the current synchronization.
-Pinned synchronizations will not be replaced by the next synchronization of the same type
-while unpinned synchronizations will be replaced.
-This allows you to keep a synchronization around for easy access. Such a synchronization 
-will automatically update when changes to Workbench resources take place and can be configured
-to perform scheduled refreshes in order to keep up-to-date with the remote state of the resources. </p>
-</div>
-
-<div class="Topic"> 
-<h3>Models drop down</h3>  
-<p>This drop down list presents the models that can be displayed in the Sync View.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Next Difference</h3>  
-<p>This command will go to the next difference displayed by the view. All the
-differences within a single file will be visited before opening the next file in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Previous Difference</h3>  
-<p>This command will go to the previous difference displayed by the view. All the
-differences within a single file will be visited before opening the previous file in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Collapse All</h3>  
-<p>Collapse all the expanded entries in the view.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Incoming Mode</h3>  
-<p>In this mode, only resources which have been changed in the repository 
-       since they were last loaded or synchronized with those in the Workbench 
-       (incoming changes) are visible.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Outgoing Mode</h3>  
-<p>In this mode, only resources which have been modified in the Workbench 
-       (outgoing changes) are visible.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Incoming/Outgoing Mode</h3>  
-<p> In this mode both incoming and outgoing changes are shown, and you can 
-      both update and commit. The advantage to using this dual mode is 
-      you can do either task as you choose. The disadvantage is that performing 
-      a simultaneous bi-directional merge is often complicated.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Conflicts Mode</h3>  
-  <p> In this mode only conflicts (resources modified both in the Workbench 
-    and in the repository) are shown.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Update All Incoming Changes</h3>  
-  <p>This command updates all the incoming changes visible in the view. 
-    The command will also update conflicts that are auto-mergeable but will skip 
-    files whose contents contain conflicts.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Commit All Outgoing Changes</h3>  
-  <p>This command commits all the outgoing changes visible in the view. 
-    Conflicts are not included in the commit.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Drop Down Menu</h3>  
-  <p>The drop down menu allows you to pin or remove the current or remove all 
-    synchronizations, change the mode or layout, restore removed from view 
-    items, configure the current synchronization to perform scheduled refreshes 
-    as well as set other view preferences.</p>
-</div>
-
-<h2>Context menu </h2>
-     
-<p>From the context menu of the Synchronize view you can  perform
-a number    of interesting operations.</p>
-     
-<h3>Open</h3>
-<p>This command open the local resource for the selected change in 
-the default Workbench editor for the file type.</p>
-
-<h3>Open With</h3>
-<p>This command allows you to open the local resource for the selected 
-  change in the a Workbench editor.</p>
-
-<h3>Open in Compare Editor</h3>
-<p>This command open the selected change in a Compare editor which allows 
-you to inspect the changes within the file.</p>
-
-<h3>Edit</h3>
-<p>This menu allows for renaming, deleting, moving or copying the resource.</p>
-
-<h3>Synchronize</h3>
-<p>This command refreshed the remote state of the selected resources.
-  In addition, this command will adjust the timestamps of outgoing changes whose 
-  contents already match the contents of the corresponding resource on the server 
-  so that the file is no longer an outgoing change. This is useful in situations 
-  where build tools regenerate files whose contents have not changed.</p>
-
-<h3>Remove From View</h3>
-<p>This command removes the selected resources from the view. The
-resources will only reappear if the state of the removed resources changes or the 
-Workbench is restarted or the <strong> Restore Removed Items </strong> action is
-invoked from the Drop Down menu.</p>
-
-<h3>Expand All</h3>
-<p >This command expands all of the selected resource's children.</p>
-
-<h3>Update</h3>
-<p>This command updates the selected resources. Conflicts can be 
-  included in an update but only auto-mergeable conflicts will be updated. Non-mergeable 
-  conflicts will be skipped and should be merged manually using a compare editor.</p>
-
-<h3>Commit</h3>
-<p>This command commits the selected resources. Only outgoing 
-changes can be committed.</p>
-
-<h3>Override and Update</h3>
-<p>This command operates on conflicts and outgoing changes
-and replaces the local contents of those resources with the contents 
-from the server.</p>
-
-<h3>Mark as Merged</h3>
-<p>This command adjusts the CVS timestamps of conflicting changes
-so they become outgoing changes. This command should be performed after
-conflicts are merged manually using a compare editor.</p>
-
-<h3>Add to .cvsignore</h3>
-<p>This command will add the selected resource to the .cvsignore list which will
- cause CVS to skip the resource during all CVS operations.</p>
-
-<h3>Create Patch</h3>
-<p>This command will bring up the Create Patch wizard and populate it with the selected
-resources.</p>
-
-<h3>Branch...</h3>
-<p>This command will create a new branch and a new branch tag which can be used to merge
-the branch back to the source branch.</p>
-
-<h3>Show Annotation</h3>
-<p>Depending on your Annotation preferences, this command will either bring up turn on the Quick Diff annotate
-or open the Annotate view for the selected resource.</p>
-
-<h3>Show in History</h3>
-<p>This command will show the history for the selected resource..</p>
-
-<h3>Change ASCII/Binary Property...</h3>
-<p>This command will open a dialog containing all of the selected resources. You can then
-alter the ASCII/Binary property for each resource.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts">
- <br>
-    <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-    <a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
- &nbsp;   </p>
-   
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="../tasks/tasks-113.htm">Updating</a><br>
-<a href="../tasks/tasks-113b.htm">Resolving conflicts</a><br>
-<a href="../tasks/tasks-100b.htm">Merging from a branch</a><br>
-<a href="../tasks/tasks-114.htm">Committing</a><br>
-<a href="../tasks/tasks-68.htm">Comparing resources</a><br>
-<a href="../tasks/tasks-68dg.htm">Merging changes in the compare editor</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="ref-25.htm">Compare editor</a>  </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm
deleted file mode 100644
index 205d65e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-33a.htm
+++ /dev/null

@@ -1,137 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Merge Synchronization</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-<h1>CVS Merge Synchronization</h1>
-<p class="Para">CVS Merge synchronizations launched using the <b>Team &gt; Merge</b> 
-  menu command will appear in the Synchronize view. This view allows you to inspect 
-  the differences between the local Workbench resources and their remote counterparts 
-  that are being merged and allows you to update the local resources. Committing 
-  is not supported when merging.</p>
-   
-<p class="Para"> Here is what the CVS Merge Synchronization in the Synchronize view looks like:</p>
-   
-<p class="Para"> <img src="../images/cvs-merge-sync.png"  align="top" border="0" alt="CVS Merge Synchronization">
-
- </p>
-
-<h2>Features</h2>
-
-<p class="Para"> 
-The features of the CVS Merge Synchronization are similar to those of the 
-<a href="ref-33.htm">CVS Workspace Synchronization</a> with the following
-differences.
-</p>
-
-<ul>
-<li><b>Modes:</b>
-When merging, only incoming and conflicting changes are possible. 
-As such, only the Incoming Mode and Conflicts mode are supported.</li>
-
-  <li><b>Operations:</b> Only updating is supported when merging.</li>
-  <li><b>Ongoing merges:</b> In order to compensate for the poor ongoing merge 
-support of CVS, a CVS Merge Synchronization can be pinned and kept indefinitely.
-The timestamps of merged changes are recorded and, on refresh, only new changes since the last
-merge are shown in the view.</li>
-</ul>
-
-<h2>Toolbar</h2>
-
-<p>The Toolbar buttons are the exact same as in the <a href="ref-33.htm">CVS Workspace Synchronization</a>,
-with the omission of an Outgoing mode and Both mode buttons.</p> 
-
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the Synchronize view you can  perform
-a number of interesting operations.</p>
-        
-<h3>Open</h3>
-<p class="Para">This command open the local resource for the selected change in 
-the default Workbench editor for the file type.</p>
-
-<h3>Open With</h3>
-<p class="Para">This command allows you to open the local resource for the selected 
-  change in the a Workbench editor.</p>
-
-<h3>Open in Compare Editor</h3>
-<p class="Para">This command open the selected change in a Compare editor which allows 
-you to inspect the changes within the file.</p>
-
-<h3>Synchronize</h3>
-<p class="Para">This command refreshed the remote state of the selected resources.
-  In addition, this command will adjust the timestamps of outgoing changes whose 
-  contents already match the contents of the corresponding resource on the server 
-  so that the file is no longer an outgoing change. This is useful in situations 
-  where build tools regenerate files whose contents have not changed.</p>
-
-<h3>Remove From View</h3>
-<p class="Para">This command removes the selected resources from the view. The
-resources will only reappear if the state of the removed resources changes or the 
-Workbench is restarted.</p>
-
-<h3>Expand All</h3>
-<p class="Para">This command expands all of the selected resource's children.</p>
-
-<h3>Merge</h3>
-<p class="Para">This command updates the selected resources. Conflicts can be 
-  included in an update but only auto-mergeable conflicts will be updated. Non-mergeable 
-  conflicts will be skipped and should be merged manually using a compare editor.</p>
-
-<h3>Overwrite</h3>
-<p class="Para">This command operates on conflicts
-and replaces the local contents of those resources with the contents 
-from the server.</p>
-
-<h3>Mark as Merged</h3>
-<p class="Para">This command adjusts the CVS timestamps of conflicting changes
-so they become outgoing changes. This command should be performed after
-conflicts are merged manually using a compare editor.</p>
-
-<h3>Show Annotation</h3>
-<p class="Para">Depending on your Annotation preferences, this command will either bring up turn on the Quick Diff annotate
-or open the Annotate view for the selected resource.</p>
-
-<h3>Show in History</h3>
-<p class="Para">This command will show the history for the selected resource..</p>
-
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- >
- <br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
- </p>
-   
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"
- >
-<br><a href="../tasks/tasks-113b.htm">Resolving conflicts</a><br>
-<a href="../tasks/tasks-100b.htm">Merging from a branch</a><br>
-<a href="../tasks/tasks-68.htm">Comparing resources</a><br>
-<a href="../tasks/tasks-68dg.htm">Merging changes in the compare editor</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br><a href="../reference/ref-47.htm">CVS</a>
- <br><a href="ref-41a.htm">Merge wizard</a>
- <br><a href="ref-33.htm">CVS Workspace Synchronization</a>
- <br><a href="ref-25.htm">Compare editor</a>
- </p>
-
-
-   
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-35.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-35.htm
deleted file mode 100644
index d91d2cc..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-35.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Quick Diff Preference Page</title>
-   
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-
-<h1 class="Head">Quick Diff Preference Page</h1>
-<div class="Para"></div>
-
-<div class="Para">
-  <p>The following preferences can be changed on the
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.QuickDiff)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Editors &gt; Text Editors &gt; Quick Diff</strong></a>
-  
-  preference page.</p>
-</div>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Enable quick 
-          diff<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option will enable 
-          or disable the quick diff option.</div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show differences in overview 
-        ruler<br> </td>
-      <td style="vertical-align: top;">
-        This option will show differences in the overview ruler.</td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Colors - Changes<br>
-        </div></td>
-      <td align="left" valign="top">This option controls the color of changes. 
-      </td>
-      <td align="left" valign="top">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Colors - Additions<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls the 
-          color of additions. <br>
-        </div></td>
-      <td align="left" valign="top"> <br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Colors - Deletions<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls the 
-          color of deletions. <br></div></td>
-      <td align="left" valign="top"> <br></td>
-    </tr>
-     <tr> 
-      <td style="vertical-align: top; width: 25%;">Use this reference source<br> </td>
-      <td style="vertical-align: top;">
-        This option sets which reference to use as the base for generating quick diff comparisons. Options are: 
-      <ul>
-        <li><STRONG>Version on Disk: </STRONG>Current file is compared against the last saved version on disk.</li>
-        <li><strong>Latest CVS Revision: </strong>Current file is compared against the latest CVS revision for the file.</li>
-      </ul></td>
-      <td style="vertical-align: top;">Version on Disk<br> </td>
-    </tr>
-  </tbody>
-</table>
-
-<p></p>
-<p>Here is what the Quick Diff preference page looks like: </p>
-<p><img src="../images/ref-quickdiffpref.png" alt="Image of the Quick Diff preference page"><br>
-</p>
-<p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-36.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-36.htm
deleted file mode 100644
index 6ef96c5..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-36.htm
+++ /dev/null

@@ -1,143 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Spelling preference page</title>
-   
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-<h1 class="Head">Spelling Preference Page</h1>
-<div class="Para">
-  <p>The following preferences can be changed on the
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Spelling)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Editors &gt; Text Editors &gt; Spelling</strong></a>
-  
-  preference page.</p>
-</div>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Enable spell 
-          checking<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option enables spell 
-          checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Ignore words with digits <br> 
-      </td>
-      <td style="vertical-align: top;">This option ignores words with digits when 
-        performing spell checking.<br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Ignore mixed 
-          case words <br>
-        </div></td>
-      <td align="left" valign="top">This option ignores mixed case words when 
-        performing spell checking. </td>
-      <td align="left" valign="top">On<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Ignore sentence 
-          capitalization<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores sentence 
-          capitalization when performing spell checking. <br>
-        </div></td>
-      <td align="left" valign="top">On<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Ignore upper 
-          case words<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores upper 
-          case words when performing spell checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Ignore internet addresses<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores internet 
-          addresses when performing spell checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Ignore non-letters at word boundaries<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores non-letters 
-          at word boundaries when performing spell checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Ignore single letters<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores single 
-          letters when performing spell checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Ignore Java string literals<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores 
-          Java string literals when performing spell checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Ignore '&amp;' in Java properties files<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option ignores '&amp;' 
-          in Java properties files when performing spell checking. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Platform dictionary<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option selects a platform
-	 dictionary to use. </div></td>
-      <td align="left" valign="top"> <div class="Para">English (United States)</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">User defined dictionary<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option selects a User defined
-	 dictionary to use. </div></td>
-      <td align="left" valign="top"> <div class="Para">-</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Encoding<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option selects which encoding to use for reading the dictonaries. </div></td>
-      <td align="left" valign="top"> <div class="Para">Default (depends on Platform)</div></td>
-    </tr>
-    <tr>
-      <td align="left" valign="top"> <div class="Para">Maximum number of correction proposals<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option limits the possible corrections 
-	 displayed to the given value. </div></td>
-      <td align="left" valign="top"> <div class="Para">20</div></td>
-    </tr>
-  </tbody>
-</table>
-
-<p></p>
-<p>Here is what the Spelling preference page looks like: </p>
-<p><img src="../images/ref-spellingpref.png" alt="Image of the Spelling preference page"><br>
-  &nbsp;<br>
-</p>
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-37.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-37.htm
deleted file mode 100644
index 8f1444b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-37.htm
+++ /dev/null

@@ -1,121 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-   <title>New Project wizard</title>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body bgcolor="#FFFFFF">
-
-<h1 CLASS="Head">
-New Project wizard</h1>
-
-<div CLASS="Intro">This wizard helps you create a new project in the Workbench.</div>
-
-
-<p CLASS="Para">When you first bring up the New Project wizard, you need to select 
-  the type of project you want to create.&nbsp; Select the General type if you 
-  want to create a generic project. To assist in locating a particular wizard, 
-  the text field can be used to show only the wizards that match the entered text. </p>
-
-<p CLASS="Para"><img src="../images/Image247_projsel_wiz.png" alt="New project wizard" border="0" ></p> 
-<div CLASS="Topic">
-<h2>
-Create a New Project Resource Page</h2>
-When you select Next, you will be presented with the New Project Resource
-Page, containing the following edit fields:
-<br>&nbsp;
-<table BORDER CELLSPACING=0 >
-<tr>
-<th>
-<div CLASS="Para">Field</div>
-</th>
-
-<th>
-<div CLASS="Para">Description</div>
-</th>
-
-<th>
-<div CLASS="Para">Default</div>
-</th>
-</tr>
-
-<tr>
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">Project Name</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">The name of the new project to be created.</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">&lt;blank&gt;</div>
-</td>
-</tr>
-
-<tr>
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">Location</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">The location in the file system where the project will
-be created. De-select "Use default location" to specify a location other
-than the default.&nbsp; You can type the new location or browse to select
-a file system location for the new project.</div>
-</td>
-
-<td ALIGN=LEFT VALIGN=TOP>
-<div CLASS="Para">The workspace root directory</div>
-</td>
-</tr>
-</table>
-
-
-  <p CLASS="Para">After you indicate a name and location for the project, you 
-    can either click <strong>Finish </strong>to create the project, or you can 
-    click <strong>Next </strong>to set up project dependencies on the Select Referenced 
-    Projects page.</p> 
-  <p CLASS="Para">Here is what the New Project Resource page looks like:</p>
-
-  <p CLASS="Para"><img src="../images/Image251_proj_wiz.png" alt="New project name and location page" border="0" ></p></div>
-
-<div CLASS="Topic">
-<h2>
-Select Referenced Projects page</h2>
-
-<div CLASS="Para">In the Referenced Projects list, you can set project
-dependencies for the new project. In the list of other projects in the
-Workbench, you can select one or more projects on which you want the new
-project to depend.&nbsp; Initially, no projects will be selected.</div>
-
-
-  <p CLASS="Para">Click <strong>Finish</strong> when you are done to create the 
-    new project in the Workbench.</p> 
-  <p CLASS="Para">Here is what the Select Referenced Projects page looks
-like:</p>
-
-  <p CLASS="Para"><img src="../images/Image252_projref_page.png" alt="Project references page" border="0" ></p></div>
-
-<div CLASS="Topic">
-<h2>
-New Project perspective options</h2>
-
-  <div CLASS="Para">On the preferences page (<strong>Window &gt; Preferences &gt; General 
-    &gt; Perspectives</strong>), you can change the way that new projects are initially 
-    displayed. For details on how to change this option see <a href="ref-10.htm">Workbench</a>.</div>
-</div>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-27.htm">Project Explorer View</a>
-</p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-38.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-38.htm
deleted file mode 100644
index 134e0c1..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-38.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New Folder wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-New Folder wizard</H1>
-<P CLASS="Para">
-This wizard helps you create a new folder in the Workbench.</P>
-<P CLASS="Para">
-Here is what the New Folder wizard looks like:</P>
-<P CLASS="Para"> <img src="../images/Image248_folder_wiz.png" alt="New folder wizard" border="0" ></P>
-<P CLASS="Para">&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-New Folder Fields</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Field</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Enter or select the parent folder</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource in which the new folder will be created. Type or navigate the list to
-select the resource.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource that was selected when you chose to create the new folder</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Folder name</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name for the new folder.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<H2>Advanced</H2>
-<P>The <B>Advanced</B> button reveals or hides a section of the wizard used 
-to create a linked folder. Check the <B>Link to folder in the file system</B> 
-checkbox if you want the new folder to reference a folder in the file
-system. Use the field below the checkbox to enter a folder path or the
-name of a path variable. Use the <B>Browse...</B> button to browse for a folder 
-in the file system. Use the <B>Variables...</B> button if you want to use a path 
-variable to reference a file system folder.</P>
-
-<P><IMG border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><A href="../concepts/concepts-13.htm">Linked resources</A>
-<br><A href="../concepts/cpathvars.htm">Path variables</A>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-43.htm">Creating a folder</a>
-<br><a href="../tasks/tasks-45.htm">Creating linked resources</a>
-</P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-27.htm">Project Explorer View</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-39.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-39.htm
deleted file mode 100644
index 802770a..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-39.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>New File wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-New File wizard</H1>
-<P CLASS="Para">
-This wizard helps you create a new file in the Workbench.</P>
-<P CLASS="Para">
-Here is what the New File wizard looks like:</P>
-<P CLASS="Para"> <img src="../images/Image246_file_wiz.png" alt="New file dialog" border="0" ></P>
-<P CLASS="Para">&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-New File Fields</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Field</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Enter or select the parent folder</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource in which the new file will be created. Type or browse the list to select the resource.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The resource that was selected when you invoked the New File wizard.</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">File name</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name for the new file, including the file extension.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<H2>Advanced</H2>
-<P>The <B>Advanced</B> button reveals or hides a section of the wizard used 
-to create a linked file. Check the <B>Link to file in the file system</B> checkbox if 
-you want the new file to reference a file in the file system. Use the field below the 
-checkbox to enter a file path or the name of a path variable. Use the 
-<B>Browse...</B> button to browse for a file in the file system. Use the 
-<B>Variables...</B> button if you want to use a path variable to reference a file system file.</P>
-
-<P><IMG border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br>
-<A href="../concepts/concepts-13.htm">Linked resources</A>
-<br>
-<A href="../concepts/cpathvars.htm">Path variables</A>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-44.htm">Creating a file</a>
-<br><a href="../tasks/tasks-45.htm">Creating linked resources</a>
-</P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-27.htm">Project Explorer View</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm
deleted file mode 100644
index 49eb5e5..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-39a.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS Wizards</title>
-
-</HEAD>
-<body>
-<H1 CLASS="Head">
-CVS Wizards</H1>
-
-<P>There are several CVS specific wizards. These include the Import CVS Project 
-  wizard (which is also available from the New Project wizard) and the New CVS 
-  Repository Location wizard. There are also wizards for several CVS operations, 
-  such as committing and merging.</p>
-<P>  See Team Support in the
-Reference section for details on these wizards.
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
-  <br>
-  <a href="ref-40a.htm">CVS Checkout wizard</a><br>
-     <a href="ref-40.htm">New CVS Repository Location wizard</a><br>
-     <a href="ref-41a.htm">Merge wizard</a>
-     
-   </p>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm
deleted file mode 100644
index 3ac162b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-3a.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Fast View bar</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Fast View Bar</H1>
-<P class="Intro"> The fast view bar is the place where fast views are docked. 
-  It may be docked on any side of the workbench. </p>
-<p>Here is an example of what a fast view bars looks like:&nbsp;</P> 
-<P CLASS="Para">
-<img src="../images/Image211_fastview.png" alt="Fast View Bar" border="0"></P>
-<P CLASS="Para">
-By default the fast view bar is always visible. You can use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Perspectives</b></a>
-  preference page to hide the fast view bar if it is empty.</P>
-<DIV CLASS="Topic">
-<h3>
-View Buttons</h3>
-<P CLASS="Para">
-These buttons provide a quick way to display the
-fast views in the current perspective.&nbsp; Fast views are essentially
-minimized views that have been dragged onto the shortcut bar.&nbsp; Fast views
-pop up when selected, and revert back to their minimized state when you click 
-outside of the view.  They may be oriented either horizontally or vertically according to their configuration.
-To convert a fast view back into a normal view, click <b>Fast View</b> 
-in the view's menu or drag it back to the workbench. To add a view to the fast view bar you can:</P>
-<ul>
-<li>Click the button on the left of the fast view bar. This will open a menu containing the views appropriate to the current perspective.</li>
-<li>Right click the view in the workbench and select <b>Fast View</b>.</li>
-<li>Drag the view from the workbench to the Fast View bar.</li>
-</ul>
-</DIV>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" > <br>
-  <a href="ref-4.htm">View Toolbars</a> <br>
-  <a href="ref-23.htm">Workbench Window Layout</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-4.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-4.htm
deleted file mode 100644
index 84d16fd..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-4.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>View toolbars</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-View toolbars</H1>
-<P CLASS="Para">
-View toolbars contain actions that apply only to the particular view in which they appear.&nbsp;
-The view toolbar also contains a context menu that contains other actions for that view.
-This menu is opened by clicking on the
-downwards pointing triangle.&nbsp;If there is enough space, view toolbars are in the view tab area.  Otherwise they appear in the view.</P>
-<P CLASS="Para">
-Here is an example of the view toolbar for the Properties view:</P>
-<P CLASS="Para">
-<img src="../images/Image215_toolbar_view.png" alt="Properties View Tool Bar" border="0" ></P>
-
-<h2>
-Title Bar</h2>
-<P CLASS="Para">
-View title bars contain the view name, its icon, and
-the view toolbar. </P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-3.htm">Shortcut Bar</a>
-<br><a href="ref-2.htm">Workbench Toolbar</a>
-<br><a href="ref-23.htm">Workbench Window Layout</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-40.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-40.htm
deleted file mode 100644
index 4a7389d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-40.htm
+++ /dev/null

@@ -1,153 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Add CVS Repository wizard</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head">Add CVS Repository wizard</h1>
-   
-<p class="Para"> This wizard helps you create a repository location.</p>
-   
-<p class="Para"> Here is what the New CVS Repository Location wizard looks 
-like:</p>
-   
-<p class="Para"> <img align="top" border="0"
- src="../images/Image249_repo_wiz.png" alt="Repositories View" >
- </p>
-   
-<div class="Topic">  
-<h2 class="Head">Fields</h2>
-   
-<p class="Head"> The following are the editable fields for a new CVS repository 
-location:</p>
-     
-<table border="1" cellspacing="0" cellpadding="3">
-      <thead>      <tr>
-         <th rowspan="1" colspan="1">               
-    <p class="Para"> Option</p>
-        </th>
-        <th rowspan="1" colspan="1">               
-    <p class="Para"> Description</p>
-        </th>
-        <th rowspan="1" colspan="1">               
-    <p class="Para"> Default</p>
-        </th>
-      </tr>
-      </thead> <tbody>
-       <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       Host
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     	The address of the host (e.g., "hostmachine.com").
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-      &lt;blank&gt;
-        </td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       Repository Path
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     	The path to the repository on the host (e.g., "/x/y/z",&nbsp; 
-           "d:/myrepo").
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     	&lt;blank&gt;
-        </td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       	User Name
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-		The user name under which you want to connect to the 
-           server.
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-	    &lt;blank&gt;
-        </td>
-      </tr>
-      <tr>
-        <td colspan="1" valign="top" align="left">Password</td>
-        <td colspan="1" valign="top" align="left">The password required for 
-the          above user name to access the above host.</td>
-        <td colspan="1" valign="top" align="left">&lt;blank&gt;</td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-		 Connection Type
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-		The type of CVS connection for the repository, either 
-           "pserver", "extssh", "pserverssh2" or "ext".
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-		pserver
-        </td>
-      </tr>
-      <tr>
-         <td colspan="1" valign="top" align="left">Port</td>
-        <td colspan="1" valign="top" align="left">Option to use a custom
-port for          the connection.</td>
-        <td colspan="1" valign="top" align="left">Use Default Port</td>
-      </tr>
-      <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-		Validate connection on finish
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     
-    Check this option if you want to attempt a connection 
-           to the host upon completion of the wizard to validate that the 
-entered            information is correct.&nbsp; If this option is not enabled, 
-you will            not know whether the information entered is correct until 
-you try to            access the contents of a repository for the first time. 
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     
-      <p class="Para">On</p>
-        </td>
-      </tr>
-         
-       <tr>
-         <td rowspan="1" colspan="1" valign="top" align="left">         
-       	Save Password
-        </td>
-        <td rowspan="1" colspan="1" valign="top" align="left">Check this option 
-          if you want the password to be saved between sessions. To persist 
-          login credentials in a safe, encrypted form 
-          <a href="../reference/ref-securestorage-start.htm">Secure Storage</a> 
-          is used.</td>
-        <td rowspan="1" colspan="1" valign="top" align="left">           
-     
-      <p class="Para">Off</p>
-        </td>
-      </tr>
-      
-  </tbody>     
-</table>
-    <img border="0" src="../images/ngrelr.png" alt="Related reference">
- <br>
-    <a href="ref-32.htm">CVS Repositories View</a><br> 
-    <a href="../reference/ref-securestorage-start.htm">Secure Storage</a><br>
-	<a href="../reference/ref-securestorage-prefs.htm">Secure storage preference page</a></div>
-    
-
-    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm
deleted file mode 100644
index 2986527..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-40a.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Checkout wizard</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head">CVS Checkout wizard</h1>
-   
-<p class="Para"> This wizard helps you check out one or more projects from a CVS repository.
-It is available from the Import menu, the New &gt; Project menu and the toolbar of the CVS
-Repository Exploring perspective. It is also opened when performing a Checkout As from the
-CVS Repositories view.</p>
-   
-<p class="Para">The first page of the checkout wizard allows you to choose an existing repository
-location or create a new one. If you choose to create a new location, the page from the 
-<a href="ref-40.htm">New Repository Location wizard</a> is shown.</p>
-   
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout1.png" alt="CVS Checkout wizard" >
-</p>
-
-<p class="Para"> After a repository location is selected, you can now choose one 
-  or more modules to check out. You can either enter a module path or select one 
-  or more from the list of existing modules. A dot (.) can be entered to checkout 
-  the entire contents of the repository for those rare cases where the repository 
-  represents a single project. </p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout2.png" alt="CVS Checkout wizard" >
-</p>
-
-<p class="Para"> Once one or more modules are selected, you can choose to check 
-  out one or more selected modules as a new projects or into an existing project 
-  or folder. If one module is selected and it does not contain a .project file 
-  (the Workbench project configuration file), you will also have the option to 
-  configure the project using the new project wizard (in order to make the project 
-  a Java project, for instance). The option to check out subfolders is selected by default. 
-  Also, you are given the option to add the checked out modules to a working set.</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout3.png" alt="CVS Checkout wizard" >
-</p> 
-
-<p class="Para">
-For a single project, you can configure the location of the project to be either
-the default location or a custom location outside the workspace. For multiple
-projects, you can configure the parent folder where all the projects should be
-located.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout4.png" alt="CVS Checkout wizard" >
-</p> 
-
-<p class="Para">
-Finally, you can choose the tag to be used for the check out.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-checkout5.png" alt="CVS Checkout wizard" >
-</p> 
-   
-<img border="0" src="../images/ngrelr.png" alt="Related reference">
- <br><a href="ref-32.htm">CVS Repositories View</a>
- <br><a href="ref-40.htm">Add CVS Repository wizard</a> 
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm
deleted file mode 100644
index 9037ee6..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-40b.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-     
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-     
-  <meta http-equiv="Content-Style-Type" content="text/css">
-      
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>CVS Sharing wizard</title>
-   
-</head>
- <body style="background-color: rgb(255,255,255);">
-   
-<h1 class="Head">CVS Sharing wizard</h1>
-   
-<p class="Para"> This wizard helps you share a project with others using a CVS 
-  repository. It is available from the <strong>Team &gt; Share Project </strong>menu 
-  command of views that display resources such as one of the navigation views 
-  and the Java Packages Explorer.</p>
-   
-<p class="Para">The first page of the Sharing wizard allows you to choose the type of
-repository you would like to share you project with. If the repository type
-you wish to share with is not listed, you can click the Show All Wizards checkbox
-to see repository types that are installed but not enabled.</p>
-   
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share1.png" alt="Sharing wizard" >
-</p>
-
-<p class="Para">
-Selecting CVS will bring you to the CVS Sharing wizard. On the first page of the
-CVS wizard, you can select the repository you wish to share with. If the repository
-is not in the list, you can select to create a new repository.
-If you choose to create a new location, the page from the 
-<a href="ref-40.htm">New Repository Location wizard</a> is shown.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share2.png" alt="CVS Sharing wizard" >
-</p>
-
-<p class="Para">
-After you have selected the repository, you must indicate the name of the module
-that will be used to share the project. You can choose to use the same name
-as the local project or you can type in a path containing one or more folder segments
-indicating the remote module. There is also an option to reconnect the local project to an existing
-module.
-</p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share3.png" alt="CVS Sharing wizard" >
-</p>
-
-<p class="Para"> The final page of the CVS Sharing wizard allows you to decide 
-  which resources to commit and which to ignore. There are toolbar items for changing 
-  the layout of the view and for committing and ignoring resources. If there are 
-  resources left in the view when Finish is pressed, you will be prompted to commit 
-  the remaining resources in the background (if the <em>Launch the Commit Wizard</em> 
-  option is enabled) which will allow you to return to work while the commit takes 
-  place. </p>
-
-<p class="Para"> <img align="top" border="0"
- src="../images/cvs-share4.png" alt="CVS Sharing wizard" >
-</p>
-
-<img border="0" src="../images/ngrelr.png" alt="Related reference">
- <br><a href="ref-40.htm">Add CVS Repository wizard</a>    
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm
deleted file mode 100644
index b5ab3e7..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-41a.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Merge wizard</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Merge wizard</H1>
-<P CLASS="Intro"> This wizard helps you merge changes between two states of a 
-  project into your workspace. Often the Merge Wizard is used to move changes 
-  from one branch into another, for example after splitting a branch to work on 
-  a bug fix. The merge operation takes changes between two points in a branch, 
-  the <b> start point</b> and the <b> end point</b>, and merges them into your 
-  workspace. Typically the start point will be the root of a branch (version tag) 
-  and the end point can either be the tip (latest and best) of the branch 
-  or another version tag.<br>
-  <br>
-  It is very important to understand that the destination of the merge is always 
-  the project in your workspace. After the merge has been completed you can test the 
-  changes locally and then commit them to the new branch (usually HEAD).</p>
-<P CLASS="Intro">To start a merge, select a project (or one or more resources), 
-  and select <b>Team &gt; Merge...</b> from the pop-up menu. The following dialog 
-  will appear.</p>
-<P><img src="../images/Image269_merge_init.png" alt="Merge dialog initial state" border="0" > 
-</P>
-
-
-<p>First, you should choose the end tag of the merge. This is the branch or version 
-  being merged into the workspace. Choose a version when you want to merge the 
-  differences between two versions of a project into your workspace. Choose a 
-  branch if you want to merge the changes made in the branch into your local workspace.</p>
-<p>The wizard will try to pick an appropriate tag for the start tag or base tag. 
-  If one cannot be determined, you should enter it manually. If there is no start 
-  tag, you can choose to merge without a preview, in which case a start tag is 
-  not required but the merge will happen directly into the workspace. The drawback 
-  of this is that CVS uses a text base markup to identify conflicts and this is 
-  cumbersome to work with.</p>
-
-
-<P>If the merge preview option is selected, after the finish button is pressed, 
-  the changes between the start point and end point are calculated and displayed 
-  as a <a href="ref-33a.htm">CVS Merge Synchronization</a> in the Synchronize 
-  view. Depending on the size of the project you are merging, this may take some 
-  time but can be run in the background. In the Synchronize view you can update 
-  or merge changes into your Workbench. Also, you have the option to automatically 
-  merge non-conflicting changes which means you will only need to deal with the conflicting changes in
-  the Synchronize view.</P>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-<br><a href="../concepts/concepts-27b.htm">Branches</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-100a.htm">Branching</a>
-<br><a href="../tasks/tasks-100b.htm">Merging from a branch</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br><a href="../reference/ref-47.htm">CVS</a>
-  <br><a href="ref-33a.htm">CVS Merge Synchronization</a>  
- <br><a href="ref-25.htm">Compare editor</a>  
- </p>
-    
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-42.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-42.htm
deleted file mode 100644
index 415a298..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-42.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Web Browser preferences</title>
-</head>
-<body>
-
-<h1>Web Browser preferences</h1>
-
-<div class="Para"> 
-  <p>The following preferences can be changed on the
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.browser.preferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Web Browser</strong></a>
-  
-  preference page.</p>
-</div>
-
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top" width="25%"> <div class="Para">Use internal 
-          Web browser<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option enables you 
-          to use an internal Web browser. </div></td>
-      <td align="left" valign="top"> <div class="Para">On</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Use external Web browser<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option enables you 
-          to use an external Web browser. Select the required browser from the 
-          list of available external web browsers.</div></td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-  </tbody>
-</table>
-<p></p>
-<p>Here is what the Web Browser preference page looks like: </p>
-<p><img src="../images/ref-webbrowserpref.png" alt="Image of the Web Browser preference page"><br>
-</p>
-<p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-43.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-43.htm
deleted file mode 100644
index e90e65e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-43.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Workbench User Guide</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Workbench User Guide</H1>
-<P CLASS="Para">
-The Help view displays help related to using the Workbench. If you select Workbench
-User Guide in the list of books displayed in the Help window, you will see help
-topics related to using the Workbench in the Contents tab. The Workbench User Guide
-is broken down into four main sections, described below.</P>
-<DIV CLASS="Topic">
-
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Getting started</H2>
-<P CLASS="Para">
-This section contains tutorials that will help you
-when you start using the Workbench.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Concepts</H2>
-<P CLASS="Para">
-Concepts are high level descriptions of the schema
-and functions of the Workbench.&nbsp; This section helps provide a general
-understanding of how the Workbench functions.&nbsp; For example, the Concepts section includes a discussion of what perspectives and views are and how they relate to one another.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Tasks</H2>
-<P CLASS="Para">
-Task descriptions are step by step instructions for
-performing specific actions and tasks in the Workbench. For example, the Tasks section contains step by step instructions for
-creating a repository location, and for importing a file from the file system into the Workbench.</P>
-</DIV>
-<DIV CLASS="Subtopic">
-<H2 CLASS="Head">
-Reference</H2>
-<P CLASS="Para">
-Reference materials are helpful resources that will assist you while you are using the Workbench. This includes descriptions of various wizards, dialogs, and fields as well as Workbench resources such as specific views and perspectives.</P>
-<P CLASS="Para">
-The Reference section also includes a glossary of terms that you might find useful while using the Workbench.</P>
-</DIV>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-45.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-45.htm
deleted file mode 100644
index aa89c34..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-45.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>File search</title></head>
-
-<body>
-
-<h1>File search</h1>
-
-<p>
-In the Search Dialog, the File Search tab allows you to search for files or text in the Workbench.
-You can bring up the Search Dialog by clicking on the Search toolbar button.</p>
-
-<p>
-<img src="../images/Image45_file_search.png"  alt="File search dialog" border="0"></p>
-
-<h2>Containing text</h2>
-<p>Type the expression for which you wish to do the text search. Leave this field empty to search for files.&nbsp;</p>
-
-<p>From the drop-down menu, you can choose to repeat or
-modify a recent search.</p>
-
-<h3>Wildcards</h3>
-<p>The available wildcards for search expressions are displayed in the search dialog:</p>
-
-<ul>
-	<li>"*" matches any set of characters, including the empty string</li>
-	<li>"?" matches for any character</li>
-	<li> "\" is the escape for a literal; if you want to search for an asterisk, question mark, or backslash character, type a backslash before it to indicate that you are not using these characters as wildcards (e.g., "\*", "\?", or "\\")</li>
-</ul>
-
-<h2>File name patterns</h2>
-<p>In this field, enter all the file name patterns for the files to find or search
-through for the specified expression.<br>
-</p>
-
-<h3>Wildcards</h3>
-<p>The available wildcards for file name patterns are displayed in the search dialog:</p>
-<ul>
-	<li>"*" matches any set of characters, including the empty string</li>
-	<li>"?" matches for any character</li>
-</ul>
-
-<h2>Case sensitive</h2>
-<p>Turn this option on if you want the text search to be case sensitive.</p>
-
-<h2>Scope</h2>
-<p>Choose the scope of your search. You can either search the whole workspace,
-pre-defined working sets, previously selected resources or projects enclosing
-the selected resources.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br>
-<a href="../concepts/csearchview.htm">Search view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a><br>
-<a href="../tasks/tasks-84.htm">Searching for text within a file</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br>
-<a href="ref-26.htm">Search view</a><br>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-47.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-47.htm
deleted file mode 100644
index fe4d6a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-47.htm
+++ /dev/null

@@ -1,26 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> CVS </H1>
-<DIV CLASS="Topic"> 
-  <P CLASS="Para"> The Workbench is shipped with a built in client for the Concurrent 
-    Versions System (CVS). With this client you can access CVS repositories.</P>
-  <P CLASS="Para"> You can find more information on CVS at&nbsp; <a href="http://ximbiot.com/cvs/" target="_blank">http://ximbiot.com/cvs/</a>.</P>
-  <P CLASS="Para">You can also visit the <a href="http://wiki.eclipse.org/index.php/CVS_FAQ" target="_blank">Eclipse 
-    CVS FAQ</a>.</P>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm
deleted file mode 100644
index 7f4c918..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-48a.htm
+++ /dev/null

@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ignoring resources from version control</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Ignoring resources from version control</H1>
-<P CLASS="Para" Label=Type>When synchronizing resources, it is possible that there 
-  are some resources that you do not want to commit to the repository. There 
-  are two ignore facilities provided, allowing you to specify what resources 
-  should be excluded from update and commit operations.</P>
-<P CLASS="Para" Label=Type>The first is a global ignore facility, provided by the
-Workbench. The second is the CVS ignore facility, which reads the contents of a
-special file .<i>cvsignore</i> to determine what to ignore.</P>
-<h2 Label=Type>Why ignore files when synchronizing?</h2>
-<P Label=Type>There are many files that a user may not want to commit to the repository.&nbsp;
-For example, external editors may create temporary files in your project. Compilation of .java files creates .class files, and
-likewise many build operations result in binary files. These files, when taken together, may
-be quite large. In addition, they may be re-generated whenever a build is performed,
-resulting in many&nbsp; outgoing changes.  Typically these are not files that one wants to share with other members of a team or persist in the repository.&nbsp;&nbsp;</P>
-<DIV CLASS="Subtopic">
-<h2>
-Global ignore facility</h2>
-<p CLASS="Head">A global ignore facility is provided by the Workbench via the
-Team preference page.
-There is a list of file patterns against which resources will be matched before they are
-considered as version control candidates.&nbsp;
-These patterns may contain the wildcard characters "*" and "?".&nbsp; "*"
-represents any sequence of zero or more characters.&nbsp; "?" represents any one
-character.&nbsp; For example, you can specify a pattern of "*~", which would match
-any temporary files that end with "~".&nbsp;&nbsp; Any file or directory that matches any one of the
-patterns will be ignored during&nbsp; update or commit operations.&nbsp; When
-you specify a file pattern to ignore, you can temporarily disable ignoring the
-file pattern by de-selecting it from the list; you do not have to remove the
-specified file pattern from the list.<br>
-<br>
-The patterns in the global ignore facility are matched against resource names during a
-synchronize operation.&nbsp; It is important to note that the path leading up to the resource name is not
-included in the matching.&nbsp; For example, for the file &quot;/path/to/file.txt&quot;, only the string
-&quot;file.txt&quot; is matched against the patterns.&nbsp; This facility is not intended for specifying fully-qualified
-path names but for specifying globally-applicable patterns.<br>
-</p>
-<h2>CVS ignore facility</h2>
-  <p CLASS="Head">The Eclipse CVS client recognizes a file named &quot;.cvsignore&quot; 
-    in each directory of a project.&nbsp; This is a standard CVS facility and 
-    many existing CVS projects may contain this file.<br>
-    <br>
-    This text file consists of a list of files, directories, or patterns.&nbsp; 
-    In a similar way to the global ignore facility, the wildcards "*" and "?" 
-    may be present in any entry in the .cvsignore file.&nbsp; Any file or sub-directory 
-    <b> in the current directory</b> that matches any one of the patterns will 
-    be ignored.&nbsp; It is important to note that the semantics of this file 
-    differs from that of the global ignore facility in that it applies only to 
-    files and&nbsp; directories in the same directory as the .cvsignore file itself.&nbsp; 
-    A project may contain one .cvsignore file in each directory.&nbsp; For more 
-    information, please visit&nbsp; <a href="http://ximbiot.com/cvs/" target="_blank">http://ximbiot.com/cvs/</a>.</p>
-  <p CLASS="Head">Resources that have not been added to CVS control can be ignored 
-    by selecting <b>Team &gt; Add to .cvsignore</b> from the pop-up menu of the 
-    resource in one of the navigation views. This menu option is also available 
-    in the Synchronize view.</p>
-</DIV>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-5.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-5.htm
deleted file mode 100644
index 6c681ee..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-5.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Builds</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1 class="Head">Builds</h1>
-<p class="Para">Builders create or modify workspace resources,
-usually based on the existence and state of other resources. They are a powerful
-mechanism for enforcing the constraints of some domain. For example, a Java
-builder converts Java source files (.java files) into executable class files
-(.class files), a web link builder updates links to files whose name/location
-have changed, etc.&nbsp; As resources are created and modified, builders are run
-and the constraints are maintained. This transform need not be one to one. For
-example, a single .java file can produce several .class files.&nbsp;</p>
-<h2>Auto-build vs. Manual Build</h2>
-<p class="Intro">There are two distinct user work modes with respect to
-building: relying on Auto-build, or user initiated manual building.</p>
-<p class="Intro">If you don't need fine-grained control over when builds occur,
-you can turn on auto-building. With auto-building on,
-builds occur after every set of resource changes (e.g., saving a file, importing
-a ZIP, ...). Auto-building is efficient because the amount of work done is
-proportional to the amount of change done.&nbsp; The benefit of auto-building is
-that your derived resources (e.g., Java .class files) are always up to date.
-Auto-building is turned on/off via the <b>Build automatically</b> option on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Workspace</b></a> preference page.</p>
-<p class="Intro">If you need more control over when builds occur, you can turn off
-auto-building and invoke builds manually. This is sometimes desirable in
-cases where, for example, you know building is of no value until you finish a
-large set of changes. In this case there is no benefit to paying the cost of
-auto-building. Builds can be invoked manually in numerous ways, for example, by
-right-clicking the project and selecting <b>Build Project</b>.</p>
-<p class="Intro">The disadvantage of manual building is that the problems that
-were generated to indicate build errors quickly become out of date until you
-build. In addition, it is very important that you remember to manually build
-before relying on build output (e.g. before running your Java program).</p>
-<h2>Building and Cleaning</h2>
-<p class="Intro">Builds work incrementally based on a previous built state. They
-will apply the transforms of the configured builders only on the resources that have 
-changed since that previous state was computed (i.e., since the last build).
-Auto-building always uses incremental building for efficiency.</p>
-<p class="Intro">A clean build (<b>Project &gt; Clean</b>) discards any existing
-built state.  The next build after a clean will transform all resources according the 
-domain rules of the configured builders.</p>
-<p class="Intro">Depending on your needs, build and clean can
-be done over a specific set of projects or the workspace as a whole.&nbsp;Specific
-files and folders cannot be built separately.</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-56.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-56.htm
deleted file mode 100644
index d5853b0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-56.htm
+++ /dev/null

@@ -1,120 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>File menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h1>File menu</h1>
-   
-<p>The <b>File</b> menu enables you to create, save, close, print, import, and export Workbench resources and to exit the Workbench.
-</p>
-
-<dl>
-
-<dt><b>New</b> (Shift+Alt+N)</dt>
-<dd>Enables you to create new resources.
-Before you can create a new file, you must create a project in which to store the file.
-</dd>
-
-<dt><b>Open File</b></dt>
-<dd>Enables you to open a file for editing - including files that do not reside in the Workspace.
-</dd>
-
-<dt><b>Close</b> (Ctrl+W)</dt>
-<dd>Closes the active editor.
-You are prompted to save changes before the file closes.
-</dd>
-
-<dt><b>Close All</b> (Shift+Ctrl+W)</dt>
-<dd>Closes all open editors.
-You are prompted to save changes before the files close.
-</dd>
-
-<dt><img src="../images/save_edit.png" alt="Save edit image"> <b>Save</b> (Ctrl+S)</dt>
-<dd>Saves the contents of the active editor.
-</dd>
-
-<dt><img src="../images/saveas_edit.png" alt="Save as image"> <b>Save As</b></dt>
-<dd>Enables you to save the contents of the
-active editor under another file name or location.
-</dd>
-
-<dt><img src="../images/saveall_edit.png" alt="Save all image"> <b>Save All</b> (Shift+Ctrl+S)</dt>
-<dd>Saves the contents of all open editors.
-</dd>
-
-<dt><b>Revert</b></dt>
-<dd>Replaces the contents of the active editor with the previously saved contents.
-</dd>
-
-<dt><b>Move</b></dt>
-<dd>Enables you to move the currently selected resources to a different project
-or to create a Java package with those resources.
-</dd>
-
-<dt><b>Rename</b> (F2)</dt>
-<dd>Enables you to change the name of the currently selected resource.
-</dd>
-
-<dt><b>Refresh</b> (F5)</dt>
-<dd>Refreshes the resource with the contents in the file system.
-</dd>
-
-<dt><b>Convert Line Delimiters To</b></dt>
-<dd>Alters the line delimiters for the selected files.
-Changes are immediate and persist until you change the delimiter 
-again - you do not need to save the file.
-</dd>
-
-<dt><img src="../images/print_edit.png" alt="Print editor image"> <b>Print</b> (Ctrl+P)</dt>
-<dd>Prints the contents of the active editor.
-</dd>
-
-<dt><b>Switch Workspace</b></dt>
-<dd>Opens the <b>Workspace Launcher</b>, from which you can
-switch to a different workspace. This restarts the Workbench.
-</dd>
-
-<dt><img src="../images/import_wiz.png" alt="Import wizard image"> <b>Import</b></dt>
-<dd>Launches the <b>Import</b> wizard, which enables you to add resources to the Workbench.
-</dd>
-
-<dt><img src="../images/export_wiz.png" alt="Export wizard image"> <b>Export</b></dt>
-<dd>Launches the <b>Export</b> wizard, which enables you to export resources from the Workbench.
-</dd>
-
-<dt><b>Properties</b> (Alt+Enter)</dt>
-<dd>Opens the <b>Properties</b> dialog for the currently selected resource.
-You can learn:
-<ul>
-<li>The path to the resource in your file system</li>
-<li>The date of the last modification</li>
-<li>Whether a file is writable or executable, and what its encoding is</li>
-<li>Whether a project's resources inherit their encoding and line delimiters
-or whether they are set to a particular value.</li>
-</ul> 
-</dd>
-
-<dt><b>Recent file list</b></dt>
-<dd>Contains a list of the most recently accessed files in the Workbench. 
-You can open any of these files from the <b>File</b> menu by simply clicking the file name.
-You can control the number of files in this list from the 
-<a href="ref-12.htm">Editors preference page</a>.
-</dd>
-
-<dt><b>Exit</b></dt>
-<dd>Closes and exits the Workbench.
-</dd>
-
-</dl>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-57.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-57.htm
deleted file mode 100644
index b0ec663..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-57.htm
+++ /dev/null

@@ -1,119 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Edit menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-
-<h1 class="Head">Edit menu</h1>
-<p class="Intro"><a name="pgfId-1010738"></a>This menu helps you manipulate
-resources in the editor area.</p>
-<div class="Topic">
-  <a name="elementId-1010741"></a><a name="pgfId-1010746"></a>
-  <h2>Undo</h2>
-  <p class="Para"><a name="pgfId-1010752"></a>This command reverses your most
-  recent editing action.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007106"></a><a name="pgfId-1010758"></a>
-  <h2>Redo</h2>
-  <p class="Para"><a name="pgfId-1007117"></a>This command re-applies the editing
-  action that has most recently been reversed by the Undo action.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007120"></a><a name="pgfId-1007125"></a>
-  <h2>Cut</h2>
-  <p class="Para"><a name="pgfId-1007131"></a>This command removes the selection
-  and places it on the clipboard.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007134"></a><a name="pgfId-1007139"></a>
-  <h2>Copy</h2>
-  <p class="Para"><a name="pgfId-1007145"></a>This command places a copy of the
-  selection on the clipboard.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007148"></a><a name="pgfId-1007153"></a>
-  <h2>Paste</h2>
-  <p class="Para"><a name="pgfId-1007159"></a>This command places the text or
-  object on the clipboard at the current cursor location in the currently active
-  view or editor.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007162"></a><a name="pgfId-1007167"></a>
-  <h2>Delete</h2>
-  <p class="Para"><a name="pgfId-1007173"></a>This command removes the current
-  selection.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007176"></a><a name="pgfId-1007181"></a>
-  <h2>Select All</h2>
-  <p class="Para"><a name="pgfId-1007187"></a>This command selects all text or
-  objects in the currently active view or editor.</p>
-</div>
-<div class="Topic">
-  <a name="elementId-1007190"></a><a name="pgfId-1007195"></a>
-  <h2>Find/Replace</h2>
-  <p class="Para"><a name="pgfId-1007201"></a>This command allows you to search
-  for an expression in the active editor, and optionally replace the expression with a new expression.</p>
-</div>
-<DIV CLASS="Topic">
-<h2>Find Next</h2>
-<P CLASS="Para">
-This command allows you to search for the next occurrence of the current selection, or
-for the next occurrence of the most recent expression found using the Find/Replace action.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Find Previous</h2>
-<P CLASS="Para">
-This command allows you to search for the previous occurrence of the current selection, or
-for the previous occurrence of the most recent expression found using the Find/Replace action.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Incremental Find Next</h2>
-<P CLASS="Para">
-This command allows you to search for expressions in the active editor.  As you type the search
-expression, it will incrementally jump to the next exact match in the active editor.  While in this
-mode, the up and down cursor keys can be used to navigate between matches, and the search
-can be cancelled by pressing left or right cursor keys, the enter key, or the escape key.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Incremental Find Previous</h2>
-<P CLASS="Para">
-This command allows you to search for expressions in the active editor.  As you type the search
-expression, it will incrementally jump to the previous exact match in the active editor.  While in this
-mode, the up and down cursor keys can be used to navigate between matches, and the search
-can be cancelled by pressing left or right cursor keys, the enter key, or the escape key.</P>
-</DIV>
-<div class="Topic">
-  <a name="elementId-1007218"></a><a name="pgfId-1007223"></a>
-  <h2>Add Bookmark</h2>
-  <p class="Para"><a name="pgfId-1007230"></a>This command adds a bookmark in
-  the active file on the line where the cursor is currently displayed.</p>
-</div>
-<DIV CLASS="Topic">
-<h2>Add Task</h2>
-<P CLASS="Para">
-This command adds a task in the active file on the line where the cursor is currently displayed.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Word Completion</h2>
-<P CLASS="Para">
-This action will attempt to complete the word currently being entered in the active editor.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>Set Encoding</h2>
-<P CLASS="Para">
-This action launches a dialog that allows you to change the file encoding used to read and write the file in the active editor.</P>
-</DIV>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-58.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-58.htm
deleted file mode 100644
index d7f7d8d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-58.htm
+++ /dev/null

@@ -1,104 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigate menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Navigate menu
-</h1>
-<P CLASS="Intro">
-This menu allows you to locate and navigate through resources and other artifacts displayed in the Workbench.</p>
-<DIV CLASS="Topic">
-<h2>
-Go Into</h2>
-<P CLASS="Para">
-This command refocuses the active view so that the current selection is at the root.  This allows web 
-browser style navigation within hierarchies of artifacts.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2 CLASS="Head">
-Go To</H2>
-
-<UL CLASS="UnorderedList">
-<LI CLASS="Item">
-<b>Back</b>:&nbsp; This command displays the hierarchy that was displayed immediately prior to the current display.&nbsp; For example, if
-you Go Into a resource, then the Back command in the resulting display returns the view to the same hierarchy from which you activated the Go Into command.&nbsp; This command is similar to the Back button in an HTML browser.</LI>
-<LI CLASS="Item">
-<b>Forward</b>:&nbsp; This command displays the hierarchy that was displayed immediately after the current display.&nbsp; For example, if you've just selected the Back command, then selecting the Forward command in the resulting display returns the view to the same hierarchy from which you activated the Back command.&nbsp; This command is similar to the Forward button in an HTML browser.</LI>
-<LI CLASS="Item">
-<b>Up one level</b>:&nbsp; This command displays the hierarchy of the parent of the current highest-level resource.</LI>
-  <LI CLASS="Item"><B>Resource</B>: This command allows you to navigate quickly to a resource. For more information
-  see the links to related tasks below.</LI>
-</UL>
-</DIV>
-<DIV CLASS="Topic">
-<H2>Open Resource</H2>
-<P>This command displays a dialog that lets you select any resource in the
-workspace to open it in an editor. For more information see the links
-to related tasks below.</P>
-</DIV>
-<DIV CLASS="Topic">
-<H2>Show In</H2>
-<P>This sub-menu is used to find and select the currently selected resource in another view.
-If an editor is active, these commands are used to select the resource currently being edited
-in another view.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Next</h2>
-<P CLASS="Para">
-This command navigates to the next item in a list or table in the active view.  For example, when the search results view
-is active, this navigates to the next search result.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Previous</h2>
-<P CLASS="Para">
-This command navigates to the previous item in a list or table in the active view.  For example, when the search results view
-is active, this navigates to the previous search result.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>Last Edit Position</h2>
-<P CLASS="Para">
-This command allows you to jump the last edit position.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>Go to Line</h2>
-<P CLASS="Para">
-This command allows you to jump to a specific line in the active editor.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Back</h2>
-<P CLASS="Para">
-This command navigates to the previous resource that was viewed in an editor.
-Analogous to the <b>Back</b> button on a web browser.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Forward</h2>
-<P CLASS="Para">
-This command navigates to undo the effect of the previous
-<b>Back</b> command.  Analogous to the <b>Forward</b> button on a web browser.</P>
-</DIV>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-46ag.htm">Finding a resource quickly</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-59.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-59.htm
deleted file mode 100644
index 300bf34..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-59.htm
+++ /dev/null

@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Project menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Project menu</H1>
-<P CLASS="Para">
-The Project menu allows you to perform actions (builds or compilations) on projects in the Workbench.</P>
-<DIV CLASS="Topic">
-<h2>
-Open Project</h2>
-<P CLASS="Para">
-This command opens the currently selected project or projects.  The selected projects must currently 
-be closed for this command to be available.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Close Project</h2>
-<P CLASS="Para">
-This command closes the currently selected project or projects.  The selected projects must be
-currently open for this command to be available.  Closing a project will remove all of that project's
-state from memory, but the contents on disk are left untouched.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build All</h2>
-<P CLASS="Para">
-This command performs an incremental build on all projects in the Workbench. That is, it builds 
-(compiles) all resources in the Workbench that are affected by any resource changes since the 
-last incremental build.  This command is only available if auto-build is turned off.  Auto-build is turned
-off via the <strong>Build Automatically</strong> menu option or from the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build Project</h2>
-<P CLASS="Para">
-This command performs an incremental build on the currently selected project. That is, it builds 
-(compiles) all resources in the project that are affected by any resource changes since the 
-last build.  This command is only available if auto-build is turned off.  Auto-build is turned
-off via the <strong>Build Automatically</strong> menu option or from the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build Working Set</h2>
-<P CLASS="Para">
-This menu allows you to performs an incremental build on a working set. That is, it builds 
-(compiles) all resources in the working set that are affected by any resource changes since the 
-last build.  This command is only available if auto-build is turned off.  Auto-build is turned
-off via the <strong>Build Automatically</strong> menu option or from the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Clean</h2>
-<P CLASS="Para">
-This command discards all previous build results.  If autobuild is on, then this invokes a full build.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Build Automatically</h2>
-<P CLASS="Para">
-This command allows you to toggle the auto build preference.  The auto-build preference is also located on the <b>General &gt; Workspace</b> preference page.
-</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Properties</h2>
-<P CLASS="Para">
-This command opens a dialog showing the properties of the selected project or of the project that contains the
-selected resource.</P>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-6.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-6.htm
deleted file mode 100644
index 4d3f61e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-6.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Perspectives</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Perspectives</H1>
-
-<P CLASS="Intro">
-A perspective defines the initial set and layout of views in the Workbench
-window. One or more perspectives can exist in a single Workbench window.</p>
-<p CLASS="Para" Label=Type>Perspectives can be opened either in the same 
-(existing) Workbench window, hiding the current perspective, or in a new 
-Workbench window</p>
-<p CLASS="Para" Label=Type>Perspectives define visible action sets, which you
-can change to customize a perspective.&nbsp; You can save a perspective that you
-build in this manner, making your own custom perspective that you can open again
-later.&nbsp;&nbsp;</p>
-<P CLASS="Para">
-The Workbench defines the <i>Resource</i> perspective by default. This 
-perspective shows views relevant to resource management.
-</P>
-
-<P><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-60.htm">Window Menu</a>
-<br><a href="ref-24.htm">Editor Area</a>
-<br><a href="ref-27.htm">Project Explorer View</a>
-<br><a href="ref-30.htm">Outline View</a>
-<br><a href="ref-31.htm">Tasks View</a>
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-60.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-60.htm
deleted file mode 100644
index b75bd82..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-60.htm
+++ /dev/null

@@ -1,163 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Window menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Window menu</H1>
-<P CLASS="Intro">
-This menu allows you to display, hide, and otherwise manipulate the various views, perspectives, and actions in the Workbench.</p>
-
-<DIV CLASS="Topic">
-<h2>
-New Window</h2>
-<P CLASS="Para">
-This command opens a new Workbench window with the same perspective as the current perspective.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-New Editor</h2>
-<P CLASS="Para">
-This command opens an editor based on the currently active editor.  It will have the same editor type and input as the original.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h2>
-Open Perspective</h2>
-<P CLASS="Para">
-This command opens a new perspective in this Workbench window.
-This preference can be changed on the <b>General &gt; Perspectives</b>
-preference page. All of the perspectives that are open within the Workbench window are
-shown on the shortcut bar.</P>
-<P CLASS="Para">
-The perspectives you will likely want to open are
-listed first.&nbsp;This list is dependent on the current perspective. From the <b>Other...</b> submenu you can open any perspective.</P>
-<P CLASS="Para"><img src="../images/Image207_persp_sel.png" alt="Select Perspective dialog" border="0" ></P>
-<P CLASS="Para">&nbsp;</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Show View</h2>
-<P CLASS="Para">
-This command displays the selected view in the
-current perspective.&nbsp; You can configure how views are opened on the <b>General &gt; 
-Perspectives</b> preference page. Views you are likely to want to open are listed
-first.&nbsp;This list is dependent on the current perspective. From the <b>Other...</b> submenu you can open any view.&nbsp; The views
-are sorted into categories in the Show View dialog.</P>
-<P CLASS="Para"><img src="../images/Image208_view_sel.png" alt="Show View Dialog" border="0" ></P>
-</DIV>
-
-<DIV CLASS="Topic">
-  <h2> Customize Perspective</h2>
-</DIV>
-<DIV CLASS="Topic">
-  <P CLASS="Para"> Each perspective includes a predefined set of actions that are 
-    accessible from the menu bar and Workbench toolbar.&nbsp;</P>
-<P CLASS="Para"><img src="../images/Image258_perps_custom.png" alt="Customize Perspective Dialog" border="0" > 
-  </P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Save Perspective As</h2>
-<P CLASS="Para">
-This command allows you to save the current perspective,
-creating your own custom perspective.&nbsp; You can open more perspectives of
-this type using the <b>Window &gt; Open Perspective &gt; Other</b> menu item once you have
-saved a perspective.&nbsp;</P>
-  <P CLASS="Para"> <img src="../images/Image206_persp_saveas.png" alt="Save Perspective As dialog" border="0" >x</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Reset Perspective</h2>
-<P CLASS="Para">
-This command changes the layout of the current perspective to its original
-configuration.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Close Perspective</h2>
-<P CLASS="Para">
-This command closes the active perspective.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Close All Perspectives</h2>
-<P CLASS="Para">
-This command closes all open perspectives in the
-Workbench window.</P>
-</DIV>
-
-<DIV CLASS="Topic"> 
-  <h2> Navigation</h2>
-<P CLASS="Para">
-This submenu contains shortcut keys for navigating between the views, perspectives, and editors in the Workbench window.</P>
-  <UL CLASS="UnorderedList">
-    <LI CLASS="Item"> <b>Show System Menu</b>:&nbsp; Shows the menu that is used 
-      for resizing, closing or pinning the current view or editor.</LI>
-    <LI CLASS="Item"> <b>Show View Menu</b>:&nbsp; Shows the drop down menu that 
-      is available in the toolbar of the active view.</LI>
-    <LI CLASS="Item"> <strong>Maximize active view or editor: </strong>Causes 
-      the active part to take up the entire screen, or if it already is, returns 
-      it to its previous state. </LI>
-    <LI CLASS="Item"> <strong>Minimize active view or editor: </strong>Causes 
-      the active part to be minimized. </LI>
-    <LI><b>Activate Editor</b>:&nbsp; Makes the current editor active.</LI>
-    <LI CLASS="Item"> <b>Next Editor</b>:&nbsp; Activates the next open editor 
-      in the list of most recently used editors.</LI>
-    <LI CLASS="Item"> <b>Previous Editor</b>:&nbsp; Activates the previous open 
-      editor in the list of most recently used editors.</LI>
-    <LI CLASS="Item"> <strong>Switch to editor:</strong> Shows a dialog that allows 
-      switching to opened editors. Shows a dialog that allows switching to opened 
-      editors. </LI>
-    <LI CLASS="Item"> <strong>Quick switch editor:</strong> Shows a searchable 
-	popup that allows switching to a new editor. </LI>
-    <LI><b>Next View</b>:&nbsp; Activates the next open view in the list of most 
-      recently used views.</LI>
-    <LI CLASS="Item"> <b>Previous View</b>:&nbsp; Activates the previous open 
-      view in the list of most recently used editors.</LI>
-    <LI CLASS="Item"> <b>Next Perspective</b>:&nbsp; Activates the next open perspective 
-      in the list of most recently used perspectives.</LI>
-    <LI CLASS="Item"> <b>Previous Perspective</b>:&nbsp; Activates the previous 
-      open perspective in the list of most recently used perspectives.</LI>
-  </UL>
-</DIV>
-<DIV CLASS="Topic"></DIV>
-<DIV CLASS="Topic">
-<h2>
-Working Sets</h2>
-<P CLASS="Para">
-This submenu contains entries to select or edit working sets.
-</P>
-<DIV CLASS="XRefList">
-</DIV>
-</DIV>
-<DIV CLASS="Topic"></DIV>
-<DIV CLASS="Topic">
-<h2>
-Preferences</h2>
-<P CLASS="Para">
-This command allows you to indicate your preferences for using the Workbench.&nbsp;  There
-are a wide variety of preferences for configuring the appearance of the Workbench and its views, 
-and for customizing the behavior of all tools that are installed in the Workbench.
-</P>
-<DIV CLASS="XRefList">
-</DIV>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-61.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-61.htm
deleted file mode 100644
index 33dfe7b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-61.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Help menu</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h1>
-Help menu</h1>
-<P CLASS="Para">
-This menu provides help on using the Workbench.</P>
- <h2 CLASS="Head"> Welcome</h2>
-<p CLASS="Head">
-This command will open the welcome content.</p>
-<DIV CLASS="Topic">
-<h2 CLASS="Head">
-Help Contents</h2>
-<P CLASS="Para">
-This command displays the help contents in a help window or external browser.
-The help contents contains help books, topics, and information related to the Workbench and installed
-features.</P>
-<h2 CLASS="Head">
-Search</h2>
-<P CLASS="Para">
-This command displays the help view opened on the Search page.</P>
-<h2 CLASS="Head">
-Dynamic Help</h2>
-<P CLASS="Para">
-This command displays the help view opened to Related Topics page.</P>
-<h2 CLASS="Head"> Key Assist ...</h2>
-  <p CLASS="Head"> This command will display a list of key bindings</p>
-  <h2 CLASS="Head"> Tips and Tricks ...</h2>
-<p CLASS="Head">
-This command will open a list of interesting productivity features that you may not have discovered.</p>
-<h2 CLASS="Head"> Cheat Sheets ...</h2>
-  <p CLASS="Head"> This command will open the cheat sheet selection dialog.</p>
-<h2 CLASS="Head">
-<a NAME="SoftwareUpdates"></a>Check for Updates</h2>
-<P CLASS="Para">
-This command will check for updates to the installed software.</P>
-<h2 CLASS="Head">
-<a NAME="InstallNewSoftware"></a>Install New Software...</h2>
-<P CLASS="Para">
-This command allows you to download and install new software.</P>
-<h2 CLASS="Head">
-About Eclipse SDK</h2>
-<P CLASS="Para">
-This command displays information about the product, installed features, and
-available plug-ins.</P>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-65.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-65.htm
deleted file mode 100644
index 6713429..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-65.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<title>Project Explorer view icons</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h1>Project Explorer view icons</h1>
-
-<p>The following icons can appear in the navigation views:
-</p>
-
-<table border="1" cellspacing="0" cellpadding="4">
-<caption>Project Explorer view icons</caption>
-<thead>
-<tr>
-<th>Icon</th>
-<th>Description</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-10.png" alt="Open Project icon"></td>
-<td>Project (open)</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-12.png" alt="Folder icon"></td>
-<td>Folder (open)</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-11.png" alt="Closed Project icon"></td>
-<td>Project (closed)</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-15.png" alt="File icon"></td>
-<td>Generic File</td>
-</tr>
-</tbody>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-66.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-66.htm
deleted file mode 100644
index 6d6bde0..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-66.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<title>Editor area marker bar</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h1>Editor area marker bar</h1>
-
-<p>The following markers can appear in the marker bar (to the left of the editor area):
-</p>
-
-<table border="1" cellspacing="0" cellpadding="4">
-<caption>Marker Bar Markers</caption>
-<thead>
-<tr>
-<th>Icon</th>
-<th>Description</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td align="center" valign="middle" align="center" valign="middle"><img src="../images/ref-16.png" alt="Bookmark icon"></td>
-<td>Bookmark</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle" align="center" valign="middle"><img src="../images/ref-17.png" alt="Breakpoint icon"></td>
-<td>Breakpoint</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-18.png" alt="Task marker icon"></td>
-<td>Task marker</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/searchm_obj.png" alt="Search result icon"></td>
-<td>Search result</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-24.png" alt="Error marker icon"></td>
-<td>Error marker</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-22.png" alt="Warning marker icon"></td>
-<td>Warning marker</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-20.png" alt="Information marker icon"></td>
-<td>Information marker</td>
-</tr>
-</tbody>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-67.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-67.htm
deleted file mode 100644
index b3b2f98..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-67.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<title>Tasks view</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h1>Tasks view</h1>
-<p>The following markers can appear in the Tasks view:
-</p>
-
-<table border="1" cellspacing="0" cellpadding="4">
-<caption>Tasks View Icons</caption>
-<thead>
-<tr>
-<th>Icon</th>
-<th>Description</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td align="center" valign="middle" align="center" valign="middle"><img src="../images/ref-21.png" alt="High priority task icon"></td>
-<td>High priority task</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-23.png" alt="Low priority task icon"></td>
-<td>Low priority task</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/ref-25.png" alt="Completed task icon"></td>
-<td>Completed task</td>
-</tr>
-</tbody>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-68.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-68.htm
deleted file mode 100644
index 67b5ed4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-68.htm
+++ /dev/null

@@ -1,189 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<title>Toolbar buttons</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h1>Toolbar buttons</h1>
-
-<p>The following buttons may appear in the Workbench toolbar, toolbars for views, and the shortcut bar:
-</p>
-
-<table border="1" cellspacing="0" cellpadding="4">
-<thead>
-<tr>
-<th>Button</th>
-<th>Description</th>
-<th>Button</th>
-<th>Description</th>
-</tr>
-</thead>
-
-<tbody>
-<tr>
-<td align="center" valign="middle"><img src="../images/new_persp.png" alt="New perspective image"></td>
-<td>Open a new perspective</td>
-<td align="center" valign="middle"><img src="../images/save_edit.png" alt="Save edit image"></td>
-<td>Save the active editor contents</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/saveall_edit.png" alt="Save all image"></td>
-<td>Save the contents of all editors</td>
-<td align="center" valign="middle"><img src="../images/saveas_edit.png" alt="Save as image"></td>
-<td>Save editor contents under a new name or location</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/search_src.png" alt="Open search dialog image"></td>
-<td>Opens the search dialog</td>
-<td align="center" valign="middle"><img src="../images/print_edit.png" alt="Print editor image"></td>
-<td>Print editor contents</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/new_wiz.png" alt="New wizard image"></td>
-<td>Open a resource creation wizard</td>
-<td align="center" valign="middle"><img src="../images/newfile_wiz.png" alt="New file image"></td>
-<td>Open a file creation wizard</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/newfolder_wiz.png" alt="New folder image"></td>
-<td>Open a folder creation wizard</td>
-<td align="center" valign="middle"><img src="../images/newprj_wiz.png" alt="New project image"></td>
-<td>Open a project creation wizard</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/import_wiz.png" alt="Import wizard image"></td>
-<td>Open the import wizard</td>
-<td align="center" valign="middle"><img src="../images/export_wiz.png" alt="Export wizard image"></td>
-<td>Open the export wizard</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/build_exec.png" alt="Build image"></td>
-<td>Run incremental build</td>
-<td align="center" valign="middle"><img src="../images/run_exec.png" alt="Run image"></td>
-<td>Run a program</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/debug_exec.png" alt="Debug image"></td>
-<td>Debug a program</td>
-<td align="center" valign="middle"><img src="../images/external_tools.png" alt="Run external tool image"></td>
-<td>Run an external tool or Ant</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/cut_edit.png" alt="Cut image"></td>
-<td>Cut selection to clipboard</td>
-<td align="center" valign="middle"><img src="../images/copy_edit.png" alt="Copy image"></td>
-<td>Copy selection to clipboard</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/paste_edit.png" alt="Paste image"></td>
-<td>Paste selection from clipboard</td>
-<td align="center" valign="middle"><img src="../images/undo_edit.png" alt="Undo edit image"></td>
-<td>Undo most recent edit</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/redo_edit.png" alt="Redo edit image"></td>
-<td>Redo most recent undone edit</td>
-<td align="center" valign="middle"><img src="../images/next_nav.png" alt="Navigate next image"></td>
-<td>Navigate to next item in a list</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/prev_nav.png" alt="Navigate previous image"></td>
-<td>Navigate to previous item in a list</td>
-<td align="center" valign="middle"><img src="../images/forward_nav.png" alt="Navigate forwards image"></td>
-<td>Navigate forwards</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/backward_nav.png" alt="Navigate backwards image"></td>
-<td>Navigate backwards</td>
-<td align="center" valign="middle"><img src="../images/up_nav.png" alt="Navigate up image"></td>
-<td>Navigate up one level</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/addbkmrk_tsk.png" alt="Add bookmark or task image"></td>
-<td>Add bookmark or task</td>
-<td align="center" valign="middle"><img src="../images/view_menu.png" alt="View menu image"></td>
-<td>Open a view's drop down menu</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/close_view.png" alt="Close view image"></td>
-<td>Close view or editor</td>
-<td align="center" valign="middle"><img src="../images/pin_editor.png" alt="Pin editor image"></td>
-<td>Pin editor to prevent automatic reuse</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/filter_ps.png" alt="Filter tasks or properties image"></td>
-<td>Filter tasks or properties</td>
-<td align="center" valign="middle"><img src="../images/gotoobj_tsk.png" alt="Goto object image"></td>
-<td>Go to a task, problem, or bookmark in the editor</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/defaults_ps.png" alt="Restore defaults image"></td>
-<td>Restore default properties</td>
-<td align="center" valign="middle"><img src="../images/tree_mode.png" alt="Tree mode image"></td>
-<td>Show items as a tree</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/refresh_nav.png" alt="Refresh image"></td>
-<td>Refresh view contents</td>
-<td align="center" valign="middle"><img src="../images/alpha_mode.png" alt="Alphabetical order image"></td>
-<td>Sort list in alphabetical order</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/stop_nav.png" alt="Cancel operation image"></td>
-<td>Cancel a long running operation</td>
-<td align="center" valign="middle"><img src="../images/delete_edit.png" alt="Delete image"></td>
-<td>Delete selected item or content</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/last_edit_pos.png" alt="Last edit location image"></td>
-<td>Last edit location</td>
-<td align="center" valign="middle"><img src="../images/mark_occurrences.png" alt="Toggle Mark Occurrences image"></td>
-<td>Toggle Mark Occurrences</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/block_selection_mode.gif" alt="Toggle Block Selection Mode"></td>
-<td>Toggle Block Selection Mode</td>
-<td align="center" valign="middle"><img src="../images/show_whitespace_chars.gif" alt="Show Whitespace Characters"></td>
-<td>Show Whitespace Characters</td>
-</tr>
-
-<tr>
-<td align="center" valign="middle"><img src="../images/segment_edit.png" alt="Show source of selected element only image"></td>
-<td>Show source of selected element only</td>
-<td>&nbsp;</td>
-<td>&nbsp;</td>
-</tr>
-</tbody>
-</table>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts">
-<br><a href="../concepts/concepts-18.htm">Toolbars</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm
deleted file mode 100644
index 928aebf..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-6a.htm
+++ /dev/null

@@ -1,112 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Local history</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Local history</H1>
-<p>Local history of a file is maintained when you create or modify a file. Each time you edit and save
-a file,&nbsp;a copy of it is saved. This allows you to compare
-your current file state to a previous state, or replace the file with a previous
-state.&nbsp;Each state in the local
-history is identified by the date and time the file was
-saved.&nbsp;&nbsp;</p>
-<p>Neither projects nor folders have local history.</p>
-<p>Local History is displayed in the History View. Here is a look at what the local history of a Workbench file might look
-like: </p>
-<p><img src="../images/Image273_local_hist.png" alt="Local history dialog" border="0" ></p>
-<P>To view the local history of a file, choose <b>Team &gt; Show Local History</b> from the pop-up
-menu.&nbsp; This will bring up the History view and populate it with the revisions of the selected
-file. You can open different revisions from the table (by using <b>Open</b> from the context menu or 
-by double clicking on a revision), compare them against the latest revision or against a
-previous revisions (by using <b>Compare With Revision</b> from the context menu), and replace the current revision 
-with the contents of a previous revisions (by using <b>Get Contents</b> from the context menu). 
-</P>
-
-<p><i>Note</i>: Projects that are managed by CVS now have the local history revisions displayed
-alongside remote revisions. In order to see the local history for a CVS managed file, select the
-<b>Team &gt; Show History</b> menu item and make sure that the History View is one of the modes capable
-of showing local history. </p>
-
-<h2>Toolbar</h2>
-
-<div class="Topic"> 
-<h3>Refresh</h3>  
-<p class="Para">This command refreshes the contents of the view, 
-fetching the latest history information for the resource from the server.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Link with Editor and Selection</h3>  
-<p class="Para">When enabled, the view will display the history for the resource 
-of the active editor or of the active selection.</p>
-</div> 
-
-<div class="Topic"> 
-<h3>Pin</h3>  
-<p class="Para">When enabled will pin the view and its contents. Any new requests for history
-will open a new instance of the History View.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Group Revisions by Date</h3>  
-<p class="Para">When enabled, all history items will be sorted into one of the following date
-categories: </p>
-<ul>
-<li>Today</li>
-<li>Yesterday</li>
-<li>This Month</li>
-<li>Previous</li>
-</ul>
-
-</div>
-
-<div class="Topic"> 
-<h3>Collapse All</h3>  
-<p class="Para">Will the view is in the Group by Date mode, Collapse All will collapse all of the
-date categories.</p>
-</div>
-
-<div class="Topic"> 
-<h3>Compare Mode</h3>  
-<p class="Para">When enabled, a double click (or a single click depending on your Open Mode strategy set
-in <b>Preferences&gt;General</b>) will open a compare editor. When it is disabled, clicking on a revision
-will open that revision.</p>
-</div>
-
-<h2 class="Para">Context menu </h2>
-     
-<p class="Para">From the context menu of the Local History view you can perform
-the following operations:</p>
-     
-<h3>Open</h3>   
-<p class="Para">This command will open the contents of the selected revision in a read only
-editor. (The editor used is the one that is registered as the default editor for the file type).
-<i>Note</i>: If the revision being opened is the current version of the file, then it will be opened
-in a regular editor.</p>
-
-<h3>Compare Current With Revision/Compare With Each Other</h3>   
-<p class="Para">The compare command differs based on the number of revisions selected in the 
-history view. For a single selection, <b>Compare Current With Revision</b> will the compare the
-current version of the resource with the selected revision. For two selections, <b>Compare with Each
-Other</b> will compare the selected revisions.</p>
-
-<h3>Get Contents</h3>   
-<p class="Para">This command will load the contents of the selected revision
-into the local copy of the file whose history
-is displayed in the view.</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- >
- <br>
-    <a href="ref-32a.htm">CVS History view</a>  </p>
-     
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-7.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-7.htm
deleted file mode 100644
index 5d3295d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-7.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!doctype doctype public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<title>Accessibility preference page</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-</head>
-<body bgcolor="#ffffff">
-
-<h1 class="Head">Accessibility preference page</h1>
-
-<p>You can change the following preferences on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Accessibility)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"><strong>General &gt; Editors &gt; Text Editors &gt; Accessibility</strong></a> preference page:
-</p>
-
-<table border="1" cellspacing="0" cellpadding="5">
-<thead>
-<tr valign="top">
-<th>Option</th>
-<th>Description</th>
-<th>Default</th>
-</tr>
-</thead>
-<tbody>
-<tr valign="top">
-<td><b>Use custom caret</b></td>
-<td>Replaces the original <i>caret</i> (the marker that indicates where the next character will appear) 
-with a custom caret and shows a different caret for Overwrite and Insert modes.</td>
-<td>On</td>
-</tr>
-<tr valign="top">
-<td><b>Enable thick caret</b></td>
-<td>Replaces the original caret with a more visible, thicker caret.</td>
-<td>On</td>
-</tr>
-<tr valign="top">
-<td><b>Use characters to show changes on line number bar</b></td>
-<td>Quick Diff shows the changes in a vertical ruler using colors. 
-Color-blind persons can enable this option to show differences with different characters 
-in the line number ruler.</td>
-<td>Off</td>
-</tr>
-</tbody>
-</table>
-
-<p>The <b>Accessibility</b> preference page:
-</p>
-
-<p><img src="../images/ref-accessibility.png" alt="Accessibility preference page">
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-70.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-70.htm
deleted file mode 100644
index 58f6bd9..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-70.htm
+++ /dev/null

@@ -1,639 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Import wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Import wizard</H1>
-<P CLASS="Para">
-This wizard helps you import resources into the Workbench.</P>
-<P CLASS="Para">
-When the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Import wizard</b></a>
-first comes up, you must choose what type of import to
-do. To assist in locating a particular wizard, 
-the text field can be used to show only the wizards that match the entered text. </P>
-<img src="../images/Image261_import_sel.png" alt="Import wizard" border="0">
-<P CLASS="Para"> </P>
-
-<DIV CLASS="Topic">
-  <h2> Archive File</h2>
-  <p CLASS="Head"> If you choose this option, you will import files from an archive 
-    file.</p>
-  <P>&nbsp;<img src="../images/Image263_import_zip.png" alt="Archive file import wizard page" border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Import - Archive File Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Archive File</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The file from which to import.&nbsp; Type in the full path or Browse to select
-the path on the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Filter Types...</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Dialog to select which file types to import.&nbsp; Use this to restrict the
-import to only certain file types.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all resources for import</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Folder
-</TD>
-<TD COLSPAN="1">
-The folder into which the resources will be imported.&nbsp; Type the path or
-Browse to select a path in the Workbench.
-</TD>
-<TD COLSPAN="1">
-The folder holding the selected resource
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing resources without warning
-</TD>
-<TD COLSPAN="1">
-Determines whether importing a resource should silently overwrite a resource
-which already exists in the Workbench. If this option is off, you will be
-prompted before a given resource is overwritten, in which case you can either
-overwrite the resource, skip it, or cancel the import.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-<DIV CLASS="Topic">
-  <h2>Checkout projects from CVS</h2>
-  <p CLASS="Head">Import a project from a CVS Repository.</p>
-  <P>&nbsp;<img src="../images/Image263_import_cvs.png" alt="CVS project import wizard page" border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Import - Checkout projects from CVS Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Create a new repository location</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Go to the <a href="ref-40.htm">New CVS Repository Location
-wizard</a>.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&lt;disabled&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Use existing repository location</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Use a previously datafilled CVS location.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>enabled</i></P>
-</TD>
-</TR>
-
-</TBODY>
-</TABLE>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>
-Existing Project into Workspace</h2>
-<p CLASS="Head">
-Imports a project into this workspace that was previously located in this workspace, or
-that currently exists in another workspace.</p>
-  <P>&nbsp;<img src="../images/Image264_existing_project.png" alt="Existing project import wizard page"  border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - Existing Project Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select root directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Root directory in the File System to start
-scanning for projects to import. Type in the full path or Browse to
-select the path on the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select archive file</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Archive file to scan for projects to import.
-Type in the full path or Browse to select the archive on the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;disabled&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Check all of the projects that were found for import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Uncheck all projects.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Refresh</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Rescan the selected source for projects to import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Copy projects into workspace</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-When selected this will cause the imorted project to be copied into
-the current workspace.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">&nbsp;Off
-</P>
-</TD>
-</TR>
-
-</TBODY>
-</TABLE>
-</DIV>
-
-<DIV CLASS="Topic">
-<h2>File System</h2>
-<p CLASS="Head">
-If you choose this option, you will import files from the file system.</p>
-  <p CLASS="Head"> <img src="../images/Image262_import_file.png" alt="Import file system page" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - File System Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The directory from which to import files.&nbsp; Select a previous path from the
-drop down combo or Browse to select the path in the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Filter Types</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Dialog to select which file types to import.&nbsp; Use this to
-restrict the import to only certain file types.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all files and folders for import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Folder
-</TD>
-<TD COLSPAN="1">
-The folder into which the resources will be imported.&nbsp; Type the path or
-Browse to select a path in the Workbench.
-</TD>
-<TD COLSPAN="1">
-The folder holding the selected resource&nbsp;
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing resources without warning
-</TD>
-<TD COLSPAN="1">
-Determines whether importing a resource should silently overwrite a resource
-which already exists in the Workbench. If this option is off, you will be
-prompted before a given resource is overwritten, in which case you can either
-overwrite the resource, skip it, or cancel the import.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create complete folder structure</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the Workbench to accommodate the
-resources being imported, and all parent folders of those resources in the file system. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Off</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create selected folders only</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the Workbench to accommodate the
-resources being imported. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">On</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic">
-<h2>
-Preferences</h2>
-<p CLASS="Head">
-Import preferences from the local file system.</p>
-<!-- PWDOC need a new screenshot for the Import preferences wizard -->
-  <p CLASS="Head"> <img src="../images/Image262_import_preferences.png" 
-   alt="Import Preferences wizard page" width="431" height="491" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - Preferences Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-From preference file</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The file from which to import preferences.&nbsp; Select a previous file from the
-drop down combo or Browse to select the file in the file system.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Import All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Import all of the preferences.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;checked&gt;</P>
-</TD>
-</TR>
-
-<TR>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Choose specific preferences to import</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Choose from the preferences contained in the file, like CVS connection 
-preferences or JRE preferences.</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">&nbsp;
-</P>
-</TD>
-</TR>
-
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all files and folders for import.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-
-
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic">
-<h2>
-Team Project Set</h2>
-<p CLASS="Head">
-Imports a description of the repository and version control information for a set of projects.
-This allows you to synchronize correctly with the appropriate project state in your repository.
-</p>
-  <P>&nbsp;<img src="../images/Image265_team_project.png" alt="Team project set import wizard page" border="0" > 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Import - Team Project Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-File name</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name of the team project set export file</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-71.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-71.htm
deleted file mode 100644
index 4db3c05..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-71.htm
+++ /dev/null

@@ -1,659 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Export wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Export wizard</H1>
-<P CLASS="Para">
-This wizard help you export resources from the Workbench.</P>
-<P CLASS="Para">
-When the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Export wizard</b></a>
-first comes up, you must choose what type of export to
-do. To assist in locating a particular wizard, 
-the text field can be used to show only the wizards that match the entered text. </P>
-<P CLASS="Para"> <img src="../images/Image264_export_sel.png" alt="Export selection page" border="0"></P>
-
-
-<DIV CLASS="Topic">
-  <h2>Ant Buildfiles</h2>
-  <p CLASS="Head">Generates Ant buildfiles based on the configuration 
-     of the Java projects.</p>
-     <P>&nbsp;<img src="../images/Image266_export_ant.png" 
-     alt="ant buildfile export"  border="0"> </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Ant Buildfiles Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select the projects to use to generate the buildfiles</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project (and resources within that project) to use to generate the 
-buildfiles.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Java projects selected.</P>
-</TD>
-</tr>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Check all resources for export.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-N/A</P>
-</TD>
-</tr>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-N/A</P>
-</TD>
-</tr>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Check projects for Ant compatibility</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Check if the source directories of the projects have cycles or if there are dependencies between them that do not conform with the classpath order and therefore functional Ant buildfiles cannot be created.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-On</P>
-</TD>
-</tr>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create target to compile project using Eclipse compiler</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Add an Ant target to the buildfile that will compile the project using the Eclipse compiler.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-On</P>
-</TD>
-</tr>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Name for Ant buildfile</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name to use for the generated Ant buildfile.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-build.xml</P>
-</TD>
-</tr>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-JUnit output directory</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The name of the directory where the generated JUnit reports are placed after the build.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-junit</P>
-</TD>
-</tr>
-
-</TBODY>
-</TABLE>
-</DIV> 
-<DIV CLASS="Topic">
-  <h2> Archive File</h2>
-  <p CLASS="Head">Choose this option to export files to an archive file.</p>
-  <P>&nbsp;<img src="../images/Image266_export_zip.png" alt="ZIP file export" border="0"> 
-  </P>
-<P>&nbsp;
-</P>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-    Export - Archive File Options 
-    </CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<tr>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select resources to export</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project (and resources within that project) to export to an archive.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project holding the selected resource</P>
-</TD>
-</tr>
-<TR>
-<TD COLSPAN="1">
-<P CLASS="Para">
-Select Types...</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para"> Dialog to select which file types to export.&nbsp; Use this to 
-            restrict the export to only certain file types.</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Check off all resources for export.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-        <TD COLSPAN="1"> Archive File </TD>
-<TD COLSPAN="1">
-The path and name of an archive file into which the resources will be exported.&nbsp; Type the path,
-select a previous path from the drop down list, or Browse to select a path and file name on the file system.
-</TD>
-        <TD COLSPAN="1"> The archive file of the previous export, or &lt;blank&gt;. 
-        </TD>
-</TR>
-<TR>
-        <TD COLSPAN="1"> Zip file</TD>
-<TD COLSPAN="1">
-Export  the file in zip format</TD>
-        <TD COLSPAN="1"> true</TD>
-</TR>
-<TR>
-        <TD COLSPAN="1"> Tar file</TD>
-<TD COLSPAN="1">
-Export  the file in tar format</TD>
-        <TD COLSPAN="1"> true</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Compress the contents of the file
-</TD>
-<TD COLSPAN="1">
-Compresses the contents (resources selected to be exported) in the archive that
-is created.
-</TD>
-<TD COLSPAN="1">
-On
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing file without warning
-</TD>
-<TD COLSPAN="1">
-If the specified archive already exists in the file system, you will be prompted
-to overwrite the file.&nbsp; If you do not want to be prompted turn this option
-on.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create directory structure for files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system as it exists in the Workbench. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Off</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create only selected directories</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system only for selected folders. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">On</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-<DIV CLASS="Topic">
-<h2>File System</h2>
-<p CLASS="Head">
-If you choose this option, you will export files to the file system.</p>
-  <p CLASS="Head"> <img src="../images/Image265_export_file.png" alt="Export file system" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Export - File System Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select resources to export</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project (and resources within that project) to export to the file
-system.&nbsp;</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project holding the selected resource</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select Types...</P>
-</TD>
-        <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Dialog 
-            to select which file types to export.&nbsp; Use this to restrict the 
-            export to only certain file types.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Checks off all resources for export.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Deselect All</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Uncheck all resources.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<i>N/A</i></P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Directory
-</TD>
-<TD COLSPAN="1">
-The directory on the file system into which the resources will be exported.&nbsp; Type the path,
-select a previous export path from the drop down list, or Browse to select a path.
-</TD>
-<TD COLSPAN="1">
-The directory of the last export, or &lt;blank&gt;
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-Overwrite existing files without warning
-</TD>
-<TD COLSPAN="1">
-Determines whether exporting a resource should silently overwrite a resource
-which already exists in the file system. If this option is off, you will be
-prompted before a given file is overwritten, in which case you can either
-overwrite the file, skip it, or cancel the export.
-</TD>
-<TD COLSPAN="1">
-Off
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create directory structure for files</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system as it exists in the Workbench. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Off</P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create only selected directories</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Create hierarchy (folder) structure in the file system only for selected folders. </P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">On</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-
-
-
-<h2>
-</h2>
-
-<h2>Preferences</h2>
-  <p class="Head">Export preferences to the local file system.</p>
-     <p>&nbsp;<img src="../images/Image266_export_preferences.png" alt="Preferences export wizard" width="470" height="550" border="0"> </p>
-<p>&nbsp;
-</p>
-<table border="1" cellspacing="0">
-<caption>
-    Export - Preference Options 
-    </caption>
-<thead>
-<tr>
-<th rowspan="1" colspan="1">
-<p class="Para">
-Option</p>
-</th>
-<th rowspan="1" colspan="1">
-<p class="Para">
-Description</p>
-</th>
-<th rowspan="1" colspan="1">
-<p class="Para">
-Default</p>
-</th>
-</tr>
-</thead>
-<tbody>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Export All</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Export all of the preferences in this session.</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-&lt;checked&gt;</p>
-</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Choose specific preferences to export</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Select preferences from this session to export, like
-CVS repository preferences.</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-&lt;disabled&gt;</p>
-</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Select All</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Select all of the available preferences.</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">&nbsp;
-</p>
-</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Deselect All</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Clear all of the available preferences.</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">&nbsp;
-</p>
-</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-To preference file</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-A file on the file system to store the preferences.
-Type the file, select a previous export file
-from the drop down list, or Browse to select a file.</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-&lt;blank&gt;</p>
-</td>
-</tr>
-
-<tr>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Overwrite existing files without warning</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-Overwrite a pre-existing file.</p>
-</td>
-<td rowspan="1" colspan="1" valign="top" align="left">
-<p class="Para">
-&lt;unchecked&gt;</p>
-</td>
-</tr>
-
-
-</tbody>
-</table>
- 
-<DIV CLASS="Topic">
-<h2>
-Team Project Set</h2>
-<p CLASS="Head">
-Exports a description of the repository and version control information for a set of projects.
-This allows you to synchronize those projects correctly in a different workspace.
-</p>
-  <p CLASS="Head"> <img src="../images/Image268_export_team.png" alt="Export team project set page" border="0" ></p>
-<p CLASS="Head">&nbsp;
-</p>
-
-<TABLE BORDER="1" cellspacing="0">
-<CAPTION>
-Export - Team Project Set Options</CAPTION>
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-</THEAD>
-<TBODY>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Select projects</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The project(s) to export to the team project set file.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-The selected projects</P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1">
-<P CLASS="Para">
-File name</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-The path and name of the file to export to.</P>
-</TD>
-<TD COLSPAN="1">
-<P CLASS="Para">
-&lt;blank&gt;</P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-</DIV>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related pages" ><br>
-<a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/ref-export-jar.htm">JAR Export Wizard</a><br>
-<a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/ref-export-javadoc.htm">Export Javadoc Wizard</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-72.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-72.htm
deleted file mode 100644
index ef8820d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-72.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation, Red Hat, and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Preferences</title>
-</head>
-<body>
-
-<h1>Preferences</h1>
-
-<p>Use the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Preferences</b></a> dialog pages to set how you want Eclipse to 
-operate. 
-</p>
-
-<p>You can browse the Preferences dialog pages by looking through all the titles 
-in the left pane or search a smaller set of titles by using the filter field at 
-the top of the left pane. 
-The results returned by the filter will match both Preference page titles and
-keywords such as "appearance" and "java". 
-However, to find specific functions you may have to search the online help 
-instead.
-</p>
-
-<p>The arrow controls in the upper-right of the right pane 
-<img src="../images/backward_nav.png" alt="Navigate backwards image">
-<img src="../images/forward_nav.png" alt="Navigate forwards image"> 
-enable you to navigate through previously viewed pages. 
-To return to a page after viewing several pages, 
-click the drop-down arrow to display a list of your recently viewed 
-preference pages.
-</p> 
-
-<p>The preferences dialog displaying the <b>General</b> preferences:</p> 
-<p><img src="../images/Image217_pref_wb.png" alt="Preference dialog" border="0" ></p>
-
-<p>Preference pages contributed by plug-ins are included in this dialog.</p> 
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="ref-23.htm">Workbench window layout</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-73.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-73.htm
deleted file mode 100644
index fefed13..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-73.htm
+++ /dev/null

@@ -1,216 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright"
-	content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1"
-	TYPE="text/css">
-<title>Project Explorer view</title>
-<script language="JavaScript"
-	src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Project Explorer view</H1>
-<P CLASS="Intro">This view provides a hierarchical view of the
-artifacts in the Workbench, which is customized by the specific
-configuration of your Workbench.</p>
-<P CLASS="Para">A typical Project Explorer with only the Java
-Development Tools (JDT) installed looks similar to the Package Explorer:</P>
-<P CLASS="Para"><img src="../images/Image275_project_explorer.png"
-	alt="Project Explorer View" border="0"></P>
-<p CLASS="Head">To add the Project Explorer view to the current
-perspective, click <a class="command-link"
-	href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.navigator.ProjectExplorer)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"> <b>Window
-&gt; Show View &gt; Other... &gt; General &gt; Project Explorer</b></a>.</p>
-<P CLASS="Para">&nbsp;</P>
-<h2>Toolbar</h2>
-<DIV CLASS="Topic"></DIV>
-<H3>Collapse All</H3>
-<P>This command collapses the tree expansion state of all resources
-in the view.</P>
-<H3>Link with Editor</H3>
-<P>This command toggles whether the Project Explorer selection is
-linked to the active editor. When this option is selected, changing the
-active editor will automatically update the Project Explorer selection to the
-resource being edited.</P>
-<P><BR>
-</P>
-<H2>Menus</H2>
-<P>Click the black upside-down triangle icon to open a menu of items
-specific to the Project Explorer. Right-click inside the view to open a
-context menu.&nbsp;</P>
-<H3>Select Working Set</H3>
-<P>Opens the <B>Select Working Set</B> dialog to allow selecting a
-working set for the Project Explorer.</P>
-<H3>Deselect Working Set</H3>
-<P>Deselects the current working set.</P>
-<H3>Edit Active Working Set</H3>
-<P>Opens the <B>Edit Working Set</B> dialog to allow changing the
-current working set.</P>
-<DIV CLASS="Topic">
-<h3>Customize View</h3>
-<P CLASS="Para">This command allows you to change the view for your
-specific needs. You may select filters to apply to the view so that you
-can show or hide various artifacts as needed. The default filters
-available with the Java development tools (JDT) is shown below:</P>
-<P CLASS="Para"><img src="../images/Image276_available_filters.png"
-	alt="Available Customizations &gt; Filters dialog" border="0"></P>
-<P CLASS="Para">You may also choose the types of content for the view
-to show as well. The default content extensions available with the
-Java development tools (JDT) is shown below, but your specific extensions
-will be determined by your workbench configuration:</P>
-<P CLASS="Para"><img src="../images/Image276_available_content.png"
-	alt="Available Customizations &gt; Content dialog" border="0"></P>
-</DIV>
-<H3>Link with Editor</H3>
-<P>See the toolbar item description above.</P>
-<P><BR>
-In addition to these menu items, the Project Explorer menu shows a list of
-recently used working sets that have been selected in the view.</P>
-<P><BR>
-</P>
-<h2>Context menu</h2>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">New</H3>
-<P CLASS="Para">This command allows you to create a new resource in
-the Workbench. Select the type of resource to create from the submenu.</P>
-</DIV>  
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Copy</H3>
-<P CLASS="Para">This command copies the selected resource to the
-clipboard.</P>
-</DIV>
-<H3>Paste</H3>
-<P>This command pastes resources on the clipboard into the selected
-project or folder. If a resource is selected the resources on the
-clipboard are pasted as siblings of the selected resource.</P>
-<h3 CLASS="Head">Delete</H3>
-<P CLASS="Para">This command deletes the selected resource from the
-workspace.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Move</H3>
-<P CLASS="Para">This command moves the selected resource to another
-location. A dialog will appear, prompting for the destination location
-to which the resource will be moved.&nbsp;&nbsp;</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Rename</H3>
-<P CLASS="Para">This command allows you to specify a new name for
-the selected resource.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Import</H3>
-<P CLASS="Para">This command opens the import wizard and allows you
-to select resources to import into the Workbench.</P>
-</DIV>
-
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Export</H3>
-<P CLASS="Para">This command opens the export wizard and allows you
-to export resources to an external location.</P>
-</DIV>
-
-<h3 CLASS="Head">Refresh</H3>
-<P CLASS="Para">This command refreshes the Workbench's view of the
-selected resource and its children. For example, this is used when you
-create a new file for an existing project outside the Workbench and want
-the file to appear in the Project Explorer view.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Close Project</H3>
-<P CLASS="Para">The close project command is visible when an open
-project is selected. This command closes the selected project.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Close Unrelated Projects</H3>
-<P CLASS="Para">This command will close any project which are
-unrelated to the selected project.</P>
-</DIV>
-<H3>Open Project</H3>
-<P>The open project command is visible when a closed project is
-selected. This command opens the selected project.</P>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Team</H3>
-<p CLASS="Head">Menu items in the Team sub-menu are related to
-version control management and are determined by the version control
-management system that is associated with the project. Eclipse provides
-the special menu item<b> Share Project...</b> for projects that are not
-under version control management. This command will present a wizard
-that allows you to choose to share the project with any version control
-management systems that has been added to Eclipse. Eclipse ships with
-support for CVS.</p>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Compare With</H3>
-
-<P CLASS="Para">Commands on the Compare With sub-menu allow you to
-do one of the following types of compares:</P>
-<UL CLASS="UnorderedList">
-	<LI CLASS="Item">Compare two or three selected resources with each
-	other</LI>
-	<LI CLASS="Item">Compare the selected resource with remote
-	versions (if the project is associated with a version control
-	management system).</LI>
-	<LI CLASS="Item">Compare the selected resource with a local
-	history state</LI>
-</UL>
-
-<P CLASS="Para">After you select the type of compare you want to do,
-you will either see a compare editor or a compare dialog. In the compare
-editor, you can browse and copy various changes between the compared
-resources.&nbsp; In the compare dialog, you can only browse through the
-changes.&nbsp;&nbsp;</P>
-
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Replace With</h3>
-<P CLASS="Para">Commands on the Replace With sub-menu allow you to
-replace the selected resource with another state from the local history.
-If the project is under version control management, there may be
-additional items supplied by the version control management system as
-well.</P>
-</DIV>
-<DIV CLASS="Topic">
-<h3 CLASS="Head">Properties</H3>
-<P CLASS="Para">This command displays the properties of the selected
-resource. The kinds of properties that are displayed depend on what type
-of resource is selected. Resource properties may include (but are not
-limited to):</P>
-<UL CLASS="UnorderedList">
-	<LI CLASS="Item">Path relative to the project in which it is held</LI>
-	<LI CLASS="Item">Type of resource</LI>
-	<LI CLASS="Item">Absolute file system path, or name of path
-	variable when using linked resources</LI>
-	<LI CLASS="Item">Resolved path variable when using a path variable
-	for a linked resource</LI>
-	<LI CLASS="Item">Size of resource</LI>
-	<LI CLASS="Item">Last modified date</LI>
-	<LI CLASS="Item">Read-only status</LI>
-	<LI CLASS="Item">Derived resource status</LI>
-	<LI CLASS="Item">Execution arguments, if it is an executable
-	resource</LI>
-	<LI CLASS="Item">Program launchers, if it is launchable</LI>
-	<LI CLASS="Item">Project dependencies, if any</LI>
-</UL>
-</DIV>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts">
-<br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> <br>
-<A HREF="../concepts/concepts-29.htm">Three-way compare</A> <br>
-<a href="../concepts/concepts-13.htm">Linked resources</a></p>
-
-<p><img border="0" src="../images/ngrelr.png"
-	alt="Related references"> <br>
-<a href="ref-25.htm">Compare editor</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-8.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-8.htm
deleted file mode 100644
index cfe40d3..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-8.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation, Red Hat, and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page."/>
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<meta http-equiv="Content-Style-Type" content="text/css"/>
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"/>
-<title>Minimizing data loss from crashes</title>
-
-</head>
-<body bgcolor="#ffffff">
-<h1 class="Head">Minimizing data loss from crashes</h1>
-<p class="Intro">
-The Workbench periodically saves a snapshot in order to reduce the risk of
-losing data due to crashes.
-The default period between saves is 5 minutes, but you can change this
-from the <a href="ref-9.htm">Workspace preferences page</a>
-(<b>Window &gt; Preferences &gt; General &gt; Workspace</b>).
-From that page you can also set Eclipse to save all modified resources before 
-a manual build. 
-</p>
-
-<p>Previously created projects and saved editor data are never lost as they are 
-written to disk immediately upon save. However, there is a risk of data loss in these areas:
-</p>
-
-<ul class="UnorderedList">
-<li class="Item">
-Unsaved data in open editors may be lost, depending on the editor implementation.</li>
-<li class="Item">
-Bookmarks and tasks might be lost.</li>
-<li class="Item">
-If a crash occurs during CVS synchronization, the Workbench may be out of sync.
-You can check by performing the synchronize operation again.</li>
-</ul>
-
-<p>Developers of plug-ins can also choose to participate in the autosave 
-lifecycle and have the Workbench also save the state of their plug-ins.
-See "<b><i>Workspace save participation</i></b>" in the 
-<b><i>Platform Plug-in Development Guide</i></b> for details.
-</p>
-
-<pre>
-&lt;enablement&gt;
-   &lt;systemTest property="osgi.os" value="linux"/&gt;
-&lt;/enablement&gt;
-</pre>
-<h2>Restarting after a crash on Linux</h2>
-
-<p>After a crash you may find that Eclipse will not open because it 
-has (erroneously) detected that your workspace is in use. 
-To remedy this, enter:
-</p>
-
-<pre>
-rm workspace/.metadata/.lock
-</pre>
-
-<p>You can now restart Eclipse.</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"/>
-<br/><a href="ref-9.htm">Workspace preferences page</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-9.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-9.htm
deleted file mode 100644
index e553f30..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-9.htm
+++ /dev/null

@@ -1,99 +0,0 @@
-<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css">
-   <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
-   <title>Workspace</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-</head>
-<body bgcolor="#FFFFFF">
-
-<h1 CLASS="Head"> Workspace</h1>
-<p CLASS="Head">On the
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Workspace</strong></a>
-
-  preference page, you can manage 
-  various IDE-specific workspace preferences settings in the Workbench. </p>
-
-<table width="75%" border="1">
-  <tr> 
-    <td><strong>Option</strong></td>
-    <td><strong>Description</strong></td>
-    <td><strong>Default</strong></td>
-  </tr>
-  <tr> 
-    <td>Build automatically</td>
-    <td>If this option is turned on, then the Workbench will perform an automatic 
-      build whenever a modified resource is saved.</td>
-    <td>On</td>
-  </tr>
-  <tr> 
-    <td>Save automatically before build</td>
-    <td>If this option is selected, when a manual build is performed the Workbench 
-      will automatically save all resources that have been modified since the 
-      last build was performed.<br></td>
-    <td>Off<br></td>
-  </tr>
-  <tr> 
-    <td>Always close unrelated projects without prompt</td>
-    <td>If this option is selected, unrelated projects will be closed without prompt.
-    <br>Uncheck this option if you want to be asked first.
-     </td>
-    <td>Off</td>
-  </tr>
-  <tr> 
-    <td>Workspace save interval (in minutes) </td>
-    <td>This number indicates how often the state of the workspace is automatically 
-      saved to disk.</td>
-    <td>5</td>
-  </tr>
-  <tr> 
-    <td>Refresh automatically</td>
-    <td><p>If this option is turned on then the workspace resources will be synchronized 
-        with their corresponding resources in the file system automatically.</p>
-      <p><strong>Note</strong>: This can potentially be a lengthy operation depending 
-        on the number of resources you have in your workspace. </p></td>
-    <td>Off </td>
-  </tr>
-  <TR> 
-    <TD COLSPAN="1" valign="top" align="left">Open referenced projects when a 
-      project is opened</TD>
-    <TD COLSPAN="1" valign="top" align="left">If this option is enabled opening 
-      a project will also open and closed projects it references. Select prompt 
-      if you wish to be asked first.</TD>
-    <TD COLSPAN="1" valign="top" align="left">Prompt</TD>
-  </TR>
-  <TR> 
-    <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Text 
-        file encoding</P></TD>
-    <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> Use 
-        this option to specify the encoding to use when saving text files in editors. 
-      </P></TD>
-    <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Default 
-        (CP1252)</P></TD>
-  </TR>
-  <TR> 
-    <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Text 
-        File line delimiter</P></TD>
-    <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> Use 
-        this option to specify the line delimiter to use for new text files. <strong>Note:</strong> 
-        This will generally not effect the file line delimiter for<br>
-        existing files.</P></TD>
-    <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Default 
-      </P></TD>
-  </TR>
-</table>
-<p>&nbsp;</p><p>Here is what the <strong>Workspace</strong> preferences page looks like:</p> 
-<p><img src="../images/Image209_workspace.png" alt="Preference dialog" border="0" ></p>
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm
deleted file mode 100644
index 577e73d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antcodeassist.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Content Assist Preferences</title>
-
-</HEAD>
-<body>
-<h1> Ant Content Assist Preferences</h1>
-<p>
-	The following preferences can be changed on the
-	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntCodeAssistPreferencePage)")'>
-	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-	<strong>Ant &gt; Editor &gt; Content Assist</strong></a> preference page.
-</p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  <tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td width="25%"> Insert single proposals automatically</td>
-      <td>This option allows you to automatically insert single proposals.</td>
-      <td width="8%" align="center">On</td>
-    </tr>
-    <tr> 
-      <td width="25%">Provide proposals for user defined tasks (may lock referenced JAR files)</td>
-      <td>This option allows you to provide proposals for user defined tasks.</td>
-      <td width="8%" align="center">On</td>
-    </tr>
-    <tr> 
-      <td width="25%">Enable auto activation</td>
-      <td >This option enables and disables auto activation.</td>
-      <td width="8%" align="center">On</td>
-    </tr>
-    <tr> 
-      <td width="25%">Auto activation delay</td>
-      <td>This option allows you to set the auto activation delay.</td>
-      <td width="8%" align="center">500</td>
-    </tr>
-    <tr> 
-      <td width="25%">Auto activation triggers</td>
-      <td >This option allows you to set the auto activation triggers.</td>
-      <td width="8%" align="center">&lt;${</td>
-    </tr>
-    <tr> 
-      <td width="25%"> Code assist color options</td>
-      <td> This option allows you to set the color for the completion proposal background and foreground.</td>
-      <td width="8%" align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-
-<P CLASS="Para">Here is what the Ant Code Assist preference page looks like.</P>
-<P CLASS="Para">
-<img src="../images/ant_code_assist.png" alt="Ant Code Assist preference page" border="0"></P>
-
-<P CLASS="Para"> <img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-	<a href="../concepts/concepts-antsupport.htm">Ant support</a> 
-</P>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-	<a href="ref-anteditor.htm">Ant Editor</a><br>
-	<a href="../reference/ref-antprefs.htm">Ant preference page</a><br>
-	<a href="ref-anteditorprefs.htm">Ant editor preferences</a><br>
-	<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-	<a href="../reference/ref-antformatter.htm">Ant formatter preferences</a><br>
-	<a href="../reference/ref-anttemplates.htm">Ant templates preferences</a>
-</p>
-</body>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm
deleted file mode 100644
index 4e9efa4..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditor.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Ant editor</title> 
-</head>
-<body>
-     
-<h1> Ant editor</h1>
-     
-<p>The Ant editor provides specialized features for editor Ant buildfiles. 
-Associated with the editor is a Ant buildfile specific <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/ref-view-outline.htm">Outline view</a></b> which shows the structure of the Ant build file. 
-It is updated as you edit the buildfile</p>
-
-The editor includes the following features:
-
-<ul>
-  <li>Syntax highlighting</li>
-
-  <li>Content/code assist (including Ant specific templates)</li>
-
-  <li>Annotations</li>
-</ul> 
-<p>
-	The most common way to invoke the Ant editor is to open an Ant buildfile from 
-  	one of the navigation views or <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/ref-view-package-explorer.htm">Package explorer</a></b> using pop-up menus or by clicking 
-  	the file (single or double-click depending on your preference settings).
-</p>  
-<p>
-	<img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-    <a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-    <a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-	<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a><br>
-	<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-	<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-	<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a></p>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-    <a href="ref-anteditorprefs.htm">Ant editor preferences</a><br>
-    <a href="ref-anticons.htm">External Tools and Ant icons</a><br>
-    <a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/ref-view-outline.htm">Outline view</a><br>
-    <a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/ref-view-package-explorer.htm">Package explorer</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm
deleted file mode 100644
index 1c360ec..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anteditorprefs.htm
+++ /dev/null

@@ -1,208 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Editor Preferences</title>
-
-</HEAD>
-<BODY>
-<H1 CLASS="Head">Ant Editor Preferences</H1>
-<p>The following preferences can be changed on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntEditorPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Ant &gt; Editor</strong></a> page.</p>
-<h2>Appearance options</h2>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td> Mark occurrences of the selected element in the current buildfile</td>
-      <td>This option allows you to select elements and mark occurrences in the current buildfile.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Keep marks when selection changes</td>
-      <td>This option allows you to keep marks when the selection changes.</td>
-      <td align="center">On</td>
-    </tr>
-  </tbody>
-</table>
-<P>Here is what the Appearance tab of the Ant editor preference page 
-  looks like.
-</P>
-<P>
-	<img src="../images/ant_editor_appearance.png" alt="Ant editor appearance preference page" border="0">
-</P>
-
-<h2>Syntax options</h2>
-<p>The Foreground options located on the Syntax tab, allow you to format the font 
-  of comments, constant strings, DTD declarations, processing instructions, tags 
-  and text. The Preview pane allows you to see your changes before you apply them. 
-  </p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Foreground</td>
-      <td>This table is used to change the foreground colour of the selected element (within the table).</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Colour</td>
-      <td>This option allows you to select a colour to set for the selected foreground element.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Bold</td>
-      <td>This option allows you to set the bold state of the selected foreground element.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Italic</td>
-      <td>This option allows you to set the italic state of the selected foreground element.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Preview</td>
-      <td>Shows you a preview of the changes made to the selected foreground element.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-Here is what the Syntax tab of the Ant editor preference page looks like.
-</p>
-<p><img src="../images/ant_editor_syntax.png" alt="Ant editor syntax preference page" border="0"></p>
-     
-<h2>Problems options</h2>
-<p>The Problems options allow you to ignore all buildfile problems or to specify 
-  the specific files that you do not want the Ant Editor to check for problems. 
-  You can also set the severity level for buildfile problems such as task configuration, 
-  an incomplete classpath, property setting tasks, import tasks, and security 
-  problems. </p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Ignore all buildfile problems</td>
-      <td>This option allows you to ignore all buildfile problems by default.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Names</td>
-      <td>This option allows you to specify the names of buildfiles that will NOT be checked for problems in the Ant editor.
-      Entries in this field are comma-separated.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Task configuration</td>
-      <td>This option allows you to set the severity for task configuration problems.</td>
-      <td align="center">Ignore</td>
-    </tr>
-    <tr> 
-      <td>Incomplete classpath</td>
-      <td>This option allows you to set the severity for incomplete classpath problems.</td>
-      <td align="center">Warning</td>
-    </tr>
-    <tr> 
-      <td>Property setting tasks</td>
-      <td>This option allows you to set the severity for property setting tasks problems.</td>
-      <td align="center">Ignore</td>
-    </tr>
-    <tr> 
-      <td>Import tasks</td>
-      <td>This option allows you to set the severity for import tasks problems.</td>
-      <td align="center">Warning</td>
-    </tr>
-    <tr> 
-      <td>Security problems</td>
-      <td>This option allows you to set the severity for security problems.</td>
-      <td align="center">Warning</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-Here is what the Problems tab of the Ant editor preference page looks like.
-</p>
-<p><img src="../images/ant_editor_problems.png" alt="Ant editor Problems preference page" border="0"></p>
-<h2>Folding options</h2>
-<p>The Folding options allow you to enable folding when opening a new editor and 
-  to specify which region types should be folded.</p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Enable folding when opening a new editor</td>
-      <td>This option allows you to always enable folding for any newly created Ant editors.</td>
-      <td align="center">On</td>
-    </tr>
-    <tr> 
-      <td>DTD blocks</td>
-      <td>This option allows you to always have DTD blocks in a buildfile automatically folded when opened in an Ant editor.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Comments</td>
-      <td>This option allows you to always have comments in a buildfile automatically folded when opened in an Ant editor.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Defining tasks</td>
-      <td>This option allows you to always have defining tasks in a buildfile automatically folded when opened in an Ant editor.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Targets</td>
-      <td>This option allows you to always have targets in a buildfile automatically folded when opened in an Ant editor.</td>
-      <td align="center">Off</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-Here is what the Folding tab of the Ant editor preference page looks like.
-</p>
-<p><img src="../images/ant_editor_folding.png" alt="Ant editor Folding preference page" border="0"></p>
-
-<p> <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-	<a href="../concepts/concepts-antsupport.htm">Ant support</a> 
-</p>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-	<a href="ref-anteditor.htm">Ant Editor</a><br>
-	<a href="../reference/ref-antprefs.htm">General Ant preferences</a><br>
-	<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-	<a href="../reference/ref-antformatter.htm">Ant formatter preferences</a><br>
-	<a href="../reference/ref-anttemplates.htm">Ant templates preferences</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm
deleted file mode 100644
index 64357fd..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antformatter.htm
+++ /dev/null

@@ -1,73 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Formatter Preferences</title>
-
-</HEAD>
-<BODY>
-<h1>Ant Formatter Preferences</h1>
-<p>
-	The following preferences can be changed on the
-  	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntCodeFormatterPreferencePage)")'>
-  	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  	<strong>Ant &gt; Editor &gt; Formatter</strong></a> preference page.
-</p>
-<table border="1" cellspacing="0" style="width: 80%;">
-  <thead>
-  <tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Indentation - Tab size</td>
-      <td>This option controls how many spaces are used to display tabs in the Ant editor.</td>
-      <td align="center">4</td>
-    </tr>
-    <tr> 
-      <td>Line Wrapping - Maximum line width</td>
-      <td>This option allows you to set the maximum line width for the Ant editor.</td>
-      <td align="center">80</td>
-    </tr>
-    <tr> 
-      <td>Line Wrapping - Wrap long element tags</td>
-      <td>This option allows you to wrap long element tags. The Preview pane will display a sample buildfile 
-          with this option.</td>
-      <td align="center">Off</td>
-    </tr>
-    <tr> 
-      <td>Line Wrapping - Align final '&gt;' in multi-line element tags</td>
-      <td>This option allows you 
-          to align the final '&gt;' in multi-line element tags. The Preview pane 
-          will display a sample buildfile with this option.</td>
-      <td align="center">Off</td>
-    </tr>
-  </tbody>
-</table>
-
-<P>Here is what the Ant Formatter preference page looks like.</P>
-<P>
-	<img src="../images/ant_formatter.png" alt="Ant Formatter preference page" border="0">
-</P>
-<P> <img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  	<a href="../concepts/concepts-antsupport.htm">Ant support</a> 
-</P>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-	<a href="ref-anteditor.htm">Ant Editor</a><br>
-	<a href="../reference/ref-antprefs.htm">General Ant preferences</a><br>
-	<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-	<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a><br>
-	<a href="../reference/ref-anttemplates.htm">Ant templates preferences</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm
deleted file mode 100644
index 00a9d99..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anticons.htm
+++ /dev/null

@@ -1,260 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-	<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-	<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-	<meta http-equiv="Content-Style-Type" content="text/css">
-	<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-    <title>External Tools and Ant icons</title>
-</head>
-<body>
-	<h1>External Tools and Ant icons</h1>
-    <h2>Objects</h2>
-    <table cellspacing="0" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/ant_buildfile.png"  alt="Ant buildfiles"><br>
-          </td>
-          <td valign="top">
-            Ant buildfiles<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/ant_target_err.png"  alt="Ant target containing an error"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant target containing an error<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/invalid_build_tool.png"  alt="Invalid project builder"><br>
-          </td>
-          <td valign="top" width="90%">
-            Invalid project builder<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/defaulttarget_obj.png"  alt="Default target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Default target<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/targetpublic_obj.png"  alt="Ant target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Public Ant target (target with description)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/targetinternal_obj.png"  alt="Ant internal target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant internal target (target with no description)<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/jar_l_obj.png"  alt="Jar file"><br>
-          </td>
-          <td valign="top" width="90%">
-            Jar file<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/property_obj.png"  alt="Ant property"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant property<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/task_obj.png"  alt="Ant task"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant task<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/type.png"  alt="Ant type"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant type<br>
-          </td>
-        </tr>
-         <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/import_obj.png"  alt="Ant import task"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant import task<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/macrodef_obj.png"  alt="Ant macrodef task"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant macrodef task<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-    <h2>
-      Launch configurations
-    </h2>
-    <table cellspacing="0" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/ctool16/external_tools.png"  alt="Launch external tool"><br>
-          </td>
-          <td valign="top" width="90%">
-            Launch external tool<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/ant.png"  alt="Ant launch configuration"><br>
-          </td>
-          <td valign="top">
-            Ant launch configuration<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/ctool16/external_tools.png"  alt="Program launch configuration"><br>
-          </td>
-          <td valign="top" width="90%">
-            Program launch configuration<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/main_tab.png"  alt="Main tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Main tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/refresh.png"  alt="Refresh tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Refresh tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/build_tab.png"  alt="Build tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Build tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/ant_targets.png"  alt="Targets tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Targets tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/prop_ps.png"  alt="Properties tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Properties tab<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/obj16/classpath.png"  alt="Classpath tab"><br>
-          </td>
-          <td valign="top" width="90%">
-            Classpath tab<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-   <br>
-    <h2>
-      Ant View
-    </h2>
-    <table cellspacing="0" border="1" width="40%">
-      <tbody>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/cview16/ant_view.png"  alt="Ant view"><br>
-          </td>
-          <td valign="top" width="90%">
-            Ant view<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/add_co.png"  alt="Add buildfile"><br>
-          </td>
-          <td valign="top" width="90%">
-            Add buildfile<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/search.png"  alt="Add buildfiles with search"><br>
-          </td>
-          <td valign="top" width="90%">
-            Add buildfiles with search<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/run_tool.png"  alt="Run selected buildfile or selected target"><br>
-          </td>
-          <td valign="top" width="90%">
-            Run selected buildfile or selected target<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/remove_co.png"  alt="Remove selected buildfiles"><br>
-          </td>
-          <td valign="top" width="90%">
-            Remove selected buildfiles<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png"  alt="Remove all buildfiles"><br>
-          </td>
-          <td valign="top" width="90%">
-            Remove all buildfiles<br>
-          </td>
-        </tr>
-        <tr>
-          <td valign="middle" align="center">
-            <img src="../images/org.eclipse.ui.externaltools/clcl16/filter_internal_targets.png"  alt="Hide Internal Targets"><br>
-          </td>
-          <td valign="top" width="90%">
-            Hide Internal Targets<br>
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <br>
-  </body>
-</html>
-

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm
deleted file mode 100644
index 9a2dd07..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antprefs.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>General Ant Preferences</title>
-</head>
-<body>
-
-<h1>General Ant Preferences</h1>
-
-<p>
-	You can change the following preferences on the
-	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntPreferencePage)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"><strong>Ant</strong></a> preference page.
-</p>
-
-<table border="1" cellspacing="0" cellpadding="5" width="80%">
-	<thead>
-		<tr>
-			<th width="25%">Option</th>
-			<th>Description</th>
-			<th width="8%">Default</th>
-		</tr>
-	</thead>
-	<tbody>
-		<tr >
-			<td>Names</td>
-			<td>Configures the buildfiles that Ant's "-find" emulation searches for.</td>
-			<td align="center">build.xml</td>
-		</tr>
-		<tr >
-			<td>Separate JRE Timeout</td>
-			<td>The time in milliseconds to wait for communication with the Java virtual machine when running an Ant build in a separate Java runtime environment.</td>
-			<td align="center">20000</td>
-		</tr>
-		<tr >
-			<td>Documentation URL</td>
-			<td>Enables you to browse for the applicable documentation URL.</td>
-			<td align="center"><a href="http://ant.apache.org/manual" target="_blank">http://ant.apache.org/manual</a></td>
-		</tr>
-		<tr >
-			<td>Warn when tools.jar is not on the classpath</td>
-			<td>Displays a warning when tools.jar is not on the classpath.</td>
-			<td align="center">On</td>
-		</tr>
-		<tr >
-			<td>Show error dialog when Ant build fails</td>
-			<td>Displays an error message when the Ant build fails.</td>
-			<td align="center">On</td>
-		</tr>
-		<tr >
-			<td>Create problem markers from <code>javac</code> results</td>
-			<td>Create warning and error markers from the build results of an Ant <code>javac</code> task. Marker creation requires that a console is allocated for the build and that the <code>listfiles</code> attribute of the <code>javac</code> task be set to true.</td>
-			<td align="center">Off</td>
-		</tr>
-		<tr >
-			<td>Ant Color Options</td>
-			<td>Configures the colors of the Ant build output.</td>
-			<td align="center">Varies by Ant output</td>
-		</tr>
-	</tbody>
-</table>
-<p>
-	The Ant preference page:
-	<br><br>
-	<img src="../images/ant_prefs.png" alt="Ant preference page" border="0">
-</p>
-<p>
-	<img src="../images/ngrelc.png" alt="Related concepts" border="0"><br>
-	<a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-	<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-	<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a><br>
-	<a href="../reference/ref-antformatter.htm">Ant formatter preferences</a><br>
-	<a href="../reference/ref-anttemplates.htm">Ant templates preferences</a>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm
deleted file mode 100644
index e4cd71e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antruntimeprefs.htm
+++ /dev/null

@@ -1,226 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Ant Runtime Preferences</title>
-
-</HEAD>
-<BODY>
-<h1>Ant Runtime Preferences</h1>
-<p>
-	The following preferences can be changed on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-	<strong>Ant &gt; Runtime</strong></a> preference page.
-</p>
-<h2>Classpath options</h2>
-<p>
-	On the Classpath tab you can add additional classes defining tasks and types to the Ant classpath. New tasks and types
-	can be added to either the Ant Home or the Global Entries section(s). The Contributed Entries section cannot be modified.
-	</p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Add Jars...</td>
-      <td>Allows you to add a <code>jar</code> file from the current workspace to the Ant classpath for the Ant Home and / or Global sections.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Add External Jars...</td>
-      <td>Allows you to add a <code>jar</code> file from the local filesystem to the Ant classpath for the Ant Home and / or Global sections.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Add Folder...</td>
-      <td>Allows you to add a folder from the local filesystem to the Ant classpath for the Ant Home and / or Global sections.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Add Variable...</td>
-      <td>Allows you to add a new classpath variable to the Ant Home and / or Global sections.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Ant Home</td>
-      <td>Allows you to add a new folder to the Ant Home location.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Remove</td>
-      <td>Allows you to remove the selected entry element(s) from the Ant classpath for the Ant Home and / or Global sections.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Up</td>
-       <td>Allows you to move the selected entry element up one space in its listing.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Down</td>
-      <td>Allows you to move the selected entry element down one space in its listing.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-	Here is what the Classpath tab of the Ant Runtime preferences page looks like:
-</p>
-<p>
-	<img src="../images/Image91_ant_prefs_1.png" alt="Ant classpath preference tab" border="0">
-</p>
-<h2>Tasks options</h2>
-<p>
-	On the Tasks tab you can add tasks defined in one of the classes on the Ant classpath.
-</p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Add Task...</td>
-      <td>Allows you to add a new Ant task definition to the runtime.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Edit Task...</td>
-      <td>Allows you to edit an existing Ant task. <br><br>
-      Note: you can only edit tasks that are not contributed (i.e. yellow decorated tasks are contributed 
-      and cannot be edited).</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Remove</td>
-      <td>Allows you to remove an existing Ant task from the runtime. <br><br>
-      Note: you can only remove tasks that are not contributed (i.e. yellow decorated tasks are contributed 
-      and cannot be removed).</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-	Here is what the Tasks tab of the Ant Runtime preferences page looks like:
-</p>
-<p>
-	<img src="../images/Image91_ant_prefs_2.png" alt="Ant tasks preference page" border="0">
-</p>
-<h2>Types options</h2>
-<p>
-	On the Types tab you can add types defined in one of the classes on the classpath.
-</p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Add Type...</td>
-      <td>Allows you to add a new type defined in one of the classes on the Ant classpath.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Edit Type...</td>
-      <td>Allows you to edit an existing type.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Remove</td>
-      <td>Allows you to remove an existing type.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-	Here is what the Types tab of the Ant Runtime preferences page looks like:
-</p>
-<p>
-	<img src="../images/Image91_ant_prefs_3.png" alt="Ant types preference page" border="0" >
-</p>
-<h2>Properties options</h2>
-<p>
-	On the Properties tab you can add properties and property files that will be passed into Ant.
-</p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>Add Property...</td>
-      <td>Allows you to add a new Ant property to the runtime.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Edit Property...</td>
-      <td>Allows you to edit an existing Ant property. <br><br>
-      Note: you can only edit properties that are not contributed (i.e. yellow decorated properties are contributed 
-      and cannot be edited).</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Remove</td>
-      <td>Allows you to remove an existing Ant property from the runtime. <br><br>
-      Note: you can only remove properties that are not contributed (i.e. yellow decorated properties are contributed 
-      and cannot be removed).</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Add Files...</td>
-      <td>Allows you to add a <code>*.properties</code> file from the workspace to be used in the runtime.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Add External...</td>
-      <td>Allows you to add a <code>*.properties</code> file from the local filesystem to be used in the runtime.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Remove</td>
-      <td>Allows you to remove an existing <code>*.properties</code> file from the runtime.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-	Here is what the Properties tab of the Ant Runtime preferences page looks like:
-</p>
-<p>
-	<img src="../images/ant_runtime_properties.png" alt="Ant properties preference page" border="0">
-</p>
-<p>
-	<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-	<a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-	<a href="../reference/ref-antprefs.htm">General Ant preferences</a><br>
-	<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a><br>
-	<a href="../reference/ref-antformatter.htm">Ant formatter preferences</a><br>
-	<a href="../reference/ref-anttemplates.htm">Ant templates preferences</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm
deleted file mode 100644
index 8da3f03..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-anttemplates.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Ant Templates Preference</title>
-</head>
-<body>
-
-<h1>Ant Templates Preferences</h1>
-
-<p>
-	The following preferences can be changed on the 
-	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.TemplatesPreferencePage)")'>
-	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"><strong>Ant &gt; Editor &gt; Templates</strong></a>
-    preference page.
-</p>
-<p> 
-	You can use the Templates preferences to create, edit, remove, import existing templates, restore removed templates and revert 
-    to the default templates. The preview pane enables you to see what your new or 
-    edited template will look like before applying your changes.
-</p>
-<table border="1" cellspacing="0" width="80%">
-  <thead>
-  	<tr> 
-      <th width="25%">Option</th>
-      <th>Description</th>
-      <th width="8%">Default</th>
-    </tr>
-  </thead>
-  <tbody>
-    <tr> 
-      <td>New...</td>
-      <td>Allows you to add a new template.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Edit...</td>
-      <td>Allows you to edit an existing template. Changes to a template can be viewed in the Preview Pane before they are applied.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Remove</td>
-      <td>Allows you to remove and existing template. A removed template can be restored by using Restore Removed or by re-importing the template (if
-      it was imported initially).</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Restore Removed</td>
-      <td>Allows you to add a new classpath variable to the Ant Home and / or Global sections.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Revert to Default</td>
-      <td>Allows you to revert changes to a selected template back to their factory defaults</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Import...</td>
-      <td>Allows you to import template(s) from a selected <code>*.xml</code> file.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-    <tr> 
-      <td>Export...</td>
-       <td>Allows you to export the currently selected set of templates to an <code>xml</code> file in the local filesystem.</td>
-      <td align="center">&nbsp;</td>
-    </tr>
-  </tbody>
-</table>
-<p>
-	Here is what the Ant Templates preference page looks like:
-</p>
-<p>
-	<img src="../images/ant_templates.png" alt="Ant Templates preference page" border="0">
-</p>
-<p>
-	<img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-	<a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-	<a href="ref-anteditor.htm">Ant Editor preferences</a>
-	<a href="../reference/ref-antprefs.htm">General Ant preferences</a><br>
-	<a href="../reference/ref-anteditorprefs.htm">Ant editor preferences</a><br>
-	<a href="../reference/ref-antformatter.htm">Ant formatter preferences</a><br>
-	<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preferences</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm
deleted file mode 100644
index 2a9423f..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-antview.htm
+++ /dev/null

@@ -1,145 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Ant View</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>    
-</head>
-<body>
-	<h1> Ant View</h1>
-	<p>
-		The Ant view provides a place to view Ant buildfiles and makes it
-		easy to execute a buildfile or a given target within a buildfile. You can add files
-		to the view and expand buildfiles to reveal the targets defined within them.
-	</p>    
-	<p>
-		The pop-up menu for this view also allows you to open an editor on a
-		buildfile, execute the selected target or buildfile, and configure the launch
-		configuration used when executing.
-	</p>
-	<p>
-		Here is what the Ant view looks like:
-	</p>
-	<p>
-		<img align="top" border="0" src="../images/ant_view.png" alt="Ant View">
-  	</p>
-	<p>
-		Like other views in the Workbench, the Ant view has its own
-      	toolbar. Toolbar buttons are provided for adding buildfiles to the view and for
- 		executing them.
- 	</p>
-	<p>
-		To add the Ant view to the current perspective, click
-		<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ant.ui.views.AntView)")'>
-		<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-		<b>Window &gt; Show View &gt; Other... &gt; Ant &gt; Ant</b></a>.
-	</p>    
-	<table border="1" cellpadding="5" cellspacing="0" summary="The commands available in the Ant View">
-		<caption>Ant View Commands</caption>
-  		<thead>
-		    <tr>
-		      <th width="1%" colspan="1" rowspan="1"> <p> Command </p></th>
-		      <th width="20%" colspan="1" rowspan="1"> <p> Name </p></th>
-		      <th colspan="1" rowspan="1"> <p> Description </p></th>
-		      <th width="15%" colspan="1" rowspan="1"> <p> Availability </p></th>
-		    </tr>
-  		</thead>
-  		<tbody>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/clcl16/add_co.png" alt="Add Buildfiles view and context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Add Buildfiles</td>
-		      <td colspan="1" valign="top" align="left">Allows you to add buildfile(s) to the view.</td>
-		      <td colspan="1" valign="top" align="left">View action and context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/clcl16/search.png" alt="Add Buildfiles with Search view toolbar command"></td>
-		      <td colspan="1" valign="top" align="left">Add Buildfile with Search</td>
-		      <td colspan="1" valign="top" align="left">Allows you to add buildfile(s) to the view using searching tools.</td>
-		      <td colspan="1" valign="top" align="left">View action</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/clcl16/filter_internal_targets.png" alt="Hide Internal Targets view toolbar command"></td>
-		      <td colspan="1" valign="top" align="left">Hide Internal Targets</td>
-		      <td colspan="1" valign="top" align="left">Allows you to hide / filter all internal targets from the view.</td>
-		      <td colspan="1" valign="top" align="left">View action</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/clcl16/run_tool.png" alt="Run Selected Target view toolbar command"></td>
-		      <td colspan="1" valign="top" align="left">Run Selected Target</td>
-		      <td colspan="1" valign="top" align="left">Allows you to run the selected target in the view.</td>
-		      <td colspan="1" valign="top" align="left">View action</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/clcl16/remove_co.png" alt="Remove Selected Buildfile view toolbar and context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Remove Selected Buildfile</td>
-		      <td colspan="1" valign="top" align="left">Allows you to remove the selected buildfile from the view.</td>
-		      <td colspan="1" valign="top" align="left">View action and context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/clcl16/removeAll_co.png" alt="Remove All Buildfiles view toolbar and context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Remove All Buildfiles</td>
-		      <td colspan="1" valign="top" align="left">Allows you to quickly remove all buildfiles from the view.</td>
-		      <td colspan="1" valign="top" align="left">View action and context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left">&nbsp;</td>
-		      <td colspan="1" valign="top" align="left">Open With &gt;</td>
-		      <td colspan="1" valign="top" align="left">Allows you to open an editor on the selected buildfile.</td>
-		      <td colspan="1" valign="top" align="left">Context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/clcl16/refresh.png" alt="Refresh Buildfiles context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Refresh Buildfiles</td>
-		      <td colspan="1" valign="top" align="left">Refreshes the contents of the view to reflect the current state of all the represented buildfiles.</td>
-		      <td colspan="1" valign="top" align="left">Context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/obj16/ant.png" alt="Run As &gt; Ant Build context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Run As &gt; Ant Build</td>
-		      <td colspan="1" valign="top" align="left">Launches an Ant build for the selected buildfile or for a specific selected target of the buildfile in Run mode.</td>
-		      <td colspan="1" valign="top" align="left">Context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/obj16/ant.png" alt="Run As &gt; Ant Build... context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Run As &gt; Ant Build...</td>
-		      <td colspan="1" valign="top" align="left">Brings up the launch configuration dialog to edit the configuration associated with the selected buildfile in Run mode.</td>
-		      <td colspan="1" valign="top" align="left">Context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/obj16/ant.png" alt="Debug As &gt; Ant Build context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Debug As &gt; Ant Build</td>
-		      <td colspan="1" valign="top" align="left">Launches an Ant build for the selected buildfile or for a specific selected target of the buildfile in Debug mode.</td>
-		      <td colspan="1" valign="top" align="left">Context menu</td>
-		    </tr>
-		    <tr>
-		      <td colspan="1" valign="top" align="left"><img src="../images/org.eclipse.ui.externaltools/obj16/ant.png" alt="Debug As &gt; Ant Build... context menu command"></td>
-		      <td colspan="1" valign="top" align="left">Debug As &gt; Ant Build...</td>
-		      <td colspan="1" valign="top" align="left">Brings up the launch configuration dialog to edit the configuration associated with the selected buildfile in Debug mode.</td>
-		      <td colspan="1" valign="top" align="left">Context menu</td>
-		    </tr>
-  		</tbody>
-	</table>
-<p>
-	<img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-	<a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-	<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>  
-<p>
-	<img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-	<a href="../tasks/tasks-ant-running.htm">Running Ant buildfiles</a><br>
-	<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-	<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-	<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a>
-</p>
-<p>
-	<img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-	<a href="ref-antruntimeprefs.htm">Ant runtime preferences</a><br>
-	<a href="ref-anteditor.htm">Ant Editor</a><br>
-	<a href="ref-anticons.htm">External Tools and Ant icons</a>
-</p>  
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-capabilitiespref.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-capabilitiespref.htm
deleted file mode 100644
index 35c3fce..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-capabilitiespref.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Capabilities</title>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<h2>Capabilities</h2>
-<P CLASS="Para">The
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.sdk.capabilities)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Capabilities</strong></a>
-
-  preference page allows you to enable or disable 
-  various product components such as Java development and plug-in development. By 
-  default, the page only shows general categories of behavior.  If you would like
-  configure fine-grained capabilities you should use the &quot;Advanced&quot; dialog.</P>
-<P CLASS="Para"><strong>Note:</strong> Some capability selections have dependencies 
-  on other capabilities, disabling a required capability while leaving dependant 
-  capabilities enabled will only result in them becoming re-enabled. This is the 
-  case when deselecting Java development and Core Team Support.</P>
-<P CLASS="Para">Here is what the Capabilities preference page looks like: </P>
-
-<p><img src="../images/cap-pref.png" alt="Image of Capabilities Preference page" border="0" ></p>
-
-<P CLASS="Para">The advanced dialog appears as follows:</P>
-<p><img src="../images/cap-pref-advanced.png" alt="Image of advanced Capabilities Preference page dialog"></p>
-
-<p>When attempting to enable an action after its capability has been disabled 
-  or has yet to be enabled in the preferences page, the following <strong>Confirm 
-  Enablement </strong>prompt will appear verifying that you do indeed want to 
-  enable the required capability. Click <strong>Details</strong> to display a 
-  description of the capability.</p>
-  
-<p><img src="../images/cap-conf.png" alt="Image of Confirm Enablement prompt" border="0" ></p>
-
-<P CLASS="Para"><strong>Note:</strong> This dialog only appears if the 
-  "Prompt when enabling capabilities" preference has not been disabled.</P>
-  
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm
deleted file mode 100644
index 7c653b2..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-cheatsheets.htm
+++ /dev/null

@@ -1,135 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Working with cheat sheets</title>
-</head>
-<body>
-
-<h1>Working with cheat sheets</h1>
-
-<P CLASS="Para">Eclipse provides cheat sheets to guide you through some of its 
-  application development processes. Each cheat sheet is designed to help you 
-  complete some task, and it lists the sequence of steps required to help you 
-  achieve that goal. As you progress from one step to the next, the cheat sheet 
-  will automatically launch the required tools for you. If there is a manual step 
-  in the process, the step will tell you to perform the task and click a button 
-  in the cheat sheet to move on to the next step. Also, relevant help information 
-  to guide you through a task is retrieved in a single click so that lengthy documentation 
-  searches will no longer be required. </P>
-<P CLASS="Para">A <a href="ref-composite-cheatsheets.htm">composite cheat sheet</a> 
-is another kind of cheat sheet that provides guidance for larger tasks or a group of related tasks.</P>
-<h3>Launching a cheat sheet</h3>
-<p>To launch a cheat sheet from the Workbench</p>
-<ol>
-  <li>Select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Help &gt; Cheat Sheets</strong></a> from the menu bar.
-  If this command is not in the menu, it can be added from <b>Window &gt;
-  Customize Perspective &gt; Commands</b>, and check <b>Cheat Sheets</b>.
-  <img src="../images/image92-opencheat.png" alt="Accessing Cheat sheet via Help menu" border="0"></li> 
-  <li>The available cheat sheets are listed, select one and click <strong>OK</strong>. 
-  Alternatively if you know the location of a cheat sheet content file on your 
-  file system or on the web you can enter its path.</li>
-</ol>
-<p>The cheat sheet opens as a view. At any time, only one cheat sheet is open 
-  and active. When you launch a cheat sheet, any opened cheat sheet is closed 
-  before the new one is opened. The completion status of closed cheat sheet is 
-  saved.</p>
-<p>The cheat sheet has a toolbar at the top right edge. These icons appear in 
-  the toolbar:</p>
-<ul>
-  <li>
-  <img src="../images/image92-collapse.png" alt="Collapse button" border="0">Collapses 
-    all the expanded steps except the current step or expands steps to the last 
-    expanded state. Click to toggle between these two states. </li>
-  <li>
-  <img src="../images/image92-select.png" alt="Select button" border="0">Allows 
-    you to select and open another cheat sheet. The completion status of the active 
-    cheat sheet is saved. Then, the active cheat sheet is closed and the selected 
-    cheat sheet is opened. </li>
-  <li>
-  <img src="../images/image92-hide.png" alt="Hide button" border="0">Hides 
-    the cheat sheet. </li>
-  <li>
-  <img src="../images/image92-save.png" alt="Save button" border="0">Saves 
-    the completion status of the active cheat sheet and closes it. <br>
-  </li>
-</ul>
-<p>Note that some cheat sheets can also be launched from the welcome page by 
-first selecting <b>Tutorials </b>and then selecting one of the tutorials.<br>
-  </p>
-<h3>Starting the cheat sheet</h3>
-<p> Each cheat sheet has a list of steps and it always begins with an Introduction 
-  step. When you launch a fresh cheat sheet, the Introduction step is expanded 
-  so that you can read a brief description of the cheat sheet. To start working 
-  with the cheat sheet, click <strong> Click to Begin</strong> <strong>
-<img src="../images/image92-begin.png" alt="Click to Begin button" border="0"> 
-  </strong>in that step. The next step is expanded and highlighted. You should 
-  also see one or more actions buttons, such as <strong>Click to Perform </strong><strong>
-<img src="../images/image92-perform.png" alt="Click to Perform button" border="0"></strong> 
-  in the highlighted step. You can now begin working through the tasks using the 
-  cheat sheet. At any time, the only highlighted step in the cheat sheet is the 
-  current step. </p>
-<h3>Restarting the cheat sheet</h3>
-<p>Any time after starting a cheat sheet, you can restart from the first step 
-  by clicking <strong>Click to Restart </strong><strong>
-<img src="../images/image92-restart.png" alt="Click to Restart button" border="0"></strong> 
-  in the Introduction step. If you have already created some artifacts, you will 
-  have to manually clean up the workspace before restarting the cheat sheet.</p>
-<h3>Progressing through the steps</h3>
-<p>In the current step, when you click <strong>Click to Perform 
-<img src="../images/image92-perform.png" alt="Click to Perform button" border="0"></strong>, 
-  a tool (which can be a wizard), will be launched and you will be required to 
-  work with that tool. When you finish working with that tool, the next step is 
-  automatically highlighted and it becomes the current step. When the current 
-  step is a manual task, you will need to perform the work and click <strong>Click 
-  to Complete </strong><strong>
-<img src="../images/image92-complete.png" alt="Click to Complete button" border="0"></strong> 
-  to move to the next step. A check mark <strong>
-<img src="../images/image92-check.png" alt="Check mark icon" border="0"></strong> 
-  appears in the left margin of each completed step.</p>
-<h3>Getting help information for tasks</h3>
-<p>To get step-by-step instructions for that step, click the help link <strong>
-<img src="../images/image92-help.png" alt="Help Link Icon" border="0"></strong> 
-  in the step before you click <strong>Click to Perform</strong> <strong>
-<img src="../images/image92-perform.png" alt="Click to Perform button" border="0"></strong>, 
-  and the step-by-step instructions on how to work with that tool will be displayed 
-  in the Help window. </p>
-<p>Additional help for entry fields in the tool or wizard may be available by 
-  focusing on the field (use the <strong>Tab</strong> key to position to that 
-  entry) and pressing <strong>F1</strong>.</p>
-<h3>Skipping a step</h3>
-<p>If a current step has a <strong>Click to Skip</strong> option<strong> 
-<img src="../images/image92-skip.png" alt="Click to Skip button" border="0"></strong>, 
-  then it is an optional step. You must click <strong>Click to Skip</strong> <strong>
-<img src="../images/image92-skip.png" alt="Click to Skip button" border="0"></strong> 
-  to skip the current step, when you do, the step will have the skip mark <strong>
-<img src="../images/image92-skip-mark.png" alt="Skip mark icon" border="0"></strong> 
-  in the left margin. If the task does not present <strong>Click to Skip</strong>, 
-  you must perform that step and you cannot skip it.</p>
-<h3>Redoing a step </h3>
-<p>You can redo any step that you may have completed or skipped in the current 
-  cheat sheet. To redo the step, expand the step by clicking its expand <strong>
-<img src="../images/image92-expand.png" alt="Expand Icon" border="0"></strong>icon 
-  and then clicking <strong>Click to Redo</strong> <strong>
-<img src="../images/image92-redo.png" alt="Click to Redo button" border="0"></strong>. 
-  After redoing a step, the cheat sheet will continue from the redo step.</p>
-<h3>Closing the cheat sheet</h3>
-<p>When you finish the last step in a cheat sheet, it automatically restarts. 
-  You can also close the active cheat sheet by clicking the close icon <strong>
-<img src="../images/image92-close.png" alt="Close icon" border="0"></strong> 
-  in the cheat sheet's toolbar. The active cheat sheet saves its completion status 
-  when it is closed so that you can continue where you left off at a later time.</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="ref-composite-cheatsheets.htm">Working with composite cheat sheets</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm
deleted file mode 100644
index 75220cb..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-composite-cheatsheets.htm
+++ /dev/null

@@ -1,105 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Working with composite cheat sheets</title>
-</head>
-<body>
-
-<h1>Working with composite cheat sheets</h1>
-
-<P CLASS="Para">Composite cheat sheets provide guidance through a complex 
-problem by breaking that problem into a set of smaller tasks. Each task consists 
-of a series of steps which must be performed in order. Composite cheat sheets 
-are launched in the cheat sheet view and show two panels which will be side by 
-side or one above the other depending on the relative height and width of the 
-view.</P>
-<P CLASS="Para">
-<img border="0" src="../images/cheatsheet_composite_running.png" alt="Picture of a composite cheat sheet"></P>
-<P CLASS="Para">&nbsp;</P>
-<P CLASS="Para">The panel which appears on the left or on top (depending on the 
-view orientation) is called the task explorer and shows all of the tasks which 
-need to be completed and their state. The lower or right panel is called the 
-task detail panel and shows the task which is selected in the explorer.</P>
-<h3>Launching a composite cheat sheet</h3>
-<p>Composite cheat sheets are launched in the same way as any other
-<a href="ref-cheatsheets.htm">cheat sheet</a> by selecting&nbsp;
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Help &gt; Cheat Sheets</strong></a> from the menu bar.
-  If this command is not in the menu, it can be added from <b>Window &gt;
-  Customize Perspective &gt; Commands</b>, and check <b>Cheat Sheets</b>.
-  </p>
-<h3>The task explorer</h3>
-<p>The task explorer is the tree view which shows the tasks and groups of tasks&nbsp; 
-in a composite cheat sheet. Each task will also have an overlay image at the 
-lower right corner it it is in progress, has been completed or has been skipped. 
-Selecting a task in the task explorer will cause that task to be displayed in 
-the task detail pane. Right clicking on a task in the task explorer brings up a 
-context menu which depending on the state of the task will allow the task to be 
-started, skipped or reset.</p>
-<h3>The task detail pane</h3>
-<p>The task detail pane will show different contents depending on the kind of 
-task and whether it has been started. A cheat sheet task which has not been 
-started will show a description and a button to start the task (or if it cannot 
-be started the reason why not). When in progress a cheat sheet task will show a 
-cheatsheet, and when it has been completed it will show a link to the next task.</p>
-<h3>Task groups</h3>
-<p>There are three kinds of task groups, &quot;set&quot;, &quot;sequence&quot; and &quot;choice&quot;. A 
-sequence represents a set of subtasks that must be performed in order, a set 
-represents a set of subtasks that can be performed in any order, a choice 
-represents a set of tasks only one of which should be performed. A set or 
-sequence is complete when all of its subtasks have been completed. A choice is 
-complete when one of its subtasks has been completed. </p>
-<h3>Cheat sheet tasks</h3>
-<p>A cheat sheet task represents a single
-<a href="ref-cheatsheets.htm">cheat sheet</a>. When a cheat sheet task is first 
-visited the task detail pane shows a description of the task and gives the 
-option to start working on the task and possibly to skip the task. The picture 
-below also shows the images for task sets, sequences and choices. Note that some 
-images are shown in gray, that is because these tasks cannot yet be started 
-because prerequisite tasks have not been completed.</p>
-<p>
-<img border="0" src="../images/cheatsheet_composite_start.png" alt="Picture of a composite cheat sheet"></p>
-<h3>Task dependencies</h3>
-<p>A composite cheat sheet may have dependencies which require one task to be 
-completed before another can be started. An example of where this might happen 
-would be if one task created a project and a second task uses that project. In 
-this case the first task must be completed or skipped before the second task can 
-start.</p>
-<h3>Skipping tasks</h3>
-<p>The author of a composite cheat sheet can choose to make a task or task group 
-optional. If a task is optional it can be skipped, either by right clicking on 
-that task in the task explorer and selecting skip from the context menu, or by 
-clicking on the &quot;Skip this task&quot; hyperlink in the task detail pane. 
-Skipping a task will allow tasks which depend on this task to be started.<br>
-</p>
-<h3>Order of task completion</h3>
-<p>The task detail area will provide hyperlinks which will walk through the 
-tasks in order. It is also possible to perform tasks out of order by selecting 
-the task in the task explorer and starting work on that task. This is useful if 
-you want to go directly to a task of interest without working through all 
-earlier tasks.</p>
-<h3>Restarting tasks</h3>
-<p>Right clicking on the root node in the task explorer shows a menu item 
-&quot;Restart all tasks&quot;. If selected this will reset the state of every task in the 
-composite cheat sheet. Use this only if you want to reset all tasks. The context 
-menu for any other task will have a menu option to reset an individual task. Any 
-tasks which depend on this task will also be reset, and for task groups all 
-subtasks will also be reset.</p>
-<h3>Closing the composite cheat sheet</h3>
-<p>A composite cheat sheet is closed if the cheat sheet view is closed, if 
-Eclipse is closed or if another cheat sheet is opened. The state of each task is 
-saved so that when the composite cheat sheet is reopened its state will be 
-restored.</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="ref-cheatsheets.htm">Working with cheat sheets</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm
deleted file mode 100644
index 5885c87..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-content-type.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" type="text/css">
-<title>Content Types preference page</title>
-</head>
-<body bgcolor="#ffffff">
-
-<h1 class="Head">Content Types preference page</h1>
-
-<p class="Para">The <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ContentTypes)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"><strong>General &gt; Content Types</strong></a>
-  preference page enables you to edit content types and their associated file names and character sets.
-  You can also associate arbitrary file names or file extensions with content types. 
-  A <i>content type</i> acts as a description 
-  of a certain class of files (for instance, XML files). Eclipse uses this description 
-  in various scenarios, such as editor look-ups and file comparisons.
-</p>
-
-<p class="Para">To access the <b>Content Types</b> preference page, select <strong>Window 
-  &gt; Preferences &gt; General &gt; Content Types</strong>. 
-</p>
-
-<p>The <b>Content Types</b> preference page:
-</p>
-
-<p><img src="../images/content_type.png" alt="Content types preference page">
-</p>
-
-<p class="Para">By selecting a content type in the topmost tree, you can alter 
-  the file names and extensions that are associated with it. 
-</p>
-
-<p class="note"><strong>Note:</strong> 
-  Certain items will be marked as "locked". An item is locked if it is one of 
-  the associations provided by the plug-in that declares the content type. In 
-  other words, you can remove only user-contributed associations.
-</p>
-
-<p class="Para">Adding an association is as simple as clicking <strong>Add...</strong>. 
-  A dialog prompts you to enter the file name or extension.
-</p>
-
-<p><img src="../images/Image201_filetype.png" alt="New file type dialog" border="0">
-</p>
-
-<p class="Para">In addition to adding and removing file names or extensions, you 
-  can also set the default encoding for a given content type. To do this, simply 
-  enter the encoding name in the provided field and click <strong>Update</strong>.
-</p>
-
-<p><img src="../images/contenttype-pref-charset.png" alt="Image of character set field">
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm
deleted file mode 100644
index f441d27..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-cvs-decorations.htm
+++ /dev/null

@@ -1,75 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>CVS Label Decorations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">CVS Label Decorations</H1>
-<P CLASS="Para"> Label Decorations are used by CVS to show important synchronization 
-  information about workspace resources. Decorations can effect the text or the 
-  icon of the label associated with a resource. The text decorators are configurable 
-  on the <a href="../tasks/tasks-107b.htm">CVS Label Decorations Preference page</a> which can also be used to indicate 
-  which icons are to be enabled. Here is a description of the icons used by CVS.</P>
-<table width="94%" border="1">
-  <tr>
-    <td align="center"><strong>Decoration</strong></td>
-    <td><strong>Resource type</strong></td>
-    <td><strong>Description</strong></td>
-  </tr>
-  <tr> 
-    <td width="14%" align="center"><img src="../images/version_controlled.png" alt="Version control icon" ></td>
-    <td width="22%">Any</td>
-    <td width="64%">Indicates that the resource is under version control.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/dirty_ov.png" alt="Outgoing icon" ></td>
-    <td>Any</td>
-    <td>Indicates that the resource or one of its children contains outgoing changes.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/edited_ov.png" alt="Edit local icon" ></td>
-    <td>File</td>
-    <td>Indicates that the project containing the file has been configured to 
-      use watch/edit and the file is being edited locally.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/merged_ov.png" alt="Merge conflict icon" ></td>
-    <td>File</td>
-    <td>Indicates that the file contains a merge conflict which has not yet been 
-      resolved. The conflict is considered resolved once the file is modified 
-      and saved.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/no_remotedir_ov.png" alt="No remote folder icon" ></td>
-    <td>Project or Folder</td>
-    <td>Indicates that the folder is under version control but does not correspond 
-      to an existing remote directory but is instead most likely a module defined 
-      in the CVSROOT/modules file.</td>
-  </tr>
-  <tr> 
-    <td align="center"><img src="../images/question_ov.png" alt="Not under version control icon" ></td>
-    <td>File or Folder</td>
-    <td>Indicates that the resource is not under version control.</td>
-  </tr>
-</table>
-<P CLASS="Para"><em>Note</em>: Resources that are ignored by CVS will not be decorated 
-  by any of the above CVS decorations.</P>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/cdecorations.htm">Label Decorations</a> </P>
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-107b.htm">Enabling the CVS resource decorations</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm
deleted file mode 100644
index 11faa24..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-decorations.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Label Decorations</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Label Decorations</H1>
-<P CLASS="Para">
-Label Decorations allow additional information to be displayed in an item's
-label and icon.</P>
-<P CLASS="Para">
-The
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Appearance &gt; Label Decorations</strong></a>
-
-preference page provides a description of each decoration
-and allows the selection of which decorations are visible.&nbsp;</P>
-
-
-<P>Here is what the Label Decorations preference page looks like:&nbsp;
-</P>
-
-
-<P><img src="../images/Image84_decorator_pref.png" alt="Decorators preference page" border="0">
-</P>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/cdecorations.htm">Label Decorations</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm
deleted file mode 100644
index cd8333c..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-exttoolsprefs.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>External Tools</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-External Tools</H1>
-<P CLASS="Intro">
-
-The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.externaltools.ExternalToolsPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Run/Debug &gt; External Tools</strong></a>
-
-page.</p>
-<P>&nbsp;You can configure whether or not you are prompted before external tool project builders are migrated.&nbsp;
-</P>
-
-<P><img src="../images/external_tools_prefs.png" alt="External Tools preference page" border="0" >
-</P>
-
-<p><img src="../images/ngrelc.png" alt="Related concepts" border="0" >
-<br><a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-antprefs.htm">Ant preference page</a><br>
-<a href="../reference/ref-antruntimeprefs.htm">Ant runtime preference page</a><br>
-<a href="../reference/ref-anteditorprefs.htm">Ant editor preference page</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm
deleted file mode 100644
index 6751b23..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-fonts.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Colors and Fonts</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Colors and Fonts</H1>
-<P CLASS="Para"> Many of the fonts and colors and used by eclipse components can be set using the 
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Appearance &gt; Colors and Fonts</strong></a>
-  
-  preference page.</P>
-<P CLASS="Para"> A tree is used to navigate among and show a short preview of 
-  the various colors and fonts. The current face (but not size) of any font is 
-  previewed in its label. Colors are previewed in the icon associated with its 
-  label. Additionally, some categories (Workbench in particular) provide a more 
-  detailed preview of their contributions. This preview is shown below the description 
-  area if available.</P>
-<P CLASS="Para"> Font settings can be changed either by selecting the font from 
-  the list and clicking <strong>Use System Font </strong> to choose the Operating 
-  System font setting or by clicking <strong>Change </strong>to open up a font 
-  selection dialog. <strong>Reset</strong> can be used to return to the default 
-  value.</P>
-<P CLASS="Para"> Color settings can be changed by clicking <strong>color</strong> 
-  to the right of the tree area when a color is selected. <strong>Reset</strong> 
-  can be used to return to the default value.</P>
-
-
-<P>Here is what the Colors and Fonts preference page looks like:&nbsp; </P>
-
-
-<P><img src="../images/Image274_fonts_preference.png" alt="Fonts preference page" border="0" >
-</P>
-
-<p>The Colors and Fonts text field can be used to filter the contents. Simply 
-  type in an entry and any matching results will remain in the tree view.</p>
-<p>Descriptions and previews are provided when the Workbench colors and font settings 
-  are selected.</p>
-<p><img src="../images/Image274_fonts_preference2.png" alt="Fonts preference page" border="0"> 
-</p>
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-20.htm">Changing fonts and colors</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm
deleted file mode 100644
index f5a6643..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-keybindings.htm
+++ /dev/null

@@ -1,546 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<TITLE>
-List of key bindings
-</TITLE>
-
-<link rel="stylesheet" type="text/css" HREF="../book.css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>List of key bindings</h1>
-The list of available key bindings in Eclipse depends on many factors, including
-what view or editor is selected, whether a dialog is open, what plug-ins are
-installed, and what operating and windowing system is being used.  At any
-time, you can obtain a list of available key bindings using Key Assist 
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.showKeyAssist")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help &gt; Key Assist...</b></a>
-or Ctrl+Shift+L).  The following tables list some 
-popular key bindings available in the Eclipse SDK.
-
-<p>&nbsp;</p>
-<h3><strong>File actions</strong></h3>
-
-<table width="75%" border="1">
-  <tr style="height: 64.5pt;" height="86"> 
-    <td class="xl29" style="height: 64.5pt; width: 126pt;" height="86">New</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Create a 
-      Java element or a new resource. Configure which elements are shown in the 
-      submenu in Window &gt; Customize Perspective. In a Java perspective, by 
-      default action for creating a project, package, class, interface , source 
-      folder, scrapbook, file and folder are available.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + N</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Close</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Close 
-      the current editor. If the editor contains unsaved data, a save request 
-      dialog will be shown.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + F4</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Close 
-      All</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Close all editors. 
-	If editor contains unsaved data, a save request dialog will be shown.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + F4</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Save</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Save 
-      the content of the current editor. Disabled if the editor does not contain 
-      unsaved changes.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + S</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Save 
-      As</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Save 
-      the content of the current editor under a new name.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;"></td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Save 
-      All</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Save 
-      the content of all editors with unsaved changes. Disabled if no editor contains 
-      unsaved changes.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + S</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Print</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Prints 
-      the content of the current editor. Enabled when an editor has the focus.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + P</td>
-  </tr>
-  <tr style="height: 51.75pt;" height="69"> 
-    <td class="xl27" style="border-top: medium none; height: 51.75pt; width: 126pt;" height="69">Properties</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Opens 
-      the property pages of the select elements. Opened on Java projects the Java 
-      Build Path page and the Javadoc Location page are available. For JAR archives, 
-      configure the JAR's Source Attachment and Javadoc Location here.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Enter</td>
-  </tr>
-</table>
-<h3><strong>Edit actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 13.5pt;" height="18"> 
-    <td class="xl29" style="height: 13.5pt; width: 126pt;" height="18">Undo</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Revert the 
-      last change in the editor</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + Z</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Redo</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Revert 
-      an undone change</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Y</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Cut</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Copies 
-      the currently selected text or element to the clipboard and removes the 
-      element. On elements, the remove is not performed before the clipboard is 
-      pasted.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + X</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Copy</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Copies 
-      the currently selected text or elements to the clipboard</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + C</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Paste</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Paste 
-      the current content as text to the editor, or as a sibling or child element 
-      to the a currently selected element.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + V</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Delete</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Delete 
-      the current text or element selection.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Delete</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Select 
-      All</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Select 
-      all the editor content..</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + A</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Find 
-      / Replace</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Open 
-      the Find / Replace dialog. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + F</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Find 
-      Next</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Finds 
-      the next occurrence of the currently selected text. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + K</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Find 
-      Previous</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Finds 
-      the previous occurrence of the currently selected text. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + K</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Incremental 
-      Find Next</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the incremental find mode. After invocation, enter the search text as instructed 
-      in the status bar. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + J</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Incremental 
-      Find Previous</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the incremental find mode. After invocation, enter the search text as instructed 
-      in the status bar. Editor only.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + J</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Add 
-      Task</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Add 
-      a user defined task to the current text selection or selected element.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Enter</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td rowspan="4" class="xl27" style="border-top: medium none; height: 127.5pt; width: 126pt;" height="170">Expand 
-      Selection to</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Enclosing 
-      Element: Selects the enclosing expression, block, method in the code. This 
-      action is aware of the Java syntax. It may not function properly when the 
-      code has syntax errors. (Arrow Up).</td>
-    <td rowspan="4" class="xl27" style="border-top: medium none; width: 110pt;">Alt 
-      + Shift + Arrow Keys</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl28" style="border-left: medium none; height: 25.5pt; width: 269pt;" height="34">Next 
-      Element: Selects the current and next element. (Arrow Right)</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl28" style="border-left: medium none; height: 25.5pt; width: 269pt;" height="34">Previous 
-      Element: Selects the current and the previous element (Arrow Left)</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl28" style="border-left: medium none; height: 25.5pt; width: 269pt;" height="34">Restore 
-      Last Selection: After an invocation of Expand Selection to restore the previous selection. (Arrow Down)</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="height: 38.25pt; width: 126pt;" height="51">Show Tooltip 
-      Description</td>
-    <td class="xl25" style="border-left: medium none; width: 269pt;">Shows the 
-      value of a hover that would appear at the current cursor location. The dialog 
-      shown is scrollable and does not shorten descriptions.</td>
-    <td class="xl25" style="border-left: medium none; width: 110pt;">F2</td>
-  </tr>
-  <tr style="height: 89.25pt;" height="119"> 
-    <td class="xl25" style="border-top: medium none; height: 89.25pt; width: 126pt;" height="119">Content 
-      Assist</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Opens 
-      a context assist dialog at the current cursor position to bring up Java 
-      code assist proposals and templates. See the Templates preference page for 
-      available templates (Window &gt; Preferences &gt; Java &gt; Editor &gt; 
-      Templates) and go to the Editor preference page (Window &gt; Preferences 
-      &gt; Java &gt; Editor &gt; Code Assist) for configuring the behavior of 
-      code assist.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Space</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Quick 
-      Fix</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">If 
-      the cursor is located at a location with problem indication this opens a 
-      context assist dialog at the current cursor to present possible corrections.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + 1</td>
-  </tr>
-  <tr style="height: 51.75pt;" height="69"> 
-    <td class="xl27" style="border-top: medium none; height: 51.75pt; width: 126pt;" height="69">Parameter 
-      Hints</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">If 
-      the cursor is located at the parameter specification for method reference, 
-      this actions shows a hover with parameter types information.The parameter 
-      at the current cursor location is shown in bold.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + Space</td>
-  </tr>
-</table>
-<h3><strong>Navigate actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 26.25pt;" height="35"> 
-    <td class="xl29" style="height: 26.25pt; width: 126pt;" height="35">Open</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Tries to 
-      resolve the element referenced at the current code selection and opens the 
-      file declaring the reference.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">F3</td>
-  </tr>
-  <tr style="height: 63.75pt;" height="85"> 
-    <td class="xl25" style="border-top: medium none; height: 63.75pt; width: 126pt;" height="85">Open 
-      Type Hierarchy</td>
-    <td class="xl26" style="width: 269pt;">Tries to resolve the element referenced 
-      at the current code selection and opens the element in the Type Hierarchy 
-      view. Invoked on elements, opens the type hierarchy of the element. Supported 
-      in the Java editor and views showing Java elements.</td>
-    <td class="xl25" style="border-top: medium none; width: 110pt;">F4</td>
-  </tr>
-  <tr style="height: 102pt;" height="136"> 
-    <td class="xl25" style="border-top: medium none; height: 102pt; width: 126pt;" height="136">Open 
-      External Javadoc</td>
-    <td class="xl25" style="border-left: medium none; width: 269pt;">Opens the 
-      Javadoc documentation of the currently selected element or text selection. 
-      The location of the Javadoc of a JAR or a project is specified in the Javadoc 
-      Location property page on projects or JARs. Note that this external Javadoc 
-      documentation may not be up to date with the Javadoc specified in the current 
-      code. You can create Javadoc documentation for source files in a Java project 
-      using the Javadoc export wizard.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Shift 
-      + F2</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Open 
-      Type</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Brings 
-      up the Open Type selection dialog to open a type in the editor.The Open 
-      Type selection dialog shows all types existing in the workspace.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + T</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td class="xl25" style="border-top: medium none; height: 51pt; width: 126pt;" height="68">Open 
-      Type In Hierarchy</td>
-    <td class="xl26" style="width: 269pt;">Brings up the Open Type selection dialog 
-      to open a type in the editor and the Type Hierarchy view. The Open Type 
-      selection dialog shows all types that exist in the workspace.</td>
-    <td class="xl25" style="border-top: medium none; width: 110pt;">Ctrl + Shift 
-      + H</td>
-  </tr>
-  <tr style="height: 25.5pt;" height="34"> 
-    <td class="xl25" style="border-top: medium none; height: 25.5pt; width: 126pt;" height="34">Show 
-      Outline</td>
-    <td class="xl25" style="border-left: medium none; width: 269pt;">Opens the 
-      lightweight outliner for the currently selected type.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + O</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Go 
-      to Next Problem</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Selects 
-      the next problem. Supported in the Java editor.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + . (Period)</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Go 
-      to Previous Problem</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Selects 
-      the previous problem. Supported in the Java editor.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + , (Comma)</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Go 
-      to Last Edit Location</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Reveal 
-      the location where the last edit occurred.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Q</td>
-  </tr>
-  <tr style="height: 26.25pt;" height="35"> 
-    <td class="xl27" style="border-top: medium none; height: 26.25pt; width: 126pt;" height="36">Go 
-      to Line</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Opens 
-      an a dialog which allows entering the line number to which the editor should 
-      jump to. Editor only.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + L</td>
-  </tr>
-</table>
-<h3><strong>Search actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 13.5pt;" height="18"> 
-    <td class="xl29" style="height: 13.5pt; width: 126pt;" height="18">Search...</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Opens the 
-      search dialog</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + H</td>
-  </tr>
-  <tr style="height: 26.25pt;" height="35"> 
-    <td class="xl27" style="border-top: medium none; height: 26.25pt; width: 126pt;" height="35">Occurrences 
-      in File</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 269pt;">Finds 
-      all occurrences of the selected Java element in its file</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + U</td>
-  </tr>
-</table>
-<h3><strong>Project actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 52.5pt;" height="70"> 
-    <td class="xl28" style="height: 52.5pt; width: 126pt;" height="70">Build All</td>
-    <td class="xl28" style="border-left: medium none; width: 269pt;">Builds the 
-      all projects in the workspace. This is an incremental build, means that 
-      the builder analyzes the changes since the last time of build and minimizes 
-      the number of changed files.</td>
-    <td class="xl28" style="border-left: medium none; width: 110pt;">Ctrl + B</td>
-  </tr>
-</table>
-<h3><strong>Source actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 13.5pt;" height="18"> 
-    <td class="xl29" style="height: 13.5pt; width: 126pt;" height="18">Comment</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Comments 
-      out all lines containing the current selection.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Ctrl + /</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">Uncomment</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Uncomments 
-      all lines containing the current selection.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + \</td>
-  </tr>
-  <tr style="height: 12.75pt;" height="17"> 
-    <td class="xl25" style="border-top: medium none; height: 12.75pt; width: 126pt;" height="17">
-	Indent</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">
-	Indent current line.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">
-	Ctrl + I</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Shift 
-      Right</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Increments 
-      the level of indentation of the currently select lines. Only activated when 
-      the selection covers multiple lines or a single whole line.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Tab</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Shift 
-      Left</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Decrements 
-      the level of indentation of the currently select lines. Only activated when 
-      the selection covers multiple lines or a single whole line.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Shift 
-      + Tab</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td class="xl25" style="border-top: medium none; height: 51pt; width: 126pt;" height="68">Format</td>
-    <td class="xl24" style="border-top: medium none; border-left: medium none; width: 269pt;">Uses 
-      the code formatter to format the current text selection. The formatting 
-      options are configured on the Code Formatter preference page (Window &gt; 
-      Preferences &gt; Java &gt; Code Formatter)</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + F</td>
-  </tr>
-  <tr style="height: 140.25pt;" height="187"> 
-    <td class="xl27" style="border-top: medium none; height: 140.25pt; width: 126pt;" height="187">Organize 
-      Imports</td>
-    <td class="xl31" style="border-left: medium none; width: 269pt;">Organizes 
-      the import declarations in the compilation unit currently open or selected. 
-      Unnecessary import declarations are removed, and required import declarations 
-      are ordered as specified in the Organize Import preference page (Window 
-      &gt; Preferences &gt; Java &gt; Organize Import). Organize import can be 
-      executed on incomplete source and will prompt you when a referenced type 
-      name can not be mapped uniquely to a type in the current project. You can 
-      also organize multiple compilation units by invoking the action on a package 
-      or selecting a set of compilation units.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Ctrl 
-      + Shift + O</td>
-  </tr>
-  <tr style="height: 90pt;" height="120"> 
-    <td class="xl27" style="height: 90pt; width: 126pt;" height="120">Add Import</td>
-    <td class="xl26" style="width: 269pt;">Creates an import declaration for a 
-      type reference currently selected. If the type reference if qualified, the 
-      qualification will be removed if possible. If the referenced type name can 
-      not be mapped uniquely to a type of the current project you will be prompted 
-      to specify the correct type. Add Import tries to follow the import order 
-      as specified in the Organize Import preference page.</td>
-    <td class="xl27" style="width: 110pt;">Ctrl + Shift + M</td>
-  </tr>
-</table>
-<h3><strong>Refactor actions</strong></h3>
-<table width="75%" border="1">
-  <tr style="height: 39pt;" height="52"> 
-    <td class="xl29" style="height: 39pt; width: 126pt;" height="52">Undo</td>
-    <td class="xl29" style="border-left: medium none; width: 269pt;">Does an Undo 
-      of the last refactoring. The refactoring undo buffer is only valid as long 
-      as no other source changes than refactoring have been performed.</td>
-    <td class="xl29" style="border-left: medium none; width: 110pt;">Alt + Shift 
-      + Z</td>
-  </tr>
-  <tr style="height: 38.25pt;" height="51"> 
-    <td class="xl25" style="border-top: medium none; height: 38.25pt; width: 126pt;" height="51">Redo</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Does 
-      a Redo of the last undone refactoring. The refactoring undo/redo buffer 
-      is only valid as long as no other source changes than refactoring have been 
-      performed.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + Y</td>
-  </tr>
-  <tr style="height: 89.25pt;" height="119"> 
-    <td class="xl25" style="border-top: medium none; height: 89.25pt; width: 126pt;" height="119">Rename</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Rename refactoring dialog: Renames the selected element and (if enabled) 
-      corrects all references to the elements (also in other files). Is available 
-      on methods, fields, local variables, method parameters, types, compilation 
-      units, packages, source folders, projects and on a text selection resolving 
-      to one of these element types.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + R</td>
-  </tr>
-  <tr style="height: 102pt;" height="136"> 
-    <td class="xl25" style="border-top: medium none; height: 102pt; width: 126pt;" height="136">Move</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Move refactoring dialog: Moves the selected elements and (if enabled) 
-      corrects all references to the elements (also in other files). Can be applied 
-      to one instance method (which can be moved to a component), one or more 
-      static methods, static fields, types, compilation units, packages, source 
-      folders and projects and on a text selection resolving to one of these element 
-      types.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + V</td>
-  </tr>
-  <tr style="height: 51pt;" height="68"> 
-    <td class="xl25" style="border-top: medium none; height: 51pt; width: 126pt;" height="68">Inline</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Inline refactoring dialog. Inlines local variables, methods or constants. 
-      This refactoring is available on methods, static final fields and text selections 
-      that resolve to methods, static final fields or local variables.</td>
-    <td class="xl25" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + I</td>
-  </tr>
-  <tr style="height: 89.25pt;" height="119"> 
-    <td class="xl27" style="border-top: medium none; height: 89.25pt; width: 126pt;" height="119">Extract 
-      Method</td>
-    <td class="xl24" style="border-top: medium none; border-left: medium none; width: 269pt;">Starts 
-      the Extract Method refactoring dialog. Creates a new method containing the 
-      statements or expression currently selected and replaces the selection with 
-      a reference to the new method. You can use Expand Selection from the Edit menu to get a 
-	  valid selection range. This feature is useful for cleaning up lengthy, cluttered, or overly-complicated methods.</td>
-    <td class="xl27" style="border-top: medium none; border-left: medium none; width: 110pt;">Alt 
-      + Shift + M</td>
-  </tr>
-  <tr class="xl30" style="height: 76.5pt;" height="102"> 
-    <td class="xl25" style="height: 76.5pt; width: 126pt;" height="102">Extract 
-      Local Variable</td>
-    <td class="xl30" style="width: 269pt;">Starts the Extract Variable refactoring 
-      dialog. Creates a new variable assigned to the expression currently selected 
-      and replaces the selection with a reference to the new variable. This refactoring 
-      is available on text selections that resolve to local variables. You can 
-      use Expand Selection from the Edit menu to get a valid selection range.</td>
-    <td class="xl25" style="width: 110pt;">Alt + Shift + L</td>
-  </tr>
-</table>
-<p><strong>Related information</strong></p>
-<p>
-<a href="../concepts/accessibility/navigation.htm">
-Navigating the user interface using the keyboard</a><br>
-<a href="../concepts/accessibility/keyboardshortcuts.htm">
-Keys and accessibility for the workbench</a></p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-<p>&nbsp;</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-net-preferences.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-net-preferences.htm
deleted file mode 100644
index 0f58c8f..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-net-preferences.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Network Connections</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">Network Connections</H1>
-<p class="Head">The following sections describe the preferences available on the
-  
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.net.NetPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Network Connections</strong></a>
-  
-  preference page.</p>
-
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Option</P></TH>
-      <TH> <P class="Para">Description</P></TH>
-      <TH> <P class="Para">Default</P></TH>
-    </TR>
-  </THEAD>
-  <TR> 
-    <TD valign="top" align="left"><NOBR>Active Provider</NOBR></TD>
-    <TD valign="top" align="left">Specifies the settings profile to be used when opening connections.
-    Choosing the <strong>Direct</strong> provider causes all the connections to be opened without the use
-    of a proxy server. Selecting <strong>Manual</strong> causes settings defined in Eclipse to be used. On some
-    platforms there is also a <strong>Native</strong> provider available, selecting this one causes
-    settings that were discovered in the OS to be used.</TD>
-    <TD valign="top" align="left"><NOBR>Native (if present)</NOBR><BR><nobr>Manual (otherwise)</nobr></TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Proxy entries</TD>
-    <TD valign="top" align="left">The table displays entries that are available for all 
-    providers. Checkboxes in the first column of the table indicate entries to be used for the
-    currently selected provider.</TD>
-    <TD> &nbsp;</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">Proxy bypass</TD>
-    <TD valign="top" align="left">Use this table to specify, either by name or pattern,
-    which hosts should not use any proxy. A direct connection will always be used for matching hosts.
-     Checkboxes in the first column of the table indicate entries to be used for the currently selected provider.</TD>
-    <TD> &nbsp;</TD>
-  </TR>
-</TABLE>
-
-<h3>Proxy entries</h3>
-<p>When using <strong>Manual</strong> proxy provider there are three predefined schemas to set
-settings for: HTTP, HTTPS and SOCKS<a href="#SOCKS"> [1]</a>. Configuration for each schema is displayed
-in the <strong>Proxy entries</strong> table. To edit settings for a particular schema double-click
-the entry or select the entry and click <strong>Edit...</strong> button. If <strong>Port</strong>
-field is left blank default port number will be used. Following table lists default port numbers for
-each of the predefined schemas.</p> 
-
-<TABLE border="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH> <P class="Para">Schema</P></TH>
-      <TH> <P class="Para">Default Port</P></TH>
-    </TR>
-  </THEAD>
-<TR> 
-    <TD valign="top" align="left">HTTP</TD>
-    <TD>80</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">SSL</TD>
-    <TD>443</TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left">SOCKS</TD>
-    <TD>1080</TD>
-  </TR>
-</TABLE>
-
-<p>The <strong>Network Connections</strong> preference page</p>
-<p><img alt="Network Connections preference page" src="../images/net-general.png"></p>
-
-<p><a name="SOCKS"></a>
-1. The SOCKS proxy support in Java 1.4 had certain limitations. Due to these limitations,
-the setting of the SOCKS system properties is not performed when a 1.4 VM is used. The SOCKS proxy
-may still be used by some tooling when running on a 1.4 VM (e.g. CVS). However, users should use a 1.5 (or 5.0)
-VM if they require full SOCKS proxy support.
-</p>
-<P><IMG alt="Related reference" src="../images/ngrelr.png" border="0"><BR>
-  <A href="ref-ssh2-preferences.htm">SSH2 Preferences</A></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-p2-autoupdate.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-p2-autoupdate.htm
deleted file mode 100644
index c9a494b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-p2-autoupdate.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Automatic updates</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Automatic Updates</H1>
-<P CLASS="Intro"> The following preferences can be changed on the
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.internal.p2.ui.sdk.scheduler.AutomaticUpdatesPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Install/Update &gt; Automatic Updates</strong></a>
-
-  page:</p> 
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <tr> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Automatically find new updates and notify me</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          When selected, Update manager will automatically search for update, 
-          as defined&nbsp; by the update schedule</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </tr>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Update Schedule</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Look for updates on each startup, or once a day or some day a week, 
-          at a predefined time.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On startup</P></TD>
-    </TR>
-    <TR> 
-      <TD height="23" COLSPAN="1" ROWSPAN="1" align="left" valign="top"> <P CLASS="Para"> 
-          Download Options</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to choose between having Eclipse search for updates 
-          and notifying you of them once they are available or having Eclipse 
-          automatically download new updates and asking you to install them.</p>
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Search and notify</P></TD>
-    </TR>
-    <TR> 
-      <TD height="23" COLSPAN="1" ROWSPAN="1" align="left" valign="top"> <P CLASS="Para"> 
-          When updates are found</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-      	  Choose to be notified about new updates only once, or to receive reminders
-      	  until the updates are installed.</p>
-      </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Notify once</P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-
-<P>Here is what the Automatic Updates preference page looks like:&nbsp;&nbsp; 
-</P>
-<P> </P>
-<img src="../images/ref-p2-autoupdate.png" alt="Automatic Update Preference Page" border="0">
-<P>&nbsp; </P>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-122.htm">Scheduling automatic updates</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a HREF="ref-61.htm">Help Menu</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-p2-installupdate.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-p2-installupdate.htm
deleted file mode 100644
index 77b25df..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-p2-installupdate.htm
+++ /dev/null

@@ -1,76 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Install/Update</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Install/Update</H1>
-<P CLASS="Intro"> The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.internal.p2.ui.sdk.ProvisioningPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>Install/Update</strong></a>
-  page:</p> 
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <tr> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Browsing for updates</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-      	This option allows you to configure what software versions are shown in the
-      	<b>Available Updates</b> wizard.  You can select to show only the 
-      	latest version of an update, or all versions of updates that are available.</P>
-	  </TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Show latest</P></TD>
-    </tr>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          When software selected for an install wizard may not be compatible</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This preference allows you to configure how incompatibilities are reported.
-          If you attempt to update, uninstall, or install software that is
-          not compatible with the software you already have installed, you can elect
-          to open a wizard to edit your software selections, or you can just have the 
-          problem reported in the error log without opening the wizard. By
-          default you will be prompted about what you want to do in this situation.</p></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Ask me</P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-
-<p>Here is what the Install/Update preference page looks like:&nbsp;&nbsp; </p>
-<P> </P><img src="../images/ref-p2-installupdate.png" alt="Install/Update Preference Page" border="0">
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-120.htm">Updating the installation</a>
-<br><a href="../tasks/tasks-124.htm">Installing new software</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a HREF="ref-net-preferences.htm">Network Connections</a>
-<br><a HREF="ref-61.htm">Help Menu</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-p2-siteprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-p2-siteprefs.htm
deleted file mode 100644
index 5e9c28d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-p2-siteprefs.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Available Software Sites</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Available Software Sites</H1>
-<P CLASS="Intro"> The following preferences can be changed on the
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.internal.provisional.p2.ui.dialogs.RepositoryManipulationPage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Install/Update &gt; Available Software Sites</strong></a>
-
-  page:</p> 
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Button</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
- <TR>
-<TH align="left">
-<span style="font-weight: 400">Add/Edit/Remove</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Add, edit or remove a software site.</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Test Connection</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Tests to see if it is possible to connect to the 
-selected software site.</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Disable/Enable</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Allows a software site to be disabled so that the
-update system will not try to find software on the site when updating or installing
-software.</span></TH>
-</TR>
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Import/Export</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Import or export the list of software sites from a file.</span></TH>
-</TR>
-  </TBODY>
-</TABLE>
-
-
-<P>Here is what the Available Software Sites preference page looks like:&nbsp;&nbsp; 
-</P>
-<P> </P>
-<img src="../images/ref-p2-siteprefs.png" alt="Available Software Sites Preference Page" border="0">
-<P>&nbsp; </P>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" >
-<br><a href="../tasks/tasks-128.htm">Working with the Available Software sites</a>
-<br><a href="../tasks/tasks-122.htm">Scheduling automatic updates</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a HREF="ref-61.htm">Help Menu</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-regex-find-replace.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-regex-find-replace.htm
deleted file mode 100644
index af7ee22..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-regex-find-replace.htm
+++ /dev/null

@@ -1,54 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Supported Regular Expressions</title>
-   
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-
-<h1 class="Head">Supported Regular Expressions</h1>
-
-<p>
-When searching for text you can use the regular expressions as defined by the <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html">Pattern class</a>.
-<br>Additionally, \R can be used to match any form of line delimiter (Unix, Windows, Mac OS 9).
-Note that \R does not work in character groups ([]).
-</p>
-
-<p>
-The replace string allows the following constructs:
-</p>
-  <table border="1" cellpadding="5" summary="supported constructs in the replace field">
-    <tbody>
-      <tr>
-        <td>$i</td>
-        <td>inserts
-          <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html#cg">capturing group</a>
-          i.
-        </td>
-      </tr>
-      <tr>
-        <td>\i</td>
-        <td>inserts
-          <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html#cg">capturing group</a>
-          i (same as $i).
-        </td>
-      </tr>
-      
-      <tr> <td>\<i>x</i></td> <td>quotes character <i>x</i> (unless \<i>x</i> has a special meaning)</td> </tr>
-      <tr> <td>\R</td> <td>inserts the default line delimiter of the document</td> </tr>
-      <tr> <td>\x<i>hh</i></td> <td>inserts the hexadecimal character <i>hh</i></td> </tr>
-      <tr> <td>\u<i>hhhh</i></td> <td>inserts the Unicode character <i>hhhh</i></td> </tr>
-      <tr> <td>\n</td> <td>inserts a newline character (usually, you should use \R instead)</td> </tr>
-      <tr> <td>\r</td> <td>inserts a carriage-return character (usually, you should use \R instead)</td> </tr>
-      <tr> <td>\t</td> <td>inserts a tab character</td> </tr>
-      <tr> <td>\f</td> <td>inserts a form-feed character</td> </tr>
-      <tr> <td>\a</td> <td>inserts an alert (beep) character</td> </tr>
-      <tr> <td>\e</td> <td>inserts an escape character</td> </tr>
-      <tr> <td>\c<i>C</i></td> <td>inserts a the control character for <i>C</i></td> </tr>
-      <tr> <td>\C</td> <td>retains the casing of the match (all lower case, all upper case, capitalized)</td> </tr>
-      
-    </tbody>
-  </table>
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-search.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-search.htm
deleted file mode 100644
index e47d54b..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-search.htm
+++ /dev/null

@@ -1,95 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"><title>Search</title></head>
-<body>
-
-<h1>Search</h1>
-<p> The
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.search.preferences.SearchPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Search</strong></a>
-preference page allows you to set preferences for searches. 
-</p>
-<p>&nbsp; </p>
-<TABLE BORDER="1" cellspacing="0">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Reuse editors to show matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to keep using the same editor for search 
-          results to reduce the number of open editors.</P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Bring Search view to front after search</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option will display the search view at the front after performing 
-          a search. </P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Ignore potential matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Select this option if you only want to see exact matches.</P></TD>
-      <TD> Off</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Emphasize potential matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to highlight potential matches in the Search 
-          view. If the Search engine isn't 100% sure about the match then it is 
-          considered a potential match. </P></TD>
-      <TD> On</TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Foreground color for potential matches</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to select the foreground color for potential 
-          matches.</P></TD>
-      <TD>&nbsp; </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Default perspective for the Search view</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          This option allows you to define which perspective should be brought 
-          to the front when there are new search results.</P></TD>
-      <TD>None</TD>
-    </TR>
-  </TBODY>
-</TABLE>
-<p>&nbsp;</p>
-
-<p>Here is what the Search preference page looks like:&nbsp;
-</p>
-
-
-<p><img src="../images/Image276_search_preference.png" alt="Search Preference Page" border="0"> 
-</p>
-
-
-<p>&nbsp;
-</p>
-
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-options.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-options.htm
deleted file mode 100644
index 605cc13..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-options.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Secure storage runtime options</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">Secure storage runtime options</H1>
-
-<h4>Changing location of secure storage</h4>
-
-<p>By default, secure storage is located in your home directory. On Windows that typically resolves to 
-<i>&quot;C:\Documents and Settings\&lt;user_name&gt;\.eclipse\org.eclipse.equinox.security&quot;</i>. This location is selected 
-to allow multiple Eclipse-based applications to share the same secure storage.</p>
-
-<p>If you would like to modify the location of the default secure storage, you can use the 
-&quot;-eclipse.keyring &lt;file_path&gt;&quot; runtime option. The &lt;file_path&gt; is a path to the file which is used 
-to persist the secure storage data.</p>
-
-<p>The current location of the default secure storage can be found on the 
-   <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.security.ui.storage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Security &gt; Secure Storage</strong></a> 
-preferences page.</p>
-
-<h4>Password file</h4>
-
-<p>The password provider mechanism can be bypassed if you specify the
-&quot;-eclipse.password &lt;file path&gt;&quot; runtime option. In this case the contents of the file you specified 
-as the argument will be used as a master password. While this option is valuable in some circumstances 
-(such as headless applications), the protection of the password file becomes a consideration. The password file 
-can be protected by the operating system access rights and/or by placing it on a removable storage, 
-such as a USB key.</p>
-
-<p><img alt="Related concepts" src="../images/ngrelc.png" border="0">
-  <br><A href="ref-securestorage-start.htm">Secure storage</A>
-  <br><A href="ref-securestorage-works.htm">How secure storage works</A>
-  <br><A href="ref-securestorage-recovery.htm">Password recovery</A>
-  <br><A href="ref-securestorage-passwd.htm">Life of a master password</A>
-</p>
-<p><img alt="Related reference" src="../images/ngrelr.png" border="0">
-  <br><a href="ref-securestorage-prefs.htm">Secure storage preference page</a>
-</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-passwd.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-passwd.htm
deleted file mode 100644
index 2981ac3..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-passwd.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Life of a master password</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">Life of a master password</H1>
-
-<p>The &quot;master&quot; password is used to encrypt and decrypt data stored by the secure storage. 
-The master passwords are specific to providers: each provider has a separate master password.</p> 
-
-<p>The life of a master password begins when a password provider is asked for it for a first time. 
-Depending on the provider, it will either generate a master password behind the scenes, or will ask you 
-for some input. The same master password is then used for all subsequent use of this password provider.</p>
-
-<p align=center><img alt="Lifecycle of a master password." src="../images/equinox_secure_storage_pswd.png"><br>
-</p>
-<p align=center><b>Picture 1. Lifecycle of a master password.</b></p>
-
-<p>Once the master password is obtained from the password provider, it is cached in memory until 
-the application is closed or the password cache is cleared using the <b>Secure Storage</b> preference page.</p>
-
-<p>The master password can be changed using the <b>Secure Storage</b> preference page. Depending on 
-the provider, the password change operation might require some input from you or might happen completely 
-behind the scenes.</p>
-
-<p>In case the master password is lost, it can be recovered if password recovery questions and answers were 
-specified. The password recovery allows working around both human and machine problems. For instance, if 
-a UI prompt was used to enter a password and the user forgot the password. If an operating system integration 
-module was used, the operating system might have been re-installed or an entry deleted in the system keyring 
-that was used for the master password.</p>
-
-<p><img alt="Related concepts" src="../images/ngrelc.png" border="0">
-  <br><A href="ref-securestorage-start.htm">Secure storage</A>
-  <br><A href="ref-securestorage-works.htm">How secure storage works</A>
-</p>
-<p><img alt="Related reference" src="../images/ngrelr.png" border="0">
-  <br><a href="ref-securestorage-prefs.htm">Secure storage preference page</a>
-  <br><a href="ref-securestorage-options.htm">Secure storage runtime options</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-prefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-prefs.htm
deleted file mode 100644
index e7814a8..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-prefs.htm
+++ /dev/null

@@ -1,96 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Secure storage preference page</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">Secure storage preference page</H1>
-
-<p>The <b>Secure Storage</b> preference page is used to manage storage of
-encrypted information such as passwords. Typically you will have no reason to
-alter the preferences on this page. The options here are mostly for troubleshooting,
-and, to a lesser degree, for system administrators and power users.</p>
-
-<h2>Password options</h2>
-
-<p>The <b>Password</b> tab combines functionality related to the master password 
-lifecycle and password providers.</p> 
-
-<p>The <b>Clear Passwords</b> button clears cached master passwords from memory. 
-This is analogous to logging out of the secure storage. Note that some password providers obtain 
-credentials from the operating system automatically. To prevent them from doing so, you'll need to log out 
-from the operating system account.</p>
-
-<p>The <b>Master password providers</b> section contains a list of currently available password providers. 
-By default, the enabled provider with the highest priority is used to encrypt data added to secure storage. 
-The priority range is from 0 to 10, with 10 being the highest. A password provider can be disabled it if malfunctions, 
-or if you prefer a lower priority password provider.</p> 
-
-<p>Note that data can only be decrypted by the same provider that encrypted the data. 
-This means that changes to the list of the password providers affect only new entries. 
-The password provider for existing entries can only be overwritten by the application storing the data.</p>
-
-<p>By default all password providers are enabled.</p>
-
-<p>Each password provider that has been used at least once will have a master password associated with it. 
-Use the <b>Change Password...</b> button can to change the master password of the selected 
-password provider.</p> 
-
-<p>The <b>Recover Password...</b> button opens the password recovery dialog. Use this option if you
-have forgotten the master password and have configured password recovery questions.
-The button will be disabled if the password recovery setup was cancelled 
-when the master password was created. Note that the answers for the password recovery questions have to be entered 
-exactly as they were specified during the password recovery setup. Answers are case-sensitive and white space 
-inside answers are significant.</p>
-
-<h2>Contents options</h2>
-
-<p>The <b>Contents</b> tab displays contents of the default secure storage.</p>
-
-<p>Secure storage is organized as a tree where nodes represent context of the information and values are associated 
-with each node. Selecting a node in the tree will display a table of values associated with that node. Values stored in 
-a non-encrypted form will be displayed; the encrypted values will be shown as &quot;*********&quot;.</p> 
-
-<p>At the bottom of this tab, you will find the actual file location used to persist secure storage data.</p>
-
-<p>To force changes to the contents of secure storage to be saved, click <b>Save</b>.</p>
-
-<p>To delete stored data to recover from an error or to reflect a change in the setup, 
-click <b>Delete</b>. This will delete <b>all</b> of the contents of secure storage. 
-In some cases, other parts of the application may depend on the contents of secure storage that you deleted.  
-To avoid unexpected errors, it is highly recommended to restart the application after secure storage has been deleted.</p>
-
-<h2>Advanced options</h2>
-
-<p>The <b>Advanced</b> tab of the preferences page offers some extra tweaks to secure storage.</p>
-
-<p>The encryption algorithm used by secure storage can be modified from this page. 
-The drop-down list displays the discovered algorithms that are provided by the Java virtual machine 
-which are compatible with secure storage.</p> 
-
-<p>Changes in the encryption algorithm are only applied to data stored after the change. If you 
-have already created a secure storage it would have to be deleted and re-created to use the newly selected encryption 
-algorithm.</p>
-
-<p>Note that the list of available algorithm might be different for different Java virtual machines and could 
-be extended by providing custom algorithms using the Java security provider mechanism.</p>
-
-<p><img alt="Related concepts" src="../images/ngrelc.png" border="0">
-  <br><A href="ref-securestorage-start.htm">Secure storage</A>
-  <br><A href="ref-securestorage-works.htm">How secure storage works</A>
-  <br><A href="ref-securestorage-recovery.htm">Password recovery</A>
-  <br><A href="ref-securestorage-passwd.htm">Life of a master password</A>
-</p>
-<p><img alt="Related reference" src="../images/ngrelr.png" border="0">
-  <br><a href="ref-securestorage-options.htm">Secure storage runtime options</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-recovery.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-recovery.htm
deleted file mode 100644
index 944344d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-recovery.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Password recovery</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">Password recovery</H1>
-
-<p>When the secure storage is used for the first time, it will generate a master password used to encrypt 
-data. This same master password will be required to retrieve data from secure storage in future. 
-In case the master password becomes unavailable, secure storage provides optional support for password recovery. 
-If the master password is lost or forgotten, providing exactly the same answers to the questions will recover 
-the master password and will allow data to be retrieved from secure storage. This can help prevent data loss 
-in case you forget or lose your master password.</p>
-
-<p>Pick password recovery questions that will be easy for you to answer, but hard for other people to guess. 
-For example, consider asking about a memorable date, a place you liked when you were a child, or your favorite quote. 
-The strength of secure storage is determined by its weakest link; don't use answers that are very short or 
-easy to guess.</p>
-
-<p><img alt="Related concepts" src="../images/ngrelc.png" border="0">
-  <br><A href="ref-securestorage-start.htm">Secure storage</A>
-  <br><A href="ref-securestorage-works.htm">How secure storage works</A>
-  <br><A href="ref-securestorage-passwd.htm">Life of a master password</A>
-</p>
-<p><img alt="Related reference" src="../images/ngrelr.png" border="0">
-  <br><a href="ref-securestorage-prefs.htm">Secure storage preference page</a>
-  <br><a href="ref-securestorage-options.htm">Secure storage runtime options</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-start.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-start.htm
deleted file mode 100644
index b2fb52f..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-start.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>Secure storage</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">Secure storage</H1>
-
-<p>The secure storage saves data in an encrypted form. On some operating systems, 
-it uses your operating system account information to provide a single sign-on experience.</p> 
-
-<p>The secure storage itself does not contain encryption code. It uses algorithms 
-supplied by the Java virtual machine and/or the operating system.</p>
-
-<h3>Frequently asked questions</h3>
-<ul>
-<li><h4>What encryption is used?</h4>
-<p>By default, the 56-bit DES algorithm is requested from the Java virtual machine.</p> 
-<p>The <b>Secure Storage</b> preference page allows you to change the encryption algorithm. Note that the new algorithm 
-will be applied to newly created secure storages only. The list of compatible algorithms depends on the Java 
-virtual machine running this application.</p>
-</li>
-<li><h4>How do I change a password?</h4>
-<p>You can change password via the <b>Change Password...</b> button on the <b>Secure Storage</b> preference page.</p>
-</li>
-</ul>
-
-<p>The <b>Secure Storage</b> preference page can be found under
-   <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.security.ui.storage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Security &gt; Secure Storage</strong></a>
-.</p>
-
-<h2>Resolving problems</h2>
-
-<ul>
-<li><h4>Lost secure storage password or invalid secure storage password</h4>
-
-<p>If you have specified password recovery questions/answers, you can use the <b>Secure Storage</b> preference page to 
-recover the master password. After the master password has been recovered, it is strongly 
-recommended that you change the master password using the <b>Change Password...</b> button on 
-the <b>Secure Storage</b> preference page.</p>
-<p>The recovered password is not displayed, but stored in the memory cache until the application is closed.</p>
-</li>
-<li><h4>If all else fails</h4>
-<p>If you have a problem with secure storage that you can not find a workaround for, the secure storage can be deleted 
-using the <b>Delete</b> button on the <b>Secure Storage</b> preference page. This, of course, will delete all the contents 
-of the secure storage. It is highly recommended that you restart the application after secure storage has been deleted.</p>
-</li>
-</ul>
-
-<p><img alt="Related concepts" src="../images/ngrelc.png" border="0">
-  <br><A href="ref-securestorage-works.htm">How secure storage works</A>
-  <br><A href="ref-securestorage-recovery.htm">Password recovery</A>
-  <br><A href="ref-securestorage-passwd.htm">Life of a master password</A>
-</p>
-<p><img alt="Related reference" src="../images/ngrelr.png" border="0">
-  <br><a href="ref-securestorage-prefs.htm">Secure storage preference page</a>
-  <br><a href="ref-securestorage-options.htm">Secure storage runtime options</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-works.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-works.htm
deleted file mode 100644
index b0fe3ee..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-securestorage-works.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>How secure storage works</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">How secure storage works</H1>
-
-<p>Let's consider a concrete example of CVS integration. When you specify a password for a CVS connection, 
-the application offers you an option to save your user name and password using secure storage.</p>
-
-<p align=center><img alt="Schema of secure storage encrypting data" src="../images/equinox_secure_storage_start.png"><br>
-</p>
-<p align=center><b>Picture 1. How secure storage works.</b></p>
-
-<p>Your CVS password is passed as data to secure storage. Secure storage uses a &quot;master&quot; password 
-to encrypt it and store the encrypted CVS password in a file on disk.</p>
-
-<p>The master password is obtained from a password provider module. The master passwords 
-are obtained in a &quot;lazy&quot; fashion, only when they are about to be used. Password providers can use 
-different techniques:</p>
-<ul>
-<li>on <i>Windows</i>, the master password is generated as a random value that is encrypted based on your 
-Windows login information and stored in secure storage;</li>
-<li>on <i>Macintosh</i>, the master password is initially created as a random value that is stored in 
-the OS keyring;</li>
-<li>the default password provider simply prompts you for a password;</li>
-<li>other password providers might be supplied in your application.</li>
-</ul>
-
-<p>When data is saved with secure storage, the password provider is selected based on the priorities from 
-the list of enabled password providers. Only that provider can be used in future to decrypt the data.</p>
-
-<p><img alt="Related concepts" src="../images/ngrelc.png" border="0">
-  <br><A href="ref-securestorage-start.htm">Secure storage</A>
-  <br><A href="ref-securestorage-recovery.htm">Password recovery</A>
-  <br><A href="ref-securestorage-passwd.htm">Life of a master password</A>
-</p>
-<p><img alt="Related reference" src="../images/ngrelr.png" border="0">
-  <br><a href="ref-securestorage-prefs.htm">Secure storage preference page</a>
-  <br><a href="ref-securestorage-options.htm">Secure storage runtime options</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-ssh2-preferences.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-ssh2-preferences.htm
deleted file mode 100644
index 482ad27..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-ssh2-preferences.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-
-<!DOCTYPE html public "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<META http-equiv="Content-Style-Type" content="text/css"><LINK rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<TITLE>SSH2</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff">
-<H1 class="Head">SSH2</H1>
-<p class="Head">The preferences on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jsch.ui.SSHPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Network Connections &gt; SSH2</strong></a>
-  preferences page are divided into 3 groups.</p>
-
-<table border="1" cellspacing="0" width="100%">
-  <tbody><tr> 
-    <td align="left" valign="middle" width="17%">General</td>
-    <td align="left" valign="middle" width="83%"> Use the options in this tab 
-      group to configure where the ssh key directory is and what keys are to be 
-      sent to a server when connecting.</td>
-  </tr>
-  
-  <tr> 
-    <td align="left" valign="middle">Key Management</td>
-    <td align="left" valign="top"> Use the options in this tab group to create, 
-      manage and export keys.</td>
-  </tr>
-  <tr>
-    <td align="left" valign="middle">Known Hosts</td>
-    <td align="left" valign="top">Use the options in this tab group to manage 
-      the keys for the known hosts.</td>
-  </tr>
-  </tbody>
-</table>
-
-<p>Here's what the General tab of the SSH2 preference page looks like:</p>
-<p><img alt="SSH2 preference page - General tab" src="../images/ssh2-general.png"></p>
-
-<p>Here's what the Key Management tab of the SSH2 preference page looks like:</p>
-<p><img alt="SSH2 preference page - Key Management tab" src="../images/ssh2-keys.png"></p>
-
-<p>Here's what the Known Hosts tab of the SSH2 preference page looks like:</p>
-<p><img alt="SSH2 preference page - Known Hosts tab" src="../images/ssh2-hosts.png"></p>
-
-<P><IMG alt="Related reference" src="../images/ngrelr.png" border="0"><BR>
-  <A href="ref-net-preferences.htm">Network Connections Preferences</A></P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-startup-workspaces.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-startup-workspaces.htm
deleted file mode 100644
index e1166ac..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-startup-workspaces.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) Eric Rizzo and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Startup and Shutdown, Workspaces</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Startup and Shutdown, Workspaces </H1>
-<P CLASS="Para"> The
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Startup.Workspaces)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Startup and Shutdown &gt; Workspaces</strong></a>
-
-  preference page allows configuration of the workspace prompting during IDE startup.</P>
-
-
-<table BORDER CELLSPACING=0 >
-  <caption>
-  </caption>
-  <tr>
-    <th> <div CLASS="Para">Option</div></th>
-    <th> <div CLASS="Para">Description</div></th>
-    <th> <div CLASS="Para">Default</div></th>
-  </tr>
-  <tr>
-    <td> <div CLASS="Para">Prompt for workspace on startup</div></td>
-    <td> <div CLASS="Para">If this option is turned on then the workbench will
-        prompt you each time it is started for what workspace to use.</div></td>
-    <td> <div CLASS="Para">On</div></td>
-  </tr>
-  <tr>
-    <td> <div CLASS="Para">Number of recent workspaces to remember</div></td>
-    <td> <div CLASS="Para">The maximum number of recently-used workspaces that will be remembered and presented in the "Workspace Launcher" dialog.</div></td>
-    <td> <div CLASS="Para">5</div></td>
-  </tr>
-  <tr>
-    <td> <div CLASS="Para">Recent workspaces</div></td>
-    <td> <div CLASS="Para">The list of recently used workspaces that are presented in the "Workspace Launcher" dialog.</div></td>
-    <td> <div CLASS="Para">&lt;none&gt;</div></td>
-  </tr>
-</table>
-
-<P>Here is what the workspaces preference page looks like:&nbsp; </P>
-
-
-<P>
-</P>
-
-
-<P>&nbsp;
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm
deleted file mode 100644
index 988aa36..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-startup.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Startup and Shutdown</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Startup and Shutdown </H1>
-<P CLASS="Para"> The
-
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Startup)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Startup and Shutdown</strong></a>
-
-  preference page allows the selection
-  of plug-ins to be automatically activated during workbench startup.&nbsp;</P>
-
-
-<P CLASS="Para">Normally plug-ins are not activated until they are needed.
-However some plug-ins may specify that they wish to be activated during startup.
-This preference page allows the selection of which of these plug-ins will
-actually be activated during startup.</P>
-
-<table BORDER CELLSPACING=0 >
-  <caption>
-  </caption>
-  <tr>
-    <th> <div CLASS="Para">Option</div></th>
-    <th> <div CLASS="Para">Description</div></th>
-    <th> <div CLASS="Para">Default</div></th>
-  </tr>
-  <tr>
-    <td> <div CLASS="Para">Refresh workspace on startup</div></td>
-    <td> <div CLASS="Para">If this option is turned on then the workbench will
-        synchronize its contents with the file system on startup.</div></td>
-    <td> <div CLASS="Para">Off</div></td>
-  </tr>
-  <tr>
-    <td> <div CLASS="Para">Confirm exit when closing last window</div></td>
-    <td> <div CLASS="Para">If this option is turned on then the workbench will
-        ask if you wish to exit when closing the last window if.</div></td>
-    <td> <div CLASS="Para">On</div></td>
-  </tr>
-  <tr>
-    <td> <div CLASS="Para">Plug-ins activated on startup</div></td>
-    <td> <div CLASS="Para">This option allows you to select which available plug-ins
-        should be activated on startup.</div></td>
-    <td> <div CLASS="Para"></div></td>
-  </tr>
-</table>
-
-<P>Here is what the Startup and Shutdown preference page looks like:&nbsp; </P>
-
-
-<P><img src="../images/Image275_startup_preference.png" alt="Startup Preference Page" border="0">
-</P>
-
-
-<P>&nbsp;
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-templates-view.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-templates-view.htm
deleted file mode 100644
index d85b5ed..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-templates-view.htm
+++ /dev/null

@@ -1,28 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-<title>Templates view</title>
-<link rel="stylesheet" href="../book.css" charset="ISO-8859-1" type="text/css">
-</head>
-<body>
-<h1>Templates view</h1>
-<p>This view allows to work with the templates of the currently active editor. The contents of this view is editor-specific and not all editors provide templates.</p>
-<p>In the example below, we see the Templates view showing the templates for a Java source file:</p>
-<p>
-<img src="../images/ref-templates-view.png" alt="Picture of the Templates view showing the templates for the Java editor" border="0" >
-</p>
-
-<p CLASS="Head">
-To add the Templates view to the current perspective, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.texteditor.TemplatesView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Templates</b></a>.
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"></p>
-<p><a href="views/ref-viewsandeditors.htm">Views and editors</a></p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm
deleted file mode 100644
index 1f9bb5e..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-texteditorprefs.htm
+++ /dev/null

@@ -1,143 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Text Editors preference page</title>
-   
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head><body bgcolor="#ffffff">
-
-<h1 class="Head">Text Editors preference page</h1>
-
-<p>The following preferences can be changed on the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.GeneralTextEditor)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<strong>General &gt; Editors &gt; Text Editors</strong></a>
-
-page.</p>
-
-<h2>Appearance options</h2>
-<table border="1" cellspacing="0" style="width: 100%;">
-  <caption>
-  </caption>
-  <thead>
-  </thead>
-  <tbody>
-  </tbody>
-  <tbody>
-    <tr> 
-      <th width="25%"> <div class="Para">Option</div></th>
-      <th> <div class="Para">Description</div></th>
-      <th> <div class="Para">Default</div></th>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Undo history size<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to set the size of the undo history for text editors. </div></td>
-      <td align="left" valign="top"> <div class="Para">200</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Displayed tab width<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you 
-          to set the displayed tab width for text editors. </div></td>
-      <td align="left" valign="top"> <div class="Para">4</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Insert spaces for tabs<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you to insert space characters in place of tab characters.</div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Highlight current line<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls whether 
-          or the current line is highlighted or not.<br>
-        </div></td>
-      <td align="left" valign="top"> On<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show print margin<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option controls whether 
-          the print margin is visible or not.</div></td>
-      <td align="left" valign="top"> <div class="Para">Off</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Print margin column<br>
-        </div></td>
-      <td align="left" valign="top"> <div class="Para">This option allows you
-          to set the print margin column position.</div></td>
-      <td align="left" valign="top"> <div class="Para">80</div></td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show line numbers<br>
-        </div></td>
-      <td align="left" valign="top">This option controls whether or not line numbers 
-        are shown on the left side of the text editor.<br> </td>
-      <td align="left" valign="top"> Off<br> </td>
-    </tr>
-    <tr> 
-      <td align="left" valign="top"> <div class="Para">Show range indicator<br>
-        </div></td>
-      <td align="left" valign="top">This option controls whether or not range 
-        indicators are shown in the text editor.<br> </td>
-      <td align="left" valign="top"> On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show whitespace characters<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls whether to display whitespace characters in text editors.<br> </td>
-      <td style="vertical-align: top;">Off<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Enable drag and drop of text<br> </td>
-      <td style="vertical-align: top;">This option controls whether text drag and drop is enabled.<br> </td>
-      <td style="vertical-align: top;">On<br></td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Warn before editing a derived file<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls whether to warn if a derived file is going to be edited.<br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Smart caret positioning at line start and end<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls whether the editor automatically positions the caret and the start or end of a line.<br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top; width: 25%;">Show affordance in hover on how to make it sticky<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls whether to show an affordance in the hover on how to make it sticky.<br> </td>
-      <td style="vertical-align: top;">On<br> </td>
-    </tr>
-    <tr> 
-      <td style="vertical-align: top;" width="25%">Appearance color options<br> 
-      </td>
-      <td style="vertical-align: top;">This option controls various appearance 
-        colors.<br> </td>
-      <td style="vertical-align: top;"><br> </td>
-    </tr>
-  </tbody>
-</table>
-
-<p></p>
-<p>Here is how the Text Editors preference page looks like:
-</p><p><img src="../images/ref-texteditorpref.png" alt="Image of the Text Editors preference page"><br>
-
-
-</p><p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../concepts/concepts-6.htm">Editor</a>
-<br>
-</p><p>&nbsp;<br>
-
-</p>
-
-
-</body></html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-workspaceswitch.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-workspaceswitch.htm
deleted file mode 100644
index 5370074..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/ref-workspaceswitch.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE doctype PUBLIC "-//w3c//dtd html 4.0 transitional//en"><html lang="en"><head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-   <meta http-equiv="Content-Style-Type" content="text/css"><title>Switching workspaces</title>
-   
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css"></head>
-
-<body>
-<h1>Switching workspaces</h1>
-<p>The current workspace for Eclipse can be switched by using the<strong> File-&gt;Switch 
-  Workspace </strong>command. If you have already switched your workspace previously 
-  the previous workspaces will be available for selection in the Switch Workspace 
-  menu.</p>
-<p>The Switch Workspace --&gt; Other.. menu item will open the switch workspace 
-  dialog. The dialog will allow you to browse for or manually enter a new workspace 
-  location. The combo will also allow you to select your previously selected workspaces.</p>
-<p><img src="../images/switch_workspace.png" width="438" height="274"></p>
-<h2>Settings Transfers</h2>
-<p>When you switch your workspace you can select settings than will be transferred 
-  to the new workspace. These settings are supplied by the org.eclipse.ui.preferenceTransfer 
-  extension. </p>
-<p>The SDK supplies transfers for:</p>
-<ul>
-  <li>Workspace Layout: Opened views, thier size, and selected perspectives.</li>
-  <li>Working Sets: The user defined working sets.</li>
-</ul>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/reference/welcome_preferences.htm b/bundles/org.eclipse.platform.doc.user/reference/welcome_preferences.htm
deleted file mode 100644
index 774788d..0000000
--- a/bundles/org.eclipse.platform.doc.user/reference/welcome_preferences.htm
+++ /dev/null

@@ -1,177 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Customize Welcome Dialog</title>
-</head>
-<body>
-
-<h1>Customize Welcome Dialog</h1>
-
-<P CLASS="Para">
-The Customize Welcome dialog which is opened using the "customize page" button above the Welcome screen allows you to modify the welcome appearance and
-content. You can select an overall theme, decide which pages will be available,
-and configure the order, layout, and visibility of the items within pages.
-</P>
-
-<p>
-<em>Note: The customize page button will only appear when the product is configured to use the
-Universal Welcome</em>.
-</p>
-
-<TABLE BORDER="1" cellspacing="0">
-<THEAD>
-<TR>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Option</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Description</P>
-</TH>
-<TH ROWSPAN="1" COLSPAN="1">
-<P CLASS="Para">
-Default</P>
-</TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Home Page Theme</span></TH>
-<TH align="left">
-<span style="font-weight: 400">This option will change the overall appearance of welcome.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">Circles</span></TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Root Pages</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Select the welcome pages you would like to see in welcome.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">Overview, Tutorials, Samples, What's New</span></TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Apply settings to all products sharing this workbench</span></TH>
-<TH align="left">
-<span style="font-weight: 400">If you have multiple products sharing the same eclipse
-workbench, using this option will cause the changes for all of them, as opposed to
-only the currently running product.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">Off</span></TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Save As...</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Converts the current preferences in this page to XML
-content compatible with the <code>introData.xml</code> format used to define the
-defaults for a product's welcome configuration. This is meant for product
-developers and assemblers, and is not needed by end users.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">N/A</span></TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Available Extensions</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Items in this container will not be shown in the
-selected welcome page.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">N/A</span></TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Left Column</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Items that should appear in the left half of the selected
-welcome page, arranged vertically from top to bottom. The bottom containers are explained
-below the table.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">N/A</span></TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Right Column</span></TH>
-<TH align="left">
-<span style="font-weight: 400">Items that should appear in the right half of the selected
-welcome page, arranged vertically from top to bottom. The bottom containers are explained
-below the table.</span>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">N/A</span></TH>
-</TR>
-
-<TR>
-<TH align="left">
-<span style="font-weight: 400">Importance</span></TH>
-<TH align="left">
-<span style="font-weight: 400">
-The importance is shown as an icon next to the item, and determines the item's
-importance relative to others. Themes may use this information to present the items
-differently, depending on their importance. To change the importance, click on the
-icon and a drop down menu will appear. The possible settings are:
-</span>
-<ul>
-<li><span style="font-weight: 400"><b>low</b> - The item will not be emphasized.</span></li>
-<li><span style="font-weight: 400"><b>medium</b> - The item will be given some emphasis.</span></li>
-<li><span style="font-weight: 400"><b>high</b> - The item will be strongly emphasized.</span></li>
-<li><span style="font-weight: 400"><b>new</b> - The item is new and will be presented as such.</span></li>
-<li><span style="font-weight: 400"><b>callout</b> - The item is of a different nature, or is special in some way (e.g. a video/animation)</span></li>
-</ul>
-</TH>
-<TH align="left">
-<span style="font-weight: 400">low</span></TH>
-</TR>
-
-</THEAD>
-<TBODY>
-</TBODY>
-</TABLE>
-
-<p>
-For each page, there are four quadrants in which to place items; two for each column.
-The quadrants will be separated in the presentation, and are used to classify
-distinct groups of items that should be kept separate from each other. If you do not
-want to separate items into four quadrants and only have columns, place all items
-in the top two quadrants.
-</p>
-
-
-<P>
-Here is what the Customize Welcome dialog looks like:
-</P>
-
-
-<P>
-<img src="../images/welcome_preference.png" alt="Welcome Preference Page" border="0">
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/welcome.htm">Welcome</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="../tasks/welcome.htm">Customizing Welcome</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm b/bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm
deleted file mode 100644
index a280cc8..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/antRunner.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-          
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>antRunner application entry point</title>
-    
-</head>   
-<body>  
-<h1>AntRunner application entry point</h1>
-     
-<p>The Ant core plug-in declares a main entry point that allows the running of Eclipse's integrated Ant support in a headless environment.
-An Ant build can then be run directly from the main platform launcher.</p>
-<p>This is an example <code>.bat</code> file that shows how to make use of the antRunner application entry point on Windows.</p>
-<pre> 
-echo off
-setlocal
-
-REM ****************************************************
-
-REM The JRE java.exe to be used
-set JAVAEXE="C:\jdk1.4.2\jre\bin\java.exe"
-
-REM The Eclipse launcher jar
-set LAUNCHERJAR="C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.0.v20070319.jar"
-
-REM The location of your workspace
-set WORKSPACE=C:\runtime-workspace
-
-REM The buildfile to use for the build
-set BUILDFILE=build.xml
-
-REM ****************************************************
-
-if not exist %JAVAEXE% echo ERROR: incorrect java.exe=%JAVAEXE%, edit this file and correct the JAVAEXE envar
-if not exist %JAVAEXE% goto done
-
-if not exist %LAUNCHERJAR% echo ERROR: incorrect equinox.launcher jar=%LAUNCHERJAR%, edit this file and correct the LAUNCHERJAR envar
-if not exist %LAUNCHERJAR% goto done
-
-if not exist %WORKSPACE% echo ERROR: incorrect workspace=%WORKSPACE%, edit this file and correct the WORKSPACE envar
-if not exist %WORKSPACE% goto done
-
-if not exist %BUILDFILE% echo ERROR: incorrect buildfile=%BUILDFILE%, edit this file and correct the BUILDFILE envar
-if not exist %BUILDFILE% goto done
-
-:run
-@echo on
-%JAVAEXE% -cp %LAUNCHERJAR% org.eclipse.equinox.launcher.Main -noupdate -application org.eclipse.ant.core.antRunner -data %WORKSPACE% -buildfile %BUILDFILE%
-
-:done
-pause
-</pre>
-        
-<p>
-	<img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-	<a href="../concepts/concepts-antsupport.htm">Ant support</a>
-</p>
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/help.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/help.xhtml
deleted file mode 100644
index 0b0fc16..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/help.xhtml
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Accessing Help</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body>
-
-<h1>Accessing Help</h1>
-
-<p>
-The workbench provides a number of ways to access help information, including 
-context-sensitive help and online documentation. See the <strong>Related
-tasks</strong> links below for details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"/><br/>
-<a href="../concepts/help.htm">Help</a><br/>
-<a href="../concepts/help_view.htm">Help view</a><br/>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"/><br/>
-<a href="help_navigate.htm">Navigating help topics</a><br/>
-<a href="help_context.htm">Accessing context-sensitive help</a><br/>
-<a href="help_settings.htm">Help display settings</a><br/>
-<a href="help_search.htm">Searching help</a><br/>
-<a href="help_accessibility.htm" filter="ws=win32">Help accessibility</a><br/>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/help_accessibility.htm b/bundles/org.eclipse.platform.doc.user/tasks/help_accessibility.htm
deleted file mode 100644
index 41b035f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/help_accessibility.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Help accessibility</title>
-</head>
-<body>
-
-<h2>Help accessibility</h2>
-
-<p>The help browser uses your operating system's settings for the font colors,
-styles, and sizes. Users with visual impairments may wish to
-change some of these settings to increase the readability of the documentation.
-</p>
-
-<p> <img src="../images/win_only.png" alt="The following information applies to Windows." border="0" /> 
-In addition, on Windows platforms using Microsoft Internet Explorer, the help 
-browser uses a component of Internet Explorer to display documentation, so changes 
-you make to its display settings also affect the help display. To change the 
-help browser's font and color settings:
-</p>
-
-<ol>
-  <li>Open Microsoft Internet Explorer.</li>
-  <li>Select <b>Tools &gt; Internet Options</b>.</li>
-  <li>On the <b>General</b> page, click the <b>Colors</b>, <b>Fonts</b>, or <b>Accessibility</b> button.</li>
-  <li>Set the formatting options you desire.</li>
-  <li>Optionally, you can specify a cascading style sheet (CSS) to apply to the content.</li>
-  <li>Click <b>OK</b> and exit Internet Explorer.</li>
-  <li>Restart the Workbench. Open the Help perspective and browse the documentation to see the changes.</li>
-</ol>
-
-<p><b>Note:</b> The help system also uses the Icon font setting on the Display Properties <b>Appearance</b> tab.</p>
-
-<p>For more information about creating a CSS, consult a CSS reference. The W3 
-Consortium (www.w3.org) has an extensive collection of information about CSS 
-and links to valuable resources.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"/><br/>
-<a href="../concepts/help.htm">Help</a><br/>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"/><br/>
-<a href="help_navigate.htm">Navigating help topics</a><br/>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/help_context.htm b/bundles/org.eclipse.platform.doc.user/tasks/help_context.htm
deleted file mode 100644
index ebe2164..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/help_context.htm
+++ /dev/null

@@ -1,115 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Accessing context-sensitive help</title>
-</head>
-<body>
-
-<h2>Accessing context-sensitive help</h2>
-
-<p>To access the context-sensitive help for a given widget:</p>
-
-<ol>
-  <li>Select the widget by putting focus on it (see the table below).</li>
-  <li>Press the <strong><code>F1</code></strong> key
-    (<strong><code>Shift+F1</code></strong> on Linux, <strong><code>Help</code>
-    </strong> on the Mac). Or, in dialogs, click on the
-    <img src="../images/help_icon.png" alt="Help button"> <strong>Help</strong>
-    icon in the button bar.</li>
-</ol>
-
-<p>This displays a description of the selected widget, 
-and usually, a list of links to related information, in the help view. If you
-  want more information than what is shown in the description, click a link to
-one of the related topic, or one of the search results appearing in the dynamic
-  help section in the help view.</p>
-  
-<p>
-<img src="../images/help_view_context.png"
-alt="Context help displayed in the Help view">
-</p>
-
-<p>Depending
-    on help preference settings, requesting context-sensitive help may display
-  context help in an <em>infopop</em> instead of help view. You can dismiss
-  the 
-infopop by clicking outside it, or by pressing <code>Esc</code>.
-</p>
-
-<p>
-<img src="../images/help_infopop.png"
-alt="Context help displayed as an infopop">
-</p>
-
-<p>
-If you want more information
-than what is shown in the infopop, click a link to the related information. This
-opens the Help browser to the selected topic and
-closes the infopop. The list of related links stays in the left hand frame, 
-so you do not have to press <code>F1</code> again if you are interested in other
-topics related 
-to the same widget.</p>
-<p>To access context sensitive help for a widget, you must put focus on it and 
-then press <code>F1</code>. The following table shows how to put focus on some of the different 
-kinds of widgets.
-</p>
-
-<table border="1" width="500" cellspacing="0" cellpadding="5" summary="Widget selection table">
-  <tr>
-    <th>Widget type</th>
-    <th>How to select it</th>
-  </tr>
-  <tr>
-    <td>Menu item (for example <strong>Save</strong> in the <strong>File</strong> menu)</td>
-    <td>Let your mouse pointer rest over it so that it is highlighted, but don't click on it.</td>
-  </tr>
-  <tr>
-    <td>Field</td>
-    <td>Put the cursor in the field.</td>
-  </tr>
-  <tr>
-    <td>Button (for example <b>Cancel</b> button on a Dialog)</td>
-    <td>Tab until the button is in focus.</td>
-  </tr>
-  <tr>
-    <td>List</td>
-    <td>Click an item in the list.</td>
-  </tr>
-  <tr>
-    <td>View or pane</td>
-    <td>Click the title bar of the View or pane.</td>
-  </tr>
-  <tr>
-    <td>checkbox</td>
-    <td>Click the checkbox (which changes its state) or use the Tab key
-      to bring it into focus.</td>
-  </tr>
-</table>
-
-<p>
-<em>Note:</em> Context-sensitive help is unavailable for toolbar buttons. Instead,
-let your mouse pointer hover over a toolbar button to view tooltip help for buttons.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/help.htm">Help</a><br>
-<a href="../concepts/help_view.htm">Help view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="help_navigate.htm">Navigating help topics</a><br>
-<a href="help_search.htm">Searching help</a><br>
-<a href="help_settings.htm">Help display settings</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/help_preferences.htm">Help preferences</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/help_navigate.htm b/bundles/org.eclipse.platform.doc.user/tasks/help_navigate.htm
deleted file mode 100644
index b3102df..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/help_navigate.htm
+++ /dev/null

@@ -1,125 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Navigating help topics</title>
-</head>
-<body>
-
-<h2>Navigating help topics</h2>
-
-<p>
-You can browse help topics using the <a href="#help_window">Help window</a> or
-<a href="#help_view">Help view</a>. Which one you use is simply a matter of
-preference; the view is well integrated with the workbench and is good for
-quick help lookups. The Help window, on the other hand, has more real estate and
-may be preferable for longer reading.
-</p>
-
-<h3>
-<a name="help_window">Using the Help window</a>
-</h3>
-
-<p>
-The Help window is a window separate from the workbench used exclusively for
-browsing, searching, and printing help. To open the window, select <b>Help &gt;
-Help Contents</b> from the menu. This opens the help window with the Contents
-view visible, which shows the table of contents.
-</p>
-
-<p>
-<img src="../images/help_window.png" alt="Help window">
-</p>
-
-<p>
-To navigate the Help window:
-</p>
-
-<ol>
-  <li>Find the topic you want to read in the table of contents by clicking
-    to expand the subtopics.</li>
-  <li>Most topics provide a list of links to related topics at the bottom.
-    Follow these links to learn more.</li>
-  <li>Use the <img src="../images/help_icon_back.png" alt="Go back" border="0">
-    <b>Go Back</b> and <img src="../images/help_icon_forward.png"
-    alt="Go forward" border="0"> <b>Go Forward</b> buttons to navigate back and
-    forth. These behave the same way as in Web browsers.</li>
-  <li>Use the <img src="../images/help_icon_home.png" alt="Home" border="0">
-   <b>Home</b> button to return to the help home page as shown above.</li>
-</ol>
-
-<h4>Maximizing help frames</h4>
-
-<p>
-The two main frames of the Help window can be maximized to take up the
-entire window. To maximize a frame, click the <img
-src="../images/help_icon_maximize.png" alt="Maximize button" border="0"> <b>Maximize</b>
-button in the toolbar, or double click on the view's title header. To return the
-view to its original size, click the <img src="../images/help_icon_restore.png"
-alt="Restore button" border="0"> <b>Restore</b> button or double click the title
-header again.
-</p>
-
-<h4>Printing help</h4>
-
-<p>
-To print a topic from the Help window:
-</p>
-
-<ol>
-  <li>Select the topic in the navigation frame.</li>
-  <li>Click the <img src="../images/help_icon_print.png" alt="Print button"
-    border="0"> <b>Print</b> button in the Help toolbar.</li>
-  <li>Select the desired printer settings, and click <b>Print</b>.</li>
-</ol>
-
-<h3>
-<a name="help_view">Using the Help view</a>
-</h3>
-
-<p>
-The 
-<a href="../concepts/help_view.htm">Help view</a> provides the same features as the Help window, but in the same window as the workbench instead of a separate one.
-</p>
-
-<h4>Capabilities</h4>
-
-<p>
-To show documentation about capabilities that are disabled in the application,
-select the <img src="../images/help_icon_capabilities.png" alt="Show All Topics button"
-border="0"> <b>Show All Topics</b> button. When you choose to show all topics in
-the table of contents, the headings for documentation about any disabled
-activities are shown in the table of contents and also appear in search results.
-</p>
-
-<h4>Show in table of contents</h4>
-
-<p>
-While reading a topic, you can find out where the topic is located in the table
-of contents by clicking the <img src="../images/help_icon_sync.png"
-alt="Show in Table of Contents button" border="0"> <strong>Show in table of
-contents</strong> button in the toolbar. This will display the table of
-contents with the topic highlighted.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/help.htm">Help</a><br>
-<a href="../concepts/help_view.htm">Help view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="help_search.htm">Searching help</a><br>
-<a href="help_context.htm">Accessing context-sensitive help</a><br>
-<a href="help_settings.htm">Help display settings</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/help_preferences.htm">Help preferences</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/help_search.htm b/bundles/org.eclipse.platform.doc.user/tasks/help_search.htm
deleted file mode 100644
index 843f28e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/help_search.htm
+++ /dev/null

@@ -1,206 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Searching help</title>
-</head>
-<body>
-
-<h2>Searching help</h2>
-
-<p>
-The help system includes a search engine that can run simple or complex queries
-on the documentation to help you find the information you are looking for.
-</p>
-
-<p>
-To search help:
-</p>
-
-<ol>
-  <li>From the main menu, select <strong>Help &gt; Search</strong></li>
-  <li>Type in the word or phrase for which you want to search</li>
-  <li>Click <strong>GO</strong> or press Enter. The list of results will be
-    displayed below</li>
-  <li>To view the content of a topic in the list of results, click on it</li>
-</ol>
-
-<p>
-Alternatively, you can search from the Help window using the <em>Search</em>
-field at the top of the window.
-</p>
-
-<h3>Refining the search results in the help view</h3>
-
-<p>
-If the search yields too many results, the information you are looking for may
-not appear in the top 10 or 15 results. You can then refine the search to reduce
-the number of results.
-</p>
-
-<p>
-To refine a search:
-</p>
-
-<ol>
-  <li>Click the <strong>Search Scope</strong> link. to expand search scope
-    section</li>
-  <li>Click on the <strong>Advanced Settings</strong> link. The Search Scope
-    preference dialog will open</li>
-  <li>Select <strong>Local Help</strong> from the list</li>
-  <li>Select the <strong>Search only the following topics</strong> button to
-    narrow down the search scope</li>
-  <li>In the working set content tree, select the topics to which you want to
-    narrow the search</li>
-  <li>Click <strong>OK</strong> to activate the changes and return to search
-    page in the Help view</li>
-  <li>Click <strong>GO</strong> again. The new list of results will appear</li>
-</ol>
-
-<p>Changing the appearance of the results</p>
-<p>Two buttons on the toolbar can be used to change the way results are 
-displayed. The <img border="0" src="../images/showcat_co.png"
-alt="Show result categories" > <b>Show result categories</b> button,
-when pressed, will cause the results to be grouped by book. The 
-<img border="0" src="../images/showdesc_co.png" alt="Show result descriptions" > 
-<b>Show result descriptions</b> button, when pressed, causes descriptions to show. </p>
-
-<h3>Highlighting Search Terms</h3>
-
-<p>
-By default, when a search result is selected, the search terms that were used
-to find the document will be highlighted. By using the <img
-src="../images/help_icon_highlight.png" alt="Highlight Search Terms" border="0">
-<b>Highlight Search Terms</b> toolbar button, you can toggle this feature on and
-off. This button is available in both the help window and the help view and each
-will remember the state of the button for displaying subsequent search results.
-</p>
-
-<h3>Query syntax</h3>
-
-<p>
-Follow the following search expression rules for searching local help content:
-</p>
-
-<ul>
-  <li>Unless otherwise stated, there is an implied AND between all search terms. 
-    In other words, topics that contain all the search terms will be returned. 
-    For example: 
-    <pre>Java project</pre>
-    <p>returns topics that contain the word <i>Java</i> and the word <i>project</i>, 
-      but does not return topics that contain only one of these words.</p></li>
-  <li>Use OR before optional terms . For example: 
-    <pre>applet OR application</pre>
-    <p>returns topics that contain the word <i>applet</i> or the word <i>application</i> 
-      (or both).</p></li>
-  <li>Use NOT before terms you want to exclude from search results. For example: 
-    <pre>servlet NOT ejb</pre>  
-    <p>returns topics that contain the word <i>servlet</i> and do not contain 
-      the word <i>ejb</i>. <b>Note:</b> NOT only works as a binary operator (that 
-      is, &quot;NOT servlet&quot; is not a valid expression).</p></li>
-  <li>Use ? for a single-character wildcard and * for a multi-character wildcard. 
-    For example: 
-    <pre>par?</pre>
-    <p>returns topics that contain <i>part</i> or <i>park</i>, but not <i> participate</i>. 
-      On the other hand:</p>
-    <pre>par*</pre>
-    <p>returns topics that contain <i>part</i>, <i>park</i>, <i>participate</i>,
-      <i>pardon</i>, and so on. <b>Note:</b> The search engine does not accept
-      terms with a wild card at first character position.</p></li>
-  <li>Use double quotation marks around terms you want treated as a phrase. For 
-    example: 
-    <pre>&quot;creating projects&quot;</pre>
-    <p>returns topics that contain the entire phrase <i>creating projects</i>, 
-      and not <i>creating</i> or <i>project</i> on its own.</p></li>
-  <li>Punctuation acts as term delimiters. For example:
-    <pre>plugin.xml</pre>
-    <p>returns hits on topics that contain <i>plugin.xml</i>, <i>plugin</i>, and 
-      <i>xml</i>, which is likely broader than you want. If you want to find just 
-      those topics containing <i>plugin.xml</i>, use double quotes, as in:</p>
-    <pre>&quot;plugin.xml&quot;</pre></li>
-  <li>The search engine ignores character case. For example: 
-    <pre>Workbench</pre>
-    <p>returns topics that contain 'workbench', 'Workbench', 'WorkBench', and 
-      'WORKBENCH'.</p></li>
-  <li>The following stop words are common English words which will be ignored 
-    (not searched for) if they appear in the search expression: a, and, are, as, 
-    at, be, but, by, in, into, is, it, no, not, of, on, or, s, such, t, that, 
-    the, their, then, there, these, they, to, was, will, with.</li>
-  <li>The search engine does &quot;fuzzy&quot; searches and word stemming. If 
-    you enter <i>create</i>, it will return hits on topics that contain <i>creates</i>, 
-    <i>creating</i>, <i>creator</i>, and so on.  To prevent search engine from stemming
-    terms, enclose them in double quotes.</li>
-</ul>
-
-<h3>Extending the search scope</h3>
-
-<p>If you cannot locate information in the local help, you can extend search
-  scope to remote info-center or search engines.</p>
-<p>To enable search engines: </p>
-<ol>
-  <li>Click the <b>Search Scope </b> link. to expand search scope section. The
-    list of search engine is displayed.</li>
-  <li> Select the ones that contain information you are looking for.</li>
-</ol>
-<p>In addition to search engines provided, you may define additional search engines.</p>
-<p>To define a new search engine: </p>
-<ol>
-  <li>Click the <b>Search Scope </b> link. to expand search scope section. </li>
-  <li>Click the <b>Advanced Settings</b> link. Search Scope preference dialog
-    opens.</li>
-  <li>Click <b>New</b>.</li>
-  <li>Select the search engine type.</li>
-  <li>Click <strong>OK</strong>.</li>
-  <li>Provide a name and a description</li>
-  <li>Select engine specific settings and scope below. For the remote search
-    engines, accessed using URL, fill in a full URL to query the engine. Use <code>{expression}</code> in
-    the place of search expression.</li>
-</ol>
-
-<h3>Defining multiple search scopes</h3>
-
-<p>By default, changing search scope modifies the search scope named &quot;default&quot;.
-  You can define multiple search scope. They will be saved, allowing to quickly
-  change search scope to one of them.</p>
-<p>To define a new search scope:</p>
-<ol>
-  <li>Click the current search scope name, beside the <b>Search Scope </b> link.
-    .Search Scope Sets dialog appears.</li>
-  <li>Click <strong>New</strong>.</li>
-  <li>Type a name, and confirm.</li>
-  <li>Select the newly created search scope.</li>
-  <li>Click <strong>OK</strong>. The new search scope becomes current.</li>
-</ol>
-<p>Changes to the search scope affect current search scope.</p>
-
-<h3>Search index generation</h3>
-
-<p>The first time you search the online help, the help system might initiate
-  an  index-generation process. This process builds the indexes for the search
-  engine 
-to use. It may take several minutes, depending on the amount of documentation
-  and whether prebuilt indexes are installed. Results of the search will be available
-  upon completion of the indexing process.</p>
-
-<p>Each time you add or modify the documentation set (for example, when you install 
-a new feature or update an existing one), the index will be updated to reflect 
-the new information set.
-</p>
-
-<p>
-<img border="0" src="../images/ngrelc.png" alt="Related concepts" width="159" height="27"><br>
-<a href="../concepts/help.htm">Help</a><br>
-<a href="../concepts/help_view.htm">Help view</a><br>
-</p>
-
-<p>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" width="159" height="27"><br>
-<a href="help_navigate.htm">Navigating help topics</a><br>
-</p>
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/help_settings.htm b/bundles/org.eclipse.platform.doc.user/tasks/help_settings.htm
deleted file mode 100644
index ec6d953..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/help_settings.htm
+++ /dev/null

@@ -1,87 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Help display settings</title>
-</head>
-<body>
-
-<h2>Help display settings</h2>
-
-<h3>External browser</h3>
-
-<p>
-The Help system can be accessed in Help view, or separate Help window. The
-window can be the default window with an embedded browser, or a full external
-browser of your choice.
-</p>
-
-<p>
-If the embedded browser is supported on your system, help will use it by default
-to display help. If you prefer to always use a full external browser, you may
-select this behavior in the
-
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.help.ui.browsersPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help preference page</b></a>.
-</p>
-
-<p>
-<img src="../images/help_window_external.png"
-alt="Help shown in external Web browser">
-</p>
-
-<h3>Context-sensitive help</h3>
-
-<p>
-By default, context-sensitive help for workbench elements is displayed in
-the Help view, and context-sensitive help for dialogs is displayed in the
-dialog's tray, which is similar to the Help view.
-</p>
-
-<p>
-<img src="../images/help_view_context.png"
-alt="Help view showing context-sensitive help">
-</p>
-
-<p>
-If you prefer to display
-context-sensitive help in infopops when working in the workbench, in dialogs or
-both, change the selection in the help preference page.
-</p>
-
-<p>
-<img src="../images/help_infopop.png"
-alt="Context-sensitive help shown as an infopop">
-</p>
-
-<h3>Displaying topics</h3>
-
-<p>
-A topic selected in the Help view can be displayed in place, in the Help view,
-or in the editor area. You can set this preference in the Help preference page.
-On some platforms, with no embedded browser, the topics will always be displayed
-in an external browser.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/help.htm">Help</a><br>
-<a href="../concepts/help_view.htm">Help view</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="help_navigate.htm">Navigating help topics</a><br>
-<a href="help_search.htm">Searching help</a><br>
-<a href="help_context.htm">Accessing context-sensitive help</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/help_preferences.htm">Help preferences</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm b/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
deleted file mode 100644
index 2599657..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/running_eclipse.htm
+++ /dev/null

@@ -1,330 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running Eclipse</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Running Eclipse</h1>
-<!-- ************* BEGIN SECTION COPIED FROM README FILE **************** -->
-<p>After installing the Eclipse SDK in a directory, you can start the Workbench
-by running the Eclipse executable included with the release (you also need a 1.4.2
-JRE, not included with the Eclipse SDK). On Windows, the executable file is called <samp>eclipse.exe</samp>,
-and is located in the <code>eclipse</code> sub-directory of the install. If
-installed at <code>c:\eclipse-SDK-3.5-win32</code>, the executable is <code>c:\eclipse-SDK-3.5-win32\eclipse\eclipse.exe</code>.
-
-<b>Note:</b> Set-up on most other operating environments is analogous. Special
-instructions for Mac OS X are listed <a href="#macosx">below</a>.</p>
-
-<h3>Allocating enough memory and solving OutOfMemoryErrors</h3>
-<p>By default, Eclipse will allocate up to 256 megabytes of Java heap memory. This should
-be ample for all typical development tasks. However, depending on the JRE
-that you are running, the number of additional plug-ins you are using, and
-the number of files you will be working with, you could conceivably have to increase this amount. 
-Eclipse allows you to pass arguments directly to the Java VM using the
-<code>-vmargs</code> command line argument, which must follow all other Eclipse specific arguments.
-Thus, to increase the available heap memory, you would typically use:</p>
-<blockquote>
-  <p><code>eclipse -vmargs -Xmx&lt;memory size&gt;</code></p>
-</blockquote>
-<p>with the <code>&lt;memory size&gt;</code> value set to greater than
-&quot;256M&quot; (256 megabytes -- the default). 
-</p>
-<p>
-When using a Sun VM, you may also need to increase the size of the permanent
-generation memory.  The default maximum is 64 megabytes, but more may
-be needed depending on your plug-in configuration and use.  When the VM runs
-out of permanent generation memory, it may crash or hang during class loading.
-This failure is less common when using Sun JRE version 1.5.0_07 or greater.
-The maximum permanent generation size is increased using the -XX:MaxPermSize=&lt;memory size&gt; argument:</p>
-<blockquote>
-  <p><code>eclipse -vmargs -XX:MaxPermSize=&lt;memory size&gt;</code></p>
-</blockquote>
-<p>This argument may not be available for all VM versions and platforms; consult your VM documentation
-for more details.
-</p>
-<p>
-Note that setting memory sizes to be larger than the amount of available physical
-memory on your machine will cause Java to &quot;thrash&quot; as it copies objects
-back and forth to virtual memory, which will severely degrade your performance.
-</p>
-<h3>Selecting a workspace</h3>
-<p>When the Workbench is launched, the first thing you see is a 
-dialog that allows you to select where the workspace will be located. The
-workspace is the directory where your work will be stored.
-If you do not specify otherwise, Eclipse creates the workspace in your
-user directory.
-This workspace directory is used as the default content area for your projects
-as well as for holding any required metadata. For shared or multi-workspace
-installs you must explicitly specify the location for your workspace using the
-dialog (or via the &quot;<code>-data</code>&quot; command line argument).</p>
-<h3>Specifying the Java virtual machine</h3>
-<p>Here is a typical Eclipse command line:&nbsp;</p>
-
-<blockquote>
-  <p><code>eclipse -vm c:\jdk1.4.2\jre\bin\javaw</code></p>
-</blockquote>
-<p><i>Tip:</i> It's generally a good idea to explicitly specify which Java VM to
-use when running Eclipse. This is achieved with the &quot;<code>-vm</code>&quot;
-command line argument as illustrated above. If you don't use &quot;<code>-vm</code>&quot;,
-Eclipse will look on the O/S path. When you install other Java-based products,
-they may change your path and could result in a different Java VM being used
-when you next launch Eclipse.</p>
-<p>To create a Windows shortcut to an installed Eclipse:</p>
-<ol>
-  <li>Navigate to <code>eclipse.exe</code> in Windows Explorer and use Create
-    Shortcut on the content menu.</li>
-  <li>Select the shortcut and edit its Properties. In the Target: field append
-    the command line arguments.</li>
-</ol>
-<p>Opening this shortcut launches Eclipse. (You can drag the shortcut to the 
-Windows Desktop if you want to keep it in easy reach.)</p>
-
-<h3><a name="macosx">Mac OS X</a></h3>
-<p>On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to 
-pass arguments to Eclipse, you'll have to edit the <code>eclipse.ini</code> file
-inside the Eclipse application bundle: select the Eclipse application bundle icon while holding down the Control Key.
-This will present you with a popup menu. Select &quot;Show Package Contents&quot; in the popup menu.
-Locate <code>eclipse.ini</code> file in the <code>Contents/MacOS</code> sub-folder and open it with your favorite text editor to edit the command line options.
-</p>
-
-<p>
-On MacOS X you can only launch a UI program more than once if you have separate
-copies of the program on disk. The reason for this behavior is that every UI
-application on Mac can open multiple documents, so typically there is no need
-to open a program twice. Since Eclipse cannot open more than one workspace, this means you have to make
-a copy of the Eclipse install if you want to open more then one workspace at
-the same time (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=139319">139319</a>).
-</p>
-
-<p>If you need to launch Eclipse from the command line, you can use the symbolic link &quot;eclipse&quot; in the
-top-level eclipse folder. It refers to the eclipse executable inside the application bundle and takes
-the same arguments as &quot;eclipse.exe&quot; on other platforms. 
-</p>
-<p>On Mac OS X 10.4 and later, you may notice a slow down when working with significant
-numbers of resources if you allow Spotlight to index your workspace. To prevent this, start
-System Preferences, select the Spotlight icon, then the Privacy tab, then click the Add button
-(&quot;+&quot;) and find your workspace directory in the dialog that appears.</p>
-<h3><a name="SharedInstall">Shared Install</a></h3>
-<p>The startup speed of a shared install can be improved if proper cache information is stored in the shared 
-install area. To achieve this, after unzipping Eclipse distribution, run Eclipse once with the &quot;-initialize&quot; 
-option from an account that has a write access to the install directory.</p>
-<!-- ************* END SECTION COPIED FROM README FILE **************** -->
-
-<h1>Advanced Topics in Running Eclipse </h1>
-
-<p>The Eclipse executable and the platform itself offer a number of execution 
-  options of interest to people developing or debugging parts of Eclipse. This 
-  is a list of the commonly used options, for a full list see the Eclipse runtime 
-  options page in the Platform Plug-in Developer Guide. The general form of running 
-  the Eclipse executable is:</p>
-
-<blockquote>
-
-<pre>eclipse [platform options] [-vmargs [Java VM arguments]]</pre>
-
-</blockquote>
-
-<TABLE width="95%" border=1 height="2005">
-  <caption>
-  <b> Eclipse Startup Parameters </b> 
-  </caption>
-  <TBODY>
-    <tr> 
-      <th width="31%"> <b>Command</b></th>
-      <th width="65%"><b>Description</b></th>
-      <TD width="4%"><b>Since</b></TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="31%"> <pre><b>-arch</b> <var>architecture</var></pre></TD>
-      <TD width="65%">Defines the processor architecture on which the Eclipse 
-        platform is running. The Eclipse platform ordinarily computes the optimal 
-        setting using the prevailing value of Java <code>os.arch</code> property. 
-        If specified here, this is the value that the Eclipse platform uses. The 
-        value specified here is available to plug-ins as Platform.getOSArch(). 
-        Example values: &quot;x86&quot;, &quot;sparc&quot;, &quot;PA-RISC&quot;, 
-        &quot;ppc&quot;.</TD>
-      <TD width="4%">2.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="31%"> <PRE><b>-application</b> <var>applicationId</var></PRE></TD>
-      <TD width="65%">The application to run. Applications are declared by plug-ins 
-        supplying extensions to the org.eclipse.core.runtime.applications extension 
-        point. This argument is typically not needed. If specified, the value 
-        overrides the value supplied by the configuration. If not specified, the 
-        Eclipse Workbench is run.</TD>
-      <TD width="4%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="31%"> <pre><b>-clean</b></pre></TD>
-      <TD width="65%">Cleans cached data used by the OSGi framework and Eclipse runtime. 
-      Try to run Eclipse once with this option if you observe startup errors after install, 
-      update, or using a shared configuration. </TD>
-      <TD width="4%">3.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="31%"> <pre><b>-configuration</b> <var>configURL</var></pre></TD>
-      <TD width="65%">The location for the Eclipse Platform configuration file, 
-        expressed as a URL. The configuration file determines the location of 
-        the Eclipse platform, the set of available plug-ins, and the primary feature. 
-        Note that relative URLs are not allowed. The configuration file is written 
-        to this location when the Eclipse platform is installed or updated. </TD>
-      <TD width="4%">2.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="31%"><PRE><b>-consolelog</b></PRE></TD>
-      <TD width="65%">Mirrors the Eclipse platform's error log to the console 
-        used to run Eclipse. Handy when combined with <code>-debug</code>.</TD>
-      <TD width="4%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="31%"> <PRE><b>-data</b> <var>workspacePath</var></PRE></TD>
-      <TD width="65%">The path of the workspace on which to run the Eclipse platform. 
-        The workspace location is also the default location for projects. Relative 
-        paths are interpreted relative to the directory that Eclipse was started 
-        from.</TD>
-      <TD width="4%">1.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="31%"> <PRE><b>-debug</b> [<var>optionsFile</var>]</PRE></TD>
-      <TD width="65%"> Puts the platform in debug mode and loads the debug options 
-        from the file at the given location, if specified. This file indicates 
-        which debug points are available for a plug-in and whether or not they 
-        are enabled. If a file location is not given, the platform looks in the 
-        directory that eclipse was started from for a file called ".options". 
-        Both URLs and file system paths are allowed as file locations. </TD>
-      <TD width="4%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD width="31%" height="133" vAlign=top> <PRE><b>-dev</b> [<var>classpathEntries</var>]</PRE></TD>
-      <TD width="65%">Puts the platform in development mode. The optional classpath 
-        entries (a comma separated list) are added to the runtime classpath of 
-        each plug-in. For example, when the workspace contains plug-ins being 
-        developed, specifying <code>-dev bin</code> adds a classpath entry for 
-        each plug-in project's directory named <code>bin</code>, allowing freshly 
-        generated class files to be found there. Redundant or non-existent classpath 
-        entries are eliminated.</TD>
-      <TD width="4%">1.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="31%"> <pre><b>-initialize</b></pre></TD>
-      <TD width="65%"> Initializes the configuration being run. All runtime related data 
-      structures and caches are refreshed. Handy with shared installs: running Eclipse once 
-      with this option from an account with write privileges will improve startup 
-      performance.</TD>
-      <TD width="4%">3.0</TD>
-    </TR>
-    <TR> 
-      <TD vAlign=top width="31%"> <pre><b>-keyring</b> <var>keyringFilePath</var></pre></TD>
-      <TD width="65%"> The location of the authorization database (or &quot;key 
-        ring&quot; file) on disk. This argument must be used in conjunction with 
-        the <code>-password</code> option. Relative paths are interpreted relative 
-        to the directory that Eclipse was started from.</TD>
-      <TD width="4%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="31%"> <pre><b>-nl</b> <var>locale</var></pre></TD>
-      <TD width="65%">Defines the name of the locale on which the Eclipse platform 
-        is running. The Eclipse platform ordinarily computes the optimal setting 
-        automatically. If specified here, this is the value that the Eclipse platform 
-        uses. The value specified here is available to plug-ins as Platform.getNL(). 
-        Example values: &quot;en_US&quot; and &quot;fr_FR_EURO&quot;.</TD>
-      <TD width="4%">2.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="31%"> <PRE><b>-nosplash</b></PRE></TD>
-      <TD width="65%">Runs the platform without putting up the splash screen.</TD>
-      <TD width="4%">1.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="31%"> <PRE><b>-os</b> <var>operatingSystem</var></PRE></TD>
-      <TD width="65%">Defines the operating system on which the Eclipse platform 
-        is running. The Eclipse platform ordinarily computes the optimal setting 
-        using the prevailing value of Java <code>os.name</code> property. If specified 
-        here, this is the value that the Eclipse platform uses. The value specified 
-        here is available to plug-ins as Platform.getOS(), and used to resolve 
-        occurrences of the <code>$os$</code> variable in paths mentioned in the 
-        plug-in manifest file. Example values: &quot;win32&quot;, &quot;linux&quot;, 
-        &quot;hpux&quot;, &quot;solaris&quot;, &quot;aix&quot;.</TD>
-      <TD width="4%">1.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="31%"> <pre><b>-password</b> <var>password</var></pre></TD>
-      <TD width="65%">The password for the authorization database. Used in conjunction 
-        with the <code>-keyring</code> option.</TD>
-      <TD width="4%">1.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="31%"> <PRE><b>-perspective</b> <var>perspectiveId</var></PRE></TD>
-      <TD width="65%">The perspective to open in the active workbench window on 
-        startup. If this parameter is not specified, the perspective that was 
-        active on shutdown will be opened.</TD>
-      <TD width="4%">1.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top width="31%"> <pre><b>-plugincustomization</b>
-	  <var>propertiesFile</var></pre></TD>
-      <TD width="65%">The location of a properties file containing default settings 
-        for plug-in preferences. These default settings override default settings 
-        specified in the primary feature. Relative paths are interpreted relative 
-        to the directory that eclipse was started from.</TD>
-      <TD width="4%">2.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top> <pre><b>-product</b> <em>productId</em><br></pre></TD>
-      <TD height="16">The ID of the product to run. The product gives the launched 
-        instance of Eclipse its personality, and determines the product customization 
-        information used. This replaces -feature, which is still supported for 
-        compatibility.</TD>
-      <TD height="16">3.0</TD>
-    </tr>
-    <TR> 
-      <TD vAlign=top width="31%" height="16"><pre><b>-refresh</b> </pre></TD>
-      <TD width="65%" height="16">Option for performing a global refresh of the 
-        workspace on startup. This will reconcile any changes that were made in 
-        the file system since the platform was last run. </TD>
-      <TD width="4%" height="16">1.0</TD>
-    </TR>
-    <TR> 
-      <TD vAlign=top width="31%" height="16"><pre><b>-showlocation</b> [<var>workspaceName</var>]</pre></TD>
-      <TD width="65%" height="16">Option for displaying the location of the workspace 
-        in the window title bar. In release 2.0 this option only worked in conjunction 
-        with the -data command line argument. In 3.2, an optional workspace name argument was added that  displays the  provided name  in the window title bar instead of the location of the workspace. </TD>
-      <TD width="4%" height="16">2.0</TD>
-    </TR>
-    <tr> 
-      <TD vAlign=top width="31%"> <PRE><b>-vm</b> <var>vmPath</var></PRE></TD>
-      <TD width="65%">The location of Java Runtime Environment (JRE) to use to 
-        run the Eclipse platform. If not specified, the launcher will attempt to find
-        a JRE.  It will first look for a directory called <code>jre</code> as a sibling
-        of the Eclipse executable, and then look on the operating system path.  
-        Relative paths are interpreted relative to the directory that eclipse was started from.</TD>
-      <TD width="4%">1.0</TD>
-    </tr>
-    <tr> 
-      <TD vAlign=top> <PRE><b>-vm</b><strong>args</strong> <em>args</em></PRE></TD>
-      <TD>When passed to the Eclipse, this option is used to customize the operation 
-        of the Java VM used to run Eclipse. If specified, this option must come 
-        at the end of the command line. The given arguments are dependant on VM 
-        that is being run.</TD>
-      <TD>1.0</TD>
-    </tr>
-  </TBODY>
-</TABLE>
-
-<p>All arguments following (but not including) the -vmargs entry are passed
-directly through to the indicated Java VM as virtual machine arguments (that is,
-before the class to run).  <b>Note:</b> If an Eclipse startup argument, such as -data,
-is provided after the Java vm arguments (-vmargs), Eclipse will not start and you will receive 
-a &quot;JVM terminated. Exit code=1&quot; error.
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm b/bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm
deleted file mode 100644
index 4ec3202..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/task-team-cmdlineclient.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running the CVS command-line client outside of Eclipse</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Running the CVS command-line client outside of Eclipse</H1>
-<h2>Compatibility</h2>
-<p>Because the Eclipse CVS plug-in stores its meta information in a format that 
-  is compatible with the command-line CVS client you should be able to use a CVS 
-  command line client against Eclipse workspace files on disk. The metadata is 
-  stored in CVS/ sub-directories but you rarely see them within Eclipse. They are 
-  marked as private which causes them to be hidden from view. If you open a (non-Eclipse) 
-  file explorer you will see that these directories and their contents appear 
-  on the file system.</p>
-<h2> Don't forget to refresh!</h2>
-
-
-<p>Whenever you use external tools to modify workspace files, you must perform 
-  a <strong>Refresh</strong> from within Eclipse to make the workspace aware of 
-  the changes. If you get a <em>resource out of sync</em> error in Eclipse it 
-  is a sign that there are resources in Eclipse that have been modified outside 
-  of Eclipse. One solution is to perform a refresh (available from a resource's 
-  popup menu) on any resources or projects that where modified outside of Eclipse. 
-  There is also a preference to refresh automatically.</p>
-<h3>Caveats</h3>
-<p><strong>1. Deleted folders</strong></p>
-<p>You may encounter unexpected behavior when using the command-line CVS client 
-  in conjunction with deleted folders. Eclipse's CVS support keeps track of deleted 
-  folders and their contents so that, on the next synchronization, the Synchronize 
-  view can properly report on the changes. This information is kept outside of 
-  the CVS meta folder structure. This is because in CVS you normally inform the 
-  repository of deletions prior to deleting them locally, which is a different 
-  workflow than we like to support in the Synchronization view. Thus it is recommended 
-  that you do not use the command-line CVS client while you have pending deletions 
-  to commit. In some circumstances it could cause the Synchronize view to display 
-  incorrect contents, although it will not cause any lost work. </p>
-<p><strong>2. CVS directories appear in the workbench</strong></p>
-<p>When you use the command-line CVS the CVS folders can sometimes appear 
-  in one of the navigation views. There are some cases where CVS folders are not hidden from the 
-  UI as you would expect. For instance, CVS folders will appear if a user 
-  imports a CVS project into Eclipse before the CVS plug-in is loaded. To avoid 
-  this, open the CVS Repositories view (thus loading the CVS plug-in) before importing 
-  CVS projects into Eclipse. </p>
-<p><strong>3. The 'extssh' connection method</strong></p>
-<p>The <em>extssh</em> connection method is unique to Eclipse CVS and doesn't 
-  exist in the command-line CVS client. If you are using <em>extssh</em> to connect 
-  to a SSH2 repository and would like to use the command line client for some 
-  CVS operations you can configure the <em>ext</em> connection method to use <em>extssh</em> 
-  when inside Eclipse.</p>
-<ol>
-  <li>Create a new repository location that uses the <em>ext</em> connection method. 
-    The repository path, host, and user should be identical to those in the <em>extssh</em> 
-    location.</li>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ExtMethodPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; CVS &gt; Ext Connection Method</strong></a> preference page.</li>
-  <li>Enable<strong> Use another connection method type to connect</strong> and 
-    choose <em>extssh</em>.</li>
-  <li>Now when you use the <em>ext</em> connection method inside Eclipse, <em>extssh</em> 
-    will be used instead of an external client.</li>
-</ol>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-95.htm">Changing the properties of a CVS repository location</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-117a.htm">Using projects checked out with another CVS tool</a>
-</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm
deleted file mode 100644
index 4da8cc0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Customizing the Workbench</title>
-</head>
-<body>
-
-<h1>Customizing the Workbench</h1>
-
-<p>Many aspects of the appearance and behavior of the Workbench
- can be customized to suit your individual needs. For example, you can:
-</p>
-
-<ul>
-<li>Rearrange where items appear in the main toolbar.</li>
-<li>Change the key bindings used by editors.</li>
-<li>Change the fonts and colors which are used.</li>
-</ul>
-
-<p>See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-2.htm">Workbench</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="welcome.htm">Customizing welcome</a><br>
-<a href="ttoolbars.htm">Rearranging the main toolbar</a><br>
-<a href="tkeybindings.htm">Changing the key bindings</a><br>
-<a href="topenmode.htm">Controlling single and double click behavior</a><br>
-<a href="tasks-20.htm">Changing fonts and colors</a><br>
-<a href="tasks-9.htm">Changing the placement of the tabs</a><br>
-<a href="timpandexp.htm">Importing and Exporting Preferences</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm
deleted file mode 100644
index a44b48b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a version of a project</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a version of a project</H1>
-
-<P><em>Prerequisite</em>: The project that you want to version must first be in 
-  the workspace.
-</P>
-
-<P><em>Tip</em>: It is often preferable to synchronize resources with the CVS 
-  repository before versioning. This will ensure that there are no outstanding 
-  incoming or outgoing changes that might be accidentally excluded from the version.
-</P>
-
-<P>To make a version of a project:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the project that you want to version.</li>
-  <li>From the project's context menu, select <b> Team &gt; Tag as Version</b>.</li>
-  <li>Enter the name of the version you wish to create.</li>
-  <li>Click <b>OK</b> to close the Tag Resources dialog and create the version.</li>
-</ol>
-
-<p><em>Tip:</em> You can browse existing versions of your project by clicking 
-  on the <b>Details</b> button in the Tag Resources dialog. Clicking <b>Refresh 
-  from Repository</b> should populate the Existing Versions list. It is sometimes 
-  helpful to see existing versions before naming your new version.
-</p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-17a.htm">Local history</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-118.htm">Versioning projects in the repository</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-107b.htm">Enabling the CVS resource decorations</a> 
-</P>
-   
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm
deleted file mode 100644
index d79a6ce..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100a.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Branching</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Branching</H1>
-
-<P>Creating a branch and releasing resources to that branch is useful in cases 
-  where you are not yet ready to put your changes in the main development flow. 
-  It is also useful for creating incremental patches to existing versions.
-</P>
-
-<P>To create a branch:
-</P>
-
-<ol>
-  <li>From the context menu of the project, select <b>Team &gt; Branch</b>.
-  <p><img src="../images/cvs_new_branch.png" alt="Create a new CVS Branch dialog" border="0">
-  </p></li>
-  <li>Enter the Branch Name for the new branch in the text area.</li>
-  <li>A default version tag  name will be proposed by the dialog. If you do not like the suggested name, you can change
-   it in the text area.</li>
-  <li>If you would like to start working in the branch immediately, make sure 
-    the checkbox is selected.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><em>Note:</em> The Version Name is important; you will need this when you want 
-  to merge your changes later on. It identifies the point at which the branch 
-  was created.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm
deleted file mode 100644
index 0954990..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100b.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Merging from a branch</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Merging from a branch</H1>
-
-<P>After creating and working in a CVS branch for some time, you may want to merge 
-  your changes from the branch into another branch, or into HEAD. To do this, 
-  you will need to know:
-</P>
-
-<ol>
-  <li>The name of the branch or version that contains your changes.</li>
-  <li>The version from which the branch was created. This is the version name 
-    that you supplied when branching.</li>
-</ol>
-
-<p>To merge your changes:
-</p>
-
-<ol>
-  <li>Ensure that the destination is loaded into your workspace. For example, 
-    if you wish to merge your changes into HEAD, make sure the project is shared 
-    with HEAD in your workspace. To do this, select the project and choose <b>Replace 
-    With &gt; Another Branch or Version</b> from the context menu. Then select 
-    the branch to replace with.</li>
-  <li>Select the project and choose <b>Team &gt; Merge</b>.</li>
-  <li>Enter the branch or version which contains the changes you want to merge.</li>
-  <li>The merge dialog will try to guess an appropriate start point. If that fails, 
-    enter the start point of the merge. This is the version from which the branch 
-    was created. Click <b>Finish</b>.</li>
-  <li>A CVS Merge synchronization will be added to the Synchronize view, showing 
-    all differences between your workspace and the branch with the changes.</li>
-  <li>Load all of the desired changes into the workspace. This may be accomplished 
-    by either manually merging changes, or by choosing <b>Update</b>, <b>Override 
-    and Update</b>, or <b>Mark as Merged</b> from the tree's context menu.</li>
-  <li>After all desired changes are in the workspace, choose <b>Team &gt; Synchronize 
-    with Repository</b>. You may then commit all the changes to the repository.</li>
-</ol>
-<p><em>Tip</em>: If you don't know the start point of the merge, you can choose 
-  to perform the merge directly into the workspace. This relies on the CVS server 
-  to pick an appropriate start point. Because the merge is performed directly 
-  into the workspace, CVS may introduce a text based conflict markup into the 
-  file. This markup is typically hard to deal with so merging directly into the 
-  workspace should only be done when necessary.</p>
-<h3>Merge actions</h3>
-<p>The actions in the merge editor complement the manual merge toolbar actions 
-  that are available in the bottom half of the merge editor.</p>
-<table width="100%" border="0">
-  <tr> 
-    <td width="20%"><strong>Merge</strong></td>
-    <td width="80%">Running this action will bring the changes into the file in 
-      the workspace. Any conflicts that are not auto-mergeable will be skipped.</td>
-  </tr>
-  <tr> 
-    <td><strong>Override and Update</strong></td>
-    <td>This action is enabled on files with conflicting changes. Running this 
-      action will discard any local changes you have and replace the file with 
-      the remote contents.</td>
-  </tr>
-  <tr> 
-    <td><strong>Mark as Merged</strong></td>
-    <td>This action will remove the selected changes from the view. The changes 
-      will only reappear if the remote state of the resource changes and the CVS 
-      Merge Synchronization is refreshed.</td>
-  </tr>
-</table>
-<p><em>Tip</em>: You can perform ongoing merges by pinning a CVS Merge Synchronization 
-  in the Synchronize view. This will allow you to keep your workspace up-to-date 
-  with the changes released to a different branch.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" > 
-  <br>
-  <a href="../reference/ref-47.htm">CVS</a> <br>
-  <a href="../reference/ref-41a.htm">Merge wizard</a><br>
-  <a href="../reference/ref-33a.htm">CVS Merge Synchronization</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm
deleted file mode 100644
index 32b1bc7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d.htm
+++ /dev/null

@@ -1,98 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Version control life cycle: adding and ignoring resources</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Version control life cycle: adding and ignoring resources</H1>
-
-<p>When committing resources, often there are resources that you do not want to 
-  store in the repository. For example, external editors might create temporary 
-  files in your project, compilation of .java files might create .class files, 
-  or some build operations might result in binary files. When put together, these 
-  generated files may be quite large. They may also be regenerated whenever 
-  a build is performed, resulting in many outgoing changes. Typically these are 
-  not files that one wants to persist in the repository or to share with other 
-  members of a team.
-</p>
-
-<p>Team CVS has two related tasks that allow you to control which files are stored 
-  in the repository: adding a resource to version control, and ignoring a resource. 
-</p>
-  
-<h2>Adding a file to version control</h2>
-
-<p>Team CVS does not automatically add files to version control. Rather, it's 
-  your choice to explicitly add files to version control. This is accomplished 
-  by selecting the <b>Team &gt; Add to Version Control</b> menu.
-</p>
-
-<p>When performed on a file, it will add that file to version control. The result 
-  is that the CVS repository immediately creates an entry so that it can 
-  start maintaining history state for that file. This occurs even before you commit 
-  the file to the repository.
-</p>
-
-<p>When adding a folder or project, the action will recursively descend into sub-folders, 
-  adding those files it finds to version control, provided the files have not 
-  been explicitly ignored. </p>
-
-<p><em>Tip:</em> When committing files, if the selection either directly or recursively 
-  contains files which have not been added to version control, you will be prompted 
-  whether or not you want them added. This is a convenience function to help ensure 
-  that you do not miss committing new resources which were unintentionally never 
-  added. </p>
-
-<h2><i>How may I ignore thee, let me count the ways</i></h2>
-
-<P>There are several facilities that allow you to specify which resources should 
-  be excluded from version control:
-</P>
-
-<ol>
-  <li>There is a global preference which you can use for ignoring files and directories 
-    that match a certain filename pattern. For example, if you create a global 
-    ignore for <samp>/bin</samp>, and any resource that matches &quot;bin&quot; 
-    in any directory in the workspace will be ignored for version control. Use the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.IgnorePreferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Team &gt; Ignored Resources</b></a>
-    preference page to globally exclude resources from version control.</li>
-  <li>Any resource marked as <i>derived</i> will be automatically ignored for 
-    version management by Team CVS. Some builders, such as the Java builder, mark 
-    all of its build output (e.g. .class files) as derived.</li>
-  <li>CVS supports the creation of a special <i>.cvsignore</i> file whose contents 
-    describe which files or folders to ignore for version management. The .cvsignore 
-    file only applies the pattern to resources in the <i> same</i> directory as 
-    the .cvsignore file itself.</li>
-</ol>
-
-<P><em>Tip</em>: Once a resource is under version control, it cannot be 
-  subsequently ignored easily. This is why you must invoke an explicit command 
-  to add resources to version control.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100d1.htm">Creating a global ignore pattern</a><br>
-<a href="tasks-100d2.htm">Authoring the CVS .cvsignore file</a><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-113.htm">Updating</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm
deleted file mode 100644
index e0009e0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a global ignore pattern</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a global ignore pattern</H1>
-
-<P>When synchronizing resources, often there are resources that you do not want 
-  to commit to the repository. The Workbench provides a global pattern matching 
-  facility for ignoring resources that can appear anywhere in your project hierarchy.
-</P>
-
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.IgnorePreferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Team &gt; Ignored Resources</b></a> preference page.
-    This displays a list of resource 
-    name patterns against which resources will be screened, before they are considered 
-    as candidates for version control.</li>
-  <li>Click the <b>Add Pattern...</b> push button and type the pattern that you want to match, 
-    for example <samp>*.obj</samp>.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>All files with an extension that matches the pattern that you added will be 
-  excluded from version control.
-</p>
-
-<p>The patterns that you define may contain the wildcard characters * and ?. The 
-  asterisk represents any sequence of zero or more characters, the question mark 
-  represents a single character. For example, you can specify a pattern 
-  of <samp>*~</samp>, which would match any temporary files that end with a tilde 
-  (~). Any file or directory that matches any one of the patterns will be ignored 
-  when files are being considered for version control. You can temporarily disable 
-  ignoring the resource name pattern by deselecting it from the list. You do not 
-  have to remove the specified pattern from the list.
-</p>
-  
-<p>It is important to note that the path leading up to the resource name is not 
-  included in the matching. For example, for the file &quot;/path/to/file.txt&quot;, 
-  only the string &quot;file.txt&quot; is matched against the patterns.
-  This facility is not intended for specifying fully-qualified path names but 
-  for specifying globally applicable patterns.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-100d1b.htm">Overriding or removing resource ignore patterns</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm
deleted file mode 100644
index c05cec0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d1b.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Overriding or removing resource ignore patterns</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Overriding or removing resource ignore patterns</H1>
-
-<p>After you have added global file-matching patterns to the list of files to 
-  be ignored for version management, you may wish to occasionally override the 
-  &quot;ignore&quot;.
-</p>
-
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.IgnorePreferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Team &gt; Ignored Resources</b></a> preference page.</li>
-  <li>To temporarily override one or more of the file-matching patterns, clear 
-    their checkboxes.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>Files that match the patterns you have deselected will be considered for version 
-  control.
-</p>
-
-<p>To permanently remove a pattern, select it and click <b>Remove</b>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-100d1.htm">Creating a global ignore pattern</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm
deleted file mode 100644
index dae9a45..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-100d2.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Authoring the CVS .cvsignore file</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Authoring the CVS .cvsignore file</H1>
-
-<P>When committing resources, often there are resources that you do not want to 
-  add to version control. One way you can do this is by using the CVS &quot;ignore&quot; 
-  facility, which reads the contents of the file <i>.cvsignore</i> to determine 
-  what to ignore.</P>
-
-<P>The <i>.cvsignore</i> file can be added to any directory of a project. Many 
-  existing CVS projects already contain several of these files. This text file 
-  consists of a list of files, directories, or patterns.
-</P>
-
-<P>For example, to add a .cvsignore file to ignore the entire bin directory of
-  an existing project:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select a project that contains a /bin directory. 
-    The bin directory will commonly contain the projects build output. These are 
-    files that are generated from the project's source files and are usually not 
-    version-controlled.</li>
-  <li>From the pop-up menu for the project, select <b> New &gt; File</b>.&nbsp;</li>
-  <li>Type <i>.</i><samp>cvsignore</samp> as the file name, then press <b>Finish</b>. 
-    The file will be created in your project's root directory. You should see 
-    it in one of the navigation views.</li>
-  <li>Enter <samp>bin</samp> in the .cvsignore file and save it.</li>
-  <li>Select the project.&nbsp; From the context menu, select the <b> Team &gt; 
-    Synchronize with Repository</b> menu item.&nbsp; Notice that the bin directory 
-    does not show as an outgoing change. It is ignored.</li>
-</ol>
-
-<P>The cvsignore file consists of a list of files, directories, or patterns. 
-  In a similar way to the global ignore facility, the wildcards * and ? may be 
-  present in any entry in the .cvsignore file. Any file or sub-directory 
-  <i>in the current directory</i> that matches any one of the patterns will 
-  be ignored.
-</P>
-
-<p><b>Tip:</b> In the Team menu and in the Synchronize view resource context menu there is a menu item (<b>Add to .cvsignore</b>)
-for adding a file pattern
-to the appropriate .cvsignore file. This menu item is enabled for resources that are not yet under CVS version
-control.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-100d1.htm">Creating a global ignore pattern</a>
-</p>
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm
deleted file mode 100644
index 64f5e56..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-101.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing resources with repository versions</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Comparing resources with repository versions</H1>
-
-<P>To compare Workbench resources with those in the repository:
-</p>
-
-<ol>
-  <li>Select a resource in one of the navigation views.</li>
-  <li>From the resource's pop-up menu, select one of the following menu items: 
-    <ul>
-      <li><b>Compare With &gt; Latest From &lt;Branch Name&gt;</b> or <strong>&lt;Version&gt;</strong>- 
-        Compare the Workbench resource with the latest resources currently committed 
-        to the branch that the local project is shared with or if the local project 
-        is checked out as a version then compare against the version. A compare 
-        editor will be opened. This editor will display a tree of all resource 
-        differences between the workspace resource and the latest resources in 
-        the repository.</li>
-      <li><b>Compare With &gt; Another Branch or Version</b> - Compare the Workbench 
-        resource with a specific version or branch that you select in the repository. 
-        A compare editor will be opened. The editor will display a tree of all 
-        resource differences between the workspace resource and the resources 
-        in the specified version or branch.</li>
-      <li><b>Compare With &gt; History...</b> - (available only on a file) Compare 
-        the Workbench file with another revision of the file. Based on your preference 
-        settings, either the History view or a dialog will open. The History view (or dialog)
-        will contain a table of all available revisions 
-        of the selected file. Selecting one of the revisions will show the differences 
-        between the workspace revision and the selected revision. </li>
-    </ul>
-  </li>
-</ol>
-<p><em>Tip</em>: When comparing with a branch or version, you can specify a particular 
-  date instead of a version or branch tag. This can be done by right clicking 
-  on the <strong>Dates</strong> category in the tag selection list and choosing 
-  <strong>Add Date</strong>. A Date Tag dialog is displayed that allows you to 
-  specify a date and optionally a time. After you click <strong>Ok</strong>, the 
-  date tag will appear in the tag selection list.</p>
-<P CLASS="Intro"><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a></p>
-<p>
-
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm
deleted file mode 100644
index dc92fda..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-103.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Replacing resources in the Workbench</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Replacing resources in the Workbench</H1>
-
-<p>To replace Workbench resources with versions in the repository:
-</p>
-
-<ol>
-  <li>Select a resource in one of the navigation views.</li>
-  <li>From the resource's pop-up menu, select one of the following menu items: 
-    <UL>
-      <LI><b>Replace With &gt; Latest From &lt;Branch Name&gt;</b> or <strong>&lt;Version&gt;</strong> 
-        - replace the Workbench resource with the latest resources currently committed 
-        to the branch that the local project is shared with or if the local project 
-        is checked out as a version then replace with the same version.</LI>
-      <LI><b>Team &gt; Revert to Base</b> 
-        - replace the Workbench resource with the last checked out revision. 
-        Deleted files are restored. </LI>  
-      <LI><b>Replace With &gt; Another Branch or Version</b> - replace the Workbench 
-        resource with a specific version or branch that you select in the repository. 
-        When you select this option, another window opens, so that you can browse 
-        through the branch and version tags in the repository and select the one 
-        that you want.</LI>
-      <LI><b>Replace With &gt; History...</b> - (available only on a file) replace 
-        the Workbench file with another revision of the file. Based on your preference settings,
-        either the History view or a dialog will open. The History view (or dialog) 
-        will contain a table of all available revisions of the selected file.
-        Selecting one of the revisions will show the differences between the workspace 
-        revision and the selected revision. To replace the workspace revision, you
-        should select the revision that you want and choose 'Get Contents' from the 
-        context menu. This will replace the contents of the workspace file with those
-        of the selected revision.</LI>
-      <LI><strong>Team &gt; Switch to Another Branch or Version</strong> - this 
-        update will replace Workbench resources with those on the tag specified 
-        in the Update dialog. The behavior differs from the above replace operations 
-        in that uncommitted modifications in the Workbench are not replaced but 
-        instead are &quot;moved&quot; to the resources from the selected tag. 
-        For more details on the specifics of this operation, see the CVS documentation 
-        at <a href="http://ximbiot.com/cvs/">http://ximbiot.com/cvs/</a> relating to the 
-        use of the <em>-r </em>option with <em>cvs update</em>.</LI>
-    </UL>
-  </li>
-</ol>
-<p><em>Tip</em>: When replacing with a branch or version or when updating, you 
-  can specify a particular date instead of a a version or branch tag. This can 
-  be done by right clicking on the <strong>Dates</strong> category in the tag 
-  selection list and choosing <strong>Add Date</strong>. A Date Tag dialog is 
-  displayed that allows you to specify a date and optionally a time. After you 
-  click <strong>Ok</strong>, the date tag will appear in the tag selection list.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-119.htm">Viewing a file's revision history</a><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm
deleted file mode 100644
index eecce14..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing CVS team settings</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing CVS team settings</H1>
-
-<P>You can customize the settings related to a number of CVS team views and operations.
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.TeamPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Team</b></a> preference page. You will see a number of general Team options. These options can 
-    be used by any Eclipse integrated repository. In our case, they are all applicable 
-    to CVS.</li>
-  <li>You will also see a
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Team &gt; CVS</b></a> preference page containing
-  various CVS options.</li>
-  <li>Underneath the <strong>Team &gt; CVS</strong> preference page are several sub-pages. 
-    For example, there are pages for <strong>Watch/Edit</strong>, <strong>Console</strong>, 
-    <strong>Label Decorations</strong> and <strong>SSH2</strong> among others.</li>
-</ol>
-
-<p>In the Preferences dialog, you can search by keywords such as CVS or SSH2 in 
-  order to show only the relevant pages.</p>
-
-<h2>Changing CVS Project Settings</h2>
-<p>You can change CVS project settings in the properties dialog of a project.</p>
-<ul>
-  <li>From the context menu of a view showing the project, select Properties</li>
-  <li>Click on the CVS category</li>
-</ul>
-<p>From this dialog, you can:</p>
-<ul>
-  <li>Enable Watch/Edit on the project.</li>
-  <li>Specify whether new or absent folders should be fetched when an update is 
-    performed.</li>
-  <li>Change the repository location to which the project is associated.</li>
-</ul>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-19cvs.htm">CVS Preference pages</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm
deleted file mode 100644
index 3b83865..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105a.htm
+++ /dev/null

@@ -1,53 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Restoring deleted files from the repository</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Restoring deleted files from the repository</H1>
-
-<P>The CVS plug-in allows you to delete files from the CVS repository. If you 
-  delete a managed file and commit the deletion to the server, the file is deleted 
-  from the current branch or version. Although the file has been deleted from 
-  the current branch, the file and its previous revisions are actually still on 
-  the server. The CVS plug-in provides a tool to help restore a file to your workspace 
-  that has previously been deleted from the CVS repository:</p>
-
-<ol>
-  <li>Select a folder managed by CVS and from the context menu select <strong>Team 
-    &gt; Restore from Repository</strong>.</li> 
-  <li>The repository will be searched for deleted files and the list will be shown 
-    in a dialog.</li> 
-  <li>Select a file in the left most pane to display the revisions of the file 
-    that are available in the repository.</li>
-  <li>Select a revision in the right-most pane to view the contents in the bottom 
-    text pane.</li>
-  <li>Check the revision that you would like to restore.</li> 
-  <li>Click <strong>Finish</strong> once you have checked off a revision for each 
-    file you wish to restore.</li>
-  <li>After restoring the file if you want to actually restore the file to the 
-    current branch you have to add then commit the file back into the repository. 
-    If the filename does not change, revision history will be maintained for the 
-    restored file.</li> 
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm
deleted file mode 100644
index a476eec..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105b.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Reverting a branch to a previous version</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Reverting a branch to a previous version</H1>
-<p>
-It is often useful to revert the contents of a branch to those of a specific version. For example, if your current branch contains changes that you no longer want to release you can revert all or a portion of a project to the contents of any version.</p>
-
-<ol>
-  <li>Checkout into your workspace the contents from the branch that you want 
-    to revert. </li>
-  <li>Select <strong>Compare With &gt; Another Branch or Version</strong> on the 
-    resource(s) that you want to revert. </li>
-  <li>From the tag selection dialog box select the version to which you want to 
-    revert the branch.</li>
-  <li>When the compare editor opens, review the differences that are shown and 
-    ensure that they are what you expected. </li>
-  <li>Select the root folder in the compare view and from the context menu select 
-    <strong>Override and Update</strong>. After the operation is completed the 
-    folder or project you compared against will have exactly the same contents 
-    as the remote revision. </li>
-  <li>You can verify this by performing another comparison against the version. 
-    (<strong>Note</strong>: That the CVS preference to <strong>Consider file contents 
-    in comparisons</strong> in the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ComparePreferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Team &gt; CVS &gt; Synchronize/Compare</b></a>
-    preference page should be enabled for this to work.) </li>
-  <li>The comparison should report that there are no changes.</li>
-</ol>
-<p CLASS="Head">Once your workspace contains the new contents, run your tests 
-  then commit the changes to the branch.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm
deleted file mode 100644
index 1139295..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-105c.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving version tags</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Moving version tags</H1>
-<p>Warning: Although many people would prefer a CVS version to be frozen in time and not be modifiable, version and branch tags in CVS are mutable. As a result many are convinced that modifying a version is bad practice, but there are a couple of scenarios where it actually comes in handy. With that said, please be cautious when moving tags around.</p>
-<h2>Moving a tag on a single file</h2>
-<p>Let's say that you have just submitted your build by versioning your project 
-  as R1. But you soon after discover that there is a small change to a file that 
-  should be made and included in the build. Instead of having to re-version the 
-  project you can move the R1 version tag for the modified file.</p>
-<ol>
-  <li>Modify the file(s) Select the file that was modified after R1 was created 
-    and from the context menu select <strong>Team &gt; Show in Resource History</strong>.</li>
-  <li>From within the Resource History view select the revision that should be 
-    marked with the R1 version. </li>
-  <li>From the context menu select <strong>Tag with Existing...</strong>.</li>
-  <li>Select the R1 version from the dialog box and press OK. </li>
-  <li>The resource history view will be updated to confirm that the version had 
-    been moved.</li>
-</ol>
-<h2>Moving a tag from within the repositories view</h2>
-<p>Many projects use a well defined version name for their current stable lineup in HEAD. For example, by versioning HEAD with the STABLE tag the build scripts could simply checkout the STABLE version for builds. As the code evolves the STABLE tag is moved regularly to mark the most current stable lineup. The repositories view provides an action for moving an existing tag.
-</p>
-<ol>
-<li>Open the Repositories view and select a resource.</li>
-<li>From the context menu select <b>Tag with Existing</b></li> 
-<li>A tag selection dialog will appear from which you can select the tag to move. If the tag you wish to apply is not show in the list, you can click <b>Refresh from Repository</b>. If this doesn't find the tag, you can click <b>Configure Tags</b> which opens a dialog that allows you to search for tags on specific files in the repository.</li>
-<li>Then press <b>OK</b> and your tag will be moved. The operation will move an existing tag to the selected resources and can be used to move both version and branch tags.</li>
-</ol>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-114.htm">Committing</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm
deleted file mode 100644
index cda4ad5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-107b.htm
+++ /dev/null

@@ -1,121 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Enabling the CVS resource decorations</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Enabling the CVS resource decorations</H1>
-
-<P>When enabled, CVS will decorate resources in Workbench views with icon and 
-label decorations that indicate the CVS state of the resource.
-</P>
-
-<P>To enable the CVS decorations:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Appearance &gt; Label Decorations</b></a>
-  preference page. This page allows the enabling and disabling of all decorations 
-  defined by different plug-ins in the Workbench.</li>
-  <li>Click on the CVS box to enable the CVS decorations.</li>
-  <li> Click <b>OK</b>.</li>
-</ol>
-
-<p><em>Note:</em> In some cases, the decorations may not appear immediately due 
-  to the fact that they are expensive to compute. In those cases, they are calculated 
-  in the background. </p>
-
-<p>To configure the CVS decorations:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSDecoratorPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Team &gt; CVS &gt; Label Decorations</b></a>
-  preference page. This page allows the configuration of how decorations appear on CVS 
-  projects, folders and files.</li>
-  <li>To configure the text label decorations click the <strong>Text</strong> 
-    tab and then: 
-    <ol type="a">
-      <li>Pick the resource type (file, folder, project) for which you want to 
-        change the decoration.</li>
-      <li>Click in the decoration string for that resource type at the location 
-        where the new decoration element should go.</li>
-      <li>Click the <b>Add Variables</b> button for that resource type.</li>
-      <li>Choose the CVS information variable to add. For instance, for files 
-        you could select the <i>added_flag</i> which will be inserted in the decoration 
-        where you placed the cursor. The string <i>{added_flag}</i> will be added 
-        to the decoration string which will decorate newly added resources using 
-        the added resource label (which can be set in the <i>Label Decoration 
-        for Added</i> field).</li>
-    </ol>
-  </li>
-  <li>Repeat the above for any other decorations to be added.</li>
-  <li>Decorations can be removed by deleting the decoration variable name (i.e.<i> 
-    {added_flag}</i>) from the decoration string. In a similar manner, spacing 
-    can be added.</li>
-  <li>To configure icon decorations, click the <strong>Icon</strong> tab simply 
-    enable/disable the icon checkboxes.</li>
-  <li>Click <b>OK</b> or <b>Apply</b> for the new decorations to take effect.</li>
-</ol>
-
-<p><em>Note</em>: Under the <strong>General</strong> tab is an option to disable 
-  the deep dirty decoration of folders. This will make decorator determination 
-  more efficient but will make it harder to find dirty resources in one of the 
-  navigation views. Under the <strong>Synchronize View</strong> tab, the Synchronize 
-  view can be configured to show the synchronization state of a resource as part 
-  of the text label displayed in the Structure Compare pane.</p>
-<p>You can also change the color and font of items based on the item's CVS state. 
-  To set the color and font:</p>
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSDecoratorPreferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Team &gt; CVS &gt; Label Decorations</b></a>
-    preference page.</li>
-  <li>Check the box to <em>Enable font and color decorations</em>.</li>
-  <li>Next, Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>General &gt; Appearance &gt; Colors and Fonts</b></a> preference page.</li>
-  <li>In the <strong>CVS</strong> category are the various CVS states for which 
-    you can set the colors and fonts. Set them as desired.</li>
-  <li>You can return to the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.CVSDecoratorPreferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Team &gt; CVS &gt; Label Decorations</b></a>
-    preference page to preview the changes.</li>
-  <li>Click <b>OK</b> or <b>Apply</b> for the new decorations to take effect.</li>
-</ol>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-  <a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a> 
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-cvs-decorations.htm">CVS Label Decorations</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm
deleted file mode 100644
index ba190ae..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-110.htm
+++ /dev/null

@@ -1,100 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Discovering branch and version tags</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Discovering branch and version tags</H1>
-
-<p><em>Prerequisite:</em>Before you can discover the branch and version tags for 
-  a repository, you must have a valid repository location in the CVS Repositories 
-  view. </p>
-<P>To discover existing branch tags for multiple folders in a single repository 
-  location:</p>
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, select a repository location.</li>
-  <li>From the pop-up menu for the CVS Repositories view, select <b>Refresh Branches</b>. 
-    The Refresh Branches dialog will open (depending on the repository location selected
-    listed remote projects can differ):
-    <p> <img src="../images/cvs_refresh_branches.png" alt="Refresh Branches dialog" border="0"></p>
-  </li>
-  <li>In the folder list, select the folders whose tags you would like to refresh. 
-    Alternatively, at the bottom of the dialog, you can choose a working set and 
-    all remote folders whose names match the name of a project in the working 
-    set will become checked.</li>
-  <li>Click <b>Finish</b> to discovered the tags for the checked projects. These 
-    tags will be added to the repositories view. </li>
-</ol>
-<P><em>Note:</em> This operation may be long running especially if the number 
-  of selected folders is large. </p>
-<P><em>Tip</em>: If the above operation does not result in the discovery of any 
-  tags, it is probable that the folder in the repository does not have a .project 
-  file in it. The .project file is the default file used by the tag discovery 
-  process. The file can be changed for individual projects using <strong>Configure 
-  Branches and Versions</strong> (see below).</p>
-<P>To discover existing branch and version tags for a single project folder: </p>
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand the repository location.</li>
-  <li>Expand <strong>HEAD</strong> and select the root folder whose tags are to 
-    be discovered.</li>
-  <li>From the pop-up menu for the CVS Repositories view, select <b>Configure 
-    Branches and Versions</b>. The Tag Configuration dialog similar to the one below will open.
-    <p> <img src="../images/cvs_configure_branches_and_versions.png" alt="Project Explorer view" border="0"></p>
-  </li>
-  <li>In the top pane on the left (titled <i>Browse files for tags</i>), expand 
-    one or more projects to find a file that is known to have tags that should 
-    be added to the CVS Repositories view.</li>
-  <li>Select a file in the left top pane. If the file selected has tags defined 
-    on it, they will be displayed in the right top pane (titled <i>New tags found 
-    in selected files</i>).</li>
-  <li>Check or uncheck the tags in the right pane as desired.</li>
-  <li>Click <b>Add Checked Tags</b> to add the checked tags to the list of remembered 
-    tags.</li>
-  <li>Click <b>OK</b> to add the remembered tags to the selected repository location 
-    or project.</li>
-</ol>
-<p><em>Note</em>: You can also set the auto-refresh files by selecting a file 
-  in the files pane and clicking<strong> Add Selected Files</strong> in the lower 
-  right hand portion of the dialog. </p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm
deleted file mode 100644
index 136eda7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113.htm
+++ /dev/null

@@ -1,167 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Updating</H1>
-
-<P>While you are working on a project in the Workbench, other members of your 
-  team may be committing changes to the copy of the project in the repository. 
-  To get these changes, you may &quot;update&quot; your Workbench to match the 
-  state of the branch. The changes you will see will be specific to the branch 
-  that your Workbench project is configured to share. You control when you choose 
-  to update.
-</P>
-
-<p>The update command can be issued from two places: the <b>Team &gt; Update</b> 
-  menu, or the <b>Synchronize</b> view. In order to understand the difference 
-  between these two commands, it is important to know about the three different 
-  kinds of incoming changes.
-</p>
-
-<ul>
-  <li>A <i>non-conflicting</i> change occurs when a file has been changed remotely 
-    but has not been modified locally.</li>
-  <li>An <i>auto-mergeable conflicting</i> change occurs when an ASCII file has 
-    been changed both remotely and locally (i.e. has non-committed local changes) 
-    but the changes are on different lines.</li>
-  <li>A <i>non-auto-mergeable conflicting</i> change occurs when one or more of 
-    the same lines of an ASCII file or when a binary file has been changed both 
-    remotely and locally (binary files are never auto-mergeable).</li>
-</ul>
-
-<p>When you select <b>Team &gt; Update</b>, the contents of the local resources 
-  will be updated with incoming changes of all of the above three types. You can specify what
-  the update behaviour should be in the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.UpdateMergePreferences)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Team &gt; CVS &gt; Update/Merge</b></a>
-  preference page. The choices are:</p>
-  <ul>
-  <li><b>Preview all incoming changes before Updating</b>: All changes will be displayed in either the Sync View or 
-  a dialog (depending on your settings). You can then merge each change in line by line, or update all non-conflicting
-  changes at once and then deal with the remaining conflicts.</li>
-  
-  <li><b>Update all non-conflicting changes and then preview the remaining changes</b>: All
-  non-conflicting incoming changes will be merged in automatically and any remaining conflicts will be
-  displayed either in the Sync View (<em>default</em>) or in a dialog. You can specify where to display conflicts
-  from the Update/Merge preference page. </li>
-   
-  <li><b>Never preview and use CVS text markup to indicate conflicts (<em>default</em>)</b>: This option will automatically
-  merge all changes in without any user interaction. Conflicting changes will be merged in using the CVS text markup:<br>
-  	<br>&lt;&lt;&lt;&lt;&lt;&lt;&lt; original file revision
-  	<br>[original code]
-  	<br>= = = = = = =
-  	<br>[incoming code]
-  	<br>&gt;&gt;&gt;&gt;&gt;&gt;&gt; incoming file revision<br>
-  
-   <br>You will then have to go in to each file that contains a merge conflict and edit the file to the desired final state.
-  </li>
-  </ul>
- <p>
-  It is often desirable to know what incoming changes there are before updating any local resources. These issues are addressed by 
-  the Synchronize view.
-</p>
-
-<p>To open the Synchronize view in incoming mode:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources which you want to update.</li>
-  <li>From the pop-up menu for the selected resources, select <b>Team &gt; Synchronize 
-    with Repository</b>. The Synchronize view will open.</li>
-  <li>On the toolbar of the Synchronize View, click the <b> Incoming mode</b> 
-    button to filter out any modified Workbench resources (outgoing changes) that 
-    you may have.</li>
-</ol>
-
-<p>In incoming mode, you will see changes that have been committed to the branch 
-  since you last updated. The view will indicate the type of each incoming change. 
-  There are two update commands (available from the context menu of any resource 
-  in the view) to deal with the different types of conflicts: <b>Update</b> and 
-  <b>Override and Update</b>. When you select the <b>Update</b> command in the 
-  Synchronize view, all selected incoming and auto-mergeable conflicting changes 
-  are processed while conflicts that are not auto-mergeable will not be updated 
-  (any files that have been successfully processed are removed from the view). 
-  The <b>Override and Update</b> command operates on conflicts and will replace 
-  the local resources with the remote contents. This &quot;replace&quot; behavior 
-  is rarely what is desired. An alternative is described later. </p>
-
-<p>To update non-conflicting and auto-mergeable files:</p>
-<ol>
-  <li>The Structure Compare pane at the top of the Synchronize view contains the 
-    hierarchy of resources with incoming changes.</li>
-  <li>Select all conflicting files and choose <b>Update </b> from the pop-up menu. 
-    This will update the selected resources that are either incoming changes or 
-    auto-mergeable conflicts and remove them from the view. Conflicts whose contents 
-    are not auto-mergeable will be left in the view.</li>
-</ol>
-
-<p>If your local Workbench contains any outgoing changes that are not auto-mergeable 
-  with incoming changes from the branch, then, instead of performing an <b>Override 
-  and Update</b>, you can merge the differences into your Workbench manually, 
-  as follows:
-</p>
-
-<ol>
-  <li>In the Structure Compare pane, if there is a conflict in the resource list 
-    (represented by red arrows), open it (either by double-clicking or selecting 
-    <strong>Open in Compare Editor</strong> from the context menu).</li>
-  <li>In the Text Compare area of the compare editor, local Workbench data is 
-    represented on the left, and repository branch data is represented on the 
-    right. Examine the differences between the two.</li>
-  <li>Use the text compare area to merge any changes. You can copy changes from 
-    the repository revision of the file to the Workbench copy of the file and 
-    save the merged Workbench file (using the pop-up menu in the left pane).</li>
-  <li>Once you are completed merging the remote changes into a local file, choose 
-    <b>Mark as Merged</b> from the pop-up menu in the Synchronize view. This will 
-    mark the local file as having been updated and allow your changes to be committed.</li>
-</ol>
-
-<p><em>Note:</em> The repository contents are not changed when you update. When 
-  you accept incoming changes, these changes are applied to your Workbench. The 
-  repository is only changed when you commit your outgoing changes.
-</p>
-
-<p><em>Tip:</em> In the Synchronize view, selecting an ancestor of a set of incoming 
-  changes will perform the operation on all the appropriate children. For instance, 
-  selecting the top-most folder and choosing <b>Update </b> will process all incoming 
-  and auto-mergeable conflicting changes and leave all other incoming changes unprocessed. 
-</p>
-
-<p><em>Warning:</em> The behavior of the <b>Override and Update</b> command described 
-  above only applies to the incoming mode of the Synchronize view. In the <b>Incoming/Outgoing 
-  mode</b> of the view, the behavior for incoming changes and conflicts is the 
-  same but the command will revert outgoing changes to whatever the repository 
-  contents are. Exercise great caution if using this command in Incoming/Outgoing 
-  mode. </p>
-
-<p CLASS="Intro"><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm
deleted file mode 100644
index 635d499..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-113b.htm
+++ /dev/null

@@ -1,117 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resolving conflicts</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Resolving conflicts</H1>
-
-<P>When updating or committing you may encounter conflicts. A conflict occurs 
-  when you have locally modified a resource for which a more recent revision is 
-  available in the branch in the repository. Specifically, the branch will contain 
-  a revision newer than the base revision of your resource. In this situation 
-  you can choose to do one of the following:
-</P>
-
-<ul>
-  <li>You can take the change from the branch, discarding your local work. This 
-    could occur if you have made unintended changes locally, or if you realize 
-    that the revision in the repository is better than yours. Overwriting your 
-    local changes should be done with caution since you are in essence throwing 
-    work out.</li>
-  <li>You can commit your change, subsuming the revision in the repository. This 
-    should be done with great caution since you are in essence throwing away someone 
-    else's work. In particular, the change you are overwriting may have other 
-    dependencies in the branch (for example there may be other incoming changes 
-    which depend on the conflict).</li>
-  <li>You can merge your work and the repository resource, saving locally the 
-    merged resource. You may then later choose to commit this merged result.</li>
-</ul>
-
-<P>Typically, you will want to take the third option, that is to merge, because 
-  of the loss of work issues with the other two choices.
-</P>
-
-<h2><a name="MergingChanges">Manually merging changes</a></h2>
-
-<P>The Synchronize View indicates those resources which are in conflict with the 
-  branch. For a given resource in conflict, typically you will want to merge your 
-  changes with changes in the branch's resource.
-</P>
-
-<P CLASS="Para">For example, let us assume that both you and another team member 
-  have modified the same html page. Opening that resource from the Synchronize 
-  view will display a comparison of the local resource and the branch revision. 
-  By cycling through and merging the individual changes, you can decide for each 
-  change whether to accept the incoming change, reject it, or merge it with your 
-  local changes. When you are finished merging, you save your changes. This overwrites 
-  your local resource with the result of the merge. You can subsequently commit 
-  this merged resource. </P>
-
-<P><em>Tip:</em> When merging changes, it is often convenient to be able to distinguish 
-  which files you have completed merging. When you're done merging a file, you 
-  can pick <b>Mark as Merged</b> from the context menu. This will change the status 
-  of the file from being a conflict to being an outgoing change.
-</P>
-
-<P>You can merge differences in the Synchronization view on two levels:
-</P>
-
-<ul>
-  <li><b>Whole Document</b> - In the Synchronize view, open the resource that 
-    you want to merge in a Compare editor. In the Compare editor, click the Copy 
-    all non-conflicting Changes from Right to Left button to copy all non-conflicting 
-    changes. Conflicting changes will have to copied individually.</li>
-  <li><b>Current Change</b> - In the Text Compare editor, either use the Go to 
-    Next Difference and Go to Previous Difference buttons to navigate to the change 
-    that you want to merge, or simply click in either source pane somewhere in 
-    the desired change difference fragment. Click the Copy current change from 
-    right to left button as needed to overwrite the highlighted fragment either 
-    with the corresponding modification in the branch.</li>
-</ul>
-
-<h2><a name="AutoMergingChanges">Auto merging changes</a></h2>
-
-<p>It is also possible to have your changes automatically merged for you. For 
-  any resource marked as ASCII, performing a <b>Team &gt; Update</b> will automatically 
-  merge into your local resource differences with the branch resource. This works 
-  fine provided there are no lines with conflicting changes. If there are, CVS 
-  inserts special markup in the file to indicate those lines which could not be 
-  merged.
-</p>
-
-<p>Updating from within the Synchronization view works a bit differently. In the 
-  case of a conflict, <strong>Update</strong> will only process files whose contents 
-  contain no conflicts. Files that have content conflicts will be skipped and 
-  left in the Synchronize view as conflicts.</p>
-
-<P>&nbsp;<img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm
deleted file mode 100644
index 7907d66..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-114.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Committing</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Committing</H1>
-
-<P>You can commit Workbench resources that you have modified to the repository 
-  so that other team members can see your work. Only those changes committed on 
-  that branch will be visible to others working on that branch. The commit command 
-  can be issued from two places: the <b>Team &gt; Commit</b> menu, or the <b>Synchronize</b>
-  view.
-</p>
-
-<h2>Committing changes using <b>Team &gt; Commit</b></h2>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to commit.</li>
-  <li>Right-click on the resources and select <b>Team &gt; Commit</b> from the 
-    pop-up menu.</li>
-  <li>If there are new files whose file types cannot be determined automatically, 
-    the first page of the Commit dialog will present the unknown types and allow 
-    you to set them appropriately to either ASCII or binary. Click <strong>Next</strong> 
-    to continue.</li>
-  <li>On the Comment page, provide a comment for your changes (for example, <samp>Fixed 
-    the spelling mistakes</samp>).</li>
-</ol>
-
-<P>You can preview files that are about to be committed from the Comment page.
-  If any of the files are known to be conflicting changes, the commit 
-  will not be allowed. If there are no known conflicting changes the commit will 
-  be allowed but there could still be conflicting changes on the server (i.e. 
-  conflicting changes on the server become known to the client during a synchronize 
-  operation). If there are conflicting changes on any files that are committed, 
-  the operation will fail. If this occurs, you must either perform an update or 
-  use the Synchronize view to resolve the conflicts. It is considered a more ideal 
-  workflow to always update before committing in order to ensure that you have 
-  the latest state of the repository before committing more changes. </p>
-<P>If one or more of the resources being committed are new and not yet added to 
-  CVS control, they will be added automatically unless they are explicitly removed 
-  by choosing <strong>Remove from View</strong> from the context menu.</p>
-
-<h2>Committing changes in the Synchronize view</h2>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to commit.</li>
-  <li>Right-click to open the pop-up menu and select <b> Team &gt; Synchronize 
-    with Repository</b>. The Synchronize view will open.</li>
-  <li>On the toolbar of the Synchronize view, select the <b>Outgoing mode</b> 
-    button to show any modified Workbench resources (outgoing changes) that you 
-    may have.</li>
-  <li>If there are conflicts (red arrows), resolve them. To do so open them in 
-    a Compare editor and use the text compare area to merge resources with conflicts. 
-    You can copy changes from the repository revision of the file to the Workbench 
-    revision of the file and save the merged Workbench resource. Once all the 
-    conflicts in the Structure Compare area have been resolved, perform a <strong>Mark 
-    as Merged</strong> on the resource in the Synchronize view to make the change 
-    an outgoing change and you are ready to commit.</li>
-  <li>In the Structure Compare pane, right-click the top of the hierarchy that 
-    you want to commit, and select <b>Commit</b> from the pop-up menu.</li>
-  <li>In the Commit Comment dialog box, provide a comment for your changes (for 
-    example, <samp>Fixed the spelling mistakes</samp>). Again, if there are new 
-    files of an unknown type, you will be asked to specify what type they should 
-    be. </li>
-</ol>
-
-<P><em>Tip:</em> You can commit files that are in conflict by performing an <b>Override 
-  and Commit</b>. This will commit the Workbench copy of the resource into the 
-  repository and thus remove any of the incoming changes.
-</p>
-
-<P><em>Warning:</em> The behavior of the <b>Override and Commit</b> command described 
-  above only applies to the outgoing mode of the Synchronize view. In the <b>Incoming/Outgoing 
-  mode</b> of the view, the behavior for outgoing changes and conflicts is the 
-  same but the command will revert incoming changes to whatever the local Workbench 
-  contents are. Exercise great caution if using this command in incoming/outgoing 
-  mode. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm
deleted file mode 100644
index c12ca9f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-115.htm
+++ /dev/null

@@ -1,122 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Synchronizing with the repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Synchronizing with the repository</H1>
-Working with shared resources requires tracking their state in context of the repository
-content. This could be done by creating a synchronization that populates the Synchronize
-view and benefiting following advantages:
-<ul>
-  <li>The local modification state of the resources being synchronized is kept 
-    up-to-date. This means that, if you modify a file locally that is within the 
-    scope of a synchronization that appears in the Synchronize view, the resource 
-    will appear automatically in the view, if it is not already there.</li>
-  <li>The remote state of all of the resources being synchronized can be refreshed 
-    using the Synchronize <img src="../images/synch_participants.png" alt="" border="0" > 
-    button in the toolbar of the Synchronize view.</li>
-  <li>The remote state of a selection of resources can be refreshed using the 
-    Synchronize command from the context menu in the Synchronize view.</li>
-</ul>
-<p>Following methods can be used to create a synchronization.</p> 
-<h2>Method 1: Using the context menu</h2>
-<p>To synchronize resources in the Workbench with those in the repository: </p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to synchronize.</li>
-  <li>Right click and select <b>Team &gt; Synchronize with Repository</b>. The 
-    Synchronize view opens.</li>
-</ol>
-<h2>Method 2: Using the synchronize action</h2>
-<ol>
-  <li>From the Team Synchronizing perspective select the <strong>Synchronize...</strong> 
-    action from the Synchronize <img src="../images/synch_participants.png" alt="" border="0" > 
-    button drop down.</li>
-  <li>Select <strong>CVS</strong> from the list of possible synchronization types 
-    and click <strong>Next</strong>.<br><em>Note:</em> If there are no other repository providers registered with the
-    Workbench, then you will bypass this screen altogether.</li>
-  <li>Select the resource scope for the synchronize by either selecting Workspace, 
-    Selected Resources or Working Set. Then select <strong>Finish.</strong></li>
-  <li>The Synchronize view will open.</li>
-</ol>
-<p> <em>Note</em>: The synchronize action is not enabled by default in 
-  other perspectives. You can enable the action to appear in your current perspective 
-  by selecting
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Window &gt; Customize Perspective</strong></a>. Then click 
-  on the <strong>Commands</strong> tab and check off <strong>Team</strong>.</p>
-<p><em>Tip</em>: You can use method 3 below to avoid loosing the created synchronization.</p>
-<h2>Method 3: Using a pinned CVS Workspace Synchronization in the Synchronize 
-  view</h2>
-<p>Once you have a CVS workspace synchronization in the Synchronize view, you 
-  can pin it. This will prevent it from being replaced by the next CVS workspace 
-  synchronization that is launched using one of the previous 2 methods. Here are 
-  some of the advantages of using a pinned synchronization.</p>
-<ul>
-  <li>You can remove any not pinned synchronization to make the pinned one visible.
-    To do it select <strong>Remove Current Synchronization</strong> from the Synchronize
-    view toolbar's menu.</li>
-  <li>You can schedule the refreshing of the remote state to happen at particular 
-    intervals (each hour, for example)</li>
-</ul>
-<p>The implications of this is that you can see you outgoing resources without 
-  re-fetching the remote state from the server (a potentially long running operation). 
-  Also, the fetching of the remote state is run in the background so you can do 
-  other things (e.g. inspect changes) while the remote state is fetched.</p>
-<h3>From within the synchronize view</h3>
-<p>Use the toolbar buttons to switch modes for this view. There are four modes:</p> 
-<ul>
-  <li>Incoming mode - shows incoming changes only (resources in the repository 
-    that differ from what is in the Workbench).</li>
-  <li>Outgoing mode - shows outgoing changes only (resources modified in the 
-    Workbench).</li>
-  <li>Incoming/Outgoing mode - shows both incoming and outgoing changes.</li>
-  <li>Conflicts mode - shows only conflicting resources.</li>
-</ul>
-<p><em>Note:</em> It is possible that someone has committed a new revision of your
-  file since you started working on it. This will result in a <em>conflict</em>, and care 
-  must be taken to resolve this. For this reason, conflicts are shown in all modes of the
-  Synchronize view.
-</p>
-<p><em>Important:</em> It is preferable to update resources in the Workbench 
-  first, resolve any conflicts that exist by merging, then commit Workbench 
-  resources to the repository.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-114.htm">Committing</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a><br>
-<a href="tasks-100d.htm">Version control life cycle: adding and ignoring resources</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-33.htm">Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm
deleted file mode 100644
index aea51d8..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117.htm
+++ /dev/null

@@ -1,79 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Sharing a new project using CVS</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Sharing a new project using CVS</H1>
-
-<P>There are several scenarios that can occur when sharing a project using CVS. 
-The most common scenario is sharing a new project using CVS when the project 
-does not already exist remotely.
-</P>
-  
-<P>To share a new project using CVS:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the project to be shared.</li>
-  <li>Select <b>Team &gt;</b> <b>Share Project...</b> from the project's pop-up 
-    menu. The Share Project wizard opens.</li>
-  <li>From the list of available repository providers, choose <b>CVS</b> and click 
-    <b>Next </b>to go to the next page. (<b>Note</b>: If CVS is not present in 
-    the list, it may be disabled. Clicking on the <strong>Show All Wizards</strong> 
-    button should make it visible. Also note that if there is only repository provider registered
-    for your workspace, you will automatically bypass this step entirely.)</li>
-  <li>Select the target repository from the list of known repositories or, if 
-    the target repository is not in this list, choose to create a new repository 
-    location and click <b>Next</b>.</li>
-  <li>If entering a new repository location, enter the repository information 
-    and click <b>Next</b> when completed. (<b>Note</b>: this page is the same 
-    format as the <a href="tasks-92.htm">Creating a CVS repository location</a> 
-    wizard.)</li>
-  <li>Either choose to use the name of the local project as the remote project 
-    name or enter another name and click <strong>Next</strong>.</li>
-  <li>The final page shows you the resources of the new project as outgoing additions. 
-    You can choose to commit or ignore resources from this page. (<b>Note</b>: 
-    If the project already exists remotely, the page will show conflicts on any 
-    files that exist both locally and remotely. Only those files whose contents 
-    do not match are shown.)</li>
-  <li>Click <b>Finish</b> to share the project with the repository. You will be 
-    prompted to commit any resources in the new project that have not yet been 
-    committed or ignored. Choosing to do so will run the commit operation in the 
-    background. </li>
-</ol>
-
-<h4>Consequences for Linked Resources</h4>
-<p>As mentioned in <a href="../concepts/concepts-13.htm">Linked resources</a>, different
-providers may handle linked resources differently.  For Team CVS, linked resources
-are allowed but ignored.  Specifically, projects which contain linked resources can be shared with CVS,
-but the linked resources themselves cannot be version controlled.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-117a.htm">Project checked out with another CVS tool</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm
deleted file mode 100644
index cfc84c9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117a.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Project checked out with another CVS tool</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Project checked out with another CVS tool</H1>
-
-<P CLASS="Para">It is possible to use a CVS project checked out using another 
-  CVS tool into Eclipse. A common concern for those migrating to Eclipse is that 
-  they already have their CVS project checked out on their local machine. You 
-  <em>don't</em> have to check out the contents again to create a project in Eclipse. 
-  When such a project is imported into Eclipse, the CVS plug-in may detect that 
-  CVS folders exist and auto-share the project. However, there are some instance 
-  were this does not occur and the project will need to be shared manually within 
-  Eclipse in order to enable the CVS Team menu operations.</P>
-<P>To share an CVS project that was already checked out:</P>
-
-<ol>
-  <li>In one of the navigation views, select the project to be shared.</li>
-  <li>Select <b>Team &gt;</b> <b>Share Project...</b> from the project's pop-up 
-    menu. The Share Project wizard opens.</li>
-  <li>From the list of available repository providers, choose <b>CVS</b> and click 
-    <b>Next </b>to go to the next page. (<b>Note</b>: If CVS is not present in 
-    the list, it may be disabled. Clicking on the <strong>Show All Wizards</strong> 
-    button should make it visible.)</li>
-  <li>The next page displays the sharing information stored in the CVS folder 
-    of the project. Click <strong>Finish</strong> to share the project and enable 
-    the CVS Team menu operations.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm
deleted file mode 100644
index 58bb033..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-117b.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the sharing of a project</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the sharing of a project</H1>
-
-<P>If a project is shared with a CVS repository location, you can change the 
-sharing information so it is shared with a different repository location. The
-new location must map to the same repository but can have a different 
-connection method and/or user name.
-</p>
-
-<P>To change the sharing of a project:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the project whose sharing information is to be changed.</li>
-  <li>Select <b>Properties</b> from the pop-up menu. The properties dialog will open.</li>
-  <li>Select <b>CVS</b> to see the CVS properties page for the project.</li>
-  <li>Click <b>Change Sharing...</b>. A repository selection dialog opens containing 
-    the compatible repository locations. (<strong>Note</strong>: You can change 
-    the sharing to a non-compatible repository location by unchecking the<strong> 
-    Show only compatible repository locations</strong> button.)</li>
-  <li>Select the desired location and click <b>OK</b> to change the sharing for the project.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-95.htm">Changing the properties of a CVS Repository Location</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm
deleted file mode 100644
index 655342b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-118.htm
+++ /dev/null

@@ -1,70 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Versioning projects in the repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Versioning projects in the repository</H1>
-
-<P> You can version a project in the repository without adding the project to 
-  the Workbench.
-</P>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand a repository location and find the 
-    project you wish to version.</li>
-  <li>Right-click on the project and select <b>Tag as Version</b>.</li>
-  <li>Enter the name of the version you wish to create.</li>
-  <li>Click <b>OK</b> to close the dialog and create the version.</li>
-</ol>
-
-<p><em>Tip:</em> You can browse existing versions of your project by clicking 
-  on the <b>Details</b> button in the Tag Resources dialog. Clicking <b>Refresh 
-  from Repository</b> should populate the Existing Versions list. It is sometimes 
-  helpful to see existing versions before naming your new version.
-</p>
-
-<p><em>Tip:</em> If the version tag you wish to apply already exists on some of 
-  the resources to be versioned, you can perform a <b>Tag with Existing</b> instead. 
-  This operation will move an existing tag to the selected resources and can be 
-  used to move both version and branch tags. If the tag you wish to apply is not 
-  show in the list, you can click <b>Refresh from Repository</b>. If this doesn't 
-  find the tag, you can click <b>Configure Tags</b> which opens a dialog that 
-  allows you to search for tags on specific files in the repository.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-27b.htm">Branches</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100.htm">Creating a version of a project</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-119.htm">Viewing a file's revision history</a><br>
-<a href="tasks-100a.htm">Branching</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm
deleted file mode 100644
index 99d0d30..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-119.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Viewing a file's revision history</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Viewing a file's revision history</H1>
-
-<P>Every time you commit a file to the CVS repository, a new revision is created. 
-  Each revision is identified by a number (for example, 1.1 or 1.11.3.5). Along 
-  with each revision is stored the author, the date, and a commit comment.
-</P>
-
-<P>To view the resource history for a file:
-</P>
-
-<ol>
-  <li>Select the file in one of the navigation views. From the context menu, choose <b>Team 
-    &gt; Show in History</b>.</li>
-  <li>The History view will open and show a history for the selected CVS
-    file.</li>
-</ol>
-
-<p><em>Note:</em> The History view also shows you all version and branch 
-  tags that are associated with the file.
-</p>
-
-<p><em>Tip:</em> You can show different types of revisions (your options are: Local and Remote
-revisions, only Remote revisions or only Local revisions) by using the History 
-view's mode toggle buttons. These toggle buttons are located on the History view toolbar. 
-</p>
-
-<p><em>Tip:</em> You can drag and drop a file from one of the navigation views into the History 
-view instead of choosing the menu item.
-</p>
-
-<p><em>Tip</em>: You can have the History view update automatically 
-  to the history of the file in the active editor by enabling the <strong>Link 
-  with Editor</strong> item in the view's toolbar.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-32a.htm">CVS Resource History view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-120.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-120.htm
deleted file mode 100644
index 4c20585..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-120.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating the installation</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Updating the installation</H1>
-<p>To check to see whether there are updates for the items installed in your
-   system (requires Internet access):
-</p>
-
-<ol>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.equinox.p2.ui.sdk.update")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Check for Updates</b></a>. 
-  </li>
-  <li>This will contact 
-    the Web sites defined in your Available Software Sites preferences to look for upgrades.
-    If upgrades are available, they will be presented in the 
-    <a href="tasks-125.htm">Available Updates wizard</a>.
-  </li>
-</ol>
-<p>
-To check for updates for only certain items in your installation, 
-use the Installed Software page to select the items you are interested in and check for
-updates.
-</p>
-<ol>
-<li>Click <b>Help &gt; About</b> and then click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> to open a dialog showing pages that provide more detail about your installation. </li>
-<li> Click the <b>Installed Software</b> tab to see a list of the software items that you have installed into your system.</li>
-<li>Select the items that you wish to update. </li>
-<li>Click <b>Update...</b>.  This will contact 
-    the Web sites defined in your Available Software Sites preferences to look for upgrades.
-    If upgrades are available, they will be presented in the 
-    <a href="tasks-125.htm">Available Updates wizard</a>.
-  </li>
-  </ol>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-<a href="tasks-125.htm">Updating software using the Available Updates wizard</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-123.htm">Reverting to a saved configuration</a><br>
-<a href="tasks-122.htm">Scheduling automatic updates</a><br>
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-122.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-122.htm
deleted file mode 100644
index 1878b9f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-122.htm
+++ /dev/null

@@ -1,102 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Scheduling automatic updates</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Scheduling automatic updates</h1>
-<p>You can configure Eclipse update to automatically search for updates to the installed software 
-on a periodic basis. You can configure how these updates
-are scheduled and performed from the <b>Install/Update &gt; Automatic Updates</b> preference page.
-</p>
-<h3>Scheduling options</h3>
-<p>Each time an Eclipse-based product starts, the update scheduler will
-activate based on the chosen scheduling. You can choose between the following
-update policies:</p>
-<ul>
-  <li>No automatic search</li>
-  <li>On each startup (default)</li>
-  <li>Every day at a specific time (i.e. 3:00PM) *</li>
-  <li>On a scheduled day of the week at a specific time (i.e. Monday 8:00AM) *</li>
-</ul>
-<p>* assuming the application is active. If the application is not active at a 
-scheduled time and the search is past due, it will immediately start on the next 
-startup</p>
-<h3>Download options</h3>
-<p>Scheduling options define when searches are performed but do not 
-define what actually happens when updates are found. Download options 
-control this behavior (this set of options is disabled if automatic search is 
-turned off). You can choose between:</p>
-<ul>
-  <li>Search for updates and notify me when they are available (default)</li>
-  <li>Download new updates automatically and notify me when ready to install them</li>
-</ul>
-<p>In both cases, the update scheduler will execute in the background 
-when necessary based on the scheduling options. There will be no messages if no 
-updates are found. If there are updates, the behavior will depend on the 
-chosen download option.</p>
-<h4>Search and notify</h4>
-<p>If search only is selected, a popup will appear notifying you that updates
-have been found, and an updates icon will appear in the status bar.  
-You may click on the popup to review the list of updates. The 
-same <a href="tasks-125.htm">Available Updates wizard</a>
- is used when you search for updates manually using
-<a class="command-link" href='javascript:executeCommand("org.eclipse.equinox.p2.ui.sdk.update")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Check for Updates</b></a>.</p>
-  <p>If you do not wish to update your system right away, you may dismiss the notification
-  popup by clicking on the <font color="#0000FF">[X]</font> in the corner of the popup.  When you are ready to review
-  the updates, you may then click on the update icon in the status bar.
-  </p>
-<h4>Download new updates</h4>
-<p>If the second option has been selected (download updates automatically), the 
-search will be scheduled as before, but when new updates are found, the 
-download will commence immediately. When all the features have been successfully 
-downloaded, a popup will appear notifying you that updates have been found
-and downloaded, and an updates icon will appear in the status bar.
-You may click on the popup to review the list of updates. The 
-same <a href="tasks-125.htm">Available Updates wizard</a>
- is used when you search for updates manually using
-<a class="command-link" href='javascript:executeCommand("org.eclipse.equinox.p2.ui.sdk.update")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Check for Updates</b></a>.</p>
-  <p>If you do not wish to update your system right away, you may dismiss the notification
-  popup by clicking on the <font color="#0000FF">[X]</font> in the corner of the popup.  When you are ready to review
-  the updates, you may then click on the update icon in the status bar.  The software that was downloaded
-  will be used the next time you update the system.
-  </p>
-  <h3>Reminder options</h3>
-<p>Reminder options define what happens when updates are found.
-You can choose between:</p>
-<ul>
-  <li>Notify me once about updates (default)</li>
-  <li>Remind me about updates.  This option lets you choose the time
-  interval for being reminded about updates.</li>
-</ul>
-<p>In either case, a popup will appear when updates are available.  Clicking
-the popup will open the <a href="tasks-125.htm">Available Updates wizard</a>
-so that you can review the updates.  If you do not wish to update your system right away, 
-you may dismiss the notification popup by clicking on the <font color="#0000FF">[X]</font> in the corner of the popup.  
-If you have selected a time interval for reminders, the popup will appear when the
-specified interval has passed.
-</p>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-125.htm">Updating software using the Available Updates wizard</a><br>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-123.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-123.htm
deleted file mode 100644
index 78e938c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-123.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Reverting to a previous install configuration</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Reverting to a previous install configuration</h1>
-<p>As you install, upgrade, and uninstall software into your system, configuration
-  snapshots are kept in a history.  Reverting to a previous configuration allows you
-  to back out of the results of an unsuccessful install, upgrade, or uninstall. 
-  To revert to a saved configuration:
-</p>
-
-<ol>
-<li>Click <b>Help &gt; About</b> and then click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> to open a dialog showing pages that provide more detail about your installation. </li>
-  <li> Click the <b>Installation History</b> tab to see a list of previously saved configurations.  Selecting each configuration
-  will show you what was installed in that configuration.  When you have found the configuration
-  to which you want to revert, click <b>Revert</b>.</li>
-  <li>Click <b>Yes</b> when asked to exit and restart the Workbench for the changes 
-    to take effect.</li>
-  <li>When you restart, you should see that the <b>Installed Software</b> page list matches
-  the configuration that you chose.</li>
-</ol>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-125.htm">Updating software using the Available Updates wizard</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-124.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-124.htm
deleted file mode 100644
index 4972b53..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-124.htm
+++ /dev/null

@@ -1,103 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Installing software using the Install wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Installing new software</H1>
-<p>The <b>Install New Software</b> wizard allows you to add new software to your
-installation.  To install new software:
-</p>
-<ol>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.equinox.p2.ui.sdk.install")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Install New Software...</b></a>.  This wizard shows you the items that are
-    available for installation.</li>
-  <li>You may type the location of a software site or select an existing software site
-    using the <b>Work With</b> combo at the top of the page.  By default, the items in
-    a site are grouped by category, with only the latest version of each item shown.
-    You can change the way
-    that you browse available software using the following mechanisms:
-    <ul>
-    <li>Using the <b>Work With</b> combo box, you can select a site to browse its
-    contents, or you can choose to browse software from all sites.  Browsing all 
-    sites is useful when you know the name of something but do not know where it
-    is located.</li>
-    <li>The filter box can be used to type part of the name of something that you are
-    looking for.  The list of items will be filtered to only those matching the
-    text that you type.</li>
-    <li>A checkbox at the bottom of the page can be used to control whether the items
-    should be grouped in categories, or listed by name. </li>
-    <li>A checkbox at the bottom of the page can be used to control whether
-    all versions, or only the latest versions, of software are shown in the list. </li>
-    <li>A checkbox at the bottom of the page can be used to control whether
-    items that are already installed should be shown in the list.</li> 
-    </ul>
-    </li>
-    <li>As you browse the available software, you can check the items that you wish to install.
-  </li>
-  <li>
-    When you have finished making your selections, click <b>Next</b> to install the checked items.  
-    If the items you are installing require other software items in order to operate, those
-    requirements will be included in your request.  A checkbox at the bottom of this page controls 
-    whether all software sites will contacted when looking for requirements, or only the site
-    shown in the <b>Work With</b> combo box.
-  </li>
-  <li>Once you click <b>Next</b>, the wizard will validate your selections against your installed software, and report any configuration
-    problems that might prevent you from installing a particular software item.
-   <ul>
-    <li>If there are conflicts that prevent you from installing one or more of your selections, the problems
-    will be reported in the details area at the bottom of the wizard.  You may uncheck one or more
-    of the selected items and validate the install by clicking <b>Next</b> again.  Or, you
-    may click <b>Back</b> to return to the first page and change your selections.
-    </li>
-   <li>If all of the requirements are available and there are no other installation
-   conflicts, clicking <b>Next</b> will show the <b>Install Details</b> page.
-   The items to be installed will be listed.  Expanding each item will show what additional items will be required
-   to complete the install.  You will see an estimated size of the installation at the bottom
-   of the page.</li>
-   </ul>
-  </li>
-  <li>If the selected items have license agreements to be reviewed, you must click <b>Next</b>.  
-    Carefully review the license agreements for the items you wish to install.  You may also 
-    notice items in the license list that you did not choose for install, but that are required
-    by the the items that you are installing. If the 
-    terms of all these licenses are acceptable, check &quot;I accept the terms 
-    in the license agreements.&quot; Do not proceed to download the features if 
-    the license terms are not acceptable.</li>
-  <li>If the license agreements are acceptable, or if the selected items did not have 
-  license agreements to review, click <b>Finish</b>.  This will begin the download and
-  installation of the new software.</li>  
-  <li><p>Some of the items may be digitally signed by the company that provides them. 
-    This allows you to verify more easily that the features and plug-ins 
-    that are about to be downloaded and installed are coming from a trusted supplier. You
-    may be prompted to verify digitally signed content once the signature is
-    detected.</p><br>
-    <p><b>Warning:</b> Because of the possibility of harmful or even malicious software, 
-    you should only download software from parties that you trust.</p></li>
-  <li>Once all of the software is downloaded successfully and the necessary
-    files installed into the product on the local computer, you will be prompted
-    to restart for the Workbench.  Click <b>Yes</b> 
-    when asked to exit and restart the Workbench for the changes to take effect.</li>
-</ol><P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-<a href="tasks-123.htm">Reverting to a saved configuration</a>
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-125.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-125.htm
deleted file mode 100644
index 779edb5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-125.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating software using the Available Updates wizard</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Updating software using the Available Updates wizard</H1>
-<p>The <b>Available Updates</b> wizard shows you what updates are available for your software.
-This wizard is shown if you click the automatic updates notification popup, or if you
-check for updates using the <a class="command-link" href='javascript:executeCommand("org.eclipse.equinox.p2.ui.sdk.update")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Check for Updates</b></a> command.  To update your system:
-</p>
-<ol>
-  <li>Review the list of upgrades shown in the wizard.  If you do not wish to accept all
-  of the proposed updates, you may check and uncheck different items in the list.</li>
-  <li>Click <b>Next</b> to see the detailed list of items that will be upgraded.  Expanding 
-  each item will show what additional items (if any) will be upgraded as part of the update.</li>
-  <li>If the selected items have license agreements to be reviewed, you must click <b>Next</b>.  
-    Carefully review the license agreements for the upgraded items. If the 
-    terms of all these licenses are acceptable, check &quot;I accept the terms 
-    in the license agreements.&quot; Do not proceed to download the software if 
-    the license terms are not acceptable.</li>
-  <li>If the license agreements are acceptable, or if the selected items did not have 
-  license agreements to review, click <b>Finish</b>.  This will begin the download and
-  installation of the updated software.</li>  
-  <li><p>Some of the items may be digitally signed by the company that provides them. 
-    This allows you to verify more easily that the features and plug-ins 
-    that are about to be downloaded and installed are coming from a trusted supplier. You
-    may be prompted to verify digitally signed content once the signature is
-    detected.</p><br>
-    <p><b>Warning:</b> Because of the possibility of harmful or even malicious software, 
-    you should only download software from parties that you trust.</p></li>
-  <li>Once all of the software is downloaded successfully and the necessary
-    files installed into the product on the local computer, you will be prompted
-    to restart for the Workbench.  Click <b>Yes</b> 
-    when asked to exit and restart the Workbench for the changes to take effect.</li>
-</ol><P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-122.htm">Scheduling automatic updates</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-123.htm">Reverting to a saved configuration</a><br>
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-126.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-126.htm
deleted file mode 100644
index eaef0c3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-126.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Uninstalling software</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Uninstalling software</H1>
-<p>The <b>Uninstall</b> wizard allows you to review and uninstall items in your
-configuration.  This wizard is shown when you select items and press <b>Uninstall...</b> from the
-<b>Installed Software</b> page.  To uninstall software from your system:  
-</p>
-<ol>
-  <li>Click <b>Help &gt; About</b> and then click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> to open a dialog showing pages that provide more detail about your installation. </li>
-  <li> Click the <b>Installed Software</b> tab to see a list of the software items that you have installed into your system.</li>
-  <li>Select the items that you wish to uninstall. </li>
- <li>Click <b>Uninstall...</b>.</li> 
-  <li>The <b>Uninstall Details</b> page will show you a list of the items that will be uninstalled.  Expanding each item will
-  show what additional items (if any) will be uninstalled as a result of your choice.</li>
-  <li>If you change your mind about which items should be uninstalled, you may click <b>Back</b>
-  to see a checkmark list of the items you selected before.  You may check and 
-  uncheck different items in the list, and click <b>Next</b> when you are ready to continue.</li>
-  <li>Click <b>Finish</b> to start the uninstall.</li>  
-  <li>Once all of the software is uninstalled successfully, you will be prompted
-    to restart for the Workbench.  Click <b>Yes</b> 
-    when asked to exit and restart the Workbench for the changes to take effect.</li>
-</ol><P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-123.htm">Reverting to a saved configuration</a>
-<a href="tasks-122.htm">Scheduling automatic updates</a><br>
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-127.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-127.htm
deleted file mode 100644
index 2639aec..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-127.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding a new software site</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Adding a new software site</H1>
-<p>There are several different ways to add a software site to the list of sites that
-are used when browsing available software and checking for updates.  You must
-know the Web Site location (URL) of the site that you want to add.  To add the site, use 
-one of the following procedures:
-</p>
-<ul>
-<li>Add a new site using the  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.internal.provisional.p2.ui.dialogs.RepositoryManipulationPage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Install/Update &gt; Available Software Sites</strong></a> preference page.
-<ol>
-  <li>Click the <b>Add...</b> button.</li>
-  <li>Type a name into the <b>Name</b> text box.</li>
-  <li>If the software site is located on the web, type the Web Site location (URL)
-  of the site into the <b>Location</b> text box.  You may also paste or drag and drop a
-  URL from a web browser into this text box.</li>
-  <li>If the software site is in your local file system (including a CD), click 
-  <b>Local...</b> to specify the directory location of the site.  </li>
-  <li>If the software site is in your local file system but is packaged
-  as a jar or zip file, click <b>Archive...</b> to specify the name
-  of the file.</li>
- </ol>
-</li>
-<li>Drag and drop the site URL from a browser into one
-of the following locations:
-<ol>
-  <li>The <b>Work With</b> combo box or the software list on the first page of the
-  <b>Install New Software</b> wizard.</li>
-  <li>The <b>Available Software Sites</b> preference page. </li>
-  <li>The <b>Location</b> text field in the <b>Add Site...</b> dialog.</li>
-</ol>
-</li>
-<li>On some platforms, you may be able to drag and drop a local directory
-or archive file from the file system into the same locations.</li>
-</ul>
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-128.htm">Working with the Available Software sites</a><br>
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-128.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-128.htm
deleted file mode 100644
index 4cea01c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-128.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with the Available Software sites</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with the Available Software sites</H1>
-<p>The <b>Available Software Sites</b> preference page allows you to define the software
-sites that are consulted when browsing for available software or updating the
-system.  To manage the list of sites used by the system:</p>
-<ol>
-  <li>Open the  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.internal.provisional.p2.ui.dialogs.RepositoryManipulationPage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Install/Update &gt; Available Software Sites</strong></a> preference page to see 
-  the list of sites that
-  are used to gather the available software and search for updates.</li>
-  <li>All sites registered in the system are shown in the list.  Sites marked as 
-  <b>Enabled</b> are those that are used to search for updates and browse
-  available software.  Sites marked as <b>Disabled</b> are not consulted by the
-  system.  For example, you may wish to disable a site that is temporarily not
-  available or experiencing network problems in order to speed up the search
-  for updates.</li>
-  <li>Select a site to see optional information about the status of the site at
-  the bottom of the page.  For example, if the system has been unable to find the
-  site on the network, the status will indicate that it is not available.</li>
-  <li>Click <b>Test Connection</b> to see if a site can be found by the system.</li>
- </ol>
-<p>
-You may change the sites that are used by the system in several ways:</p>
-<ul>
-<li>To add sites to the system:
-<ul>
-<li>Click <b>Add...</b> to enter the location of a new site.</li>
-<li>You may select a disabled site and click <b>Enable</b> in order to make it available
-to the system.</li>
-<li>Click <b>Import...</b> to import a list of sites that was previously
-exported to a file.</li>
-</ul></li>
-<li>To remove sites from the system:
-<ul>
-<li>Select a site and click <b>Disable</b> if you want to temporarily
-stop using the site.  This will keep the site in the list so that you can
-enable it later.</li>
-<li>Click <b>Remove</b> to remove the site from the list of sites.</li>
-</ul></li>
-<li>Click <b>Export...</b> to save the list of sites to a file.  This
-is useful for sharing site lists with other users or across multiple
-Eclipse installations.</li>
-</ul>
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-127.htm">Adding a new software site</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-122.htm">Scheduling automatic updates</a><br>
-</P>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-129.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-129.htm
deleted file mode 100644
index 213e9db..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-129.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating and installing software</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Updating and installing software</H1>
-
-<p>Eclipse provides facilities for adding new software to the platform or updating
-software in the system.  See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-125.htm">Updating software using the Available Updates wizard</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-130.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-130.htm
deleted file mode 100644
index 37d9212..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-130.htm
+++ /dev/null

@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Installation Details</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Installation Details</H1>
-
-<p>The
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; About Eclipse SDK</b></a>
-  dialog summarizes information about the installation.  To get detailed
-  information about the installation, click the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> button.  This will open a dialog showing pages that provide more detail about different aspects of
-  your installation.
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-<a href="tasks-123.htm">Reverting to a saved configuration</a><br>
-<a href="tasks-131.htm">Installation Details for Plug-ins</a><br>
-<a href="tasks-132.htm">Installation Details for Features </a><br>
-<a href="tasks-133.htm">Installation Details for the Configuration</a><br>
-</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-131.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-131.htm
deleted file mode 100644
index dbe1b9e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-131.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Installation Details for Plug-ins</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Installation Details for Plug-ins</H1>
-
-<p>You can browse detailed information about the individual plug-ins that compose your installation.
-This view is useful when the list of installed software or the feature detail is not enough.  
-At times you want to know exactly which versions of which plug-ins are installed into your system, without
-having to know what feature contained the plug-in.  To browse the plug-in details:
-</p>
-<ol>
-<li>Click <b>Help &gt; About</b> and then click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> to open a dialog showing pages that provide more detail about your installation. </li>
-  <li> Click the <b>Plug-ins</b> tab to see a list of the plug-ins that are installed in your
-  configuration.  The list includes each plug-in's name, provider, id, and version.</li>
-  <li>Select a plug-in to see additional detail.
-  <ul>
-  <li>Click <b>Legal Info</b> to launch a browser that shows any legal information that may be provided with the plug-in.</li>
-  <li>Click <b>Show Signing Info</b> to view information about the signing certificate provided with the plug-in.</li>
-  </ul>
-  </li>
-</ol>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-<a href="tasks-132.htm">Installation Details for Features </a><br>
-<a href="tasks-133.htm">Installation Details for the Configuration</a><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-132.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-132.htm
deleted file mode 100644
index 85e958f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-132.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Installation Details for Features</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Installation Details for Features</H1>
-
-<p>You can browse detailed information about the individual features that compose your installation.
-This view is useful when the list of installed software does not provide enough detail.  For example, you may have
-installed a particular feature that required some other features.  At times you want to know
-exactly which versions of which features are installed into your system without having to know
-what installed software item required that feature.  To browse the feature details:
-</p>
-<ol>
-<li>Click <b>Help &gt; About</b> and then click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> to open a dialog showing pages that provide more detail about your installation. </li>
-  <li> Click the <b>Features</b> tab to see a list of the features that are installed in your
-  configuration.  The list includes each feature's name, provider, id, and version.</li>
-  <li>Select a feature to see additional detail.
-  <ul>
-  <li>Click <b>License</b> to launch a browser that shows the feature's license.</li>
-  <li>Click <b>Plug-in Details</b> to open a dialog that lists all of the plug-ins provided as part of the feature.</li>
-  </ul>
-  </li>
-</ol>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-<a href="tasks-131.htm">Installation Details for Plug-ins</a><br>
-<a href="tasks-133.htm">Installation Details for the Configuration</a><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-</p>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a><br>
-</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-133.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-133.htm
deleted file mode 100644
index da18b11..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-133.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Installation Details for the Configuration</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Installation Details for the Configuration</H1>
-
-<p>You can browse detailed information about the current installation and capture that
-information when reporting a problem with your setup.  To view the
-configuration details:
-</p>
-
-<ol>
-<li>Click <b>Help &gt; About</b> and then click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> to open a dialog showing pages that provide more detail about your installation. </li>
-  <li> Click the <b>Configuration</b> tab to view a report containing various pieces of information about your 
-      installation, including plug-in versions, preference settings, and the contents 
-      of the internal log file. </li>
-  <li>Click <b>Copy to Clipboard</b> to copy the information.  You may then paste
-  this information into a file and attach it to a problem report.</li>
-</ol>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-<a href="tasks-131.htm">Installation Details for Plug-ins</a><br>
-<a href="tasks-132.htm">Installation Details for Features </a><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-134.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-134.htm
deleted file mode 100644
index 7e46876..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-134.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>About your installation</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>About your installation</H1>
-
-<p>The
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; About Eclipse SDK</b></a>
-  dialog summarizes information about your installation.  This is useful when reporting bugs or problems with your setup.
-  The detailed id of the build is shown, along with copyright information.
-</p>
-<p>
-  Underneath the product summary information is a row of buttons.
-  If you have not installed any additional features or plug-ins into your setup, you'll see only one button with the
-  Eclipse logo.  Clicking the button will open a dialog that shows information about the Eclipse features in your setup.
-  If you have installed additional features from other sources, you'll see additional buttons, one for each software
-  provider.  Clicking each provider's button will show the features from that provider.
- </p>
- <p>To get detailed
-  information about the installation, click the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.installationDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Installation Details...</b></a> button.  This will open a dialog showing pages that provide more detail about different aspects of
-  your installation.
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-130.htm">Installation Details</a><br>
-<a href="tasks-124.htm">Installing new software</a><br>
-<a href="tasks-132.htm">Installation Details for Features </a><br>
-<a href="tasks-131.htm">Installation Details for Plug-ins</a><br>
-<a href="tasks-120.htm">Updating the installation</a><br>
-<a href="tasks-126.htm">Uninstalling software</a><br>
-</p>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm
deleted file mode 100644
index d227fd8..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-14.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing build order</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing build order</H1>
-
-<p>By default, the Workbench computes the build order by interpreting project 
-references as prerequisite relationships. Alternatively, you can explicitly 
-define the order in which projects are built.
-</p>
-
-<p>The Build Order preference page allows you to disable the <b>Use default build 
-order</b> option so that you can access the projects list and manipulate 
-the order of it.
-</p>
-
-<p>To define the order in which the Workbench performs builds projects:
-</p>
-
-<ol>
-  <li>Open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.BuildOrder)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>General &gt; Workspace &gt; Build Order</b></a>
-  preference page.</li>
-  <li>Ensure that the <b>Use default build order</b> checkbox is cleared. If 
-    it is selected, the buttons on this page are disabled, and builds are performed 
-    in the order of the project list.</li>
-  <li>(Optional) Click <b>Add Project</b> and <b>Remove Project</b> buttons to 
-    add and remove projects from the list.</li>
-  <li>Select one or more projects in the list and click <b>Up</b> or <b>Down </b>to 
-    to set the preferred project build order.</li>
-  <li>Click <b>OK</b> to close the Preferences dialog.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-16.htm">Performing builds automatically</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm
deleted file mode 100644
index 80388de..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-16.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Performing builds automatically</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Performing builds automatically</H1>
-
-<P>To indicate that you want the Workbench to perform incremental builds whenever
-resources are saved:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Workspace</b></a>
-  preference page.</li>
-  <li>Select the <b>Build automatically</b> checkbox.</li>
-  <li>Click <b>OK</b> to close the Preferences page. The Workbench will automatically 
-    perform incremental builds of resources modified since the last build. Whenever 
-    a resource is modified, another incremental build occurs.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-14.htm">Changing build order</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm
deleted file mode 100644
index 2709aa5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-17.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Saving resources automatically before a manual build</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Saving resources automatically before a manual build</H1>
-
-<P>To automatically save all modified resources in the Workbench before a manual 
-build is done:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Workspace</b></a>
-  preference page.</li>
-  <li>Select the <b>Save automatically before build</b> checkbox.</li>
-  <li>Click <b>OK</b> to close the Preferences page.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-73.htm">Building resources</a><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-14.htm">Changing build order</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm
deleted file mode 100644
index b4eed3c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-18.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Linking the Project Explorer view to the active editor</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Linking the Project Explorer view to the active editor</H1>
-
-<P>When you have multiple files open for editing, you can configure one of the navigation views to automatically bring an open file to the foreground (make its editor 
-  session the active editor) every time you select that open file in one of the navigation views. There are two ways to set this.</P>
-
-<ol>
-  <li>From the Project Explorer menu, select <b>Link With Editor.</b></li>
-  <li>Click on the Link With Editor icon <img src="../images/synced.png" alt="Link with editor icon" >on 
-    one of the navigation bars.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-51.xhtml">Associating editors with file types</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm
deleted file mode 100644
index affb579..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1a.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with perspectives</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with perspectives</H1>
-<p>Perspectives define the initial set and layout of views in the Workbench window. 
-  They provide a set of functionality aimed at accomplishing a specific type of 
-  task or working with specific types of resources.
-</p>
-
-<p>
-See the Related tasks links for more details.
-</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-21a.htm">Detached views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-28.htm">Switching between perspectives</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a><br>
-<a href="tasks-9m.htm">Configuring perspective command groups</a><br>
-<a href="tasks-9k.htm">Configuring perspective shortcuts</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9d.htm">Deleting a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm
deleted file mode 100644
index be2a42e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1b.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with views and editors</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with views and editors</H1>
-<p>Views and editors are the main visual entities which appear in the Workbench. 
-  In any given perspective there is a single editor area, which can contain multiple 
-  editors, and a number of surrounding views which provide context.
-</p>
-
-<p>The Workbench provides a number of operations for working with views and editors.
-See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-21a.htm">Detached views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-<a href="tasks-3h.htm">Rearranging tabbed views</a><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-9l.htm">Detaching views</a><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-51.xhtml">Associating editors with file types</a><br>
-<a href="tasks-52.htm">Editing files outside the Workbench</a><br>
-<a href="tasks-3g.htm">Tiling editors</a><br>
-<a href="../gettingStarted/qs-39g.htm">Maximizing a view or editor</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm
deleted file mode 100644
index 1ead4a7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1c.htm
+++ /dev/null

@@ -1,36 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Navigating and finding resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Navigating and finding resources</H1>
-
-<p>The Workbench provides a number of mechanisms for navigating and finding resources.
-See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Project Explorer view</a><br>
-<a href="../concepts/csearchview.htm">Search view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="tasks-84b.htm">Searching for files</a><br>
-<a href="tasks-84.htm">Searching for text within a file</a><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Project Explorer view</a><br>
-  <a href="tasks-18.htm">Linking the Project Explorer view to the active editor</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm
deleted file mode 100644
index f3a1e47..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1d.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Problems, bookmarks, tasks and other markers</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Problems, bookmarks, tasks and other markers</H1>
-
-<p>Markers are objects that may be associated with Workbench resources.
-There are many uses of markers in the Workbench, including providing
-support for bookmarking resources or locations within resources, tracking
-ongoing tasks, or displaying error messages. See the related tasks section
-for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a><br>
-<a href="../concepts/concepts-11.htm">Markers</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-82.htm">Deleting a bookmark</a><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="tasks-78.htm">Deleting tasks</a><br>
-<a href="tasks-79.htm">Filtering the Task view</a><br>
-<a href="tquickfix.htm">Automatically fixing problems</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm
deleted file mode 100644
index c01bcb2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1e.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with projects, folders and resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with projects, folders and files</H1>
-
-<p>There are three different types of resources in the workbench: projects, folders,
-and files.  Projects are the largest structural unit used by the Workbench. Projects contain
-folders and files, and they can be opened, closed, or built. Folders can contain other folders 
-and files. The Workbench provides a number of mechanisms for working with projects, folders 
-and files.  See the related tasks section for more details.
-</p>
-<p>
-Folders and files can be linked to locations in the file system
-outside of the project's location.  These special folders and files are called 
-<a href="../concepts/concepts-13.htm">linked resources</a>.
-</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-2.htm">Workbench</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-47.htm">Closing projects</a><br>
-<a href="tasks-42b.htm">Deleting projects</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-63.htm">Moving resources</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-66.htm">Renaming resources</a><br>
-<a href="tasks-67.htm">Deleting resources</a><br>
-<a href="tasks-49.htm">Viewing resources properties</a>
-</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm
deleted file mode 100644
index 263c10e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1f.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with local history</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with local history</H1>
-
-<p>A local edit history of a file is maintained when you create or modify a file. 
-Each time you edit and save the file, a copy is saved so that you can replace 
-the current file with a previous edit or even restore a deleted file.
-You can also compare the contents of 
-all the local edits. Each edit in the local history is uniquely represented 
-by the date and time the file was saved. See the Related tasks links for more
-details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm
deleted file mode 100644
index 477196f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1h.htm
+++ /dev/null

@@ -1,33 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working in the team environment</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working in the team environment with CVS</H1>
-
-<p>The Workbench provides tools to manage, share and synchronize resources. The 
-  CVS standard is supported by default. See the Related tasks links below for 
-  more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-1i.htm">Working with a CVS repository</a><br>
-<a href="tasks-1j.htm">Working with projects shared with CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-1k.htm">Versioning</a>
-</p>
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm
deleted file mode 100644
index 6660367..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1i.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with a CVS repository</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with a CVS repository</H1>
-
-<p>In the CVS team programming environment, team members do all of their work 
-in their own Workbenches, isolated from others. Eventually they will want to 
-share their work. They do this via a CVS repository. The Workbench provides 
-a number of mechanisms which support working with CVS repositories. See the 
-Related tasks links for more details. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-cvs-ssh2.htm">Connecting and configuring CVS with SSH</a><br>
-<a href="tasks-cvs-passwords.htm">Password Management</a><br>
-<a href="tasks-94.htm">Discarding a CVS repository location</a><br>
-<a href="tasks-93.htm">Refreshing the CVS Repositories view</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-95.htm">Changing the properties of a CVS repository location</a><br>
-<a href="tasks-95a.htm">Changing the encoding of a CVS repository location</a><br>
-<a href="tasks-team-1.htm">Setting the content type of a file extension</a>
-
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm
deleted file mode 100644
index c069190..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1j.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with projects shared with CVS</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with projects shared with CVS</H1>
-
-<p>The Workbench provides a number of mechanisms which support working with projects 
-shared via CVS. See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-107b.htm">Enabling the CVS resource decorations</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-117a.htm">Project checked out with another CVS tool</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-<a href="tasks-96b.htm">Checking out a folder into an existing project</a><br>
-<a href="tasks-cvs-10.htm">Disconnecting a project from CVS</a><br>
-<a href="tasks-cvs-11.htm">Setting the CVS keyword substitution mode</a><br>
-<a href="tasks-cvs-16.htm">Filtering CVS Revisions in the History view</a><br>
-<a href="tasks-117b.htm">Changing the sharing of a project</a><br>
-<a href="tasks-cvs-project-set.htm">Sharing your workspace setup using Project Sets</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm
deleted file mode 100644
index a67957d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-1k.htm
+++ /dev/null

@@ -1,34 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Versioning</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Versioning</H1>
-
-<p>Resources can be versioned in order to capture a snapshot of their current state
-at one specific point in time. See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-100.htm">Creating a version of a project</a><br>
-<a href="tasks-107b.htm">Enabling the CVS resource decorations</a><br>
-<a href="tasks-118.htm">Versioning projects in the repository</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm
deleted file mode 100644
index 15404f2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-2.htm
+++ /dev/null

@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Upgrading Eclipse</title>
-</head>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Upgrading Eclipse</h1>
-<p>
-If you are upgrading to a newer release of Eclipse from an older release, there are
-simple steps to follow to migrate your workspace to the new release.  Your workspace
-is the directory on disk that contains all of your project files, as well as meta-data such
-as preferences you may have customized.  The steps to follow for upgrading depend on
-whether or not you used the &quot;-data&quot; command line argument when starting 
-Eclipse.  The &quot;-data&quot; argument is recommended because it clearly specifies the 
-location of your workspace.
-</p>
-<p><i>Tip:</i> It doesn't hurt to make a backup of your workspace before
-upgrading.  After you've upgraded your workspace, you won't be able to use it
-again with an older version of Eclipse.  If you ever want to go &quot;back in time&quot;
-to an earlier release, you'll need that backup!
-</p>
-
-<p>The workspace chooser dialog allows you to choose the location of your
-workspace.  This dialog appears on first startup in the absence of a -data argument. 
-The default location provided by this dialog will be a "workspace" child of your home directory 
-(for example, C:\Documents and Settings\UserName\workspace.)</p> 
-<p>Unless you have an existing workspace from a previous Eclipse version, you can
-keep this default or choose some other location.  You should not store your workspace
-inside the Eclipse install directory, because that will make it more difficult to upgrade
-to a newer version of Eclipse.  You should not copy or move the workspace directory, because it may
-contain metadata with absolute file system paths, which will be invalid if the workspace is copied elsewhere.</p>
-<p>In Eclipse 3.0 and earlier, Eclipse's default location for the workspace was 
-  under the Eclipse directory. For example, if the eclipse.exe was in D:\eclipse-SDK-3.0.1\eclipse, 
-  then the default workspace location would be D:\eclipse-SDK-3.0.1\eclipse\workspace.</p>
-<p>To load a workspace created using 3.0 or earlier, just point to 
-  the old workspace directory using the workspace chooser, whether it's under 
-  the old install directory or elsewhere.</p>
-<p>&nbsp;</p>
-<h2>Using the &quot;-data&quot; argument</h2>
-<p>
-If you were previously using the &quot;-data&quot; argument to start Eclipse, your 
-upgrade path is much easier:</p>
-<ol>
-<li>Install the new version of Eclipse in a new location, separate from any old version
-of Eclipse.</li>
-<li>Start this new version of Eclipse, using the &quot;-data&quot; command line argument to 
-point to your old workspace location.</li>
-</ol>
-<p>See the example in the previous section for an illustration.</p>
-
-<h2>Adding third party plug-ins</h2>
-<p>
-If you have installed extra plug-ins in your Eclipse environment, you will need to add
-these new plug-ins to each new build or version of Eclipse you install.  Before you do
-this, refer to the documentation for those plug-ins to ensure they are compatible
-with the version of Eclipse you are moving to.  There are several ways to add these
-extra plug-ins to your new Eclipse install:</p>
-<ol>
-<li>Copy the directories for each plug-in into the &quot;dropins&quot; directory of your
-new Eclipse version.</li>
-<li>Use an Eclipse update site to re-install those extra plug-ins or features in the
-new version of Eclipse.</li>
-<li>If you are using product extensions, simply copy the &quot;links&quot; directory
-into the new Eclipse version install directory.  For more details on product extensions,
-see the documentation in the Platform Plug-in Developer Guide, under <b>Programmer's
-Guide &gt; Packaging and delivering Eclipse based products &gt; Product extensions</b>.</li>
-</ol>
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm
deleted file mode 100644
index e4cf33f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-20.htm
+++ /dev/null

@@ -1,136 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing fonts and colors</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing fonts and colors
-</H1>
-
-<p>By default, the Workbench uses the fonts and colors provided by the operating 
-  system. However, there are a number of ways that this behavior can be customized. 
-</p>
-
-<h2>Fonts</h2>
-
-<p>The Workbench lets you directly configure the following fonts: </p>
-
-<dl>
-  <dt>Banner Font</dt>
-  <dd>Used in PDE editors, welcome pages and in the title area of many wizards. 
-    For instance the New Project wizard uses this font for the top title.</dd>
-  <dt>Dialog Font</dt>
-  <dd>Used for widgets in dialogs.</dd>
-  <dt>Header Font</dt>
-  <dd>Used as a section heading. For instance the Welcome page for the Eclipse 
-    Platform uses this font for the top title.</dd>
-  <dt>Text Font</dt>
-  <dd>Used in text editors.</dd>
-  <dt>CVS Console Font</dt>
-  <dd>Used in the CVS console.</dd>
-  <dt>Ignored Resource Font</dt>
-  <dd>Used to display resources that are ignored from CVS.</dd>
-  <dt>Outgoing Change Font</dt>
-  <dd>Used to display outgoing changes in CVS.</dd>
-  <dt>Console Font (defaults to text font)</dt>
-  <dd>Used by the debug console.</dd>
-  <dt>Detail Pane Text Font (defaults to text font)</dt>
-  <dd>Used in the detail panes of debug views.</dd>
-  <dt>Memory View Table Font (defaults to text font)</dt>
-  <dd>Used in the table of the memory view.</dd>
-  <dt>Java Editor Text Font (defaults to text font)</dt>
-  <dd>Used by Java editors.</dd>
-  <dt>Properties File Editor Text Font (defaults to text font)</dt>
-  <dd>Used by Properties File editors.</dd>
-  <dt>Compare Text Font (defaults to text font)</dt>
-  <dd>Used by textual compare/merge tools.</dd>
-  <dt>Java Compare Text Font (defaults to text font)</dt>
-  <dd>Used by Java compare/merge tools.</dd>
-  <dt>Java Properties File Compare Text Font (defaults to properties file editor 
-    text font )</dt>
-  <dd>Used by Java properties file compare/merge tools.</dd>
-  <dt>Part Title Font (defaults to properties file editor text font )</dt>
-  <dd>Used for view and editor titles. <strong>Note:</strong> It is recommended 
-    that this font not be bold or italic because the workbench will use bold and 
-    italic versions of this font to display progress.</dd>
-  <dt>View Message Font (defaults to properties file editor text font )</dt>
-  <dd>Used for messages in the view title bar (if present).</dd>
-  
- </dl>
-
-<p>To change these fonts:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a>
-  preference page.</li>
-  <li>Select the font you want to change.</li>
-  <li>Click <b>Change</b>.</li>
-  <li>Use the dialog which opens to select a font.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><strong>Note:</strong> You can also click <b>Use System Font</b> to set the 
-  font to a reasonable value chosen by the operating system. For example, on Windows 
-  this will use the font selected in the Display Properties control panel.</p>
-
-<p>Plug-ins that use other fonts may also provide preference entries to allow them to
-be customized. For example, the Java development tools provide a setting for controlling
-the font used by the Java editor (see <b>Java &gt; Java Editor Text Font</b> on the preferences page).
-</p>
-
-<p>In addition to the above, some text is always displayed in the system font. For example, 
-the navigator tree always does this. To change the font used in these areas, you can use the
-configuration tools provided by the operating system (for example, the Display Properties control panel on
-Windows, or the .Xdefaults file in Motif).
-</p>
-
-<h2>Colors</h2>
-
-<p>To set the colors used by the Workbench to display error text and hyperlink text:
-</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ColorsAndFonts)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Appearance &gt; Colors and Fonts</b></a>
-  preference page.</li>
-  <li>Select the color you want to change in the tree view and click the color 
-    bar on the right.</li>
-  <li>Use the dialog which opens to select a color.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>Plug-ins that use other colors may also provide preference entries to allow them to
-be customized. For example, the searching support provides a preference for controlling
-the color used to display potential matches
-(see the <b>Foreground color for potential matches</b> item on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.search.preferences.SearchPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Search</b></a> preference page).
-</p>
-
-<p>In general, the Workbench uses the colors that are chosen by the operating 
-  system. To change these colors you can use the configuration tools provided 
-  by the system (for example, the Display Properties control panel on Windows, 
-  or the .Xdefaults file in Motif). </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/accessibility/fontsandcolors.htm">Fonts and Colors in Eclipse</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm
deleted file mode 100644
index 200be18..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-24.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing where perspectives open</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1>Changing where perspectives open</H1>
-
-<p>You can change the default behavior for how perspectives are opened in the Workbench.
-</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Perspectives</b></a> preference page.</li>
-  <li>Select either <b>In the same window</b> or <b>In a new window</b> from the
-	<b>Open a new perspective</b> group.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p CLASS="Para" Label="Type"><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-28.htm">Switching between perspectives</a><br>
-<a href="tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a><br>
-<a href="tasks-9m.htm">Configuring perspective command groups</a><br>
-<a href="tasks-9k.htm">Configuring perspective shortcuts</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm
deleted file mode 100644
index c47066e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-28.htm
+++ /dev/null

@@ -1,31 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Switching between perspectives</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Switching between perspectives</H1>
-<P> Open perspectives are represented by icons on the perspective bar. When you 
-  have more than one perspective open, you can switch between them by clicking 
-  the icons on the shortcut bar. </P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts."><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm
deleted file mode 100644
index 04b3668..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening views</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Opening views</H1>
-<P>Perspectives offer pre-defined combinations of views and editors. 
-  To open a view that is not included in the current perspective, select <b>Window 
-  &gt; Show View</b> from the main menu bar.
-</P>
-
-<P>You can create <i>fast views</i> to provide quick access to views that you 
-  use often. </P>
-
-<P>After adding a view to the current perspective, you may wish 
-  to save your new layout by clicking 
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.savePerspective")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Save Perspective As...</b></a>.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts."><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-21a.htm">Detached views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-9l.htm">Detaching views</a><br>
-<a href="../gettingStarted\qs-39g.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm
deleted file mode 100644
index 2cfcbae..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-31.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Specifying the default perspective</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Specifying the default perspective</H1>
-<P>The default perspective is indicated in the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-Select Perspective</a> dialog (accessible via the <b> Window &gt; Open Perspective 
-  &gt; Other... </b> menu). The pre-defined default perspective is indicated by the 
-  word default in brackets following the perspective name, for example, <strong>Resource 
-  (default)</strong>. </P>
-
-<P>To change the default perspective:</P>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Perspectives</b></a> preference page.</li>
-  <li>Select the perspective that you want to define as the
-    default from the list of available perspectives, and click <b>Make Default</b>.
-    The default indicator moves to the perspective that you selected.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts."><br>
-<a href="../concepts/concepts-2.htm">Workbench</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-9f.htm">Opening perspectives</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-9n.htm">Showing and hiding menu items and toolbar buttons</a><br>
-<a href="tasks-9m.htm">Configuring perspective command groups</a><br>
-<a href="tasks-9k.htm">Configuring perspective shortcuts</a><br>
-
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-32.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-32.htm
deleted file mode 100644
index ccb61d1..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-32.htm
+++ /dev/null

@@ -1,39 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using the classic update manager</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Using the classic update manager</H1>
-<P>In some situations you may not be able to install or update software using the
-menu commands in the <b>Help</b> menu. In these situations you will automatically be
-redirected to the classic <em>update manager</em>. You can also access the
-classic update manager from the <b>General &gt; Capabilities</b> preference
-page by enabling the <b>Classic Update</b> capability. When this capability
-is enabled, a <b>Software Updates...</b> sub-menu will appear in the <b>Help</b>
-menu, providing access to classic update commands.</p>
-<p>The remaining topics in this section, and the related tasks below, 
-pertain only to use of the classic update commands</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts."><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-34.htm">Installing new features with the update manager</a><br>
-<a href="tasks-35.htm">Enabling, disabling, and uninstalling features with the update manager</a><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-<a href="tasks-37.htm">Controlling the Eclipse update policy</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm
deleted file mode 100644
index 53b1499..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-33.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Inspecting the current configuration</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Inspecting the current configuration</H1>
-
-<p>The
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; About Eclipse SDK</b></a>
-  dialog shows most of the important information about the features and plug-in configured in 
-  the product. To find out further detailed information about the current configuration:
-</p>
-
-<ol>
-  <li>Open the update configuration manager by clicking
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.manageConfiguration")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Software Updates &gt; Manage Configuration</b></a>.
-  This opens the Product Configuration dialog.</li>
-  <li>In the Product Configuration dialog expand the root node (current&nbsp; 
-  configuration).
-    The first tier of items are locations on the local computer where the files
-    for features and plug-ins are stored. For a typical product, all features
-    are installed in a single directory sub-tree. However, a feature that is
-    installed as an extension of another product are usually located in a
-    separate directory sub-tree.</li>
-  <li>Expand the location to see the feature versions installed there.</li>
-  <li>The nesting of the features indicates which child features are included in
-    a given parent feature. Nested features act as a unit.</li>
-  <li>Select a feature version and click <b>Show Properties</b> to open the 
-  Properties dialog which presents more detailed information about the selected feature.</li>
-  <li>Click <b>Show Disabled Features</b> filter on the toolbar of the Product
-    Configuration dialog. Any feature versions that are disabled are now
-    shown (you might not have any). Disabled feature versions are ones that are
-    installed on the local computer but excluded from the current configuration.
-    At most one version of any given feature can be present in a given
-    configuration; usually the ones with the lower version numbers will be in a
-    disabled state.</li>
-  <li>In the Properties dialog of a feature, click <b>Status</b> to find out whether
-    the selected feature is configured exactly as packaged. The status will show
-    when a feature's plug-ins are present at different versions, or disabled due
-    to missing prerequisite plug-ins that are expected to be supplied by some
-    other feature.</li>
-</ol>
-
-<p>
-In this dialog you can revert to a previous install configuration, view the installation history, or
-even add another eclipse product extension. A product extension is a local folder that has a similar
-file layout as the eclipse installation, but with a .eclipseextension marker (instead of .eclipseproduct). 
-If you add a product extension, make sure there are no duplicate features in the extension
-you add.
-</p>
-<p>
-When the install wizard is used to install features in a user selected location, that location
-automatically becomes an eclipse product extension.
-</p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-34.htm">Installing new features with the update manager</a><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-<a href="tasks-37.htm">Controlling the Eclipse update policy</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm
deleted file mode 100644
index 0afc6eb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-34.htm
+++ /dev/null

@@ -1,94 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Installing new features with the update manager</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Installing new features with the update manager</H1>
-
-<p>To locate and install a new feature into a product (ordinarily requires web 
-  access):
-</p>
-
-<ol>
-  <li>Open the Install Wizard by clicking
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.findAndInstallUpdates")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Software Updates &gt; Find and Install...</b></a>.
-  This opens the wizard. </li>
-  <li>Select the second button, &quot;<b>Search for new features to install</b>&quot; and 
-  click <b>Next</b>.</li>
-  <li>Create a bookmark for an update site where Eclipse features and plug-ins 
-  are published. In the sites to search list, select <b>Add&nbsp; Update Site</b> to 
-  add a remote site, or <b>Add Local Site</b> if the site is available on a local drive 
-  (including a CD), or <b>Add Archived Site</b>, when the site is available locally 
-  but is packaged as a jar or zip file.</li>
-  <li>In the add site dialog, give the site a name such as 
-    &quot;CompanyA&quot; and enter the URL such as
-	&quot;http://companyA.example.com/eclipseupdates&quot;.</li>
-  <li>After adding the site, expand it to the
-    categories of feature versions available at that update site. This will
-    contact the web site to discover what features are available.</li>
-  <li>Select the categories you want to search and click <b>Next</b>.</li>
-  <li>Wait for the search to finish and selecting the features to be added. You 
-  can view the description or more detailed properties for any feature by 
-  selecting the feature and pressing the &quot;Properties&quot; button.</li>
-  <li>Once you're decided which features to install, click <b>Next</b>.</li>
-  <li>Carefully review the license agreements for the  features. If the
-    terms of all these licenses are acceptable, check &quot;I accept the terms
-    in the license agreements&quot;. Do not proceed to download the features if
-    the license terms are not acceptable.</li>
-  <li>If a feature selected for install include optional features, a page will
-    show up allowing you to select whether you want them installed or not.
-    Optional features typically carry functionality that is not essential for
-    proper functioning of the main feature.</li>
-  <li>The Install Location page controls where the new feature's files are to be
-    installed on the local computer. Select the directory into which the product
-    is installed and hit <b>Next</b>. (If the product is installed in a
-    directory to which you do not have write access, you should contact your
-    system administrator and get them to install this feature so that it will be
-    generally available. The other option is to click <b>Add</b> and point to a 
-  directory to which you do have write access.</li>
-  <li><p>Feature versions can be digitally signed by the company that provides
-    them. This allows you to verify more easily that the features and
-    plug-ins that are about to be downloaded and installed are coming from a
-    trusted supplier.</p><br><p><b>Warning:</b> Because of the possibility of harmful or even
-    malicious plug-ins, you should only download features from parties that
-    you trust.</p><br> <p>Click <b>Install</b> to allow the downloading and installing
-    to proceed.</p></li>
-  <li>Once the new feature and plug-ins have been downloaded successfully and
-    their files installed into the product on the local computer, a new
-    configuration that incorporates these features and plug-ins will be
-    formulated. Click <b>Yes</b> when asked to exit and restart the workbench for the
-    changes to take effect. To add other new features at the same time before
-    restarting, click <b>No</b> and repeat. If this was a new feature and can be 
-  dynamically installed into the current configuration, you will also be 
-  presented with a <b>&quot;Apply Now&quot;</b> button. This will not restart the 
-  platform, but configures the feature and the plug-ins into the current 
-  configuration.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-32.htm">Using the classic update manager</a><br>
-<a href="tasks-33.htm">Inspecting the current configuration</a><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-<a href="tasks-38.htm">Restoring a saved configuration</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm
deleted file mode 100644
index 43ce034..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-35.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Enabling, disabling, and uninstalling features</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Enabling, disabling, and uninstalling features with the update manager</H1>
-
-<p>You can browse and manage your configuration from the <b>Product Configuration</b> dialog.
-Open the <b>Product Configuration</b> dialog by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.manageConfiguration")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help &gt; Software Updates &gt; Manage Configuration</b></a>. 
-</p>
-<ol>
-  <li><b>Disabling a feature</b>: select the feature and click <b>Disable</b>
-  in the right pane of the dialog.  This option is available only when the feature is 
-  currently enabled, and the feature is either an optional feature or a root feature 
-  (not included by other features).</li>
-  <li><b>Enabling a feature</b>: First, ensure <b>Show Disabled Features</b>
-  is turned on in the tool bar.  Then, select a disabled optional or root feature and click  
-  <b>Enable</b> in the right pane of the dialog.</li>
-  <li><b>Uninstalling a feature</b>: features that you have installed using
-  the update manager can be uninstalled, provided they are already disabled, or that they 
-  are optional or root features. If the feature is disabled, make sure 
-  <b>Show Disabled Features</b> is turned on in the tool bar.  Select the feature 
-  and click <b>Uninstall</b> in the right page of the dialog.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-32.htm">Using the classic update manager</a><br>
-<a href="tasks-34.htm">Installing new features with the update manager</a><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-<a href="tasks-37.htm">Controlling the Eclipse update policy</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm
deleted file mode 100644
index d235ba4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-36.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Updating features with the update manager</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Updating features with the update manager</h1>
-
-<p>To check to see whether there are updates for a product's existing features
-  (requires Internet access):
-</p>
-
-<ol>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.findAndInstallUpdates")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Software Updates &gt; Find and Install...</b></a> and select the 
-  first choice (search for updates). This will contact 
-    the Web sites associated with the product's features to discover what versions 
-    of those features are available. The potential upgrades are presented in on 
-  the next page.</li>
-  <li>Select the feature versions that you wish to upgrade, and click <b>Next</b>.</li>
-  <li>Carefully review the license agreements for the upgraded features. If the 
-    terms of all these licenses are acceptable, check &quot;I accept the terms 
-    in the license agreements.&quot; Do not proceed to download the features if 
-    the license terms are not acceptable.</li>
-  <li><p>Feature versions can be digitally signed by the company that provides them. 
-    This allows you to verify more easily that the features and plug-ins 
-    that are about to be downloaded and installed are coming from a trusted supplier. </p><br>
-    <p><b>Warning:</b> Because of the possibility of harmful or even malicious plug-ins, 
-    you should only download features from parties that you trust. </p><br><p>Click 
-    <b>Install</b> to allow the downloading and installing to proceed.</p></li>
-  <li>Once all the features and plug-ins have been downloaded successfully and 
-    their files installed into the product on the local computer, a new configuration 
-    that incorporates these features and plug-ins will be formulated. Click <b>Yes</b> 
-    when asked to exit and restart the Workbench for the changes to take effect.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-32.htm">Using the classic update manager</a><br>
-<a href="tasks-33.htm">Inspecting the current configuration</a><br>
-<a href="tasks-34.htm">Installing new features with the update manager</a><br>
-<a href="tasks-35.htm">Enabling, disabling, and uninstalling features</a><br>
-<a href="tasks-37.htm">Controlling the Eclipse update policy</a><br>
-<a href="tasks-37a.htm">Scheduling automatic updates</a><br>
-<a href="tasks-38.htm">Restoring a saved configuration</a>
-</P>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm
deleted file mode 100644
index 1c99864..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37.htm
+++ /dev/null

@@ -1,166 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Controlling the Eclipse update policy</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Controlling the Eclipse update policy</h1>
-
-<p>Eclipse Update allows users to search for updates to the currently installed 
-features. For each installed feature, Update uses the embedded URL to 
-connect to the remote server and search for new versions. If there are updates, 
-Eclipse allows users to initiate the install procedure. After downloading, 
-installing and restarting the platform, new feature version is ready for use.</p>
-<p>In companies with many users of the same Eclipse-based product (typically a 
-commercial one), several problems can arise from this model:</p>
-<ol>
-  <li>Updates for very large products (e.g. 500+ plug-ins) are also large. 
-  I/T support teams may not like the idea of hundreds of developers individually 
-  downloading 500MEG updates to their individual machines. In addition to the 
-  bandwidth hit, such a large download request may fail, leading to repeated 
-  attempts and increased developers' downtime.</li>
-  <li>Some companies explicitly don't want the developers downloading updates 
-  directly from the Internet. For example, they can set up a local support team 
-  that may not be ready to handle requests related to the version of the product
-    already available from the provider's update site. They may want to restrict updates and 
-  fixes to the internally approved list. Ideally, they would do that by setting 
-  up 'proxy' update sites on the LAN (behind the firewall).</li>
-  <li>Once updates are set in the proxy sites as above, administrators need a 
-  way of letting users know that updates are available.</li>
-</ol>
-<h2>Update policy to the rescue</h2>
-
-<h3>Support for creating local (proxy) update sites</h3>
-<p>First step for a product administrator would be to set up a local Eclipse 
-update site on a server connected to the company's LAN (behind the firewall). 
-The update site would be a subset of the product's update site on the Internet 
-because it would contain only features and plug-ins related to the updates that 
-the company wants applied at the moment. Technically, this site would be a 
-regular Eclipse update site with site.xml, feature and plug-in archives.</p>
-<p>Administrators would construct this site in two ways:</p>
-<ol>
-  <li>Product support teams would make a zip file of the update site readily 
-  available for this particular purpose. Administrators would simply need to 
-  download the zip file from the product support web page using the tool of 
-  their choice and unzip it in the local server. This approach is useful for 
-  very large zip files that require modern restartable downloading managers 
-  (those that can pick up where they left off in case of the connection 
-  problems).</li>
-  <li>Eclipse Update provides a tool to mirror remote update sites 
-  entirely or allow administrators to select updates and fixes to download.
-  This mirroring capability would be fully automated and would greatly simplify administrator's task 
-  but it relies on Update network connection support.</li>
-</ol>
-<h3>Common update policy control</h3>
-<p>Since features have the update site URL embedded in the manifest, they are unaware of the local 
-update sites set up by the administrators. It is therefore important to provide <b>
-redirection capability</b>. This and other update policy settings can be set for
-an Eclipse product by creating an update policy file and configuring Update to 
-use that file when searching.</p>
-<p>The file in question uses XML format and can have any name. The file can be set in
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.update.internal.ui.preferences.MainPreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Preferences &gt; Install/Update</b></a>
-<font color="#0000FF"> </font>in the <b>Update Policy</b> field. The text field 
-is empty by default: users may set the URL of the update policy file. The file 
-is managed by the local administrator and is shared for all the product 
-installations. Sharing can be achieved in two ways:</p>
-<ul>
-  <li>If users install the product: users are told to open the preference page 
-  and enter the provided URL</li>
-  <li>If administrators install the product: administrators edit the file 'plugin_customization.ini' 
-  in the primary product feature and set the default value of the 'updatePolicyURL' 
-  property as follows:<br>
-  <br>
-&nbsp;&nbsp;&nbsp; <code>org.eclipse.update.core/updatePolicyURL = &lt;URL value&gt;<br>
-  </code><font color="#0000FF"></font><br>
-  <br>
-  This will cause all the installations to have this file set by default.</li>
-</ul>
-<p>The policy file must conform to the following DTD:</p>
-<blockquote>
-  <p><tt>&lt;?xml encoding=&quot;ISO-8859-1&quot;?&gt;</tt></p>
-  <p><tt>&lt;!ELEMENT update-policy (url-map)*&gt;</tt><br>
-  <tt>&lt;!ATTLIST update-policy</tt><br>
-  <tt>&gt;</tt></p>
-  <p><tt>&lt;!ELEMENT url-map EMPTY&gt;<br>
-  &lt;!ATTLIST url-map<br>
-  &nbsp;&nbsp;&nbsp; pattern&nbsp;&nbsp;&nbsp; CDATA #REQUIRED<br>
-  &nbsp;&nbsp;&nbsp; url&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CDATA
-  #REQUIRED<br>
-  &gt;</tt></p>
-</blockquote>
-<h4>url-map</h4>
-<ul>
-  <li><b>pattern</b> - a string that represents prefix of a feature ID (up to
-    and including a complete ID). A value of "*" matches all the features.</li>
-  <li><b>url</b> - a URL of the alternative update site that should be used if
-    the feature ID begins with the pattern. If the string is empty, features matching 
-    pattern will not be updateable.</li>
-</ul>
-<p>This element is used to override Update URLs embedded in feature manifests. When
-looking for new updates, Eclipse search will check the update policy (if 
-present) and check if <b>url-map</b> for the matching feature prefix is 
-specified. If a match is found, the mapped URL will be used <b> instead</b> of the 
-embedded one. This way, administrators can configure Eclipse products to search 
-for updates in the local server behind the firewall. Meanwhile, third-party
-features installed by Eclipse Update will continue to be updated using the
-default mechanism because they will not find matches in the policy.</p>
-<p>Several <b>url-map</b> elements may exist in the file. Feature prefixes can be 
-chosen to be less or more specific. For example, to redirect all Eclipse 
-updates, the pattern attribute would be <code>&quot;org.eclipse&quot;</code>. Similarly, it is 
-possible to use a complete feature ID as a pattern if redirection is required on 
-a per-feature basis.</p>
-<p>Patterns in the file may be chosen to progressively narrow the potential
-matches. This may result in multiple matches for a given feature. In this case,
-the <b>match with a longest pattern</b> will be used. For
-example:</p>
-<blockquote>
-<pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;update-policy&gt;
-	&lt;url-map pattern=&quot;org.eclipse&quot; url=&quot;URL1&quot;/&gt;
-	&lt;url-map pattern=&quot;org.eclipse.jdt&quot; url=&quot;URL2&quot;/&gt;
-&lt;/update-policy&gt;</pre>
-</blockquote>
-<p>In the case above, all Eclipse features will be updated from URL1, except <code>org.eclipse.jdt</code> that will use URL2.</p>
-<p>Update policy files do not contain translatable strings and therefore do not
-require special NL handling. In general, the files should use UTF-8 encoding.</p>
-<h3>Automatic discovery of updates</h3>
-<p>The third part of the overall solution is covered by another 
-<a href="tasks-37a.htm">topic</a> but is mentioned here because it is an integral part 
-of the solution. <a href="tasks-37a.htm">Automatic updates</a> will allow Eclipse to run update search on a 
-specified schedule (on each startup (the default), once a day, once a week 
-etc.). </p>
-<h2>Summary </h2>
-<p>Here is the complete sequence of steps that comprise the solution:</p>
-<ol>
-  <li>Administrator allocates a server on the company LAN for hosting local 
-  product updates. Initially it contains no update sites. The machine must have
-    an HTTP server running.</li>
-  <li>Administrator sets up an update policy file on that server and instructs 
-  all users to set the update policy preference the provided URL.</li>
-  <li>As the product provider ships updates and fixes on their update sites,
-    administrator downloads supported updates onto the local server.</li>
-  <li>Automatic update executed at the scheduled frequency when the client's
-    product is up picks up the local 
-  updates and notifies the user</li>
-  <li>User chooses to install the discovered updates</li>
-</ol>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-37a.htm">Automatic Update Scheduler</a><br>
-</P>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm
deleted file mode 100644
index 82e7c92..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-37a.htm
+++ /dev/null

@@ -1,78 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Scheduling automatic updates</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-
-<h1>Scheduling automatic updates</h1>
-<p>You can configure Eclipse update to search for updates to the installed features 
-on a periodic basis automatically. You can configure how these updates
-are scheduled and performed from the <b>Install/Update &gt; Automatic Updates</b> preference page.
-</p>
-<h3>Scheduling options</h3>
-<p>Each time an Eclipse-based product starts, the update scheduler will
-activate based on the chosen scheduling. You can choose between the following
-update policies:</p>
-<ul>
-  <li>No automatic search</li>
-  <li>On each startup (default)</li>
-  <li>Every day at a specific time (i.e. 3:00PM) *</li>
-  <li>On a scheduled day of the week at a specific time (i.e. Monday 8:00AM) *</li>
-</ul>
-<p>* assuming the application is active. If the application is not active at a 
-scheduled time and the search is past due, it will immediately start on the next 
-startup</p>
-<h3>Download options</h3>
-<p>Scheduling options define when searches are performed but do not 
-define what actually happens when updates are found. Download options 
-control this behavior (this set of options is disabled if automatic search is 
-turned off). You can choose between:</p>
-<ul>
-  <li>Search for updates and notify  when they are available (default)</li>
-  <li>Download new updates automatically and notify  when ready to install them</li>
-</ul>
-<p>In both cases, the update scheduler will execute in the background 
-when necessary based on the scheduling options. There will be no messages if no 
-updates are found. If there are updates, the behavior will depend on the 
-chosen download option.</p>
-<h4>Search and notify</h4>
-<p>If search only is selected, a message box will open to notify you when updates
-are found:</p>
-<p><font color="#0000FF">New updates have been found for this product. Do you want to 
-download them?</font></p>
-<p><font color="#0000FF">[Yes] [No] </font></p>
-<p>If <b>Yes</b> is pressed, an update wizard will show a list of detected updates. The 
-same wizard is used when you search for updates manually using
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.findAndInstallUpdates")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Help &gt; Software Updates &gt; Find and Install...</b></a>.</p>
-<p>If <b>No</b> is pressed, the dialog closes and the updates are ignored.</p>
-<h4>Download new updates</h4>
-<p>If the second option has been selected (download updates automatically), the 
-search will be scheduled as before, but when new updates are found, the 
-download will commence immediately. When all the features have been successfully 
-downloaded, a different message box will show up:</p>
-<p><font color="#0000FF">New updates have been found and downloaded. Do you want to install them?</font></p>
-<p><font color="#0000FF">[Yes] [No] </font></p>
-<p>If <b>No</b> is pressed, the dialog will close and no updates will occur.
-If <b>Yes</b> is pressed, installation of the new updates will proceed.</p>
-<p>If you choose not to install the downloaded features, but later launch the 
-<b>Help &gt; Find and Install...</b> wizard for updating, the downloaded files will be reused, 
-unless there are newer versions on the server or you have restarted eclipse. </p>
-
-<P>
-<img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-36.htm">Updating features with the update manager</a><br>
-</P>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm
deleted file mode 100644
index ce81ece..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-38.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Restoring a saved configuration</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Restoring a saved configuration</h1>
-
-<p>A previously saved configuration (or any configuration recorded in the history) 
-  can be restored, thereby backing out of the results of an unsuccessful upgrade. 
-  Restoring a saved configuration does not delete the files for feature and plug-in 
-  versions from the local computer; it merely ignores them and acts as it did 
-  when they were not present. To restore a saved configuration to be the current 
-  configuration:
-</p>
-
-<ol>
-  <li> Select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.update.manageConfiguration")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Help &gt; Software Updates &gt; Manage Configuration</b></a> to 
-    open the Manage Configuration dialog. </li>
-  <li>In the Product Configuration view, click the Installation History icon and 
-    select the desired configuration. Click <b>Restore</b>.</li>
-  <li>Click <b>Yes</b> when asked to exit and restart the Workbench for the changes 
-    to take effect.</li>
-  <li>Expand the Current Configuration (and children) to confirm that the current 
-    configuration now matches the configuration saved earlier.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-25.htm">Features</a>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-33.htm">Inspecting the current configuration</a><br>
-<a href="tasks-37.htm">Controlling the Eclipse update policy</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm
deleted file mode 100644
index e483c32..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3e.htm
+++ /dev/null

@@ -1,122 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving and docking views</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Moving and docking views</H1>
-
-<p>To change the location of a view in the current perspective:
-</p>
-
-<ol>
-  <li>Drag the view by its title bar. Do not release the left
-    mouse button yet.</li>
-  <li>As you move the view around the Workbench, the mouse pointer
-    changes to one of the <i>drop cursors</i> shown in the table below. The drop
-    cursor indicates where the view will be docked if you release the left mouse
-    button. To see the drop cursor change, drag the view over the left, right,
-    top, or bottom border of another view or editor. You may also drag the view
-    <i>outside</i> of the Workbench area to turn it into a "Detached" view.</li>
-  <li>When the view is in the location that you want, relative to
-    the view or editor area underneath the drop cursor, release the left mouse
-    button.</li>
-  <li>(Optional) If you want to save your changes, select
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.savePerspective")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Window &gt; Save Perspective As...</b></a> from the main menu bar.</li>
-  <li>Note that a group of stacked views can be dragged using the empty space to
-    the right of the view tabs.</li>
-</ol>
-
-<p>You can also move a view by using the pop-up menu for the view. (Left-click
-on the icon at the left end of the view's title bar, or right-click anywhere
-else in the view's title bar). As well as moving the view this menu will provide
-sortcut options for turning a view into either a "Fast" or "Detached" view.
-</p>
-
-<TABLE BORDER="1" cellspacing="0" cellpadding="5">
-  <THEAD>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <th COLSPAN="1" valign="bottom" align="left" height="38"> Drop cursor </th>
-      <th COLSPAN="1" valign="bottom" align="left" height="38"> Where the view 
-        will be moved to </th>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <P CLASS="Para"> <img src="../images/drop_top_source.png" alt=" Up icon" border="0" > 
-        </P></TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> <P CLASS="Para"> 
-          Dock above: The view is docked above the view underneath the cursor.</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" align="center" height="38"> <P CLASS="Para"> 
-          <img src="../images/drop_bottom_source.png" alt="  Down icon" border="0" > 
-        </P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left" height="38"> <p CLASS="Para"> 
-          Dock below: The view is docked below the view underneath the cursor.</p> 
-      </TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" align="center" height="38"> <P CLASS="Para"><img align="texttop" border="0" src="../images/drop_right_source.png" alt="Right icon" > 
-        </P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left" height="38"> <p CLASS="Para"> 
-          Dock to the right: The view is docked to the right of the view underneath 
-          the cursor.</p></TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <img align="texttop" border="0" src="../images/drop_left_source.png" alt=" Left icon" > 
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> Dock to the left: 
-        The view is docked to the left of the view underneath the cursor. </TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <img align="texttop" border="0" src="../images/drop_stack.png" alt=" Stack views" > 
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> Stack: The view is 
-        docked as a Tab in the same pane as the view underneath the cursor. </TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <img align="texttop" border="0" src="../images/drop_offscreen_source.png" alt=" Tear off icon " > 
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> Detached: The view is 
-        detached from the Workbench window and is shown in its own separate window. </TD>
-    </TR>
-    <TR> 
-      <TD COLSPAN="1" align="center" height="38"> <img align="texttop" border="0" src="../images/drop_invalid_source.png" alt=" Restricted icon" > 
-      </TD>
-      <TD COLSPAN="1" valign="top" align="left" height="38"> Restricted: You cannot 
-        dock the view in this area. </TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-21a.htm">Detached views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-9l.htm">Detaching views</a><br>
-<a href="../gettingStarted/qs-39g.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm
deleted file mode 100644
index f05fc09..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3g.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Tiling editors</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Tiling editors</H1>
-
-<P>The Workbench allows you to have multiple files open in multiple editors. Unlike
-views, editors cannot be dragged outside the Workbench to create new windows.
-However, you can tile editor sessions within the editor area, in order to view
-source files side by side.
-</P>
-
-<ol>
-  <li>With two or more files open in the editor area, select one of the editor tabs.</li>
-  <li>Holding down the left mouse button, drag that editor over
-    the left, right, top or bottom border of the editor area. Notice that the
-    mouse pointer changes to a &quot;drop cursor&quot; that indicates where the
-    editor session will be moved when you release the mouse button.</li>
-  <li>(Optional) Drag the borders of the editor area or each
-    editor, to resize as desired.</li>
-</ol>
-
-<p>This is a similar operation to moving and docking views inside
-the Workbench, except that all editor sessions must be contained within the
-editor area.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-9.htm">Changing the placement of the tabs</a><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm
deleted file mode 100644
index 8c5af88..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-3h.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging tabbed views</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Rearranging tabbed views</H1>
-<p>In addition to dragging and dropping (docking) views inside the Workbench,
-you can rearrange the order of views within a tabbed notebook.
-</p>
-<ol>
-  <li>Click on the tab of the view that you want to move and drag
-    it to where you want it. A stack symbol
-	<img border="0" src="../images/drop_stack.png" alt="drop stack image" >
-	appears as you drag the view across other view tabs.</li>
-  <li>Release the mouse button when you have the view tab in the
-    desired location. The view that you selected is now moved.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3e.htm">Moving and docking views</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm
deleted file mode 100644
index 93e4816..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a project</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a project</H1>
-
-<P>To create a project:
-</P>
-
-<ol>
-  <li>On the main menu bar, click <b>File &gt; New Project</b>. The New Project 
-    wizard opens.</li>
-  <li>Select a category from the left column and then select the type of project to 
-    create from the right column. To assist in locating a particular wizard, the text field can be used to show only the wizards that match the entered text. Click <b>Next</b>.</li>
-  <li>In the <b>Project name</b> field, type a name for your new
-    project.</li>
-  <li>(Optional) The project that you create will map to a directory structure 
-    in the file system. The default file system location is displayed in the Location 
-    field. If you want to create the project and its contained resources in a 
-    different location, clear the <b>Use default location</b> checkbox and specify 
-    the new location.</li>
-  <li>If you want the new project to be dependent on one or more other projects, 
-    click <b> Next</b> and select the projects to be referenced.</li>
-  <li>Click <b>Finish</b>. The new project is listed in one of the navigation views.</li>
-</ol>
-
-<p><em>Tip:</em> The <b>General &gt; Perspectives &gt;</b> preference page
-allows you to specify the perspective behavior when a new project is created.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm
deleted file mode 100644
index 8fea953..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-42b.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting projects</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting projects</H1>
-
-<P>To delete a project and remove its contents from the file system:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Delete</b> on the pop-up menu.</li>
-  <li>In the dialog which opens select <b>Also delete contents under ...</b>.</li>
-  <li>Click <b>Yes</b>.</li>
-</ol>
-
-<P>To delete a project from the workspace without removing its contents from the
-file system:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Delete</b> on the pop-up menu.</li>
-  <li>In the dialog which opens select <b>Do not delete contents</b>.</li>
-  <li>Click <b>Yes</b>.</li>
-</ol>
-
-<p CLASS="Para"><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-47.htm">Closing projects</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm
deleted file mode 100644
index 6e12b5b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-43.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a folder</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a folder</H1>
-
-<P>To create a new folder:
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the project or folder
-    where you want to create the new folder.</li>
-  <li>From the pop-up menu, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.folder)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>New &gt; Folder</b></a>.</li>
-  <li>Enter the name of the new folder and click <b>Finish</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm
deleted file mode 100644
index ba72e68..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-44.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating a file</H1>
-
-<P>To create a file:
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the project or folder
-    where you want to create the new file.</li>
-  <li>From the pop-up menu, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.file)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>New &gt; File</b></a>.</li>
-  <li>Specify the name of the file, including the file extension (for
-    example, newfile.txt).</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-
-<p>The file opens in the editor associated with its type.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources<br></a>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm
deleted file mode 100644
index 0c67f91..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-45.htm
+++ /dev/null

@@ -1,92 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating linked resources</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating linked resources</H1>
-<p>
-Folders and files can be linked to locations in the file system
-outside of the project's location.  These special folders and files are called 
-<a href="../concepts/concepts-13.htm">linked resources</a>.
-</p>
-
-<P>To create a linked folder:
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the project or folder
-    where you want to create the linked folder.</li>
-  <li>From the pop-up menu, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.folder)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>New &gt; Folder</b></a>.</li>
-  <li>Specify the name of the folder as it will appear in the workbench.  This 
-  name can be different from the name of the folder in the file system.</li>
-  <li>Click <b>Advanced</b>.</li>
-  <li>Check <b>Link to folder in the file system</b>.</li>
-  <li>Enter a file system path, or click <b>Browse</b> to select a folder in the file system.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-
-<P>To create a linked file, follow the same steps as above, except choose
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.file)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>New &gt; File</b></a> instead of
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.newWizard(newWizardId=org.eclipse.ui.wizards.new.folder)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>New &gt; Folder</b></a> in the context menu. </P>
-<P>Linked resource locations can also be specified relative to a variable.  This makes
-it easier to share projects containing linked resources with other team members,
-since it avoids hard-coded absolute file system paths that may vary from one
-machine to the next.
-</P>
-<P>
-To define a linked resource relative to a path variable, do the following after step 5
-above:
-</P>
-<ol start="6">
-  <li>Click the <b>Variables</b> button.</li>
-  <li>In the resulting dialog, select an existing path variable or create a new one.</li>
-  <li>If the chosen variable defines the exact path of the linked resource, click <b>OK</b>.
-  Otherwise, click <b>Extend</b> to specify a file or folder below the location described
-  by the path variable, then click <b>OK</b>.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-<p><em>Tip:</em> The 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Workspace &gt; Linked Resources</b></a>
-preference page also allows you to define path variables. 
-</p>
-<P>Note that, once you create a linked resource you will not be able to change
-the link target path that you entered in step 6. or 8. above.</P>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</P>
-
-<P><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-</P>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-14b.htm">Linked resources</a> 
-<br><a href="../reference/ref-38.htm">New Folder wizard</a> 
-<br><a href="../reference/ref-39.htm">New File wizard</a> 
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm
deleted file mode 100644
index b01e8aa..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening files for editing</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Opening files for editing</H1>
-<p>
-You can launch an editor for a given file in several ways.
-</p>
-
-<ul>
-  <li>By right-clicking the file in one of the navigation views and then
-    selecting <b> Open</b> from the pop-up menu.</li>
-  <li>By double-clicking the file in one of the navigation views.</li>
-  <li>By double-clicking a bookmark that is associated with that file, in the 
-    Bookmarks view.</li>
-  <li>By double-clicking an error or warning, or task record that is associated 
-    with that file, in the Problems view.</li>
-</ul>
-
-<p>All of the above alternatives open the file in the default
-editor for that type of file. To open it in a different editor, select
-<b>Open With</b> from the file's pop-up menu.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-6a.htm">External editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-51.xhtml">Associating editors with file types</a><br>
-<a href="tasks-52.htm">Editing files outside the Workbench</a><br>
-  <a href="tasks-18.htm">Linking the Project Explorer view to the active editor</a><br>
-<a href="tasks-3g.htm">Tiling editors</a><br>
-<a href="tasks-9.htm">Changing the placement of editor tabs</a><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm
deleted file mode 100644
index b997f0b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-46ag.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Finding a resource quickly</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Finding a resource quickly</H1>
-
-<P>To navigate to a particular resource in a view such as the Project Explorer view: 
-</P>
-
-<ol>
-  <li>From <b>Navigate</b> menu, select <b>Go To &gt; Resource</b>.</li>
-  <li>In the window that opens, start typing the name of the
-    resource in the <b>Pattern</b> field. As you type the file name, the system
-    offers a list of possible matches, based on what you have entered so far.</li>
-  <li>Select the resource that you want from the <b>Matching
-    Resources</b> list, and click <b>OK</b>.</li>
-</ol>
-
-<p>The view displays the selected resource.</p>
-<p>
-If you want to open a particular resource in an editor rather than select
-it in a view, you can use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.navigate.openResource")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Navigate &gt; Open Resource</b></a> action.
-This action presents the same dialog as the <b>Go To &gt; Resource</b> action,
-but immediately opens the matching resource for editing.
-</p>
-<p>You can also do a contextual search for character strings contained within 
-  files in the Workbench. See the links to related tasks below. </p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/cnav.htm">Project Explorer view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-84.htm">Searching for text within a file</a><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Project Explorer view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm
deleted file mode 100644
index 0f9a2f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-47.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Closing projects</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Closing projects</H1>
-
-<P>When a project is closed, it can no longer be changed in the Workbench and 
-its resources no longer appear in the Workbench, but they do still reside on 
-the local file system. Closed projects require less memory. Also, since they 
-are not examined during builds, closing a project can improve build time.
-</P>
-
-<P>To close a project:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Close Project</b> on the pop-up menu.</li>
-</ol>
-
-<P>To re-open the project:
-</P>
-
-<ol>
-  <li>Select the project in one of the navigation views.</li>
-  <li>Click <b>Open Project</b> on the pop-up menu.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-42b.htm">Deleting projects</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm
deleted file mode 100644
index da687f7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-48b.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Showing or hiding files in the Project Explorer view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Showing or hiding files in the Project Explorer view</H1>
-
-<P>You can choose to hide system files or generated class files in one of the navigation views. (System files are those that have only a file extension but no file
-name, for example .classpath.)</P>
-
-<ol>
-  <li>On the toolbar for the Project Explorer, click the <b>Menu</b> 
-    button <img src="../images/ref-79.png" alt="Menu button" border="0" >
-	to open the drop-down menu of display options.</li>
-  <li>Select <b>Customize View..,</b>.</li>
-  <li>In the dialog box that opens, select the Filters tab and then select the checkboxes for the
-    types of files that you want to hide.</li>
-</ol>
-<P>In addition, you can restrict the displayed files to a working set.</P>
-<ol>
-  <li>On the toolbar for the Project Explorer, click the <b>Menu</b> 
-    button <IMG src="../images/ref-79.png" alt="Menu button" border="0" >
-	to open the drop-down menu of display options.</li>
-  <li>Choose <B>Select Working Set...</B></li>
-  <li>Select an existing working set from the list or create a new one by selecting
-  <B>New...</B></li>
-</ol>
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/concepts-17.htm">Resource hierarchies</a><br>
-<a href="../concepts/cnav.htm">Project Explorer view</a><br>
-<a href="../concepts/cworkset.htm">Working sets</a>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-49.htm">Viewing resource properties</a><br>
-<a href="tasks-46ag.htm">Finding a resource quickly</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm
deleted file mode 100644
index 4666cc6..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-49.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Viewing resource properties</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Viewing resource properties</H1>
-
-<P>To display the various properties of a Workbench resource:
-</P>
-
-<ol>
-  <li>Right-click the resource in one of the navigation views.</li>
-  <li>Select <b>Properties</b> from the pop-up menu.</li>
-</ol>
-
-<P>The kinds of properties that are displayed depend on the specific resource 
-you have selected and the features and plug-in that are installed in the Workbench.
-</P> <P><em>Tip:</em> When the resource is selected in one of the navigation views you can also see basic properties for a resource by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Properties</b></a>.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-27.htm">Project Explorer view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-48b.htm">Showing or hiding files in the Project Explorer view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml
deleted file mode 100644
index 3c4fb13..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-51.xhtml
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Associating editors with file types</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1>Associating editors with file types</h1>
-<p>To associate editors with various file types in the Workbench:</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileEditors)&quot;)">
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"/>
-  <b>General &gt; Editors &gt; File Associations</b></a> preference page.</li>
-  <li>Select the file type from the <b>File types</b> list, or click <b>Add</b>
-    to add a type that is not already on the list.</li>
-  <li>In the <b>Associated editors</b> list, select the editor that you want 
-    to associate with that file type. To add an editor to the list: 
-    <ol type="a">
-      <li>Click <b>Add</b>. The Editor Selection dialog box opens.</li>
-      <li>Select <b>Internal Editors</b> or <b>External Programs</b>, depending on
-          whether the editor that you want was built for the Workbench or runs outside the Workbench.</li>
-      <li>If you select <b>External Programs</b>, you can click the Browse button to
-          browse the file system.</li>
-      <li>Select the editor from the list and click <b>OK</b>.</li>
-    </ol>
-  </li>
-  <li>Click <b> OK</b> to finish associating the editor with the selected file type.</li>
-</ol>
-
-<p>When you associate an internal editor with a file type, that editor opens in
-the editor area of the Workbench. For example,  if you double-click a file in the
-Project Explorer or an entry in the Bookmarks or Tasks view it opens in the editor area.
-</p>
-
-<p filter="ws=win32"><img border="0" src="../images/win_only.png" alt="Windows only" />
-Editors that support OLE document mode can also run in the editor area of the Workbench.
-</p>
-
-<p><b>Tip</b>: You can choose to override your default editor selections by
-selecting <b>Open With</b> from the pop-up menu for any resource in one of the navigation views.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" /><br />
-<a href="../concepts/concepts-6.htm">Editors</a><br />
-<a href="../concepts/concepts-6a.htm">External editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" /><br />
-<a href="tasks-46.htm">Opening files for editing</a><br />
-<a href="tasks-52.htm">Editing files outside the Workbench</a><br />
-  <a href="tasks-18.htm">Linking the Project Explorer view to the active editor</a> </p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm
deleted file mode 100644
index 7ecb84d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-52.htm
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Editing files outside the Workbench</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Editing files outside the Workbench</H1>
-<P>To edit a Workbench resource outside the Workbench:</P>
-<ol>
-  <li>Navigate in the file system to the Workbench's installation directory. Go 
-    into the workspace directory and open the file that you want to edit with 
-    the external editor.</li>
-  <li>Edit the file as needed. Save and close it as usual.</li>
-  <li><em>Important</em>: Go back to the Workbench, right-click the edited file 
-    in one of the navigation views, and select <b>Refresh</b> from the pop-up 
-    menu. The Workbench will perform any necessary build or update operations 
-    to process the changes that you made outside the Workbench.</li>
-</ol>
-<p><em>Tip</em>: If you work with external editors regularly, you may want to 
-  enable auto-refresh. This can be done by opening the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Workspace</b></a> preference page, and checking 
-  the <strong>Refresh automatically</strong> option. When this option is enabled, 
-  any external changes will be automatically discovered by the Workbench. Depending 
-  on the platform this may not happen immediately.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-6.htm">Editors</a><br>
-<a href="../concepts/concepts-6a.htm">External editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-51.xhtml">Associating editors with file types</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml
deleted file mode 100644
index e593db7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-53.xhtml
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Importing</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1 class="Head">Importing</h1>
-
-<p>You can import files into the Workbench in several ways, depending on your operating system:
-</p>
-
-<ul>
-  <li>By using the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.file.import&quot;)">
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"/>
-  Import wizard</a>.</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" />
-    By dragging files or folders from the file system to one of the navigation views</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" />
-    By copying files or folders from the file system and pasting them into one of the navigation views</li>
-</ul>
-
-<p>See the related tasks section for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" /><br />
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" /><br />
-<a href="tasks-55.htm">Importing resources from the file system</a><br />
-<a href="tasks-55bg.htm">Importing resources from an Archive File</a><br />
-<a href="tasks-57.xhtml">Exporting</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm
deleted file mode 100644
index b8ac8ab..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing resources from the file system</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Importing resources from the file system</h1>
-
-<p>You can use the Import Wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.ui.wizards.import.FileSystem)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-import resources from the local file system into an existing project</a>.
-</p>
-
-<ol>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>File &gt; Import...</b></a>. The Import wizard opens.</li>
-  <li>Select <b>General &gt; File System</b> and click <b>Next</b>.</li>
-  <li>Click the <b>Browse</b> button on the next page of the wizard to select
-    the directories from which you would like to add the resources.</li>
-  <li>In the import selection panes, use the following methods to select exactly 
-    the resources you want to add: 
-    <UL>
-      <LI>Expand the hierarchies in the left pane and select or clear the checkboxes 
-        that represent the folders in the selected directory. Then in the right 
-        pane, select or clear checkboxes for individual files.</LI>
-      <LI>Click <b>Filter Types</b> to filter the current selection for files 
-        of a specific type.</LI>
-      <LI>Click <b>Select All</b> to select all resources in the directory, 
-        then go through and deselect the ones that you do not want to add.</LI>
-      <LI>Click <b>Deselect All</b> to deselect all resources in the directory, 
-        then go through and choose individual resources to add.</LI>
-    </UL></li>
-  <li>Specify the Workbench project or folder that will be the import destination.</li>
-  <li>When you have finished specifying your import options, click <b>Finish.</b></li>
-</ol>
-
-<P><em>Tip:</em> You can also import folders and files by dragging them from the 
-  file system and dropping them into one of the navigation views, or by copying 
-  and pasting. </P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-70.htm">Import wizard</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-importproject.htm">Importing existing projects</a><br>
-<a href="tasks-55bg.htm">Importing resources from a ZIP File</a><br>
-<a href="tasks-57.xhtml">Exporting</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm
deleted file mode 100644
index cf8daf7..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-55bg.htm
+++ /dev/null

@@ -1,66 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing resources from an Archive file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Importing resources from an Archive file</h1>
-
-<P>You can use the Import wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.ui.wizards.import.ZipFile)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>extract files from an archive file into the Workbench</b></a>. </P>
-
-<ol>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>File &gt; Import...</b></a>. The Import wizard opens.</li>
-  <li>Select <b>General &gt; Archive File</b> and click <b>Next</b>.</li>
-  <li>Click the <b>Browse</b> button on the next page of the wizard, to select 
-    the archive files that contain the files you want to extract and import into 
-    the Workbench.</li>
-  <li>In the import selection panes, use the following methods to select exactly
-    the resources you want to add:
-    <ul>
-      <li>Expand the hierarchies in the left pane and select or
-        clear the checkboxes that represent the folders in the selected
-        directory. Then in the right pane, select or clear checkboxes for
-        individual files.</li>
-      <li>Click <b>Filter Types</b> to filter the current selection
-        for files of a specific type.</li>
-      <li>Click <b>Select All </b>to select all resources in the
-        directory, then go through and deselect the ones that you do not want to
-        add.</li>
-      <li>Click <b>Deselect All</b> to deselect all resources in
-        the directory, then go through and choose individual resources to add.</li>
-    </ul></li>
-  <li>Specify the Workbench project or folder that will be the import destination.</li>
-  <li>When you have finished specifying your import options. click <b>Finish.</b></li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-70.htm">Import wizard</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-importproject.htm">Importing existing projects</a><br>
-<a href="tasks-55.htm">Importing resources from the file system</a><br>
-<a href="tasks-57.xhtml">Exporting</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml b/bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml
deleted file mode 100644
index ba56acd..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-57.xhtml
+++ /dev/null

@@ -1,48 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." />
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css" />
-<title>Exporting</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body bgcolor="#ffffff">
-<h1 class="Head">Exporting</h1>
-
-<p>You can export files from the Workbench in several ways, depending on your operating system:
-</p>
-
-<ul>
-  <li>By using the
-  <a class="command-link" href="javascript:executeCommand(&quot;org.eclipse.ui.file.export&quot;)">
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png"/>
-  Export wizard</a>.</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" /> By
-    dragging files or folders from one of the navigation views to the file system.</li>
-  <li filter="ws=win32"><img src="../images/win_only.png" alt="For Windows:" border="0" /> By
-    copying files or folders from one of the navigation views and pasting them into the file
-    system.</li>
-</ul>
-
-<p>See the related tasks section for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" /><br />
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" /><br />
-<a href="tasks-59.htm">Exporting resources to the file system</a><br />
-  <a href="tasks-59ag.htm">Exporting resources to an Archive File</a><br />
-<a href="tasks-53.xhtml">Importing</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm
deleted file mode 100644
index 3ba293e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Exporting resources to the file system</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Exporting resources to the file system</H1>
-
-<P>You can use the Export wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.ui.wizards.export.FileSystem)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-export resources from the Workbench to the file system</a>.
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to export.</li>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>File &gt; Export...</b></a>. The Export wizard opens.</li>
-  <li>Select <b>General &gt; File System</b> and click <b>Next</b>.</li>
-  <li>By default, the resources that you selected will be exported, along with
-    all their children. Optionally, use the checkboxes in the left and right
-    panes to select the set of resources to export, and use push buttons such as
-    <b>Select Types</b> to filter the types of files that you want to export.</li>
-  <li>Click the <b>Browse</b> button on the next page of the wizard, to select
-    the directory you would like to export the resources to.</li>
-  <li>Specify the directory in the file system that will be the export destination.</li>
-  <li>Click <b>Finish</b>.</li>
-</ol>
-
-<p><em>Tip:</em> You can also export folders and files by dragging them from
-one of the navigation views to the file system and dropping them in the file system, or
-by copy and paste.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-53.xhtml">Importing</a><br>
-<a href="tasks-59ag.htm">Exporting resources to a ZIP File</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm
deleted file mode 100644
index 3350d98..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-59ag.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Exporting resources to an Archive file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Exporting resources to an Archive file</h1>
-
-<p>You can use the Export wizard to
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export(exportWizardId=org.eclipse.ui.wizards.export.ZipFile)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-export resources from the Workbench to an archive file in the file system</a>.
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to export.</li>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>File &gt; Export...</b></a>. The Export wizard opens.</li>
-  <li>Select <b>General &gt; Archive File</b> and click <b>Next</b>.</li>
-  <li>By default, the resources that you selected will be exported along with 
-    their children. Optionally, use the checkboxes in the left and right panes 
-    to select the set of resources to export, and use push buttons such as <b>Select 
-    Types</b> to filter the types of files that you want to export.</li>
-  <li>Specify the path and name of the archive file into which you want to export 
-    the selected resources.</li>
-  <li>Click <b>Finish.</b></li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-59.htm">Exporting resources to the file system</a><br>
-<a href="tasks-53.xhtml">Importing</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm
deleted file mode 100644
index 4b2c919..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Moving resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Moving resources</h1>
-
-<P>You can move resources from one Workbench location to another (for example,
-from one project to another project).
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to move.</li>
-  <li>From the pop-up menu, select <b>Move</b>.</li>
-  <li>In the Folder Selection window, select the project or folder
-    where you want to move the resources to and click <b>OK</b>.</li>
-</ol>
-
-<p><em>Tip:</em> You can also move resources by dragging them from the original
-location to the new location in one of the navigation views.
-</p>
-<P>Moving a linked resource always moves the link and not the resource that it is 
-linked to. E.g., when moving a linked folder the folder contents is not moved on
-the file system.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Project Explorer view</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46ag.htm">Finding a resource quickly</a><br>
-<a href="tasks-63cg.htm">Copying resources</a><br>
-<a href="tasks-66.htm">Renaming resources</a><br>
-<a href="tasks-67.htm">Deleting resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm
deleted file mode 100644
index 4571e09..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-63cg.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Copying resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Copying resources</H1>
-
-<P>You can copy resources from one Workbench location to another (for example, 
-  from one project to another project).
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to copy.</li>
-  <li>From the pop-up menu, select <b>Copy</b>.</li>
-  <li>In one of the navigation views, select the project or folder where you want to copy 
-    the resources to.</li>
-  <li>From the pop-up menu, select <b>Paste</b>.</li>
-</ol>
-
-<P><em>Tip:</em> You can also copy resources by holding down the Ctrl key and
-dragging them from the original location to the new location in one of the navigation views.
-</P>
-<P>Copying a linked resource always copies the link and not the resource that it is 
-linked to. E.g., when copying a linked folder the folder contents is not copied on
-the file system. Instead, a new linked folder is created linking to the same location 
-on the file system.
-</P>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Project Explorer view</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-63.htm">Moving resources</a><br>
-<a href="tasks-66.htm">Renaming resources</a><br>
-<a href="tasks-67.htm">Deleting resources</a>
-</p>
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm
deleted file mode 100644
index b189be5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-66.htm
+++ /dev/null

@@ -1,40 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Renaming resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Renaming resources</H1>
-
-<P>You can rename Workbench resources using the Rename command on the context 
-  menu in one of the navigation views.
-</P>
-
-<ol>
-  <li>In one of the navigation views, right-click the resource that you want to rename.</li>
-  <li>From the pop-up menu, select <b>Rename</b>.</li>
-  <li>Type the new name for the resource.</li>
-  <li>Hit the return key.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Project Explorer view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-49.htm">Viewing resource properties</a><br>
-<a href="tasks-63.htm">Moving resources</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm
deleted file mode 100644
index a927601..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-67.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting resources</H1>
-
-<p>To delete a resource from the Workbench:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resources that you want to
-    delete. (Hold down the Ctrl key to select more than one resource.)</li>
-  <li>Press the Delete key.</li>
-  <li>Click <b>Yes</b> in the dialog which appears.</li>
-</ol>
-
-<p><em>Tip:</em> You can achieve the same result by selecting <b>Delete</b>
-from the pop-up menu.
-</p>
-<p>
-Deleting resources from the workspace will also delete the corresponding files and/or
-folders from the local file system.  The only exception is linked resources, which are
-not removed from the file system when you delete the link in the workspace.  However,
-deleting child resources of linked folders <em>will</em> delete those resources
-from the local file system.
-</p>
-<p>
-In most cases it is possible to undo a resource delete, which will restore
-deleted files from the local history.  The files can also be restored manually from
-the history. See the related
-tasks for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-12.htm">Resources</a><br>
-<a href="../concepts/cnav.htm">Project Explorer view</a><br>
-<a href="../concepts/concepts-13.htm">Linked resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-42b.htm">Deleting projects</a><br>
-<a href="tasks-42.htm">Creating a project</a><br>
-<a href="tasks-43.htm">Creating a folder</a><br>
-<a href="tasks-44.htm">Creating a file</a><br>
-<a href="tasks-45.htm">Creating linked resources</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm
deleted file mode 100644
index 2c05799..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68.htm
+++ /dev/null

@@ -1,97 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing resources</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Comparing resources</H1>
-
-<p>When a comparison is performed, comparison 
-editors appear in the editor area. The differences between files are highlighted
-in the comparison editors, allowing you to browse and copy changes between the compared 
-resources.
-</p>
-
-<p>To compare resources:
-</p>
-
-<ol>
-  <li>Select one or more resources in one of the navigation views.</li>
-  <li>From the resource's pop-up menu, select <b>Compare With</b>.</li>
-</ol>
-
-<p>A tool for viewing differences is opened in the editor area.
-</p>
-
-<p>Here are some of the comparisons that you can perform.&nbsp;
-</p>
-
-<dl>
-  <dt><b>Compare With &gt; Latest from HEAD</b></dt>
-  <dd>compares the selected resource with the version of the same resource that 
-    is currently committed to the active branch. This option is available for 
-    CVS. This ,or a similar option, may or may not be available for other repository 
-    types.</dd>
-  <dt><b>Compare With &gt; Another Branch or Version</b></dt>
-  <dd>compares the selected resource with a version that has been committed to 
-    the repository or to the latest version in a particular branch. This requires 
-    you to choose a version of the resource or a branch from a list. This option 
-    is available for CVS. This, or a similar option, may or may not be available 
-    for other repository types.</dd>
-  <dt><b>Compare With &gt; Each Other</b></dt>
-  <dd>compares two or three selected resources with each other</dd>
-  <dt><b>Compare With &gt; History...</b></dt>
-  <dd>compares the selected resource with a version of the same resource that 
-    was committed to the active branch. This action will open the History view in
-    <em>compare mode</em>. You will then be able to choose which revision you wish to compare 
-    by double clicking on a revision in the History view. This option is available for CVS. This, or a 
-    similar option, may or may not be available for other repository types.</dd>
-  <dt><b>Compare With &gt; Local History</b></dt>
-  <dd>compares the selected resource to one that is in the local history, which 
-    is maintained when you save changes. (<em>Tip:</em> to configure the size 
-    and depth of your local history, use the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>General &gt; Workspace &gt; Local History</b></a> preference page.)</dd>
-</dl>
-
-<p><em>Tip:</em> You can customize the behavior of the comparison editor with the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.compare.internal.ComparePreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Compare/Patch</b></a> preference page.
-  You can select to &quot;synchronize scrolling&quot; of the pane contents, as well 
-  as setting options for showing conflicts with other team members and changing 
-  the default font.</p>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-17a.htm">Local history</a></p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a><br>
-<a href="tasks-101.htm">Comparing resources with repository versions</a><br>
-<a href="tasks-68bg.htm">Understanding the comparison</a><br>
-<a href="tasks-68c.htm">Working with patches</a><br>
-<a href="tasks-3g.htm">Tiling editors</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-<br><a href="../reference/ref-33.htm">CVS Synchronize view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm
deleted file mode 100644
index c30df31..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68b.htm
+++ /dev/null

@@ -1,192 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting preferences for comparing files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Setting preferences for comparing files</H1>
-
-<P>When you select to compare or synchronize two or more resources in the
-Workbench, one or more comparison editors usually open. To customize how these
-editors behave:
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.compare.internal.ComparePreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Compare/Patch</b></a> preference page.</li>
-  <li>Set your preferences and click <b>OK</b>.</li>
-</ol>
-
-<p CLASS="Para">You can configure the following options on the <b>General</b> tab.
-</p>
-
-<TABLE BORDER="1" cellspacing="0" width="100%">
-  <THEAD>
-    <TR> 
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH ROWSPAN="1" COLSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Open structure compare automatically</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Makes an additional information area visible which shows differences 
-          in the underlying structure of the resources being compared. This information 
-          may not be available for all comparisons.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-	<TR> 
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"><P CLASS="Para">
-		Show structure compare in Outline view when possible</P></TD>
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-		If this option is on, structure compare will be displayed in the Outline
-		view whenever it is possible.</P></TD>
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-		Off</P></TD>
-	</TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Show additional compare information in the status line</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Causes the status line to display additional context information about 
-          the comparison.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Ignore white space</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">Causes 
-          the comparison to ignore differences which are whitespace characters 
-          (spaces, tabs, etc.). Also causes differences in line terminators ( 
-          LF versus CRLF) to be ignored.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Automatically save dirty editors before patching</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-      	  This option controls whether any unsaved changes are automatically saved before
-      	  a patch is applied.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-  </TBODY>
-</TABLE>
-
-<p CLASS="Para">You can configure the following options in the <b>Text Compare</b> tab.
-</p>
-
-<TABLE BORDER="1" cellspacing="0" width="100%">
-  <THEAD>
-    <TR> 
-      <TH width="122" COLSPAN="1" ROWSPAN="1"> <P CLASS="Para"> Option</P></TH>
-      <TH width="327" COLSPAN="1" ROWSPAN="1"> <P CLASS="Para"> Description</P></TH>
-      <TH width="53" COLSPAN="1" ROWSPAN="1"> <P CLASS="Para"> Default</P></TH>
-    </TR>
-  </THEAD>
-  <TBODY>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Synchronize scrolling between panes in compare viewers</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          The two compare viewers will &quot;lock scroll&quot; along with one 
-          another in order to keep identical and corresponding portions of the 
-          code in each pane side by side.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para"> Initially show ancestor pane</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">Sometimes you may want to compare two versions of a resource with
-the previous version from which they were both derived. This is called their <i>common ancestor</i>,
-and it appears in its own comparison pane during a three way comparison.</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Off</P>
-</TD>
-</TR>
-   <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Show pseudo conflicts</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Displays conflicts that occur when two developers make the same change, 
-          for example when both add or remove the same line of code.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Off</P></TD>
-    </TR>
-    <TR> 
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Connect ranges with single line</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          Controls whether differing ranges are visually connected by a single
-          line or a range delimited by two lines.</P></TD>
-      <TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para"> 
-          On</P></TD>
-    </TR>
-	<TR> 
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-		Highlight individual changes</P></TD>
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-		Controls whether the individual changes inside conflicts are highlighted
-		.</P></TD>
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-		On</P></TD>
-	</TR>
-	<TR>
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-		When the end/beginning is reached while navigating an element</P></TD>
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-		Use this option to configure what occurs when
-		the end/beginning is reached while navigating an element. The options are:</P>
-		<ul>
-			<li>Prompt</li>
-			<li>Loop back to the beginning/end</li>
-			<li>Go to the next/previous element</li>
-		</ul>
-		</TD>
-		<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left"> <P CLASS="Para">
-		Prompt</P></TD>
-	</TR>	
-  </TBODY>
-</TABLE>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-<br><a href="../reference/ref-11.htm">Compare/Patch preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm
deleted file mode 100644
index 0829c2f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68bg.htm
+++ /dev/null

@@ -1,82 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Understanding the comparison</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Understanding the comparison</H1>
-
-<p>If you compare two files (file1.txt and file2.txt), the following results
-are shown in the compare editor. The left side shows the contents of file1.txt and the right side
-shows the contents of file2.txt. The lines connecting the left and right panes
-indicate the differences between the files.
-</p>
-
-<p>You can double click on the editor tab to maximize the editor.
-</p>
-
-<p><img src="../images/Image80_compare_editor2.png" alt="Compare view" border="0" >
-</p>
-
-<p>Looking at the numbered changes in the above image:
-</p>
-
-<ul>
-  <li>Starting with the top line (in the left pane) we can see that the difference 
-    bar (in the area of the blue circle) indicates something is missing from the 
-    very top of the left file. If we follow the difference band (see #1) to the 
-    right file we can see that it contains &quot;This is line 1&quot; .</li>
-  <li>The next line &quot;This is line 2.&quot; is white indicating it matches 
-    the right file.</li>
-  <li>Moving onto the next line (colored in gray) we can see that the left file 
-    and right file have different contents for this line (see #2).Also, you can 
-    observe that a part of the line is highlighted. You can turn this option off 
-    on the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.compare.internal.ComparePreferencePage)")'>
-	<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-	<b>General &gt; Compare/Patch</b></a> preference page.</li>
-  <li>The next line (&quot;This is line 4&quot;) is once again in white, so we
-    can skip it, since the contents are the same in both.</li>
-  <li>The next line exists in the left file&nbsp; but since it is gray we follow 
-    its difference bar to the right (see #3) and notice that the right file does 
-    not contain the line (see red circle).</li>
-</ul>
-
-<p><em>Hint:</em> On the right-hand side of the comparison, to the right of the
-scrollbar, there is a column which shows a graphical representation of all differences 
-between the resources. You can click on any of the segments displayed there 
-to quickly scroll to that difference.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-17a.htm">Local history</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-68dg.htm">Merging changes in the Compare editor</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a><br>
-<a href="tasks-101.htm">Comparing resources with repository versions</a><br>
-<a href="tasks-3g.htm">Tiling editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-25.htm">Compare editor</a><br>
-<a href="../reference/ref-33.htm">CVS Workspace Synchronization</a><br>
-<a href="../reference/ref-11.htm">Compare/Patch preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm
deleted file mode 100644
index 0d004ce..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68c.htm
+++ /dev/null

@@ -1,176 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with patches</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Working with patches</H1>
-
-<p>Patches allow developers to share work without storing it in a repository. 
-  This is helpful when a developer wants to contribute to a project that is shared 
-  through a repository but does not have write access to the repository. In this 
-  situation, the developer can create a patch and either e-mail it to a developer 
-  who does have write access or attach it to a bug in the bug reporting system 
-  used by the project, depending on the process defined by the project. A developer 
-  that does have write access can then apply the patch to the project and commit 
-  the changes.</p>
-<H2>To create a patch from a CVS project:</H2>
-<ol>
-  <li>Select the resource that contains the modifications to be included in the 
-    patch. You can select resources that reside in multiple projects and at any level
-    as the Create Patch wizard, when run in its default mode, knows how to create a multi-project
-    patch. The patch should also be applied to the same file revisions that it 
-    is generated on so steps should be taken to ensure that the patch is applied 
-    to the same resource line-up (the easiest way to do this is to create the 
-    patch on top of a version).</li>
-  <li>From the popup menu, select <b>Team &gt; Create Patch...</b>. The Create 
-    Patch wizard will open.</li>
-  <li>Choose where the patch should be saved: 
-    <ol type="a">
-      <li><i>Save to Clipboard</i> - this will place the patch on the clipboard 
-        so it can be pasted into a text editor such as an e-mail program.</li>
-      <li><i>Save to File System</i> - this will place the patch in the specified 
-        file in the local file system</li>
-      <li><i>Save in Workspace</i> - this will place the patch in the specified 
-        file inside one of the existing workbench projects.</li>
-    </ol>For small patches it may be reasonable to transfer the patch using the clipboard 
-    but in most cases the local file system in the best option to use. </li>
-    <li>You can preview and fine tune your patch selection by expanding the Resources tree presented
-    in the Changes pane. Only those elements which are checked will be included in the patch. Click <b>Next</b> to configure how the patch is generated.</li>
-  <li>Choose how to configure the patch:
-    <ol type="a">
-      <li><i>Diff output format</i> - Allows the choice of several common diff 
-        output formats. <i>Unified</i> is the format used by many patch application 
-        tools including Eclipse. The format used in Context and Unified diffs allows to apply a patch, even though the line number mentioned 
-        for the hunk (patch terminology) is incorrect. In this case, when applying the patch, the algorithm scans both forwards and backwards
-        for a set of lines matching the context given for the hunk.</li>
-      <li><i>Patch Root</i> - Allows you to specify at what level your patch is rooted at. The choices
-      are <i>Workspace</i>, <i>Project</i> and <i>Selection</i>.<br>
-      <br><i>Workspace</i> allows you to include resources from multiple projects in your patch and is the <em>default</em> option. Workspace 
-      patches can be applied to any resource in the workspace - they contain enough information to allow the Apply Patch wizard
-      to figure out which resources need to be patched.<br>
-      <br><i>Project</i> patches are rooted at the project level - which means they can only contain resources from one project and must
-      be applied to the same project.<br>
-      <br><i>Selection</i> patches are rooted at whatever the selected resource is and must be applied to the same resource.
-   	</li>
-    </ol>
-  </li>
-  <li>Click <b>Finish</b>. </li>
-  <li>Transfer the patch as appropriate for the project being patched.</li>
-</ol>
-<H2>To apply a patch:</H2>
-<ol>
-  <li>Select the resource that the patch was generated on. This resource should 
-    contain the same file revisions as the line-up on which the patch was generated.</li>
-  <li>From the pop-up menu, select <b>Team &gt; Apply Patch...</b>. The Resource 
-    Patcher wizard will open.</li>
-  <li>Indicate where the patch is to be found:
-    <ol type="a">
-      <li><i>File</i> - the patch is in a file on the local file system. Either 
-        type in the full path to the file or use the <b>Browse...</b> button to 
-        find the file.</li>
-      <li><i>Clipboard</i> - the patch is on the clipboard. <b>Warning:</b> It 
-        is safer to use a file based patch. Line endings may not be handled properly 
-        if the clipboard is used and the patch was generated on a different platform 
-        (i.e. Linux vs. Windows).</li>
-       <li><i>Workspace</i> - the patch has been saved somewhere in the workspace.</li>
-    </ol> Click <b>Next</b> to see the effect of applying the patch.</li>
-  <li>
-  <b>Optional Step</b>: <i>this step only applies if you have a patch rooted at the project or selection level - workspace
-  rooted patches will automatically proceed to the Patch Preview Page.</i> In the Patch Target Specification page, you should
-  select the resource that is to act as the root of the patch.
-  </li>
-  <li>The patch preview page shows whether the patch could be successfully applied
-  to files in your workspace. The top pane shows the list of changes contained in your patch.
-  There are two types of entries in the top pane: file changes and unmatched patch segments 
-  (known as 'hunk' in patch terminology).
-  <ol type="a">
-  <li>If one of more of the patch segments can be automatically applied to the file, the file will be shown
-  with an incoming change indicator. You can inspect the change by double-clicking on the file.</li>
-  <li>If one or more hunks cannot be automatically applied, the hunk entries will appear as children of the
-  file in the top pane and a red exclamation mark indicates that there is a problem with a patch or hunk. 
-  You can inspect the hunk by double-clicking on it. You can then manually apply the hunk
-  from the right pane to the file on the left. Saving from the left pane will update the parent file entry in the top pane but
-  will not modify the file on disk. The file on disk is only modified when Finish is pressed.
-  In order to apply the full patch
-    successfully you will have to eliminate the problems (red exclamation marks) either by manually
-    applying the patch segments, by excluding the patch segment from the operation by 
-    selecting <strong>Remove</strong> from the 
-  context menu or by tweaking the options on this wizard page (see 'Options' below).
-  </li>
-  </ol>
-  </li>
-  <li>If all is well, click <b>Finish</b> to apply the patch. The workspace will 
-    now contain outgoing changes for each file modified by the patch.</li>
-</ol>
-
-
-<H3>Options for applying a patch</H3>
-
-  	For getting successful matches of your patch file you have the following options:
-   	<ol>
-   	
-   		<li>
-   			Go back to the first page of the Apply Patch wizard and
-   			select the correct resource to which the patch should be applied.
-   		</li>
-   	
-   	  	<li>
-   	  		If a common prefix of the path names stored in the patch file doesn't match
-   	  		the path names in you current workspace, you can <i>Ignore leading path name segments</i>.
-  		</li>
-
-   	  	<li>
-   	  		Use the <i>Ignore whitespace</i> button to make the matching process
-   	  		independent from whitespace differences between the patch file and files
-   	  		in your workspace. 
-  		</li>
-
-   	  	<li>
-   	  		Adjust the <i>Fuzz factor</i> (patch terminology). This factor indicates the amount of hunk context lines to ignore. 
-			If the Fuzz factor value is zero all lines need to match.
-			If the fuzz factor is greater than zero, for example 2, the first two context lines before the hunk and the last two context lines after the hunk are ignored. 
-			Click <b>Guess</b> to calculate the fuzz factor that allows the most hunks to be matched.
-  		</li>
-
-   	  	<li>
-   	  		Use the <i>Reverse patch</i> option for patch files that already have been applied to your
-   	  		workspace. This option is also useful to undo or redo a patch.
-  		</li>
-  		
-  		<li>
-  			For Workspace patches, you can select another project in your workspace
-  			to apply the patch changes to. To do this, select a project in the top pane and select <b>Move</b> from the context menu. This will launch a dialog with a list of all available projects in your
-  			workspace. Select a project and click <b>OK</b>; the patch changes will be applied to your selected project.
-  		</li>
-  		<li>
-  		Use the <i>Show Excluded</i> 
-  		option to show the hunks which you have already selected to not include in the patch.</li>
-
-   	</ol>
-
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm
deleted file mode 100644
index 1a5d518..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-68dg.htm
+++ /dev/null

@@ -1,69 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Merging changes in the compare editor</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Merging changes in the compare editor</H1>
-
-<p>The toolbar buttons in the compare editor allows you to merge changes from the left file to the
-right file and vice versa. There are four types of merges you can perform:
-</p>
-
-<ul>
-  <li>Copy All from Left to Right</li>
-  <li>Copy All from Right to Left</li>
-  <li>Copy Current Change from Left to Right</li>
-  <li>Copy Current Change from Right to Left</li>
-</ul>
-
-<p>The <b>Copy All from Left to Right</b> and <b>Copy All from Right to Left</b>
-actions completely replace the contents of one resource with the other resource.
-</p>
-
-<p>To merge a single change:
-</p>
-
-<ol>
-  <li>Select the highlighted difference that you want to merge.</li>
-  <li>Depending on what you want to do, click either the <b>Copy Current Change 
-    from Right to Left</b> or the <b>Copy Current Change from Left to Right</b> 
-    toolbar button. The selected text is copied from one file to the other.</li>
-  <li>Right click to get the resource's pop-up menu, and select <b>Save</b>.</li>
-</ol>
-
-<p>The image below gives an example of two files (file1.txt and file2.txt) compared.
-</p>
-
-<p><img src="../images/Image80_compare_editor.png" alt="Compare view" border="0" >
-</p>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-29.htm">Three way comparisons</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</P>
-
-<p><img src="../images/ngrelt.png" alt="Related tasks" border="0" ><br>
-<a href="tasks-68.htm">Comparing resources</a><br>
-<a href="tasks-68bg.htm">Understanding the comparison</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-68b.htm">Setting preferences for comparing files</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" >
-<br><a href="../reference/ref-25.htm">Compare editor</a>
-<br><a href="../reference/ref-33.htm">CVS Workspace Synchronization</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm
deleted file mode 100644
index 9b7e48b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-70.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Comparing resources with the local history</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Comparing resources with the local history</H1>
-<p>To compare an unmanaged Workbench resource with a state in the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resource that you want to compare with 
-    a local history state.</li>
-  <li>From the resource's pop-up menu, select <b>Compare With</b> &gt; <b>Local 
-    History</b>. The Compare with Local History page opens.</li>
-  <li>Select a state in the <b>Local History</b> list. The Text Compare editor opens.</li>
-  <li>Click the <b>Select Next Change</b> and <b>Select Previous Change</b> buttons 
-    to browse the changes made between the state in the local history and the 
-    Workbench resource.</li>
-  <li>Click <b>OK</b> when you are finished.</li>
-</ol>
-
-<p>To compare a Workbench resource that is managed by CVS with a state in the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resource that you want to compare with 
-    a local history state.</li>
-  <li>From the resource's pop-up menu, select <b>Compare With</b> &gt; <b>History...</b>. The History View opens.</li>
-  <li>Put the History View into <em>Local Revisions</em> mode by clicking on the Local Revisions toolbar button in the History View. 
-  This filters out all revisions except for Local History revisions.</li>
-  <li>Select a revision from the History View. The Text Compare editor opens.</li>
-  <li>Click the <b>Select Next Change</b> and <b>Select Previous Change</b> buttons 
-    to browse the changes made between the state in the local history and the 
-    Workbench resource.</li>
-  <li>Click <b>OK</b> when you are finished.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a><br>
-<a href="tasks-68.htm">Comparing resources</a>
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm
deleted file mode 100644
index 9fec341..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-73.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Building resources</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Building resources</H1>
-
-<p>There are a number of ways that resources in the Workbench can be built. The 
-scope of a build can be one or more selected projects, a working set, or the entire workspace. 
-</p>
-
-<p>A build will typically only operate on resources that have changed since
-the last build.  A clean build will discard all existing built state, causing the
-next build to operate on all resources within the scope of the build.</p>
-
-<p>Builds can be done automatically (each time resources are modified), or manually, 
-using a menu item or keyboard shortcut. See the Related tasks links for more details.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-75.htm">Performing builds manually</a><br>
-<a href="tasks-16.htm">Performing builds automatically</a><br>
-<a href="tasks-17.htm">Saving resources automatically before a manual build</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm
deleted file mode 100644
index 01f7d3d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-75.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Performing builds manually</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Performing builds manually</h1>
-
-<P>By default, builds are performed automatically when you save resources. If 
-  you need more control over when builds occur, you can disable automatic building 
-  and manually invoke builds. This is sometimes desirable in cases where you know 
-  building should wait until you finish a large set of changes. The disadvantage 
-  of manual building is that tasks generated to indicate build errors quickly 
-  become out of date until you build. In addition, it is very important that you 
-  remember to manually build before relying on build output (for example, before 
-  running your Java program).
-</P>
-
-<p><em>Note:</em> Some of the menu items described below are only available when 
-the automatic build preference is disabled (ensure
-<b>Project &gt; Build Automatically</b> is not checked).
-</p>
-
-<p>To build projects in the workspace select the projects and click <b>Project 
-  &gt; Build Project</b>. Alternatively, click <b>Project &gt; Build All</b> to
-  build all projects in the workspace. Both of these commands will search through
-  the projects and only build the resources that have changed since the last build.
-  To build all resources, even those that have not changed since the last build,
-  run <b>Project &gt; Clean...</b> before doing the build.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-22.htm">Builds</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-17.htm">Saving resources automatically before a manual build</a><br>
-<a href="tasks-14.htm">Changing build order</a><br>
-<a href="tasks-16.htm">Performing builds automatically</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm
deleted file mode 100644
index 7b9e0f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding line items in the Tasks view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Adding line items in the Tasks view</H1>
-
-<P>The Tasks view contains line items for system-generated problems, warnings, and
-errors. You can add your own entries to the table to build a list
-of to-do items, or tasks.
-</P>
-
-<ol>
-  <li>On the toolbar in the Tasks view, click the <b>New Task</b> button
-      <img src="../images/Image52_new_task.png"  alt="New Task button" border="0">.
-      The <b>New Task</b> dialog will open.</li>
-  <li>Type a brief description for the task in the <b>Description</b> field. 
-      The new task is assigned default priority and completed values. 
-      These values may also be modified within the <b>New Task</b> dialog.</li>
-  <li>Press <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/ctskview.htm">Tasks view</a><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-78.htm">Deleting tasks</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="tasks-79.htm">Filtering the Tasks view</a><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm
deleted file mode 100644
index 200d29a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-77b.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Associating a task with a resource</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<a NAME="elementId-1032839"></a>
-<a NAME="pgfId-1032844"></a>
-<h1>Associating a task with a resource</h1>
-
-<p>You can associate tasks with an editable resource, for instance
-to remind yourself to update a line of source code later.
-</p>
-
-<ol>
-  <li>In one of the navigation views, double-click the resource with which
-      you wish to associate the new task. The resource opens in the editor area.</li>
-  <li>Right-click in the gray border at the left of the editor
-      area, beside the line of text or source code against which you want to log
-      the new task.</li>
-  <li>On the pop-up menu, select <b>Add Task</b>.</li>
-  <li>When prompted, enter a brief description of the task.</li>
-</ol>
-
-<p>A new task icon appears in the border of the editor area, to
-the left of the line where you added the task. When you move the mouse pointer
-over the marker, the description of the task is displayed as a tooltip. The task
-is also added to the Tasks view. You can delete a task either by right-clicking
-its icon in the editor area and selecting <b>Remove Task</b>, or by pressing the 
-Delete key in the Tasks view.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/ctskview.htm">Tasks view</a><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-78.htm">Deleting tasks</a><br>
-<a href="tasks-79.htm">Filtering the Tasks view</a><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm
deleted file mode 100644
index a514879..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-78.htm
+++ /dev/null

@@ -1,41 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting tasks</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting tasks</H1>
-
-<P>You can delete associated tasks from the gray border at the left of the editor area.
-</P>
-
-<ol>
-  <li>In the marker bar in the editor area, locate the task marker that you want to delete.</li>
-  <li>From the marker's pop-up menu, select <b>Remove Task</b>.</li>
-  <li>The task marker disappears and the task is removed from the Tasks view.</li>
-</ol>
-
-<p>You can also delete one or more line items from the Tasks view
-by pressing the Delete key or by clicking the <b>Delete</b> button on the Tasks
-view toolbar, or from the pop-up menu.
-</p>
-
-<p><em>Tip:</em> To delete all completed tasks, right-click in the Tasks view and
-select <b>Delete Completed Tasks</b> from the pop-up menu.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm
deleted file mode 100644
index 53fcdd1..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-79.htm
+++ /dev/null

@@ -1,42 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Filtering the Tasks and Problems views</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Filtering the Tasks and Problems views</H1>
-
-<P>You can filter the tasks or problems that are displayed in the Tasks or Problems 
-  views. For example, you might wish to see only problems that have been logged 
-  by the Workbench, or tasks that you have logged as reminders to yourself. You 
-  can filter items according to which resource or group of resources they are 
-  associated with, by text string within the Description field, by problem severity, 
-  by task priority, or by task status. </P>
-<ol>
-  <li>On the toolbar of the Tasks or Problems view, click <b>Filter</b>.<img src="../images/Image400_filterbutton.png" alt="filter button" border="0">.</li>
-  <li>Select the radio buttons and checkboxes that correspond to
-      your filtering objectives.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a><br>
-<a href="tasks-78.htm">Deleting tasks</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm
deleted file mode 100644
index b469d6b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81.htm
+++ /dev/null

@@ -1,51 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a bookmark within a file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<a NAME="elementId-1001031"></a>
-<a NAME="pgfId-1001036"></a>
-<h1>Creating a bookmark within a file</h1>
-
-<p>The Workbench allows you to create bookmarks in files that you
-edit so that you can quickly reopen those files from the Bookmarks view
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>).
-</p>
-
-<ol>
-  <li>With the file open in an editor, right-click in the gray border at the left
-  of the editor area, next to the line of code or text that you want to bookmark.</li>
-  <li>Select <b>Add Bookmark </b>from the pop-up menu.</li>
-  <li>Notice that an icon for the bookmark now appears in the left
-    border of the editor area. A line is also added to the Bookmarks view.)</li>
-</ol>
-
-<p CLASS="Head">You can reopen the file for editing at any time by double-clicking 
-  the bookmark in the Bookmarks view. </p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-82.htm">Deleting a Bookmark</a><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm
deleted file mode 100644
index 5954dcb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-81b.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a bookmark for an entire file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<a NAME="elementId-1001031"></a>
-<a NAME="pgfId-1001036"></a>
-
-<h1>Creating a bookmark for an entire file</h1>
-
-<p>You can bookmark individual files in the Workbench, in order to open them
-quickly from the Bookmarks view
-(<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>)
-later.
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the file that you want to
-    add to your list of bookmarks.</li>
-  <li>From the main Workbench menu select <strong>Edit &gt; Add Bookmark</strong>.</li>
-</ol>
-
-<p>At any time, you can open the bookmarked file for editing by
-double-clicking the bookmark in the Bookmarks view.
-</p>
-
-<p>You can also create bookmarks for specific lines of text or
-source code or within a file. See the list of related topics below.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a><br>
-<a href="tasks-82.htm">Deleting a Bookmark</a><br>
-<a href="tasks-77.htm">Adding line items in the Tasks view</a><br>
-<a href="tasks-77b.htm">Associating a task with a resource</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm
deleted file mode 100644
index bb2b2a6..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-82.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting a bookmark</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting a bookmark</H1>
-
-<p>To delete any bookmark:
-</p>
-
-<ol>
-  <li>Open the Bookmarks view
-  (<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.BookmarkView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Show View &gt; Other... &gt; General &gt; Bookmarks</b></a>).</li>
-  <li>Right-click the bookmark that you want to delete and select <b>Delete</b>
-    from the pop-up menu.</li>
-</ol>
-
-<p>If you have added bookmarks for specific lines within a source
-file, you can also delete them while editing the file by right-clicking the
-bookmark icon in the editor area.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/cbookmrk.htm">Bookmarks</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-81b.htm">Creating a bookmark for an entire file</a><br>
-<a href="tasks-81.htm">Creating a bookmark within a file</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm
deleted file mode 100644
index c1a90d6..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Searching for text within a file</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<h1>Searching for text within a file</h1>
-
-<p>The <b>Go To</b> selection in the pop-up menu for one of the navigation views allows you
-to quickly find a resource in the Workbench by searching resource <i>names</i>.
-</p>
-
-<p>You can also do contextual searches for information that is contained <i>inside</i>
-files in the Workbench. To find all files that contain a particular string of characters:
-</p>
-
-<ol>
-  <li>On the main toolbar, click the 
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.search.ui.openSearchDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Search</b></a> button <img src="../images/Image50_search.png"  alt="search icon" border="0">.</li>
-  <li>Type your search string in the <b>Containing Text</b> field, or use the 
-      pull-down list to select a previously entered search expression.<br> Use <code>\</code> as an escape 
-      character for search strings that contain the special characters <code>*</code>, <code>?</code>, or <code>\</code>, 
-	  (for example: <code>d:\\directory\\filename.ext</code>).</li>
-  <li>Finish entering your search options, (for example, to scope
-      the search to specified file types), and click <b>Search</b>.</li>
-  <li>The Search view displays the results of your search. Right-click on any item in
-      the Search view to open a pop-up menu that allows you to remove items from the
-      list, copy search results to the clipboard, or rerun the search. To open one of
-      the listed files, double-click it or select <b>Go to File</b> from its pop-up
-      menu.</li>
-</ol>
-
-<p>If you close the Search view, you can return to it later by selecting
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.search.ui.views.SearchView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Search</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/csearchview.htm">Search view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-84b.htm">Searching for files</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-26.htm">Search view</a><br>
-<a href="../reference/ref-45.htm">File search</a>
-</p>
-
-
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm
deleted file mode 100644
index 145fd9e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-84b.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<title>Searching for files</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<h1>Searching for files</h1>
-
-<p>The <b>Go To &gt; Resource</b> action in the <b>Navigate</b> menu 
-allows you to quickly find a resource in the Workbench by searching resource <i>names</i>.
-</p>
-
-<p>You can also do more complex searches for files in the Workbench. For example, 
-to find all files that end with .xml:
-</p>
-
-<ol>
-  <li>On the main toolbar, click the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.search.ui.openSearchDialog")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Search</b></a> button <img src="../images/Image50_search.png" alt="Search icon" border="0" >.</li>
-  <li>Type <code>.xml</code> into the <b>File name patterns</b> field and leave 
-    the <b>Containing text</b> field empty. <br>
-    (You can use the pull-down list to select <code>.xml</code> if it had been previously entered.)</li>
-  <li>Finish entering your search options, for example to scope the search to 
-    specified working sets, and click <b>Search</b>.</li>
-  <li>The Search view displays the results of your search. Right-click on any 
-    item in the Search view to open a pop-up menu that allows you to remove items 
-    from the list, copy search results to the clipboard, or rerun the search. 
-    To open one of the listed files, double-click it or select <b>Go to File</b> 
-    from its pop-up menu.</li>
-</ol>
-<p>
-If you close the Search view, you can return to it later by selecting
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.search.ui.views.SearchView)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Show View &gt; Other... &gt; General &gt; Search</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/csearchview.htm">Search view</a>
-<a href="../concepts/cworkset.htm"><br>Working sets</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-84.htm">Searching for text within a file</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-26.htm">Search view</a><br>
-<a href="../reference/ref-45.htm">File search</a><br>
-</p>
-
-
-
-</body>
-</html>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm
deleted file mode 100644
index bf91064..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87.htm
+++ /dev/null

@@ -1,68 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Replacing a resource with local history</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Replacing a resource with local history</H1>
-
-<p>To replace an unmanaged Workbench resource with a state in the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resource that you want to replace with 
-    a local history state.</li>
-  <li>From the resources pop-up menu, select <b>Replace with</b> &gt; <b>Local 
-    History</b>. The Replace from Local History page opens.</li>
-  <li>Select a state from the <b>Local History</b> list. The Text Compare editor opens.</li>
-  <li>Click the <b>Select Next Change</b> and <b>Select Previous Change</b> buttons 
-    to browse through the changes made between states in the local history and 
-    the Workbench resource.</li>
-  <li>Select the state you want to replace, and click <b>Replace</b>.</li>
-</ol>
-
-<p>To replace a Workbench resource managed by CVS with a state in the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the resource that you want to replace with 
-    a local history state.</li>
-  <li>From the resources pop-up menu, select <b>Replace with</b> &gt; <b>History...</b>. 
-  The History View opens.</li>
-  <li>Put the History View into <em>Local Revision</em> mode by clicking on the Local Revision
-  toolbar button. This will display only Local History revisions in the History View.</li>
-  <li>Select the revision you want to replace the current revision and select <b>Get Contents</b>
-   from the context menu. </li>
-</ol>
-
-<P><em>Tip</em>: You can configure your general preferences to specify how many 
-  days to keep files, or how many entries per file you want to keep, or the maximum 
-  file size for files to be kept with the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Workspace &gt; Local History</b></a> preference page.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from the local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm
deleted file mode 100644
index b17ce48..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-87b.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Restoring deleted resources from local history</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Restoring deleted resources from local history</H1>
-
-<p>To restore a deleted Workbench resource with a state from the local history:
-</p>
-
-<ol>
-  <li>In one of the navigation views, select the folder or project into which you want to restore  
-    a local history state.</li>
-  <li>From the resource's pop-up menu, select <b>Restore from Local History...</b>.
-  The Restore From Local History dialog opens showing all files that were previously contained
-  in the selected folder or project and all of their sub-folders.</li>
-  <li>Check the files that you want to restore</li>
-  <li>If you don't want to restore just the last state of a file you can 
-  select any other state of the file from the <b>Local History</b> list on the right hand side
-  of the dialog. The bottom pane of the dialog shows the contents of the state.</li>
-  <li>If you are done with all files click <b>Restore</b>.</li>
-</ol>
-
-<P><em>Tip</em>: You can configure your Workbench preferences to specify how many 
-  days to keep files, or how many entries per file you want to keep, or the maximum 
-  file size for files to be kept with the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Workspace &gt; Local History</b></a> preference page.
-</P>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87.htm">Replacing resources with the local history</a><br>
-<a href="tasks-88.htm">Setting local history preferences</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm
deleted file mode 100644
index 4265d78..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-88.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting local history preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Setting local history preferences</H1>
-
-<p>To indicate the level of local history that should be kept for 
-each resource in the Workbench:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.FileStates)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Workspace &gt; Local History</b></a> preference page.</li>
-  <li>In the <b>Limit history size</b> field, specify whether you want
-  to limit the local history size using following options.</li>
-  <li>In the <b>Days to keep files</b> field, type the number of days that you 
-    want to keep records for any one Workbench resource. For example, if you type 
-    7, then a history of saved states from the last seven days will be kept.</li>
-  <li>In the <b>Maximum entries per file</b> field, type the number of states to keep 
-    for any one Workbench resource. Note that when you exceed the number of 
-    entries per file, the oldest changes are discarded to make room for the newer 
-    changes.</li>
-  <li>In the <b>Maximum file size (MB)</b> field, type the maximum file size (in 
-    MB) of a resource for which a local history should be kept. If 
-    the size of the resource exceeds the maximum amount of file size allocated, 
-    no local history is kept for that resource.</li>
-  <li>Click <b>OK</b> to set your preferences and close the Local History Preferences page.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-17a.htm">Local history</a><br>
-<a href="../concepts/concepts-27.htm">Versions</a><br>
-<a href="../concepts/concepts-12.htm">Resources</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-70.htm">Comparing resources with the local history</a><br>
-<a href="tasks-87.htm">Replacing a resource with local history</a><br>
-<a href="tasks-87b.htm">Restoring deleted resources from local history</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm
deleted file mode 100644
index 46a0473..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the placement of the tabs</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the placement of the tabs</H1>
-
-<P>You can change the placement of the tabs.  The tabs for stacked views or editors can appear at the top or bottom
-of the area which contains them.
-</P>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Appearance</b></a> preference page.</li>
-  <li>Select from the choices displayed in the <b>Editor tab positions</b> group 
-    or <b>View tab positions</b> group to control whether you want the tabs at 
-    the top or the bottom.</li>
-  <li>Click <b>Apply</b> or <b>OK</b>.</li>
-  <li>The tabs will immediately move to their new locations.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-6.htm">Editors</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-46.htm">Opening files for editing</a><br>
-<a href="tasks-3g.htm">Tiling editors</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm
deleted file mode 100644
index d338d43..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-92.htm
+++ /dev/null

@@ -1,108 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating a CVS repository location</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Creating a CVS repository location</H1>
-
-<P><em>Prerequisite</em>: A CVS server must already be configured on the host machine to create a
-valid repository location in the Workbench.
-</P>
-
-<P>To create a new repository location:
-</P>
-
-<ol>
-  <li>Open the CVS Repositories view by selecting
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Show View &gt; Other... &gt; CVS &gt; CVS Repositories</b></a>.
-  Alternatively, the CVS Repositories view is also shown in the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective.</li>
-  <li>On the toolbar, click on <strong>Add CVS Repository</strong> (or from the 
-    context menu of the CVS Repositories View, select <b>New &gt; Repository Location</b>). 
-    The Add CVS Repository wizard opens.</li>
-  <li>Enter the information required to identify and connect to the repository 
-    location: 
-    <ol type="a">
-      <li>In the <b> Host </b> field, type the address of the host. (For example: 
-        <samp>mymachine.com)</samp>. </li>
-      <li>In the <b> Repository path </b> field, type the path to the repository 
-        on the host (for example <samp>/home/repo, d:/repo.)</samp></li>
-      <li>In the <b> User </b> field, type the user name under which you want 
-        to connect to the repository. </li>
-      <li>In the <b>Password</b> field, type the password for the above user name.</li>
-      <li> From the <b> Connection Type</b> list, select the authentication protocol 
-        of the CVS server.&nbsp; There are three connection methods that come 
-        with the Eclipse CVS client: 
-        <ul>
-          <li><b>pserver</b> - a CVS specific connection method.</li>
-          <li><b>extssh</b> - an SSH 2.0 client included with Eclipse</li>
-          <li><b>pserverssh2</b> - provides a pserver connection over ssh2.</li>
-          <li><b>ext</b> - the CVS ext connection method which uses an external 
-            tool such as SSH to connect to the repository. The tool used by ext 
-            is configured in the <b>Team &gt; CVS &gt; EXT Connection Method</b> 
-            preference page. </li>
-        </ul>
-      </li>
-      <li>If the host uses a custom port, enable <b>Use Port</b> and enter the 
-        port number.</li>
-    </ol>
-  </li>
-  <li><em>Optional:</em> Select <b>Validate Connection on Finish</b> if you want to authenticate 
-    the specified user to the specified host when you close this wizard. (If you 
-    do not select this option, the user name will be authenticated later, when 
-    you try to access the contents of the repository.)</li>
-  <li><em>Optional:</em> Select <strong>Save Password</strong> if you want to 
-  	save the password between sessions, so you do not have to enter the password
-  	again the next time you start Eclipse. To persist login credentials in a 
-  	safe, encrypted form <a href="../reference/ref-securestorage-start.htm">
-  	Secure Storage</a> is used.</li>
-  <li> Click <b>Finish</b>. The repository location is created. </li>
-</ol>
-
-<p><strong>Note</strong>: Prior to Eclipse 3.0, the <strong>extssh</strong> connection 
-  method only supported SSH 1.0. In 3.0 or later, this connection method was upgraded to 
-  support SSH 2.0 as well.</p>
-<p><em>Tip</em>: If you want to use the <strong>extssh</strong> connection method 
-  but want to keep your local workspace (sandbox) compatible with the CVS command 
-  line client, you can use the <strong>ext</strong> connection method and configure 
-  it to use <strong>extssh</strong> from inside Eclipse on the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.ExtMethodPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; CVS &gt; Ext Connection Method</strong></a> preference page.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-  <a href="../concepts/concepts-27c.htm">CVS Repositories</a> </p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-94.htm">Discarding a CVS repository location</a><br>
-<a href="tasks-93.htm">Refreshing the CVS repositories view</a><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-95.htm">Changing the properties of a CVS Repository Location</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-<a href="../reference/ref-securestorage-start.htm">Secure Storage</a><br>
-<a href="../reference/ref-securestorage-prefs.htm">Secure storage preference page</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm
deleted file mode 100644
index 038f65a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-93.htm
+++ /dev/null

@@ -1,46 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Refreshing the CVS Repositories view</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Refreshing the CVS Repositories view</H1>
-
-<P> There are two ways to refresh the CVS Repositories view in order to see the 
-current connection status of all repositories:
-</p>
-
-<ul>
-  <li>Click the <b>Refresh View</b> button on the view's toolbar&nbsp;</li>
-  <li>Press F5 on the keyboard</lI>
-</ul>
-
-<p><em>Note</em>: Refreshing the CVS Repositories view may change the resources 
-  displayed by the view but does not change the branch and version tags known 
-  to the view. Refreshing the tags is discussed in <a href="tasks-110.htm">Discovering 
-  branch and version tags</a></p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-  <a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-  <a href="../concepts/concepts-27c.htm">CVS Repositories</a> </p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a><br>
-  <a href="tasks-94.htm">Discarding a CVS repository location</a> <br>
-  <a href="tasks-110.htm">Discovering branch and version tags</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm
deleted file mode 100644
index b094a8b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-94.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Discarding a CVS repository location</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Discarding a CVS repository location</H1>
-
-<P><em>Note:</em> You cannot discard a location if you have projects in the Workbench that
-are shared with that location.
-</p>
-
-<P>To discard a CVS repository location:
-</p>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, select the repository location that you want 
-    to delete from the Workbench.</li>
-  <li>Select <b>Discard Location</b> from the pop-up menu or press the DELETE 
-    key. Press <b>Yes</b> when prompted.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm
deleted file mode 100644
index 0c6b86a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95.htm
+++ /dev/null

@@ -1,59 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the properties of a CVS repository location</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the properties of a CVS repository location</H1>
-
-<P>You can change the connection properties of an existing repository location.</p>
-
-<P>To change the properties of a CVS repository location:
-</p>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, select the repository location whose properties 
-    you want to change.</li>
-  <li>Select <b>Properties</b> from the pop-up menu. The properties dialog will 
-    open.</li>
-  <li>Select the <strong>CVS</strong> tab.</li>
-  <li>Change one or more of the location's properties.</li>
-  <li>Click <b>OK</b> to change the properties.</li> 
-</ol>
-
-<p><b>Note:</b> The properties will be changed for all projects shared with the selected repository location.</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a><br>
-  <a href="tasks-117b.htm">Changing the sharing of a Project</a><br>
-  <a href="tasks-95a.htm">Changing the encoding of a CVS repository location</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm
deleted file mode 100644
index b361ed9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-95a.htm
+++ /dev/null

@@ -1,63 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the encoding of a CVS repository location</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the encoding of a CVS repository location</H1>
-
-<P>You can change encoding of an existing repository location. This encoding will 
-  be used to translate file paths and commit messages from the client encoding 
-  to the server encoding and vice versa. The encoding does not affect the contents 
-  of file. You may use the editor encoding (available from the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.ContentTypes)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Content Types</strong></a> preference page)
-  or resource encodings (available from the <strong>Properties&nbsp;&gt;&nbsp;Resource</strong> 
-  page of resources) to configure the Workbench to use the proper file encodings.</p>
-
-<P>To change the server encoding of a CVS repository location: </p>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, select the repository location whose properties 
-    you want to change.</li>
-  <li>Select <b>Properties</b> from the pop-up menu. The properties dialog will 
-    open.</li>
-  <li>Select the <strong>Server Encoding</strong> tab.</li>
-  <li>Choose to set the encoding and either choose or type in the desired encoding.</li>
-  <li>Click <b>OK</b> to change the properties.</li> 
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-32.htm">CVS Repositories view</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm
deleted file mode 100644
index 179ee25..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96.htm
+++ /dev/null

@@ -1,135 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Checking out a project from a CVS repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Checking out a project from a CVS repository</H1>
-
-<P>Projects can be checked out from a CVS repository into the Workbench using 
-  the Checkout wizard or from the CVS Repositories view.</P>
-<h2>Checking out using the Checkout Wizard</h2>
-<p>It is available from the Import menu, the New &gt; Project menu and the toolbar 
-  of the CVS Repository Exploring perspective. It is also opened when performing 
-  a Checkout As from the CVS Repositories view.</p>
-<ol>
-  <li>Launch the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.team.cvs.ui.newProjectCheckout)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    Checkout wizard</a>. It is available from the <strong>Import</strong> 
-    menu, the <strong>New &gt; Project</strong> menu and the toolbar of the CVS 
-    Repository Exploring perspective. It is also opened when performing a Checkout 
-    As from the CVS Repositories view. (<strong>Note</strong>: If the CVS capability 
-    is disabled, the Checkout wizard may only be available from the <strong>Import</strong> 
-    menu).</li>
-  <li>Select the desired repository from the list of known repositories or, if 
-    the desired repository is not in this list, choose to create a new repository 
-    location and click <b>Next</b>.</li>
-  <li>If entering a new repository location, enter the repository information 
-    and click <b>Next</b> when completed. <b>(Note</b>: this page is the same 
-    format as the <a href="tasks-92.htm">Creating a CVS repository location</a> 
-    wizard.)</li>
-  <li>Either select one or more modules from the list of existing modules or type 
-    in the name of the module to be checked out. Entering a name is supported 
-    for those situations where obtaining the list of existing modules from the 
-    server is impractical or unsupported. You can also enter a dot (.) as the 
-    module name if the repository is configured to host a single project at its 
-    root. Click <strong>Next</strong> when the module or modules to be checked 
-    out are specified.</li>
-  <li><em>Optional</em>: Choose whether to check out one or more selected modules as a 
-    new projects or into an existing project or folder. If one module is selected 
-    and it does not contain a .project file (the Workbench project configuration 
-    file), you will also have the option to configure the project using the New 
-    Project wizard (in order to make the project a Java project, for instance). 
-    Click <strong>Next</strong>.</li>
-  <li><em>Optional</em>: For a single project, you can configure the location of the project 
-    to be either the default location or a custom location outside the workspace. 
-    For multiple projects, you can configure the parent folder where all the projects 
-    should be located. Click <strong>Next</strong>.</li>
-  <li><em>Optional</em>: Select the tag to check out from and click <strong>Finish</strong>.</li>
-</ol>
-<h2>Checking out from the CVS Repositories view</h2>
-<P>To check out a project from the CVS repositories view to the Workbench: </P>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand the repository location.</li>
-  <li>Expand <b>HEAD</b> and select the folders that you want to add as projects 
-    to the Workbench. If you are looking for a folder in a particular version: 
-    <ol type="a">
-      <li>Expand the <b> Versions</b> category and find the folder name 
-        that you want to add to the Workbench.</li>
-      <li>Expand the folder to reveal its versions.</li>
-    </ol>
-	<p>If you are looking for the latest folder in a branch:</p>
-    <ol type="a">
-      <li>Expand the <b> Branches</b> category.</li>
-      <li>Expand the branch that holds the folder that you want to add to the 
-        Workbench.</li>
-    </ol>
-  </li>
-  <li>From the pop-up menu for the selected folders, select one of the following: 
-    <ol type="a">
-      <li><b>Check Out </b> to check out each of the selected folders as a project 
-        in the local workspace with the same name as the folder in the repository.</li>
-      <li><b>Check Out As...</b> to check out the selected folders into a custom 
-        configured project in the local workspace. <em>Note:</em> When multiple 
-        folders are selected, this operations only allows the specification of 
-        a custom parent location for the new projects.</li>
-    </ol>
-  </li>
-  <li>If <b>Check Out As...</b> was chosen on a single project, one of two possible 
-    dialogs is displayed depending on whether the folder in the repository contains 
-    a .project file or not. 
-    <ol type="a">
-      <li>If there is a .project file, the dialog will accept a custom project 
-        name and location.</li>
-      <li>Otherwise, the dialog will be the New Project wizard which allows full 
-        customization of the project (e.g. Java project).</li>
-    </ol>
-  </li>
-</ol>
-
-<p><em>Tip:</em> Any folder, including non-root folders, can be checked out from 
-a CVS repository.
-</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-<a href="tasks-96b.htm">Checking out a folder into an existing project</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm
deleted file mode 100644
index 2dad12b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96a.htm
+++ /dev/null

@@ -1,64 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Checking out a module from a CVS repository</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Checking out a module from a CVS repository</H1>
-
-<P>Modules can be defined in the CVSROOT/modules file of a CVS repository. To check out such a module from a 
-CVS repository to the Workbench:
-</P>
-
-<ol>
-  <li>Switch to the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.team.cvs.ui.cvsPerspective)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repository Exploring</a> perspective or add the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.team.ccvs.ui.RepositoriesView)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  CVS Repositories</a> view to the current perspective.</li>
-  <li>In the CVS Repositories view, expand the repository location.</li>
-  <li>Expand <b>HEAD</b> and select the modules that you want to add to the Workbench. 
-    <em>Note</em>: Modules appear as root folders of the repository but are associated 
-    with the <img src="../images/tasks-96b-module_rep.png" alt="CVS module icon" border="0" > 
-    icon.</li>
-  <li>From the pop-up menu select <b>Check Out</b>. This will checkout the module 
-    into one or more projects in the local workspace, depending on how the module 
-    is defined in the repository.</li>
-</ol>
-<p><strong>Note</strong>: Defined modules can also be checkout out using the Checkout 
-  Wizard.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96b.htm">Checking out a folder into an existing project</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm
deleted file mode 100644
index 13f98da..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-96b.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Checking out a folder into an existing project</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Checking out a folder into an existing project</H1>
-
-<P>To check out a folder from a CVS repository into an existing project in the 
-  Workbench, you can use either the <strong>Checkout</strong> wizard or <strong>Check 
-  Out As</strong> from the CVS Repositories view. Follow these steps to use the 
-  Checkout wizard.</P>
-
-<ol>
-  <li>Launch the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.team.cvs.ui.newProjectCheckout)")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    Checkout wizard</a>..</li>
-  <li>Select the desired repository from the list of known repositories or, if 
-    the desired repository is not in this list, choose to create a new repository 
-    location and click <b>Next</b>. If entering a new repository location, enter 
-    the repository information and click <b>Next</b> when completed.</li>
-  <li>Either select one or more modules from the list of existing modules or type 
-    in the name of the module to be checked out and click <strong>Next</strong>.</li>
-  <li>Choose whether to check out one or more selected modules into an existing 
-    project and click <b>Next</b>.</li>
-  <li>On the next page you can provide the following information: 
-    <ol>
-      <li><strong>Target folder name</strong> (only when checking out a single 
-        module):  The name of a local folder in which the contents of the remote 
-        folder will be placed. <em>Note</em>: If the local folder exists, its 
-        contents will be deleted and replaced by the contents of the remote folder.</li>
-      <li><strong>Parent of target folder</strong>: The existing local folder 
-        into which the target folders will be created.</li>
-      <li><strong>Checkout sub-folders</strong> (only when checking out a single 
-        module): The option to indicate whether 
-        the sub-folders of the remote folder should be checked out as children 
-        of the target folder.</li>
-    </ol>
-  </li>
-  <li>(Optional) Select the tag to check out from and click <strong>Finish</strong>.</li>
-</ol>
-
-<p><em>Note:</em> Only folders within non-shared projects or projects shared with 
-  the same CVS repository as the selected remote folder are valid targets for 
-  the <em>Checkout Into</em> operation. Also, if the target project of the operation 
-  is an unshared project, the project will be connected to the CVS repository 
-  (i.e. the project will become a shared CVS project) but any pre-existing content 
-  will be ignored.</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-110.htm">Discovering branch and version tags</a><br>
-<a href="tasks-117.htm">Sharing a new project using CVS</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm
deleted file mode 100644
index 2c4f176..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9b.htm
+++ /dev/null

@@ -1,61 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Creating fast views</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Creating fast views</H1>
-
-<p>Fast views are hidden views that can be quickly opened and closed. They work 
-  like other views except they do not take up space in your Workbench window.
-</p>
-
-<p>To create a fast view:</p>
-<ol>
-  <li>Click the title bar of the view that you want. Hold the mouse button down.</li>
-  <li>Drag the view to the Fast View bar and release the mouse button. By default the shortcut bar is located in the lower left corner of the window.</li>
-</ol>
-
-<p>Alternatively, you can click on the button located on the left side of the 
-  Fast View bar which will present you with a selection of views. Choosing one 
-  of these views will add it to the Fast View bar immediately. </p>
-<p><img src="../images/fast_view_menu.png" alt="Picture of the fast view menu">&nbsp;</p>
-
-<p>The icon for the view that you dragged now appears on the shortcut 
-  bar. You can look at the view by clicking its icon on the shortcut bar. As soon 
-  as you click somewhere else outside the view, it is hidden again.
-</p>
-
-<p>To restore the view to its original location (and remove it from the Fast View bar), toggle 
-  the fast view item in the view button's context menu. </p>
-<p>You can also create and restore fast views by selecting <b>Fast 
-  View</b> from the context menu that opens when you click the 
-  icon at the left side of the view's title bar.
-</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21.htm">Fast views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9c.htm">Working with fast views</a><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-<a href="../gettingStarted/qs-39g.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9i.htm">Saving a user-defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm
deleted file mode 100644
index 6708d92..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9c.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Working with fast views</title>
-
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">
-Working with fast views</H1>
-<p CLASS="Head">If you have converted the Project Explorer to a fast view it will
-appear in the shortcut bar as shown below.&nbsp;</p>
-<blockquote>
-  <p CLASS="Head"><img src="../images/Image60_fast_view1.png" alt="Show fast view" border="0" ></p>
-</blockquote>
-  <p CLASS="Head">To work with a fast view proceed as follows.</p>
-<TABLE BORDER="0" cellspacing="0" cellpadding="3">
-<THEAD>
-</THEAD>
-<TBODY>
-<TR>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>
-1.</b>
-</P>
-</TD>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">In the shortcut bar click on the Project Explorer fast view button.</P>
-</TD>
-</TR>
-<TR>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>2.</b>
-</P>
-</TD>
-<TD COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-Observe the Project Explorer view slides out from the shortcut bar.&nbsp; </P>
-        <P CLASS="Para"> <img src="../images/Image61_nav_fast.png" alt="Fast view" border="0" ></P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>3.</b>
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-You can use the Project Explorer fast view as you would normally.&nbsp;&nbsp; </P>
-</TD>
-</TR>
-<TR>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-<b>4.</b>
-</P>
-</TD>
-<TD ROWSPAN="1" COLSPAN="1" valign="top" align="left">
-<P CLASS="Para">
-To hide the fast view simply click off of it or click on the Minimize button on
-the fast view's toolbar </P>
-<P CLASS="Para">
-<img src="../images/Image61_fast_minimize.png" alt="Minimize button" border="0" > </P>
-<P CLASS="Para">&nbsp; </P>
-        <P CLASS="Para"><strong>Note:</strong> If you open a file from the Project Explorer 
-          fast view, the fast view will automatically hide itself to allow you 
-          to work with the file.&nbsp;&nbsp; </P>
-</TD>
-</TR>
-</TBODY>
-</TABLE>
-<P>To convert a fast view that has been maximized back to a regular sized view, 
-  select <strong>Restore </strong>from the context menu of the icon in the top 
-  left corner of the view. To reposition a fast view, drag the fast view's title 
-  bar (or close the fast view and then drag its button from the shortcut bar) 
-  and drop it on the workbench like a normal view.</P>
-<p></p>
-<P CLASS="Para">
-An empty fast view bar can be hidden using the 'Hide empty fast view bar' preference on the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Perspectives</b></a>
-  preference page.</P>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts."  ><br>
-  <a href="../concepts/concepts-5.htm">Views</a><br>
-  <a href="../concepts/concepts-21.htm">Fast views</a><br>
-  <a href="../concepts/concepts-4.htm">Perspectives</a> </P>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"  ><br>
-<a href="tasks-9b.htm">Creating fast views</a><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Docking views</a><br>
-<a href="../gettingStarted/qs-39g.htm">Maximizing a view or editor</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm
deleted file mode 100644
index baa2c08..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9d.htm
+++ /dev/null

@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Deleting a user defined perspective</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Deleting a user defined perspective</H1>
-<P>You can delete perspectives that you defined yourself, but not
-those that are delivered with the Workbench.</P>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Perspectives</b></a> preference page.</li>
-  <li>From the <b>Available perspectives</b> list, select the one that you want
-    to delete and click <b>Delete</b>.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts."><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm
deleted file mode 100644
index c6263e4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9f.htm
+++ /dev/null

@@ -1,60 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Opening perspectives</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Opening perspectives</H1>
-<p>Perspectives provide combinations of views and editors that are
-suited to performing a particular set of tasks. For example, you would normally
-open the Debug perspective to debug a Java program.
-</p>
-
-<p>To open a new perspective:</p>
-<ol>
-  <li>Click the <b>Open Perspective</b> button 
-      <img border="0" src="../images/ref-52.png"  alt="Open Perspective button"> 
-      on the shortcut bar on the left side of the Workbench window. (This provides 
-      the same function as the <b>Window &gt; Open Perspective</b> menu on the menu bar.)</li>
-  <li> To see a complete list of perspectives, select <b>Other...</b>
-    from the drop-down menu.</li>
-  <li>Select the perspective that you want to open.</li>
-</ol>
-
-<p>When the perspective opens, the title bar of the window it is in changes to
-display the name of the perspective. In addition, an icon is added to the shortcut bar, 
-allowing you to quickly switch back to that perspective from other perspectives in the same
-window.
-</p>
-
-<p>
-By default, a perspective will open in the same window.
-If you would rather it opened in a new window, change the setting in the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Perspectives</b></a> preference page.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-28.htm">Switching between perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm
deleted file mode 100644
index 635af52..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9i.htm
+++ /dev/null

@@ -1,47 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Saving a user defined perspective</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Saving a user defined perspective</H1>
-<P>If you have modified a perspective by adding, deleting, or
-moving (docking) views, you can save your changes for future use.
-</P>
-
-<ol>
-  <li>Switch to the perspective that you want to save.</li>
-  <li>Click <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.savePerspective")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Save Perspective As...</b></a>.</li>
-  <li>Type a new name for the perspective into the <b>Name</b> field.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>The name of the new perspective is added to the <b>Window &gt; Open Perspective</b> menu.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a><br>
-<a href="../concepts/concepts-5.htm">Views</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9j.htm">Resetting perspectives</a><br>
-<a href="tasks-9d.htm">Deleting a user defined perspective</a><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm
deleted file mode 100644
index e283ad4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9j.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Resetting perspectives</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Resetting perspectives</H1>
-<p>To restore a perspective to its original layout:</p>
-<ol>
-  <li>Open the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Perspectives)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General &gt; Perspectives</b></a> preference page.</li>
-  <li>From the <b>Available perspectives</b> list, select the perspective you want to restore.</li>
-  <li>Click <b>Reset</b>.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm
deleted file mode 100644
index 3679679..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9k.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Configuring perspective shortcuts</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Configuring perspective shortcuts</H1>
-<p>You can choose which menu items are available under the <b>File &gt; New</b>, 
-<b>Window &gt; Open Perspective</b> and <b>Window &gt; Show View</b> menus
-using the <b>Shortcuts</b> tab of the <b>Customize Perspective</b> dialog.
-To configure shortcuts:</p>
-
-<ol>
-  <li>Switch to the perspective that you want to configure.</li>
-  <li>Select <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Window &gt; Customize Perspective...</b></a>.</li>
-  <li>Open the <b>Shortcuts</b> tab.</li>
-  <li>Choose the sub menu whose shortcuts you want to edit.</li>
-  <li>Use the Categories tree to turn groups of related shortcuts on or off, or
-  select categories to work with individual menu items in the Shortcuts list.</li>
-  <li>Click <b>OK</b> to cause the changes to take effect.</li>
-</ol>
- <p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9l.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9l.htm
deleted file mode 100644
index dc4f7f9..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9l.htm
+++ /dev/null

@@ -1,52 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Detaching views</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Detaching views</H1>
-
-<p><img src="../images/win_only.png" alt="Windows only" border="0" > Detached views are
-  views that are shown in a separate window with a smaller trim.
-  They work like other views except they they are always shown in front of the Workbench window.
-</p>
-
-<p>To detach a view:</p>
-<ol>
-  <li>If the Workbench window is maximized, resize it so that it does not fill the entire screen.</li>
-  <li>Click the title bar of the view that you want to detach. Hold the mouse button down.</li>
-  <li>Drag the view to the outside of the Workbench window and release the mouse button.</li>
-</ol>
-
-<p>To restore the view to be shown inside of the Workbench window, drag it into the
-  Workbench window.
-</p>
-
-<p>You can also detach a view by selecting <b>Detached</b> from the context menu
-  that opens when you click the icon at the left side of the view's title bar.
-</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-5.htm">Views</a><br>
-<a href="../concepts/concepts-21a.htm">Detached views</a><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-3.htm">Opening views</a><br>
-<a href="tasks-3e.htm">Moving and docking views</a><br>
-<a href="tasks-9i.htm">Saving a user-defined perspective</a><br>
-<a href="tasks-9j.htm">Resetting perspectives</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9m.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9m.htm
deleted file mode 100644
index d759b7a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9m.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Configuring perspective command groups</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Configuring perspective command groups</H1>
-<p>You can choose which command groups are available in a perspective. Command 
-  groups contribute menu items, toolbar buttons and key bindings, all of which 
-  run commands. Making a command group unavailable in a perspective removes 
-  these methods of running commands. Making a command group available makes it 
-  possible for these methods to be used, however they can be turned on and off 
-  with more fine-grained control via the <b>Menu Visibility</b> and 
-  <b>Tool Bar Visibility</b> tabs of the <b>Customize Perspective</b> 
-  dialog.</p>
-
-<p>To configure command group availability:</p>
-
-<ol>
-  <li>Switch to the perspective that you want to configure.</li>
-  <li>Select <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Window &gt; Customize Perspective...</b></a>.</li>
-  <li>Open the <b>Command Groups Availability</b> tab.</li>
-  <li>Select the command group in the <b>Available command groups</b> list whose
-  	availability you want to edit.</li>
-  <li>Preview the menu items and toolbar buttons which are contributed by the 
-  	selected command group in the <b>Menubar details</b> and
-  	<b>Toolbar details</b> trees. Hover over items in these trees to view
-  	their key bindings. </li> 
-  <li>Use the check box next to the command group to make it available
-    or unavailable.</li>
-  <li>Click <b>OK</b> to cause the changes to take effect.</li>
-</ol>
- <p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9n.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-9n.htm
deleted file mode 100644
index 864ce23..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-9n.htm
+++ /dev/null

@@ -1,80 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005, 2008. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Showing and hiding menu items and toolbar buttons</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Showing and hiding menu items and toolbar buttons</H1>
-<p>You can choose to hide menu items and toolbar buttons and then show
-  them again.</p>
-<h2>Hiding a menu item or toolbar button</h2>
-<p>To hide a menu item or toolbar button:</p>
-<ol>
-  <li>Switch to the perspective that you want to configure.</li>
-  <li>Select <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <b>Window &gt; Customize Perspective...</b></a>.</li>
-  <li>Open the <b>Menu Visibility</b> or <b>Tool Bar Visibility</b> tab.</li>
-  <li>Find the item you want to hide. You can do this two ways:
-    <ul>
-      <li>Expand the menu or toolbar hierarchy to find the item you want to 
-        hide.</li>
-      <li>Click the <b>Filter by command group</b> check box to see a list
-        of command groups which contribute items, and choose the command
-        group the item you wish to hide. Then navigate to the item in the
-        hierarchy in the Structure tree.</li>
-    </ul>
-  </li>
-  <li>Hover over the item to get additional information:
-    <ul>
-      <li>a description of what the item does</li>
-      <li>the name of the command group which contributes the item (click the
-      	link in this item to switch to the <b>Command Groups Availability</b>
-      	tab with the appropriate command group selected).</li>
-      <li>any key bindings associated with the command the item performs (click 
-      	the link in this item to open the <b>Keys</b> page of the 
-      	<b>Preferences</b> dialog with the command selected, if possible).</li>
-      <li>if the item is dynamic, a preview of its current appearance (dynamic
-      	items are listed as [Dynamic]).</li>
-    </ul>
-  </li> 
-  <li>Uncheck the check box next to the item. Uncheck a menu to hide all
-    its children.</li>
-  <li>Click <b>OK</b> to cause the changes to take effect.</li>
-</ol>
-<p>Using the tooltip which appears over items, you can navigate to the
-  <b>Command Group Availability</b> tab and make the entire command 
-  group unavailable if you wish to remove all menu items, toolbar 
-  buttons and keybindings of all commands contributed by the command 
-  group.</p>
-
-<h2>Showing a menu item or toolbar button</h2>
-<p>To show a menu item or toolbar button, you can follow the same 
-  instructions as hiding one, except check the check box instead of
-  unchecking it.</p>
-<p>If an item you want to make visible is grayed out, this is 
-  because the command group which contributes it is not available.
-  You need to make it available before you can show or hide items
-  it contributes. You can do this by hovering over the item, and
-  clicking the command group link in the tooltip which appears.</p>
- <p><img border="0" src="../images/ngrelc.png" alt="Related concepts." ><br>
-<a href="../concepts/concepts-4.htm">Perspectives</a>
-</p>
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-24.htm">Changing where perspectives open</a><br>
-<a href="tasks-31.htm">Specifying the default perspective</a><br>
-<a href="tasks-9i.htm">Saving a user defined perspective</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm
deleted file mode 100644
index daafcc5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-addtasksandtypes.htm
+++ /dev/null

@@ -1,49 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Adding new Ant tasks and types</title>
-<meta name="keyword" content="ant">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-<body>
-<H1>Adding new Ant tasks and types</H1>
-
-<p>Add new Ant tasks and types through the Ant preferences page. These tasks and 
-types will be available for buildfiles running in the Workbench without, having 
-to use taskdef or typedef in the script declaration (For more on taskdef or 
-typedef see the Ant documentation in
-<a href="http://ant.apache.org/index.html" target="_blank">http://ant.apache.org</a>).
-</p>
-
-<p>To add a new task or type:</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Ant &gt; Runtime</b></a> preference page.</li>
-  <li>Click the <b>Tasks</b> tab or the <b>Types</b> tab.</li>
-  <li>Click <b>Add Task</b> or <b>Add Type</b>.</li>
-  <li>Provide a name and class for the task or type.</li>
-  <li>Select the library where the task or type is declared. If the library is not present on the list, 
-    you must add it to the Ant classpath (see the Related task link below).</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant Support</a><br>
-<a href="../concepts/concepts-22.htm">Builds</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a>
-</p>
-</body>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm
deleted file mode 100644
index ee0bf34..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-classpath.htm
+++ /dev/null

@@ -1,58 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Modifying the Ant classpath</title>
-<meta name="keyword" content="ant">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-<body>
-<H1>Modifying the Ant classpath</H1>
-
-<p>When using an optional or custom task it is usually necessary to add extra 
-  libraries to the classpath. The Ant classpath can be modified globally or per
-  launch configuration.
-</p>
-
-<p>To modify the Ant classpath globally:</p>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Ant &gt; Runtime</b></a> preference page.</li>
-  <li>If you are not on it already, click the <b>Classpath</b> tab.</li>
-  <li>To add a JAR file to the classpath, click <b>Add Jar</b> and select the JAR file.</li>
-  <li>To add a folder to the classpath, click <b>Add Folder</b> and select the folder.</li>
-  <li>To remove an item from the classpath, select it and click <b>Remove</b>.</li>
-  <li>To restore the classpath to the default, click <b>Restore Defaults</b>.</li>
-</ol>
-
-<p>To modify the Ant classpath for a launch configuration:</p>
-<ol>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Run &gt; External Tools &gt; External Tools...</b></a>.</li>
-  <li>Select the Ant configuration whose classpath you wish to modify</li>
-  <li>Select the <b>Classpath</b> tab</li>
-  <li>To add a JAR file to the classpath, click <b>Add Jar</b> and select the JAR file.</li>
-  <li>To add a folder to the classpath, click <b>Add Folder</b> and select the folder.</li>
-  <li>To remove an item from the classpath, select it and click <b>Remove</b>.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a><br>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="./tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-</p>
-</body>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm
deleted file mode 100644
index 7201700..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-running.htm
+++ /dev/null

@@ -1,57 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running Ant buildfiles</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-<body>
-<H1>Running Ant buildfiles</H1>
-
-<p>To run an Ant buildfile in the Workbench:
-</p>
-<ol>
-  <li>In one of the navigation views, select an XML file.</li>
-  <li>From the file's pop-up menu, select <b>Run Ant...</b>. The launch configuration
-  	dialog opens.</li>
-  <li>Select one or more targets from the <b>Targets</b> tab. The order 
-    in which you select the items is the order in which they will run. The order 
-    is displayed in the <b>Target execution order</b> box at the bottom of the tab.
-    You can change the order of the targets by clicking the <b>Order...</b> button.</li>
-  <li>(Optional) Configure options on the other tabs. For example, on the <b>Main</b> tab,
-    type any required arguments in the <b>Arguments</b> field.</li>
-  <li>Click <b>Run</b>.</li>
-</ol>
-
-<p>The Ant buildfile will run on the selected targets. Unless you disabled the <b>Capture
-output</b> option on the <b>Main</b> tab, the console displays any applicable execution results 
-as the buildfile runs.
-</p>
-
-<p>These steps create a persisted launch configuration. The newly created configuration will
-appear in the launch history under <b>Run &gt; External Tools</b> and will be available in the
-launch configuration dialog which is opened by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Run &gt; External Tools &gt; External Tools...</b></a>.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant support</a><br>
-<a href="../concepts/concepts-22.htm">Builds</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-version.htm">Using a different version of Ant</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-</p>
-</body>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm
deleted file mode 100644
index 9cbb03f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-ant-version.htm
+++ /dev/null

@@ -1,88 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Using a different version of Ant</title>
-<meta name="keyword" content="ant">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-<body>
-<H1>Using a different version of Ant</H1>
-
-<P> The Eclipse platform provides Ant 1.7.1 as a plug-in library. When running 
-an Ant buildfile in the Workbench, version 1.7.1 is used by default. It is possible 
-to use different versions, although they are not supported. There are at least 
-two ways of using a different version of Ant:
-</P>
-
-<dl>
-<dt><b>Changing the Ant runtime classpath:</b></dt>
-<dd>When Ant runs a buildfile, it looks for the necessary classes on the Ant classpath. 
-The Ant classpath consists of the plug-ins contributing new tasks, types or 
-libraries, plus the classpath defined in the Ant runtime classpath preferences. To 
-access the preferences, click
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntRuntimePreferencePage)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Window &gt; Preferences &gt; Ant &gt; Runtime</b></a>. 
-The JARs related to Ant 1.7.1 are grouped under the <b>Ant Home Entries</b> item.
-To change the Ant Home entries, click on the <b>Ant Home...</b> button and choose the Ant
-installation you wish to use.
-
-<p>After you change the Ant classpath, all future Ant builds will use the updated 
-version instead of the default. To restore the Ant classpath to its original 
-state, <b>Restore Defaults</b> button on the preference page.
-</p>
-</dd>
-<dt><b>Using Ant as an external tool:</b></dt>
-<dd>When changing the Ant classpath is not an option, or if you just want to test 
-a newer or beta version of Ant, using it as an external tool is an option. 
-Usually when it is running in the Workbench, the Ant buildfile 
-itself is considered to be a external tool, but this is not the only way. 
-To install a binary distribution of Ant as an external tool (<b>Note:</b> 
-These steps are for Windows, but similar methods can be used for other operating systems): 
-<ol type="a">
-  <li>Download and install the binary version of Ant from
-    <a href="http://ant.apache.org" target="_blank">http://ant.apache.org</a> .</li>
-  <li>Click
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Run &gt; External Tools &gt; External Tools...</b></a>.</li>
-  <li>Click <b>Program</b></li>
-  <li>Click <b>New</b>.</li>
-  <li>Enter a name for your external tool (for example, External Ant).</li>
-  <li>For the <b>Location</b> field, click <b>Browse File System</b>.</li>
-  <li>Find and select a file called <code>ant.bat</code> (it should be 
-  in the <code>bin</code> folder of your Ant installation).</li>
-  <li>In the <b>Arguments</b> field enter the arguments for your 
-    buildfile that would normally enter for running the buildfile outside of the 
-    Workbench.</li>
-  <li>In the <b>Working Directory</b> field enter the directory of your buildfile.</li>
-  <li>Click <b>Run</b> to execute the buildfile.</li>
-</ol>
-
-<p>When you run Ant as an external tool, none of the tasks or types 
-contributed by Eclipse will work. Also, the Ant classpath preference has no 
-effect in the buildfile execution.
-</p>
-</dd>
-</dl>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-antsupport.htm">Ant Support</a><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="./tasks-ant-running.htm">Running Ant buildfiles</a><br>
-<a href="../tasks/tasks-exttools-running.htm">Running external tools</a><br>
-<a href="../tasks/tasks-ant-classpath.htm">Modifying the Ant classpath</a><br>
-<a href="../tasks/tasks-ant-addtasksandtypes.htm">Adding new Ant tasks and types</a><br>
-</p>
-
-</body>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm
deleted file mode 100644
index be31104..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-10.htm
+++ /dev/null

@@ -1,62 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Disconnecting a project from CVS</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Disconnecting a project from CVS</H1>
-
-<P>Disconnect a project from CVS to disable the CVS operations that can be performed 
-  on the project and it resources and optionally to remove the CVS information 
-  (stored in the CVS folders) associated with the project. </P>
-
-<P>To disconnect a project from CVS:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the project to be disconnected.</li>
-  <li>Select <b>Team &gt; Disconnect</b> from the project's pop-up menu. The Confirm 
-    Disconnect from CVS dialog opens.</li>
-  <li>In the dialog, choose one of: 
-    <ol type="a">
-      <li><b>Delete the CVS meta information</b> - disables the CVS team menu 
-        operations and removes the CVS folders and their contents from the file 
-        system.</li>
-      <li><b>Do not delete the CVS meta information</b> - disables the CVS team menu 
-        operations but leaves the CVS meta information.</li>
-    </ol></li>
-  <li>Click <b>Yes</b> to disconnect the project.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from the CVS repository</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm
deleted file mode 100644
index 14e91bb..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-11.htm
+++ /dev/null

@@ -1,81 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting the CVS keyword substitution mode</title>
-<meta name="keyword" content="team">
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head">Setting the CVS keyword substitution mode</H1>
-
-<P>CVS uses the keyword substitution mode of a file to differentiate binary files 
-from ASCII files and to indicate what type of keyword substitution is to take 
-place when files are committed and checked out.
-</P>
-  
-<P>To set the CVS keyword substitution mode:
-</P>
-
-<ol>
-  <li>In one of the navigation views, select the files or containing folders for which 
-    a change in keyword substitution mode is desired. <b>Note</b>: Ensure that 
-    any new files that are to be committed are added to CVS version control as 
-    the keyword substitution mode can only be set for files that are already under 
-    CVS control.</li>
-  <li>From the pop-up menu, select<b> Team &gt; Change ASCII/Binary Property</b>. 
-    The Set Keyword Substitution Mode wizard will open. The following dialog was opened 
-    was opened on the org.eclipse.jdt.core project:
-    <p><img src="../images/cvs_change_ascii_binary_prop.png" alt="The Set Keyword Substitution Mode wizard" border="0" ></p>
-  </li>
-  <li>The wizard contains a list of all founds found in the selection. On this 
-    page, you can do the following: 
-    <ul>
-      <li>You can enter a file pattern to filter the list of files.</li>
-      <li>You can change the mode for files individually.</li>
-      <li>You can select multiple files and change the mode for the all using 
-        the drop down at the bottom of the page.</li>
-      <li>You can select multiple files and click <strong>Propose</strong> which 
-        determines the mode based on your preference settings.</li>
-      <li>You can check the <em>Only show those files that will be changed</em> option to see only the files 
-        whose mode has been changed in the wizard.</li>
-    </ul>
-  </li>
-  <li>When you are done specifying the new modes for any files, enter the commit 
-    comment to be associated with any file commits. Files will need to be committed 
-    if changing the file type from Binary to ASCII results in a change in the 
-    file content due to line terminator adjustments. Click <b>Finish</b> to apply 
-    the changes.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27b.htm">Branches</a><br>
-<a href="../concepts/concepts-30.htm">Synchronizing with a CVS repository</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-96.htm">Checking out a project from the CVS repository</a><br>
-<a href="tasks-103.htm">Replacing resources in the Workbench</a><br>
-<a href="tasks-100a.htm">Branching</a><br>
-<a href="tasks-115.htm">Synchronizing with the repository</a><br>
-<a href="tasks-113.htm">Updating</a><br>
-<a href="tasks-113b.htm">Resolving conflicts</a><br>
-<a href="tasks-100b.htm">Merging from a branch</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-20-fileContent.htm">File Content</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm
deleted file mode 100644
index 3237210..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-16.htm
+++ /dev/null

@@ -1,45 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Filtering CVS Revisions in the History View</title>
-<meta name="keyword" content="team">
-</HEAD>
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Filtering CVS Revisions in the History View</H1>
-<P CLASS="Para">Over time, the revision history for a file can grow drastically. 
-  As a result, it may be difficult to find the revision or revisions that you 
-  are looking for. Using the filtering mechanism of the History View 
-  can help.</P>
-<P CLASS="Para">To set a filter on a CVS managed resource that is currently being displayed in the History View:</P>
-<ol>
-  <li>Select the <b>Filter...</b> action from the dropdown menu on the History View toolbar.</li>
-  <li>Enter any author, comment, or date range that you would like the view to display.
-  <p><img src="../images/cvs_filter_res_history.png" alt="Filter Resource History dialog" border="0" ></p>
-  </li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-<p>The view will now display only those revisions that match the criteria you 
-  entered.</p>
-<p><b>Tip:</b> You can remove the filter at a later time by selecting <b>Remove Filters</b> from the dropdown menu on the History View toolbar.</p>
-<p><b>Tip:</b> You can choose whether the filter should match any or all of the 
-  criteria by selecting the appropriate radio button in the dialog.</p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-<br><a href="../reference/ref-32a.htm">CVS History View</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm
deleted file mode 100644
index ec9a351..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-annotate.htm
+++ /dev/null

@@ -1,56 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta content="text/html; charset=ISO-8859-1"
- http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css"
- rel="STYLESHEET">
-  <title>Determining who last modified a line with the Annotate command</title>
-  <meta content="team" name="keyword">
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h1 class="Head">Determining who last modified a line with the Annotate command</h1>
-<p>Let's say you have found some code that you don't understand on line 65 of a file. 
-  Who do you ask about it?  Well you could start by 
-  looking at the resource history for the file, but that won't tell you who changed 
-  that particular line. This is why the <span
- style="font-weight: bold;">Annotate</span> command is useful. 
-  Sometimes jokingly referred to as the <span style="font-weight: bold;">blame</span>, 
-  it allows you to pick any 
-  ASCII file (see note on binary files) and get a listing of who changed what 
-  line. </p>
-
-<p>The <span style="font-weight: bold;">Team &gt; Show Annotation</span> action
-is available from the following places: History View, Repository Explorer,
-Synchronize View, the Project and Package Explorers, and text editor context menus. The action works in a Quick Diff
-flavor and offers the following features:</p>
-<ul>
-  <li>Displays the annotations on a local file right in the same editor.</li>
-  <li>Clicking on an annotation or clicking on any line in the editor will prompt the
-    History View to show the corresponding revision information.</li>
-  <li>Doesn't lose your place in the editor when displaying the annotation; simply adds the
-    annotations to the annotation bar of the editor that you are currently using.</li>
-  <li>To turn off annotations, you have to select <span style="font-weight: bold;">Revisions &gt; Hide Revision Information</span> from the annotation
-    bar context menu.</li>
-</ul>
-
-<h2>Only works with text files</h2>
-<p>The annotate command will only work with files that are marked as ASCII in 
-  the CVS repository. Also, the command will open a text file to show the changes 
-  even if the associated editor in the workbench is a non-text editor. For example, 
-  if you run annotate on a plugin.xml file a simple text editor will be opened 
-  instead of the full PDE editor.</p>
-<p><img  alt="Related concepts"
- src="../images/ngrelc.png" border="0"> <br>
-<a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img  alt="Related reference"
- src="../images/ngrelr.png" border="0"> <br>
-<a href="../reference/ref-47.htm">CVS</a> </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm
deleted file mode 100644
index 10346a0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-passwords.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Password Management</title>
-  <meta name="keyword" content="team">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-<body style="background-color: rgb(255, 255, 255);">
-<h1 class="Head">Password Management</h1>
-<p>When creating a repository location, an option is provided at the bottom of 
-  the wizard to save the password between sessions. <br>
-</p>
-<p style="text-align: left; margin-left: 40px;"><img alt="Save passwords prompt" src="../images/Image83_cvs_savedpasswords.png">
-</p>
-<p>In previous releases, passwords were automatically saved between sessions whereas 
-now you have full control over this behavior. To persist login credentials in 
-a safe, encrypted form <a href="../reference/ref-securestorage-start.htm">Secure Storage</a> is now used.</p>
-<p>You can manage the list of passwords that have been saved via the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.equinox.security.ui.storage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>General &gt; Security &gt; Secure Storage</strong></a> preference page.
-The page displays the currently saved passwords and allows you to clear or delete them all.</p>
-<p>As an alternative you can use 
-<a href="tasks-cvs-ssh2.htm">keypair authentication</a> provided by the <em>extssh</em> 
-  connection method.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="tasks-cvs-ssh2.htm">Connecting and configuring CVS with SSH</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/ref-47.htm">CVS</a><br>
-<a href="../reference/ref-securestorage-start.htm">Secure Storage</a><br>
-<a href="../reference/ref-securestorage-prefs.htm">Secure storage preference page</a></p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm
deleted file mode 100644
index e7ef49a..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-project-set.htm
+++ /dev/null

@@ -1,84 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Sharing your workspace setup using Project Sets</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Sharing your workspace setup using Project Sets</H1>
-<P CLASS="Para">Your workspace setup may consist of several projects from one 
-  or more repositories. Once you have setup your workspace, you can share it with 
-  others by exporting a Team Project Set. A project set is a text file that contains 
-  a pointer to each of the projects contained in the project set.When a project 
-  set is imported, these pointers are used to fetch the projects from the repository. 
-  Project sets can include any projects that are mapped to repository tooling 
-  that provides support for them, such as CVS. To export a project set:</P>
-<ol>
-  <li>Setup your workspace with all the projects you want to work on by checking 
-    them out of CVS or obtaining them in any manner appropriate for the repository 
-    tooling you are using.</li>
-  <li>From the <strong>File</strong> menu, choose <strong>Export</strong>. The
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    Export dialog</a> will open.</li>
-  <li>In the Export dialog, choose <b>Team &gt; Team Project Set</b> and click <strong>Next</strong>. 
-    The dialog will now display all the projects that are eligible for export.</li>
-  <li>Check the projects you wish to include in the project set. Either browse 
-    for or type in the name of the file where you wish to save the project set 
-    and then click <strong>Finish</strong>.</li>
-</ol>
-<P CLASS="Para">Now you have created a project set file. You can now share this 
-  file with others or use it yourself to recreate your workspace. To Import a 
-  project set:</P>
-<ol>
-  <li>From the <strong>File</strong> menu, choose <strong>Import</strong>. This 
-    will open the
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    Import dialog</a>.</li>
-  <li>In the Import dialog, choose <b>Team &gt; Team Project Set</b> and click <strong>Next</strong>.</li>
-  <li>Browse for or type in the name of the file containing the project set and 
-    click Finish.</li>
-  <li>The projects contained in the project set will be fetched from the repository.</li>
-</ol>
-<P CLASS="Para">For CVS, you will be prompted to provide the authentication information 
-  (user name and password) for the repository as it is not included in the project 
-  set. </P>
-<P CLASS="Para"><b>Specify Repository Information dialog</b></P>
-<P CLASS="Para">When the project set contains only partial repository information
-(not all locations are known) the Specify Repository Information window is displayed offering three options for Repository locations:</P>
-<ol>
-<li>Use the original location that is displayed in the first row of the Repository location column drop down list.</li>
-<li>Click <b>OK</b> to choose a known repository location from the same drop down list (default).</li>
-<li>Create a new repository location by clicking the <b>Create Location</b> button.</li>
-</ol>
-<P CLASS="Para">The user can fully configure the repository location, specify a user name, and change the connection method if required. For example, a project set file containing extssh connections can be used by a non-committer as they can reconfigure the repository location connection method on import to a pserver.</P>
-<p><img src="../images/cvs-specify-repository.png" alt="Repositories configuration dialog"></p>
-  
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a><br>
-<a href="../concepts/concepts-27c.htm">CVS Repositories</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="tasks-96.htm">Checking out a project from a CVS repository</a><br>
-<a href="tasks-96a.htm">Checking out a module from a CVS repository</a><br>
-  <a href="tasks-92.htm">Creating a CVS repository location</a><br>
-  <a href="tasks-117.htm">Sharing a new project using CVS</a></p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related references" ><br>
-  <a href="../reference/ref-47.htm">CVS</a><br>
-  <a href="../reference/ref-32.htm">CVS Repositories view</a><br>
-  <a href="../reference/ref-40a.htm">CVS Checkout wizard</a></p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm
deleted file mode 100644
index bdd0b22..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-quickdiff.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-  <meta http-equiv="Content-Type"
- content="text/html; charset=ISO-8859-1">
-  <meta http-equiv="Content-Style-Type" content="text/css">
-  <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1"
- type="text/css">
-  <title>Quick Diff: showing changes in a text editor</title>
-  <meta name="keyword" content="team">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body style="background-color: rgb(255, 255, 255);">
-<h1 class="Head">Quick Diff: Showing changes in a text editor</h1>
-<p>Instead of using a compare editor, which will show changes between 2
-or
-3 files by showing each file side-by-side, you can enable quick diff
-support and see the changes within the text editor (e.g. any text
-editor based on the Eclipse text editor). This feature can be enabled
-via the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.QuickDiff)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<span style="font-weight: bold;">General &gt; Editors &gt; Text Editors &gt; Quick Diff</span></a>
-preference page. You should select the
-<span style="font-weight: bold;">Latest CVS Revision</span> as the reference
-source. This will annotate the text file with diffs against the
-latest revision in CVS. Here are the following scenarios that are
-useful:</p>
-<ol>
-  <li>
-    <p><span>Open a file and make changes to it. You will see the
-difference <span>annotations marking the changes. Then if you run <span
- style="font-weight: bold;">Team &gt; Replace with latest</span>. The
-annotations are removed and the file is clean. </span></span></p>
-  </li>
-  <li>
-    <p><span>Open a file and make changes to it. You will see the
-difference <span>annotations marking the changes. Then if you run <span
- style="font-weight: bold;">Team &gt; Commit</span> the annotations are
-removed and the file is clean.</span></span></p>
-  </li>
-  <li>
-    <p><span><span>If you synchronize the file with the server and a new revision 
-      is found on the server, the editor will update showing the incoming changes.</span></span></p>
-  </li>
-</ol>
-<p>If you enable showing the differences in the overview ruler, you can, at a 
-  glance, get an idea of how many changes you have made to a file since your last 
-  commit. The differencing happens in a background thread to minimize the impact 
-  on actual editing of the file.</p>
-<p><em>Note:</em> this feature requires an active 
-  connection to your CVS server so that remote contents can be fetched when an 
-  editor is opened.</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"
- > <br>
-<a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"
- > <br>
-<a href="../reference/ref-47.htm">CVS</a> </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm
deleted file mode 100644
index 824ce7c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-ssh2.htm
+++ /dev/null

@@ -1,125 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-  <meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
-  <meta content="text/css" http-equiv="Content-Style-Type">
-  <link type="text/css" charset="ISO-8859-1" href="../book.css" rel="STYLESHEET">
-  <title>Connecting and configuring CVS with SSH</title>
-  <meta content="team" name="keyword">
-  <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</head>
-
-<body>
-<h1>Connecting and configuring CVS with SSH</h1>
-<p>Eclipse includes an SSH client for accessing a remote CVS server.
-The client supports both the SSH1 and SSH2 protocol versions. To use SSH2
-with a CVS repository select the <span style="font-weight: bold;">extssh</span>
-connection type.</p>
-<p>Different methods can be used to authenticate, 
-  depending on the level of functionality and security you want. User authentication 
-  methods used by the client by default are, in the following order: public-key, 
-  Keyboard-Interactive, and password authentication.</p>
-<h2>Authentication with Public Keys (keypair)</h2>
-<p> Public-key authentication allows you to connect to a remote CVS server without 
-  sending your password over the wire. This is a more secure authentication method 
-  than password authentication. Public-key authentication uses two keys, a private 
-  key that only you have--it should be kept in a secure place and protected with 
-  a password. And the public key, which is placed on the server you wish to gain 
-  access to.</p>
-<p>
-  Eclipse supports generating both keys and you can copy the public key to the 
-  server from within Eclipse. In order to use public key authentication follow 
-  these steps:</p>
-<ol>
-  <li>
-    <p>If you already have a private/public key for the CVS server, simply open the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.jsch.ui.SSHPreferences)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <em class="UILabel">General &gt; Network Connections &gt;&nbsp; SSH2</em></a>
-       preference page and on the <em class="UILabel">General</em> tab add your private key to the list 
-      by selecting the <em class="UILabel">Add Private Key</em> 
-      button. Your key will be used when authenticating.</p>
-  </li>
-  <li>
-    <p>If you don't have a keypair yet, in the preferences page, go to the <em class="UILabel">Key 
-      Management</em> page.</p>
-  </li>
-  <li>
-    <p>Select either a <em class="UILabel">Generate RSA key</em> 
-      (if your server supports version 1 of the protocol) or 
-      <em class="UILabel">Generate DSA key</em> (for version 2).</p>
-  </li>
-  <li>
-    <p>A public key and private key will be generated. The public key
-will be shown in the read-only text area. </p>
-  </li>
-  <li>
-    <p>The next step is to copy the public key to your server. If your
-server is running an OpenSSH server than you can use the 
-<em class="UILabel">Export via sftp</em> action. Otherwise
-you will have to copy and paste the public key into your remote
-~/.ssh/authorized_keys file.</p>
-  </li>
-  <li>
-    <p>Now you have to provide a password for your private key, and
-save
-it on your computer.</p>
-  </li>
-</ol>
-<p>So now that you have your keypairs generated and installed, the next
-time you create a CVS location to the server you shouldn't enter a
-password. When the connection is initialized, you will be prompted for
-the passphrase for your private key. This is the most secure method of
-authentication, as long as your private key is protected with a
-passphrase.</p>
-<p>
-<span style="font-weight: bold;">Note</span>: exporting the public key
-is only supported on OpenSSH enabled SSH servers.</p>
-<h2>Authentication with Passwords</h2>
-<p>
-If your server is configured to support password authentication, then
-you can simply enter your password when you create a CVS repository
-location and that password will be used when authenticating with the
-server. This is the simplest authentication method.<br>
-<br>
-  <span style="font-weight: bold;">Note</span>: To persist login credentials
-  in a safe, encrypted form <a href="../reference/ref-securestorage-start.htm">
-  Secure Storage</a> is used.</p>
-<h2>Pserver over SSH2</h2>
-<p>
-The <span style="font-weight: bold;">pserverssh2</span> connection method allows you to use pserver
-connections to a CVS repository over ssh2 port-forwarding without any
-external ssh2 programs. The SSH2 connection information is encoded in the
-<em class="UILabel">Host</em> field of the repository location: The format is:
-</p>
-<pre>ssh_user@ssh_host#port_number@cvs_host</pre>
-<p>
-where the port_number is only required if the SSH2 host's port is not 22.
-</p>
-
-<h2>Using Proxies</h2>
-
-<p>Both the <span style="font-weight: bold;">extssh</span> and <span style="font-weight: bold;">pserver</span> connection
-methods support the use the proxies specified on the 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.net.NetPreferences)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <em class="UILabel">General &gt; Network Connections</em></a>
-preference page. If a SOCKS proxy is specified, it will be used. Otherwise, the specified SSL proxy will be used. If neither of these
-proxy types are specified or if the host being contacted is in the host exclusion list, the connection will be made directly to the target host.</p>
-       
-
-
-<p><img  alt="Related concepts"
- src="../images/ngrelc.png" border="0"><br>
-<a href="tasks-92.htm">Creating a CVS repository location</a><br>
-<a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img  alt="Related reference"
- src="../images/ngrelr.png" border="0">
-  <br><a href="../reference/ref-net-preferences.htm">Network Connections</a> 
- <br><a href="../reference/ref-47.htm">CVS</a> 
- </p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm
deleted file mode 100644
index 40c34c1..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-cvs-watch.htm
+++ /dev/null

@@ -1,110 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Finding out who's working on what: watch/edit</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Finding out who's working on what: watch/edit</H1>
-<P CLASS="Para">CVS provides a notification scheme which allows you to know if 
-  someone is modifying a file that you care about. This facility is known as <em>watches</em>. 
-  By setting a <em>watch</em> on a file, you can have CVS notify you via email 
-  (or other) if someone else starts to <em>edit</em> this file. </P>
-<p class="Para">There are two parts to CVS watches: <em>watch</em>, and <em>edit</em>. 
-  The first, <em>watch</em>, is how you specify which files you wish to be notified 
-  about. The second, <em>edit</em>, is how you inform the CVS server (and thus 
-  others) that you are about to modify a file.</p>
-<p class="Para"><em>Edit</em> is useful on its own without ever setting up any 
-  watches and lots of people work this way. This is because when you edit a file, 
-  you will be told immediately if someone else is already editing that file. Since 
-  most people just want to know up front that they may have to merge their changes 
-  on commit, <em>edit</em> on its own is sufficient for most. Another advantage 
-  to using just <em>edit</em> is that it doesn't require any administrative changes 
-  to the server, where as <em>watch</em> does. All that <em>watches</em> gives 
-  above this is the email notification that some file you are watching is being 
-  modified.</p>
-<p class="Para">For these reasons, <em>edit</em> is supported natively by Team 
-  CVS where as <em>watch</em> isn't.</p>
-<h2 class="Para">Setting up Watches</h2>
-<p class="Para">As mentioned, you can't set watches in Team CVS. If you are interested 
-  in doing this, you should consult your cvs documentation. In brief though, this 
-  is what's involved:</p>
-<ol>
-  <li>First, you or your CVS administrator will need to modify the CVSROOT/notify 
-    file. Consult the CVS documentation on watches for details on how to configure 
-    this file. </li>
-  <li>Next, you will need to perform a command line &quot;cvs watch add &lt;filename&gt;&quot; 
-    for each file that you wish to watch. If &lt;filename&gt; is a directory name, 
-    then all files within that directory will be watched.</li>
-</ol>
-<h2>Setting up a Project for Watch/Edit</h2>
-<p>Watches and editing are optional in CVS. To use this facility, you must turn 
-  on this option in the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.WatchEditPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; CVS &gt; Watch/Edit</strong></a>
-  preference page. Select &quot;Configure projects to use Watch/Edit on checkout&quot;, accept 
-  the preference dialog, and then checkout your project. All the files in the 
-  project will be checked out read-only. This tells the CVS client which files 
-  are being edited by you and which aren't (writable files are being edited). 
-  If you've already checked out the project before you turned on this option, 
-  you can either check it out again or enable the &quot;Use Watch/Edit for this 
-  project&quot; option on the project's CVS properties page. Either of these operations 
-  will make the files in the project read-only.</p>
-<h2>Editing</h2>
-<p class="Para"></p>
-<p>Although typical CVS clients require you to perform an explicit edit, Team 
-  CVS automatically issues an edit as soon as you start to modify a file. This 
-  support is built deep into Eclipse, so typing in a text editor, performing Java 
-  refactoring, etc., will all issue a CVS edit for you. You can also perform an 
-  explicit edit via the <strong>Team &gt; Edit</strong> context menu on a resource.</p>
-<p>When an <em>edit</em> is issued, you will be informed immediately if someone 
-  is already editing that file. In addition, everyone who is <em>watching</em> 
-  that file will be notified by the CVS server via email etc. Since watches simply 
-  give you email notification, <em>edit</em> without ever setting up watch lists 
-  is still a useful (and popular) workflow.</p>
-<p>If you prefer, you can turn off automatic issuing of edits. This means you 
-  will need to manually perform a Team &gt; Edit for each file you are working 
-  on. To use this work mode, open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.WatchEditPreferencePage)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>Team &gt; CVS &gt; Watch/Edit</strong></a>
-  preference page
-  and enable &quot;Edit the file without informing the server&quot;. </p>
-<p>Finally, you can see the list of editors of a file at any time by selecting 
-  <strong>Team &gt; Show Editors</strong> from the context menu of that file. 
-</p>
-<h2>Unediting</h2>
-<p>Just as you can tell CVS that you are editing a file, there also needs to be 
-  a way of telling CVS that you are no longer editing that file. This is referred 
-  to as <em>unedit</em>. This way, if someone checks the editors list for a file, 
-  they'll know if someone is still working on that file. This happens in one of 
-  two ways:</p>
-<ul>
-  <li>When you commit an edited file, an unedit is automatically issued.</li>
-  <li>If you discover that you want to back out of the changes to a file, you 
-    can explicit unedit the file. In addition to notifying the server, an explicit 
-    unedit will revert the file to its base (i.e. the workspace will then contain 
-    the copy of the file before you started modifying it).</li>
-</ul>
-<p>&nbsp;</p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" > 
-  <br>
-  <a href="../concepts/concepts-cvs-watch.htm">Watch/Edit</a></p>
-<p><a href="../concepts/concepts-26.htm">Team programming with CVS</a> </p>
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" > 
-  <br>
-  <a href="../reference/ref-47.htm">CVS</a> </p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm
deleted file mode 100644
index 195209b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-exttools-running.htm
+++ /dev/null

@@ -1,67 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Running external tools</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Running external tools</H1>
-
-<p>The Workbench provides a mechanism for running tools that are not part of it.
-To configure an external tool:
-</p>
-
-<ol>
-  <li>Click <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Run &gt; External Tools &gt; External Tools...</b></a>.
-  </li>
-  <li>Select the Program configuration</li>
-  <li>Click the <b>New</b> button.</li>
-  <li>Enter a name for your external tool (for example, My External Tool).</li>
-  <li>Click the <b>Browse File System</b> button.</li>
-  <li>Find the tool you want to run (for example, on Windows it is usually a file 
-    with the extension .exe or .bat).</li>
-  <li>(Optional) In the <b>Arguments</b> field enter the necessary arguments 
-    for the tool.</li>
-  <li>(Optional)In the <b>Working directory</b> field enter the working directory 
-    for the tool.</li>
-  <li>Click <b>Run</b>.</li>
-</ol>
-
-<p>These steps create a persisted launch configuration. The newly created configuration will
-appear in the launch history under <b>Run &gt; External Tools</b> and will be available in the
-launch configuration dialog which is opened by clicking
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.externalTools.commands.OpenExternalToolsConfigurations")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>Run &gt; External Tools &gt; External Tools...</b></a>.
-</p>
-
-<p>It is also possible to set up and run an external tool to build a project.
-</p>
-
-<ol>
-  <li>Select the desired project.</li>
-  <li>From its pop-up menu choose <b>Properties</b>.</li>
-  <li>Click <b>Builders</b> from the list, and configure the tool as described above.</li>
-</ol>
-
-<P><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-exttools.htm">External tools</a><br>
-</P>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks" ><br>
-<a href="./tasks-ant-running.htm">Running Ant buildfiles</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm
deleted file mode 100644
index e9ea162..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-importproject.htm
+++ /dev/null

@@ -1,50 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing existing projects</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Importing existing projects</h1>
-
-<p>You can use the Import Wizard to 
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.ui.wizards.import.ExternalProject)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-import an existing project into workspace</a>.
-</p>
-
-<ol>
-  <li>From the main menu bar, select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>File &gt; Import...</b></a>. The Import wizard opens.</li>
-  <li>Select <b>General &gt; Existing Project into Workspace</b> and click <b>Next</b>.</li>
-  <li> Choose either <strong>Select root directory </strong>or <strong>Select 
-    archive file</strong> and click the associated <b>Browse</b> to locate the 
-    directory or file containing the projects.</li>
-  <li>Under <strong>Projects</strong> select the project or projects which you 
-    would like to import.</li>
-  <li>Click <b>Finish</b> to start the import.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/ref-70.htm">Import wizard</a>
-</p>
-
-<p><img border="0" src="../images/ngrelt.png" alt="Related tasks"><br>
-<a href="tasks-55.htm">Importing resources from the file system</a><br>
-<a href="tasks-55bg.htm">Importing resources from a ZIP File</a><br>
-<a href="tasks-57.xhtml">Exporting</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm b/bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm
deleted file mode 100644
index d889bac..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tasks-team-1.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Setting the content type of a file extension</title>
-<meta name="keyword" content="team">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1 CLASS="Head"> Setting the content type of a file extension</H1>
-<P CLASS="Para">CVS repositories distinguish between files that contain ASCII 
-  data and those that do not. For ASCII files, additional helpful functionality 
-  is available. This includes:</P>
-<ul>
-  <li>Proper end of line conversion between the client and the server. This ensures 
-    that a Windows user and a UNIX user can work on the same file without introducing 
-    incompatibilities.</li>
-  <li>Auto merging of conflicts. If a file contains both incoming and outgoing 
-    changes but none on the same line as another, then the file may be automatically 
-    merged when updating.</li>
-</ul>
-<p class="Para">Certain file types invariably contain either ASCII data or binary 
-  data. For example, *.txt files usually contain ASCII data, and *.exe files usually 
-  contain binary data. Eclipse comes with a pre-defined set of file types, which 
-  you may add to or modify.</p>
-<P CLASS="Para">To set the content type associated with a file extension: </P>
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.ui.TextPreferences)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>Team &gt; File Content</b></a> preference page. 
-    This page displays a list of file extensions and content type (ASCII or Binary) 
-    for file extensions whose content type is known.</li>
-  <li> 
-    <p CLASS="Para">To add a file extension, click the <b>Add Extension</b> button and enter 
-      the file extension in the text prompt that appears. Once <b>OK</b> is clicked, 
-      the extension will be added to the list with a content type of ASCII.</p>
-  </li>
-  <li>To change the content type for an existing file extension, select the file 
-    extension entry and click the <b>Change</b> button. This will toggle the type 
-    from ASCII to Binary or vice versa.</li>
-  <li>To remove a file extension, select the file extension entry and click the 
-    <b>Remove</b> button.<br>
-  </li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<br><a href="../concepts/concepts-26.htm">Team programming with CVS</a>
-</p>
-
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" >
-<br><a href="../reference/ref-47.htm">CVS</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm b/bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm
deleted file mode 100644
index 39e06f3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/timpandexp.htm
+++ /dev/null

@@ -1,65 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Importing and exporting preferences</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<h1>Importing and exporting preferences</h1>
-<p CLASS="Para">Preference files can be both imported to and exported from the 
-  Workbench allowing you to easily share individual or group preferences. </p>
-<p CLASS="Para">The Import wizard can be used to import preferences from the local 
-  file system to the Workbench.</p>
-<p CLASS="Para">To import a preference file:</p>
-<ol>
-  <li>Select 
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>File &gt; Import</strong></a>.</li>
-  <li>In the Import wizard select <strong>General &gt; Preferences</strong> and click <strong>Next</strong>.</li>
-  <li>Click <strong>Browse...</strong> and locate the Preferences file on the 
-    local file system.</li>
-  <li>Select one of the following: 
-    <ul>
-      <li><strong>Import all</strong> to accept all of the preferences defined 
-        in the file.</li>
-      <li><strong>Choose specific preferences to import</strong> to select only 
-        specified preferences defined in the file.</li>
-    </ul>
-  </li>
-  <li>Click <strong>Finish</strong>.</li>
-</ol>
-<p CLASS="Para">&nbsp;</p>
-<p CLASS="Para">The Export wizard can be used to export preferences from the Workbench 
-  to the local file system.</p>
-<p CLASS="Para">To export a preference file:</p>
-<ol>
-  <li>Select
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <strong>File &gt; Export</strong></a>.</li>
-  <li>In the Export wizard select <strong>General &gt; Preferences</strong> and click <strong>Next</strong>.</li>
-  <li>Select one of the following: 
-    <ul>
-      <li><strong>Export all</strong> to add all of the preferences to the file.</li>
-      <li><strong>Choose specific preferences to export</strong> to add only specified 
-        preferences to the file.</li>
-    </ul>
-  </li>
-  <li>Click <strong>Browse...</strong> and locate the preferences file on the 
-    local file system.</li>
-  <li>Click <strong>Finish</strong></li>
-</ol>
-<p><strong>Note:</strong> If no changes have been made to the original preference 
-  settings the preferences file will be empty.</p>
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm b/bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm
deleted file mode 100644
index 61ac5c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tkeybindings.htm
+++ /dev/null

@@ -1,32 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Changing the key bindings</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Changing the key bindings</H1>
-<p>
-The function of the keyboard can be extensively customized in Eclipse.
-</p>
-<p>
-Use the
-<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-<img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-<b>General &gt; Keys</b></a> preference page to 
-<a href="../concepts/accessibility/keyboardshortcuts.htm">assign key sequences</a> to many of the commands in Eclipse. </p>
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/accessibility/keyboardshortcuts.htm">Keys</a><br>
-<a href="../concepts/accessibility/navigation.htm">Navigating the user interface by using the keyboard</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm b/bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm
deleted file mode 100644
index 633c344..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/topenmode.htm
+++ /dev/null

@@ -1,55 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Controlling single and double click behavior</title>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Controlling single and double click behavior</H1>
-
-<p>You can control how the Workbench responds to single and double clicks. To do this:
-</p>
-
-<ol>
-  <li>Open the
-  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-  <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-  <b>General</b></a> preference page.</li>
-  <li>Select the behavior you want to change from the <b>Open mode</b> group.</li>
-  <li>Click <b>OK</b>.</li>
-</ol>
-
-<p>The effect of these selections varies by view. For example, in one of the navigation 
-  views: </p>
-
-<dl>
-<dt>Double click</dt>
-<dd>Will cause a single click on a resource to select it, and a 
-double click to open it in an editor.</dd>
-<dt>Single click</dt>
-<dd>Will cause a single click on a resource to both select it and
-immediately open an editor on it.</dd>
-</dl>
-
-<p>The checkboxes under the <b>Single click</b> radio button further refine
-the single click behavior. Checking <b>Select on hover</b> will cause the resource
-to be selected if you hover over it with the mouse. Checking <b>Open when using
-arrow keys</b> will cause the resource to be opened if you use the arrow keys to
-navigate to it.
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-10.htm">Workbench</a><br>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm b/bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm
deleted file mode 100644
index 8f42d0d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/tquickfix.htm
+++ /dev/null

@@ -1,43 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Automatically fixing problems</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Automatically fixing problems</H1>
-
-<P>Problems displayed in the Problems view may offer a <b>Quick Fix</b> menu option 
-  in the context menu. Selecting this menu option will present one or more possible 
-  fixes that can be automatically applied for you. </P>
-
-<P>Certain Java problems may be resolved using the Quick Fix feature. For example, 
-  a missing import statement in a Java file will result in a Quick Fix suggestion 
-  to add the import statement or change the type name to a name that is already 
-  imported. </P>
-
-<ol>
-  <li>In the Problems view, right-click the task you want to Quick Fix.</li>
-  <li>Select <b>Quick Fix</b> from the pop-up menu.</li>
-  <li>Choose from one of the suggested fixes.</li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" ><br>
-<a href="../concepts/concepts-11.htm">Markers</a><br>
-<a href="../concepts/ctskview.htm">Tasks view</a>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference" ><br>
-<a href="../reference/ref-31.htm">Tasks view</a>
-</p>
-
-
-
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm b/bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm
deleted file mode 100644
index 663f390..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/ttoolbars.htm
+++ /dev/null

@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"><html lang="en">
-<HEAD>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2005. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
-<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
-<title>Rearranging the main toolbar</title>
-</HEAD>
-
-<BODY BGCOLOR="#ffffff">
-<H1>Rearranging the main toolbar</H1>
-<p>
-You can rearrange sections of the main toolbar. Toolbar sections are divided
-by a thin vertical line.
-</p>
-
-<ol>
-  <li> Make sure the toolbar is unlocked. The toolbar is unlocked if it has thick 
-    vertical bars next to the thin vertical toolbar dividers.<br>
-    <img src="../images/Image90_locked_toolbar.png" alt="Locked toolbar" border="0" > 
-    <img src="../images/Image90_unlocked_toolbar.png" alt="Unlocked toolbar" border="0" ><br>
-    If it is locked, unlock the toolbar by right clicking the toolbar and selecting 
-    the <b>Lock the Toolbars</b> menu item. </li>
-  <li> Grab the section of the toolbar you want to rearrange by moving the mouse 
-    over the thick vertical line on the left side of the desired segment. The 
-    mouse cursor changes its shape to indicate that you can click to move the 
-    toolbar section. </li>
-  <li> Click and hold the left mouse button to grab the toolbar section. </li>
-  <li> Move the section left and right or up and down. Release the mouse button 
-    to place it in the new location. </li>
-  <li> To prevent accidental changes to the toolbar lock it again by right clicking 
-    the toolbar and selecting the <b>Lock the Toolbars</b> menu item. </li>
-</ol>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts" >
-<a href="../concepts/concepts-18.htm"><br>Toolbars</a>
-</p>
-
-
-
-</BODY>
-</HTML>

diff --git a/bundles/org.eclipse.platform.doc.user/tasks/welcome.htm b/bundles/org.eclipse.platform.doc.user/tasks/welcome.htm
deleted file mode 100644
index bb9376d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tasks/welcome.htm
+++ /dev/null

@@ -1,37 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2006. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"> </script>
-<title>Customizing Welcome</title>
-</head>
-<body>
-
-<h2>Customizing Welcome</h2>
-
-<p>
-The welcome appearance can be customized via the
-"customize page" button above the welcome page. This opens a customize dialog which allows you to select one of the pre-defined
-themes, which affects the overall look of the welcome. You can also select which
-pages will be displayed, and the visibility, layout, and priority of the items
-within each page.
-</p>
-
-<p>
-For more information about customizing welcome, see the <a href="../reference/welcome_preferences.htm">reference documentation</a> for the
-customize welcome dialog.
-</p>
-
-<p><img border="0" src="../images/ngrelc.png" alt="Related concepts"><br>
-<a href="../concepts/welcome.htm">Welcome</a><br>
-</p>
-
-<p><img border="0" src="../images/ngrelr.png" alt="Related reference"><br>
-<a href="../reference/welcome_preferences.htm">Customize Welcome Dialog</a><br>
-</p>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png b/bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png
deleted file mode 100644
index a2245a6..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/annotations-preferences.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png b/bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png
deleted file mode 100644
index 6749199..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/backgroundpref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png b/bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png
deleted file mode 100644
index a9d090b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/backward_nav.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/cap-pref.png b/bundles/org.eclipse.platform.doc.user/tips/images/cap-pref.png
deleted file mode 100644
index 79ca309..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/cap-pref.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif b/bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif
deleted file mode 100644
index f988003..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/changelog-obj.gif
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png b/bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png
deleted file mode 100644
index 57a1303..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/collapse-all.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png b/bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png
deleted file mode 100644
index d84936e..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/compare-merge-button.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png b/bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png
deleted file mode 100644
index 54f37d3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/compare-showancestor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/detachview1.png b/bundles/org.eclipse.platform.doc.user/tips/images/detachview1.png
deleted file mode 100644
index 8757c2f..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/detachview1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/detachview2.png b/bundles/org.eclipse.platform.doc.user/tips/images/detachview2.png
deleted file mode 100644
index 41c9f99..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/detachview2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png b/bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png
deleted file mode 100644
index 30b4eb0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/editor-tiles.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png b/bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png
deleted file mode 100644
index 8210042..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/fastview-drag.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_1.png b/bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_1.png
deleted file mode 100644
index 255abf1..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_2.png b/bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_2.png
deleted file mode 100644
index 5cfd5fe..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/help_bookmarks_2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/help_external_window.png b/bundles/org.eclipse.platform.doc.user/tips/images/help_external_window.png
deleted file mode 100644
index 0b302da..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/help_external_window.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/help_show_topic.png b/bundles/org.eclipse.platform.doc.user/tips/images/help_show_topic.png
deleted file mode 100644
index ef9c67c..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/help_show_topic.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png b/bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png
deleted file mode 100644
index 9b41be4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/key-assist.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png b/bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png
deleted file mode 100644
index b159316..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/key-bindings.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png b/bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png
deleted file mode 100644
index d605a1b..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/keyboard-shortcut.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/keycompletions.png b/bundles/org.eclipse.platform.doc.user/tips/images/keycompletions.png
deleted file mode 100644
index 32dedb4..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/keycompletions.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png b/bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png
deleted file mode 100644
index 2643256..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/last_edit_pos.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/line-delimiter.png b/bundles/org.eclipse.platform.doc.user/tips/images/line-delimiter.png
deleted file mode 100644
index fdac3f5..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/line-delimiter.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png b/bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png
deleted file mode 100644
index 4ceb436..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/link-with-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png b/bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png
deleted file mode 100644
index 4998f95..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/mini-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png b/bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png
deleted file mode 100644
index 9531a16..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/path-vars.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png b/bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png
deleted file mode 100644
index ea05d43..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/pb-context-menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png b/bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png
deleted file mode 100644
index 79210fc..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/perspective-other.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png b/bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png
deleted file mode 100644
index bb31648..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/pin-editor.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/props-view.png b/bundles/org.eclipse.platform.doc.user/tips/images/props-view.png
deleted file mode 100644
index 9a60f19..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/props-view.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/quickaccess.png b/bundles/org.eclipse.platform.doc.user/tips/images/quickaccess.png
deleted file mode 100644
index 3a43c07..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/quickaccess.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png b/bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png
deleted file mode 100644
index f2e1769..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/quickdiff-hover.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png b/bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png
deleted file mode 100644
index 60a710d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/restore-local.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/show-in.png b/bundles/org.eclipse.platform.doc.user/tips/images/show-in.png
deleted file mode 100644
index f40c2f3..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/show-in.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png b/bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png
deleted file mode 100644
index 3eea66d..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/images/team-project-set.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/tips/platform_tips.html b/bundles/org.eclipse.platform.doc.user/tips/platform_tips.html
deleted file mode 100644
index e9621d0..0000000
--- a/bundles/org.eclipse.platform.doc.user/tips/platform_tips.html
+++ /dev/null

@@ -1,1004 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-
-<head>
-
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
-
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-<title>Platform Tips and Tricks</title>
-</head>
-
-<body>
-
-<h1>Tips and Tricks</h1>
-
-<p>The following tips and tricks give some helpful ideas for increasing your
-productivity. They are divided into the following sections:</p>
-<ul>
-<li><a href="#Workbench">Workbench</a></li>
-<li><a href="#Editing">Editing</a></li>
-<li><a href="#Ant">Ant</a></li>
-<li><a href="#Help">Help</a></li>
-<li><a href="#CVS">Team - CVS</a></li>
-</ul>
-
-<h3><a name="Workbench">Workbench</a></h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670">
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Now, where was I?</b></td>
-    <td width="80%" valign="top" align="left">Workbench editors keep a navigation 
-      history. If&nbsp; you open a second editor while you're editing, you 
-      can press <b>Navigate &gt; Backward</b>  (<b>Alt+Left Arrow</b>, or the <img border="0" src="images/backward_nav.png" alt="Left arrow icon" >
-      back arrow 
-      on the workbench toolbar) to go back to the last editor. This makes working with several open editors a whole lot easier.</td>
-  </tr>
-    
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Ctrl+3 quick access</b></td>
-    <td width="80%" valign="top" align="left">You can quickly find all manner of contributions with the <b>Ctrl+3</b> binding including (but not limited to) open editors, available perspectives, views, preferences, wizards, and commands.
-    Simply start typing the name of the item you wish to invoke and we will attempt to find something in the Workbench that matches the provided string.
-    <p><img src="images/quickaccess.png" alt="Quick Access dialog" > </p>
-    </td>    
-  </tr>
-  
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Ctrl+E editor list</b></td>
-    <td width="80%" valign="top" align="left">You can quickly switch editors using 
-      the <b>Ctrl+E</b> keybinding which opens a list of all open editors. The list supports 
-      type-ahead to find the editor as well as allows you to close editors using 
-      a popup menu or the Delete key. </td>
-  </tr>
- 
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Like to start afresh each session?</b></td>
-    <td width="80%" valign="top" align="left">A setting on the 
-    
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Editors</strong></a>
-
-      preference page closes all open editors automatically whenever 
-      you exit. This makes start-up cleaner and a bit faster.</td>
-  </tr>
-
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Prevent in-place OLE editors</b></td>
-    <td width="80%" valign="top" align="left">By default, on Windows, OLE applications like Microsoft Word or Excel open as in-place editors inside of Eclipse.
-    You can force OLE applications to open as stand-alone applications by unchecking the "Allow in-place system editors" option on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Editors</strong></a>
-    preference page.</td>
-  </tr>
-  
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>Opening editors using drag and 
-      drop</b></td>
-    <td width="80%" valign="top" align="left">You can open an editor on an item 
-      by dragging the item from a view like the Project Explorer or Package Explorer 
-      and dropping it over the editor area.</td>
-  </tr>
-     <tr> 
-    <td width="20%" valign="top" align="left"><b>Tiling the editor work area</b></td>
-    <td width="80%" valign="top" align="left">You can use drag and drop to modify 
-      the layout of your editor work area. Grab an editor tab and drag it to the 
-      edge of the editor work area. The arrow dock icons (e.g., <img src="../images/drop_left_source.png" align="texttop" border="0" alt="Left arrow icon">) 
-      indicate which way the editor work area will split. 
-      <p><img src="images/editor-tiles.png" alt="Tiled editor work area"  border="0"></p></td>
-  </tr>
-     <tr> 
-    <td width="20%" valign="top" align="left"><b>Splitting an editor</b></td>
-    <td width="80%" valign="top" align="left">You can open a second editor instance
-    via <b>Window &gt; New Editor</b> or by selecting <b>New Editor</b>
-    from the editor tab's context menu. Use the previous tip to view the new editor
-    aside the first one.</td>
-  </tr>
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>Open editors with a single click</b></td>
-    <td width="80%" valign="top" align="left">Use the Open mode setting on the 
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General</strong></a>
-      
-      preference page to activate single click opening for editors. 
-      In single click mode, a single click on a file in the Project Explorer view (and 
-      similar views) selects and immediately opens it. </td>
-  </tr>
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>Collapsing all open items</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Collapse All</b> button 
-      on the toolbar of the Project Explorer view (and similar views) to collapse all 
-      expanded project and folder items. 
-      <p><img src="images/collapse-all.png" alt="Collapse all button on navigator toolbar" > </p> </td></tr>
-    <tr> 
-    <td valign="top" align="left" width="20%"> <strong>Global find/replace</strong> 
-    </td>
-    <td valign="top" align="left" width="80%"> Use
-    
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.search.ui.openFileSearchPage")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Search &gt; File</strong></a>
-    
-      from the main menu to specify the text that you want to replace and the scope
-      in which you want to replace it. Then press <b>Replace...</b>.</td>
-  </tr>
-  <TR>
-		<TD width="20%" valign="top" align="left"><B>Replace from Search view</B>
-		</TD>
-		<TD width="80%" valign="top" align="left">You can replace the matches in the files by using <B>Replace...</B> or <B>Replace
-			Selected...</B> from the context menu in the Search view.</TD>
-  </TR>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Linking view to current open 
-      editor</b></td>
-    <td width="80%" valign="top" align="left"> <p>The resource Project Explorer view 
-        (and similar views) is not tightly linked to the currently open editor 
-        by default. This means that closing or switching editors does not change 
-        the selection in the Project Explorer view. Toggling the <b>Link with Editor</b> 
-        button in the Project Explorer view toolbar ties the view to always show the 
-        current file being edited. </p>
-      <p><img src="images/link-with-editor.png" alt="Project Explorer linked with editor"  border="0"></p></td>
-  </tr>
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>Manual editor / view 
-      synchronization</b></td>
-    <td width="80%" valign="top" align="left">The <b>Navigate &gt; Show In</b> 
-      command provides a uniform way to navigate from an open editor to a view 
-      showing the corresponding file (e.g., in the resource Project Explorer view), or 
-      from a file selected in one view to the same file in a different view (e.g., 
-      from the resource Project Explorer view to the Packages Explorer view).
-      <p>Typing <b>Alt+Shift+W</b> opens a shortcut menu with the available view
-      targets.</p>
-      <p><img src="images/show-in.png" alt="Shortcut menu for Show in command"  border="0"></p>
-    </td>
-  </tr>
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>Quick navigation between views, 
-      editors and perspectives</b></td>
-    <td width="80%" valign="top" align="left">A look at the <b>Window &gt; Navigation</b> 
-      menu reveals a number of ways to quickly navigate between the various views, 
-      editors, perspectives, and menus in the workbench. These commands have keyword 
-      accelerators such as <b>Ctrl+F6</b> for switching between editors, <b>Ctrl+F7</b> 
-      for switching between views, <b>Ctrl+F8</b> for switching between perspectives, 
-      and <b>F12</b> for activating the editor. 
-      <p><img src="images/keyboard-shortcut.png" alt="Navigation shortcuts menu"  border="0"></p> 
-      <p>To directly navigate to a particular view you can define a keyboard shortcut 
-        to a view via the <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Keys</strong></a></p></td>
-  </tr>
-  <tr id="switch-editors">
-    <td width="30%" valign="top" align="left">
-        <b>Switch editors and multi-page editors</b>
-    </td>
-    <td width="70%" valign="top">
-        You can use <b>Ctrl</b>+<b>PageDown</b> and <b>Ctrl</b>+<b>PageUp</b> to
-        activate the next or previous editor tab, even in multi-page editors. To switch between pages of a multi-page
-        editor, use <b>Alt</b>+<b>PageDown</b> and <b>Alt</b>+<b>PageUp</b>.
-    </td>
-  </tr>
-
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>Pinning editors</b></td>
-    <td width="80%" valign="top" align="left">When the <b> Close editors automatically</b> 
-      preference is active (found on the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Editors)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Editors</strong></a>
-
-      preference page), you can stop an editor from being closed by using the
-      <b>Pin Editor</b> button which appears in the workbench toolbar. 
-      <p><img src="images/pin-editor.png" alt="Pin editor button"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Reordering editor tabs</b></td>
-    <td width="80%" valign="top" align="left">You can rearrange the order of open 
-      editors by using drag and drop. Grab the editor tab and drag it to the position 
-      you want the editor to appear. When positioning editors, the stack icon 
-      <img src="../images/drop_stack.png"  align="texttop" border="0" alt="Stack icon"> 
-      indicates a valid spot to drop.</td>
-  </tr>
-
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Middle mouse button closes tabs</b></td>
-    <td width="80%" valign="top" align="left">You can click on a view or editor tab with your middle mouse button to close
-    it. If you do not have a middle mouse button, try clicking on the scroll wheel if you have one.</td>
-  </tr>
-  
-     <tr> 
-    <td width="20%" valign="top" align="left"><b>Minimizing views and editors</b>
-    </td>
-    <td width="80%" valign="top" align="left">Running out of space? Try minimizing 
-      your unused views to reclaim screen real-estate. Each view stack contains 
-      a minimize icon along side the maximize icon. 
-      <p><img src="images/mini-view.png" alt="Minimized View Stack"  border="0" align="left"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Maximizing views and editors</b></td>
-    <td width="80%" valign="top" align="left">You can maximize a view or editor 
-      by double-clicking on the view's title bar or the editor's tab. Double-click 
-      again to restore it to its usual size.</td>
-  </tr>
-   <tr>
-    <td width="20%" valign="top" align="left"><b>Managing screen real estate 
-      with fast views</b></td>
-    <td width="80%" valign="top" align="left">Use fast views to free up screen 
-      real estate while keeping views easily accessible. Clicking on the icon 
-      for a fast view temporarily reveals it over top of the other views. The 
-      fast view retracts as soon you click outside of it. The <b>Fast View</b> 
-      command in the view's system menu toggles whether it is a fast view. You 
-      can also create a fast view by dragging a view onto the Fast View Bar 
-      in the bottom left hand corner.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Fast views and the perspective 
-      bar</b>
-     </td>
-    <td width="80%" valign="top" align="left">The fast view and perspective bars 
-      may be docked in different locations, independent of one 
-      another. 
-      <p>By default the Perspective Bar is located in the upper right hand corner 
-        of the screen. It may also be docked on the top left, under the main toolbar 
-        or to the far left. It may be moved via the perspective bar context menu 
-        or via the
-        
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-        <strong>General &gt; Appearance</strong></a>
- 
-        preference page. </p>
-      <p><img src="images/pb-context-menu.png" alt="Perspective Bar Context Menu"  border="0"></p>
-      <p>By default the Fast View Bar is located in the bottom left hand corner 
-        of the screen. Like the Perspective Bar, it may be docked elsewhere. This 
-        may be done by dragging the area to either the left or right side of the 
-        screen (or back to the bottom if it is already in one of these positions).</p> 
-      <p><img src="images/fastview-drag.png" alt="Fast View Area"  border="0"></p></td>
-  </tr>
-     <tr> 
-    <td width="20%" valign="top" align="left"><b>Detached views</b>
-    </td>
-    <td width="80%" valign="top" align="left">It's possible to detach a view
-          so that it can be placed wherever desired, including over another Eclipse 
-          window.
-        <p>Right-click on the view to be moved and select <b>Detached</b> from the menu.
-    (Alternatively, drag the view by its tab to detach the view from its position in the perspective.)</p>
-        <p><img src="images/detachview1.png" alt="Screenshot of the context menu's 'Detach' option"></p>
-        <p>Then, place the view where you choose. You can also drag and drop other views into the same 
-          window.</p> 
-        <p><img src="images/detachview2.png" alt="Screenshot of the floating view"> </p>
-       <p>To return the view to the workbench window, use the view tab context menu's <b>Detached</b> function again.
-    (Alternatively, drag the view by its tab.)</p></td>
-  </tr>
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>Restoring a perspective's layout</b></td>
-    <td width="80%" valign="top" align="left">Rearranging and closing the views 
-      in a perspective can sometimes render it unrecognizable and hard to work 
-      with. To return it to a familiar state, use
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.resetPerspective")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Window &gt; Reset Perspective</strong></a>.
-    </td>
-  </tr>
-    <tr> 
-    <td width="20%" valign="top" align="left"><b>User customizable<br>
-      key bindings</b></td>
-    <td width="80%" valign="top" align="left">If you find yourself repeatedly 
-      doing some command, you might be able to streamline things by assigning 
-      a key sequence to trigger that command. Assigning new key bindings, and 
-      viewing existing bindings, is done from the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Keys</strong></a>
-      preference page. 
-      <p><img src="images/key-bindings.png" alt="Key bindings preference dialog"></p></td>
-  </tr>
-   <tr> 
-      <td width="20%" valign="top" align="left"><b>View all 
-          keyboard shortcuts</b></td>
-      <td width="80%" valign="top" align="left">While working with your favorite editors and 
-        views in Eclipse, just press <b>Ctrl+Shift+L</b> to see a full list of the currently 
-        available key bindings. This is a great way to learn what is available 
-        in the UI and to speed up your productivity by learning more key bindings. 
-        This information is also available in the improved
-        
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Keys)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-        <strong>General &gt; Keys</strong></a>
-        
-        preference page.
-        <p><img border="0" src="images/keycompletions.png" alt="Screenshot of keybindings" ></p></td>
-    </tr>
-      <tr> 
-    <td width="20%" valign="top" align="left"><b>Key binding assistance</b></td>
-    <td width="80%" valign="top" align="left">Eclipse supports key bindings 
-        that contain more than one key stroke. Examples of such key bindings are 
-        <b>Ctrl+X S</b> (<b>Save</b> in the Emacs key configuration) or <b>Alt+Shift+Q Y</b> 
-        (<b>Show View (View: Synchronize)</b> in the Default key configuration). It is hard 
-        to learn these keys, and it can also be hard to remember them if you don't 
-        use them very often. If you initiate such a key sequence and wait a second, a little pop-up showing 
-        you the possible completions will appear.
-      <p><img src="images/key-assist.png" alt="Key Assist"  border="0"></p>
-    </td>
-  </tr>
-   <tr> 
-    <td width="20%" valign="top" align="left"><b>Customizing toolbar and menu 
-      bar</b></td>
-    <td width="80%" valign="top" align="left">You can customize which items appear 
-      on the main toolbar and menu bar using the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Window &gt; Customize Perspective</strong></a>
-      
-      command. 
-      <p><img src="images/perspective-other.png" alt="Customizing toolbar and menu bar"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Restoring deleted resources</b></td>
-    <td width="80%" valign="top" align="left">Select a container resource and 
-      use <b>Restore from Local History</b> to restore deleted files. You can 
-      restore more than one file at one time. 
-      <p><img src="images/restore-local.png"  border="0" alt="Restore from local history dialog" align="left"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Faster workspace navigation</b></td>
-    <td width="80%" valign="top" align="left">
-    
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.navigate.openResource")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Navigate &gt; Open Resource...</strong></a>
-
-      (<b>Ctrl+Shift+R</b>) brings up a dialog that allows you to quickly locate and 
-      open an editor on any file in the workspace.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Quickly find a resource</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Navigate &gt; Go To &gt; 
-      Resource</b> command to quickly find a resource. If the <b>Go To &gt; Resource</b> 
-      command does not appear in your perspective, you can add it by selecting 
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Window &gt; Customize Perspective</strong></a>,
-      
-      then <b>Other &gt; Resource Navigation</b>.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Copying and moving resources</b></td>
-    <td width="80%" valign="top" align="left">You can drag and drop files and 
-      folders within the Project Explorer view to move them around. Hold down the <b>Ctrl</b> 
-      key to make copies.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Importing files</b></td>
-    <td width="80%" valign="top" align="left">You can quickly import files and 
-      folders into your workspace by dragging them from the file system (e.g., 
-      from a Windows Explorer window) and dropping them into the Project Explorer view. 
-      The files and folder are always copied into the project; the originals are 
-      not affected. Copy and paste also work.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Exporting files</b></td>
-    <td width="80%" valign="top" align="left">Dragging files and folder from the 
-      Project Explorer view to the file system (e.g., to a Windows Explorer window) exports 
-      the files and folders. The files and folder are always copied; workspace 
-      resources are not affected. Copy and paste also work.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Workspace project management</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Project &gt; Close Project</b> 
-      command to manage projects within your workspace. When a project is closed, 
-      its resources are temporarily &quot;offline&quot; and no longer appear in 
-      the Workbench (they are still sitting in the local file system). Closed 
-      projects require less memory. Also, since they are not examined during builds, 
-      closing a project can improve build times. </td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Describing your configuration</b></td>
-    <td width="80%" valign="top" align="left">When reporting a problem, it's often 
-      important to be able to capture details about your particular setup. The 
-      <b>Installation Details</b> button on the
-
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.help.aboutAction")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Help &gt; About <i>Product</i></strong></a>
-      
-      dialog opens a dialog containing pages that describe different aspects of
-      your installation.  The <b>Configuration</b> page displays a file 
-      containing various pieces of information about your 
-      setup, including plug-in versions, preference settings, and the contents 
-      of the internal log file. You can copy and save this information, and attach the saved file to your 
-      problem report.</td>
-  </tr>
- <tr> 
-    <td width="20%" valign="top" align="left"><b>Deleting completed tasks</b></td>
-    <td width="80%" valign="top" align="left">Use the <b>Delete Completed Tasks</b> 
-      command in the Task view context menu to remove all completed tasks from 
-      the Tasks view. This is more convenient than individually selecting and 
-      deleting completed tasks.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Viewing resource properties</b></td>
-    <td width="80%" valign="top" align="left">Use the Properties view
-
-      (<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.ui.views.PropertySheet)")'><img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Window &gt; Show View &gt; Properties</strong></a>)
-    
-      when viewing the properties for many 
-      resources. Using this view is faster than opening the Properties dialog 
-      for each resource. 
-      <p><img src="images/props-view.png" alt="Resource properties dialog"  border="0"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Extra resource information</b></td>
-    <td width="80%" valign="top" align="left">Label decorations are a general 
-      mechanism for showing extra information about a resource. Use the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Decorators)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Appearance &gt; Label Decorations</strong></a>
-      
-      preference page to select which of the available 
-      kinds of decorations you want to see.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Filtering resources</b></td>
-    <td width="80%" valign="top" align="left">Most views that show resources 
-      support filtering of their items. You control which items are visible by 
-      applying filters or working sets. The commands to filter are found 
-      in the view menu.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Quick fix in Tasks view</b></td>
-    <td width="80%" valign="top" align="left">You can use the <b>Quick Fix</b> 
-      command in the Tasks view to suggest an automatic fix for the selected item. 
-      The <b>Quick Fix</b> command is only enabled when there is a suggested fix.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Creating path variables</b></td>
-    <td width="80%" valign="top" align="left">When creating a linked folder or 
-      file, you can specify the target location relative to a path variable. By 
-      using path variables, you can share projects containing linked resources 
-      without requiring team members to have exactly the same path in the file 
-      system. You can define a path variable at the time you create a linked resource, 
-      or via the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.LinkedResources)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Workspace &gt; Linked Resources</strong></a>
-      
-      preference page. 
-      <p><img src="images/path-vars.png" alt="Path variables dialog"></p></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"> <strong>Comparing zip archives 
-      with each other or with a folder</strong> </td>
-    <td valign="top" align="left" width="80%"> Select two zip archives or one 
-      archive and a folder in the resource Project Explorer view and choose <strong>Compare 
-      With &gt; Each Other</strong> from the view's popup menu. Any differences 
-      between the two inputs are opened in a Compare editor. The top pane shows 
-      all the archive entries that differ. Double clicking on an item performs 
-      a content compare in the bottom pane. 
-      <p> This works in any context where a file comparison is involved. So if 
-        a CVS Synchronize operation lists an archive in the resource tree, you 
-        can double click on it in order to drill down into changes within the 
-        archive.</p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Switch workspace</b>
-    </td>
-    <td width="80%" valign="top" align="left">Instead of shutting down eclipse and restarting 
-    	with a different workspace you can instead use
-    	
-    	<a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.openWorkspace")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-        <strong>File &gt; Switch Workspace</strong></a>.  From here you can either open previous workspaces 
-        directly from the menu or you can open the workspace chooser dialog to choose a new one.
-    	
-      <p>When you change certain preferences that require 
-        a restart to take effect (such as the
-        
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Views)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-        <strong>General &gt; Appearance</strong></a>
-        
-        preferences), use <b>File &gt; Restart</b>.</p>
-    </td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left"><strong>Always run in background</strong>
-    </td>
-    <td valign="top" align="left">Many operations can be optionally 
-        run in the background so that you can continue working while they complete.
-      <p><img src="../images/res_build.png" alt="Progress dialog with Run in background button"></p>
-      <p>Click <b>Always run in background</b> or toggle this on the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General</strong></a>
-      
-      preference page so that you never get the initial dialog for these operations.</p>
-      <p><img src="images/backgroundpref.png" alt="Always run in background preference" ></p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Disabling unused capabilities</b></td>
-    <td width="80%" valign="top" align="left">If there are parts of the Eclipse 
-        Platform that you never use (for instance, you don't use CVS repositories 
-        or you don't develop Plug-ins) it's possible that you can disable them 
-        from the UI entirely. Segments of the Workbench that may be filtered can 
-        be found in the
-        
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.sdk.capabilities)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-        <strong>General &gt; Capabilities</strong></a>
-        
-        preference page. By disabling capabilities you are able to hide views,
-        perspectives, preference pages and other assorted contributions.
-	    
-      <p><img src="images/cap-pref.png" alt="Capabilities Preference Page"></p>
-    </td>
-  </tr>  
-  </table>
-
-<h3><a name="Editing">Editing</a></h3>
-<table border="1" cellpadding="10" cellspacing="0" width="670">
-  <tr>
-	<td valign="top" align="left" width="20%">
-		<b>Finding a string incrementally</b></td>
-    <td valign="top" align="left" width="80%">
-        Use <b>Edit &gt; Incremental Find Next (Ctrl+J)</b> or <b>Edit &gt; Incremental Find Previous
-        (Ctrl+Shift+J)</b>
-        to enter the incremental find mode, and start typing the string to match.
-        Matches are found incrementally as you type.
-        The search string is shown in the status line. Press <b>Ctrl+J</b> or
-        <b>Ctrl+Shift+J</b> to go to the next or previous match. Press <b>Enter</b> or <b>Esc</b> to
-        exit incremental find mode.
-	</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Go to last edit location</b></td>
-    <td width="80%" valign="top" align="left"><b>Navigate &gt; Go
-      to Last Edit Location (Ctrl+Q)</b> takes you back to
-      the place where you last made a change. A corresponding button marked <img border="0" src="images/last_edit_pos.png" alt="Go to last edit position icon" >
-      is shown in the toolbar. If this toolbar button does not appear in your perspective, you can 
-    add it by selecting
-    
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.customizePerspective")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <strong>Window &gt; Customize Perspective</strong></a>,
-    
-    then <b>Other &gt; Editor Navigation</b>.</td>
-  </tr>
-	<TR>
-		<TD width="20%" valign="top" align="left">
-      <B>Shortcuts for manipulating lines</B>
-      </TD><TD width="80%" valign="top">
-      
-			All text editors based on the
-			Eclipse editor framework support editing functions, including
-			moving lines up or down (<b>Alt+Arrow Up</b> and <b>Alt+Arrow Down</b>),
-			copying lines (<b>Ctrl+Alt+Arrow Up</b> and <b>Ctrl+Alt+Arrow Down</b>), inserting
-			a new line above or below the current line (<b>Ctrl+Shift+Enter</b> and
-			<b>Shift+Enter</b>), and converting to lowercase or uppercase (<b>Ctrl+Shift+Y</b>
-			and <b>Ctrl+Shift+X</b>).
-			</TD>
-		
-	</TR>
-		<TR>
-			<TD width="20%" valign="top" align="left"><B>Quick Diff: seeing what has changed as you edit</B>
-			</TD>
-			
-    <TD width="80%" valign="top"> Quick Diff provides color-coded change indication 
-      while you are typing. It can be turned on for text editors using either 
-      the ruler context menu, <b>Ctrl+Shift+Q</b> or for all new editors on the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.QuickDiff)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Editors &gt; Text Editors &gt; Quick Diff</strong></a>
-      
-      preference page. The 
-      colors show additions, deletions, and changes to the editor buffer as compared 
-      to a reference, for example, the contents of the file on disk or its latest 
-      CVS revision. 
-      <P><img src="images/quickdiff-hover.png"  alt="Quick Diff"></P>
-			<P>When the mouse cursor is placed over a change in the vertical
-			ruler, a hover displays the original content, which can be restored using the ruler's context
-			menu. The context menu also allows you to enable/disable Quick Diff.</P></TD>
-		</TR>
-		<TR>
-			<TD width="20%" valign="top" align="left"><b>Customizing the presentation of 
-      annotations</b></TD>
-			
-    <TD width="80%" valign="top"> You can customize the presentation of annotations 
-      in editors on the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.editors.preferencePages.Annotations)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>General &gt; Editors &gt; Text Editors &gt; Annotations</strong></a>
-      
-      preference page: 
-      <P><img src="images/annotations-preferences.png" alt="Annotations preference page" title="Annotations Preference Page">
-</P>
-			</TD>
-		</TR>
- 
- 
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Next / previous navigation</b></td>
-    <td width="80%" valign="top" align="left">You can use <b>Ctrl+.</b> and <b>Ctrl+,</b> to 
-      navigate to the next or previous search match, editor error, or compare 
-      difference. These are the shortcut keys for <b>Navigate &gt; Next</b> and 
-      <b>Navigate &gt; Previous</b>.</td>
-  </tr>
-      <tr> 
-    <td width="20%" valign="top" align="left"><b>Line delimiter support</b></td>
-    <td width="80%" valign="top" align="left">You can set the line delimiter that 
-          is used when creating new text files. You can provide a single setting 
-          for the entire workspace, using the
-          
-          <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workspace)")'>
-          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-          <strong>General &gt; Workspace</strong></a>
-          
-          preferences, or for a given project.
-        <p><img src="images/line-delimiter.png" alt="Screenshot of default delimiter dialog"></p>
-        <p><strong>Note:</strong> Changing those settings does not convert existing files. To convert
-        the line delimiters in a project, folder or file use <b>File &gt; Convert Line Delimiters To &gt;</b>.</p>
-        </td>
-    </tr>
-        <tr> 
-      <td width="20%" valign="top" align="left"><b>Word completion</b></td>
-      <td width="80%" valign="top" align="left">In any text editor you can complete a 
-        prefix to a word occurring in all currently open editors or buffers. The 
-        default key binding for word completion is <b>Alt+/.</b> (<b>Ctrl+.</b> on the Mac).
-    </td>
-    </tr>
-
-    <tr> 
-      <td width="20%" valign="top" align="left"><b>Open untitled 
-          files</b></td>
-      <td width="80%" valign="top" align="left">A text editor can be opened without creating 
-        a file first: select <strong>File &gt; New &gt; Untitled Text File</strong>.
-        </td> 
-    </tr>
-  
-
-</table>
-
-<h3><a name="Ant">Ant</a></h3>
-<table border="1" cellpadding="10" cellspacing="0" width="670">
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Launching from the Context menu</b>
-    </td>
-    <td width="80%" valign="top" align="left">You can launch an Ant build from 
-      the context menu. Select an Ant buildfile and then choose <b>Run &gt; Ant 
-      Build</b> from the context menu. To configure options before running the 
-      build, use <strong>Run &gt; Ant Build...</strong> which will open the
-      launch configuration dialog. A build can also be started from the Ant
-      editor outline context menu.</td>
-  </tr>
-   <tr>
-    <td width="20%" valign="top" align="left"><b>Specification of JRE</b>
-    </td>
-    <td width="80%" valign="top" align="left">You can specify the JRE that an 
-      Ant build occurs in using the <b>JRE</b> tab of the launch configuration 
-      dialog for an Ant launch configuration. The build can be set to run in a 
-      separate JRE (the default setting) or the same JRE as the Eclipse workspace. 
-      Note that some Eclipse specific tasks require that the build occurs in the 
-      same JRE as Eclipse.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Running Ant targets in the Ant view</b></td>
-    <td width="80%" valign="top" align="left">You can double click on a target
-      in the Ant view to run it (equivalent to selecting the target and choosing
-      the <b>Run</b> command from the context menu). </td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Terminating Ant builds</b></td>
-    <td width="80%" valign="top" align="left">The <b>Terminate</b> command in the
-      console (or Debug view) can be used to terminate an Ant build running in
-      the background.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Ant output and hyperlinks</b></td>
-    <td width="80%" valign="top" align="left">The output from Ant builds is
-      written to the <b><a href="PLUGINS_ROOT/org.eclipse.jdt.doc.user/reference/views/console/ref-console_view.htm">Console view</a></b> in the same hierarchical format seen
-      when running Ant from the command line. Ant tasks (for example <code>[mkdir]</code>)
-      are hyper-linked to the associated Ant buildfile, and <code>javac</code> error reports
-      are hyper-linked to the associated Java source file and line number.
-      <p>The Console supports hyperlinks for <code>javac</code> and <code>jikes</code> as well as the
-        Eclipse Java compiler. All such error reports are hyper-linked to the associated 
-        Java source file and line number.</p></td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Ant can find it</b></td>
-    <td width="80%" valign="top" align="left"> When the <b>Run &gt; External Tools &gt; Run As &gt; Ant Build</b>
-      launch shortcut is used, it searches for the buildfile
-      to execute starting in the folder of the selected resource and working its way
-      upwards (some will recognize this as Ant's &quot;-find&quot;
-      feature).
-      The names of buildfiles to search for are specified in the  <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ant.ui.AntPreferencePage)")'>
-          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-          <strong>Ant</strong></a> preference page.</td>
-  </tr>
-</table>
-
-<h3><a name="Help">Help</a></h3>
-<table border="1" cellpadding="10" cellspacing="0" width="670">
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Show in external window</b></td>
-    <td width="80%" valign="top" align="left">Having trouble reading help topics
-    from the Help view/tray? Use the <img border="0"
-    src="images/help_external_window.png" alt="Show in external window"> <b>Show
-    in external window</b> button from the toolbar to view the document in the
-    full help window.
-    </td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Find that topic</b></td>
-    <td width="80%" valign="top" align="left">While browsing a searched topic,
-    you can find out where that topic is in the table of contents by using
-    the <img border="0" src="images/help_show_topic.png"
-    alt="Show in table of contents"> <b>Show in table of contents</b> button in
-    the toolbar.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Bookmarks</b></td>
-    <td width="80%" valign="top" align="left">You can keep your own list of
-      bookmarks to pages in help books. Create a bookmark with the
-      <img border="0" src="images/help_bookmarks_1.png" alt="Bookmark document icon">
-      <b>Bookmark Document</b> button on the toolbar of the Help browser. The
-      bookmarks show up in the <img border="0" src="images/help_bookmarks_2.png"
-      alt="Bookmarks icon"> <b>Bookmarks</b> tab.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Infopops</b></td>
-    <td width="80%" valign="top" align="left">If you prefer the yellow pop-ups
-      (infopops) used in previous releases for context-sensitive help, you can
-      configure Help to use these instead of the Help view/tray from the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.help.ui.browsersPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Help</strong></a>
-      
-      preference page.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Cheat Sheets</b></td>
-    <td width="80%" valign="top" align="left">Cheat sheets provide step by step 
-    guidance on how to perform common tasks. To see what cheat sheets exist use 
-    the
-    
-    <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet")'>
-    <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-    <strong>Help &gt; Cheat Sheets...</strong></a>
-    
-    menu item. This menu item may not appear in all perspectives.</td>
-  </tr>
-  <tr>
-    <td width="20%" valign="top" align="left"><b>Cheat Sheet State</b></td>
-    <td width="80%" valign="top" align="left">A cheat sheet will remember which 
-    steps you have performed even if you close the cheat sheet view, open 
-    another cheat sheet or exit Eclipse.</td>
-  </tr>
-</table>
-
-<h3><a name="CVS">Team - CVS</a></h3>
-
-<table border="1" cellpadding="10" cellspacing="0" width="670">
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>CVS Watch/Edit</b></td>
-    <td width="80%" valign="top" align="left">Through settings on the
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.team.cvs.ui.WatchEditPreferencePage)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Team &gt; CVS &gt; Watch/Edit</strong></a>
-      
-      preference page (which must be set before the projects 
-      are added to your workspace), you can choose to automatically notify the 
-      CVS server whenever you start to edit a file. In turn, the CVS server will 
-      notify others on the watch list for that file. When you go to edit a file, 
-      you are warned if there are others editing the same file. <b>Team &gt; Show 
-      Editors</b> on a file's context menu lists everyone currently working on 
-      the file. There are also <b>Team &gt; Edit</b> and <b>Unedit</b> commands.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Working set for imported team 
-      projects</b></td>
-    <td width="80%" valign="top" align="left">There is an option to create a working 
-      set for projects imported into the workspace via
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.team.ui.ProjectSetImportWizard)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>Import &gt; Team Project Set</strong></a>.
-      
-      This works for all types of repositories. 
-      <p><img border="0" src="images/team-project-set.png"  alt="Team project set import dialog"></p></td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Working sets in CVS Repositories view</b></td>
-    <td width="80%" valign="top" align="left">You can define working sets 
-      which will limit the number of projects shown in the CVS Repositories view.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Comparing different versions</b></td>
-    <td width="80%" valign="top" align="left">Select any folder or file in the 
-      CVS Repositories view and choose <b>Compare With</b> from context menu to 
-      compare it against another version, branch, or date.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Restoring deleted files from 
-      CVS</b></td>
-    <td width="80%" valign="top" align="left">Deleted files can be queried 
-      and restored from the CVS repository using the <b>Team &gt; Restore from 
-      Repository </b>command, which is available on CVS projects and folders.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Pin a Synchronization</b> </td>
-    <td width="80%" valign="top" align="left">You can have multiple synchronizations 
-      defined and available in the Synchronize view. Use the <b>Pin Current Synchronization</b> toolbar button 
-      in the Synchronize view to pin a synchronization. The next time you synchronize 
-      a new synchronization will be created. This way you can synchronize different 
-      sets of resources.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Checkout Wizard</b> </td>
-    <td width="80%" valign="top" align="left">You can checkout projects in 
-      one easy step via the
-      
-      <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import(importWizardId=org.eclipse.team.cvs.ui.newProjectCheckout)")'>
-      <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-      <strong>File &gt; Import &gt; Checkout projects from CVS wizard</strong></a>.
-      
-      This also allows checking out projects from a CVS server that doesn't support 
-      browsing of its contents.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Browsing changes by CVS change 
-      set</b> </td>
-    <td width="80%" valign="top" align="left">You can browse a set of changes 
-      shown in the Synchronize view grouped logically by author, comment, and 
-      date. Enable the layout by clicking on the Change Set <img alt="Picture of the change set toolbar button" src="images/changelog-obj.gif"> 
-      toolbar button. This layout can be used in the Incoming mode when synchronizing 
-      and when comparing.</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left"><p><strong>Group outgoing changes</strong></p>
-      </td>
-    <td valign="top" align="left">You can group outgoing changes into change sets 
-      in the Synchronize view. To enable this, switch to Outgoing mode or Both mode and choose
-      the Change Set model <img alt="Picture of the change set toolbar button" src="images/changelog-obj.gif"> from the model
-      selection dropdown in the toolbar. 
-      You can then create outgoing change sets and assign changes to them.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Schedule a synchronize</b> </td>
-    <td width="80%" valign="top" align="left">You can schedule that a certain 
-      synchronization run periodically. You can schedule any CVS synchronization 
-      from within the Synchronize view via the <b>Schedule...</b> action in the 
-      view's dropdown menu.</td>
-  </tr>
-  <tr> 
-    <td width="20%" valign="top" align="left"><b>Want to release changes to an 
-      existing branch</b> </td>
-    <td width="80%" valign="top" align="left">If you have changes in your workspace 
-      that you would like to commit to another branch than the one currently connected 
-      to, you can run the <b>Team &gt; Switch to Another Branch or Version</b> command 
-      and switch to another branch. This operation won't modify the changed files 
-      and you can then commit them to the other branch.</td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"><strong>Sharing your CVS lineup 
-      with others</strong></td>
-    <td valign="top" align="left" width="80%">You can save the 
-        list of projects shared with CVS into a team project set. This provides 
-        an easy way of re-creating your workspace with shared CVS projects.
-      <ol>
-        <li>Once you have checked out the set of projects from the CVS repository, 
-          select
-          
-          <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.export")'>
-          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-          <strong>File &gt; Export</strong></a>
-          
-          from the main menu.</li>
-        <li> Select <strong>Team Project Set</strong> from the list and then select 
-          the projects to be exported. The generated file can be shared with your 
-          team to allow quick setups of your development environment. </li>
-        <li>To import the project set select
-        
-          <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.file.import")'>
-          <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-          <strong>File &gt; Import</strong></a>
-          
-          and select <strong>Team Project Set</strong>. The projects will be checked 
-          out of CVS and a repository location will automatically be created.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"><strong>Reverting a managed CVS 
-      file that was edited, but not committed</strong></td>
-    <td valign="top" align="left" width="80%">There are a three 
-        ways of doing this:
-      <ol>
-        <li>Select the file and from the context menu select <b> Team 
-          &gt; Revert to Base</b>.</li>
-      </ol>
-      <p>or</p>  
-      <ol>
-        <li>Select the file and from the context menu select <b> Replace With 
-          &gt; Latest from HEAD</b>.</li>
-      </ol>
-      <p>or</p>
-      <ol>
-        <li>Select the file or a parent folder and from the context menu select 
-          <strong>Team &gt; Synchronize with Repository</strong>.</li>
-        <li>Next switch to incoming/outgoing mode using the toolbar button in 
-          the view.</li>
-        <li>Select the file and from the context menu select <strong>Override 
-          and Update</strong>.</li>
-      </ol></td>
-  </tr>
-  <tr> 
-    <td valign="top" align="left" width="20%"> <b>Show ancestor pane in 3-way 
-      compares</b> </td>
-    <td valign="top" align="left" width="80%"> Whenever a CVS synchronization 
-      results in a conflict, it is helpful to view the common ancestor on which 
-      the two conflicting versions are based. 
-      <p> You can view the common ancestor by toggling the <b>Show Ancestor Pane</b> 
-        button in the compare viewer's local toolbar.</p> 
-      <p> <img src="images/compare-showancestor.png"  alt="Show Ancestor Pane button in compare viewer" border="0"> </p>
-      <p> If you always want to have the ancestor pane open automatically for 
-        conflicts, you can check the option <b>Initially show ancestor pane</b> 
-        on the Text Compare tab of the Compare/Patch preference page.</p> </td>
-  </tr>
-  <TR> 
-    <TD width="20%" valign="top" align="left"><B>Merge in Compare editor</B> </TD>
-    <TD width="80%" valign="top" align="left">You can merge incoming changes in 
-      the compare editor with one click. Hover over the small square in the middle 
-      of the line connecting two ranges of an incoming or conflicting change. 
-      A button appears that allows you to accept the change. 
-      <P><IMG border="0" src="images/compare-merge-button.png" alt="Merge button" ></P>
-      <P>Note that for this the option <B>Connect ranges with single line</B> 
-        on the
-
-        <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.compare.internal.ComparePreferencePage)")'>
-        <img src="PLUGINS_ROOT/org.eclipse.help/command_link.png">
-        <strong>General &gt; Compare/Patch</strong></a>
-        
-        <strong>&gt; Text Compare</strong> preference page has to be enabled.</P></TD>
-  </TR>
-  <TR> 
-    <TD valign="top" align="left"><strong>Content assist for branching and 
-        merging</strong>
-      </TD>
-    <TD valign="top" align="left">When branching and merging with CVS, you can 
-      use content assist in the tag fields to help select an appropriate tag. 
-      For instance, when branching, you can use content assist to pick a tag from 
-      the list of branch tags that exist on the other projects in your workspace. 
-      When merging, you can use content assist to pick the branch that contains 
-      the changes you are merging. The merge wizard will also try to pick the 
-      proper start tag for you so you do not have to pick it manually.</TD>
-  </TR>
-  <TR>
-    <TD valign="top" align="left"><strong>Filtering in tag selection dialogs</strong>
-      </TD>
-    <TD valign="top" align="left">There are several CVS operations that allow 
-      you to specify a tag (e.g. Replace With Branch or Version, Compare 
-      With Branch or Version, Checkout, etc.). These dialogs  allow you to 
-      type in part of the tag name (or simple name filters using the * and ? wildcard 
-      characters) and display all the tags that match what you have typed so far. 
-      This greatly simplifies finding the desired tag when performing these operations.</TD>
-  </TR>
-</table>
-
-</body>
-</html>

diff --git a/bundles/org.eclipse.platform.doc.user/toc.xml b/bundles/org.eclipse.platform.doc.user/toc.xml
deleted file mode 100644
index 149aeef..0000000
--- a/bundles/org.eclipse.platform.doc.user/toc.xml
+++ /dev/null

@@ -1,27 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================================================================= -->
-<!-- Define the top level topics                                                   -->
-<!-- ============================================================================= -->
-
-<toc label="Workbench User Guide">
-   <topic label="Eclipse platform overview" href="gettingStarted/intro/overview.htm"/> 
-	<topic label="Getting started">
-		<link toc="topics_GettingStarted.xml" />
-	</topic>
-	<topic label="Concepts">
-		<link toc="topics_Concepts.xml" />
-	</topic>
-	<topic label="Tasks">
-		<link toc="topics_Tasks.xml" />
-	</topic>
-	<topic label="Reference">
-		<link toc="topics_Reference.xml" />
-	</topic>
-	<topic label="Tips and tricks" href="tips/platform_tips.html"/>
-	<topic label="What's new" href="whatsNew/platform_whatsnew.html"/>
-	<topic label="Legal" href="notices.html"/>
-	<enablement>
-		<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.workbench"/>
-	</enablement>
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/topics_Concepts.xml b/bundles/org.eclipse.platform.doc.user/topics_Concepts.xml
deleted file mode 100644
index 430f36f..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_Concepts.xml
+++ /dev/null

@@ -1,92 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ============================== -->
-<!-- Define topics for the Concepts -->
-<!-- ============================== -->
-
-<toc label="Concepts">
-   <topic label="Welcome" href="concepts/welcome.htm">
-      <enablement>
-         <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.intro"/>
-      </enablement>
-   </topic>
-   <topic label="Workbench" href="concepts/concepts-2.htm" >
-      <topic label="Resources" href="concepts/concepts-12.htm" />
-      <topic label="Resource hierarchies" href="concepts/concepts-17.htm" />
-      <topic label="Linked resources" href="concepts/concepts-13.htm" />
-      <topic label="Path variables" href="concepts/cpathvars.htm" />
-      <topic label="Working sets" href="concepts/cworkset.htm"/>
-      <topic label="Builds" href="concepts/concepts-22.htm" />
-      <topic label="Local history" href="concepts/concepts-17a.htm" />
-   </topic>
-   <anchor id="c_afterworkbench" />
-   <topic label="Perspectives" href="concepts/concepts-4.htm" />
-   <anchor id="c_afterperspectives" />
-   <topic label="Editors" href="concepts/concepts-6.htm" >
-      <topic href="reference/ref-anteditor.htm" label="Ant Editor">
-      </topic>
-      <topic label="External editors" href="concepts/concepts-6a.htm" />
-   </topic>
-   <anchor id="c_aftereditors" />
-   <topic label="Views" href="concepts/concepts-5.htm" >
-      <topic label="Fast views" href="concepts/concepts-21.htm" />
-      <topic label="Detached views" href="concepts/concepts-21a.htm" />
-      <topic href="reference/ref-antview.htm" label="Ant view">
-      </topic>
-      <topic label="Project Explorer view" href="concepts/cnav.htm" />
-      <topic label="Help view" href="concepts/help_view.htm">
-         <enablement>
-            <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.help.ui"/>
-         </enablement>
-      </topic>
-      <topic label="Tasks view" href="concepts/ctskview.htm" />
-      <topic label="Problems view" href="concepts/cprbview.htm" />
-      <topic label="Outline view" href="concepts/coutline.htm" />
-      <topic label="Properties view" href="concepts/cpropview.htm" />
-      <topic label="Search view" href="concepts/csearchview.htm" />
-   </topic>
-   <anchor id="c_afterviews" />
-   <topic label="Toolbars" href="concepts/concepts-18.htm" />
-   <anchor id="c_aftertoolbars" />
-   <topic label="Markers" href="concepts/concepts-11.htm" />
-   <anchor id="c_aftermarkers" />
-   <topic label="Bookmarks" href="concepts/cbookmrk.htm" />
-   <anchor id="c_afterbookmarks" />
-   <topic label="Label decorations" href="concepts/cdecorations.htm" />
-   <anchor id="c_afterdecorations" />
-   <topic label="Help" href="concepts/help.htm">
-      <enablement>
-         <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.help.ui"/>
-      </enablement>
-   </topic>
-   <anchor id="c_afterhelp" />
-   <topic label="Ant &amp; External tools" href="concepts/concepts-antexttools.htm" >
-      <topic label="Ant support" href="concepts/concepts-antsupport.htm"/>
-      <enablement>
-         <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-      </enablement>
-      <topic href="concepts/concepts-exttools.htm" label="External tools">
-      </topic>
-   </topic>
-   <anchor id="c_afterexternaltools" />
-   <topic label="Team programming with CVS" href="concepts/concepts-26.htm" >
-      <topic label="Versions" href="concepts/concepts-27.htm" />
-      <topic label="Branches" href="concepts/concepts-27b.htm" />
-      <topic label="CVS Repositories" href="concepts/concepts-27c.htm" />
-      <topic label="Three way comparisons" href="concepts/concepts-29.htm" />
-      <topic label="Synchronizing with a CVS repository" href="concepts/concepts-30.htm" />
-      <topic label="Watch/Edit" href="concepts/concepts-cvs-watch.htm" />
-      <enablement>
-         <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-      </enablement>
-   </topic>
-   <anchor id="c_afterteam" />
-   <topic label="Accessibility features in Eclipse" href="concepts/accessibility/accessmain.htm">
-      <topic label="Navigating the user interface using the keyboard"  href="concepts/accessibility/navigation.htm"/>
-      <topic label="Configuring accessibility features for textual editors"  href="concepts/accessibility/text_editor.htm"/>
-      <topic label="Fonts and colors in Eclipse"  href="concepts/accessibility/fontsandcolors.htm"/>
-   </topic>
-   <anchor id="c_afteraccessibility" />
-   <topic label="Features" href="concepts/concepts-25.htm" />
-   <anchor id="c_afterfeatures" />
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml b/bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml
deleted file mode 100644
index 00367a5..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_GettingStarted.xml
+++ /dev/null

@@ -1,150 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the GettingStarted -->
-<!-- ========================== -->
-<toc label="GettingStarted">
-   <topic label="Basic tutorial" href="gettingStarted/qs-01.htm">
-      <topic label="The Workbench" href="gettingStarted/qs-02a.htm"/>
-      <topic label="Editors and views" href="gettingStarted/qs-02b.htm">
-         <topic label="Editors" href="gettingStarted/qs-02d.xhtml"/>
-         <topic label="Views" href="gettingStarted/qs-02e.htm"/>
-      </topic>
-          
-      <topic label="A simple project" href="gettingStarted/qs-07a.htm">
-         <topic label="Using the File menu" href="gettingStarted/qs-07b.htm"/>
-         <topic label="Using the popup" href="gettingStarted/qs-07c.htm"/>
-         <topic label="Using the New button" href="gettingStarted/qs-07d.htm"/>
-      </topic>
- 
-      <topic label="Closing an editor" href="gettingStarted/qs-10b.htm"/>
-
-      <topic label="Navigating resources" href="gettingStarted/qs-12.htm">
-         <topic label="Opening resources in the Project Explorer" href="gettingStarted/qs-12b.htm"/>
-         <topic label="Go To" href="gettingStarted/qs-12c.htm"/>
-      </topic>
-
-      <topic label="Files" href="gettingStarted/qs-13.htm"/>
-
-      <topic label="Exporting files" href="gettingStarted/qs-24a.xhtml"/>
-
-      <topic label="Importing files" href="gettingStarted/qs-31a.htm">
-         <topic label="Drag and drop or copy and paste" href="gettingStarted/qs-31b.htm"/>
-         <topic label="Import wizard" href="gettingStarted/qs-31c.htm"/>
-      </topic>
-
-      <topic label="Deleting resources" href="gettingStarted/qs-32.htm"/>
-	  
-      <topic label="Working with other editors" href="gettingStarted/qs-34a.xhtml">
-         <topic label="External editors" href="gettingStarted/qs-34b.xhtml"/>
-         <topic label="Embedded editors" href="gettingStarted/qs-34c.xhtml"
-             filter="ws=win32"/>
-         <topic label="Editing files outside the Workbench" href="gettingStarted/qs-34d.htm"/>
-	 </topic>
-
-      <topic label="Copying, renaming and moving" href="gettingStarted/qs-35.htm">
-         <topic label="Copying" href="gettingStarted/qs-35b.htm"/>
-         <topic label="Renaming" href="gettingStarted/qs-35c.htm"/>
-         <topic label="Moving" href="gettingStarted/qs-35d.htm"/>
-      </topic>
-
-      <topic label="Searching" href="gettingStarted/qs-36.htm">
-         <topic label="Starting a search" href="gettingStarted/qs-36a.htm"/>
-         <topic label="The Search view" href="gettingStarted/qs-36b.htm"/>
-      </topic>
-
-      <topic label="Tasks and markers" href="gettingStarted/qs-37-2b.htm">
-         <topic label="Unassociated tasks" href="gettingStarted/qs-37-2d.htm"/>
-         <topic label="Associated tasks" href="gettingStarted/qs-37-2d2.htm"/>
-         <topic label="Opening files" href="gettingStarted/qs-37-2f.htm"/>
-      </topic>
-
-      <topic label="Bookmarks" href="gettingStarted/qs-37-3b.htm">
-         <topic label="Adding and viewing bookmarks" href="gettingStarted/qs-37-3c.htm"/>
-         <topic label="Using bookmarks" href="gettingStarted/qs-37-3e.htm"/>
-        <topic label="Removing bookmarks" href="gettingStarted/qs-37-3f.htm"/>
-      </topic>
-
-      <topic label="Rearranging views and editors" href="gettingStarted/qs-39.htm">
-         <topic label="Drop cursors" href="gettingStarted/qs-39c.htm"/>
-         <topic label="Rearranging views" href="gettingStarted/qs-39d.htm"/>
-         <topic label="Tiling editors" href="gettingStarted/qs-39e.htm"/>
-         <topic label="Rearranging tabbed views" href="gettingStarted/qs-39f.htm" />
-         <topic label="Maximizing and minimizing" href="gettingStarted/qs-39g.htm"/>
-      </topic>
-
-      <topic label="Perspectives" href="gettingStarted/qs-43.htm">
-         <topic label="New perspectives" href="gettingStarted/qs-43b.htm"/>
-         <topic label="New windows" href="gettingStarted/qs-43c.htm"/>
-         <topic label="Saving perspectives" href="gettingStarted/qs-43e.htm"/>
-         <topic label="Turning menu and tool bar items on and off" href="gettingStarted/qs-43f.htm"/>
-      </topic>
-
-      <topic label="Comparing" href="gettingStarted/qs-52.htm">
-         <topic label="Simple compare" href="gettingStarted/qs-52c.htm"/>
-         <topic label="Understanding the comparison" href="gettingStarted/qs-52d.htm"/>
-         <topic label="Working with the comparison" href="gettingStarted/qs-52e.htm"/>
-         <enablement>
-            <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.compare"/>
-         </enablement>
-      </topic>
-
-      <topic label="Local history" href="gettingStarted/qs-55.htm"/>
-	  
-	  <topic label="Responsive UI" href="gettingStarted/qs-responsiveUI.htm"/>	
-
-      <topic label="Exiting the Workbench" href="gettingStarted/qs-55b.htm"/>
-
-   </topic>
-   
-   <anchor id="gs_afterbasic" />
-
-   <topic label="Team CVS tutorial" href="gettingStarted/qs-60_team.htm">
-      <topic label="Setting up a CVS repository" href="gettingStarted/qs-60a_setup.htm"/>
-      <topic label="Starting offline" href="gettingStarted/qs-61c_offline.htm"/>
-
-      <topic label="Sharing the project" href="gettingStarted/qs-61d_repoloca.htm">
-         <topic label="Specifying a repository location" href="gettingStarted/qs-61d_repolocb.htm"/>
-         <topic label="Repository locations" href="gettingStarted/qs-61e_whatisloc.htm"/>
-         <topic label="Sharing a project" href="gettingStarted/qs-61f_syncproject.htm"/>
-      </topic>
-
-      <topic label="Working with another user" href="gettingStarted/qs-64a_another.htm">
-         <topic label="Checking out a project" href="gettingStarted/qs-64b_fredadd.htm"/>
-         <topic label="Another user making changes" href="gettingStarted/qs-64b_fredmod.htm"/>
-         <topic label="Making our own changes" href="gettingStarted/qs-64c_catch_mod.htm"/>
-         <topic label="Working with conflicting changes" href="gettingStarted/qs-64c_catch_sync_view.htm"/>
-         <topic label="Replacing" href="gettingStarted/qs-70_replace.htm"/>
-         <topic label="Versioning your project" href="gettingStarted/qs-74_version.htm"/>
-         <topic label="A quick review" href="gettingStarted/qs-74_review.htm"/>
-      </topic>
-      <topic label="Working with CVS History" href="gettingStarted/qs-70_workingWithHistory.htm"/>
-      <enablement>
-         <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-      </enablement>
-   </topic>
-
-   <anchor id="gs_afterteam" />
-
-   <topic label="Ant &amp; external tools tutorial" href="gettingStarted/qs-80_ant.htm">
-     <topic label="Eclipse Ant basics" href="gettingStarted/qs-81_basics.htm">
-       <topic label="Creating Ant buildfiles" href="gettingStarted/qs-82_create.htm"/>
-       <topic label="Editing Ant buildfiles" href="gettingStarted/qs-83_edit.htm"/>
-       <topic label="Running Ant buildfiles" href="gettingStarted/qs-84_run_ant.htm"/>
-       <topic label="Saving &amp; Reusing Ant options" href="gettingStarted/qs-85_ant_configs.htm"/>
-       <topic label="Using the Ant view" href="gettingStarted/qs-85a_ant_view.htm"/>
-     </topic>    
-     <topic label="Ant buildfiles as project builders" href="gettingStarted/qs-92_project_builders.htm">
-       <topic label="Creating a project builder Ant buildfile" href="gettingStarted/qs-93_project_builder.htm"/>
-       <topic label="Executing project builders" href="gettingStarted/qs-94_run_pj.htm"/>       
-     </topic>      	
-     <topic label="External tools" href="gettingStarted/qs-95_external_tools.htm">
-       <topic label="Non-Ant project builders" href="gettingStarted/qs-96_non_ant_pjs.htm"/>
-       <topic label="Stand-alone external tools" href="gettingStarted/qs-97_standalone_ets.htm"/>
-     </topic>	
-     <enablement>
-        <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-     </enablement>
-   </topic>
-   <anchor id="gs_afterant" />
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/topics_Reference.xml b/bundles/org.eclipse.platform.doc.user/topics_Reference.xml
deleted file mode 100644
index a0bbaec..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_Reference.xml
+++ /dev/null

@@ -1,316 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Reference -->
-<!-- ========================== -->
-<toc label="Reference">
-
-<!-- <topic label="Keyboard shortcuts" /> -->
-<topic label="Minimizing data loss from crashes" href="reference/ref-8.htm" />
-
-<anchor id="r_aftercrash" />
-
-	<topic label="Preferences" href="reference/ref-72.htm">
-		<topic label="Accessibility" href="reference/ref-7.htm"></topic>
-		<topic label="Annotations" href="reference/ref-22.htm"></topic>
-		<topic label="Ant" href="reference/ref-antprefs.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Ant Code Assist" href="reference/ref-antcodeassist.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>		
-		<topic label="Ant Editor" href="reference/ref-anteditorprefs.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>		
-		<topic label="Ant Formatter" href="reference/ref-antformatter.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>		
-		<topic label="Ant Runtime" href="reference/ref-antruntimeprefs.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Ant Templates" href="reference/ref-anttemplates.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>	
-		<topic label="Appearance" href="reference/ref-16.htm"></topic>
-		<topic label="Automatic Updates" href="reference/ref-p2-autoupdate.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.equinox.p2.ui.sdk"/>
-			</enablement>
-		</topic>
-		<topic label="Available Software Sites" href="reference/ref-p2-siteprefs.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.equinox.p2.ui.sdk.scheduler"/>
-			</enablement>
-		</topic>
-		<topic label="Build Order" href="reference/ref-17.htm"></topic>
-		<topic label="Capabilities" href="reference/ref-capabilitiespref.htm"></topic>
-		<topic label="Colors and Fonts" href="reference/ref-fonts.htm"></topic>
-		<topic label="Compare/Patch" href="reference/ref-11.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.compare"/>
-			</enablement>
-		</topic>
-		<topic label="Content Types" href="reference/ref-content-type.htm"></topic>
-		<topic label="CVS" href="reference/ref-19cvs.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Annotate" href="reference/ref-19cvs-annotate.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Comment Templates" href="reference/ref-19cvs-commenttemplates.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Console" href="reference/ref-19cvs-console.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Ext Connection Method" href="reference/ref-19cvs-ext.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Label Decorations" href="reference/ref-19cvs-decorations.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Synchronize/Compare" href="reference/ref-19cvs-sync.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Update/Merge" href="reference/ref-19cvs-updatemerge.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="CVS Watch/Edit" href="reference/ref-19cvs-watch-edit.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Editors" href="reference/ref-12.htm"></topic>
-		<topic label="External Tools" href="reference/ref-exttoolsprefs.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.externaltools"/>
-			</enablement>
-		</topic>
-		<topic label="File Associations" href="reference/ref-13.htm"></topic>
-		<topic label="General" href="reference/ref-10.htm"></topic>
-		<topic label="Help" href="reference/help_preferences.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.help.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Help Content" href="reference/help_preferences_content.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.help.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Install/Update" href="reference/ref-p2-installupdate.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.equinox.p2.ui.sdk"/>
-			</enablement>
-		</topic>
-		<topic label="Keys" href="concepts/accessibility/keyboardshortcuts.htm"></topic>
-		<topic label="Label Decorations" href="reference/ref-decorations.htm"></topic>
-		<topic label="Linked Resources" href="reference/ref-14b.htm"></topic>
-		<topic label="Local History" href="reference/ref-14.htm"></topic>
-		<topic label="Network Connections" href="reference/ref-net-preferences.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.net"/>
-			</enablement>
-		</topic>
-		<topic label="Perspectives" href="reference/ref-15.htm"></topic>
-		<topic label="Quick Diff" href="reference/ref-35.htm"></topic>
-		<topic label="Search" href="reference/ref-search.htm"></topic>
-		<topic label="Secure Storage" href="reference/ref-securestorage-prefs.htm"></topic>
-		<topic label="Spelling" href="reference/ref-36.htm"></topic>
-	    <topic label="SSH2" href="reference/ref-ssh2-preferences.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.jsch.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Startup and Shutdown" href="reference/ref-startup.htm"></topic>
-		<topic label="Workspaces" href="reference/ref-startup-workspaces.htm"></topic>
-		<topic label="Team" href="reference/ref-19.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Team File Content" href="reference/ref-20-fileContent.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Team Ignored Resources" href="reference/ref-20.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Team Models" href="reference/ref-20team-models.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Text Editors" href="reference/ref-texteditorprefs.htm"></topic>
-		<topic label="Web Browser" href="reference/ref-42.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.browser"/>
-			</enablement>
-		</topic>
-		<topic label="Workspace" href="reference/ref-9.htm"></topic>
-	</topic>
-    
-    <anchor id="r_afterpref" />
-	
-	<topic label="Team support with CVS">
-		<topic label="CVS" href="reference/ref-47.htm"></topic>
-		<topic label="CVS Checkout wizard" href="reference/ref-40a.htm"></topic>
-		<topic label="CVS Console" href="reference/ref-32b.htm"></topic>
-		<topic label="CVS History view" href="reference/ref-32a.htm"></topic>
-		<topic label="CVS Repositories view" href="reference/ref-32.htm"></topic>
-		<topic label="CVS Workspace Synchronization" href="reference/ref-33.htm"></topic>
-		<topic label="CVS Merge Synchronization" href="reference/ref-33a.htm"></topic>
-		<topic label="Merge wizard" href="reference/ref-41a.htm"></topic>
-	    <topic label="Add CVS Repository wizard" href="reference/ref-40.htm"></topic>
-		<topic label="CVS Sharing wizard" href="reference/ref-40b.htm"></topic>
-		<topic label="CVS Label Decorations" href="reference/ref-cvs-decorations.htm"></topic>
-		<topic label="Ignoring resources from version control" href="reference/ref-48a.htm" ></topic>
-		<enablement>
-			<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-		</enablement>
-	</topic>
-	
-	<anchor id="r_afterteam" />
-	
-	<topic label="Secure storage" href="reference/ref-securestorage-start.htm">
-		<topic label="How secure storage works" href="reference/ref-securestorage-works.htm"></topic>
-		<topic label="Password recovery" href="reference/ref-securestorage-recovery.htm"></topic>
-		<topic label="Life of a master password" href="reference/ref-securestorage-passwd.htm"></topic>
-		<topic label="Secure storage runtime options" href="reference/ref-securestorage-options.htm"></topic>
-		<enablement>
-			<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.equinox.security"/>
-		</enablement>
-	</topic>
-	
-	<anchor id="r_aftersecstore" />
-	
-<topic label="User interface information" >
-	<topic label="Development environment">
-		<topic label="Workbench toolbar" href="reference/ref-2.htm"></topic>
-		<topic label="Perspective Bar" href="reference/ref-3.htm"></topic>
-		<topic label="Fast View Bar" href="reference/ref-3a.htm"></topic>
-		<topic label="View toolbars" href="reference/ref-4.htm"></topic>
-		<topic label="Builds" href="reference/ref-5.htm"></topic>
-		<topic label="Perspectives" href="reference/ref-6.htm"></topic>
-		<topic label="Local history" href="reference/ref-6a.htm"></topic>		
-		<topic label="List of key bindings" href="reference/ref-keybindings.htm"></topic>
-		<topic label="Switching workspaces" href="reference/ref-workspaceswitch.htm"></topic>
-	</topic>
-
-
-	<topic label="Views and editors">
-		<topic label="Workbench window layout" href="reference/ref-23.htm"></topic>
-		<topic label="Editor area" href="reference/ref-24.htm"></topic>
-		<topic label="Compare editor" href="reference/ref-25.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.compare"/>
-			</enablement>
-		</topic>
-		<topic label="Search view" href="reference/ref-26.htm"></topic>
-		<topic label="Project Explorer view" href="reference/ref-27.htm"></topic>
-		<topic label="Bookmarks view" href="reference/ref-28.htm"></topic>
-		<topic label="Properties view" href="reference/ref-29.htm"></topic>
-		<topic label="Outline view" href="reference/ref-30.htm"></topic>
-		<topic label="CVS views" href="reference/ref-30a.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-        <topic label="Tasks view" href="reference/ref-31.htm"></topic>
-		<topic label="Problems view" href="reference/ref-31a.htm"></topic>
-		<topic label="Ant editor" href="reference/ref-anteditor.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>
-		<topic label="Ant view" href="reference/ref-antview.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-			</enablement>
-		</topic>
-	</topic>
-
-	<topic label="Wizards">
-		<topic label="New Project wizard" href="reference/ref-37.htm"></topic>
-		<topic label="New Folder wizard" href="reference/ref-38.htm"></topic>
-		<topic label="New File wizard" href="reference/ref-39.htm"></topic>
-		<topic label="CVS Wizards" href="reference/ref-39a.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-			</enablement>
-		</topic>
-        <topic label="Import wizard" href="reference/ref-70.htm"></topic>
-		<topic label="Export wizard" href="reference/ref-71.htm"></topic>
-	</topic>
-
-
-	<topic label="Help contents">
-		<topic label="Workbench User Guide" href="reference/ref-43.htm"></topic>
-		<topic label="Working with cheat sheets" href="reference/ref-cheatsheets.htm">
-		    <topic label="Working with composite cheat sheets" href="reference/ref-composite-cheatsheets.htm"></topic>
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.cheatsheets"/>
-			</enablement>
-		</topic>
-	</topic>
-
-	<topic label="Search">
-		<topic label="File search" href="reference/ref-45.htm"></topic>
-	</topic>
-
-	<topic label="Workbench menus">
-		<topic label="File menu" href="reference/ref-56.htm"></topic>
-		<topic label="Edit menu" href="reference/ref-57.htm"></topic>
-		<topic label="Navigate menu" href="reference/ref-58.htm"></topic>
-		<topic label="Project menu" href="reference/ref-59.htm"></topic>
-		<topic label="Window menu" href="reference/ref-60.htm"></topic>
-		<topic label="Help menu" href="reference/ref-61.htm"></topic>
-	</topic>
-
-	<topic label="Icons and buttons">
-		<topic label="Project Explorer view icons" href="reference/ref-65.htm"></topic>
-		<topic label="Editor area marker bar" href="reference/ref-66.htm"></topic>
-		<topic label="Tasks view" href="reference/ref-67.htm"></topic>
-		<topic label="Toolbar buttons" href="reference/ref-68.htm"></topic>
-		<topic label="External Tools and Ant Icons" href="reference/ref-anticons.htm">
-			<enablement>
-				<test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.externaltools"/>
-			</enablement>
-		</topic>
-	</topic>
-</topic>
-
-<anchor id="r_afteruser" />
-
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/topics_Tasks.xml b/bundles/org.eclipse.platform.doc.user/topics_Tasks.xml
deleted file mode 100644
index 05ee934..0000000
--- a/bundles/org.eclipse.platform.doc.user/topics_Tasks.xml
+++ /dev/null

@@ -1,271 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<?NLS TYPE="org.eclipse.help.toc"?>
-<!-- ========================== -->
-<!-- Define topics for the Tasks -->
-<!-- ========================== -->
-<toc label="Tasks">
-
-<topic label="Running Eclipse" href="tasks/running_eclipse.htm" />
-
-<anchor id="t_afterrunning" />
-
-<topic label="Upgrading Eclipse" href="tasks/tasks-2.htm" />
-
-<anchor id="t_afterupgrading" />
-
-<topic label="Working with perspectives" href="tasks/tasks-1a.htm" >
-  <topic label="Switching between perspectives" href="tasks/tasks-28.htm" />
-  <topic label="Specifying the default perspective" href="tasks/tasks-31.htm" />
-  <topic label="Opening perspectives" href="tasks/tasks-9f.htm" />
-  <topic label="Changing where perspectives open" href="tasks/tasks-24.htm" />
-  <topic label="Showing and hiding menu items and toolbar buttons" href="tasks/tasks-9n.htm"/>
-  <topic label="Configuring perspective command groups" href="tasks/tasks-9m.htm"/>
-  <topic label="Configuring perspective shortcuts" href="tasks/tasks-9k.htm"/>
-  <topic label="Saving a user defined perspective" href="tasks/tasks-9i.htm" />
-  <topic label="Deleting a user defined perspective" href="tasks/tasks-9d.htm" />
-  <topic label="Resetting perspectives" href="tasks/tasks-9j.htm" />
-</topic>
-
-<anchor id="t_afterworking_perspectives" />
-
-<topic label="Working with views and editors"  href="tasks/tasks-1b.htm" >
-  <topic label="Opening views" href="tasks/tasks-3.htm" />
-  <topic label="Moving and docking views" href="tasks/tasks-3e.htm" />
-  <topic label="Rearranging tabbed views" href="tasks/tasks-3h.htm" />
-  <topic label="Creating fast views" href="tasks/tasks-9b.htm" />
-  <topic label="Working with fast views" href="tasks/tasks-9c.htm" />
-  <topic label="Detaching views" href="tasks/tasks-9l.htm" />
-  <topic label="Opening files for editing" href="tasks/tasks-46.htm" />
-  <topic label="Associating editors with file types" href="tasks/tasks-51.xhtml" />
-  <topic label="Editing files outside the Workbench" href="tasks/tasks-52.htm" />
-  <topic label="Tiling editors" href="tasks/tasks-3g.htm" />
-  <topic label="Maximizing and minimizing in the eclipse presentation" href="gettingStarted/qs-39g.htm" />
-</topic>
-
-<anchor id="t_afterworking_views" />
-
-<topic label="Customizing the Workbench" href="tasks/tasks-1.htm" >
-  <topic label="Customizing welcome" href="tasks/welcome.htm">
-    <enablement>
-       <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.intro"/>
-    </enablement>
-    <topic label="Customize Welcome Dialog" href="reference/welcome_preferences.htm"/>
-  </topic>
-  <topic label="Rearranging the main toolbar" href="tasks/ttoolbars.htm" />
-  <topic label="Changing the key bindings" href="tasks/tkeybindings.htm" />
-  <topic label="Changing fonts and colors" href="tasks/tasks-20.htm" />
-  <topic label="Changing the placement of the tabs" href="tasks/tasks-9.htm" />
-  <topic label="Controlling single and double click behavior" href="tasks/topenmode.htm" />
-  <topic label="Importing and exporting preferences" href="tasks/timpandexp.htm"/>
-</topic>
-
-<anchor id="t_aftercustomizing" />
-
-<topic label="Working with projects, folders and files" href="tasks/tasks-1e.htm" >
-  <topic label="Creating a project" href="tasks/tasks-42.htm" />
-  <topic label="Closing projects" href="tasks/tasks-47.htm" />
-  <topic label="Deleting projects" href="tasks/tasks-42b.htm" />
-  <topic label="Creating a folder" href="tasks/tasks-43.htm" />
-  <topic label="Creating a file" href="tasks/tasks-44.htm" />
-  <topic label="Creating linked resources" href="tasks/tasks-45.htm" />
-  <topic label="Moving resources" href="tasks/tasks-63.htm" />
-  <topic label="Copying resources" href="tasks/tasks-63cg.htm" />
-  <topic label="Renaming resources" href="tasks/tasks-66.htm" />
-  <topic label="Deleting resources" href="tasks/tasks-67.htm" />
-  <topic label="Viewing resources properties" href="tasks/tasks-49.htm" />
-</topic>
-
-<anchor id="t_afterworking_projects" />
-
-
-<topic label="Navigating and finding resources" href="tasks/tasks-1c.htm" >
-  <topic label="Finding a resource quickly" href="tasks/tasks-46ag.htm" />
-  <topic label="Searching for files" href="tasks/tasks-84b.htm" />  
-  <topic label="Searching for text within a file" href="tasks/tasks-84.htm" />
-  <topic label="Showing or hiding files in the Project Explorer view" href="tasks/tasks-48b.htm" />
-  <topic label="Linking the Project Explorer view to the active editor" href="tasks/tasks-18.htm" />
-</topic>
-
-<anchor id="t_afternavigating" />
-
-<topic label="Problems, bookmarks, tasks and other markers" href="tasks/tasks-1d.htm" >
-  <topic label="Creating a bookmark within a file" href="tasks/tasks-81.htm" />
-  <topic label="Creating a bookmark for an entire file" href="tasks/tasks-81b.htm" />
-  <topic label="Deleting a bookmark" href="tasks/tasks-82.htm" />
-  <topic label="Adding line items in the Tasks view" href="tasks/tasks-77.htm" />
-  <topic label="Associating a task with a resource" href="tasks/tasks-77b.htm" />
-  <topic label="Deleting tasks" href="tasks/tasks-78.htm" />
-  <topic label="Filtering the Tasks and Problems views" href="tasks/tasks-79.htm" />
-  <topic label="Automatically fixing problems" href="tasks/tquickfix.htm" />
-</topic>
-
-<anchor id="t_afterbookmarks" />
-
-<topic label="Comparing resources" href="tasks/tasks-68.htm" >
-  <topic label="Setting preferences for comparing files" href="tasks/tasks-68b.htm" />
-  <topic label="Understanding the comparison" href="tasks/tasks-68bg.htm" />
-  <topic label="Merging changes in the compare editor" href="tasks/tasks-68dg.htm" />
-  <enablement>
-     <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.compare"/>
-  </enablement>
-</topic>
-
-<anchor id="t_aftercomparing" />
-
-<topic label="Working with local history" href="tasks/tasks-1f.htm" >
-  <topic label="Comparing resources with the local history" href="tasks/tasks-70.htm" />
-  <topic label="Replacing a resource with local history" href="tasks/tasks-87.htm" />
-  <topic label="Restoring deleted resources from local history" href="tasks/tasks-87b.htm" />
-  <topic label="Setting local history preferences" href="tasks/tasks-88.htm" />
-</topic>
-
-<anchor id="t_afterworking_local" />
-
-<topic label="Importing" href="tasks/tasks-53.xhtml" >
-  <topic label="Importing existing projects" href="tasks/tasks-importproject.htm" />
-  <topic label="Importing resources from the file system" href="tasks/tasks-55.htm" />
-  <topic label="Importing resources from an Archive file" href="tasks/tasks-55bg.htm" />
-</topic>
-
-<anchor id="t_afterimporting" />
-
-<topic label="Exporting" href="tasks/tasks-57.xhtml" >
-  <topic label="Exporting resources to the file system" href="tasks/tasks-59.htm" />
-  <topic label="Exporting resources to an Archive file" href="tasks/tasks-59ag.htm" />
-</topic>
-
-<anchor id="t_afterexporting" />
-
-<topic label="Building resources" href="tasks/tasks-73.htm" >
-  <topic label="Performing builds automatically" href="tasks/tasks-16.htm" />
-  <topic label="Performing builds manually" href="tasks/tasks-75.htm" />
-  <topic label="Saving resources automatically before a manual build" href="tasks/tasks-17.htm" />
-  <topic label="Changing build order" href="tasks/tasks-14.htm" />
-  <topic label="Running external tools" href="tasks/tasks-exttools-running.htm">
-    <enablement>
-      <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ui.externaltools"/>
-    </enablement>
-  </topic>
-  <topic label="Running Ant buildfiles" href="tasks/tasks-ant-running.htm">
-    <topic label="Modifying the Ant classpath" href="tasks/tasks-ant-classpath.htm"/>
-    <topic label="Using a different version of Ant" href="tasks/tasks-ant-version.htm"/>
-    <topic label="Adding new Ant tasks and types" href="tasks/tasks-ant-addtasksandtypes.htm"/>
-    <enablement>
-      <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.ant.ui"/>
-    </enablement>
-  </topic>
-</topic>
-
-<anchor id="t_afterbuilding" />
-
-<!-- help topics -->
-<topic label="Accessing help" href="tasks/help.xhtml" >
-  <topic label="Navigating help topics" href="tasks/help_navigate.htm" />
-  <topic label="Searching help" href="tasks/help_search.htm" />
-  <topic label="Accessing context-sensitive help" href="tasks/help_context.htm" />
-  <topic label="Help display settings" href="tasks/help_settings.htm" />
-  <topic label="Help accessibility" href="tasks/help_accessibility.htm">
-    <enablement>
-      <systemTest property="osgi.os" value="win32"/>
-    </enablement>
-  </topic>
-  <enablement>
-    <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.help.ui"/>
-  </enablement>
-</topic>
-
-<anchor id="t_afterusing" />
-
-<!-- team topics -->
-<topic label="Working in the team environment with CVS" href="tasks/tasks-1h.htm" >
-  <topic label="Working with a CVS repository" href="tasks/tasks-1i.htm" >
-    <topic label="Creating a CVS repository location" href="tasks/tasks-92.htm" />
-	<topic label="Connecting and configuring CVS with SSH" href="tasks/tasks-cvs-ssh2.htm" />
-	<topic label="Password Management" href="tasks/tasks-cvs-passwords.htm" />
-    <topic label="Discarding a CVS repository location" href="tasks/tasks-94.htm" />
-    <topic label="Refreshing the CVS Repositories View" href="tasks/tasks-93.htm" />
-    <topic label="Discovering branch and version tags" href="tasks/tasks-110.htm" />
-    <topic label="Changing the properties of a CVS repository location" href="tasks/tasks-95.htm" />
-    <topic label="Changing the encoding of a CVS repository location" href="tasks/tasks-95a.htm" />
-    <topic label="Setting the content type of a file extension" href="tasks/tasks-team-1.htm" />
-  </topic>
-  <topic label="Working with projects shared with CVS" href="tasks/tasks-1j.htm" >
-      <topic label="Enabling the CVS resource decorations" href="tasks/tasks-107b.htm" />
-	  <topic label="Sharing a new project using CVS" href="tasks/tasks-117.htm" />
-	  <topic label="Project checked out with another CVS tool" href="tasks/tasks-117a.htm" />
-	  <topic label="Checking out a project from a CVS repository" href="tasks/tasks-96.htm" />
-	  <topic label="Checking out a module from a CVS repository" href="tasks/tasks-96a.htm" />
-	  <topic label="Checking out a folder into an existing project" href="tasks/tasks-96b.htm" />
-	  <topic label="Disconnecting a project from CVS" href="tasks/tasks-cvs-10.htm" />
-	  <topic label="Setting the CVS keyword substitution mode" href="tasks/tasks-cvs-11.htm" />
-	  <topic label="Filtering CVS Revisions in the History view" href="tasks/tasks-cvs-16.htm" />
-	  <topic label="Changing the sharing of a project" href="tasks/tasks-117b.htm" />
-	  <topic label="Sharing your workspace setup using Project Sets" href="tasks/tasks-cvs-project-set.htm" />
-  </topic>
-  <topic label="Synchronizing with the repository" href="tasks/tasks-115.htm" >
-    <topic label="Updating" href="tasks/tasks-113.htm" />
-    <topic label="Committing" href="tasks/tasks-114.htm" />
-    <topic label="Version control life cycle: adding and ignoring resources" href="tasks/tasks-100d.htm" >
-      <topic label="Creating a global ignore pattern" href="tasks/tasks-100d1.htm" />
-      <topic label="Authoring the CVS .cvsignore file" href="tasks/tasks-100d2.htm" />
-      <topic label="Overriding or removing resource ignore patterns" href="tasks/tasks-100d1b.htm" />
-    </topic>
-    <topic label="Resolving conflicts" href="tasks/tasks-113b.htm" />
-    <topic label="Branching" href="tasks/tasks-100a.htm" />
-    <topic label="Merging from a branch" href="tasks/tasks-100b.htm" />
-    <topic label="Viewing a file's revision history" href="tasks/tasks-119.htm" />
-  </topic>
-  <topic label="Versioning" href="tasks/tasks-1k.htm" >
-    <topic label="Creating a version of a project" href="tasks/tasks-100.htm" />    
-    <topic label="Versioning projects in the repository" href="tasks/tasks-118.htm" />
-  </topic>
-  <topic label="Comparing resources with repository versions" href="tasks/tasks-101.htm" />
-  <topic label="Working with patches" href="tasks/tasks-68c.htm" />
-  <topic label="Replacing resources in the workbench" href="tasks/tasks-103.htm" />
-  <topic label="Finding out who's working on what: watch/edit" href="tasks/tasks-cvs-watch.htm" />
-  <topic label="Determining who last modified a line with the Annotate command" href="tasks/tasks-cvs-annotate.htm" />
-  <topic label="Quick Diff: Showing changes in a text editor" href="tasks/tasks-cvs-quickdiff.htm" />
-  <topic label="Changing CVS team settings" href="tasks/tasks-105.htm" />
-  <topic label="Restoring deleted files from the repository" href="tasks/tasks-105a.htm" />
-  <topic label="Reverting a branch to a previous version" href="tasks/tasks-105b.htm" />
-  <topic label="Moving version tags" href="tasks/tasks-105c.htm" />
-  <topic label="Running the CVS command-line client outside of Eclipse" href="tasks/task-team-cmdlineclient.htm" />
-  <enablement>
-    <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.team.cvs.ui"/>
-  </enablement>
-</topic>
-
-<anchor id="t_afterworking_team" />
-
-
-<!-- install update topics -->
-  <topic label="Updating and installing software" href="tasks/tasks-129.htm" >
-  <topic label="Updating the installation" href="tasks/tasks-120.htm" />
-  <topic label="Installing new software" href="tasks/tasks-124.htm" />
-  <topic label="Updating software using the Available Updates wizard" href="tasks/tasks-125.htm" />
-  <topic label="Uninstalling software" href="tasks/tasks-126.htm" />
-  <topic label="Installation Details" href="tasks/tasks-130.htm">
-  	<topic label="Installation Details for Plug-ins" href="tasks/tasks-131.htm" />
-  	<topic label="Installation Details for Features" href="tasks/tasks-132.htm" />
-  	<topic label="Installation Details for the Configuration" href="tasks/tasks-133.htm" />
-  </topic>
-  <topic label="Adding a new software site" href="tasks/tasks-127.htm" />
-  <topic label="Working with the Available Software sites" href="tasks/tasks-128.htm" />
-  <topic label="Reverting to a previous install configuration" href="tasks/tasks-123.htm" />
-  <topic label="Scheduling automatic updates" href="tasks/tasks-122.htm" />
-  <topic label="Using the classic update manager" href="tasks/tasks-32.htm">
-  	<topic label="Inspecting the current configuration" href="tasks/tasks-33.htm" />
-    <topic label="Updating features with the update manager" href="tasks/tasks-36.htm"/>
-    <topic label="Restoring a saved configuration" href="tasks/tasks-38.htm" />
-    <topic label="Installing new features with the update manager" href="tasks/tasks-34.htm" />
-    <topic label="Enabling, disabling, and uninstalling features" href="tasks/tasks-35.htm" />
-    <topic label="Controlling the Eclipse update policy" href="tasks/tasks-37.htm" />
-    <enablement>
-    <test property="org.eclipse.core.runtime.isBundleInstalled" args="org.eclipse.update.ui"/>
-    </enablement>
-  </topic>
-</topic>
-
-<anchor id="t_afterupdating" />
-
-</toc>

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/alternate.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/alternate.png
deleted file mode 100644
index bdcbdbd..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/alternate.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/apply-patch-syncview.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/apply-patch-syncview.png
deleted file mode 100644
index 80efd92..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/apply-patch-syncview.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/block-selection-mode.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/block-selection-mode.png
deleted file mode 100644
index 2f46941..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/block-selection-mode.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cnf-gointo.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/cnf-gointo.png
deleted file mode 100644
index ad95363..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cnf-gointo.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cocoa.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/cocoa.png
deleted file mode 100644
index 3b6c5b5..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/cocoa.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/collapse-projection.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/collapse-projection.png
deleted file mode 100644
index 9f5b6a9..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/collapse-projection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/contentMergeViewerSwitching.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/contentMergeViewerSwitching.png
deleted file mode 100644
index d04da64..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/contentMergeViewerSwitching.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/customicon.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/customicon.png
deleted file mode 100644
index 8b33158..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/customicon.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/customize-perspective.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/customize-perspective.png
deleted file mode 100644
index 58565ca..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/customize-perspective.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-1.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-1.png
deleted file mode 100644
index 0d90897..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-2.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-2.png
deleted file mode 100644
index de5f8bc..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-3.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-3.png
deleted file mode 100644
index 10cacfc..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/debug-breadcrumb-3.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/gotoLine.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/gotoLine.png
deleted file mode 100644
index 8baa697..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/gotoLine.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/injection_graph_func.js b/bundles/org.eclipse.platform.doc.user/whatsNew/images/injection_graph_func.js
deleted file mode 100644
index 7216ce4..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/injection_graph_func.js
+++ /dev/null

@@ -1,463 +0,0 @@
-var skype_injection_path = 'chrome://skype_ff_toolbar_win/content/';

-var skype_tool = null;

-

-/*window.addEventListener("click",skype_click_handler,true);

-function skype_click_handler(event)

-{

-	if (skype_tool)

-		skype_tool.closemenu();

-	//HideSkypeMenuFull();

-} */

-

-//CALL BUTTON

-var SkypeActiveCallButtonPart = 0;

-function SkypeSetCallButtonPart(obj)

-{

-	if (obj.getAttribute('id') == '__skype_highlight_id_left')

-	{

-		SkypeActiveCallButtonPart = 0;

-	}

-	else if (obj.getAttribute('id') == '__skype_highlight_id_right')

-	{

-		SkypeActiveCallButtonPart = 1;

-	}

-}

-

-function SkypeSetCallButton(obj, hl, isInternational, isFax)

-{

-	var cb_part_l = null;

-	var cb_part_ml = null;

-	var cb_part_mr = null;

-	var cb_part_r = null;

-	if (obj.getAttribute('rtl') == 'false')

-	{

-		cb_part_l = obj.firstChild.firstChild;

-		cb_part_ml = obj.firstChild.lastChild;

-		cb_part_mr = obj.lastChild.firstChild;

-		cb_part_r = obj.lastChild.lastChild;

-

-		cb_flag = obj.firstChild.lastChild.firstChild;

-		if (cb_flag && cb_flag.isSameNode(obj.firstChild.firstChild.firstChild) == true)

-			cb_flag = null;

-	}

-	else

-	{

-		cb_part_l = obj.lastChild.lastChild;

-		cb_part_ml = obj.lastChild.firstChild;

-		cb_part_mr = obj.firstChild.lastChild;

-		cb_part_r = obj.firstChild.firstChild;

-

-		cb_flag = obj.lastChild.firstChild.lastChild;

-		if (cb_flag && cb_flag.isSameNode(obj.lastChild.lastChild.lastChild) == true)

-			cb_flag = null;

-	}

-

-	if (hl == 1)

-	{

-		cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_l.gif')";

-		if (cb_part_l.isSameNode(cb_part_ml) != true)

-			cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_m.gif')";

-		cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_m.gif')";

-

-

-		if (isInternational == "0")

-		{

-			if (SkypeActiveCallButtonPart == 0)    //left

-			{

-				cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseonflag_r"+(isFax?"_fax":"")+".gif')";

-				//shadow

-				if (cb_flag)

-				{

-					cb_flag.style.top = '1px';

-					cb_flag.style.left = '1px';

-					/*top right bottom left*/

-					cb_flag.style.padding = '1px 0px 0px 1px';//'2px 0px 0px 0px';

-				}

-			}

-			else                            //right

-			{

-				cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_r"+(isFax?"_fax":"")+".gif')";

-				//flag

-				if (cb_flag)

-				{

-					cb_flag.style.top = '0px';

-					cb_flag.style.left = '0px';

-					cb_flag.style.padding = '0px 1px 1px 0px';//'0px 1px 1px 0px';

-					cb_flag.style.margin = '0px 0px 2px 0px;';

-				}

-			}

-		}

-		else

-		{

-			cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_mouseover_r"+(isFax?"_fax":"")+".gif')";

-			//flag

-			if (cb_flag)

-			{

-				cb_flag.style.top = '0px';

-				cb_flag.style.left = '0px';

-				cb_flag.style.padding = '0px 1px 1px 0px';

-				cb_flag.style.margin = '0px 0px 2px 0px;';

-			}

-		}

-	}

-	else

-	{

-		cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_l.gif')";

-		if (cb_part_l.isSameNode(cb_part_ml) != true)

-			cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_m.gif')";

-		cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_m.gif')";

-		cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_normal_r"+(isFax?"_fax":"")+".gif')";

-

-		//flag

-		if (cb_flag)

-		{

-			cb_flag.style.top = '0px';

-			cb_flag.left = '0px';

-			cb_flag.style.padding = '0px 1px 1px 0px';

-			cb_flag.style.margin = '0px 0px 2px 0px;';

-		}

-	}

-}

-var skype_cb_l = '';

-var skype_cb_m = '';

-var skype_cb_r = '';

-

-function SkypeSetCallButtonPressed(obj, pr, isInternational, isFax)

-{

-	var cb_part_l = null;

-	var cb_part_ml = null;

-	var cb_part_mr = null;

-	var cb_part_r = null;

-	if (obj.getAttribute('rtl') == 'false')

-	{

-		cb_part_l = obj.firstChild.firstChild;

-		cb_part_ml = obj.firstChild.lastChild;

-		cb_part_mr = obj.lastChild.firstChild;

-		cb_part_r = obj.lastChild.lastChild;

-

-		cb_flag = obj.firstChild.lastChild.firstChild;

-		if (cb_flag && cb_flag.isSameNode(obj.firstChild.firstChild.firstChild) == true)

-			cb_flag = null;

-	}

-	else

-	{

-		cb_part_l = obj.lastChild.lastChild;

-		cb_part_ml = obj.lastChild.firstChild;

-		cb_part_mr = obj.firstChild.lastChild;

-		cb_part_r = obj.firstChild.firstChild;

-

-		cb_flag = obj.lastChild.firstChild.lastChild;

-		if (cb_flag && cb_flag.isSameNode(obj.lastChild.lastChild.lastChild) == true)

-			cb_flag = null;

-	}

-	if (pr == 1)

-	{

-		skype_cb_l = cb_part_l.style.backgroundImage;//getAttribute('src');

-		skype_cb_m = cb_part_mr.style.backgroundImage;

-		skype_cb_r = cb_part_r.style.backgroundImage;//getAttribute('src');

-

-		if (isInternational == "0")

-		{

-			if (SkypeActiveCallButtonPart == 0)    //left

-			{

-				//obj.firstChild.firstChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_l.gif');

-				cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_l.gif')";

-				if (cb_part_l.isSameNode(cb_part_ml) != true)

-					cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-			}

-			else                            //right

-			{

-				//obj.firstChild.firstChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_l.gif');

-				cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_l.gif')";

-				if (cb_part_l.isSameNode(cb_part_ml) != true)

-					cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-				cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-				//obj.lastChild.lastChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif');

-				cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif')";

-			}

-		}

-		else

-		{

-			//obj.firstChild.firstChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_l.gif');

-			cb_part_l.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_l.gif')";

-			if (cb_part_l.isSameNode(cb_part_ml) != true)

-				cb_part_ml.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-			cb_part_mr.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_m.gif')";

-				//obj.lastChild.lastChild.setAttribute('src', 'chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif');

-			cb_part_r.style.backgroundImage = "url('chrome://skype_ff_toolbar_win/content/cb_down_r"+(isFax?"_fax":"")+".gif')";

-		}

-	}

-	else

-	{

-		//obj.firstChild.firstChild.setAttribute('src', skype_cb_l);

-		cb_part_l.style.backgroundImage = skype_cb_l;

-		if (cb_part_l.isSameNode(cb_part_ml) != true)

-			cb_part_ml.style.backgroundImage = skype_cb_m;

-		cb_part_mr.style.backgroundImage = skype_cb_m;

-		//obj.lastChild.lastChild.setAttribute('src', skype_cb_r);

-		cb_part_r.style.backgroundImage = skype_cb_r;

-	}

-}

-

-//COMMANDS

-function SkypeToolBarInit(tb)

-{

-	skype_tool = tb;

-}

-

-function doRunCMDSkype(event, link, id, name)

-{

-	if (skype_tool)

-	{

-		if (link == 'chdial')

-		{

-			var obj=event.originalTarget;

-			if (!obj)

-				obj=event;

-

-			/*var brd=SkypeGetBounds(obj);

-		   var docelem = document.documentElement;

-		   if ((docelem.scrollTop == 0 && document.body.scrollTop != 0) || (docelem.scrollLeft == 0 && document.body.scrollLeft != 0))

-			   docelem=document.body;

-   

-		   scrollY=docelem.scrollTop;

-		   scrollX=docelem.scrollLeft;

-   

-		   var my=brd.top+16, mx=brd.left;/*brd.height*/

-

-			//var oDoc = obj.ownerDocument;

-

-			/*var obj2 = document.getBoxObjectFor(element);

-   

-		   var html_box = new XPCNativeWrapper(obj2).wrappedJSObject;

-		   if (!html_box)

-			 html_box = obj2;

-   

-		   var screenX = html_box.screenX;

-		   var screenY = html_box.screenY;

-			   */

-

-			SkypeFlagColor='rgb(184, 203, 255)';

-			skype_tool.chprefix(id, document, obj, screenY);

-		}

-		else if (link == 'copy')

-			skype_tool.copy_num(id, document);

-		else if (link == 'sms')

-			skype_tool.sms(id);

-		else if (link == 'add')

-			skype_tool.add(id, name);

-		else

-			skype_tool.call(id);

-	}

-}

-

-function runCMDSkype(link)

-{

-	HideSkypeFull();

-	doRunCMDSkype(null, link, skype_curid, skype_cur_name);

-}

-

-//FLAG TOOLTIP

-function HideSkypeFull()

-{

-	//   skype_active=false;

-	document.getElementById('skype_dc').style.visibility = "hidden";

-}

-

-function ShowSkype(event, title)

-{

-	//  skype_active=true;

-	DoShowSkype(event.pageX, event.pageY + 20, title);

-}

-

-function DoShowSkype(cX, cY, title)

-{

-	var menu = document.getElementById('skype_dc');

-	menu.firstChild.nodeValue = title;

-	menu.style.visibility = "visible";

-

-	menu.style.left = cX + 'px';

-	menu.style.top = cY + 'px';

-

-}

-var SkypeFlagColor = 'rgb(184, 203, 255)';

-function doSkypeFlag(obj, brd)

-{

-	SkypeFlagColor = brd;

-}

-

-//MENU

-var skype_curid = 0,skype_active = false,skype_showseed = 0,skype_ctm = 0,skype_cur_name = '';

-var skype_curbutton = null;

-function SkypeCheckCallButton(obj)

-{

-	var res = false;

-	if (skype_curbutton && skype_curbutton.isSameNode(obj) == true)

-		res = true;

-

-	skype_curbutton = obj;

-	return res;

-}

-

-function HideSkypeMenu()

-{                       //skype_tool.sd('HideSkypeMenu skype_active='+skype_active);

-	if (!skype_active)

-		HideSkypeMenuFull();

-	else

-		setTimeout("HideSkypeMenu()", 1000);

-}

-

-function HideSkypeMenu2(event)

-{

-	skype_showseed = 0;

-	if (!skype_active)

-		HideSkypeMenuFull();

-	else

-	{

-		skype_active = false;

-		setTimeout("HideSkypeMenu()", 1000);

-	}

-}

-

-function HideSkypeMenuFull()

-{                                 //skype_tool.sd('HideSkypeMenuFull skype_active='+skype_active);

-	/*   skype_active=false;

-	document.getElementById('skype_menu').style.visibility="hidden";*/

-}

-

-function CheckSkype()

-{

-	skype_active = true;

-}

-

-function ShowSkypeMenu(event, call_msg, id, callto, isMobile, name, x, y)

-{

-	try {

-		/*  	skype_active=true;       						//skype_tool.sd('ShowSkypeMenu skype_curid='+skype_curid+'   callto='+callto+'  id='+id);

-		if(document.getElementById('skype_menu').style.visibility!="hidden" && skype_curid==callto)//id

-		  return;

-		skype_showseed=Math.random();

-		clearTimeout(skype_ctm);

-	  var obj=event.originalTarget;

-	  if (!obj)

-		  obj=event;

-  //  	var brd=SkypeGetBounds(obj);

-		//var pcx=brd.left, pcy=brd.top+16;/*brd.height;* /   //alert(pcx+'--'+pcy);

-  

-	  scrolls=SkypeGetDivScroll(obj);

-  

-		var pcx = x+scrolls.left, pcy = y+scrolls.top;

-  

-		skype_ctm=setTimeout('DoShowSkypeMenu(\''+call_msg+'\','+skype_showseed+',"'+callto+'",'+pcx+','+pcy+','+isMobile+',"'+name+'")',0);*/

-	} catch(e) {

-	}

-}

-

-function DoShowSkypeMenu(call_msg, seed, callto, pcx, pcy, isMobile, name)

-{

-	try {                                                        //skype_tool.sd('DoShowSkypeMenu seed='+seed+'   skype_showseed='+skype_showseed);

-		/*  	if(seed!=skype_showseed)

-		  return;

-		skype_showseed=0;

-		skype_curid=callto;

-	  skype_cur_name=name;

-		var menu=document.getElementById('skype_menu');

-  

-		var my=pcy, mx=pcx;

-  

-	  var menubox=document.getBoxObjectFor(menu);

-	  //var docelem = document.documentElement;

-									//alert(menubox.height);

-									//alert('doc h='+document.height + ' y='+my+' menu h='+menubox.height);

-	  var docH=document.height;

-	  if (docH < document.documentElement.clientHeight) docH=document.documentElement.clientHeight;

-	  if (docH < document.documentElement.scrollHeight) docH=document.documentElement.scrollHeight;

-	  if (docH < document.body.clientHeight) docH=document.body.clientHeight;

-	  if (docH < document.body.scrollHeight) docH=document.body.scrollHeight;

-	  if ((my + menubox.height) > docH)

-		  my=my - 16 - menubox.height;

-	  if (my < 0) my=0;

-  //    if (document.height != 0 && (my + menubox.height) > document.height && (my + menubox.height) > document.documentElement.scrollHeight)//docelem.clientHeight)

-		  //my=document.height - menubox.height;

-  

-	  var docW=document.width;

-	  if (docW < document.documentElement.clientWidth) docW=document.documentElement.clientWidth;

-	  if (docW < document.documentElement.scrollWidth) docW=document.documentElement.scrollWidth;

-	  if (docW < document.body.clientWidth) docW=document.body.clientWidth;

-	  if (docW < document.body.scrollWidth) docW=document.body.scrollWidth;

-	  if ((mx + menubox.width) > docW)

-		  mx=document.width - menubox.width;

-	  if (mx < 0) mx=0;

-  //	if (document.width != 0 && (mx + menubox.width) > document.width && (mx + menubox.width) > document.documentElement.scrollWidth)//docelem.clientWidth)

-  

-		menu.style.left=mx+'px';

-		menu.style.top=my+'px';

-  

-	  skype_tool.doFixMenu(menu, isMobile, document);

-  

-	  menu.style.visibility="visible";  */

-	} catch(e) {

-	}

-}

-

-function SkypeSetBgColor(obj, color)

-{

-	try {

-		obj.lastChild.style.backgroundColor = color;

-	} catch(e) {

-	}

-}

-

-//UTIL

-function SkypeGetBounds(element)

-{

-	try {

-		var left = element.left;

-		var top = element.top;

-		while (!(element.tagName.toLowerCase() == 'span' && element.getAttribute('id') == '__skype_highlight_id'))

-		{

-			element = element.parentNode;

-		}

-		left = element.offsetLeft;

-		top = element.offsetTop;

-		for (var parent = element.offsetParent; parent; parent = parent.offsetParent)

-		{

-			left += parent.offsetLeft;

-			top += parent.offsetTop;

-			if (parent.tagName.toLowerCase() == 'div')

-			{

-				left -= parent.scrollLeft;

-				top -= parent.scrollTop;

-			}

-		}

-

-

-		return {left: left, top: top, width: element.offsetWidth, height: element.offsetHeight};

-	} catch(e) {

-	}

-}

-

-function SkypeGetDivScroll(element)

-{

-	try {

-		var left = 0;

-		var top = 0;

-		while (!(element.tagName.toLowerCase() == 'span' && element.getAttribute('id') == '__skype_highlight_id'))

-		{

-			element = element.parentNode;

-		}

-

-		for (var parent = element.offsetParent; parent; parent = parent.offsetParent)

-		{

-			if (parent.tagName.toLowerCase() == 'div')

-			{

-				left -= parent.scrollLeft;

-				top -= parent.scrollTop;

-			}

-		}

-

-

-		return {left: left, top: top};

-	} catch(e) {

-	}

-}
\ No newline at end of file

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-instance-properties.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-instance-properties.png
deleted file mode 100644
index cca62c2..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/multi-instance-properties.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/open-resource-dialog.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/open-resource-dialog.png
deleted file mode 100644
index c8c52e6..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/open-resource-dialog.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install-details-wizard.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install-details-wizard.png
deleted file mode 100644
index 08e9967..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install-details-wizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install.png
deleted file mode 100644
index c8fd4a1..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2install.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2installwizard.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2installwizard.png
deleted file mode 100644
index 10198a3..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2installwizard.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2menu.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2menu.png
deleted file mode 100644
index b2f8e75..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2menu.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2repoprefs2.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2repoprefs2.png
deleted file mode 100644
index f61a80d..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2repoprefs2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2revert.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2revert.png
deleted file mode 100644
index db8a4c1..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2revert.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard1.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard1.png
deleted file mode 100644
index db40c26..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard1.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard2.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard2.png
deleted file mode 100644
index 6cdd07e..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/p2updatewizard2.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/proxy-settings-ui.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/proxy-settings-ui.png
deleted file mode 100644
index e77f108..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/proxy-settings-ui.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/quicksearch.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/quicksearch.png
deleted file mode 100644
index 49dd156..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/quicksearch.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/solarisx86.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/solarisx86.png
deleted file mode 100644
index 63c9604..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/solarisx86.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/switch-editors.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/switch-editors.png
deleted file mode 100644
index 8a62e84..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/switch-editors.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/sync-schedule.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/sync-schedule.png
deleted file mode 100644
index 9844107..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/sync-schedule.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-history.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-history.png
deleted file mode 100644
index 103186f..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/tag-history.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/textSelection.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/textSelection.png
deleted file mode 100644
index cf7b955..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/textSelection.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/welcomescale.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/welcomescale.png
deleted file mode 100644
index 6d337d5..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/welcomescale.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/wordinplace.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/wordinplace.png
deleted file mode 100644
index 2acd93e..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/wordinplace.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/images/workspaces-preference-page.png b/bundles/org.eclipse.platform.doc.user/whatsNew/images/workspaces-preference-page.png
deleted file mode 100644
index a4f7a4c..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/images/workspaces-preference-page.png
+++ /dev/null
Binary files differ

diff --git a/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html b/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
deleted file mode 100644
index 0b8d0a0..0000000
--- a/bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html
+++ /dev/null

@@ -1,426 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html lang="en">
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2009. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page.">
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="STYLESHEET" href="../book.css"  type="text/css">
-<style type="text/css">
-td {border-top: solid thin black;}
-img[alt] {background-color:#ffdddd;}
-tr {vertical-align: top;}
-</style>
-<title>Eclipse Platform What's New in 3.5</title>
-</head>
-
-<body>
-
-<h2>What's New in 3.5</h2>
-
-<p>Here are descriptions of some of the more interesting or significant changes 
-made to the Eclipse Platform for the 3.5 release of Eclipse. They are grouped into:</p>
-
-<ul>
-<li><a href="#Platform">Platform Changes</a></li>
-<li><a href="#Install">Install/Update Changes</a></li>
-<li><a href="#Text">Editor Changes</a></li>
-<li><a href="#TeamCVS">Team/CVS Changes</a></li>
-<li><a href="#Debug">Debug Changes</a></li>
-</ul>
-
-<p>
-Plug-in developers will also be interested in the corresponding 
-<a href="../../org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html">What's new</a>
-document in the plug-in developer's guide.
-</p>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table cellpadding="10" cellspacing="0" width="600">
-  <colgroup>
-  <col width="30%">
-  <col width="70%">
-  </colgroup>
-  <tbody>
-    <!-- ******************** Platform ********************** -->
-    <tr> 
-      <td colspan="2"><a name="Platform"></a> <div style="font-size: 20px; font-weight: bold;">Platform 
-          Changes</div></td>
-    </tr>
-
-  <tr id="cocoa">
-    <td width="30%" valign="top" align="left"><b>Eclipse on Cocoa</b></td>
-    <td width="70%" valign="top">32 and 64-bit OSX Cocoa have joined the line-up of supported configurations for which SWT and Eclipse are routinely
-	built. Cocoa is now a first class Eclipse configuration, including advanced libraries such as OpenGL for SWT. Cocoa replaces Carbon
-	as the primary toolkit for Eclipse and SWT on Mac.
-	<p>
-	  <img src="images/cocoa.png" alt="Eclipse on Cocoa">
-	</p>
-    </td>
-  </tr>
-
-  <tr id="solaris-x86"> 
-    <td width="30%" valign="top" align="left"><b>Solaris x86</b></td>
-    <td width="70%" valign="top">Solaris x86 has joined the line-up of supported configurations for which SWT and Eclipse are routinely built.
-		<p><img src="images/solarisx86.png" alt="Solaris x86"></p>
-	</td>
-  </tr>
-
-  <tr id="s390"> 
-    <td width="30%" valign="top" align="left"><b>Eclipse on s390 and s390x</b></td>
-    <td width="70%" valign="top">It's time to dust off that old mainframe in your basement, because Eclipse has
-    arrived on the s390 and s390x architectures. This new port is still early access, so give
-    it a spin and report any problems you encounter in bugzilla.
-	</td>
-  </tr>
-
-  <tr id="buttonorder">
-    <td width="30%" valign="top" align="left"><b>Alternate button order</b></td>
-    <td width="70%" valign="top">
-		On GTK, it is now possible to change the default button order for Eclipse.  
-		To have the <b>OK</b> button on the left, edit the ~/.gtkrc-2.0 file and include the line 
-		"gtk-alternative-button-order=1".
-		<p><img src="images/alternate.png" alt="Alternate button order"></p>
-	</td>
-  </tr>
-
-  <tr id="customize-perspective">
-    <td width="30%" valign="top" align="left"><b>Customize menus and toolbars</b></td>
-    <td width="70%" valign="top">The customize perspective dialog has been improved and
-      extended with new functionality. It can now be used to hide or show individual menu 
-      or toolbar items.
-      <p><img src="images/customize-perspective.png" alt="Customize Perspective dialog"></p>
-   </td>
-  </tr>
-
-  <tr id="multi-instance-properties">
-    <td width="30%" valign="top" align="left"><b>Multi-instance Properties view</b></td>
-    <td width="70%" valign="top">You can now pin the Properties view to a given selection.
-    This allows you to see the properties of a particular selection while 
-    having the freedom to select alternate items.
-    <p>You can now create new instances of the Properties view from an existing 
-    one. The existing one will be pinned to the contents it is currently 
-    displaying and the new view will be set to follow the workbench's 
-    selection.</p>
-    <p><img src="images/multi-instance-properties.png" alt="The Multi-instance Properties View"></p>
-    </td>
-  </tr>
-
-  <tr id="workspace-compare-editor-enhancements">
-    <td width="30%" valign="top" align="left"><b>Compare Editor enhancements</b></td>
-    <td width="70%" valign="top"> 
-    New features have been added to the Compare Editor:
-    <ul>
-    	<li>The <b>Go to Line</b> action added to the context menu allows for rapid navigation</li>
-    	<li>The current text selection will be used to populate the filter field of the <b>Open Type</b> and <b>Open Resource</b> dialogs</li>
-    	<li>The current line is now highlighted in each viewer</li>
-    	<li>Background and foreground color preferences are now honored</li>
-    	<li> The <b>Set Encoding...</b> action has been added to the context menu. 
-    	This allows you to change the encoding of each side of the comparison</li>
-   	</ul>
-    <p><img src="images/gotoLine.png" alt="Go to Line" ></p>
-    <p><img src="images/textSelection.png" alt="TextSelection" ></p>
-	</td>
-  </tr>
-
-    <TR id="compare-word">
-      <TD vAlign=top align=left width="30%"><B>Compare Word documents</B></TD>
-      <TD vAlign=top width="70%">Comparing Word document changes in Eclipse now
-        uses the Word compare support to show you the changes as revisions.
-        <P><IMG alt="Compare Word documents" 
-      src="images/wordinplace.png" ></p></TD>
-    </TR>
-
-  <tr id="workspace-compare-switch-viewer">
-    <td width="30%" valign="top" align="left"><b>Switching compare viewers</b></td>
-    <td width="70%" valign="top">The <b>Compare Editor</b> allows you to switch to 
-      optional merge viewers available for the compared content. For instance, while comparing 
-      two Java files, you can use the simple <b>Text Compare</b> viewer instead of the default <b>Java 
-      Source Compare</b>.
-      <p>You can also switch between content-specific merge viewers; 
-      for example when an alternative Java compare viewer is available, you can use it instead of the default one.</p>
-      <p><img src="images/contentMergeViewerSwitching.png" alt="Viewer switching" ></p>
-	</td>
-  </tr>
-
-  <tr id="open-resource-open-with">
-    <td width="30%" valign="top" align="left">
-        <b>Open Resource dialog allows choice of editor</b>
-    </td>
-    <td width="70%" valign="top">
-        The Open Resource dialog now allows you to open files with the the editor of your choice.
-        You can either choose the editor from the <b>Open With</b> context menu or
-        use the drop-down menu besides the <b>Open</b> button.
-        <p><img src="images/open-resource-dialog.png" alt="Open Resource dialog"></p>
-    </td>
-  </tr>
-
-  <tr id="switch-editors">
-    <td width="30%" valign="top" align="left">
-        <b>Switch editors and multi-page editors</b>
-    </td>
-    <td width="70%" valign="top">
-        Switching between open editors and multiple editor pages has been streamlined.
-        <b>Ctrl</b>+<b>PageDown</b> and <b>Ctrl</b>+<b>PageUp</b> now always activate the next or
-        previous editor tab, even in multi-page editors. To switch between pages of a multi-page
-        editor, use <b>Alt</b>+<b>PageDown</b> and <b>Alt</b>+<b>PageUp</b>.
-        <p><img src="images/switch-editors.png" alt="Multi-page editor (PDE manifest editor)"></p>
-    </td>
-  </tr>
-
-  <tr id="workspace_team-proxy-settings-ui">
-    <td width="30%" valign="top" align="left"><b>Improved Network Connections page</b></td>
-    <td width="70%" valign="top">
-	The <b>Network Connection</b> page has been changed to better show the current
-	proxy configuration. Now if you go to <b>Preferences &gt; General &gt; Network Connections</b>,
-	you are able to see and change Eclipse proxy settings as well as see 
-	settings provided by the operating system. If you want to use your browser
-	or Gnome settings, or you have your proxy configured using environmental variables on Linux, 
-	you can see them all in this new UI.
-    <p><img src="images/proxy-settings-ui.png" alt="New Proxy Settings UI" ></p>
-	</td>
-  </tr>
-
-  <tr id="workspaces_preference_page">
-    <td width="30%" valign="top" align="left"><b>Workspaces preference page</b></td>
-    <td width="70%" valign="top">A new preference page supports managing the startup prompt to select a
-    workspace: <b>General &gt; Startup and Shutdown &gt; Workspaces</b>. You can
-    enable or disable the prompt altogether (this setting used to be on 
-    <b>General &gt; Startup and Shutdown</b>) and specify the maximum number of
-    recent workspaces to be remembered. The page also lists the recently used
-    workspaces and allows you to remove unwanted workspaces from that list.
-    <p><img src="images/workspaces-preference-page.png" alt="The Workspaces preference page"></p></td>
-  </tr>
-
-  <tr id="platform-ui.cnf.gointo">
-    <td width="30%" valign="top" align="left"><b>Project Explorer improvements</b></td>
-    <td width="70%" valign="top">As a step in the campaign to bring
-    the <b>Project Explorer</b> up to parity with the <b>Package Explorer</b>, the
-    <b>Go Into</b> and <b>Go To</b> functionality has been added.  You can now
-    go into any folder/project/etc. and have that be the only contents of the <b>Project Explorer</b>.
-    <p><img src="images/cnf-gointo.png" alt="Showing the Project Explorer after Go Into selected" title="Go Into" border="1"></p>
-    </td>
-  </tr>
-
-      <!-- ******************** User Assistance ********************** -->
-
-  <tr id="customIcons">
-    <td width="30%" valign="top" align="left"><b>Custom icons in help system</b></td>
-    <td width="70%" valign="top">Custom icons can be specified for books and topics in the help system using
-	the &lt;tocIcon&gt; element in the <tt>org.eclipse.help.toc</tt> extension point. 
-      <p><img src="images/customicon.png" alt="table of contents"></p></td>
-  </tr>
-
-  <tr id="welcomeFont">
-    <td width="30%" valign="top" align="left"><b>Buttons to change font size in Welcome</b></td>
-    <td width="70%" valign="top">To improve accessibility two new buttons (a large and a small 'A') have been 
-    added above the welcome area which can be used to increase or decrease the font size on the welcome pages. 
-    <p><img src="images/welcomescale.png" alt="welcome page"></p></td>
-  </tr>
-
-  <tr id="abouthtml">
-    <td width="30%" valign="top" align="left"><b>About page in help system</b></td>
-    <td width="70%" valign="top">It is now possible to open a web page, about.html from 
-    the help system that shows plug-in version information. This makes it possible to determine 
-    the versions of plug-ins running in a Help infocenter.</td>
-  </tr>
-
-  <tr id="helpQuickSearch">
-    <td width="30%" valign="top" align="left"><b>Help quick search</b></td>
-    <td width="70%" valign="top">A search of the help system can be initiated with a  
-      scope limited to the selected book or topic.
-      <p> <img src="images/quicksearch.png" alt="help quick search"></p>
-    </td>
-  </tr>
-
-      <!-- ******************** Install/Update ********************** -->
-
-    <tr> 
-      <td colspan="2"><a name="Install"></a> <div style="font-size: 20px; font-weight: bold;">Install/Update Changes</div></td>
-    </tr>
-
-  <tr id="p2ui-software-updates">
-    <td width="30%" valign="top" align="left"><b>Software updates menu items</b></td>
-    <td width="70%" valign="top">New menu items have been added to the <b>Help</b> menu, allowing you to
-       invoke the most common software management tasks immediately.  Instead of launching a single updates dialog and navigating pages with
-       action buttons, you can now perform common tasks immediately from the <b>Help</b> menu.
-       <p> <img src="images/p2menu.png" alt="Software updates menu items in the Help menu" title="Software Updates Menu Items"></p>
-       <p>For example, you can now check for software updates in one step using <b>Help &gt; Check for Updates</b>.
-       This menu command will check for updates (in the foreground or background depending on your 
-       <b>General &gt; Always run in background</b> preference), and launch the software updates wizard if updates are available.</p>
-    </td>
-  </tr>
-
-  <tr id="p2ui-installing-new-software">
-    <td width="30%" valign="top" align="left"><b>Installing new software</b></td>
-    <td width="70%" valign="top">The <b>Available Software</b> page has been merged into the install wizard and
-       can be accessed using <b>Help &gt; Install New Software...</b>.   The same navigation features previously 
-       appearing in the <b>Available Software</b> page, such as filtering and viewing by site, category, or name, 
-       are now on the first page of the wizard.
-       <p> <img src="images/p2installwizard.png" alt="Available Software Page in the Install Wizard" title="Available Software Wizard Page"></p>
-       <p>Some of the most common workflow and usability complaints have also been addressed:</p>
-       <ul><li>The wizard will now open immediately without waiting to connect to any update sites.
-       This makes the view itself much more responsive once the wizard is opened.</li>
-       <li>A description field has been added to the page to show more information about the selected item.</li>
-       <li>You can now change many selections at once without computing the install results on each change.  Once 
-       you've selected the items to install, the <b>Next</b> button will take you to the review page.  If there
-       is an error or you otherwise want to change your selections, you can now go back and change the selections in the first
-       page, and the resulting changes won't be computed until you move forward again.</li>
-       </ul>
-    </td>
-  </tr>
-
-  <tr id="p2ui-install-from-new-site">
-    <td width="30%" valign="top" align="left"><b>Installing software from a new site</b></td>
-    <td width="70%" valign="top">The install wizard has been reorganized to make it simpler to
-       add a new site and install software from it.  You can add a new site by typing, pasting, or
-       dragging a URL link into the <b>Work with</b> combo box.  You can also use the <b>Add...</b> button
-       to add a site. Auto-completion on names and locations is supported when typing in the <b>Work with</b> field,
-       including completion of repositories that are currently disabled.
-       <p>Only the content for a newly added site will be shown, making it simpler to find
-       what you want to install.  You can also use the combo to change the filtering of the available software by any
-       site.  The wizard has also been streamlined by placing the links to other views closer to the
-       relevant information in the wizard.</p>
-       <p> <img src="images/p2install.png" alt="Available Software view in Install Wizard" title="Install Wizard"></p>
-       <p>A new checkbox at the bottom of the page lets you control whether all sites will be used when
-       searching for the new software's requirements, or whether only the site selected will be
-       consulted.  Previously, all sites were always used when gathering the requirements.</p>
-    </td>
-  </tr>
-
-  <tr id="p2ui-install-wizard">
-    <td width="30%" valign="top" align="left"><b>More detail in install wizards</b></td>
-    <td width="70%" valign="top">The wizards for installing, updating, and uninstalling software now provide
-       more detailed information about the software required to complete an operation.  For example, when you 
-       install a feature, you will see a list of the other features required that will also be installed.
-       <p> <img src="images/p2install-details-wizard.png" alt="Install wizard with detail" title="Install Wizard"></p>
-       <p>The update wizard has also been reorganized so that you can change your update selections
-       in a separate selection page.  When available updates are shown, the wizard will open directly
-       on the details page.</p>
-       <p> <img src="images/p2updatewizard1.png" alt="Update wizard detail" title="Update Wizard Detail Page"></p>
-       <p>From this page, use the wizard <b>&lt; Back</b> button to see all of the possible update proposals and
-       change the selections.</p>
-       <p> <img src="images/p2updatewizard2.png" alt="Update wizard with multiple proposals" title="Update Wizard Selection Page"></p>
-    </td>
-  </tr>
-
-  <tr id="p2ui-info-in-about">
-    <td width="30%" valign="top" align="left"><b>Installation information now appears in About</b></td>
-    <td width="70%" valign="top">The <b>Installed Software</b> and <b>Installation History</b> pages
-       have been moved into the new <b>Installation Details</b> dialog.  To access these pages, choose <b>Help&gt;About</b>
-       and press the <b>Installation Details</b> button. In addition, you can now expand the top level items in the 
-       <b>Installed Software</b> page to see what software each item requires. From the
-       <b>Installation History</b> page you can browse previous install configurations, and
-       <b>Revert</b> to previous configurations.
-       <p> <img src="images/p2revert.png" alt="Installation History page in Installation Information dialog" title="Installation History"></p>
-    </td>
-  </tr>
-
-  <tr id="p2ui-software-sites-preferences">
-    <td width="30%" valign="top" align="left"><b>Software sites preference page</b></td>
-    <td width="70%" valign="top">
-       The available sites for installing and updating software are now managed from 
-       a preference page (<b>Preferences &gt; Install/Update &gt; Available Software Sites</b>). 
-       To find a particular site quickly, you can sort by name, location, or enablement.  You can also use the filter field to filter the list of sites.
-	   
-	   <p>This preference page also allows you to define your own name for available
-	   software sites. Names can be defined when adding a new site, or edited from the available
-	   sites preference page. If you don't provide a name, the name defined by the site itself will be used.
-	   </p>
-       <p> <img src="images/p2repoprefs2.png" alt="Available Software Sites preference page" title="Available Software Sites"></p>
-    </td>
-  </tr>
-
-    <!-- ******************** Text ********************** -->
-    <tr> 
-      <td colspan="2"><a name="Text"></a> <div style="font-size: 20px; font-weight: bold;">Editor Changes</div>
-      <p>
-      <em>These changes apply to all textual editors in the SDK.</em></p></td>
-    </tr>
-
-  <tr id="block-selection-mode">
-    <td width="30%" valign="top" align="left">
-        <b>Block selection mode in textual editors</b>
-    </td>
-    <td width="70%" valign="top">
-    	Textual editors now support block (aka column or rectangular) selection mode:
-       <p> <img src="images/block-selection-mode.png" alt="Block selection in text editor"></p>
-       <p>To enable it either use <b>Alt+Shift+A</b> or activate the 'Editor Presentation' action set to get
-       		a tool bar button for toggling the block selection mode.</p>  
-    </td>
-  </tr>
-
-  <tr id="collapse-projection">
-    <td width="30%" valign="top" align="left">
-        <b>Double-click on folding line collapses the folding region</b>
-    </td>
-    <td width="70%" valign="top">
-        Double-click on the vertical folding line now collapses the folding region:
-       <p><img src="images/collapse-projection.png" alt="Double-click collapses the folding region" ></p>
-    </td>
-  </tr>
-
-    <!-- ******************* Team/CVS ******************** -->
-    <tr> 
-      <td colspan="2"><a name="TeamCVS"></a> <div style="font-size: 20px; font-weight: bold;">Team/CVS 
-          Changes</div></td>
-    </tr>
-
-    <TR id=tagHistory>
-      <TD vAlign=top align=left width="30%"><B>History in Tag Resources dialog</B></TD>
-      <TD vAlign=top width="70%">When tagging a project you can now choose a
-        previously used tag.
-        <P><IMG alt="The Tag Resources dialog with the history list" 
-      src="images/tag-history.png" ></p></TD>
-    </TR>
-
-    <TR id=applyPatch>
-      <TD vAlign=top align=left width="30%"><B>Apply patch in the Synchronize
-          view</B></TD>
-      <TD vAlign=top width="70%">You can now apply a patch directly in the Synchronize
-        view.
-        <P><IMG alt="Apply patch in the Synchronize view" 
-      src="images/apply-patch-syncview.png" ></p></TD>
-    </TR>
-
-  <tr id="workspace_sync-schedule">
-    <td width="30%" valign="top" align="left"><b>More options for synchronization scheduling</b></td>
-    <td width="70%" valign="top">New options are available in the Configure Synchronize Schedule dialog.
-    Synchronization can be started at a specified time, run once or repeated at selected intervals.
-    <p><img src="images/sync-schedule.png" alt="Synchronize schedule dialog" ></p></td>
-  </tr>
-
-    <!-- ******************** Debug ********************* -->
-    <tr> 
-      <td colspan="2"><a name="Debug"></a> <div style="font-size: 20px; font-weight: bold;">Debug 
-          Changes</div></td>
-    </tr>
-
-  <tr id="debug-view-breadcrumb">
-    <td align="left" valign="top" width="30%"><b>Debug view breadcrumb</b></td>
-    <td valign="top" width="70%">Debug view now offers a breadcrumb
-      which shows the current active debug context. The breadcrumb is
-      activated automatically when the Debug view is resized to show only one
-      line of text.
-      <p><img alt="Debug view Breadcrumb" title="Debug view Breadcrumb"
-      src="images/debug-breadcrumb-1.png"><br><br></p>
-      <p>Each element in the breadcrumb can be selected and actions can
-      be invoked through a context menu or keyboard short cuts.
-      </p>
-      <p><img alt="Debug Breadcrumb Popup Menu"
-      title="Debug Breadcrumb Popup Menu" src="images/debug-breadcrumb-2.png"><br><br>
-      </p>
-      <p>Finally, a drop-down menu allows navigating to a new
-      element and changing the active debug context.
-      </p>
-      <p><img alt="Debug view Breadcrumb Drop-Down"
-      title="Debug view Breadcrumb Drop-Down"
-      src="images/debug-breadcrumb-3.png"></p>
-    </td>
-  </tr>
-
-    <!-- ****************** END OF N&N TABLE ****************** -->
-  </tbody>
-</table>
-
-</body>
-</html>